Home > Clinical > DeviceCapabilities [devicecapabilities]
Resource DeviceCapabilities - Content4.20
Describes the set of data produced by a device.
The resource name as it appears in a RESTful URL is [root]/devicecapabilities/
There are 4 device related resources
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. (TODO: What's the communication protocol?) 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. The Device Capabilities and Device Log resources may be used in a RESTful context, but in many contexts this will not be very useful - the data should be converted to a device observation for normal RESTful use in a patient care context.
Note that this resource is entirely concerned with devices that report data; interacting with and controlling devices such as infusion pumps etc. is not in scope for this resource (no solution for this yet). This resource is based on ISO 11073.
Structure of the Device Capabilities4.20.0.1
A medical device is conceived of as a measuring device that is capable of reporting a series of groups of measurements on a regular basis. The device capabilities resource describes the kind of data that a medical device reports. Devices are conceptualised using the following main structure:
Very simple devices may have only a single compartment with a single channel and one metric, while complex devices may have multiple items at every level.
When the data emitted by the device is converted to a Device Observation based on the information in the capabilities, and known local context, the Metrics level usually corresponds to a single Observation, but this is not appropriate in all cases.
Resource Content4.20.1
<DeviceCapabilities xmlns="http://hl7.org/fhir"> <!-- from Resource: extension, narrative, and contained --> <name value="[string]"/><!-- 0..1 The name of this device --> <type><!-- 0..1 CodeableConcept The type of device --></type> <manufacturer value="[string]"/><!-- 0..1 Company that built the device --> <identity><!-- 0..1 Resource(Device) Identifies this particular device uniquely --></identity> <virtualDevice> <!-- 0..* A medical-related subsystem of a medical device --> <code><!-- 0..1 CodeableConcept Describes the compartment --></code> <channel> <!-- 0..* Groups related data items --> <code><!-- 0..1 CodeableConcept Describes the channel --></code> <metric> <!-- 0..* Piece of data reported by device --> <code><!-- 1..1 CodeableConcept Describes the metrics --></code> <key value="[string]"/><!-- 1..1 Used to link to data in device log --> <info> <!-- 1..1 How to interpret this metric value --> <type value="[code]"/><!-- 1..1 Quantity | Coding | Array | string --> <units value="[string]"/><!-- 0..1 Human Readable units of data value --> <ucum value="[code]"/><!-- 0..1 UCUM units for data value --> <template><!-- 0..1 SampledData Array template (fixed values) --></template> <system value="[uri]"/><!-- 0..1 System for coding --> </info> <facet> <!-- 0..* Additional clarifying or qualifiying data --> <code><!-- 1..1 CodeableConcept Describes the facet --></code> <scale value="[decimal]"/><!-- 0..1 Factor to apply to raw values (default = 1) --> <key value="[string]"/><!-- 1..1 Used to link to data in device log --> <info><!-- 1..1 Content as for DeviceCapabilities.virtualDevice.channel.metric.info How to interpret this facet value --></info> </facet> </metric> </channel> </virtualDevice> </DeviceCapabilities>
Alternate definitions: Schema/Schematron, Resource Profile
Constraints4.20.1.2
Usage Notes4.20.1.3
Search Parameters for RESTful searches. The standard parameters also apply. See Searching for more information.