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.


Sent from my iPhone

On 24 Apr 2018, at 5:23 pm, Seref Arikan 

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 that this is not really about authentication (SSO) but rather it is about 


Dr Michael Lawley
Research Group Leader, Health Informatics
The Australia e-Health Research Centre
work: +61 7 3253 3609; mob: +61 427 456 260
From: openEHR-technical 
 on behalf of Pablo Pazos 
Sent: Tuesday, 24 April 2018 9:29 AM
To: For openEHR technical discussions
Subject: Re: SMART on FHIR integration

SSO is a front end feature, that is not on the current scope of the openEHR 

I think any openEHR implementer can do SSO at the front-end app level to access 
SMART apps.

On Mon, Apr 23, 2018 at 6:14 PM, Brian Nantz 
<<>> wrote:
I see you have had discussions on FHIR and SMART on FHIR.  Is it on the roadmap 
for openEHR to support SMART on FHIR launch sequence 
( for single sign on?  I know many 
customers who would like this seemless integration.

openEHR-technical mailing list<>

Ing. Pablo Pazos GutiƩrrez<>
+598 99 043 145
skype: cabolabs
Subscribe to our newsletter<>

openEHR-technical mailing list<>

openEHR-technical mailing list<>
openEHR-technical mailing list

Reply via email to