ForgeRock: ID Bytes: How ForgeRock Enables CMS Final Rules Interoperability Requirements

ForgeRock: ID Bytes: How ForgeRock Enables CMS Final Rules Interoperability Requirements

 ET
Online

Identity Bytes Part 4: How ForgeRock Enables CMS Final Rules Interoperability Requirements

The CMS Interoperability and Patient Access final rule requires CMS-regulated payers to implement and maintain a secure, standards-based Patient Access API (using Health Level 7® (HL7) Fast Healthcare Interoperability Resources® (FHIR) 4.0.1) that allows patients to easily access their claims and encounter information, including cost, as well as a defined sub-set of their clinical information through third-party applications of their choice.

This rule also requires CMS-regulated payers to make provider directory information publicly available via a FHIR-based Provider Directory API.

We will show you how ForgeRock can help you quickly meet these new CMS requirements in a complete and secure manor, with little rework to your current applications and services. Specifically:

  • OAuth Authorization to FIHR APIs
  • Consent Management
  • SMART on FHIR Scopes and Context