Why rehabilitation data never comes back from a separate app
Published · 6 min read
When the exercise programme lives in one system and the medical record in another, what comes back to the record is a report. Not data. That distinction looks like a technicality on the day you sign the contract, and it decides what you can answer six months later.
What "integration" actually delivers
Most rehabilitation platforms connect to a hospital record. The connection is real, and it usually moves two things: the patient identifier on the way out, and a summary on the way back.
The summary is the problem. It arrives as a PDF attachment, a free text note, or a handful of fields in a custom section. A human can read it. A query cannot.
So the record now says that a patient completed a programme, and perhaps what their final pain score was. It does not hold which exercise they skipped in week three, or that their pain rose on the days they did the single leg work.
Three things you lose, in order of how much they cost
You lose the per-entry grain. A programme is not one event. The ACL programme we publish runs 42 days and contains 606 exercises and 101 check-ins. Flattened into a summary, those 707 data points become one row. Everything you might have asked about the middle of the programme is gone.
You lose the ability to ask across patients. The first question a head of department asks is never about one patient. It is whether the protocol works, whether one surgeon's patients recover differently, whether adherence falls off at a predictable point. Each of those is a query across many instances. A folder of PDFs cannot answer it, and neither can a summary field.
You lose the alignment with the encounter. In a separate system, the programme is attached to a patient. In the record, care is attached to an encounter: this admission, this operation, this discharge. When those do not line up, the rehabilitation outcome is not part of the episode of care. It sits beside it.
Why the category sells integration as the feature
Because for most vendors it is the only option available. A rehabilitation platform that is not a hospital system has to connect to one. The engineering is genuine and often good.
The result is still two systems with a pipe between them, and a pipe carries what it was built to carry. You can widen it. You cannot make it carry something the sending system never recorded in the first place.
What the other shape looks like
The alternative is that the rehabilitation instance is part of the same record, attached to the same encounter, written by the same clinician who signed the discharge.
Then a pain score is a field, not a line in an attachment. A missed session is a state, not an absence from a report. The outcome is in the medical record because it never left it.
That is the design of Ormeda's rehabilitation module, and the reason the platform is a hospital information system first rather than a rehabilitation product that grew sideways.
The trade-off nobody mentions
One system means one vendor. That is a real concentration of risk and you should weigh it honestly.
A best of breed stack lets you replace the weak part without touching the rest. A single system does not. What you get in return is that the data has one shape, one access model and one audit trail, and that nothing is lost in a hand off that never happens.
Which of those matters more depends on how much you intend to ask of the data later. If rehabilitation is a service you deliver and tick off, integration is enough. If it is something you intend to measure, report on and improve, the hand off is where that ambition dies.
See it rather than take our word for it
The programme we sell to patients is published in full: the ACL conservative programme, with its day structure, its dosage and its questionnaires visible before anyone pays for anything. It is the same structure a hospital composes inside the platform.
If you want to see it against your own ward round and your own discharge, request a demo. A clinician is on the call.
Programme content is written and assigned by the treating hospital or clinic. Ormeda provides the platform and the content library. Clinical decisions, including whether a programme suits a patient, are made by the clinician responsible for that patient.