Testscript-example-update - FHIR v6.0.0-ballot2

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 Group

Maturity Level: N/A

Standards Status: Informative

Compartments: 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 testscript-example-update

StructureDefinition Work Group: fhir

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

identifier: Uniform Resource 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: 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

purpose:

Patient (Conditional) Create, Update, Delete Operations

copyright:

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.
capability
required: true
validated: false
description: Patient Update and Delete Operations
link: http://hl7.org/fhir/http.html#update, http://hl7.org/fhir/http.html#delete
capabilities: http://hl7.org/fhir/CapabilityStatement/example

fixture
id
fixture-patient-create
autocreate: false
autodelete: false
resource: Peter Chalmers

fixture
id
fixture-patient-update
autocreate: false
autodelete: false
resource: Donald Duck

profile: Patient

Variables

Name

Path

SourceId

createResourceId

Patient/id

fixture-patient-create

setup
action
Operations

- Type Resource Label Description Accept EncodeRequestUrl Params

* FHIR Restful Interactions delete: delete http://hl7.org/fhir/StructureDefinition/Patient SetupDeletePatient Execute a delete operation to insure the patient does not exist on the server. xml true /${createResourceId}
action
Asserts

- Description Direction Operator ResponseCode StopTestOnFail WarningOnly

* Confirm that the returned HTTP status is 200(OK) or 204(No Content). response in 200,204 false false
action
Operations

- Type Resource Label Description Accept ContentType EncodeRequestUrl Params SourceId

* FHIR Restful Interactions update: update http://hl7.org/fhir/StructureDefinition/Patient SetupCreatePatient Create patient resource on test server using the contents of fixture-patient-create xml xml true /${createResourceId} fixture-patient-create
action
Asserts

- Description Direction ResponseCode StopTestOnFail WarningOnly

* Confirm that the returned HTTP status is 201(Created). response 201 false false

test
id
01-UpdatePatient
name: Update Patient
description: Update a Patient and validate response.
action
Operations

- Type Resource Label Description Accept ContentType EncodeRequestUrl Params SourceId

* FHIR Restful Interactions update: update http://hl7.org/fhir/StructureDefinition/Patient SetupUpdatePatient Update patient resource on test server using the contents of fixture-patient-update xml xml true /${createResourceId} fixture-patient-update
action
Asserts

- Description Response StopTestOnFail WarningOnly

* Confirm that the returned HTTP status is 200(OK). okay false false
action
Asserts

- Description ContentType StopTestOnFail WarningOnly

* Confirm that the returned format is XML. xml false false
action
Asserts

- Description HeaderField Operator StopTestOnFail WarningOnly

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

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.