ONC Rule open API
summary
ONC proposes an API condition of certification that requires certified health IT to publish FHIR servers, FHIR R2 + SMART/OAuth2 support, and public service URLs, with a 24‑month rollout target and endpoint publication for maintenance. Rule lists seven exceptions to sharing, allows three objective fee categories (development/deployment, API usage excluding patient access, value‑added), mandates app‑auth verification within five business days, drew 2,000 public comments, and assigns enforcement up to $1 million per violation.
AI-written summary · about
chapters (16)
- 0:00Start
- 3:06Conditions of Certification
- 8:55Healthcare Providers
- 9:05Definitions Matter
- 13:14Deep Dive for the Api Conditions Certification
- 13:43Api Data Providers
- 16:23Certification Criteria
- 17:37Regulatory Strategy
- 18:33Us Core Data for Interoperability
- 24:22Permitted Fees
- 25:50Openness and Pro-Competitive
- 26:37Maintenance of Certification Provisions
- 26:58Maintenance of Certification Requirements
- 35:08General Conditions
- 38:58Associated with Api Usage Costs
- 40:15Value Added Services
related talks
33mHealthcare Interoperability : From Buzzword to APIs
45mPanel: State Implementation of Patient Access API
26mUsing APIs to Transform the way CMS Shares Medicare Claims Data
42mAll of Us / Sync for Science
33mRegulation and Innovation in Healthcare
42mBuilding on Cerner with SMART on FHIR
49mFHIR Bulk Data API and what's new in v2
22mAPI’s in public healthcare – case Health Village