Specialty Eyecare CDA Implementation Guide, published by Dogwood Health Consulting. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/cda-eyecare/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org/cda/us/eyecare/ImplementationGuide/hl7.cda.us.eyecare | Version: 0.1.0 | |||
Draft as of 2024-02-07 | Computable Name: CDAEyecare |
A lot of the focus on interoperability and exchanging of clinical data has been around mainstream EHRs. However, there are a lot of clinical data systems that deal with specialty care, such as eyecare, dental, chiropractic and physiotherapy, to name a few examples. This implementation guide (IG) provides consistent guidance for capturing key eyecare testing information in healthcare information technology (HIT) products.
The audience for this IG includes architects and developers of eyecare HIT systems that exchange patient clinical data. Business analysts and policy managers can also benefit from a basic understanding of the use of CDA templates across multiple implementation use cases.
This guide specifies a template based on the Physical Exam section that defines the eyecare examination codes along with the use of a Eyecare Results Organizer entry. This Eyecare Exam template can be used in any of the existing C-CDA document types that include a Physical Exam section. The Eyecare Exam template restricts the entries to different templates based on the ResultOrganizer which contains different eyecare ResultObservations. The data elements represented in this guide are based on commonly used terms across the industry. Many of these data elements are captured in Eyecare EHRs today.
This publication includes IP covered under the following statements.
There are no Global profiles defined
This IG Contains the following dependencies on other IGs.
Package hl7.fhir.uv.extensions.r5#1.0.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00) |
Package hl7.fhir.uv.extensions.r4#1.0.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00) |
Package hl7.fhir.uv.bulkdata#2.0.0 FHIR based approach for exporting large data sets from a FHIR server to a client application (built Fri, Nov 26, 2021 05:56+1100+11:00) |
Package hl7.fhir.r4.examples#4.0.1 Example resources in the R4 version of the FHIR standard |
Package hl7.fhir.uv.sdc#3.0.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR. |
Package ihe.formatcode.fhir#1.1.0 Implementation Guide for IHE defined FormatCode vocabulary. (built Thu, Feb 24, 2022 16:55-0600-06:00) |
Package hl7.fhir.uv.extensions#5.1.0-ballot1 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Tue, Dec 19, 2023 08:38+1100+11:00) |
Package hl7.fhir.us.core#current The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum conformance requirements for accessing patient data. The Argonaut pilot implementations, ONC 2015 Edition Common Clinical Data Set (CCDS), and ONC U.S. Core Data for Interoperability (USCDI) v1 provided the requirements for this guide. The prior Argonaut search and vocabulary requirements, based on FHIR DSTU2, are updated in this guide to support FHIR Version R4. This guide was used as the basis for further testing and guidance by the Argonaut Project Team to provide additional content and guidance specific to Data Query Access for purpose of ONC Certification testing. These profiles are the foundation for future US Realm FHIR implementation guides. In addition to Argonaut, they are used by DAF-Research, QI-Core, and CIMI. Under the guidance of HL7 and the HL7 US Realm Steering Committee, the content will expand in future versions to meet the needs specific to the US Realm. These requirements were originally developed, balloted, and published in FHIR DSTU2 as part of the Office of the National Coordinator for Health Information Technology (ONC) sponsored Data Access Framework (DAF) project. For more information on how DAF became US Core see the US Core change notes. (built Tue, Dec 19, 2023 16:46+0000+00:00) |