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.

Name changes over time

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

please confirm what we actually do now: in case of a typo in case of a change do you use the Alias ID collection for this?

• SMW

• Cargo

• Categories

See also: Crosschecking data with Manitoba Health

Minimal Data Set

This entry is part of the Minimal Data Set. Special collection instructions apply, see that page for more info.

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.

Data Integrity Checks (automatic list)

	App	Status
Check duplicate patient	CCMDB.accdb	implemented
Query check minimal data set incomplete	CCMDB.accdb	implemented
Check function Validate Last name	CCMDB.accdb	implemented
PL Diff Phin SameLN FN DOB	Centralized data front end.accdb	implemented

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