This
page
is
part
of
the
FHIR
Specification
(v4.0.1:
R4
(v5.0.0:
R5
-
Mixed
Normative
and
STU
)
).
This
is
the
current
published
version
in
it's
permanent
home
(it
will
always
be
available
at
this
URL).
The
current
version
which
supercedes
this
version
is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
R3
R2
FHIR
Infrastructure
Work
Group
|
Maturity Level : N | Normative (from v4.0.0) | Security Category : Not Classified |
Compartments
:
|
Detailed Descriptions for the elements in the Binary resource.
| Binary | |
| Element Id | Binary |
| Definition |
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. |
| Short Display | Pure binary content defined by a format other than FHIR |
| Cardinality | 0..* |
| Type | Resource |
| Requirements |
There are situations where it is useful or required to handle pure binary content using the same framework as other resources. |
| Summary | false |
| Comments |
Typically, Binary resources are used for handling content such as:
|
| Binary.contentType | |
| Element Id | Binary.contentType |
| Definition |
MimeType of the binary content represented as a standard MimeType (BCP 13). |
| Short Display | MimeType of the binary content |
| Cardinality | 1..1 |
| Terminology Binding |
|
| Type | code |
| Summary | true |
| Binary.securityContext | |
| Element Id | Binary.securityContext |
| Definition |
This
element
identifies
another
resource
that
can
be
used
as
a
proxy
of
the
security
sensitivity
to
use
when
deciding
and
enforcing
access
control
rules
for
the
Binary
resource.
Given
that
the
Binary
resource
contains
very
few
elements
that
can
be
used
to
determine
the
sensitivity
of
the
data
and
relationships
to
individuals,
the
referenced
resource
stands
in
as
a
proxy
equivalent
for
this
purpose.
This
referenced
resource
may
be
related
to
the
Binary
(e.g.
|
| Short Display | Identifies another resource to use as proxy when enforcing access control |
| Cardinality | 0..1 |
| Type | Reference ( Any ) |
| Summary | true |
| Comments |
Very often, a server will also know of a resource that references the binary, and can automatically apply the appropriate access rules based on that reference. However, there are some circumstances where this is not appropriate, e.g. the binary is uploaded directly to the server without any linking resource, the binary is referred to from multiple different resources, and/or the binary is content such as an application logo that has less protection than any of the resources that reference it. |
| Binary.data | |
| Element Id | Binary.data |
| Definition |
The actual content, base64 encoded. |
| Short Display | The actual content |
| Cardinality | 0..1 |
| Type | base64Binary |
| Summary | false |
| Comments |
If the content type is itself base64 encoding, then this will be base64 encoded twice - what is created by un-base64ing the content must be the specified content type. |