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

FHIR ID Support and Usage

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Da Vinci CDex (FHIR)
    • 2.0.0-ballot
    • Patient Care
    • Direct Query
    • Hide

      There is no requirement that the requester knows the FHIR Patient.id in advance of the exchange.  The FHIR Patient.id is solicited via one of two methods 

      1) query for patient by .identifier (using an MRN or Member ID) or 

      2) Performing the Patient Match operation and providing sufficient demographics to match to a single patient

      Each of the above will return a FHIR Patient.id for a successful query/match.

      Expand the documentation to clarify the above process

      Add that the source system SHOULD support the patient match operation.

      Show
      There is no requirement that the requester knows the FHIR Patient.id in advance of the exchange.  The FHIR Patient.id is solicited via one of two methods  1) query for patient by .identifier (using an MRN or Member ID) or  2) Performing the Patient Match operation and providing sufficient demographics to match to a single patient Each of the above will return a FHIR Patient.id for a successful query/match. Expand the documentation to clarify the above process Add that the source system SHOULD support the patient match operation.
    • Eric Haas/Jay Lyle: 7-0-1
    • Clarification
    • Non-substantive

    Description

      So much of this IG relies on the support and use of FHIR IDs. It would be helpful to know how widespread support and usage of FHIR IDs are today. Is the community ready to adopt a guide dependent on FHIR IDs or is this IG meant to drive the use of FHIR IDs?

      Attachments

        Activity

          People

            Unassigned Unassigned
            apreisler Andrea Preisler
            Andrea Preisler
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: