|Data Element (edit)|
|CCMDB Label:||First Name|
|CCMDB tab:||Top Row|
|Table:||L_Log table, L_PHI table|
|Program:||Med and CC|
Last Name of patient
Legacy implementation right in the table
See also LastName field.
Enter the patient name as in EPR.
Data Processing at main office
Name changes over time
When people change names, eg marriage, the Data Processor changes all old records to be consistent with the current one.
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
Information about other names for the patient may be available in Alias ID collection.
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)
|Check duplicate patient||CCMDB.accdb||implemented|
|Query check minimal data set incomplete||CCMDB.accdb||implemented|
|Check function Validate First name||CCMDB.accdb||implemented|
|PL Diff Phin SameLN FN DOB||Centralized data front end.accdb||implemented|
Legacy ContentThis page contains Legacy Content.
- Explanation: we used to change names around for consistency but stopped doing this.
- Successor: use rules above
Click Expand to show legacy content.
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 preferrably only have one first name used
- last names that use two names were hyphenated