This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 4.0.1. For a full list of available versions, see the Directory of published versions
This is the narrative for the resource. See also the XML or JSON format. This example conforms to the profile TestScript.
Generated Narrative with Details
id: search
name: Read, Search and Conditional Create and Delete
description: Test Script for testing search, read, and conditional create and delete
- | Resource |
* | Patient/patient-example.xml |
variable
name: V1
sourceId: R1
headerField: Location
variable
name: V2
sourceId: R3
path: fhir:Patient/fhir:name/fhir:given/@value
setup
action
Operations
- Type Resource Params * delete Patient given=John&family=Doe
test
name: Create
description: Create, read, search, conditional create, conditional delete.
metadata
Links
- Url Description * http://hl7.org/implement/standards/FHIR-Develop/patient.html FHIR Patient operation
type: create
resource: Patient
description: Conditional Create Operation
link: http://hl7-fhir.github.io/http.html#2.1.0.13.1
required: true
validated: true
operation
type: delete
resource: Patient
description: Conditional Delete Operation
link: http://hl7-fhir.github.io/http.html#2.1.0.12.1
required: true
validated: true
operation
type: read
resource: Patient
description: Patient Read Operation
link: http://hl7.org/implement/standards/FHIR-Develop/http.html#read
validated: true
operation
type: search
resource: Patient
description: Patient Search Operation
link: http://hl7-fhir.github.io/http.html#2.1.0.14
validated: true
action
Operations
- * action
Asserts
- * action
Operations
- * action
Asserts
- * action
Asserts
- * action
Operations
- * action
Asserts
- * action
Asserts
- * action
Operations
- * action
Asserts
- * action
Asserts
- * action
Asserts
- * action
Asserts
- * action
Operations
- * action
Asserts
- * action
Operations
- * action
Operations
- * 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.