MSK clinical decision support is software that helps a clinician make a decision about a patient with a musculoskeletal problem, by putting the relevant criteria, reasoning and evidence in front of them at the moment the decision is being made. It supports the clinician. It does not replace them.
In musculoskeletal care one decision dominates the others: does this patient need a specialist orthopaedic opinion now, or a clear plan that does not involve one? That question is asked hundreds of times a week in every service in the country, usually in a ten or fifteen minute appointment, and it determines almost everything that happens to the patient afterwards. Musculoskeletal means the joints, muscles, bones and soft tissues, and MSK is the standard NHS abbreviation.
This page explains the category rather than the product. If you want the product, it is described on what Orwyn does.
Clinician-facing MSK decision support is built for the people who see musculoskeletal patients first, which in the NHS today is rarely a hospital doctor.
That means musculoskeletal first contact practitioners working in general practice, advanced practice physiotherapists in community MSK and interface services, GPs, podiatrists, osteopaths, sports and exercise medicine doctors, and advanced practitioners running triage clinics. These are experienced clinicians, and in musculoskeletal assessment most of them are more expert than the doctor the patient would otherwise have seen. Our companion pages explain what a first contact practitioner is and how the MSK roles and bands fit together and how MSK triage works and where it happens.
These two things are constantly confused, and they are not variations of the same idea. They serve different users, solve different problems and carry different risks.
The patient answers questions themselves, usually on a phone, before or instead of an appointment. The output is advice for the patient. It depends on the patient describing their own problem accurately, and there is no examination behind it.
The clinician uses it while the patient is in front of them. It draws on the clinician's own history and examination findings, and the output is a suggestion for the clinician, who decides. It fits inside a normal appointment.
A tool that gives advice directly to patients is doing something categorically different from one that supports a registered clinician's decision. Orwyn is the second kind, and gives no advice directly to patients or the public.
Clinical decision support is an old category with two very different modern forms, and the same phrase is used for both.
A rules-based system applies criteria a named clinician has written and signed off. Every output traces back to a specific rule, and every rule traces back to the evidence it rests on, so a suggestion can always be explained and audited. A machine learning model derives its behaviour from data, which can be powerful, but its reasoning may not be inspectable and its behaviour can change when it is retrained.
Both are called decision support. Only one of them can be handed to a clinician, an information governance reviewer or a coroner with the reasoning shown. That is why Orwyn is a rules engine, and why it is not described as artificial intelligence.
The clinician does, always. Decision support offers a suggestion with its reasons attached; the clinician assesses the patient, weighs what the software has said against what is in front of them, and decides.
The design consequence of that is specific: the clinician has to be able to disagree, easily, without friction and without penalty, and the disagreement should be recorded rather than overruled. A tool that makes disagreement difficult has stopped being decision support and become a compliance system, and clinicians are right to reject it. Orwyn keeps disagreement, and treats it as one of the most useful things it collects, because a rule clinicians repeatedly disagree with is usually a rule that needs to change.
Software that sits inside a referral decision is close enough to patient harm that good intentions are not a safety argument. Four properties do most of the work.
Safety questions are asked first, and nothing is suggested until every one of them has been explicitly answered, with an unanswered question never read as a no. Every suggestion carries its reasoning and the evidence each part of it rests on. The clinician can disagree, and the disagreement is kept. And the behaviour of the software changes only when a named clinician changes a rule in writing, with a version and a date, so any decision can be traced to the exact rule that produced it.
Alongside those sit the formal requirements: clinical risk management under DCB0129, which requires a named Clinical Safety Officer, the deploying organisation's own assessment under DCB0160, the NHS Digital Technology Assessment Criteria, and UK medical device regulation. How Orwyn meets each of them, and where each one currently stands, is set out on standards, and the design principles behind it are on safety.
The value of clinician-facing MSK decision support is not that it reduces referrals. It is that it makes the referral decision right more often, in both directions.
A patient who needs a surgical opinion reaches one sooner. A patient who does not need one gets a clear plan on the day instead of a place in a queue that ends in discharge. NHS England's own guidance calls this referral optimisation, and describes formalising specialist advice, where an informal approach may already exist, as enabling safe and timely access to specialist care. We explain that in full on MSK referral optimisation.
Musculoskeletal orthopaedic approach to referral optimisation, NHS England, publication reference PR2103. Read it here.
DCB0129: Clinical Risk Management, its Application in the Manufacture of Health IT Systems, NHS England. Read it here.
Digital Technology Assessment Criteria (DTAC): guidance for buyers and suppliers, NHS England. Read it here.
MSK referral optimisation, our companion reference page. Read it here.
Written by Dr Arj Imbuldeniya, consultant orthopaedic knee and hip surgeon, and last reviewed on 20 August 2026. If anything here is out of date or wrong, please tell me and I will correct it. None of the organisations named or linked on this page has reviewed, approved or endorsed Orwyn.
Orwyn is being co-designed with the clinicians who will use it and with patients, and is designed for NHS Trusts and the services that commission musculoskeletal care.
Get in touch