Signature

$10 / year

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. There are a number of places where content must be signed in healthcare.

Complexity

The elements of the Signature Resource are for ease of access of these elements. For digital signatures (EXtensible Markup Language (Xml) DigSig, JavaScript Object Notation Web Signature/ JSON Web Signature (JWS)), the non-repudiation proof comes from the Signature validation, which includes validation of the referenced objects (e.g. Resources) (also known as, Content) in the XML-Signature Detached form.

Signature.type is 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.

One consequence of signing the document is that Universal Resource Locators (URLs), identifiers and internal references are frozen and cannot be changed. This might be a desired feature, but it may also cripple interoperability between closed ecosystems where re-identification frequently occurs. For this reason, it is recommended that systems consider carefully the impact of any signature processes. The impact of signatures on Document bundles and their related processes is the most well understood use of digital signatures.

Signature is used in the following places:
– Bundle
– Contract
– Provenance
– VerificationResult

Date Created

2018-09-20

Last Modified

2019-11-01

Version

4.0.1

Update Frequency

Annual

Temporal Coverage

N/A

Spatial Coverage

United States

Source

John Snow Labs; Health Level Seven International;

Source License URL

Source License Requirements

N/A

Source Citation

N/A

Keywords

FHIR, HL7, Medical Terminology, Processes Data, Processes Information, Processes Documentation, Health Information Exchange, Electronic Health Records, FHIR Smart, Smart on FHIR

Other Titles

FHIR Signature Datatype, Electronic Health Records Exchange Through FHIR

NameDescriptionTypeConstraints
Concept_NameName of the concept in the FHIR structure.stringrequired : 1
Computer_Ready_NameA Computer-ready name (e.g. a token) that identifies the structure - suitable for code generation. Note that this name (and other names relevant for code generation, including element & slice names, codes etc) may collide with reserved words in the relevant target language, and code generators will need to handle this.string-
TypeThe type the structure describes.string-
Dollar_RefThe "$ref" string value contains a Uniform Resource Identifier (URI) which identifies the location of the JSON value being referenced.string-
DescriptionA free text natural language description of the structure and its use.string-
ItemsThe value of the keyword should be an object or an array of objects. If the keyword value is an object, then for the data array to be valid each item of the array should be valid according to the schema in this value.string-
RequiredThe value of the keyword should be an array of unique strings. The data object to be valid should contain all properties with names equal to the elements in the keyword value.string-
Concept NameComputer Ready NameTypeDollar RefDescriptionItemsRequired
Signatureid#/definitions/stringUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
SignatureextensionarrayMay 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.{'$ref': '#/definitions/Extension'}
SignaturetypearrayAn 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.{'$ref': '#/definitions/Coding'}
Signaturewhen#/definitions/instantWhen the digital signature was signed.
Signature_when#/definitions/ElementExtensions for when
Signaturewho#/definitions/ReferenceA reference to an application-usable description of the identity that signed (e.g. the signature used their private key).
SignatureonBehalfOf#/definitions/ReferenceA reference to an application-usable description of the identity that is represented by the signature.
SignaturetargetFormat#/definitions/codeA mime type that indicates the technical format of the target resources signed by the signature.
Signature_targetFormat#/definitions/ElementExtensions for targetFormat
SignaturesigFormat#/definitions/codeA 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
Related Data Packages