Purpose
Migrating Electronic Health Information (EHI) from one certified Electronic Health Record (EHR) system to another, whether a single patient or all patients in the platform, represents great risks to project timelines and patient continuity of care. TechCare® supports organizations, users, and patients alike via 170.315 (b)(10) Electronic Health Information Export with the formats, definitions, and processes set forth in this publicly accessible hyperlink .
Documentation, Format Types and Processes
Recognizing the scope and variations in technology not only across different EHR platforms but also among old and new versions of the same EHR, TechCare®’s EHI output for a single patient or all patients is built upon the combination of three (3) of the most universally accepted and simple documentation and file types: 1) .CSV files, 2) Consolidated-Clinical Document Architecture (C-CDA), and 3) PDF (without restrictions). Each are electronic and in a computable format .
The publicly accessible link to this document and its data dictionaries and export format explanations is included with every output.
The export of TechCare®’s EHI data for a single patient can be done at any time the user chooses without Developer assistance. In a timely fashion (minutes or seconds), the logged in user is notified via a message that all the EHI for their single patient is ready for download:
Only a specific set of users have the ability to create the export file, limited to those with administrative rights.
The export of all EHI for all patients in TechCare® outputs the same data file types, only for all patients via its side-loaded export engine that scalably produces the files continuously for all patients.
Assumptions
Unless otherwise specified, INMATES.ID is the demographic database table’s unique and primary key and it is the foundational link in all other database tables that associates each discreet data element set (e.g. IMMUNIZATIONS) to a specific patient in both one to one and one to many relationships. All of the structure and syntax information of the EHI data is included below in the Data Dictionary.
All categories of EHI in the data dictionary are output as .CSV files with header row and named appropriately.
Images and scanned paper records are automatically processed into the universally accepted and human readable PDF format and their computability is limited to positive patient identification by their nature.
No 3rd party software(s) is required for the described functionality.
This page is updated regularly as needed. Current as of 11/28/2023.
Data Dictionary
Demographics
Medications
Allergies
Problem List
Flags
Appointments
>
Diet Orders
Lab Orders
>
Treatment Orders
Specialty Consult Orders
Admission Orders
Immunizations
C-CDA
In order to ensure all EHI for both single patient and full roster exports, each individual patient’s C-CDA document is also provided. The following data types are available from within the C-CDA document exclusively, since they are EHI, but due to their format and archival structure, they remain the most broadly useful and importable into other certified EHRs via existing C-CDA functionality:
Medication Administrations
Vitals Signs
Diagnostic Results
Treatment Plans (Plan of Care)
Social History
Assessments
Functional Status
Mental Status
PDF - Images and Scanned Paper Records
In order to ensure all EHI for both single patient and full roster exports are included, each individual patient’s entire encounter history documentation is also provided. Any and all images (eg wound pictures) and scanned paper records (eg faxed progress notes from outside clinics) are automatically processed into the universally accepted and human readable PDF format.
Given their source and nature, there is no discreet data elements to ingest. However, their importance to continuity of care across health systems and EHR platforms cannot be overstated. They are provided with a naming convention that ensures positive patient identification and frictionless import or reference regardless of their final destination or platform.