Orwyn logoorwyn™
A reference page

Musculoskeletal (MSK) clinical decision support, explained.

The definition

What MSK clinical decision support is

MSK clinical decision support is software that helps a clinician make a decision about a patient with a musculoskeletal problem. It puts 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 matters more than the others. Does this patient need a specialist orthopaedic opinion now, or a clear plan that does not involve one? Clinicians face that question many times a week in every service, usually in a ten or fifteen minute appointment. The answer shapes almost everything that happens to the patient afterwards. Musculoskeletal means the joints, muscles, bones and soft tissues. MSK is the standard short form in the NHS (National Health Service).

This page explains the category rather than the product. If you want the product, it is described on what Orwyn does.

The user

Who it is for

Clinician-facing MSK decision support is built for the people who see musculoskeletal patients first. In the NHS today, that is rarely a hospital doctor.

That means musculoskeletal first contact practitioners in general practice, and advanced practice physiotherapists in community MSK and interface services (between general practice and hospital). It also means GPs (family doctors), podiatrists, osteopaths, sports and exercise medicine doctors, and advanced practitioners running triage clinics. These are experienced clinicians. 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 (job grades) fit together. They also explain how MSK triage works and where it happens.

The distinction that matters most

Clinician-facing decision support is not patient self-triage

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.

Patient self-triage

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.

Clinician-facing decision support

The clinician uses it while the patient is in front of them. It draws on the clinician's own history and examination findings. The output is a suggestion for the clinician, who decides. It fits inside a normal appointment.

Why the difference matters

A tool that gives advice directly to patients does a completely different job from one that supports a registered clinician's decision. Orwyn is the second kind, and gives no advice directly to patients or the public.

The other distinction

Rules a clinician wrote, or a model nobody can inspect

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. Every rule traces back to the evidence it rests on. So a suggestion can always be explained and audited. A machine learning model learns its behaviour from data, which can be powerful. But its reasoning may not be open to inspection, 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 (AI).

Responsibility

Who makes the final decision

The clinician does, always. Decision support offers a suggestion with its reasons attached. The clinician assesses the patient and weighs what the software has said against what is in front of them. Then the clinician decides.

That shapes the design. The clinician has to be able to disagree easily, without friction and without penalty. The disagreement should be recorded rather than overruled. A tool that makes disagreement difficult is no longer decision support. It has become a compliance system, and clinicians are right to reject it. Orwyn records its plan and the clinician’s decision, with the reason for any change. A disagreement is one of the most useful things to learn from. Records for real patients, the outcome coming back to the clinician and the link to the record system are planned. A rule clinicians repeatedly disagree with is usually a rule that needs to change.

Safety

What makes it safe enough to use at first contact

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.

The safety questions come first, and the clinician confirms them before anything else appears. Every suggestion carries its reasoning and the evidence each part of it rests on. The clinician can disagree, and each disagreement should be recorded. And the software's behaviour changes only when a named clinician changes a rule in writing, with a version and a date. So any suggestion can be traced to the exact rule that produced it.

Alongside those sit the formal requirements. Clinical risk management under DCB0129 (the NHS standard for makers of health software) requires a named clinical safety officer. Under DCB0160, the matching standard for organisations that use health software, each organisation makes its own assessment. There are also the NHS Digital Technology Assessment Criteria, and medical device regulation in the United Kingdom. Where Orwyn stands on each of them today is set out on our standards page. The design principles behind it are on our safety page.

What it changes

How decision support improves referral pathways

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. They do not wait in a queue that ends in discharge. NHS England's own guidance calls this referral optimisation. It says making specialist advice formal, where it may already happen informally, enables safe and timely access to specialist care. We explain that in full on MSK referral optimisation.

Sources

Where to read more

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.

If you are comparing products, see what an MSK triage tool should do and AI in MSK triage.

Read next

Surgeon-governed decision support for first contact MSK clinicians.

See the demoGet in touch

The demo uses draft rules awaiting final sign-off, and example patients only.

Decision support for clinicians only. The clinician assesses the patient and makes every decision. Orwyn is not a service for patients and gives no advice directly to patients or the public. This page is general information and is not clinical advice.