Difference between revisions of "PCD Brief Profile Proposal 2009 Device Specialization - Infusion Pump"

From IHE Wiki
Jump to navigation Jump to search
m (Initial Version)
 
 
Line 23: Line 23:
  
 
<infusion therapy protocol support>
 
<infusion therapy protocol support>
 +
 +
<MEM support>
  
 
<relationship to comm architecture support>
 
<relationship to comm architecture support>
 
  
 
==Standards & Systems==
 
==Standards & Systems==

Latest revision as of 13:11, 5 October 2009


Proposed Workitem: Device Specialiation - Infusion Pump

  • Proposal Editor: Todd Cooper
  • Editor: TBD
  • Date: N/A (Wiki keeps history)
  • Version: N/A (Wiki keeps history)
  • Domain: Patient Care Devices (PCD)


The Problem

Though the IHE PCD Technical Framework ("TF") provides profile components that may be implemented in an infusion pump or infusion system, end users are interested in specialized configurations of TF constructs that enable specific (esp. clinical) funtionality. Additionally, higher-level clinical integration profiles or ICE-based scenario profiling often call for device classes, such as a ventilator or infusion pumps. These device specialization include appropriate configurations of transactions, content profiles, or persistence / document templates.

This integration profile should address baseline funtionality + optional capabilities that may be tested (at a connectathon), leveraged by other profiles and called out in Integration Statements and RFPs.


Key Use Cases

<device types>

<infusion therapy protocol support>

<MEM support>

<relationship to comm architecture support>

Standards & Systems

<TBD>


Additional Considerations

  1. <tbd>

Discussion

Technological Risks

  • <TBD>