RingMD’s work with the Indian Health Service, Ohio’s 988 network and Alaska’s IDD telehealth program shows why public-health scale cannot be reduced to a user count. Scale may be geographic, operational or intensely personal—and each form changes what a system must do well.
At RingMD, we have learned that public-health scale looks different in every program.
Sometimes it is measured in geography, sometimes in organizations, and sometimes in how deeply a service matters to one person or family.
The number alone never tells the whole story.
Public-health infrastructure resists that simplicity. A service can reach a population measured in millions and still succeed or fail in one low-bandwidth encounter. A platform can connect nineteen organizations and face more workflow variation than a product used by thousands of individuals in the same way. A statewide program can serve a comparatively narrow population yet demand extraordinary specialization, availability and continuity for each person.
RingMD’s U.S. portfolio illustrates three different meanings of scale.
At IHS, RingMD supported a national telehealth mission within an agency serving approximately 2.7 million American Indian and Alaska Native people and 574 federally recognized Tribes in 2022. In Ohio, our 988 work spans nineteen local crisis contact centers and the services surrounding them. In Alaska, scale is personal: repeated, specialized support can matter deeply to an individual, caregiver and household.
Each program asks RingMD to carry a different kind of responsibility.
IHS: scale across geography, governance and conditions
In 2022, IHS made RingMD’s secure clinical video platform available across its federal facilities. We designed the platform for patient-to-provider and provider-to-provider meetings across common devices, including use in homes and schools where broadband may be limited.
At IHS, scale is as much about variation as population.
Care is delivered across 37 states through federal, Tribal and urban Indian health programs. Communities differ in geography, infrastructure, local governance, clinical workflows and digital access. A national platform cannot assume that every site has the same staffing, connectivity or relationship to the central agency.
At this scale, standardization and local reality must coexist. Security controls, identity, administration and support need enough consistency to sustain federal trust. The user experience needs enough flexibility to work across browsers, common devices and uneven bandwidth. Training materials must be reusable without pretending that every facility operates identically.
We configured and implemented the platform, onboarded and trained users, provided continuing support and completed the security work that led to an IHS agency Authorization to Operate. RingMD Telemedicine is currently FedRAMP Certified Class C (Moderate).
At this scale, the obligation is to maintain one secure foundation across many distinct operating environments.
Ohio 988: scale as coordination among autonomous actors
Ohio’s state-centralized 988 platform presents another kind of complexity.
Ohio brings together nineteen local contact centers, each with established teams, coverage areas, community relationships and local knowledge. RingMD is building a shared technology environment that gives the State greater coordination without asking those centers to become interchangeable.
But crisis response depends on context that cannot be flattened.
Which Public Safety Answering Point has an established relationship with a center? Which mobile team covers a particular location? What happens when a local center is at capacity? How should a warm transfer preserve information without making the caller repeat the story? Which community resources are useful in practice, not merely present in a list? What does a state leader need to see without interfering with frontline judgment?
Through discovery sessions and workshops with contact centers, behavioral-health authorities and mobile crisis partners, we are bringing voice, text, chat, routing, referral, documentation and analytics into a shared operational environment. We are building statewide clarity while preserving the local knowledge crisis response depends on.
Here, scale means coordinating organizations without treating them as interchangeable nodes. It is the number of handoffs, exceptions, relationships and decisions that must remain coherent when the person in crisis cannot afford friction.
Alaska: scale as depth, frequency and consequence
Alaska’s IDD telehealth program is statewide, but its most revealing measure is not the size of the eligible population. It is what repeated access can mean in one person’s life.
Eligible Alaskans enrolled in the IDD and ISW waivers can reach licensed clinicians around the clock for crisis support, assessment and ongoing behavioral-health follow-up, at no cost to the participant.
Our early Alaska reporting shows individuals returning daily or multiple times a day during certain periods. One person began using RingMD during a recurring gap in structured programming that had historically been associated with escalating behavior. Another caregiver used the service for practical guidance and emotional support, with engagement eventually reaching more than one family member.
These early stories show how recurring access can create value at the level of a person, caregiver and household.
A single recurring interaction may affect the individual, caregiver, direct-support staff, siblings, emergency responders and local providers. Thirty minutes of support may be modest as a transaction count and substantial as a stabilizing part of someone’s routine.
Scale, in this context, is intensity and consequence. The system must be available consistently enough to become trusted and specialized enough to interpret the situation well.
The wrong metric can distort the service
If all three programs were judged by the same dashboard, important work would disappear.
In 2022, IHS served approximately 2.7 million people across its broader system. At that scale, our work centers on facility adoption, availability, support performance, training, encounter quality, low-bandwidth performance and security operations.
Ohio’s platform should be measured through transfer quality, routing accuracy, specialist workload, regional capacity, referral completion and interoperability. The purpose is to improve the response to each call across the network.
Alaska’s service could be undervalued if success were defined only as the number of unique users. Repeat engagement, caregiver benefit, use during high-risk windows, appropriate escalation and continuity may be more revealing than breadth alone.
Metrics shape behavior. A system optimized for registrations may attract people without helping them return. A contact center optimized only for speed may shorten an interaction that needed time. A telehealth program optimized only for encounter volume may miss the value of a familiar provider connection.
At RingMD, we choose measures that reflect the mission each program is built to serve.
One platform does not mean one workflow
Our value across these programs comes from adapting a reusable foundation to three distinct missions.
The reusable foundation includes secure communications, configurable workflows, role-based administration, reporting, integration patterns, support and low-bandwidth design. Those capabilities become useful only when configured around the mission.
For IHS, the foundation supported secure patient-to-provider and provider-to-provider video in a federal environment. For Ohio, it is being developed into a crisis-operations layer spanning voice, text, chat, routing, warm transfers, mobile response, referrals and human-reviewed documentation. For Alaska, it supports device-flexible and telephone-accessible connections to clinicians familiar with IDD needs, along with follow-up and program reporting.
The reusable foundation gives each program a faster, proven starting point.
We preserve what is clinically and operationally essential, then configure our reusable capabilities around each service model. Agencies gain the benefits of a proven foundation without having to reshape frontline work around a fixed application.
Varun Arora keeps three missions moving
As RingMD’s Chief Operating Officer, Varun Arora leads our work across these different expressions of scale.
Varun connects each government mission to clear operating commitments: what the platform must do, who must participate, how the work will be governed and how RingMD and its agency partners will measure progress.
In practice, he works directly with agency leaders, program teams, clinicians, technical staff and external partners. He keeps federal security and usability connected at IHS, turns Ohio’s stakeholder discovery into routing, documentation and integration decisions, and makes sure Alaska’s requirements become a service that people and caregivers can actually reach and use.
Across all three programs, he keeps our team focused on the kind of reliability each mission requires.
In practice, that reliability may mean low-bandwidth performance across a continental system, a warm transfer that preserves a crisis interaction or a familiar door available during an unstructured hour.
Scale also changes the shape of risk
At IHS scale, a configuration or security failure can propagate across a national environment. Governance, change control and continuous monitoring become central to trust.
At Ohio’s operational scale, a workflow failure can appear at the boundary between organizations. The platform may perform as designed while a handoff, data mapping or local exception breaks continuity. Testing therefore has to follow the interaction across systems, not stop at the edge of one application.
At Alaska’s intensity scale, the risk can be personal. An interface that is confusing, a support line that is not answered or a provider who lacks relevant context can cause a person or caregiver to stop using the service. Reliability includes the emotional experience of reaching for help and finding that the pathway works.
For us, a support failure is serious even when it looks small on a technical dashboard.
That is why we combine security testing, integration testing, workflow validation, training, support monitoring, user feedback and outcome review. Each gives us a different view of whether the service is working as people need it to work.
The common unit is continuity
Across all three, our work is organized around keeping the next appropriate step available.
Care must continue when distance, fragmentation, bandwidth or crisis would otherwise interrupt it.
For IHS, continuity may mean that a patient can reach a clinician from a low-broadband setting or that one provider can collaborate securely with another. For Ohio, it may mean that a caller moves from 988 to mobile response without losing context. For Alaska, it may mean that an individual or caregiver can reach specialized support during a gap in ordinary services and reconnect with longer-term care afterward.
Population reach matters. Organizational coordination matters. Individual intensity matters. But each matters because it preserves a path from need to an appropriate next step.
RingMD earns trust when scale becomes invisible to the person using the service—when a federal operating model, a network of local centers or a statewide clinical service resolves into one connection that works.
Public-health scale has at least three dimensions: how far a system reaches, how many moving parts it coordinates and how much each interaction can matter. RingMD’s work across IHS, Ohio and Alaska is built around all three, with continuity of care as the common unit of success.