Chart Relations CSV API

The purpose of this page is to define data and fields that may be imported into MIE systems (i.e., WebChart, Enterprise Health) using the Chart Relations Import.

Audience

The abstract that follows should be presented to decision-makers or stakeholders interested in a general explanation of the Chart Relations CSV API. Technical details are provided in the remaining sections.

Abstract

The Chart Relations CSV API is used to import various relationships between charts; between patients, users, organizations, or other entities.
chart is a patient’s electronic medical information organized in tabular form. A chart is simply a way to collect different information on one topic, just like a physical patient chart would contain a variety of information on an individual patient. A chart can represent a person, organization, or other entity. Chart-to-chart relationships are used by Enterprise Health systems to connect a patient (employee) to another patient (employee), patient population (employee group), or non-employees.

relation type is used to define the type of connection between two charts. See the Relation Types section  for more information. CSV refers to the type of file and format of data needed to import information into the EH system. API refers to how the data interacts with the  EH system. See the Import Overview  page for a more detailed explanation of terminology.

Specifications

The following detailed specifications are available for the Chart Relations CSV API:

Column Definitions and Specific Coded Values

Definitions for the columns utilized in the specification information below. Commonly used specific coded values appear on the Data Import Standards  page.
High Level: Patient 2 is related to Patient 1 with Relation Type.

  • R = Required
  • O = Optional
NameTypeRequiredComments
PAT1_PARTITIONcharRPartition of first patient
PAT1_MRNintegerRMR Number of first patient
PAT2_PARTITIONcharRPartition of second patient
PAT2_MRNintegerRMR Number of second patient
RELATION_TYPE_IDintegerRRelation type between both patients
Relation Types The following table outlines default relation types.
Relation TypeRelation ID
Self1
Spouse2
Parent3
Grandparent4
Child5
Sibling6
Aunt/Uncle7
Cousin8
Mother9
Father10
Unknown11
Grandchild12
Niece/Nephew13
Provider14
Provider Organization15
Contact16
[[Relation Type ID]]
These ID numbers vary from system to system, and because of this, a help bubble in the import tool describes the available relation types.

Example

In this example we are using William Hart’s chart to establish a sibling relationship with Jane Doe.

Examples of CSV

Adding a Credentialing Contact (RELATION_TYPE_ID: 20) relationship between two patients (MIE 10019 & MIE 10006) MIE 10006 is a Credentialing Contact for MIE 10019.

  
  
  
  
  
PAT1_PARTITION,PAT1_MRN,PAT2_PARTITION,PAT2_MRN,RELATION_TYPE_ID  
MIE,10019,MIE,10006,20  
  
  
  

  
  
  

Example file 1 Adding multiple relations between patients:

  
  
  
  
  
PAT1_PARTITION,PAT1_MRN,PAT2_PARTITION,PAT2_MRN,RELATION_TYPE_ID  
MIE,10019,MIE,10006,20  
MIE,10021,MIE,10020,3  
CCHIT,41205325,MIE,10019,8  
  
  
  

  
  
  

Example file 2

Data Import Master List


Enterprise Health Documentation

Page Created:
Last Updated:
Last Build: Sun, 13 Nov 2022 01:02:21 UTC
WikiGDrive Version: 8799ccfd58b47ed721e42eeadb589071776ed64f