Package | hl7.fhir.us.exchange-routing |
Type | CapabilityStatement |
Id | exchange-routing-destination-server |
FHIR Version | R4 |
Source | http://hl7.org/fhir/us/exchange-routing/https://build.fhir.org/ig/HL7/fhir-exchange-routing-ig/CapabilityStatement-exchange-routing-destination-server.html |
URL | http://hl7.org/fhir/us/exchange-routing/CapabilityStatement/exchange-routing-destination-server |
Version | 1.0.0 |
Status | active |
Date | 2022-05-17T00:00:00-05:00 |
Name | ExchangeRoutingDestinationServerCapabilityStatement |
Title | Exchange Routing Destination Server Capability Statement |
Realm | us |
Authority | hl7 |
Description | This CapabilityStatement describes the expected capabilities of an destination FHIR server that conforms to the conventions of the Hybrid / Intermediary Exchange FHIR implementation guide. |
Kind | requirements |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Generated Narrative: CapabilityStatement exchange-routing-destination-server
xml
, json
application/json-patch+json
Note to Implementers: FHIR Capabilities
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.
server
When participating in exchanges described in the Hybrid / Intermediary FHIR IG, the destination server SHALL populate references to itself within FHIR resources it returns (e.g., in the Bundle.entry.fullUrl element) and in HTTP header parameters (e.g., Content-Location within the FHIR Asynchronous Pattern) with its public FHIR service base URL. 1. Implement RESTful behavior according to the FHIR specification. 1. Support the JSON source format. When participating in exchanges involving an intermediary as described in the Hybrid / Intermediary FHIR IG, the server SHOULD: 1. Support the XML source format.
- Communication security implemented by the server SHALL conform with the guidelines stated in FHIR Security for all exchanges covered in this IG.
- The server MAY implement the HL7 / UDAP Security for Scalable Registration, Authentication, and Authorization FHIR Implementation Guide. 1. For general security considerations refer to FHIR Security and Privacy Considerations.
{ "resourceType": "CapabilityStatement", "id": "exchange-routing-destination-server", "text": { "status": "extensions", "div": "<!-- snip (see above) -->" }, "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg", "valueCode": "fhir" }, { "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm", "valueInteger": 1, "_valueInteger": { "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom", "valueCanonical": "http://hl7.org/fhir/us/exchange-routing/ImplementationGuide/exchange-routing" } ] } }, { "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status", "valueCode": "trial-use", "_valueCode": { "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom", "valueCanonical": "http://hl7.org/fhir/us/exchange-routing/ImplementationGuide/exchange-routing" } ] } } ], "url": "http://hl7.org/fhir/us/exchange-routing/CapabilityStatement/exchange-routing-destination-server", "version": "1.0.0", "name": "ExchangeRoutingDestinationServerCapabilityStatement", "title": "Exchange Routing Destination Server 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": "David Pyke", "telecom": [ { "system": "email", "value": "david@pyke.ca" } ] } ], "description": "This CapabilityStatement describes the expected capabilities of an destination FHIR 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 destination server **SHALL** populate references to itself within FHIR resources it returns (e.g., in the Bundle.entry.fullUrl element) and in HTTP header parameters (e.g., Content-Location within the FHIR Asynchronous Pattern) with its public FHIR service base URL. 1. Implement RESTful behavior according to the FHIR specification. 1. Support the JSON source format. \nWhen participating in exchanges involving an intermediary as described in the Hybrid / Intermediary FHIR IG, the server **SHOULD**: 1. Support the XML source format.", "security": { "description": "1. Communication security implemented by the server SHALL conform with the guidelines stated in [FHIR Security](https://www.hl7.org/fhir/security.html) for all exchanges covered in this IG. \n1. The 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)." } } ] }