Serenity BDD Report
Home > Requirements > Stufe5
Report generated 23-03-2026 09:36

Theme: Stufe5

Feature Coverage By Scenario

Requirements Overview

Key Statistics

Number of Scenarios 248
Total Number of Test Cases 350
Tests Started März 23, 2026 09:36:16
Tests Finished März 23, 2026 09:41:56
Total Duration 5m 40s
Fastest Test 209ms
Slowest Test 24s
Average Execution Time 933ms
Total Execution Time 5m 27s

Feature Coverage By Scenario

Test Outcomes

Test Performance

Key Statistics

Number of Scenarios 248 Total Duration 5m 40s
Total Number of Test Cases 350 Fastest Test 209ms
Number of Manual Test Cases 0 Slowest Test 24s
Tests Started März 23, 2026 09:36:16 Average Execution Time 933ms
Tests Finished März 23, 2026 09:41:56 Total Execution Time 5m 27s

Automated Tests

feature Scenario Context 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
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) 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) Validation of the search parameter definitions in the CapabilityStatement
6 passing test cases
1 09:41:18 1s 369ms SUCCESS
Testing search parameters against a resource of type Account (@Account-Search) Search for the Account by ID
1 passing test case
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 Type 3 09:41:23 1s 212ms 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
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) Precondition 2 09:37:42 422ms 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) Upload of an incorrect DocumentBundle with the POST Operation
3 passing test cases
5 09:37:44 4s 212ms 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 "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) 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
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) 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) Validation of the search parameter definitions in the CapabilityStatement
7 passing test cases
1 09:41:07 1s 595ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by ID
1 passing test case
3 09:41:09 968ms SUCCESS
Testing search parameters against a resource of type Condition (@Condition-Search) Search for the Condition by Count
1 passing test case
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 'subject')
1 passing test case
3 09:41:11 1s 288ms 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
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) 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 "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) Precondition 2 09:40:08 429ms 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) Validation of the search parameter definitions in the CapabilityStatement
6 passing test cases
1 09:36:19 1s 298ms SUCCESS
Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) Search for the Coverage by ID
1 passing test case
3 09:36:20 1s 757ms SUCCESS
Testing search parameters against a resource of type "private" Coverage (@Coverage-Search-Private) Search for the Coverage by Beneficiary and Payor
2 passing test cases
3 09:36:22 1s 931ms 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 "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) Validation of the search parameter definitions in the CapabilityStatement
6 passing test cases
1 09:37:17 1s 306ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Search for the Coverage by ID
1 passing test case
3 09:37:18 943ms SUCCESS
Testing search parameters against a resource of type "statutory" Coverage (@Coverage-Search-Statutory) Search for the Coverage by insured person's number
1 passing test case
3 09:37:19 940ms 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 Type 3 09:37:21 895ms 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) 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 "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) 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 "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) 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
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) 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) Validation of the search parameter definitions in the CapabilityStatement
13 passing test cases
1 09:38:37 3s 042ms SUCCESS
Testing search parameters against a resource of type encounter-read-in-progress (@Encounter-Search) Search for the encounter by ID
1 passing test case
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 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 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 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 '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) 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) 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 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 identifier.system 3 09:39:00 930ms 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) 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 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) Precondition 2 09:39:35 423ms 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) 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) Validation of the search parameter definitions in the CapabilityStatement
14 passing test cases
1 09:40:26 3s 134ms SUCCESS
Testing search parameters against a resource of type Patient (@Patient-Search) Search for Patient by ID
1 passing test case
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 identifier 3 09:40:31 1s 125ms 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 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 gender 3 09:40:36 936ms 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 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 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 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 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 Address (postal code) 3 09:40:54 954ms 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) 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
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) 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) Validation of the search parameter definitions in the CapabilityStatement
5 passing test cases
1 09:37:25 1s 091ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) Search for Practitioner resource by ID
1 passing test case
3 09:37:27 1s 034ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) Search for Practitioner resource by Count
1 passing test case
2 09:37:28 718ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) Search for Practitioner resource by Identifier LANR
1 passing test case
4 09:37:28 1s 154ms SUCCESS
Testing search parameters against a resource of type Practitioner (@Practitioner-Search) Search for Practitioner resource by Identifier Telematik-ID
1 passing test case
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 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
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
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
Read Information from a resource of type Procedure (@Procedure-Read) Read and Validate Procedure by its ID 12 09:36:32 24s 297ms 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) Validation of the search parameter definitions in the CapabilityStatement
8 passing test cases
1 09:39:55 1s 816ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) Search for Procedure resource by ID
1 passing test case
3 09:39:57 956ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) Search for Procedure resource by Count
1 passing test case
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 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) Search for Procedures by Patient reference 3 09:40:03 932ms SUCCESS
Testing search parameters against a resource of type Procedure (@Procedure-Search) Search for Procedures by references
2 passing test cases
3 09:40:04 1s 967ms 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) 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
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) 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) Validation of the search parameter definitions in the CapabilityStatement
3 passing test cases
1 09:39:22 663ms SUCCESS
Testing search parameters against a resource of type RelatedPerson (@RelatedPerson-Search) Search for RelatedPerson by ID
1 passing test case
4 09:39:22 1s 198ms SUCCESS
Testing search parameters against a resource of type RelatedPerson (@RelatedPerson-Search) Search for RelatedPerson resource by Count
1 passing test case
2 09:39:24 847ms SUCCESS
Testing search parameters against a resource of type RelatedPerson (@RelatedPerson-Search) Search for RelatedPerson by Patient ID
1 passing test case
4 09:39:25 1s 140ms 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
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) 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) Validation of the search parameter definitions in the CapabilityStatement
6 passing test cases
1 09:41:37 1s 347ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) Search for ValueSet by ID
1 passing test case
5 09:41:39 1s 546ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) Search for ValueSet resource by Count
1 passing test case
2 09:41:40 686ms SUCCESS
Testing search parameters against a resource of type ValueSet (@ValueSet-Search) Search for ValueSet by additional search parameters
4 passing test cases
3 09:41:41 4s 061ms 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
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) POST an incorrect DocumentBundle
3 passing test cases
5 09:40:18 6s 298ms 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
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) 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) Validation of the search parameter definitions in the CapabilityStatement
9 passing test cases
1 09:38:18 1s 963ms SUCCESS
Testing search parameters against a resource of type DocumentReference (@DocumentReference-Search) Search for the DocumentReference metadata by ID
1 passing test case
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 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 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 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 Category 3 09:38:27 885ms 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) 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 (@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) Precondition 2 09:36:27 416ms 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) 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
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) 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) Validation of the search parameter definitions in the CapabilityStatement
9 passing test cases
1 09:41:46 2s 142ms 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 Service Type 3 09:41:51 1s 169ms 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 Slot 3 09:41:54 1s 132ms 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 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) 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
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) 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) Validation of the search parameter definitions in the CapabilityStatement
6 passing test cases
1 09:39:28 1s 363ms SUCCESS
Testing search parameters against the HealthcareService resource (@HealthcareService-Search) Search for the HealthcareService by ID
1 passing test case
4 09:39:29 1s 142ms 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) Search for the HealthcareService by service type
1 passing test case
3 09:39:32 991ms 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) 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
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) Precondition 2 09:36:56 417ms 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) Validation of the search parameter definitions in the CapabilityStatement
5 passing test cases
1 09:36:58 1s 071ms SUCCESS
Testing search parameters against the Schedule resource (@Schedule-Search) Search for the Schedule by ID
1 passing test case
3 09:36:59 1s 010ms 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 Active state 3 09:37:01 1s 226ms SUCCESS
Testing search parameters against the Schedule resource (@Schedule-Search) Search for the Schedule by Service Type 3 09:37:02 983ms 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) 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
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) 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) Validation of the search parameter definitions in the CapabilityStatement
5 passing test cases
1 09:38:06 1s 093ms SUCCESS
Testing search parameters against the Slot resource (@Slot-Search) Search for the Slot by ID
1 passing test case
4 09:38:07 1s 155ms 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 Schedule 3 09:38:09 1s 192ms 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   80 Appointment-Book   4 Coverage-Read-Statutory   3 Coverage-Search-Private   14 Binary-Read   3 Procedure-Read   3 Relatedperson-Read   3 Account-Read   3 Documentreference-Post   6 Condition-Read-Resolved   3 Appointment-Book-By-Schedule   2 Healthcareservice-Search   14 Dokumentenaustausch   31 Composition-Post   5 Relatedperson-Search   8 Documentreference-Search   21 Healthcareservice-Read   3 Stufe5   350 Valueset-Search   14 Encounter-Appointment-Read   3 Encounter-Read-Finished   3 Slot-Read   3 Slot-Search   13 Condition-Read-Active   3 Procedure-Search   20 Basis   239 Account-Search   14 Practitioner-Search   14 Patient-Search   39 Patient-Read   3 Schedule-Search   13 Mandatory   350 Encounter-Read-In-Progress   3 Coverage-Read-Private   3 Documentreference-Read   4 Schedule-Read   3 Precondition   40 Encounter-Read-Planned   3 Condition-Search   16 Practitioner-Read   3 Patient-Read-Extended   2 Appointment-Read   3 Appointment-Search   19 Coverage-Search-Statutory   14 Encounter-Search   37 Valueset-Read   3
Serenity BDD version 4.3.2