-
Notifications
You must be signed in to change notification settings - Fork 88
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
Location should not be a standard launch context parameter #131
Labels
Comments
👍 Specially, we should remove:
|
+1 Also noting: #133 address another use case that some have expressed for |
isaacvetter
added a commit
to isaacvetter/smart-on-fhir.github.io
that referenced
this issue
Jul 26, 2017
Fixes smart-on-fhir#131 Note that I removed documentation of both the launch param and the launch/location scope. The spec already enables launch scopes and corresponding launch params to be extended if required.
isaacvetter
added a commit
to tmp-smart-into-hl7/smart-on-fhir.github.io
that referenced
this issue
Jul 26, 2017
Fixes smart-on-fhir#131 Remove location from both launch scope and launch parameter. Note that spec already accounts for extending launch scopes/params if required.
This was referenced Dec 21, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Location should not be a standard launch context parameter because a clinical location in which the app is being used already exists in the Encounter resource's class and Location elements.
Additionally, very few and perhaps no production FHIR server support Location yet. I think that no one has actually implemented a launch parameter specifying to specify a FHIR Location resource (unlike Patient and Encounter).
Pull request #132
The text was updated successfully, but these errors were encountered: