This portal provides an open platform for user feedback and product change requests. Anyone can add an idea and remain as a Guest, but please consider signing up so that others can see who has created the ideas!
Note: this is a public facing web portal, any text here can be viewed by anyone over the internet, so please consider carefully the content you wish to share and please do not post anything of a sensitive nature.
Our virtual ward pathways require a discharge summary to be sent to the GP at the end of the 'stay'. As it's not possible for the remote monitoring provider (Spirit Health currently) to send structured information to S1 we were wondering whether a document could be created from existing Interweave information resources and sent (via MESH?) to a S1 unit. This could then be appended to documentation created within S1 to send on to the GP.
Note: we are working on the data provision elements with Spirit separately (they'll be onboarded as a new data provider).
Not an ideal solution obviously but the lack of inbound FHIR interfaces in S1 prevents us from doing anything better I think.
Hi Toby,
Have had a chat with Sophie and Ian about this one following your presentation at the previous TDA meeting.
There may be central funding to complete this work as part of the proposed NRL project (connecting instances of our hub to the NRL to give and get data). I will mark this as a future consideration while we await a decision on funding from the centre.
Morning @Guest
Just checking if there's any update on this one?
Thanks for your time today, Toby.
As I mentioned on the call, the idea has been marked as 'Awaiting Feedback'. When you've done some digging, let us know and we can arrange a session to run through your findings.
This is also a feature Notts would be interested in … we have a number of processes/use cases where it we’d like to inform GPs of an event / activity that has happened, in any of those cases the GP would not naturally access the patient’s record and launch the portal. The ability to send a document to the GP (possibly based on a subscription to an event on the exchange) would overcome this challenge