Leveraging FHIR Capabilities to Enable Patient Access and Provider Directory APIs
summary
Tutorial demonstrates concrete steps to make a FHIR R4 server meet the CMS July 1 requirements for Patient Access and Provider Directory APIs: posts US Core Patient StructureDefinition and race extension, uses $validate to catch invalid gender and race codes, creates a SearchParameter then runs a reindex job (13 patients → 100% indexed), runs $everything and member-match (returns patient with added identifier or 422 on no match), converts HL7v2 into a FHIR bundle via $convert-data, and exercises Touchstone test suites.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:51Timeline Overview
- 4:48FHIR Requirements
- 7:34FHIR Capabilities
- 9:50Demo
- 13:40Search Parameters
- 17:04Patient Everything
- 19:04Member Match
- 22:05Additional Search Requirements
- 25:13Dollar Convert Data
- 27:42Testing
- 28:57Summary
- 30:08QA
related talks
49mFHIR Bulk Data API and what's new in v2
26mUsing APIs to Transform the way CMS Shares Medicare Claims Data
45mMechanics of FHIR in Reporting and Referrals
13mLightning Talks - Leveraging APIs to Transform Healthcare
39mFHIR to reduce burden and solve prior authorization challenges
41mThe role of HL7® FHIR® in patient cost transparency
16mThe Future of Healthcare and Clinical Research Under FHIR
45mDa Vinci, Broad Update