Skip to content

Issues: smart-on-fhir/smart-on-fhir.github.io

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.

Sign up for GitHub

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

23 Open 56 Closed
23 Open 56 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Sources for fhir-client.js on "Tutorial - Building a JavaScript App" are broken
#175 opened Oct 14, 2019 by ghost
4
The Sandbox page states "The open source code to do this will be released soon."
#173 opened May 30, 2019 by medinuity
https://docs.smarthealthit.org broken
#172 opened Apr 24, 2019 by johnstairs
FHIR genomic sample data download not working
#170 opened Jan 17, 2019 by vpl-profess
2
possible typo in conformance guidance descriptions for context-ehr-* capabilities
#164 opened Mar 17, 2018 by lcmaas
Granted scope = none
#163 opened Mar 17, 2018 by lcmaas
decision to deny is not typically communicated by returning an authorization code
#162 opened Mar 17, 2018 by lcmaas
clarification of requirement to validate state
#161 opened Mar 17, 2018 by lcmaas
Link to dynamic client registration documentation points to draft rather than final RFC
#160 opened Mar 17, 2018 by lcmaas
cannot get authorization code after launch
#158 opened Feb 13, 2018 by yanandyan
Consider STU3 for http://docs.smarthealthit.org/tutorials/server-quick-start/
#157 opened Jan 12, 2018 by col-panic
1
Minor typo: phyical instead of physical
#151 opened Sep 5, 2017 by daliboz
Suggested wording changes for *Support for “public” and “confidential” apps* Section
#149 opened Sep 5, 2017 by Healthedata1
SMART server can return Person resource to identify user if Patient or Practitioner or RelatedPerson doesn't work
#148 opened Sep 5, 2017 by isaacvetter
7
Include a discovery parameter for optional OAuth 2.0 Token Introspection
#147 opened Sep 5, 2017 by jmandel
Clarify language about when client-side apps might be able to keep a secret
#146 opened Sep 5, 2017 by jmandel
Use 'fhirUser' scope/claim instead of 'profile' scope/claim for OIDC into-hl7
#141 opened Jul 14, 2017 by kpshek
8
Document /metadata differences between DSTU2 (and earlier) and STU3+ into-hl7
#139 opened May 31, 2017 by kpshek
2
"resource" launch context parameter into-hl7
#138 opened May 12, 2017 by gotdan
6
Define a mechanism to declare support for specific capabilities into-hl7
#136 opened Apr 10, 2017 by jmandel
11
Spec should clarify that id_token is required, userinfo endpoint is optional for AS OIDC support. into-hl7
#135 opened Mar 24, 2017 by isaacvetter
20
SMART style properties are not widely implemented into-hl7
#134 opened Mar 22, 2017 by isaacvetter
5
Location should not be a standard launch context parameter into-hl7
#131 opened Mar 22, 2017 by isaacvetter
2
ProTip! Mix and match filters to narrow down what you’re looking for.