Chart number: Difference between revisions
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) |
||
| Line 19: | Line 19: | ||
=== Dashes near the end of the number === | === Dashes near the end of the number === | ||
*EPR sometimes lists something like MRN 123456-1; in that case, we code 1234561, i.e. leave out the dash, but code the trailing number. | |||
*EPR sometimes lists something like MRN 123456-1; in that case, | |||
=== Unclear or changing chart numbers === | === Unclear or changing chart numbers === | ||
Revision as of 18:25, 2019 November 7
| Data Element (edit) | |
| Field Name: | Chart |
| CCMDB Label: | Chart |
| CCMDB tab: | Top Row |
| Table: | L_Log table, L_PHI table |
| Data type: | string |
| Length: | 8 |
| Program: | Med and CC |
| Created/Raw: | Raw |
| Start Date: | 1988-07-11 |
| End Date: | 2300-01-01 |
| Sort Index: | 6 |
The number used by medical records to uniquely identify a patient's chart; it is different for the same patients at different hospitals.
The number is assigned to a patient by Admitting. This is done once the patient has been seen by Triage in ER or new to the hospital for clinics, testing and various workups. This number remains the patient's chart number for all hospital visits, admissions, tests, etc.
Collection instructions
Leading Zeros
If your chart number system uses leading zeros, don't enter the leading zeros, start with the first non-zero number.
Dashes near the end of the number
- EPR sometimes lists something like MRN 123456-1; in that case, we code 1234561, i.e. leave out the dash, but code the trailing number.
Unclear or changing chart numbers
See
Minimal Data Set
This entry is part of the Minimal Data Set. Special collection instructions apply, see that page for more info.
Data Processing
The Centralized_data_front_end.mdb has queries that make sure that the chart number for each Hospital site is the same for the same patient and make sure the chart number has valid format.
- query PL_SameCHART_Site_Diff_PHIN
- query PL_SamePHIN_Site_Diff_chart
- query PL_Chart_9_Digit
The Data Processor fixes any inconsistencies found from these queries by crosschecking from EPR and adds the alias identifier to the tmp project Alias ID collection.
In addition, the Statistician uses SAS to check key identifiers so they are consistent for same patient including Hosp chart etc.
L_PHI vs L_Log
This field is stored in the L_PHI table in CFE but in the L_Log table in CCMDB.accdb. See L_PHI table for details why.
Cross checks
Data Integrity Checks (automatic list)
| App | Status | |
|---|---|---|
| Check duplicate patient | CCMDB.accdb | implemented |
| Query check minimal data set incomplete | CCMDB.accdb | implemented |
| Function PHIN same as Chart | CCMDB.accdb | implemented |
| Function Validate Chart | CCMDB.accdb | implemented |
| PL SamePHIN Site Diff chart | Centralized data front end.accdb | implemented |
| PL SameCHART Site Diff PHIN | Centralized data front end.accdb | implemented |
| PL Chart 9 Digit | Centralized data front end.accdb | implemented |