Where Software Actually Touches Patient Care
"Health tech" sounds like a single industry, but it's really software touching an actual patient somewhere along the way — a record, a device, a diagnosis, or an appointment. This track treats it as one connected system rather than four separate topics.
Say “health tech” and most people picture one thing: a hospital running software instead of paper charts. That is a sliver of it. Health tech is any software that touches an actual patient somewhere along the way — a record, a device, a diagnosis, or an appointment — and once you see it that way, three things you already use every month turn out to belong to the same category.
Health tech is software touching an actual patient
It is not an industry the way “retail” or “banking” is. It is a description that applies the moment code touches something a real person's body, treatment, or medical history depends on. A hospital's billing system barely counts — a bug there loses money. The same hospital's medication-dosing screen absolutely counts — a bug there can hurt someone.
That distinction, does this software sit between a decision and a patient, is the thread the rest of this track pulls on. It is why a scheduling app and a diagnosis-assist model get discussed in the same breath here, even though they look nothing alike.
Run the test on a few real examples and the category gets less abstract. A hospital payroll system, a shift-swap tool for nurses, the cafeteria's ordering app — none of that is health tech, no matter how much of it runs inside a hospital's walls. A medication-dosing screen, a diagnosis-assist model, an appointment booking that syncs straight into your chart — all three are, no matter how far outside the hospital's walls they run.
Sits between a decision and a patient
A medication-dosing screen.
A diagnosis-assist model.
An online booking that syncs to your chart.
Doesn't, even inside a hospital
A hospital's payroll system.
The cafeteria ordering app.
An internal shift-swap tool for staff.
Three places it already lives in your life
Booked a doctor's appointment online in the last year? That booking flowed into the same electronic record system the doctor pulls up during your visit — you already touched health tech before you sat in the waiting room.
Checked your step count or resting heart rate on a phone or watch? Wearables that track something health-adjacent are now an everyday purchase, and some of those readings end up in front of an actual clinician — shown at an appointment, or fed into a monitoring programme.
Had a video call with a doctor instead of driving to a clinic? Telehealth visits went from a rounding error before 2020 to a routine option most insurers now cover without a second thought. All three are health tech. None of them look like a hospital.
Requested a prescription refill through a pharmacy app, or checked whether a claim was approved through your insurer's portal instead of calling and waiting on hold? Same category, just quieter. Insurance and pharmacy software now handle a meaningful share of what used to require a phone call, and both eventually write into systems that feed back into the record your doctor sees.
Where the boundary gets blurry
Not every case resolves as cleanly as a payroll system versus a dosing screen. A general meditation app, a step counter, a sleep tracker — by default, none of these are health tech. They are wellness software, and a bug in one is an inconvenience, not a harm, exactly like the shopping-app comparison in the next chapter.
Then a cardiologist enrols the same person in a remote-monitoring programme built on that same watch's heart-rate feature, and overnight, the identical code is now feeding a clinical decision. Nothing about the software changed. What changed is what sits downstream of it.
Why this track treats it as one connected system
A patient's data gets created somewhere (a record), has to move somewhere else (interoperability), sometimes gets analysed by something (AI), reaches the patient through something (an app or a video call), and has to stay protected the entire time (security and regulation). Six parts, one pipeline — each part of this track is a stage that data actually passes through, not an unrelated topic bolted on because it sounded relevant.
- 1A record gets created
Part 2 — the EHR and what actually lives inside one.
- 2It has to move between systems
Part 2 — why two hospitals' systems don't just talk to each other.
- 3Sometimes something analyses it
Part 4 — what a diagnosis-assist model actually outputs.
- 4It reaches the patient through something
Part 5 — an app, a portal, or a video call, and who gets left out.
- 5It has to stay protected the entire way
Part 6 — security, and how new health tech actually gets approved.
Skip a stage and the others stop making sense. Bias in a diagnosis model (Part 4) is only dangerous because that model's output reaches a real patient through an app or a doctor's screen (Part 5), built on a record (Part 2) that was supposed to be protected the whole way through (Part 6). Treat health tech as one system and every later chapter has somewhere to attach to.
Key takeaways
- Health tech is not an industry — it is any software that sits between a decision and an actual patient, from a scheduling form to a diagnosis-assist model.
- You have already used it this year: an online booking, a wearable reading, or a telehealth call all count, and none of them look like a hospital.
- The same feature can be ordinary consumer software for most users and health tech for the one whose doctor is reading its output — the test is about what's downstream, not the codebase itself.
- The six parts of this track follow one real pipeline — data created, moved, analysed, delivered, and protected — not six unrelated topics.
- A problem in any one stage, like bias in an AI model, only matters because of how it reaches the patient through every other stage.
Before you move on
Quick check
Answer these to unlock the next chapter: 3 of 4 to pass. You can retake it anytime.
Make a free account to read on
Every chapter is free — an account lets your course progress follow you from your laptop to your phone. No payment, no trial.