HEALTHJUMP
jumpSTART
Last Updated: 05.11.2018
TABLE OF CONTENTS
OVERVIEW ………..………………………………………………………... 4
VERSIONING ………………………………………………………………………………………………… 5
FLOWCHART …………………….………………………….……….………………….…………………... 5
SUPPORTED SYSTEMS ……….……………..………………….………………….……………... 6
TIMELINES ………………….……………………….……………………….…………………………………. 8
SPECIFICATIONS ……….……………………………………………. 9
TECHNICAL …………………….……………………….……………………………………………………... 9
SECURITY ……………………….……………………….……………………….……………………….…… 9
OUTPUT …………………...………………….……………………….……………………….………………... 10
INSTALLATION ……………………………….…….……………………….……………………………... 10
DATA ELEMENTS ……….……………………………………………. 11
ALLERGY DATA ……….….……………………….……………………….……………………………... 12
APPOINTMENT DATA ……………………….…………………….…….………………….………. 13
ATTRIBUTION DATA ……….…………………….…………………………….……………………... 14
CHARGE DATA ……………………………………….…………………………….……………………... 15
DEMOGRAPHIC DATA …………………….….…………………………….……………………... 17
DIAGNOSIS DATA ………………………………….…………………………….……………………... 19
ENCOUNTER ………………….……………………….…………………………….……………………... 20
IMMUNIZATION DATA ………………………...…………………………….……………………... 21
LAB ORDER DATA …………….………………….…………………………….…………….………... 22
LAB RESULT DATA ……………………………….………………….………….……………….…….. 23
LOCATION DIM ……………………….………………….…………….………….…………….……….. 24
MEDICAL/SURGICAL HISTORY DATA ……………………….………………………... 25
MEDICATION DATA ……………………….………………………………………..……………….... 26
MSSP BENEFICIARY ENROLLMENT PREFERENCE DATA ……….... 28
ORDER FACT DATA ……………………….……………………….………………………..…………. 29
PROCEDURE DATA ……………………….……………………….………………………..………... 31
PROVIDER DATA ……………………….……………………….………………………………..……... 33
QUALITY DATA ……………………….……………………….…………………………….……………... 34
SOCIAL HISTORY DATA ……………………….……………………….…………………………... 35
TRANSACTION DATA ……………………….……………………….……………………………….. 36
VITALS DATA ……………………….……………………….…………………………….………………….. 37
CROSS REFERENCE TABLES …………………………… 39
GENDER CODES .………………….……………………….………………………...………………… 39
MARITAL STATUS ………….……………………………………….……………………….………….. 39
RACE ………….……………………….……………………….……………………….…………………………. 40
ETHNIC GROUP ……………………….……………………….……………………….……………….. 40
TELEPHONE TYPE ……………………….……………………….…………………………………... 40
ALLERGEN TYPE ……………………….……………………….……………………….……………... 41
ALLERGY ACTION TYPE ……………………….……………………….………………………... 41
SMOKING STATUS ……………………….……………………….…………………….……………... 42
EMPLOYMENT CODES ……………………….……………………….…………………………... 42
LIVING ARRANGEMENT CODES ………………………..………………………………... 43
LEVEL OF EDUCATION CODES ……………………….……………………….…………... 43
MEDICATION STATUS DESCRIPTION ……………………….……………………….... 43
ALLERGY/ADVERSE EVENT ……………………….……………………...………………….... 44
Overview
jumpSTART is Datavant Site Connect’s ETL software that organizations use to gain access to health data that resides within health information systems. It extracts, transforms, then securely transmits that data to a series of static pipe delimited files or to Datavant Site Connect’s jumpCONNECT data warehouse.
From demographics and appointments to encounters and charges to allergies and medications to clinical quality data, jumpSTART extracts a broad range of data elements that cover both clinical and financial data.
jumpSTART is easy to deploy and requires very little technical resources. Enter in the database credentials, download jumpSTART and install!
Data extraction happens on a routine basis, which is configurable based on the specific client needs. Standard queries can also be customized to meet specific needs of the client to handle those unique data capture workflows.
VERSIONING
We increment the version number based on the following format. Major.Minor.Patch
Major – Adding or removing a permanent table.
Minor – Adding or removing a column in a table.
Patch – Increasing or decreasing a column size.
As we make changes to our model, we increase the version number based on criteria included within the table above.
The version number does NOT change as this document changes, it only increments as our model changes. We may include more detail to this document without making physical changes to our data model.
FLOWCHART
SUPPORTED SYSTEMS
The following systems are currently supported for data extraction:
System |
Type |
Data In |
Docs |
AdvancedMD |
Cloud |
||
Allscripts PM |
On Premise |
||
Allscripts PRO |
On Premise & Cloud |
X |
|
Allscripts Touchworks |
On Premise & Cloud |
||
Altapoint PM |
On Premise |
||
Amazing Charts |
On Premise |
||
American Medical Software |
On Premise |
||
Aprima PM |
On Premise |
X |
X |
Aprima EHR |
On Premise |
X |
X |
Athena |
Cloud |
X |
X |
Chart Logic EHR |
On Premise |
||
Cerner |
Vendor Feed |
||
eClinicalWorks |
On Premise |
||
eMD’s |
On Premise |
||
Exscribe |
On Premise |
||
GE Centricity – PM |
On Premise |
X |
|
GE Centricity – EHR |
On Premise |
X |
|
gloStream |
On Premise |
||
Greenway Intergy |
On Premise |
||
Greenway Primesuite |
On Premise |
X |
|
IntrinsiQ- Urochart |
On Premise |
||
McKesson InteGreat – EHR |
On Premise |
||
McKesson Medisoft – PM |
On Premise |
X |
|
McKesson Medisoft – EHR |
On Premise |
X |
|
McKesson Practice Partner – EHR |
On Premise |
||
MDRhythmn |
On Premise |
X |
|
MD Suite |
On Premise |
||
MedicsElite |
On Premise |
||
MedInformatix |
On Premise |
||
Meditech |
On Premise |
||
NextGen EHR |
On Premise |
X |
X |
NextGen PM |
On Premise |
X |
X |
PDS Cortex |
On Premise |
||
Phoenix Ortho EHR |
On Premise |
||
Soapware |
On Premise |
||
SystemMedex |
On Premise |
||
SRS Soft |
On Premise |
||
STI |
On Premise |
X |
|
TRAKnet |
On Premise |
||
Varian |
On Premise |
TIMELINES
Implementation timelines vary depending on whether or not the source system is already on our support systems list, which can be found by clicking here. For supported systems, differential data feeds can start as soon as that evening. Obtaining backloads of data is a bit more labor intensive and requires proper planning. See the Output section of this document for more details on backloads of data.[a]
It is our commitment to our clients to deliver data securely, quickly, accurately and affordably. Below is our standard timeline for additions and changes to our current solution.
Version Changes |
Custom Client Queries |
New Interfaces |
30 Days |
30 Days |
90 Days |
[b]
*All times listed above are from the time Datavant Site Connect has obtained proper access to the source systems.
*If a shorter timeline is required, please contact Datavant Site Connect sales to see if something can be done.
Vendor Hosted Cloud Systems[c]
Vendor hosted cloud systems, not on our current supported systems list[d], are the most difficult interfaces to complete due to the fact that a relationship with the vendor needs to be established for data access. Careful consideration should be exercised when providing timelines for these interfaces. Practices can assist Datavant Site Connect with this process by providing contact information for the practice’s account manager or representative.
SPECIFICATIONS
You will find the specifications you need to properly implement jumpSTART here.
Technical
Windows Agent – Applicable for installation on MS Windows Server and Desktop environments (Java based agent available for UNIX/OSX based environments)
Operating System – Windows Server 2008 R2 or Later
Software Requirements – .Net 4.0 or Higher
Recommended Disk Space and RAM – 5 GB Minimum free space and 1 GB RAM
Extraction Intervals – Once daily (times are configurable).
Desktop / Server Permissions – [Installation] privileges, [Run as a service] privileges and Access to the C: drive, which is where the agent gets installed.
Database Permissions – Read Only is required, Read & Write access is required for bidirectional interfaces.
SECURITY
After installation, a secure connection is established from the client database to the Datavant Site Connect data warehouse. For more information on Datavant Site Connect security, please visit: http://www.healthjump.com/security
OUTPUT
The data will be exported out in a pipe delimitated[f] file. A file will be created for each data element.
A historical backload of data can be requested and completed by Datavant Site Connect. The time it takes to complete the backload of data depends on the interface type, API or direct database, amount of data, server storage, memory and processing power. The backload can take as quick as one night up to several weeks depending on the resources. The backload will contain all data for all of the data elements for the selected data.
*Historical backloads of data are not part of the jumpSTART or jumpCONNECT licensing. Please contact Datavant Site Connect sales for pricing options.[g]
Once the historical backload is complete, jumpSTART will then be configured to run on a scheduled basis and will provide a differential output file. The differential file will show all changes made to each data element. For example, if a medication was updated, that medication will show up as a row in the output file.
*The differential data file is based on the data element and will not include a complete patient chart update. If this is something your organization needs, please contact the Datavant Site Connect sales team about our jumpCONNECT product.[h]
*The output file will not indicate what has changed in the data. The receiving party will need to develop a process to determine this.
INSTALLATION
Coming Soon!
DATA ELEMENTS
Overview
The jumpSTART ETL application exports data on a scheduled basis. This schedule can be configured by the practice so it does not interfere with database backups or maintenance jobs. This export will provide all data that was changed from the last time the application ran. It is up to the receiving application to then append this data with the data previously received. If a client requires a historical back load of data, Datavant Site Connect can provide this backload at an additional cost.
The following are considered standard data elements:
Allergies
Appointments
Attribution
Charge
Demographic
Diagnosis
Encounter
Immunization
Lab Order
Lab Result
Medical / Surgical History
Medication
Procedure
Provider
Quality Data
Social History
Transaction
Vitals
* The following are not part of standard extracts but can be provided on an as-needed basis.
Location DIM
MSSP Beneficiary Enrollment Preference Update
Order Fact
ALLERGY DATA
This file contains allergy data for patients.
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Allergy Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
40 |
Y |
Patient ID |
Related to demographic data. patient_id = [i]demographic.patient_id |
VARCHAR |
40 |
Allergy ID |
The ID used by the source system to identify the allergy. |
|
VARCHAR |
40 |
Encounter ID |
The encounter ID from when this allergy was first recorded. |
|
VARCHAR |
2 |
Allergen Type |
Allergen type. See Table 006 for cross-reference. |
|
VARCHAR |
1000 |
Y |
Allergy Description |
Description of allergy. |
VARCHAR |
8 |
Onset Date |
Format: YYYYMMDD |
|
VARCHAR |
8 |
Resolved Date |
Format: YYYYMMDD |
|
VARCHAR |
2000 |
Allergy Severity |
Allergy severity description. |
|
VARCHAR |
2000 |
Reaction Code |
Code describing the reaction based on HITSP C80 Section 2.2.3.4.1 |
|
VARCHAR |
2000 |
Allergy Reaction |
Allergy reaction description. |
|
VARCHAR |
20 |
Product Code |
Code describing the product, HITSP C80 Section(s): 2.2.3.3.9, 2.2.3.3.11, 2.2.3.3.7, 2.2.3.3.8) |
|
VARCHAR |
4000 |
Comment |
Allergy comments from the source system. |
APPOINTMENT DATA
This file contains a list of scheduled appointments.
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Appointment Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
40 |
Y |
Patient ID |
Related to demographic data. patient_id = [j]demographic.patient_id |
VARCHAR |
8 |
Y |
Appointment Date |
Date of appointment. Format: YYYYMMDD |
VARCHAR |
4 |
Y |
Begin Time |
Beginning time of appointment. Format: HHMM |
VARCHAR |
4 |
End Time |
Ending time of appointment. Format: HHMM |
|
VARCHAR |
20 |
Appointment Duration |
Duration in minutes. |
|
VARCHAR |
100 |
Resource |
This could be the doctor’s name, room number, equipment, etc. |
|
VARCHAR |
1000 |
Appointment Reason |
Reason for the appointment. |
|
VARCHAR |
100 |
Appointment Type |
Type of appointment. |
|
VARCHAR |
1000 |
Appointment Detail |
Appointment details. |
|
VARCHAR |
10 |
Provider ID |
Rendering provider’s NPI |
|
VARCHAR |
100 |
Provider Name |
Full name of rendering provider. |
|
VARCHAR |
100 |
Y |
Client Appointment ID |
This is the appointment ID from the source system |
VARCHAR |
1 |
Delete Indicator |
Y or N |
ATTRIBUTION DATA
Enter in a definition of what this is.[k]
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Attribution Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
40 |
Y |
Patient ID |
Related to demographic data. patient_id = [l]demographic.patient_id |
VARCHAR |
40 |
Y |
Source Provider Identifier |
The source system identifier for the provider this patient is attributed to |
VARCHAR |
10 |
Provider NPI |
||
VARCHAR |
50 |
Provider First Name |
||
VARCHAR |
50 |
Provider Last Name |
||
VARCHAR |
100 |
Program Name |
The program, or group, that this patient is part of |
|
VARCHAR |
40 |
Location ID |
The source system identifier for the location this patient is attributed to |
|
VARCHAR |
100 |
Location Name |
||
VARCHAR |
250 |
Comment |
CHARGE DATA
This file contains all charge related data.
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Charge Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
36 |
Client Charge ID |
Charge ID obtained from the source system. |
|
VARCHAR |
50 |
Visit ID |
Visit ID obtained from the source system. |
|
VARCHAR |
36 |
Primary Payer ID |
Related to Charge Fact Data. PrimaryPayerID = [m]ChargeFact.PrimaryPayerID |
|
VARCHAR |
1000 |
Primary Financial Class |
Name of financial class. |
|
VARCHAR |
1000 |
Primary Insurance Payer |
Name of primary insurance payer. |
|
VARCHAR |
36 |
Secondary Payer ID |
Related to Charge Fact Data. SecondaryPayerID = ChargeFact.SecondaryPayerID |
|
VARCHAR |
1000 |
Secondary Financial Class |
Name of financial class. |
|
VARCHAR |
1000 |
Secondary Insurance Payer |
Name of secondary insurance payer. |
|
VARCHAR |
36 |
Tertiary Payer ID |
Related to Charge Fact Data. TertiaryPayerID = ChargeFact.TertiaryPayerID |
|
VARCHAR |
1000 |
Tertiary Financial Class |
Name of tertiary financial class. |
|
VARCHAR |
1000 |
Tertiary Insurance Payer |
Name of the tertiary insurance payer. |
|
VARCHAR |
500 |
CPT Code |
||
VARCHAR |
100 |
CPT Modifiers |
||
VARCHAR |
2 |
Place of Service |
||
VARCHAR |
200 |
Location of Service |
||
VARCHAR |
8 |
Beginning Date of Service |
Format: YYYYMMDD |
|
VARCHAR |
8 |
Ending Date of Service |
Format: YYYYMMDD |
|
VARCHAR |
8 |
Posting Date of Charge |
Format: YYYYMMDD |
|
VARCHAR |
8 |
Entered Date of Charge |
Format: YYYYMMDD |
|
NUMERIC |
19, 2 |
Units |
||
NUMERIC |
19, 2 |
Charge Amount |
||
NUMERIC |
19, 2 |
Allowed Amount |
||
NUMERIC |
19, 2 |
Primary Payer Amount Paid |
||
NUMERIC |
19, 2 |
Secondary Payer Amount Paid |
||
NUMERIC |
19, 2 |
Tertiary Payer Amount Paid |
||
NUMERIC |
19, 2 |
Patient Amount Paid |
||
NUMERIC |
19, 2 |
Primary Payer Adjusted Amount |
||
NUMERIC |
19, 2 |
Secondary Payer Adjusted Amount |
||
NUMERIC |
19, 2 |
Tertiary Payer Adjusted Amount |
||
NUMERIC |
19, 2 |
Patient Adjusted Amount |
||
VARCHAR |
36 |
Rendering Provider ID |
Rendering provider ID obtained from the source system. |
|
VARCHAR |
50 |
Rendering Provider NPI |
||
VARCHAR |
200 |
Rendering Provider Name |
Rendering providers full name. |
DEMOGRAPHIC DATA
This file contains all of the patient’s demographic data.
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Demographic ID |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
40 |
Y |
Client Patient ID (Patient ID) |
Client ID acquired from the source system. |
VARCHAR |
50 |
Y |
First Name |
Patient’s first name. |
VARCHAR |
50 |
Middle Name |
Patient’s middle name. |
|
VARCHAR |
50 |
Y |
Last Name |
Patient’s last name. |
VARCHAR |
30 |
Name Prefix |
Mr. / Mrs. / Ms., etc. |
|
VARCHAR |
30 |
Name Suffix |
MD / LNP / Sr. / Jr., etc. |
|
VARCHAR |
9 |
Social Security Number |
||
VARCHAR |
8 |
Date of Birth |
Format: YYYYMMDD |
|
VARCHAR |
40 |
Patient Other ID |
Source System MRN, Medicare #, etc. |
|
VARCHAR |
40 |
Account ID |
Account ID acquired by the source system. |
|
VARCHAR |
1 |
Gender |
See Table 001 for cross reference. Translated during extraction. [n] |
|
VARCHAR |
6 |
Race |
See Table 003 for cross reference. Translated during extraction. |
|
VARCHAR |
1 |
Ethnic Group |
See Table 004 for cross reference. Translated during extraction. |
|
VARCHAR |
20 |
Primary Language |
Spoken, written or understood primary language, HITSPC80 Section 2.2.1.2.9 value set, http://www.ietf.org/rfc/rfc4646.txt |
|
VARCHAR |
10 |
Primary Phone Number |
Patient’s primary phone number. |
|
VARCHAR |
10 |
Primary Phone Ext |
||
VARCHAR |
1 |
Primary Phone Type |
See Table 005 for cross reference. Translated during extraction. |
|
VARCHAR |
10 |
Secondary Phone Number |
||
VARCHAR |
10 |
Secondary Phone Ext |
||
VARCHAR |
1 |
Secondary Phone Type |
See Table 005 for cross reference. Translated during extraction. |
|
VARCHAR |
100 |
Primary Email |
Patient’s email address. |
|
VARCHAR |
100 |
Secondary Email |
Patient’s secondary email address. |
|
VARCHAR |
1 |
Patient Death Indication |
Y – Patient is deceased / N – Patient is not deceased |
|
VARCHAR |
8 |
Patient Death Date |
Format: YYYYMMDD |
|
VARCHAR |
= .10 |
Address Type Code |
||
VARCHAR |
= .500 |
Address Line 1 |
||
VARCHAR |
500 |
Address Line 2 |
||
VARCHAR |
50 |
City |
||
VARCHAR |
3 |
State |
||
VARCHAR |
20 |
Zip Code |
||
VARCHAR |
20 |
Primary Care Provider ID |
Provider NPI |
|
TIMESTAMP |
Create Timestamp |
Timestamp from source system. |
||
TIMESTAMP |
Modify Timestamp |
Timestamp from source system. |
DIAGNOSIS DATA
This file contains patient diagnosis data.
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Diagnosis Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
40 |
Y |
Patient ID |
Related to demographic data. patient_id = demographic.patient_id [o] |
VARCHAR |
10 |
Y* |
ICD9 Code |
The actual ICD9, 10 or SNOMED code |
VARCHAR |
10 |
Y* |
ICD10 Code |
|
VARCHAR |
10 |
Y* |
LOINC Code |
|
VARCHAR |
20 |
Y* |
SNOMED Code |
|
VARCHAR |
100 |
Diagnosis Description |
Includes diagnoses from the problem list. |
|
VARCHAR |
8 |
Diagnosis Date |
Format: YYYYMMDD |
|
VARCHAR |
8 |
Onset Date |
Format: YYYYMMDD |
|
VARCHAR |
8 |
Resolved Date |
Format: YYYYMMDD |
|
VARCHAR |
100 |
Diagnosis Status Text |
||
VARCHAR |
100 |
Diagnosis Severity Text |
||
VARCHAR |
100 |
Clinician |
||
VARCHAR |
40 |
Encounter Unique ID |
Encounter ID obtained from the source system. |
|
VARCHAR |
2 |
Confidentiality Indicator |
Y or N |
|
VARCHAR |
3 |
Diagnosis Classification |
||
VARCHAR |
2 |
Chronic Indicator |
Y or N |
|
VARCHAR |
40 |
Diagnosis ID |
The ID issued in the source system to uniquely identify the diagnosis |
*Y* – One of these values must be specified.
[p]ENCOUNTER DATA
This file contains patient encounter data.
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Encounter Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
40 |
Y |
Visit ID |
When available, this should be an alternate human readable encounter id (e.g. encounter number (enc_nbr)). When not available, this should be the same as the unique encounter id. |
VARCHAR |
40 |
Y |
Patient ID |
Related to demographic data. patient_id = demographic.patient_id [q] |
VARCHAR |
200 |
Encounter Type |
||
VARCHAR |
8 |
Y |
Encounter Date |
Format: YYYYMMDD |
VARCHAR |
6 |
Encounter Time |
Format: HHMMSS |
|
VARCHAR |
200 |
Location |
||
VARCHAR |
1000 |
Comment |
||
VARCHAR |
40 |
Encounter Unique ID |
Encounter ID from the source system. Related in other tables by client_encounter_ID. |
|
VARCHAR |
1000 |
Reason for Visit – ICD9 |
ICD-9 describing the patient’s stated reason for seeking care. |
|
VARCHAR |
200 |
Clinician |
The name of the rendering provider |
|
VARCHAR |
1000 |
Reason for Visit – ICD10 |
ICD-10 describing the patient’s stated reason for seeking care. |
|
VARCHAR |
1000 |
Reason for Visit – LOINC |
LINC describing the patient’s stated reason for seeking care. |
|
VARCHAR |
1000 |
Reason for Visit – SNOMED |
SNOMED describing the patient’s stated reason for seeking care. |
|
VARCHAR |
100 |
Member / Subscriber ID |
Identifier assigned to patient by health plan. |
|
VARCHAR |
100 |
Status |
Ex. Filed, Pushed, Signed “Y” = Locked; “N” = Not Locked |
IMMUNIZATION DATA
This data contains patient immunization data.
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Immunization Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
40 |
Y |
Patient ID |
Related to demographic data. patient_id = demographic.patient_id [r] |
VARCHAR |
8 |
Y |
Service Date |
Format: YYYYMMDD (Administration Date) |
VARCHAR |
8 |
Service Time |
Format: HH:MM:SS |
|
VARCHAR |
10 |
CPT Code |
||
VARCHAR |
10 |
Y |
CVX Code |
Must have CVX or RxNorm. Cannot use CPT, SNOMED or LOINC. |
VARCHAR |
250 |
Y |
Immunization Description |
|
VARCHAR |
50 |
Immunization Does |
||
VARCHAR |
50 |
Immunization Units |
Describes the dose, ex. mg |
|
VARCHAR |
10 |
Route Code |
||
VARCHAR |
250 |
Route Description |
Ex. Oral / Intramuscular |
|
VARCHAR |
10 |
Performing Clinician NPI |
NPI of the provider that administered the immunization (NPI) |
|
VARCHAR |
100 |
Performing Clinician |
The name of the provider that administered the immunization |
|
VARCHAR |
20 |
Lot Number |
The manufacturer’s lot number for the product administered |
|
VARCHAR |
40 |
Encounter Unique ID |
Identifies the encounter during which this was performed |
|
VARCHAR |
10 |
LOINC Code |
||
VARCHAR |
20 |
SNOMEDCode |
||
VARCHAR |
20 |
Exception Reason Code |
Coded exception reason for not administering the immunization (patient refusal, not available), SNOMED |
|
VARCHAR |
40 |
Immunization ID |
Immunization ID from the client’s source system |
LAB ORDER DATA
This data contains lab orders.
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Lab Order Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
40 |
Y |
Patient ID |
Related to demographic data. patient_id = demographic.patient_id [s] |
VARCHAR |
50 |
Y |
Order Number |
Unique ID for this lab order obtained from the source system. |
VARCHAR |
50 |
Y |
Service Code |
|
VARCHAR |
1000 |
Service Description |
||
VARCHAR |
10 |
Ordering Provider ID |
NPI |
|
VARCHAR |
100 |
Ordering Provider Name |
||
VARCHAR |
50 |
Service Coding System Name |
||
VARCHAR |
40 |
Encounter Unique ID |
Unique encounter ID obtained from the source system. |
|
VARCHAR |
10 |
Order Date |
Format: YYYYMMDD |
LAB RESULT DATA
This data contains lab result data.
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Lab Result Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
40 |
Y |
Patient ID |
Related to demographic data. patient_id = demographic.patient_id [t] |
VARCHAR |
50 |
Y |
Order Number |
Unique ID for this lab order obtained from the source system. |
VARCHAR |
8 |
Observation Date |
Format: YYYYMMDD |
|
VARCHAR |
8 |
Observation Time |
HH:MM:SS |
|
VARCHAR |
50 |
Y |
Observation Code |
|
VARCHAR |
50 |
Y |
Observation Value |
|
VARCHAR |
50 |
Observation Units |
||
VARCHAR |
50 |
Reference Range |
The upper and lower bounds that define a normal value |
|
VARCHAR |
5 |
Abnormal Indicator Flag |
Abnormal Flat returned from lab (ex H, L, HH, LL, ABN) |
|
VARCHAR |
1000 |
Result Comment |
||
VARCHAR |
50 |
Observation Coding System |
Ex. “LOINC” |
|
VARCHAR |
250 |
Observation Description |
||
VARCHAR |
50 |
Status |
Whether or not the lab result was reviewed by the provider |
LOCATION DIM DATA
This data contains the location DIM data.
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Location Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
50 |
Y |
Location ID |
Location ID obtained from the source system |
VARCHAR |
500 |
Y |
Location Name |
|
VARCHAR |
500 |
Address Line 1 |
Location address line 1. |
|
VARCHAR |
500 |
Address Line 2 |
Location address line 2. |
|
VARCHAR |
100 |
City |
Location city. |
|
VARCHAR |
100 |
State |
Location state. |
|
VARCHAR |
50 |
Zip |
Location zip. |
|
TIMESTAMP |
Y |
Create Timestamp |
Create timestamp acquired from the source system. |
|
TIMESTAMP |
Y |
Modify Timestamp |
Modify timestamp acquired from the source system |
*Not part of standard extracts but can be provided on an as-needed basis.
[u]MEDICAL / SURGICAL HISTORY DATA
This data contains patient’s medical / surgical historical data.
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Med / Surg Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
40 |
Y |
Patient ID |
Related to demographic data. patient_id = [v]demographic.patient_id |
VARCHAR |
8 |
Med/Surg History Date |
Format: YYYYMMDD |
|
VARCHAR |
20 |
Med/Surg History Code |
Type of medical/surgical history observation. (SNOMED, ICD9 or ICD10) |
|
VARCHAR |
1000 |
Med/Surg History Description |
Value describing the medical/surgical history. (CABG, AMI, Colectomy, etc.) |
|
VARCHAR |
1000 |
Med/Surg History Comments |
MEDICATION DATA
This data contains patient medication data.
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Medication Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
40 |
Y |
Patient ID |
Related to demographic data. patient_id = demographic.patient_id [w] |
VARCHAR |
40 |
Y* |
Medication ID – NDC |
|
VARCHAR |
40 |
Y* |
Medication ID – RxNorm |
|
VARCHAR |
40 |
Y* |
Medication ID – Other |
|
VARCHAR |
10 |
Medication Type |
Prescription or OTC HITSP C80 Section 2.2.3.3.5 |
|
VARCHAR |
100 |
Y |
Medication Name |
|
VARCHAR |
60 |
Medication Dose |
Use HITSP C80 Section 2.2.6.6 value set |
|
VARCHAR |
100 |
Medication Form |
Use HITSP C80 Section 2.2.3.3 value set |
|
VARCHAR |
100 |
Medication Route |
How the medication is to be taken. (Intramuscular, Oral, Etc.) |
|
VARCHAR |
30 |
Medication SIGCode |
||
VARCHAR |
1000 |
Medication SIG |
The medication instructions. |
|
VARCHAR |
50 |
Duration |
Length of time medication should be continued. |
|
VARCHAR |
50 |
Frequency |
How often the medication is to be administered. |
|
VARCHAR |
10 |
Y |
Start Date |
Date medication was dispensed. Format: YYYYMMDD |
VARCHAR |
10 |
Stop Date |
Format: YYYYMMDD |
|
VARCHAR |
1000 |
Comment |
||
VARCHAR |
10 |
Quantity |
How much of the medication is prescribed per refill. |
|
VARCHAR |
3 |
Refills |
The number of refills remaining / allowed for the medication. |
|
VARCHAR |
50 |
Fill Status |
completed, never, dispensed, etc. |
|
CHAR |
1 |
Sample Indicator |
Y = this prescription is a sample, N = this prescription is not a sample |
|
CHAR |
1 |
Generic Allowed Indicator |
Y = generic version may be dispensed, N = generic version is not allowed |
|
VARCHAR |
20 |
Brand Name Code |
HITSP C80 Section 2.2.3.3.7, 2.2.3.3.10 |
|
VARCHAR |
10 |
Prescribed By NPI |
The NPI of the provider that prescribed the medication. |
|
VARCHAR |
15 |
Status Description |
Active, Inactive, etc. |
|
VARCHAR |
40 |
Encounter Unique ID |
Identifies the encounter during which this medication was prescribed. |
*Y* – One of these values must be specified.
[x]MSSP BENEFICIARY ENROLLMENT PREFERENCE DATA
Enter in a description of this data.[y]
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
MSSP Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
12 |
Y |
HICNO |
CMS Patient Identification (Health Insurance Claim Number) |
VARCHAR |
8 |
Mail Date |
Format: YYYYMMDD |
|
VARCHAR |
8 |
USPS Returned Mail Indicator |
Y or N |
|
VARCHAR |
8 |
Response Date |
Format: YYYYMMDD |
|
CHAR |
1 |
Data Sharing Preference |
Y or N |
|
CHAR |
1 |
Data Sharing Decision Mechanism |
N, O or R (N = None, O = Office, R = Response by Mail) |
|
CHAR |
1 |
Substance Abuse Data Share Preference Indicator |
Y or N |
|
CHAR |
1 |
Substance Abuse Data Share Decision Mechanism |
N, O, R (N = None, O = Office, R = Response by Mail) |
|
VARCHAR |
100 |
Claims Received |
*Not part of standard extracts but can be provided on an as-needed basis.
[z]ORDER FACT DATA
Enter description of this data.[aa]
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Order Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
50 |
Y |
Order ID |
Charge ID obtained from the source system. |
VARCHAR |
50 |
Y |
Encounter ID |
Encounter ID obtained from the source system. |
VARCHAR |
50 |
Y |
Patient ID |
Related to demographic data. patient_id = demographic.patient_id [ab] |
VARCHAR |
50 |
Y |
MRN |
Patient medical record number obtained from the source system. |
VARCHAR |
250 |
Y |
Patient First Name |
|
VARCHAR |
250 |
Patient Middle Name |
||
VARCHAR |
250 |
Y |
Patient Last Name |
|
VARCHAR |
20 |
Y |
Patient Date of Birth |
Format: YYYYMMDD |
VARCHAR |
250 |
Patient Address 1 |
||
VARCHAR |
250 |
Patient Address 2 |
||
VARCHAR |
50 |
Patient City |
||
VARCHAR |
10 |
Patient State |
PA, DE, NJ, Etc. |
|
VARCHAR |
20 |
Patient Zip |
Format: ######### |
|
VARCHAR |
50 |
Y |
CPT Code |
|
VARCHAR |
1000 |
CPTDescription[ac] |
||
VARCHAR |
50 |
Y |
Diagnosis Code |
|
VARCHAR |
1000 |
Diagnosis Description |
||
VARCHAR |
50 |
Side |
The side of the body that the procedure is going to happen on. (left, right, bilateral, etc.) |
|
VARCHAR |
50 |
Site |
Body part undergoing the procedure. (shoulder, elbow, ankle, etc.) |
|
VARCHAR |
100 |
Status |
scheduled, ordered, etc. |
|
VARCHAR |
1 |
Delete Indicator |
Y = Deleted, N = Not Deleted |
|
VARCHAR |
250 |
Location Name |
Where procedure was ordered. |
|
VARCHAR |
16k |
Notes |
Notes pertaining to the order. (rendering provider name, etc.) |
|
TIMESTAMP |
Order Date |
Order date obtained from the source system. |
||
VARCHAR |
250 |
Ordering Provider |
Name of the provider placing the order. |
|
VARCHAR |
50 |
Ordering Provider ID |
ID used to identify the provider in the system |
|
TIMESTAMP |
Scheduled Date |
When the order was scheduled to happen from the source system. |
||
TIMESTAMP |
Y |
Create Timestamp |
When the order was created in the system. |
|
TIMESTAMP |
Y |
Modify Timestamp |
When the order was last modified in the system. |
|
VARCHAR |
50 |
Order Type |
*Not part of standard extracts but can be provided on an as-needed basis.[ad]
PROCEDURE DATA
Enter in data description here.[ae]
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Procedure Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
40 |
Y |
Patient ID |
Related to demographic data. patient_id = demographic.patient_id |
VARCHAR |
100 |
Y |
CPT4/HCPCS Code |
|
VARCHAR |
1000 |
Procedure Description |
||
VARCHAR |
10 |
Procedure Date |
Format: YYYYMMDD |
|
VARCHAR |
20 |
Units |
||
VARCHAR |
20 |
Modifier Code 1 |
CPT-4 or HCPCS modifier code |
|
VARCHAR |
20 |
Modifier Code 2 |
CPT-4 or HCPCS modifier code |
|
VARCHAR |
20 |
Modifier Code 3 |
CPT-4 or HCPCS modifier code |
|
VARCHAR |
20 |
Modifier Code 4 |
CPT-4 or HCPCS modifier code |
|
VARCHAR |
100 |
Place of Service |
CMS place of service. Needs to be the actual name of the location. |
|
VARCHAR |
200 |
Performed by Clinician |
Must be NPI |
|
VARCHAR |
200 |
Ordered by Clinician |
Must be NPI |
|
VARCHAR |
40 |
Encounter Unique ID |
Identifies the encounter during which this was performed from the source system. |
|
VARCHAR |
20 |
Internal Charge Code |
||
VARCHAR |
20 |
Total Charges |
||
VARCHAR |
20 |
Y* |
LINC Code |
|
VARCHAR |
20 |
Y* |
SNOMEDCode |
|
VARCHAR |
1000 |
Procedure Result |
Any result data associated with the performed procedure such as PHQ9, HCPCS, LOINC, SNOMED (mammogram, colonoscopy, diabetic eye exam results, etc.) |
|
VARCHAR |
10 |
Dx1 Code |
||
VARCHAR |
10 |
Dx2 Code |
||
VARCHAR |
10 |
Dx3 Code |
||
VARCHAR |
10 |
Dx4 Code |
||
VARCHAR |
10 |
Dx5 Code |
||
VARCHAR |
10 |
Dx6 Code |
||
VARCHAR |
10 |
Dx7 Code |
||
VARCHAR |
10 |
Dx8 Code |
*Y* – One of these values must be specified.[af]
PROVIDER DATA
Enter data description here. [ag]
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Allergy Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
40 |
Y |
Source Provider Identifier |
The unique identifier from the source system for this provider record. |
VARCHAR |
10 |
Y |
NPI |
|
VARCHAR |
9 |
Provider SSN |
||
VARCHAR |
25 |
TIN |
The provider tax ID. |
|
VARCHAR |
50 |
Y |
Provider’s first name |
|
VARCHAR |
50 |
Provider’s middle name |
||
VARCHAR |
50 |
Y |
Provider’s last name |
|
VARCHAR |
25 |
Degree |
MD, PA, etc. |
|
VARCHAR |
500 |
Address Line 1 |
||
VARCHAR |
500 |
Address Line 2 |
||
VARCHAR |
50 |
City |
||
VARCHAR |
3 |
State |
||
VARCHAR |
10 |
Zip |
||
VARCHAR |
25 |
Phone 1 |
||
VARCHAR |
100 |
Phone 1 Description |
See Table 005 – Translated during the extraction of data from the source system. [ah] |
|
VARCHAR |
25 |
Phone 2 |
||
VARCHAR |
100 |
Phone 2 Description |
See Table 005 – Translated during the extraction of data from the source system. |
|
VARCHAR |
50 |
Specialty 1 |
||
VARCHAR |
50 |
Specialty 2 |
QUALITY DATA
This file contains clinical quality measure data: BMI, BP, Colonoscopy, Depression Screening, Diabetic Eye Exam, Fall Risk Assessment, HbA1c, Influenza, LVEF, Mammogram, Medication Reconciliation, Pneumo Vaccine, Tobacco Screening.
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Quality Data Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
40 |
Y |
Patient ID |
Related to demographic data. patient_id = demographic.patient_id [ai] |
VARCHAR |
40 |
Y |
Encounter ID |
Related to encounter data. |
VARCHAR |
500 |
Y |
Item Name |
Name of the quality data being captured. |
VARCHAR |
500 |
Value |
The value obtained / recorded for the test / procedure performed. |
|
VARCHAR |
30 |
Y |
Observation Date |
Format: MM/DD/YYYY HH:MM:SS AM/PM |
VARCHAR |
50 |
Code |
Value only exists if it is obtained from the source system. |
|
VARCHAR |
250 |
Code Type |
LOINC, SNOMED, etc. |
|
VARCHAR |
250 |
EMR Section |
HPI, Lab, Etc. This is the module from the EMRsystem where the data is pulled. |
|
VARCHAR |
1 |
Recorded Elsewhere in Extracts |
Y = is recorded elsewhere in the data captured by jumpSTART. |
SOCIAL HISTORY DATA
Enter a description of the data.[aj]
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Social History Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
40 |
Y |
Patient ID |
Related to demographic data. patient_id = [ak]demographic.patient_id |
VARCHAR |
15 |
Smoking Status |
SNOMED smoking indicator code defined by CMS. See Table 008 |
|
VARCHAR |
1 |
Marital Status |
||
VARCHAR |
9 |
Employment Status |
||
VARCHAR |
1 |
Transportation Indicator |
Y = has available transportation, N = does not have transportation available |
|
VARCHAR |
1 |
Living Arrangement |
||
VARCHAR |
1 |
Alcohol User |
Y = Uses alcohol, N = Does not use alcohol, SNOMED219006 (Y), SNOMED 105542008 (N) |
|
VARCHAR |
1 |
Drug User |
Y = Uses drugs, N = Does not use drugs |
|
VARCHAR |
1 |
Caffeine User |
Y = Uses caffeine, N = does not use caffeine, SNOMED67961000119106 (Y) |
|
VARCHAR |
1 |
Sexually Active |
Y = Is sexually active, N = Is not sexually active, SNOMED228453005 (Y), SNOMED 162171002 (N) |
|
VARCHAR |
2 |
Hours of Exercise per Week |
||
VARCHAR |
2 |
Level of Education |
||
VARCHAR |
40 |
First Encounter ID |
The encounter ID from when the social history was first recorded |
TRANSACTION DATA
Enter in a description of the data.[al]
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Transaction Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
36 |
Client Charge ID |
Charge ID obtained from the source system. |
|
VARCHAR |
36 |
Y |
Trans ID |
ID used to identify the transaction in the source system. |
VARCHAR |
40 |
Y |
Visit ID |
|
VARCHAR |
13 |
CPT Code |
||
CHAR |
1 |
Payer |
Expecting: 1, 2, 3 or P (1 = Primary, 2 = Secondary, 3 = Tertiary and P = Patient Paid) |
|
CHAR |
1 |
Type |
Expecting: A, C or R (A = Adjustment, C = Payment, R = Refund) |
|
NUMERIC |
19, 2 |
Amount Paid |
||
NUMERIC |
19, 2 |
Adjusted Amount |
||
VARCHAR |
8 |
Post Date |
Format: YYYYMMDD |
|
VARCHAR |
50 |
Trans Description |
VITALS DATA
This data contains vitals data capture at the time of the patient visit.
TYPE |
LEN |
REQ |
VALUE |
NOTES |
PK |
Y |
Vitals Primary Key |
||
VARCHAR |
100 |
Y |
Client ID |
Datavant Site Connect’s client identifier. |
VARCHAR |
40 |
Y |
Patient ID |
Related to demographic data. patient_id = demographic.patient_id [am] |
VARCHAR |
8 |
Y |
Service Date |
Format: YYYYMMDD |
VARCHAR |
8 |
Service Time |
Format: HH:MM:SS |
|
VARCHAR |
20 |
Height – CM |
Height in centimeters. |
|
VARCHAR |
20 |
Height – IN |
Height in inches. |
|
VARCHAR |
1000 |
Height Comment |
e.g. SNOMED 50373000 |
|
VARCHAR |
20 |
Weight – KG |
Weight in kilograms. |
|
VARCHAR |
20 |
Weight – LBS |
Weight in pounds. |
|
VARCHAR |
1000 |
Weight Comment |
e.g. SNOMED 27113001 |
|
VARCHAR |
20 |
Temperature – C |
Temperature in Celsius. |
|
VARCHAR |
20 |
Temperature – F |
Temperature in Fahrenheit. |
|
VARCHAR |
1000 |
Temperature Comment |
e.g. Temporal, SNOMED 386725007 Body Temp, SNOMED 276885007 Core Temp |
|
VARCHAR |
20 |
Pulse |
||
VARCHAR |
1000 |
Pulse Comment |
Regular, SNOMED 78564009 Pulse Rate |
|
VARCHAR |
20 |
Respiration |
||
VARCHAR |
1000 |
Respiration Comment |
Unlabored, SNOMED 86290005 Respiratory Rate |
|
VARCHAR |
20 |
Blood Pressure – Systolic |
||
VARCHAR |
20 |
Blood Pressure – Diastolic |
||
VARCHAR |
1000 |
Blood Pressure Comment |
Patient position, cuff location, cuff size, SNOMED271649006 Systolic, SNOMED 271650006 Diastolic |
|
VARCHAR |
20 |
Oxygen Saturation – SpO2 |
||
VARCHAR |
1000 |
Oxygen Saturation – Comment |
SNOWMED 431314004 Peripheral |
|
VARCHAR |
20 |
BMI |
LOINC 39256-5 |
|
VARCHAR |
1000 |
BMI Comment |
Above Normal Range, Below Normal Range, SNOMED238131007 Overweight, SNOMED 248342006 Underweight |
|
VARCHAR |
100 |
Clinician |
The name of the provider that took the vital readings |
|
VARCHAR |
40 |
Encounter Unique ID |
Identifies the encounter during which this was performed obtained by the source system. |
|
VARCHAR |
2000 |
Vitals Comment |
SNOWMED 46680005 Vital Signs |
CROSS REFERENCE TABLES
Below are cross reference tables Datavant Site Connect uses when doing pre or post translations.
GENDER CODES
Gender Codes
Value |
Description |
Comment |
M |
Male |
|
F |
Female |
|
U |
Unknown |
MARITAL STATUS
Marital Status
Value |
Description |
Comment |
A |
Separated |
|
D |
Divorced |
|
M |
Married |
|
S |
Single |
|
W |
Widowed |
|
C |
Common Law |
|
G |
Living Together |
|
P |
Domestic Partner |
|
R |
Registered Domestic Partner |
|
E |
Legally Separated |
|
N |
Annulled |
|
I |
Interlocutory |
|
B |
Unmarried |
|
U |
Unknown |
|
O |
Other |
|
T |
Unreported |
RACE
Race
Value |
Description |
Comment |
1002-5 |
American Indian or Alaska Native |
|
2028-9 |
Asian |
|
2054-5 |
Black or African American |
|
2076-8 |
Native Hawaiian or Other Pacific Islander |
|
2106-3 |
White |
|
2131-1 |
Other Race |
ETHNIC GROUP
Ethnic Group
Value |
Description |
Comment |
H |
Hispanic or Latino |
|
N |
Not Hispanic or Latino |
|
U |
Unknown |
TELEPHONE TYPE
Telephone Type
Value |
Description |
Comment |
U |
Unknown |
|
H |
Home |
|
W |
Work |
|
M |
Mobile |
|
F |
Fax |
|
O |
Other |
ALLERGEN TYPE
Allergen Types
Value |
Description |
Comment |
DA |
Drug Allergy |
|
FA |
Food Allergy |
|
MA |
Miscellaneous Allergy |
|
MC |
Miscellaneous Contraindication |
|
EA |
Environment Allergy |
|
AA |
Animal Allergy |
|
PA |
Plant Allergy |
|
LA |
Pollen Allergy |
ALLERGY ACTION TYPE
Allergy Action Types
Value |
Description |
Comment |
A |
Add / Insert |
|
D |
Delete |
|
U |
Update |
|
X |
No Change |
SMOKING STATUS
Smoking statuses using the SNOMED CT vocabulary.
Value |
Description |
Comment |
449868002 |
Current everyday smoker |
|
428041000124106 |
Current some day smoker |
|
8517006 |
Former Smoker |
|
266919005 |
Never smoker |
|
77176002 |
Smoker, current status unknown |
|
266927001 |
Unknown if ever smoked |
|
428071000124103 |
Heavy tobacco smoker |
|
428061000124105 |
Light tobacco smoker |
EMPLOYMENT CODES
Employment codes using the SNOMED CT vocabulary.
Value |
Description |
Comment |
224372004 |
Volunteer |
|
73760000 |
Homemaker |
|
406156006 |
Employed for Wages |
|
49588008 |
Active Duty Military |
|
65853000 |
Student |
|
73438004 |
Unemployed |
LIVING ARRANGEMENT CODES
Living Arrangement Codes.
Value |
Description |
Comment |
A |
Alone |
|
F |
Family |
|
I |
Institution |
|
R |
Relative |
|
U |
Unknown |
|
S |
Spouse |
|
M |
Friend / Roommate |
LEVEL OF EDUCATION CODES
Level of Education Codes.
Value |
Description |
Comment |
AH |
Attended High School |
|
GE |
GED |
|
CH |
Completed High School |
|
AU |
Attended a University |
|
CU |
Completed Undergraduate Degree |
|
AG |
Attended Graduate School |
|
CG |
Completed Graduate Degree |
MEDICATION STATUS DESCRIPTION
Medication Status Description.
Value |
Description |
Comment |
Active |
||
Completed |
||
Discontinued |
ALLERGY / ADVERSE EVENT
Allergy and adverse events using the recommended code set of HITSP C80 Section 2.2.3.4.2.
Value |
Description |
Comment |
420134006 |
Propensity to adverse reactions (disorder) |
|
418038007 |
Propensity to adverse reactions to substance (disorder) |
|
419511003 |
Propensity to adverse reactions to drug (disorder) |
|
418471000 |
Propensity to adverse reatctions[an] to food (disorder) |
|
419199007 |
Allergy to substance (disorder) |
|
416098002 |
Drugy[ao] allergy (disorder) |
|
414285001 |
Food allergy (disorder) |
|
59037007 |
Drug intolerance (disorder) |
|
235719002 |
Food intolerance (disorder) |
HEALTHJUMP TECHSPEC
Date: 05.09.2018 System: jumpSTART Page:
[a]Need to update links.
[b]Need to center these blue footnotes, and make smaller.
[c]On the site this is a mini header and dark green - if I change it to that color or font it labels it in the Outline and it does not need to be.
[d]Need to update link.
[e]Need to update links.
[f]Misspelling?
[g]Need to center these blue footnotes, and make smaller.
[h]Need to center these blue footnotes, and make smaller.
[i]Need to update links.
[j]Need to update link.
[k]Need to enter a description.
[l]Need to update link.
[m]Need to update links.
[n]Need to update links.
[o]Need to update link.
[p]Need to center these blue footnotes, and make smaller.
[q]Need to update link.
[r]Need to update link.
[s]Need to update link.
[t]Need to update link.
[u]Need to center these blue footnotes, and make smaller.
[v]Need to update link.
[w]Need to update link.
[x]Need to center these blue footnotes, and make smaller.
[y]Need to enter a description
[z]Need to center these blue footnotes, and make smaller.
[aa]Need to enter description
[ab]Need to update link.
[ac]Should there be a space between CPT and Description?
[ad]Need to center these blue footnotes, and make smaller.
[ae]Need to enter a description.
[af]Need to center these blue footnotes, and make smaller.
[ag]Need to enter a description.
[ah]Need to update links.
[ai]Need to update links.
[aj]Need to enter a description.
[ak]Need to update links.
[al]Need to enter a description.
[am]Need to update links.
[an]Mispelling?
[ao]Misspelling?