http://wiki.ihe.net/api.php?action=feedcontributions&user=Bikram&feedformat=atomIHE Wiki - User contributions [en]2024-03-29T01:47:14ZUser contributionsMediaWiki 1.35.5http://wiki.ihe.net/index.php?title=PCD_Tools&diff=45688PCD Tools2010-10-19T18:59:59Z<p>Bikram: /* IHE-PCD Testing Tools */</p>
<hr />
<div>== IHE-PCD Testing Tools ==<br />
<br />
'''Medical Enterprise Simulators and Analyzer (MESA)'''<br />
* The latest version of the [http://ihedoc.wustl.edu MESA Test Tools]<br />
<br />
<br />
'''NIST Medical Device Communication Test Tools (based on ISO/IEEE 11073)'''<br />
* [http://www.nist.gov/medicaldevices/ ICSGenerator and ValidatePDU]<br />
<br />
<br />
'''NIST HL7 V2 Tools''' <br />
* [http://xreg2.nist.gov:8080/HL7Web/index.html Message Validation, Profile Validation, and Message Generation]<br />
<br />
<br />
'''NIST CDA Guideline Validation'''<br />
* [http://xreg2.nist.gov/cda-validation/index.html CDA Guideline Validation Tool]<br />
<br />
'''Alschuler Associates CDA Validation'''<br />
* [http://www.alschulerassociates.com/validator/ CDA Validator]<br />
<br />
<br />
'''HIT Implementation Testing and Support (ONC/NHIN, HITSP, CCHIT, and NIST)'''<br />
* [http://xreg2.nist.gov/hit-testing/ Testing and Support web site for the Nationwide Health Information Network (NHIN) Initiative]<br />
<br />
'''HL7 utility tools for testing with NIST tools'''<br />
* [http://nule.org/wp/?page_id=55 {nule.org}] Useful cross-platform (java) utilities that help capture and allow HL7 browser capabilities that complement the NIST test tools. <br />
<br />
'''Peter Rontey, VHA Office of Information Messaging and Interface Services'''<br />
* [http://www.hl7.org/special/committees/ictc/docs.cfm Messaging Work Bench (MWB) HL7 site - Implementation and Conformance web page]<br />
* [https://ihe.webex.com/ihe/lsr.php?AT=pb&SP=MC&rID=28385312&rKey=E3D0394C8A8A1D8D Advanced Usage Webinar (2008.11.17)]<br />
<br />
==See Also==<br />
<br />
'''Medical Enterprise Simulators and Analyzer (MESA)'''<br />
* The latest version of the [http://ihedoc.wustl.edu MESA Test Tools]<br />
<br />
<br />
'''NIST Medical Device Communication Test Tools (based on ISO/IEEE 11073)'''<br />
* [http://www.nist.gov/medicaldevices/ ICSGenerator and ValidatePDU]<br />
<br />
<br />
'''NIST HL7 V2 Tools''' <br />
* [http://xreg2.nist.gov:8080/HL7Web/index.html Message Validation, Profile Validation, and Message Generation]<br />
<br />
<br />
'''NIST CDA Guideline Validation'''<br />
* [http://xreg2.nist.gov/cda-validation/index.html CDA Guideline Validation Tool]<br />
<br />
<br />
'''Alschuler Associates CDA Validation'''<br />
* [http://www.alschulerassociates.com/validator/ CDA Validator]<br />
<br />
<br />
'''HIT Implementation Testing and Support (ONC/NHIN, HITSP, CCHIT, and NIST)'''<br />
* [http://xreg2.nist.gov/hit-testing/ Testing and Support web site for the Nationwide Health Information Network (NHIN) Initiative]<br />
<br />
<br />
'''Peter Rontey, VHA Office of Information Messaging and Interface Services'''<br />
* [http://www.hl7.org/special/committees/ictc/docs.cfm Messaging Work Bench (MWB) HL7 site - Implementation and Conformance web page]<br />
* [https://ihe.webex.com/ihe/lsr.php?AT=pb&SP=MC&rID=28385312&rKey=E3D0394C8A8A1D8D Advanced Usage Webinar (2008.11.17)]<br />
<br />
<br />
'''MindJet "MindMap" Readers'''<br />
* [http://www.mindjet.com/resources/downloads/mm_viewer.aspx Readers for .mmap files sometimes used during PCD development activities.]<br />
<br />
<br />
==See Also==<br />
[[Implementation#Implementation_Tools| IHE Implementation Tools]]<br />
<br />
<br />
[[Category:PCD]]</div>Bikramhttp://wiki.ihe.net/index.php?title=PCD_Virtual_Connectathon_Testing_2010&diff=35442PCD Virtual Connectathon Testing 20102009-08-11T19:16:04Z<p>Bikram: Removing all content from page</p>
<hr />
<div></div>Bikramhttp://wiki.ihe.net/index.php?title=PCD_Pre-Connectathon_Testing_2010&diff=35441PCD Pre-Connectathon Testing 20102009-08-11T19:15:14Z<p>Bikram: DynDNS VPN virtual pre-connectathon</p>
<hr />
<div>== Using Dynamic DNS to map your home (or work) Dynamic IP address to a DNS name. ==<br />
<br />
<br />
There are several providers who do this, I have used DynDns.com[http://www.dyndns.com/services/dns/dyndns/] for several years with good results.<br />
Your home router may support this or other vendors, check your router configuration/help files for this information. You can also run an update client on a machine on your home network. All the services needed to do this should be '''free''', you ''should '''not''' need'' to purchase premium services.<br />
<br />
Here is the '''Howto'''[http://www.dyndns.com/services/dns/dyndns/howto.html] to do this.''' Be sure to read the README''' [http://www.dyndns.com/services/dns/dyndns/readme.html]''' before!<br />
'''<br />
Another vendor that provides this service is '''FreeDNS'''[http://freedns.afraid.org/].</div>Bikramhttp://wiki.ihe.net/index.php?title=PCD_Virtual_Connectathon_Testing_2010&diff=35440PCD Virtual Connectathon Testing 20102009-08-11T18:51:00Z<p>Bikram: DynDNS VPN virtual connectathon</p>
<hr />
<div>== Using Dynamic DNS to map your home (or work) Dynamic IP address to a DNS name. ==<br />
<br />
<br />
There are several providers who do this, I have used DynDns.com[http://www.dyndns.com/services/dns/dyndns/] for several years with good results.<br />
Your home router may support this or other vendors, check your router configuration/help files for this information. You can also run an update client on a machine on your home network. All the services needed to do this should be '''free''', you ''should '''not''' need'' to purchase premium services.<br />
<br />
Here is the '''Howto'''[http://www.dyndns.com/services/dns/dyndns/howto.html] to do this.''' Be sure to read the README''' [http://www.dyndns.com/services/dns/dyndns/readme.html]''' before!<br />
'''<br />
Another vendor that provides this service is '''FreeDNS'''[http://freedns.afraid.org/].</div>Bikramhttp://wiki.ihe.net/index.php?title=PCD_Technical_Committee&diff=14807PCD Technical Committee2008-03-21T19:51:25Z<p>Bikram: /* Roster */</p>
<hr />
<div>==Roster==<br />
<br />
Committee participation is open and voluntary. Roster is based on attendance at one TCON or Face-to-Face meeting within an 18-month period. Policy regarding membership status is being finalized so this list may be adjusted to reflect the policy decision and follow the format of the [[Committee Template|Committee Page Template]]. <br />
<br />
Representatives with a '''[[Roster Status]]''' of '''Co-chair''', '''Liaison''', '''Voting''' (or possibly '''Alternate''') may vote and count towards quorum. A - represents a missed meeting.<br />
<br />
Representatives with a '''[[Roster Status]]''' of '''Secretary''' or '''Non-voting''' or may not vote or count towards quorum. A + represents an attended meeting.<br />
<br />
{| style="width:85%" border="1" cellpadding="3"<br />
! Name<br />
! Title<br />
! Member Organization<br />
! Roster Status<br />
<br />
|-<br />
|Todd Cooper<br />
|President<br />
|Breakthrough Solutions<br />
|Co-chair<br />
|-<br />
|Jack J. Harrington<br />
|Sr. Director Integrated Solutions<br />
|Philips Medical Systems<br />
|Co-chair<br />
|-<br />
|Jonathan Barmettler<br />
|Senior Consultant<br />
|ACS<br />
|&nbsp;<br />
|-<br />
|Jeff Secunda<br />
|Associate Vice President, Technology & Regulatory Affairs<br />
|AdvaMed<br />
|&nbsp;<br />
|-<br />
|J. Michael Fitzmaurice PhD, FACMI<br />
|Sr. Science Advisor for Information Technology<br />
|Agency for Healthcare Research and Quality<br />
|&nbsp;<br />
|-<br />
|Cathy Glenz<br />
|Sr. Software Consultant and Director Interoperability<br />
|Alert Life Sciences Computing, Inc.<br />
|&nbsp;<br />
|-<br />
|Melvin I. Reynolds, MISciT, MBCS<br />
|&nbsp;<br />
|AMS Consulting<br />
|&nbsp;<br />
|-<br />
|Alan Lang<br />
|Program Manager of Research<br />
|ASTRO<br />
|&nbsp;<br />
|-<br />
|Slav Lerner<br />
|Sr. Business Development Manager<br />
|Auriga<br />
|&nbsp;<br />
|-<br />
|Steve Merritt<br />
|&nbsp;<br />
|Bay State Healthcare System<br />
|&nbsp;<br />
|-<br />
|Michael J. Zakrewski<br />
|Product Director<br />
|B. Braun Medical, Inc.<br />
|&nbsp;<br />
|-<br />
|Marcia A. Wylie<br />
|Director<br />
|Biomedical Engineering<br />
|&nbsp;<br />
|-<br />
|Lionel Michael Fraai, MS, CCE<br />
|Director<br />
|Brigham and Women's Hospital<br />
|&nbsp;<br />
|-<br />
|Jennifer L. Jackson, MBA, CCE<br />
|Assistant Director<br />
|Brigham and Women's Hospital<br />
|&nbsp;<br />
|-<br />
|Beth Hurter<br />
|Director of Product Development<br />
|CapMed <br />
|&nbsp;<br />
|-<br />
|Bikram Day<br />
|&nbsp;<br />
|[http://www.capsuletech.com Capsule Technologies]<br />
|&nbsp;<br />
|-<br />
|John McHutcheon<br />
|&nbsp;<br />
|[http://www.capsuletech.com Capsule Technologies]<br />
|&nbsp;<br />
|-<br />
|Rich Fronek<br />
|&nbsp;<br />
|Cardiac Science<br />
|&nbsp;<br />
|-<br />
|Jeremy R. Malecha<br />
|&nbsp;<br />
|CardioDynamics<br />
|&nbsp;<br />
|-<br />
|Chris Riha<br />
|Director of Clinical Systems Engineering<br />
|Carilion Health System<br />
|&nbsp;<br />
|-<br />
|Bob Fetters<br />
|&nbsp;<br />
|Catalyst Consulting of Kennett<br />
|&nbsp;<br />
|-<br />
|Timothy T. Jimenez<br />
|Solutions Designer<br />
|Cerner<br />
|&nbsp;<br />
|-<br />
|Mark Scnhell<br />
|&nbsp;<br />
|Cisco Systems, Inc. Technology Center<br />
|&nbsp;<br />
|-<br />
|Robert Tassin, MD<br />
|CMR Physician Support Director<br />
|C & M Medical Services<br />
|&nbsp;<br />
|-<br />
|Michael Schmidt, PhD<br />
|Assistant Professor of Clinical Neuropsychology<br />
|Columbia Presbyterian<br />
|&nbsp;<br />
|-<br />
|James Power<br />
|&nbsp;<br />
|Datascope<br />
|&nbsp;<br />
|-<br />
|Andrea Poli<br />
|&nbsp;<br />
|DEEI, University of Trieste<br />
|&nbsp;<br />
|-<br />
|Henry Stankiewicz<br />
|Chief Clinical Engineer, VA New England Healthcare System<br />
|Department of Veterans Affairs<br />
|&nbsp;<br />
|-<br />
|Peter Rontey<br />
|OI Field Office (19A)<br />
|Department of Veterans Affairs<br />
|&nbsp;<br />
|-<br />
|Kenneth Fuchs<br />
|Director of Clinical and Systems Engineering<br />
|Draeger Medical Systems, Inc.<br />
|&nbsp;<br />
|-<br />
|Terri G. Monk, MD<br />
|Professor<br />
|Duke University Medical Center<br />
|&nbsp;<br />
|-<br />
|Frank Ralfs<br />
|&nbsp;<br />
|Draeger Medical AG & Co. KG<br />
|&nbsp;<br />
|-<br />
|Jonathan Gaev<br />
|&nbsp;<br />
|ECRI<br />
|&nbsp;<br />
|-<br />
|Monroe Pattillo<br />
|Technical Product Manager<br />
|Emergin<br />
|&nbsp;<br />
|-<br />
|Byron Mattingly<br />
|Principal Software Engineer<br />
|Endovations Boston Scientific 100 Boston <br />
|&nbsp;<br />
|-<br />
|Robert Snyder<br />
|&nbsp;<br />
|Enterprise Consulting Services, LLC<br />
|&nbsp;<br />
|-<br />
|Ronald Baumann<br />
|&nbsp;<br />
|EQ International<br />
|&nbsp;<br />
|-<br />
|Peter O'Connor<br />
|&nbsp;<br />
|EQ International<br />
|&nbsp;<br />
|-<br />
|Julie Burgoon<br />
|Technology Management Div.<br />
|Erlanger<br />
|&nbsp;<br />
|-<br />
|Thomas Norgall, MSc<br />
|&nbsp;<br />
|Fraunhofer IIS<br />
|&nbsp;<br />
|-<br />
|Marc Goodwin<br />
|Program Manager<br />
|[http://www.gehealthcare.com GE Healthcare]<br />
|&nbsp;<br />
|-<br />
|Robert Flanders<br />
|&nbsp;<br />
|[http://www.gehealthcare.com GE Healthcare]<br />
|&nbsp;<br />
|-<br />
|Ken Marks<br />
|Sr. Software Engineer<br />
|[http://www.gehealthcare.com GE Healthcare]<br />
|&nbsp;<br />
|-<br />
|Paul S. Schluter, PhD<br />
|Principal Engineer<br />
|[http://www.gehealthcare.com GE Healthcare]<br />
|&nbsp;<br />
|-<br />
|Luis R. Bernal<br />
|&nbsp;<br />
|GHESA Ingenieria y Tecnologia, S.A.<br />
|&nbsp;<br />
|-<br />
|Paul M. Connelly<br />
|VP & Chief Information Security Officer<br />
|HCA<br />
|&nbsp;<br />
|-<br />
|In K. Mun, PhD<br />
|VP, Research & Technology, NFD<br />
|HCA<br />
|&nbsp;<br />
|-<br />
|Steve Starkey<br />
|VP, Product Development<br />
|Healthcare Management Systems, Inc.<br />
|&nbsp;<br />
|-<br />
|Dave Dyell<br />
|CEO<br />
|Healthcare Technology Solutions, Inc.<br />
|&nbsp;<br />
|-<br />
|Didi Davis<br />
|Director, IHE<br />
|[http://www.himms.org/IHE HIMSS]<br />
|&nbsp;<br />
|-<br />
|Joyce Sensmeier<br />
|Vice President, Informatics<br />
|[http://www.himms.org/IHE HIMSS]<br />
|&nbsp;<br />
|-<br />
|Thomas Canup<br />
|&nbsp;<br />
|Hospira Worldwide, Inc<br />
|&nbsp;<br />
|-<br />
|Patrick B. Keely<br />
|VP and General Manager<br />
|Hospira Worldwide, Inc<br />
|&nbsp;<br />
|-<br />
|Juliana M. Reed<br />
|Director, Health Policy & Reimbursement<br />
|Hospira Worldwide, Inc.<br />
|&nbsp;<br />
|-<br />
|Steve Wehba<br />
|Software Architect<br />
|Hospira Worldwide, Inc.<br />
|&nbsp;<br />
|-<br />
|Randy Carroll<br />
|&nbsp;<br />
|IBM<br />
|&nbsp;<br />
|-<br />
|Karen Witting<br />
|&nbsp;<br />
|IBM<br />
|&nbsp;<br />
|-<br />
|Andrew Kim<br />
|Software Engineer<br />
|IBM Korea, Korea Solution Software Laboratory<br />
|&nbsp;<br />
|-<br />
|Pete Renzi<br />
|Chief Technology Officer<br />
|Image Stream Medical<br />
|&nbsp;<br />
|-<br />
|Emanuel Furst, PhD, CCE<br />
|President<br />
|Improvement Technologies, LLC<br />
|&nbsp;<br />
|-<br />
|Kenny Bailey<br />
|Strategic Planning Director, Digital Health Group<br />
|Intel Corporation<br />
|&nbsp;<br />
|-<br />
|Alan Boucher<br />
|Director, Healthcare Architecture & Concept Engineering<br />
|Intel Corporation<br />
|&nbsp;<br />
|-<br />
|Julie N. Fleischer<br />
|&nbsp;<br />
|Intel Corporation<br />
|&nbsp;<br />
|-<br />
|Eric White<br />
|&nbsp;<br />
|Intel Corporation<br />
|&nbsp;<br />
|-<br />
|David L. Whitlinger<br />
|Standards Development Manager<br />
|Intel Corporation<br />
|&nbsp;<br />
|-<br />
|Pekka Kola<br />
|&nbsp;<br />
|Intensium Ltd.<br />
|&nbsp;<br />
|-<br />
|Bill Hawley<br />
|DIA/GE CDI Project<br />
|Intermountain Healthcare, Inc.<br />
|&nbsp;<br />
|-<br />
|Martin J. Hurrell, PhD<br />
|&nbsp;<br />
|IOTA<br />
|&nbsp;<br />
|-<br />
|Keith Naylor<br />
|&nbsp;<br />
|iSOFT <br />
|&nbsp;<br />
|-<br />
|Mary L. Moewe, MS, FACHE, PMP, SHIMSS<br />
|Director, Clinical Solutions<br />
|IT Strategy & Planning<br />
|&nbsp;<br />
|-<br />
|Caren Adno<br />
|Vice President<br />
|ITAC -Information Technology Association of Canada for Ontario<br />
|&nbsp;<br />
|-<br />
|Joshua Pearl<br />
|&nbsp;<br />
|IXXAT, Inc.<br />
|&nbsp;<br />
|-<br />
|William E. Seitz<br />
|President<br />
|IXXAT, Inc.<br />
|&nbsp;<br />
|-<br />
|Roy Kerns<br />
|Manager, Clinical Engineering<br />
|Kadlec Medical Center<br />
|&nbsp;<br />
|-<br />
|George Panagiotopoulos<br />
|&nbsp;<br />
|Kaiser Foundation Hospitals<br />
|&nbsp;<br />
|-<br />
|Tracy L. Rausch, MSME<br />
|Biomedical Engineer<br />
|Kaiser Permanente<br />
|&nbsp;<br />
|-<br />
|Karin Kajbjer<br />
|&nbsp;<br />
|Kiwok<br />
|&nbsp;<br />
|-<br />
|Sudhakar Nagavalli, MS, CCE, CBET<br />
|General Manager, Medical Equipment Planning Services<br />
|KJWW Engineering Consultants<br />
|&nbsp;<br />
|-<br />
|Sungkee Lee, PhD<br />
|Professor<br />
|Kyungpook National University<br />
|&nbsp;<br />
|-<br />
|John Hotchkiss<br />
|Technology Consultant<br />
|LiveData Inc<br />
|&nbsp;<br />
|-<br />
|Jeff Robbins<br />
|CEO, CTO<br />
|LiveData<br />
|&nbsp;<br />
|-<br />
|Jeff Scott<br />
|&nbsp;<br />
|LiveData<br />
|&nbsp;<br />
|-<br />
|James Welch<br />
|VP Engineering<br />
|Masimo Corp.<br />
|&nbsp;<br />
|-<br />
|Julian M. Goldman, MD<br />
|Anesthesiologist<br />
|Massachusetts General Hospital<br />
|&nbsp;<br />
|-<br />
|Rick Schrenker<br />
|Systems Engineering Manager<br />
|Massachusetts General Hospital<br />
|&nbsp;<br />
|-<br />
|Bob Baumgartner<br />
|&nbsp;<br />
|McKesson Medical Imaging Group<br />
|&nbsp;<br />
|-<br />
|Brian L. Gunderson, MS, MT(ASCP), CISSP<br />
|Director of Product Portfolio Management<br />
|Medical Automation Systems<br />
|&nbsp;<br />
|-<br />
|Timothy Gee<br />
|&nbsp;<br />
|Medical Connectivity Consulting<br />
|&nbsp;<br />
|-<br />
|Joseph Ahrens<br />
|Business Consultant<br />
|MediServe Information Systems<br />
|&nbsp;<br />
|-<br />
|John P. Van Danacker<br />
|Sr. Director, Patient Management Development & Operations<br />
|Medtronic, Inc.<br />
|&nbsp;<br />
|-<br />
|Ruomei Zhang, PhD<br />
|CTO<br />
|Midmark Diagnostics Group<br />
|&nbsp;<br />
|-<br />
|Nancy Gertudiz<br />
|&nbsp;<br />
|Ministry of Health<br />
|&nbsp;<br />
|-<br />
|Larry Washington<br />
|Product Manager, Enterprise Solutions<br />
|Misys Healthcare<br />
|&nbsp;<br />
|-<br />
|Devin Upton<br />
|Manager<br />
|Montefiore Medical Center<br />
|&nbsp;<br />
|-<br />
|Jason Williams<br />
|Sales Engineer<br />
|NeoTool<br />
|&nbsp;<br />
|-<br />
|Rick Crawford<br />
|&nbsp;<br />
|Newport Medical<br />
|&nbsp;<br />
|-<br />
|Victor Rosero<br />
|Software Engineer<br />
|Newport Medical Instruments, Inc.<br />
|&nbsp;<br />
|-<br />
|Robert Barker<br />
|Interoperability Analyst<br />
|NextGen<br />
|&nbsp;<br />
|-<br />
|Lee Patty<br />
|Director of Marketing and Professional Services<br />
|Niceware International, LLC<br />
|&nbsp;<br />
|-<br />
|Masaaki Hirai<br />
|&nbsp;<br />
|Nihon Kohden Co. <br />
|&nbsp;<br />
|-<br />
|Kevin Standen<br />
|National Support Services Manager<br />
|Nihon Kohden<br />
|&nbsp;<br />
|-<br />
|Lisa Carnahan<br />
|Computer Scientist<br />
|NIST<br />
|&nbsp;<br />
|-<br />
|John J. Garguilo<br />
|&nbsp;<br />
|NIST<br />
|&nbsp;<br />
|-<br />
|Sandra I. Martinez<br />
|Computer Scientist<br />
|NIST<br />
|&nbsp;<br />
|-<br />
|Richard M. Rivello<br />
|Computer Scientist<br />
|NIST<br />
|&nbsp;<br />
|-<br />
|Lynne Rosenthal<br />
|Computer Scientist<br />
|NIST<br />
|&nbsp;<br />
|-<br />
|Shaji Nathan<br />
|Chief Technology Officer<br />
|Nuvon<br />
|&nbsp;<br />
|-<br />
|Gary Semans<br />
|Executive VP<br />
|Nuvon<br />
|&nbsp;<br />
|-<br />
|Mike Stallone<br />
|VP of Marketing<br />
|Nuvon<br />
|&nbsp;<br />
|-<br />
|Michael Krupnick<br />
|&nbsp;<br />
|Olympus<br />
|&nbsp;<br />
|-<br />
|Richard King<br />
|&nbsp;<br />
|OpticScan<br />
|&nbsp;<br />
|-<br />
|Antonio Hernandez<br />
|&nbsp;<br />
|Pan American Health Organization<br />
|&nbsp;<br />
|-<br />
|Jon J. Blasingame, CCE<br />
|Major Account Support Mgr<br />
|[http://www.medical.philips.com/main/index.asp Philips Medical Systems]<br />
|&nbsp;<br />
|-<br />
|John Rhoads, PhD<br />
|Software Development Engineer<br />
|[http://www.medical.philips.com/main/index.asp Philips Medical Systems]<br />
|&nbsp;<br />
|-<br />
|Robert Snyder<br />
|&nbsp;<br />
|[http://www.medical.philips.com/main/index.asp Philips Medical Systems]<br />
|&nbsp;<br />
|-<br />
|Jan Wittenber<br />
|Engineer/Scientist<br />
|[http://www.medical.philips.com/main/index.asp Philips Medical Systems]<br />
|&nbsp;<br />
|-<br />
|Ellen Bellini<br />
|Interoperability Product Manager<br />
|PICIS<br />
|&nbsp;<br />
|-<br />
|Rick Ellis<br />
|VP, Business Development<br />
|Precision Dynamics Corp.<br />
|&nbsp;<br />
|-<br />
|Irwin Thall<br />
|Manager RFID Healthcare<br />
|Precision Dynamics Corp.<br />
|&nbsp;<br />
|-<br />
|Peter E. Bausbacher<br />
|President<br />
|Protolink, Inc.<br />
|&nbsp;<br />
|-<br />
|Al Engelbert<br />
|&nbsp;<br />
|ProtoLink, Inc.<br />
|&nbsp;<br />
|-<br />
|Steven Weisner<br />
|VP Software Development<br />
|Radianese, Inc.<br />
|&nbsp;<br />
|-<br />
|Dann R. Lemerand<br />
|VP, Marketing and Business Development<br />
|Reliance Software Systems<br />
|&nbsp;<br />
|-<br />
|William (Chip) Furniss<br />
|&nbsp;<br />
|Respironics<br />
|&nbsp;<br />
|-<br />
|Michael Madison<br />
|&nbsp;<br />
|Respironics<br />
|&nbsp;<br />
|-<br />
|Richard W. Landuyt<br />
|President/CEO<br />
|RFIDeas inc.<br />
|&nbsp;<br />
|-<br />
|Terry Hinkle<br />
|Director of Medical Products<br />
|RFM<br />
|&nbsp;<br />
|-<br />
|Jeff Raponi<br />
|Marketing Manager, Hospital IT<br />
|Roche<br />
|&nbsp;<br />
|-<br />
|Christopher Carr<br />
|Director of Informatics<br />
|RSNA<br />
|&nbsp;<br />
|-<br />
|Vern Williams<br />
|&nbsp;<br />
|SAIC<br />
|&nbsp;<br />
|-<br />
|Brenda Bland<br />
|&nbsp;<br />
|Saint Elizabeth Regional Medical Center<br />
|&nbsp;<br />
|-<br />
|Dirk Huske-Draus<br />
|Product Manager<br />
|Siemens AG<br />
|&nbsp;<br />
|-<br />
|Allen Enebo<br />
|&nbsp;<br />
|Spacelabs Medical, an OSI Systems Company<br />
|&nbsp;<br />
|-<br />
|David Teixeira<br />
|&nbsp;<br />
|Spacelabs<br />
|&nbsp;<br />
|-<br />
|Jospeh Hatleli<br />
|Executive Director, Clinical Equipment Planning and Support<br />
|SSM Integrated Health Technologies<br />
|&nbsp;<br />
|-<br />
|Rick Cnossen<br />
|&nbsp;<br />
|Standards Technology Manager Digital Health Group (DHeG)<br />
|&nbsp;<br />
|-<br />
|Ken Andersen<br />
|&nbsp;<br />
|SunTech Medical, Inc.<br />
|&nbsp;<br />
|-<br />
|Tony Francisco<br />
|&nbsp;<br />
|SunTech Medical<br />
|&nbsp;<br />
|-<br />
|Christine Winters<br />
|Product Manager, ABPM<br />
|SunTech Medical, Inc.<br />
|&nbsp;<br />
|-<br />
|Dave Chmielewski<br />
|&nbsp;<br />
|Sybase, Inc.<br />
|&nbsp;<br />
|-<br />
|Raymond Peter Zambuto, CCE, FACCE, FASHE, FHIMSS<br />
|President<br />
|Technology in Medicine, Inc.<br />
|&nbsp;<br />
|-<br />
|David Sterry<br />
|Standards Administrator<br />
|The Clinical and Laboratory Standards Institute<br />
|&nbsp;<br />
|-<br />
|Joseph Cafazzo<br />
|Director, Medical Device Informatics and Healthcare Human Factor<br />
|Toronto General Hospital, University Health Network<br />
|&nbsp;<br />
|-<br />
|Tony Easty<br />
|&nbsp;<br />
|Toronto General Hospital<br />
|&nbsp;<br />
|-<br />
|John Leung<br />
|&nbsp;<br />
|Toronto General Hospital<br />
|&nbsp;<br />
|-<br />
|Mat Trudel<br />
|&nbsp;<br />
|Toronto General Hospital<br />
|&nbsp;<br />
|-<br />
|Kyung Hee Kang<br />
|&nbsp;<br />
|u-Health Division<br />
|&nbsp;<br />
|-<br />
|Ronald Marchessault, Jr.<br />
|&nbsp;<br />
|US Army Medical Research and Materiel Command<br />
|&nbsp;<br />
|-<br />
|Stephen L. Grimes<br />
|&nbsp;<br />
|Vanderbilt Univ. Medical Ctr<br />
|&nbsp;<br />
|-<br />
|Joe Strachan<br />
|National Sales Manager<br />
|VeriChip<br />
|&nbsp;<br />
|-<br />
|Walter K. Bordett, CCE<br />
|Biomedical Engineer<br />
|Veterans Affairs Medical Center<br />
|&nbsp;<br />
|-<br />
|Elliot B. Sloane, PhD<br />
|Ass't Professor of Decison and Information Technology<br />
|Villanova University<br />
|&nbsp;<br />
|-<br />
|Angelo D'Agostino<br />
|Director, Program Management<br />
|Viterion TeleHealthcare<br />
|&nbsp;<br />
|-<br />
|Terry Bettis<br />
|Manager, Applications Engineering<br />
|Welch Allyn<br />
|&nbsp;<br />
|-<br />
|James J. DelloStritto<br />
|System Architect/Device Interoperability<br />
|Welch Allyn<br />
|&nbsp;<br />
|-<br />
|Jeffrey H. Schmidt<br />
|Global Director Service; Chair S/W & Connectivity<br />
|Welch Allyn Medical<br />
|&nbsp;<br />
|-<br />
|Pascal Gand<br />
|&nbsp;<br />
|Welch Allyn Europe<br />
|&nbsp;<br />
|-<br />
|Deborah Chan<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Craig Cunic<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Deborah Dahl<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Deborah Domelle<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Michael Ganzlin<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Mike Higgins<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|John Howse<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|John D. Hughes<br />
|Director, Contracts Administration<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Ersel Llukacej<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Brad Lund<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Austin Montgomery<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Ioana Singureanu<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Rick Smith<br />
|&nbsp; <br />
|&nbsp; <br />
|&nbsp;<br />
|-<br />
|Scott Zaffrin<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Zachary Zimmerman<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|- <br />
|&nbsp;<br />
|&nbsp;<br />
|'''Quorum'''<br />
|align="center" | '''2'''<br />
|-<br />
|}<br />
<br />
<br />
If your organization is an IHE Member and you would like to be added to this roster, please provide the name of your voting representative (and optionally, alternates) to the Secretary.<br />
<br />
If your status needs to be adjusted, please contact the Secretary and or a Cochair.</div>Bikramhttp://wiki.ihe.net/index.php?title=PCD_Planning_Committee&diff=14806PCD Planning Committee2008-03-21T19:49:40Z<p>Bikram: /* Roster */</p>
<hr />
<div>==Roster==<br />
<br />
Committee participation is open and voluntary. Roster is based on attendance at one TCON or Face-to-Face meeting within an 18-month period. Policy regarding membership status is being finalized so this list may be adjusted to reflect the policy decision and follow the format of the [[Committee Template|Committee Page Template]]. <br />
<br />
Representatives with a '''[[Roster Status]]''' of '''Co-chair''', '''Voting''' or '''Liaison''' may vote and count towards quorum. A - represents a missed meeting.<br />
<br />
Representatives with a '''[[Roster Status]]''' of '''Secretary''' or '''Non-voting''' or may not vote or count towards quorum. A + represents an attended meeting.<br />
<br />
Note: The roster is for active participants in Committee Meetings. Members of the [[Mailing Lists|Mailing List]] are not formally recorded. <br />
<br />
{| style="width:85%" border="1" cellpadding="3"<br />
! Name<br />
! Title<br />
! Affiliation<br />
! Roster Status<br />
<br />
|-<br />
|Todd Cooper<br />
|President<br />
|Breakthrough Solutions<br />
|Co-chair<br />
|-<br />
|Raymond Peter Zambuto, CCE, FACCE, FASHE, FHIMSS<br />
|President<br />
|Technology in Medicine, Inc.<br />
|Co-chair<br />
|-<br />
|Jonathan Barmettler<br />
|Senior Consultant<br />
|ACS<br />
|&nbsp;<br />
|-<br />
|Jeff Secunda<br />
|Associate Vice President, Technology & Regulatory Affairs<br />
|AdvaMed<br />
|&nbsp;<br />
|-<br />
|J. Michael Fitzmaurice PhD, FACMI<br />
|Sr. Science Advisor for Information Technology<br />
|Agency for Healthcare Research and Quality<br />
|&nbsp;<br />
|-<br />
|Cathy Glenz<br />
|Sr. Software Consultant and Director Interoperability<br />
|Alert Life Sciences Computing, Inc.<br />
|&nbsp;<br />
|-<br />
|Melvin I. Reynolds, MISciT, MBCS<br />
|&nbsp;<br />
|AMS Consulting<br />
|&nbsp;<br />
|-<br />
|Alan Lang<br />
|Program Manager of Research<br />
|ASTRO<br />
|&nbsp;<br />
|-<br />
|Slav Lerner<br />
|Sr. Business Development Manager<br />
|Auriga<br />
|&nbsp;<br />
|-<br />
|Alan Gresch<br />
|Manager, Corporate Clinical Engineering<br />
|Aurora Health<br />
|&nbsp;<br />
|-<br />
|John-Paul Guimond<br />
|Manager, Corporate Clinical Engineering<br />
|Aurora Health<br />
|&nbsp;<br />
|-<br />
|Steve Merritt<br />
|&nbsp;<br />
|Bay State Healthcare System<br />
|&nbsp;<br />
|-<br />
|Gale T. White<br />
|Vice President<br />
|B. Braun Medical Inc.<br />
|&nbsp;<br />
|-<br />
|Michael J. Zakrewski<br />
|Product Director<br />
|B. Braun Medical, Inc.<br />
|&nbsp;<br />
|-<br />
|Shankar Krishnan<br />
|Assistant Director<br />
|Biomedical Engineering<br />
|&nbsp;<br />
|-<br />
|Marcia A. Wylie<br />
|Director<br />
|Biomedical Engineering<br />
|&nbsp;<br />
|-<br />
|Carla D. Smith<br />
|&nbsp;<br />
|Booz Allen Hamilton<br />
|&nbsp;<br />
|-<br />
|Jennifer L. Jackson, MBA, CCE<br />
|Assistant Director<br />
|Brigham and Women's Hospital<br />
|&nbsp;<br />
|-<br />
|Beth Hurter<br />
|Director of Product Development<br />
|CapMed <br />
|&nbsp;<br />
|-<br />
|Bikram Day<br />
|&nbsp;<br />
|[http://www.capsuletech.com Capsule Technologies]<br />
|&nbsp;<br />
|-<br />
|John McHutcheon<br />
|&nbsp;<br />
|[http://www.capsuletech.com Capsule Technologies]<br />
|&nbsp;<br />
|-<br />
|Rich Fronek<br />
|&nbsp;<br />
|Cardiac Science<br />
|&nbsp;<br />
|-<br />
|Jeremy R. Malecha<br />
|&nbsp;<br />
|CardioDynamics<br />
|&nbsp;<br />
|-<br />
|Chris Riha<br />
|Director of Clinical Systems Engineering<br />
|Carilion Health System<br />
|&nbsp;<br />
|-<br />
|Bob Fetters<br />
|&nbsp;<br />
|Catalyst Consulting of Kennett<br />
|&nbsp;<br />
|-<br />
|Robert Tassin, MD<br />
|CMR Physician Support Director<br />
|C & M Medical Services<br />
|&nbsp;<br />
|-<br />
|Michael Schmidt, PhD<br />
|Assistant Professor of Clinical Neuropsychology<br />
|Columbia Presbyterian<br />
|&nbsp;<br />
|-<br />
|James Power<br />
|&nbsp;<br />
|Datasope<br />
|&nbsp;<br />
|-<br />
|Andrea Poli<br />
|&nbsp;<br />
|DEEI, University of Trieste<br />
|&nbsp;<br />
|-<br />
|Henry Stankiewicz<br />
|Chief Clinical Engineer, VA New England Healthcare System<br />
|Department of Veterans Affairs<br />
|&nbsp;<br />
|-<br />
|Kenneth Fuchs<br />
|Director of Clinical and Systems Engineering<br />
|Draeger Medical Systems, Inc.<br />
|&nbsp;<br />
|-<br />
|Frank Visgalio, Jr.<br />
|&nbsp;<br />
|Draeger Medical, Inc.<br />
|&nbsp;<br />
|-<br />
|Terri G. Monk, MD<br />
|Professor<br />
|Duke University Medical Center<br />
|&nbsp;<br />
|-<br />
|Frank Ralfs<br />
|&nbsp;<br />
|Draeger Medical AG & Co. KG<br />
|&nbsp;<br />
|-<br />
|Jonathan Gaev<br />
|&nbsp;<br />
|ECRI<br />
|&nbsp;<br />
|-<br />
|Monroe Pattillo<br />
|Technical Product Manager<br />
|Emergin<br />
|&nbsp;<br />
|-<br />
|Byron Mattingly<br />
|Principal Software Engineer<br />
|Endovations Boston Scientific 100 Boston <br />
|&nbsp;<br />
|-<br />
|Ronald Baumann<br />
|&nbsp;<br />
|EQ International<br />
|&nbsp;<br />
|-<br />
|Steve Juett<br />
|&nbsp;<br />
|EQ International<br />
|&nbsp;<br />
|-<br />
|Peter O'Connor<br />
|&nbsp;<br />
|EQ International<br />
|&nbsp;<br />
|-<br />
|Julie Burgoon<br />
|Technology Management Div.<br />
|Erlanger<br />
|&nbsp;<br />
|-<br />
|Thomas Norgall, MSc<br />
|&nbsp;<br />
|Fraunhofer IIS<br />
|&nbsp;<br />
|-<br />
|Marc Goodwin<br />
|Program Manager<br />
|[http://www.gehealthcare.com GE Healthcare]<br />
|&nbsp;<br />
|-<br />
|Robert Flanders<br />
|&nbsp;<br />
|[http://www.gehealthcare.com GE Healthcare]<br />
|&nbsp;<br />
|-<br />
|Ken Marks<br />
|Sr. Software Engineer<br />
|[http://www.gehealthcare.com GE Healthcare]<br />
|&nbsp;<br />
|-<br />
|Cristina Purtill<br />
|Global Product Manager<br />
|[http://www.gehealthcare.com GE Healthcare]<br />
|&nbsp;<br />
|-<br />
|Paul S. Schluter, PhD<br />
|Principal Engineer<br />
|[http://www.gehealthcare.com GE Healthcare]<br />
|&nbsp;<br />
|-<br />
|Luis R. Bernal<br />
|&nbsp;<br />
|GHESA Ingenieria y Tecnologia, S.A.<br />
|&nbsp;<br />
|-<br />
|Paul M. Connelly<br />
|VP & Chief Information Security Officer<br />
|HCA<br />
|&nbsp;<br />
|-<br />
|In K. Mun, PhD<br />
|VP, Research & Technology, NFD<br />
|HCA<br />
|&nbsp;<br />
|-<br />
|Steve Starkey<br />
|VP, Product Development<br />
|Healthcare Management Systems, Inc.<br />
|&nbsp;<br />
|-<br />
|Dave Dyell<br />
|CEO<br />
|Healthcare Technology Solutions, Inc.<br />
|&nbsp;<br />
|-<br />
|Didi Davis<br />
|Director, IHE<br />
|[http://www.himms.org/IHE HIMSS]<br />
|&nbsp;<br />
|-<br />
|Joyce Sensmeier<br />
|Vice President, Informatics<br />
|[http://www.himms.org/IHE HIMSS]<br />
|&nbsp;<br />
|-<br />
|Thomas Canup<br />
|&nbsp;<br />
|Hospira Worldwide, Inc.<br />
|&nbsp;<br />
|-<br />
|Patrick B. Keely<br />
|VP and General Manager<br />
|Hospira Worldwide, Inc<br />
|&nbsp;<br />
|-<br />
|Juliana M. Reed<br />
|Director, Health Policy & Reimbursement<br />
|Hospira Worldwide, Inc.<br />
|&nbsp;<br />
|-<br />
|Steve Wehba<br />
|Software Architect<br />
|Hospira Worldwide, Inc.<br />
|&nbsp;<br />
|-<br />
|Karen Witting<br />
|&nbsp;<br />
|IBM<br />
|&nbsp;<br />
|-<br />
|Pete Renzi<br />
|Chief Technology Officer<br />
|Image Stream Medical<br />
|&nbsp;<br />
|-<br />
|Emanuel Furst, PhD, CCE<br />
|President<br />
|Improvement Technologies, LLC<br />
|&nbsp;<br />
|-<br />
|Alan Boucher<br />
|Director, Healthcare Architecture & Concept Engineering<br />
|Intel Corporation<br />
|&nbsp;<br />
|-<br />
|Eric White<br />
|&nbsp;<br />
|Intel Corporation<br />
|&nbsp;<br />
|-<br />
|David L. Whitlinger<br />
|Standards Development Manager<br />
|Intel Corporation<br />
|&nbsp;<br />
|-<br />
|Bill Hawley<br />
|DIA/GE CDI Project<br />
|Intermountain Healthcare, Inc.<br />
|&nbsp;<br />
|-<br />
|Martin J. Hurrell, PhD<br />
|&nbsp;<br />
|IOTA<br />
|&nbsp;<br />
|-<br />
|Keith Naylor<br />
|&nbsp;<br />
|iSOFT <br />
|&nbsp;<br />
|-<br />
|Mary L. Moewe, MS, FACHE, PMP, SHIMSS<br />
|Director, Clinical Solutions<br />
|IT Strategy & Planning<br />
|&nbsp;<br />
|-<br />
|Caren Adno<br />
|Vice President<br />
|ITAC -Information Technology Association of Canada for Ontario<br />
|&nbsp;<br />
|-<br />
|Joshua Pearl<br />
|&nbsp;<br />
|IXXAT, Inc.<br />
|&nbsp;<br />
|-<br />
|William E. Seitz<br />
|President<br />
|IXXAT, Inc.<br />
|&nbsp;<br />
|-<br />
|Roy Kerns<br />
|Manger, Clinical Engineering<br />
|Kadlec Medical Center<br />
|&nbsp;<br />
|-<br />
|Peter Hendler, MD<br />
|&nbsp;<br />
|Kaiser<br />
|&nbsp;<br />
|-<br />
|George Panagiotopoulos<br />
|&nbsp;<br />
|Kaiser Foundation Hospitals<br />
|&nbsp;<br />
|-<br />
|James Lewis<br />
|Sr. Technology Analyst<br />
|Kaiser Permanente<br />
|&nbsp;<br />
|-<br />
|Bridget A. Moorman, CCE<br />
|Clinical Systems Engineer<br />
|Kaiser Permanente<br />
|&nbsp;<br />
|-<br />
|Tracy L. Rausch, MSME<br />
|Biomedical Engineer<br />
|Kaiser Permanente<br />
|&nbsp;<br />
|-<br />
|Michael B. Robkin<br />
|Principle Enterprise Architect<br />
|Kaiser Permanente<br />
|&nbsp;<br />
|-<br />
|Andrew Kim<br />
|Software Engineer<br />
|IBM Korea, Korea Solution Software Laboratory<br />
|&nbsp;<br />
|-<br />
|Karin Kajbjer<br />
|&nbsp;<br />
|Kiwok<br />
|&nbsp;<br />
|-<br />
|Sudhakar Nagavalli, MS, CCE, CBET<br />
|General Manager, Medical Equipment Planning Services<br />
|KJWW Engineering Consultants<br />
|&nbsp;<br />
|-<br />
|Sungkee Lee, PhD<br />
|Professor<br />
|Kyungpook National University<br />
|&nbsp;<br />
|-<br />
|John Hotchkiss<br />
|Technology Consultant<br />
|LiveData Inc<br />
|&nbsp;<br />
|-<br />
|Jeff Robbins<br />
|CEO, CTO<br />
|LiveData<br />
|&nbsp;<br />
|-<br />
|Jeff Scott<br />
|&nbsp;<br />
|LiveData<br />
|&nbsp;<br />
|-<br />
|Greg Mika<br />
|Manager, Clinical Engineering<br />
|Martha Jefferson Hospital<br />
|&nbsp;<br />
|-<br />
|James Welch<br />
|VP Engineering<br />
|Masimo Corp.<br />
|&nbsp;<br />
|-<br />
|Julian M. Goldman, MD<br />
|Anesthesiologist<br />
|Massachusetts General Hospital<br />
|&nbsp;<br />
|-<br />
|Rick Schrenker<br />
|Systems Engineering Manager<br />
|Massachusetts General Hospital<br />
|&nbsp;<br />
|-<br />
|Bob Baumgartner<br />
|&nbsp;<br />
|McKesson Medical Imaging Group<br />
|&nbsp;<br />
|-<br />
|Tim LeCuyer<br />
|Director, Clinical Engineering<br />
|MD Anderson<br />
|&nbsp;<br />
|-<br />
|Brian L. Gunderson, MS, MT(ASCP), CISSP<br />
|Director of Product Portfolio Management<br />
|Medical Automation Systems<br />
|&nbsp;<br />
|-<br />
|Timothy Gee<br />
|&nbsp;<br />
|Medical Connectivity Consulting<br />
|&nbsp;<br />
|-<br />
|Joseph Ahrens<br />
|Business Consultant<br />
|MediServe Information Systems<br />
|&nbsp;<br />
|-<br />
|Nancy Gertudiz<br />
|&nbsp;<br />
|Ministry of Health<br />
|&nbsp;<br />
|-<br />
|Larry Washington<br />
|Product Manager, Enterprise Solutions<br />
|Misys Healthcare<br />
|&nbsp;<br />
|-<br />
|Devin Upton<br />
|Manager<br />
|Montefiore Medical Center<br />
|&nbsp;<br />
|-<br />
|Jason Williams<br />
|Sales Engineer<br />
|NeoTool<br />
|&nbsp;<br />
|-<br />
|Rick Crawford<br />
|&nbsp;<br />
|Newport Medical<br />
|&nbsp;<br />
|-<br />
|Victor Rosero<br />
|&nbsp;<br />
|Newport Medical Instruments, Inc.<br />
|&nbsp;<br />
|-<br />
|Robert Barker<br />
|Interoperability Analyst<br />
|NextGen<br />
|&nbsp;<br />
|-<br />
|Lee Patty<br />
|Director of Marketing and Professional Services<br />
|Niceware International, LLC<br />
|&nbsp;<br />
|-<br />
|Masaaki Hirai<br />
|&nbsp;<br />
|Nihon Kohden Co. <br />
|&nbsp;<br />
|-<br />
|Kevin Standen<br />
|National Support Services Manager<br />
|Nihon Kohden<br />
|&nbsp;<br />
|-<br />
|Lisa Carnahan<br />
|Computer Scientist<br />
|NIST<br />
|&nbsp;<br />
|-<br />
|John J. Garguilo<br />
|&nbsp;<br />
|NIST<br />
|&nbsp;<br />
|-<br />
|Sandra I. Martinez<br />
|Computer Scientist<br />
|NIST<br />
|&nbsp;<br />
|-<br />
|Richard M. Rivello<br />
|Computer Scientist<br />
|NIST<br />
|&nbsp;<br />
|-<br />
|Lynne Rosenthal<br />
|Computer Scientist<br />
|NIST<br />
|&nbsp;<br />
|-<br />
|Shaji Nathan<br />
|Chief Technology Officer<br />
|Nuvon<br />
|&nbsp;<br />
|-<br />
|Gary Semans<br />
|Executive VP<br />
|Nuvon<br />
|&nbsp;<br />
|-<br />
|Mike Stallone<br />
|VP of Marketing<br />
|Nuvon<br />
|&nbsp;<br />
|-<br />
|Michael Krupnick<br />
|&nbsp;<br />
|Olympus<br />
|&nbsp;<br />
|-<br />
|Richard King<br />
|&nbsp;<br />
|OpticScan<br />
|&nbsp;<br />
|-<br />
|Antonio Hernandez<br />
|&nbsp;<br />
|Pan American Health Organization<br />
|&nbsp;<br />
|-<br />
|Jon J. Blasingame, CCE<br />
|Major Account Support Mgr<br />
|[http://www.medical.philips.com/main/index.asp Philips Medical Systems]<br />
|&nbsp;<br />
|-<br />
|Jack J. Harrington<br />
|Sr. Director Integrated Solutions<br />
|[http://www.medical.philips.com/main/index.asp Philips Medical Systems]<br />
|&nbsp;<br />
|-<br />
|John Rhoads, PhD<br />
|Software Development Engineer<br />
|[http://www.medical.philips.com/main/index.asp Philips Medical Systems]<br />
|&nbsp;<br />
|-<br />
|Robert Snyder<br />
|&nbsp;<br />
|[http://www.medical.philips.com/main/index.asp Philips Medical Systems]<br />
|&nbsp;<br />
|-<br />
|Jan Wittenber<br />
|Engineer/Scientist<br />
|[http://www.medical.philips.com/main/index.asp Philips Medical Systems]<br />
|&nbsp;<br />
|-<br />
|Ellen Bellini<br />
|Interoperability Product Manager<br />
|PICIS<br />
|&nbsp;<br />
|-<br />
|Rick Ellis<br />
|VP, Business Development<br />
|Precision Dynamics Corp.<br />
|&nbsp;<br />
|-<br />
|Peter Bausbacher<br />
|President<br />
|Protolink, Inc.<br />
|&nbsp;<br />
|-<br />
|Al Engelbert<br />
|&nbsp;<br />
|ProtoLink, Inc.<br />
|&nbsp;<br />
|-<br />
|Steven Weisner<br />
|VP Software Development<br />
|Radianese, Inc.<br />
|&nbsp;<br />
|-<br />
|Dann R. Lemerand<br />
|VP, Marketing and Business Development<br />
|Reliance Software Systems<br />
|&nbsp;<br />
|-<br />
|William (Chip) Furniss<br />
|&nbsp;<br />
|Respironics<br />
|&nbsp;<br />
|-<br />
|Michael Madison<br />
|&nbsp;<br />
|Respironics<br />
|&nbsp;<br />
|-<br />
|Richard W. Landuyt<br />
|President/CEO<br />
|RFIDeas inc.<br />
|&nbsp;<br />
|-<br />
|Jeff Raponi<br />
|Marketing Manager, Hospital IT<br />
|Roche<br />
|&nbsp;<br />
|-<br />
|Christopher Carr<br />
|Director of Informatics<br />
|RSNA<br />
|&nbsp;<br />
|-<br />
|Vern Williams<br />
|&nbsp;<br />
|SAIC<br />
|&nbsp;<br />
|-<br />
|Brenda Bland<br />
|&nbsp;<br />
|Saint Elizabeth Regional Medical Center<br />
|&nbsp;<br />
|-<br />
|Yossi Pri-Paz<br />
|Director, Clinical Engineering & Technology<br />
|Sanz Medical Center Laniado Hospital<br />
|&nbsp;<br />
|-<br />
|Dirk Huske-Draus<br />
|Product Manager<br />
|Siemens AG<br />
|&nbsp;<br />
|-<br />
|Tobias Komischke, PhD<br />
|System Analyst<br />
|Siemens Medical Solutions<br />
|&nbsp;<br />
|-<br />
|Allen Enebo<br />
|&nbsp;<br />
|Spacelabs Medical, an OSI Systems Company<br />
|&nbsp;<br />
|-<br />
|David Teixeira<br />
|&nbsp;<br />
|Spacelabs<br />
|&nbsp;<br />
|-<br />
|Joseph Hatleli<br />
|Executive Director, Clinical Equipment Planning & Support<br />
|SSM Integrated Health Technologies<br />
|&nbsp;<br />
|-<br />
|Heidi Horn<br />
|Vice President<br />
|SSM Health Care<br />
|&nbsp;<br />
|-<br />
|Rick Cnossen<br />
|&nbsp;<br />
|Standards Technology Manager Digital Health Group (DHeG)<br />
|&nbsp;<br />
|-<br />
|Tony Francisco<br />
|&nbsp;<br />
|SunTech Medical<br />
|&nbsp;<br />
|-<br />
|Christine Winters<br />
|Product Manager, ABPM<br />
|SunTech Medical, Inc.<br />
|&nbsp;<br />
|-<br />
|Edward Wright<br />
|&nbsp;<br />
|SunTech Medical<br />
|&nbsp;<br />
|-<br />
|Dave Chmielewski<br />
|&nbsp;<br />
|Sybase, Inc.<br />
|&nbsp;<br />
|-<br />
|David E. Sterry, MT(ASCP)<br />
|Standards Administrator<br />
|The Clinical and Laboratory Standards Insitiute<br />
|&nbsp;<br />
|-<br />
|Joseph Cafazzo<br />
|Director-Medical Device Informatics and Healthcare Human Factors<br />
|Toronto General Hospital, University Health Network<br />
|&nbsp;<br />
|-<br />
|Tony Easty<br />
|&nbsp;<br />
|Toronto General Hospital<br />
|&nbsp;<br />
|-<br />
|John Leung<br />
|&nbsp;<br />
|Toronto General Hospital<br />
|&nbsp;<br />
|-<br />
|Mat Trudel<br />
|&nbsp;<br />
|Toronto General Hospital<br />
|&nbsp;<br />
|-<br />
|Kyung Hee Kang<br />
|&nbsp;<br />
|u-Health Division<br />
|&nbsp;<br />
|-<br />
|Ronald Marchessault, Jr.<br />
|&nbsp;<br />
|US Army Medical Research and Materiel Command<br />
|&nbsp;<br />
|-<br />
|Sandy Weininger<br />
|Senior Biomedical Engineer<br />
|US FDA/CDRH/OSEL<br />
|&nbsp;<br />
|-<br />
|Stephen L. Grimes<br />
|&nbsp;<br />
|Vanderbilt Univ. Medical Ctr<br />
|&nbsp;<br />
|-<br />
|Joe Strachan<br />
|National Sales Manager<br />
|VeriChip<br />
|&nbsp;<br />
|-<br />
|Walter K. Bordett, CCE<br />
|Biomedical Engineer<br />
|Veterans Affairs Medical Center<br />
|&nbsp;<br />
|-<br />
|Terry Blansfield<br />
|&nbsp;<br />
|Viasys Healthcare<br />
|&nbsp;<br />
|-<br />
|Elliot B. Sloane, PhD<br />
|Ass't Professor of Decison and Information Technology<br />
|Villanova University<br />
|&nbsp;<br />
|-<br />
|Linda Chan<br />
|Clinical Engineer<br />
|Virtua Health<br />
|&nbsp;<br />
|-<br />
|Angelo D'Agostino<br />
|Director, Program Management<br />
|Viterion TeleHealthcare<br />
|&nbsp;<br />
|-<br />
|Lee Herrmann<br />
|CIO<br />
|Washington Hospital Healthcare System<br />
|&nbsp;<br />
|-<br />
|Sam Carello<br />
|&nbsp;<br />
|Welch Allyn<br />
|&nbsp;<br />
|-<br />
|Pascal Gand<br />
|&nbsp;<br />
|Welch Allyn Europe<br />
|&nbsp;<br />
|-<br />
|Jeffrey H. Schmidt<br />
|Global Director Service; Chair S/W & Connectivity<br />
|Welch Allyn Medical<br />
|&nbsp;<br />
|-<br />
|Stephen J. Staats<br />
|&nbsp;<br />
|Zoe Medical, Inc.<br />
|&nbsp;<br />
|-<br />
|Deborah Chan<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Craig Cunic<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Deborah Dahl<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Deborah Domelle<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Michael Ganzlin<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Mike Higgins<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|John Howse<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|John D. Hughes<br />
|Director, Contracts Administration<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Ersel Llukacej<br />
|Software Engineer<br />
|LiveData<br />
|&nbsp;<br />
|-<br />
|Brad Lund<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Glen Marshall<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Austin Montgomery<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Michael Phelps<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Ioana Singureanu<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Rick Smith<br />
|&nbsp; <br />
|&nbsp; <br />
|&nbsp;<br />
|-<br />
|Scott Zaffrin<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Zachary Zimmerman<br />
|&nbsp;<br />
|&nbsp;<br />
|&nbsp;<br />
|- <br />
|&nbsp;<br />
|&nbsp;<br />
|'''Quorum'''<br />
|align="center" | '''2'''<br />
|-<br />
|}<br />
<br />
<br />
If your organization is an IHE Member and you would like to be added to this roster, please provide the name of your voting representative (and optionally, alternates) to the Secretary.<br />
<br />
If your status needs to be adjusted, please contact the Secretary and or a Cochair.</div>Bikramhttp://wiki.ihe.net/index.php?title=PCD_Profile_ACM_Proposal_Detailed&diff=13367PCD Profile ACM Proposal Detailed2008-02-24T13:03:58Z<p>Bikram: /* Actors */</p>
<hr />
<div><center>'''IHE Profile Proposal (Detailed)'''</center><br />
<br />
= Proposed Profile:Alarm Communication Management =<br />
'''Proposal Editor:''' Monroe Pattillo<br />
<br />
'''Planning Committee:''' Susan Blyde, Yadin David, Tobey Clark, Bikram Day, Manny Furst, Jeff Heyman, John Leung, Monroe Pattillo, John Rhoads, Richard Roa, Ray Zambuto <br />
<br />
'''Technical Committee:''' Susan Blyde, Bikram Day, Robert Flanders, Ken Fuchs, Joel Halle, Jeff Heyman, John Hotchkiss, Ken Marks, Mary Moewe, Monroe Pattillo, Paul Schluter<br />
<br />
'''Interested Parties:''' Ted Cohen, Bill Hyman, Bruce Hyndman, Tom Judd, Nagesh Mallugari, Rautee Riina<br />
<br />
'''Date (Initial):''' November 27, 2007 (kick-off TCon)<br />
<br />
'''Date (Current):''' February 21, 2008 (update)<br />
<br />
'''Version:''' 0.11<br />
<br />
'''Domain:''' Patient Care Device<br />
<br />
= Summary =<br />
This profile defines the communication of alarms from alarm source systems to alarm management systems and from alarm management systems to alarm historical systems.<br />
This profile provides for alarm dissemination between alarm source devices and systems, from the connector to and within the communication services to the required abstract semantics, in a manner that, if complied with, enables multi-vendor multi-modality interoperation.<br />
<br />
This profile relates to the following…<br />
Patient Care Devices (PCD) Domain<br />
<br />
Technical Framework<br />
<br />
Device Enterprise Communication (DEC) Profile<br />
Point-of-Care Real-Time Plug-and-Play Medical Device Integration Profile<br />
IT Infrastructure (ITI) Domain<br />
Patient Identifier Cross Referencing (PIX) Profile<br />
The Alarm Communication profile combined with the related profiles should provide, where practicable, a consistent way of uniquely identifying each alarm source, both the required and optional communicated information, and the patient with which it is associated. <br />
The identification of the source of the alarm communicated information and the identification of the associated patient are to be “globally unique” in that it must apply no matter where it is used in the world. Applications such as telemedicine, as well as global marketing and sales, necessitate this requirement.<br />
<br />
= Scope =<br />
The covering name of this profile and the scope of required, optional, and not covered areas of this profile accommodates the time period in which this profile was created for timely approval for demonstation in the IHE Interoperability Showcase at 2009 HIMSS. It also accommodates this time period by making use of exiting IHE profile defined communication and messaging as well as HL7 defined communication and messaging. Subsequent changes to related profiles, if any, may require revisions to one or more aspects of this profile.<br />
<br />
== In Scope ==<br />
Within the scope of the profile there are required and optional components.<br />
<br />
'''Required'''<br />
<br />
This profile defines unsolicited communication of alarms from alarm source systems to alarm management systems and from alarm management systems to alarm historical systems.<br />
While Real-Time Location Services (RTLS) is considered out of scope, location identification via physical association means, Point of Care, Room, and Bed are utilized.<br />
<br />
'''Optional'''<br />
<br />
The profile also defines optional solicited alarm communication as well as optional alarm receipt communication.<br />
This profile also defines optional alarm communication to alarm historical management systems.<br />
Location information from an RTLS may optionally be included in the alarm. This information might serve to identify the location of the patient, the caregiver, or patient care devices.<br />
<br />
== Out of Scope ==<br />
Aside from that which is directly affected by this profile, communication and functionality within alarm management systems and the communication protocols and messaging used between alarm management systems and alarm dissemination and alarm endpoint client systems is not within the scope of this profile. <br />
“Smart” alarming, or alarm correlation or reduction across alarm sources is outside the scope of this profile.<br />
Additionally query and reporting capabilities of the alarm historical and reporting system is outside the scope of this profile.<br />
<br />
[[Image:ActorsOverview_Figure1_ACMD20071127.png]]<br />
<center>'''Actors Overview – Fig. 1'''</center><br />
<br />
= Actors =<br />
This profile consists of the following actors each of which is comprised of multiple functional units which are potential actors in more detailed profiles. <br />
<br />
The Alarm Source (AS) actor sources the alarm to Alarm Management (AM). <br />
<br />
The Alarm Management (AM) actor receives the alarm from the Alarm Source (AS), potentially analyzes the alarm, and dispatches the alarm to Alarm Communication (AC). <br />
<br />
The Alarm Communication (AC) actor receives the alarm from Alarm Management (AM) and sends the alarm to the client application in the endpoint device.<br />
<br />
Communication between these actors is covered in this profile. Communication between functional units within an actor is not covered in this profile. <br />
<br />
Each actor is identified below. The identity can be explicitly provided in the alarm or can be inferred based upon connections to an adjoining actor.<br />
<br />
The functional units comprising an actor may be provided by one or more vendors in one or more systems. Reducing the total number of systems is preferred, but is not required.<br />
<br />
Data flow of individual use model messaging communication indicates the command response sequences and directions.<br />
<br />
For this profile Alarm Query (AQ) is considered a standalone actor.<br />
<br />
== Alarm Source (AS) ==<br />
This actor originates the alarm. <br />
<br />
Actor should be IEC 60601-1-8 compliant. <br />
<br />
A single source can produce multiple, possibly concurrent, alarms.<br />
<br />
This profile specifies the required data and data types produced by this actor.<br />
<br />
This profile specifies communication of the data produced by this actor. <br />
<br />
This actor may optionally cancel an outstanding alarm condition.<br />
<br />
This may optionally indicate cancellation of any related escalation.<br />
<br />
An outstanding alarm condition may be optionally escalated via follow-on alarm. <br />
<br />
This actor aggregates and adapts alarms from multiple sources as needed to make them interoperable with the the AM actor. <br />
<br />
In large alarm source populations an aggregation system may be useful for concentration and possible alarm coordination (smart alarming).<br />
<br />
== Alarm Management (AM) ==<br />
This actor receives alarms from the AS, manages them, and dispatches them to the AC actor. <br />
<br />
This actor should be IEC 60601-1-8 compliant. <br />
<br />
This profile specifies the required data and data types produced by this actor in communication to the AC actor.<br />
<br />
If the following is performed, it is likely performed within the AM. <br />
<br />
Alarm formating for dissemination<br />
<br />
Alarm harmonization across multiple similar and dissimilar AS<br />
<br />
Any additional alarm priority actioning following any performed by the AS<br />
<br />
Alarm mapping to AC actor endpoints<br />
<br />
Alarm dissemination escalation<br />
<br />
Alarm dissemination sequencing to AC actor endpoints<br />
<br />
Alarm dissemination escalation to AC actor endpoints<br />
<br />
Patient to staff assignments<br />
<br />
Staff to AC actor endpoint assignments<br />
<br />
Alarm reporting<br />
<br />
Alarm historian<br />
<br />
To accomplish assignments the AM may receive HL7 ADT message feeds from one or more sourcing systems for the following purposes.<br />
<br />
Identify patients<br />
<br />
Assign resources to patients (staff, equipment, rooms)<br />
<br />
This profile specifies the required data and data types produced by this actor.<br />
<br />
This profile does not specify the protocol used in the communication of the data to the AC actor. <br />
<br />
== Alarm Communication (AC) ==<br />
Th Alarm Communications (AC) actor receives alarms from the Alarm Management (AM) actor. Endpoint devices are connected either directly or indirectly to the Alarm Communications (AC) actor. The AC may utilize a locally controlled or public infrastructure.<br />
<br />
'''Examples of locally controlled infrastrcutures'''<br />
<br />
* One-way paging system (no ability to reply)<br />
<br />
* Two-way paging system (varying abilities: read receipt, accept, cancel)<br />
<br />
* Wired telephony communication (e.g. PBX) (e.g. text to speech/DTMF/IVR)<br />
<br />
* Wireless telephony communication server (e.g. VoIP standard or proprietary)<br />
<br />
* Local server based e-mail (SMTP-POP/IMAP)<br />
<br />
* Local server based Instant Messaging (IM)<br />
<br />
* Examples of public infrastructures<br />
<br />
* One-way paging service (no ability to reply)<br />
<br />
* Two-way paging service (varying abilities: read receipt, accept, cancel)<br />
<br />
* Internet based e-mail (SMTP-POP/IMAP)<br />
<br />
* Internet based Instant Messaging (IM)<br />
<br />
* Internet based Multimedia Messaging (MMS)<br />
<br />
* Wired telephony communication (PSTN) (text to speech/DTMF/IVR)<br />
<br />
* Local wireless gateway to Internet for VoIP telephony<br />
<br />
This profile specifies the required data and data types produced by this actor.<br />
<br />
This profile does not specify the protocol used in the communication of the data to th AE actor.<br />
<br />
This is the client application in the communication endpoint responsible for communicating the alarm to the final destination, be it a person or a system.<br />
<br />
This profile specifies the required data and data types produced by the actor.<br />
<br />
This profile does not specify the protocol used in the communication of the data to the final destination, be it a GUI or application interface.<br />
<br />
This profile does not specify the presentation of the data.<br />
<br />
== Alarm Query (AQ) ==<br />
This actor sends alarm queries to the AM actor and receives query responses from the AH actor. The AQ is considered a standalone actor.<br />
<br />
This profile specifies communication with the AM actor. <br />
<br />
This profile specifies the required data and data types communicated with the AM actor.<br />
<br />
= Interaction Models =<br />
An alarm is essentially a Device Observation Report (DOR) sent to an Alarm Management (AM) actor instead of or in addition to a Device Observation Consumer (DOC) actor. Refer to the Device Enterprise Communication profile for details on the DOR and the DOC actor.<br />
<br />
The AM actor does not function as a DOC actor. It is merely a re-use of the DOR communication for alarm purposes. <br />
<br />
Receipt of a DOR by an AM implies the DOR is being submitted for consideration as an alarm. <br />
<br />
Based upon DOR content and/or configuration of the AM the DOR may or may not be processed as an alarm.<br />
<br />
== Patient Anonymous Alarms ==<br />
The PID segment of a DOR submitted by the AS to the AM is considered optional in some interactions. <br />
<br />
An example is a nurse call system which provides only room/location information to the AM. In such cases the PV1 segment is considered mandatory to identify alarm location. This is recognized as not in concert with current requirements of the '''''Joint Commission'''''. It is an adaptation in support of existing environments.<br />
<br />
Another example is when a patient care device is connected to a patient and begins sending alarms to the AM prior to being configured with patient identification information. In such cases the alarm source equipment identification is the alarm source identification.<br />
<br />
In all other cases a PID segment is considered mandatory for patient identification and should be used without regard to the presence or absence of a PV1 segment.<br />
<br />
Equipment location can be determined from the PV1 segment if the equipment is fixed to a location, such as with current nurse call systems, or if the equipment is integrated with location identifying equipment.<br />
<br />
If the equipment is not fixed in location and is not integrated with location identifying equipment the location of the alarm source can not be determined directly but may be correlated by the AM using alarm source equipment identification.<br />
<br />
== Unsolicited Alarms ==<br />
This is the minimally required interaction model. Alarms are sourced at the AS actor and are delivered to the AM actor in an unsolicited manner. The alarm then travels from the AM actor to the AC actor for delivery to endpoint. The delivery manner, unsolicited or solicited, is defined by the operating environment and not by this profile. <br />
<br />
Prior configuration of all involved actors is a means for allowing alarms to arrive and be processed in an unsolicited manner.<br />
<br />
Mapping of alarm source to AC actor endpoints may be provided in the alarm or may be assigned during the passge of the alarm through the AM actor to the AC actor.<br />
<br />
Alarm data<br />
<br />
Alarm instance identification<br />
<br />
Alarm source identification<br />
<br />
Alarm latch state (latched or unlatched)<br />
<br />
Alarm timestamp<br />
<br />
Alarm type<br />
<br />
physiological<br />
<br />
technical<br />
<br />
equipment maintenance<br />
<br />
demonstration<br />
<br />
Alarm priority (high, medium, low, informative)<br />
<br />
Alarm text<br />
<br />
Alarm recipients (optional)<br />
<br />
Recipeients indicated by any of…<br />
<br />
Recipient name(s)<br />
<br />
Individuals or groups<br />
<br />
Communication endpoint identification(s)<br />
<br />
Carrier and device identifier<br />
<br />
Alarm delivery confirmation (optional)<br />
<br />
Response to AS<br />
<br />
Accept (not specified, correct)<br />
<br />
Reject (not specified, nuisance but correct, false positive)<br />
<br />
Via AC actions<br />
<br />
Deliverable, had a mapped destination<br />
<br />
Queued to communications<br />
<br />
Accepted by communications<br />
<br />
Delivered to endpoint<br />
<br />
Read at endpoint<br />
<br />
Accepted by endpoint<br />
<br />
Rejected by endpoint<br />
<br />
Cancelled by endpoint<br />
<br />
Cancelled by other than endpoint<br />
<br />
Callback start at endpoint<br />
<br />
Callback end at endpoint<br />
<br />
== Solicited Alarms ==<br />
This use case is optional in this profile. <br />
<br />
This delivery method requires the AS actor to request the ability to deliver alarms to the AM actor and for the AM actor to request the ability to deliver alarms to the AC actor.<br />
<br />
== Alarm Query ==<br />
The AQ actor posts queries to the AM actor and receives responses from the AM actor. The queries may includes one or more filters. <br />
<br />
'''Filter keys'''<br />
<br />
*Alarm origination date range<br />
<br />
*Patient by name and ID<br />
<br />
*Assigned Patient Location (PV1-3) components<br />
<br />
*Alarm response time by start to status point<br />
<br />
= Reports =<br />
*Alarms by date<br />
<br />
*Alarms by patient by name and ID<br />
<br />
*Alarms by Assigneed Patient Location (PV1-3) components<br />
<br />
*Alarms by type<br />
<br />
*Alarms by source<br />
<br />
*Alarms by interface<br />
<br />
= Alarm Communication =<br />
*Alarm Source Parameters<br />
<br />
*Priority<br />
<br />
= Examples =<br />
*Alarm to one-way pager device<br />
<br />
*Alarm to two-way communication device<br />
<br />
*Alarm to two-way with callback<br />
<br />
= Use Cases =<br />
Alarm Communication Management is meant to improve clinical efficiency by using technology to deliver the right alarms, with the right priority, to the right individuals via devices with the right content, escalating under configuration communication to other individuals via devices.<br />
<br />
'''Use Case 1 (location sourced):''' Patient Assigned to Room, Nurse Call Alarm (AS), Alarm to Alarm Mgmt System (AM), Alarm to Communication Endpoint (AC)<br />
<br />
'''Use Case 2 (identified patient source):''' PCD Assigned to Patient, Patient Monitoring Alarm Occurs (AS), Sends Alarm to Alarm Mgmt System (AM), Alarm to Communication Endpoint (AC)<br />
<br />
'''Use Case 3:''' (same as use case 1 or 2 with escalation with cancel at source) if the communication destination is inaccessible or the target individual is indicated as unavailable then the alarm is rerouted to one or more alternatives with escalation to higher levels of responsibility until the alarm is canceled at its source and the alarm system notified of the cancel.<br />
<br />
'''Use Case 4:''' (same as use case 1 or 2 with escalation with cancel at communication endpoint) if the communication destination is inaccessible or the target individual is indicated as unavailable then the alarm is rerouted to one or more alternatives with escalation to higher levels of responsibility until the alarm is canceled by a recipient at a communication endpoint.<br />
<br />
'''Use Case 5:''' (same as use case 1 or 2 with escalation with cancel at alarm mgmt system) if the communication destination is inaccessible or the target individual is indicated as unavailable then the alarm is rerouted to one or more alternatives with escalation to higher levels of responsibility until the alarm is canceled by a user on the alarm management system, however not automatically via algorithms in the alarm management system.<br />
<br />
= Standards =<br />
# HL7 version 2.5<br />
# IEC 60601-1-8 Alarm Management<br />
# ISO/IEEE 11073-10201 Domain Information Model<br />
# ISO/IEEE 11073-10101 Nomenclature<br />
# ISO/IEEE 11073-20101 Application Profile – Base Standard<br />
# CEN env13735 (and in process equivalents – 11073-202xx)<br />
# ISO/IEEE 11073-30200 Transport Profile – Cable Connected<br />
# ISO/IEEE 11073-30300 Transport Profile – Infrared (incl. TCP/IP & UDP/IP Access Point specification)<br />
<br />
= References =<br />
# ACCE Healthcare Technology Foundation ''“Impact of Clinical Alarms on Patient Safety”'' [http://www.acce-htf.org/clinical.asp]<br />
# ECRI Institute ''“The Hazards of Alarm Overload”'' [http://www.ecri.org/Press/Pages/AlarmOverload.aspx]<br />
<br />
= Technical Approach =<br />
Refer to IHE PCD Technical Framework for a detailed description.</div>Bikramhttp://wiki.ihe.net/index.php?title=File:ActorsOverview_Figure1_ACMD20071127.png&diff=13366File:ActorsOverview Figure1 ACMD20071127.png2008-02-24T13:01:28Z<p>Bikram: </p>
<hr />
<div></div>Bikramhttp://wiki.ihe.net/index.php?title=PCD_Profile_ACM_Proposal_Detailed&diff=13365PCD Profile ACM Proposal Detailed2008-02-24T13:00:55Z<p>Bikram: New page: <center>'''IHE Profile Proposal (Detailed)'''</center> = Proposed Profile:Alarm Communication Management = '''Proposal Editor:''' Monroe Pattillo '''Planning Committee:''' Susan Blyde, Y...</p>
<hr />
<div><center>'''IHE Profile Proposal (Detailed)'''</center><br />
<br />
= Proposed Profile:Alarm Communication Management =<br />
'''Proposal Editor:''' Monroe Pattillo<br />
<br />
'''Planning Committee:''' Susan Blyde, Yadin David, Tobey Clark, Bikram Day, Manny Furst, Jeff Heyman, John Leung, Monroe Pattillo, John Rhoads, Richard Roa, Ray Zambuto <br />
<br />
'''Technical Committee:''' Susan Blyde, Bikram Day, Robert Flanders, Ken Fuchs, Joel Halle, Jeff Heyman, John Hotchkiss, Ken Marks, Mary Moewe, Monroe Pattillo, Paul Schluter<br />
<br />
'''Interested Parties:''' Ted Cohen, Bill Hyman, Bruce Hyndman, Tom Judd, Nagesh Mallugari, Rautee Riina<br />
<br />
'''Date (Initial):''' November 27, 2007 (kick-off TCon)<br />
<br />
'''Date (Current):''' February 21, 2008 (update)<br />
<br />
'''Version:''' 0.11<br />
<br />
'''Domain:''' Patient Care Device<br />
<br />
= Summary =<br />
This profile defines the communication of alarms from alarm source systems to alarm management systems and from alarm management systems to alarm historical systems.<br />
This profile provides for alarm dissemination between alarm source devices and systems, from the connector to and within the communication services to the required abstract semantics, in a manner that, if complied with, enables multi-vendor multi-modality interoperation.<br />
<br />
This profile relates to the following…<br />
Patient Care Devices (PCD) Domain<br />
<br />
Technical Framework<br />
<br />
Device Enterprise Communication (DEC) Profile<br />
Point-of-Care Real-Time Plug-and-Play Medical Device Integration Profile<br />
IT Infrastructure (ITI) Domain<br />
Patient Identifier Cross Referencing (PIX) Profile<br />
The Alarm Communication profile combined with the related profiles should provide, where practicable, a consistent way of uniquely identifying each alarm source, both the required and optional communicated information, and the patient with which it is associated. <br />
The identification of the source of the alarm communicated information and the identification of the associated patient are to be “globally unique” in that it must apply no matter where it is used in the world. Applications such as telemedicine, as well as global marketing and sales, necessitate this requirement.<br />
<br />
= Scope =<br />
The covering name of this profile and the scope of required, optional, and not covered areas of this profile accommodates the time period in which this profile was created for timely approval for demonstation in the IHE Interoperability Showcase at 2009 HIMSS. It also accommodates this time period by making use of exiting IHE profile defined communication and messaging as well as HL7 defined communication and messaging. Subsequent changes to related profiles, if any, may require revisions to one or more aspects of this profile.<br />
<br />
== In Scope ==<br />
Within the scope of the profile there are required and optional components.<br />
<br />
'''Required'''<br />
<br />
This profile defines unsolicited communication of alarms from alarm source systems to alarm management systems and from alarm management systems to alarm historical systems.<br />
While Real-Time Location Services (RTLS) is considered out of scope, location identification via physical association means, Point of Care, Room, and Bed are utilized.<br />
<br />
'''Optional'''<br />
<br />
The profile also defines optional solicited alarm communication as well as optional alarm receipt communication.<br />
This profile also defines optional alarm communication to alarm historical management systems.<br />
Location information from an RTLS may optionally be included in the alarm. This information might serve to identify the location of the patient, the caregiver, or patient care devices.<br />
<br />
== Out of Scope ==<br />
Aside from that which is directly affected by this profile, communication and functionality within alarm management systems and the communication protocols and messaging used between alarm management systems and alarm dissemination and alarm endpoint client systems is not within the scope of this profile. <br />
“Smart” alarming, or alarm correlation or reduction across alarm sources is outside the scope of this profile.<br />
Additionally query and reporting capabilities of the alarm historical and reporting system is outside the scope of this profile.<br />
<br />
[[Image:ActorsOverview_Figure1_ACMD20071127.png]]<br />
<center>'''Actors Overview – Fig. 1'''</center><br />
<br />
= Actors =<br />
This profile consists of the following actors each of which is comprised of multiple functional units which are potential actors in more detailed profiles. <br />
<br />
<br />
The Alarm Source (AS) actor sources the alarm to Alarm Management (AM). <br />
<br />
<br />
The Alarm Management (AM) actor receives the alarm from the Alarm Source (AS), potentially analyzes the alarm, and dispatches the alarm to Alarm Communication (AC). <br />
<br />
<br />
The Alarm Communication (AC) actor receives the alarm from Alarm Management (AM) and sends the alarm to the client application in the endpoint device.<br />
<br />
<br />
Communication between these actors is covered in this profile. Communication between functional units within an actor is not covered in this profile. <br />
<br />
<br />
Each actor is identified below. The identity can be explicitly provided in the alarm or can be inferred based upon connections to an adjoining actor.<br />
<br />
<br />
The functional units comprising an actor may be provided by one or more vendors in one or more systems. Reducing the total number of systems is preferred, but is not required.<br />
<br />
<br />
Data flow of individual use model messaging communication indicates the command response sequences and directions.<br />
<br />
<br />
For this profile Alarm Query (AQ) is considered a standalone actor.<br />
<br />
== Alarm Source (AS) ==<br />
This actor originates the alarm. <br />
<br />
Actor should be IEC 60601-1-8 compliant. <br />
<br />
A single source can produce multiple, possibly concurrent, alarms.<br />
<br />
This profile specifies the required data and data types produced by this actor.<br />
<br />
This profile specifies communication of the data produced by this actor. <br />
<br />
This actor may optionally cancel an outstanding alarm condition.<br />
<br />
This may optionally indicate cancellation of any related escalation.<br />
<br />
An outstanding alarm condition may be optionally escalated via follow-on alarm. <br />
<br />
This actor aggregates and adapts alarms from multiple sources as needed to make them interoperable with the the AM actor. <br />
<br />
In large alarm source populations an aggregation system may be useful for concentration and possible alarm coordination (smart alarming).<br />
<br />
== Alarm Management (AM) ==<br />
This actor receives alarms from the AS, manages them, and dispatches them to the AC actor. <br />
<br />
This actor should be IEC 60601-1-8 compliant. <br />
<br />
This profile specifies the required data and data types produced by this actor in communication to the AC actor.<br />
<br />
If the following is performed, it is likely performed within the AM. <br />
<br />
Alarm formating for dissemination<br />
<br />
Alarm harmonization across multiple similar and dissimilar AS<br />
<br />
Any additional alarm priority actioning following any performed by the AS<br />
<br />
Alarm mapping to AC actor endpoints<br />
<br />
Alarm dissemination escalation<br />
<br />
Alarm dissemination sequencing to AC actor endpoints<br />
<br />
Alarm dissemination escalation to AC actor endpoints<br />
<br />
Patient to staff assignments<br />
<br />
Staff to AC actor endpoint assignments<br />
<br />
Alarm reporting<br />
<br />
Alarm historian<br />
<br />
To accomplish assignments the AM may receive HL7 ADT message feeds from one or more sourcing systems for the following purposes.<br />
<br />
Identify patients<br />
<br />
Assign resources to patients (staff, equipment, rooms)<br />
<br />
This profile specifies the required data and data types produced by this actor.<br />
<br />
This profile does not specify the protocol used in the communication of the data to the AC actor. <br />
<br />
== Alarm Communication (AC) ==<br />
Th Alarm Communications (AC) actor receives alarms from the Alarm Management (AM) actor. Endpoint devices are connected either directly or indirectly to the Alarm Communications (AC) actor. The AC may utilize a locally controlled or public infrastructure.<br />
<br />
'''Examples of locally controlled infrastrcutures'''<br />
<br />
* One-way paging system (no ability to reply)<br />
<br />
* Two-way paging system (varying abilities: read receipt, accept, cancel)<br />
<br />
* Wired telephony communication (e.g. PBX) (e.g. text to speech/DTMF/IVR)<br />
<br />
* Wireless telephony communication server (e.g. VoIP standard or proprietary)<br />
<br />
* Local server based e-mail (SMTP-POP/IMAP)<br />
<br />
* Local server based Instant Messaging (IM)<br />
<br />
* Examples of public infrastructures<br />
<br />
* One-way paging service (no ability to reply)<br />
<br />
* Two-way paging service (varying abilities: read receipt, accept, cancel)<br />
<br />
* Internet based e-mail (SMTP-POP/IMAP)<br />
<br />
* Internet based Instant Messaging (IM)<br />
<br />
* Internet based Multimedia Messaging (MMS)<br />
<br />
* Wired telephony communication (PSTN) (text to speech/DTMF/IVR)<br />
<br />
* Local wireless gateway to Internet for VoIP telephony<br />
<br />
This profile specifies the required data and data types produced by this actor.<br />
<br />
This profile does not specify the protocol used in the communication of the data to th AE actor.<br />
<br />
This is the client application in the communication endpoint responsible for communicating the alarm to the final destination, be it a person or a system.<br />
<br />
This profile specifies the required data and data types produced by the actor.<br />
<br />
This profile does not specify the protocol used in the communication of the data to the final destination, be it a GUI or application interface.<br />
<br />
This profile does not specify the presentation of the data.<br />
<br />
== Alarm Query (AQ) ==<br />
This actor sends alarm queries to the AM actor and receives query responses from the AH actor. The AQ is considered a standalone actor.<br />
<br />
This profile specifies communication with the AM actor. <br />
<br />
This profile specifies the required data and data types communicated with the AM actor.<br />
<br />
= Interaction Models =<br />
An alarm is essentially a Device Observation Report (DOR) sent to an Alarm Management (AM) actor instead of or in addition to a Device Observation Consumer (DOC) actor. Refer to the Device Enterprise Communication profile for details on the DOR and the DOC actor.<br />
<br />
The AM actor does not function as a DOC actor. It is merely a re-use of the DOR communication for alarm purposes. <br />
<br />
Receipt of a DOR by an AM implies the DOR is being submitted for consideration as an alarm. <br />
<br />
Based upon DOR content and/or configuration of the AM the DOR may or may not be processed as an alarm.<br />
<br />
== Patient Anonymous Alarms ==<br />
The PID segment of a DOR submitted by the AS to the AM is considered optional in some interactions. <br />
<br />
An example is a nurse call system which provides only room/location information to the AM. In such cases the PV1 segment is considered mandatory to identify alarm location. This is recognized as not in concert with current requirements of the '''''Joint Commission'''''. It is an adaptation in support of existing environments.<br />
<br />
Another example is when a patient care device is connected to a patient and begins sending alarms to the AM prior to being configured with patient identification information. In such cases the alarm source equipment identification is the alarm source identification.<br />
<br />
In all other cases a PID segment is considered mandatory for patient identification and should be used without regard to the presence or absence of a PV1 segment.<br />
<br />
Equipment location can be determined from the PV1 segment if the equipment is fixed to a location, such as with current nurse call systems, or if the equipment is integrated with location identifying equipment.<br />
<br />
If the equipment is not fixed in location and is not integrated with location identifying equipment the location of the alarm source can not be determined directly but may be correlated by the AM using alarm source equipment identification.<br />
<br />
== Unsolicited Alarms ==<br />
This is the minimally required interaction model. Alarms are sourced at the AS actor and are delivered to the AM actor in an unsolicited manner. The alarm then travels from the AM actor to the AC actor for delivery to endpoint. The delivery manner, unsolicited or solicited, is defined by the operating environment and not by this profile. <br />
<br />
Prior configuration of all involved actors is a means for allowing alarms to arrive and be processed in an unsolicited manner.<br />
<br />
Mapping of alarm source to AC actor endpoints may be provided in the alarm or may be assigned during the passge of the alarm through the AM actor to the AC actor.<br />
<br />
Alarm data<br />
<br />
Alarm instance identification<br />
<br />
Alarm source identification<br />
<br />
Alarm latch state (latched or unlatched)<br />
<br />
Alarm timestamp<br />
<br />
Alarm type<br />
<br />
physiological<br />
<br />
technical<br />
<br />
equipment maintenance<br />
<br />
demonstration<br />
<br />
Alarm priority (high, medium, low, informative)<br />
<br />
Alarm text<br />
<br />
Alarm recipients (optional)<br />
<br />
Recipeients indicated by any of…<br />
<br />
Recipient name(s)<br />
<br />
Individuals or groups<br />
<br />
Communication endpoint identification(s)<br />
<br />
Carrier and device identifier<br />
<br />
Alarm delivery confirmation (optional)<br />
<br />
Response to AS<br />
<br />
Accept (not specified, correct)<br />
<br />
Reject (not specified, nuisance but correct, false positive)<br />
<br />
Via AC actions<br />
<br />
Deliverable, had a mapped destination<br />
<br />
Queued to communications<br />
<br />
Accepted by communications<br />
<br />
Delivered to endpoint<br />
<br />
Read at endpoint<br />
<br />
Accepted by endpoint<br />
<br />
Rejected by endpoint<br />
<br />
Cancelled by endpoint<br />
<br />
Cancelled by other than endpoint<br />
<br />
Callback start at endpoint<br />
<br />
Callback end at endpoint<br />
<br />
== Solicited Alarms ==<br />
This use case is optional in this profile. <br />
<br />
This delivery method requires the AS actor to request the ability to deliver alarms to the AM actor and for the AM actor to request the ability to deliver alarms to the AC actor.<br />
<br />
== Alarm Query ==<br />
The AQ actor posts queries to the AM actor and receives responses from the AM actor. The queries may includes one or more filters. <br />
<br />
'''Filter keys'''<br />
<br />
*Alarm origination date range<br />
<br />
*Patient by name and ID<br />
<br />
*Assigned Patient Location (PV1-3) components<br />
<br />
*Alarm response time by start to status point<br />
<br />
= Reports =<br />
*Alarms by date<br />
<br />
*Alarms by patient by name and ID<br />
<br />
*Alarms by Assigneed Patient Location (PV1-3) components<br />
<br />
*Alarms by type<br />
<br />
*Alarms by source<br />
<br />
*Alarms by interface<br />
<br />
= Alarm Communication =<br />
*Alarm Source Parameters<br />
<br />
*Priority<br />
<br />
= Examples =<br />
*Alarm to one-way pager device<br />
<br />
*Alarm to two-way communication device<br />
<br />
*Alarm to two-way with callback<br />
<br />
= Use Cases =<br />
Alarm Communication Management is meant to improve clinical efficiency by using technology to deliver the right alarms, with the right priority, to the right individuals via devices with the right content, escalating under configuration communication to other individuals via devices.<br />
<br />
'''Use Case 1 (location sourced):''' Patient Assigned to Room, Nurse Call Alarm (AS), Alarm to Alarm Mgmt System (AM), Alarm to Communication Endpoint (AC)<br />
<br />
'''Use Case 2 (identified patient source):''' PCD Assigned to Patient, Patient Monitoring Alarm Occurs (AS), Sends Alarm to Alarm Mgmt System (AM), Alarm to Communication Endpoint (AC)<br />
<br />
'''Use Case 3:''' (same as use case 1 or 2 with escalation with cancel at source) if the communication destination is inaccessible or the target individual is indicated as unavailable then the alarm is rerouted to one or more alternatives with escalation to higher levels of responsibility until the alarm is canceled at its source and the alarm system notified of the cancel.<br />
<br />
'''Use Case 4:''' (same as use case 1 or 2 with escalation with cancel at communication endpoint) if the communication destination is inaccessible or the target individual is indicated as unavailable then the alarm is rerouted to one or more alternatives with escalation to higher levels of responsibility until the alarm is canceled by a recipient at a communication endpoint.<br />
<br />
'''Use Case 5:''' (same as use case 1 or 2 with escalation with cancel at alarm mgmt system) if the communication destination is inaccessible or the target individual is indicated as unavailable then the alarm is rerouted to one or more alternatives with escalation to higher levels of responsibility until the alarm is canceled by a user on the alarm management system, however not automatically via algorithms in the alarm management system.<br />
<br />
= Standards =<br />
# HL7 version 2.5<br />
# IEC 60601-1-8 Alarm Management<br />
# ISO/IEEE 11073-10201 Domain Information Model<br />
# ISO/IEEE 11073-10101 Nomenclature<br />
# ISO/IEEE 11073-20101 Application Profile – Base Standard<br />
# CEN env13735 (and in process equivalents – 11073-202xx)<br />
# ISO/IEEE 11073-30200 Transport Profile – Cable Connected<br />
# ISO/IEEE 11073-30300 Transport Profile – Infrared (incl. TCP/IP & UDP/IP Access Point specification)<br />
<br />
= References =<br />
# ACCE Healthcare Technology Foundation ''“Impact of Clinical Alarms on Patient Safety”'' [http://www.acce-htf.org/clinical.asp]<br />
# ECRI Institute ''“The Hazards of Alarm Overload”'' [http://www.ecri.org/Press/Pages/AlarmOverload.aspx]<br />
<br />
= Technical Approach =<br />
Refer to IHE PCD Technical Framework for a detailed description.</div>Bikramhttp://wiki.ihe.net/index.php?title=PCD_Proposals_Cycle_2&diff=13202PCD Proposals Cycle 22008-02-15T06:27:06Z<p>Bikram: /* Profile Proposals Submitted */</p>
<hr />
<div>=== Current Proposals under development ===<br />
<br />
These '''Detailed Profile Proposals''' were short-listed, evaluated by the Technical Committee and '''selected''' by both committees for development in this Cycle (note: The PoC Real Time PnP Device Integration and Home Telehealth profiles may be developed in steps over a two year period. The latest versions can be found at ftp://ftp.ihe.net/Patient_Care_Devices/IHEPCDyr2-2007-2008/PlanningCommitteeYr2/ProfileProposalsDetailedYr2/<br />
<br />
# Patient ID Binding (tying the patient to the device and its data).<br />
# Point of Care (PoC) Real Time PnP Device Integration.<br />
# Home Telehealth.<br />
# PCD02 Subscribe To Patient Data (permits an EMR to select the data desired); this is a continuation of the PCD's Year 1 effort.<br />
<br />
=== Profile Proposals Submitted ===<br />
<br />
The following '''Brief Profile Proposals''' were submitted for the 2007-2008 Development Cycle and can be found at:<br />
<br />
ftp://ftp.ihe.net/Patient_Care_Devices/IHEPCDyr2-2007-2008/PlanningCommitteeYr2/ProfileProposalsBriefYr2/<br />
<br />
# Small Data Element Exchange<br />
# IHE ECG Workflow<br />
# Patient ID Binding (tying the patient to the device and its data)<br />
# Real Time Clinical Data Management Storage And Retrieval<br />
# Infusion Pump Integration To BPOC<br />
# Point of Care (PoC) Real Time PnP Device Integration<br />
# Home Telehealth<br />
# [[ Alarm Proposal Detailed |Alarm Interoperability ]]<br />
# PCA Infusion Safety<br />
<br />
=== New Proposals ===<br />
<br />
Feel free to create new proposal pages based on the [[Brief Proposal Template]], or use the complete [[Profile Template]].<br />
Remember to save your work under a new page name and post below. <br />
<br />
# [[Remote Monitoring]] - 2007-08 work to be addressed by PCD, Initiated from PCC<br />
<br />
=== PCD Technical Framework Maintenance ===<br />
<br />
The current versions of volumes 1 and 2 of the '''PCD Technical Framework''' can be found at:<br />
<br />
ftp://ftp.ihe.net/Patient_Care_Devices/TechnicalFrameworkforTrialImplementation/</div>Bikramhttp://wiki.ihe.net/index.php?title=PCD_Proposals_Cycle_2&diff=12049PCD Proposals Cycle 22007-12-05T18:28:02Z<p>Bikram: /* New Proposals */</p>
<hr />
<div>=== Current Proposals under development ===<br />
<br />
These '''Detailed Profile Proposals''' were short-listed, evaluated by the Technical Committee and '''selected''' by both committees for development in this Cycle (note: The PoC Real Time PnP Device Integration and Home Telehealth profiles may be developed in steps over a two year period. The latest versions can be found at ftp://ftp.ihe.net/Patient_Care_Devices/IHEPCDyr2-2007-2008/PlanningCommitteeYr2/ProfileProposalsDetailedYr2/<br />
<br />
# Patient ID Binding (tying the patient to the device and its data).<br />
# Point of Care (PoC) Real Time PnP Device Integration.<br />
# Home Telehealth.<br />
# PCD02 Subscribe To Patient Data (permits an EMR to select the data desired); this is a continuation of the PCD's Year 1 effort.<br />
<br />
=== Profile Proposals Submitted ===<br />
<br />
The following '''Brief Profile Proposals''' were submitted for the 2007-2008 Development Cycle and can be found at:<br />
<br />
ftp://ftp.ihe.net/Patient_Care_Devices/IHEPCDyr2-2007-2008/PlanningCommitteeYr2/ProfileProposalsBriefYr2/<br />
<br />
# Small Data Element Exchange<br />
# IHE ECG Workflow<br />
# Patient ID Binding (tying the patient to the device and its data)<br />
# Real Time Clinical Data Management Storage And Retrieval<br />
# Infusion Pump Integration To BPOC<br />
# Point of Care (PoC) Real Time PnP Device Integration<br />
# Home Telehealth<br />
# Alarm Interoperability<br />
# PCA Infusion Safety<br />
<br />
=== New Proposals ===<br />
<br />
Feel free to create new proposal pages based on the [[Brief Proposal Template]], or use the complete [[Profile Template]].<br />
Remember to save your work under a new page name and post below. <br />
<br />
# [[Remote Monitoring]] - 2007-08 work to be addressed by PCD, Initiated from PCC<br />
<br />
=== PCD Technical Framework Maintenance ===<br />
<br />
The current versions of volumes 1 and 2 of the '''PCD Technical Framework''' can be found at:<br />
<br />
ftp://ftp.ihe.net/Patient_Care_Devices/TechnicalFrameworkforTrialImplementation/</div>Bikramhttp://wiki.ihe.net/index.php?title=PCD_Proposals_Cycle_2&diff=12048PCD Proposals Cycle 22007-12-05T18:27:20Z<p>Bikram: /* New Proposals */</p>
<hr />
<div>=== Current Proposals under development ===<br />
<br />
These '''Detailed Profile Proposals''' were short-listed, evaluated by the Technical Committee and '''selected''' by both committees for development in this Cycle (note: The PoC Real Time PnP Device Integration and Home Telehealth profiles may be developed in steps over a two year period. The latest versions can be found at ftp://ftp.ihe.net/Patient_Care_Devices/IHEPCDyr2-2007-2008/PlanningCommitteeYr2/ProfileProposalsDetailedYr2/<br />
<br />
# Patient ID Binding (tying the patient to the device and its data).<br />
# Point of Care (PoC) Real Time PnP Device Integration.<br />
# Home Telehealth.<br />
# PCD02 Subscribe To Patient Data (permits an EMR to select the data desired); this is a continuation of the PCD's Year 1 effort.<br />
<br />
=== Profile Proposals Submitted ===<br />
<br />
The following '''Brief Profile Proposals''' were submitted for the 2007-2008 Development Cycle and can be found at:<br />
<br />
ftp://ftp.ihe.net/Patient_Care_Devices/IHEPCDyr2-2007-2008/PlanningCommitteeYr2/ProfileProposalsBriefYr2/<br />
<br />
# Small Data Element Exchange<br />
# IHE ECG Workflow<br />
# Patient ID Binding (tying the patient to the device and its data)<br />
# Real Time Clinical Data Management Storage And Retrieval<br />
# Infusion Pump Integration To BPOC<br />
# Point of Care (PoC) Real Time PnP Device Integration<br />
# Home Telehealth<br />
# Alarm Interoperability<br />
# PCA Infusion Safety<br />
<br />
=== New Proposals ===<br />
<br />
Feel free to create new proposal pages based on the [[Brief Proposal Template]], or use the complete [[Proposal Template]].<br />
Remember to save your work under a new page name and post below. <br />
<br />
# [[Remote Monitoring]] - 2007-08 work to be addressed by PCD, Initiated from PCC<br />
<br />
=== PCD Technical Framework Maintenance ===<br />
<br />
The current versions of volumes 1 and 2 of the '''PCD Technical Framework''' can be found at:<br />
<br />
ftp://ftp.ihe.net/Patient_Care_Devices/TechnicalFrameworkforTrialImplementation/</div>Bikramhttp://wiki.ihe.net/index.php?title=PCD_Proposals_Cycle_2&diff=11803PCD Proposals Cycle 22007-11-22T00:36:37Z<p>Bikram: /* Current Proposals under development */</p>
<hr />
<div>=== Current Proposals under development ===<br />
<br />
These '''Detailed Profile Proposals''' were short-listed, evaluated by the Technical Committee and '''selected''' by both committees for development in this Cycle (note: The PoC Real Time PnP Device Integration and Home Telehealth profiles may be developed in steps over a two year period. The latest versions can be found at ftp://ftp.ihe.net/Patient_Care_Devices/IHEPCDyr2-2007-2008/PlanningCommitteeYr2/ProfileProposalsDetailedYr2/<br />
<br />
# Patient ID Binding (tying the patient to the device and its data).<br />
# Point of Care (PoC) Real Time PnP Device Integration.<br />
# Home Telehealth.<br />
# PCD02 Subscribe To Patient Data (permits an EMR to select the data desired); this is a continuation of the PCD's Year 1 effort.<br />
<br />
=== Profile Proposals Submitted ===<br />
<br />
The following '''Brief Profile Proposals''' were submitted for the 2007-2008 Development Cycle and can be found at:<br />
<br />
ftp://ftp.ihe.net/Patient_Care_Devices/IHEPCDyr2-2007-2008/PlanningCommitteeYr2/ProfileProposalsBriefYr2/<br />
<br />
# Small Data Element Exchange<br />
# IHE ECG Workflow<br />
# Patient ID Binding (tying the patient to the device and its data)<br />
# Real Time Clinical Data Management Storage And Retrieval<br />
# Infusion Pump Integration To BPOC<br />
# Point of Care (PoC) Real Time PnP Device Integration<br />
# Home Telehealth<br />
# Alarm Interoperability<br />
# PCA Infusion Safety<br />
<br />
=== New Proposals ===<br />
<br />
Feel free to create new proposal pages based on the [[Brief Proposal Template]]. Remember to save your work under a new page name and post below. <br />
<br />
# [[Remote Monitoring]] - 2007-08 work to be addressed by PCD, Initiated from PCC<br />
<br />
<br />
=== PCD Technical Framework Maintenance ===<br />
<br />
The current versions of volumes 1 and 2 of the '''PCD Technical Framework''' can be found at:<br />
<br />
ftp://ftp.ihe.net/Patient_Care_Devices/TechnicalFrameworkforTrialImplementation/</div>Bikramhttp://wiki.ihe.net/index.php?title=PCD_Proposals_Cycle_2&diff=11794PCD Proposals Cycle 22007-11-21T20:56:05Z<p>Bikram: New page: === Current Proposals under development === These '''Detailed Profile Proposals''' were short-listed, evaluated by the Technical Committee and '''selected''' by both committees for develo...</p>
<hr />
<div>=== Current Proposals under development ===<br />
<br />
These '''Detailed Profile Proposals''' were short-listed, evaluated by the Technical Committee and '''selected''' by both committees for development in this Cycle (note: The PoC Real Time PnP Device Integration and Home Telehealth profiles may be developed in steps overa two year period. The latest versions can be found at ftp://ftp.ihe.net/Patient_Care_Devices/IHEPCDyr2-2007-2008/PlanningCommitteeYr2/ProfileProposalsDetailedYr2/<br />
<br />
# Patient ID Binding (tying the patient to the device and its data)<br />
# Point of Care (PoC) Real Time PnP Device Integration<br />
# Home Telehealth<br />
# PCD02 Subscribe To Patient Data (permits an EMR to select the data desired); this is a continuation of the PCD's Year 1 effort<br />
<br />
<br />
=== Profile Proposals Submitted ===<br />
<br />
The following '''Brief Profile Proposals''' were submitted for the 2007-2008 Development Cycle and can be found at:<br />
<br />
ftp://ftp.ihe.net/Patient_Care_Devices/IHEPCDyr2-2007-2008/PlanningCommitteeYr2/ProfileProposalsBriefYr2/<br />
<br />
# Small Data Element Exchange<br />
# IHE ECG Workflow<br />
# Patient ID Binding (tying the patient to the device and its data)<br />
# Real Time Clinical Data Management Storage And Retrieval<br />
# Infusion Pump Integration To BPOC<br />
# Point of Care (PoC) Real Time PnP Device Integration<br />
# Home Telehealth<br />
# Alarm Interoperability<br />
# PCA Infusion Safety<br />
<br />
=== New Proposals ===<br />
<br />
Feel free to create new proposal pages based on the [[Brief Proposal Template]]. Remember to save your work under a new page name and post below. <br />
<br />
# [[Remote Monitoring]] - 2007-08 work to be addressed by PCD, Initiated from PCC<br />
<br />
<br />
=== PCD Technical Framework Maintenance ===<br />
<br />
The current versions of volumes 1 and 2 of the '''PCD Technical Framework''' can be found at:<br />
<br />
ftp://ftp.ihe.net/Patient_Care_Devices/TechnicalFrameworkforTrialImplementation/</div>Bikramhttp://wiki.ihe.net/index.php?title=Patient_Care_Device&diff=11793Patient Care Device2007-11-21T20:42:02Z<p>Bikram: /* Current Activity */</p>
<hr />
<div>'''IHE Patient Care Device Domain (PCD)''' <br />
<br />
The Patient Care Devices Domain is concerned with Use Cases in which at least one actor is a regulated patient care device. The PCD coordinates with other IHE clinical specialty based domains such as medical imaging.<br />
<br />
'''The Mission of the PCD:'''<br />
<br />
The IHE Patient Care Devices Domain will apply the proven, Use Case driven IHE processes to:<br />
* Deliver the technical framework for the IHE-PCD domain [[profiles]]; <br />
* Validate IHE-PCD profile implementations via Connectathons; and <br />
* Demonstrate marketable solutions at public trade shows.<br />
<br />
'''The PCD's Vision Statement is:'''<br />
<br />
''The IHE Patient Care Devices Domain (IHE PCD) is the nexus for vendors and providers to jointly define and demonstrate unambiguous interoperability specifications, called profiles, which are based on industry standards, and which can be brought to market. '' <br />
<br />
IHE-PCD profiles:<br />
* improve patient safety and clinical efficacy,<br />
* reduce healthcare delivery cost by improving efficiency, reliability, and operational flexibility for healthcare providers,<br />
* enable innovative patient care capabilities, and<br />
* expand the international marketplace for patient care device vendors. <br />
<br />
<br />
IHE Patient Care Device is sponsored by the [http://www.accenet.org American College of Clinical Engineering (ACCE)] and the [http://www.himss.org Health Information Management Systems Society (HIMSS)] and manages the [[Profiles#IHE Patient Care Devices Profiles| IHE Patient Care Device Profiles]] and the [[Frameworks| IHE Patient Care Device Technical Framework]].<br />
<br />
<br />
__TOC__<br />
<br />
==Timeline : 2007-2008 Development Cycle as of April 24, 2007==<br />
<br />
{| style="width:100%" border="1" cellpadding="3"<br />
! Timeframe<br />
! Activity<br />
! Scheduled<br />
! Location<br />
|-<br />
| colspan="4" align="center" style="background:#dddddd" | '''2006'''<br />
|-<br />
|Dec. <br />
| Submit Brief Profile Proposals to Planning Committee (PC)<br />
|-<br />
| colspan="4" align="center" style="background:#dddddd" | '''2007'''<br />
|-<br />
| May 22-23, 23-24<br />
| Face To Face Meetings (Planning then Technical Committees)<br />
|<br />
| Oak Brook, IL (RSNA Offices)<br />
|- <br />
| May 22-June 25<br />
| Develop 2007 Technical Framework Document<br />
|-<br />
| June 1<br />
| Publish final Technical Framework for Year 1<br />
|<br />
|-<br />
| <br />
| Face To Face Meetings to complete the Year 2 TF for Public Comment<br />
| June 20-21 <br />
| Boston area<br />
|-<br />
| June 30<br />
| Publish Technical Framework for Year 2 for Public Comment<br />
|-<br />
| June 30-July 30<br />
| Public Comment Period TF Year 2<br />
|-<br />
| August 20<br />
| After review of public comments, publish TF for Trial Implementation<br />
|-<br />
| September<br />
| Revise Roadmap<br />
|-<br />
| September<br />
| Test Tools available<br />
|-<br />
| October<br />
| Individual Test Results Due Selected Transactions<br />
|-<br />
| October<br />
| Develop HIMSS Showcase Scenario<br />
|-<br />
| November <br />
| Virtual Connectathon for PCD<br />
|-<br />
| colspan="4" align="center" style="background:#dddddd" | '''2008'''<br />
|-<br />
| Jan.<br />
| Test implementations at Connectathon<br />
| <br />
| Chicago<br />
|-<br />
| Feb.<br />
| Demonstration at HIMSS Showcase<br />
|<br />
| Orlando, FL<br />
|}<br />
<br />
==Roadmap==<br />
<br />
The Roadmap found at ftp://ftp.ihe.net/Patient_Care_Devices/Roadmap/ outlines the PCD's goals and plans over the next 5-10 years.<br />
<br />
==Current Activity==<br />
<br />
The IHE Patient Care Device Domain is working on the 2007-2008 Cycle. Four Profiles are in development along with finalizing the PCD-01 Profile developed in Year 1 (2006-7). The four profiles currently under development are listed in [[PCD Proposals 2007-2008]]. Contact Manny at efurst@imp-tech.com if you would like to participate, or watch for Public Comment drafts in December 2007. <br />
<br />
===Profile Selection===<br />
<br />
# The [[PCD-01 Profile]] developed in Year 1 (2006-2007)<br />
# The [[PCD Proposals 2007-2008]] section contains the details on current and proposed Proposals that the PCD Planning and Technical committees are considering for 2007 and 2008.<br />
<br />
==Demonstrations & Presentations==<br />
<br />
{| style="width:100%" border="1" cellpadding="3"<br />
! Date<br />
! Location<br />
! Event<br />
! Details<br />
|-<br />
| 2007.02.27<br />
| New Orleans, LA<br />
| 20070227-HIMSSShowcase-IHE-PCD-C.ppt presented at HIMSS Annual Meeting<br />
| found at ftp://ftp.ihe.net/Patient_Care_Devices/Presentations/''<br />
|-<br />
| April 2007<br />
| Webex Presentation<br />
| "Orientation to the PCD" PDF version: 20070404-IHE-PCD-Orientation.pdf<br />
| found at ftp://ftp.ihe.net/Patient_Care_Devices/Presentations/<br />
|<br />
|-<br />
| Earlier<br />
| <br />
| Earlier presentations are also available<br />
| found at ftp://ftp.ihe.net/Patient_Care_Devices/Presentations/<br />
|<br />
|-<br />
|}<br />
<br />
==Supporters and Endorsements==<br />
<br />
IHE Patient Care Device is supported or endorsed by the following organizations:<br />
<br />
* [http://www.accenet.org American College of Clinical Engineering (ACCE)]<br />
* [http://www.himss.org Health Information Management Systems Society (HIMSS)]<br />
<br />
==See Also==<br />
<br />
[[Committees]]<br />
<br />
[[Patient Care Device Planning Committee]]<br />
<br />
[[Patient Care Device Technical Committee]]<br />
<br />
<br />
This page is based on the [[Domain Template]].</div>Bikramhttp://wiki.ihe.net/index.php?title=Patient_Care_Device&diff=11792Patient Care Device2007-11-21T20:36:32Z<p>Bikram: /* Profile Selection */</p>
<hr />
<div>'''IHE Patient Care Device Domain (PCD)''' <br />
<br />
The Patient Care Devices Domain is concerned with Use Cases in which at least one actor is a regulated patient care device. The PCD coordinates with other IHE clinical specialty based domains such as medical imaging.<br />
<br />
'''The Mission of the PCD:'''<br />
<br />
The IHE Patient Care Devices Domain will apply the proven, Use Case driven IHE processes to:<br />
* Deliver the technical framework for the IHE-PCD domain [[profiles]]; <br />
* Validate IHE-PCD profile implementations via Connectathons; and <br />
* Demonstrate marketable solutions at public trade shows.<br />
<br />
'''The PCD's Vision Statement is:'''<br />
<br />
''The IHE Patient Care Devices Domain (IHE PCD) is the nexus for vendors and providers to jointly define and demonstrate unambiguous interoperability specifications, called profiles, which are based on industry standards, and which can be brought to market. '' <br />
<br />
IHE-PCD profiles:<br />
* improve patient safety and clinical efficacy,<br />
* reduce healthcare delivery cost by improving efficiency, reliability, and operational flexibility for healthcare providers,<br />
* enable innovative patient care capabilities, and<br />
* expand the international marketplace for patient care device vendors. <br />
<br />
<br />
IHE Patient Care Device is sponsored by the [http://www.accenet.org American College of Clinical Engineering (ACCE)] and the [http://www.himss.org Health Information Management Systems Society (HIMSS)] and manages the [[Profiles#IHE Patient Care Devices Profiles| IHE Patient Care Device Profiles]] and the [[Frameworks| IHE Patient Care Device Technical Framework]].<br />
<br />
<br />
__TOC__<br />
<br />
==Timeline : 2007-2008 Development Cycle as of April 24, 2007==<br />
<br />
{| style="width:100%" border="1" cellpadding="3"<br />
! Timeframe<br />
! Activity<br />
! Scheduled<br />
! Location<br />
|-<br />
| colspan="4" align="center" style="background:#dddddd" | '''2006'''<br />
|-<br />
|Dec. <br />
| Submit Brief Profile Proposals to Planning Committee (PC)<br />
|-<br />
| colspan="4" align="center" style="background:#dddddd" | '''2007'''<br />
|-<br />
| May 22-23, 23-24<br />
| Face To Face Meetings (Planning then Technical Committees)<br />
|<br />
| Oak Brook, IL (RSNA Offices)<br />
|- <br />
| May 22-June 25<br />
| Develop 2007 Technical Framework Document<br />
|-<br />
| June 1<br />
| Publish final Technical Framework for Year 1<br />
|<br />
|-<br />
| <br />
| Face To Face Meetings to complete the Year 2 TF for Public Comment<br />
| June 20-21 <br />
| Boston area<br />
|-<br />
| June 30<br />
| Publish Technical Framework for Year 2 for Public Comment<br />
|-<br />
| June 30-July 30<br />
| Public Comment Period TF Year 2<br />
|-<br />
| August 20<br />
| After review of public comments, publish TF for Trial Implementation<br />
|-<br />
| September<br />
| Revise Roadmap<br />
|-<br />
| September<br />
| Test Tools available<br />
|-<br />
| October<br />
| Individual Test Results Due Selected Transactions<br />
|-<br />
| October<br />
| Develop HIMSS Showcase Scenario<br />
|-<br />
| November <br />
| Virtual Connectathon for PCD<br />
|-<br />
| colspan="4" align="center" style="background:#dddddd" | '''2008'''<br />
|-<br />
| Jan.<br />
| Test implementations at Connectathon<br />
| <br />
| Chicago<br />
|-<br />
| Feb.<br />
| Demonstration at HIMSS Showcase<br />
|<br />
| Orlando, FL<br />
|}<br />
<br />
==Roadmap==<br />
<br />
The Roadmap found at ftp://ftp.ihe.net/Patient_Care_Devices/Roadmap/ outlines the PCD's goals and plans over the next 5-10 years.<br />
<br />
==Current Activity==<br />
<br />
The IHE Patient Care Device Domain is working on the 2007-2008 Cycle. Four Profiles are in development along with finalizing the PCD-01 Profile developed in Year 1 (2006-7). The four prfiles currently under development are listed below. Contact Manny at efurst@imp-tech.com if you would like to participate, or watch for Public Comment drafts in December 2007. <br />
<br />
===Profile Selection===<br />
<br />
The [[PCD Proposals 2007-2008]] section contains the details on current and proposed Proposals that the PCD Planning and Technical committees are considering for 2007 and 2008.<br />
<br />
==Demonstrations & Presentations==<br />
<br />
{| style="width:100%" border="1" cellpadding="3"<br />
! Date<br />
! Location<br />
! Event<br />
! Details<br />
|-<br />
| 2007.02.27<br />
| New Orleans, LA<br />
| 20070227-HIMSSShowcase-IHE-PCD-C.ppt presented at HIMSS Annual Meeting<br />
| found at ftp://ftp.ihe.net/Patient_Care_Devices/Presentations/''<br />
|-<br />
| April 2007<br />
| Webex Presentation<br />
| "Orientation to the PCD" PDF version: 20070404-IHE-PCD-Orientation.pdf<br />
| found at ftp://ftp.ihe.net/Patient_Care_Devices/Presentations/<br />
|<br />
|-<br />
| Earlier<br />
| <br />
| Earlier presentations are also available<br />
| found at ftp://ftp.ihe.net/Patient_Care_Devices/Presentations/<br />
|<br />
|-<br />
|}<br />
<br />
==Supporters and Endorsements==<br />
<br />
IHE Patient Care Device is supported or endorsed by the following organizations:<br />
<br />
* [http://www.accenet.org American College of Clinical Engineering (ACCE)]<br />
* [http://www.himss.org Health Information Management Systems Society (HIMSS)]<br />
<br />
==See Also==<br />
<br />
[[Committees]]<br />
<br />
[[Patient Care Device Planning Committee]]<br />
<br />
[[Patient Care Device Technical Committee]]<br />
<br />
<br />
This page is based on the [[Domain Template]].</div>Bikramhttp://wiki.ihe.net/index.php?title=Patient_Care_Device&diff=10808Patient Care Device2007-10-26T15:29:34Z<p>Bikram: </p>
<hr />
<div>'''IHE Patient Care Device Domain (PCD)''' <br />
<br />
The Patient Care Devices Domain is concerned with Use Cases in which at least one actor is a regulated patient care device. The PCD coordinates with other IHE clinical specialty based domains such as medical imaging.<br />
<br />
'''The Mission of the PCD:'''<br />
<br />
The IHE Patient Care Devices Domain will apply the proven, Use Case driven IHE processes to:<br />
* Deliver the technical framework for the IHE-PCD domain [[profiles]]; <br />
* Validate IHE-PCD profile implementations via Connectathons; and <br />
* Demonstrate marketable solutions at public trade shows.<br />
<br />
'''The PCD's Vision Statement is:'''<br />
<br />
''The IHE Patient Care Devices Domain (IHE PCD) is the nexus for vendors and providers to jointly define and demonstrate unambiguous interoperability specifications, called profiles, which are based on industry standards, and which can be brought to market. '' <br />
<br />
IHE-PCD profiles:<br />
* improve patient safety and clinical efficacy,<br />
* reduce healthcare delivery cost by improving efficiency, reliability, and operational flexibility for healthcare providers,<br />
* enable innovative patient care capabilities, and<br />
* expand the international marketplace for patient care device vendors. <br />
<br />
<br />
IHE Patient Care Device is sponsored by the [http://www.accenet.org American College of Clinical Engineering (ACCE)] and the [http://www.himss.org Health Information Management Systems Society (HIMSS)] and manages the [[Profiles#IHE Patient Care Devices Profiles| IHE Patient Care Device Profiles]] and the [[Frameworks| IHE Patient Care Device Technical Framework]].<br />
<br />
<br />
__TOC__<br />
<br />
==Timeline : 2007-2008 Development Cycle as of April 24, 2007==<br />
<br />
{| style="width:100%" border="1" cellpadding="3"<br />
! Timeframe<br />
! Activity<br />
! Scheduled<br />
! Location<br />
|-<br />
| colspan="4" align="center" style="background:#dddddd" | '''2006'''<br />
|-<br />
|Dec. <br />
| Submit Brief Profile Proposals to Planning Committee (PC)<br />
|-<br />
| colspan="4" align="center" style="background:#dddddd" | '''2007'''<br />
|-<br />
| May 22-23, 23-24<br />
| Face To Face Meetings (Planning then Technical Committees)<br />
|<br />
| Oak Brook, IL (RSNA Offices)<br />
|- <br />
| May 22-June 25<br />
| Develop 2007 Technical Framework Documents<br />
|-<br />
| June 1<br />
| Publish final Technical Framework for Year 1<br />
|-<br />
| June 20-21 <br />
| Face To Face Meetings to complete the Year 2 TF for Public Comment<br />
| The meeting will take place in the Boston area<br />
|-<br />
| June 30<br />
| Publish Technical Framework for Year 2 for Public Comment<br />
|-<br />
| June 30-July 30<br />
| Public Comment Period TF Year 2<br />
|-<br />
| August 20<br />
| After review of public comments, publish TF for Trial Implementation<br />
|-<br />
| September<br />
| Revise Roadmap<br />
|-<br />
| September<br />
| Test Tools available<br />
|-<br />
| October<br />
| Individual Test Results Due Selected Transactions<br />
|-<br />
| October<br />
| Develop HIMSS Showcase Scenario<br />
|-<br />
| November <br />
| Virtual Connectathon for PCD<br />
|-<br />
| colspan="4" align="center" style="background:#dddddd" | '''2008'''<br />
|-<br />
| Jan.<br />
| Test implementations at Connectathon<br />
| <br />
| Chicago<br />
|-<br />
| Feb.<br />
| Demonstration at HIMSS Showcase<br />
|<br />
| Orlando, FL<br />
|}<br />
<br />
==Roadmap==<br />
<br />
The Roadmap found at ftp://ftp.ihe.net/Patient_Care_Devices/Roadmap/ outlines the PCD's goals and plans over the next 5-10 years.<br />
<br />
==Current Activity==<br />
<br />
The IHE Patient Care Device Domain is working on the 2007-2008 Cycle. Four Profiles are in development along with finalizing the PCD-01 Profile developed in Year 1 (2006-7). The four prfiles currently under development are listed below. Contact Manny at efurst@imp-tech.com if you would like to participate, or watch for Public Comment drafts in December 2007. <br />
<br />
===Profile Selection===<br />
<br />
The following '''Brief Profile Proposals''' were submitted for the 2007-2008 Development Cycle and can be found at ftp://ftp.ihe.net/Patient_Care_Devices/IHEPCDyr2-2007-2008/PlanningCommitteeYr2/ProfileProposalsBriefYr2/<br />
* Small Data Element Exchange<br />
* IHE ECG Workflow<br />
* Patient ID Binding (tying the patient to the device and its data)<br />
* Real Time Clinical Data Management Storage And Retrieval<br />
* Infusion Pump Integration To BPOC<br />
* Point of Care (PoC) Real Time PnP Device Integration<br />
* Home Telehealth<br />
* Alarm Interoperability<br />
* PCA Infusion Safety<br />
<br />
These '''Detailed Profile Proposals''' were short-listed, evaluated by the Technical Committee and '''selected''' by both committees for development in this Cycle (note: The PoC Real Time PnP Device Integration and Home Telehealth profiles may be developed in steps overa two year period. The latest versions can be found at ftp://ftp.ihe.net/Patient_Care_Devices/IHEPCDyr2-2007-2008/PlanningCommitteeYr2/ProfileProposalsDetailedYr2/<br />
* Patient ID Binding (tying the patient to the device and its data)<br />
* Point of Care (PoC) Real Time PnP Device Integration<br />
* Home Telehealth<br />
* PCD02 Subscribe To Patient Data (permits an EMR to select the data desired); this is a continuation of the PCD's Year 1 effort<br />
<br />
* TF Maintenance<br />
<br />
The current versions of volumes 1 and 2 of the '''PCD Technical Framework''' can be found at<br />
ftp://ftp.ihe.net/Patient_Care_Devices/TechnicalFrameworkforTrialImplementation/<br />
<br />
==Demonstrations & Presentations==<br />
<br />
{| style="width:100%" border="1" cellpadding="3"<br />
! Date<br />
! Location<br />
! Event<br />
! Details<br />
|-<br />
| 2007.02.27<br />
| New Orleans, LA<br />
| 20070227-HIMSSShowcase-IHE-PCD-C.ppt presented at HIMSS Annual Meeting<br />
| found at ftp://ftp.ihe.net/Patient_Care_Devices/Presentations/''<br />
|-<br />
| April 2007<br />
| Webex Presentation<br />
| "Orientation to the PCD" PDF version: 20070404-IHE-PCD-Orientation.pdf<br />
| found at ftp://ftp.ihe.net/Patient_Care_Devices/Presentations/<br />
|<br />
|-<br />
| Earlier<br />
| <br />
| Earlier presentations are also available<br />
| found at ftp://ftp.ihe.net/Patient_Care_Devices/Presentations/<br />
|<br />
|-<br />
|}<br />
<br />
==Supporters and Endorsements==<br />
<br />
IHE Patient Care Device is supported or endorsed by the following organizations:<br />
<br />
* [http://www.accenet.org American College of Clinical Engineering (ACCE)]<br />
* [http://www.himss.org Health Information Management Systems Society (HIMSS)]<br />
<br />
==See Also==<br />
<br />
[[Committees]]<br />
<br />
<br />
<br />
This page is based on the [[Domain Template]].</div>Bikramhttp://wiki.ihe.net/index.php?title=Talk:Patient_Care_Device&diff=10723Talk:Patient Care Device2007-10-24T20:49:46Z<p>Bikram: /* This page is for moderator discussions - */</p>
<hr />
<div>== This page is for moderator discussions - ==<br />
<br />
The previous page has been moved here: [[PCD COMMENTS ON DRAFT IHE GOVERNANCE DOCUMENT IN PUBLIC COMMENT PERIOD]]<br />
--[[User:Bikram|Bikram]] 15:47, 24 October 2007 (CDT)<br />
<br />
----</div>Bikramhttp://wiki.ihe.net/index.php?title=Talk:Patient_Care_Device&diff=10720Talk:Patient Care Device2007-10-24T20:47:31Z<p>Bikram: </p>
<hr />
<div>== This page is for moderator discussions - ==<br />
<br />
The previous page has been moved here: [[PCD COMMENTS ON DRAFT IHE GOVERNANCE DOCUMENT IN PUBLIC COMMENT PERIOD]]<br />
--[[User:Bikram|bikram]] 15:47, 24 October 2007 (CDT)<br />
<br />
----</div>Bikramhttp://wiki.ihe.net/index.php?title=Talk:Patient_Care_Device&diff=10715Talk:Patient Care Device2007-10-24T20:40:16Z<p>Bikram: Talk:Patient Care Devices moved to PCD COMMENTS ON DRAFT IHE GOVERNANCE DOCUMENT IN PUBLIC COMMENT PERIOD: Free up main talk page for moderator comments</p>
<hr />
<div>#REDIRECT [[PCD COMMENTS ON DRAFT IHE GOVERNANCE DOCUMENT IN PUBLIC COMMENT PERIOD]]</div>Bikramhttp://wiki.ihe.net/index.php?title=PCD_COMMENTS_ON_DRAFT_IHE_GOVERNANCE_DOCUMENT_IN_PUBLIC_COMMENT_PERIOD&diff=10714PCD COMMENTS ON DRAFT IHE GOVERNANCE DOCUMENT IN PUBLIC COMMENT PERIOD2007-10-24T20:40:16Z<p>Bikram: Talk:Patient Care Devices moved to PCD COMMENTS ON DRAFT IHE GOVERNANCE DOCUMENT IN PUBLIC COMMENT PERIOD: Free up main talk page for moderator comments</p>
<hr />
<div>== Headline text ==<br />
'''PCD COMMENTS ON DRAFT IHE GOVERNANCE DOCUMENT IN PUBLIC COMMENT PERIOD'''<br />
<br />
PLEASE PROVIDE YOUR COMMENTS BELOW. PLEASE INDICATE IF YOUR COMMENT(S) IS/ARE SUBSTANTIVE OR EDITORIAL (PLEASE GROUP THEM INTO THESE TWO CATEGORIES). BE AS SPECIFIC AS POSSIBLE: PROVIDE A PAGE/SECTION OR LINE NUMBER, YOUR NAME, EMAIL AND PHONE NUMBER.<br />
<br />
BY APRIL 28 YOU WILL HAVE RECEIVED NOTICE OF A WEBEX SUPPORTED CONFERENCE CALL FOR THURSDAY, MAY 3 AT 3PM EDT/NOON PDT.<br />
<br />
PLEASE CLICK ON THE + TAB ABOVE (article, discussion, edit tabs precede the + tab). ENTER YOUR COMMENT, THEN SCROLL DOWN TO FIND THE '''SAVE''' BUTTON.<br />
<br />
Ray: [[SUBSTANTIVE QUESTION]] There has been expressed concerns amongst the PCD that the notification requirements for meetings may be too long to be practical, given the relatively rapid pace of development and frquescy of meetings in the domain. Would an alternative to 60 days notice of a meeting, 30 of a T-con be to post a schedule for regularly occurring meetings and then post/notify of cancellations within 24-48 hours? - rzambuto@techmed.com<br />
<br />
Manny, efurst@imp-tech.com, 520-721-2856:<br />
SUBSTANTIVE<br />
|What is a Partnership Agreement (line 176)?<br />
|Is the Board Operations Committee providing advice to the sponsoring organizations or to the IHE Board (line 283)?<br />
|Line 299 does not refer to public availability of the minutes. Line 889 does, but not specifically. Should the minutes or a summary of actions be "required" to be promulgated as part of the transparency effort?<br />
|Is each Deployment Committee to provide a budget for the IHE International Board (line 332) or to provide its own budget? This appears to relate to the next item on the list.<br />
|In a related matter, the next paragraph (lines 339-345) describes an agreement to support the Secretariat, but not the items listed in #6 above.<br />
|Would the users not be making or participating in acquisition decisions (lines 357-9)? If not, what interest would some have in the IHE? Similarly, would the developer representatives not be making or participating in development (lines 360-5)? In contrast, 10.1.2, page 22 says members must have a material and direct interest.<br />
|What is the meaning of the "committee's standard" (line 466)?<br />
|What do they do with the information obtained and what actions are taken to optimize the development (line 503)?<br />
|Are the results of a Connectathon applicable internationally, or does a vendor need to participate in other regional/national Connectathons?<br />
|Which committees/groups make annual reports to the Board (this is in lines 564,)<br />
|Do the National/Regional committees provide annual reports (line 670)?<br />
|Membership doesn't appear to include individual companies, but rather trade organizations (680-3) yet does appear in the table on page 21.<br />
|Patient representatives and payers are not clearly organizations, and public interest groups or other entities are not included to represent the individual patient (lines 681-3) yet appear to be included on page 21.<br />
|Voting and Quorum, Section 10.2.3: What steps would a committee have to take to conform to the 50% rule? The PCD has almost 200 "members,” with only about 15 actively participating in the Planning or Technical Committees. E.g., would we have two levels - active and observers? <br />
|Is the recall process defined (line 811)?<br />
|Subcommittees (lines 814-6): would "working groups" of those developing a specific profile be considered a subcommittee?<br />
|Terms of office appear to be calendar years, but this is not stated (line 858).<br />
|Does this apply to all committees at all levels (line 866)?<br />
|What is the representation/voting role of an individual (e.g., a single-person consulting organization or a member of the public)?<br />
|A.1.1.1 Copyright License: should this be expanded to include IHE presentations (e.g., slide presentations at HIMSS).<br />
<br />
EDITORIAL<br />
|Why are governmental organizations excluded (line 189) but not in 10.1.2, page 22?<br />
|Member Organizations has not yet been defined (line 197) (could be a reference to a later section); since mention has earlier been made to Stakeholders this definition may be helpful in distinguishing between individuals, individual companies, etc.<br />
|IHE International Sponsor has not yet been defined (line 199).<br />
|Is there a reason why the two co-chairs are not elected in alternate years (in line 220) but is generally the case (line 850)? Why have this information in multiple, and perhaps differently worded, locations?<br />
|For consistency with the other numbered items, insert "or" near end of line 227 and place or remove semicolons from inconsistent lines in 4.2.3 (see other numbered lists for comparison as well).<br />
|For consistency, insert "of the IHE Board" in line 234.<br />
|"IHE International Sponsor" has not yet been defined (line 295)?<br />
|Initiative Sponsors (line 366) are not identified in the section heading. "support" is not defined - logistics, financial, etc.? This contrasts with the detail in 4.3.4.<br />
|Place or remove period & semicolon from inconsistent lines in lines 396, 400.<br />
|Should Profile be capitalized (line 417) for consistency?<br />
|The Technical Committee can adopt committee policies and procedures (line 467); the same is not included for the Planning Committee.<br />
|Where published (line 470) and where announced to the public?<br />
|Are definitions required for (or a reference to later definitions of) Technical Project Management (line 532, 553), Technical Management Group (line 541)?<br />
|Is a definition/reference to a definition needed for Technical Steering Committee (line 572)?<br />
|The two word term "Integration Profile" appears in line 628 and as far as I can see, nowhere else.<br />
|Typo, line 643: "ore"<br />
|Should "objects" be "objectives" (line 656)?<br />
|National Deployment and Regional Deployment Committees have distinct sections (8. 9), yet section 9 addresses both, and they appear to have different membership requirements (one doesn't appear to include individual companies, organizations). <br />
|Typo: line 686 has an extra "1".<br />
|Both "subcommittees" and "working groups" are in 9.2.2 (line 684); this is the first time "working groups" appears - is this a separate definition/role?<br />
|Semicolon in line 688.<br />
|Should co-chair be plural (line 749)?<br />
|Section 10.2.1 appears to mix requirements for the Board with those for committees (lines 765-6). Is it necessary to have 60 days notice of F2F meetings at all committee levels? In comparison, amendments only require 30 days notice (line 952).<br />
|Reword lines 943-7 consistent with a leading sentence ending in a colon.<br />
|There were several references to Intellectual Property throughout the document. Would it help to insert "(Appendix A)" in some of these to make the location clear?<br />
|Appendix, end: should title of the person signing, and the name, address of the company be added?</div>Bikram