Creating a patient centred mobile app using FHIR
summary
Mobile app implements FHIR Questionnaire and Observation resources (Questionnaire for EQ‑5D‑5L, earlier EORTC QLQ‑C30 replaced for brevity), native iOS/Android front end rendering questionnaires via a Stencil web component in a WebView, backend proxy to a HAPI FHIR server with Keycloak auth, and periodic import from Google Fit/Apple Health into Observations. User testing includes a six‑week usability run and ongoing simulation where a sensor‑based QoL score is calculated and compared to validated questionnaire results to validate accuracy. Practical lessons: version control/implementation guide needed, offline proxy reduces requests, and publishing stores takes extra time.
AI-written summary · about
chapters (17)
- 0:00Introduction and speaker intro
- 0:22What is quality of life?
- 2:29App features and tech stack
- 3:09First iteration and user testing
- 4:18Improving questionnaire and diary
- 5:42Need for FHIR implementation guide
- 6:02Adding self-observations
- 7:28Proxy server for performance
- 8:33Health data integration
- 10:00App publication challenges
- 10:22Future personalized questions
- 11:04Fatigue diary and physician access
- 12:30Q&A on physician data sharing
- 13:37Q&A on user retention
- 15:22Q&A on health device integration
- 16:05Q&A on data requirements
- 17:09Q&A on questionnaire rendering
