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

From IHE Wiki
Jump to navigation Jump to search
ToddCooper (talk | contribs)
Jrhoads (talk | contribs)
m add category PCD DPI
 
(5 intermediate revisions by 2 users not shown)
Line 2: Line 2:




==1. Proposed Workitem: Device Point-of-care Integration - Synchronous Communication (DPI-SYC) ==
==1. Proposed Workitem: Device Point-of-care Integration - Symmetric Communication (DPI-SYM) ==


* Proposal Editor: Todd Cooper
* Proposal Editor: Todd Cooper
Line 12: Line 12:
==2. The Problem==
==2. The Problem==


Within the framework of Device Point-of-Care Integration (DPI) profiles, many participating systems not only report their internal information but also have need for discovering, connecting to and retrieving information from external sources.  This discovery and retrieval may be a one time occurrance (e.g., current patient weight), or it may be a persistent connection with specific quality of service requirements needed to support internal algorithmic functions.
Within the framework of Device Point-of-Care Integration (DPI) profiles, many participating systems not only report their internal information but also have need for discovering, connecting to and retrieving information from external sources.  This discovery and retrieval may be a one time occurrance (e.g., current patient weight), or it may be a persistent connection with specific quality of service requirements needed to support internal algorithmic functions.  The information can be from other systems around the point-of-care or from a remote system that is brokered / proxied to the DPI network.


This profile shall support those functions needed to achieve this bi-directional or "symmetric" communication between systems in a DPI network.
This profile shall support those functions needed to achieve this bi-directional or "symmetric" communication between devices and systems in a DPI network.




==3. Key Use Case==
==3. Key Use Case==


''<Infusion pump use case>''
'''<use case with a physiological monitor, ventilator and infusion pump>'''
 
''<Ventilator use case>''


Additional use cases include acute care CRRT (Continuous Renal Replacement Therapy) dialysis systems that not only report their status but also need to collect patient "fluids" information (in & out flows; e.g., from infusion pumps) so as to properly drive their calculations.


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


''<List existing systems that are/could be involved in the problem/solution.>''
:1. ISO/IEEE 11073 standards, including draft 11073-20302 Optional Package - Symmetric Communication


''<If known, list standards which might be relevant to the solution>''
:2. HL7 and IHE Publish & Subscribe Standards / Profiles




==5. Discussion==
==5. Discussion==


''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''
:1. This profile is one of the set of DPI profiles.  It is dependent on the (proposed) DPI-DnA and DPI-DR profiles.
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''
 
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''
:2. The associated standards are either in draft form or need some development.  Completion of this profile is dependent on completion of those standards.
:''<What are some of the risks or open issues to be addressed?>''
 
:3. The draft 11073-20302 standard could be seen as overly heavy for applications where a device needs a simple parameter for display.




[[Category:PCD]]
[[Category:PCD]][[Category:PCD DPI]]

Latest revision as of 17:19, 28 January 2009


1. Proposed Workitem: Device Point-of-care Integration - Symmetric Communication (DPI-SYM)

  • 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, many participating systems not only report their internal information but also have need for discovering, connecting to and retrieving information from external sources. This discovery and retrieval may be a one time occurrance (e.g., current patient weight), or it may be a persistent connection with specific quality of service requirements needed to support internal algorithmic functions. The information can be from other systems around the point-of-care or from a remote system that is brokered / proxied to the DPI network.

This profile shall support those functions needed to achieve this bi-directional or "symmetric" communication between devices and systems in a DPI network.


3. Key Use Case

<use case with a physiological monitor, ventilator and infusion pump>

Additional use cases include acute care CRRT (Continuous Renal Replacement Therapy) dialysis systems that not only report their status but also need to collect patient "fluids" information (in & out flows; e.g., from infusion pumps) so as to properly drive their calculations.

4. Standards & Systems

1. ISO/IEEE 11073 standards, including draft 11073-20302 Optional Package - Symmetric Communication
2. HL7 and IHE Publish & Subscribe Standards / Profiles


5. Discussion

1. This profile is one of the set of DPI profiles. It is dependent on the (proposed) DPI-DnA and DPI-DR profiles.
2. The associated standards are either in draft form or need some development. Completion of this profile is dependent on completion of those standards.
3. The draft 11073-20302 standard could be seen as overly heavy for applications where a device needs a simple parameter for display.