eReferral Spec Development work stream

A reminder about today's biweekly meeting at 11:00 regarding the development of an eReferral FHIR specification. This one will just be 30 min.

zoom.us/j/265383594
teleconference #: 1 877 369 0926
Meeting ID: 265 383 594

Chair: Tim Berezny
Co-Chair: Caryn Harris
Contact : Tim Berezny

Agenda: We will be going over some of the documentation underway.

Biweekly Workstream Teleconference - September 19, 2017 Meeting Notes

ATTENDEES:
1. Yaron Derman - eHealth Ontario
2. Tim Berezny – CareDove
3. Caryn Harris – Orion Health
4. Aidan Lee - OntarioMD
5. John Wills - eHealth Centre of Excellence
6. Ted Jin - eHealth Ontario
7. Jeff Kavanagh - CognisantMD
8. Smita Kachroo - eHealth Ontario
9. Jake Redekop - Interior Health Authority

DISCUSSION
• Tim reviewed Lloyd's presentation to the workstream last meeting
o discussed whether the eReferral paradigm we will be following is 'pure REST, document or messaging
o Jeff raised that for a very chatty interface (tell me more about the referral, here's a link to the patient profile, here's a link to the lab data), then a different approach using binary files (e.g. images) as part of a structured messaging format creates fewer issues
o OTN eConsult takes a different approach by only providing a document reference URL where the system can then go to download the actual document
• This separation of concerns may be the right thing to do for privacy reasons as well; ONE ID can alleviate the identifying system requesting access to the referenced document
• Smita provided a walkthrough of the structuredefinition for all the FHIR resources that would be required for the full eReferral lifecycle. The specification is documented in SIMPLIFIER.net
• ACTION 9:19:1 Smita can share the profile and everyone can open it in Furore Forge
o The workstream needs to provide the 'fine-grained' constraints as to which Resource attributes should be mandatory/optional/removed
o Need to review as a group to make decisions rather than individuals making changes
o ACTION 9:19:2 Tim is writing up the messaging flows to guide which Resources should be sent at different steps
o Following step is to set up a sandbox to test out the Resources being used to ensure they meet the use cases and messaging flows that we anticipate 'in the wild'
o Smita has referenced the National Health Service (UK) eReferral spec (which is DSTU 2) so that we are not reinventing the wheel
• ACTION 9:19:3: Tim and Smita to work offline to determine how to make collaboration possible

Tim - I really like the videos. They help visualize what the eReferral workstream is building towards and how SMART on FHIR can be used. They'll be very helpful to bring folks onboard as jurisdictional eReferral integrations begin gaining traction.

A reminder about today's biweekly meeting at 11:00 regarding the development of an eReferral FHIR specification

zoom.us/j/265383594
teleconference #: 1 877 369 0926
Meeting ID: 265 383 594

Chair: Tim Berezny
Co-Chair: Caryn Harris
Contact : Tim Berezny

Agenda:
1. Overview of the videos posted
2. Lloyd McKenzie will be joining us to provide his insights on the process thus far, particularly related to the usage of the /task resource.

Hello,

I have put together some videos summarizing some of the work to date with the specifications working group, and demonstrating a working prototype of using FHIR to send eReferrals through a number of pathways. I think that this update will be of interest to members on all working groups.

The main purpose of the videos is to solicit feedback.

a. An overview of the various eReferral workflows
Diagram: www.screencast.com/t/U9bm36WwjX
Video (11min): www.screencast.com/t/8vTZX9OMU

b. A demo video of some eReferral workflows in action in a pilot environment.

Video 1 - Simple Direct eReferral (3 min): www.screencast.com/t/Hu84gqOjB
Video 2 - SMART on FHIR eReferral (6 min): www.screencast.com/t/bnB486ApQ
Video 3 - Advanced Business Logic (5 min): www.screencast.com/t/kuS3NMUy9J

Thanks Tim

-Joel