IHE Patient Care Coordination Technical Framework Vol I
IHE Patient Care Coordination Technical Framework Vol I
IHE Patient Care Coordination Technical Framework Vol I
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
PCC <strong>Technical</strong> <strong>Framework</strong> V3.0, vol. 1<br />
________________________________________________________________________<br />
295<br />
300<br />
305<br />
310<br />
The first of these principles is that any extensions or clarifications to the <strong>Technical</strong><br />
<strong>Framework</strong> must maintain backward compatibility with previous versions of the<br />
framework (except in rare cases for corrections) in order to maintain interoperability with<br />
systems that have implemented <strong>IHE</strong> Actors and Integration Profiles defined there. The<br />
<strong>IHE</strong> <strong>Patient</strong> <strong>Care</strong> <strong>Coordination</strong> <strong>Technical</strong> <strong>Framework</strong> is developed and re-published<br />
annually following a three-step process:<br />
1. The <strong>Patient</strong> <strong>Care</strong> <strong>Coordination</strong> <strong>Technical</strong> Committee develops supplements to the<br />
current stable version of the <strong>Technical</strong> <strong>Framework</strong> to support new functionality<br />
identified by the <strong>IHE</strong> Strategic and PCC Planning Committees and issues them for<br />
public comment.<br />
2. The Committee addresses all comments received during the public comment<br />
period and publishes an updated version of the <strong>Technical</strong> <strong>Framework</strong> for “Trial<br />
Implementation.” This version contains both the stable body of the <strong>Technical</strong><br />
<strong>Framework</strong> from the preceding cycle and the newly developed supplements. It is<br />
this version of the <strong>Technical</strong> <strong>Framework</strong> that is used by vendors in developing<br />
trial implementation software for the <strong>IHE</strong> Connectathons.<br />
3. The Committee regularly considers change proposals to the Trial Implementation<br />
version of the <strong>Technical</strong> <strong>Framework</strong>, including those from implementers who<br />
participate in the Connectathon. After resolution of all change proposals received<br />
within 60 days of the Connectathon, the <strong>Technical</strong> <strong>Framework</strong> version is<br />
published as “Final Text”.<br />
As part of the <strong>Technical</strong> framework maintenance the Committee will consider change<br />
proposals received after the publication to the “Final Text”.<br />
315<br />
320<br />
325<br />
2.4 History of Annual Changes<br />
In the 2005-2006 cycle of the <strong>IHE</strong> <strong>Patient</strong> <strong>Care</strong> <strong>Coordination</strong> initiative, the first release of<br />
the <strong>IHE</strong> PCC <strong>Technical</strong> <strong>Framework</strong> introduced the following integration profile:<br />
• Cross-Enterprise Sharing of Medical Summaries (XDS-MS) – a mechanism to<br />
automate the sharing process between care providers of Medical Summaries, a<br />
class of clinical documents that contain the most relevant portions of information<br />
about the patient intended for a specific provider or a broad range of potential<br />
providers in different settings. Medical Summaries are commonly created and<br />
consumed at points in time of transfers of care such as referrals or discharge.<br />
In the 2006-2007 cycle of the <strong>IHE</strong> <strong>Patient</strong> <strong>Care</strong> <strong>Coordination</strong> initiative, the following<br />
integration profiles were added to the technical framework.<br />
• Exchange of Personal Health Record Content (XPHR) – provides a standardsbased<br />
specification for managing the interchange of documents between a<br />
Personal Health Record used by a patient and systems used by other healthcare<br />
providers to enable better interoperability between these systems.<br />
_____________________________________________________________________<br />
10<br />
Revision 3.0 Public Comment — June 25, 2007<br />
Copyright © 1997-2007: ACC/HIMSS/RSNA