Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"resource" launch context parameter #138

Open
gotdan opened this issue May 12, 2017 · 6 comments
Open

"resource" launch context parameter #138

gotdan opened this issue May 12, 2017 · 6 comments
Labels

Comments

@gotdan
Copy link
Contributor

gotdan commented May 12, 2017

Do any EHRs support the "resource" launch context parameter? If not, do we want to keep it as part of the spec? If we do keep it, I think we should probably add it to the capabilities extensions in #136...

@kpshek
Copy link
Contributor

kpshek commented May 13, 2017

Cerner's implementation doesn't support the resource launch context parameter.

cc @isaacvetter, @bdoolittle, @SiddShah

@isaacvetter
Copy link
Member

Hey @gotdan,

Same with my EHR. I see the problem with the resource launch context parameter is that it's not specific enough.

I'd recommend removing it as well.

Isaac

@jmandel
Copy link
Member

jmandel commented Jul 27, 2017

As we finalize the ballot package, I'm going to add resource to https://github.com/smart-on-fhir/smart-on-fhir.github.io/blob/into-hl7/conformance/index.md for consistency. But then: I'll recommend during ballot reconciliation that we can plan to drop resource from both places.

@jmandel
Copy link
Member

jmandel commented Sep 9, 2017

@grahamegrieve can you comment on this? I think yours is the only implementation I've heard about that may be using this scope.

@grahamegrieve
Copy link
Contributor

well, i won't be - as the use of smart on fhir extends outside the pure EHR plug-in context, a whole lot of people are going to need new contexts beyond the ones the smart app launch currently defines

@jmandel
Copy link
Member

jmandel commented Sep 9, 2017

OK -- so on that view, we can remove this specific scope from the spec and leave room for ad-hoc new scopes as needed or particular use cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants