Post-discharge follow-up for hospitals

Post-surgery recovery, followed up on WhatsApp

Hitaishi checks in with your patients every day after they go home, on the app they already use. Your care team sees who needs attention, based on red-flag rules your own clinicians set.

Product demo with simulated patients A patient reports severe pain on WhatsApp (left). Seconds later the care team dashboard flags her for review (right).
  • No app for patients
  • Red-flag rules set by your clinicians
  • No changes to your HIS
  • Data hosted in India
An elderly Indian man recovering at home sits in an armchair, smiling at a phone with his adult daughter, a walking stick beside him
The gap after discharge

After discharge, recovery happens out of sight

The surgery went well and the patient goes home. The next six weeks decide how the recovery goes, yet most of what happens at home never reaches the people who operated.

  • Families are unsure what is normal

    They worry and call, or wait and hope. Small concerns are easy to miss.

  • Exercises and follow-ups slip

    Physio is hard to keep up at home, and review visits get postponed.

  • Care teams hear late, if at all

    Manual follow-up calls don’t scale. Problems surface at the next OPD visit, or in emergency.

Product tour

See it in two minutes: remote patient follow-up, end to end

Eight steps from discharge to outcome report, shown in the real product with simulated patients.

Step 1

Enrol at discharge, with consent

A nurse or coordinator enrols the patient in about a minute, or uploads a CSV or Excel list, and records how consent was given. Consent is recorded per purpose: care messages (required) and anonymised benchmarking (optional). A family member can be added with their own consent. The WhatsApp welcome goes out straight away.

Step 2

A daily check-in on WhatsApp

Each morning the patient taps through a few short questions: pain, wound, fever, calf pain and exercises, with exercise videos. Nothing to install, under a minute a day.

Product demo with simulated patients. WhatsApp chat on a phone: the Hitaishi day 7 check-in asks about pain, the wound and fever, and the patient taps her answers.
Step 3

Family can follow along, and answer

A son or daughter can get their own WhatsApp messages: an evening update, a note when the care team is alerted, and the daily check-in. If the patient needs help, they answer for them, and the record shows who answered, for example “by Karthik Prasad (son)”. Each family member gives their own consent and can stop any time.

Step 4

Red flag, on the dashboard in seconds

Every answer is checked against the red-flag rules your clinicians set. A match moves the patient to the top of the dashboard and notifies the staff responsible for that unit on WhatsApp and SMS. Family members who opted in get a short note that the care team has been informed.

Step 5

If nobody responds, it escalates

A red flag that nobody acknowledges moves up: to the coordinator after 15 minutes, then to the treating surgeon or duty doctor after 30, on WhatsApp and SMS. A patient who misses three check-ins in a row raises a red alert to call them or their family. Your clinicians set the times per pathway and unit, and acknowledging stops the escalation.

Step 6

The nurse reviews and calls, and it is all audited

The nurse opens the alert, calls the patient, adds a note and marks it reviewed. Each step goes on the patient’s timeline and into the audit log.

Step 7

Physio and follow-up booked from the chat

In week one the patient chooses hospital or home physiotherapy. On day 12 they pick a review slot. Every booking shows up for your team to confirm and track, and is linked to the message that prompted it.

Product demo with simulated patients. WhatsApp chat on a phone: the patient chooses physiotherapy at the hospital and Hitaishi confirms the booking with session days and times.
Step 8

Outcome scores, analytics and a pilot report

Validated outcome scores (KOOS JR for knees, HOOS JR for hips) at baseline, week 6, month 3 and month 12. Activity generated by Hitaishi: physio packages, follow-up visits, review and referral links. Plus attendance, alerts and time to acknowledge, completion and pain by week, by unit and surgeon.

All screens are from the Hitaishi product running in demo mode with simulated patients. No real patient data is shown.

Two sides, one system

WhatsApp for patients and families. A dashboard for your care team.

One conversation, one record. What the patient says on WhatsApp is what your team sees, in the same minute.

Product demo with simulated patients. WhatsApp chat on a phone: Hitaishi welcomes the patient on behalf of the hospital’s joint replacement team and asks for consent; the patient taps Yes, start.

Patients and families

  • Nothing to install. WhatsApp, on the phone they already have.
  • Asked first. Consent on WhatsApp before any check-in. STOP ends it at any time.
  • Tap to answer. Short questions, exercise videos and booking in the chat.
  • Never left guessing. Always told to call the hospital or go to emergency if it feels urgent.
  • Family in the loop. Caregivers give their own consent, get an evening update and red-flag notices, and can answer check-ins for the patient.
Product demo with simulated patients. The recovery dashboard: patients sorted by who needs attention first, with recovery day, pain trend, exercise adherence, follow-up and status, and an alerts and activity feed.

Your care team

  • Who needs attention first. Patients sorted by risk, with day of recovery, pain trend and adherence.
  • Nothing left waiting. Unacknowledged red flags escalate to the coordinator, then the surgeon or duty doctor.
  • The whole story. Answers (and who gave them), wound photos, pain and outcome-score charts, family contacts and the full chat in one record.
  • Right people, right unit. Role-based access for nurses, coordinators, surgeons and admins.
  • Works from any browser. Staff sign in with their own account, with optional or required two-factor sign-in. No installation at the hospital.
Features

Everything your post-discharge follow-up needs

Built for orthopaedic teams first, around how nurses, physiotherapists and surgeons already work.

Product demo with simulated patients. The red-flag rules editor: each rule, such as severe pain, fever or calf pain, has a threshold, a severity and the staff to alert, editable by the hospital’s surgeons.

Your surgeons set the red flags

Thresholds, severity and who gets alerted are set by your clinicians in the rules editor, not by us. Rules can look at a single answer, rising pain over several days, missed check-ins or keywords. Every change is saved as a new version and recorded in the audit log, and the escalation times are set in the same place.

Hitaishi applies the rules and alerts your team. It does not diagnose or give medical advice.

Daily check-ins

Pain, wound photo, fever, calf pain and exercises on a 6-week schedule, with tap-to-reply buttons that are easy for older patients.

Alerts that escalate

Red flags reach the dashboard within seconds and the staff your clinicians chose, on WhatsApp and SMS. If nobody acknowledges, they move up to the coordinator, then the surgeon or duty doctor.

Physio and follow-up booking

Patients book physiotherapy and their review visit in the chat. Your front desk sees each booking and marks it attended or missed, and each one is linked to the message that prompted it.

Enrol one by one or in bulk

Add a patient at discharge in about a minute, or upload a CSV or Excel list. Consent is required either way.

Family and caregivers

Each family member has their own consent and chooses an evening update, red-flag notices, or answering check-ins for the patient. Answers are recorded with who gave them.

Validated outcome scores

KOOS JR (knee) and HOOS JR (hip) on WhatsApp at baseline, week 6, month 3 and month 12, with a trend on each patient’s record and averages by unit and surgeon.

Analytics and a pilot report

Attendance, alerts and time to acknowledge, completion, pain by week and satisfaction. “Activity generated by Hitaishi” counts the bookings and review and referral links that started from a message, and a printable report compares the pilot with your baseline.

English today, Indian languages next

Messages are in English today. ಕನ್ನಡ and हिन्दी are in progress, translated by people and reviewed by clinicians before use.

Staff access under control

Access by role and unit, two-factor sign-in that admins can require by role, and staff invites, role changes and deactivation from the dashboard. All of it audited.

Outcomes and results

See how patients recover, and what the programme generated

Patient-reported outcome scores, attributable activity and a pilot report you can take to your management, all from the same WhatsApp conversations.

Product demo with simulated patients. An outcome score card on a knee replacement patient’s record: KOOS JR at baseline, week 6 and month 3, with the change from baseline and a trend line.

Validated outcome scores, on WhatsApp

Hitaishi sends KOOS JR to knee patients and HOOS JR to hip patients at baseline, week 6, month 3 and month 12, one question per message, using the published English wording. Each patient’s record shows the trend and the change from baseline, and analytics compares units and surgeons on the same patients over time.

Outcome questionnaires are answered by the patient only, never by family on their behalf.

Product demo with simulated patients and illustrative baseline figures. The printable pilot results report compares a baseline agreed before the pilot with the pilot period: follow-up attendance and booking, physio uptake, completion, response rate, time to acknowledge an alert, satisfaction, outcome score change and readmissions entered by staff.

A pilot report against your own baseline

Before the pilot, you agree the baseline numbers with us. At the end, the printable report sets them beside the pilot period: follow-up attendance, physio uptake, completion, time to acknowledge alerts, satisfaction and outcome-score change. Readmissions come from your HIS and are entered by your staff.

“Activity generated by Hitaishi” counts what started from a Hitaishi message: physio packages and follow-up visits booked in the chat, and review and referral links opened, with an estimated value if you set your prices.

The figures in these screens are from the demo with simulated patients. They are not results from a hospital.

Product demo with simulated patients. The Activity generated by Hitaishi panel: physio packages and follow-up visits booked via the WhatsApp chat, review links and referral links opened, and an estimated attributable revenue based on prices the hospital sets.
Product demo with simulated patients Every booking and link is traced to the WhatsApp message that prompted it.
Pathways

Starting with a knee replacement recovery program

Joint replacement first, where the weeks at home matter most. The pathway engine is built to extend to other surgeries.

First pathway

Knee replacement

Total and partial knee replacement, 6 weeks.

First pathway

Hip replacement

Total hip replacement, 6 weeks.

Planned

Spine surgery

Post-operative follow-up for spine procedures.

Planned

Cardiac surgery

Recovery check-ins after cardiac procedures.

Planned

Oncology

Follow-up support between treatment visits.

Privacy and security

Patient data handled with care, and kept in India

Recovery check-ins are sensitive conversations. Hitaishi is designed to respect that from the very first message.

  • Data hosted in India

    Patient data is stored and processed on cloud infrastructure in India.

  • Consent first, per purpose

    No enrolment without recorded consent, then a second opt-in on WhatsApp. Care messages and anonymised benchmarking are consented to, and can be withdrawn, separately. Family members give their own consent. Anyone can stop at any time.

  • Audit log

    Every view of patient data and every action on the dashboard is recorded: who, what and when, including escalations and rule changes.

  • Names and phone numbers encrypted

    Patient and family names and phone numbers are encrypted field by field in the database (AES-256-GCM), on top of encrypted storage.

  • Two-factor sign-in and staff control

    Authenticator-app 2FA, which admins can require by role. Admins invite staff, set roles and units, and deactivate accounts. Password resets use single-use links.

  • Designed around the DPDP Act

    Clear purpose, minimal data, defined retention, and patient data export and erasure for admins.

  • No changes to your HIS

    Runs alongside your hospital information system. No IT project to start.

Product demo with simulated patients. The audit log: a time-stamped list of staff logins, record views, alert reviews and rule changes, with who did each one.
The audit log, as admins see it. Product demo with simulated patients.

A follow-up tool, not a doctor. Hitaishi does not diagnose or give medical advice. It asks the questions your clinicians choose, applies the rules they set, and brings the answers to your care team. Every clinical decision stays with your clinicians.

60days

Start with a 60‑day pilot at one unit

Pick one unit, such as your joint replacement service. We set Hitaishi up with your clinicians, train your team, and review the results with you at the end. No long contract, and no IT project to start.

  1. Before go-liveSet up the pathway with your clinicians

    Agree the check-in schedule, red-flag rules, escalation times and who is alerted for your unit, and the baseline numbers to compare against.

  2. Week 1Train the team and start enrolling

    Short training for nurses and coordinators. New patients are enrolled at discharge.

  3. Day 30Mid-pilot review

    Look at engagement and alerts with your team, and adjust the rules if needed.

  4. Day 60Review and decide

    Go through the pilot results report together: your baseline beside the pilot, week-6 outcome scores and the activity generated. Then decide on next steps.

FAQ

Questions hospitals ask about post-discharge follow-up

Do patients need to install an app?

No. Patients use WhatsApp, which most families already have on their phones. There is nothing to download and no account to create.

Does Hitaishi diagnose patients or give medical advice?

No. Hitaishi is a communication and follow-up tool. It asks the questions your clinicians choose, flags answers that match the rules they set, and brings those to your care team. Diagnosis, advice and every clinical decision stay with your clinicians.

Who decides what counts as a red flag?

Your clinicians. Surgeons can edit the thresholds, severity, who is alerted and the escalation times for each rule in the dashboard, for example a pain score above a set value, pain rising over several days, fever or a wound concern. Each change is saved as a new version and recorded in the audit log.

What happens if nobody responds to an alert?

It escalates. If a red flag is not acknowledged, it goes to the coordinator after 15 minutes, then to the treating surgeon and the unit's duty doctor after 30 minutes, on WhatsApp and SMS. Your clinicians can change these times per pathway and unit. If a patient misses three check-ins in a row, a red alert asks your team to call the patient or their family. Every escalation is shown on the dashboard and recorded in the audit log.

Do we need to change our hospital information system?

No. Hitaishi runs alongside your existing systems. Your team enrols patients from the Hitaishi dashboard at discharge, one by one or by uploading a CSV or Excel list, so no HIS integration or IT changes are needed to get started.

How does our care team log in?

Each staff member signs in to the Hitaishi web dashboard from any browser with their own account, using the Hospital login button at the top of this page. Access depends on their role and unit, and every view of patient data is recorded in the audit log.

Where is patient data stored?

On cloud infrastructure hosted in India. Patient and family names and phone numbers are also encrypted field by field in the database. Access to the dashboard is role-based, staff can be required to use two-factor sign-in, and every view and action is recorded in an audit log.

How does Hitaishi handle consent and India's DPDP Act?

Hitaishi is designed around India's Digital Personal Data Protection Act, 2023. A patient cannot be enrolled without recorded consent. Consent is recorded per purpose: care messages are required, and anonymised benchmarking is optional and can be withdrawn on its own. Patients are told on WhatsApp what will be collected and why, confirm before check-ins begin, and can stop at any time by typing STOP. Family members give their own consent.

Which languages are supported?

English today. Kannada and Hindi are in progress: every message is being translated by people and reviewed by clinicians before it is used, with no machine translation of clinical text. Until a language is ready, patients receive English.

Can family members follow the patient's recovery?

Yes. Your team can add one or more family members, each with their own recorded consent. Each one can get a short evening update, a message when the care team is alerted or when the patient stops replying, and the daily check-in, which they can answer on the patient's behalf. The record shows who answered. A family member can stop their own messages at any time by typing STOP. Outcome questionnaires are answered by the patient only.

Does Hitaishi measure clinical outcomes?

It collects validated patient-reported outcome scores: KOOS JR for knee replacement and HOOS JR for hip replacement, at baseline, week 6, month 3 and month 12, on WhatsApp. Each patient's record shows the trend and change from baseline, and analytics compares units and surgeons. There is also a week-6 check on walking, overall progress and satisfaction. The questionnaires are from the Hospital for Special Surgery and are used in their published English wording.

How do we see whether the pilot worked?

Before the pilot we agree baseline numbers with you, such as follow-up attendance and physio uptake. Hitaishi then produces a printable pilot results report that sets the baseline beside the pilot period, including outcome-score change and time to acknowledge alerts. It also shows the activity generated by Hitaishi: physio packages and follow-up visits booked from the chat, and review and referral links opened, each traced to the message that prompted it. Readmissions are entered by your staff from your HIS.

Are the screenshots and videos on this page real patients?

No. Every screenshot and video on this page is from the Hitaishi product running in demo mode with simulated patients. No real patient data is shown.

Which surgeries does Hitaishi support?

Knee and hip replacement are the first pathways. Spine, cardiac and oncology pathways are planned next.

How do we get started?

With a 60-day pilot at one unit. Write to us to book a demo, and we will plan the pilot with your clinical and operations leads.

See Hitaishi with your team

A 30-minute walkthrough of the patient experience on WhatsApp and the care team dashboard, and a conversation about a pilot at your hospital.

Book a demo hello@myhitaishi.in