Current View
File name:

-

File size:

-

Title:

-

Author:

-

Subject:

-

Keywords:

-

Creation Date:

-

Modification Date:

-

Creator:

-

PDF Producer:

-

PDF Version:

-

Page Count:

-

Page Size:

-

Fast Web View:

-

Preparing document for printing…
0%
# Provider Atlas Edge FAQ (HealthEdge): Security, Integrations, Data Quality, and Implementation ## Key Facts - **AES-256 encryption at rest** is used to protect sensitive data, alongside role-based security for critical data elements. (Q1: “What security and data protections…”) - **Single sign-on (SSO) is natively supported and required** for authentication, enabling enforcement of login rules such as **account lockout** and **multifactor authentication (MFA)**. (Q1: “What security and data protections…”) - **Annual third-party penetration tests** are conducted to improve the platform’s security posture. (Q1: “What security and data protections…”) - **500+ built-in quality checks** support provider data quality, complemented by third-party validations such as **National Plan and Provider Enumeration System (NPPES)**, plus match-and-merge rules. (Q5: “How are you ensuring data quality…”) - **FHIR (Fast Healthcare Interoperability Resources) standards** are used for provider directory updates to support standardized interoperability, including needs tied to the **No Surprises Act**. (Q8: “Does this solution use FHIR?”) - Provider Atlas Edge is **cloud-native and SaaS-based**, **hosted on Microsoft Azure** (no on-premise deployment described). (Q10: “Are there cloud options…”) ## Summary ## What Provider Atlas Edge is and what this FAQ covers Provider Atlas Edge (formerly Provider Data Management) is presented as a platform for managing and distributing provider data across an organization’s ecosystem, with emphasis on security controls, integration options, data correction workflows, and data quality governance. The FAQ explains how Provider Atlas Edge supports role-based access, encryption, authentication requirements, and ongoing security testing, while also describing integration approaches, data quality methods, and cloud deployment. (Q1–Q10) ## Security and data protections Provider Atlas Edge states it supports role-based security for critical data elements and that its data model complies with applicable regulations including **HIPAA** and **HITECH**. It also specifies that sensitive data is encrypted at rest using **AES-256**. For authentication, the platform “natively supports and requires” **single sign-on (SSO)**, which enables enforcement of login rules such as **account lockout** and **multifactor authentication (MFA)**. The FAQ also notes **annual third-party penetration tests**. (Q1) ## Integrations and interoperability (APIs, HealthEdge products, and FHIR) The FAQ describes Provider Atlas Edge as designed for integration with both HealthEdge solutions (including **HealthRules® Edge**) and external Core Administrative Processing Systems (CAPS) via configurable APIs, with distribution across downstream systems including **PBMs** and care management platforms. It also states that API-based distribution supports integration with other HealthEdge solutions such as **Clinical Edge** and **Payment Accuracy Edge**, including real-time API and event-based distribution features. For provider directory updates, the platform adheres to **FHIR (Fast Healthcare Interoperability Resources)** standards, positioned as supporting interoperability required by regulatory frameworks like the **No Surprises Act**. (Q2, Q3, Q8) ## Data correction, quality controls, migration, and configuration When incorrect or conflicting data is found, Provider Atlas Edge provides a data correction and editing interface, using preconfigured match-and-merge rules or manual edits through a portal. For ongoing data quality and integrity, it specifies **500+ built-in quality checks**, plus third-party validations (example: **NPPES**) and match-and-merge rules; it also describes dashboards for real-time monitoring and compliance support (including the **No Surprises Act**). For migrations, the platform supports a **one-time full load** from legacy systems, followed by incremental changes and “near real-time updates.” Business rules for match/merge, validation, and distribution are described as highly configurable via a low/no-code framework. (Q4–Q7) ## Implementation and deployment model Implementation is characterized as rapid due to a low/no-code framework and pre-configured workflows, with support for incremental data loads and real-time updates. Deployment is described as **cloud-native** and **SaaS-based**, specifically **hosted on Microsoft Azure**. (Q9–Q10)

About this content