Generated Narrative: StructureDefinition MODS-Allergy Name Flags Card. Type Description & Constraints MODS-Allergy 0..* Base MODS Allergy Instances of this logical model can be the target of a Reference #xD; subjectOfCare 1..1 Reference(MODS Subject of Care) Subject of care who is the focus of the record #xD; type 0..1 Coding The type of reaction experienced by the person (allergic, adverse, intolerance). Binding: MODS Allergy - Type of Reaction (required) #xD; causativeAgent 1..1 Coding The agent such as food, drug or substances that has caused or may cause an allergy, intolerance or adverse reaction in this person Or 'No known drug allergies or adverse reactions' Or 'Information not available'. Binding: UK Core Allergy Code (required) #xD; observer 0..1 Reference(MODS Care Worker) Care actor who made or recorded the observation. #xD; firstExperienced 0..1 dateTime When the reaction was first experienced i.e this may not be the first this has happened. May be a date or partial date (e.g. year) or text (e.g. during childhood) #xD; endDate 0..1 dateTime The date the allergy was diagnosed as ended #xD; comment 0..1 string Comment #xD; evidence 0..1 string Evidence #xD; reaction 0..* BackboneElement Reaction #xD; substance 0..1 Coding Substance Binding: UK Core Allergy Substance (required) #xD; description 0..1 Coding Description Binding: SNOMEDCTClinicalFindings (required) #xD; severity 0..1 Coding Severity Binding: MODS Allergy - Allergy Severity (required) #xD; route 0..1 Coding Route of exposure Binding: UK Core Substance Or Product Administration Route (required) #xD; Documentation for this format
Synanetics Ltd on behalf of DHSC/Social Care Interoperability Platform
MODS Definition: Details about the Subject of care's allergies or adverse reactions.
United Kingdom of Great Britain and Northern Ireland
Subject of care who is the focus of the record
The type of reaction experienced by the person (allergic, adverse, intolerance).
The agent such as food, drug or substances that has caused or may cause an allergy, intolerance or adverse reaction in this person Or 'No known drug allergies or adverse reactions' Or 'Information not available'.
Care actor who made or recorded the observation.
When the reaction was first experienced i.e this may not be the first this has happened. May be a date or partial date (e.g. year) or text (e.g. during childhood)
The date the allergy was diagnosed as ended
Any further comments on the person's allergies or adverse reactions.
Results of investigations that confirmed the certainty of the diagnosis. Examples might include results of skin prick allergy tests.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them