SD's Project | Signature - SIMPLIFIER.NET

Signature			Element	Element id Signature Short description A Signature - XML DigSig, JWS, Graphical image of signature, etc. Definition 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. Comments The elements of the Signature Resource are for ease of access of these elements. For digital signatures (Xml DigSig, JWS), 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. Data type Element Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
id		0..1		There are no (further) constraints on this element Element id Signature.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Mappings rim: n/a
extension		0..*	Extension	There are no (further) constraints on this element Element id Signature.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings rim: n/a
type	Σ	1..*	CodingBinding	Element id Signature.type Short description 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". Data type Coding Binding An indication of the reason that an entity signed the object. SignatureTypeCodes (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding
when	Σ	1..1	instant	Element id Signature.when Short description When the signature was created Definition When the digital signature was signed. Comments This should agree with the information in the signature. Data type instant Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
who	Σ I	1..1	Reference(Practitioner \| PractitionerRole \| RelatedPerson \| Patient \| Device \| Organization)	Element id Signature.who Short description Who signed Definition A reference to an application-usable description of the identity that signed (e.g. the signature used their private key). Comments This should agree with the information in the signature. Data type Reference(Practitioner \| PractitionerRole \| RelatedPerson \| Patient \| Device \| Organization) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %resource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity)
onBehalfOf	Σ I	0..1	Reference(Practitioner \| PractitionerRole \| RelatedPerson \| Patient \| Device \| Organization)	Element id Signature.onBehalfOf Short description The party represented Definition A reference to an application-usable description of the identity that is represented by the signature. Requirements used when the signature is on behalf of a non-signer. Comments The party that can't sign. For example a child. Data type Reference(Practitioner \| PractitionerRole \| RelatedPerson \| Patient \| Device \| Organization) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %resource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity)
targetFormat		0..1	codeBinding	Element id Signature.targetFormat Short description The technical format of the signed resources Definition A mime type that indicates the technical format of the target resources signed by the signature. Comments "xml", "json" and "ttl" are allowed, which describe the simple encodings described in the specification (and imply appropriate bundle support). Otherwise, mime types are legal here. Data type code Binding The mime type of an attachment. Any valid mime type is allowed. Mime Types (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
sigFormat		0..1	codeBinding	Element id Signature.sigFormat Short description 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/jose for JWS, and image/* for a graphical image of a signature, etc. Data type code Binding The mime type of an attachment. Any valid mime type is allowed. Mime Types (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
data		0..1	base64Binary	Element id Signature.data Short description The actual signature content (XML DigSig. JWS, picture, etc.) Definition The base64 encoding of the Signature content. When signature is not recorded electronically this element would be empty. 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. Data type base64Binary Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`

Documentation:

https://simplifier.net/sdsproject/signature

Last updated on 9/13/2019, 12:08:58 PM