Attachment Reference Exchange (ARex)
0.1.0 - ci-build
Attachment Reference Exchange (ARex) - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://fhir.onyxhealth.io/us/arex/CapabilityStatement/ARexContentConsumer | Version: 0.1.0 | |||
| Draft as of 2026-08-10 | Computable Name: ARexContentConsumer | |||
The party that retrieves a manifest and the content it references.
Raw OpenAPI-Swagger Definition file | Download
jsonNote 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.
clientConsumers SHALL verify the manifest signature and SHALL verify the declared digest of every object retrieved. Consumers SHALL persist retrieved content under their own retention obligations and SHALL NOT rely on re-retrieval.
The summary table lists the resources that are part of this configuration, and for each resource it lists:
_include_revinclude| Resource Type | Profile | R | S | U | C | Searches | _include | _revinclude | Operations |
|---|---|---|---|---|---|---|---|---|---|
| List | https://fhir.onyxhealth.io/us/arex/StructureDefinition/arex-manifest | y | y | ||||||
| Binary | https://fhir.onyxhealth.io/us/arex/StructureDefinition/arex-binary | y |
read, search-type.read.