Reimbursement, training, service and utilisation decide the real cost of a clinical exoskeleton. A framework for modelling all four.
ExoSelect researchContinue reading
Editorial QA
Checked for sourced parameters, internal links and prohibited claims.
Quick answer. Reimbursement, training, service and utilisation decide the real cost of a clinical exoskeleton. A framework for modelling all four.
Clinical exoskeleton business cases rarely fail because the device cannot walk. They fail because the utilisation assumption was optimistic, the reimbursement pathway was unclear, or the service model was left out of the five-year model.
This analysis sets out the cost lines that belong in a clinical exoskeleton business case. It does not provide a price benchmark for any specific system; public list prices are rare and configuration dominates.
Purchase price includes the device, but often excludes installation, therapist training, software licences, spare batteries, transport cases and the first service interval. Ask for a five-year total cost of ownership schedule, not a single number.
For leased or treatment-programme models, the economics shift from capital to volume. Model the break-even number of sessions per month and the utilisation rate needed to reach it.
Reimbursement pathways differ by country and, in federal systems, by region. A device with a clear code in one market may be purchased as capital equipment in another and funded through research or philanthropy in a third. Confirm the pathway before the purchase order, not after.
Ask the maker for named sites that have successfully billed or funded the device in your jurisdiction. Treat a general statement about “reimbursement support” as a lead, not evidence.
A clinical exoskeleton is usually supervised. The relevant unit is not the device-hour but the therapist-hour. If a session requires two staff and 30 minutes of setup, the marginal cost per session is dominated by labour.
This is why self-balancing systems and therapist-controlled systems can have different business cases despite similar capital prices. The workflow, not the actuator count, drives throughput.
Model the eligible patient population conservatively. Include contraindications, screening time and the proportion of patients who discontinue. A device used by 40% of the eligible cohort at 60% of planned sessions is a different business case from the brochure scenario.
Then add the case-mix effect: a system that fits a broad neurological population may have higher utilisation than one designed for a narrow indication, even if its per-session assistance is lower.
Ask for mean time to repair, spare-parts lead time and the cost of a service contract after warranty. For a single-device department, one week of downtime can remove a meaningful share of annual capacity.
Battery replacement is a predictable cost. Confirm cycle life, replacement price and whether the device can operate on mains power during a service visit.
Build the case in five lines: annual sessions, revenue or grant per session, therapist labour, device ownership cost and service. Then stress-test utilisation down by 30%. If the case still works, the decision is robust. If it only works at brochure utilisation, it is a pilot, not a purchase.
Compare the shortlisted systems on the same assumptions using our comparison tool, and record every missing input as a question for the maker.
An exoskeleton analysis is only useful if it changes what a buyer does next. The purpose of a dossier is not to declare a winner in the abstract, but to make the next conversation more specific: which task, which users, which environment, which constraints and which evidence is still missing.
The first step is to translate the task into a written requirement. Describe the posture, load, repetition, duration, reach height, floor surface and clothing. Add the practical constraints that decide adoption: donning time, heat, tool clearance, cleaning and storage. A system that performs well in a demonstration but interferes with the actual workflow will not be worn after the pilot team leaves.
The second step is to separate the system from the deployment. A device can be well engineered and still fail because the service network is thin, the training is inadequate or the spare-parts lead time is measured in months. Ask for the service model in writing, including response time, replacement units and the cost of consumables.
Data quality should be scored explicitly. A dossier that publishes weight, runtime, user limits and certification scope is easier to pilot than one that leaves those values unknown. Missing values are not automatically disqualifying, but they are a cost: someone has to resolve them before a purchase order, and that work belongs in the project plan.
Use the product index to narrow the field by category, drive type, weight, runtime and region. Treat the filters as a way to structure the question, not as a substitute for reading the parameter states. A system that disappears from a weight band because its weight is not disclosed is telling you something about the dossier.
Place the shortlisted systems side by side in the comparison tool and focus on the rows where they diverge. Differences are useful; similarities are useful too. If two systems are identical on the parameters that matter, the decision may turn on service, fit or commercial terms rather than engineering.
Check the manufacturer profile for verification level, product line and company documentation. A maker with a clear primary source for each claim is easier to audit than one whose brochure is the only available reference. Where a claim matters to safety, ask for the declaration of conformity and the technical file summary.
Finally, write the brief. Include the task, environment, user profile, deployment volume, region and budget range. A good brief lets the research desk separate sourced values from open questions, so the next conversation starts with evidence rather than a demonstration.
Training is part of the system, not an afterthought. Ask who delivers the first session, how competency is assessed and what happens when a new operator joins the team. A device that requires a specialist to fit it every morning has a different operating cost from one that a trained supervisor can deploy independently.
Keep a decision log beside the shortlist. Record what was verified, what was assumed and who owns each open question. When the recommendation goes to a capital committee, the log is often more persuasive than another product demonstration because it shows exactly which risks have been retired.
Send the requirement when the shortlist is ready. The response should make the gaps visible, not hide them behind a polished recommendation. That is the standard this index is built to support.
Start with the intended use, the certification scope and the service model. Those three items decide whether a system can be deployed, not just demonstrated.
No. Published parameters support shortlisting, but fit, comfort, training quality and local service response require a structured evaluation with the intended users.
Missing values are recorded as Unknown or Not disclosed and are never inferred from a similar product. Each dossier shows the date of the last update and links to its primary sources.
Editorial note
This analysis is based on published specifications and named sources. No first-party physical evaluation was performed.
Reviewed by the ExoSelect editorial desk
Sources and notes
