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 68: | Line 68: | ||
As a rule, Profiles should encompass all of these aspects. | As a rule, Profiles should encompass all of these aspects. | ||
--> | --> | ||
| + | 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== | ==Ownership== | ||
Revision as of 18:18, 3 October 2014
This page documents a Pending FHIR Resource Proposal
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
- Work Group Name
- or link
- or "None"
Expected implementations
gForge Users
FHIR Profile Development Project Insight ID
Plans
Timelines
- TargetDateForInternalReview
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
