Track record
We did not learn hospice eligibility from a whiteboard.
Before Atulya, our team lived inside the eligibility pipeline across Florida, at volume, under contract, with real physicians and families waiting. The product choices we make now are shaped by that history: what breaks at 2 a.m., what EHRs reward, and what actually gets a patient onto service.
Across dozens of counties with hospice access; includes weekend and on-call coverage patterns typical of statewide programs.
Eligibility at scale across Florida
We have supported 50,000+ patient referrals and admissions for hospice programs serving dozens of counties statewide. That volume spans urban and rural catchments, different referral patterns, and varied documentation expectations. That experience we lean on when we design defaults, error handling, and escalation paths in Atulya.
Weekend and on-call coverage were part of the reality: referrals do not wait for Monday. We built operational muscle around after-hours queues, physician availability, and clear handoffs so patients were not stuck in limbo when the timing mattered most.
Patient-to-physician software before it was table stakes
We developed a patient-to-physician web application to tighten the eligibility loop: healthcare organizations could route a case so a physician could review the patient and context without the usual phone tag or fax round-trips.
The goal was speed with accountability: structured intake on one side, a decision-ready view on the other, and an audit trail in between. That same philosophy (single source of truth, physician-ready artifacts) is what Atulya extends end-to-end.
Native Android for how hospices actually work
As our two largest customers, VITAS Healthcare and Empath Health, scaled bedside and field workflows, we evolved the product into a native Android solution to integrate more cleanly with the EHR and device ecosystems their teams already used.
Mobile web was not always enough for SSO, certificate pinning, peripheral workflows, or the reliability clinicians expect at the bedside. Moving to native Android let us meet those constraints while keeping the physician experience fast and consistent.
AI that turns forms into physician-ready summaries
We integrated an AI-powered pipeline to ingest intake paperwork, normalize fields, and produce concise, reviewable documents for physicians, so MD time went to clinical judgment, not retyping or hunting through PDFs.
Human-in-the-loop was non-negotiable: models suggested structure and language; physicians still owned the decision. Atulya’s AI-drafted CTI continues that pattern: generated from structured intake, always editable, always attributable.
Operations across county contracts
Beyond engineering, we ran day-to-day operations for multi-county programs: staffing coverage, escalation playbooks, and ongoing client relationships so eligibility work kept moving when volume spiked or edge cases appeared.
That operational load taught us where software alone fails: handoffs, SLAs, and communication rhythms matter as much as features. We carry that into how we partner on Atulya rollouts.
Product leadership grounded in constraints
We defined product requirements and roadmaps that balanced what nurses and medical directors needed in the field with what engineering, compliance, and EHR reality allowed, sequencing releases so the highest-risk bottlenecks (physician access, form completion, certification) were addressed first.
Atulya is the next chapter: the same problems, fewer compromises, and a platform purpose-built for hospice eligibility from day one.
