Export Requirements
Dataset
Each dataset (patient and patient visit) must be exported into a separate
tab-delimited file. There is no file naming that needs to be
followed, though the standard extension for tab-delimited files is "txt". It
is a good idea to name the file so that the filename indicates its contents. For
example, for a tab-delimited file containing the list of patients, name it "Patients.txt"
and for the one containing the patient visits name it "Patient_Visits.txt".
Date
Range
The performance year must be specified to determine the correct dates to include
in the export. For example, if an EHR user needs to export patient visits
for the baseline year, then the visit dates have to be between January 1, 2006 and
December 31, 2006. Similarly, if the user wants to export patient information
(not the visits) for the baseline year, then the dates when the laboratory procedures
and blood pressure results were taken have to be within the specified date range.
The table below describes the measurement period of each performance year.
| Performance Year |
Start Date |
End Date |
| Baseline year |
01/01/2006 |
12/31/2006 |
| Performance Year 1 |
07/01/2007 |
06/30/2008 |
| Performance Year 2 |
07/01/2008 |
06/30/2009 |
| Performance Year 3 |
07/01/2009 |
06/30/2010 |
Columns
These are the requirements that involved the columns in the tab-delimited file.
See the file specifications for the names of columns
and their valid values.
- The primary key columns are required and must exist in the source file.
- The values or combination of values of primary key columns must be unique for each
row.
- There must be no duplicate column names.
- There must be no extra column names in a dataset. For example, a column named
“LastName” will cause an error if the dataset to be imported is Patient
Visit.
Rules
General Rules
- Column names are not case sensitive.
- Column names do not have to be in a certain order.
- Null values will be ignored and will not overwrite existing values.
- Invalid values will be ignored and will not overwrite existing values.
- Critical errors will prevent all records from being imported.
- Non-critical errors and warnings will be ignored and will
not prevent the valid values from being imported.
- "X" is not an acceptable value for unknown dates during import. This is valid
only during manual abstraction.
- No record is deleted during the import process.
Patient Dataset Rules
- The patient information in the database is only updated during the import process.
No record is added.
- If the HIC number of the patient (PatIDHIC) to be imported is not found in the database,
the information for that patient will not be imported.
- Each patient record must hold only one line in the tab-delimited file. That
is, the value of PatIDHIC must be unique in each row.
Visit Dataset
Rules
- If the HIC number of the patient (PatIDHIC) to be imported is not found in the database,
the visit will not be imported. No error or warning will be dislayed.
- If the HIC number of the patient (PatIDHIC) to be imported is found in
the database but the visit date is invalid or outside of valid date range, the visit
will not be imported. No error or warning will be dislayed.
- If the values of the PatIDHIC and HFPCVisitDate columns in a row to be imported
exist in the database, the existing record is updated with the imported values (depending
on the options set and the values to be imported).
- If the values of the PatIDHIC and HFPCVisitDate columns to be imported do not exist
in the database, a new record is added for that visit (as long as the value of PatIDHIC
to be imported exists in the database).
- If a visit to be imported has been marked as "Invalid" (HFPCInvalid =
1) and it is not in the database, then it will be reset as valid (HFPCInvalid =
0) during the import. User-added visits including those that are added during import
cannot be marked as invalid. Only pre-filled visits can be marked as invalid.
Visits added during manual editing or during import are not pre-filled visits.
- There must be no duplicate visit dates for each patient in the tab-delimited file.
That is, the combination of PatIDHIC and HFPCVisitDate columns must be
unique in each row.
Laboratory and Blood Pressure Rules
These apply only if the dataset to be imported is Patient.
- If the lab or BP date to be imported is earlier than the stored date and the user
specified not to overwrite more recent dates (default), then the related lab and
BP values will not be imported.
- If the date to be imported is invalid, then the related lab and BP values will not
be imported.
- The columns representing a laboratory result with date and blood pressure must
be imported as a group. Either none or all of these columns must be imported.
If these columns do not appear as a group, it will be considered a critical
error and the import utility will not continue. The table below shows the
columns that must be imported as a group
| Topic |
Measure # |
Columns |
Remarks |
| DM |
DM-1 & DM-2 |
DMHbA1cDate & DMHbA1cValue |
Either none or both of these columns must be in the source file. |
| DM |
DM-3 |
DMBPDate, DMBPSystolic
& DMBPDiastolic |
Either none or all of these columns must be in the source file. |
| DM |
DM-5 |
DMLDLCDate & DMLDLCValue |
Either none or both of these columns must be in the source file. |
| CAD |
CAD-6 |
CADLDLCDate & CADLDLCValue |
Either none or both of these columns must be in the source file. |
The table below shows the effect of importing lab and blood pressure results.
| Import Options
|
Data to
Import |
Stored Data
|
Result After
Import |
| Overwrite 'Yes'? |
Overwrite All Dates? |
Test1 |
Date2 |
Value3 |
Test1 |
Date2 |
Value3 |
Test1 |
Date2 |
Value3 |
| No |
Yes/No |
No/0 |
Any |
Any |
Yes/1 or No/0 |
Any |
Any |
Stored Value |
Stored Value |
Stored Value |
| Yes/No |
Yes/No |
Yes/1 |
01/01/2006 |
100 |
No/0 |
|
|
Yes/1 |
01/06/2006
|
100
|
| Yes/No |
No |
Yes/1 |
01/01/2006 |
100 |
Yes/1 |
06/06/2006 |
50 |
Yes/1 |
06/06/2006 |
50 |
| Yes/No |
No |
Yes/1 |
06/06/2006 |
66 |
Yes/1 |
06/06/2006 |
50 |
Yes/1 |
06/06/2006 |
66 |
| Yes/No |
No |
Yes/1 |
12/12/2006 |
120 |
Yes/1 |
06/06/2006 |
50 |
Yes/1 |
12/12/2006 |
120
|
| Yes/No |
Yes |
Yes/1 |
01/01/2006 |
100 |
Yes/1 or No/0 |
Any |
Any |
Yes/1 |
01/01/2006 |
100 |
| Yes |
Yes |
Yes/1 |
01/01/2006 |
100 |
Yes/1 |
06/06/2006 |
50 |
Yes/1 |
01/01/2006 |
100 |
1 This represents DMHbA1cTest, DMBPMeasure, CADLDLCTest and CADLDLCTest
columns in the tab-delimited file. A value of "No" could indicate that
the column value was not provided, the value was invalid, or the column is missing
from the tab-delimited file.
2 This column represents DMHbA1cDate, DMBPDate, DMLDLCDate and CADLDLCDate.
3 This column represents DMHbA1cValue, DMBPSystolic, DMBPDiastolic,
DMLDLCValue and CADLDLCValue.
Clean Up
If the patient is not ranked under a topic, the information to be imported under
that topic is ignored and no error or warning is raised.
Related Topics
Import File Specifications
Import Data menu
|