Panel: State Implementation of Patient Access API
summary
Federal rule forces Medicaid, MA, CHIP and FFE QHP issuers to serve adjudicated claims, provider directory and formulary data via FHIR R4 APIs and SMART/OAuth; states must follow implementation guides like Blue Button/CARIN to avoid penalties. Most states have no developer portals or API teams, so Colorado builds its first public Medicaid API (redirects to a MuleSoft sandbox at developer.colorado.gov), aims to cut manual PHI requests from 30 days to 15 days, and plans multi‑state app vetting and HIE integration.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:07Medicaid Apis
- 5:40Micah Jones
- 9:07The Cms Patient Access Interoperability Rule
- 10:09Consumer Directed Exchange
- 13:57How Members Get Their Data from the Medicaid Agency
- 18:39Interoperability Rule
- 29:06The Open Api Initiative
- 32:04Open Api
- 38:28Trust Frameworks
related talks
26mUsing APIs to Transform the way CMS Shares Medicare Claims Data
33mHealthcare Interoperability : From Buzzword to APIs
13mLightning Talks - Leveraging APIs to Transform Healthcare
23mMaking the Healthcare Developer Experience
39mFHIR to reduce burden and solve prior authorization challenges
34mFHIR Projects
17mEHR and Application Development Integration
20mMastering API Management for Enhanced Patient Care