Generated Narrative: StructureDefinition ext-R5-AdverseEvent.supportingInfo Name Flags Card. Type Description & Constraints Extension 0..* Extension(4.0.1) R5: Supporting information relevant to the event (new) #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:item 1..1 Extension R5: Subject medical history or document relevant to this adverse event (new) #xD; url 1..1 uri "item" #xD; <a href="StructureDefinition-ext-R5-AdverseEvent.supportingInfo-definitions.html#Extension.extension:item.value[x]" title="Relevant past history for the subject. In a clinical care context, an example being a patient had an adverse event following a pencillin administration and the patient had a previously documented penicillin allergy. In a clinical trials context, an example is a bunion or rash that was present prior to the study. Additionally, the supporting item can be a document that is relevant to this instance of the adverse event that is not part of the subject's medical history. For example, a clinical note, staff list, or material safety data sheet (MSDS). Supporting information is not a contributing factor, preventive action, or mitigating action.">value[x] 1..1 Subject medical history or document relevant to this adverse event #xD; valueReference Reference(Cross-version Profile for R5.Condition for use in FHIR R4(0.1.0) | Condition | Cross-version Profile for R5.Observation for use in FHIR R4(0.1.0) | Observation | Cross-version Profile for R5.AllergyIntolerance for use in FHIR R4(0.1.0) | AllergyIntolerance | Cross-version Profile for R5.FamilyMemberHistory for use in FHIR R4(0.1.0) | FamilyMemberHistory | Cross-version Profile for R5.Immunization for use in FHIR R4(0.1.0) | Immunization | Cross-version Profile for R5.Procedure for use in FHIR R4(0.1.0) | Procedure | Cross-version Profile for R5.DocumentReference for use in FHIR R4(0.1.0) | Media | Cross-version Profile for R5.MedicationAdministration for use in FHIR R4(0.1.0) | MedicationAdministration | Cross-version Profile for R5.MedicationStatement for use in FHIR R4(0.1.0) | MedicationStatement | Cross-version Profile for R5.QuestionnaireResponse for use in FHIR R4(0.1.0) | QuestionnaireResponse) #xD; valueCodeableConcept CodeableConcept #xD; url 1..1 uri "http://hl7.org/fhir/5.0/StructureDefinition/extension-AdverseEvent.supportingInfo" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
R5: Supporting information relevant to the event (new)
R5: `AdverseEvent.supportingInfo` (new:BackboneElement)
This extension is part of the cross-version definitions generated to enable use of the element `AdverseEvent.supportingInfo` as defined in FHIR R5 in FHIR R4. The source element is defined as: `AdverseEvent.supportingInfo` 0..* `BackboneElement` Across FHIR versions, the element set has been mapped as: * R5: `AdverseEvent.supportingInfo` 0..* `BackboneElement` Following are the generation technical comments: Element `AdverseEvent.supportingInfo` has a context of AdverseEvent based on following the parent source element upwards and mapping to `AdverseEvent`. Element `AdverseEvent.supportingInfo` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `AdverseEvent.supportingInfo` has a context of AdverseEvent based on following the parent source element upwards and mapping to `AdverseEvent`. Element `AdverseEvent.supportingInfo` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
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
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
R5: Subject medical history or document relevant to this adverse event (new)
R5: `AdverseEvent.supportingInfo.item[x]` (new:CodeableConcept, Reference(Condition,Observation,AllergyIntolerance,FamilyMemberHistory,Immunization,Procedure,DocumentReference,MedicationAdministration,MedicationStatement,QuestionnaireResponse))
Element `AdverseEvent.supportingInfo.item[x]` is part of an existing definition because parent element `AdverseEvent.supportingInfo` requires a cross-version extension. Element `AdverseEvent.supportingInfo.item[x]` has a context of AdverseEvent based on following the parent source element upwards and mapping to `AdverseEvent`. Element `AdverseEvent.supportingInfo.item[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
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.
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Subject medical history or document relevant to this adverse event
Relevant past history for the subject. In a clinical care context, an example being a patient had an adverse event following a pencillin administration and the patient had a previously documented penicillin allergy. In a clinical trials context, an example is a bunion or rash that was present prior to the study. Additionally, the supporting item can be a document that is relevant to this instance of the adverse event that is not part of the subject's medical history. For example, a clinical note, staff list, or material safety data sheet (MSDS). Supporting information is not a contributing factor, preventive action, or mitigating action.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).