- This version of the UK Core is a development copy.
- This contains BREAKING CHANGES as a result of the C&TA Sprint 7 Review, and STU2 Sequence ballot reconciliation.
- This version is not yet reviewed for implementation. Other versions are available on the UK Core Version History Guide
- Please follow the guidance on the Contact Us page if you need any assistance.
- A summary of changes is available on the STU3 Sequence Change Log
StructureDefinition UKCore-AllergyIntolerance
Canonical_URL | Status | Current_Version | Last_Updated | Description |
---|---|---|---|---|
https://fhir.hl7.org.uk/StructureDefinition/UKCore-AllergyIntolerance | active | 2.5.0 | 2024-07-11 | This profile defines the UK constraints and extensions on the International FHIR resource AllergyIntolerance. |
Profile_Purpose |
---|
This profile allows a record of a clinical assessment of an allergy or intolerance; a propensity, or a potential risk to an individual, to have an adverse reaction on future exposure to the specified substance, or class of substance. Where a propensity is identified, to record information or evidence about a reaction event that is characterised by any harmful or undesirable physiological response that is specific to the individual and triggered by exposure of an individual to the identified substance or class of 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. This resource is used to record physical conditions. It SHALL NOT be used to record preferences for or against types of treatment, for example on religious grounds. For such use cases consider the use of the FHIR Consent resource. |
Detailed Descriptions
AllergyIntolerance | |
Definition | Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance. |
Cardinality | 0...* |
Alias | Allergy, Intolerance, Adverse Reaction |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
AllergyIntolerance.meta | |
Definition | The 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. |
Cardinality | 0...1 |
Type | Meta |
Summary | True |
Invariants |
|
Mappings |
|
AllergyIntolerance.implicitRules | |
Definition | A 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. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. |
Comments | 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). |
Invariants |
|
Mappings |
|
AllergyIntolerance.text | |
Definition | A 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. |
Cardinality | 0...1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.contained | |
Definition | These 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. |
Cardinality | 0...* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | 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. |
Mappings |
|
AllergyIntolerance.extension | |
Definition | May 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
AllergyIntolerance.extension:evidence | |
Definition | A reference to results of investigations that confirmed the certainty of the diagnosis. |
Cardinality | 0...* |
Type | Extension(Reference(DiagnosticReport)) |
Alias | extensions, user content |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.modifierExtension | |
Definition | May 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
Requirements | 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. |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
AllergyIntolerance.identifier | |
Definition | Business 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. |
Cardinality | 0...* |
Type | Identifier |
Summary | True |
Requirements | Allows identification of the AllergyIntolerance as it is known by various participating systems and in a way that remains consistent across servers. |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.clinicalStatus | |
Definition | The clinical status of the allergy or intolerance. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | The clinical status of the allergy or intolerance. |
Must Support | True |
Modifier | True |
Summary | True |
Comments | Refer to discussion if clincalStatus is missing data. The data type is CodeableConcept because clinicalStatus 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.clinicalStatus.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
AllergyIntolerance.clinicalStatus.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
AllergyIntolerance.clinicalStatus.extension:allergyIntoleranceEnd | |
Definition | Supports the date when the allergy or intolerance was no longer valid, and/or, the reason why the allergy or intolerance is no longer valid. |
Cardinality | 0...1 |
Type | Extension(Complex) |
Alias | extensions, user content |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.clinicalStatus.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 0...* |
Type | Coding |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Invariants |
|
Mappings |
|
AllergyIntolerance.clinicalStatus.text | |
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
AllergyIntolerance.verificationStatus | |
Definition | Assertion about certainty associated with the propensity, or potential risk, of a reaction to the identified substance (including pharmaceutical product). |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Assertion about certainty associated with a propensity, or potential risk, of a reaction to the identified substance. |
Must Support | True |
Modifier | True |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.type | |
Definition | Identification of the underlying physiological mechanism for the reaction risk. |
Cardinality | 0...1 |
Type | code |
Binding | Identification of the underlying physiological mechanism for a Reaction Risk. |
Summary | True |
Alias | Category, Class |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.category | |
Definition | Category of the identified substance. |
Cardinality | 0...* |
Type | code |
Binding | Category of an identified substance associated with allergies or intolerances. |
Summary | True |
Alias | Category, Type, Reaction Type, Class |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.criticality | |
Definition | Estimate of the potential clinical harm, or seriousness, of the reaction to the identified substance. |
Cardinality | 0...1 |
Type | code |
Binding | Estimate of the potential clinical harm, or seriousness, of a reaction to an identified substance. |
Summary | True |
Alias | Severity, Seriousness, Contra-indication, Risk |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.code | |
Definition | Code for an allergy or intolerance statement (either a positive or a negated/excluded statement). This may be a code for a substance or pharmaceutical product that is considered to be responsible for the adverse reaction risk (e.g., "Latex"), an allergy or intolerance condition (e.g., "Latex allergy"), or a negated/excluded code for a specific substance or class (e.g., "No latex allergy") or a general or categorical negated statement (e.g., "No known allergy", "No known drug allergies"). Note: the substance for a specific reaction may be different from the substance identified as the cause of the risk, but it must be consistent with it. For instance, it may be a more specific substance (e.g. a brand medication) or a composite product that includes the identified substance. It must be clinically safe to only process the 'code' and ignore the 'reaction.substance'. If a receiving system is unable to confirm that AllergyIntolerance.reaction.substance falls within the semantic scope of AllergyIntolerance.code, then the receiving system should ignore AllergyIntolerance.reaction.substance. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | Type of the substance/product, allergy or intolerance condition, or negation/exclusion codes for reporting no known allergies. |
Must Support | True |
Summary | True |
Alias | Code |
Comments | It is strongly recommended that this element be populated using a terminology, where possible. For example, some terminologies used include RxNorm, SNOMED CT, DM+D, NDFRT, ICD-9, IDC-10, UNII, and ATC. Plain text should only be used if there is no appropriate terminology available. Additional details can be specified in the text. When a substance or product code is specified for the 'code' element, the "default" semantic context is that this is a positive statement of an allergy or intolerance (depending on the value of the 'type' element, if present) condition to the specified substance/product. In the corresponding SNOMED CT allergy model, the specified substance/product is the target (destination) of the "Causative agent" relationship. The 'substanceExposureRisk' extension is available as a structured and more flexible alternative to the 'code' element for making positive or negative allergy or intolerance statements. This extension provides the capability to make "no known allergy" (or "no risk of adverse reaction") statements regarding any coded substance/product (including cases when a pre-coordinated "no allergy to x" concept for that substance/product does not exist). If the 'substanceExposureRisk' extension is present, the AllergyIntolerance.code element SHALL be omitted. |
Invariants |
|
Mappings |
|
AllergyIntolerance.patient | |
Definition | The patient who has the allergy or intolerance. |
Cardinality | 1...1 |
Type | Reference(Patient) |
Must Support | True |
Summary | True |
Alias | Patient |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.encounter | |
Definition | The encounter when the allergy or intolerance was asserted. |
Cardinality | 0...1 |
Type | Reference(Encounter) |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.onset[x] | |
Definition | Estimated or actual date, date-time, or age when allergy or intolerance was identified. |
Cardinality | 0...1 |
Type | dateTime |
Invariants |
|
Mappings |
|
AllergyIntolerance.recordedDate | |
Definition | The recordedDate represents when this particular AllergyIntolerance record was created in the system, which is often a system-generated date. |
Cardinality | 0...1 |
Type | dateTime |
Invariants |
|
Mappings |
|
AllergyIntolerance.recorder | |
Definition | Individual who recorded the record and takes responsibility for its content. |
Cardinality | 0...1 |
Type | Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) |
Alias | Author |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.asserter | |
Definition | The source of the information about the allergy that is recorded. |
Cardinality | 0...1 |
Type | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) |
Summary | True |
Alias | Source, Informant |
Comments | The recorder takes responsibility for the content, but can reference the source from where they got it. |
Invariants |
|
Mappings |
|
AllergyIntolerance.lastOccurrence | |
Definition | Represents the date and/or time of the last known occurrence of a reaction event. |
Cardinality | 0...1 |
Type | dateTime |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.note | |
Definition | Additional narrative about the propensity for the Adverse Reaction, not captured in other fields. |
Cardinality | 0...* |
Type | Annotation |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.reaction | |
Definition | Details about each adverse reaction event linked to exposure to the identified substance. |
Cardinality | 0...* |
Type | BackboneElement |
Must Support | True |
Invariants |
|
Mappings |
|
AllergyIntolerance.reaction.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
AllergyIntolerance.reaction.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
AllergyIntolerance.reaction.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.reaction.substance | |
Definition | Identification of the specific substance (or pharmaceutical product) considered to be responsible for the Adverse Reaction event. Note: the substance for a specific reaction may be different from the substance identified as the cause of the risk, but it must be consistent with it. For instance, it may be a more specific substance (e.g. a brand medication) or a composite product that includes the identified substance. It must be clinically safe to only process the 'code' and ignore the 'reaction.substance'. If a receiving system is unable to confirm that AllergyIntolerance.reaction.substance falls within the semantic scope of AllergyIntolerance.code, then the receiving system should ignore AllergyIntolerance.reaction.substance. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Codes defining the type of the substance (including pharmaceutical products). |
Comments | 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'. |
Invariants |
|
Mappings |
|
AllergyIntolerance.reaction.manifestation | |
Definition | Clinical symptoms and/or signs that are observed or associated with the adverse reaction event. |
Cardinality | 1...* |
Type | CodeableConcept |
Binding | Clinical symptoms and/or signs that are observed or associated with an Adverse Reaction Event. |
Alias | Symptoms, Signs |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.reaction.description | |
Definition | Text description about the reaction as a whole, including details of the manifestation if required. |
Cardinality | 0...1 |
Type | string |
Alias | Narrative, Text |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.reaction.onset | |
Definition | Record of the date and/or time of the onset of the Reaction. |
Cardinality | 0...1 |
Type | dateTime |
Invariants |
|
Mappings |
|
AllergyIntolerance.reaction.severity | |
Definition | Clinical assessment of the severity of the reaction event as a whole, potentially considering multiple different manifestations. |
Cardinality | 0...1 |
Type | code |
Binding | Clinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations. |
Must Support | True |
Comments | 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. |
Invariants |
|
Mappings |
|
AllergyIntolerance.reaction.exposureRoute | |
Definition | Identification of the route by which the subject was exposed to the substance. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject. |
Comments | Coding of the route of exposure with a terminology should be used wherever possible. |
Invariants |
|
Mappings |
|
AllergyIntolerance.reaction.note | |
Definition | Additional text about the adverse reaction event not captured in other fields. |
Cardinality | 0...* |
Type | Annotation |
Comments | 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. |
Invariants |
|
Mappings |
|
Table View
AllergyIntolerance | .. | |
AllergyIntolerance.extension | Extension | .. |
AllergyIntolerance.clinicalStatus | .. | |
AllergyIntolerance.clinicalStatus.extension | Extension | .. |
AllergyIntolerance.verificationStatus | .. | |
AllergyIntolerance.code | 1.. | |
AllergyIntolerance.patient | .. | |
AllergyIntolerance.reaction | .. | |
AllergyIntolerance.reaction.substance | .. | |
AllergyIntolerance.reaction.manifestation | .. | |
AllergyIntolerance.reaction.severity | .. | |
AllergyIntolerance.reaction.exposureRoute | .. |
XML View
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="UKCore-AllergyIntolerance" /> <url value="https://fhir.hl7.org.uk/StructureDefinition/UKCore-AllergyIntolerance" /> <version value="2.5.0" /> <name value="UKCoreAllergyIntolerance" /> <title value="UK Core Allergy Intolerance" /> <status value="active" /> <date value="2024-07-11" /> <publisher value="HL7 UK" /> <contact> <name value="HL7 UK" /> <telecom> <system value="email" /> <value value="ukcore@hl7.org.uk" /> <use value="work" /> <rank value="1" /> </telecom> </contact> <description value="This profile defines the UK constraints and extensions on the International FHIR resource [AllergyIntolerance](https://hl7.org/fhir/R4/AllergyIntolerance.html)." /> <purpose value="This profile allows a record of a clinical assessment of an allergy or intolerance; a propensity, or a potential risk to an individual, to have an adverse reaction on future exposure to the specified substance, or class of substance. \n\nWhere a propensity is identified, to record information or evidence about a reaction event that is characterised by any harmful or undesirable physiological response that is specific to the individual and triggered by exposure of an individual to the identified substance or class of substance. \n\nSubstances 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. \n\nThis resource is used to record physical conditions. It SHALL NOT be used to record preferences for or against types of treatment, for example on religious grounds. For such use cases consider the use of the FHIR [Consent](https://hl7.org/fhir/R4/consent.html) resource." /> <copyright value="Copyright © 2021+ HL7 UK Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at https://www.hl7.org/fhir/license.html." /> <fhirVersion value="4.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="AllergyIntolerance" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/AllergyIntolerance" /> <derivation value="constraint" /> <differential> <element id="AllergyIntolerance.extension:evidence"> <path value="AllergyIntolerance.extension" /> <sliceName value="evidence" /> <short value="A reference to a DiagnosticReport resource for investigations that confirm the certainty of the allergy or intolerance diagnosis." /> <type> <code value="Extension" /> <profile value="https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-Evidence" /> </type> </element> <element id="AllergyIntolerance.clinicalStatus"> <path value="AllergyIntolerance.clinicalStatus" /> <short value="Defines whether the allergy or intolerance is active, inactive or resolved." /> <mustSupport value="true" /> </element> <element id="AllergyIntolerance.clinicalStatus.extension:allergyIntoleranceEnd"> <path value="AllergyIntolerance.clinicalStatus.extension" /> <sliceName value="allergyIntoleranceEnd" /> <short value="The date when the allergy or intolerance clinicalStatus is updated to inactive or resolved." /> <type> <code value="Extension" /> <profile value="https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-AllergyIntoleranceEnd" /> </type> <isModifier value="false" /> </element> <element id="AllergyIntolerance.verificationStatus"> <path value="AllergyIntolerance.verificationStatus" /> <short value="Defines the assertion of the allergy or intolerance." /> <mustSupport value="true" /> </element> <element id="AllergyIntolerance.code"> <path value="AllergyIntolerance.code" /> <short value="This code identifies the allergy or intolerance." /> <min value="1" /> <mustSupport value="true" /> <binding> <strength value="preferred" /> <valueSet value="https://fhir.hl7.org.uk/ValueSet/UKCore-AllergyCode" /> </binding> </element> <element id="AllergyIntolerance.patient"> <path value="AllergyIntolerance.patient" /> <short value="Links the allergy or intolerance to the patient." /> <mustSupport value="true" /> </element> <element id="AllergyIntolerance.reaction"> <path value="AllergyIntolerance.reaction" /> <short value="Details about each adverse reaction event." /> <mustSupport value="true" /> </element> <element id="AllergyIntolerance.reaction.substance"> <path value="AllergyIntolerance.reaction.substance" /> <binding> <strength value="preferred" /> <valueSet value="https://fhir.hl7.org.uk/ValueSet/UKCore-AllergySubstance" /> </binding> </element> <element id="AllergyIntolerance.reaction.manifestation"> <path value="AllergyIntolerance.reaction.manifestation" /> <binding> <strength value="preferred" /> <valueSet value="https://fhir.hl7.org.uk/ValueSet/UKCore-AllergyManifestation" /> </binding> </element> <element id="AllergyIntolerance.reaction.severity"> <path value="AllergyIntolerance.reaction.severity" /> <short value="A clinical assessment of the severity of the reaction event as a whole." /> <mustSupport value="true" /> </element> <element id="AllergyIntolerance.reaction.exposureRoute"> <path value="AllergyIntolerance.reaction.exposureRoute" /> <binding> <strength value="preferred" /> <valueSet value="https://fhir.hl7.org.uk/ValueSet/UKCore-SubstanceOrProductAdministrationRoute" /> </binding> </element> </differential> </StructureDefinition>
JSON View
{ "resourceType": "StructureDefinition", "id": "UKCore-AllergyIntolerance", "url": "https://fhir.hl7.org.uk/StructureDefinition/UKCore-AllergyIntolerance", "version": "2.5.0", "name": "UKCoreAllergyIntolerance", "title": "UK Core Allergy Intolerance", "status": "active", "date": "2024-07-11", "publisher": "HL7 UK", "contact": [ { "name": "HL7 UK", "telecom": [ { "system": "email", "value": "ukcore@hl7.org.uk", "use": "work", "rank": 1 } ] } ], "description": "This profile defines the UK constraints and extensions on the International FHIR resource [AllergyIntolerance](https://hl7.org/fhir/R4/AllergyIntolerance.html).", "purpose": "This profile allows a record of a clinical assessment of an allergy or intolerance; a propensity, or a potential risk to an individual, to have an adverse reaction on future exposure to the specified substance, or class of substance. \n\nWhere a propensity is identified, to record information or evidence about a reaction event that is characterised by any harmful or undesirable physiological response that is specific to the individual and triggered by exposure of an individual to the identified substance or class of substance. \n\nSubstances 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. \n\nThis resource is used to record physical conditions. It SHALL NOT be used to record preferences for or against types of treatment, for example on religious grounds. For such use cases consider the use of the FHIR [Consent](https://hl7.org/fhir/R4/consent.html) resource.", "copyright": "Copyright © 2021+ HL7 UK Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at https://www.hl7.org/fhir/license.html.", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "AllergyIntolerance", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/AllergyIntolerance", "derivation": "constraint", "differential": { "element": [ { "id": "AllergyIntolerance.extension:evidence", "path": "AllergyIntolerance.extension", "sliceName": "evidence", "short": "A reference to a DiagnosticReport resource for investigations that confirm the certainty of the allergy or intolerance diagnosis.", "type": [ { "code": "Extension", "profile": [ "https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-Evidence" ] } ] }, { "id": "AllergyIntolerance.clinicalStatus", "path": "AllergyIntolerance.clinicalStatus", "short": "Defines whether the allergy or intolerance is active, inactive or resolved.", "mustSupport": true }, { "id": "AllergyIntolerance.clinicalStatus.extension:allergyIntoleranceEnd", "path": "AllergyIntolerance.clinicalStatus.extension", "sliceName": "allergyIntoleranceEnd", "short": "The date when the allergy or intolerance clinicalStatus is updated to inactive or resolved.", "type": [ { "code": "Extension", "profile": [ "https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-AllergyIntoleranceEnd" ] } ], "isModifier": false }, { "id": "AllergyIntolerance.verificationStatus", "path": "AllergyIntolerance.verificationStatus", "short": "Defines the assertion of the allergy or intolerance.", "mustSupport": true }, { "id": "AllergyIntolerance.code", "path": "AllergyIntolerance.code", "short": "This code identifies the allergy or intolerance.", "min": 1, "mustSupport": true, "binding": { "strength": "preferred", "valueSet": "https://fhir.hl7.org.uk/ValueSet/UKCore-AllergyCode" } }, { "id": "AllergyIntolerance.patient", "path": "AllergyIntolerance.patient", "short": "Links the allergy or intolerance to the patient.", "mustSupport": true }, { "id": "AllergyIntolerance.reaction", "path": "AllergyIntolerance.reaction", "short": "Details about each adverse reaction event.", "mustSupport": true }, { "id": "AllergyIntolerance.reaction.substance", "path": "AllergyIntolerance.reaction.substance", "binding": { "strength": "preferred", "valueSet": "https://fhir.hl7.org.uk/ValueSet/UKCore-AllergySubstance" } }, { "id": "AllergyIntolerance.reaction.manifestation", "path": "AllergyIntolerance.reaction.manifestation", "binding": { "strength": "preferred", "valueSet": "https://fhir.hl7.org.uk/ValueSet/UKCore-AllergyManifestation" } }, { "id": "AllergyIntolerance.reaction.severity", "path": "AllergyIntolerance.reaction.severity", "short": "A clinical assessment of the severity of the reaction event as a whole.", "mustSupport": true }, { "id": "AllergyIntolerance.reaction.exposureRoute", "path": "AllergyIntolerance.reaction.exposureRoute", "binding": { "strength": "preferred", "valueSet": "https://fhir.hl7.org.uk/ValueSet/UKCore-SubstanceOrProductAdministrationRoute" } } ] } }
Feedback
Click here to:Report issue for UKCore-AllergyIntolerance, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
Examples
Allergy - An example to illustrate an allergy to medication.Example UKCore-AllergyIntolerance-Amoxicillin
Allergy entered in error - An example to illustrate an allergy which was entered in error and has been marked as ended.
Example UKCore-AllergyIntolerance-EnteredInError
Allergy evidence - An example to illustrate a reference to results of investigations that confirmed the certainty of the diagnosis for an allergy or intolerance.
Example UKCore-Extension-Evidence
Allergy List - An example to illustrate a list of allergies contained in a Bundle resource.
Example UKCore-Bundle-AllergyList
Example Usage Scenarios
The following are feasible use cases for the UK Core AllergyIntolerance profile:
- Query for patient allergy information
- Exchange patient allergy information within a FHIR Document or FHIR Message
- Migration of allergies data between systems.
Profile Specific Implementation Guidance:
Use Case: Query
The query against a clinical system or shared record to return recorded allergies as AllergyIntolerance
resources.
Returned results could be ordered by AllergyIntolerance.recordedDate
and/or AllergyIntolerance.lastOccurrence
.
Returned results MAY include multiple instances of the same allergy, as per the causative agent (AllergyIntolerance.code
), but with different AllergyIntolerance.clinicalStatus
values. The newer of such records either by AllergyIntolerance.recordedDate
or AllergyIntolerance.lastOccurrence
SHOULD be deemed the latest or current record of the allergy.
Use Case: Exchange
For when systems need to exchange allergy information within a point-to-point message. The AllergyIntolerance
resources can be included within a FHIR Message (within the Bundle), or within a FHIR Document alongside other structured resources and text-based data.
Allergy information SHOULD NOT be duplicated between systems (and, in England, this aligns with the NHS Data Strategy). When exchanging allergies data between systems be mindful of whether the receiving system plans to persist the data. If persisted, processes SHALL be put in place to ensure the data is updated if/when the source record is updated.
Use Case: Migration
When allergy records are migrated between systems, the AllergyIntolerance
resource could be used as a data migration standard.
Where migrated data is not coded, uses retired / invalidated codes, or coded with a terminology which cannot be mapped to SNOMED CT, then refer to the guidance on using degraded drug / non-drug allergy codes.
Mandatory and Must Support Data Elements
The following elements are identified as MustSupport, and it is expected that consumers and suppliers SHALL support these as per the MustSupport Guidance.
Element | Reason |
---|---|
AllergyIntolerance.clinicalStatus | Defines whether the allergy or intolerance is active, inactive or resolved. |
AllergyIntolerance.verificationStatus | Defines the assertion of the allergy or intolerance. |
AllergyIntolerance.code | This code identifies the allergy or intolerance. |
AllergyIntolerance.patient | Links the allergy or intolerance to the patient. |
AllergyIntolerance.reaction | Details about each adverse reaction event. |
AllergyIntolerance.reaction.severity | A clinical assessment of the severity of the reaction event as a whole. |
Extensions
More information about the extensions on the UKCore-AllergyIntolerance
profile can be found using the links below.
Extension | Context | Link | Comment |
---|---|---|---|
evidence | AllergyIntolerance.extension | https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-Evidence | A reference to a DiagnosticReport resource for investigations that confirm the certainty of the allergy or intolerance diagnosis. |
allergyIntoleranceEnd | AllergyIntolerance.clinicalStatus.extension | https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-AllergyIntoleranceEnd | The date when the allergy or intolerance clinicalStatus is updated to inactive or resolved. |
Bindings (differential)
More information about the bindings to UK Core ValueSets can be found below.
Context | Strength | Link |
---|---|---|
AllergyIntolerance.code | preferred | https://fhir.hl7.org.uk/ValueSet/UKCore-AllergyCode |
AllergyIntolerance.reaction.substance | preferred | https://fhir.hl7.org.uk/ValueSet/UKCore-AllergySubstance |
AllergyIntolerance.reaction.manifestation | preferred | https://fhir.hl7.org.uk/ValueSet/UKCore-AllergyManifestation |
AllergyIntolerance.reaction.exposureRoute | preferred | https://fhir.hl7.org.uk/ValueSet/UKCore-SubstanceOrProductAdministrationRoute |
verificationStatus
An optional value from a required terminology binding containing the values;
unconfirmed
confirmed
refuted
entered-in-error
.
Note: The use of entered-in-error
dictates the population of the AllergyIntolerance.clinicalStatus
element, via the ait-1
and ait-2
constraints in the base resource.
code
Identifies the causative agent for the allergy or intolerance.
When recording an allergy to a medication substance, the provider system SHOULD use a dm+d concept class or alternatively, when the allergy is not recorded against a medication substance, the relevant set of SNOMED CT. These can be found within the ValueSet UKCore-AllergyCode.
Using transfer degraded drug / non-drug allergy codes
Degraded drug allergy codes can be used in three scenarios, with examples.
1. If only a text representation of the allergy is known.
Table View
AllergyIntolerance.id[0] | UKCore-AllergyIntolerance-Sn-NonDrugAllergy-Example |
AllergyIntolerance.clinicalStatus[0].coding[0].system[0] | http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical |
AllergyIntolerance.clinicalStatus[0].coding[0].code[0] | active |
AllergyIntolerance.clinicalStatus[0].coding[0].display[0] | Active |
AllergyIntolerance.verificationStatus[0].coding[0].system[0] | http://terminology.hl7.org/CodeSystem/allergyintolerance-verification |
AllergyIntolerance.verificationStatus[0].coding[0].code[0] | confirmed |
AllergyIntolerance.verificationStatus[0].coding[0].display[0] | Confirmed |
AllergyIntolerance.code[0].coding[0].system[0] | http://snomed.info/sct |
AllergyIntolerance.code[0].coding[0].code[0] | 196471000000108 |
AllergyIntolerance.code[0].coding[0].display[0] | Transfer-degraded non-drug allergy (record artifact) |
AllergyIntolerance.code[0].text[0] | Latex |
AllergyIntolerance.patient[0].reference[0] | Patient/UKCore-Patient-RichardSmith-Example |
Tree View
AllergyIntolerance |
id : UKCore-AllergyIntolerance-Sn-NonDrugAllergy-Example |
clinicalStatus |
coding |
system : http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical |
code : active |
display : Active |
verificationStatus |
coding |
system : http://terminology.hl7.org/CodeSystem/allergyintolerance-verification |
code : confirmed |
display : Confirmed |
code |
coding |
system : http://snomed.info/sct |
code : 196471000000108 |
display : Transfer-degraded non-drug allergy (record artifact) |
text : Latex |
patient |
reference : Patient/UKCore-Patient-RichardSmith-Example |
XML View
<AllergyIntolerance xmlns="http://hl7.org/fhir"> <id value="UKCore-AllergyIntolerance-Sn-NonDrugAllergy-Example" /> <clinicalStatus> <coding> <system value="http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical" /> <code value="active" /> <display value="Active" /> </coding> </clinicalStatus> <verificationStatus> <coding> <system value="http://terminology.hl7.org/CodeSystem/allergyintolerance-verification" /> <code value="confirmed" /> <display value="Confirmed" /> </coding> </verificationStatus> <!-- **************Snippet start************** --> <code> <coding> <system value="http://snomed.info/sct" /> <code value="196471000000108" /> <display value="Transfer-degraded non-drug allergy (record artifact)" /> </coding> <text value="Latex" /> </code> <!-- **************Snippet end************** --> <patient> <reference value="Patient/UKCore-Patient-RichardSmith-Example" /> </patient> </AllergyIntolerance>
JSON View
{ "resourceType": "AllergyIntolerance", "id": "UKCore-AllergyIntolerance-Sn-NonDrugAllergy-Example", "clinicalStatus": { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical", "code": "active", "display": "Active" } ] }, "verificationStatus": { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/allergyintolerance-verification", "code": "confirmed", "display": "Confirmed" } ] }, "code": { "coding": [ { "system": "http://snomed.info/sct", "code": "196471000000108", "display": "Transfer-degraded non-drug allergy (record artifact)" } ], "text": "Latex" }, "patient": { "reference": "Patient/UKCore-Patient-RichardSmith-Example" } }
2. If a text representation of the allergy is known but any associated coding is not recognised by the system.
Table View
AllergyIntolerance.id[0] | UKCore-AllergyIntolerance-Sn-DrugAllergy-Example |
AllergyIntolerance.clinicalStatus[0].coding[0].system[0] | http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical |
AllergyIntolerance.clinicalStatus[0].coding[0].code[0] | active |
AllergyIntolerance.clinicalStatus[0].coding[0].display[0] | Active |
AllergyIntolerance.verificationStatus[0].coding[0].system[0] | http://terminology.hl7.org/CodeSystem/allergyintolerance-verification |
AllergyIntolerance.verificationStatus[0].coding[0].code[0] | confirmed |
AllergyIntolerance.verificationStatus[0].coding[0].display[0] | Confirmed |
AllergyIntolerance.code[0].coding[0].system[0] | http://snomed.info/sct |
AllergyIntolerance.code[0].coding[0].code[0] | 196461000000101 |
AllergyIntolerance.code[0].coding[0].display[0] | Transfer-degraded drug allergy (record artifact) |
AllergyIntolerance.code[0].text[0] | 9339101000001105 | Septrin |
AllergyIntolerance.patient[0].reference[0] | Patient/UKCore-Patient-RichardSmith-Example |
Tree View
AllergyIntolerance |
id : UKCore-AllergyIntolerance-Sn-DrugAllergy-Example |
clinicalStatus |
coding |
system : http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical |
code : active |
display : Active |
verificationStatus |
coding |
system : http://terminology.hl7.org/CodeSystem/allergyintolerance-verification |
code : confirmed |
display : Confirmed |
code |
coding |
system : http://snomed.info/sct |
code : 196461000000101 |
display : Transfer-degraded drug allergy (record artifact) |
text : 9339101000001105 | Septrin |
patient |
reference : Patient/UKCore-Patient-RichardSmith-Example |
XML View
<AllergyIntolerance xmlns="http://hl7.org/fhir"> <id value="UKCore-AllergyIntolerance-Sn-DrugAllergy-Example" /> <clinicalStatus> <coding> <system value="http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical" /> <code value="active" /> <display value="Active" /> </coding> </clinicalStatus> <verificationStatus> <coding> <system value="http://terminology.hl7.org/CodeSystem/allergyintolerance-verification" /> <code value="confirmed" /> <display value="Confirmed" /> </coding> </verificationStatus> <!-- **************Snippet start************** --> <code> <coding> <system value="http://snomed.info/sct" /> <code value="196461000000101" /> <display value="Transfer-degraded drug allergy (record artifact)" /> </coding> <text value="9339101000001105 | Septrin" /> </code> <!-- **************Snippet end************** --> <patient> <reference value="Patient/UKCore-Patient-RichardSmith-Example" /> </patient> </AllergyIntolerance>
JSON View
{ "resourceType": "AllergyIntolerance", "id": "UKCore-AllergyIntolerance-Sn-DrugAllergy-Example", "clinicalStatus": { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical", "code": "active", "display": "Active" } ] }, "verificationStatus": { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/allergyintolerance-verification", "code": "confirmed", "display": "Confirmed" } ] }, "code": { "coding": [ { "system": "http://snomed.info/sct", "code": "196461000000101", "display": "Transfer-degraded drug allergy (record artifact)" } ], "text": "9339101000001105 | Septrin" }, "patient": { "reference": "Patient/UKCore-Patient-RichardSmith-Example" } }
Note: “Septrin” is a long discontinued brand name of an antibiotic.
3. If a pre-coordinated allergy code is known which this is not part of the permitted value set for causative agent defined above.
AllergyIntolerance.id[0] | UKCore-AllergyIntolerance-Sn-DrugAllergyToEggProtein-Example |
AllergyIntolerance.clinicalStatus[0].coding[0].system[0] | http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical |
AllergyIntolerance.clinicalStatus[0].coding[0].code[0] | active |
AllergyIntolerance.clinicalStatus[0].coding[0].display[0] | Active |
AllergyIntolerance.verificationStatus[0].coding[0].system[0] | http://terminology.hl7.org/CodeSystem/allergyintolerance-verification |
AllergyIntolerance.verificationStatus[0].coding[0].code[0] | confirmed |
AllergyIntolerance.verificationStatus[0].coding[0].display[0] | Confirmed |
AllergyIntolerance.code[0].coding[0].system[0] | http://snomed.info/sct |
AllergyIntolerance.code[0].coding[0].code[0] | 196461000000101 |
AllergyIntolerance.code[0].coding[0].display[0] | Transfer-degraded drug allergy (record artifact) |
AllergyIntolerance.code[0].text[0] | 213020009 | Allergy to egg protein |
AllergyIntolerance.patient[0].reference[0] | Patient/UKCore-Patient-RichardSmith-Example |
Tree View
AllergyIntolerance |
id : UKCore-AllergyIntolerance-Sn-DrugAllergyToEggProtein-Example |
clinicalStatus |
coding |
system : http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical |
code : active |
display : Active |
verificationStatus |
coding |
system : http://terminology.hl7.org/CodeSystem/allergyintolerance-verification |
code : confirmed |
display : Confirmed |
code |
coding |
system : http://snomed.info/sct |
code : 196461000000101 |
display : Transfer-degraded drug allergy (record artifact) |
text : 213020009 | Allergy to egg protein |
patient |
reference : Patient/UKCore-Patient-RichardSmith-Example |
XML View
<AllergyIntolerance xmlns="http://hl7.org/fhir"> <id value="UKCore-AllergyIntolerance-Sn-DrugAllergyToEggProtein-Example" /> <clinicalStatus> <coding> <system value="http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical" /> <code value="active" /> <display value="Active" /> </coding> </clinicalStatus> <verificationStatus> <coding> <system value="http://terminology.hl7.org/CodeSystem/allergyintolerance-verification" /> <code value="confirmed" /> <display value="Confirmed" /> </coding> </verificationStatus> <!-- **************Snippet start************** --> <code> <coding> <system value="http://snomed.info/sct" /> <code value="196461000000101" /> <display value="Transfer-degraded drug allergy (record artifact)" /> </coding> <text value="213020009 | Allergy to egg protein" /> </code> <!-- **************Snippet end************** --> <patient> <reference value="Patient/UKCore-Patient-RichardSmith-Example" /> </patient> </AllergyIntolerance>
JSON View
{ "resourceType": "AllergyIntolerance", "id": "UKCore-AllergyIntolerance-Sn-DrugAllergyToEggProtein-Example", "clinicalStatus": { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical", "code": "active", "display": "Active" } ] }, "verificationStatus": { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/allergyintolerance-verification", "code": "confirmed", "display": "Confirmed" } ] }, "code": { "coding": [ { "system": "http://snomed.info/sct", "code": "196461000000101", "display": "Transfer-degraded drug allergy (record artifact)" } ], "text": "213020009 | Allergy to egg protein" }, "patient": { "reference": "Patient/UKCore-Patient-RichardSmith-Example" } }
Handling of 'No known allergies'
There can be an explicit assertion of ‘No Known Allergies’ using the SNOMED CT 'No known allergy' hierarchy 716186003 | No known allergy. The parent concept, or any child concept MAY be used.
Example of AllergyIntolerance.code
usage for 'No known drug allergy':
Table View
AllergyIntolerance.id[0] | UKCore-AllergyIntolerance-Sn-NegHandlNoKnownAllergies-Example |
AllergyIntolerance.clinicalStatus[0].coding[0].system[0] | http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical |
AllergyIntolerance.clinicalStatus[0].coding[0].code[0] | active |
AllergyIntolerance.clinicalStatus[0].coding[0].display[0] | Active |
AllergyIntolerance.verificationStatus[0].coding[0].system[0] | http://terminology.hl7.org/CodeSystem/allergyintolerance-verification |
AllergyIntolerance.verificationStatus[0].coding[0].code[0] | confirmed |
AllergyIntolerance.verificationStatus[0].coding[0].display[0] | Confirmed |
AllergyIntolerance.code[0].coding[0].system[0] | http://snomed.info/sct |
AllergyIntolerance.code[0].coding[0].code[0] | 409137002 |
AllergyIntolerance.code[0].coding[0].display[0] | No known drug allergy (situation) |
AllergyIntolerance.patient[0].reference[0] | Patient/UKCore-Patient-RichardSmith-Example |
Tree View
AllergyIntolerance |
id : UKCore-AllergyIntolerance-Sn-NegHandlNoKnownAllergies-Example |
clinicalStatus |
coding |
system : http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical |
code : active |
display : Active |
verificationStatus |
coding |
system : http://terminology.hl7.org/CodeSystem/allergyintolerance-verification |
code : confirmed |
display : Confirmed |
code |
coding |
system : http://snomed.info/sct |
code : 409137002 |
display : No known drug allergy (situation) |
patient |
reference : Patient/UKCore-Patient-RichardSmith-Example |
XML View
<AllergyIntolerance xmlns="http://hl7.org/fhir"> <id value="UKCore-AllergyIntolerance-Sn-NegHandlNoKnownAllergies-Example" /> <clinicalStatus> <coding> <system value="http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical" /> <code value="active" /> <display value="Active" /> </coding> </clinicalStatus> <verificationStatus> <coding> <system value="http://terminology.hl7.org/CodeSystem/allergyintolerance-verification" /> <code value="confirmed" /> <display value="Confirmed" /> </coding> </verificationStatus> <!-- **************Snippet start************** --> <code> <coding> <system value="http://snomed.info/sct" /> <code value="409137002" /> <display value="No known drug allergy (situation)" /> </coding> </code> <!-- **************Snippet end************** --> <patient> <reference value="Patient/UKCore-Patient-RichardSmith-Example" /> </patient> </AllergyIntolerance>
JSON View
{ "resourceType": "AllergyIntolerance", "id": "UKCore-AllergyIntolerance-Sn-NegHandlNoKnownAllergies-Example", "clinicalStatus": { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical", "code": "active", "display": "Active" } ] }, "verificationStatus": { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/allergyintolerance-verification", "code": "confirmed", "display": "Confirmed" } ] }, "code": { "coding": [ { "system": "http://snomed.info/sct", "code": "409137002", "display": "No known drug allergy (situation)" } ] }, "patient": { "reference": "Patient/UKCore-Patient-RichardSmith-Example" } }
If other AllergyIntolerance
resources exist in the patient record with a AllergyIntolerance.clinicalStatus
of active
then the system SHALL ignore the 'No Known Allergies' resource instance. The existence of recorded and active allergies takes precedence over instances of 'No Known Allergies' records.
Use of plain text only
The representation of the causative agent as text is supported within the FHIR standard but this SHOULD only be used as a last resort if a suitable coded term does not exist within the SNOMED CT terminology or if using a degraded allergy code is not appropriate.
Use of nullFlavor
The UK Core recommendation is that the nullFlavor
is not used for the causative agent, even though it is permitted within the FHIR standard.
patient
Where possible, it is expected that the resource being referenced SHOULD conform to Profile UKCore-Patient.
encounter
Where possible, it is expected that the resource being referenced SHOULD conform to Profile UKCore-Encounter.
onset[x]
Record of the date and/or time of the onset of the reaction caused by the allergy or intolerance which can be recorded in one of five ways;
onsetDateTime
onsetAge
onsetPeriod
onsetRange
onsetString
.
Provider Systems
Provider systems are recommended to support at least AllergyIntolerance.onsetDateTime
and AllergyIntolerance.onsetAge
where this date is available.
It is recommended not to record the onset using an AllergyIntolerance.onsetPeriod
or AllergyIntolerance.onsetRange
as these data types are complex and less useful. If the exact onset date is not known, but was between two known dates, e.g. 2018 and 2019, then use the lower/older date as the AllergyIntolerance.onsetDateTime
instead of using an AllergyIntolerance.onsetPeriod
.
It is recommended not to record the onset using an AllergyIntolerance.onsetString
as this data will not be machine processable.
Provider Systems
Consumer systems SHALL be able to handle any of the AllergyIntolerance.onset
data types.
recordedDate
The date the first version of the resource instance was recorded.
The recordedDate represents when this particular AllergyIntolerance
record was created in the system, which is often a system-generated date.
If the instance of the resource is updated via an operation like a RESTful PATCH
or PUT
then the AllergyIntolerance.recordedDate
is not updated and remains the date the resource instance was recorded.
recorder
A reference to the individual who recorded the record and takes responsibility for its content.
Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles:
- Profile UKCore-Patient
- Profile UKCore-Practitioner
- Profile UKCore-PractitionerRole
- Profile UKCore-RelatedPerson
asserter
A reference to the source of the information about the allergy.
Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles:
- Profile UKCore-Patient
- Profile UKCore-Practitioner
- Profile UKCore-PractitionerRole
- Profile UKCore-RelatedPerson
Provider Systems
Provider systems SHOULD provide at least the following minimum data within the referenced resource.
Practitioner
- identifier
- name
PractitionerRole
- identifier
- practitioner (as above) OR organisation.identifier OR healthcareService.identifier
Patient
- identifier:nhsNumber
- name
RelatedPerson
- identifier
- name
- patient
Where a human asserter is not captured or cannot be confirmed, i.e. the asserter is not a Practitioner
, Patient
or RelatedPerson
, the provider systems SHOULD reference a PractitionerRole.organisation
and/or PractitionerRole.healthcareService
within a PractitionerRole
resource, using the associated ODS code, as per the following example, asserted by "MILTON KEYNES UNIVERSITY HOSPITAL NHS FOUNDATION TRUST".
Example of PractitionerRole.organisation
for ODS code usage:
Table View
PractitionerRole.id[0] | UKCore-PractitionerRole-Sn-Organization-Code-Example |
PractitionerRole.identifier[0].system[0] | https://fhir.nhs.uk/Id/sds-role-profile-id |
PractitionerRole.identifier[0].value[0] | 100334993514 |
PractitionerRole.organization[0].identifier[0].system[0] | https://fhir.nhs.uk/Id/ods-organization-code |
PractitionerRole.organization[0].identifier[0].value[0] | RD8 |
PractitionerRole.organization[0].display[0] | MILTON KEYNES UNIVERSITY HOSPITAL NHS FOUNDATION TRUST |
Tree View
PractitionerRole |
id : UKCore-PractitionerRole-Sn-Organization-Code-Example |
identifier |
system : https://fhir.nhs.uk/Id/sds-role-profile-id |
value : 100334993514 |
organization |
identifier |
system : https://fhir.nhs.uk/Id/ods-organization-code |
value : RD8 |
display : MILTON KEYNES UNIVERSITY HOSPITAL NHS FOUNDATION TRUST |
XML View
<PractitionerRole xmlns="http://hl7.org/fhir"> <id value="UKCore-PractitionerRole-Sn-Organization-Code-Example" /> <!-- **************snippet start************** --> <identifier> <system value="https://fhir.nhs.uk/Id/sds-role-profile-id" /> <value value="100334993514" /> </identifier> <organization> <identifier> <system value="https://fhir.nhs.uk/Id/ods-organization-code" /> <value value="RD8" /> </identifier> <display value="MILTON KEYNES UNIVERSITY HOSPITAL NHS FOUNDATION TRUST" /> </organization> <!-- **************snippet end************** --> </PractitionerRole>
JSON View
{ "resourceType": "PractitionerRole", "id": "UKCore-PractitionerRole-Sn-Organization-Code-Example", "identifier": [ { "system": "https://fhir.nhs.uk/Id/sds-role-profile-id", "value": "100334993514" } ], "organization": { "identifier": { "system": "https://fhir.nhs.uk/Id/ods-organization-code", "value": "RD8" }, "display": "MILTON KEYNES UNIVERSITY HOSPITAL NHS FOUNDATION TRUST" } }
lastOccurrence
Represents the date and/or time of the last known occurrence of a reaction event.
note
An optional element for when the clinical user wishes to provide supporting textual information for the allergy record that cannot be conveyed within other elements of the resource.
Provider Systems
Where a provider system only has the capability to record a note at one level it SHOULD populate the AllergyIntolerance.note
elements with any notes data captured within the system, irrespective of the data level that the system uses to capture that data.
Where a provider system has the capability to record a note at both the AllergyIntolerance
and at the AllergyIntolerance.reaction
level it SHOULD populate both with the relevant notes applicable to each level.
Provider Systems
Consumer systems SHALL be able to handle both multiple AllergyIntolerance.note
and multiple AllergyIntolerance.reaction.note
elements.
reaction
Details about each adverse reaction event linked to exposure to the identified substance.
The AllergyIntolerance.reaction
is optional, but where a AllergyIntolerance.reaction.severity
is available in the provider system it SHALL be included to convey severity even if no other reaction details are explicitly available. If this is the case the AllergyIntolerance.reaction.manifestation
SHALL be coded as the nullFlavor NI
.
reaction.substance
An element to record the specific substance or pharmaceutical product considered to be responsible for event using the ValueSet UKCore-AllergySubstance
reaction.manifestation
A mandatory element if a AllergyIntolerance.reaction
is recorded for the clinical symptoms and/or signs that are observed or associated with the adverse reaction event.
Use nullFlavor NI
for the case when a AllergyIntolerance.reaction.severity
needs to be shared but where a AllergyIntolerance.reaction.manifestation
is not known.
reaction.severity
An optional value from a required terminology binding containing the values;
mild
moderate
severe
Provider Systems
Where a severity
is available in the provider system it SHALL be included to convey severity even if no other reaction details are explicitly available.
Where the severity is not known, this element SHOULD be omitted.
Provider Systems
Use of this element when populated as severe
MAY be used to express life threatening allergies, used in conjunction with the AllergyIntolerance.criticality
element.
An omitted AllergyIntolerance.reaction.severity
will either mean severity data is not available within the provider system or the severity is not known by the provider system.
reaction.exposureRoute
An optional element to identify the route by which the patient was exposed to the substance.
Provider Systems
If this data is available the binding SHOULD be to the ValueSet UKCore-SubstanceOrProductAdministrationRoute.
Provider Systems
Consumer systems are recommended not to include this coded information within automated clinical decision support. This is because it could either mean two quite different things;
- The reaction only occurs if the substance enters the body via the specified route, implying the use of other routes is safe.
OR
- The reaction was identified when the substance entered the body via the specified route, but could also react when using other routes.
reaction.note
An optional element for when the clinical user wishes to provide supporting textual information for the reaction that cannot be conveyed within other elements of the backbone element.
See the related guidance above for AllergyIntolerance.note
.