This point-of-care device manager starts and ends a monitoring session:

+

This point-of-care '''Device Manager''' starts and ends a monitoring session using FHIR resources to start/stop monitoring:

−

* The creates a [http://hl7-fhir.github.io/procedure.html Procedure] when a

+

* The Device Manager ''creates'' a [http://hl7-fhir.github.io/procedure.html Procedure] when a patient starts to be monitored by a vital signs monitor ** The [http://hl7-fhir.github.io/procedure.html Procedure] will reference a contained [http://hl7-fhir.github.io/device.html Device] resources

−

patient starts to be monitored by a vital signs monitor

+

** The [http://hl7-fhir.github.io/device.html Device] will use [http://hl7-fhir.github.io/device-definitions.html#Device.udiCarrier Device.udiCarrier] to specify the device using its manufacturer-assigned UDI.

** The [http://hl7-fhir.github.io/device.html Device] will use [http://hl7-fhir.github.io/device-definitions.html#Device.udiCarrier Devie.udiCarrier] to specify the device using its manufacturer assigned UDI.

+

'''NOTE:''' This is a new capability to the IHE PCD Technical Framework that allows a Device Manager to assign devices to a patient.

+

Currently such solutions ad-hoc HL7 V2 visit or appointment to start and stop a monitoring session.

Device Data Integration

The focus for this track is the exchange of information from a variety of healthcare devices, such as a simple pulse oximeter, a physiological monitor or an infusion pump, to other applications and systems such as EHR flowsheets or electronic medication administration records (eMAR). Scenarios and test scripts will ensure that at least 80% of the core data elements for these device-related resources are leveraged. Data exchanged will be consistent (per resource mappings) with the ISO/IEEE 11073 standards for device semantic content. This will include integration of data that is sourced from an IEEE 11073-based Personal Health Device (PHD), as well as, communicated using the HL7 v2-based profiles supported by the IHE Patient Care Device (PCD) group.

For the 2016-09 track, device data will include physiological data ("observations"),both periodic and aperiodic, and device settings. Waveform data may be considered as a stretch goal; however, device alert information will be deferred to a subsequent FHIR connectathon.

NOTE: Subsequent FHIR connectathon tracks will include more advanced scenarios and applications, such as medication administration or CDS utilization of real-time high granularity device acquired information.

Submitting WG/Project/Implementer Group

Justification

This track is intended to advance the maturity of device-related FHIR resources (i.e., Device, DeviceComponent and DeviceMetric) to FMM2 (see FHIR Maturity Model). It will test mappings for the ISO/IEEE 11073 information model, as well as the IHE Patient Care Device (PCD) profiles based on HL7 v2. This work will inform the potential development of an implementation guide for device information integration, as well as the possible definition of profiles for specific device modalities (e.g., an LVP Infusion Pump).

NOTE: This is a new capability to the IHE PCD Technical Framework that allows a Device Manager to assign devices to a patient.
Currently such solutions ad-hoc HL7 V2 visit or appointment to start and stop a monitoring session.

(from Eric Haas) "As far as the Argonaut work. Our goal was to establish the minimal requirements for meeting the MU 2015 CCDS requirements and hence only the carrier string is mandatory. However for the this track, I think there many use cases where the PI and DI would be present instead of or in addition to it."

(from Hans B.) Per Eric's quote above: "As part of the use case outside of logistics I would suggest not to use 'instead of', rather address the UDI carrier in HRF plus one, some, or all of the UDI components."

Scenario 1: <Acute Care Reporting Scenario>

Scenario 2: <PHD Reporting Scenario>

Scenario 3: <CDS Scenario>

This scenario uses FHIR Procedure and Device to associate a patient to one or more device(s) and operator/nurse/physician who configured or implanted the device. The device will be identified using the UDI scanned at the point of care along the patient id wristband, and the provider's badge.

Create a FHIR Procedure specifying the patient, the device or devices involved, and the operator (i.e. nurse, respiratory therapist, etc) or provider who configured the device, validated its configuration and initiated the procedure.

If the device is implanted, a FHIR Device resource will associate the patient with the implanted device. The Patient Device List will be created by querying the EHR using a Device.search (by patient) operation.

If the device is used monitor the patient or administer medication the procedure indicates duration, the associated medication order.

Implantable Devices

This scenario relies on scanning the UDI in order to convey information about devices implanted to during a procedure.
The Medical Device Adapter (FHIR client) submits to the EHR (FHIR server):