LastName field

Data Element (edit)
Field Name:	LastName
CCMDB Label:	Last Name
CCMDB tab:	Top Row
Table:	L_Log table, L_PHI table
Data type:	string
Length:	40
Program:	Med and CC
Created/Raw:	Raw
Start Date:	1988-07-11
End Date:	2300-01-01
Sort Index:	2

Last Name of patient

• SMW

Legacy implementation right in the table

• Cargo

• Categories

• Forms

See also LastName field.

Corrections to names

If an inconsistency is found between old and current records,

• edit only if there is something incorrect, e.g. a typo
• use the value in the EPR for the correction
• we change the old entries to be consistent with the most current entry

See also: Crosschecking data with Manitoba Health

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:	* can't be blank can't start with a space can't start with a hyphen only allows letters, spaces and hyphens
Related:	[[LastName field]]
Firmness:	hard check
Timing:	always
App:	CCMDB.mdb
Coding:	function Validate_Last_name
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 (SAP, not entered, Centralized data front end.accdb, DSM Labs Consistency check.accdb, CCMDB.accdb, TISS28.accdb) of allowed values for the "DICApp" property. 

• Categories:  

• form:

This was implemented a long time ago, not clear what date

Legacy info

We used to standardize names to make it easier to keep them consistent over time. We decided to stop using our own standards to make it facilitate comparison with Manitoba Health and similar data. 13:34, 2015 April 27 (CDT) It used to be:

• if a name changed we retained the original one and changed new encounters of the patient to the old one.
• for first names we decided not to use hyphens if there was more than one, and to preferably only have one first name used
• last names that use two names were hyphenated