Consolidated Clinical Document Architecture Research Articles

Interoperability in the Wild: Comparison of Real-World Electronic C-CDA Documents from Two Sources.

Although health information exchange (HIE) networks exist in multiple nations, providers still require access multiple sources to obtain medical records. We sought to measure and compare differences in data presence and concordance across regional HIE and EHR vendor-based networks. Using 1,054 randomly selected patients from a large health system in the US, we generated consolidated clinical document architecture (C-CDA) documents from each network. 778 (74%) patients had at least one C-CDA document present from either source. Among these patients, two-thirds had information in only one source. All documents contained demographics, but less than half of patients had data in clinical data domains. Moreover, data across HIE networks were not concordant. Results suggest that HIE networks have different, likely complementary, data available for the same patient, suggesting the need for better integration and deduplication for national HIE efforts.

Enabling health information exchange at a US Poison Control Center.

ObjectiveThe objective of this project was to enable poison control center (PCC) participation in standards-based health information exchange (HIE). Previously, PCC participation was not possible due to software noncompliance with HIE standards, lack of informatics infrastructure, and the need to integrate HIE processes into workflow.Materials and MethodsWe adapted the Health Level Seven Consolidated Clinical Document Architecture (C-CDA) consultation note for the PCC use case. We used rapid prototyping to determine requirements for an HIE dashboard for use by PCCs and developed software called SNOWHITE that enables poison center HIE in tandem with a poisoning information system.ResultsWe successfully implemented the process and software at the PCC and began sending outbound C-CDAs from the Utah PCC on February 15, 2017; we began receiving inbound C-CDAs on October 30, 2018.DiscussionWith the creation of SNOWHITE and initiation of an HIE process for sending outgoing C-CDA consultation notes from the Utah Poison Control Center, we accomplished the first participation of PCCs in standards-based HIE in the US. We faced several challenges that are also likely to be present at PCCs in other states, including the lack of a robust set of patient identifiers to support automated patient identity matching, challenges in emergency department computerized workflow integration, and the need to build HIE software for PCCs.ConclusionAs a multi-disciplinary, multi-organizational team, we successfully developed both a process and the informatics tools necessary to enable PCC participation in standards-based HIE and implemented the process at the Utah PCC.

Data standards for interoperability of care team information to support care coordination of complex pediatric patients

ObjectiveSeamless access to information about the individuals and organizations involved in the care of a specific patient (“care teams”) is crucial to effective and efficient care coordination. This is especially true for vulnerable and complex patient populations such as pediatric patients with special needs. Despite wide adoption of electronic health records (EHR), current EHR systems do not adequately support the visualization and management of care teams within and across health care organizations. Electronic health information exchange has the potential to address this issue. In the present study, we assessed the adequacy of available health information exchange data standards to support the information needs related to care coordination of complex pediatric patients. MethodsWe derived data elements from the information needs of clinicians and parents to support patient care teams; and mapped them to data elements in the Health Level Seven (HL7) Consolidated Clinical Document Architecture (C-CDA) standard and in the HL7 Fast Healthcare Interoperability Resources (FHIR) standard. We also identified additional C-CDA data elements and FHIR resources that include patients’ care team members. ResultsInformation about care team members involved in patient care is generally well-represented in the C-CDA and FHIR specifications. However, there are gaps related to patients’ non-clinical events and care team actions. In addition, there is no single place to find information about care team members; rather, information about practitioners and organizations may be available in several different types of C-CDA data elements and FHIR resources. ConclusionThrough standards-based electronic health information exchange, it appears to be feasible to build patient care team representations irrespective of the location of patient care. In order to gather care team information across disparate systems, exchange of multiple C-CDA documents and/or execution of multiple FHIR queries will be necessary. This approach has the potential to enable comprehensive patient care team views that may help improve care coordination.

Simple Workflow Changes Enable Effective Patient Identity Matching in Poison Control.

Background U.S. poison control centers pose a special case for patient identity matching because they collect only minimal patient identifying information. Methods In early 2017, the Utah Poison Control Center (Utah PCC) initiated participation in regional health information exchange by sending Health Level Seven Consolidated Clinical Document Architecture (C-CDA) documents to the Utah Health Information Network and Intermountain Healthcare. To increase the documentation of patient identifiers by the Utah PCC, we (1) adapted documentation practices to enable more complete and consistent documentation, and (2) implemented staff training to improve collection of identifiers. Results Compared with the same time period in 2016, the Utah PCC showed an increase of 27% ( p < 0.001) in collection of birth date for cases referred to a health care facility, while improvements in the collection of other identifiers ranged from 0 to 8%. Automated patient identity matching was successful for 77% (100 of 130) of the C-CDAs. Conclusion Historical processes and procedures for matching patient identities require adaptation or added functionality to adequately support the PCC use case.

Synthea: An approach, method, and software mechanism for generating synthetic patients and the synthetic electronic health care record.

ObjectiveOur objective is to create a source of synthetic electronic health records that is readily available; suited to industrial, innovation, research, and educational uses; and free of legal, privacy, security, and intellectual property restrictions.Materials and MethodsWe developed Synthea, an open-source software package that simulates the lifespans of synthetic patients, modeling the 10 most frequent reasons for primary care encounters and the 10 chronic conditions with the highest morbidity in the United States.ResultsSynthea adheres to a previously developed conceptual framework, scales via open-source deployment on the Internet, and may be extended with additional disease and treatment modules developed by its user community. One million synthetic patient records are now freely available online, encoded in standard formats (eg, Health Level-7 [HL7] Fast Healthcare Interoperability Resources [FHIR] and Consolidated-Clinical Document Architecture), and accessible through an HL7 FHIR application program interface.DiscussionHealth care lags other industries in information technology, data exchange, and interoperability. The lack of freely distributable health records has long hindered innovation in health care. Approaches and tools are available to inexpensively generate synthetic health records at scale without accidental disclosure risk, lowering current barriers to entry for promising early-stage developments. By engaging a growing community of users, the synthetic data generated will become increasingly comprehensive, detailed, and realistic over time.ConclusionSynthetic patients can be simulated with models of disease progression and corresponding standards of care to produce risk-free realistic synthetic health care records at scale.

Communicating Nursing Care Using the Health Level Seven Consolidated Clinical Document Architecture Release 2 Care Plan.

A care plan provides a patient, family, or community picture and outlines the care to be provided. The Health Level Seven Consolidated Clinical Document Architecture (C-CDA) Release 2 Care Plan Document is used to structure care plan data when sharing the care plan between systems and/or settings. The American Nurses Association has recommended the use of two terminologies, Logical Observation Identifiers Names and Codes (LOINC) for assessments and outcomes and Systematized Nomenclature of Medicine-Clinical Terms (SNOMED CT) for problems, procedures (interventions), outcomes, and observation findings within the C-CDA. This article describes C-CDA, introduces LOINC and SNOMED CT, discusses how the C-CDA Care Plan aligns with the nursing process, and illustrates how nursing care data can be structured and encoded within a C-CDA Care Plan.

Are Meaningful Use Stage 2 certified EHRs ready for interoperability? Findings from the SMART C-CDA Collaborative

Background and objectiveUpgrades to electronic health record (EHR) systems scheduled to be introduced in the USA in 2014 will advance document interoperability between care providers. Specifically, the second stage of the federal incentive program for EHR adoption, known as Meaningful Use, requires use of the Consolidated Clinical Document Architecture (C-CDA) for document exchange. In an effort to examine and improve C-CDA based exchange, the SMART (Substitutable Medical Applications and Reusable Technology) C-CDA Collaborative brought together a group of certified EHR and other health information technology vendors.Materials and methodsWe examined the machine-readable content of collected samples for semantic correctness and consistency. This included parsing with the open-source BlueButton.js tool, testing with a validator used in EHR certification, scoring with an automated open-source tool, and manual inspection. We also conducted group and individual review sessions with participating vendors to understand their interpretation of C-CDA specifications and requirements.ResultsWe contacted 107 health information technology organizations and collected 91 C-CDA sample documents from 21 distinct technologies. Manual and automated document inspection led to 615 observations of errors and data expression variation across represented technologies. Based upon our analysis and vendor discussions, we identified 11 specific areas that represent relevant barriers to the interoperability of C-CDA documents.ConclusionsWe identified errors and permissible heterogeneity in C-CDA documents that will limit semantic interoperability. Our findings also point to several practical opportunities to improve C-CDA document quality and exchange in the coming years.

Data standards to support health information exchange between poison control centers and emergency departments.

Poison control centers (PCCs) routinely collaborate with emergency departments (EDs) to provide care for poison-exposed patients. During this process, a significant amount of information is exchanged between EDs and PCCs via telephone, leading to important inefficiencies and safety vulnerabilities. In the present work, we identified and assessed a set of data standards to enable a standards-based health information exchange process between EDs and PCCs. Based on a reference model for PCC-ED health information exchange, we (1) mapped PCC-ED information exchange events to clinical documents specified in the Health Level Seven (HL7) Consolidated Clinical Document Architecture (C-CDA) Standard, and (2) mapped information types routinely exchanged in PCC-ED telephone conversations to C-CDA sections. Four C-CDA document types were necessary to support the PCC-ED information exchange process: History & Physical Note, Consultation Note, Progress Note, and Discharge Summary. Information types that are commonly exchanged between PCCs and EDs can be reasonably well represented within these C-CDA documents. A standards-based health information exchange process between PCCs and EDs appears to be feasible given a set of clinical data standards that are required for EHR certification in the USA, although the proposed approach still needs to be validated in actual system implementations. Such a process has the potential to improve the safety and efficiency of PCC-ED communication, ultimately resulting in improved patient care outcomes.

Taking advantage of continuity of care documents to populate a research repository.

Clinical data warehouses have accelerated clinical research, but even with available open source tools, there is a high barrier to entry due to the complexity of normalizing and importing data. The Office of the National Coordinator for Health Information Technology's Meaningful Use Incentive Program now requires that electronic health record systems produce standardized consolidated clinical document architecture (C-CDA) documents. Here, we leverage this data source to create a low volume standards based import pipeline for the Informatics for Integrating Biology and the Bedside (i2b2) clinical research platform. We validate this approach by creating a small repository at Partners Healthcare automatically from C-CDA documents. We designed an i2b2 extension to import C-CDAs into i2b2. It is extensible to other sites with variances in C-CDA format without requiring custom code. We also designed new ontology structures for querying the imported data. We implemented our methodology at Partners Healthcare, where we developed an adapter to retrieve C-CDAs from Enterprise Services. Our current implementation supports demographics, encounters, problems, and medications. We imported approximately 17 000 clinical observations on 145 patients into i2b2 in about 24 min. We were able to perform i2b2 cohort finding queries and view patient information through SMART apps on the imported data. This low volume import approach can serve small practices with local access to C-CDAs and will allow patient registries to import patient supplied C-CDAs. These components will soon be available open source on the i2b2 wiki. Our approach will lower barriers to entry in implementing i2b2 where informatics expertise or data access are limited.