CMS FHIR Certification
CMS FHIR Certification is for payors who want to fulfill CMS requirements, particularly the requirements of CMS 9115. At a high level, the process entails implementing several FHIR Implementation Guides (IG). An Implementation Guide is a set of rules that defines how to use FHIR resources to solve a particular problem or implement a particular data flow.
Once the IG is in place, you'll need to test against Touchstone Aegis test suite to confirm conformance. Depending on your program requirements, you may or may not choose to certify. CMS requires and recommends new IGs each year as regulations change and systems mature. Designing a system that can continually upgrade and adapt to new IG requirements will help streamline operations.
In general, organizations can expect that new FHIR functionality, especially for organization to organization data flow will be a theme of the coming mandates. This includes payor-to-payor interfacing as well as payor-provider FHIR interfacing.
Medplum can be used to implement the FHIR IGs in a quick and cost-effective manner. At a high level the workflow process is as follows:
- Configure your Medplum project to capture well-formed FHIR data
- Use existing tooling such as
Strict Mode, Bots, External Auth and more to ensure data correctness
- Test against the relevant Touchstone FHIR IG suite
- Certify and receive badges as needed
The following are common IGs relevant for payors:
|Service Name||Implementation Guides||Notes||Touchstone Conformance Suite|
|Patient Access API – Claims and Encounter Data||CARIN IG for Blue Button®||An example of the API in the wild can be seen on the CMS Blue Button developer documentation||Claims and Encounter Data|
|Provider Directory API||DaVinci PDEX Payer Network||An example of this API in the wild can be seen on Central California Alliance website.||Provider Directory JSON Suite|
|Patient Access API – Drug Formulary||DaVinci Payer Data Exchange (PDex) US Drug Formulary||This API exposes the brand name and generic drugs a health insurer agrees to pay for as part of coverage.||Provider Drug Formulary API|
|Patient Access API – Clinical Data||ONC API Resource Guide||Testing of Clinical Data API aligns with the standards and requirements set forth by ONC in their 21ST Century Cures Final Rule for 170.315(g)(10) for Single Patient API. Medplum has certified (g)(10).|
|Bulk Data Export API||Medplum Bulk FHIR Implementation||Testing of Clinical Data API aligns with the standards and requirements set forth by ONC in their 21ST Century Cures Final Rule for 170.315(g)(10) for Single Patient API. Medplum has certified (g)(10).|
|Admission, Discharge, and Event Notifications||DaVinci IG for Notifications||This is an event driven implementation guide that enables notifications for hospital admissions, clinic visits and more.||Notification Sender Test Suite|
Future Implementation Guides
At present more implementation guides are being discussed, developed and balloted, and the Federal regulations related to this field are under constant revision. The DaVinci Project confluence is a good resource for monitoring proposed IGs, and assessing their adoption and maturity.