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 Account-Read test case 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 "Account"
And CapabilityStatement contains definition of search parameter "{searchParamValue}" of type "{searchParamType}" for resource "Account"
When Get FHIR resource at "http://fhirserver/Account/?_id=${data.account-read-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.account-read-id}" with error message "The requested Account ${data.account-read-id} is not contained in the response bundle."
When Get FHIR resource at "http://fhirserver/Account/?_tag=${data.tag-system}%7C${data.tag-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(meta.tag.where(code='${data.tag-value}').exists())" with error message 'There are search results, but they do not fully match the search criteria'
When Get FHIR resource at "http://fhirserver/Account/?_count" with content type "xml"
And FHIR current response body evaluates the FHIRPath 'total } 0 and 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.account-read-identifier-value}' and system = '${data.account-read-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/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 FHIR current response body evaluates the FHIRPath "entry.resource.all(identifier.where(value = '${data.account-read-identifier-value}' and system = '${data.account-read-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/Account/?status=active" 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.where(status = 'active').exists()" with error message 'There are search results, but they do not fully match the search criteria'
When Get FHIR resource at "http://fhirserver/Account/?type=IMP" 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='IMP').exists())" with error message 'There are search results, but they do not fully match the search criteria'
When Get FHIR resource at "http://fhirserver/Account/?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 "subject" in all bundle resources references resource with ID "${data.account-read-patient-id}" with error message 'There are search results, but they do not fully match the search criteria'
| Number of Scenarios | 9 | Total Duration | 8s |
| Total Number of Test Cases | 14 | Fastest Test | 210ms |
| Number of Manual Test Cases | 0 | Slowest Test | 1s |
| Tests Started | März 23, 2026 09:41:16 | Average Execution Time | 604ms |
| Tests Finished | März 23, 2026 09:41:25 | Total Execution Time | 8s |
| feature | Scenario | Context | Steps | Started | Total Duration | Result |
|---|---|---|---|---|---|---|
| Testing search parameters against a resource of type Account (@Account-Search) | Precondition | 2 | 09:41:16 | 428ms | ||
| Testing search parameters against a resource of type Account (@Account-Search) | Read and Validation of the CapabilityStatement | 2 | 09:41:17 | 735ms | ||
| Testing search parameters against a resource of type Account (@Account-Search) |
Validation of the search parameter definitions in the CapabilityStatement
6 passing test cases |
1 | 09:41:18 | 1s 369ms | ||
| Testing search parameters against a resource of type Account (@Account-Search) | Search for the Account by ID | 3 | 09:41:19 | 905ms | ||
| Testing search parameters against a resource of type Account (@Account-Search) | Search for the Account by Tag | 3 | ||||
| Testing search parameters against a resource of type Account (@Account-Search) | Search for the Account by Count | 3 | 09:41:20 | 917ms | ||
| Testing search parameters against a resource of type Account (@Account-Search) | Search for the Account by Identifier | 3 | 09:41:21 | 958ms | ||
| Testing search parameters against a resource of type Account (@Account-Search) | Search for the Account by Status | 3 | 09:41:22 | 999ms | ||
| Testing search parameters against a resource of type Account (@Account-Search) | Search for the Account by Type | 3 | 09:41:23 | 1s 212ms | ||
| Testing search parameters against a resource of type Account (@Account-Search) | Search for the Account by Patient | 3 | 09:41:24 | 952ms |