Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-36802

FHIR Identity Matching Guide should give guidance for matching on previous names or addresses

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • Interoperable Digital Identity and Patient Matching (FHIR)
    • 1.0.0-ballot
    • Patient Administration
    • STU
    • Patient Matching
    • 4.4
    • Hide

      Adding to current version skews the weight for current elements. Would require substantial rework. Should be explicitly noted as out of scope.
      Will add guidance: Names are verified at a point in time and previous names are often useful in matching. However, best practices include periodic reverification, and it is generally expected that First and Last names reflect current names. Best practice data stewardship expects previous names to be designated as such within the Patient resource. Appropriate use of Patient.name.use and Patient.name.period are expected for use of previous names.

      Show
      Adding to current version skews the weight for current elements. Would require substantial rework. Should be explicitly noted as out of scope. Will add guidance: Names are verified at a point in time and previous names are often useful in matching. However, best practices include periodic reverification, and it is generally expected that First and Last names reflect current names. Best practice data stewardship expects previous names to be designated as such within the Patient resource. Appropriate use of Patient.name.use and Patient.name.period are expected for use of previous names.
    • Dave deRoode / Brian Postlethwaite : 5 - 0 - 0
    • Clarification
    • Non-substantive
    • current

    Description

      The description throughout the identity matching document refers to First and Last Name, as well as various pieces of addresses.  What it doesn't specify is whether previous values in these fields should be considered or not. Patient name changes and address changes are common and if a system has a previous value, that value should be allowed to be used in matching.

      Attachments

        Activity

          People

            Unassigned Unassigned
            mvisker Matthew Visker
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: