This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "DeviceAlert FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 80: Line 80:
 
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document  
 
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document  
 
  -->
 
  -->
 +
This DeviceAlert resource is solely used to communicate a single alarm that produced by any medical device that implements or derives from the ISO/IEEE 11073 standard. If there is a need to communicate multiple alarms are triggered from the same medical device, refers to the DeviceAlertList profile for a more appropriate usage.
  
 
==Expected implementations==
 
==Expected implementations==

Revision as of 18:26, 3 October 2014



DeviceAlert

Owning committee name

Health Care Devices (DEV) WG

Contributing or Reviewing Work Groups

Health Care Devices (DEV) WG

FHIR Resource Development Project Insight ID

TBD

Scope of coverage

The DeviceAlert resource is used to represent the status of a simple alarm condition check that a medical device is able to detect. It represents a single alarm only, and alarm can be one of the following type:

  • Physiological alarm (for example: Low SpO2)
  • Technical alarm (for example: Fluid line occlusion)
  • Advisory alert (for example: Alarm of undocumented timeout prior to a surgical procedure)

Note: For the initial scope, this DeviceAlert resource is only applicable to the alarm condition produced by any medical device that implements or derives from the ISO/IEEE 11073 standard.

RIM scope

TBD

Resource appropriateness

This DeviceAlert resource is solely used to communicate a single alarm that produced by any medical device that implements or derives from the ISO/IEEE 11073 standard. If there is a need to communicate multiple alarms are triggered from the same medical device, refers to the DeviceAlertList profile for a more appropriate usage.

Expected implementations

Content sources

Example Scenarios

Resource Relationships

Timelines

gForge Users