Profile Comparison between https://hl7.cz/fhir/core/StructureDefinition/cz-signature vs https://hl7.cz/fhir/core/StructureDefinition/cz-signature

Left:Signature (CZ core) (https://hl7.cz/fhir/core/StructureDefinition/cz-signature)
Right:Signature (CZ core) (https://hl7.cz/fhir/core/StructureDefinition/cz-signature)

Messages

ErrorStructureDefinition.versionValues for version differ: '0.3.0' vs '0.4.0'
InformationStructureDefinition.dateValues for date differ: '2026-03-06T09:02:49+01:00' vs '2026-05-18T07:26:58+00:00'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Signature
      .copyright
        .date2026-03-06T09:02:49+01:002026-05-18T07:26:58+00:00
        • Values Differ
        .descriptionCzech national profile on Signature holds an electronic representation of a signature or timestamp and its supporting context in a FHIR accessible form.
          .experimentalfalse
            .fhirVersion4.0.1
              .jurisdiction
                ..jurisdiction[0]urn:iso:std:iso:3166#CZ
                  .kindcomplex-type
                    .nameCZ_Signature
                      .publisherHL7 Czech Republic
                        .purpose
                          .statusactive
                            .titleSignature (CZ core)
                              .typeSignature
                                .urlhttps://hl7.cz/fhir/core/StructureDefinition/cz-signature
                                  .version0.3.00.4.0
                                  • Values Differ

                                  Structure

                                  NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                                  .. Signature C0..*SignatureSignature according to Czech conventions
                                  Constraints: data-must-be
                                  C0..*SignatureSignature according to Czech conventions
                                  Constraints: data-must-be
                                    ... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                      ... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                      Slice: Unordered, Open by value:url
                                      0..*ExtensionAdditional content defined by implementations
                                      Slice: Unordered, Open by value:url
                                        ... type SΣ1..*CodingIndication of the reason the entity signed the object(s)
                                        Binding: ?? (preferred): An indication of the reason that an entity signed the object.
                                        SΣ1..*CodingIndication of the reason the entity signed the object(s)
                                        Binding: ?? (preferred): An indication of the reason that an entity signed the object.
                                          ... who SΣ1..1Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Related Person (CZ core) | Device: Performer/Observer (CZ core) | Medical Device (CZ core) | Organization (CZ core) | Patient (CZ core))Who signedSΣ1..1Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Related Person (CZ core) | Device: Performer/Observer (CZ core) | Medical Device (CZ core) | Organization (CZ core) | Patient (CZ core))Who signed
                                            ... onBehalfOf Σ0..1Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Related Person (CZ core) | Device: Performer/Observer (CZ core) | Medical Device (CZ core) | Organization (CZ core))The party representedΣ0..1Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Related Person (CZ core) | Device: Performer/Observer (CZ core) | Medical Device (CZ core) | Organization (CZ core))The party represented
                                              ... targetFormat 0..1codeThe technical format of the signed resources
                                              Binding: ?? (required): The mime type of an attachment. Any valid mime type is allowed.
                                              0..1codeThe technical format of the signed resources
                                              Binding: ?? (required): The mime type of an attachment. Any valid mime type is allowed.
                                                ... sigFormat 0..1codeThe technical format of the signature
                                                Binding: ?? (required): The mime type of an attachment. Any valid mime type is allowed.
                                                0..1codeThe technical format of the signature
                                                Binding: ?? (required): The mime type of an attachment. Any valid mime type is allowed.
                                                  ... data S0..1base64BinaryThe actual signature content (XML DigSig. JWS, picture, etc.)S0..1base64BinaryThe actual signature content (XML DigSig. JWS, picture, etc.)

                                                    doco Documentation for this format