Once someone has built a data product from Exchange data, like a dashboard, clinicians and patients need a way to open it.
For clinicians¶
Clinicians can open a data product in two ways. Both are still being developed, so the details may change.
On the Hub | Launched from the EHR | |
|---|---|---|
Where the clinician starts | The Hub’s website | Their EHR, with a patient’s chart open |
How they log in | With an Exchange account | No extra login. The app uses their EHR login. |
How the patient is chosen | The clinician picks one in the dashboard | The EHR passes along the patient whose chart is open |
Best for | Research teams, prototypes, and people who already use the Hub | Day-to-day clinical care |
The Hub is mainly for analysis and research, like prototyping a dashboard or sharing it with a research team. See the Hub documentation and the demos, which only run on the demo deployment. For embedding visualizations in clinical systems, we recommend launching them from the EHR with SMART on FHIR (see Where to start). The next section covers this path.
What SMART on FHIR does¶
SMART on FHIR is a standard that lets an EHR open an outside app and tell it two things: who the user is, and which patient they’re looking at. Most major EHRs, like Epic and Cerner, support SMART on FHIR.
For JupyterHealth, this means a clinician can click a button in a patient’s chart and see that patient’s wearable data from the Exchange, without a second login and without searching for the patient again.
Patients also use SMART on FHIR in step 1, when they log in to their hospital’s patient portal to bring in their own records. For clinicians, it works the other way around: their EHR uses it to open an outside app.
How a launch works¶
Two things must be set up first:
The Exchange has to trust the EHR. The Exchange admin sets this up. See Manage access to data.
The patient has to exist in both systems with the same MRN. The app uses the MRN to match the EHR’s patient to the Exchange’s patient. See Patient Identifiers.
Where to start¶
SMART on FHIR provider template: start here. Copy this repository, edit one cell of a notebook, and serve it as a dashboard with Voilà. The app runs on its own server, separate from the Hub. Its quickstart walks through a test launch, and it includes an example CGM dashboard.
jhe-smart-demo: a mock EHR, FHIR server, and Exchange that run on your own machine, for testing a launch without a real EHR. The demo still asks for a separate Exchange login instead of trading the EHR’s ID for an Exchange token.
jupyter
-smart -on -fhir: the Jupyter extension that handles the SMART launch. The provider template uses this extension, so you only need it directly if you’re building something different. Provider EHR Launch (SMART on FHIR) and the MedPlum dashboard tutorial, in the Exchange docs: how to set up the Exchange side of a launch.
For patients¶
Data products for patients are earlier along, and there isn’t a standard way to share them yet. The demos include a patient view of the CGM dashboard, as an example of what one could look like.