PCD Brief Profile Proposal 2008 DPI-DnA

From IHE Wiki
Jump to: navigation, search


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

  • Proposal Editor: Todd Cooper, Jan Wittenber
  • 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.
2. Several profiles (A-D in the following Table) are defined to evolve over IHE PCD DPI, based on capabilities and vintage of interconnecting device, e.g. medical device or gateway. In general, the following functions are incorporated in the layered services (adapted from IEEE P11073-20401, Common IP Services):
  • Obtaining IP addresses,
  • Service advertisement & discovery,
  • Timely message delivery,
  • Network access control,
  • Network availability,
  • Quality of service,
  • Time services,
  • Network management services,
  • Security and authentication.
  • Also included is any appropriate Ethernet (layer 2) switching and VLAN functionality.


Profile Composition
  A B C D
Service Level/Layer1        
Application        
        • Time Service SNTP
        • TimelyMsgDelivery RTP
        • Net Mgmt SNMP
        • Medical Device Info Base (MDIB)   IEEE 11073-10101, -10201, -20101;
CEN 13735
IEEE 11073-20601
        • Dynamic Host Discov. Non-DHCP/bootp DHCP/bootp  
        • Advert./Discovery   “CI” 2  
Transport  
        • Inter-Network Non-IP TCP-, UDP/IP
                ° Network Non-IEEE802 IEEE8023
        • Data/Physical Link  
                ° Mode Non-IEEE 11073-based IEEE 11073-30200 or -30300-based Wired Wireless
                ° MAC IEEE 802.3-based IEEE 802.11 based IEEE 802.15 based
                ° Security/Access Ctl 802.1x 802.11i  
                ° QoS   802.11e  
Key: Italicized elements are preferably dynamically coordinated but conditional pre-coordination properties may be specified in particular IHE PCD DPI profiles, esp. for initial deployment.
1 ISO OSI or Internet architectural layer hybridized for simplicity.
2 “Connection Indication (CI)” PDU required for dynamic MDIB initiation
3 Wired ↔ Wireless inter-mode may be deployed with suitable precoordination of switching method