Stream: implementers
Topic: Question about SMART documentation
John Martin (Feb 01 2018 at 13:15):
Are these the best sources for documentation for SMART?
Technical Documentation:
http://docs.smarthealthit.org/
Tutorials:
http://docs.smarthealthit.org/tutorials/
Server Implementation:
http://docs.smarthealthit.org/tutorials/server-quick-start/
Are there others? It seems like there could be more on server implementation (and a full end-to-end example).
I'm working on a new project and would very much like to propose SMART as a solution for an interoperability piece we will need to implement. I'll need to sell this proposed solution to leadership on the project and detailed documentation will go a long way in doing this.
Thanks,
John
Josh Mandel (Feb 01 2018 at 13:47):
Of course there's the technical documentation for the protocol itself at http://docs.smarthealthit.org/authorization. Then there are the "Run Apps" menu Link's at https://smarthealthit.org. The major vendors have sites outlining their own support. That's about the size of it. #smart would be a good place to describe what additional documents you would find helpful.
John Martin (Feb 01 2018 at 14:15):
Thanks Josh! Is it correct to say SMART is primarily authentication/authorization and is not so much concerned with the content of what information is sent between the server and the client. SMART on FHIR uses SMART for authentication/authorization and FHIR for messages sent by both the client and the server. I would imagine that there are also hybrid solutions where the client sends a FHIR message and the server returns content that can be directly rendered by the client (e.g. HTML5). Is this correct?
Josh Mandel (Feb 01 2018 at 14:31):
The landing page of http://docs.smarthealthit.org probably sent it the best way I know how it :simple_smile: and in short, SMART aims to define an app framework. (We are very deeply concerned with data consistency --for which we rely on the Argonaut profiles in the US -- as well as the way in which contextual information is passed from an EHR to an app.)
John Martin (Feb 01 2018 at 15:12):
Thanks again Josh!
John Martin (Feb 03 2018 at 17:58):
It sounds like I somewhat conflated Smart with CDS Hooks. Also, it looks like neither of these are suited to our use case. We have an existing web application that is called from an EHR. The EHR currently just opens the url in a browser. We would like to integrate the existing web page directly into the application. It sounds like the easiest way to implement that would be to simply open the web app in a native widget for displaying html in the EHR (e.g. Java) using something like OAuth for authentication. Is there something that FHIR/CDS Hooks/Smart would improve upon this type of solution (with out having to rewrite the entire existing web application to use FHIR messaging)?
Grahame Grieve (Feb 04 2018 at 20:29):
well, Smart App Launch (http://hl7.org/fhir/smart-app-launch) is what you want, but whether that requires you to 'rewrite the existing web application to use FHIR messaging' is not clear - it would depend on your application, but I think not so much
Last updated: Apr 12 2022 at 19:14 UTC
