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

Remove required slice for MRN identifier

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • US Da Vinci CRD (FHIR)
    • current
    • Financial Mgmt
    • CRD Patient
    • FHIR Artifacts
    • 6.1.4.1.2
    • Hide

      The requirement for MRN comes from US Core.  Even if we were to not derive from US Core in the Da Vinci profile, CDS Hooks means that the CRD Service will have access to query the Patient resource using US Core, which means that MRN would still be mandatory there.

      If there is some reason why the payer isn't allowed to see the MRN, then US Core says that the dataAbsentReason extension can be used.  (We can't come up with a use-case where it would make sense for the MRN to be considered 'sensitive'.)

      Show
      The requirement for MRN comes from US Core.  Even if we were to not derive from US Core in the Da Vinci profile, CDS Hooks means that the CRD Service will have access to query the Patient resource using US Core, which means that MRN would still be mandatory there. If there is some reason why the payer isn't allowed to see the MRN, then US Core says that the dataAbsentReason extension can be used.  (We can't come up with a use-case where it would make sense for the MRN to be considered 'sensitive'.)
    • Bob Dieterle / Mark Scrimshire : 4-0-1

    Description

      The IG currently requires at least 1 slice to be a MRN. This is an odd requirement as systems may not want to exchange MRNs. Payers and providers may choose identifiers that are account numbers, EID numbers, and/or EMPI.

      This should not be a required slice.

      Attachments

        Activity

          People

            Unassigned Unassigned
            atorres Drew Torres
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: