Canadian FHIR Baseline Profiles - Governance Stream Meeting - January 10th, 2-3pm EST

Attendees

• Igor Sirkovich
• Sheridan Cook
• Maria Hu
• Alex Goel
• Derek Ritz
• Scott Prior
• Shamil Nizamov
• Smita Kachroo
• Abdullah Khan
• Shamhad Abdi
• Michael Savage

Discussion

• Discussion on definition & usage of Must Support flag for Canadian core profiles
• Existing rule is that any profile derived from the Canadian Core profiles must inherit the Must Support flags as designated
• Strong definition candidate as proposed on FHIR Chat: Must Support = must be capable of incorporating, capturing, and storing the flagged element
• “if you get it, store it. If you have it, send it”
• For next meeting, will have a table of definitions that will help separate the different concepts and clarify each one; can be used to re-organize the content for Must Support for the Canadian Core Profiles

Hi all,

For this Friday's Solution Architecture / Canadian Core Governance Call, the draft agenda is as follows:

1. Discussion of the Canadian Core definition of 'must support'
2. Discussion of the Canadian Core usage of 'data absent reason' elements/functions
3. Updates on shorter duration of bi-weekly Profile Updates & Governance calls

Thank you!

-Mike