Import File Specifications
 
This topic describes the file format required to import data into MCMP-PAT.  There are two types of dataset that may be imported into MCMP-PAT: patient and patient visits.   The columns/fields and their valid values are listed in separate tables below.

Column Values
These are the possible values of all columns of type INTEGER with the exception of Gender and HFPCInvalid and columns that represent blood pressure and lab values (DMBPSystolic, DMBPDiastolic, DMLDLCValue & CADLDLCValue).  Refer to the "Algorithms for Measures Calculations-EHRS" document for the codes used in determining the value to be assigned to a measure element.  This document is contained in the "Quality Measurement and Reporting Specifications Report" document.  A PDF version of this document is available in the MCMP forum Arrow right..

Value Description
0 No - No Reason Doc.
1 Yes
2 Claim Not Found/Med. Rec. Not Found *
3 No - Med. Reasons
4 No - Pt. Reasons
5 No - Sys. Reasons

* In version 2.x of MCMP-PAT, the text was Skip/Skip - Rec. Not Found. Claim Not Found is an item under claims-based elements and Med. Rec. Not Found is an item under the confirmation elements.

Naming Convention
All elements under a topic begin with the acronym of that topic.  For example, all elements under diabetes mellitus are prefixed with "DM".  If an element is used in two topics, it is prefixed with the acronyms of both topics.

Table Description
This is the description of the columns under the patient and visit tables.
Column Description
Column Name Describes the name of the column.
Data Type Describes that type of data that is acceptable for the column.
Max. Chars Determines the maximum number of characters for the column. Used only for columns of type TEXT.
Min. Value Determines the minimum value for columns of type INTEGER and DECIMAL.
Max Value Determines the maximum value for columns of type INTEGER and DECIMAL.
Valid Values List of values that are acceptable for the column. Used only for columns of type INTEGER.  For columns of type DATE, valid values depend on the performance year.  See the date ranges of performance years for more information.
Unknown Value Indicates the valid digit that represents an unknown value for the column.
Parent Column Name & Value Indicates the name and value of the parent column.  For example, if DMHbA1cTest is 1/"Yes" then DMHbA1cDate and DMHbA1cValue must be provided.
Comments Notes and additional information.

Patient Dataset
Notes
  • The column names in this table are indented to show the parent-child relationships or dependencies of the columns.
  • Beginning in version 2.0, the field ClinicNumber will no longer be a valid column.

Column Name Data Type Max Chars Min Value Max Value Valid Values Unknown Value Parent Column
Name & Value		 Comments
Demographics
PatIDHIC TEXT 30
  • REQUIRED.
  • Holds the primary key value.
  • To be imported, the value must exist in the target database. Non-existing values will be ignored.
  • Each value in the row must be unique.
LastName TEXT 20
FirstName TEXT 20
DateOfBirth DATE Must be in MM/DD/YYYY format. "X" is not allowed.
Gender INTEGER 1, 2, 3 1 = Male
2 = Female
3 = Unknown
MRNumber TEXT 25
PatIDOther TEXT 20
ProviderNumber TEXT 30 If supplied, the provider number must exist in the list of providers.  See section on provider number below for more information.
Comments TEXT 250
Diabetes
DMConfirmed INTEGER 0, 1, 2, 3 If 0, 2 or 3, no need to set the values of DM columns.  This is the parent column of all columns under the DM topic.
DMHbA1cTest INTEGER 0, 1
DMHbA1cDate DATE DMHbA1cTest=1 Must be in MM/DD/YYYY format.
DMHbA1cValue DECIMAL 0 25 0 DMHbA1cTest=1
DMBPMeasure INTEGER 0, 1
DMBPDate DATE DMBPMeasure=1 Must be in MM/DD/YYYY format.
DMBPSystolic INTEGER 0 350 0 DMBPMeasure=1
DMBPDiastolic INTEGER 0 200 0 DMBPMeasure=1
DMLDLCTest INTEGER 0, 1
DMLDLCDate DATE DMLDLCTest=1 Must be in MM/DD/YYYY format.
DMLDLCValue INTEGER 0 500 0 DMLDLCTest=1
DMNephropathy INTEGER 0, 1, 2
DMEyeExam INTEGER 0, 1, 2
DMFootExam INTEGER 0, 1, 3
Heart Failure
HFConfirmed INTEGER 0, 1, 2 If 0 or 2, no need to set the values of HF columns.
HFLVFResult INTEGER 0, 1
HFHospital INTEGER 0, 1, 2
HFLVFYear INTEGER 0, 1, 3, 4 HFHospital=1
HFPtEducation INTEGER 0, 1
HFCADLVSD INTEGER 0, 1 Used under HF and CAD topics but must appear only once per tab-delimited file.  See the section HFCADLVSD Field below for more information.
HFBBlockDrug INTEGER 0, 1, 3, 4, 5 HFCADLVSD=1
HFACEARBDrug INTEGER 0, 1, 3, 4, 5 HFCADLVSD=1
HFAFib INTEGER 0, 1
HFWarfDrug INTEGER 0, 1, 3, 4, 5 HFAFib=1
Coronary Artery Disease
CADConfirmed INTEGER 0, 1, 2 If 0 or 2, no need to set the values of CAD columns.
CADAntiplatDrug INTEGER 0, 1, 3, 4, 5
CADLDLCDrug INTEGER 0, 1, 3, 4, 5
CADMI INTEGER 0, 1
CADBBlockDrug INTEGER 0, 1, 3, 4, 5 CADMI=1
CADLipid INTEGER 0, 1, 2
CADLDLCTest INTEGER 0, 1
CADLDLCDate DATE CADLDLCTest=1 Must be in MM/DD/YYYY format.
CADLDLCValue INTEGER 0 500 0 CADLDLCTest=1
CADDiabetes INTEGER 0, 1
HFCADLVSD INTEGER 0, 1 Used under HF and CAD topics but must appear only once per tab-delimited file. See  the section HFCADLVSD Field below for more information.
CADACEARBDrug INTEGER 0, 1, 3, 4, 5 CADDiabetes=1
or
HFCADLVSD=1		 This is dependent on CADDiabetes or HFCADLVSD.  Value must be provided if the value of either parent column is 1.
Preventive Care
PCConfirmed INTEGER 0, 1, 2 If 0 or 2, no need to set the values of PC columns.
PCMammogram INTEGER 0, 1, 2, 3
PCFOBTPerform INTEGER 0, 1, 3, 4, 5
PCFluShot INTEGER 0, 1, 3, 4, 5
PCPneumoShot INTEGER 0, 1, 3, 4

Patient Visits Dataset
The table below describes the valid columns for the patient visits dataset.
Column Name Data Type Max. Chars. Valid Values Parent Column
Name & Value		 Comments
PatIDHIC TEXT 30
  • REQUIRED.
  • Holds the primary key value in combination with HFPCVisitDate.
  • To be imported, the value must exist in the target database. Non-existing values will be ignored.
HFPCVisitDate DATE 10 PCConfirmed=1
or
HFConfirmed=1
  • REQUIRED.
  • The combination of PatIDHIC and HFPCVisitDate must be unique for each row in the import file.
  • Valid value depends on performance year (see Import Rules for valid date ranges).
  • Must be in MM/DD/YYYY format.
  • Does not accept "X" to represent an unknown date.
HFWeight INTEGER 0, 1, 3 HFConfirmed=1 Used only under the HF topic
PCBPMeasure INTEGER 0, 1 PCConfirmed=1 Used only under the PC topic
HFPCInvalid INTEGER 0, 1 0 = visit is not invalid
1 = visit is invalid

Default value is 0. May only be set to 1 if the visit record is pre-filled.  Only pre-filled visits may be marked as invalid. User-added visits can't be marked as invalid.

This field is always overwritten even though the user specified not to overwrite 1/"Yes" values during the import process.

Provider Number
NOTE!
For the baseline year UPIN (Unique Physician Identification Number) was used to individually identify providers.  For PY1 and succeeding years NPI (National Provider Identifier) will be used.  For this demonstration, PY1 is a transition year for provider identifiers and there may be a few providers that have PIN (Provider Identification Number) as identifiers.  For PY2 and beyond, the goal will be to identify providers using their individual NPI.

To view the list of providers click File Arrow right. Lists in the main form (or press Ctrl+L as a shortcut) and select the item "Providers" in the dropdown list.  In the grid, the column "Provider #" displays the assigned numbers of all providers in the database.  The value in the ProviderNumber field must exist in the list to be successfully imported.  The list of providers could be exported using the Exporter utility.  See the topics on Adding and Editing Providers and Lists for more information.


HFCADLVSD Field
This field is shared by HF and CAD and must appear only once per tab-delimited file.

Example #1: A user wants to import all columns for the HF topic for the purpose of completing the minimum number of records available for analysis.  HFCADLVSD must be one of the columns in the tab-delimited file.

Example #2: A user wants to import all columns for the CAD topic for the purpose of completing the minimum number of records available for analysis.  HFCADLVSD must be one of the columns in the tab-delimited file.

Example #3: A user wants to import all columns for HF and CAD topics for the purpose of completing the minimum number of records available for analysis on both topics.  HFCADLVSD must be one of the columns in the tab-delimited file and must exist only once.  There cannot be two columns named "HFCADLVSD".

Notes on the above examples:
  • HFCADLVSD is not a required field but must be included to satisfy the requirement in the example.
  • Including the HFCADLVSD column is not a guarantee that a topic will be marked as completed.  Several other factors are considered before a topic is marked as completed.  See the topic on Data Status for more information.


Related Topics
Import Rules and Requirements
Element in GUI