Building Better Care Conversations: xHeal Begins Structured US Product Pilots

Interest in Doctor Ready and Health Gaps has led to an important next step for xHeal: structured product pilots with US physicians and participating xHeal users.

Together, we have begun evaluating how xHeal can help people organize their health context before appointments, recognize information that may be missing, and arrive ready for a more focused conversation with their care team. The goal is not to assume that a feature creates value because it sounds useful. The goal is to validate where it helps, where it creates friction, and what must improve.

Starting with two practical care problems

Preparing for an appointment often means reconstructing a health story from memory, patient portals, lab files, medication lists, wearable data, and notes kept in different places. Patients know how difficult that preparation can be. Physicians know which parts of the resulting context are useful and which parts create more noise.

The pilots bring those perspectives into the same feedback loop. We are beginning with two focused use cases:

• Doctor Ready: Can xHeal help a person turn their available health information into an organized starting point for an appointment?
• Health Gaps: Can xHeal make absent, incomplete, or outdated information easier to notice and discuss with a healthcare professional?

These are deliberately practical questions. Neither report is intended to make a diagnosis, decide what is medically relevant on a physician's behalf, or replace a professional review.

What we are evaluating with physicians and users

A useful report has to work for both sides of a care conversation. It should be understandable to the person preparing for the visit while remaining focused enough for a physician to review without sorting through unnecessary detail.

During the pilots, we are looking at questions such as:

• Can users gather and organize the context they intended to share?
• Is the report structure clear, scannable, and appropriately focused?
• Are missing inputs and limitations visible rather than hidden?
• Does the experience help users prepare better questions?
• Which details help a physician orient to the conversation, and which create noise?
• Where does the application add unnecessary work instead of reducing it?

Feedback from each use informs the next product iteration. We can refine the structure, language, prioritization, and workflow, then evaluate the changes again. That repeated loop is what makes the pilots structured rather than a collection of informal reactions.

What validation means at this stage

For these pilots, validation means testing whether a defined feature is understandable, usable, and valuable in the workflow it was designed to support. It also means learning where that workflow differs across people. Someone managing recurring symptoms, someone coordinating several specialists, and someone preparing for a routine visit may need very different levels of context.

We want xHeal to bring real value to many kinds of users, but that does not come from treating every user or appointment as the same. It comes from identifying specific needs, testing the application against them, and preserving the differences that matter.

This product validation is not a clinical trial and does not establish clinical effectiveness or a medical outcome. Those are different standards, and we will continue to describe that distinction clearly.

Partnering around one validated use case at a time

We look forward to partnering with hospitals, independent practices, and physicians around use cases that can be evaluated through the application. A partnership might begin with appointment preparation, organizing records before a referral, identifying missing context, or supporting clearer follow-up questions.

For each use case, we want to understand the real workflow first, define what useful support would look like, and validate it with the people involved before expanding it. This approach can reduce avoidable back-and-forth and help patients and care teams reach the useful part of a conversation sooner. It is not about rushing clinical judgment or removing necessary safeguards.

Building with the people who will use it

The most valuable outcome of these pilots is not simply confirmation that our first idea was right. It is evidence that helps us decide what to keep, what to change, and what not to build.

Physicians bring the perspective of real care workflows. Users bring the reality of preparing, remembering, and coordinating their own health context. By building with both, we can make Doctor Ready, Health Gaps, and future xHeal use cases more focused, more transparent, and more useful.

xHeal remains a health companion and awareness tool. It supports preparation and care-team collaboration, but it does not diagnose, treat, prescribe, or replace medical professionals.