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

Make Consent optional in the $member-match operation

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci HRex (FHIR)
    • 1.0.0
    • Clinical Interoperability Council
    • HRex Member Match Operation
    • Hide

      We will loosen the cardinality to 0..1 and will remove mustSupport=true.  We will add a comment that downstream IGs may tighten conformance expectations on this element based on their use-cases.

      Show
      We will loosen the cardinality to 0..1 and will remove mustSupport=true.  We will add a comment that downstream IGs may tighten conformance expectations on this element based on their use-cases.
    • Lloyd McKenzie/Jimmy Tcheng: 9-0-0
    • Enhancement
    • Compatible, substantive

    Description

      The $member-match operation currently requires a Consent resource as a parameter (cardinality 1..1). While that works for a payer to payer use case, HRex was supposted to support multiple use cases, and for some, such as the Patient Cost Transparency (PCT) use case this is problematic. 

      Suggest making Consent optional instead of required (change cardinality to 0..1). 

      Note: I am submitting this on behalf of Artem Sopin from Edifecs. 

      Attachments

        Activity

          People

            rosemaryh Rosemary Hofstede
            rgeimer Rick Geimer
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: