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

Initializing Best Practices #64

Open
wants to merge 2 commits into
base: argonaut-dev
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions authorization/best-practices/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,12 +6,14 @@ title: "SMART on FHIR Authorization: Best Practices"
# Best Practices in Authorization for SMART on FHIR EHRs

This page is designed to catalog best practices in developing secure SMART on
FHIR EHR implementations. As such, these considerations don't directly affect
interoperability; rather, they describe pracical implications of security
decisions. This page is a work in progress; we ancicipate describing details
such as the entropy required in genearting access tokens.
FHIR EHR implementations. As such, these considerations may not directly affect
interoperability, but are likely to affect the level of assurance the server
is able to provide. These Best Practices are not intended to dictate
institutional policy, but to offer pracical solutions for making security
decisions to enforce policy. This page is a work in progress.

## Please contribute suggestions!

Please use the link at the top of this page to suggest additions to our best
practices list.