Extension to provide the organization's logo as a base64-encoded image. This allows the logo to be embedded directly in the Organization resource for display in digital product information leaflets.

An Extension

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

The organization's logo image encoded as base64. Should include the contentType (e.g., 'image/png', 'image/jpeg') and the base64-encoded data.

The MIME type of the logo image (e.g., 'image/png', 'image/jpeg', 'image/svg+xml').

BCP 13 (RFCs 2045, 2046, 2047, 4288, 4289 and 2049)

Processors of the data need to be able to know how to interpret the data.

The logo image encoded in base64 format.

The base64-encoded data SHALL be expressed in the same character set as the base resource XML or JSON.

The data needs to able to be transmitted inline.

Optional human-readable title or description of the logo (e.g., 'Company Logo', 'Organization Brand Mark').

May sometimes be derived from the source filename.

Applications need a label to display to a human user in place of the actual data if the data cannot be rendered or perceived by the viewer.

Extension to provide the organization's logo as a base64-encoded image. This allows the logo to be embedded directly in the Organization resource for display in digital product information leaflets.

The organization's logo image encoded as base64. Should include the contentType (e.g., 'image/png', 'image/jpeg') and the base64-encoded data.

The MIME type of the logo image (e.g., 'image/png', 'image/jpeg', 'image/svg+xml').

The logo image encoded in base64 format.

Optional human-readable title or description of the logo (e.g., 'Company Logo', 'Organization Brand Mark').

Extension to provide the organization's logo as a base64-encoded image. This allows the logo to be embedded directly in the Organization resource for display in digital product information leaflets.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

The organization's logo image encoded as base64. Should include the contentType (e.g., 'image/png', 'image/jpeg') and the base64-encoded data.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

The MIME type of the logo image (e.g., 'image/png', 'image/jpeg', 'image/svg+xml').

BCP 13 (RFCs 2045, 2046, 2047, 4288, 4289 and 2049)

Processors of the data need to be able to know how to interpret the data.

The human language of the content. The value can be any valid value according to BCP 47.

IETF language tag for a human language.

Users need to be able to choose between the languages in a set of attachments.

The logo image encoded in base64 format.

The base64-encoded data SHALL be expressed in the same character set as the base resource XML or JSON.

The data needs to able to be transmitted inline.

A location where the data can be accessed.

If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data.

The data needs to be transmitted by reference.

The number of bytes of data that make up this attachment (before base64 encoding, if that is done).

The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference.

Representing the size allows applications to determine whether they should fetch the content automatically in advance, or refuse to fetch it at all.

The calculated hash of the data using SHA-1. Represented using base64.

The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see Provenance.signature for mechanism to protect a resource with a digital signature.

Included so that applications can verify that the contents of a location have not changed due to technical failures (e.g., storage rot, transport glitch, incorrect version).

Optional human-readable title or description of the logo (e.g., 'Company Logo', 'Organization Brand Mark').

May sometimes be derived from the source filename.

Applications need a label to display to a human user in place of the actual data if the data cannot be rendered or perceived by the viewer.

The date that the attachment was first created.

This is often tracked as an integrity issue for use of the attachment.

Height of the image in pixels (photo/video).

Width of the image in pixels (photo/video).

The number of frames in a photo. This is used with a multi-page fax, or an imaging acquisition context that takes multiple slices in a single image, or an animated gif. If there is more than one frame, this SHALL have a value in order to alert interface software that a multi-frame capable rendering widget is required.

if the number of frames is not supplied, the value may be unknown. Applications should not assume that there is only one frame unless it is explicitly stated.

The duration of the recording in seconds - for audio and video.

The duration might differ from occurrencePeriod if recording was paused.

The number of pages when printed.