A digital or electronic signature capturing who signed, when, type, and signature data. Extension to capture the practitioner's digital signature on an Encounter resource.

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.

Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).

An indication of the reason that the entity signed this document. This may be explicitly included as part of the signature information and can be used when determining accountability for various actions concerning the document.

Examples include attesting to: authorship, correct transcription, and witness of specific event. Also known as a "Commitment Type Indication".

An indication of the reason that an entity signed the object.

When the digital signature was signed.

This should agree with the information in the signature.

A reference to an application-usable description of the identity that signed (e.g. the signature used their private key).

This should agree with the information in the signature.

A digital or electronic signature capturing who signed, when, type, and signature data. Extension to capture the practitioner's digital signature on an Encounter resource.

A digital or electronic signature capturing who signed, when, type, and signature data. Extension to capture the practitioner's digital signature on an Encounter resource.

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.

Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).

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 manageable, 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.

An indication of the reason that the entity signed this document. This may be explicitly included as part of the signature information and can be used when determining accountability for various actions concerning the document.

Examples include attesting to: authorship, correct transcription, and witness of specific event. Also known as a "Commitment Type Indication".

An indication of the reason that an entity signed the object.

When the digital signature was signed.

This should agree with the information in the signature.

A reference to an application-usable description of the identity that signed (e.g. the signature used their private key).

This should agree with the information in the signature.

A reference to an application-usable description of the identity that is represented by the signature.

The party that can't sign. For example a child.

used when the signature is on behalf of a non-signer.

A mime type that indicates the technical format of the target resources signed by the signature.

"xml", "json" and "ttl" are allowed, which describe the simple encodings described in the specification (and imply appropriate bundle support). Otherwise, mime types are legal here.

The mime type of an attachment. Any valid mime type is allowed.

A mime type that indicates the technical format of the signature. Important mime types are application/signature+xml for X ML DigSig, application/jose for JWS, and image/* for a graphical image of a signature, etc.

The mime type of an attachment. Any valid mime type is allowed.

The base64 encoding of the Signature content. When signature is not recorded electronically this element would be empty.

Where the signature type is an XML DigSig, the signed content is a FHIR Resource(s), the signature is of the XML form of the Resource(s) using XML-Signature (XMLDIG) "Detached Signature" form.