Generated Narrative: CapabilityStatement ARexContentConsumer ARex Content Consumer Implementation Guide Version: 0.1.0 FHIR Version: 4.0.1 Supported Formats: json Published on: 2026-08-10 Published by: Onyx Technology, LLC 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. FHIR RESTful Capabilities Mode: client Consumers 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. Capabilities by Resource/Profile Summary The summary table lists the resources that are part of this configuration, and for each resource it lists: The relevant profiles (if any) The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them. The required, recommended, and some optional search parameters (if any). The linked resources enabled for _include The other resources enabled for _revinclude The operations on the resource (if any) 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 Resource Conformance: unspecified List Base System Profile ARex Manifest Profile Conformance SHALL Reference Policy Interaction summary Supports read, search-type. Resource Conformance: unspecified Binary Base System Profile ARex Binary Profile Conformance SHALL Reference Policy Interaction summary Supports read.
The party that retrieves a manifest and the content it references.
Consumers 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.