Immunization (PS-BC)

Immunization Profile

BC will use PanCanadian Patient Summary(PS-CA) Immunization Profile for now with the following differences. 

 

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
id0..1string
extensionI0..*Extension
vaccineSctIpsFreeSetΣ0..*CodingBinding
atcClassΣ0..*CodingBinding
CVCTradenameΣ0..*CodingBinding
CVCGenericΣ0..*CodingBinding
absentOrUnknownImmunizationΣ0..*CodingBinding
textΣ0..1string
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
id0..1string
extensionI0..*Extension
siteIPSΣ0..*Data Type: Coding (PS-CA)Binding
siteCVCΣ0..*Data Type: Coding (PS-CA)Binding
HumanSubstanceAdministrationSiteV3Σ0..*Data Type: Coding (PS-CA)Binding
textS Σ0..1string
id0..1string
extensionI0..*Extension
routeEDQMΣ0..*Data Type: Coding (PS-CA)Binding
routeCVCΣ0..*Data Type: Coding (PS-CA)Binding
RouteOfAdministrationV3Σ0..*Data Type: Coding (PS-CA)Binding
textS Σ0..1string
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)
id0..1string
extensionI0..*Extension
targetDiseasesSctIpsFreeSetΣ0..*CodingBinding
targetDiseaseCVCΣ0..*CodingBinding
textΣ0..1string
doseNumberPositiveIntpositiveInt
doseNumberStringstring
seriesDosesPositiveIntpositiveInt
seriesDosesStringstring

 

 

BC Immunization FHIR Profile for 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. Following notes should be considered in implementation

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

  • Site & Route

    • Site and Route are 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.

    • LRA can map the display value in text.

  • ProtocolApplied[x]

    • DoseNumberPositiveInt is preferred to be mapped

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

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