member-match should not include a NewCoverage input

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Da Vinci HRex (FHIR)
    • current
    • Clinical Interoperability Council
    • (many)
    • Hide

      We will solicit and document specific use-cases from the payer community for how the old payer might use the linkage to support/enable subsequent interactions with the new payer.

      We will add language that says "For privacy reasons, the 'new' Coverage SHOULD NOT include any data elements not marked as mustSupport in the Coverage profile."

      Show
      We will solicit and document specific use-cases from the payer community for how the old payer might use the linkage to support/enable subsequent interactions with the new payer. We will add language that says "For privacy reasons, the 'new' Coverage SHOULD NOT include any data elements not marked as mustSupport in the Coverage profile."
    • Bob Dieterle / Richard Esmond : 9-0-1
    • Clarification
    • Non-substantive

      If I understand the use case for this operation it is to help a new payer learn a patient's identifier(s) from an old payer: 

      > The $member-match operation supports identifying the target payer’s member and coverage information for a specified member so the client can use that information for subsequent queries and operations.

      Furthermore from a privacy perspective unnecessary information about the patient's new health insurance coverage should not be shared with the old health plan. There is no documented purpose for communicating this to the old plan.

      Thus, The NewCoverage input parameter should be removed.

            Assignee:
            Unassigned
            Reporter:
            Josh Mandel
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: