Embedded Files
Home ＞ Administrative ＞ Device [device]
Resource Device - Content5.5
This resource identifies an instance of a manufactured thing that is used in the provision of healthcare without being substantially changed through that activity. The device may be a machine, an insert, a computer, an application, etc. This includes durable (reusable) medical equipment as well as disposable equipment used for diagnostic, treatment, and research for healthcare and public health.
The resource name as it appears in a RESTful URL is [root]/device/
This resource identifies an instance of a manufactured thing that is used in the provision of healthcare without being substantially changed through that activity. The device may be a machine, an insert, a computer, an application, etc. This includes durable (reusable) medical equipment as well as disposable equipment used for diagnostic, treatment, and research for healthcare and public health. Primarily used for recording which device performed an action and can also be used to track device location. Can also be used for prescribing and dispensing devices for patient use.
There are 4 device related resources
- Device (this resource) - an administrative resource that tracks individual devices and their location. Primarily used for attribution of actions to devices
- Device Capabilities - Defines what observations a device will provide when another device connects to it
- Device Log - A raw report from a device at a point in time. Must be paired with the correct Device Capabilities resource in order to be processed
- Device Observation - A report of observations from a device
The device capabilities and log resources are used when communicating with a device, either directly or indirectly. When a channel is opened with the device, or its proxy, it first sends the Capabilities resource, and then a series of log resources. The FHIR JSON format is used in this case.
The application that receives the log resources may choose to merge the log with the capabilities statement to create a device observation, which is suitable for wider use within a EHR/Clinical record context.
Resource Content5.5.1
<Device xmlns="http://hl7.org/fhir"> <!-- from Resource: extension, narrative, and contained --> <type><!-- 1..1 CodeableConcept What kind of device this is --></type> <manufacturer value="[string]"/><!-- 0..1 Name of device manufacturer --> <model value="[string]"/><!-- 0..1 Model id assigned by the manufacturer --> <version value="[string]"/><!-- 0..1 Version number (i.e. software) --> <expiry value="[date]"/><!-- 0..1 Date of expiry of this device (if applicable) --> <identity> <!-- 0..1 Universal Device Id fields --> <gtin value="[string]"/><!-- 0..1 Global Trade Identification Number --> <lot value="[string]"/><!-- 0..1 Lot number of manufacture --> <serialNumber value="[string]"/><!-- 1..1 Serial number assigned by the manufacturer --> </identity> <owner><!-- 0..1 Resource(Organization) Organization responsible for device --></owner> <assignedId><!-- 0..* Identifier Identifier assigned by various organizations --></assignedId> <location><!-- 0..1 Resource(Location) Where the resource is found --></location> <patient><!-- 0..1 Resource(Patient) If the resource is affixed to a person --></patient> <contact><!-- 0..* Contact Details for human/organization for support --></contact> <url value="[uri]"/><!-- 0..1 Network address to contact device --> </Device>
Alternate definitions: Schema/Schematron, Resource Profile
Terminology Bindings 5.5.1.1
Search Parameters 5.5.2
Search Parameters for RESTful searches. The standard parameters also apply. See Searching for more information.
Google Sites
Report abuse