Operating evidence · Network to reimbursement

Building the systems that connect provider access to payment.

Ian Harman · Provider-network and technology leadership · TPN.health

Ian's current work spans provider-network data, care navigation, payer rules, eligibility context, healthcare EDI, claims, and payment operations.

25 to 5,000+Claims-per-day capacity reported by TPN.health
200×Reported growth in processing capacity
130K+Verified providers reported by TPN.health
95.2%Initial clinician-client connections retained

Matching creates value only when the surrounding system can fulfill it.

At network scale, a recommended provider is one state in a much larger operating loop: participation, credentialing, fit, availability, navigation, benefit context, care delivery, claim integrity, and reimbursement.

The operating problem

Behavioral-health access spans parties that use different systems and vocabulary. Members need help in the moment. Providers need appropriate referrals and predictable payment. Payers need accurate networks, accountable operations, and measurable access.

The product has to coordinate those needs without presenting one organization's internal status as another organization's outcome.

The technology work

  • Provider-network data and participation workflows
  • Care-navigation and matching infrastructure
  • Payer, eligibility, EDI, and claim transaction context
  • Claims, denial, reimbursement, and payment operations

The hardest work lives between systems of record.

01

State must remain truthful

Eligible, referred, scheduled, seen, submitted, accepted, paid, and denied are different facts owned by different systems.

02

Automation needs boundaries

High-volume claims workflows require deterministic controls, idempotency, evidence, failure recovery, and explicit human authority.

03

Networks are living systems

Provider data, specialties, participation, availability, contracting, and payment must remain aligned after onboarding.

Automation is credible when the transaction history can explain itself.

TPN.health publicly describes an integrated credentialing and claims platform supporting claims intake, denial management, provider reimbursement, and revenue-cycle workflows. It also states that Smart Data Solutions provides advanced clearinghouse capabilities.

That distinction matters: a platform connected to clearinghouse rails should not describe itself as the clearinghouse unless its formal role supports that claim. Good product language preserves the same state and ownership boundaries as good transaction architecture.

Company metrics, attributed to the company.

Integrated credentialing and reimbursement infrastructure

TPN.health's June 30, 2026 announcement reports growth from about 25 claims per day to capacity above 5,000 per day and describes its clearinghouse collaboration.

This account describes Ian's operating experience inside TPN.health and attributes platform metrics to TPN.health. It does not disclose internal member counts, confidential architecture, payer terms, or proprietary transaction data.

Claims Native brings national-infrastructure discipline to the smallest practice workflow.

The scope is smaller, but the principles remain: explicit state, bounded automation, separate human authority, idempotent transactions, and evidence that survives the handoff.

Explore Claims Native