UW CIRG demonstrated two things

The use case described a young woman, a health care worker with a diagnosis of obesity, who was seen by a primary care provider using the Epic EMR. While using Epic, her provider reviewed and updated her immunizations in the state registry, directly enrolled her in a clinical trial using a trials information system, referred her to an outside nutritionist, and provided anonymized population data to public health. In a subsequent visit, the patient was counseled on weight and healthy habits using both individual data from the nutritionist, and population data from public health tailored for her age, occupation, and sex.

We (all) used standards

All of the systems in the demonstration used standards-based interoperability, implementing IHE "profiles" to ensure that data were exchanged without dependencies in particular vendor products. Any vendor implementing the profiles could "plug in" and exchange health data.

  • The decision support application used SMART on FHIR.
  • The public health surveillance dashboard used the Healthy Weight CDA.
  • Immunization registry used HL7 V2 over Web Services.
  • The clinical trials registry used the IHE Retrieve Form for Data Capture.

It looked very good

Here's a photo of the demonstration screen - a version of EpicCare configured for a primary care provider, showing the "Healthy Weight" tab, linked to the SMART on FHIR app. Photos of screens never come out that well, but this is so cool - the long sought after goal of public health making available a secure app, running inside the EMR, which blends patient specific information with public health knowledge.

Think of all the possibilities - not just for public health, but for patient reported outcomes, patient-centered interventions, integration of data from outside the EMR... But, more on the possibilities in a bit. For now, we have a few galleries of pictures to show you.

Gallery 1: The app itself

Below are some views of the SMART on FHIR app. We illustrated three features to give the provider information to motivate the patient to adopt healthier behaviors, and shed less healthy ones:

  • first, we show some ID information, to demonstrate that the app is reading the correct patient's data.
  • second, a graph showing the patient's body mass index (BMI) and age (the black circle) graphed against curves showing typical BMI for women of different ages and exercise levels. On average, women who exercise more have lower BMIs, at all ages.
  • third, the patient's occupation, health habits, and readiness for change, summarized from the nutritionists consult. With limited time, the provider can find the best intervention.
  • fourth, based on the patient's occupation, we provide tailored, occupation-specific patient education.
s

Gallery 2: The IHE Showcase

HIMSS and the IHE Showcase are always interesting!

Where can I learn more?

  • 2017 CIRG Healthy Weight Dashboard (smart on fhir standalone app shown on last page) - this was the other part of our HIMSS/IHE use case software.
  • Brief FHIR overview HHS Idea Lab blog post by Paula Braun - CDC/OPHSS/NCHS Entrepreneur in Residence - Winter 2016
  • Quick FHIR intro/tutorial by Pascal Brandt - UW PhD student - developed for MEBI 530, Winter 2017
  • email Bill Lober (lober@uw.edu) if you'd like to follow up on our work with SMART on FHIR or public health informatics.

Where is CIRG going with all this?

HIMSS had something over 40,000 attendees. Every year a new record. This was a record for the IHE Showcase as well; I believe I heard that 10-15% of the entire HIMSS crowd came through the Showcase.

We demonstrated an application integrated with the provider version of Epic using "SMART on FHIR". I understood from Epic that these protocols can be used on Epic 2015 or later implementations. SMART on FHIR has also been adopted by Cerner, GE, and others. I heard from Cerner that it can be used in production now, but it will become standard with their MACRA package, due out in 2017/18. So, SMART on FHIR is real.

This is big news for a lot of the work we do in the Clinical Informatics Research group. cPRO is a PRO platform developed by CIRG, and used in products like PainTracker, mPOWEr, the ePRO HIV PROs, a new Prostate Cancer PRO/intervention framework - TrueNTH, and proposed for an integrated heart failure project. With SMART on FHIR, we can insert provider interfaces for those applications as a tab into EpicCare, and we can insert patient interfaces for those applications into Epic MyChart.

This demonstration was driven by CDC, and focussed in bringing patient-specific health weight guidelines into Epic - blending public health knowledge with individual patient data from epic to help providers facilitate behavior change. The clinical data from Epic were height, weight, demographics, and some behavioral risk data. The public health decision knowledge were normative obesity data by gender, occupation, and exercise level, and occupation-specific patient education materials. The goal was to demonstrate providing tailored information to the provider, during the clinic, to support identifying the most productive health behavior to change, and to give the provider tailored information for the patient to support that change. That's an extensible concept. Here are a few ideas:

Integrated Pain Management

Longitudinal assessment, Rx for a self management intervention, and integration with statewide PDMP opiate data…

Post-surgical post-discharge assessment

Patient self assessment of wound healing and wound photographs and facilitated communication with providers (mPOWEr)

Patient Reported Outcomes

Rich patient reported outcomes (multi-instrument longitudinal assessments of patients in HIV, oncology, heart failure..)

Functional Assessment

Longitudinal functional assessment in the post-total joint replacement patient, with linkages to normative recovery trajectories