Cardiovascular Business - May/June 2008 - (Page 32)

InteroperaBIlIty › REsouRCEs foR fuRtHER InfoRmAtIon the portable document file, or PDF, standard) cardiology clinical reports from the department to the healthcare enterprise. IHE Cardiology 2005-2007 White Papers – a source for more detailed information regarding the implementation of Ihe cardiology Profiles http://www.ihe.net/cardiology/committees/index.cfm IHE Cardiology Technical Framework – a site for the publication of cardiology Ihe technical documents http://www.ihe.net/technical_Framework/index. cfm#cardiology IHE Connectathon Results – a site for viewing Ihe interoperability testing results by vendor, profile or actor http://ihe.univ-rennes1.fr/con_result/ Q A Q A Q A How long have these profiles been under development? Cardiology has been a committee for almost five years with the first profiles released in 2004 and tested at the 2005 North America Connectathon. What is the importance of these profiles for the vendor? Adoption of the profiles allows a company to identify a common interface for all vendors. This decreases the costs of implementation and development of company-specific interfaces. IHE Wiki – a collaborative site for the creation of Ihe materials http://wiki.ihe.net/index.php?title=Main_Page What is the importance of these profiles for the end-user? The cardiology profiles are workflow-oriented and are built around real-world cases and issues. The profiles are designed to facilitate the interconnectivity of the multi-vendor deployment that is commonly found in the cardiovascular environment. This not only improves the workflow for the hospital, but since IHE provides a standard methodology for this connectivity, it decreases the costs and proprietary nature of informatics interfaces. Q A Q A What cardiology profiles are under development? As Year 5 unfolds, we’re working on an Image Enabled Office Profile, an ECG Workflow Profile, and are crafting a major revision to the Implanted Device Cardiac Observations (IDCO) Profile. Q A Is it prudent for end-users to include compliance with these profiles in cardiology information system requests for proposals? We understand that the ACC has announced it will no longer be the primary sponsor of the cardiology domain. How will this affect the work of the IHE cardiology committees? The actual impact of this decision still is somewhat uncertain; but it will most likely result in a slowing of efforts within the cardiology domain. The Planning Committee has been actively recruiting funding from the various cardiovascular societies, but given today’s tight budget cycles, this funding has been hard to find. We have put a lot of effort into demonstrating how clinical customers can use the IHE cardiology profiles in their requests for proposals from informatics vendors. We have a number of white papers, available online (see list above), that can help guide interoperability requirements. 32 Cardiovascular Business May/June 2008 http://www.ihe.net/Cardiology/committees/index.cfm http://www.ihe.net/Technical_Framework/index.cfm#cardiology http://www.ihe.net/Technical_Framework/index.cfm#cardiology http://ihe.univ-rennes1.fr/con_result/ http://wiki.ihe.net/index.php?title=Main_Page

Table of Contents Feed for the Digital Edition of Cardiovascular Business - May/June 2008

Cardiovascular Business - May/June 2008 Contents First Word Cover Story - Coronary CTA: Drafting the Strategic Plan Financing New Technologies: Early Adopters, Lease vs. Purchase, and Joint Ventures Clinical Study Digest: ACE or ARB: It's Your Choice Can Off-Hour D2B Times Be Reduced Without Breaking the Bank? Digital Image Management Primer: Integrating Echo SPECT/CT for Cardiac Disease Detection: An Economic Conundrum Integrating the Healthcare Enterprise Connects IT Systems News & Views Calendar Reader's Resources The Back Page

Cardiovascular Business - May/June 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.