smart-on-fhir-tutorial | SMART on FHIR developer tutorial

by cerner JavaScript Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | smart-on-fhir-tutorial Summary

smart-on-fhir-tutorial is a JavaScript library. smart-on-fhir-tutorial has no vulnerabilities and it has low support. However smart-on-fhir-tutorial has 6 bugs. You can download it from GitHub.

SMART on FHIR developer tutorial

Support

Quality

Security

License

Reuse

Support

smart-on-fhir-tutorial has a low active ecosystem.

It has 109 star(s) with 3054 fork(s). There are 56 watchers for this library.

It had no major release in the last 6 months.

There are 4 open issues and 15 have been closed. On average issues are closed in 42 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of smart-on-fhir-tutorial is current.

Quality

smart-on-fhir-tutorial has 6 bugs (0 blocker, 0 critical, 1 major, 5 minor) and 17 code smells.

Security

smart-on-fhir-tutorial has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

smart-on-fhir-tutorial code analysis shows 0 unresolved vulnerabilities.

There are 1 security hotspots that need review.

License

smart-on-fhir-tutorial does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

smart-on-fhir-tutorial releases are not available. You will need to build from source code and install.

It has 1722 lines of code, 0 functions and 14 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed smart-on-fhir-tutorial and discovered the below as its top functions. This is intended to give you an instant insight into smart-on-fhir-tutorial implemented functionality, and help decide if they suit your requirements.

Initialize FH client .
The default ffint environment
format a value into a string
Handle the response
Search a single selector .
Animation animation class
Creates a new dom matcher .
Calculate the md5 hash .
Creates a new matcher with the given selector and context .
incoming request

Get all kandi verified functions for this library.

smart-on-fhir-tutorial Key Features

No Key Features are available at this moment for smart-on-fhir-tutorial.

smart-on-fhir-tutorial Examples and Code Snippets

No Code Snippets are available at this moment for smart-on-fhir-tutorial.

Community Discussions

Trending Discussions on smart-on-fhir-tutorial

In a SMART (FHIR) Application: Can the Application authenticate the EHR?

QUESTION

In a SMART (FHIR) Application: Can the Application authenticate the EHR?

Asked 2018-Mar-02 at 23:29

It is very clear to me how an EHR using a SMART application can authenticate that requests coming from the SMART application are legitimately coming from the authentic SMART application. However, I'm not seeing how the SMART application knows that the request coming from the EHR is a legitimate request. Is there a standard way the SMART application can authenticate that the incoming request from an EHR is actually a request from an EHR that the SMART application has registered with? In other words, is there a way that is build into the SMART specification that allows the SMART application to limit use to authenticated registered EHRs? Is there a step in the OAUTH2 protocol that ensures this?

I am looking at the SMART authorization guide here: http://docs.smarthealthit.org/authorization/

and the Cerner tutorial/demo here: http://engineering.cerner.com/smart-on-fhir-tutorial/

...

ANSWER

Answered 2018-Mar-02 at 23:29

We're talking about the "EHR Launch" flow here, where an app has been launched by an EHR. This lauch includes an iss parameter indicating the EHR that (supposedly!) initiated the launch, and an opaque launch parameter.

At this point, the app can't authenticate the request, but it can:

Check to ensure that the iss value matches the issuer for an EHR that it knows (and for which it has a client_id)
Proceed with the launch by redirecting to the EHR. If the launch works, the launch ID was valid. If, on the other hand, the EHR doesn't recognize the launch ID or hasn't associated it with the current app's client_id, then the launch fails.

This is a functional approach to validating the EHR's identity: effectively, the app uses the launch protocol to ask the EHR if this launch is valid.

(Please do raise the point on chat.fhir.org if you think this protocol leaves an important functionality or security gap!)

Source https://stackoverflow.com/questions/49057210

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install smart-on-fhir-tutorial

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: