Name Flags Card. Type Description & Constraints be-model-allergyintolerance 0..* Element Elements defined in Ancestors: @id, <a href="http://hl7.org/fhir/R4/datatypes.html#Element" title="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.">extension Allergy Intolerance Logical Model Instances of this logical model are not marked to be the target of a Reference patient 1..1 Reference() The person that has the allergy code 1..1 CodeableConcept The substance that the person is allergic to Binding: BeAllergyIntoleranceCode (extensible) category 0..* code The category of the risk (food, medication, environment, biological,...). This information will not be encoded by the Recorder but can automatically be added using the SNOMED-CT code from causative agent type 0..1 code The Type - whether it is an allergy or intolerance Binding: BeVSAllergyIntoleranceType (required) status 0..1 BackboneElement The status of the allergy clinicalStatus 1..1 CodeableConcept The status of the allergy - if it is active or resolved Binding: AllergyIntoleranceClinicalStatusCodes (required) verificationStatus 1..1 CodeableConcept The verification status of the allergy - if it is confirmed or suspected or refuted Binding: AllergyIntoleranceVerificationStatusCodes (required) recordedDate 1..1 dateTime when the allergy/intolerance was recorded recorder 1..1 Reference() Who recorded the allergy <a href="StructureDefinition-be-model-allergyintolerance-definitions.html#be-model-allergyintolerance.asserter" title="Is the person at the source of the information (eg the patient, the general practitioner, a family member, the healthcare professional who registers the information himself, ...). He is represented as much as possible by a unique identification number, namely the national register number (INSZ) or the BIS number. However, when it comes to a parent or family member, only the role (e.g. father, mother, neighbor, caregiver, friend, etc.) is coded to meet the requirements of the GDPR.">asserter 0..1 Reference() Who asserted the allergy note 0..1 string Additional text note about the allergy or intolerance reactions 0..* BackboneElement known past reactions to the allergen manifestation 1..1 CodeableConcept How the reaction manifested itself onset 0..1 dateTime Manifestation date note 0..1 string Additional text note about the allergic reaction Documentation for this format
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
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.
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
The substance that the person is allergic to
The substance - from a lst of substances - that the person is allergic to. It is possible to use free text but for the products indicated, a code must be used
The category of the risk (food, medication, environment, biological,...). This information will not be encoded by the Recorder but can automatically be added using the SNOMED-CT code from causative agent
The Type - whether it is an allergy or intolerance
the type of risk (allergy, intolerance...). When it is not possible to distinguish between a real allergy, a non-allergic hypersensitivity or an intolerance you can use the 'Intolerance' type, but code the VerificationStatus as 'Unconfirmed'
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
The status of the allergy - if it is active or resolved
The verification status of the allergy - if it is confirmed or suspected or refuted
when the allergy/intolerance was recorded
Is the person at the source of the information (eg the patient, the general practitioner, a family member, the healthcare professional who registers the information himself, ...). He is represented as much as possible by a unique identification number, namely the national register number (INSZ) or the BIS number. However, when it comes to a parent or family member, only the role (e.g. father, mother, neighbor, caregiver, friend, etc.) is coded to meet the requirements of the GDPR.
Additional text note about the allergy or intolerance
How the reaction manifested itself, e.g. rash, breathing difficulty...
For each manifestation it is possible to specify an actual date or approximate date (age, period, interval, ...) of each suspected manifestation of the risk
Additional text note about the allergic reaction