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

Consent reference to DocumentReference in member match request clarification

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci PDex (FHIR)
    • current
    • Financial Mgmt
    • Payer-to-Payer Exchange [deprecated]
    • Hide

      The exchange of Consent is being carried out between two covered entities and the content and conditions for an exchange of consent will be governed by a mutually agreed Trust Framework. The Consent resource's document reference link would be to a document maintained by the requesting payer, The content of the referenced document would NOT be used for any determination as part of the automated $member-match operation. The referenced document's only purpose is to provide evidence of an appropriate signature of the consenting member/patient.

      It is expected that the referenced document url/identifier could be used in an out-of-band audit to determine the validity of a consent request. This would be part of the Trust Framework agreed by the covered entities that are party to the framework rules. 

      Show
      The exchange of Consent is being carried out between two covered entities and the content and conditions for an exchange of consent will be governed by a mutually agreed Trust Framework. The Consent resource's document reference link would be to a document maintained by the requesting payer, The content of the referenced document would NOT be used for any determination as part of the automated $member-match operation. The referenced document's only purpose is to provide evidence of an appropriate signature of the consenting member/patient. It is expected that the referenced document url/identifier could be used in an out-of-band audit to determine the validity of a consent request. This would be part of the Trust Framework agreed by the covered entities that are party to the framework rules. 
    • Bob Dieterle / MaryKay McDaniel: 8-0-0
    • Clarification
    • Non-substantive
    • 2.0.0-ballot

    Description

      The linked [HRex specifications|https://build.fhir.org/ig/HL7/davinci-ehrx/StructureDefinition-hrex-parameters-member-match-in.html] for the member-match operations state that the Consent resource must reference a DocumentReference (via source), but where is that hosted? The natural choice would be to serve it from the Payer 2 (new payer) FHIR endpoint, that would typically require authentication though - how does Payer 1 (old payer) going to authenticate though? It is not specified

       

      Wouldn't be simpler to directly embed the consent document inside the consent resource instead?

      Attachments

        Activity

          People

            Unassigned Unassigned
            michelemottini Michele Mottini
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: