Re: SMART on FHIR integration

Could you explain what you mean by context please? On Tue, Apr 24, 2018 at 1:23 AM, wrote: > > The real value of SMART (whether its "on FHIR" or not) is that it sets a > mechanism for EMRs to pass context to external apps. This means apps are > re-usable across different back ends. > > > Note t

Re: SMART on FHIR integration

Broadly, the context is the current patient being looked at in the EMR, or other platform being used to launch the SMART App. This allows the app to request authorisation for data specific to the 'current patient' and then launch directly into the task. Michael Sent from my iPhone On 24 Apr 2

Re: SMART on FHIR integration

Thanks, would you say then, this definition of context sounds similar to the electronic health record concept openEHR is built on? As in, providing a core EHR concept exposed by APIs? If you have an application without thi

Re: SMART on FHIR integration

Maybe it is interesting to facilitate a SMART API for OpenEhr (now there is an API-definition effort in process for OpenEhr)? Or is that to market specific and is it something more suitable for vendors or other third parties to develop? That reminds me of an other discussion which runs for year

Re: SMART on FHIR integration

He is talking about user context, known as CCOW in HL7, which is to do with solving the problem of ensuring a user with possibly multiple patients open in applications doesn't mix them up. Especially important if the application is meant to stay open while focussing on different patients (i.e.

Re: SMART on FHIR integration

sorry for the sloppy text, a bit in a hurry ;-) On 24-04-18 10:34, Bert Verhees wrote: Maybe it is interesting to facilitate a SMART API for OpenEhr (now there is an API-definition effort in process for OpenEhr)? Or is that to market specific and is it something more suitable for vendors or oth

Re: SMART on FHIR integration

Thanks Tom, Based on your description, this sounds like something that is completely an app level concern for an openEHR based application. I mean, all operations on clinical data need an EHR context, the APIs don't let data written to the wrong EHR unless well, you provide the wrong EHR identifie

Re: SMART on FHIR integration

It just occurred to me that I unintentionally made a suggestion for implementing this at the app level using openEHR: match the actor to an ehr within an "app defined context", wrap current APIs with overloaded versions that require an app defined context and call the standard apis if the context i