Re: SMART on FHIR integration

[Michael.Lawley]

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  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 
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 
> 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
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org



--
Ing. Pablo Pazos Gutiérrez
pablo.pa...@cabolabs.com
+598 99 043 145
skype: cabolabs

[https://docs.google.com/uc?export=download=0B27lX-sxkymfdEdPLVI5UTZuZlU=0B27lX-sxkymfcUwzT0N2RUs3bGU2UUovakc4VXBxWFZ6OXNnPQ]
 
http://www.cabolabs.com
https://cloudehrserver.com
Subscribe to our newsletter

___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: SMART on FHIR integration

[Pablo Pazos]

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  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
> openEHR-technical@lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-
> technical_lists.openehr.org
>



-- 
Ing. Pablo Pazos Gutiérrez
pablo.pa...@cabolabs.com
+598 99 043 145
skype: cabolabs

http://www.cabolabs.com
https://cloudehrserver.com
Subscribe to our newsletter 
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

SMART on FHIR integration

[Brian Nantz]

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
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: SEC meeting 18-20 April; community issues solicited

[Thomas Beale]

Generally speaking, you can look at the 'Releases' page of any Jira 
project (remember: there is one Jira project for each 'component', i.e. 
RM, AM, SM, PROC, CNF, ...) and you will see the dates attached to each 
release. For RM, it is this view in Jira 
. 
We'll release earlier if we get the work done earlier.


Note that as items get completed within a release, the solution is 
already a commitment, so if your need is to know 'how will openEHR solve 
this problem', then you can often know the answer some time before the 
release is actually made - just look at the progress picture for that 
release. E.g. Release 1.0.4 is pretty far along 
.


- thomas


On 23/04/2018 12:00, Bert Verhees wrote:

On 23-04-18 11:06, Thomas Beale wrote:
The next RM and BASE releases are nearly finalised, and we expect to 
issue RM Release 1.0.4 within a few weeks.


Hi Thomas,

Is there some thing to say when the RM Release 1.1.0 approximately 
will be expected?


Thanks for an indication

Bert 


___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: SEC meeting 18-20 April; community issues solicited

[Thomas Beale]

We had a very useful SEC meeting in Ljubljana last week. For those 
interested in the outcomes, see the meeting wiki page 
 
and sub-pages, which contain extensive notes. Feel free to add comments 
to any of these pages.


The next RM and BASE releases are nearly finalised, and we expect to 
issue RM Release 1.0.4 within a few weeks. You will also see a lot of 
changed statuses on Problem Reports and RM Change Requests.


- thomas beale


On 10/04/2018 11:01, Thomas Beale wrote:


We have a Specifications Editorial Committee 
 
meeting in Ljubljana 18-20 April, during which we will be processing 
as many of the outstanding Problem Reports (PRs) 
 
as possible.


The agenda is posted on the meeting page 
.


If members of the community have other issues not covered by raised 
PRs, e.g. future directions questions, that they would like to be 
discussed, they may add to the agenda page under the 'Community 
Issues' heading.





--
Thomas Beale
Principal, Ars Semantica 
Consultant, ABD Team, Intermountain Healthcare 

Management Board, Specifications Program Lead, openEHR Foundation 

Chartered IT Professional Fellow, BCS, British Computer Society 

Health IT blog  | Culture blog 

___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org