PCD Brief Profile Proposal 2008 DPI-DnA: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
ToddCooper (talk | contribs)
ToddCooper (talk | contribs)
Line 21: Line 21:
==3. Key Use Case==
==3. Key Use Case==


''<Describe a short use case scenario from the user perspective. The use case should demonstrate the integration/workflow problem.>''
A medical device (e.g., physiological monitor, infusion pump or ventilator) is connected to a patient-local point-of-care networkThe device announces its presence, connects to a manager system, determines the type of connection(s) that can be established and establishes an association with the manager system.  This association includes communication protocol selection and configuration, as well as quality of service support negotiation.
 
''<Feel free to add a second use case scenario demonstrating how it “should” workTry to indicate the people/systems, the tasks they are doing, the information they need, and hopefully where the information should come from.>''
 


==4. Standards & Systems==
==4. Standards & Systems==

Revision as of 12:40, 11 November 2008


1. Proposed Workitem: Device Point-of-care Integration - Discovery and Association (DPI-DnA)

  • Proposal Editor: Todd Cooper
  • Editor: <Name of candidate Lead Editor for the Profile, if known>
  • Date: N/A (Wiki keeps history)
  • Version: N/A (Wiki keeps history)
  • Domain: PCD


2. The Problem

Within the framework of Device Point-of-Care Integration (DPI) profiles, the first step of establishing communication between systems is for a device to announce its presence, discover the system(s) that are managing network communication, and establish an association that will determine how that device can participate in network communications.

This profile shall support those functions needed to support discovery and association of devices in a DPI network.


3. Key Use Case

A medical device (e.g., physiological monitor, infusion pump or ventilator) is connected to a patient-local point-of-care network. The device announces its presence, connects to a manager system, determines the type of connection(s) that can be established and establishes an association with the manager system. This association includes communication protocol selection and configuration, as well as quality of service support negotiation.

4. Standards & Systems

1. ISO/IEEE 11073 standards for medical device communication
2. CEN 13735 (currently being migrated to ISO/IEEE 11073 standards).

5. Discussion

1. This profile is part of a set of DPI profiles that support device conneectivity, especially plug-and-play communication.