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

Patient Safety Considerations Re: UUIDs

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • Interoperable Digital Identity and Patient Matching (FHIR)
    • current
    • Patient Administration
    • Digital Identity
    • Hide

      Update the text in 4.5 from:

      "... IDI Patient L1 indicates an input weight threshold that is expected to only result in matches on the individual whose identity was verified at the minimum level required by this IG for match requests (IAL1.5)..."

      to:

      "IDI Patient L1 indicates an input weight threshold that is expected to only result in matches on the individual whose identity was verified at the minimum level required by this IG for consumer-facing match requests (IAL1.8/AAL2)..."

      The section 4.4 table has one entry that needs to be fixed to add DOB; Section 4.5 weight should be changed from 10 to 5 and that has secondary impact on both invariant calculations.

      Update third row, column one in Table under 4.4 to include DOB with First and Last name and Digital Identifier.

      Update weight score in first row to be 5 instead of 10.

      Show
      Update the text in 4.5 from: "... IDI Patient L1 indicates an input weight threshold that is expected to only result in matches on the individual whose identity was verified at the minimum level required by this IG for match requests (IAL1.5)..." to: "IDI Patient L1  indicates an input weight threshold that is expected to only result in matches on the individual whose identity was verified at the minimum level required by this IG for  consumer-facing  match requests (IAL1. 8/AAL2 )..." The section 4.4 table has one entry that needs to be fixed to add DOB; Section 4.5 weight should be changed from 10 to 5 and that has secondary impact on both invariant calculations. Update third row, column one in Table under 4.4 to include DOB with First and Last name and Digital Identifier. Update weight score in first row to be 5 instead of 10.
    • Enhancement
    • Non-compatible
    • current

    Description

      While UUIDs are globally unique, there are potential UUID collisions that may occur during authentication and/or hl7_identifier creation in IdPs. In order to avoid these conflicts, we should create a sentence to implementer to include additional demographics in JWT-tokens in addition to the hl7_identifier.

      Attachments

        Activity

          People

            Unassigned Unassigned
            nussteja Aaron Nusstein
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: