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.

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.

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

Could you explain what you mean by context please?

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 this concept or based on an organic implementation of this concept, then SMART …

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 years. …

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. not c…

sorry for the sloppy text, a bit in a hurry :wink:

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 identifier…

SMART on FHIR integration

Technical (archive)

michael.lawley 24 April 2018 07:48 5

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

Topic		Replies	Views
Help in drafting specification for building and distributing "Apps" on top of openEHR and FHIR Implementation application	11	1358	1 July 2023
SMART on openEHR ITS rest-apis , rest , smart	4	811	20 August 2024
Security, privacy and patient identity openEHR & standards	10	1875	15 March 2023
API's Implementers (archive)	22	3	17 July 2018
access control for openEHR 'resources' Implementation	27	743	5 November 2024
OpenEHR and SMART apps on FHIR Apps	1	1254	5 October 2020
need to do something to understand and then hopefuly get involved in the open EHR community Clinical (archive)	3	2	14 February 2003
SMART platform and RDF Technical (archive)	9	10	5 July 2012
Authorisation Technical (archive)	7	0	4 May 2006
Is openEHR vs FHIR a modern version of HL7x vs 13606? HL7 FHIR	5	3106	9 November 2020

SMART on FHIR integration

Related topics