RingMD’s work with the Indian Health Service shows why federal security and practical access are not competing requirements: a telehealth platform has to satisfy both before it can serve its mission.
For RingMD, federal security and simple access have always belonged in the same product.
Patients need an easy way into care, and IHS needs confidence that every encounter is protected.
Our work with IHS brought those priorities together in a secure telehealth platform designed for real devices, real clinical workflows and communities where connectivity may be limited.
That shared standard guided the implementation from the beginning.
In July 2021, IHS awarded RingMD a clinical video telehealth contract. After implementation work with agency staff and engineers, IHS launched RingMD across federal facilities on October 31, 2022, as the first telehealth-focused platform IHS had deployed.
The platform needed to protect sensitive communications inside a federal environment. It also needed to work across ordinary devices and in homes or schools where broadband might be limited.
Security and simplicity were not two versions of the product. Together, they defined whether the product could be used for care.
National scale includes many operating conditions
In 2022, IHS served approximately 2.7 million American Indian and Alaska Native people across 574 federally recognized Tribes in 37 states.
That population conveys the breadth of the IHS mission. We designed RingMD for the full range of settings and communities IHS serves, and we track platform use through actual users and encounters.
For our team, that breadth translated into a practical design challenge: one national platform had to work across very different care settings.
A national platform may be used at a federal facility, in a patient’s home or in another community setting. People may arrive with different devices, connectivity, digital confidence and accessibility needs. Clinical workflows differ across specialties and locations. Distance to in-person services can range from inconvenient to prohibitive.
The central technology must therefore be consistent without assuming the environment is uniform.
We designed for more than volume. The harder test was variation: how many real conditions could RingMD accommodate without weakening privacy, reliability or clinical responsibility?
IHS required a common foundation that could operate inside local realities rather than ask every local reality to become the same.
Low bandwidth is a design requirement
Connectivity is sometimes discussed as a temporary inconvenience that better infrastructure will eventually remove. For healthcare systems serving rural and remote communities, it is a present operating condition.
From launch, RingMD was designed to work across multiple devices and support televideo visits in homes and schools where broadband may be limited—capabilities IHS specifically highlighted because they are central to the mission.
A platform designed only for ideal connections can widen the gap it claims to close. The person closest to specialty care receives the best experience. The person for whom telehealth matters most encounters a frozen screen, a failed join or a workflow that assumes more bandwidth than the community has.
Designing for constrained connectivity involves more than reducing image quality. Joining must be simple. Essential controls must remain understandable on smaller screens. The system should avoid unnecessary steps and preserve useful communication when conditions fluctuate.
Low-bandwidth performance is not a secondary feature for rural access. It is part of whether access exists.
The visible controls carry clinical meaning
RingMD’s IHS workflow was built around several essential safeguards: clinicians obtain verbal consent, verify the patient’s identity at the beginning of the encounter and do not record the session.
We treat each of those steps as a clinical and ethical safeguard, not administrative friction.
Consent establishes that the person understands and agrees to the mode of care. Identity verification helps ensure that protected information and clinical decisions are associated with the correct patient. The prohibition on recording protects the encounter from becoming a persistent artifact simply because it occurs through a digital channel.
The platform must make these responsibilities practical while clinicians carry them out.
Our approach automates where it helps and keeps human actions visible when the action itself is the safeguard.
A well-designed workflow does not hide professional responsibility. It places responsibility at the right moment and makes it easier to perform consistently.
Encryption is necessary, not sufficient
RingMD is a secure, cloud-based system that encrypts audio and video communications. For IHS, that protection supports patient safety, privacy and the integrity of entrusted information.
Encryption is a foundation. Federal operation requires a wider discipline.
Identity and access have to be governed. Roles need appropriate permissions. Changes must be assessed. Vulnerabilities must be managed. Security documentation must remain aligned with the system that is actually operating. Incidents require clear processes. Training and support must reinforce the way controls work in practice.
We obtained an IHS agency Authorization to Operate for the cloud service, giving IHS a defined federal security basis for using RingMD in its clinical environment.
We treat the ATO as an ongoing operating obligation. Continued trust depends on managing defined conditions as the technology, threat environment and user needs change.
At RingMD, security is part of daily operations—from access management and vulnerability response to change control, monitoring and user support.
Simplicity is the result of hidden work
A patient experiences a link, a browser, a screen and a clinician. A provider experiences a joining flow, an encounter and a set of controls. Neither should have to see the full administrative and technical machinery supporting the session.
That apparent simplicity is built.
The service has to be configured. Users need clear guidance. Administrators need tools for managing access. Training materials must fit different roles. Support needs to respond when the ordinary path fails. Security controls have to operate without turning every encounter into an information-technology exercise.
Our IHS delivery included implementation, configuration, onboarding, training, user guidance and continued support alongside the cloud platform itself.
This operational layer rarely appears in a product screenshot, yet it determines whether a platform moves beyond deployment.
The true user interface includes every place a person can become stuck—and every process that helps the person continue.
Support is part of the infrastructure
When a user cannot connect to a health platform, a technical problem becomes an access problem. An appointment may be delayed. A clinician’s schedule may be disrupted. Confidence in virtual care may decline. In a remote setting, the fallback may involve substantial travel or no immediate encounter at all.
Support therefore affects access.
Good support identifies whether the problem comes from the device, network, account, workflow or system configuration. It communicates in language the user can act on. It also returns recurring problems to the product and implementation teams so the same friction is not accepted as permanent.
The clinical video telehealth initiative our team supported received a 2022 IHS Director’s Award for Customer Service—recognition of work that advanced quality and operations across the agency’s mission.
We are proud of that recognition because it reflects something our team lives every day: in government healthcare, responsive service is how the mission reaches the user.
RingMD expanded secure telehealth choice at IHS
IHS deployed RingMD alongside Webex, giving the agency two secure options for providing telehealth care.
For IHS, that meant more choice and greater operational resilience.
We did not need to replace every tool to add meaningful value. Different platforms can serve different workflows, and a dedicated clinical option gave IHS greater flexibility in how it delivered virtual care.
Our goal was to strengthen IHS’s telehealth ecosystem with a dedicated clinical option, not force every workflow through a single tool.
We brought a telehealth-focused environment designed for patient-to-provider and provider-to-provider encounters, device flexibility, lower-bandwidth conditions and federal operating requirements. IHS determined how that capability complemented other services and local practice.
That is how RingMD added value: by fitting the agency’s broader ecosystem while meeting the distinct demands of federal telehealth.
Access requires continuous governance
Telehealth accelerated during the COVID-19 pandemic, but emergency adoption did not remove the need for durable rules. IHS had already used telehealth for decades and expanded virtual care sharply during the public-health emergency. The RingMD implementation added a dedicated cloud option to that larger history.
Once deployed, a national service continues to change.
Browsers and devices update. Clinical teams discover new needs. Security standards evolve. Support patterns reveal where users struggle. The organization has to decide which changes improve access, which introduce unacceptable risk and how to implement improvements without disrupting care.
That is why authorization and usability belong in the same governance loop. A security change that unintentionally blocks a common device is an access issue. A usability shortcut that weakens identity assurance is a security issue. Operations must be able to see both consequences.
As RingMD’s COO, Varun Arora leads our operating work at that intersection—bringing federal delivery, security discipline, user support and continued accountability together after launch.
That alignment keeps federal security meaningful in the day-to-day experience of patients, clinicians and support teams.
The false choice
We have never accepted the idea that secure and accessible systems sit at opposite ends of a line. Our IHS work shows that the strongest federal health platform must do both.
Security creates the conditions under which patients and clinicians can trust the channel. Simplicity creates the conditions under which they can actually use it. Low-bandwidth performance extends those conditions to places where a conventional design might fail. Training and support keep the conditions intact when real users meet real problems.
Our operating model keeps those responsibilities connected from implementation through day-to-day support.
Together, IHS and RingMD established a reusable, telehealth-focused option across federal facilities serving a large, geographically distributed and diverse population.
We built and support that option with both sides of the obligation in view.
RingMD brings federal rigor and human access together in the same encounter—giving patients a system they can use and IHS a platform it can trust.