Supply Request

$10 / year

The scope of the SupplyRequest resource is for recording the request of supplies used in the healthcare process. This includes supplies specifically used in the treatment of patients as well as supply movement within an institution (transport a set of supplies from materials management to a service unit (nurse station).

Complexity

The SupplyRequest resource allows requesting only a single item. If a workflow requires requesting multiple items simultaneously, this is done using multiple instances of this resource. These instances can be linked in different ways, depending on the needs of the workflow.

Note that the Supply Request records the fact that a request was made. To actually act on that request, additional workflow beyond simply the existence of a Supply Request is required. This can be achieved by using an Task resource, with the Supply Request referenced from the Task.focus, or by using the SupplyRequest resource in the context of an messaging or service workflow where the request is explicit or implicit. The Supply Delivery resource represents the fulfillment as a result of Supply Request being acted upon.

Date Created

2018-09-20

Last Modified

2018-12-27

Version

4.0.0

Update Frequency

Annual

Temporal Coverage

N/A

Spatial Coverage

United States

Source

John Snow Labs; Health Level Seven International;

Source License URL

Source License Requirements

N/A

Source Citation

N/A

Keywords

FHIR, HL7, Medical Terminology, Processes Data, Processes Information, Processes Documentation, Health Information Exchange, Electronic Health Records, FHIR Smart, Smart on FHIR

Other Titles

FHIR Supply Request Resource, Electronic Health Records Exchange Through FHIR

NameDescriptionTypeConstraints
Concept_NameName of the concept in the FHIR structurestringrequired : 1
Computer_Ready_NameA Computer-ready name (e.g. a token) that identifies the structure - suitable for code generation. Note that this name (and other names relevant for code generation, including element & slice names, codes etc) may collide with reserved words in the relevant target language, and code generators will need to handle this.string-
TypeThe type the structure describes.string-
Dollar_RefThe "$ref" string value contains a Uniform Resource Identifier (URI) which identifies the location of the JSON value being referenced.string-
DescriptionA free text natural language description of the structure and its usestring-
ItemsThe value of the keyword should be an object or an array of objects. If the keyword value is an object, then for the data array to be valid each item of the array should be valid according to the schema in this value.string-
EnumThe value of the keyword should be an array of unique strings. The data object to be valid should contain all properties with names equal to the elements in the keyword value.string-
RequiredThe value of the keyword should be an array of unique strings. The data object to be valid should contain all properties with names equal to the elements in the keyword value.string-
ConstThe value of this keyword can be anything. The data is valid if it is deeply equal to the value of the keyword.string-
Concept_NameComputer_Ready_NameTypeDollar_RefDescriptionItemsEnumRequiredConst
SupplyRequest['quantity', 'resourceType']
SupplyRequest_status#/definitions/ElementExtensions for status
SupplyRequest_language#/definitions/ElementExtensions for language
SupplyRequest_priority#/definitions/ElementExtensions for priority
SupplyRequestresourceTypeThis is a SupplyRequest resourceSupplyRequest
SupplyRequest_authoredOn#/definitions/ElementExtensions for authoredOn
SupplyRequestauthoredOn#/definitions/dateTimeWhen the request was made.
SupplyRequest_ParametervalueBooleanbooleanThe value of the device detail.
SupplyRequestoccurrenceDateTimestringWhen the request should be fulfilled.
SupplyRequest_implicitRules#/definitions/ElementExtensions for implicitRules
Related Data Packages