This page is part of the FHIR Specification (v3.5.0: R4 Ballot #2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2
FHIR Infrastructure Work Group | Maturity Level: N/A | Ballot Status: Informative | Compartments: Not linked to any defined compartments |
This is the narrative for the resource. See also the XML, JSON or Turtle format. This example conforms to the profile TestScript.
Generated Narrative with Details
id: testscript-example
url: http://hl7.org/fhir/TestScript/testscript-example
identifier: urn:oid:1.3.6.1.4.1.21367.2005.3.7.9876
version: 1.0
name: TestScript Example
status: draft
experimental: true
date: 18/01/2017
publisher: HL7
contact:
description: TestScript example resource with setup to delete if present and create a new instance of a Patient; and single test definition to read the created Patient with various asserts.
useContext:
jurisdiction: United States of America (the) (Details : {urn:iso:std:iso:3166 code 'US' = 'United States of America', given as 'United States of America (the)'})
purpose: Patient Conditional Create (Update), Read and Delete Operations
copyright: © HL7.org 2011+
metadata
Links
- Url Description * http://hl7.org/fhir/patient.html Demographics and other administrative information about an individual or animal receiving care or other health-related services. Capabilities
- Required Validated Description Link Capabilities * true false Patient Update, Read and Delete Operations http://hl7.org/fhir/http.html#delete CapabilityStatement/example
fixture
autocreate: false
autodelete: false
resource: Peter Chalmers
fixture
autocreate: false
autodelete: false
resource: Peter Chalmers (minimum)
- | Name | Path | SourceId |
* | createResourceId | Patient/id | fixture-patient-create |
setup
action
Operations
- Type Resource Label Description Accept EncodeRequestUrl Params * Delete (Details: http://terminology.hl7.org/CodeSystem/testscript-operation-codes code delete = 'Delete', stated as 'null') Patient SetupDeletePatient Execute a delete operation to insure the patient does not exist on the server. json true /${createResourceId} action
Asserts
- Description Direction Operator ResponseCode WarningOnly * Confirm that the returned HTTP status is 200(OK) or 204(No Content). response in 200,204 false action
Operations
- Type Resource Label Description Accept ContentType EncodeRequestUrl Params SourceId * Update (Details: http://terminology.hl7.org/CodeSystem/testscript-operation-codes code update = 'Update', stated as 'null') Patient SetupCreatePatient Create patient resource on test server using the contents of fixture-patient-create json json true /${createResourceId} fixture-patient-create action
Asserts
- Description Direction ResponseCode WarningOnly * Confirm that the returned HTTP status is 201(Created). response 201 false action
Operations
- Type Resource Description EncodeRequestUrl TargetId * Read (Details: http://terminology.hl7.org/CodeSystem/testscript-operation-codes code read = 'Read', stated as 'null') Patient Read the created patient resource on the test server using the id from fixture-patient-create. Verify contents. true fixture-patient-create action
Asserts
- Description Direction Response WarningOnly * Confirm that the returned HTTP status is 200(OK). response okay false action
Asserts
- Description CompareToSourceId CompareToSourceExpression Operator WarningOnly * Confirm that the returned Patient contains the expected family name 'Chalmers'. Uses explicit compareToSourceId reference to fixture-patient-create used to create the Patient. fixture-patient-create Patient.name.first().family equals false
test
name: Read Patient
description: Read a Patient and validate response.
action
Operations
- * action
Asserts
- * action
Asserts
- * action
Asserts
- * action
Asserts
- * action
Asserts
- * action
Asserts
- * action
Asserts
- * action
Asserts
- * action
Asserts
- *
teardown
action
Operations
- *
Other examples that reference this example:
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.