Release 4

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) in it's permanent home (it will always be available at this URL). 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

Testscript-example-history

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

url: http://hl7.org/fhir/TestScript/testscript-example-history

identifier: urn:oid:1.3.6.1.4.1.21367.2005.3.7.9877

version: 1.0

name: TestScript Example History

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 then update that Patient to create a minimum history; and single test definition to get the history of that Patient with various asserts.

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, Delete and History (Instance) 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, Delete and History (Instance) Operationshttp://hl7.org/fhir/http.html#updateCapabilityStatement/example

fixture

autocreate: false

autodelete: false

resource: Peter Chalmers

fixture

autocreate: false

autodelete: false

resource: Donald Duck

profile: Generated Summary: url: http://hl7.org/fhir/StructureDefinition/Bundle; version: 4.0.1; name: Bundle; ACTIVE; date: 01/11/2019 9:29:23 AM; publisher: Health Level Seven International (FHIR Infrastructure); description: A container for a collection of resources.; 4.0.1; RESOURCE; type: Bundle; baseDefinition: http://hl7.org/fhir/StructureDefinition/Resource; 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

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

action

Asserts

-DescriptionDirectionResponseCodeWarningOnly
*Confirm that the returned HTTP status is 200(OK).response200false

test

name: History Patient

description: Get the history for a known Patient and validate response.

action

Operations

-
*

action

Asserts

-
*

action

Asserts

-
*

action

Asserts

-
*

action

Asserts

-
*

 

 

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.