Serenity BDD Report
Home > Requirements > Stufe5 > Basis > Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of isikcapabilitystatementstammdatenrolle (@encounter-search)
Report generated 01-09-2026 07:08

Feature: Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of isikcapabilitystatementstammdatenrolle (@encounter-search)

Feature Coverage By Scenario

Overview

Scenario: Precondition
Scenario: Read and Validation of the CapabilityStatement
Scenario Outline: Validation of the search parameter definitions in the CapabilityStatement (13 examples)
Scenario: Search for the encounter by ID
Scenario: Search for the Encounter by Count
Scenario: Search for the Encounter by Status and ID
Scenario: Search for the Encounter by Class and Patient
Scenario: Search for the Encounter by Type and Patient
Scenario: Search for the Encounter by Patient and Encounter ID
Scenario: Search for the Encounter by Account ID and Patient
Scenario: Search for the Encounter by Account Identifier
Scenario: Search for the Encounter by Admission Date with 'le' Modifier and Patient
Scenario: Search for the Encounter by Admission Date with 'gt' Modifier and Patient
Scenario: Negative Search for the Encounter by Admission Date and Patient
Scenario: Search for the Encounter by Admission Date with 'ge' und 'le' Modifiers and Patient
Scenario: Search for the Encounter by Admission Date with the Search parameter 'end-date' and Patient
Scenario: Search for the Encounter by Admission Date with the Search parameter 'date-start' and Patient
Scenario: Negative Search for the Encounter by Admission Date with the Search parameter 'date-start' and 'ge' Modifier and Patient
Scenario: Negative Search for the Encounter by Admission Date with the Search parameter 'end-date' and 'le' Modifier and Patient
Scenario: Search for the Encounter by Admission Date with both Search parameters 'date-start' and 'end-date' and Patient
Scenario: Search for the Encounter by Admission Identifier
Scenario: Search for the Encounter by identifier.system
Scenario: Search for the encounter by Location and Patient
Scenario: Search for the encounter by Service Provider and Patient
Scenario: Optional Search for the Encounter by Tag and ID
Scenario: Optional Search for the Encounter by Has and ID

Scenarios

Given the Test Description: "The system under test MUST find a previously created resource when searched using the parameter and return it in the search results (SEARCH)."

Given the Preconditions: - The Encounter-Read-In-Progress, Encounter-Read-Finished and Account-Read test cases must have been executed successfully beforehand.

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

And CapabilityStatement contains interaction "search-type" for resource "Encounter"

And CapabilityStatement contains definition of search parameter "{searchParamValue}" of type "{searchParamType}" for resource "Encounter"

Examples:

searchParamValuesearchParamType
_idtoken
_countnumber
identifiertoken
statustoken
classtoken
typetoken
patientreference
accountreference
datedate
date-startdate
end-datedate

Examples:

searchParamValuesearchParamType
_hasstring
_tagtoken

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

And FHIR current response body is a valid CORE resource and conforms to profile "https://hl7.org/fhir/StructureDefinition/Bundle"

And response bundle contains resource with ID "${data.encounter-read-in-progress-id}" with error message "The requested Encounter ${data.encounter-read-in-progress-id} is not contained in the response bundle."

When Get FHIR resource at "http://fhirserver/Encounter/?_count=2" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0 and entry.resource.count() {= 2' with error message 'The _count parameter was not applied as expected'

When Get FHIR resource at "http://fhirserver/Encounter/?status=in-progress&_id=${data.encounter-read-in-progress-id}" with content type "json"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath "entry.resource.all(status = 'in-progress')" with error message 'There are search results, but they do not fully match the search criteria'

And response bundle contains resource with ID "${data.encounter-read-in-progress-id}" with error message "The requested Encounter ${data.encounter-read-in-progress-id} is not contained in the response bundle."

When Get FHIR resource at "http://fhirserver/Encounter/?class=http://terminology.hl7.org/CodeSystem/v3-ActCode%7CIMP&patient=Patient/${data.patient-read-id}" with content type "json"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath "entry.resource.all(class.where(code = 'IMP' and system = 'http://terminology.hl7.org/CodeSystem/v3-ActCode').exists())" with error message 'There are search results, but they do not fully match the search criteria'

And response bundle contains resource with ID "${data.encounter-read-in-progress-id}" with error message "The requested Encounter ${data.encounter-read-in-progress-id} is not contained in the response bundle."

When Get FHIR resource at "http://fhirserver/Encounter/?type=http://fhir.de/CodeSystem/kontaktart-de%7Cnormalstationaer&patient=Patient/${data.patient-read-id}" with content type "json"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath "entry.resource.all(type.coding.where(code = 'normalstationaer' and system = 'http://fhir.de/CodeSystem/kontaktart-de').exists())" with error message 'There are search results, but they do not fully match the search criteria'

And response bundle contains resource with ID "${data.encounter-read-in-progress-id}" with error message "The requested Encounter ${data.encounter-read-in-progress-id} is not contained in the response bundle."

When Get FHIR resource at "http://fhirserver/Encounter/?patient=Patient/${data.patient-read-id}&_id=${data.encounter-read-in-progress-id}" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And element "subject" in all bundle resources references resource with ID "${data.patient-read-id}"

And response bundle contains resource with ID "${data.encounter-read-in-progress-id}" with error message "The requested Encounter ${data.encounter-read-in-progress-id} is not contained in the response bundle."

When Get FHIR resource at "http://fhirserver/Encounter/?account=${data.account-read-id}&patient=Patient/${data.account-read-patient-id}" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And element "account" in all bundle resources references resource with ID "${data.account-read-id}"

And response bundle contains resource with ID "${data.encounter-read-finished-id}" with error message "The requested Encounter ${data.encounter-read-finished-id} is not contained in the response bundle."

When Get FHIR resource at "http://fhirserver/Encounter/?account:identifier=${data.account-read-identifier-system}%7C${data.account-read-identifier-value}" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And element "account" in all bundle resources references resource with ID "${data.account-read-id}"

And response bundle contains resource with ID "${data.encounter-read-finished-id}" with error message "The requested Encounter ${data.encounter-read-finished-id} is not contained in the response bundle."

When Get FHIR resource at "http://fhirserver/Encounter/?date=le2050-01-01&patient=Patient/${data.patient-read-id}" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath "entry.resource.all(period.start {= @2050-01-01T23:59:59+01:00 or period.start.empty())" with error message 'There are search results, but they do not fully match the search criteria'

And response bundle contains resource with ID "${data.encounter-read-in-progress-id}" with error message "The requested Encounter ${data.encounter-read-in-progress-id} is not contained in the response bundle."

When Get FHIR resource at "http://fhirserver/Encounter/?date=gt1999-01-01&patient=Patient/${data.patient-read-id}" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath "entry.resource.all(period.end }= @1999-01-01T00:00:00+01:00 or period.end.empty())" with error message 'There are search results, but they do not fully match the search criteria'

And response bundle contains resource with ID "${data.encounter-read-in-progress-id}" with error message "The requested Encounter ${data.encounter-read-in-progress-id} is not contained in the response bundle."

When Get FHIR resource at "http://fhirserver/Encounter/?date=2026-01-05&patient=Patient/${data.patient-read-id}" with content type "xml"

And bundle does not contain resource "Encounter" with ID "${data.encounter-read-in-progress-id}" with error message "The requested encounter ${data.encounter-read-in-progress-id} must not be returned here"

When Get FHIR resource at "http://fhirserver/Encounter/?date=ge2026-01-05&date=le2026-01-14&patient=Patient/${data.patient-read-id}" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath "entry.resource.select((period.start.exists() and period.start } @2026-01-14T23:59:59+01:00) or (period.end.exists() and period.end { @2026-01-05T00:00:00+01:00)).allFalse()" with error message 'There are search results, but they do not fully match the search criteria'

When Get FHIR resource at "http://fhirserver/Encounter/?end-date=le2050-01-01&patient=Patient/${data.account-read-patient-id}" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath "entry.resource.all(period.end {= @2050-01-01T23:59:59+01:00)" with error message 'There are search results, but they do not fully match the search criteria'

And bundle does not contain resource "Encounter" with ID "${data.encounter-read-in-progress-id}" with error message "The requested encounter ${data.encounter-read-in-progress-id} must not be returned here."

And response bundle contains resource with ID "${data.encounter-read-finished-id}" with error message "The requested encounter ${data.encounter-read-finished-id} is not contained in the response bundle."

When Get FHIR resource at "http://fhirserver/Encounter/?date-start=ge1999-01-01&patient=Patient/${data.patient-read-id}" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath "entry.resource.all(period.start }= @1999-01-01T00:00:00+01:00)" with error message 'There are search results, but they do not fully match the search criteria'

And response bundle contains resource with ID "${data.encounter-read-in-progress-id}" with error message "The requested encounter ${data.encounter-read-in-progress-id} is not contained in the response bundle."

When Get FHIR resource at "http://fhirserver/Encounter/?date-start=ge2026-01-14&patient=Patient/${data.account-read-patient-id}" with content type "xml"

And bundle does not contain resource "Encounter" with ID "${data.encounter-read-in-progress-id}" with error message "The requested encounter ${data.encounter-read-in-progress-id} must not be returned here."

When Get FHIR resource at "http://fhirserver/Encounter/?end-date=le2026-01-05&patient=Patient/${data.account-read-patient-id}" with content type "xml"

And bundle does not contain resource "Encounter" with ID "${data.encounter-read-finished-id}" with error message "The requested encounter ${data.encounter-read-finished-id} must not be returned here."

When Get FHIR resource at "http://fhirserver/Encounter/?date-start=ge2026-01-05&end-date=le2026-01-14&patient=Patient/${data.account-read-patient-id}" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath "entry.resource.all(period.start } @2026-01-05T00:00:00+01:00 and period.end { @2026-01-14T23:59:59+01:00).allTrue()" with error message 'There are search results, but they do not fully match the search criteria'

And bundle does not contain resource "Encounter" with ID "${data.encounter-read-in-progress-id}" with error message "The requested encounter ${data.encounter-read-in-progress-id} must not be returned here."

And response bundle contains resource with ID "${data.encounter-read-finished-id}" with error message "The requested encounter ${data.encounter-read-finished-id} is not contained in the response bundle."

When Get FHIR resource at "http://fhirserver/Encounter/?identifier=${data.encounter-read-in-progress-identifier-system}%7C${data.encounter-read-in-progress-identifier-value}" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath "entry.resource.all(identifier.where(value = '${data.encounter-read-in-progress-identifier-value}' and system = '${data.encounter-read-in-progress-identifier-system}').exists())" with error message 'There are search results, but they do not fully match the search criteria'

When Get FHIR resource at "http://fhirserver/Encounter/?identifier=${data.encounter-read-in-progress-identifier-system}%7C" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath "entry.resource.all(identifier.where(system = '${data.encounter-read-in-progress-identifier-system}').exists())" with error message 'There are search results, but they do not fully match the search criteria'

When Get FHIR resource at "http://fhirserver/Encounter/?location=Location/${data.encounter-read-in-progress-location}&patient=Patient/${data.patient-read-id}" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath 'entry.resource.all(location.location.reference.replaceMatches("/_history/.+","").matches("\b${data.encounter-read-in-progress-location}$"))' with error message 'There are search results, but they do not fully match the search criteria'

And FHIR current response body is a valid CORE resource and conforms to profile "https://hl7.org/fhir/StructureDefinition/Bundle"

And Check if current response of resource "Encounter" is valid isik5 resource and conforms to profile "https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung"

When Get FHIR resource at "http://fhirserver/Encounter/?service-provider=${data.encounter-read-in-progress-service-provider}&patient=Patient/${data.patient-read-id}" with content type "json"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath 'entry.resource.all(serviceProvider.reference.replaceMatches("/_history/.+","").matches("\b${data.encounter-read-in-progress-service-provider}$"))' with error message 'There are search results, but they do not fully match the search criteria'

And response bundle contains resource with ID "${data.encounter-read-in-progress-id}" with error message "The requested Encounter ${data.encounter-read-in-progress-id} is not contained in the response bundle."

When Get FHIR resource at "http://fhirserver/Encounter/?_tag=${data.tag-system}%7C${data.tag-value}&_id=${data.encounter-read-in-progress-id}" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And FHIR current response body evaluates the FHIRPath "entry.resource.all(meta.tag.where(code='${data.tag-value}').exists())" with error message 'There are search results, but they do not fully match the search criteria'

And response bundle contains resource with ID "${data.encounter-read-in-progress-id}" with error message "The requested Encounter ${data.encounter-read-in-progress-id} is not contained in the response bundle."

When Get FHIR resource at "http://fhirserver/Encounter/?_id=${data.encounter-read-in-progress-id}&_has:Condition:encounter:code=${data.condition-read-active-code}" with content type "xml"

And FHIR current response body evaluates the FHIRPath 'entry.resource.count() } 0' with error message 'No search results were found'

And response bundle contains resource with ID "${data.encounter-read-in-progress-id}" with error message "The requested Encounter ${data.encounter-read-in-progress-id} is not contained in the response bundle."

Feature Coverage By Scenario

Test Outcomes

Test Performance

Key Statistics

Number of Scenarios 26 Total Duration 41s
Total Number of Test Cases 38 Fastest Test 284ms
Number of Manual Test Cases 0 Slowest Test 6s
Tests Started Sep 01, 2026 07:08:29 Average Execution Time 1s
Tests Finished Sep 01, 2026 07:09:11 Cumulative Test Time
(sum of all individual test durations)
41s

Automated Tests

feature Scenario Context Steps Started Total Duration Result
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Precondition 2 07:08:29 438ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Read and Validation of the CapabilityStatement 2 07:08:30 2s 526ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Validation of the search parameter definitions in the CapabilityStatement
13 passing test cases
1 07:08:32 8s 924ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the encounter by ID 3 07:08:41 747ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the Encounter by Count 2 07:08:42 509ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the Encounter by Status and ID 4 07:08:43 897ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the Encounter by Class and Patient 4 07:08:44 913ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the Encounter by Type and Patient 4 07:08:44 908ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the Encounter by Patient and Encounter ID 4 07:08:45 904ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the Encounter by Account ID and Patient 4 07:08:46 909ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the Encounter by Account Identifier 4 07:08:47 5s 923ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the Encounter by Admission Date with 'le' Modifier and Patient 4 07:08:53 945ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the Encounter by Admission Date with 'gt' Modifier and Patient 4 07:08:54 933ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Negative Search for the Encounter by Admission Date and Patient 2 07:08:55 472ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the Encounter by Admission Date with 'ge' und 'le' Modifiers and Patient 3 07:08:55 852ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the Encounter by Admission Date with the Search parameter 'end-date' and Patient 5 07:08:56 1s 142ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the Encounter by Admission Date with the Search parameter 'date-start' and Patient 4 07:08:57 922ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Negative Search for the Encounter by Admission Date with the Search parameter 'date-start' and 'ge' Modifier and Patient 2 07:08:58 475ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Negative Search for the Encounter by Admission Date with the Search parameter 'end-date' and 'le' Modifier and Patient 2 07:08:59 485ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the Encounter by Admission Date with both Search parameters 'date-start' and 'end-date' and Patient 5 07:08:59 1s 150ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the Encounter by Admission Identifier 3 07:09:01 822ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the Encounter by identifier.system 3 07:09:01 840ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the encounter by Location and Patient 5 07:09:02 6s 325ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Search for the encounter by Service Provider and Patient 4 07:09:09 906ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Optional Search for the Encounter by Tag and ID 4 07:09:09 920ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress, according to the definition of ISiKCapabilityStatementStammdatenRolle (@Encounter-Search) Optional Search for the Encounter by Has and ID 3 07:09:10 711ms 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 = 'search-type').exists()).exists()  Details
Read and Validation of the CapabilityStatement RBellog 0  Download Evidence
Read and Validation of the CapabilityStatement Evidence Report  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement INFO - rest.where(mode = 'server').resource.where(type = 'Encounter' and searchParam.where(name = '_id' and type = 'token').exists()).exists()  Details
Validation of the search parameter definitions in the CapabilityStatement RBellog 1  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement Evidence Report  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement INFO - rest.where(mode = 'server').resource.where(type = 'Encounter' and searchParam.where(name = '_count' and type = 'number').exists()).exists()  Details
Validation of the search parameter definitions in the CapabilityStatement RBellog 2  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement Evidence Report  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement INFO - rest.where(mode = 'server').resource.where(type = 'Encounter' and searchParam.where(name = 'identifier' and type = 'token').exists()).exists()  Details
Validation of the search parameter definitions in the CapabilityStatement RBellog 3  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement Evidence Report  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement INFO - rest.where(mode = 'server').resource.where(type = 'Encounter' and searchParam.where(name = 'status' and type = 'token').exists()).exists()  Details
Validation of the search parameter definitions in the CapabilityStatement RBellog 4  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement Evidence Report  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement INFO - rest.where(mode = 'server').resource.where(type = 'Encounter' and searchParam.where(name = 'class' and type = 'token').exists()).exists()  Details
Validation of the search parameter definitions in the CapabilityStatement RBellog 5  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement Evidence Report  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement INFO - rest.where(mode = 'server').resource.where(type = 'Encounter' and searchParam.where(name = 'type' and type = 'token').exists()).exists()  Details
Validation of the search parameter definitions in the CapabilityStatement RBellog 6  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement Evidence Report  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement INFO - rest.where(mode = 'server').resource.where(type = 'Encounter' and searchParam.where(name = 'patient' and type = 'reference').exists()).exists()  Details
Validation of the search parameter definitions in the CapabilityStatement RBellog 7  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement Evidence Report  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement INFO - rest.where(mode = 'server').resource.where(type = 'Encounter' and searchParam.where(name = 'account' and type = 'reference').exists()).exists()  Details
Validation of the search parameter definitions in the CapabilityStatement RBellog 8  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement Evidence Report  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement INFO - rest.where(mode = 'server').resource.where(type = 'Encounter' and searchParam.where(name = 'date' and type = 'date').exists()).exists()  Details
Validation of the search parameter definitions in the CapabilityStatement RBellog 9  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement Evidence Report  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement INFO - rest.where(mode = 'server').resource.where(type = 'Encounter' and searchParam.where(name = 'date-start' and type = 'date').exists()).exists()  Details
Validation of the search parameter definitions in the CapabilityStatement RBellog 10  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement Evidence Report  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement INFO - rest.where(mode = 'server').resource.where(type = 'Encounter' and searchParam.where(name = 'end-date' and type = 'date').exists()).exists()  Details
Validation of the search parameter definitions in the CapabilityStatement RBellog 11  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement Evidence Report  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement INFO - rest.where(mode = 'server').resource.where(type = 'Encounter' and searchParam.where(name = '_has' and type = 'string').exists()).exists()  Details
Validation of the search parameter definitions in the CapabilityStatement RBellog 12  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement Evidence Report  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement INFO - rest.where(mode = 'server').resource.where(type = 'Encounter' and searchParam.where(name = '_tag' and type = 'token').exists()).exists()  Details
Validation of the search parameter definitions in the CapabilityStatement RBellog 13  Download Evidence
Validation of the search parameter definitions in the CapabilityStatement Evidence Report  Download Evidence
Search for the encounter by ID INFO - None of the codings provided are in the value set 'DiagnosisRole' (http://hl7.org/fhir/ValueSet/diagnosis-role|4.0.1), and a coding is recommended to come from this value set) (codes = http://fhir.de/CodeSystem/KontaktDiagnoseProzedur#treatment-diagnosis)  Details
Search for the encounter by ID INFO - None of the codings provided are in the value set 'Admit source' (http://hl7.org/fhir/ValueSet/encounter-admit-source|4.0.1), and a coding is recommended to come from this value set) (codes = http://fhir.de/CodeSystem/dgkev/Aufnahmeanlass#E)  Details
Search for the encounter by ID WARN - Profile reference 'https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung' has not been checked because it is unknown  Details
Search for the encounter by ID WARN - Resource meta.profile differs from the passed profile for validation: meta.profile=[]; passed=https://hl7.org/fhir/StructureDefinition/Bundle  Details
Search for the encounter by ID INFO - entry.resource.where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-In-Progress-Example$')).count() = 1  Details
Search for the encounter by ID RBellog 0  Download Evidence
Search for the encounter by ID Evidence Report  Download Evidence
Search for the Encounter by Count INFO - entry.resource.count() > 0 and entry.resource.count() <= 2  Details
Search for the Encounter by Count RBellog 0  Download Evidence
Search for the Encounter by Count Evidence Report  Download Evidence
Search for the Encounter by Status and ID INFO - entry.resource.count() > 0  Details
Search for the Encounter by Status and ID INFO - entry.resource.all(status = 'in-progress')  Details
Search for the Encounter by Status and ID INFO - entry.resource.where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-In-Progress-Example$')).count() = 1  Details
Search for the Encounter by Status and ID RBellog 0  Download Evidence
Search for the Encounter by Status and ID Evidence Report  Download Evidence
Search for the Encounter by Class and Patient INFO - entry.resource.count() > 0  Details
Search for the Encounter by Class and Patient INFO - entry.resource.all(class.where(code = 'IMP' and system = 'http://terminology.hl7.org/CodeSystem/v3-ActCode').exists())  Details
Search for the Encounter by Class and Patient INFO - entry.resource.where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-In-Progress-Example$')).count() = 1  Details
Search for the Encounter by Class and Patient RBellog 0  Download Evidence
Search for the Encounter by Class and Patient Evidence Report  Download Evidence
Search for the Encounter by Type and Patient INFO - entry.resource.count() > 0  Details
Search for the Encounter by Type and Patient INFO - entry.resource.all(type.coding.where(code = 'normalstationaer' and system = 'http://fhir.de/CodeSystem/kontaktart-de').exists())  Details
Search for the Encounter by Type and Patient INFO - entry.resource.where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-In-Progress-Example$')).count() = 1  Details
Search for the Encounter by Type and Patient RBellog 0  Download Evidence
Search for the Encounter by Type and Patient Evidence Report  Download Evidence
Search for the Encounter by Patient and Encounter ID INFO - entry.resource.count() > 0  Details
Search for the Encounter by Patient and Encounter ID INFO - entry.resource.all(subject.reference.replaceMatches('/_history/.+','').matches('\\bPatient-Read-Example$'))  Details
Search for the Encounter by Patient and Encounter ID INFO - entry.resource.where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-In-Progress-Example$')).count() = 1  Details
Search for the Encounter by Patient and Encounter ID RBellog 0  Download Evidence
Search for the Encounter by Patient and Encounter ID Evidence Report  Download Evidence
Search for the Encounter by Account ID and Patient INFO - entry.resource.count() > 0  Details
Search for the Encounter by Account ID and Patient INFO - entry.resource.all(account.reference.replaceMatches('/_history/.+','').matches('\\bAccount-Read-Example$'))  Details
Search for the Encounter by Account ID and Patient INFO - entry.resource.where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-Finished-Example$')).count() = 1  Details
Search for the Encounter by Account ID and Patient RBellog 0  Download Evidence
Search for the Encounter by Account ID and Patient Evidence Report  Download Evidence
Search for the Encounter by Account Identifier INFO - entry.resource.count() > 0  Details
Search for the Encounter by Account Identifier INFO - entry.resource.all(account.reference.replaceMatches('/_history/.+','').matches('\\bAccount-Read-Example$'))  Details
Search for the Encounter by Account Identifier INFO - entry.resource.where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-Finished-Example$')).count() = 1  Details
Search for the Encounter by Account Identifier RBellog 0  Download Evidence
Search for the Encounter by Account Identifier Evidence Report  Download Evidence
Search for the Encounter by Admission Date with 'le' Modifier and Patient INFO - entry.resource.count() > 0  Details
Search for the Encounter by Admission Date with 'le' Modifier and Patient INFO - entry.resource.all(period.start <= @2050-01-01T23:59:59+01:00 or period.start.empty())  Details
Search for the Encounter by Admission Date with 'le' Modifier and Patient INFO - entry.resource.where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-In-Progress-Example$')).count() = 1  Details
Search for the Encounter by Admission Date with 'le' Modifier and Patient RBellog 0  Download Evidence
Search for the Encounter by Admission Date with 'le' Modifier and Patient Evidence Report  Download Evidence
Search for the Encounter by Admission Date with 'gt' Modifier and Patient INFO - entry.resource.count() > 0  Details
Search for the Encounter by Admission Date with 'gt' Modifier and Patient INFO - entry.resource.all(period.end >= @1999-01-01T00:00:00+01:00 or period.end.empty())  Details
Search for the Encounter by Admission Date with 'gt' Modifier and Patient INFO - entry.resource.where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-In-Progress-Example$')).count() = 1  Details
Search for the Encounter by Admission Date with 'gt' Modifier and Patient RBellog 0  Download Evidence
Search for the Encounter by Admission Date with 'gt' Modifier and Patient Evidence Report  Download Evidence
Negative Search for the Encounter by Admission Date and Patient INFO - entry.resource.ofType(Encounter).where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-In-Progress-Example$')).count() = 0  Details
Negative Search for the Encounter by Admission Date and Patient RBellog 0  Download Evidence
Negative Search for the Encounter by Admission Date and Patient Evidence Report  Download Evidence
Search for the Encounter by Admission Date with 'ge' und 'le' Modifiers and Patient INFO - entry.resource.count() > 0  Details
Search for the Encounter by Admission Date with 'ge' und 'le' Modifiers and Patient INFO - entry.resource.select((period.start.exists() and period.start > @2026-01-14T23:59:59+01:00) or (period.end.exists() and period.end < @2026-01-05T00:00:00+01:00)).allFalse()  Details
Search for the Encounter by Admission Date with 'ge' und 'le' Modifiers and Patient RBellog 0  Download Evidence
Search for the Encounter by Admission Date with 'ge' und 'le' Modifiers and Patient Evidence Report  Download Evidence
Search for the Encounter by Admission Date with the Search parameter 'end-date' and Patient INFO - entry.resource.count() > 0  Details
Search for the Encounter by Admission Date with the Search parameter 'end-date' and Patient INFO - entry.resource.all(period.end <= @2050-01-01T23:59:59+01:00)  Details
Search for the Encounter by Admission Date with the Search parameter 'end-date' and Patient INFO - entry.resource.ofType(Encounter).where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-In-Progress-Example$')).count() = 0  Details
Search for the Encounter by Admission Date with the Search parameter 'end-date' and Patient INFO - entry.resource.where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-Finished-Example$')).count() = 1  Details
Search for the Encounter by Admission Date with the Search parameter 'end-date' and Patient RBellog 0  Download Evidence
Search for the Encounter by Admission Date with the Search parameter 'end-date' and Patient Evidence Report  Download Evidence
Search for the Encounter by Admission Date with the Search parameter 'date-start' and Patient INFO - entry.resource.count() > 0  Details
Search for the Encounter by Admission Date with the Search parameter 'date-start' and Patient INFO - entry.resource.all(period.start >= @1999-01-01T00:00:00+01:00)  Details
Search for the Encounter by Admission Date with the Search parameter 'date-start' and Patient INFO - entry.resource.where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-In-Progress-Example$')).count() = 1  Details
Search for the Encounter by Admission Date with the Search parameter 'date-start' and Patient RBellog 0  Download Evidence
Search for the Encounter by Admission Date with the Search parameter 'date-start' and Patient Evidence Report  Download Evidence
Negative Search for the Encounter by Admission Date with the Search parameter 'date-start' and 'ge' Modifier and Patient INFO - entry.resource.ofType(Encounter).where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-In-Progress-Example$')).count() = 0  Details
Negative Search for the Encounter by Admission Date with the Search parameter 'date-start' and 'ge' Modifier and Patient RBellog 0  Download Evidence
Negative Search for the Encounter by Admission Date with the Search parameter 'date-start' and 'ge' Modifier and Patient Evidence Report  Download Evidence
Negative Search for the Encounter by Admission Date with the Search parameter 'end-date' and 'le' Modifier and Patient INFO - entry.resource.ofType(Encounter).where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-Finished-Example$')).count() = 0  Details
Negative Search for the Encounter by Admission Date with the Search parameter 'end-date' and 'le' Modifier and Patient RBellog 0  Download Evidence
Negative Search for the Encounter by Admission Date with the Search parameter 'end-date' and 'le' Modifier and Patient Evidence Report  Download Evidence
Search for the Encounter by Admission Date with both Search parameters 'date-start' and 'end-date' and Patient INFO - entry.resource.count() > 0  Details
Search for the Encounter by Admission Date with both Search parameters 'date-start' and 'end-date' and Patient INFO - entry.resource.all(period.start > @2026-01-05T00:00:00+01:00 and period.end < @2026-01-14T23:59:59+01:00).allTrue()  Details
Search for the Encounter by Admission Date with both Search parameters 'date-start' and 'end-date' and Patient INFO - entry.resource.ofType(Encounter).where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-In-Progress-Example$')).count() = 0  Details
Search for the Encounter by Admission Date with both Search parameters 'date-start' and 'end-date' and Patient INFO - entry.resource.where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-Finished-Example$')).count() = 1  Details
Search for the Encounter by Admission Date with both Search parameters 'date-start' and 'end-date' and Patient RBellog 0  Download Evidence
Search for the Encounter by Admission Date with both Search parameters 'date-start' and 'end-date' and Patient Evidence Report  Download Evidence
Search for the Encounter by Admission Identifier INFO - entry.resource.count() > 0  Details
Search for the Encounter by Admission Identifier INFO - entry.resource.all(identifier.where(value = '0123456789' and system = 'https://test.krankenhaus.de/fhir/sid/fallnr').exists())  Details
Search for the Encounter by Admission Identifier RBellog 0  Download Evidence
Search for the Encounter by Admission Identifier Evidence Report  Download Evidence
Search for the Encounter by identifier.system INFO - entry.resource.count() > 0  Details
Search for the Encounter by identifier.system INFO - entry.resource.all(identifier.where(system = 'https://test.krankenhaus.de/fhir/sid/fallnr').exists())  Details
Search for the Encounter by identifier.system RBellog 0  Download Evidence
Search for the Encounter by identifier.system Evidence Report  Download Evidence
Search for the encounter by Location and Patient INFO - entry.resource.count() > 0  Details
Search for the encounter by Location and Patient INFO - entry.resource.all(location.location.reference.replaceMatches("/_history/.+","").matches("\\bLocation-Read-Example$"))  Details
Search for the encounter by Location and Patient INFO - None of the codings provided are in the value set 'Admit source' (http://hl7.org/fhir/ValueSet/encounter-admit-source|4.0.1), and a coding is recommended to come from this value set) (codes = http://fhir.de/CodeSystem/dgkev/Aufnahmeanlass#E)  Details
Search for the encounter by Location and Patient WARN - Profile reference 'https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung' has not been checked because it is unknown  Details
Search for the encounter by Location and Patient INFO - None of the codings provided are in the value set 'DiagnosisRole' (http://hl7.org/fhir/ValueSet/diagnosis-role|4.0.1), and a coding is recommended to come from this value set) (codes = http://fhir.de/CodeSystem/KontaktDiagnoseProzedur#treatment-diagnosis)  Details
Search for the encounter by Location and Patient INFO - None of the codings provided are in the value set 'Admit source' (http://hl7.org/fhir/ValueSet/encounter-admit-source|4.0.1), and a coding is recommended to come from this value set) (codes = http://fhir.de/CodeSystem/dgkev/Aufnahmeanlass#E)  Details
Search for the encounter by Location and Patient WARN - Profile reference 'https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung' has not been checked because it is unknown  Details
Search for the encounter by Location and Patient WARN - Resource meta.profile differs from the passed profile for validation: meta.profile=[]; passed=https://hl7.org/fhir/StructureDefinition/Bundle  Details
Search for the encounter by Location and Patient INFO - This element does not match any known slice defined in the profile https://gematik.de/fhir/isik/StructureDefinition/ISiKKontaktGesundheitseinrichtung|5.1.2  Details
Search for the encounter by Location and Patient RBellog 0  Download Evidence
Search for the encounter by Location and Patient Evidence Report  Download Evidence
Search for the encounter by Service Provider and Patient INFO - entry.resource.count() > 0  Details
Search for the encounter by Service Provider and Patient INFO - entry.resource.all(serviceProvider.reference.replaceMatches("/_history/.+","").matches("\\bOrganization/Organization-Read-Example$"))  Details
Search for the encounter by Service Provider and Patient INFO - entry.resource.where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-In-Progress-Example$')).count() = 1  Details
Search for the encounter by Service Provider and Patient RBellog 0  Download Evidence
Search for the encounter by Service Provider and Patient Evidence Report  Download Evidence
Optional Search for the Encounter by Tag and ID INFO - entry.resource.count() > 0  Details
Optional Search for the Encounter by Tag and ID INFO - entry.resource.all(meta.tag.where(code='external').exists())  Details
Optional Search for the Encounter by Tag and ID INFO - entry.resource.where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-In-Progress-Example$')).count() = 1  Details
Optional Search for the Encounter by Tag and ID RBellog 0  Download Evidence
Optional Search for the Encounter by Tag and ID Evidence Report  Download Evidence
Optional Search for the Encounter by Has and ID INFO - entry.resource.count() > 0  Details
Optional Search for the Encounter by Has and ID INFO - entry.resource.where(id.replaceMatches('/_history/.+','').matches('\\bEncounter-Read-In-Progress-Example$')).count() = 1  Details
Optional Search for the Encounter by Has and ID RBellog 0  Download Evidence
Optional Search for the Encounter by Has and ID Evidence Report  Download Evidence
Serenity BDD version 5.3.10