| Source | hl7.fhir.us.exchange-routing#current:Hybrid / Intermediary Exchange (v4.0.1) |
| resourceType | CapabilityStatement |
| id | exchange-routing-destination-server |
| canonical | http://hl7.org/fhir/us/exchange-routing/CapabilityStatement/exchange-routing-destination-server |
| version | 1.0.0 |
| status | active |
| publisher | HL7 International - FHIR Infrastructure |
| name | ExchangeRoutingDestinationServerCapabilityStatement |
| title | Exchange Routing Destination Server Capability Statement |
| date | 2022-05-17T00:00:00-05:00 |
| experimental | false |
| 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. |
| jurisdictions | us |
| kind | requirements |
| fhirVersion | 4.0.1 |
| formats | xml json application/json-patch+json |
| implementationGuides | http://hl7.org/fhir/us/exchange-routing/ImplementationGuide/exchange-routing |
| Usages | (none) |
This CapabilityStatement describes the expected capabilities of an destination FHIR server that conforms to the conventions of the Hybrid / Intermediary Exchange FHIR implementation guide.
| Mode | SERVER |
| Description |
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. |
| Transaction | |
| System History | |
| System Search |
| Resource Type | Profile | Read | Search | Update | Create |
|---|
Produced 06 Apr 2023