Profile Comparison between https://www.ehealth.fgov.be/standards/fhir/allergy/StructureDefinition/be-allergyintolerance vs https://www.ehealth.fgov.be/standards/fhir/allergy/StructureDefinition/be-allergyintolerance

Left:BeAllergyIntolerance (https://www.ehealth.fgov.be/standards/fhir/allergy/StructureDefinition/be-allergyintolerance)
Right:BeAllergyIntolerance (https://www.ehealth.fgov.be/standards/fhir/allergy/StructureDefinition/be-allergyintolerance)

Messages

ErrorStructureDefinition.versionValues for version differ: '1.0.0' vs '1.0.1'
InformationStructureDefinition.dateValues for date differ: '2022-06-07T10:36:44+02:00' vs '2022-09-13T17:51:47+02:00'
WarningAllergyIntolerance.identifierElements differ in definition for mustSupport: 'false' vs 'true'
WarningAllergyIntolerance.clinicalStatusElements differ in definition: 'The clinical status of the allergy or intolerance. When available, a provider SHOULD include it. When given, a consumer SHALL record this in its consuming system.' vs 'The clinical status of the allergy or intolerance. When available, a provider SHOULD include it. When given, a consumer SHALL record this in its consuming system. Use 'resolved' only in case of pediatric allergies, in case of complete recovery, use 'inactive' in case of longlasting tolerance after a desensitisation treatment'
WarningAllergyIntolerance.codeElements differ in short: 'Code that identifies the allergy or intolerance' vs 'Use ATC, CNK or CTI-extended in case of medication allergy'
WarningAllergyIntolerance.codeElements differ in definition: 'Code for an allergy or intolerance statement (either a positive or a negated/excluded statement). This may be a code for a substance or pharmaceutical product that is considered to be responsible for the adverse reaction risk (e.g., 'Latex'), an allergy or intolerance condition (e.g., 'Latex allergy'), or a negated/excluded code for a specific substance or class (e.g., 'No latex allergy') or a general or categorical negated statement (e.g., 'No known allergy', 'No known drug allergies'). Note: the substance for a specific reaction may be different from the substance identified as the cause of the risk, but it must be consistent with it. For instance, it may be a more specific substance (e.g. a brand medication) or a composite product that includes the identified substance. It must be clinically safe to only process the 'code' and ignore the 'reaction.substance'. If a receiving system is unable to confirm that AllergyIntolerance.reaction.substance falls within the semantic scope of AllergyIntolerance.code, then the receiving system should ignore AllergyIntolerance.reaction.substance. A provider SHALL include it in the istance and a consumer SHALL record this in its consuming system. If needed codes can be used outside the given valueset, SNOMED-CT is preferred.' vs 'Code for an allergy or intolerance statement. This may be a code for a substance or pharmaceutical product that is considered to be responsible for the adverse reaction risk (e.g., 'Latex'), an allergy or intolerance condition (e.g., 'Latex allergy'), or a general or categorical negated statement (e.g., 'No known allergy'). Note: the substance for a specific reaction may be different from the substance identified as the cause of the risk, but it must be consistent with it. For instance, it may be a more specific substance (e.g. a brand medication) or a composite product that includes the identified substance. It must be clinically safe to only process the 'code' and ignore the 'reaction.substance'. If a receiving system is unable to confirm that AllergyIntolerance.reaction.substance falls within the semantic scope of AllergyIntolerance.code, then the receiving system should ignore AllergyIntolerance.reaction.substance. A provider SHALL include it in the instance and a consumer SHALL record this in its consuming system. Medication related allergies or intolerances will be registered using the CNK, ATC or CTI-extended namingsystem.'
WarningAllergyIntolerance.codeElements differ in comments: 'It is strongly recommended that this element be populated using a terminology, where possible. For example, some terminologies used include RxNorm, SNOMED CT, DM+D, NDFRT, ICD-9, IDC-10, UNII, and ATC. Plain text should only be used if there is no appropriate terminology available. Additional details can be specified in the text. When a substance or product code is specified for the 'code' element, the 'default' semantic context is that this is a positive statement of an allergy or intolerance (depending on the value of the 'type' element, if present) condition to the specified substance/product. In the corresponding SNOMED CT allergy model, the specified substance/product is the target (destination) of the 'Causative agent' relationship. The 'substanceExposureRisk' extension is available as a structured and more flexible alternative to the 'code' element for making positive or negative allergy or intolerance statements. This extension provides the capability to make 'no known allergy' (or 'no risk of adverse reaction') statements regarding any coded substance/product (including cases when a pre-coordinated 'no allergy to x' concept for that substance/product does not exist). If the 'substanceExposureRisk' extension is present, the AllergyIntolerance.code element SHALL be omitted.' vs 'Code for an allergy or intolerance statement. This may be a code for a substance or pharmaceutical product that is considered to be responsible for the adverse reaction risk (e.g., 'Latex'), an allergy or intolerance condition (e.g., 'Latex allergy'), or a general or categorical negated statement (e.g., 'No known allergy'). Note: the substance for a specific reaction may be different from the substance identified as the cause of the risk, but it must be consistent with it. For instance, it may be a more specific substance (e.g. a brand medication) or a composite product that includes the identified substance. It must be clinically safe to only process the 'code' and ignore the 'reaction.substance'. If a receiving system is unable to confirm that AllergyIntolerance.reaction.substance falls within the semantic scope of AllergyIntolerance.code, then the receiving system should ignore AllergyIntolerance.reaction.substance. A provider SHALL include it in the instance and a consumer SHALL record this in its consuming system. Medication related allergies or intolerances will be registered using the CNK, ATC or CTI-extended namingsystem.'
ErrorAllergyIntolerance.patientType Mismatch: Reference([CanonicalType[https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-patient]]) vs Reference([CanonicalType[https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-patient]])
WarningAllergyIntolerance.recorderElements differ in definition: 'Individual who recorded the record and takes responsibility for its content. A provider SHALL include it in the istance and a consumer SHALL record this in its consuming system.' vs 'Individual who takes responsibility for the content of the record. BePatient is added to allow a patient to record his/her own allergies. Organisations can be a recorder, using a PractitionerRole, but the you SHALL add a BePractioner who is responsable for the organisation. A provider SHALL include it in the instance and a consumer SHALL record this in its consuming system.'
WarningAllergyIntolerance.asserterElements differ in definition: 'The source of the information about the allergy that is recorded. When available, a provider SHOULD include it in the istance. When given, a consumer SHALL record this in its consuming system.' vs 'The source of the information about the allergy that is recorded. When available, a provider SHOULD include it in the instance. When given, a consumer SHALL record this in its consuming system.'
InformationAllergyIntolerance.reaction.manifestationElement maximum cardinalities differ: '2147483647' vs '1'
WarningAllergyIntolerance.reaction.onsetElements differ in definition for mustSupport: 'false' vs 'true'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/AllergyIntolerance
      .copyright
        .date2022-06-07T10:36:44+02:002022-09-13T17:51:47+02:00
        • Values Differ
        .descriptionBelgian federal profile for an allergy and/or an intolerance. Initially based on the functional description of the NIHDI.
          .experimental
            .fhirVersion4.0.1
              .jurisdiction
                ..jurisdiction[0]urn:iso:std:iso:3166#BE
                  .kindresource
                    .nameBeAllergyIntolerance
                      .publishereHealth Platform
                        .purpose
                          .statusactive
                            .title
                              .typeAllergyIntolerance
                                .urlhttps://www.ehealth.fgov.be/standards/fhir/allergy/StructureDefinition/be-allergyintolerance
                                  .version1.0.01.0.1
                                  • Values Differ

                                  Structure

                                  NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                                  .. AllergyIntolerance I0..*AllergyIntoleranceAllergy or Intolerance (generally: Risk of adverse reaction to a substance)
                                  I0..*AllergyIntoleranceAllergy or Intolerance (generally: Risk of adverse reaction to a substance)
                                  be-inv-asserter-person-rel-type: Checks that the person relationship type of the RelatedPerson in asserter is from BeVSPatientRelationshipType
                                    ... id Σ0..1stringLogical id of this artifactΣ0..1stringLogical 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 0..1NarrativeText summary of the resource, for human interpretation0..1NarrativeText summary of the resource, for human interpretation
                                            ... contained 0..*ResourceContained, inline Resources
                                            0..*ResourceContained, inline Resources
                                              ... extension 0..*ExtensionAdditional content defined by implementations
                                              0..*ExtensionAdditional content defined by implementations
                                                ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                                                ?!0..*ExtensionExtensions that cannot be ignored
                                                  ... identifier Σ0..*IdentifierExternal ids for this item
                                                  SΣ0..*IdentifierExternal ids for this item
                                                  Slice: Unordered, Open by value:system
                                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                  ... clinicalStatus ?!SΣI0..1CodeableConceptactive | inactive | resolved
                                                  Binding: todo (required): The clinical status of the allergy or intolerance.

                                                  ?!SΣI0..1CodeableConceptactive | inactive | resolved
                                                  Binding: AllergyIntoleranceClinicalStatusCodes (required): The clinical status of the allergy or intolerance.

                                                  • Elements differ in definition: 'The clinical status of the allergy or intolerance. When available, a provider SHOULD include it. When given, a consumer SHALL record this in its consuming system.' vs 'The clinical status of the allergy or intolerance. When available, a provider SHOULD include it. When given, a consumer SHALL record this in its consuming system. Use 'resolved' only in case of pediatric allergies, in case of complete recovery, use 'inactive' in case of longlasting tolerance after a desensitisation treatment'
                                                  ... verificationStatus ?!SΣI0..1CodeableConceptunconfirmed | confirmed | refuted | entered-in-error
                                                  Binding: todo (required): Assertion about certainty associated with a propensity, or potential risk, of a reaction to the identified substance.

                                                  ?!SΣI0..1CodeableConceptunconfirmed | confirmed | refuted | entered-in-error
                                                  Binding: AllergyIntoleranceVerificationStatusCodes (required): Assertion about certainty associated with a propensity, or potential risk, of a reaction to the identified substance.

                                                    ... type SΣ0..1codeallergy | intolerance - Underlying mechanism (if known)
                                                    Binding: todo (required): Identification of the underlying physiological mechanism for a Reaction Risk.

                                                    SΣ0..1codeallergy | intolerance - Underlying mechanism (if known)
                                                    Binding: AllergyIntoleranceType (required): Identification of the underlying physiological mechanism for a Reaction Risk.

                                                      ... category SΣ0..*codefood | medication | environment | biologic
                                                      Binding: todo (required): Category of an identified substance associated with allergies or intolerances.


                                                      SΣ0..*codefood | medication | environment | biologic
                                                      Binding: AllergyIntoleranceCategory (required): Category of an identified substance associated with allergies or intolerances.


                                                        ... criticality Σ0..1codelow | high | unable-to-assess
                                                        Binding: todo (required): Estimate of the potential clinical harm, or seriousness, of a reaction to an identified substance.

                                                        Σ0..1codelow | high | unable-to-assess
                                                        Binding: AllergyIntoleranceCriticality (required): Estimate of the potential clinical harm, or seriousness, of a reaction to an identified substance.

                                                          ... code SΣ1..1CodeableConceptCode that identifies the allergy or intolerance
                                                          Binding: todo (extensible): Causative agent codes as defined by NIHDI

                                                          SΣ1..1CodeableConceptUse ATC, CNK or CTI-extended in case of medication allergy
                                                          Binding: BeAllergyIntoleranceCode (extensible): Causative agent codes as defined by NIHDI

                                                          • Elements differ in short: 'Code that identifies the allergy or intolerance' vs 'Use ATC, CNK or CTI-extended in case of medication allergy'
                                                          • Elements differ in definition: 'Code for an allergy or intolerance statement (either a positive or a negated/excluded statement). This may be a code for a substance or pharmaceutical product that is considered to be responsible for the adverse reaction risk (e.g., "Latex"), an allergy or intolerance condition (e.g., "Latex allergy"), or a negated/excluded code for a specific substance or class (e.g., "No latex allergy") or a general or categorical negated statement (e.g., "No known allergy", "No known drug allergies"). Note: the substance for a specific reaction may be different from the substance identified as the cause of the risk, but it must be consistent with it. For instance, it may be a more specific substance (e.g. a brand medication) or a composite product that includes the identified substance. It must be clinically safe to only process the 'code' and ignore the 'reaction.substance'. If a receiving system is unable to confirm that AllergyIntolerance.reaction.substance falls within the semantic scope of AllergyIntolerance.code, then the receiving system should ignore AllergyIntolerance.reaction.substance. A provider SHALL include it in the istance and a consumer SHALL record this in its consuming system. If needed codes can be used outside the given valueset, SNOMED-CT is preferred.' vs 'Code for an allergy or intolerance statement. This may be a code for a substance or pharmaceutical product that is considered to be responsible for the adverse reaction risk (e.g., "Latex"), an allergy or intolerance condition (e.g., "Latex allergy"), or a general or categorical negated statement (e.g., "No known allergy"). Note: the substance for a specific reaction may be different from the substance identified as the cause of the risk, but it must be consistent with it. For instance, it may be a more specific substance (e.g. a brand medication) or a composite product that includes the identified substance. It must be clinically safe to only process the 'code' and ignore the 'reaction.substance'. If a receiving system is unable to confirm that AllergyIntolerance.reaction.substance falls within the semantic scope of AllergyIntolerance.code, then the receiving system should ignore AllergyIntolerance.reaction.substance. A provider SHALL include it in the instance and a consumer SHALL record this in its consuming system. Medication related allergies or intolerances will be registered using the CNK, ATC or CTI-extended namingsystem.'
                                                          • Elements differ in comments: 'It is strongly recommended that this element be populated using a terminology, where possible. For example, some terminologies used include RxNorm, SNOMED CT, DM+D, NDFRT, ICD-9, IDC-10, UNII, and ATC. Plain text should only be used if there is no appropriate terminology available. Additional details can be specified in the text. When a substance or product code is specified for the 'code' element, the "default" semantic context is that this is a positive statement of an allergy or intolerance (depending on the value of the 'type' element, if present) condition to the specified substance/product. In the corresponding SNOMED CT allergy model, the specified substance/product is the target (destination) of the "Causative agent" relationship. The 'substanceExposureRisk' extension is available as a structured and more flexible alternative to the 'code' element for making positive or negative allergy or intolerance statements. This extension provides the capability to make "no known allergy" (or "no risk of adverse reaction") statements regarding any coded substance/product (including cases when a pre-coordinated "no allergy to x" concept for that substance/product does not exist). If the 'substanceExposureRisk' extension is present, the AllergyIntolerance.code element SHALL be omitted.' vs 'Code for an allergy or intolerance statement. This may be a code for a substance or pharmaceutical product that is considered to be responsible for the adverse reaction risk (e.g., "Latex"), an allergy or intolerance condition (e.g., "Latex allergy"), or a general or categorical negated statement (e.g., "No known allergy"). Note: the substance for a specific reaction may be different from the substance identified as the cause of the risk, but it must be consistent with it. For instance, it may be a more specific substance (e.g. a brand medication) or a composite product that includes the identified substance. It must be clinically safe to only process the 'code' and ignore the 'reaction.substance'. If a receiving system is unable to confirm that AllergyIntolerance.reaction.substance falls within the semantic scope of AllergyIntolerance.code, then the receiving system should ignore AllergyIntolerance.reaction.substance. A provider SHALL include it in the instance and a consumer SHALL record this in its consuming system. Medication related allergies or intolerances will be registered using the CNK, ATC or CTI-extended namingsystem.'
                                                          ... patient SΣ1..1Reference(https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-patient)Who the sensitivity is forSΣ1..1Reference(BePatient)Who the sensitivity is for
                                                          • Type Mismatch: Reference([CanonicalType[https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-patient]]) vs Reference([CanonicalType[https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-patient]])
                                                          ... encounter 0..1Reference(Encounter)Encounter when the allergy or intolerance was asserted0..1Reference(Encounter)Encounter when the allergy or intolerance was asserted
                                                            ... onset[x] 0..1dateTime, Age, Period, Range, stringWhen allergy or intolerance was identified0..1dateTime, Age, Period, Range, stringWhen allergy or intolerance was identified
                                                              ... recordedDate S1..1dateTimeDate first version of the resource instance was recordedS1..1dateTimeDate first version of the resource instance was recorded
                                                                ... recorder S1..1Reference(Practitioner | PractitionerRole | Patient | RelatedPerson | https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-patient | https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-practitioner | https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-practitionerrole)Who recorded the sensitivityS1..1Reference(BePractitioner | BePractitionerRole | BePatient)Who recorded the sensitivity
                                                                • Elements differ in definition: 'Individual who recorded the record and takes responsibility for its content. A provider SHALL include it in the istance and a consumer SHALL record this in its consuming system.' vs 'Individual who takes responsibility for the content of the record. BePatient is added to allow a patient to record his/her own allergies. Organisations can be a recorder, using a PractitionerRole, but the you SHALL add a BePractioner who is responsable for the organisation. A provider SHALL include it in the instance and a consumer SHALL record this in its consuming system.'
                                                                ... asserter SΣ0..1Reference(Patient | RelatedPerson | Practitioner | PractitionerRole)Source of the information about the allergySΣ0..1Reference(Patient | RelatedPerson | Practitioner | PractitionerRole)Source of the information about the allergy
                                                                • Elements differ in definition: 'The source of the information about the allergy that is recorded. When available, a provider SHOULD include it in the istance. When given, a consumer SHALL record this in its consuming system.' vs 'The source of the information about the allergy that is recorded. When available, a provider SHOULD include it in the instance. When given, a consumer SHALL record this in its consuming system.'
                                                                ... lastOccurrence 0..1dateTimeDate(/time) of last known occurrence of a reaction0..1dateTimeDate(/time) of last known occurrence of a reaction
                                                                  ... note S0..*AnnotationAdditional text not captured in other fields
                                                                  S0..*AnnotationAdditional text not captured in other fields
                                                                    ... reaction S0..*BackboneElementAdverse Reaction Events linked to exposure to substance
                                                                    S0..*BackboneElementAdverse Reaction Events linked to exposure to substance
                                                                      .... 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
                                                                            .... substance 0..1CodeableConceptSpecific substance or pharmaceutical product considered to be responsible for event
                                                                            Binding: todo (example): Codes defining the type of the substance (including pharmaceutical products).

                                                                            0..1CodeableConceptSpecific substance or pharmaceutical product considered to be responsible for event
                                                                            Binding: SubstanceCode (example): Codes defining the type of the substance (including pharmaceutical products).

                                                                              .... manifestation S1..*CodeableConceptClinical symptoms/signs associated with the Event
                                                                              Binding: todo (extensible)
                                                                              S1..1CodeableConceptClinical symptoms/signs associated with the Event
                                                                              Binding: BeRiskManifestation (extensible)
                                                                              • Element maximum cardinalities differ: '2147483647' vs '1'
                                                                              .... description 0..1stringDescription of the event as a whole0..1stringDescription of the event as a whole
                                                                                .... onset 0..1dateTimeDate(/time) when manifestations showedS0..1dateTimeDate(/time) when manifestations showed
                                                                                • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                .... severity 0..1codemild | moderate | severe (of event as a whole)
                                                                                Binding: todo (required): Clinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations.

                                                                                0..1codemild | moderate | severe (of event as a whole)
                                                                                Binding: AllergyIntoleranceSeverity (required): Clinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations.

                                                                                  .... exposureRoute 0..1CodeableConceptHow the subject was exposed to the substance
                                                                                  Binding: todo (extensible)
                                                                                  0..1CodeableConceptHow the subject was exposed to the substance
                                                                                  Binding: BeExposureRoute (extensible)
                                                                                    .... note 0..*AnnotationText about event not captured in other fields
                                                                                    0..*AnnotationText about event not captured in other fields

                                                                                      doco Documentation for this format