|
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
|