This wiki has undergone a migration to Confluence found Here
DeviceAlertList FHIR Profile Proposal
Jump to navigation
Jump to search
DeviceAlertList
Profile Details
Parent Resource
Constraints to be Applied
- source = Resource(Device)
- subject = Resource(Device| Patient)
- ordered = True
- mode = snapshot
- entry = Resource(DeviceAlert)
Extensions to be Applied
- None
Example Scenarios
- Fluid line occlusion and low battery technical alarms from an infusion pump.
- Multiple alarms with highest priority severity that have a defined order at the generating device.
Scope of coverage
The DeviceAlertList profile is used to group and communicate the status of multiple alarm condition checks that a medical device is able to detect in a severity sorted order.
Ownership
Owning committee name
Contributing or Reviewing Work Groups
Expected implementations
- Center for Medical Interoperability will be in collaboration with Dräger Medical to work on the profile definition for DeviceAlertList.
gForge Users
TBD
FHIR Profile Development Project Insight ID
TBD
Plans
Timelines
- This proposal will not be addressed in the current DSTU cycle. It is provided as guidance to our intended overall architecture for device communications and will be implemented in the future.