Shared Health Specification and Guide Version 2.0 Revision F

The SAML token used to confirm the identity of the practitioner

none

unique id for the element within a resource (for internal references).

An Extension

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

Fixed value: http://sharedhealth.exchange/fhir/StructureDefinition/ext-practitioner-saml

The SAML token used to confirm the identity of the practitioner

none

unique id for the element within a resource (for internal references).

May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to 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.

Identifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate.

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

Fixed value: application/xml

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

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

The actual data of the attachment - a sequence of bytes. In XML, represented using base64.

The data needs to able to be transmitted inline.

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

An alternative location where the data can be accessed.

The data needs to be transmitted by reference.

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 number of bytes of data that make up this attachment.

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

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.

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

Included so that applications can verify that the contents of a location have not changed and so that a signature of the content can implicitly sign the content of an image without having to include the data in the instance or reference the url in the signature.

A label or set of text to display in place of the data.

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.