Serenity BDD Report
Home > Duration Under 1 Second
Report generated 23-03-2026 09:42:05

Duration Under 1 Second

252 tests |

Note that results include data-driven scenarios containing tests , which may also contain results other than tests .

Key Statistics

Number of Scenarios 155
Total Number of Test Cases 252
Tests Started März 23, 2026 09:36:19
Tests Finished März 23, 2026 09:41:56
Total Duration 5m 37s
Fastest Test 209ms
Slowest Test 999ms
Average Execution Time 520ms
Total Execution Time 2m 11s

Test Outcomes

Test Performance

Functional Coverage Overview

Features

Tags

Terminplanung   60 Appointment-Book   2 Coverage-Read-Statutory   1 Coverage-Search-Private   9 Binary-Read   2 Procedure-Read   2 Relatedperson-Read   2 Account-Read   2 Documentreference-Post   2 Condition-Read-Resolved   2 Appointment-Book-By-Schedule   1 Healthcareservice-Search   11 Dokumentenaustausch   20 Composition-Post   1 Relatedperson-Search   6 Documentreference-Search   16 Healthcareservice-Read   2 Stufe5   252 Valueset-Search   12 Encounter-Appointment-Read   2 Encounter-Read-Finished   2 Slot-Read   2 Slot-Search   11 Condition-Read-Active   2 Procedure-Search   17 Basis   172 Account-Search   13 Practitioner-Search   10 Patient-Search   25 Patient-Read   2 Schedule-Search   8 Mandatory   252 Encounter-Read-In-Progress   2 Coverage-Read-Private   2 Documentreference-Read   2 Schedule-Read   2 Precondition   39 Encounter-Read-Planned   2 Condition-Search   13 Practitioner-Read   2 Patient-Read-Extended   1 Appointment-Read   2 Appointment-Search   17 Coverage-Search-Statutory   11 Encounter-Search   27 Valueset-Read   2

Functional Coverage Details

Features

Feature Test Cases Scenarios % Pass Result Coverage
Stufe5/ basis > Read Information from a resource of type Account (@Account-Read) 2 2 100%
Stufe5/ basis > Testing search parameters against a resource of type Account (@Account-Search) 8 13 423%
Stufe5/ basis > Read Information from a resource of type Binary (@Binary-Read) 2 2 100%
Stufe5/ basis > Upload of a Document Bundle with POST Operation (@Composition-Post) 1 1 100%
Stufe5/ basis > Read Information from a resource of type Condition with status "active" (@Condition-Read-Active) 2 2 100%
Stufe5/ basis > Read Information from a resource of type Condition with status "resolved" (@Condition-Read-Resolved) 2 2 100%
Stufe5/ basis > Testing search parameters against a resource of type Condition (@Condition-Search) 7 13 723%
Stufe5/ basis > Read Information from a resource of type "private" Coverage (@Coverage-Read-Private) 2 2 100%
Stufe5/ basis > Read Information from a resource of type "statutory" Coverage (@Coverage-Read-Statutory) 1 1 100%
Stufe5/ basis > Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) 3 9 522%
Stufe5/ basis > Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) 6 11 609%
Stufe5/ basis > Read Information from a resource of type Encounter with status "finished" (@Encounter-Read-Finished) 2 2 100%
Stufe5/ basis > Read Information from a resource of type Encounter with status "in progress" (@Encounter-Read-In-Progress) 2 2 100%
Stufe5/ basis > Read Information from a resource of type Encounter with status "planned" (@Encounter-Read-Planned) 2 2 100%
Stufe5/ basis > Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) 15 27 774%
Stufe5/ basis > Read Information from a resource of type Patient (@Patient-Read) 2 2 100%
Stufe5/ basis > Read extended Information from a resource of type Patient (@Patient-Read-Extended) 1 1 100%
Stufe5/ basis > Testing search parameters against a resource of type Patient (@Patient-Search) 12 25 940%
Stufe5/ basis > Read Information from a resource of type Practitioner (@Practitioner-Read) 2 2 100%
Stufe5/ basis > Testing search parameters against a resource of type Practitioner (@Practitioner-Search) 6 10 580%
Stufe5/ basis > Read Information from a resource of type Procedure (@Procedure-Read) 2 2 100%
Stufe5/ basis > Testing search parameters against a resource of type Procedure (@Procedure-Search) 9 17 641%
Stufe5/ basis > Read Information from a resource of type RelatedPerson (@RelatedPerson-Read) 2 2 100%
Stufe5/ basis > Testing search parameters against a resource of type RelatedPerson (@RelatedPerson-Search) 4 6 433%
Stufe5/ basis > Read Information from a resource of type ValueSet (@ValueSet-Read) 2 2 100%
Stufe5/ basis > Testing search parameters against a resource of type ValueSet (@ValueSet-Search) 5 12 583%
Stufe5/ dokumentenaustausch > Upload of a DocumentReference with POST Operation (Dokumentenbereitstellung) (@DocumentReference-Post) 2 2 100%
Stufe5/ dokumentenaustausch > Read information from a resource of type DocumentReference (@DocumentReference-Read) 2 2 100%
Stufe5/ dokumentenaustausch > Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) 8 16 662%
Stufe5/ terminplanung > Booking an appointment (@Appointment-Book) 2 2 100%
Stufe5/ terminplanung > Booking an appointment by schedule reference (@Appointment-Book-By-Schedule) 1 1 100%
Stufe5/ terminplanung > Read Information from a resource of type Appointment (@Appointment-Read) 2 2 100%
Stufe5/ terminplanung > Testing search parameters against the Appointment resource (@Appointment-Search) 9 17 524%
Stufe5/ terminplanung > Read a resource of type Encounter that has a valid Appointment reference (@Encounter-Appointment-Read) 2 2 100%
Stufe5/ terminplanung > Read Information from a resource of type HealthcareService (@HealthcareService-Read) 2 2 100%
Stufe5/ terminplanung > Testing search parameters against the HealthcareService resource (@HealthcareService-Search) 6 11 427%
Stufe5/ terminplanung > Read Information from a resource of type Schedule (@Schedule-Read) 2 2 100%
Stufe5/ terminplanung > Testing search parameters against the Schedule resource (@Schedule-Search) 4 8 412%
Stufe5/ terminplanung > Read Information from a resource of type Slot (@Slot-Read) 2 2 100%
Stufe5/ terminplanung > Testing search parameters against the Slot resource (@Slot-Search) 7 11 327%

Tags

Terminplanung   60 Appointment-Book   2 Coverage-Read-Statutory   1 Coverage-Search-Private   9 Binary-Read   2 Procedure-Read   2 Relatedperson-Read   2 Account-Read   2 Documentreference-Post   2 Condition-Read-Resolved   2 Appointment-Book-By-Schedule   1 Healthcareservice-Search   11 Dokumentenaustausch   20 Composition-Post   1 Relatedperson-Search   6 Documentreference-Search   16 Healthcareservice-Read   2 Stufe5   252 Valueset-Search   12 Encounter-Appointment-Read   2 Encounter-Read-Finished   2 Slot-Read   2 Slot-Search   11 Condition-Read-Active   2 Procedure-Search   17 Basis   172 Account-Search   13 Practitioner-Search   10 Patient-Search   25 Patient-Read   2 Schedule-Search   8 Mandatory   252 Encounter-Read-In-Progress   2 Coverage-Read-Private   2 Documentreference-Read   2 Schedule-Read   2 Precondition   39 Encounter-Read-Planned   2 Condition-Search   13 Practitioner-Read   2 Patient-Read-Extended   1 Appointment-Read   2 Appointment-Search   17 Coverage-Search-Statutory   11 Encounter-Search   27 Valueset-Read   2

Automated Tests

feature Scenario Steps Started Total Duration Result
Read Information from a resource of type Account (@Account-Read) Precondition 2 09:37:49 414ms SUCCESS
Read Information from a resource of type Account (@Account-Read) Read and Validation of the CapabilityStatement 2 09:37:49 698ms SUCCESS
Testing search parameters against a resource of type Account (@Account-Search) Precondition 2 09:41:16 428ms SUCCESS
Testing search parameters against a resource of type Account (@Account-Search) Read and Validation of the CapabilityStatement 2 09:41:17 735ms SUCCESS
Testing search parameters against a resource of type Account (@Account-Search) 1: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_id, searchParamType=token 		1 09:41:18 214ms SUCCESS
Testing search parameters against a resource of type Account (@Account-Search) 2: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_count, searchParamType=number 		1 09:41:18 276ms SUCCESS
Testing search parameters against a resource of type Account (@Account-Search) 3: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=identifier, searchParamType=token 		1 09:41:18 214ms SUCCESS
Testing search parameters against a resource of type Account (@Account-Search) 4: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=status, searchParamType=token 		1 09:41:18 210ms SUCCESS
Testing search parameters against a resource of type Account (@Account-Search) 5: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=type, searchParamType=token 		1 09:41:19 217ms SUCCESS
Testing search parameters against a resource of type Account (@Account-Search) 6: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=patient, searchParamType=reference 		1 09:41:19 221ms SUCCESS
Testing search parameters against a resource of type Account (@Account-Search) 1: Search for the Account by ID (null) 3 09:41:19 905ms SUCCESS
Testing search parameters against a resource of type Account (@Account-Search) Search for the Account by Count 3 09:41:20 917ms SUCCESS
Testing search parameters against a resource of type Account (@Account-Search) Search for the Account by Identifier 3 09:41:21 958ms SUCCESS
Testing search parameters against a resource of type Account (@Account-Search) Search for the Account by Status 3 09:41:22 999ms SUCCESS
Testing search parameters against a resource of type Account (@Account-Search) Search for the Account by Patient 3 09:41:24 952ms SUCCESS
Read Information from a resource of type Binary (@Binary-Read) Precondition 2 09:41:03 430ms SUCCESS
Read Information from a resource of type Binary (@Binary-Read) Read and Validation of the CapabilityStatement 2 09:41:03 689ms SUCCESS
Upload of a Document Bundle with POST Operation (@Composition-Post) Precondition 2 09:37:42 422ms SUCCESS
Read Information from a resource of type Condition with status "active" (@Condition-Read-Active) Precondition 2 09:38:30 423ms SUCCESS
Read Information from a resource of type Condition with status "active" (@Condition-Read-Active) Read and Validation of the CapabilityStatement 2 09:38:31 908ms SUCCESS
Read Information from a resource of type Condition with status "resolved" (@Condition-Read-Resolved) Precondition 2 09:41:26 431ms SUCCESS
Read Information from a resource of type Condition with status "resolved" (@Condition-Read-Resolved) Read and Validation of the CapabilityStatement 2 09:41:26 702ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Precondition 2 09:41:06 430ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Read and Validation of the CapabilityStatement 2 09:41:07 696ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) 1: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_id, searchParamType=token 		1 09:41:07 216ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) 2: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_count, searchParamType=number 		1 09:41:08 219ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) 3: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=patient, searchParamType=reference 		1 09:41:08 223ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) 4: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=subject, searchParamType=reference 		1 09:41:08 221ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) 5: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=encounter, searchParamType=reference 		1 09:41:08 223ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) 6: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=recorded-date, searchParamType=date 		1 09:41:09 221ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) 7: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=related, searchParamType=reference 		1 09:41:09 223ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) 1: Search for the Condition by ID (null) 3 09:41:09 968ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) 1: Search for the Condition by Count (null) 2 09:41:10 760ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by Patient(Search Parameter 'patient') 3 09:41:12 907ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by Encounter 3 09:41:13 972ms SUCCESS
Read Information from a resource of type "private" Coverage (@Coverage-Read-Private) Precondition 2 09:39:14 418ms SUCCESS
Read Information from a resource of type "private" Coverage (@Coverage-Read-Private) Read and Validation of the CapabilityStatement 2 09:39:14 811ms SUCCESS
Read Information from a resource of type "statutory" Coverage (@Coverage-Read-Statutory) Precondition 2 09:40:08 429ms SUCCESS
Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) 1: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_id, searchParamType=token 		1 09:36:19 209ms SUCCESS
Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) 2: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_count, searchParamType=number 		1 09:36:19 212ms SUCCESS
Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) 3: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=status, searchParamType=token 		1 09:36:19 213ms SUCCESS
Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) 4: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=type, searchParamType=token 		1 09:36:20 212ms SUCCESS
Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) 5: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=beneficiary, searchParamType=reference 		1 09:36:20 211ms SUCCESS
Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) 6: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=payor, searchParamType=reference 		1 09:36:20 209ms SUCCESS
Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) 1: Search for the Coverage by Beneficiary and Payor
searchParameter=beneficiary, searchValue=${data.patient-read-id} 		3 09:36:22 944ms SUCCESS
Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) 2: Search for the Coverage by Beneficiary and Payor
searchParameter=payor, searchValue=${data.patient-read-id} 		3 09:36:23 984ms SUCCESS
Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) Search for the Coverage by Type of Insurance 3 09:36:26 979ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Precondition 2 09:37:16 422ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Read and Validation of the CapabilityStatement 2 09:37:16 817ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) 1: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_id, searchParamType=token 		1 09:37:17 210ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) 2: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_count, searchParamType=number 		1 09:37:17 213ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) 3: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=status, searchParamType=token 		1 09:37:17 210ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) 4: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=type, searchParamType=token 		1 09:37:18 214ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) 5: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=beneficiary, searchParamType=reference 		1 09:37:18 212ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) 6: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=payor, searchParamType=reference 		1 09:37:18 210ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) 1: Search for the Coverage by ID (null) 3 09:37:18 943ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) 1: Search for the Coverage by insured person's number (null) 3 09:37:19 940ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Search for the Coverage by Type 3 09:37:21 895ms SUCCESS
Read Information from a resource of type Encounter with status "finished" (@Encounter-Read-Finished) Precondition 2 09:37:10 417ms SUCCESS
Read Information from a resource of type Encounter with status "finished" (@Encounter-Read-Finished) Read and Validation of the CapabilityStatement 2 09:37:11 855ms SUCCESS
Read Information from a resource of type Encounter with status "in progress" (@Encounter-Read-In-Progress) Precondition 2 09:37:05 412ms SUCCESS
Read Information from a resource of type Encounter with status "in progress" (@Encounter-Read-In-Progress) Read and Validation of the CapabilityStatement 2 09:37:06 816ms SUCCESS
Read Information from a resource of type Encounter with status "planned" (@Encounter-Read-Planned) Precondition 2 09:37:37 417ms SUCCESS
Read Information from a resource of type Encounter with status "planned" (@Encounter-Read-Planned) Read and Validation of the CapabilityStatement 2 09:37:38 732ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Precondition 2 09:38:36 425ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Read and Validation of the CapabilityStatement 2 09:38:37 919ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) 1: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_id, searchParamType=token 		1 09:38:37 215ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) 2: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_count, searchParamType=number 		1 09:38:38 221ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) 3: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=identifier, searchParamType=token 		1 09:38:38 214ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) 4: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=status, searchParamType=token 		1 09:38:38 374ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) 5: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=class, searchParamType=token 		1 09:38:39 210ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) 6: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=type, searchParamType=token 		1 09:38:39 216ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) 7: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=patient, searchParamType=reference 		1 09:38:39 216ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) 8: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=account, searchParamType=reference 		1 09:38:39 210ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) 9: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=location, searchParamType=reference 		1 09:38:39 214ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) 10: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=service-provider, searchParamType=reference 		1 09:38:40 217ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) 11: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=date, searchParamType=date 		1 09:38:40 218ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) 12: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=date-start, searchParamType=date 		1 09:38:40 214ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) 13: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=end-date, searchParamType=date 		1 09:38:40 215ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) 1: Search for the encounter by ID (null) 3 09:38:41 916ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the Encounter by Count 2 09:38:41 714ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the Encounter by Status 3 09:38:42 965ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the Encounter by Type 3 09:38:44 925ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the Encounter by Patient ID 3 09:38:45 946ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the Encounter by Account ID 3 09:38:46 990ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the Encounter by Admission Date with 'le' Modifier 3 09:38:48 938ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the Encounter by Admission Date with 'gt' Modifier 3 09:38:49 994ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Negative Search for the Encounter by Admission Date 2 09:38:50 808ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Negative Search for the Encounter by Admission Date with the Search parameter 'date-start' and 'ge' Modifier 2 09:38:55 951ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Negative Search for the Encounter by Admission Date with the Search parameter 'end-date' and 'le' Modifier 2 09:38:56 782ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the Encounter by identifier.system 3 09:39:00 930ms SUCCESS
Read Information from a resource of type Patient (@Patient-Read) Precondition 2 09:41:32 433ms SUCCESS
Read Information from a resource of type Patient (@Patient-Read) Read and Validation of the CapabilityStatement 2 09:41:32 790ms SUCCESS
Read extended Information from a resource of type Patient (@Patient-Read-Extended) Precondition 2 09:39:35 423ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Precondition 2 09:40:25 435ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Read and Validation of the CapabilityStatement 2 09:40:25 931ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) 1: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_id, searchParamType=token 		1 09:40:26 217ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) 2: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_count, searchParamType=number 		1 09:40:26 217ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) 3: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=identifier, searchParamType=token 		1 09:40:27 222ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) 4: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=given, searchParamType=string 		1 09:40:27 220ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) 5: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=family, searchParamType=string 		1 09:40:27 217ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) 6: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=birthdate, searchParamType=date 		1 09:40:27 217ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) 7: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=gender, searchParamType=token 		1 09:40:28 213ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) 8: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=name, searchParamType=string 		1 09:40:28 216ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) 9: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=address, searchParamType=string 		1 09:40:28 218ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) 10: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=address-city, searchParamType=string 		1 09:40:28 220ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) 11: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=address-country, searchParamType=string 		1 09:40:28 218ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) 12: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=address-postalcode, searchParamType=string 		1 09:40:29 222ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) 13: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=active, searchParamType=token 		1 09:40:29 219ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) 14: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=telecom, searchParamType=token 		1 09:40:29 221ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) 1: Search for Patient by ID (null) 3 09:40:29 933ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patient by Count 2 09:40:30 825ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patient by first name 3 09:40:32 927ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patient with parameter family 3 09:40:33 962ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patient by gender 3 09:40:36 936ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patients by last name with special characters 3 09:40:40 926ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patients by first name with special characters 3 09:40:41 979ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patient with an empty search parameter to be ignored 3 09:40:49 891ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patients by Address (postal code) 3 09:40:54 954ms SUCCESS
Read Information from a resource of type Practitioner (@Practitioner-Read) Precondition 2 09:38:13 422ms SUCCESS
Read Information from a resource of type Practitioner (@Practitioner-Read) Read and Validation of the CapabilityStatement 2 09:38:14 681ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) Precondition 2 09:37:24 416ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) Read and Validation of the CapabilityStatement 2 09:37:25 755ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) 1: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_id, searchParamType=token 		1 09:37:25 215ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) 2: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_count, searchParamType=number 		1 09:37:26 215ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) 3: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=identifier, searchParamType=token 		1 09:37:26 212ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) 4: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=given, searchParamType=string 		1 09:37:26 209ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) 5: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=family, searchParamType=string 		1 09:37:26 214ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) 1: Search for Practitioner resource by Count (null) 2 09:37:28 718ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) Search for Practitioner resource by First Name 3 09:37:31 926ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) Search for Practitioner resource by Last Name 3 09:37:32 955ms SUCCESS
Read Information from a resource of type Procedure (@Procedure-Read) Precondition 2 09:36:31 415ms SUCCESS
Read Information from a resource of type Procedure (@Procedure-Read) Read and Validation of the CapabilityStatement 2 09:36:31 764ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) Precondition 2 09:39:54 426ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) Read and Validation of the CapabilityStatement 2 09:39:55 716ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) 1: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_id, searchParamType=token 		1 09:39:55 217ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) 2: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_count, searchParamType=number 		1 09:39:56 221ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) 3: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=status, searchParamType=token 		1 09:39:56 222ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) 4: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=category, searchParamType=token 		1 09:39:56 220ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) 5: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=code, searchParamType=token 		1 09:39:56 222ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) 6: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=patient, searchParamType=reference 		1 09:39:56 221ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) 7: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=encounter, searchParamType=reference 		1 09:39:57 219ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) 8: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=date, searchParamType=date 		1 09:39:57 221ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) 1: Search for Procedure resource by ID (null) 3 09:39:57 956ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) 1: Search for Procedure resource by Count (null) 2 09:39:58 921ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) Search for Procedures by Status 3 09:39:59 920ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) Search for Procedures by Category 3 09:40:00 976ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) Search for Procedures by Patient reference 3 09:40:03 932ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) 1: Search for Procedures by references
contentType=xml, entrytype=encounter, path=encounter, query=Encounter/, data=${data.encounter-read-in-progress-id} 		3 09:40:04 969ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) 2: Search for Procedures by references
contentType=json, entrytype=subject, path=patient, query=Patient/, data=${data.patient-read-id} 		3 09:40:05 993ms SUCCESS
Read Information from a resource of type RelatedPerson (@RelatedPerson-Read) Precondition 2 09:39:04 428ms SUCCESS
Read Information from a resource of type RelatedPerson (@RelatedPerson-Read) Read and Validation of the CapabilityStatement 2 09:39:05 775ms SUCCESS
Testing search parameters against a resource of type RelatedPerson (@RelatedPerson-Search) Precondition 2 09:39:21 417ms SUCCESS
Testing search parameters against a resource of type RelatedPerson (@RelatedPerson-Search) Read and Validation of the CapabilityStatement 2 09:39:21 704ms SUCCESS
Testing search parameters against a resource of type RelatedPerson (@RelatedPerson-Search) 1: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_id, searchParamType=token 		1 09:39:22 216ms SUCCESS
Testing search parameters against a resource of type RelatedPerson (@RelatedPerson-Search) 2: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_count, searchParamType=number 		1 09:39:22 219ms SUCCESS
Testing search parameters against a resource of type RelatedPerson (@RelatedPerson-Search) 3: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=patient, searchParamType=reference 		1 09:39:22 215ms SUCCESS
Testing search parameters against a resource of type RelatedPerson (@RelatedPerson-Search) 1: Search for RelatedPerson resource by Count (null) 2 09:39:24 847ms SUCCESS
Read Information from a resource of type ValueSet (@ValueSet-Read) Precondition 2 09:39:39 421ms SUCCESS
Read Information from a resource of type ValueSet (@ValueSet-Read) Read and Validation of the CapabilityStatement 2 09:39:40 713ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) Precondition 2 09:41:36 424ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) Read and Validation of the CapabilityStatement 2 09:41:37 748ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) 1: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_id, searchParamType=token 		1 09:41:37 218ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) 2: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_count, searchParamType=number 		1 09:41:38 221ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) 3: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=url, searchParamType=uri 		1 09:41:38 219ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) 4: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=version, searchParamType=token 		1 09:41:38 218ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) 5: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=name, searchParamType=string 		1 09:41:38 224ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) 6: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=status, searchParamType=token 		1 09:41:39 221ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) 1: Search for ValueSet resource by Count (null) 2 09:41:40 686ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) 1: Search for ValueSet by additional search parameters
contentType=xml, searchParameter=url, searchValue=http://example.org/fhir/ValueSet/TestValueSet 		3 09:41:41 946ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) 2: Search for ValueSet by additional search parameters
contentType=json, searchParameter=name, searchValue=TestValueSet 		3 09:41:42 979ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) 4: Search for ValueSet by additional search parameters
contentType=json, searchParameter=version, searchValue=1.0.0 		3 09:41:44 912ms SUCCESS
Upload of a DocumentReference with POST Operation (Dokumentenbereitstellung) (@DocumentReference-Post) Precondition 2 09:40:12 431ms SUCCESS
Upload of a DocumentReference with POST Operation (Dokumentenbereitstellung) (@DocumentReference-Post) Read and Validation of the CapabilityStatement 2 09:40:13 944ms SUCCESS
Read information from a resource of type DocumentReference (@DocumentReference-Read) Precondition 2 09:37:56 421ms SUCCESS
Read information from a resource of type DocumentReference (@DocumentReference-Read) Read and Validation of the CapabilityStatement 2 09:37:56 690ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) Precondition 2 09:38:17 417ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) Read and Validation of the CapabilityStatement 2 09:38:17 976ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) 1: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_id, searchParamType=token 		1 09:38:18 212ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) 2: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_count, searchParamType=number 		1 09:38:19 212ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) 3: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=patient, searchParamType=reference 		1 09:38:19 212ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) 4: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=status, searchParamType=token 		1 09:38:19 212ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) 5: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=identifier, searchParamType=token 		1 09:38:19 213ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) 6: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=type, searchParamType=token 		1 09:38:19 213ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) 7: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=category, searchParamType=token 		1 09:38:20 213ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) 8: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=creation, searchParamType=date 		1 09:38:20 215ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) 9: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=encounter, searchParamType=reference 		1 09:38:20 224ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) 1: Search for the DocumentReference metadata by ID (null) 2 09:38:20 764ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) Search for the DocumentReference by Count 2 09:38:21 885ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) Search for the DocumentReference that belong to a Patient, by Document Identifier 3 09:38:24 925ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) Search for DocumentReference that belong to a Patient, knowing their identifier 2 09:38:25 767ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) Search for the DocumentReference that belong to a Patient, by Category 3 09:38:27 885ms SUCCESS
Booking an appointment (@Appointment-Book) Precondition 2 09:39:49 425ms SUCCESS
Booking an appointment (@Appointment-Book) Read and Validation of the CapabilityStatement 2 09:39:49 759ms SUCCESS
Booking an appointment by schedule reference (@Appointment-Book-By-Schedule) Precondition 2 09:36:27 416ms SUCCESS
Read Information from a resource of type Appointment (@Appointment-Read) Precondition 2 09:39:08 422ms SUCCESS
Read Information from a resource of type Appointment (@Appointment-Read) Read and Validation of the CapabilityStatement 2 09:39:09 823ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) Precondition 2 09:41:45 428ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) Read and Validation of the CapabilityStatement 2 09:41:46 793ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) 1: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_id, searchParamType=token 		1 09:41:46 218ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) 2: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_tag, searchParamType=token 		1 09:41:47 221ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) 3: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_count, searchParamType=number 		1 09:41:47 219ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) 4: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=status, searchParamType=token 		1 09:41:47 224ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) 5: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=service-type, searchParamType=token 		1 09:41:47 218ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) 6: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=specialty, searchParamType=token 		1 09:41:48 355ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) 7: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=date, searchParamType=date 		1 09:41:48 214ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) 8: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=slot, searchParamType=reference 		1 09:41:48 216ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) 9: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=actor, searchParamType=reference 		1 09:41:48 220ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) Search for the Appointment by ID 3 09:41:49 910ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) Search for the Appointment by Count 2 09:41:50 794ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) Search for the Appointment by Status 3 09:41:50 976ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) Search for the Appointment by Specialty 3 09:41:52 936ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) Search for the Appointment by Date 3 09:41:53 976ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) Search for the Appointment by Actor 3 09:41:56 927ms SUCCESS
Read a resource of type Encounter that has a valid Appointment reference (@Encounter-Appointment-Read) Precondition 2 09:40:58 429ms SUCCESS
Read a resource of type Encounter that has a valid Appointment reference (@Encounter-Appointment-Read) Read and Validation of the CapabilityStatement 2 09:40:58 746ms SUCCESS
Read Information from a resource of type HealthcareService (@HealthcareService-Read) Precondition 2 09:39:17 419ms SUCCESS
Read Information from a resource of type HealthcareService (@HealthcareService-Read) Read and Validation of the CapabilityStatement 2 09:39:18 747ms SUCCESS
Testing search parameters against the HealthcareService resource (@HealthcareService-Search) Precondition 2 09:39:27 427ms SUCCESS
Testing search parameters against the HealthcareService resource (@HealthcareService-Search) Read and Validation of the CapabilityStatement 2 09:39:27 719ms SUCCESS
Testing search parameters against the HealthcareService resource (@HealthcareService-Search) 1: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_id, searchParamType=token 		1 09:39:28 221ms SUCCESS
Testing search parameters against the HealthcareService resource (@HealthcareService-Search) 2: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_count, searchParamType=number 		1 09:39:28 222ms SUCCESS
Testing search parameters against the HealthcareService resource (@HealthcareService-Search) 3: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=active, searchParamType=token 		1 09:39:28 219ms SUCCESS
Testing search parameters against the HealthcareService resource (@HealthcareService-Search) 4: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=service-type, searchParamType=token 		1 09:39:28 218ms SUCCESS
Testing search parameters against the HealthcareService resource (@HealthcareService-Search) 5: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=specialty, searchParamType=token 		1 09:39:29 217ms SUCCESS
Testing search parameters against the HealthcareService resource (@HealthcareService-Search) 6: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=name, searchParamType=string 		1 09:39:29 222ms SUCCESS
Testing search parameters against the HealthcareService resource (@HealthcareService-Search) Search for the HealthcareService by Count 2 09:39:30 704ms SUCCESS
Testing search parameters against the HealthcareService resource (@HealthcareService-Search) Search for the HealthcareService by Active state 3 09:39:31 999ms SUCCESS
Testing search parameters against the HealthcareService resource (@HealthcareService-Search) 1: Search for the HealthcareService by service type
searchParameter=service-type, coding=type, searchValue=${data.healthcareservice-read-servicetype-code} 		3 09:39:32 991ms SUCCESS
Read Information from a resource of type Schedule (@Schedule-Read) Precondition 2 09:37:34 419ms SUCCESS
Read Information from a resource of type Schedule (@Schedule-Read) Read and Validation of the CapabilityStatement 2 09:37:34 731ms SUCCESS
Testing search parameters against the Schedule resource (@Schedule-Search) Precondition 2 09:36:56 417ms SUCCESS
Testing search parameters against the Schedule resource (@Schedule-Search) 1: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_id, searchParamType=token 		1 09:36:58 209ms SUCCESS
Testing search parameters against the Schedule resource (@Schedule-Search) 2: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=active, searchParamType=token 		1 09:36:58 209ms SUCCESS
Testing search parameters against the Schedule resource (@Schedule-Search) 3: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=service-type, searchParamType=token 		1 09:36:58 211ms SUCCESS
Testing search parameters against the Schedule resource (@Schedule-Search) 4: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=specialty, searchParamType=token 		1 09:36:59 213ms SUCCESS
Testing search parameters against the Schedule resource (@Schedule-Search) 5: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=actor, searchParamType=reference 		1 09:36:59 210ms SUCCESS
Testing search parameters against the Schedule resource (@Schedule-Search) Search for the Schedule by Count 2 09:37:00 822ms SUCCESS
Testing search parameters against the Schedule resource (@Schedule-Search) Search for the Schedule by Service Type 3 09:37:02 983ms SUCCESS
Read Information from a resource of type Slot (@Slot-Read) Precondition 2 09:37:53 413ms SUCCESS
Read Information from a resource of type Slot (@Slot-Read) Read and Validation of the CapabilityStatement 2 09:37:53 698ms SUCCESS
Testing search parameters against the Slot resource (@Slot-Search) Precondition 2 09:38:05 420ms SUCCESS
Testing search parameters against the Slot resource (@Slot-Search) Read and Validation of the CapabilityStatement 2 09:38:05 715ms SUCCESS
Testing search parameters against the Slot resource (@Slot-Search) 1: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_id, searchParamType=token 		1 09:38:06 213ms SUCCESS
Testing search parameters against the Slot resource (@Slot-Search) 2: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=_count, searchParamType=number 		1 09:38:06 212ms SUCCESS
Testing search parameters against the Slot resource (@Slot-Search) 3: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=schedule, searchParamType=reference 		1 09:38:06 213ms SUCCESS
Testing search parameters against the Slot resource (@Slot-Search) 4: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=status, searchParamType=token 		1 09:38:07 212ms SUCCESS
Testing search parameters against the Slot resource (@Slot-Search) 5: Validation of the search parameter definitions in the CapabilityStatement
searchParamValue=start, searchParamType=date 		1 09:38:07 215ms SUCCESS
Testing search parameters against the Slot resource (@Slot-Search) Search for the Slot by Count 2 09:38:08 819ms SUCCESS
Testing search parameters against the Slot resource (@Slot-Search) Search for the Slot by Status and Schedule 3 09:38:10 921ms SUCCESS
Testing search parameters against the Slot resource (@Slot-Search) Search for the Slot by Start time 3 09:38:11 951ms SUCCESS
Testing search parameters against the Slot resource (@Slot-Search) Chaining search for slots by Practitioner 2 09:38:12 773ms SUCCESS

Manual Tests

No manual tests were recorded

Tags

Terminplanung   60 Appointment-Book   2 Coverage-Read-Statutory   1 Coverage-Search-Private   9 Binary-Read   2 Procedure-Read   2 Relatedperson-Read   2 Account-Read   2 Documentreference-Post   2 Condition-Read-Resolved   2 Appointment-Book-By-Schedule   1 Healthcareservice-Search   11 Dokumentenaustausch   20 Composition-Post   1 Relatedperson-Search   6 Documentreference-Search   16 Healthcareservice-Read   2 Stufe5   252 Valueset-Search   12 Encounter-Appointment-Read   2 Encounter-Read-Finished   2 Slot-Read   2 Slot-Search   11 Condition-Read-Active   2 Procedure-Search   17 Basis   172 Account-Search   13 Practitioner-Search   10 Patient-Search   25 Patient-Read   2 Schedule-Search   8 Mandatory   252 Encounter-Read-In-Progress   2 Coverage-Read-Private   2 Documentreference-Read   2 Schedule-Read   2 Precondition   39 Encounter-Read-Planned   2 Condition-Search   13 Practitioner-Read   2 Patient-Read-Extended   1 Appointment-Read   2 Appointment-Search   17 Coverage-Search-Statutory   11 Encounter-Search   27 Valueset-Read   2
Serenity BDD version 4.3.2