Signature
A signature along with supporting context. The signature may be a digital signature that is cryptographic in nature, or some other signature acceptable to the domain. This other signature may be as simple as a graphical image representing a hand-written signature, or a signature ceremony Different signature approaches have different utilities. If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions
type Signature implements Element {
type: [Coding]
when: String
who: Reference
onBehalfOf: Reference
targetFormat: String
sigFormat: String
data: String
extension: [Extension]
id: String
}
Fields
Signature.type ● [Coding] list object
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.
Signature.when ● String scalar
When the digital signature was signed.
Signature.who ● Reference object
A reference to an application-usable description of the identity that signed (e.g. the signature used their private key).
Signature.onBehalfOf ● Reference object
A reference to an application-usable description of the identity that is represented by the signature.
Signature.targetFormat ● String scalar
A mime type that indicates the technical format of the target resources signed by the signature.
Signature.sigFormat ● String scalar
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.
Signature.data ● String scalar
The base64 encoding of the Signature content. When signature is not recorded electronically this element would be empty.
Signature.extension ● [Extension] list object
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.
Signature.id ● String scalar
Interfaces
Element interface
Base definition for all elements in a resource. If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions
Member Of
ContractSigner object ● ElementDefinition object ● ElementDefinitionExample object ● Extension object ● Provenance object ● StructureMapSource object ● TaskInput object ● TaskOutput object ● VerificationResultAttestation object ● VerificationResultValidator object