Upcoming FHIR Community Call - June 28, 12-1 EST

June 28 FHIR community call

Open Action Items Summary
May 24:2: Yaron to see if there is anyone at OTN who wants to share what they are doing with SMART on FHIR.
June 28:1 - Gavin to ask Infoway if we can gain some of the Partnership agenda time to showcase the progress we are making AND an Infocentral newsletter item
June 28:2 - Yaron to update the landing page content with a summary of the progress over tha past 6 months
June 28:3 - Igor to post on FHIR chat about this community to make new people
June 28:4 - Yaron to coordinate with Vaughan to get up to speed with the various workstreams

June 28, 2017 Attendees:
Shamil Nizamov (BC Health)
Alex Goel, (Cancer Care Ontario)
Igor Sirkovich (Ontario Ministry of Health and Long Term Care)
Federick Laroche (Gevity)
Kris Lewis (Sierra Systems)
Randy Noray (Alberta Health)
Kemp Watson (Objective Pathology Services)
David Kwan (Cancer Care Ontario)
Gavin Tong (Gevity)
Yaron Derman (eHealth Ontario)
Smita Kachroo (eHealth Ontario
Alan Leung (Sierra Systems)
Vaughan van der Merwe (Strata Health)


1. Agenda review and past action items

May 24:1: Gavin to update event instance on Infocentral with correct URL and Dial-In # COMPLETED
May 24:2: Yaron to see if there is anyone at OTN who wants to share what they are doing with SMART on FHIR. IN PROGRESS – Yaron to follow up
May 24:3: Attila to post his notes on the HL7 WGM including the link to the HL7 WIKI on Registries. COMPLETED
May 24:4: Gavin to follow up with Rod and Susan to see if they know people who want to join the eReferral workstream. COMPLETED – Caryn Harris (Orion Health) is now the co-chair

2. Midpoint check-in
• Gavin provided a summary of the past 6 months of this community
• Tooling workstream has made some progress in its objectives
• Solution Architecture workstream has enabled discussion on some core FHIR topics and a central point / registry for URIs
• Registries workstream has had some good discussions with the draft FHIR specs from Ontario as a basis.
• eReferral - gaining a picture of the actors and APIs that will need to be in place to enable broader interoperability between POS systems and various platforms to enable broad sharing of eReferrals
• How are we sharing this info more broadly? Gavin suggested that we consider using the upcoming Partnership as a forum to share.
• ACTION: June 28:1 - Gavin to ask Infoway if we can gain some of the Partnership agenda time to showcase the progress we are making AND an Infocentral newsletter item
• ACTION: June 28:2 - Yaron to update the landing page content with a summary of the progress over tha past 6 months
• ACTION: June 28:3 - Igor to post on FHIR chat about this community to make new people
• Workstream structure works because allows participants to devote their time to the topics of most relevance/interest to them
• Kemp is interested in participating in FHIR for pathology - Curious about translating DICOM into FHIR
• ACTION: June 28:4 - Yaron to coordinate with Vaughan to get up to speed with the various workstreams

3. Work stream updates
a. Registries (Kris Lewis)
• Focus on the use cases for FHIR interfaces for a provider registry
• Will move to use cases for client registry and then location registry
• Pace is related to availability of participants' time
b. Tooling (Frederick Laroche)
• Covering the end-to-end needs for tools (tools for modeling, publishing, conformance, application integration that relate to the various versions of FHIR) and potentially develop tools where are gaps
• Would be ideal to have a pan-Canadian registry to browse what Canadian profiles have already been created to encourage adoption over development
o 16 business requirements for this registry already documented on Infoscribe space with feedback from workstream members
o Considering a license of Furore SIMPLIFIER product (with a distributed platform)
c. Biz case (Yaron Derman)
• Provided an overview of the sections in the Business Case, which is available here: infoscribe.infoway-inforoute.ca/display/FHIR/FHIR+-+Business+Case
• It provides more advanced details than many of the whitepapers available on FHIR
• This workstream will be merging into the tooling workstream
d. Solution Architecture (Igor Sirkovich)
• Discussions around necessary practices for URI construction to ensure consistency and uniqueness, while avoiding duplication
• Mapping of OIDS to URIs
• Working on jurisdictional health card identifiers
• This is providing emerging patterns that are necessary across most projects and jurisdictions
e. eReferral (Yaron Derman)
• Have a better picture on the actors and APIs that will be needed across the eReferral end-to-end process
• eHealth Ontario will be working on enabling a 'service directory' actor to help route eReferral requestor actors (either POS system or eReferral platforms) to Referral Recipient actors where the endpoint is unknown (e.g. the Referral Requestor wants to discover and send a referral to a Service Provider who is using a different eReferral platform)

4. Next steps
• Next call on July 26, 2017
• Video conference URL: zoom.us/j/563726340
• Teleconference #: 1 877 369 0926 (US Toll Free)
• Meeting ID: 563 726 340

Hi,

Looking forward to speaking with people at noon. As a reminder, the meeting info is below and can be found on the event page here:
infocentral.infoway-inforoute.ca/en/news-events/event-calendar/month.calendar/2017/06/28/-

Monthly FHIR Community Call - Agendas TBD
Join from PC, Mac, Linux, iOS or Android :https://zoom.us/j/563726340
Teleconference #: 1 877 369 0926 Meeting ID: 563 726 340
Location : Zoom Meeting
Contact : This email address is being protected from spambots. You need JavaScript enabled to view it.

Hi,

The next FHIR Community Call is on June 28. Draft agenda is below.

1. Agenda review and past action items (10 mins)
2. Mid point check-in. (15 mins) – purpose is to reflect on accomplishments date, see if we need to make any changes to the overall structure and format of progressing work plans, etc.
3. Work stream updates (30 mins)
a. Registries
b. Tooling
c. Biz case
d. Solution Architecture
e. eReferral
4. Next steps (5 mins)

Looking forward to catching up with everyone.

Thanks,

Gavin