No UI is the New UI

By Luis Cisneros, CEO | Serelora

My mother used to sit at the clinic computer after a long day and say the same thing. She would be clicking through the electronic health record, searching for something about a patient, toggling between screens and tabs and modules, and she would turn to me and say I just wish I could talk to it. I wish I could ask it to bring up what I need so I can focus on the patient. So I can focus on the procedure. So I can focus on actually doing the work.

My father felt it even more deeply. He was old school. He kept his notes on paper because paper was easier. You could flip through it. You could find what you needed without clicking through endless menus trying to remember where the system hid the information you were looking for. The computer was supposed to make things faster, but for him it made things harder to find. So he wrote things down by hand and organized them the way his mind worked.

But my parents also taught me something else that took years to fully understand. They would say I have never just seen a head. I have never just seen a heart. I have never just seen an arm and I have never just seen a mouth. But I have seen a whole human being before.

That observation haunts me now. We have broken apart dentistry from medicine. We have broken apart mental health from primary care. We have broken apart primary care from specialties. Each fragment has its own system, its own records, its own way of describing the same patient. And in all that fragmentation we lost sight of the fact that there is one human body. One human being.

I think about my parents constantly as we build Serelora. They were both clinicians who spent their careers serving patients, and they both felt the same frustration with the tools that were supposed to help them. The technology that promised efficiency delivered complexity instead. The systems that promised clarity delivered navigation. And the records that were supposed to capture the patient captured only pieces, scattered across silos that never talked to each other.

That experience stayed with me through every job I held in healthcare. I managed medical and dental clinics. I worked as a medical scribe watching doctors toggle between six systems to answer one question. I processed claims and saw how much human time gets consumed by forms that could fill themselves. I built insurance plans and learned how the entire industry optimizes for documentation rather than care. And through all of it, I kept hearing my mother’s voice. Why can’t I just ask it what I need to know?

That question is no longer rhetorical. The technology to answer it finally exists. And healthcare, the industry that needs it most, is about to change in ways that will make the old world of dashboards and logins feel like a strange and painful memory.

The Weight of Navigation

Something happens to clinicians over time. They stop noticing how much of their day consists of searching rather than thinking. Open this tab. Set this filter. Export this report. Cross-reference with that other system. Copy the number. Paste it somewhere else. Click. Click. Click. The cognitive load accumulates so gradually that it becomes invisible, like background noise you forget you are hearing until someone finally turns it off.

Consider something as simple as wanting to know how a patient’s blood sugar has trended over five years. In most systems today, that question requires opening a dashboard, finding the right analytics module, setting the date range, selecting the lab type, pulling the trend view, and then still wondering whether those data points are accurate or where they actually came from. The doctor asked one question. The system demanded fifteen actions.

My father was right to prefer paper. At least with paper you knew where things were.

We started building Serelora because we believe that pattern is fundamentally wrong. Clinical software should not feel like navigation. It should feel like understanding. It should feel like asking a question and receiving an answer so you can get back to the work that actually matters.

Why Big Tech Will Not Solve This

Something remarkable is happening in AI right now. The infrastructure for connecting systems has become almost magical. Tools that once required months of custom engineering can now talk to each other with minimal configuration. This is why every major technology company wants into healthcare. They see the opportunity and they see the scale.

But there is something they do not see.

Healthcare is not another sector to conquer. When big tech looks at this industry, they see market size and growth curves and another vertical to add to the portfolio. They build general-purpose tools and assume healthcare will adapt. That approach has failed for decades, and AI will not change the fundamental mismatch. You cannot bolt clinical safety onto a consumer product as an afterthought. You cannot treat patient data like any other data. You cannot optimize for engagement when the stakes are human lives.

There is another problem brewing that the industry has not fully confronted. Every day, physicians are discovering that they can build their own AI tools. They write prompts, create workflows, and share solutions for real clinical pain points. On the surface this is wonderful. The people closest to the work should shape the tools.

But when you look closer, two failures emerge almost immediately. Most of these projects remain prototypes that never integrate into electronic health records, identity systems, or audit trails. They exist as islands. And when tools sit outside the clinical environment, patients pay the price through fragmentation. They get pushed into a patchwork of portals and links and one-off apps that do not communicate with each other. The physician experience improves while the patient experience fractures.

Healthcare does not need more tools. It needs infrastructure that makes tools unnecessary. It needs a unifying principle that serves patients rather than individual workflows. It needs a standard.

What Serelora Delivers Today

The user opens a chat and asks for what they need. That is it. No dashboards. No navigation. Just a question and an answer.

That simplicity is not accidental. It is the result of everything the system has already done before anyone ever types a word.

When patients or providers feed in their data, whether intake forms, PDFs, labs, notes, claims, or images, Serelora builds a Patient Knowledge Graph. Every piece of information becomes a verifiable claim tied to its source, its date, and its confidence level. This graph is not a summary. It is a structured representation of everything known about the patient, with every assertion traceable to the document that produced it.

But the graph alone is just the foundation. Once it is built, the system sends it through an intelligence layer that performs the analysis a physician would otherwise have to do manually. It generates risk scores for emergency visits, hospitalization, and mortality. It identifies social determinants of health barriers and financial coverage gaps. It constructs a causal inference table that traces problems back to their root causes rather than simply listing symptoms and diagnoses side by side. And perhaps most valuably, it identifies what is missing. Which labs would increase confidence in these risk assessments. Which imaging reports would clarify the clinical picture. These gaps become recommended actions for the care team, and when those tests get ordered they also become billable events for the practice.

All of these generated insights then get appended onto the original graph as a new version. The system preserves what was known when, what analysis was performed, and what conclusions were drawn at each stage. This versioning matters for medico-legal purposes. It matters for auditability. It matters for the kind of trust that healthcare demands.

By the time someone asks for a report, the thinking has already been done. The AI does not generate new answers in that moment. It compiles what the graph already knows into exactly the format requested, with every statement linked to its source evidence, every clinical term connected to its definition and anchored codes, every recommendation tied to the guidelines and protocols that support it.

This means the user can ask for exactly what they need and nothing more. A full comprehensive report. An analysis of labs. A financial report showing SDOH risks and coverage gaps. A plan comparison showing what insurance would be optimal for this patient’s care needs. A physician who needs a quick clinical snapshot does not have to scroll through ten pages of financial analysis. A care coordinator focused on benefits optimization does not have to wade through diagnostic histories. Each report serves its purpose.

The clinical reports themselves are structured to support real reasoning rather than overwhelm with data. Risks are organized into functional domains with their respective phenotypes. Cardio metabolic domain with cardiovascular manifestations. Pharmacological domain with polypharmacy concerns. This structure matters because it connects symptoms to systems to root causes in a way that mirrors how experienced clinicians actually think.

That structure is also what allows something elegant to emerge. The system does not just recommend what to add to a patient’s care. It surfaces de-prescribing opportunities that most workflows overlook entirely. Consider a patient taking gabapentin for chronic pain who is not getting meaningful relief. The system can trace the causal chain and surface that the underlying issue might be jaw clenching, that a dental appliance could address the root cause, and that reducing the gabapentin could lower the patient’s polypharmacy burden along with their hospitalization and mortality risk. That kind of insight gets buried in traditional systems where records are fragmented across silos. In Serelora it rises to the surface because the graph connects what those silos cannot.

The reports go beyond analysis to include actionable next steps with the proper guidelines and protocols for this type of patient. When the recommended action after a denial is an appeal, the system drafts the appeal letter ready to be reviewed and sent. When the next step is a referral, the system can prepare that too. The goal is to extend what the user can see and do, augmenting both clinical and financial understanding of the patient while generating the actual artifacts that move care forward.

Through all of this, every statement has provenance one click away. No unattributed assertions. No hallucinations slipping through. This is not magic. It is disciplined architecture and intelligent compilation of what the graph already knows.

The Architecture of Trust

The key design choice in Serelora is storing claims rather than facts. This distinction matters more than it might initially seem.

A fact is treated as final. A claim is an assertion with evidence, confidence, and the ability to be revised when better data arrives. This architecture enables longitudinal correction without corrupting the record. When new evidence comes in, whether a corrected lab result or a new clinical note or a physician override, the system updates the relevant claims and appends a new version of the graph. The record becomes living. It continuously reassesses risk and barriers and drivers as new information lands while preserving the full history of what was known and concluded at every point along the way.

This solves a problem that has plagued healthcare AI since its inception. When every field in every output traces back to its source evidence and the exact steps that produced it, errors become easier to catch. Denials become easier to appeal. Trust becomes something you can actually verify rather than something you hope for.

Where We Are Going Next

The foundation we are building today enables something powerful tomorrow.

The next evolution makes reports fully interactive. A clinician will be able to ask to see A1C trends over five years, and Serelora will generate a graph they can actually explore. Every data point will link back to its source document. The visualization becomes a window into the evidence, not just a picture of numbers.

More importantly, the same interface will let users correct the record when something is wrong. They will be able to highlight an area of the response and say this is incorrect. If the AI generated something that does not match reality, the user uploads a document showing the correct information, and the system revises the underlying claim. That correction document gets saved as part of the permanent audit trail, linked to the claim it corrected, so future queries can trace back not just to the original source but to the correction and the proof behind it.

Instead of one-off reports that drift out of date, every interaction improves the patient’s record. The system learns. The record evolves. Trust compounds.

The Longer Vision

Once exploration and correction are rock-solid, the chat becomes the place for operational work.

Users will be able to generate prior-auth packets, appeals, referrals, claim forms, FMLA paperwork, disability letters, and DME requests as reviewable artifacts. The system will compile every field from the Patient Knowledge Graph, attach provenance to every value, and present only the exceptions for human review.

This is where the philosophy becomes concrete. Human in the loop should feel like signing, not typing. The user sees what changed since last time. They see the handful of things that actually need attention. They approve or edit or route. No scrolling through pages of payer requirements. No hunting for evidence. No retyping the same demographics and history into yet another form.

Where direct APIs exist, submission will be clean and electronic. Where no API exists, controlled automation can work through portals as a pragmatic bridge, always with explicit permission and auditability and a human approval checkpoint.

The goal is not to remove people from the loop. It is to remove the busywork that keeps them from doing meaningful work.

The Shape of What Comes Next

The end state is something healthcare has never had before. One patient. One source of truth. And every stakeholder able to access what they need in the language they understand.

This is not a system built only for doctors. The Patient Knowledge Graph serves the patient directly, giving them visibility into their own health in terms they can actually understand. It serves the physician who needs clinical depth and diagnostic reasoning. It serves the broker who needs to match coverage to care needs. It serves the payer who needs to understand risk and utilization. It serves the TPA who needs to coordinate benefits across plans. It serves the caregiver who needs to know what medications to watch and what symptoms to report. It serves the clinical biller and coder who needs accurate documentation tied to proper codes.

Each of these users looks at the same patient. Each of them needs different information presented in different ways. And until now, none of them have had access to a comprehensive, connected record that captures the whole human being rather than fragmented pieces scattered across incompatible systems.

The insight that makes this possible is understanding what AI chatbots actually are at their core. They are magnificent translation tools. The underlying data does not change. The source of truth remains constant. But the system can translate that truth into the narrative and lexicon that each user needs. A physician gets clinical terminology and diagnostic frameworks. A patient gets plain language explanations and actionable guidance. A biller gets codes and documentation requirements. A broker gets coverage analysis and plan comparisons. The graph is the same. The intelligence is the same. The translation adapts.

This is how we finally solve the fragmentation my parents observed decades ago. Dentistry and medicine can connect because the graph holds both. Mental health and primary care can connect because the graph holds both. Specialties and generalists can connect because the graph holds both. The system sees what my parents always saw. Not just a head or a heart or an arm or a mouth. A whole human being.

A user asks for information and receives it. They click any point and see the originating evidence. They click any concept and see the definition and codes appropriate to their role. They click any recommendation and see the rationale and supporting citations. And when action is needed, the same interface produces the paperwork and routes it outward with the user staying in control.

One interface. One evidence spine. One place where anyone involved in a patient’s care can retrieve reality, verify it, and act on it.

Healthcare AI has overpromised instant everything for too long. We are taking a different approach. Build a foundation that earns trust through rigor and transparency, then layer capabilities deliberately. Not because we cannot move faster, but because healthcare has been burned too many times by systems that moved fast and broke things that mattered.

My mother was right all those years ago. She just wanted to ask the computer what she needed to know so she could focus on taking care of people. That future is finally here. And for everyone who touches a patient’s care, from the patient themselves to the clinician to the coordinator to the payer to the family member helping them navigate, everything is about to get so much better.

Luis Cisneros is CEO and Co-Founder of Serelora.