I Named It Lilah — A Platform That Revolutionized Home Health Care

I I T : A P L AT FO R M T H AT R E VO L T H In 2012, a remote patient monitoring system cleared the FDA. It let elderly and chronically ill patients live at home — in their own houses, on their own terms — while their vital signs flowed automatically to a secure portal, where family members and caregivers could set thresholds. Cross a threshold, and someone who loved you got an alert. If that architecture sounds familiar, it should. Caregiver-configurable thresholds triggering alerts to family and care teams is now the standard model of the entire remote patient monitoring industry. Every modern RPM platform works this way. I named that system. I designed that threshold model. I led the engineering and drove it through two FDA clearances. Fourteen years later, I'm writing the origin story down — because it's a good one, and because the work deserves to be connected to the people who did it. "We didn't teach machines to watch patients. We taught them to tell the people who love you when it's time to look." — Rob Gaudet, product owner and engineering lead, LILAH (FDA-cleared 2012). How it started I was Director of Operations at Synapse Multimedia in Shreveport when a client named Lannie Richardson, owner of Central Control in Alexandria Louisiana, came to us wanting to build a home health monitoring product. The project was big — big enough that on top of running operations, I took on the product owner role and led engineering

myself. I worked alongside Jodi Funderburk, and together we built something ahead of its time. I named the platform LILAH: Living Independent Life at Home. That was the whole mission in four words. Your mother, your grandfather, the veteran down the street — living in their own home, with dignity, with a safety net made of software instead of a nursing home hallway. The core idea I brought to it was thresholds. Not just collecting vitals — anybody can collect vitals — but letting a caregiver or family member say "if Mom's blood pressure goes above this number, tell me." Non-emergency, human-in-the-loop alerting. Technology that didn't replace the family; it armed the family. Remember the context: this was 2011. The iPad was a year old. "Telehealth" was barely a word. We were designing touchscreen software for patients in their seventies and eighties, wireless integrations with glucose meters, scales, blood pressure cuffs and pulse oximeters, video visits with care teams, and a secure caregiver portal — years before COVID made remote care mainstream and a decade before the industry caught up to the model. The federal record Here's what makes this story verifiable: the FDA wrote it down, and you can look all of this up yourself. On March 27, 2012, we submitted 510(k) premarket notification K120941 for the "Constant Care LILAH Home Health Monitoring System." It cleared on July 3, 2012. The cleared Indications for Use include this sentence: "Healthcare professionals and remote caregivers can review the transmitted information utilizing the Caretaker Portal and set thresholds to trigger non- emergency alerts based on specific thresholds being exceeded." That's the threshold model I designed, in federal language, in a permanent government record. A year later, on April 3, 2013, we submitted a second clearance — K130360 — for the Multi-User version, so hospitals and facilities could monitor many patients through one application, cleared for both prescription and over-the-counter use. It cleared July 15, 2013. Two FDA clearances in fifteen months, from a small Louisiana team, in an industry where clearances routinely take years and burn seven figures. I led the product through both, including hiring and directing the regulatory consultants who carried the submissions through the agency. I'm still proud of that pace, and of the discipline it took.

What LILAH went on to do My hands-on involvement ended in mid-2013, right as the second clearance landed — and the platform kept going, which is exactly what you want for something you built. By October 2013, LILAH was deployed with discharged patients at Lafayette General Medical Center, in partnership with the University of Louisiana at Lafayette's Center for Business and Information Technologies. LGMC's chief medical officer reported promising early results: fewer readmissions, closer monitoring, lives potentially saved. LILAH remained a flagship product in Constant Care Technology's portfolio for years afterward, alongside the CareConnection platform, serving the long-term and post-acute care industry. And the idea at its center — thresholds set by the people who care, triggering alerts to the people who can act — became the way the whole industry works. When I look at today's remote patient monitoring platforms, I see the architecture we drew up in Shreveport in 2011. Consider what "standard" actually means here. When Medicare created its remote patient monitoring reimbursement codes in 2018 and 2019, the model it paid for was ours: connected devices in the patient's home, physiologic data transmitted to a secure platform, and clinical staff reviewing readings against parameters to decide when intervention was needed. When COVID hit in 2020 and health systems scrambled to monitor patients at home, the architecture they deployed overnight — thresholds, alerts, escalation to a human who cares — was the one we had FDA-cleared eight years earlier. Hospital-at-home programs, chronic care management platforms, the sensor systems now watching over aging parents in millions of households: strip away the branding and the modern hardware, and underneath is the same design decision we made in Shreveport. Don't just stream data at people — that drowns them. Let the caregiver define what matters, and speak up only when it does. That single idea is why remote monitoring works at scale, why a nurse can watch a hundred patients instead of ten, and why a

daughter in another state can sleep at night. Billions of dollars of industry now rests on it. We didn't get to ride that wave commercially, but I know where the wave started, and the federal record backs me up: the threshold-alert model was cleared into existence in July 2012, with LILAH's name on it — and mine on LILAH. Here's the part that surprised even me: when I built LILAH, I had no idea what it would become. I knew we were building something good — you can feel that in your hands when it's happening — but I never looked back. I left in 2013 and went on to the next chapter, and then the next. It wasn't until now, fifteen years after the work began, that I finally sat down and researched LILAH's journey: the clearance records, the hospital deployment coverage, the years it spent as a flagship product, the industry that grew up around the model. Reading it all at once, a decade and a half later, was the moment I understood the size of what we'd started. I'll offer one reflection from that discovery, in the spirit of hindsight rather than regret. At the time, I recommended to the company's owners that we negotiate an equity stake in the product, because what I was contributing went well beyond building to spec — it was the innovation itself, the product vision, the engineering leadership. They were good, hardworking Louisiana businesspeople, but they came from a world where you do the job, invoice the job, and move to the next one. Owning a piece of software you built for someone else simply wasn't in the playbook they'd learned, and I couldn't make the case land. I don't fault them for it; recognizing an inflection point while you're standing on it is genuinely hard, and I've missed a few myself. But it's the single most expensive "no" of my career, and it sharpened a conviction I've carried into everything since: when you're contributing invention, not just labor, structure the deal like it. Why I'm writing this down Architects don't always end up in the press releases. The filings carry a company name, the articles quote whoever's in the room that day, and the story of who actually conceived and engineered a thing lives in emails, whiteboards, and memory. That's normal, and I'm not here to relitigate anything. I'm here to do what every system

architect/builder should do: put my chapter on the record, in my own words, tied to documents anyone can verify. So here it is, plainly. I named LILAH. I conceived and designed its threshold-based alerting model. I served as product owner and engineering lead, and I led the platform through both of its FDA clearances. The federal record kept the work; this post connects it to the builder. One practical note for other builders, offered as encouragement rather than complaint: write your role down while it's happening. Keep the emails. Get the agreements. Your future self — the one telling the origin story fourteen years later — will thank you for every dated document you kept. I've spent the decade since building things with my name attached: a boots-on-ground disaster relief organization, software platforms, an AI consulting practice. Every one of them carries something I learned building LILAH — that the best technology doesn't replace human care, it amplifies it. That was true for a grandmother checking her blood pressure in her own kitchen in 2012, and it's true for everything I build today. The work remembers. Now the record does too. The federal filings referenced here are FDA 510(k) K120941 (cleared July 3, 2012) and K130360 (cleared July 15, 2013), both publicly searchable in the FDA 510(k) database. The October 2013 article, "Patient monitoring system shows promise," remains published by the University of Louisiana at Lafayette.