member-match does not bind parameters to targetProfiles

XMLWordPrintableJSON

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

      Will create a specific patient profile for the 'output' that forces that the member identifier is present and will update the 'response' Parameter profile to reference that new profile.

      Josh will submit a tooling issue to have the in and output profiles rendered on the OperationDefinition page.

      Show
      Will create a specific patient profile for the 'output' that forces that the member identifier is present and will update the 'response' Parameter profile to reference that new profile. Josh will submit a tooling issue to have the in and output profiles rendered on the OperationDefinition page.
    • Bob Dieterle / Richard Esmond : 9-0-1
    • Clarification
    • Non-substantive

      Values like the following don't define a targetProfile; they just bind to the "type": "Resource":

       

      { "name" : "MemberPatient", "use" : "out", "min" : 1, "max" : "1", "documentation" : "Parameter returned by the old plan resource **SHALL** contain the MemberPatient resource received from new plan with the ADDITION of an identifier of type \"UMB\" representing the unique identifier identifying the member of the old health plan.", "type" : "Resource", "referencedFrom" : [ \{ "source" : "NewCoverage", "sourceId" : "beneficiary" }

      ] },

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

              Created:
              Updated:
              Resolved: