{"resourceType":"StructureDefinition","id":"Bundle.signature","meta":{"lastUpdated":"2021-01-17T07:06:13.533+11:00"},"url":"http://hl7.org/fhir/StructureDefinition/Bundle.signature","version":"4.0.1","name":"Bundle.signature","title":"Bundle.signature","status":"draft","experimental":true,"date":"2021-01-17T07:06:13+11:00","publisher":"HL7 FHIR Standard","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"}]}],"description":"Data Element for Bundle.signature","purpose":"Data Elements are defined for each element to assist in questionnaire construction etc","fhirVersion":"4.0.1","mapping":[{"identity":"v2","uri":"http://hl7.org/v2","name":"HL7 v2 Mapping"},{"identity":"rim","uri":"http://hl7.org/v3","name":"RIM Mapping"},{"identity":"cda","uri":"http://hl7.org/v3/cda","name":"CDA (R2)"},{"identity":"w5","uri":"http://hl7.org/fhir/fivews","name":"FiveWs Pattern Mapping"}],"kind":"logical","abstract":false,"type":"Bundle.signature","baseDefinition":"http://hl7.org/fhir/StructureDefinition/Element","derivation":"specialization","snapshot":{"element":[{"id":"Bundle.signature","extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"path":"Bundle.signature","short":"Digital Signature","definition":"Digital Signature - base64 encoded. XML-DSig or a JWT.","comment":"The signature could be created by the \"author\" of the bundle or by the originating device.   Requirements around inclusion of a signature, verification of signatures and treatment of signed/non-signed bundles is implementation-environment specific.","requirements":"A Signature holds an electronic representation of a signature and its supporting context in a FHIR accessible form. The signature may either be a cryptographic type (XML DigSig or a JWS), which is able to provide non-repudiation proof, or it may be a graphical image that represents a signature or a signature process. This element allows capturing signatures on documents, messages, transactions or even search responses, to support content-authentication, non-repudiation or other business cases. This is primarily relevant where the bundle may travel through multiple hops or via other mechanisms where HTTPS non-repudiation is insufficient.","min":0,"max":"1","base":{"path":"Bundle.signature","min":0,"max":"1"},"type":[{"code":"Signature"}],"isModifier":false,"isSummary":true}]}}