- Verifiable Clinical Information·Last edited by Josh Mandel on Aug 13, 2020Linked with GitHubContributed by
There is no commentSelect some text and then click Comment, or simply add a comment to this page from below to start a discussion.Modeling W3C Verifiable Credentials in FHIR
Migrated to http://docs.smarthealthit.org/health-cards/
Read more
SMART Health Links: Technical Protocol
Content migrated to: Website: https://docs.smarthealthit.org/smart-health-links GitHub Repo: https://github.com/smart-on-fhir/smart-health-links
Aug 30, 2022SMART Health Links
Content migrated to: Website: https://docs.smarthealthit.org/smart-health-links GitHub Repo: https://github.com/smart-on-fhir/smart-health-links
Aug 30, 2022SHCLinks: GNAP Sketch
Background and Design goals See https://hackmd.io/kvyVFD5cQK2Bg1_vnXSh_Q See https://datatracker.ietf.org/doc/draft-ietf-gnap-core-protocol/ protocol for reference Design Sketch #3: GNAP Method GNAP Method: Software components Resource Server. Hosts static files (which can be updated over time). These files are (may be?) encrypted so the resource server can't read them. Authorization Server. Manages access control for files in the Resource Server. The Authorization Server is also blind to the contents of encrypted static files.
May 31, 2022SMART Health Links: Historical Design
Older design sketches below... See historical archive. Protocol Ideas OAuth Method. Using extension on OAuth 2.0, where client registrations can be tied to a specific data access policyy Pros: Leverages existing healthcar domain expertise with OAuth 2.0 (SMART on FHIR) Cons: Requires new extension parameters, requires a flavor of dynamic registration
Apr 28, 2022
HackMD