Skip to main content

Binary

A resource that represents the data of a single raw artifact as digital content accessible in its native format. A Binary resource can contain any content, whether text, image, pdf, zip archive, etc.

These interaction paths describe standard FHIR R4 patterns. Availability can depend on the API capabilities enabled for your Ovok project.

InteractionMethodPath
ReadGET/fhir/R4/Binary/[id]
VreadGET/fhir/R4/Binary/[id]/_history/[vid]
UpdatePUT/fhir/R4/Binary/[id]
PatchPATCH/fhir/R4/Binary/[id]
DeleteDELETE/fhir/R4/Binary/[id]
CreatePOST/fhir/R4/Binary
SearchGET/fhir/R4/Binary
HistoryGET/fhir/R4/Binary/[id]/_history

Top-level elements​

ElementTypeCardinalityDescription
idstring0..1Logical id of this artifact
metaMeta0..1Metadata about the resource
implicitRulesuri0..1A set of rules under which this content was created
languagecode0..1Language of the resource content
contentTypecode1..1MimeType of the binary content
securityContextReference0..1Identifies another resource to use as proxy when enforcing access control
database64Binary0..1The actual content

Resource-specific search parameters​

ParameterTypeDescription
——No resource-specific search parameters are listed in the package.

Reference​

Official FHIR R4 spec: Binary.
Maturity: Trial Use 5 (FMM 5).