HdBe-AllergyIntolerance
Profile | Description | Status | URL |
---|---|---|---|
HdBe-AllergyIntolerance | An allergy or intolerance describes a patient’s tendency towards hypersensitivity to a certain substance, so that an unwanted physiological reaction is expected after exposure to the substance, while most people would not exhibit such a reaction to that amount. The observed physiological changes are usually the result of an immunological reaction. The substances can be categorized as follows:
| draft | https://fhir.healthdata.be/StructureDefinition/HdBe-AllergyIntolerance |
AllergyIntolerance | I | AllergyIntolerance | Element idAllergyIntolerance AllergyIntolerance Alternate namesAllergy, Intolerance, Adverse Reaction, AllergieIntolerantie DefinitionRisk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance. Substances include, but are not limited to: a therapeutic substance administered correctly at an appropriate dosage for the individual; food; material derived from plants or animals; or venom from insect stings.
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idAllergyIntolerance.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idAllergyIntolerance.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idAllergyIntolerance.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idAllergyIntolerance.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idAllergyIntolerance.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it 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 is allowed to 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idAllergyIntolerance.identifier External ids for this item DefinitionBusiness identifiers assigned to this AllergyIntolerance by the performer or other systems which remain constant as the resource is updated and propagates from server to server. Allows identification of the AllergyIntolerance as it is known by various participating systems and in a way that remains consistent across servers. This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.
|
clinicalStatus | Σ ?! I | 0..1 | CodeableConceptBinding | Element idAllergyIntolerance.clinicalStatus AllergyStatus Alternate namesAllergieStatus DefinitionStatement on the status of the patient’s hypersensitivity. See the comment on the root element for guidance on mapping zib AllergyStatus to FHIR. Use ConceptMap AllergyStatusCodelist_to_AllergyIntoleranceClinicalStatusCodes to translate terminology from the functional model to profile terminology in ValueSet AllergyIntoleranceClinicalStatusCodes Permitted Values AllergyStatus_to_AllergyIntoleranceClinicalStatusCodes Constraints
|
verificationStatus | Σ ?! I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idAllergyIntolerance.verificationStatus unconfirmed | confirmed | refuted | entered-in-error DefinitionAssertion about certainty associated with the propensity, or potential risk, of a reaction to the identified substance (including pharmaceutical product). The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity. Assertion about certainty associated with a propensity, or potential risk, of a reaction to the identified substance.
|
type | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idAllergyIntolerance.type allergy | intolerance - Underlying mechanism (if known) Alternate namesCategory, Class DefinitionIdentification of the underlying physiological mechanism for the reaction risk. Allergic (typically immune-mediated) reactions have been traditionally regarded as an indicator for potential escalation to significant future risk. Contemporary knowledge suggests that some reactions previously thought to be immune-mediated are, in fact, non-immune, but in some cases can still pose a life threatening risk. It is acknowledged that many clinicians might not be in a position to distinguish the mechanism of a particular reaction. Often the term "allergy" is used rather generically and may overlap with the use of "intolerance" - in practice the boundaries between these two concepts might not be well-defined or understood. This data element is included nevertheless, because many legacy systems have captured this attribute. Immunologic testing may provide supporting evidence for the basis of the reaction and the causative substance, but no tests are 100% sensitive or specific for sensitivity to a particular substance. If, as is commonly the case, it is unclear whether the reaction is due to an allergy or an intolerance, then the type element should be omitted from the resource. Identification of the underlying physiological mechanism for a Reaction Risk.
|
category | Σ | 0..1 | codeBinding | Element idAllergyIntolerance.category AllergyCategory Alternate namesCategory, Type, Reaction Type, Class, AllergieCategorie DefinitionIdentifies the allergy category such as medication, food or environment. This data element has been included because it is currently being captured in some clinical systems. This data can be derived from the substance where coding systems are used, and is effectively redundant in that situation. When searching on category, consider the implications of AllergyIntolerance resources without a category. For example, when searching on category = medication, medication allergies that don't have a category valued will not be returned. Refer to search for more information on how to search category with a :missing modifier to get allergies that don't have a category. Additionally, category should be used with caution because category can be subjective based on the sender. Use ConceptMap AllergyCategoryCodelist_to_AllergyIntoleranceCategory to translate terminology from the functional model to profile terminology in ValueSet AllergyIntoleranceCategory Permitted Values AllergyCategory_to_AllergyIntoleranceCategory Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.category.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.category.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
allergyCategoryCodelist | I | 0..1 | Extension(CodeableConcept) | Element idAllergyIntolerance.category.extension:allergyCategoryCodelist Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.category.extension:allergyCategoryCodelist.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.category.extension:allergyCategoryCodelist.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idAllergyIntolerance.category.extension:allergyCategoryCodelist.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification
| |
value[x] | 0..1 | Binding | Element idAllergyIntolerance.category.extension:allergyCategoryCodelist.value[x] AllergyCategory Alternate namesAllergieCategorie DefinitionIdentifies the allergy category such as medication, food or environment.
| |
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
value | 0..1 | System.String | There are no (further) constraints on this element Element idAllergyIntolerance.category.value Primitive value for code DefinitionPrimitive value for code System.String Maximum string length1048576 | |
criticality | Σ | 0..1 | codeBinding | Element idAllergyIntolerance.criticality Criticality Alternate namesSeverity, Seriousness, Contra-indication, Risk, MateVanKritiekZijn DefinitionCritical extent is defined as “the potential severity of future reactions.” This represents a clinical evaluation of the worst case scenario for a future reaction. It can be based on the severity of past reactions, the dose and manner of exposure which caused reactions in the past, and the life-threatening potential of the type of reaction. Critical extent is a property of the allergy, and not of the reaction itself. The default criticality value for any propensity to an adverse reaction should be 'Low Risk', indicating at the very least a relative contraindication to deliberate or voluntary exposure to the substance. 'High Risk' is flagged if the clinician has identified a propensity for a more serious or potentially life-threatening reaction, such as anaphylaxis, and implies an absolute contraindication to deliberate or voluntary exposure to the substance. If this element is missing, the criticality is unknown (though it may be known elsewhere). Systems that capture a severity at the condition level are actually representing the concept of criticality whereas the severity documented at the reaction level is representing the true reaction severity. Existing systems that are capturing both condition criticality and reaction severity may use the term "severity" to represent both. Criticality is the worst it could be in the future (i.e. situation-agnostic) whereas severity is situation-dependent. Use ConceptMap CriticalExtentCodelist_to_AllergyIntoleranceCriticality to translate terminology from the functional model to profile terminology in ValueSet AllergyIntoleranceCriticality Permitted Values CriticalExtent_to_AllergyIntoleranceCriticality Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
criticalExtentCodelist | I | 0..1 | Extension(CodeableConcept) | Element idAllergyIntolerance.criticality.extension:criticalExtentCodelist Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.extension:criticalExtentCodelist.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.extension:criticalExtentCodelist.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.extension:criticalExtentCodelist.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification
| |
value[x] | 0..1 | Binding | Element idAllergyIntolerance.criticality.extension:criticalExtentCodelist.value[x] Criticality Alternate namesMateVanKritiekZijn DefinitionCritical extent is defined as “the potential severity of future reactions.” This represents a clinical evaluation of the worst case scenario for a future reaction. It can be based on the severity of past reactions, the dose and manner of exposure which caused reactions in the past, and the life-threatening potential of the type of reaction. Critical extent is a property of the allergy, and not of the reaction itself.
| |
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
value | 0..1 | System.String | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.value Primitive value for code DefinitionPrimitive value for code System.String Maximum string length1048576 | |
code | Σ | 0..1 | CodeableConceptBinding | Element idAllergyIntolerance.code CausativeAgent Alternate namesCode, VeroorzakendeStof DefinitionSubstance, group of substances or environmental factor to which the patient is allergic or hypersensitive. 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. Type of the substance/product, allergy or intolerance condition, or negation/exclusion codes for reporting no known allergies.
|
patient | Σ I | 1..1 | Reference(Patient | HdBe-Patient) | Element idAllergyIntolerance.patient Who the sensitivity is for Alternate namesPatient DefinitionThe patient who has the allergy or intolerance. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Patient | HdBe-Patient) Constraints
|
encounter | I | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idAllergyIntolerance.encounter Encounter when the allergy or intolerance was asserted DefinitionThe encounter when the allergy or intolerance was asserted. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
onset[x] | 0..1 | Element idAllergyIntolerance.onset[x] When allergy or intolerance was identified DefinitionEstimated or actual date, date-time, or age when allergy or intolerance was identified. Unordered, Open, by $this(Type) Constraints
| ||
onsetAge | Age | There are no (further) constraints on this element Data type | ||
onsetPeriod | Period | There are no (further) constraints on this element Data type | ||
onsetRange | Range | There are no (further) constraints on this element Data type | ||
onsetString | string | There are no (further) constraints on this element Data type | ||
onsetDateTime | 0..1 | dateTime | Element idAllergyIntolerance.onset[x]:onsetDateTime StartDateTime Alternate namesBeginDatumTijd DefinitionThe date and time at which the allergy or undesired reaction was determined. This can be an exact date and time, or a rough indication of the date (such as only the year, or the month and the year).
| |
recordedDate | 0..1 | dateTime | There are no (further) constraints on this element Element idAllergyIntolerance.recordedDate Date first version of the resource instance was recorded DefinitionThe recordedDate represents when this particular AllergyIntolerance record was created in the system, which is often a system-generated date.
| |
recorder | I | 0..1 | Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) | There are no (further) constraints on this element Element idAllergyIntolerance.recorder Who recorded the sensitivity Alternate namesAuthor DefinitionIndividual who recorded the record and takes responsibility for its content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) Constraints
|
asserter | Σ I | 0..1 | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) | There are no (further) constraints on this element Element idAllergyIntolerance.asserter Source of the information about the allergy Alternate namesSource, Informant DefinitionThe source of the information about the allergy that is recorded. The recorder takes responsibility for the content, but can reference the source from where they got it. Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) Constraints
|
lastOccurrence | 0..1 | dateTime | Element idAllergyIntolerance.lastOccurrence LastReactionDateTime Alternate namesLaatsteReactieDatumTijd DefinitionEntry of the last time a hypersensitive reaction took place. This date may be replicated by one of the Onset of Reaction dates. Where a textual representation of the date of last occurrence is required e.g. 'In Childhood, '10 years ago' the Comment element should be used.
| |
note | 0..1 | Annotation | There are no (further) constraints on this element Element idAllergyIntolerance.note Additional text not captured in other fields DefinitionAdditional narrative about the propensity for the Adverse Reaction, not captured in other fields. For example: including reason for flagging a seriousness of 'High Risk'; and instructions related to future exposure or administration of the substance, such as administration within an Intensive Care Unit or under corticosteroid cover. The notes should be related to an allergy or intolerance as a condition in general and not related to any particular episode of it. For episode notes and descriptions, use AllergyIntolerance.event.description and AllergyIntolerance.event.notes.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.note.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.note.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
author[x] | Σ | 0..1 | There are no (further) constraints on this element Element idAllergyIntolerance.note.author[x] Individual responsible for the annotation DefinitionThe individual responsible for making the annotation. Organization is used when there's no need for specific attribution as to who made the comment.
| |
authorString | string | There are no (further) constraints on this element Data type | ||
authorReference | Reference(Practitioner | Patient | RelatedPerson | Organization) | There are no (further) constraints on this element Data type Reference(Practitioner | Patient | RelatedPerson | Organization) | ||
time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idAllergyIntolerance.note.time When the annotation was made DefinitionIndicates when this particular annotation was made.
|
text | Σ | 1..1 | markdown | Element idAllergyIntolerance.note.text Comment Alternate namesToelichting DefinitionTextual explanation of the hypersensitivity which cannot be entered in any of the other fields. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
|
reaction | 0..* | BackboneElement | Element idAllergyIntolerance.reaction Reaction Alternate namesReactie DefinitionDetails about each adverse reaction event linked to exposure to the identified substance.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.reaction.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.reaction.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.reaction.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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. 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.
|
substance | 0..1 | CodeableConceptBinding | Element idAllergyIntolerance.reaction.substance SpecificSubstance Alternate namesSpecifiekeStof DefinitionMore specific indication of the substance that caused the reaction. This can be a specific substance from a group of substances to which the patient is allergic or hypersensitive. Coding of the specific substance (or pharmaceutical product) with a terminology capable of triggering decision support should be used wherever possible. The 'code' element allows for the use of a specific substance or pharmaceutical product, or a group or class of substances. In the case of an allergy or intolerance to a class of substances, (for example, "penicillins"), the 'reaction.substance' element could be used to code the specific substance that was identified as having caused the reaction (for example, "amoxycillin"). Duplication of the value in the 'code' and 'reaction.substance' elements is acceptable when a specific substance has been recorded in 'code'. Codes defining the type of the substance (including pharmaceutical products).
| |
manifestation | 1..* | CodeableConceptBinding | Element idAllergyIntolerance.reaction.manifestation Symptom Alternate namesSymptoms, Signs, Symptoom DefinitionThe content specifications of the reaction that takes place when the patient is exposed to the causative substance. Manifestation can be expressed as a single word, phrase or brief description. For example: nausea, rash or no reaction. It is preferable that manifestation should be coded with a terminology, where possible. The values entered here may be used to display on an application screen as part of a list of adverse reactions, as recommended in the UK NHS CUI guidelines. Terminologies commonly used include, but are not limited to, SNOMED CT or ICD10. Clinical symptoms and/or signs that are observed or associated with an Adverse Reaction Event.
| |
description | 0..1 | string | Element idAllergyIntolerance.reaction.description ReactionDescription Alternate namesNarrative, Text, ReactieBeschrijving DefinitionTextual description of the reaction as a whole. Use the description to provide any details of a particular event of the occurred reaction such as circumstances, reaction specifics, what happened before/after. Information, related to the event, but not describing a particular care should be captured in the comment field. For example: at the age of four, the patient was given penicillin for strep throat and subsequently developed severe hives.
| |
onset | 0..1 | dateTime | Element idAllergyIntolerance.reaction.onset ReactionTime Alternate namesReactieTijdstip DefinitionDate and time at which the reaction took place. This may also be just the date or a partial date, in the event that the exact date is unknown.
| |
severity | 0..1 | codeBinding | Element idAllergyIntolerance.reaction.severity Severity Alternate namesErnst DefinitionThe severity of the reaction as a result of exposure to the causative substance. It is acknowledged that this assessment is very subjective. There may be some specific practice domains where objective scales have been applied. Objective scales can be included in this model as extensions. Use ConceptMap CriticalExtentCodelist_to_AllergyIntoleranceSeverity to translate terminology from the functional model to profile terminology in ValueSet AllergyIntoleranceSeverity Permitted Values CriticalExtent_to_AllergyIntoleranceSeverity Constraints
| |
exposureRoute | 0..1 | CodeableConceptBinding | Element idAllergyIntolerance.reaction.exposureRoute RouteOfExposure Alternate namesWijzeVanBlootstelling DefinitionWay in which the patient came into contact with the causative agent or the way in which the agent was administered. Coding of the route of exposure with a terminology should be used wherever possible. A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject.
| |
note | 0..* | Annotation | There are no (further) constraints on this element Element idAllergyIntolerance.reaction.note Text about event not captured in other fields DefinitionAdditional text about the adverse reaction event not captured in other fields. Use this field to record information indirectly related to a particular event and not captured in the description. For example: Clinical records are no longer available, recorded based on information provided to the patient by her mother and her mother is deceased.
|
AllergyIntolerance | I | AllergyIntolerance | Element idAllergyIntolerance AllergyIntolerance Alternate namesAllergy, Intolerance, Adverse Reaction, AllergieIntolerantie DefinitionRisk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance. Substances include, but are not limited to: a therapeutic substance administered correctly at an appropriate dosage for the individual; food; material derived from plants or animals; or venom from insect stings.
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idAllergyIntolerance.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idAllergyIntolerance.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idAllergyIntolerance.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idAllergyIntolerance.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idAllergyIntolerance.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it 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 is allowed to 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idAllergyIntolerance.identifier External ids for this item DefinitionBusiness identifiers assigned to this AllergyIntolerance by the performer or other systems which remain constant as the resource is updated and propagates from server to server. Allows identification of the AllergyIntolerance as it is known by various participating systems and in a way that remains consistent across servers. This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.
|
clinicalStatus | Σ ?! I | 0..1 | CodeableConceptBinding | Element idAllergyIntolerance.clinicalStatus AllergyStatus Alternate namesAllergieStatus DefinitionStatement on the status of the patient’s hypersensitivity. See the comment on the root element for guidance on mapping zib AllergyStatus to FHIR. Use ConceptMap AllergyStatusCodelist_to_AllergyIntoleranceClinicalStatusCodes to translate terminology from the functional model to profile terminology in ValueSet AllergyIntoleranceClinicalStatusCodes Permitted Values AllergyStatus_to_AllergyIntoleranceClinicalStatusCodes Constraints
|
verificationStatus | Σ ?! I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idAllergyIntolerance.verificationStatus unconfirmed | confirmed | refuted | entered-in-error DefinitionAssertion about certainty associated with the propensity, or potential risk, of a reaction to the identified substance (including pharmaceutical product). The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity. Assertion about certainty associated with a propensity, or potential risk, of a reaction to the identified substance.
|
type | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idAllergyIntolerance.type allergy | intolerance - Underlying mechanism (if known) Alternate namesCategory, Class DefinitionIdentification of the underlying physiological mechanism for the reaction risk. Allergic (typically immune-mediated) reactions have been traditionally regarded as an indicator for potential escalation to significant future risk. Contemporary knowledge suggests that some reactions previously thought to be immune-mediated are, in fact, non-immune, but in some cases can still pose a life threatening risk. It is acknowledged that many clinicians might not be in a position to distinguish the mechanism of a particular reaction. Often the term "allergy" is used rather generically and may overlap with the use of "intolerance" - in practice the boundaries between these two concepts might not be well-defined or understood. This data element is included nevertheless, because many legacy systems have captured this attribute. Immunologic testing may provide supporting evidence for the basis of the reaction and the causative substance, but no tests are 100% sensitive or specific for sensitivity to a particular substance. If, as is commonly the case, it is unclear whether the reaction is due to an allergy or an intolerance, then the type element should be omitted from the resource. Identification of the underlying physiological mechanism for a Reaction Risk.
|
category | Σ | 0..1 | codeBinding | Element idAllergyIntolerance.category AllergyCategory Alternate namesCategory, Type, Reaction Type, Class, AllergieCategorie DefinitionIdentifies the allergy category such as medication, food or environment. This data element has been included because it is currently being captured in some clinical systems. This data can be derived from the substance where coding systems are used, and is effectively redundant in that situation. When searching on category, consider the implications of AllergyIntolerance resources without a category. For example, when searching on category = medication, medication allergies that don't have a category valued will not be returned. Refer to search for more information on how to search category with a :missing modifier to get allergies that don't have a category. Additionally, category should be used with caution because category can be subjective based on the sender. Use ConceptMap AllergyCategoryCodelist_to_AllergyIntoleranceCategory to translate terminology from the functional model to profile terminology in ValueSet AllergyIntoleranceCategory Permitted Values AllergyCategory_to_AllergyIntoleranceCategory Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.category.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.category.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
allergyCategoryCodelist | I | 0..1 | Extension(CodeableConcept) | Element idAllergyIntolerance.category.extension:allergyCategoryCodelist Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.category.extension:allergyCategoryCodelist.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.category.extension:allergyCategoryCodelist.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idAllergyIntolerance.category.extension:allergyCategoryCodelist.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification
| |
value[x] | 0..1 | Binding | Element idAllergyIntolerance.category.extension:allergyCategoryCodelist.value[x] AllergyCategory Alternate namesAllergieCategorie DefinitionIdentifies the allergy category such as medication, food or environment.
| |
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
value | 0..1 | System.String | There are no (further) constraints on this element Element idAllergyIntolerance.category.value Primitive value for code DefinitionPrimitive value for code System.String Maximum string length1048576 | |
criticality | Σ | 0..1 | codeBinding | Element idAllergyIntolerance.criticality Criticality Alternate namesSeverity, Seriousness, Contra-indication, Risk, MateVanKritiekZijn DefinitionCritical extent is defined as “the potential severity of future reactions.” This represents a clinical evaluation of the worst case scenario for a future reaction. It can be based on the severity of past reactions, the dose and manner of exposure which caused reactions in the past, and the life-threatening potential of the type of reaction. Critical extent is a property of the allergy, and not of the reaction itself. The default criticality value for any propensity to an adverse reaction should be 'Low Risk', indicating at the very least a relative contraindication to deliberate or voluntary exposure to the substance. 'High Risk' is flagged if the clinician has identified a propensity for a more serious or potentially life-threatening reaction, such as anaphylaxis, and implies an absolute contraindication to deliberate or voluntary exposure to the substance. If this element is missing, the criticality is unknown (though it may be known elsewhere). Systems that capture a severity at the condition level are actually representing the concept of criticality whereas the severity documented at the reaction level is representing the true reaction severity. Existing systems that are capturing both condition criticality and reaction severity may use the term "severity" to represent both. Criticality is the worst it could be in the future (i.e. situation-agnostic) whereas severity is situation-dependent. Use ConceptMap CriticalExtentCodelist_to_AllergyIntoleranceCriticality to translate terminology from the functional model to profile terminology in ValueSet AllergyIntoleranceCriticality Permitted Values CriticalExtent_to_AllergyIntoleranceCriticality Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
criticalExtentCodelist | I | 0..1 | Extension(CodeableConcept) | Element idAllergyIntolerance.criticality.extension:criticalExtentCodelist Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.extension:criticalExtentCodelist.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.extension:criticalExtentCodelist.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.extension:criticalExtentCodelist.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification
| |
value[x] | 0..1 | Binding | Element idAllergyIntolerance.criticality.extension:criticalExtentCodelist.value[x] Criticality Alternate namesMateVanKritiekZijn DefinitionCritical extent is defined as “the potential severity of future reactions.” This represents a clinical evaluation of the worst case scenario for a future reaction. It can be based on the severity of past reactions, the dose and manner of exposure which caused reactions in the past, and the life-threatening potential of the type of reaction. Critical extent is a property of the allergy, and not of the reaction itself.
| |
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
value | 0..1 | System.String | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.value Primitive value for code DefinitionPrimitive value for code System.String Maximum string length1048576 | |
code | Σ | 0..1 | CodeableConceptBinding | Element idAllergyIntolerance.code CausativeAgent Alternate namesCode, VeroorzakendeStof DefinitionSubstance, group of substances or environmental factor to which the patient is allergic or hypersensitive. 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. Type of the substance/product, allergy or intolerance condition, or negation/exclusion codes for reporting no known allergies.
|
patient | Σ I | 1..1 | Reference(Patient | HdBe-Patient) | Element idAllergyIntolerance.patient Who the sensitivity is for Alternate namesPatient DefinitionThe patient who has the allergy or intolerance. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Patient | HdBe-Patient) Constraints
|
encounter | I | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idAllergyIntolerance.encounter Encounter when the allergy or intolerance was asserted DefinitionThe encounter when the allergy or intolerance was asserted. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
onset[x] | 0..1 | Element idAllergyIntolerance.onset[x] When allergy or intolerance was identified DefinitionEstimated or actual date, date-time, or age when allergy or intolerance was identified. Unordered, Open, by $this(Type) Constraints
| ||
onsetAge | Age | There are no (further) constraints on this element Data type | ||
onsetPeriod | Period | There are no (further) constraints on this element Data type | ||
onsetRange | Range | There are no (further) constraints on this element Data type | ||
onsetString | string | There are no (further) constraints on this element Data type | ||
onsetDateTime | 0..1 | dateTime | Element idAllergyIntolerance.onset[x]:onsetDateTime StartDateTime Alternate namesBeginDatumTijd DefinitionThe date and time at which the allergy or undesired reaction was determined. This can be an exact date and time, or a rough indication of the date (such as only the year, or the month and the year).
| |
recordedDate | 0..1 | dateTime | There are no (further) constraints on this element Element idAllergyIntolerance.recordedDate Date first version of the resource instance was recorded DefinitionThe recordedDate represents when this particular AllergyIntolerance record was created in the system, which is often a system-generated date.
| |
recorder | I | 0..1 | Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) | There are no (further) constraints on this element Element idAllergyIntolerance.recorder Who recorded the sensitivity Alternate namesAuthor DefinitionIndividual who recorded the record and takes responsibility for its content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) Constraints
|
asserter | Σ I | 0..1 | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) | There are no (further) constraints on this element Element idAllergyIntolerance.asserter Source of the information about the allergy Alternate namesSource, Informant DefinitionThe source of the information about the allergy that is recorded. The recorder takes responsibility for the content, but can reference the source from where they got it. Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) Constraints
|
lastOccurrence | 0..1 | dateTime | Element idAllergyIntolerance.lastOccurrence LastReactionDateTime Alternate namesLaatsteReactieDatumTijd DefinitionEntry of the last time a hypersensitive reaction took place. This date may be replicated by one of the Onset of Reaction dates. Where a textual representation of the date of last occurrence is required e.g. 'In Childhood, '10 years ago' the Comment element should be used.
| |
note | 0..1 | Annotation | There are no (further) constraints on this element Element idAllergyIntolerance.note Additional text not captured in other fields DefinitionAdditional narrative about the propensity for the Adverse Reaction, not captured in other fields. For example: including reason for flagging a seriousness of 'High Risk'; and instructions related to future exposure or administration of the substance, such as administration within an Intensive Care Unit or under corticosteroid cover. The notes should be related to an allergy or intolerance as a condition in general and not related to any particular episode of it. For episode notes and descriptions, use AllergyIntolerance.event.description and AllergyIntolerance.event.notes.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.note.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.note.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
author[x] | Σ | 0..1 | There are no (further) constraints on this element Element idAllergyIntolerance.note.author[x] Individual responsible for the annotation DefinitionThe individual responsible for making the annotation. Organization is used when there's no need for specific attribution as to who made the comment.
| |
authorString | string | There are no (further) constraints on this element Data type | ||
authorReference | Reference(Practitioner | Patient | RelatedPerson | Organization) | There are no (further) constraints on this element Data type Reference(Practitioner | Patient | RelatedPerson | Organization) | ||
time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idAllergyIntolerance.note.time When the annotation was made DefinitionIndicates when this particular annotation was made.
|
text | Σ | 1..1 | markdown | Element idAllergyIntolerance.note.text Comment Alternate namesToelichting DefinitionTextual explanation of the hypersensitivity which cannot be entered in any of the other fields. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
|
reaction | 0..* | BackboneElement | Element idAllergyIntolerance.reaction Reaction Alternate namesReactie DefinitionDetails about each adverse reaction event linked to exposure to the identified substance.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.reaction.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.reaction.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.reaction.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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. 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.
|
substance | 0..1 | CodeableConceptBinding | Element idAllergyIntolerance.reaction.substance SpecificSubstance Alternate namesSpecifiekeStof DefinitionMore specific indication of the substance that caused the reaction. This can be a specific substance from a group of substances to which the patient is allergic or hypersensitive. Coding of the specific substance (or pharmaceutical product) with a terminology capable of triggering decision support should be used wherever possible. The 'code' element allows for the use of a specific substance or pharmaceutical product, or a group or class of substances. In the case of an allergy or intolerance to a class of substances, (for example, "penicillins"), the 'reaction.substance' element could be used to code the specific substance that was identified as having caused the reaction (for example, "amoxycillin"). Duplication of the value in the 'code' and 'reaction.substance' elements is acceptable when a specific substance has been recorded in 'code'. Codes defining the type of the substance (including pharmaceutical products).
| |
manifestation | 1..* | CodeableConceptBinding | Element idAllergyIntolerance.reaction.manifestation Symptom Alternate namesSymptoms, Signs, Symptoom DefinitionThe content specifications of the reaction that takes place when the patient is exposed to the causative substance. Manifestation can be expressed as a single word, phrase or brief description. For example: nausea, rash or no reaction. It is preferable that manifestation should be coded with a terminology, where possible. The values entered here may be used to display on an application screen as part of a list of adverse reactions, as recommended in the UK NHS CUI guidelines. Terminologies commonly used include, but are not limited to, SNOMED CT or ICD10. Clinical symptoms and/or signs that are observed or associated with an Adverse Reaction Event.
| |
description | 0..1 | string | Element idAllergyIntolerance.reaction.description ReactionDescription Alternate namesNarrative, Text, ReactieBeschrijving DefinitionTextual description of the reaction as a whole. Use the description to provide any details of a particular event of the occurred reaction such as circumstances, reaction specifics, what happened before/after. Information, related to the event, but not describing a particular care should be captured in the comment field. For example: at the age of four, the patient was given penicillin for strep throat and subsequently developed severe hives.
| |
onset | 0..1 | dateTime | Element idAllergyIntolerance.reaction.onset ReactionTime Alternate namesReactieTijdstip DefinitionDate and time at which the reaction took place. This may also be just the date or a partial date, in the event that the exact date is unknown.
| |
severity | 0..1 | codeBinding | Element idAllergyIntolerance.reaction.severity Severity Alternate namesErnst DefinitionThe severity of the reaction as a result of exposure to the causative substance. It is acknowledged that this assessment is very subjective. There may be some specific practice domains where objective scales have been applied. Objective scales can be included in this model as extensions. Use ConceptMap CriticalExtentCodelist_to_AllergyIntoleranceSeverity to translate terminology from the functional model to profile terminology in ValueSet AllergyIntoleranceSeverity Permitted Values CriticalExtent_to_AllergyIntoleranceSeverity Constraints
| |
exposureRoute | 0..1 | CodeableConceptBinding | Element idAllergyIntolerance.reaction.exposureRoute RouteOfExposure Alternate namesWijzeVanBlootstelling DefinitionWay in which the patient came into contact with the causative agent or the way in which the agent was administered. Coding of the route of exposure with a terminology should be used wherever possible. A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject.
| |
note | 0..* | Annotation | There are no (further) constraints on this element Element idAllergyIntolerance.reaction.note Text about event not captured in other fields DefinitionAdditional text about the adverse reaction event not captured in other fields. Use this field to record information indirectly related to a particular event and not captured in the description. For example: Clinical records are no longer available, recorded based on information provided to the patient by her mother and her mother is deceased.
|
AllergyIntolerance | I | AllergyIntolerance | Element idAllergyIntolerance AllergyIntolerance Alternate namesAllergy, Intolerance, Adverse Reaction, AllergieIntolerantie DefinitionRisk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance. Substances include, but are not limited to: a therapeutic substance administered correctly at an appropriate dosage for the individual; food; material derived from plants or animals; or venom from insect stings.
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idAllergyIntolerance.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idAllergyIntolerance.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idAllergyIntolerance.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idAllergyIntolerance.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idAllergyIntolerance.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it 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 is allowed to 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idAllergyIntolerance.identifier External ids for this item DefinitionBusiness identifiers assigned to this AllergyIntolerance by the performer or other systems which remain constant as the resource is updated and propagates from server to server. Allows identification of the AllergyIntolerance as it is known by various participating systems and in a way that remains consistent across servers. This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.
|
clinicalStatus | Σ ?! I | 0..1 | CodeableConceptBinding | Element idAllergyIntolerance.clinicalStatus AllergyStatus Alternate namesAllergieStatus DefinitionStatement on the status of the patient’s hypersensitivity. See the comment on the root element for guidance on mapping zib AllergyStatus to FHIR. Use ConceptMap AllergyStatusCodelist_to_AllergyIntoleranceClinicalStatusCodes to translate terminology from the functional model to profile terminology in ValueSet AllergyIntoleranceClinicalStatusCodes Permitted Values AllergyStatus_to_AllergyIntoleranceClinicalStatusCodes Constraints
|
verificationStatus | Σ ?! I | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idAllergyIntolerance.verificationStatus unconfirmed | confirmed | refuted | entered-in-error DefinitionAssertion about certainty associated with the propensity, or potential risk, of a reaction to the identified substance (including pharmaceutical product). The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity. Assertion about certainty associated with a propensity, or potential risk, of a reaction to the identified substance.
|
type | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idAllergyIntolerance.type allergy | intolerance - Underlying mechanism (if known) Alternate namesCategory, Class DefinitionIdentification of the underlying physiological mechanism for the reaction risk. Allergic (typically immune-mediated) reactions have been traditionally regarded as an indicator for potential escalation to significant future risk. Contemporary knowledge suggests that some reactions previously thought to be immune-mediated are, in fact, non-immune, but in some cases can still pose a life threatening risk. It is acknowledged that many clinicians might not be in a position to distinguish the mechanism of a particular reaction. Often the term "allergy" is used rather generically and may overlap with the use of "intolerance" - in practice the boundaries between these two concepts might not be well-defined or understood. This data element is included nevertheless, because many legacy systems have captured this attribute. Immunologic testing may provide supporting evidence for the basis of the reaction and the causative substance, but no tests are 100% sensitive or specific for sensitivity to a particular substance. If, as is commonly the case, it is unclear whether the reaction is due to an allergy or an intolerance, then the type element should be omitted from the resource. Identification of the underlying physiological mechanism for a Reaction Risk.
|
category | Σ | 0..1 | codeBinding | Element idAllergyIntolerance.category AllergyCategory Alternate namesCategory, Type, Reaction Type, Class, AllergieCategorie DefinitionIdentifies the allergy category such as medication, food or environment. This data element has been included because it is currently being captured in some clinical systems. This data can be derived from the substance where coding systems are used, and is effectively redundant in that situation. When searching on category, consider the implications of AllergyIntolerance resources without a category. For example, when searching on category = medication, medication allergies that don't have a category valued will not be returned. Refer to search for more information on how to search category with a :missing modifier to get allergies that don't have a category. Additionally, category should be used with caution because category can be subjective based on the sender. Use ConceptMap AllergyCategoryCodelist_to_AllergyIntoleranceCategory to translate terminology from the functional model to profile terminology in ValueSet AllergyIntoleranceCategory Permitted Values AllergyCategory_to_AllergyIntoleranceCategory Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.category.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.category.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
allergyCategoryCodelist | I | 0..1 | Extension(CodeableConcept) | Element idAllergyIntolerance.category.extension:allergyCategoryCodelist Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.category.extension:allergyCategoryCodelist.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.category.extension:allergyCategoryCodelist.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idAllergyIntolerance.category.extension:allergyCategoryCodelist.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification
| |
value[x] | 0..1 | Binding | Element idAllergyIntolerance.category.extension:allergyCategoryCodelist.value[x] AllergyCategory Alternate namesAllergieCategorie DefinitionIdentifies the allergy category such as medication, food or environment.
| |
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
value | 0..1 | System.String | There are no (further) constraints on this element Element idAllergyIntolerance.category.value Primitive value for code DefinitionPrimitive value for code System.String Maximum string length1048576 | |
criticality | Σ | 0..1 | codeBinding | Element idAllergyIntolerance.criticality Criticality Alternate namesSeverity, Seriousness, Contra-indication, Risk, MateVanKritiekZijn DefinitionCritical extent is defined as “the potential severity of future reactions.” This represents a clinical evaluation of the worst case scenario for a future reaction. It can be based on the severity of past reactions, the dose and manner of exposure which caused reactions in the past, and the life-threatening potential of the type of reaction. Critical extent is a property of the allergy, and not of the reaction itself. The default criticality value for any propensity to an adverse reaction should be 'Low Risk', indicating at the very least a relative contraindication to deliberate or voluntary exposure to the substance. 'High Risk' is flagged if the clinician has identified a propensity for a more serious or potentially life-threatening reaction, such as anaphylaxis, and implies an absolute contraindication to deliberate or voluntary exposure to the substance. If this element is missing, the criticality is unknown (though it may be known elsewhere). Systems that capture a severity at the condition level are actually representing the concept of criticality whereas the severity documented at the reaction level is representing the true reaction severity. Existing systems that are capturing both condition criticality and reaction severity may use the term "severity" to represent both. Criticality is the worst it could be in the future (i.e. situation-agnostic) whereas severity is situation-dependent. Use ConceptMap CriticalExtentCodelist_to_AllergyIntoleranceCriticality to translate terminology from the functional model to profile terminology in ValueSet AllergyIntoleranceCriticality Permitted Values CriticalExtent_to_AllergyIntoleranceCriticality Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
criticalExtentCodelist | I | 0..1 | Extension(CodeableConcept) | Element idAllergyIntolerance.criticality.extension:criticalExtentCodelist Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.extension:criticalExtentCodelist.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.extension:criticalExtentCodelist.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.extension:criticalExtentCodelist.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification
| |
value[x] | 0..1 | Binding | Element idAllergyIntolerance.criticality.extension:criticalExtentCodelist.value[x] Criticality Alternate namesMateVanKritiekZijn DefinitionCritical extent is defined as “the potential severity of future reactions.” This represents a clinical evaluation of the worst case scenario for a future reaction. It can be based on the severity of past reactions, the dose and manner of exposure which caused reactions in the past, and the life-threatening potential of the type of reaction. Critical extent is a property of the allergy, and not of the reaction itself.
| |
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
value | 0..1 | System.String | There are no (further) constraints on this element Element idAllergyIntolerance.criticality.value Primitive value for code DefinitionPrimitive value for code System.String Maximum string length1048576 | |
code | Σ | 0..1 | CodeableConceptBinding | Element idAllergyIntolerance.code CausativeAgent Alternate namesCode, VeroorzakendeStof DefinitionSubstance, group of substances or environmental factor to which the patient is allergic or hypersensitive. 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. Type of the substance/product, allergy or intolerance condition, or negation/exclusion codes for reporting no known allergies.
|
patient | Σ I | 1..1 | Reference(Patient | HdBe-Patient) | Element idAllergyIntolerance.patient Who the sensitivity is for Alternate namesPatient DefinitionThe patient who has the allergy or intolerance. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Patient | HdBe-Patient) Constraints
|
encounter | I | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idAllergyIntolerance.encounter Encounter when the allergy or intolerance was asserted DefinitionThe encounter when the allergy or intolerance was asserted. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
onset[x] | 0..1 | Element idAllergyIntolerance.onset[x] When allergy or intolerance was identified DefinitionEstimated or actual date, date-time, or age when allergy or intolerance was identified. Unordered, Open, by $this(Type) Constraints
| ||
onsetAge | Age | There are no (further) constraints on this element Data type | ||
onsetPeriod | Period | There are no (further) constraints on this element Data type | ||
onsetRange | Range | There are no (further) constraints on this element Data type | ||
onsetString | string | There are no (further) constraints on this element Data type | ||
onsetDateTime | 0..1 | dateTime | Element idAllergyIntolerance.onset[x]:onsetDateTime StartDateTime Alternate namesBeginDatumTijd DefinitionThe date and time at which the allergy or undesired reaction was determined. This can be an exact date and time, or a rough indication of the date (such as only the year, or the month and the year).
| |
recordedDate | 0..1 | dateTime | There are no (further) constraints on this element Element idAllergyIntolerance.recordedDate Date first version of the resource instance was recorded DefinitionThe recordedDate represents when this particular AllergyIntolerance record was created in the system, which is often a system-generated date.
| |
recorder | I | 0..1 | Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) | There are no (further) constraints on this element Element idAllergyIntolerance.recorder Who recorded the sensitivity Alternate namesAuthor DefinitionIndividual who recorded the record and takes responsibility for its content. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) Constraints
|
asserter | Σ I | 0..1 | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) | There are no (further) constraints on this element Element idAllergyIntolerance.asserter Source of the information about the allergy Alternate namesSource, Informant DefinitionThe source of the information about the allergy that is recorded. The recorder takes responsibility for the content, but can reference the source from where they got it. Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) Constraints
|
lastOccurrence | 0..1 | dateTime | Element idAllergyIntolerance.lastOccurrence LastReactionDateTime Alternate namesLaatsteReactieDatumTijd DefinitionEntry of the last time a hypersensitive reaction took place. This date may be replicated by one of the Onset of Reaction dates. Where a textual representation of the date of last occurrence is required e.g. 'In Childhood, '10 years ago' the Comment element should be used.
| |
note | 0..1 | Annotation | There are no (further) constraints on this element Element idAllergyIntolerance.note Additional text not captured in other fields DefinitionAdditional narrative about the propensity for the Adverse Reaction, not captured in other fields. For example: including reason for flagging a seriousness of 'High Risk'; and instructions related to future exposure or administration of the substance, such as administration within an Intensive Care Unit or under corticosteroid cover. The notes should be related to an allergy or intolerance as a condition in general and not related to any particular episode of it. For episode notes and descriptions, use AllergyIntolerance.event.description and AllergyIntolerance.event.notes.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.note.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.note.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
author[x] | Σ | 0..1 | There are no (further) constraints on this element Element idAllergyIntolerance.note.author[x] Individual responsible for the annotation DefinitionThe individual responsible for making the annotation. Organization is used when there's no need for specific attribution as to who made the comment.
| |
authorString | string | There are no (further) constraints on this element Data type | ||
authorReference | Reference(Practitioner | Patient | RelatedPerson | Organization) | There are no (further) constraints on this element Data type Reference(Practitioner | Patient | RelatedPerson | Organization) | ||
time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idAllergyIntolerance.note.time When the annotation was made DefinitionIndicates when this particular annotation was made.
|
text | Σ | 1..1 | markdown | Element idAllergyIntolerance.note.text Comment Alternate namesToelichting DefinitionTextual explanation of the hypersensitivity which cannot be entered in any of the other fields. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
|
reaction | 0..* | BackboneElement | Element idAllergyIntolerance.reaction Reaction Alternate namesReactie DefinitionDetails about each adverse reaction event linked to exposure to the identified substance.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idAllergyIntolerance.reaction.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.reaction.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAllergyIntolerance.reaction.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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. 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.
|
substance | 0..1 | CodeableConceptBinding | Element idAllergyIntolerance.reaction.substance SpecificSubstance Alternate namesSpecifiekeStof DefinitionMore specific indication of the substance that caused the reaction. This can be a specific substance from a group of substances to which the patient is allergic or hypersensitive. Coding of the specific substance (or pharmaceutical product) with a terminology capable of triggering decision support should be used wherever possible. The 'code' element allows for the use of a specific substance or pharmaceutical product, or a group or class of substances. In the case of an allergy or intolerance to a class of substances, (for example, "penicillins"), the 'reaction.substance' element could be used to code the specific substance that was identified as having caused the reaction (for example, "amoxycillin"). Duplication of the value in the 'code' and 'reaction.substance' elements is acceptable when a specific substance has been recorded in 'code'. Codes defining the type of the substance (including pharmaceutical products).
| |
manifestation | 1..* | CodeableConceptBinding | Element idAllergyIntolerance.reaction.manifestation Symptom Alternate namesSymptoms, Signs, Symptoom DefinitionThe content specifications of the reaction that takes place when the patient is exposed to the causative substance. Manifestation can be expressed as a single word, phrase or brief description. For example: nausea, rash or no reaction. It is preferable that manifestation should be coded with a terminology, where possible. The values entered here may be used to display on an application screen as part of a list of adverse reactions, as recommended in the UK NHS CUI guidelines. Terminologies commonly used include, but are not limited to, SNOMED CT or ICD10. Clinical symptoms and/or signs that are observed or associated with an Adverse Reaction Event.
| |
description | 0..1 | string | Element idAllergyIntolerance.reaction.description ReactionDescription Alternate namesNarrative, Text, ReactieBeschrijving DefinitionTextual description of the reaction as a whole. Use the description to provide any details of a particular event of the occurred reaction such as circumstances, reaction specifics, what happened before/after. Information, related to the event, but not describing a particular care should be captured in the comment field. For example: at the age of four, the patient was given penicillin for strep throat and subsequently developed severe hives.
| |
onset | 0..1 | dateTime | Element idAllergyIntolerance.reaction.onset ReactionTime Alternate namesReactieTijdstip DefinitionDate and time at which the reaction took place. This may also be just the date or a partial date, in the event that the exact date is unknown.
| |
severity | 0..1 | codeBinding | Element idAllergyIntolerance.reaction.severity Severity Alternate namesErnst DefinitionThe severity of the reaction as a result of exposure to the causative substance. It is acknowledged that this assessment is very subjective. There may be some specific practice domains where objective scales have been applied. Objective scales can be included in this model as extensions. Use ConceptMap CriticalExtentCodelist_to_AllergyIntoleranceSeverity to translate terminology from the functional model to profile terminology in ValueSet AllergyIntoleranceSeverity Permitted Values CriticalExtent_to_AllergyIntoleranceSeverity Constraints
| |
exposureRoute | 0..1 | CodeableConceptBinding | Element idAllergyIntolerance.reaction.exposureRoute RouteOfExposure Alternate namesWijzeVanBlootstelling DefinitionWay in which the patient came into contact with the causative agent or the way in which the agent was administered. Coding of the route of exposure with a terminology should be used wherever possible. A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject.
| |
note | 0..* | Annotation | There are no (further) constraints on this element Element idAllergyIntolerance.reaction.note Text about event not captured in other fields DefinitionAdditional text about the adverse reaction event not captured in other fields. Use this field to record information indirectly related to a particular event and not captured in the description. For example: Clinical records are no longer available, recorded based on information provided to the patient by her mother and her mother is deceased.
|
Mapping FHIR profile to CBB
Path | map | CBB |
---|---|---|
AllergyIntolerance | AllergyIntolerance | HdBe-AllergyIntolerance |
AllergyIntolerance.clinicalStatus | AllergyIntolerance.AllergyStatus | HdBe-AllergyIntolerance |
AllergyIntolerance.category | AllergyIntolerance.AllergyCategory | HdBe-AllergyIntolerance |
AllergyIntolerance.category.extension:allergyCategoryCodelist.value[x] | AllergyIntolerance.AllergyCategory | HdBe-AllergyIntolerance |
AllergyIntolerance.criticality | AllergyIntolerance.Criticality | HdBe-AllergyIntolerance |
AllergyIntolerance.criticality.extension:criticalExtentCodelist.value[x] | AllergyIntolerance.Criticality | HdBe-AllergyIntolerance |
AllergyIntolerance.code | AllergyIntolerance.CausativeAgent | HdBe-AllergyIntolerance |
AllergyIntolerance.onset[x]:onsetDateTime | AllergyIntolerance.StartDateTime | HdBe-AllergyIntolerance |
AllergyIntolerance.lastOccurrence | AllergyIntolerance.LastReactionDateTime | HdBe-AllergyIntolerance |
AllergyIntolerance.note.text | AllergyIntolerance.Comment | HdBe-AllergyIntolerance |
AllergyIntolerance.reaction | AllergyIntolerance.Reaction | HdBe-AllergyIntolerance |
AllergyIntolerance.reaction.substance | AllergyIntolerance.Reaction.SpecificSubstance | HdBe-AllergyIntolerance |
AllergyIntolerance.reaction.manifestation | AllergyIntolerance.Reaction.Symptom | HdBe-AllergyIntolerance |
AllergyIntolerance.reaction.description | AllergyIntolerance.Reaction.ReactionDescription | HdBe-AllergyIntolerance |
AllergyIntolerance.reaction.onset | AllergyIntolerance.Reaction.ReactionTime | HdBe-AllergyIntolerance |
AllergyIntolerance.reaction.severity | AllergyIntolerance.Reaction.Severity | HdBe-AllergyIntolerance |
AllergyIntolerance.reaction.exposureRoute | AllergyIntolerance.Reaction.RouteOfExposure | HdBe-AllergyIntolerance |
zib [zib-profile name] difference
Concept | Category | Description |
---|---|---|
AllergyIntolerance (root) |
textual | Removed comment regarding clinicalStatus and AllergyStatus ConceptMap. |
clinicalStatus |
terminology | Replaced AllergyStatus valueSet values with SNOMED CT codes of active and inactive, which are equal to the values in the AllergyIntolerance-v4.0 2021 pre-adopt version. |
clinicalStatus |
terminology | Adapted ConceptMap AllergyStatus-to-AllergyIntoleranceClinicalStatusCodes to match with the AllergyStatus values. |
verificationStatus |
mapping | Removed mapping of AllergyStatus to verificationStatus because the pre-adopt of the 2021 zib does not nescessetate the mapping anymore. |
category |
terminology | Added SNOMED CT code for unknown to AllergyCategory valueSet and replaced Other value with SNOMED CT code. |
category |
terminology | Adapted ConceptMap AllergyCategory-to-AllergyIntoleranceCategory to match with the AllergyCategory values. |
code |
terminology | Replaced existing Codelists in ValueSet with Belgium SNOMED refset with code: 751000172100. |
reaction.substance |
terminology | Replaced existing Codelists with valueSet CausativeAgent which contains Belgium SNOMED refset with code: 751000172100. |
reaction.manifestation |
terminology | Added SNOMED CT code for unknown to Symptom valueSet and replaced Other value with SNOMED CT code. |
reaction.severity |
terminology | Replaced valueSet with CriticalExtent valueSet, which is also used at the criticality element. |
reaction.severity |
terminology | Added a ConceptMap CriticalExtent-to-AllergyIntoleranceSeverity to map the CriticalExtent valueSet with the AllergyIntolerance values. |
Terminology Bindings
Path | Name | Strength | URL | ConceptMap |
---|---|---|---|---|
AllergyIntolerance.clinicalStatus | allergyintolerance-clinical|4.0.1 | required | http://hl7.org/fhir/ValueSet/allergyintolerance-clinical|4.0.1 | |
AllergyIntolerance.category | allergy-intolerance-category|4.0.1 | required | http://hl7.org/fhir/ValueSet/allergy-intolerance-category|4.0.1 | |
AllergyIntolerance.category.extension.value[x] | AllergyCategory | required | https://fhir.healthdata.be/ValueSet/AllergyCategory | No bound ConceptMap |
AllergyIntolerance.criticality | allergy-intolerance-criticality|4.0.1 | required | http://hl7.org/fhir/ValueSet/allergy-intolerance-criticality|4.0.1 | |
AllergyIntolerance.criticality.extension.value[x] | CriticalExtent | required | https://fhir.healthdata.be/ValueSet/CriticalExtent | No bound ConceptMap |
AllergyIntolerance.code | CausativeAgent | required | https://fhir.healthdata.be/ValueSet/CausativeAgent | No bound ConceptMap |
AllergyIntolerance.reaction.substance | CausativeAgent | required | https://fhir.healthdata.be/ValueSet/CausativeAgent | No bound ConceptMap |
AllergyIntolerance.reaction.manifestation | Symptom | extensible | https://fhir.healthdata.be/ValueSet/Symptom | No bound ConceptMap |
AllergyIntolerance.reaction.severity | reaction-event-severity|4.0.1 | required | http://hl7.org/fhir/ValueSet/reaction-event-severity|4.0.1 | |
AllergyIntolerance.reaction.exposureRoute | RouteOfExposure | required | https://fhir.healthdata.be/ValueSet/RouteOfExposure | No bound ConceptMap |