The missing layer in corporate healthcare

Imagine an employee whose annual health check finds something worth discussing with a doctor. The employer has already assembled a meaningful set of benefits: the screening itself, a teleconsultation option, an insurer network and perhaps a wellness programme. On paper, several routes to help are available.

But the employee still has to work out which route applies. They have to interpret the report, decide how quickly to act, find the right appointment, repeat the relevant history and remember what should happen afterwards. The services exist. The journey between them does not.

This is one of the quiet contradictions in corporate healthcare. A programme can offer more access than ever and still feel fragmented to the person using it. The problem is not necessarily that any one provider has failed. It is that each provider can complete its own task while coordination remains nobody’s task.

Fragmentation is what the employee experiences when every service works, but the journey does not.

The problem is not the number of benefits

Corporate health programmes are often described as a list: annual screening, doctor consultations, insurance cover, mental-health support, pharmacy discounts and specialist networks. Each addition can be useful. But usefulness does not automatically turn a list into a system.

A directory tells an employee what is available. A connected care journey tells them what is relevant now. Those are different jobs. The first is about access; the second is about making sense of access in the context of one person’s health, preferences and prior care.

The distinction becomes visible at the handoffs. Does the doctor see the finding that prompted the consultation? Does the employee leave with an understandable plan? If a medicine, repeat test or specialist opinion is suggested, does that action appear anywhere beyond the consultation note? If nothing happens, who notices?

The employee becomes the integration layer

When services are not designed to work together, the person has to connect them manually. They download a report from one portal, describe it on a call in another app, search an insurer network elsewhere and keep the next step in their head. People with time, confidence and familiarity with healthcare may manage. Others postpone, choose an unsuitable route or simply stop.

It is tempting to call this an engagement problem. That diagnosis is convenient because it places the responsibility on the employee: send another reminder, run another campaign, increase awareness. But an employee can be fully aware of a benefit and still be unsure whether it is the right thing to use. More communication cannot compensate for an unclear pathway.

What the missing layer actually does

The World Health Organization’s framework for integrated, people-centred care argues for services coordinated around people’s needs across the continuum of care. Applied to an employer programme, that does not mean one company must own every clinic, insurer or diagnostic centre. It means someone must own the logic that connects them.

That operating layer has a small number of responsibilities. It preserves relevant context. It identifies the next sensible action without pretending every result is urgent. It routes the person to a service that can actually help. It records what was agreed. And it returns at the right time to see whether the loop closed.

Digital infrastructure can make this easier. The Ayushman Bharat Digital Mission, for example, is designed around consent-based personal health records and a citizen’s ability to share information across the health ecosystem. That is an important foundation. Yet interoperable information is only one part of the job. A record can move successfully while the person remains uncertain about what to do.

The missing layer is not another benefit. It is the accountability that makes existing benefits work together.

This is not an argument for a healthcare super-app

Connecting care does not require forcing every service into one interface or pretending one platform can replace the health system. Employees will continue to use hospitals, laboratories, insurers, family doctors and specialists. They may prefer WhatsApp for one interaction and an app for another. The continuity layer should reduce the cost of moving between those settings, not trap people inside a new one.

Nor should coordination become surveillance. An employer may need to know whether the programme is being delivered, whether broad needs are being met and where a pathway repeatedly breaks. It does not need an individual’s report, diagnosis or private conversation. Personal care and organisational learning have to be separated by design.

What we are building

Oxology is being built as this continuity layer for corporate healthcare. A health check becomes the beginning of a longitudinal, employee-controlled record. Results are explained in plain language. The next action is made visible. A physician remains responsible wherever clinical judgment is required. The plan then stays present long enough for follow-through to happen.

AI has a supporting role in that system: organising information, translating complexity and remembering agreed actions. It should make coordination easier for people and clinicians. It should not diagnose independently, manufacture certainty or become an invisible substitute for medical accountability.

We are early, and the operating details will keep changing as we learn from employees, HR teams, insurers, brokers and clinicians. The standard we are working toward is straightforward: an employee should not have to become the project manager of their own corporate healthcare.