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.
In LLR we're working with Spirit Health to deliver virtual ward pathways. Part of this includes an interoperability obligation from them to provide information collected from patients as part of their remote treatment.
We're undertaking accompanying discovery work to ascertain specific use cases but we would like to being discussions on the technical feasibility of connecting their platform to Interweave as a (complex?) data provider. They have the ability to generate FHIR resources from the information they hold and this will most likely be encounters/questionnaires and observations.
thanks Toby, as you say, let's understand the role of the ShCR here first, then we can consider how to satisfy the use cases and look at the data that would come from Spirit
Thanks Ian. Yes, I think a discussion is needed. The thought that it might be a 'complex' provider was because it may provide information associated with multiple organisations (much like the Equipment info), but I'm open to suggestions and always keen to ensure we don't have to re-work things.
Good point about the observations and this was discussed during some of our initial discovery calls with Virtual Ward clinicians (i.e. recognising that everyone won't be interested in the level of detail that the managing clinician is). I was kind of thinking it might be a bespoke panel actually, but would be good to validate the UX requirements from different consumer roles/settings.
Hi Toby, I think we should consider why this provider is a 'complex' provider, and see if there's anything we can do to enhance Connect to cope. Ideally all providers will connect using the FHIR appliance and remove the need for bespoke work. I think a conversation with Tim and Steve Marsden might be useful to see if/how we can develop Connect further and save extra work in future situations?
Separately, we also need to consider the provision of Observations, if these are remote observations from patient devices then you might imagine how the Obs panel quickly becomes swamped with data or perhaps limited value to some/most users?
Not making a judgement here, just an observation... excuse the pun ;-)