eReferral Spec Development work stream
- Tim Berezny
- Offline
- Posts: 84
7 years 1 week ago #3214
by Tim Berezny
Replied by Tim Berezny on topic eReferral Spec Development work stream
We've made significant progress on two important pages in the eReferral iGuide. They are fairly short and relatively easy to read (for a specification). They are meant to leverage the existing FHIR documentation whenever possible and describe processes and data flow in detail. Specific profiles are to be tackled later.
Process - Choose Recipient :
simplifier.net/ui/ig/eRefferaldraftiGuide/ChooseRecipient-Direct
Process - Submit eReferral :
simplifier.net/ui/ig/eRefferaldraftiGuide/SubmiteReferral-Direct
For members of the eReferral working group, and anybody else interested, please review these pages and post any feedback into the forum (or on Asana). I would also like to gather some insights from FHIR experts in the community, or those that have deployed FHIR is other projects. There are a number of questions listed at the bottom of the page for items that still need to be addressed.
The main agenda item of Tuesday's eReferral working group meeting will be to review these two pages, solicit feedback, and try to answer some of the questions listed at the bottom of the page.
Process - Choose Recipient :
simplifier.net/ui/ig/eRefferaldraftiGuide/ChooseRecipient-Direct
Process - Submit eReferral :
simplifier.net/ui/ig/eRefferaldraftiGuide/SubmiteReferral-Direct
For members of the eReferral working group, and anybody else interested, please review these pages and post any feedback into the forum (or on Asana). I would also like to gather some insights from FHIR experts in the community, or those that have deployed FHIR is other projects. There are a number of questions listed at the bottom of the page for items that still need to be addressed.
The main agenda item of Tuesday's eReferral working group meeting will be to review these two pages, solicit feedback, and try to answer some of the questions listed at the bottom of the page.
Please Log in or Create an account to join the conversation.
- Tim Berezny
- Offline
- Posts: 84
7 years 3 weeks ago #3158
by Tim Berezny
Replied by Tim Berezny on topic eReferral Spec Development work stream
This is where the eReferral spec is currently being drafted:
simplifier.net/ui/ig/eRefferaldraftiGuide/Overview2
simplifier.net/ui/ig/eRefferaldraftiGuide/Overview2
Please Log in or Create an account to join the conversation.
- Tim Berezny
- Offline
- Posts: 84
7 years 3 weeks ago #3157
by Tim Berezny
Replied by Tim Berezny on topic 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.
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.
Please Log in or Create an account to join the conversation.
- Yaron Derman
- Offline
- Posts: 41
7 years 1 month ago #3083
by Yaron Derman
Replied by Yaron Derman on topic eReferral Spec Development work stream
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
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
Please Log in or Create an account to join the conversation.
- Yaron Derman
- Offline
- Posts: 41
7 years 2 months ago #3021
by Yaron Derman
Replied by Yaron Derman on topic eReferral Spec Development work stream
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.
Please Log in or Create an account to join the conversation.
- Tim Berezny
- Offline
- Posts: 84
7 years 2 months ago #3006
by Tim Berezny
Replied by Tim Berezny on topic eReferral Spec Development work stream
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.
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.
Please Log in or Create an account to join the conversation.