This starter-kit application is a simple SMART on FHIR App.
- Fetches Patient FHIR data
- Displays Patient information using FHIR Visualizer
- Allows User to Modify Patient information
yarn installyarn start- Goto SMART Launcher
- Leave everything as default, at the bottom of the form change the launch url to
http://localhost:3000 - Click Launch
SMART on FHIR is secure and so this app will need to be able to fetch tokens from the same identity provider as your EMR.
This guide walks through the setup process for a SMART on FHIR app using the Azure SMART Proxy for Azure Active Directory.
Not covered: Running with an identity provider other than Azure Activer Directory.
- Change client ID in index.js to the client ID generated in the above steps.
yarn start- Follow these steps to create a SMART Launcher from your EMR:
- Click on the link
Think about what this app does. It has all the boiler plate you need to access and modify a FHIR resrouce. If you've ever had a piece of functionality you've wanted to add to an EMR you can code it in a SMART on FHIR app- using all the web dev tech you already know. Then just add that app to your EMR.
An example use of this is the Chestist demo app that packages ML assisted image analysis.
#References: This project was bootstrapped with Create React App.
Quickstart on deploying a SMART app in Azure
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.