Resource type: immunization

Description

Describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party.

Elements

PathShortDefinitionComments
Immunization event informationDescribes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party.
identifierBusiness identifierA unique identifier assigned to this immunization record.
statuscompleted | entered-in-error | not-doneIndicates the current status of the immunization event.Will generally be set to show that the immunization has been completed or not done. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
statusReasonReason not doneIndicates the reason the immunization event was not performed.This is generally only used for the status of "not-done". The reason for performing the immunization event is captured in reasonCode, not here.
vaccineCodeVaccine product administeredVaccine that was administered or was to be administered.
patientWho was immunizedThe patient who either received or did not receive the immunization.
encounterEncounter immunization was part ofThe visit or admission or other contact between patient and health care provider the immunization was performed as part of.
occurrence[x]Vaccine administration dateDate vaccine administered or was to be administered.When immunizations are given a specific date and time should always be known. When immunizations are patient reported, a specific date might not be known. Although partial dates are allowed, an adult patient might not be able to recall the year a childhood immunization was given. An exact date is always preferable, but the use of the String data type is acceptable when an exact date is not known. A small number of vaccines (e.g. live oral typhoid vaccine) are given as a series of patient self-administered dose over a span of time. In cases like this, often, only the first dose (typically a provider supervised dose) is recorded with the occurrence indicating the date/time of the first dose.
recordedWhen the immunization was first captured in the subject's recordThe date the occurrence of the immunization was first captured in the record - potentially significantly after the occurrence of the event.
primarySourceIndicates context the data was recorded inAn indication that the content of the record is based on information from the person who administered the vaccine. This reflects the context under which the data was originally recorded.Reflects the “reliability” of the content.
reportOriginIndicates the source of a secondarily reported recordThe source of the data when the report of the immunization event is not based on information from the person who administered the vaccine.Should not be populated if primarySource = True, not required even if primarySource = False.
locationWhere immunization occurredThe service delivery location where the vaccine administration occurred.
manufacturerVaccine manufacturerName of vaccine manufacturer.
lotNumberVaccine lot numberLot number of the vaccine product.
expirationDateVaccine expiration dateDate vaccine batch expires.
siteBody site vaccine was administeredBody site where vaccine was administered.
routeHow vaccine entered bodyThe path by which the vaccine product is taken into the body.
doseQuantityAmount of vaccine administeredThe quantity of vaccine product that was administered.
performerWho performed eventIndicates who performed the immunization event.
performer.idUnique id for inter-element referencingUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
performer.extensionAdditional content defined by implementationsMay 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.
performer.modifierExtensionExtensions that cannot be ignored even if unrecognizedMay 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).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.
performer.functionWhat type of performance was doneDescribes the type of performance (e.g. ordering provider, administering provider, etc.).
performer.actorIndividual or organization who was performingThe practitioner or organization who performed the action.When the individual practitioner who performed the action is known, it is best to send.
noteAdditional immunization notesExtra information about the immunization that is not conveyed by the other attributes.
reasonCodeWhy immunization occurredReasons why the vaccine was administered.
reasonReferenceWhy immunization occurredCondition, Observation or DiagnosticReport that supports why the immunization was administered.
isSubpotentDose potencyIndication if a dose is considered to be subpotent. By default, a dose should be considered to be potent.Typically, the recognition of the dose being sub-potent is retrospective, after the administration (ex. notification of a manufacturer recall after administration). However, in the case of a partial administration (the patient moves unexpectedly and only some of the dose is actually administered), subpotency may be recognized immediately, but it is still important to record the event.
subpotentReasonReason for being subpotentReason why a dose is considered to be subpotent.
educationEducational material presented to patientEducational material presented to the patient (or guardian) at the time of vaccine administration.
education.idUnique id for inter-element referencingUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
education.extensionAdditional content defined by implementationsMay 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.
education.modifierExtensionExtensions that cannot be ignored even if unrecognizedMay 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).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.
education.documentTypeEducational material document identifierIdentifier of the material presented to the patient.
education.referenceEducational material reference pointerReference pointer to the educational material given to the patient if the information was on line.
education.publicationDateEducational material publication dateDate the educational material was published.
education.presentationDateEducational material presentation dateDate the educational material was given to the patient.
programEligibilityPatient eligibility for a vaccination programIndicates a patient's eligibility for a funding program.
fundingSourceFunding source for the vaccineIndicates the source of the vaccine actually administered. This may be different than the patient eligibility (e.g. the patient may be eligible for a publically purchased vaccine but due to inventory issues, vaccine purchased with private funds was actually administered).
reactionDetails of a reaction that follows immunizationCategorical data indicating that an adverse event is associated in time to an immunization.A reaction may be an indication of an allergy or intolerance and, if this is determined to be the case, it should be recorded as a new AllergyIntolerance resource instance as most systems will not query against past Immunization.reaction elements.
reaction.idUnique id for inter-element referencingUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
reaction.extensionAdditional content defined by implementationsMay 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.
reaction.modifierExtensionExtensions that cannot be ignored even if unrecognizedMay 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).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.
reaction.dateWhen reaction startedDate of reaction to the immunization.
reaction.detailAdditional information on reactionDetails of the reaction.
reaction.reportedIndicates self-reported reactionSelf-reported indicator.
protocolAppliedProtocol followed by the providerThe protocol (set of recommendations) being followed by the provider who administered the dose.
protocolApplied.idUnique id for inter-element referencingUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
protocolApplied.extensionAdditional content defined by implementationsMay 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.
protocolApplied.modifierExtensionExtensions that cannot be ignored even if unrecognizedMay 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).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.
protocolApplied.seriesName of vaccine seriesOne possible path to achieve presumed immunity against a disease - within the context of an authority.
protocolApplied.authorityWho is responsible for publishing the recommendationsIndicates the authority who published the protocol (e.g. ACIP) that is being followed.
protocolApplied.targetDiseaseVaccine preventatable disease being targettedThe vaccine preventable disease the dose is being administered against.
protocolApplied.doseNumber[x]Dose number within seriesNominal position in a series.The use of an integer is preferred if known. A string should only be used in cases where an integer is not available (such as when documenting a recurring booster dose).
protocolApplied.seriesDoses[x]Recommended number of doses for immunityThe recommended number of doses to achieve immunity.The use of an integer is preferred if known. A string should only be used in cases where an integer is not available (such as when documenting a recurring booster dose).

Scope and Usage

The Immunization resource is intended to cover the recording of current and historical administration of vaccines to patients across all healthcare disciplines in all care settings and all regions. This includes immunization of both humans and animals but does not include the administration of non-vaccine agents, even those that may have or claim to have immunological effects. While the terms "immunization" and "vaccination" are not clinically identical, for the purposes of the FHIR resources, the terms are used synonymously.

Additionally, the Immunization resource is expected to cover key concepts related to the creation, revision and querying of a patient's immunization history. This resource - through consultation with the Public Health work group - is believed to meet key use cases and information requirements as defined in the existing HL7 v2 immunization implementation guide, HL7 v3 POIZ domain and Immunization Domain Analysis Model.

Boundaries and Relationships

Administration of vaccines is intended to be handled using the Immunization resource. MedicationAdministration is intended for tracking the administration of non-vaccine medications. Some systems treat immunizations in the same way as any other medication administration. Such systems SHOULD use an immunization resource to represent these. If systems need to use a MedicationAdministration resource to capture vaccinations for workflow or other reasons, they SHOULD also expose an equivalent Immunization instance.

Immunization.reaction may be an indication of an allergy or intolerance. If this is deemed to be the case, a separate AllergyIntolerance resource instance should be created to indicate it, as most systems will not query against past Immunization.reaction.

Search Parameters

locationThe service delivery location or facility in which the vaccine was / was to be administeredImmunization.location
lot-numberVaccine Lot NumberImmunization.lotNumber
manufacturerVaccine ManufacturerImmunization.manufacturer
performerThe practitioner or organization who played a role in the vaccinationImmunization.performer.actor
reactionAdditional information on reactionImmunization.reaction.detail
reaction-dateWhen reaction startedImmunization.reaction.date
reason-codeReason why the vaccine was administeredImmunization.reasonCode
reason-referenceWhy immunization occurredImmunization.reasonReference
seriesThe series being followed by the providerImmunization.protocolApplied.series
statusImmunization event statusImmunization.status
status-reasonReason why the vaccine was not administeredImmunization.statusReason
target-diseaseThe target disease the dose is being administered againstImmunization.protocolApplied.targetDisease
vaccine-codeVaccine Product AdministeredImmunization.vaccineCode

Extension Definitions

These are extension definitions for this resource defined by the spec