Serenity BDD Report
Home > Duration 1 To 10 Seconds
Report generated 23-03-2026 09:42:05

Duration 1 To 10 Seconds

97 tests |

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

Key Statistics

Number of Scenarios 93
Total Number of Test Cases 97
Tests Started März 23, 2026 09:36:16
Tests Finished März 23, 2026 09:41:56
Total Duration 5m 39s
Fastest Test 1s
Slowest Test 7s
Average Execution Time 1s
Total Execution Time 2m 51s

Test Outcomes

Test Performance

Functional Coverage Overview

Features

Tags

Terminplanung   20 Appointment-Book   2 Coverage-Read-Statutory   2 Coverage-Search-Private   5 Binary-Read   1 Relatedperson-Read   1 Account-Read   1 Documentreference-Post   4 Condition-Read-Resolved   1 Appointment-Book-By-Schedule   1 Healthcareservice-Search   3 Dokumentenaustausch   11 Composition-Post   4 Relatedperson-Search   2 Documentreference-Search   5 Healthcareservice-Read   1 Stufe5   97 Valueset-Search   2 Encounter-Appointment-Read   1 Encounter-Read-Finished   1 Slot-Read   1 Slot-Search   2 Condition-Read-Active   1 Procedure-Search   3 Basis   66 Account-Search   1 Practitioner-Search   4 Patient-Search   14 Patient-Read   1 Schedule-Search   5 Mandatory   97 Encounter-Read-In-Progress   1 Coverage-Read-Private   1 Documentreference-Read   2 Schedule-Read   1 Precondition   1 Encounter-Read-Planned   1 Condition-Search   3 Practitioner-Read   1 Patient-Read-Extended   1 Appointment-Read   1 Appointment-Search   2 Coverage-Search-Statutory   3 Encounter-Search   10 Valueset-Read   1

Functional Coverage Details

Features

Feature Test Cases Scenarios % Pass Result Coverage
Stufe5/ basis > Read Information from a resource of type Account (@Account-Read) 1 1 100%
Stufe5/ basis > Testing search parameters against a resource of type Account (@Account-Search) 1 1 100%
Stufe5/ basis > Read Information from a resource of type Binary (@Binary-Read) 1 1 100%
Stufe5/ basis > Upload of a Document Bundle with POST Operation (@Composition-Post) 2 4 250%
Stufe5/ basis > Read Information from a resource of type Condition with status "active" (@Condition-Read-Active) 1 1 100%
Stufe5/ basis > Read Information from a resource of type Condition with status "resolved" (@Condition-Read-Resolved) 1 1 100%
Stufe5/ basis > Testing search parameters against a resource of type Condition (@Condition-Search) 3 3 400%
Stufe5/ basis > Read Information from a resource of type "private" Coverage (@Coverage-Read-Private) 1 1 100%
Stufe5/ basis > Read Information from a resource of type "statutory" Coverage (@Coverage-Read-Statutory) 2 2 100%
Stufe5/ basis > Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) 5 5 220%
Stufe5/ basis > Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) 3 3 100%
Stufe5/ basis > Read Information from a resource of type Encounter with status "finished" (@Encounter-Read-Finished) 1 1 100%
Stufe5/ basis > Read Information from a resource of type Encounter with status "in progress" (@Encounter-Read-In-Progress) 1 1 100%
Stufe5/ basis > Read Information from a resource of type Encounter with status "planned" (@Encounter-Read-Planned) 1 1 100%
Stufe5/ basis > Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) 10 10 100%
Stufe5/ basis > Read Information from a resource of type Patient (@Patient-Read) 1 1 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) 14 14 100%
Stufe5/ basis > Read Information from a resource of type Practitioner (@Practitioner-Read) 1 1 100%
Stufe5/ basis > Testing search parameters against a resource of type Practitioner (@Practitioner-Search) 4 4 700%
Stufe5/ basis > Testing search parameters against a resource of type Procedure (@Procedure-Search) 3 3 100%
Stufe5/ basis > Read Information from a resource of type RelatedPerson (@RelatedPerson-Read) 1 1 100%
Stufe5/ basis > Testing search parameters against a resource of type RelatedPerson (@RelatedPerson-Search) 2 2 600%
Stufe5/ basis > Read Information from a resource of type ValueSet (@ValueSet-Read) 1 1 100%
Stufe5/ basis > Testing search parameters against a resource of type ValueSet (@ValueSet-Search) 2 2 600%
Stufe5/ dokumentenaustausch > Upload of a DocumentReference with POST Operation (Dokumentenbereitstellung) (@DocumentReference-Post) 2 4 250%
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) 5 5 100%
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) 1 1 100%
Stufe5/ terminplanung > Testing search parameters against the Appointment resource (@Appointment-Search) 2 2 100%
Stufe5/ terminplanung > Read a resource of type Encounter that has a valid Appointment reference (@Encounter-Appointment-Read) 1 1 100%
Stufe5/ terminplanung > Read Information from a resource of type HealthcareService (@HealthcareService-Read) 1 1 100%
Stufe5/ terminplanung > Testing search parameters against the HealthcareService resource (@HealthcareService-Search) 3 3 300%
Stufe5/ terminplanung > Read Information from a resource of type Schedule (@Schedule-Read) 1 1 100%
Stufe5/ terminplanung > Testing search parameters against the Schedule resource (@Schedule-Search) 5 5 200%
Stufe5/ terminplanung > Read Information from a resource of type Slot (@Slot-Read) 1 1 100%
Stufe5/ terminplanung > Testing search parameters against the Slot resource (@Slot-Search) 2 2 350%

Tags

Terminplanung   20 Appointment-Book   2 Coverage-Read-Statutory   2 Coverage-Search-Private   5 Binary-Read   1 Relatedperson-Read   1 Account-Read   1 Documentreference-Post   4 Condition-Read-Resolved   1 Appointment-Book-By-Schedule   1 Healthcareservice-Search   3 Dokumentenaustausch   11 Composition-Post   4 Relatedperson-Search   2 Documentreference-Search   5 Healthcareservice-Read   1 Stufe5   97 Valueset-Search   2 Encounter-Appointment-Read   1 Encounter-Read-Finished   1 Slot-Read   1 Slot-Search   2 Condition-Read-Active   1 Procedure-Search   3 Basis   66 Account-Search   1 Practitioner-Search   4 Patient-Search   14 Patient-Read   1 Schedule-Search   5 Mandatory   97 Encounter-Read-In-Progress   1 Coverage-Read-Private   1 Documentreference-Read   2 Schedule-Read   1 Precondition   1 Encounter-Read-Planned   1 Condition-Search   3 Practitioner-Read   1 Patient-Read-Extended   1 Appointment-Read   1 Appointment-Search   2 Coverage-Search-Statutory   3 Encounter-Search   10 Valueset-Read   1

Automated Tests

feature Scenario Steps Started Total Duration Result
Read Information from a resource of type Account (@Account-Read) Read and Validate the Account by its ID 11 09:37:50 2s 808ms SUCCESS
Testing search parameters against a resource of type Account (@Account-Search) Search for the Account by Type 3 09:41:23 1s 212ms SUCCESS
Read Information from a resource of type Binary (@Binary-Read) Read and Validate Binary data in FHIR format by its ID 5 09:41:04 1s 360ms SUCCESS
Upload of a Document Bundle with POST Operation (@Composition-Post) Upload of a DocumentBundle with known patients and Encounters with the POST Operation 4 09:37:43 1s 368ms SUCCESS
Upload of a Document Bundle with POST Operation (@Composition-Post) 1: Upload of an incorrect DocumentBundle with the POST Operation
inputFile=Composition-Post-CompositionBundleUnknownPatient.json, responseCode=422 		5 09:37:44 1s 349ms SUCCESS
Upload of a Document Bundle with POST Operation (@Composition-Post) 2: Upload of an incorrect DocumentBundle with the POST Operation
inputFile=Composition-Post-CompositionBundleUnknownEncounter.json, responseCode=422 		5 09:37:45 1s 511ms SUCCESS
Upload of a Document Bundle with POST Operation (@Composition-Post) 3: Upload of an incorrect DocumentBundle with the POST Operation
inputFile=Composition-Post-CompositionBundleMissingText.json, responseCode=4\d\d 		5 09:37:47 1s 339ms SUCCESS
Read Information from a resource of type Condition with status "active" (@Condition-Read-Active) Read and Validate active Condition by its ID 19 09:38:32 4s 323ms SUCCESS
Read Information from a resource of type Condition with status "resolved" (@Condition-Read-Resolved) Read and Validate resolved Condition by its ID 14 09:41:27 4s 774ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) 1: Search for the Condition by Patient (Search Parameter 'subject') (null) 3 09:41:11 1s 288ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by Recorded Date with 'ge' Modifier 3 09:41:14 1s 016ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by Recorded Date with 'le' Modifier 3 09:41:15 1s 176ms SUCCESS
Read Information from a resource of type "private" Coverage (@Coverage-Read-Private) Read and Validate private Coverage by its ID 8 09:39:15 1s 972ms SUCCESS
Read Information from a resource of type "statutory" Coverage (@Coverage-Read-Statutory) Read and Validation of the CapabilityStatement 2 09:40:08 1s 011ms SUCCESS
Read Information from a resource of type "statutory" Coverage (@Coverage-Read-Statutory) Read and Validate statutory Coverage by its ID 12 09:40:09 2s 895ms SUCCESS
Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) Precondition 2 09:36:16 1s 232ms SUCCESS
Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) Read and Validation of the CapabilityStatement 2 09:36:17 1s 710ms SUCCESS
Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) 1: Search for the Coverage by ID (null) 3 09:36:20 1s 757ms SUCCESS
Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) Search for the Coverage Coverage by Beneficiary 3 09:36:24 1s 019ms SUCCESS
Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) Search for the Coverage by Status 3 09:36:25 1s 230ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Search for the Coverage by Status 3 09:37:20 1s 065ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Search for the Coverage by Beneficiary 3 09:37:22 1s 019ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Search for the Coverage by Type (Negative Test) 3 09:37:23 1s 050ms SUCCESS
Read Information from a resource of type Encounter with status "finished" (@Encounter-Read-Finished) Read and Validate finished Encounter by its ID 16 09:37:12 3s 694ms SUCCESS
Read Information from a resource of type Encounter with status "in progress" (@Encounter-Read-In-Progress) Read and Validate in-progress Encounter by its ID 13 09:37:07 3s 250ms SUCCESS
Read Information from a resource of type Encounter with status "planned" (@Encounter-Read-Planned) Read and Validate planned Encounter by its ID 15 09:37:38 3s 686ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the Encounter by Class 3 09:38:43 1s 194ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the Encounter by Account Identifier 3 09:38:47 1s 197ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the Encounter by Admission Date with 'ge' und 'le' Modifiers 3 09:38:51 1s 119ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the Encounter by Admission Date with the Search parameter 'end-date' 5 09:38:52 1s 433ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the Encounter by Admission Date with the Search parameter 'date-start' 4 09:38:54 1s 199ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the Encounter by Admission Date with both Search parameters 'date-start' and 'end-date' 5 09:38:57 1s 380ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the Encounter by Admission Identifier 3 09:38:58 1s 014ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the Encounter by Patient 3 09:38:59 1s 192ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the encounter by Location 5 09:39:01 1s 465ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the encounter by Service Provider 3 09:39:03 1s 269ms SUCCESS
Read Information from a resource of type Patient (@Patient-Read) Read and Validate Patient by their ID 13 09:41:33 3s 132ms SUCCESS
Read extended Information from a resource of type Patient (@Patient-Read-Extended) Read and Validate Patient by their ID 13 09:39:36 3s 306ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patient by identifier 3 09:40:31 1s 125ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patient by date of birth 3 09:40:34 1s 131ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patient by ID and date of birth 4 09:40:35 1s 107ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patient by ID and gender 4 09:40:37 1s 188ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patient using family 4 09:40:39 1s 353ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patient using birthdate=gt 3 09:40:42 1s 871ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patients by Encounter 3 09:40:44 3s 324ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Negative test 3 09:40:47 1s 035ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patients by Date of birth 3 09:40:48 1s 231ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patients by Name 5 09:40:50 1s 519ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patients by Address 3 09:40:52 1s 080ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patients by Address 3 09:40:53 1s 109ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patients by Status 3 09:40:55 1s 084ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patients by Phone Number 3 09:40:56 1s 140ms SUCCESS
Read Information from a resource of type Practitioner (@Practitioner-Read) Read and Validate Practitioner resource by its ID 11 09:38:14 2s 623ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) 1: Search for Practitioner resource by ID (null) 3 09:37:27 1s 034ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) 1: Search for Practitioner resource by Identifier LANR (null) 4 09:37:28 1s 154ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) 1: Search for Practitioner resource by Identifier Telematik-ID (null) 4 09:37:29 1s 292ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) Search for Practitioner resource by First Name (negative test) 3 09:37:33 1s 119ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) Search for Procedures by Code 3 09:40:01 1s 088ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) Search for Procedures by Performed Date 4 09:40:02 1s 430ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) Negative search for Procedure by ID and status 3 09:40:06 1s 092ms SUCCESS
Read Information from a resource of type RelatedPerson (@RelatedPerson-Read) Read and Validate RelatedPerson resource by its ID 9 09:39:06 2s 246ms SUCCESS
Testing search parameters against a resource of type RelatedPerson (@RelatedPerson-Search) 1: Search for RelatedPerson by ID (null) 4 09:39:22 1s 198ms SUCCESS
Testing search parameters against a resource of type RelatedPerson (@RelatedPerson-Search) 1: Search for RelatedPerson by Patient ID (null) 4 09:39:25 1s 140ms SUCCESS
Read Information from a resource of type ValueSet (@ValueSet-Read) Read and Validate ValueSet by its ID 12 09:39:41 7s 749ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) 1: Search for ValueSet by ID (null) 5 09:41:39 1s 546ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) 3: Search for ValueSet by additional search parameters
contentType=json, searchParameter=status, searchValue=active 		3 09:41:43 1s 205ms SUCCESS
Upload of a DocumentReference with POST Operation (Dokumentenbereitstellung) (@DocumentReference-Post) POST a DocumentBundle with known patient and encounter 19 09:40:14 4s 608ms SUCCESS
Upload of a DocumentReference with POST Operation (Dokumentenbereitstellung) (@DocumentReference-Post) 1: POST an incorrect DocumentBundle
inputFile=DocumentReference-Post-UnknownPatient.json, responseCode=422 		5 09:40:18 1s 418ms SUCCESS
Upload of a DocumentReference with POST Operation (Dokumentenbereitstellung) (@DocumentReference-Post) 2: POST an incorrect DocumentBundle
inputFile=DocumentReference-Post-UnknownEncounter.json, responseCode=422 		5 09:40:20 3s 490ms SUCCESS
Upload of a DocumentReference with POST Operation (Dokumentenbereitstellung) (@DocumentReference-Post) 3: POST an incorrect DocumentBundle
inputFile=DocumentReference-Post-MissingAttachmentData.json, responseCode=4\d\d 		5 09:40:23 1s 380ms SUCCESS
Read information from a resource of type DocumentReference (@DocumentReference-Read) Read document metadata by ID 21 09:37:57 5s 864ms SUCCESS
Read information from a resource of type DocumentReference (@DocumentReference-Read) Read the Binary resource referenced in the DocumentReference resource 5 09:38:03 1s 430ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) Search for DocumentReference that belong to a Patient 3 09:38:22 1s 067ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) Search for the DocumentReference that belong to a Patient, by Document Status 3 09:38:23 1s 287ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) Search for the DocumentReference that belong to a Patient, by Type 3 09:38:26 1s 144ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) Search for the DocumentReference that belong to a Patient, by Encounter 3 09:38:28 1s 022ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) Search for the DocumentReference that belong to a Patient, by Creation Date 3 09:38:29 1s 056ms SUCCESS
Booking an appointment (@Appointment-Book) Book an appointment using a free slot 9 09:39:50 2s 263ms SUCCESS
Booking an appointment (@Appointment-Book) Book an appointment when the request is incomplete (no slot or schedule provided) 5 09:39:52 1s 386ms SUCCESS
Booking an appointment by schedule reference (@Appointment-Book-By-Schedule) Book an appointment by schedule reference 11 09:36:28 2s 825ms SUCCESS
Read Information from a resource of type Appointment (@Appointment-Read) Read an Appointment by ID 16 09:39:09 4s 009ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) Search for the Appointment by Service Type 3 09:41:51 1s 169ms SUCCESS
Testing search parameters against the Appointment resource (@Appointment-Search) Search for the Appointment by Slot 3 09:41:54 1s 132ms SUCCESS
Read a resource of type Encounter that has a valid Appointment reference (@Encounter-Appointment-Read) Read and Validate planned Encounter by its ID 14 09:40:59 3s 325ms SUCCESS
Read Information from a resource of type HealthcareService (@HealthcareService-Read) Read a HealthcareService by ID 7 09:39:18 1s 869ms SUCCESS
Testing search parameters against the HealthcareService resource (@HealthcareService-Search) 1: Search for the HealthcareService by ID (null) 4 09:39:29 1s 142ms SUCCESS
Testing search parameters against the HealthcareService resource (@HealthcareService-Search) Search for the HealthcareService by Specialty 3 09:39:33 1s 228ms SUCCESS
Testing search parameters against the HealthcareService resource (@HealthcareService-Search) Search for the HealthcareService by Name 3 09:39:34 1s 022ms SUCCESS
Read Information from a resource of type Schedule (@Schedule-Read) Read a Schedule by ID 8 09:37:35 2s 154ms SUCCESS
Testing search parameters against the Schedule resource (@Schedule-Search) Read and Validation of the CapabilityStatement 2 09:36:57 1s 310ms SUCCESS
Testing search parameters against the Schedule resource (@Schedule-Search) 1: Search for the Schedule by ID (null) 3 09:36:59 1s 010ms SUCCESS
Testing search parameters against the Schedule resource (@Schedule-Search) Search for the Schedule by Active state 3 09:37:01 1s 226ms SUCCESS
Testing search parameters against the Schedule resource (@Schedule-Search) Search for the Schedule by Specialty 3 09:37:03 1s 015ms SUCCESS
Testing search parameters against the Schedule resource (@Schedule-Search) Search for the Schedule by Actor 3 09:37:04 1s 110ms SUCCESS
Read Information from a resource of type Slot (@Slot-Read) Read a Slot by ID 7 09:37:54 1s 771ms SUCCESS
Testing search parameters against the Slot resource (@Slot-Search) 1: Search for the Slot by ID (null) 4 09:38:07 1s 155ms SUCCESS
Testing search parameters against the Slot resource (@Slot-Search) Search for the Slot by Schedule 3 09:38:09 1s 192ms SUCCESS

Manual Tests

No manual tests were recorded

Tags

Terminplanung   20 Appointment-Book   2 Coverage-Read-Statutory   2 Coverage-Search-Private   5 Binary-Read   1 Relatedperson-Read   1 Account-Read   1 Documentreference-Post   4 Condition-Read-Resolved   1 Appointment-Book-By-Schedule   1 Healthcareservice-Search   3 Dokumentenaustausch   11 Composition-Post   4 Relatedperson-Search   2 Documentreference-Search   5 Healthcareservice-Read   1 Stufe5   97 Valueset-Search   2 Encounter-Appointment-Read   1 Encounter-Read-Finished   1 Slot-Read   1 Slot-Search   2 Condition-Read-Active   1 Procedure-Search   3 Basis   66 Account-Search   1 Practitioner-Search   4 Patient-Search   14 Patient-Read   1 Schedule-Search   5 Mandatory   97 Encounter-Read-In-Progress   1 Coverage-Read-Private   1 Documentreference-Read   2 Schedule-Read   1 Precondition   1 Encounter-Read-Planned   1 Condition-Search   3 Practitioner-Read   1 Patient-Read-Extended   1 Appointment-Read   1 Appointment-Search   2 Coverage-Search-Statutory   3 Encounter-Search   10 Valueset-Read   1
Serenity BDD version 4.3.2