Serenity BDD Report
Report generated 01-09-2026 07:02

Read Information From A Resource Of Type Condition With Status "Active" (@condition-Read-Active)

  Mandatory   Basis   1 To 10 Seconds (Duration)   Stufe5

Read and Validate active Condition by its ID
Steps Outcome
When Get FHIR resource at "http://fhirserver/Condition/${data.condition-read-active-id}" with content type "xml"
SUCCESS 256ms
And FHIR current response body is a valid isik5 resource and conforms to profile "https://gematik.de/fhir/isik/StructureDefinition/ISiKDiagnose"
SUCCESS 229ms
And resource has ID "Condition-Read-Active-Example" with error message "The ID does not match the expected value"
SUCCESS 239ms
And FHIR current response body evaluates the FHIRPath "code.coding.where(system = 'http://fhir.de/CodeSystem/bfarm/icd-10-gm' and code = 'J06.9' and version = '2026.0.0').exists()" with error message "The Condition code is missing or a required value is absent"
SUCCESS 210ms
And element "subject" references resource with ID "Patient-Read-Example" with error message "The referenced case does not match the expected value."
SUCCESS 205ms
And FHIR current response body evaluates the FHIRPath "clinicalStatus.coding.where(system = 'http://terminology.hl7.org/CodeSystem/condition-clinical' and code = 'active').exists()" with error message "The Clinical status does not have the value 'active'"
SUCCESS 205ms
And FHIR current response body evaluates the FHIRPath 'recordedDate.toString().contains("2021-02-12")' with error message 'The documentation date does not contain the expected value'
SUCCESS 205ms
And FHIR current response body evaluates the FHIRPath 'note.text = "Test note"' with error message 'The note does not match the expected value'
SUCCESS 205ms
And FHIR current response body evaluates the FHIRPath "bodySite.coding.where(system = 'http://snomed.info/sct' and version = 'http://snomed.info/sct/11000274103/version/20251115' and code = '49076000').exists()" with error message 'The body site code does not match the expected value'
SUCCESS 206ms
And TGR the custom failure message is set to "The related condition does not match the expected url"
SUCCESS 205ms
And TGR current response with attribute "$.body.Condition.extension.url" matches "http://hl7.org/fhir/StructureDefinition/condition-related"
SUCCESS 204ms
And TGR the custom failure message is set to "The related condition does not match the expected reference value"
SUCCESS 204ms
And TGR current response with attribute "$.body.Condition.extension.valueReference.reference.value" matches "Condition/Condition-Read-Resolved-Example"
SUCCESS 204ms
And TGR the custom failure message is set to "The onsetAge system field does not match the expected value."
SUCCESS 204ms
And TGR current response with attribute "$.body.Condition.onsetAge.system.value" matches "http://unitsofmeasure.org"
SUCCESS 204ms
And TGR the custom failure message is set to "The onsetAge unit field does not match the expected value."
SUCCESS 204ms
And TGR current response with attribute "$.body.Condition.onsetAge.unit.value" matches "years"
SUCCESS 204ms
And TGR the custom failure message is set to "The onsetAge value field was not found."
SUCCESS 205ms
And TGR current response contains node "$.body.Condition.onsetAge.value.value"  RBellog 0  Evidence Report
SUCCESS 210ms
SUCCESS 4.03s
Serenity BDD version 5.3.10