Canadian FHIR Baseline Profiles - Oct 9th Due Diligence Review Notes

Hi,

In Alberta, we use the following rules for 1 name persons:
- One name (Last Name only)
Clients with only a last name (i.e. family name) should have the last name entered in both the last name and first name fields, e.g. Mauli Mauli.

- One Name (First Name only)
Clients with only a first name should have the first name entered in both the first name and last name fields, e.g. Huhulo Huhulo.

So in either case, we are just repeating the name in both first and last name.

Attendees

Michael Savage
Sheridan Cook
Igor Sirkovich
Anne Belford
Harsh Sharma
Karl Stroetmann
Kenneth Sinn
Kristina Garrels
Randy Nonay
Rita Pyle
Shamil Nizamov
Thomas Zhou

• Sheridan continued to lead the group through the Due Diligence Review, comparing the CA Baseline Profiles to the DHIR iGuide profiles
• For DHIR iGuide, assume all elements shown in their display of FHIR elements are Must Support (i.e. they don’t identify the elements that are not modified from the Base R4 definition)

• ImmunizationRecommendation

o Issue identified: .recommendation is defined in DHIR iGuide as 0..* ; doesn’t seem to be possible as it is defined in 1..* in base R4 ; IR folks to investigate

• .vaccineCode
o Some discussion to be had on Baseline side; looking to implement slicing approach to match what is defined in DHIR iGuide (i.e. slice for generic name, slice for trade name)

• Patient (Submission)

• .identifier
o For JHN, some on the call would have expected to see a pan-Canadian code set / URI registry
o Would need a list of jurisdictions as a code set
o Question: should we be enforcing more in the CA Baseline for the JHN slice?
o For the “all slices” part of identifier, recommend to relax the .type from MS + 1..1

• .name
o Question: what to do when a person has just one name?
o i.e. do we use .given or .family
o for now will look at adding to usage notes, unless there is widespread common practice as to how to handle this situation

• .telecom
o Shared Health spec also supports an extension defined as “is confidential” (yes/no)

• General note reminder to selves that we should provide a general email for consumers of the CA Baseline iGuide to use to submit questions, comments on the profiles