Configuration 2 |
|
Applicable to |
|
Configured for use with |
|
Return to EHI Export homepage.
The export zip contains files to help a consumer understand and navigate the folder tree and files contained within.
File |
Description |
README.txt | Contains a description of the export zip file |
SCHEMA.txt | Contains Documentation URL (directs to this page) and Product Version |
JSONTOC.txt | Contains metadata for every data file in the export zip to aid in machine readability
|
The table below outlines what sections will be included within the export zip file for a given MEDITECH product version.
Each section exists as a folder or file within the export zip. This table provides details about what is contained within each section.
Section |
Details |
Patient Data (CSV) Files |
Folder: AANNNNNNNNNN - The folder name represents the internal patient’s medical record identifier.
|
FHIR Resource Bundle |
File: FHIR Resources.json, FHIR Ambulatory Resources.json
|
Clinical Reports/Documents |
The contents in this section will vary by MEDITECH platform. MEDITECH Client/Server Folder: AANNNNNNNNNN_Patient_Name - the folder name represents the account number concatenated with the patient name
MEDITECH MAGIC
MEDITECH MAGIC Ambulatory Folder: AmbDocs
MEDITECH MPM 6.08 Ambulatory Folder: AANNNNNNNNNN_Patient_Name - the folder name represents the account number concatenated with the patient name. Folder: Imaging and Phys Doc
|
Provider and Patient Messages |
The contents in this section will vary by MEDITECH platform MEDITECH Client/Server
MEDITECH MAGIC
|
Financial Reports |
File: FinancialEHI.txt
|
Structured Clinical Documents |
Folder: CCDA
|
External Documents/Images |
The contents in this section will vary by MEDITECH platform MEDITECH Client/Server Ambulatory and MPM 6.08 Ambulatory Folder: AmbScans
MEDITECH MAGIC Ambulatory Folder: AmbScans
|
Point of Contact Scanned Documents |
Folder: MPM POC Scans
|
The ndjson file contains an array of file metadata (FHIR Document Reference resources) for all of the patient data files contained within the export zip file. The pseudo-JSON below explains what each field represents.
{
"resourceType":"DocumentReference",
"id": <<Identifier of this DocumentReference>>,
"meta": {
"id": <<Identifier of this metadata>>,
"versionId": <<Identifier of this version>>,
"lastUpdated": <<When this was last updated>>,
"source": <<Where the resource came from>>,
"profile": [
"http://fhir.org/argonaut/ehi-api/StructureDefinition/ehi-document-reference"
],
"tag": [
{
"code": "ehi-export",
"display": "generated as part of an ehi-export request"
}
]
},
"implicitRules": <<A set of rules under which this content was created>>,
"language": <<Language of the resource content>>,
"status": "current",
"docStatus": <<Status options - preliminary | final | amended | entered-in-error>>,
"type": <<CodeableConcept indicating kind of document>>,
"subject": {
"reference": <<Patient Reference, resource is available in the US Core FHIR Resources.json>>
},
"date": <<Date the file was created>>,
"description": <<File description>>,
"content": [
{
"attachment": {
"id": <<Identifier of this attachment>>,
"contentType": <<File type>>,
"url": <<Pathway to the location of the file>>,
"size": <<File size>>,
"title": <<Title>>,
"creation": <<Date the file was created>>
}
}
],
"context": {
"id": <<Identifier of this context>>,
"encounter": [
{
"reference": <<Encounter Reference, resource is available in the US Core FHIR Resources.json>>
}
],
"period": {
"start": <<Beginning of the context period>>,
"end": <<End of the context period>>
}
}
}