FirstName field
| Data Element (edit) | |
| Field Name: | FirstName |
| CCMDB Label: | First 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: | 3 |
Last Name of patient
See also LastName field.
Enter the patient name as in EPR.
Data Processing at main office
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
|
under #Legacy info it said we stopped messing with names so cross checks with old data would work. If we no longer do that we should fix the reasoning there. |
EPR uses the name used at admission time. Our old records therefore become inconsistent with EPR.
When people change names, eg marriage, the Data Processor changes all old records to be consistent with the current one.
|
|
please confirm what we actually do now:
|
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 First name | CCMDB.accdb | implemented |
| PL Diff Phin SameLN FN DOB | Centralized data front end.accdb | implemented |
Legacy info
Legacy Content
This 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.