FirstName field: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
PTorres (talk | contribs)
 
(21 intermediate revisions by 2 users not shown)
Line 4: Line 4:
| CCMDB_tab = Top Row  
| CCMDB_tab = Top Row  
| element_description = Last Name of patient
| element_description = Last Name of patient
| in_table = L_Log
| in_table = L_Log table, L_PHI table
| data_type = string
| data_type = string
| datafield_length = 40  
| datafield_length = 40  
Line 14: Line 14:
See also [[LastName field]].
See also [[LastName field]].


== Corrections to names ==
'''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 this changes, update [[Biographic changes over time]] -->
If an inconsistency is found between old and current records,  
If an inconsistency is found between old and current records,  
* 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
* use the value in the EPR for the correction <!-- confirmed 16:41, 2017 February 6 (CST)) -->
* yes I used the value in the EPR.
* we change the old entries to be consistent with the most current entry
16:41, 2017 February 6 (CST)
<!-- confirmed w Pagasa 2017-11-15 -->


Information about other names for the patient may be available in [[Alias ID collection]].


See also: [[Crosschecking data with Manitoba Health]]
{{Guideline Minimal Data Set}}


{{PHI_Data}}
{{PHI_Data}}


=={{CCMDB Data Integrity Checks}}==
{{Data Integrity Check List}}
* can't be blank
* can't start with a space
* can't start with a hyphen
* only allows letters, spaces and hyphens


== Legacy info ==
== Legacy info ==
{{LegacyContent
|explanation=we used to change names around for consistency but stopped doing this.
|successor=use rules above
|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)
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:
It used to be:
Line 38: Line 45:
* for first names we decided not to use hyphens if there was more than one, and to preferrably only have one first name used
* 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
* last names that use two names were hyphenated
}}
== Related Articles ==
{{Related Articles}}


[[Category: Standards and Conventions]]
[[Category: Standards and Conventions]]
Line 43: Line 54:
[[Category: Registry Data]]
[[Category: Registry Data]]
[[Category: Patient Viewer]]
[[Category: Patient Viewer]]
[[Category: Data Processing]]
[[Category: Demographics]]
[[Category: L_Log table]]
[[Category: 1Main table]]

Latest revision as of 11:25, 2019 October 23

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

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms


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)

 AppStatus
Check duplicate patientCCMDB.accdbimplemented
Query check minimal data set incompleteCCMDB.accdbimplemented
Check function Validate First nameCCMDB.accdbimplemented
PL Diff Phin SameLN FN DOBCentralized data front end.accdbimplemented

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.

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: