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

Matching Attributes need to relate to search time frame

    XMLWordPrintableJSON

Details

    • Change Request
    • Resolution: Considered for Future Use
    • Medium
    • Interoperable Digital Identity and Patient Matching (FHIR)
    • current
    • Patient Administration
    • Guidance on Identity Assurance
      Patient Matching
    • 3.2,4.2
    • Hide

      Deferred to next ballot cycle

      Show
      Deferred to next ballot cycle
    • Jeff Brown / Dave Deroode : 7-0-1

    Description

      In another industry group, a stakeholder mentioned a match concern when a person's identity is verified after they move but only their former address is in the system from which a match is requested. We discussed how the use of email address and mobile number, as well as the responder's use of private algorithms and identity management practices likely go some way to address this, but after considering this some more it occurs to me that we probably need a more specific call-out in the IG to clarify, particularly in TEFCA queries or other use cases where historical records may be needed that 1) the identity verification process should be able to capture and verify all home addresses during the time frame a record search may cover - being mindful of the case where a patient stopped receiving care while residing at a former address, such that that former address may be all the health system is aware of - and 2) those multiple verified addresses (or other attributes which may have changed like name, telephone number, and email address) are included in the match request if they were verified at some point in time. We likely need a short addition in the identity verification tab as well as in the match tab.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              juliemaas Julie Maas
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: