Provider Enrollment Guide

Multi-state Medicaid provider enrollment verification — aggregates TMHP PEMS, CAQH ProView, CA PAVE, FL FMMIS, and NY eMedNY into a single enrollment status per provider. Includes enrollment-gate integration for claims adjudication and revalidation risk detection.

Overview

The ProviderEnrollmentService consolidates enrollment status data from state Medicaid portals and national credentialing databases into a unified view. Before a claim reaches adjudication, the Enrollment Gate verifies that the rendering provider holds an active enrollment in the claim’s state — stopping unenrolled-provider claims before they incur processing cost.

State Enrollment Sources

Each state source is implemented as a dedicated adapter that normalizes enrollment responses into a common EnrollmentRecord model. The platform ships with five production adapters:

Multi-State Aggregator

The MultiStateEnrollmentAggregator queries all configured sources in parallel and returns the first non-empty result set per NPI + state combination. This “first-non-empty-wins” strategy provides resilience — if the primary source (e.g., TMHP) is down, the aggregator falls through to CAQH ProView or other configured sources.

Resolution Pipeline

1. Parallel dispatch — All registered IEnrollmentSource implementations are queried concurrently for the given NPI and state.
2. Result ranking — Sources are evaluated in priority order (state-specific sources first, then national).
3. First-non-empty wins — The first source returning a non-empty enrollment record set is used as the canonical response.
4. Cache write-through — The resolved result is written to Redis with a configurable TTL (default: 1 hour) to avoid redundant portal queries.

Supported Lines of Business

Texas Medicaid enrollment records include LOB classification. The aggregator maps TMHP LOB codes to individual enum values:

• STAR — Medicaid managed care
• STARPlusPlus — Acute care + long-term services (adults with disabilities, age 65+)
• STARKids — Children with disabilities
• CHIP — Children’s Health Insurance Program
• DentalMaintenanceOrganization — Dental managed care

Enrollment Gate

The StateEnrollmentGate runs as a pre-adjudication middleware in the claims pipeline. For every inbound claim, the gate:

1. Extracts the rendering provider NPI and service state from the claim.
2. Resolves the tenant ID (from HttpContext.Items["TenantId"] or the authorization token).
3. Calls the aggregator to retrieve enrollment status.
4. Returns Pass if the provider has an active enrollment, or Fail with a reason code if enrollment is inactive, expired, or not found.

Gate Response Codes

Revalidation Risk Detection

Medicaid providers must revalidate their enrollment periodically (typically every 3–5 years depending on state and risk tier). The ProviderEnrollmentService detects upcoming revalidation deadlines and generates alerts:

• 90-day warning — Early notice for providers approaching revalidation. Surfaced in the Sentinel Portal provider dashboard.
• 60-day warning — Elevated urgency. Triggers notification to the provider relations team.
• 30-day warning — Critical. Provider flagged in claims pipeline with soft-hold for manual review.
• Past-due — Revalidation deadline missed. Enrollment gate may pend new claims pending confirmation.

Caching & Performance

Enrollment lookups are cached in Redis to minimize latency and reduce load on external state portals:

• Cache key: enrollment:{tenantId}:{npi}:{state}
• Default TTL: 1 hour (configurable per tenant)
• Null handling: If a cached value deserializes to null (e.g., due to a JSON parsing error), the cache entry is treated as a miss and the source is re-queried.
• Throughput: Sub-millisecond cache hits support high-volume claims processing without bottlenecking on external APIs.

Tenant Configuration

Provider enrollment is configured per-tenant via the standard Cloud Health Office configuration system. Key settings are bound via .NET options pattern:

Getting Started

1. Enable enrollment checking — Set ProviderEnrollment:EnabledStates to the states you operate in (e.g., ["TX", "CA", "FL"]).
2. Configure source credentials — Add API keys for each state source to Azure Key Vault.
3. Set gate mode — Start with audit mode to observe enrollment check results without blocking claims. Switch to enforce after validation.
4. Verify via portal — Use the Sentinel Portal provider enrollment dashboard to confirm enrollment statuses are loading correctly.
5. Monitor — Check the /health endpoint for enrollment source connectivity status.

Related Documentation