eReferral Spec Development work stream

Notes for WG Meeting 2020-12-08
====================

Next Meeting Jan 5th 2021

The main topic of the meeting was a revised design of eReferral event codes.

We evaluated the BSeR state flow diagram found here (and its associated table): hl7.org/fhir/us/bser/2019May/BSeRMessagingWorkflow.html

Also, there is a previously worked on document for revising event codes that can be found here:
docs.google.com/document/d/16a41JBVSC9DAqjhE657QvQl1kfEpXOnf7L1hQoAkYHI/edit?usp=sharing

OBSERVATIONS:
- Do we need rows 15 and 17 for fail, or should it be possible to “fail” from anywhere? Semantically what do we mean by fail - clinical vs process vs technical failure? This language needs to be made clear
- Be more rigid on “Terminal” states
- Generally we should follow the Task states, but create some standard businessStatus states

PROCESSES TO TEST AGAINST
- Splitting of a referral (at a central intake) - Need a way to “notify” the requester that there is a new sericeRequest created based on their previous referral
- Request for information: In this diagram, needs to go via “Rejected”, but this isn’t truly a rejected state, which should be considered “terminal”. - Consider adding an RFI or “revise” state… or business statuses to “Rejected” where it does not act as a terminal state, which it is waiting to be accepted or rejected.

QUESTIONS:
- What is the purpose of “Modified (Ask the author)
docs.google.com/document/d/16a41JBVSC9DAqjhE657QvQl1kfEpXOnf7L1hQoAkYHI/edit?usp=sharing

Note: The eReferral WG meetings have moved from biweekly to monthly, with the next meeting in December.

You can see the updated schedule here:
infocentral.infoway-inforoute.ca/en/monthly-calendar/month.calendar/2020/11/24/1268

-Tim Berezny, CTO Caredove | Cette adresse courriel est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser.

Thanks Ted, Radhika!

Notes from WG Meeting 2020-11-10

ATTENDEES
Tim Berezny (CareDove),
Radhika Verma (Ontario Health),
Geoff Ramsay (Think Research)

AGENDA
Proposal to move to monthly meetings
Discuss previous thinking on Task Statuses

DISCUSSION NOTES
New admin processes and needs
Move to Monthly meetings (no active development on standard right now)


Review of previous thinking on expanded Task statuses
Proposed Thinking:
docs.google.com/document/d/16a41JBVSC9DAqjhE657QvQl1kfEpXOnf7L1hQoAkYHI/edit

Review US eReferral work:
hl7.org/fhir/us/bser/WorkflowManagementResources.html

Conceptually:

• ServiceRequest -> Request to transfer care
• Requested, Acked, Cancelled, Complete...
• Task -> Tracks the workflow of processing a referral
• All other steps during processing
• Event-Code -> Instruction for the receiving system to process a specific action

...Follow up with WG to schedule an event code conversation

Discussion - Viewlets

• Review of Viewlets iGuide opens next week.
• Radhika authored the Simplifier
• Allows for 2-way context sharing between apps
• Potentially an interesting investigation as an alternative to the current SoFish approach used in eReferrals

NEXT MONTH’S AGENDA ITEMS
Event Code discussion

I would like to participate!
Thank you!

Please count me in. Thanks.

Hi Folks!

In Tuesday's Working Group meeting we discussed message header event-codes used to identify the intent of an eReferral bundle. The (limited) attending group recognised that this is an area that's still quite ambiguously defined, and that could use some focus and further refinement.

The attending group proposed an out-of-band discussion for interested parties.
If you're reading this, and would like to participate, please respond, or message/email me or Tim directly!

Proposed agenda of that (ideally 2 hour) side-chat:

• Review existing event codes and intended use.
• Review proposed event codes representing sub-events and new events
• Plan for formalization and presentation to the Working Group for feedback