Start by checking to see what others are doing ... if they have done it ... how they did it ...
Well, today we are going to look at three apps to see (probably) how they do it.
- Growth Chart (old but good)
- Wellsheet (on Epic's app store)
- OneRecord (patient facing)
I made a sheet to help ...
Who is this for?
- Providers (embedded in EHR)
- Providers (standalone launch)
- Patients (embedded in the patient portal)
- Patients (standalone launch)
- Patients (proxies)
- Insurers, Researchers, Public Health, "Backend Access"
What change is it seeking to make?
- Take an action (medication reminder app)
- Manage something better (clinical guidelines, workflow)
- Change behavior / educate (diagnoses, medications, meals, etc)
- Fast, better, more productive (Radiohead's OK Computer )
How do you enroll a patient/user? How do you launch it when it is needed? How do you know who needs it?
- System Event (ADT feed)
- Provider Initiated (Embedded in the EHR)
- Patient Initiated (Standalone Patient launch)
- Employer-Patient Initiated (Employee benefit - ie Hinge Health)
USCDI Data from FHIR
Observation, Device, DocumentReference, Binary, AllergyIntolerance, Condition, Procedure, Patient, Immunization, MedicationRequest
Other Stuff / Data / Hosting / Measure the Change
- Non USCDI - List / Appointment (Provider standalone)
- Write backs (like a clinical document into the EHR)
- Custom stuff on your AWS FHIRWorks, Azure, GCP, etc (see)
- Analytics
Boston Children's Growth Chart
Iconic FHIR App
Launch at https://launch.smarthealthit.org/
Non-FHIR
Analytics (minimal clicks, usage) - where to store this?
Wellsheet
Making a dent in a complex healthcare world
Other Data
Non-USCDI List Resource (how to figure out patient in standalone launch)
Practice patterns (user → action mapping)
Length of Stay? extracts?
Tasks? Where to save these?
OneRecord
Just beautiful
Other Data
Appointments (non-USCDI)
Number of EHRs connected per user?
Long lived token - secrets to query from webapp
?business model
No right answers, but my key ... what are you going to put in the top row?
Deconstructing Medical Apps Worksheet - Key2.pdf72.2KB
| Name | notes | url |
|---|---|---|
AWS FHIR Works | ||
Azure | ||
Google Cloud Healthcare API | ||
1upHealth | ||
Innovacer | ||
Commure | ||
Aidebox | ||
Truevault | not FHIR | |
Aptible | not FHIR | |
Redox | not storage focus, but do integrations | |
Interopion | not storage, but make SMART apps | |
Human API | not storage but make cool stuff | |
Health Gorilla | ||
Particle Health | ||
Ribbon Health | ||
