Drop contained resources in $member-match examples

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Da Vinci HRex (FHIR)
    • current
    • Clinical Interoperability Council
    • $member-match example response
      $member-match payer example request
    • Hide

      We will add language indicating that the various references in Coverage SHOULD be handled using Reference.reference (and possibly Reference.display) if the target resource is available from a RESTful endpoint or using Reference.identifier and Reference.display if the resource is not available on a RESTful endpoint.  A relative reference to a contained resource is generally not appropriate if an identifier for the target is known.

      Will update the example instances in the IG to align with this principle and to show both mechanisms of reference.

      Show
      We will add language indicating that the various references in Coverage SHOULD be handled using Reference.reference (and possibly Reference.display) if the target resource is available from a RESTful endpoint or using Reference.identifier and Reference.display if the resource is not available on a RESTful endpoint.  A relative reference to a contained resource is generally not appropriate if an identifier for the target is known. Will update the example instances in the IG to align with this principle and to show both mechanisms of reference.
    • Bob Dieterle / Richard Esmond : 9-0-1
    • Clarification
    • Compatible, substantive

      These organizations don't appear to meet the criteria to be contained - and it's not totally clear why they're needed at all.  If they are needed, consider making them separate operation criteria

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: