Canadian FHIR Baseline Profiles - Governance Stream Meeting - July 5th, 2-3pm EST

Also on the call:
- Francis Lau
- Joel Francis
- Craig Anderson
- Radhika Verma
- Sisira De Silva

There was concern raised about overall workload to review the significant number of resources/profiles, particularly as a volunteer activity.

Suggestion that there may be need for two maturity models, one pre-implementation (e.g. the current draft review process) and one post-implementation (e.g. after the current draft review process).

Reason for Change and Deviation from US-Core needs to be clearly documented.

GitHub tagging is being explored to allow for better filtering/searching in the GitHub Issues repository.

Recognition that this will be a multi-phase process, and this first pass of content review will be followed by a larger review by vendors, community at large beyond the implementers (editor's note: is this where clinical feedback would also happen? suggest clinical feedback should be captured earlier than later).

Attendees

• Michael Savage
• Andrea MacLean
• Finnie Flores
• Ben Macerola
• Alan L
• Harsh Sharma
• Igor Sirkovich
• Sheridan Cook
• John Wills
• Ken Sinn
• Laura
• Randy Nonay
• Smita Kachroo
• Fariba Behzadi

Key Links:

• Simplifier.net: simplifier.net/canadianfhirbaselineprofilesca-core
• GitHub: github.com/scratch-fhir-profiles/CA-Core
• IG Publisher: build.fhir.org/ig/scratch-fhir-profiles/CA-Core/
• Profile Review Template: infocentral.infoway-inforoute.ca/en/collaboration/wg/fhir-implementations (Go to Documents, and download Canadian Core Profile - Template for Review / Proposed Changes)
• Project Plan Deck: docs.google.com/presentation/d/1w98EOZh1ZDfyJfF6V6Jav7xyIXQ25NgyJQNZjTGTsuQ/edit?usp=sharing

Meeting Purpose

• Mike did a walk through of the profile review process, and sequence of deadlines for review and discussion
• Posed questions to the group on what to do with profiles which have received no reviews by their deadlines, and how to make decisions when there is not consensus on a proposed change, i.e. how to get the community to vote on issues

Discussion

• Summer months not ideal for reviews; may not get everyone’s reviews in during the summer
• Would be good to include the name of the submitter in the GitHub issues; allows us to follow-up with the submitter if there is anything unclear about the issue
• From past experience: decision making for the proposed changes would be made by declaring them as agenda items for a profiling call (allows people to ensure they are free), and callers either vote for / against / abstain for the proposed change
• For any votes there needs to be enough people voting, and shouldn’t be primarily from the same company
• ACTION ITEM: Draft a Terms of Reference with these particulars included
• ToR should also deal with ‘what does it mean to have participated on a call where a proposed change was discussed and approved / declined?’
• Should add a ‘maturity model’-styled indicator to each core profile; basically show the # of reviews that the profile has received
• Should also keep track of which jurisdictions have provided feedback
• Look at existing Terms of Reference from HL7, and can start from there and build in what is discussed
• The closer the process resembled that of HL7 Canada, Int’l, etc., this may further incentivize vendors to adopt the core profile approach

Hi all!

Just posting this as a reminder re: the agenda for this Friday's Governance meeting (see prior post in this thread). I had sent it out Friday afternoon so just want to make sure it doesn't get buried in people's inboxes.

-Mike

Hi all,

For the July 5th meeting (Governance Stream), we will be walking through the drafted Profile Review Process and Profile Review and Comment Deadlines. For those wanting to review the content in advance of the meeting, please refer to Slides 10, 11, and 12 in the Project Plan: docs.google.com/presentation/d/1w98EOZh1ZDfyJfF6V6Jav7xyIXQ25NgyJQNZjTGTsuQ/edit?usp=sharing

I realize it's late on Friday right before the long weekend, so I will post to this thread Tuesday morning as a reminder and to ensure this draft agenda is not missed.

Please keep in mind that, rather than waiting for the calls, you are always welcome and encouraged to email me at Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser. if you have any questions.

Thank you!

-Mike

The Zoom meeting details for joining the meeting can be found on the relevant calendar invite here:
infocentral.infoway-inforoute.ca/en/monthly-calendar/month.calendar/2019/07/28/1268