Connectathon 11 Snapshot
This page is part of the FHIR Specification (v1.2.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 
. Page versions: R5 R4B R4 R3 R2
StructureDefinition for Signature
{
"resourceType": "StructureDefinition",
"id": "Signature",
"meta": {
"lastUpdated": "2015-12-11T17:38:40.294+11:00"
},
"text": {
"status": "generated",
"div": "<div>!-- Snipped for Brevity --></div>"
},
"url": "http://hl7.org/fhir/StructureDefinition/Signature",
"name": "Signature",
"status": "draft",
"publisher": "HL7 FHIR Standard",
"contact": [
{
"telecom": [
{
"system": "other",
"value": "http://hl7.org/fhir"
}
]
}
],
"date": "2015-12-11T17:38:40+11:00",
"description": "Base StructureDefinition for Signature Type",
"requirements": "There are a number of places where content must be signed in healthcare.",
"fhirVersion": "1.2.0",
"mapping": [
{
"identity": "rim",
"uri": "http://hl7.org/v3",
"name": "RIM"
}
],
"kind": "datatype",
"abstract": false,
"base": "http://hl7.org/fhir/StructureDefinition/Element",
"snapshot": {
"element": [
{
"path": "Signature",
"short": "A digital Signature - XML DigSig, JWT, Graphical image of signature, etc.",
"definition": "A digital signature along with supporting context. The signature may be electronic/cryptographic in nature, or a graphical image representing a hand-written signature, or a signature process. Different Signature approaches have different utilities.",
"comments": "The elements of the Signature Resource are for ease of access of these elements. Foro digital signatures (Xml DigSig, JWT), the non-repudiation proof comes from the Signature validation, which includes validation of the referenced objects (e.g. Resources) (a.k.a., Content) in the XML-Signature Detached form.",
"min": 0,
"max": "*",
"type": [
{
"code": "Element"
}
],
"isSummary": true
},
{
"path": "Signature.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Signature.extension",
"short": "Additional Content defined by implementations",
"definition": "May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comments": "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.",
"alias": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Signature.type",
"short": "Indication of the reason the entity signed the object(s)",
"definition": "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.",
"comments": "Examples include attesting to: authorship, correct transcription, and witness of specific event. Also known as a "Commitment Type Indication".",
"min": 1,
"max": "*",
"type": [
{
"code": "Coding"
}
],
"isSummary": true,
"binding": {
"strength": "preferred",
"description": "An indication of the reason that an entity signed the object",
"valueSetReference": {
"reference": "http://hl7.org/fhir/ValueSet/signature-type"
}
}
},
{
"path": "Signature.when",
"short": "When the signature was created",
"definition": "When the digital signature was signed.",
"comments": "This should agree with the information in the signature.",
"min": 1,
"max": "1",
"type": [
{
"code": "instant"
}
],
"isSummary": true
},
{
"path": "Signature.who[x]",
"short": "Who signed the signature",
"definition": "A reference to an application-usable description of the person that signed the certificate (e.g. the signature used their private key).",
"comments": "This should agree with the information in the signature.",
"min": 1,
"max": "1",
"type": [
{
"code": "uri"
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/Practitioner"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/RelatedPerson"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/Patient"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/Device"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/Organization"
]
}
],
"isSummary": true
},
{
"path": "Signature.contentType",
"short": "The technical format of the signature",
"definition": "A mime type that indicates the technical format of the signature. Important mime types are application/signature+xml for X ML DigSig, application/jwt for JWT, and image/* for a graphical image of a signature.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"isSummary": true,
"binding": {
"strength": "required",
"description": "The mime type of an attachment. Any valid mime type is allowed.",
"valueSetUri": "http://www.rfc-editor.org/bcp/bcp13.txt"
}
},
{
"path": "Signature.blob",
"short": "The actual signature content (XML DigSig. JWT, picture, etc.)",
"definition": "The base64 encoding of the Signature content.",
"comments": "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.",
"min": 1,
"max": "1",
"type": [
{
"code": "base64Binary"
}
],
"isSummary": true
}
]
},
"differential": {
"element": [
{
"path": "Signature",
"short": "A digital Signature - XML DigSig, JWT, Graphical image of signature, etc.",
"definition": "A digital signature along with supporting context. The signature may be electronic/cryptographic in nature, or a graphical image representing a hand-written signature, or a signature process. Different Signature approaches have different utilities.",
"comments": "The elements of the Signature Resource are for ease of access of these elements. Foro digital signatures (Xml DigSig, JWT), the non-repudiation proof comes from the Signature validation, which includes validation of the referenced objects (e.g. Resources) (a.k.a., Content) in the XML-Signature Detached form.",
"min": 0,
"max": "*",
"type": [
{
"code": "Element"
}
],
"isSummary": true
},
{
"path": "Signature.type",
"short": "Indication of the reason the entity signed the object(s)",
"definition": "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.",
"comments": "Examples include attesting to: authorship, correct transcription, and witness of specific event. Also known as a "Commitment Type Indication".",
"min": 1,
"max": "*",
"type": [
{
"code": "Coding"
}
],
"isSummary": true,
"binding": {
"strength": "preferred",
"description": "An indication of the reason that an entity signed the object",
"valueSetReference": {
"reference": "http://hl7.org/fhir/ValueSet/signature-type"
}
}
},
{
"path": "Signature.when",
"short": "When the signature was created",
"definition": "When the digital signature was signed.",
"comments": "This should agree with the information in the signature.",
"min": 1,
"max": "1",
"type": [
{
"code": "instant"
}
],
"isSummary": true
},
{
"path": "Signature.who[x]",
"short": "Who signed the signature",
"definition": "A reference to an application-usable description of the person that signed the certificate (e.g. the signature used their private key).",
"comments": "This should agree with the information in the signature.",
"min": 1,
"max": "1",
"type": [
{
"code": "uri"
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/Practitioner"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/RelatedPerson"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/Patient"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/Device"
]
},
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/Organization"
]
}
],
"isSummary": true
},
{
"path": "Signature.contentType",
"short": "The technical format of the signature",
"definition": "A mime type that indicates the technical format of the signature. Important mime types are application/signature+xml for X ML DigSig, application/jwt for JWT, and image/* for a graphical image of a signature.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"isSummary": true,
"binding": {
"strength": "required",
"description": "The mime type of an attachment. Any valid mime type is allowed.",
"valueSetUri": "http://www.rfc-editor.org/bcp/bcp13.txt"
}
},
{
"path": "Signature.blob",
"short": "The actual signature content (XML DigSig. JWT, picture, etc.)",
"definition": "The base64 encoding of the Signature content.",
"comments": "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.",
"min": 1,
"max": "1",
"type": [
{
"code": "base64Binary"
}
],
"isSummary": true
}
]
}
}
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.
© HL7.org 2011+. FHIR DSTU2 (v1.2.0-7447) generated on Fri, Dec 11, 2015 17:41+1100.
Links: Search |
Version History |
Table of Contents |
Compare to DSTU1 |
|
Propose a change