Since you forked the tutorial, the gh-pages branch has already been created, however GitHub won’t publish your site until you make a change to the gh-pages branch, so let’s make a change.
GitHub pages works by hosting content from a gh-pages branch. Setting up GitHub pages is easy, so easy in fact that it’s already done for you. GitHub Pages is a convenient way to host static or client rendered web sites. For the purposes of this tutorial we will be hosting our SMART app through GitHub Pages. We used Slate to create the documentation for this tutorial. The other content you see in the folder is the site for this tutorial. When this page is invoked, your SMART app will have everything it needs to run and access the FHIR API. This page will be invoked via redirect from the Authorization server at the conclusion of the SMART authorization workflow. More info on this in Run your app against SMART Health IT Sandbox section. This file was created for convenience factor to allow you to use the same app to configure it against the SMART Health IT Sandbox. This is a clone of the launch.html above. More info on this in Standalone App Launch for Patient Access Workflow section. In production, you may want to create a separate app for patient facing vs provider facing version of the app. This file was created for convenience factor. Similar to the launch.html above, this file is the entry point when launching a standalone patient application.
#Smartapp gethub code#
In this tutorial, this page will be invoked when you launch your app from Cerner’s code console.Īs the entry point into your SMART app, this page will kick-off the SMART authorization workflow. In the SMART documentation, this is your app’s “launch URL”. Launch.html is the SMART app’s initial entry point and in a real production environment, would be invoked by the application launching your SMART app (for instance, the EHR or patient portal). For your production applications we’d recommend pulling in the appropriate version of fhir-client.js using npm or some other package manager to easily keep your application up to date. This tutorial is designed to have a minimal footprint so we made the decision to directly include a version of fhir-client.js for simplicity. This tutorial uses this library when walking you through building your first SMART app.Īdditional documentation on fhir-client.js can be found here.
Located in the lib folder, this is a version of fhir-client.js which is an open source library designed to assist with calling a FHIR API and handling the SMART on FHIR authorization workflow. Let’s take a look at some of the notable files contained within: The smart-on-fhir-tutorial/example-smart-app folder contains the example SMART app which you’ll be using throughout this tutorial. The branch you are going to work on is gh-pages. Prerequisitesįirst, you’ll want to fork this tutorial from smart-on-fhir-tutorial to your GitHub account. Outside of this tutorial, the use of R4 over DSTU2 is encouraged. Note: This tutorial is in the process of being updated for the newer version of FHIR - R4. Self register an app with SMART Health IT.Run an app in Cerner’s SMART on FHIR sandbox.This tutorial will walk you through creating an app in Cerner’s SMART on FHIR ecosystem.Īfter completing this tutorial you will know how to:
0 kommentar(er)
