Population Health
DemonstrationRural Tool — New Mexico Demo
A New Mexico demonstration of rural complexity planning and decision support.
Public demonstration
Illustrative scenario using a real demo—not live provider availability. Nevada history is not an Iterum client engagement.
New Mexico geography and demonstration configuration. This is not a live client production deployment.
System Phase
- Demonstration
- Version
- 1.2
- Current Phase
- Demonstration
- Last Updated
- 2026-09
- Maintainer
- Iterum Systems
Origin Context
Where this system came from
- Environment
- Configured as a public demonstration spanning urban, rural, frontier, and Tribal geographies in New Mexico.
- Trigger
- Provider-network gaps and member access complaints could not be explained by population-average reports.
- Constraint
- The work had to use existing data and staffing, with outputs defensible in both operational and contractual settings.
The Problem
Why this system exists
Rural care carries costs that population averages hide: travel, thin staffing, weather, isolation, and fragile provider networks. Without a common measure, access problems appear as anecdotes and rate discussions restart from first principles.
The Solution
How it works operationally
Rural Tool combines available New Mexico geographic, clinical, social, and network signals into member- and county-level complexity views. Operations teams can use the demonstration views to prioritize access work while planning and contracting teams use the same definitions in program and reimbursement discussions.
Core Capabilities
What the system provides
Rural complexity model
Combines the conditions that make rural service delivery operationally difficult.
Member decision support
Translates complexity signals into a prioritized next action.
County planning views
Shows where staffing, coverage, and access pressure are concentrated.
Contracting evidence
Carries the same definitions into rate and program-design discussions.
System Components
What the system is made of
Complexity index
Data ModelComposite scoring layer combining geographic, clinical, and social signals per member and per county.
Decision assist view
InterfaceFront-line view that translates the index into a suggested next action rather than a raw score.
County analysis pack
DocumentationRecurring county-level report used by operations and network teams to prioritize outreach and coverage work.
Metric definitions
DocumentationWritten definitions of every input signal, weighting choice, and refresh cadence.
Implementation Model
How it functions in practice
Inputs
What the system requires
- Member roster with residence geography
- Claims and utilization history
- Provider network and drive-time reference data
- Publicly available rural and social vulnerability indicators
Process
What the system does
- Normalize member geography against county and network reference data
- Compute per-member complexity signals on a scheduled cadence
- Aggregate to county and program views for planning use
- Surface prioritized member and county lists to operational teams
Outputs
What it produces
- Member-level complexity indicators
- County-level operational complexity views
- Statewide coverage and access reports
- Inputs for rate and program design conversations
Dependencies
What must remain true
- Reliable member address and eligibility data
- Stable provider network reference data
- An operational owner who acts on the outputs
- Ongoing definition governance so signals do not drift
Where It Works
Environments
Intended operational contribution
What this system is designed to support
- The public New Mexico demonstration shows how rural complexity can be represented across a statewide geography.
- The demonstration gives operations, planning, and contracting teams one set of definitions for discussing rural access conditions.
- The environment is configured for demonstration and does not represent a live client production deployment.
Evidence & Maturity
Documented evidence & limits
Public environment
New Mexico Demo
Uses New Mexico geography and demonstration configuration.
Cadence
Recurring
Refreshed and reviewed on a defined operational cadence.
Documentation
Written
Metric definitions, refresh logic, and interpretation guidance are documented.
Current Limitations
What this system does not solve
- Does not replace clinical judgment for an individual member.
- Depends on reliable address, eligibility, and provider-network data.
- Requires an operational owner to act on the outputs.
- Has not yet been independently validated against long-term outcomes.
- The public environment is a demonstration and does not represent a live client production deployment.
Start the Conversation
Interested in solving a similar operational problem?
Discuss one operational problemRelated Systems
Explore the portfolio
Related documented professional work
Where this system has been applied
These are documented professional-work contexts, not an Iterum commercial client list or former-employer endorsement. Descriptions below are not independently verified performance results.
Environment
Behavioral Health Organization
Standardized documentation, report recipes, validation processes, and reusable reporting infrastructure.