Standard Specification for Continuity of Care Record (CCR)

ABSTRACT
The Continuity of Care Record (CCR) is a core data set of the most relevant administrative, demographic, and clinical information facts about a patient'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. 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. To ensure interchangeability of electronic CCRs, this specification specifies XML coding that is required when the CCR is created in a structured electronic format. Conditions of security and privacy for a CCR instance must be established in a way that allows only properly authenticated and authorized access to the CCR document instance or its elements. The CCR consists of three core components: the CCR Header, the CCR Body, and the CCR Footer.
SCOPE
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’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.
1.1.1 The CCR data set includes a summary of the patient’s health status (for example, problems, medications, allergies) and basic information about insurance, advance directives, care documentation, and the patient’s care plan. It also includes identifying information and the purpose of the CCR. (See 5.1 for a description of the CCR’s components and sections, and Annex A1 for the detailed data fields of the CCR.)
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.
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.
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.  
1.3 To ensure interchangeability of electronic CCRs, this specification specifies XML coding 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.
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’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.
Note 1—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).
1.3.2 Using the required XML schema in the Adjunct to this specification or other XML schemas that may be authori...

General Information

Status
Historical
Publication Date
30-Sep-2005
Current Stage
Ref Project

Relations

Buy Standard

Technical specification
ASTM E2369-05e1 - Standard Specification for Continuity of Care Record (CCR)
English language
100 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

NOTICE: This standard has either been superseded and replaced by a new version or withdrawn.
Contact ASTM International (www.astm.org) for the latest information
An American National Standard
´1
Designation: E2369 – 05
Standard Specification for
1
Continuity of Care Record (CCR)
This standard is issued under the fixed designation E2369; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. A
superscript epsilon (´) indicates an editorial change since the last revision or reapproval.
1
´ NOTE—Section 2 was corrected editorially in August 2009.
1. Scope of use cases and workflows. Any examples offered in this
4
specification are not to be considered normative.
1.1 The Continuity of Care Record (CCR) is a core data set
1.3 To ensure interchangeability of electronic CCRs, this
of the most relevant administrative, demographic, and clinical
specification specifies XML coding that is required when the
information facts about a patient’s healthcare, covering one or
5
2
CCR is created in a structured electronic format. This speci-
more healthcare encounters. It provides a means for one
fied XML coding provides flexibility that will allow users to
healthcarepractitioner,system,orsettingtoaggregateallofthe
prepare, transmit, and view the CCR in multiple ways, for
pertinent data about a patient and forward it to another
example,inabrowser,asanelementinaHealthLevel7(HL7)
practitioner,system,orsettingtosupportthecontinuityofcare.
message or CDA compliant document, in a secure email, as a
1.1.1 The CCR data set includes a summary of the patient’s
PDF file, as an HTML file, or as a word processing document.
health status (for example, problems, medications, allergies)
It will further permit users to display the fields of the CCR in
andbasicinformationaboutinsurance,advancedirectives,care
multiple formats.
documentation, and the patient’s care plan. It also includes
1.3.1 TheCCRXMLschemaor.xsd(seetheAdjuncttothis
identifying information and the purpose of the CCR. (See 5.1
specification) is defined as a data object that represents a
for a description of the CCR’s components and sections, and
snapshot of a patient’s relevant administrative, demographic,
Annex A1 for the detailed data fields of the CCR.)
andclinicalinformationataspecificmomentintime.TheCCR
1.1.2 The CCR may be prepared, displayed, and transmitted
XML is not a persistent document, and it is not a messaging
on paper or electronically, provided the information required
standard.
by this specification is included.When prepared in a structured
electronic format, strict adherence to an XML schema and an
NOTE 1—The CCR XML schema can also be used to define an XML
accompanying implementation guide is required to support representation for the CCR data elements, subject to the constraints
3
specified in the accompanying Implementation Guide (see Annex A2).
standards-compliant interoperability. The Adjunct to this
specification contains a W3C XML schema and Annex A2
1.3.2 Using the required XMLschema in theAdjunct to this
contains an Implementation Guide for such representation.
specification or other XML schemas that may be authorized
1.2 The primary use case for the CCR is to provide a
through joints efforts of ASTM and other standards develop-
snapshot in time containing the pertinent clinical, demo-
ment organizations, properly designed electronic healthcare
graphic, and administrative data for a specific patient.
record (EHR) systems will be able to import and export all
1.2.1 This specification does not speak to other use cases or
CCR data to enable automated healthcare information trans-
to workflows, but is intended to facilitate the implementation
mission with minimal workflow disruption for practitioners.
Equally important, it will allow the interchange of the CCR
1
data between otherwise incompatible EHR systems.
This specification is under the jurisdiction of ASTM Committee E31 on
Healthcare Informatics and is the direct responsibility of Subcommittee E31.25 on
1.4 Security—The data contained within the CCR are pa-
Healthcare Data Management, Security, Confidentiality, and Privacy.
tient data and, if those data are identifiable, then end-to-end
Current edition approved July 17, 2006. Published December 2006. DOI:
CCR document integrity and confidentiality must be provided
10.1520/E2369-05E01.
2
A CCR is not intended to be a medical-legal clinical or administrative
document entered into a patient’s record, but may in specific use cases be used in
4
such a manner, provided that accepted policies and procedures in adding such data Since the CCR is a core data set of selected, relevant information, it is not a
to a patient’s record are followed. A personal health record, with the information discharge summary, that is, it does not include all of a patient’s health information
under the control of the patient or their designated represent
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.