Chart number

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.

• SMW

Legacy implementation right in the table

• Cargo

• Categories

• Forms

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.

Unclear or changing chart numbers

See

• Alias ID collection
• John or Jane Doe patient
• Stolen identities

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
Summary:	validates the Chart number: check that the entry is numerical check to ensure that PHIN field and Chart number are not identical. no further checks at this time because chart numbers are different at different hospitals
Related:	list of related pages (probably the one it's on, but there might be others...)
Firmness:	hard check (not allowed) or soft check (allowed, but give error; in CFE this means it has to go into the ... table, and cross checks have to consider that table)
Timing:	always
App:	CCMDB.mdb
Coding:	function Validate_chart()
Uses L Problem table:	not relevant for this app
Status:	implemented
Implementation Date:	2008-01-01
Backlogged:	true

• Cargo

• SMW

"CCMDB.mdb" is not in the list (CCMDB.accdb, Centralized data front end.accdb, TISS28.accdb, SAP, DSM Labs Consistency check.accdb, not entered) of allowed values for the "DICApp" property. 

• Categories:  

• form:

approximate implementation date