Profile: Immunization

Definition

The Immunization Resource 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.

It 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. It 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.

Context

The Immunization (PS-CA) profile represents the constraints applied to the Immunization resource by the PS-CA project to represent a record of immunization in the patient summary. It is informed by the constraints of the Immunization IPS-UV profile and the Canadian Baseline Profile. It describes the event of a patient being administered a vaccination or a record of a vaccination as reported by a patient, a clinician or another party.

Links

Simplifier project page: Immunization(PS-CA) Profile

Derived from: Immunization(R4) Profile

Example: PS-CA:BC Immunization

Content

idΣ0..1string
metaΣ0..1Meta
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
extensionI0..*Extension
modifierExtension?! I0..*Extension
identifier0..*Identifier
statusS Σ ?!1..1codeBinding
statusReason0..1CodeableConcept
vaccineCodeS Σ1..1CodeableConceptBinding
id0..1string
extensionI0..*Extension
referenceS Σ I1..1string
typeΣ0..1uriBinding
identifierΣ0..1Identifier
displayΣ0..1string
encounterI0..1Reference(Encounter)
id0..1string
data-absent-reasonS I0..1Extension(code)
occurrenceDateTimedateTime
occurrenceStringstring
recorded0..1dateTime
primarySourceΣ0..1boolean
reportOrigin0..1CodeableConcept
locationI0..1Reference(Location)
manufacturerI0..1Reference(Organization)
lotNumber0..1string
expirationDate0..1date
site0..1CodeableConceptPSCA
route0..1CodeableConceptPSCABinding
doseQuantityI0..1SimpleQuantity
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
functionΣ0..1CodeableConceptBinding
actorΣ I1..1Reference(Practitioner | PractitionerRole | Organization)
noteΣ0..*Annotation
reasonCode0..*CodeableConcept
reasonReferenceI0..*Reference(Condition | Observation | DiagnosticReport)
isSubpotentΣ ?!0..1boolean
subpotentReason0..*CodeableConcept
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
documentType0..1string
reference0..1uri
publicationDate0..1dateTime
presentationDate0..1dateTime
programEligibility0..*CodeableConcept
fundingSource0..1CodeableConcept
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
date0..1dateTime
detailI0..1Reference(Observation)
reported0..1boolean
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
series0..1string
authorityI0..1Reference(Organization)
targetDisease0..*CodeableConceptBinding
doseNumberPositiveIntpositiveInt
doseNumberStringstring
seriesDosesPositiveIntpositiveInt
seriesDosesStringstring

 

Usage

The Immunization Resource is used to populate entries in the Immunization section of a Patient Summary. In BC, we have Immunization FHIR Profile provided by BCY, BC and Yukon Immunization Distribution Service (IDS). There are differences between PS-CA and BCY Immunization Profiles despite all required elements exists. BC-specific notes should be considered in implementation.

BC-specific Notes

Immunization data sources for Release 1 will be both the Panorama system (BCY) and the Provider EMR.

Immunization

  • Definition: 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.

Immunization.vaccineCode

  • Definition: Vaccine that was administered or was to be administered.

Immunization.occurrence[x]

  • Definition: Date vaccine administered or was to be administered.
  • Comments: Occurance[x] in BCY has a different structure than PS-CA:
    • PS-CA requires either a dateTime or a string. As it is described in the profile above, OccurranceDateTime should hold a precise DateTime value. On the other hand, OccuranceSting is to be used if the DateTime is estimated for any reason.

    • When recieving Immunization from IDS, if the valueBoolean of the extension under occurranceDateTimeis is set to true, it means that the dateTime provided is an estimate, So LRA should map it in occurranceString. If the boolean is set to False or the extension is not provided, then the occurranceDateTime is precise and it should be mapped into occurranceDateTime.

    • Since IDS always provides a value for Occurrence (precise or estimated) data-absent-reason extension under PS-CA is not applicable and not going to be mapped.

    The note implies that BCY wants to be able to clarify if the dateTime provided (YYYY, YYYY-MM, YYYY-MM-DD or YYYY-MM-DDThh:mm:ss+zz:zz) was estimated. You can send the dateEstimated extension from the source, you don't have (and shouldn't) map it to occurrenceString to meet PS-CA. It doesn't break PS-CA to add an extension in a jurisdiction, but if you want to see that extension socialized in PS-CA for good measure that would be a good candidate for a change request.

    If it is expected to have a record that wouldn't have occurrence data, then demonstrating support of data absent reason will be important. If you think that will pose a challenge to support that capability that can't be closed through development/change management - then it might be a candidate to request the removal of the MS flag on that extension.

Immunization.site

  • Definition: The site at which the vaccine was administered.
  • Comments: Site is optional on both profiles, PS-CA has tag (S) which means if the source has it, it should be sent, Text element it is not provided on BCY to prevent sending duplicate info in display and text. We can map the display value in text. The note indicates that it can map the display value provided in Site into the text field. If we are generating the patient summary, then the MustSupport flag on site.text is met. No change is required. Will not appear in the Release 1 UI.

Immunization.route

  • Definition: CVC Route of Administration
  • Comments: Route is optional on both profiles, PS-CA has tag (S) which means if the source has it, it should be sent, Text element it is not provided on BCY to prevent sending duplicate info in display and text. We can map the display value in text. The note indicates that it can map the display value provided in Route into the text field. If we are generating the patient summary, then the MustSupport flag on site.text is met. No change is required. Will not appear in the Release 1 UI.

Immunization.note

  • Definition: Extra information about the immunization that is not conveyed by the other attributes. Will not appear in the Release 1 UI.

Immunization.protocolApplied

  • Definition: The protocol (set of recommendations) being followed by the provider who administered the dose. Will not appear in the Release 1 UI.
  • Comments:
    • DoseNumberPositiveInt is preferred to be mapped

    • DoesNumberString should be mapped if documenting recurring booster or if integer value is not provided.

    • Since IDS always sends a string, this value should be mapped in DoesNumberString

Data Fields Mapping (PS-Form & FHIR Profile)

PS Form Fields FHIR Profile Elements
Agent Immunization.vaccineCode
Date Administered Immunization.occurrence[x]DateTime