Release 5 Preview #1

This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). 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-search

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

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

identifier: urn:oid:1.3.6.1.4.1.21367.2005.3.7.9881

version: 1.0

name: TestScript Example Search

status: draft

experimental: true

date: 2017-01-18

publisher: HL7

contact:

description: TestScript example resource with simple Patient search test. The read tests will utilize user defined dynamic variables that will hold the Patient search parameter values.

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 Search Operation

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 Search Operationhttp://hl7.org/fhir/http.html#searchCapabilityStatement/example

Fixtures

-AutocreateAutodeleteResource
*falsefalsePeter Chalmers

profile: Generated Summary: id: Bundle; url: http://hl7.org/fhir/StructureDefinition/Bundle; version: 4.2.0; name: Bundle; ACTIVE; date: 31 Dec. 2019, 9:03:40 pm; publisher: Health Level Seven International (FHIR Infrastructure); description: A container for a collection of resources.; 4.2.0; RESOURCE; type: Bundle; baseDefinition: http://hl7.org/fhir/StructureDefinition/Resource; SPECIALIZATION

variable

name: PatientCreateLocation

headerField: Location

sourceId: PatientCreateResponse

variable

name: PatientSearchFamilyName

description: Enter patient search criteria for a known family name on the target system

hint: [Family name]

variable

name: PatientSearchGivenName

description: Enter patient search criteria for a known given name on the target system

hint: [Given name]

variable

name: PatientSearchBundleTotal

description: Evaluate the returned Patient searchset Bundle.total value

expression: Bundle.total.toInteger()

setup

action

Operations

-TypeResourceDescriptionAcceptEncodeRequestUrlParams
*Search (Details: http://terminology.hl7.org/CodeSystem/testscript-operation-codes code search = 'Search', stated as 'null')PatientTest simple search to verify server support.xmltrue?family=DONTEXPECTAMATCH&given=DONTEXPECTAMATCH

action

Asserts

-DescriptionDirectionOperatorRequestURLWarningOnly
*Confirm that the request url contains the family search parameter.requestcontainsfamilyfalse

action

Asserts

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

action

Asserts

-DescriptionResourceWarningOnly
*Confirm that the returned resource type is Bundle.Bundlefalse

action

Asserts

-DescriptionNavigationLinksWarningOnly
*Confirm that the returned Bundle correctly defines the navigation links.truefalse

test

name: Patient Create Search

description: Create a Patient resource and capture the returned HTTP Header Location. Then search for (read) that Patient using the Location URL value and validate the response.

action

Operations

-
*

action

Asserts

-
*

action

Asserts

-
*

action

Operations

-
*

action

Asserts

-
*

action

Asserts

-
*

test

name: Patient Search Dynamic

description: Search for Patient resources using the user defined dynamic variables ${PatientSearchFamilyName} and ${PatientSearchGivenName} and validate response.

action

Operations

-
*

action

Asserts

-
*

action

Asserts

-
*

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.