EHR Capability Statement should include $process-message

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Making EHR Data More available for Research and Public Health (MedMorph) (FHIR)
    • current
    • Public Health
    • Use Cases
    • 3.3.6
    • Hide

      We will add the following to the EHRs Capability Statement to forward the response back into the EHR.

      1. Addition of Document Reference APIs (POST) to post the response back into the EHR. The attachment within the Document Reference would be the Response Bundle.
      2. Addition of Communication Resource APIs (POST) to post the response back into the EHR.
      Show
      We will add the following to the EHRs Capability Statement to forward the response back into the EHR. Addition of Document Reference APIs (POST) to post the response back into the EHR. The attachment within the Document Reference would be the Response Bundle. Addition of Communication Resource APIs (POST) to post the response back into the EHR.
    • Becky Angeles / Genny Luensman : 31 - 0 - 0
    • Correction
    • Compatible, substantive

      In Section 3.3.6 step R6 in the diagram says "The Backend Service App forwards the response back to the EHR". Since this response is from a message this step should be submitting the response to the EHR $process-message operation right? However, the EHR Capability Statement lists no operations.

      Suggestion: either clarify how the response should be forwarded or add the $process-message operation to the EHR CapabilityStatement

            Assignee:
            Nagesh Bashyam
            Reporter:
            blangley
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: