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 authorisation. michael -- Dr Michael Lawley Research Group Leader, Health Informatics The Australia e-Health Research Centre http://aehrc.com/ work: +61 7 3253 3609; mob: +61 427 456 260 ________________________________ From: openEHR-technical <[email protected]> on behalf of Pablo Pazos <[email protected]> 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 specs. 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 <[email protected]<mailto:[email protected]>> 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 (http://docs.smarthealthit.org/authorization/) for single sign on? I know many customers who would like this seemless integration. _______________________________________________ openEHR-technical mailing list [email protected]<mailto:[email protected]> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -- Ing. Pablo Pazos Gutiérrez [email protected]<mailto:[email protected]> +598 99 043 145 skype: cabolabs [https://docs.google.com/uc?export=download&id=0B27lX-sxkymfdEdPLVI5UTZuZlU&revid=0B27lX-sxkymfcUwzT0N2RUs3bGU2UUovakc4VXBxWFZ6OXNnPQ] <http://cabolabs.com/> http://www.cabolabs.com<http://www.cabolabs.com/> https://cloudehrserver.com<https://cloudehrserver.com/> Subscribe to our newsletter<http://eepurl.com/b_w_tj>
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
