Patient access infrastructure · by Agentic Healthcare

The managed layer between every Personal Health Application and every Health Information Exchange.

Already routing production traffic across a growing footprint of connected HIEs. One governed on-ramp for PHAs. One calm, compensated connection for exchanges. Full compliance built in.

Aligned with TEFCA IAS 45 CFR Part 171 HIPAA NIST IAL2 SOC 2 (in progress)
What Cures Gateway is

One integration. Both sides of the wire.

Under the 21st Century Cures Act, every HIE must fulfil patient-directed access requests — with no volume ceiling and no default compensation. Consumer platforms are now shipping health-record access to hundreds of millions of users, and their traffic lands on HIE endpoints.

Cures Gateway sits in the middle: vetting each PHA, proving each patient's identity, honouring 50-state consent, buffering traffic, scoring every document, and keeping a compliant audit trail on every request.

HIEs receive one calm, governed connection and revenue on each request. PHAs receive one contract and one endpoint that unlocks a national footprint of exchanges.

Why now. The PHA wave is not a forecast — it's a schedule. Base-case adoption puts the network on track for 128M requests / month, with a plausible path to 30.5M / day as AI agents begin supervising individual health at scale.
UPSTREAM · PHAs ChatGPT Apple Samsung + 300 more CURES GATEWAY vetting · IAL2 · consent · buffering · IQHD · audit TEFCA IAS aligned DOWNSTREAM · HIEs SHARE LANES HeC + growing
Vet PHAsNIST IAL2Consent (50-state)Rate-limit & bufferIQHD scoringAudit trail
How it works

How a patient-directed request flows through the Gateway

Four moves, every request, in seconds.

01 · VET

Vet the PHA

Legal, security and technical vetting before any Personal Health Application can call the network.

02 · PROVE

Prove the patient

Identity assurance to NIST IAL2 — the person requesting is who they claim.

03 · CONSENT

Honour consent

Capture and enforce the applicable state consent regime, coast to coast, on every request.

04 · DELIVER

Deliver & score

Route via FHIR R4 / IHE XCPD / XCA. Score the response on 47 IQHD quality dimensions.

Who Cures Gateway serves

Two sides of the same problem. One shared infrastructure.

Whether you steward a Health Information Exchange or build a Personal Health Application, Cures Gateway removes the integration, compliance and scale work that stands between patients and their records.

For HIEs

Absorb the wave. Keep the value.

An unbounded regulatory obligation becomes governed, compensated participation — with zero infrastructure investment and full control over your rate limits.

Connected HIEs9 live Onboarding≤ 30 days ComplianceONC-defensible
$2.00 per 1,000 requests processed through the Gateway. Zero infrastructure investment required to receive it. Pricing depends on the quality, completeness and plausibility of the EHRs returned. Continuous-improvement reports are issued jointly with each HIE.
  • One integration; every current and future PHA reaches you through it.
  • Hourly XCPD / XCA-DQ / XCA-DR limits you set from your dashboard.
  • ONC-defensible audit trails and 50-state consent orchestration.
  • 47-dimension IQHD quality scoring on every CCD your network returns.
  • Per-request revenue share — negligible at pilot scale, transformational at wave scale.
For PHAs

One MSA. One endpoint. National reach.

Building a Personal Health Application that needs authorised access to patient records? Cures Gateway is the single, standards-based on-ramp to a growing footprint of connected exchanges — with the trust framework already in place.

Sandbox≤ 48 hours Production≤ 30 days Coveragenational & growing
One legal & technical integration in place of dozens. Predictable rate limits. Quality-scored responses. Sandbox and production parity. Cures Gateway operates as a request-only IAS Provider under TEFCA — your users' records, on their terms.
  • Standards-based endpoints: FHIR R4, USCDI, IHE XCPD / XCA-DQ / XCA-DR.
  • Patient identity proofed to NIST IAL2 before any record moves.
  • Consent captured and honoured under the applicable state regime.
  • TEFCA IAS alignment — Cures Gateway as your request-only IAS Provider.
  • Trust framework, contracting and compliance done once, network-wide.
The network today

Live and connected exchanges

Cures Gateway routes real production traffic through the HIEs below, with more joining every quarter.

C3HIETexas
HealtHIE NevadaNevada
HealtheConnectionsCentral / Northern NY
LANESLos Angeles
Manifest MedExCalifornia
MedalliesNational directory
Reliance eHealthOregon / Idaho
Rochester RHIOWestern NY
SHAREArkansas
+ more joining quarterly
Standards & assurance

Built on the standards regulators expect.

No custom sidecars. No proprietary lock-in. Cures Gateway speaks the same standards HIEs already run.

Data standards

FHIR R4 · USCDI

Standards-first API surface. Patient, Encounter, Condition, Medication, Observation, DocumentReference and the rest of the USCDI classes.

Exchange standards

IHE XCPD · XCA-DQ · XCA-DR

Native support for the IHE profiles HIEs already use for cross-community patient discovery, document query and retrieval.

Trust framework

TEFCA IAS aligned

Request-only IAS Provider posture. Patient-directed traffic, not treatment or payment routing.

Identity

NIST IAL2

Identity assurance on every requesting patient before any record moves.

Privacy & security

HIPAA · 45 CFR Part 171

ONC information-blocking regime honoured end-to-end. 50-state consent orchestration.

Operational assurance

SOC 2 (in progress)

Formal controls program, audit trails on every request, 24/7 operations centre.

IQHD — 47-dimension quality scoring

Every CCD returned through the network is scored on 47 quality dimensions across completeness, coding, medications and allergies — with joint continuous-improvement reports for each HIE.

See it running →

Ready to route your patient-directed traffic?

Talk to partnerships →