Concept in development

Onyx Health Technologies

Onyx Carepath

Connected records and handoffs, so care teams spend less time rebuilding context.

A bright clinic room with an examination bed and a monitor.

The division

What Health Technologies does, and why the handoff matters.

Care is a series of handoffs. A person moves between people, teams, and settings, and the record is supposed to move with them. When it does not, each new team rebuilds the context from fragments: a note in one place, a request in another, a status that never left the first room. Fragmented care and operating records make that rebuild the start of every shift. Manual patient and service workflows hide the next step in someone's memory. Limited visibility across health operations means the people running the service see capacity and quality after the day has already turned.

Onyx Health Technologies develops connected digital experiences for care and health operations. It focuses on the handoffs, records, and service moments that determine whether care feels coordinated or fragmented. The division's work is digital systems that support accessible, connected, and efficient care. The work covers health platforms, care workflows, patient experience, and operational data. Health platforms are the shared place for the record. Care workflows are the path a team can repeat. Patient experience is the service moment a person meets. Operational data is how operators see the service they are running.

Onyx Carepath is a connected workflow concept for care teams that need clearer records, smoother handoffs, and better service visibility. It is Concept in development. It is about the handoffs, the moments where coordinated care holds together or falls apart. The concept connects records, workflows, and service moments so care teams spend less time reassembling context and more on the patient in front of them.

How the work is organised

From the record to the next handoff.

This is how care records and handoffs are organised in general, and it is the path Onyx Carepath is being designed around. Carepath is a concept in development.

  1. 01

    Open one record

    A team can act when the patient and service information is already in a form they can use. Onyx Carepath is the connected workflow concept being shaped for that record.

  2. 02

    Follow the handoff

    The useful test of a record is the moment it passes to another person, team, or setting. The concept is designed to support smoother handoffs, so context travels with the work.

  3. 03

    Leave a path someone else can walk

    Manual patient and service workflows keep the next step in a conversation. Care workflows are a path a team can repeat.

  4. 04

    Keep the service moment with the record

    The division focuses on the service moments that determine whether care feels coordinated or fragmented. Patient experience is how that focus shows up for the person receiving care.

  5. 05

    Show operators the service

    Operators need a view of service quality and capacity while the work is still under way. That clearer view is one of the outcomes, and part of how Carepath is designed.

Health Technologies

Bring the handoff that loses the record.

Talk to the Group about care records, workflows, or the view operators have of the service.

Who it serves

People who reassemble the context.

Onyx Health Technologies develops connected digital experiences for care and health operations. It focuses on the handoffs, records, and service moments that determine whether care feels coordinated or fragmented.

Care providers

The problem. Fragmented care and operating records. A provider starts the next conversation by searching for what the last team already knew.

How the division helps. Onyx Carepath is a concept in development for clearer records and smoother handoffs, so patient and service information is easier for care teams to use.

Health operators

The problem. Limited visibility across health operations. Quality and capacity are reconstructed after the service moment, from pieces held by different teams.

How the division helps. A clearer view of service quality and capacity is one of the division's core outcomes, and part of how Onyx Carepath is designed.

Patients and institutions

The problem. Manual patient and service workflows. The person receiving care, and the institution around them, meet a path that depends on who is on shift.

How the division helps. The concept connects records, workflows, and service moments so teams spend less time reassembling context. That is the aim of the concept.

Outcomes

What the concept is being designed to achieve.

These are the outcomes the division is working toward. They describe records, handoffs, and operating visibility. They are the aim of Onyx Carepath, a concept in development.

Information a team can use

Make patient and service information easier for care teams to use. That is the record Carepath is being designed so a team can open.

Smoother handoffs

Support smoother handoffs between people, teams, and care settings. The handoff is the moment the concept is about.

A view of the service

Give operators a clearer view of service quality and capacity. The view is part of the design, aimed at the people running the service.

Illustrative scenarios

The kinds of handoffs this concept is built for.

Each card is an illustrative scenario: a generic archetype, the problem, the approach, and the outcome we aim for. The cards describe records and handoffs. They do not report clinical results. Onyx Carepath is a concept in development.

Illustrative scenario

A care team

Problem. The record of a person is split across notes, requests, and settings. Each handoff begins with a search for context the previous team already had.

Our approach. Connect the record, the workflow, and the service moment, which is the shape of Onyx Carepath.

The outcome we aim for. Patient and service information that a care team can use, with less time spent reassembling context.

Illustrative scenario

A health operator

Problem. Service quality and capacity are visible only after the day is assembled from separate reports. The operator learns the shape of the service once it is already over.

Our approach. Treat operational data as part of the same concept as the care workflow, so the view of the service sits with the work. That is part of the design of Onyx Carepath.

The outcome we aim for. A clearer view of service quality and capacity for the people running the service. The outcome is the aim of the concept.

Illustrative scenario

An institution coordinating care

Problem. People, teams, and settings each keep their own record, and the handoff between them is a manual retelling. The institution cannot see one path.

Our approach. Design the handoff as a shared workflow. Onyx Carepath is the connected workflow concept being shaped for that path.

The outcome we aim for. Smoother handoffs between people, teams, and care settings, on a record the next team can open.

Care coordination

Onyx Carepath

Concept in development

A connected workflow concept for care teams that need clearer records, smoother handoffs, and better service visibility.

Onyx Carepath is about the handoffs - the moments where coordinated care either holds together or falls apart. The concept connects records, workflows, and service moments so care teams spend less time reassembling context and more on the patient in front of them.

Designed capabilities

  • Patient and service information teams can use
  • Smoother handoffs between people and settings
  • A clearer view of service quality and capacity
  • Designed for coordinated, not fragmented, care

Questions

Before you write to Health Technologies.

What does Onyx Health Technologies do?

Connected records and handoffs, so care teams spend less time rebuilding context. Onyx Health Technologies develops connected digital experiences for care and health operations. It focuses on the handoffs, records, and service moments that determine whether care feels coordinated or fragmented. The work covers health platforms, care workflows, patient experience, and operational data.

What is Onyx Carepath?

Onyx Carepath is Concept in development. A connected workflow concept for care teams that need clearer records, smoother handoffs, and better service visibility. It connects records, workflows, and service moments so care teams spend less time reassembling context and more on the patient in front of them. The capabilities being shaped are patient and service information teams can use, smoother handoffs between people and settings, a clearer view of service quality and capacity, and a design aimed at coordinated care.

Who is the work for?

The work is for three groups: care providers, health operators, and patients and institutions. Providers need a record they can use at the handoff. Operators need a view of service quality and capacity. Patients and institutions meet the service through those workflows.

What problems does the division address?

The division addresses three problems: fragmented care and operating records, manual patient and service workflows, and limited visibility across health operations. The record fails when context is rebuilt at every handoff. The workflow fails when the next step lives in memory. Visibility fails when operators see the service only after the day is over.

How should the illustrative scenarios be read?

They use generic archetypes, such as a care team, a health operator, or an institution coordinating care. Each card states a problem, an approach, and the outcome the concept aims for. They are illustrations of records and handoffs. They are not patient stories, and they do not report clinical results.

How do we start a conversation?

Use the contact form for Health Technologies, or write to support@onyxgroup.global. A conversation can cover a customer need, a partnership, a technology collaboration, or an investment opportunity connected to this division.

Work with Health Technologies

Bring us the operating problem.

Talk to the Group about care records, handoffs, service visibility, or a partnership connected to this division.