Nerida Health Take Part

Platform Overview

How It Works

One patient. One thread. Seven moments that hand off to each other.

Follow a single course of care through Nerida. At each moment, see what the patient, the doctor and the practice team each have in front of them, and how the moment feeds the next.

  • Medicine and dentistry
  • Every role, its own view
  • Sample situations, not real patients

The journey

A sample course of care. The situations are illustrative; the handoffs are how the platform is built to work.

  1. Connect

    A care relationship starts when a patient asks to connect with a doctor, or accepts a doctor’s invitation. Doctors never send connection requests; the patient always chooses.

    • The patient

      Accepts the invitation into their own account, or sends a request. Sees which doctor they are connected to.

    • The doctor

      Invites a patient, or accepts a request. The relationship is what makes the record reachable.

    • The practice team

      Can help send invitations when the doctor grants that permission. Sees no clinical detail.

    Capability: Coordinated Care
  2. Prepare

    Before the visit, the patient sets out their history at home: background, medications, specialty-specific questions, documents and measurements. It is written once and updated afterwards, not repeated.

    • The patient

      Answers questions that fit the specialty, in their own language and time. Adds documents. Sees what changed since last time.

    • The doctor

      Opens a structured history with changes since the last visit highlighted, before the patient arrives.

    • The practice team

      Sees that a history is complete or outstanding, never its content.

    Capability: Preparation & Records
  3. Agree a time

    Either side proposes a time. The other confirms, declines or counters. Nothing is booked until both agree, a doctor who declines gives a reason, and rescheduling reopens the agreement.

    • The patient

      Proposes or counters in their own timezone. Sees the reason if a doctor declines.

    • The doctor

      Sees proposals against the day. Confirms, counters or declines with a reason.

    • The practice team

      Manages the schedule and proposals on the doctor’s behalf, with permission, and marks arrivals.

    Capability: Coordinated Care
  4. The visit

    The confirmed appointment becomes a consultation. Records, the prepared history, documents, plans and safety information sit in one working view. Private working notes stay separate from what is shared.

    • The patient

      Sees the shared record and anything the doctor chooses to share, never the doctor’s private notes.

    • The doctor

      Works from one view. Keeps private notes private; sharing is an explicit, visible choice.

    • The practice team

      Sees the day’s list and who has arrived. The consultation itself is out of reach.

    Capability: Clinical Workspace
  5. The plan

    The visit ends with next steps written down: a plan, tasks with owners, a referral or records request where needed, and a treatment plan the patient can review and accept or decline.

    • The patient

      Sees what happens next and why. Reviews a presented treatment plan and accepts or declines it.

    • The doctor

      Sets the plan, its check-ins and reminders. Starts referrals and requests that keep their thread.

    • The practice team

      Owns the operational tasks the plan creates, such as scheduling the next visit.

    Capability: Follow-Up
  6. Between visits

    Check-ins happen when the plan asks for them. Reminders inform rather than nag. What the patient records reaches the right doctor, in context, and a carer can help through their own account.

    • The patient

      Records what the plan asks for, when it asks. Sees who has access to their care and can end it.

    • The doctor

      Receives what comes back, connected to the plan it belongs to, not in a separate inbox.

    • The practice team

      Sends confirmations and reminders operationally, without opening clinical records.

    Capability: Follow-Up
  7. What we learn

    Because care was recorded in a structured way, reporting needs no export. Every report states who was counted, what may be missing and where the information came from. Research goes further, inside defined projects.

    • The patient

      Is never identifiable in a small group: very small counts are hidden before anyone sees them.

    • The doctor

      Reports over their own patients and practice patterns, with a path back to the source of every number.

    • The practice team

      Sees practice reporting about how the day runs, with no clinical content.

    Capability: Reports & Insights

Sample situations only. No real patient data is on the platform until clinical, legal and security review is complete.

Why the Handoffs Matter

The gaps between tools are where care gets lost

On Nerida

  • The history written before the visit is the history the doctor opens.
  • The agreed appointment is the one the consultation runs from.
  • The plan made in the room is the plan the check-ins follow.
  • The records kept during care are the records the reports count.

Across separate tools

  • Intake forms are retyped into a records system.
  • A booking tool does not know what happened in the room.
  • Reminders live in a separate app from the plan they belong to.
  • Reports start with an export and a spreadsheet.

Walk through your own day with us

Design partners bring their real workflows. We follow them through the platform together and change what does not fit.

Walkthroughs use sample information only.