FirstName field: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m m
m clean-up
Line 13: Line 13:


See also [[LastName field]].
See also [[LastName field]].
[[First Name and Last Name fields]].


{{PHI_Data}}
----
== Corrections to names ==
== Corrections to names ==
If an inconsistency is found between old and current records,  
If an inconsistency is found between old and current records,  

Revision as of 13:36, 2017 February 6

Data Element (edit)
Field Name: FirstName
CCMDB Label: First Name
CCMDB tab: Top Row
Table: L_Log
Data type:
Length:
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.

Corrections to names

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

Template:Discussion Is this still correct, Pagasa? If so, please remove the question, else please write what you do these days.

See also: Crosschecking data with Manitoba Health

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.

Template:CCMDB Data Integrity Checks

  • can't be blank
  • can't start with a space
  • can't start with a hyphen
  • only allows letters, spaces and hyphens

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