Profile Comparison between http://hl7.org/fhir/uv/ips/StructureDefinition/Composition-uv-ips vs http://hl7.org/fhir/uv/ips/StructureDefinition/Composition-uv-ips

Left:Composition (IPS) (http://hl7.org/fhir/uv/ips/StructureDefinition/Composition-uv-ips)
Right:Composition (IPS) (http://hl7.org/fhir/uv/ips/StructureDefinition/Composition-uv-ips)

Messages

ErrorStructureDefinition.versionValues for version differ: '1.0.0' vs '1.1.0'
InformationStructureDefinition.dateValues for date differ: '2020-05-19T18:37:29+00:00' vs '2022-11-22T03:32:52+00:00'
WarningCompositionElements differ in definition for mustSupport: 'true' vs 'false'
InformationComposition.subjectElement minimum cardinalities differ: '0' vs '1'
WarningComposition.encounterElements differ in definition for mustSupport: 'true' vs 'false'
WarningComposition.confidentialityElements differ in definition for mustSupport: 'true' vs 'false'
WarningComposition.relatesToElements differ in definition for mustSupport: 'true' vs 'false'
WarningComposition.relatesTo.codeElements differ in definition for mustSupport: 'true' vs 'false'
WarningComposition.relatesTo.target[x]Elements differ in definition for mustSupport: 'true' vs 'false'
WarningComposition.eventElements differ in definition: 'The main activity being described by a IPS is the provision of healthcare over a period of time. In the CDA representation of the IPS this is shown by setting the value of serviceEvent/@classCode to “PCPR” (care provision) and indicating the duration over which care was provided in serviceEvent/effectiveTime. In the FHIR representation at lest one event should be used to record this information. Additional data from outside this duration may also be included if it is relevant to care provided during that time range (e.g., reviewed during the stated time range). For example if the IPS is generated by a GP based on information recorded in his/her EHR-S, then the start value should represent the date when the treatment relationship between the patient and the GP started; and the end value the date of the latest care event.' vs 'The main activity being described by a IPS is the provision of healthcare over a period of time. In the CDA representation of the IPS this is shown by setting the value of serviceEvent/@classCode to “PCPR” (care provision) and indicating the duration over which care was provided in serviceEvent/effectiveTime. In the FHIR representation at least one event should be used to record this information. Additional data from outside this duration may also be included if it is relevant to care provided during that time range (e.g., reviewed during the stated time range). For example if the IPS is generated by a GP based on information recorded in his/her EHR-S, then the start value should represent the date when the treatment relationship between the patient and the GP started; and the end value the date of the latest care event.'
WarningComposition.eventElements differ in definition for mustSupport: 'true' vs 'false'
WarningComposition.section.codeElements differ in short: 'Classification of section (recommended)' vs 'Concept - reference to a terminology or just text'
WarningComposition.section.codeElements differ in definition: 'A code identifying the kind of content contained within the section. This must be consistent with the section title.' vs 'A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.'
WarningComposition.section.codeElements differ in comments: 'The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code.' vs 'Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.'
WarningComposition.section.codeElements differ in definition for mustSupport: 'false' vs 'true'
InformationComposition.section.codeElement minimum cardinalities differ: '0' vs '1'
WarningComposition.section.textElements differ in definition for mustSupport: 'false' vs 'true'
InformationComposition.section.textElement minimum cardinalities differ: '0' vs '1'
InformationComposition.section.emptyReasonElement maximum cardinalities differ: '1' vs '0'
InformationComposition.section.sectionElement maximum cardinalities differ: '2147483647' vs '0'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/clinicaldocument
      .copyrightHL7 International
        .date2020-05-19T18:37:29+00:002022-11-22T03:32:52+00:00
        • Values Differ
        .descriptionClinical document used to represent the International Patient Summary (IPS) data set. An International Patient Summary (IPS) document is an electronic health record extract containing essential healthcare information about a subject of care. The IPS dataset is minimal and non-exhaustive; specialty-agnostic and condition-independent; but still clinically relevant. As specified in EN 17269 and ISO/DIS 27269, it is designed for supporting the use case scenario for ‘unplanned, cross border care’, but it is not limited to it. It is intended to be international, i.e., to provide generic solutions for global application beyond a particular region or country. This profile is based on the ClinicalDocument profile.Clinical document used to represent the International Patient Summary (IPS) data set. An International Patient Summary (IPS) document is an electronic health record extract containing essential healthcare information about a subject of care. The IPS dataset is minimal and non-exhaustive; specialty-agnostic and condition-independent; but still clinically relevant. As specified in EN 17269 and ISO 27269, it is designed for supporting the use case scenario for ‘unplanned, cross border care’, but it is not limited to it. It is intended to be international, i.e., to provide generic solutions for global application beyond a particular region or country. This profile is based on the ClinicalDocument profile.
        • Values Differ
        .experimental
          .fhirVersion4.0.1
            .jurisdiction
              ..jurisdiction[0]http://unstats.un.org/unsd/methods/m49/m49.htm#001
                .kindresource
                  .nameCompositionUvIps
                    .publisherHealth Level Seven International - Patient Care Work Group
                      .purposeAn International Patient Summary (IPS) document is an electronic health record extract containing essential healthcare information about a subject of care, comprising at least the required elements of the IPS dataset. The IPS dataset is minimal and non-exhaustive; specialty-agnostic and condition-independent; but still clinically relevant. As specified in EN 17269 and ISO/DIS 27269, it is designed for supporting the use case scenario for ‘unplanned, cross border care’, but it is not limited to it. It is intended to be international, i.e., to provide generic solutions for global application beyond a particular region or country.An International Patient Summary (IPS) document is an electronic health record extract containing essential healthcare information about a subject of care, comprising at least the required elements of the IPS dataset. The IPS dataset is minimal and non-exhaustive; specialty-agnostic and condition-independent; but still clinically relevant. As specified in EN 17269 and ISO 27269, it is designed for supporting the use case scenario for ‘unplanned, cross border care’, but it is not limited to it. It is intended to be international, i.e., to provide generic solutions for global application beyond a particular region or country.
                      • Values Differ
                      .statusactive
                        .titleComposition (IPS)
                          .typeComposition
                            .urlhttp://hl7.org/fhir/uv/ips/StructureDefinition/Composition-uv-ips
                              .version1.0.01.1.0
                              • Values Differ

                              Structure

                              NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                              .. Composition S0..*Clinical DocumentInternational Patient Summary composition
                              0..*Clinical DocumentInternational Patient Summary composition
                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                              ... id Σ0..1stringLogical id of this artifactΣ0..1idLogical id of this artifact
                                ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                                  ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                                    ... text S0..1NarrativeText summary of the resource, for human interpretationS0..1NarrativeText summary of the resource, for human interpretation
                                      ... contained 0..*ResourceContained, inline Resources
                                      0..*ResourceContained, inline Resources
                                        ... Slices for extension 0..*ExtensionExtension
                                        Slice: Unordered, Open by value:url
                                        0..*ExtensionExtension
                                        Slice: Unordered, Open by value:url
                                          ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                                          ?!0..*ExtensionExtensions that cannot be ignored
                                            ... identifier SΣ0..1IdentifierVersion-independent identifier for the CompositionSΣ0..1IdentifierVersion-independent identifier for the Composition
                                              ... status ?!SΣ1..1codepreliminary | final | amended | entered-in-error
                                              Binding: CompositionStatus (required): The workflow/clinical status of the composition.

                                              ?!SΣ1..1codepreliminary | final | amended | entered-in-error
                                              Binding: CompositionStatus (required): The workflow/clinical status of the composition.

                                                ... type S1..1?pkp-2?Kind of composition ("Patient Summary")
                                                Binding: FHIRDocumentTypeCodes (preferred): Type of a composition.


                                                Required Pattern: {"coding":[{"system":"http://loinc.org","code":"60591-5"}]}
                                                S1..1CodeableConceptIPSKind of composition ("Patient Summary")
                                                Binding: FHIRDocumentTypeCodes (preferred): Type of a composition.


                                                Required Pattern: {"coding":[{"system":"http://loinc.org","code":"60591-5"}]}
                                                  ... category Σ0..*CodeableConceptCategorization of Composition
                                                  Binding: DocumentClassValueSet (example): High-level kind of a clinical document at a macro level.


                                                  Σ0..*CodeableConceptCategorization of Composition
                                                  Binding: DocumentClassValueSet (example): High-level kind of a clinical document at a macro level.


                                                    ... subject SΣ0..1Reference(Patient (IPS))Who and/or what the composition is aboutSΣ1..1Reference(Patient (IPS))Who and/or what the composition is about
                                                    • Element minimum cardinalities differ: '0' vs '1'
                                                    .... 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
                                                        .... reference SΣC1..1stringLiteral reference, Relative, internal or absolute URLSΣC1..1stringLiteral reference, Relative, internal or absolute URL
                                                          .... type Σ0..1uriType the reference refers to (e.g. "Patient")
                                                          Binding: ResourceType (extensible): Aa resource (or, for logical models, the URI of the logical model).

                                                          Σ0..1uriType the reference refers to (e.g. "Patient")
                                                          Binding: ResourceType (extensible): Aa resource (or, for logical models, the URI of the logical model).

                                                            .... identifier Σ0..1IdentifierLogical reference, when literal reference is not knownΣ0..1IdentifierLogical reference, when literal reference is not known
                                                              .... display Σ0..1stringText alternative for the resourceΣ0..1stringText alternative for the resource
                                                                ... encounter SΣ0..1Reference(Encounter)Context of the CompositionΣ0..1Reference(Encounter)Context of the Composition
                                                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                ... date SΣ1..1dateTimeComposition editing timeSΣ1..1dateTimeComposition editing time
                                                                  ... author SΣ1..*Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)Who and/or what authored the IPS
                                                                  SΣ1..*Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)Who and/or what authored the IPS
                                                                    ... title SΣ1..1stringInternational Patient SummarySΣ1..1stringInternational Patient Summary
                                                                      ... confidentiality SΣ0..1codeAs defined by affinity domain
                                                                      Binding: v3.ConfidentialityClassification (2014-03-26) (required): Codes specifying the level of confidentiality of the composition.

                                                                      Σ0..1codeAs defined by affinity domain
                                                                      Binding: v3.ConfidentialityClassification (2014-03-26) (required): Codes specifying the level of confidentiality of the composition.

                                                                      • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                      ... attester S0..*BackboneElementAttests to accuracy of composition
                                                                      S0..*BackboneElementAttests to accuracy of composition
                                                                        .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                          .... extension 0..*ExtensionAdditional content defined by implementations
                                                                          0..*ExtensionAdditional content defined by implementations
                                                                            .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                            ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                              .... mode S1..1codepersonal | professional | legal | official
                                                                              Binding: CompositionAttestationMode (required): The way in which a person authenticated a composition.

                                                                              S1..1codepersonal | professional | legal | official
                                                                              Binding: CompositionAttestationMode (required): The way in which a person authenticated a composition.

                                                                                .... time S0..1dateTimeWhen the composition was attestedS0..1dateTimeWhen the composition was attested
                                                                                  .... party S0..1Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization)Who attested the compositionS0..1Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization)Who attested the composition
                                                                                    ... custodian SΣ0..1Reference(Organization)Organization which maintains the compositionSΣ0..1Reference(Organization)Organization which maintains the composition
                                                                                      ... relatesTo S0..*BackboneElementRelationships to other compositions/documents
                                                                                      0..*BackboneElementRelationships to other compositions/documents
                                                                                      • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                      .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                        .... extension 0..*ExtensionAdditional content defined by implementations
                                                                                        0..*ExtensionAdditional content defined by implementations
                                                                                          .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                          ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                            .... code S1..1codereplaces | transforms | signs | appends
                                                                                            Binding: DocumentRelationshipType (required): The type of relationship between documents.

                                                                                            1..1codereplaces | transforms | signs | appends
                                                                                            Binding: DocumentRelationshipType (required): The type of relationship between documents.

                                                                                            • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                            .... target[x] S1..1Identifier, Reference(Composition | Composition (IPS))Target of the relationship1..1Identifier, Reference(Composition | Composition (IPS))Target of the relationship
                                                                                            • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                            ... Slices for event SΣ0..*BackboneElementThe clinical service(s) being documented
                                                                                            Slice: Unordered, Open by pattern:code
                                                                                            Σ0..*BackboneElementThe clinical service(s) being documented
                                                                                            Slice: Unordered, Open by pattern:code
                                                                                            • Elements differ in definition: 'The main activity being described by a IPS is the provision of healthcare over a period of time. In the CDA representation of the IPS this is shown by setting the value of serviceEvent/@classCode to “PCPR” (care provision) and indicating the duration over which care was provided in serviceEvent/effectiveTime. In the FHIR representation at lest one event should be used to record this information. Additional data from outside this duration may also be included if it is relevant to care provided during that time range (e.g., reviewed during the stated time range). For example if the IPS is generated by a GP based on information recorded in his/her EHR-S, then the start value should represent the date when the treatment relationship between the patient and the GP started; and the end value the date of the latest care event.' vs 'The main activity being described by a IPS is the provision of healthcare over a period of time. In the CDA representation of the IPS this is shown by setting the value of serviceEvent/@classCode to “PCPR” (care provision) and indicating the duration over which care was provided in serviceEvent/effectiveTime. In the FHIR representation at least one event should be used to record this information. Additional data from outside this duration may also be included if it is relevant to care provided during that time range (e.g., reviewed during the stated time range). For example if the IPS is generated by a GP based on information recorded in his/her EHR-S, then the start value should represent the date when the treatment relationship between the patient and the GP started; and the end value the date of the latest care event.'
                                                                                            • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                            .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                              .... extension 0..*ExtensionAdditional content defined by implementations
                                                                                              0..*ExtensionAdditional content defined by implementations
                                                                                                .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                  .... code Σ0..*CodeableConceptCode(s) that apply to the event being documented
                                                                                                  Binding: v3 Code System ActCode (example): This list of codes represents the main clinical acts being documented.


                                                                                                  Σ0..*CodeableConceptCode(s) that apply to the event being documented
                                                                                                  Binding: v3 Code System ActCode (example): This list of codes represents the main clinical acts being documented.


                                                                                                    .... period Σ0..1PeriodThe period covered by the documentationΣ0..1PeriodThe period covered by the documentation
                                                                                                      .... detail Σ0..*Reference(Resource)The event(s) being documented
                                                                                                      Σ0..*Reference(Resource)The event(s) being documented
                                                                                                        ... Slices for section SC1..*BackboneElementSections composing the IPS
                                                                                                        Slice: Unordered, Open by pattern:code
                                                                                                        SC1..*BackboneElementSections composing the IPS
                                                                                                        Slice: Unordered, Open by pattern:code
                                                                                                          .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                            .... extension 0..*ExtensionAdditional content defined by implementations
                                                                                                            0..*ExtensionAdditional content defined by implementations
                                                                                                              .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                              ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                                .... title 0..1stringLabel for section (e.g. for ToC)0..1stringLabel for section (e.g. for ToC)
                                                                                                                  .... code 0..1CodeableConceptClassification of section (recommended)
                                                                                                                  Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.

                                                                                                                  S1..1CodeableConceptIPSConcept - reference to a terminology or just text
                                                                                                                  Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.

                                                                                                                  • Elements differ in short: 'Classification of section (recommended)' vs 'Concept - reference to a terminology or just text'
                                                                                                                  • Elements differ in definition: 'A code identifying the kind of content contained within the section. This must be consistent with the section title.' vs 'A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.'
                                                                                                                  • Elements differ in comments: 'The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code.' vs 'Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.'
                                                                                                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                                                  • Element minimum cardinalities differ: '0' vs '1'
                                                                                                                  .... author 0..*Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)Who and/or what authored the section
                                                                                                                  0..*Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)Who and/or what authored the section
                                                                                                                    .... focus 0..1Reference(Resource)Who/what the section is about, when it is not about the subject of composition0..1Reference(Resource)Who/what the section is about, when it is not about the subject of composition
                                                                                                                      .... text C0..1NarrativeText summary of the section, for human interpretationSC1..1NarrativeText summary of the section, for human interpretation
                                                                                                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                                                      • Element minimum cardinalities differ: '0' vs '1'
                                                                                                                      .... mode 0..1codeworking | snapshot | changes
                                                                                                                      Binding: ListMode (required): The processing mode that applies to this section.

                                                                                                                      0..1codeworking | snapshot | changes
                                                                                                                      Binding: ListMode (required): The processing mode that applies to this section.

                                                                                                                        .... orderedBy 0..1CodeableConceptOrder of section entries
                                                                                                                        Binding: ListOrderCodes (preferred): What order applies to the items in the entry.

                                                                                                                        0..1CodeableConceptOrder of section entries
                                                                                                                        Binding: ListOrderCodes (preferred): What order applies to the items in the entry.

                                                                                                                          .... entry C0..*Reference(Resource)A reference to data that supports this section
                                                                                                                          C0..*Reference(Resource)A reference to data that supports this section
                                                                                                                            .... emptyReason C0..1CodeableConceptWhy the section is empty
                                                                                                                            Binding: ListEmptyReasons (preferred): If a section is empty, why it is empty.

                                                                                                                            C0..0
                                                                                                                            • Element maximum cardinalities differ: '1' vs '0'
                                                                                                                            .... section C0..*See sectionNested Section
                                                                                                                            C0..0
                                                                                                                            • Element maximum cardinalities differ: '2147483647' vs '0'

                                                                                                                            doco Documentation for this format