Test Name |
Description |
Status |
Duration |
Test: Step1-CreateNewDocumentReference |
Create a new DocumentReference in JSON format where the client assigns the resource id. The expected response code is 201 (Created) with a content of either the created DocumentReference resource in JSON format, an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
Test: Step1-CreateNewDocumentReference |
Create a new DocumentReference in JSON format where the client assigns the resource id. The expected response code is 201 (Created) with a content of either the created DocumentReference resource in JSON format, an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
|
Test: Step2-ReadDocumentReference |
Read the DocumentReference in JSON format created in step 1. The expected response code is 200 (OK) with a content of the found DocumentReference resource in JSON format. |
Failed |
|
Test: Step2-ReadDocumentReference |
Read the DocumentReference in JSON format created in step 1. The expected response code is 200 (OK) with a content of the found DocumentReference resource in JSON format. |
Failed |
|
|
Test: Step3-UpdateDocumentReference |
Update the DocumentReference created in step 1 in JSON format. The expected response code is 200 (OK) with a content of either the updated DocumentReference resource in JSON format, an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
Test: Step3-UpdateDocumentReference |
Update the DocumentReference created in step 1 in JSON format. The expected response code is 200 (OK) with a content of either the updated DocumentReference resource in JSON format, an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
|
Test: Step4-DocumentReferenceHistoryInstance |
Retrieve the updated DocumentReference instance's history in JSON format. The expected response code is 200 (OK) with a Bundle resource in JSON format of type history containing the created and updated versions of the DocumentReference. |
Failed |
|
Test: Step4-DocumentReferenceHistoryInstance |
Retrieve the updated DocumentReference instance's history in JSON format. The expected response code is 200 (OK) with a Bundle resource in JSON format of type history containing the created and updated versions of the DocumentReference. |
Failed |
|
|
Test: Step5-DocumentReferenceVersionRead |
Retrieve a initially created version of a DocumentReference instance in JSON format. The expected response code, if versioning is supported, is 200 (OK) with a content of the updated DocumentReference resource in JSON format; if versioning is not supported, a 404 (Not Found) with an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
Test: Step5-DocumentReferenceVersionRead |
Retrieve a initially created version of a DocumentReference instance in JSON format. The expected response code, if versioning is supported, is 200 (OK) with a content of the updated DocumentReference resource in JSON format; if versioning is not supported, a 404 (Not Found) with an OperationOutcome resource in JSON format or an empty payload. |
Failed |
|
|
Test: Step6-DocumentReferenceSearchType |
Search for DocumentReference resources in JSON format with an identifier equal to ${searchParamIdentifier}. The expected response code is 200 (OK) with a Bundle resource in JSON format of type history containing the found instances of the DocumentReference. |
Failed |
|
Test: Step6-DocumentReferenceSearchType |
Search for DocumentReference resources in JSON format with an identifier equal to ${searchParamIdentifier}. The expected response code is 200 (OK) with a Bundle resource in JSON format of type history containing the found instances of the DocumentReference. |
Failed |
|
|
Test: Step7-DocumentReferenceDelete |
Delete a DocumentReference instance in JSON format. The expected response is either a 200 (OK) with an optional OperationOutcome in JSON format or 204 (No Content) and the content is empty; i.e. no content. |
Failed |
|
Test: Step7-DocumentReferenceDelete |
Delete a DocumentReference instance in JSON format. The expected response is either a 200 (OK) with an optional OperationOutcome in JSON format or 204 (No Content) and the content is empty; i.e. no content. |
Failed |
|
|