Current Build

Testscript-example

FHIR Infrastructure Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: 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: Jan 18, 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

-UrlDescription
*http://hl7.org/fhir/patient.htmlDemographics and other administrative information about an individual or animal receiving care or other health-related services.

Capabilities

-RequiredValidatedDescriptionLinkCapabilities
*truefalsePatient Update, Read and Delete Operationshttp://hl7.org/fhir/http.html#deleteCapabilityStatement/example

fixture

autocreate: false

autodelete: false

resource: Peter Chalmers

fixture

autocreate: false

autodelete: false

resource: Peter Chalmers (minimum)

profile: Generated Summary: url: http://hl7.org/fhir/StructureDefinition/Patient; version: 4.1.0; name: Patient; ACTIVE; date: Jul 15, 2019 5:48:40 PM; publisher: Health Level Seven International (Patient Administration); description: Demographics and other administrative information about an individual or animal receiving care or other health-related services.; purpose: Tracking patient is the center of the healthcare process.; 4.1.0; RESOURCE; type: Patient; baseDefinition: http://hl7.org/fhir/StructureDefinition/DomainResource; SPECIALIZATION

Variables

-NamePathSourceId
*createResourceIdPatient/idfixture-patient-create

setup

action

Operations

-TypeResourceLabelDescriptionAcceptEncodeRequestUrlParams
*Delete (Details: http://terminology.hl7.org/CodeSystem/testscript-operation-codes code delete = 'Delete', stated as 'null')PatientSetupDeletePatientExecute a delete operation to insure the patient does not exist on the server.jsontrue/${createResourceId}

action

Asserts

-DescriptionDirectionOperatorResponseCodeWarningOnly
*Confirm that the returned HTTP status is 200(OK) or 204(No Content).responsein200,204false

action

Operations

-TypeResourceLabelDescriptionAcceptContentTypeEncodeRequestUrlParamsSourceId
*Update (Details: http://terminology.hl7.org/CodeSystem/testscript-operation-codes code update = 'Update', stated as 'null')PatientSetupCreatePatientCreate patient resource on test server using the contents of fixture-patient-createjsonjsontrue/${createResourceId}fixture-patient-create

action

Asserts

-DescriptionDirectionResponseCodeWarningOnly
*Confirm that the returned HTTP status is 201(Created).response201false

action

Operations

-TypeResourceDescriptionEncodeRequestUrlTargetId
*Read (Details: http://terminology.hl7.org/CodeSystem/testscript-operation-codes code read = 'Read', stated as 'null')PatientRead the created patient resource on the test server using the id from fixture-patient-create. Verify contents.truefixture-patient-create

action

Asserts

-DescriptionDirectionResponseWarningOnly
*Confirm that the returned HTTP status is 200(OK).responseokayfalse

action

Asserts

-DescriptionCompareToSourceIdCompareToSourceExpressionOperatorWarningOnly
*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-createPatient.name.first().familyequalsfalse

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:

  • TestReport/General
  •  

    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.