Signature
Data typeTrial use
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.
Structure
| Element | Card. | Type | Description |
|---|---|---|---|
id | 0..1 | string | Unique id for inter-element referencing |
extension | 0..* | Extension | Additional content defined by implementations |
typeRequiredΣ | 1..* | Coding | Indication of the reason the entity signed the object(s)Binding (preferred): signature-type |
whenRequiredΣ | 1..1 | instant | When the signature was created |
whoRequiredΣ | 1..1 | Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Device | Organization) | Who signed |
onBehalfOfΣ | 0..1 | Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Device | Organization) | The party represented |
targetFormat | 0..1 | code | The technical format of the signed resourcesBinding (required): mimetypes |
sigFormat | 0..1 | code | The technical format of the signatureBinding (required): mimetypes |
data | 0..1 | base64Binary | The actual signature content (XML DigSig. JWS, picture, etc.) |
Σ in _summary results · ?! modifier element · 1.. required · inherited elements in grey