FHIR Projects
summary
Built a SMART on FHIR patient education app that authenticates with OAuth2 launch, reads patient context (active problems, active meds, procedures in the past year), maps content to clinical codes, and writes exact-version history back using the Document resource write-back or vendor APIs (Epic uses an HL7 transcription API). Prototyping with clinicians speeds EHR validation, which is the longest step and includes a rigorous security audit; teams use Postman and HAPI and report the old quarterly content upload cost 25–30 hours per quarter.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:32Business Problems
- 3:55Integration Flow
- 5:35Development Stages
- 8:36Authentication
- 9:14Lessons Learned
- 11:06Validation Process
- 19:07ONC Certified Products
- 22:50Dynamic FHIR API: CCDA
- 23:20Dynamic FHIR API Client
- 25:36Logging to FHIR API
- 27:24FHIR API Development Best Practices
- 29:42FHIR App Prototype: Health Lock-It
