| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | L Type | L Description & Constraints | Comments |
|---|
  AllergyIntolerance | | 0..* | AllergyIntolerance | Argonaut AllergyIntolerance Profile
| C | 0..* | AllergyIntolerance | Allergy or Intolerance (generally: Risk of adverse reaction to a substance)
| - Elements differ in short: 'Argonaut AllergyIntolerance Profile' vs 'Allergy or Intolerance (generally: Risk of adverse reaction to a substance)'
- Elements differ in definition: 'Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance.' vs '\-'
- Elements differ in 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.' vs '\-'
- StructureDefinition USCoreAllergyIntolerance has added constraint that is not found in Argonaut AllergyIntolerance Profile and it is uncertain whether they are compatible (verificationStatus.coding.where(system = 'http://terminology.hl7.org/CodeSystem/allergyintolerance-verification' and code = 'entered-in-error').exists() or clinicalStatus.exists())
- StructureDefinition USCoreAllergyIntolerance has added constraint that is not found in Argonaut AllergyIntolerance Profile and it is uncertain whether they are compatible (verificationStatus.coding.where(system = 'http://terminology.hl7.org/CodeSystem/allergyintolerance-verification' and code = 'entered-in-error').empty() or clinicalStatus.empty())
- StructureDefinition USCoreAllergyIntolerance has added constraint that is not found in Argonaut AllergyIntolerance Profile and it is uncertain whether they are compatible (contained.contained.empty())
- StructureDefinition USCoreAllergyIntolerance has added constraint that is not found in Argonaut AllergyIntolerance Profile and it is uncertain whether they are compatible (contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty())
- StructureDefinition USCoreAllergyIntolerance has added constraint that is not found in Argonaut AllergyIntolerance Profile and it is uncertain whether they are compatible (contained.meta.versionId.empty() and contained.meta.lastUpdated.empty())
- StructureDefinition USCoreAllergyIntolerance has added constraint that is not found in Argonaut AllergyIntolerance Profile and it is uncertain whether they are compatible (contained.meta.security.empty())
- StructureDefinition USCoreAllergyIntolerance has added constraint that is not found in Argonaut AllergyIntolerance Profile and it is uncertain whether they are compatible (text.`div`.exists())
|
 id | Σ | 0..1 | id | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact | - Elements differ in 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. Bundles always have an id, though it is usually a generated UUID.' vs '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 | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource | - Elements differ in definition: 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.' vs '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.'
|
| implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created | ?!Σ | 0..1 | uri | A set of rules under which this content was created | - Elements differ in 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.' vs '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.'
- Elements differ in 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 as much as possible.' vs '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 | code | Language of the resource content
Binding: todo (required): A human language.
| | 0..1 | code | Language of the resource content
Binding: todo (preferred): A human language.
| - Elements differ in 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).' vs '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).'
|
| text | | 0..1 | Narrative | Text summary of the resource, for human interpretation | | 0..1 | Narrative | Text summary of the resource, for human interpretation | - Elements differ in definition: 'A human-readable narrative that contains a summary of the resource, and may 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.' vs '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.'
- Elements differ in comments: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs '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 | Contained, inline Resources
| | 0..* | Resource | Contained, inline Resources
| - Elements differ in 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.' vs '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 | | 0..* | Extension | Additional Content defined by implementations
| | 0..* | Extension | Additional content defined by implementations
| - Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource. In order 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.' vs '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.'
|
 modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored
| ?! | 0..* | Extension | Extensions that cannot be ignored
| - Elements differ in 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. Usually modifier elements provide negation or qualification. In order 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.' vs '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).'
|
| identifier | Σ | 0..* | Identifier | External ids for this item
| Σ | 0..* | Identifier | External ids for this item
| - Elements differ in definition: 'This records identifiers associated with this allergy/intolerance concern that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation).' vs '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.'
|
| onset | Σ | 0..1 | dateTime | Date(/time) when manifestations showed | | | | | |
| recordedDate | Σ | 0..1 | dateTime | When recorded | | 0..1 | dateTime | Date first version of the resource instance was recorded | - Elements differ in short: 'When recorded' vs 'Date first version of the resource instance was recorded'
- Elements differ in definition: 'Date when the sensitivity was recorded.' vs 'The recordedDate represents when this particular AllergyIntolerance record was created in the system, which is often a system-generated date.'
|
| recorder | Σ | 0..1 | Reference(Practitioner | Patient) | Who recorded the sensitivity | | 0..1 | Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) | Who recorded the sensitivity | - Elements differ in definition: 'Individual who recorded the record and takes responsibility for its conten.' vs 'Individual who recorded the record and takes responsibility for its content.'
|
| patient | S | 1..1 | Reference(http://fhir.org/guides/argonaut/StructureDefinition/argo-patient) | Who the sensitivity is for | SΣ | 1..1 | Reference(http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient) | (USCDI) Who the sensitivity is for | - Elements differ in short: 'Who the sensitivity is for' vs '(USCDI) Who the sensitivity is for'
|
| reporter | Σ | 0..1 | Reference(Patient | RelatedPerson | Practitioner) | Source of the information about the allergy | | | | | |
| substance | S | 1..1 | CodeableConcept | Substance, (or class) considered to be responsible for risk
Binding: todo (extensible): Type of substance responsible for reaction.
| | | | | |
| status | ?!S | 1..1 | code | active | unconfirmed | confirmed | inactive | resolved | refuted | entered-in-error
Binding: todo (required) | | | | | |
| criticality | Σ | 0..1 | code | CRITL | CRITH | CRITU
Binding: todo (required): Estimate of the potential clinical harm, or seriousness, of a reaction to an identified Substance.
| Σ | 0..1 | code | low | high | unable-to-assess
Binding: todo (required): Estimate of the potential clinical harm, or seriousness, of a reaction to an identified substance.
| - Elements differ in short: 'CRITL | CRITH | CRITU' vs 'low | high | unable-to-assess'
- Elements differ in 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).' vs '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.'
|
| type | Σ | 0..1 | code | allergy | intolerance - Underlying mechanism (if known)
Binding: todo (required): Identification of the underlying physiological mechanism for a Reaction Risk.
| Σ | 0..1 | code | allergy | intolerance - Underlying mechanism (if known)
Binding: todo (required): Identification of the underlying physiological mechanism for a Reaction Risk.
| - Elements differ in 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 may 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 may 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.' vs '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.'
|
| category | Σ | 0..1 | code | food | medication | environment | other - Category of Substance
Binding: todo (required): Category of an identified Substance.
| Σ | 0..* | code | food | medication | environment | biologic
Binding: todo (required): Category of an identified substance associated with allergies or intolerances.
| - Elements differ in short: 'food | medication | environment | other - Category of Substance' vs 'food | medication | environment | biologic'
- Elements differ in 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.' vs '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.'
- Element maximum cardinalities differ: '1' vs '2147483647'
- Elements differ in description: 'Category of an identified Substance.' vs 'Category of an identified substance associated with allergies or intolerances.'
- Elements differ in description: 'Category of an identified Substance.' vs 'Category of an identified substance associated with allergies or intolerances.'
|
| lastOccurence | Σ | 0..1 | dateTime | Date(/time) of last known occurrence of a reaction | | | | | |
| note | | 0..1 | Annotation | Additional text not captured in other fields | | 0..* | Annotation | Additional text not captured in other fields
| - Element maximum cardinalities differ: '1' vs '2147483647'
|
| reaction | | 0..* | BackboneElement | Adverse Reaction Events linked to exposure to substance
| S | 0..* | BackboneElement | (USCDI) Adverse Reaction Events linked to exposure to substance
| - Elements differ in short: 'Adverse Reaction Events linked to exposure to substance' vs '(USCDI) Adverse Reaction Events linked to exposure to substance'
- Elements differ in definition for mustSupport: 'false' vs 'true'
|
 id | | 0..1 | id | xml:id (or equivalent in JSON) | | 0..1 | string | Unique id for inter-element referencing | - Elements differ in short: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
- Elements differ in definition: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
|
| extension | | 0..* | Extension | Additional Content defined by implementations
| | 0..* | Extension | Additional content defined by implementations
| - Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. In order 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.' vs '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.'
|
| modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored
| ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized
| - Elements differ in short: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized'
- Elements differ in 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 that contains it. Usually modifier elements provide negation or qualification. In order 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.' vs '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).'
|
| substance | Σ | 0..1 | CodeableConcept | Specific substance considered to be responsible for event
Binding: todo (example): Codes defining the type of the substance.
| | 0..1 | CodeableConcept | Specific substance or pharmaceutical product considered to be responsible for event
Binding: todo (example): Codes defining the type of the substance (including pharmaceutical products).
| - Elements differ in short: 'Specific substance considered to be responsible for event' vs 'Specific substance or pharmaceutical product considered to be responsible for event'
- Elements differ in definition: 'Identification of the specific substance considered to be responsible for the Adverse Reaction event. Note: the substance for a specific reaction may be different to the substance identified as the cause of the risk, but must be consistent with it. For instance, it may be a more specific substance (e.g. a brand medication) or a composite substance that includes the identified substance. It must be clinically safe to only process the AllergyIntolerance.substance and ignore the AllergyIntolerance.event.substance.' vs '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.'
- Elements differ in comments: 'Coding of the specific substance with a terminology capable of triggering decision support should be used wherever possible. The substance field allows for the use of a specific substance or a group or class of substances, for example "Penicillins". The specific substance field could be used for Amoxycillin. Duplication is acceptable when a specific substance has been recorded in the 'substance' field.' vs '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'.'
- Elements differ in binding.description: 'Codes defining the type of the substance.' vs 'Codes defining the type of the substance (including pharmaceutical products).'
|
| certainty | Σ | 0..1 | code | unlikely | likely | confirmed - clinical certainty about the specific substance
Binding: todo (required): Statement about the degree of clinical certainty that a Specific Substance was the cause of the Manifestation in an reaction event.
| | | | | |
| manifestation | Σ | 1..* | CodeableConcept | Clinical symptoms/signs associated with the Event
Binding: todo (example): Clinical symptoms and/or signs that are observed or associated with an Adverse Reaction Event.
| S | 1..* | CodeableConcept | (USCDI) Clinical symptoms/signs associated with the Event
Binding: todo (extensible)
| - Elements differ in short: 'Clinical symptoms/signs associated with the Event' vs '(USCDI) Clinical symptoms/signs associated with the Event'
- Elements differ in definition for mustSupport: 'false' vs 'true'
|
| description | | 0..1 | string | Description of the event as a whole | | 0..1 | string | Description of the event as a whole | |
| onset | Σ | 0..1 | dateTime | Date(/time) when manifestations showed | | 0..1 | dateTime | Date(/time) when manifestations showed | |
| severity | Σ | 0..1 | code | mild | moderate | severe (of event as a whole)
Binding: todo (required): Clinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations.
| | 0..1 | code | mild | moderate | severe (of event as a whole)
Binding: todo (required): Clinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations.
| - Elements differ in comments: 'It is acknowledged that this assessment is very subjective. There may be some some specific practice domains where objective scales have been applied. Objective scales can be included in this model as extensions.' vs '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.'
|
| exposureRoute | Σ | 0..1 | CodeableConcept | How the subject was exposed to the substance
Binding: todo (example): A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject.
| | 0..1 | CodeableConcept | How the subject was exposed to the substance
Binding: todo (example): 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..1 | Annotation | Text about event not captured in other fields | | 0..* | Annotation | Text about event not captured in other fields
| - Element maximum cardinalities differ: '1' vs '2147483647'
|
| clinicalStatus | | | | | ?!SΣC | 0..1 | CodeableConcept | (USCDI) active | inactive | resolved
Binding: todo (required) | |
| verificationStatus | | | | | ?!SΣC | 0..1 | CodeableConcept | (USCDI) unconfirmed | confirmed | refuted | entered-in-error
Binding: todo (required) | |
| code | | | | | SΣ | 1..1 | CodeableConcept | (USCDI) Code that identifies the allergy or intolerance
Binding: todo (extensible) | |
| encounter | | | | | | 0..1 | Reference(Encounter) | Encounter when the allergy or intolerance was asserted | |
| onset[x] | | | | | | 0..1 | dateTime, Age, Period, Range, string | When allergy or intolerance was identified | |
| asserter | | | | | Σ | 0..1 | Reference(Patient | RelatedPerson | Practitioner | PractitionerRole) | Source of the information about the allergy | |
| lastOccurrence | | | | | | 0..1 | dateTime | Date(/time) of last known occurrence of a reaction | |
Documentation for this format |