Serenity BDD Report
Home > Requirements > Stufe5 > Basis > Read information from a resource of type encounter with status "planned" (@encounter-read-planned)
Report generated 01-09-2026 07:01

Feature: Read information from a resource of type encounter with status "planned" (@encounter-read-planned)

Scenarios

Given the Test Description: "The system under test must return the complete resource in response to an HTTP GET request to its URL (READ)."

Given the Preconditions: - The Patient-Read test case must have been executed successfully beforehand.

  • The test dataset must have been entered in the system under the specifications (manually).
  • The ID of the corresponding FHIR resource for this test dataset and the assigned facility-internal admission number must be stored in the configuration variable 'encounter-read-planned-id'.

Create an Encounter resource with these fields:

  • Admission number: a valid admission number assigned by the system (Please, set them in the configuration variables 'encounter-read-planned-identifier-system' and 'encounter-read-planned-identifier-value')
  • Status: planned
  • Type: inpatient (normalstationaer)
  • Subject: Reference to the patient from the Patient-Read test case
  • Admission reason: referral by a doctor
  • Department: General Surgery
  • Location (display): Surgery Department
  • Service provider (display): Hospital
  • Service provider ID (value): any (Please, set it in the configuration variable 'encounter-read-planned-serviceprovider-identifier-value')
  • Planned start: 2026-02-12
  • (Optional) Tag: Value defined through the configuration variables 'tag-value' and 'tag-system'

When Get FHIR resource at "http://fhirserver/metadata" with content type "json"

And CapabilityStatement contains interaction "read" for resource "Encounter"

When Get FHIR resource at "http://fhirserver/Encounter/${data.encounter-read-planned-id}" with content type "xml"

And FHIR current response body is a valid isik5 resource and conforms to profile "https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung"

And resource has ID "${data.encounter-read-planned-id}" with error message "The returned Encounter resource has not the expected ID"

And TGR current response with attribute "$..status.value" matches "planned"

And FHIR current response body evaluates the FHIRPath "identifier.where(system = '${data.encounter-read-planned-identifier-system}' and value='${data.encounter-read-planned-identifier-value}').exists()" with error message 'The Encounter does not contain the correct admission number'

And FHIR current response body evaluates the FHIRPath "class.where(code = 'IMP' and system = 'http://terminology.hl7.org/CodeSystem/v3-ActCode').exists()" with error message 'The Encounter does not contain the correct class code'

And FHIR current response body evaluates the FHIRPath "type.coding.where(code = 'normalstationaer' and system = 'http://fhir.de/CodeSystem/kontaktart-de').exists()" with error message 'The Encounter does not contain the correct type'

And FHIR current response body evaluates the FHIRPath "serviceType.coding.where(code = '1500' and system = 'http://fhir.de/CodeSystem/dkgev/Fachabteilungsschluessel').exists()" with error message 'The Encounter does not contain the correct department code'

And element "subject" references resource with ID "${data.patient-read-id}" with error message "The referenced Patient does not match the expected value"

And FHIR current response body evaluates the FHIRPath "hospitalization.admitSource.coding.where(code = 'E' and system = 'http://fhir.de/CodeSystem/dgkev/Aufnahmeanlass').exists()" with error message 'The encounter does not contain the correct admission reason'

And FHIR current response body evaluates the FHIRPath "location.location.exists(display = 'Surgery Department')" with error message 'The location display value does not match the expected value'

And FHIR current response body evaluates the FHIRPath "serviceProvider.display = 'Hospital'" with error message 'The service provider display value does not match the expected value'

And FHIR current response body evaluates the FHIRPath "serviceProvider.identifier.value = '${data.encounter-read-planned-serviceprovider-identifier-value}'" with error message 'The service provider identifier value does not match the expected value'

And FHIR current response body evaluates the FHIRPath "period.exists().not()" with error message 'A planned Encounter should not contain a period (time range).'

And FHIR current response body evaluates the FHIRPath "extension.where(url = 'http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedStartDate' and value.toString().contains('2026-02-12')).exists()" with error message 'The planned start date is missing'

Feature Coverage By Scenario

Test Outcomes

Test Performance

Key Statistics

Number of Scenarios 3 Total Duration 5s
Total Number of Test Cases 3 Fastest Test 421ms
Number of Manual Test Cases 0 Slowest Test 3s
Tests Started Sep 01, 2026 07:01:50 Average Execution Time 1s
Tests Finished Sep 01, 2026 07:01:56 Cumulative Test Time
(sum of all individual test durations)
5s

Automated Tests

feature Scenario Context Steps Started Total Duration Result
Read Information from a resource of type Encounter with status "planned" (@Encounter-Read-Planned) Precondition 2 07:01:50 421ms SUCCESS
Read Information from a resource of type Encounter with status "planned" (@Encounter-Read-Planned) Read and Validation of the CapabilityStatement 2 07:01:51 2s 301ms SUCCESS
Read Information from a resource of type Encounter with status "planned" (@Encounter-Read-Planned) Read and Validate planned Encounter by its ID 15 07:01:53 3s 191ms SUCCESS

Manual Tests

No manual tests were recorded

Evidence

Scenario Title Details
Precondition RBellog 0  Download Evidence
Read and Validation of the CapabilityStatement INFO - rest.where(mode = 'server').resource.where(type = 'Encounter' and interaction.where(code = 'read').exists()).exists()  Details
Read and Validation of the CapabilityStatement RBellog 0  Download Evidence
Read and Validation of the CapabilityStatement Evidence Report  Download Evidence
Read and Validate planned Encounter by its ID INFO - This element does not match any known slice defined in the profile https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung|5.1.2  Details
Read and Validate planned Encounter by its ID INFO - id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-Planned-Example$')  Details
Read and Validate planned Encounter by its ID INFO - identifier.where(system = 'https://test.krankenhaus.de/fhir/sid/fallnr' and value='0123456789').exists()  Details
Read and Validate planned Encounter by its ID INFO - class.where(code = 'IMP' and system = 'http://terminology.hl7.org/CodeSystem/v3-ActCode').exists()  Details
Read and Validate planned Encounter by its ID INFO - type.coding.where(code = 'normalstationaer' and system = 'http://fhir.de/CodeSystem/kontaktart-de').exists()  Details
Read and Validate planned Encounter by its ID INFO - serviceType.coding.where(code = '1500' and system = 'http://fhir.de/CodeSystem/dkgev/Fachabteilungsschluessel').exists()  Details
Read and Validate planned Encounter by its ID INFO - subject.reference.replaceMatches('/_history/.+','').matches('\\bPatient-Read-Example$')  Details
Read and Validate planned Encounter by its ID INFO - hospitalization.admitSource.coding.where(code = 'E' and system = 'http://fhir.de/CodeSystem/dgkev/Aufnahmeanlass').exists()  Details
Read and Validate planned Encounter by its ID INFO - location.location.exists(display = 'Surgery Department')  Details
Read and Validate planned Encounter by its ID INFO - serviceProvider.display = 'Hospital'  Details
Read and Validate planned Encounter by its ID INFO - serviceProvider.identifier.value = '123456789'  Details
Read and Validate planned Encounter by its ID INFO - period.exists().not()  Details
Read and Validate planned Encounter by its ID INFO - extension.where(url = 'http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedStartDate' and value.toString().contains('2026-02-12')).exists()  Details
Read and Validate planned Encounter by its ID RBellog 0  Download Evidence
Read and Validate planned Encounter by its ID Evidence Report  Download Evidence
Serenity BDD version 5.3.10