检索历史 清除

摘要<p id="s00002">1.1 The Continuity of Care Record (CCR) is a core data set of the most relevant administrative, demographic, and clinical information facts about a patient<span class=''unicode''>x2019;</span>s healthcare, covering one or more healthcare encounters. It provides a means for one healthcare practitioner, system, or setting to aggregate all of the pertinent data about a patient and forward it to another practitioner, system, or setting to support the continuity of care.</p> <p id="s00003">1.1.1 The CCR data set includes a summary of the patient<span class=''unicode''>x2019;</span>s health status (for example, problems, medications, allergies) and basic information about insurance, advance directives, care documentation, and the patient<span class=''unicode''>x2019;</span>s care plan. It also includes identifying information and the purpose of the CCR. (See 5.1 for a description of the CCR<span class=''unicode''>x2019;</span>s components and sections, and Annex A1 for the detailed data fields of the CCR.)</p> <p id="s00004">1.1.2 The CCR may be prepared, displayed, and transmitted on paper or electronically, provided the information required by this specification is included. When prepared in a structured electronic format, strict adherence to an XML schema and an accompanying implementation guide is required to support standards-compliant interoperability. The Adjunct to this specification contains a W3C XML schema and Annex A2 contains an Implementation Guide for such representation.</p> <p id="s00005">1.2 The primary use case for the CCR is to provide a snapshot in time containing the pertinent clinical, demographic, and administrative data for a specific patient.</p> <p id="s00006">1.2.1 This specification does not speak to other use cases or to workflows, but is intended to facilitate the implementation of use cases and workflows. Any examples offered in this specification are not to be considered normative. </p> <p id="s00007">1.3 To ensure interchangeability of electronic CCRs, this specification specifies XML codingnbsp;nbsp;nbsp;that is required when the CCR is created in a structured electronic format. This specified XML coding provides flexibility that will allow users to prepare, transmit, and view the CCR in multiple ways, for example, in a browser, as an element in a Health Level 7 (HL7) message or CDA compliant document, in a secure email, as a PDF file, as an HTML file, or as a word processing document. It will further permit users to display the fields of the CCR in multiple formats.</p> <p id="s00008">1.3.1 The CCR XML schema or .xsd (see the Adjunct to this specification) is defined as a data object that represents a snapshot of a patient<span class=''unicode''>x2019;</span>s relevant administrative, demographic, and clinical information at a specific moment in time. The CCR XML is not a persistent document, and it is not a messaging standard.</p> <p class="desc" id="N00001"> <span class="smallcap">Note</span> 18212;The CCR XML schema can also be used to define an XML representation for the CCR data elements, subject to the constraints specified in the accompanying Implementation Guide (see Annex A2).</p> <p id="s00009">1.3.2 Using the required XML schema in the Adjunct to this specification or other XML schemas that may be authorized through joints efforts of ASTM and other standards development organizations, properly designed electronic healthcare record (EHR) systems will be able to import and export all CCR data to enable automated healthcare information transmission with minimal workflow disruption for practitioners. Equally important, it will allow the interchange of the CCR data between otherwise incompatible EHR systems.</p> <p id="s00010">1.4 <span class="italic"><span class="italic">Security</span>8212;</span>The data contained within the CCR are patient data and, if those data arenbsp;nbsp;nbsp;identifiable, then end-to-end CCR document integrity......