HL7 Czech Base and Core Implementation Guide
0.3.0-ballot - ci-build Czechia flag

HL7 Czech Base and Core Implementation Guide, published by HL7 Czech Republic. This guide is not an authorized publication; it is the continuous build for version 0.3.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7-cz/cz-core/ and changes regularly. See the Directory of published versions

Data Type Profile: Signature (CZ)

Official URL: https://fhir.hl7cr.eu/core/StructureDefinition/cz-signature Version: 0.3.0-ballot
Standards status: Draft Maturity Level: 1 Computable Name: CZ_Signature

Czech national profile on Signature holds an electronic representation of a signature or timestamp and its supporting context in a FHIR accessible form.

Usages:

You can also check for usages in the FHIR IG Statistics

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Signature C 0..* Signature Signature according to Czech conventions
Constraints: data-must-be
... type SΣ 1..* Coding Indication of the reason the entity signed the object(s)
Binding: SignatureTypeCodes (preferred): An indication of the reason that an entity signed the object.
... when SΣ 1..1 instant When the signature was created
... who SΣ 1..1 Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Related Person (CZ core) | Device: Performer/Observer (CZ) | Medical Device (CZ) | Organization (CZ core) | Patient (CZ core)) Who signed
... data S 0..1 base64Binary The actual signature content (XML DigSig. JWS, picture, etc.)

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Signature.type Base preferred Signature Type Codes 📍4.0.1 FHIR Std.

Constraints

Id Grade Path(s) Description Expression
data-must-be error Signature Signature must contain data, author and date data.exists() and who.exists() and when.exists()
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())

This structure is derived from Signature

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Signature C 0..* Signature Signature according to Czech conventions
Constraints: data-must-be
... type S 1..* Coding Indication of the reason the entity signed the object(s)
... when S 1..1 instant When the signature was created
... who S 1..1 Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Related Person (CZ core) | Device: Performer/Observer (CZ) | Medical Device (CZ) | Organization (CZ core) | Patient (CZ core)) Who signed
... data S 0..1 base64Binary The actual signature content (XML DigSig. JWS, picture, etc.)

doco Documentation for this format

Constraints

Id Grade Path(s) Description Expression
data-must-be error Signature Signature must contain data, author and date data.exists() and who.exists() and when.exists()
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Signature C 0..* Signature Signature according to Czech conventions
Constraints: data-must-be
... id 0..1 string Unique id for inter-element referencing
... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
... type SΣ 1..* Coding Indication of the reason the entity signed the object(s)
Binding: SignatureTypeCodes (preferred): An indication of the reason that an entity signed the object.
... who SΣ 1..1 Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Related Person (CZ core) | Device: Performer/Observer (CZ) | Medical Device (CZ) | Organization (CZ core) | Patient (CZ core)) Who signed
... onBehalfOf Σ 0..1 Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Related Person (CZ core) | Device: Performer/Observer (CZ) | Medical Device (CZ) | Organization (CZ core)) The party represented
... targetFormat 0..1 code The technical format of the signed resources
Binding: Mime Types (required): The mime type of an attachment. Any valid mime type is allowed.
... sigFormat 0..1 code The technical format of the signature
Binding: Mime Types (required): The mime type of an attachment. Any valid mime type is allowed.
... data S 0..1 base64Binary The actual signature content (XML DigSig. JWS, picture, etc.)

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Signature.type Base preferred Signature Type Codes 📍4.0.1 FHIR Std.
Signature.targetFormat Base required MimeType 📍4.0.1 FHIR Std.
Signature.sigFormat Base required MimeType 📍4.0.1 FHIR Std.

Constraints

Id Grade Path(s) Description Expression
data-must-be error Signature Signature must contain data, author and date data.exists() and who.exists() and when.exists()
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1 error **ALL** extensions Must have either extensions or value[x], not both extension.exists() != value.exists()

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Signature C 0..* Signature Signature according to Czech conventions
Constraints: data-must-be
... type SΣ 1..* Coding Indication of the reason the entity signed the object(s)
Binding: SignatureTypeCodes (preferred): An indication of the reason that an entity signed the object.
... when SΣ 1..1 instant When the signature was created
... who SΣ 1..1 Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Related Person (CZ core) | Device: Performer/Observer (CZ) | Medical Device (CZ) | Organization (CZ core) | Patient (CZ core)) Who signed
... data S 0..1 base64Binary The actual signature content (XML DigSig. JWS, picture, etc.)

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Signature.type Base preferred Signature Type Codes 📍4.0.1 FHIR Std.

Constraints

Id Grade Path(s) Description Expression
data-must-be error Signature Signature must contain data, author and date data.exists() and who.exists() and when.exists()
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())

Differential View

This structure is derived from Signature

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Signature C 0..* Signature Signature according to Czech conventions
Constraints: data-must-be
... type S 1..* Coding Indication of the reason the entity signed the object(s)
... when S 1..1 instant When the signature was created
... who S 1..1 Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Related Person (CZ core) | Device: Performer/Observer (CZ) | Medical Device (CZ) | Organization (CZ core) | Patient (CZ core)) Who signed
... data S 0..1 base64Binary The actual signature content (XML DigSig. JWS, picture, etc.)

doco Documentation for this format

Constraints

Id Grade Path(s) Description Expression
data-must-be error Signature Signature must contain data, author and date data.exists() and who.exists() and when.exists()

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Signature C 0..* Signature Signature according to Czech conventions
Constraints: data-must-be
... id 0..1 string Unique id for inter-element referencing
... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
... type SΣ 1..* Coding Indication of the reason the entity signed the object(s)
Binding: SignatureTypeCodes (preferred): An indication of the reason that an entity signed the object.
... who SΣ 1..1 Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Related Person (CZ core) | Device: Performer/Observer (CZ) | Medical Device (CZ) | Organization (CZ core) | Patient (CZ core)) Who signed
... onBehalfOf Σ 0..1 Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Related Person (CZ core) | Device: Performer/Observer (CZ) | Medical Device (CZ) | Organization (CZ core)) The party represented
... targetFormat 0..1 code The technical format of the signed resources
Binding: Mime Types (required): The mime type of an attachment. Any valid mime type is allowed.
... sigFormat 0..1 code The technical format of the signature
Binding: Mime Types (required): The mime type of an attachment. Any valid mime type is allowed.
... data S 0..1 base64Binary The actual signature content (XML DigSig. JWS, picture, etc.)

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Signature.type Base preferred Signature Type Codes 📍4.0.1 FHIR Std.
Signature.targetFormat Base required MimeType 📍4.0.1 FHIR Std.
Signature.sigFormat Base required MimeType 📍4.0.1 FHIR Std.

Constraints

Id Grade Path(s) Description Expression
data-must-be error Signature Signature must contain data, author and date data.exists() and who.exists() and when.exists()
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1 error **ALL** extensions Must have either extensions or value[x], not both extension.exists() != value.exists()

 

Other representations of profile: CSV, Excel, Schematron