Mountain Biometrics

Section 71401 · Technical Factor F.2 · September 30, 2027 deadline

Transport is solved. Semantics is not.

Make your rural network mean the same thing across four EHRs and a pharmacy system.

The returns

The structural gap states are working with.

Workforce gap

40%

of local health departments have no informatics staff. (NACCHO 2024)

Usage gap

42%

of clinicians use outside clinical info — even when their hospital has access. (ONC 2023)

Vendor heterogeneity

4–6

EHR vendors per rural network — vs. 1 in an integrated delivery system.

Why it matters

The record moves through the HIE. The meaning does not travel with it.

Forty percent of local health departments have no informatics staff. The 195 rural hospitals that have closed since 2005 didn’t fail at care. They failed at reporting it.

That gap is what Technical Factor F.2 asks states to close.

One patient. Four independent rural facilities. One year. Measure not counted.

  1. Day 0

    FQHC primary care

    A1c 9.2% logged to local flowsheet field

  2. Month 2

    Community pharmacy

    30-day refill gap in dispensing record

  3. Month 5

    Community mental health

    PHQ-9 narrative, no instrument score

  4. Month 9

    Critical Access Hospital ED

    Discharge summary, local diagnosis codes

  5. Month 12 · Reporting cycle

    Reporting assembly

  6. No semantic match

    Measure not counted

    UDS / eCQM numerator miss: LOINC 4548-4 absent, PHQ-9 score absent.

The record moved through the HIE. The meaning did not travel with it.

Where it fits in the state stack

Complement, not replace.

Transport

State HIETEFCA QHINsCarequalityCommonWell
This paper

Semantic

MTN Data Foundry

Analytics

InnovaccerArcadiaAzaraHealth CatalystSnowflakeDatabricks

Sits between the layer that moves data and the layer that uses it.

Metadata, not patient data.

Foundry works on schemas and field definitions. PHI never crosses a facility boundary.

Why the burden compounds

Traditional integration grows. Mapping-artifact architecture doesn’t.

It grows with every new facility onboarded and every annual specification change.

hrs / yr25 facilitiesall rural facilities
Where the conversation is happening

Eight states have put public dollars against this gap.

MEVTNHWAMTNDMNWIMINYMAORIDWYSDIAILINOHPANJCTRINVUTCONEMOKYWVVAMDDECAAZNMKSARTNNCSCOKLAMSALGAAKTXFLHI
Montana$233.5M
California$233.6M
Oklahoma$223.5M
Missouri$216.3M
New Mexico$211.5M
Indiana$206.9M
Mississippi$205.9M
North Dakota$198.9M

Eight states. $1.7B in public RHTP plans naming the same gap.

Public allocations and program plans (FY2026 NOFO awards) — not vendor or MTN engagements.

One more thing

Today your F.2 report is reconstructed by hand across four EHRs and a pharmacy system.

Tomorrow it assembles itself from the schemas you already own.

Federal reporting stops being a fire drill.

Thirty days. Three facilities. No PHI.

What we map
UDS · MBQIP · T-MSIS · eCQM
What we quantify
Hours of manual reconciliation today
What we demonstrate
Drift-resilient mapping against a real spec change

Procurement: NASPO ValuePoint · state cooperative contracts · Rural Tech Catalyst Fund (NOFO Cat. F · supports F.2).

Rural communities are owed health data infrastructure that doesn’t require an informaticist their state can’t hire. We’re building it.

— Warren Pettine, MD, Founder & CEO MTN · University of Utah Medical Machine Intelligence Lab

Get the white paper

Rural Data Infrastructure in Weeks, Not Quarters — Executive Edition

Hitting Your RHTP F.2 Milestones Before the 2027 Deadline