✦ Insights

Telemedicine After the Hype

The urgency has faded and the grand claims with it. What remains is a set of tools that suit particular jobs, and a list of operational reasons why deployments stall.

Health TechAltisly Strategy Team27 March 20264 min read
All posts

What the pandemic years taught us, and what they did not

For a while, telemedicine was presented as the thing that would remake healthcare. Then the urgency faded, patients went back to clinics, and some of the grand claims quietly went with them. What is left is less exciting and more useful: a set of tools that work well for specific jobs and badly for others.

This is a view from the operations and technology side. We are not offering clinical guidance, and nothing here is a statement about what treatment works. The question is simply what makes remote care function as a service, and why so many deployments stall.

Where it genuinely fits

Remote consultations suit situations where the main thing needed is conversation, review or a decision, rather than a physical examination. Follow up appointments, medication reviews, test result discussions and routine check ins are common examples. Triage, where someone decides how urgently a person needs to be seen in person, is another.

The gains are practical. A patient avoids a long journey, a day off work and a waiting room. A clinic can see more people without more floor space. A specialist in one city can advise a generalist in another. None of that requires a dramatic claim about transforming medicine. It requires a reliable call and a sensible workflow.

Where it does not

Plenty of care needs hands, instruments or a physical presence. Remote consultation cannot replace those, and it is irresponsible to pretend otherwise. Where it is used as a front door, a dependable route to in person care has to sit behind it. A telemedicine service that cannot hand a patient on to a real appointment is only a more convenient way of being stuck.

There is also a quieter problem. Remote care assumes the patient has a device, a decent connection, a private space and some comfort with the technology. In many places, including parts of Nigeria and Ghana, those assumptions fail often enough to matter. Data costs, power cuts and shared phones shape who can actually use the service. Designing for the patient who has a basic phone and a weak signal is not an edge case. It may be the main case.

Why deployments stall

When telemedicine projects disappoint, the cause is rarely the video call. It is usually everything around it.

  • No link to the patient record. If the clinician cannot see history during the consultation, and notes do not flow back into the record afterwards, the call becomes an isolated event and the work doubles.
  • Messy scheduling. Remote and in person slots compete for the same clinicians. Without good scheduling, one starves the other or both overbook.
  • Unclear payment. If nobody has decided how a remote consultation is billed, charged and reconciled, finance will treat it as an exception, and exceptions get ignored.
  • Weak follow through. Prescriptions, referrals and lab requests that begin in a call need somewhere to go. If the patient has to repeat everything at the front desk, the benefit disappears.

Notice that none of these is a video problem. They are integration and process problems, which is why hospital management software matters more here than the conferencing tool does.

Privacy and trust are part of the product

A consultation is a conversation about health. Where it happens, how it is recorded, and who can access the notes are not afterthoughts. In Nigeria, the Nigeria Data Protection Act 2023 treats health data as sensitive personal data, and similar duties apply under data protection laws in the UK and Ghana. That means clear consent, sensible access controls and a defensible position on what is stored and for how long.

Patients also judge a service by small signals: whether the clinician seems to know who they are, whether the call drops, whether they can reach someone afterwards. Trust is earned in those details.

What a sensible approach looks like

If you run a clinic or a hospital group and you are considering remote services, start narrow. Pick one or two use cases where a physical examination is not the point, such as follow up reviews. Run them inside your existing patient record and scheduling system rather than beside it. Decide the billing rules before the first call, not after.

Plan the failure paths explicitly. What happens when the connection drops halfway? When a patient needs to be seen in person after all? When a prescription cannot be sent? A good service is measured less by the best call than by how it handles the bad one.

Finally, measure what matters operationally: how many consultations are completed, how often they end in an in person referral, how much staff time is saved or added. Be honest if the answer is that it adds work. That is useful information.

A quieter kind of success

The most successful telemedicine we can imagine does not feel like a separate technology at all. It is one more way for a patient to reach a clinic, using the same record, the same schedule and the same billing as everything else. When it stops being a project and becomes a normal option, the hype has done its job and can be forgotten.

TelemedicineHealthcareOperations
A

Altisly Strategy Team

Writing about systems architecture, operations software and what it takes to keep a build coherent, at Altisly.

Have a problem worth solving?

Tell us what is not working, what you are trying to build, or where you want to go next.

What happens next
01You describe the operation.
02We reply within one business day.
03If there is a fit, we tell you what the next step looks like.