Canadian FHIR Baseline Profiles - Due Diligence Review - IPS – July 16th, 2-3pm EST

Observation (Lab Results)
• DataAbsentReason
o Group has decided to leave discrepancy as-is and flag it as such, will move on

DiagnosticReport
• .category
o CA Baseline maintains a mandatory slice called Category:LabResult (1..1), not supported by IPS
o To review and decide the purpose of having this mandatory slice (URI is fixed to a particular code set)

• .code
o CA Baseline supports a Code:LabResult slice which fixes the system and code values to LOINC value set and LOINC code
o Question of the purpose of this slice; implementers could just use the default slice

• .subject
o In CA baseline the reference points to patient, device, location; in IPS it just points to patient and group
o Group feels that the IPS approach makes more sense
o Question: should we include the Group profile in the CA Baseline approach, so that it can be pointed to?

• .encounter
o Flagged as MS in the CAB but not in IPS
o Feeling is that there are some use cases where it definitely should be MS, but others where it wouldn’t make sense
o No strong feelings for or against relaxing, leaving it for now

• .performer and .resultsInterpreter
o CAB has constrained out the reference to CareTeam, IPS has left it in
o No strong feelings

• .specimen
o CAB flagged as MS, IPS does not
o Question from the group on why this is MS? Not all use cases would involve diagnostic report which involves a specimen

• For next time: Continue looking at these flagged discrepancies for DiagnosticReport

Hi all!

For this Friday's Due Diligence Review Session, we'll be continuing with the following iGuide, Profile, and Element (where we left off back in mid-June):

Intl Patient Summary > Observation (Lab Results) > dataAbsentReason

> MS flag in CA Baseline and US Core, but not flagged in IPS as MS
> May be an aspect of the specific scope of IPS not expecting not resulted observations be packaged up into a document as part of the workflow
> Need to determine if given that scenario will exist in Canadian implementations- if dataAbsentReason should be relaxed for the profile to accommodate it

Once we have worked through this item, we will then proceed to a comparison of the DiagnosticReport Profiles, between the CA Baseline and IPS iGuides.

Thank you!