Profile: ITK-Attachment-Binary-1
Binary | |
Definition | A binary resource can contain any content, whether text, image, pdf, zip archive, etc. |
Cardinality | 0...* |
Comments | Typically, Binary resources are used for handling content such as: * CDA Documents (i.e. with XDS) * PDF Documents * Images (the Media resource is preferred for handling images, but not possible when the content is already binary - e.g. XDS). |
Mappings |
|
Binary.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | id |
Summary | True |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
Invariants |
|
Mappings |
|
Binary.meta | |
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. |
Cardinality | 0...1 |
Type | Meta |
Summary | True |
Invariants |
|
Mappings |
|
Binary.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. |
Invariants |
|
Mappings |
|
Binary.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. Common Languages (extensible) |
Comments | Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). |
Invariants |
|
Mappings |
|
Binary.contentType | |
Definition | MimeType of the binary content represented as a standard MimeType (BCP 13). |
Cardinality | 1...1 |
Type | code |
Binding | The mime type of an attachment. Any valid mime type is allowed. ?? (required) |
Summary | True |
Comments | Note that FHIR strings may not exceed 1MB in size |
Invariants |
|
Mappings |
|
Binary.securityContext | |
Definition | Treat this binary as if it was this other resource for access control purposes. |
Cardinality | 0...1 |
Type | Reference(Resource) |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
Binary.content | |
Definition | The actual content, base64 encoded. |
Cardinality | 1...1 |
Type | base64Binary |
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. |
Invariants |
|
Mappings |
|
Elements required for capability
Element | Use | CareConnect | UK Core |
---|---|---|---|
id | |||
meta.profile | |||
meta.versionId | |||
meta.lastUpdated | |||
contentType | |||
content |
id
Usage
Mandatory
Guidance
The id
is the logical identifier for the ITK-Attachment-Binary-1
profile.
Example
<id value="7ea981aa-5ac1-11ed-9b6a-0242ac120002" />
meta.profile
Usage
Mandatory
Guidance
The meta.profile
contains a fixed value of the URL for the ITK-Attachment-Binary-1
profile.
Example
<meta> <profile value="https://fhir.nhs.uk/STU3/StructureDefinition/ITK-Attachment-Binary-1" /> </meta>
contentType
Usage
Mandatory
Guidance
The MIME type of the content being sent. It is expected that application/pdf
will be the most common use case for this capability; however, a list of common health related MIME types has been provided below.
Extension | Kind of document | MIME type |
---|---|---|
.pdf |
Adobe Portable Document Format (PDF) | application/pdf |
.doc |
Microsoft Word | application/msword |
.docx |
Office Open XML Word extension | application/vnd.openxmlformats-officedocument.wordprocessingml.document |
.rtf |
Rich-text format | application/mswrtford |
.html |
Hypertext Markup Language | text/html |
.txt |
Plain text | text/plain |
.xml |
Extensible Markup Language | text/xml |
.jpg / .jpeg |
JPEG images | image/jpg |
.png |
Portable Network Graphics | image/png |
.tiff |
Tag Image File Format | image/png |
Example
<contentType value="application/pdf"/>
content
Usage
Mandatory
Guidance
Example
<content value="[base64 encoded content]" />