This wiki has undergone a migration to Confluence found Here
Difference between revisions of "DeviceAlertList FHIR Profile Proposal"
Jump to navigation
Jump to search
Line 100: | Line 100: | ||
<!-- Indicate the target date for having the Profile complete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the Profile complete from a committee perspective and ready for vetting and voting --> | ||
− | * | + | * Ready for Draft for Comment ballot: January 2015 |
+ | * Complete for DSTU 2.0: August 2015 | ||
===Balloting Requirements=== | ===Balloting Requirements=== |
Revision as of 18:22, 3 October 2014
DeviceAlertList
Profile Details
Parent Resource
- [List]
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
- Ready for Draft for Comment ballot: January 2015
- Complete for DSTU 2.0: August 2015
Balloting Requirements
Choose one:
- Ballot with next FHIR DSTU or Normative Edition
- or Ballot independently as DSTU
- or Realm specific ballot
- or No Ballot
Desired Ballot Date
- PutDesiredBallotDateHere