For a long time xHeal had a person on one side of the product and nothing on the other.

A client could connect Apple Health, upload a lab report, log a flare-up and build a real health history. Their clinician could not see any of it. Whatever the person gathered stayed in the person’s app, and the next appointment started from memory again.

That was always a half product. Not because the client side was wrong, but because the most valuable thing xHeal knows is the link between what a person records and what a practitioner concludes, and that link could not cross the appointment.

Provider Workspace is the other side of it.

On iPhone, the Log New Flare-Up form where a client records symptoms and chooses what to share with their provider
Provider Workspace on a laptop, showing a client's health records, documents and reported flare-ups
The analytics view of a clinic workspace, with revenue, appointments, utilisation, active clients, no-show rate and the share of upcoming visits that have shared health context
The client app and the Provider Workspace side by side, logged by the client and seen by the provider

One Product, Two Doors

The workspace is not a separate system that has to be integrated with anything. It is the practice-facing half of the same product, reading the same health context the client chose to share.

Six areas do the work:

  • Analytics for revenue, demand, capacity, utilisation and no-shows
  • Services so a practice can publish what it offers and take bookings
  • Appointments, followed from confirmation through completion
  • Clients, with the records, trends and notes each person has chosen to share
  • Documents for reports and files held against the client profile
  • Intent, keeping the client’s goals and priorities in view before the consultation

The last one matters more than it sounds. A lot of what makes a consultation useful is what the client walked in wanting, and it is usually the first thing lost between visits.

The Loop, in Three Steps

  1. The practice publishes its services, so a client can book the next appointment inside xHeal.
  2. The client decides what to share with that appointment. Not everything by default, and not nothing. A deliberate choice, per booking.
  3. The practice reviews the shared history and writes back: lab results, imaging reports, consultation summaries, care plans, referrals, medication updates, vitals and goals.

Step three is the one that is easy to skip and expensive to skip. A practice that can read a history but cannot return a result to the client has not saved anyone a phone call. The write-back is what turns a shared record into a working relationship.

A client logs a flare-up and chooses what to share. The practice reviews it, sends a report back, and both sides work from the same record. Demonstration data.

Why the Client Decides

The consent step is the part we expected to be a compliance checkbox. Working with practices changed our view of it.

Practitioners already know a client will not hand over everything. They have spent years negotiating that boundary with every portal and app that asked for blanket access. A product that assumes consent asks the practice to fight the patient, and they lose that argument in front of the person rather than in a policy document.

So the client chooses in advance, per appointment, and the practice works with what the client agreed to. It is visible in the product rather than buried in a policy: the analytics view reports how many upcoming visits have shared health context, and says plainly that private appointments stay private. The practice can see the shape of what it is allowed to see, which is what makes the boundary something it can explain to a client instead of something it has to defend.

Practices buy in two ways. Under Partner, the client subscribes and the practice earns a share of those subscriptions plus 70% of Marketplace service sales. Under Enterprise, the practice pays per seat, sets its own client price, and keeps the same Marketplace split. Full terms are on the Provider Workspace page.

xHeal is HIPAA, GDPR and SOC 2 compliant, and the workspace was built to that standard rather than retrofitted to it. That is what makes it something a clinic can deploy instead of something it trialled and abandoned.

For Practices

If you run a longevity, functional-health or preventive practice, and you keep asking clients to reconstruct their own history at every appointment, this is the part of xHeal built for you.

Book a demo of Provider Workspace and we will walk through it against the way your practice actually works. If it is simpler to email first, support@xheal.ai reaches the team.

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