FirstName field: Difference between revisions
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) |
||
| Line 19: | Line 19: | ||
* edit only if there is something incorrect, e.g. a typo | * edit only if there is something incorrect, e.g. a typo | ||
* use the value in the EPR for the correction <!-- confirmed 16:41, 2017 February 6 (CST)) --> | * use the value in the EPR for the correction <!-- confirmed 16:41, 2017 February 6 (CST)) --> | ||
* we change the old entries to be consistent with the most current entry <!-- confirmed w Pagasa 2017-11-15 --> | * we change the old entries to be consistent with the most current entry | ||
<!-- confirmed w Pagasa 2017-11-15 --> | |||
{{Discuss | who=Pagasa | question = 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. }} | {{Discuss | who=Pagasa | question = 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. | |||
{{Discuss | who=Pagasa | question = 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? }} | |||
{{Guideline Minimal Data Set}} | {{Guideline Minimal Data Set}} | ||
Revision as of 16:11, 2019 March 9
| 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.
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
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
Related Articles
| Related articles: |
|