• No results found

i2itracks Common Interface EMR Record Specification (Version 1.4)

N/A
N/A
Protected

Academic year: 2021

Share "i2itracks Common Interface EMR Record Specification (Version 1.4)"

Copied!
6
0
0

Loading.... (view fulltext now)

Full text

(1)

i2iTracks Common Interface

EMR Record Specification (Version 1.4)

Overview

This document describes the records that i2iTracks needs to receive from the EMR system

that it is interfacing with. These records must be contained in an ASCII file in which fields

are delimited by the “|” character and records are delimited by CR / LF.

Initial and Update Files

Periodically, the external software must update i2iTracks with any relevant data changes

that have occurred since the last update (or initial export). The frequency of these updates

varies based on the needs of the customer but typically ranges from once per 10 minutes to

once per day. Each update consists of a single file that:

1. Will be placed by the external software in a pre-determined folder.

2. Must have an extension of TMP while it is being placed in the pre-determined folder.

3. Must be renamed by the external software after it has been placed in the

pre-determined folder. The new name must be based on the file’s creation date / time

and must be of format YYYYMMDDHHMMSS and have an extension of UPD.

Example file name: 20040213082300.UPD

4. Will contain one of the records described in this document for each relevant data

change that has occurred since the last update.

5. Will be deleted by i2iTracks after it has been processed by i2iTracks.

Patient Allergy Record

A record of this type is required for each of the patient’s allergies.

Index Field Type Max Size Details

1 RecordType Char 20 The record type (always PATALLERGY)

2 RecordAction Char 1 The action that was performed on the record (A = Add, E = Edit, D = Delete)

3 ID Char 50 The value that uniquely identifies this record. 4 PatientID Char 50 The ID of the patient (from the Patient Record). 5 AllergyID Char 50 The ID of the allergy (from the Allergy Record).

(2)

6 AllergyName Char 255 The name of the allergy 7 AllergyType Char 2 DA = Drug Allergy

FA = Food Allergy OA = Other Allergy

8 ReactionDesc Char 255 Short, textual description of the specific allergy reaction (convulsions, sneeze, rash, etc.)

9 IdentifiedDate Date 10 The date on which the allergy was identified (YYYY-MM-DD)

10 IdentifiedTime Time 8 The time at which the allergy was identified (HH:MM:SS)

11 Status Char 1 A = Active

N = Not Active

12 StatusDate Date 10 The effective date of the status (YYYY-MM-DD) 13 StatusTime Time 8 The effective time of the status (HH:MM:SS) Example Record:

PATALLERGY|A|1234|232323|55|Peanuts|FA|Rash|2006-01-01|8:00:00|A|2009-01-01|14:00:00

Patient Problem Record

A record of this type is required for each of the patient’s problems.

Index Field Type Max Size Details

1 RecordType Char 20 The record type (always PATPROBLEM)

2 RecordAction Char 1 The action that was performed on the record (A = Add, E = Edit, D = Delete)

3 ID Char 50 The value that uniquely identifies this record. 4 PatientID Char 50 The ID of the patient (from the Patient Record). 5 ProblemID Char 50 The ID of the problem (from the Problem Record). 6 ProblemName Char 255 The name of the problem

7 ProblemICD9Code Char 20 The ICD9 code that represents the problem (if available)

8 IdentifiedDate Date 10 The date on which the problem was identified (YYYY-MM-DD)

9 IdentifiedTime Time 8 The time at which the problem was identified (HH:MM:SS)

10 OnsetDate Date 10 The date on which the problem began (YYYY-MM-DD)

11 OnsetTime Time 8 The time at which the problem began (HH:MM:SS)

12 Status Char 1 A = Active

N = Not Active R = Resolved

13 StatusDate Date 10 The effective date of the status (YYYY-MM-DD) 14 StatusTime Time 8 The effective time of the status (HH:MM:SS)

Example Record:

PATPROBLEM|A|2345|232323|78|Hypertension|401.9|2002-06-01|8:00:00|1995-1-1||A|2009-02-01|9:00:00

(3)

Patient Vital Record

A record of this type is required for each of the patient’s vitals.

Index Field Type Max Size Details

1 RecordType Char 20 The record type (always PATVITAL)

2 RecordAction Char 1 The action that was performed on the record (A = Add, E = Edit, D = Delete)

3 ID Char 50 The value that uniquely identifies this record. 4 PatientID Char 50 The ID of the patient (from the Patient Record). 5 TypeID Char 50 The ID of the vital type. Must be one of the

following:

BPDIA = Diastolic BP (First BP Taken) BPSYS = Systolic BP (First BP Taken) BPDIA2 = Diastolic BP (Second BP Taken)

BPSYS2 = Systolic BP (Second BP Taken) BPDIA3 = Diastolic BP (Third BP Taken)

BPSYS3 = Systolic BP ((Third BP Taken) HEIGHT = Height (Inches)

PAINSCORE = Pain Score PULSE = Pulse

RESP = Respirations TEMP = Temperature (F) WEIGHT = Weight (lbs) PHQ = PHQ Value 6 NumValue Decimal 9 (2 decimals) The numeric value for the vital

7 ObservationDate Date 10 The date on which the value was observed (YYYY-MM-DD)

8 ObservationTime Time 8 The time at which the value was observed (HH:MM:SS)

9 GroupID Char 50 Identifies the group of vitals that were taken at the specified date / time.

Example Record:

(4)

Patient Event Record

The Patient Event Record is used to capture data that does not fall into the standard EHR

data types such as Medications, Vitals, Problem List etc. This data type is used to capture

data that may or may not be structured data. This data type could be used to capture

Meaningful Use: Smoking Status, Cessation, Drug and Alcohol Dependency etc. One

record will be sent for each patient status. A Patient Event Record could change over time;

for example a patient may have 1 record when the patient is a smoker, and if that patient

quits smoking a second record would be sent with a different ID, signifying the patient quit

smoking.

Index Field Type Max Size Details

1 RecordType Char 20 The record type (always PATEVENT)

2 RecordAction Char 1 The action that was performed on the record (A = Add, E = Edit, D = Delete)

3 ID Char 100 The value that uniquely identifies this record. 4 SourceID Char 50 The source ID of the record Example: EHR Name 5 PatientID Char 50 The ID of the patient (from the Patient Record). 6 EventDate Date 10 The date on which the event occurred

(YYYY-MM-DD)

7 EventTypeID Char 100 The type of the event (from the Event Type Record) 8 EventValue Char 512 The value of the event

Example Record:

PATEVENT|A|2403345|EHR_SYSTEM|232323|2002-06-01|0102|Received Cessation PATEVENT|A|2403345|EHR_SYSTEM|232323|2002-06-01|0103|10

(5)

Allergy Record (Library for Patient Allergy)

A record of this type is required for each allergy type that can be referred to by the Patient

Allergy record.

Index Field Type Max Size Details

1 RecordType Char 20 The record type (always ALLERGY)

2 RecordAction Char 1 The action that was performed on the record (A = Add, E = Edit, D = Delete)

3 ID Char 50 The value that uniquely identifies this record 4 Name Char 255 The name of the allergy

5 Description Char 255 The description of the allergy 6 AllergyType Char 2 DA = Drug Allergy

FA = Food Allergy OA = Other Allergy Example Record:

ALLERGY|A|55|Peanuts|Peanuts Allergy|FA

Problem Record (Library for Patient Problems)

A record of this type is required for each problem type that can be referred to by the Patient

Problem record.

Index Field Type Max Size Details

1 RecordType Char 20 The record type (always PROBLEM)

2 RecordAction Char 1 The action that was performed on the record (A = Add, E = Edit, D = Delete)

3 ID Char 50 The value that uniquely identifies this record 4 Name Char 255 The name of the problem

5 Description Char 255 The description of the problem

6 ICD9Code Char 20 The ICD9 code that represents the problem (if available)

Example Record:

(6)

Event Type Record (Library for Patient Event Record)

A record of this type is required for each event type that can be referred to by the Patient

Event record. The Event Type is used to create a supporting library for the Patient Events.

This library is created to show a pick list of all possible patient events. One record will be

sent for each unique Event Type.

Index Field Type Max Size Details

1 RecordType Char 20 The record type (always EVENTTYPE)

2 RecordAction Char 1 The action that was performed on the record (A = Add, E = Edit, D = Delete)

3 ID Char 100 The value that uniquely identifies this record 4 SourceID Char 50 The source ID of the record

5 Name Char 255 The name of the event type

6 CategoryName Char 255 The category name of the event type 7 Description Char 255 The description of the event type Example Record:

EVENTTYPE|A|0102|EHR_SYSTEM|Smoking Cession|Class Smk Cess EVENTTYPE|A|0103|EHR_SYSTEM|How Many Cigs per day|Cigarette Quanity

Event Value Record (Library for Patient Event Record)

A record of this type is required for each event value that can be referred to by the Patient

Event record. The Event Value is used to create a supporting library for the Patient

Events. This library is created to show a pick list of all possible patient event Value Types.

One record will be sent for each unique Value Type.

Index Field Type Max Size Details

1 RecordType Char 20 The record type (always EVENTVALUE)

2 RecordAction Char 1 The action that was performed on the record (A = Add, E = Edit, D = Delete)

3 EventTypeID Char 100 The type of the event (from the Event Type Record) 4 SourceID Char 50 The source ID of the record

5 Value Char 512 The event value

Example Record:

EVENTVALUE|A|0102|EHR_SYSTEM|Received Smoke Cessation EVENTVALUE|A|0103|EHR_SYSTEM|10

References

Related documents

The results are interesting since they uncover the optimum structure of farmers´ agricultural activities (cultivation of agroforestry crops and cassava

Domestic fuel demand in the industrial sector, 1997 fuel demand in the industrial sector, 1997 fuel demand in the industrial sector, 1997 fuel demand in the industrial

For example, our blog post, “The Ultimate Guide to Ecommerce Email Marketing (Online Retailers, this One’s for You…)” is 16,000 words long and uses over 70 pictures to make

The previous chapter outlined issues faced by mature age, career change postgraduate coursework students in their experiences with university studies and being in the

RGX–111 Phase I/II clinical trial: Administration and dose

Pengertian satwa langka diatur dalam Undang-Undang Nomor 5 Tahun 1990 tentang Konservasi Sumber Daya Alam Hayati dan Ekosistemnya yaitu : menurut Pasal 1 angka

 To propose an effective inspection plan for unfired pressure vessels based on Risk Based Inspection for aging

Future work will also focus on investigating the properties of the distance metric on graphs, and the use of those properties in graph lineage, as well as modifying the MsANN