Hybrid / Intermediary Exchange
1.0.0 - CI Build

Hybrid / Intermediary Exchange, published by HL7 International - FHIR Infrastructure. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-exchange-routing-ig/ and changes regularly. See the Directory of published versions

## : Exchange Routing CapabilityStatement - Intermediary - JSON Representation

Active as of 2022-05-17

Raw json | Download

    {
      "resourceType" : "CapabilityStatement",
      "id" : "exchange-routing-intermediary",
      "text" : {
        "status" : "extensions",
        "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: CapabilityStatement exchange-routing-intermediary</b></p><a name=\"exchange-routing-intermediary\"> </a><a name=\"hcexchange-routing-intermediary\"> </a><h2 id=\"title\">Exchange Routing Intermediary Capability Statement</h2><ul><li>Implementation Guide Version: 1.0.0 </li><li>FHIR Version: 4.0.1 </li><li>Supported Formats: <code>xml</code>, <code>json</code></li><li>Supported Patch Formats: <code>application/json-patch+json</code></li><li>Published on: 2022-05-17 00:00:00-0500 </li><li>Published by: HL7 International - FHIR Infrastructure </li></ul><blockquote class=\"impl-note\"><p><strong>Note to Implementers: FHIR Capabilities</strong></p><p>Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.</p></blockquote><h3 id=\"shallIGs\">SHALL Support the Following Implementation Guides</h3><ul><li>http://hl7.org/fhir/us/exchange-routing/ImplementationGuide/exchange-routing</li></ul><h2 id=\"rest\">FHIR RESTful Capabilities</h2><div class=\"panel panel-default\"><div class=\"panel-heading\"><h3 id=\"mode1\" class=\"panel-title\">Mode: <code>server</code></h3></div><div class=\"panel-body\"><div><p>When participating in exchanges described in the Hybrid / Intermediary FHIR IG, the intermediary server <strong>SHALL</strong> pass FHIR resources returned by the destination server to the originator unchanged. 1. Implement RESTful behavior according to the FHIR specification. 1. Support the JSON source format.\nWhen participating in exchanges described in the Hybrid / Intermediary FHIR IG, the intermediary server, the intermediary server <strong>SHOULD</strong>: 1. Support the XML source format.</p>\n</div><div class=\"lead\"><em>Security</em></div><blockquote><div><ol>\n<li>Communication security implemented by the intermediary server SHALL conform with the guidelines stated in <a href=\"https://www.hl7.org/fhir/security.html\">FHIR Security</a> for all exchanges covered in this IG. When using TLS: the inbound gateway intermediary SHALL hold the TLS certificate for the destination’s public FHIR service base URL the certificates exchanged by the destination system, and any delegated intermediaries SHALL reflect their servers’ private URLs.</li>\n<li>Security tokens generated by the destination for use by the originator SHALL be forwarded by the intermediary server to the originating client.</li>\n<li>The intermediary server MAY implement the <a href=\"http://hl7.org/fhir/us/udap-security/2021Sep\">HL7 / UDAP Security for Scalable Registration, Authentication, and Authorization FHIR Implementation Guide</a>. 1. For general security considerations refer to <a href=\"https://www.hl7.org/fhir/secpriv-module.html\">FHIR Security and Privacy Considerations</a>.</li>\n</ol>\n</div></blockquote><div class=\"lead\"><em>Summary of System-wide Interactions</em></div></div></div></div>"
      },
      "url" : "http://hl7.org/fhir/us/exchange-routing/CapabilityStatement/exchange-routing-intermediary",
      "version" : "1.0.0",
      "name" : "ExchangeRoutingIntermediaryCapabilityStatement",
      "title" : "Exchange Routing Intermediary Capability Statement",
      "status" : "active",
      "experimental" : false,
      "date" : "2022-05-17T00:00:00-05:00",
      "publisher" : "HL7 International - FHIR Infrastructure",
      "contact" : [
        {
          "name" : "HL7 International - FHIR Infrastructure",
          "telecom" : [
            {
              "system" : "url",
              "value" : "http://www.hl7.org/Special/committees/fiwg"
            }
          ]
        },
        {
          "name" : "Frank McKinney",
          "telecom" : [
            {
              "system" : "email",
              "value" : "frank.mckinney@pocp.com"
            }
          ]
        }
      ],
      "description" : "This CapabilityStatement describes the expected capabilities of an intermediary server that conforms to the conventions of the Hybrid / Intermediary Exchange FHIR implementation guide.",
      "jurisdiction" : [
        {
          "coding" : [
            {
              "system" : "urn:iso:std:iso:3166",
              "code" : "US",
              "display" : "United States of America"
            }
          ]
        }
      ],
      "kind" : "requirements",
      "fhirVersion" : "4.0.1",
      "format" : [
        "xml",
        "json"
      ],
      "patchFormat" : [
        "application/json-patch+json"
      ],
      "implementationGuide" : [
        "http://hl7.org/fhir/us/exchange-routing/ImplementationGuide/exchange-routing"
      ],
      "rest" : [
        {
          "mode" : "server",
          "documentation" : "When participating in exchanges described in the Hybrid / Intermediary FHIR IG, the intermediary server **SHALL** pass FHIR resources returned by the destination server to the originator unchanged. 1. Implement RESTful behavior according to the FHIR specification. 1. Support the JSON source format. \nWhen participating in exchanges described in the Hybrid / Intermediary FHIR IG, the intermediary server, the intermediary server **SHOULD**: 1. Support the XML source format.",
          "security" : {
            "description" : "1. Communication security implemented by the intermediary server SHALL conform with the guidelines stated in [FHIR Security](https://www.hl7.org/fhir/security.html) for all exchanges covered in this IG. When using TLS: the inbound gateway intermediary SHALL hold the TLS certificate for the destination’s public FHIR service base URL the certificates exchanged by the destination system, and any delegated intermediaries SHALL reflect their servers’ private URLs. \n1. Security tokens generated by the destination for use by the originator SHALL be forwarded by the intermediary server to the originating client. \n1. The intermediary server MAY implement the [HL7 / UDAP Security for Scalable Registration, Authentication, and Authorization FHIR Implementation Guide](http://hl7.org/fhir/us/udap-security/2021Sep). 1. For general security considerations refer to [FHIR Security and Privacy Considerations](https://www.hl7.org/fhir/secpriv-module.html)."
          }
        }
      ]
    }