FHIR Plugin for Epic

The Variables Look Neutral. The Pattern Isn't.

AequiPath โ€” FHIR Audit & Scheduling Parity Platform

AequiPath watches four ordinary-looking fields in Epic's prior-authorization and scheduling data, and flags when they quietly reproduce discrimination no one coded in.

AequiPath Snapshot
4Proxy variables monitored
2Layers, always-on + real-time
6Epic APIs integrated
Jan 1, 2027Compliance deadline
Built for
๐Ÿฅ Health Plans
๐Ÿจ Hospitals
๐Ÿ’Š Medicaid MCOs
โš–๏ธ Compliance Teams
Purpose, Mission & Values

Fairer Pathways. Healthier Communities.

Our Mission

To advance systemic fairness, structural transparency, and algorithmic governance across healthcare infrastructure.

Our Vision

A healthcare system where every person, in every community, has equitable access to timely, high-quality care, powered by trustworthy technology.

๐Ÿ›ก๏ธ

Integrity

Do what is right, always.

๐Ÿ‘ฅ

Service

People over profit.

โš–๏ธ

Justice

Fairness in every decision.

๐Ÿค

Equity

Remove barriers. Expand access.

โญ

Excellence

Build better. Go further.

๐ŸŒฑ

Evidence-Based

Use data. Drive lasting impact.

"Let justice roll on like a river, righteousness like a never-failing stream!" โ€” Amos 5:24 (NIV)Aequitas sicut torrens fortis (Vulgate)

๐Ÿ” The Problem

Neutral-Looking Data, Discriminatory Pattern

Prior authorization queues and scheduling systems routinely use claim density, zip code, Medicaid coverage, and missed-appointment history to decide who gets expedited and who waits. None of these variables mention race or income. All four are well-documented statistical proxies for them.

A prioritization rule built on these inputs can produce a discriminatory outcome without a single protected characteristic ever appearing in the code, which is exactly what makes it hard to catch, and easy to defend as "just operations."

โš™๏ธ What AequiPath Does

Two Layers, One Always Watching, One In the Room

๐Ÿ”

Retrospective Audit

Runs continuously against Epic's prior-authorization and scheduling data, risk-adjusted against clinical acuity, so it isolates the part of any gap acuity can't explain.

Layer 1 โ€” AequiPath
๐ŸŽฏ

Real-Time Flag

Sits alongside a live prior-authorization decision and flags it for human review the moment it lands in a known disparity pattern, before the patient feels the delay.

Layer 2 โ€” AequiPath

Output: a disparity report and a compliance-ready disclosure package for your quality and compliance teams, not just an alert, a paper trail.

๐Ÿ“Š See It In Action

Inside the AequiPath Dashboard

One-click audits, live disparity-ratio trend lines, and auto-generated disclosure packages, built for the compliance and quality teams who have to act on what it finds.

AequiPath dashboard: active audits, flagged records, participating hospitals, risk-adjusted disparity ratio trends by proxy variable, top flagged proxies, and recent findings
๐Ÿ”Œ How It Integrates With Epic

Built Entirely on Epic's Published APIs

AequiPath runs on Epic's Da Vinci and native FHIR APIs, nothing proprietary, nothing that requires custom Epic configuration.

CRD โ€” Coverage Requirements Discovery DTR โ€” Documentation Templates & Rules PAS โ€” Prior Authorization Support FHIR Scheduling CDS Hooks Bulk Data Access

No protected-class attribute is ever used as a model input, only claims, coverage, and scheduling data Epic already exposes.

AequiPath data flow diagram: Epic FHIR and Da Vinci APIs feeding a retrospective audit engine and a real-time CDS Hooks layer, producing the AequiPath dashboard and a point-of-care review flag
๐ŸŒฑ Who's Behind This

Built by a Former State Health-Policy Leader

๐Ÿ›๏ธ

January Montaรฑo is the founder of Aequitas Technologies, Inc. She served as Deputy Director of Sourcing on Colorado's COVID-19 Innovation Response Team, where she helped secure 27.8 million PPE items internationally, and later helped architect equity-driven policy for the 1.3 million members of Health First Colorado, the state's Medicaid program. She has testified before the Colorado General Assembly on algorithmic bias in AI systems.

โฑ๏ธ Why Now

Two Deadlines, One Date

Jan 1, 2027 The federal CMS Interoperability and Prior Authorization Final Rule requires health plans to run live FHIR prior-authorization APIs and supply specific denial reasons. Colorado's HB 26-1139, governing AI use in health insurance coverage decisions, takes effect the same day.
๐Ÿ—บ๏ธ How It Works

From Sandbox to Pilot in 4 Clear Steps

1

Discovery Call

A 30-minute consultation to understand your Epic build and current prior-auth and scheduling workflows.

2

Sandbox Proof-of-Concept

AequiPath runs against sandbox data to validate the API connections and the disparity model.

3

Pilot Validation

Runs against your live data with your compliance team, producing the first real disparity report.

4

Go Live & Scale

Full deployment with ongoing monitoring, reporting, and Aequitas Technologies as your engineering partner.

Ready to See What Your Data Shows?

AequiPath is built for a health plan, hospital system, or Medicaid MCO ready to see what its own prior-authorization and scheduling data actually shows.