FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Example TestScript/testscript-example-update (Narrative)

FHIR Infrastructure Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: No 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: TestScript

Resource TestScript "testscript-example-update"

StructureDefinition Work Group: fhir

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

identifier: URI/urn:oid:2.16.840.1.113883.4.642.12.5

version: 1.0

name: TestScriptExampleUpdate

title: TestScript Example Update

status: draft

experimental: true

date: 2017-01-18

publisher: HL7 International / FHIR Infrastructure

contact: Support: http://www.hl7.org/Special/committees/fiwg

description: TestScript example resource with setup to delete if present and create a new instance of a Patient; and single test definition to update that Patient with various asserts.

jurisdiction: United States of America (ISO 3166-1 Codes for the representation of names of countries and their subdivisions — Part 1: Country code#US)

purpose: Patient (Conditional) Create, Update, 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 and Delete Operationshttp://hl7.org/fhir/http.html#update, http://hl7.org/fhir/http.html#deletehttp://hl7.org/fhir/CapabilityStatement/example

fixture

autocreate: false

autodelete: false

resource: Patient/example: Peter Chalmers "Peter CHALMERS"

fixture

autocreate: false

autodelete: false

resource: Patient/pat1: Donald Duck "Donald DUCK"

profile: Patient

Variables

-NamePathSourceId
*createResourceIdPatient/idfixture-patient-create

setup

action

Operations

-TypeResourceLabelDescriptionAcceptEncodeRequestUrlParams
*delete (Details: http://hl7.org/fhir/restful-interaction code delete = 'delete', stated as 'null')PatientSetupDeletePatientExecute a delete operation to insure the patient does not exist on the server.xmltrue/${createResourceId}

action

Asserts

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

action

Operations

-TypeResourceLabelDescriptionAcceptContentTypeEncodeRequestUrlParamsSourceId
*update (Details: http://hl7.org/fhir/restful-interaction code update = 'update', stated as 'null')PatientSetupCreatePatientCreate patient resource on test server using the contents of fixture-patient-createxmlxmltrue/${createResourceId}fixture-patient-create

action

Asserts

-DescriptionDirectionResponseCodeStopTestOnFailWarningOnly
*Confirm that the returned HTTP status is 201(Created).response201falsefalse

test

name: Update Patient

description: Update a Patient and validate response.

action

Operations

-TypeResourceLabelDescriptionAcceptContentTypeEncodeRequestUrlParamsSourceId
*update (Details: http://hl7.org/fhir/restful-interaction code update = 'update', stated as 'null')PatientSetupUpdatePatientUpdate patient resource on test server using the contents of fixture-patient-updatexmlxmltrue/${createResourceId}fixture-patient-update

action

Asserts

-DescriptionResponseStopTestOnFailWarningOnly
*Confirm that the returned HTTP status is 200(OK).okayfalsefalse

action

Asserts

-DescriptionContentTypeStopTestOnFailWarningOnly
*Confirm that the returned format is XML.xmlfalsefalse

action

Asserts

-DescriptionHeaderFieldOperatorStopTestOnFailWarningOnly
*Confirm that the returned HTTP Header Last-Modified is present. Warning only as the server might not support versioning.Last-ModifiednotEmptyfalsetrue

 

 

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.