CCSD code 0135B: Thiocyanate level test billing guide

Key Takeaways

CCSD code 0135B is the code for a thiocyanate level test – a clinical biochemistry blood test, not a surgical or operative procedure.

The test measures thiocyanate in the blood. Clinics usually order it to watch for cyanide build-up in a patient on a prolonged sodium nitroprusside infusion, or to check tobacco-smoke exposure and sense-check a patient’s stated smoking status.

Because it is a lab test, a clean claim depends on tying it to an authorised consultation or investigation and naming the requesting clinician.

The exact schedule wording, unit value, and fee sit behind the CCSD login and are negotiated with each insurer.

What CCSD code 0135B actually is?

CCSD code 0135B is the CCSD Schedule code for a thiocyanate level test. In plain terms, it is a blood test from clinical biochemistry that measures how much thiocyanate is in a patient’s system. It is not a surgical procedure, an imaging study, or a consultation, and getting that clear at the outset saves you from billing it as if it were one.

The CCSD Schedule is the shared set of CCSD codes; the standard procedure and investigation codes that UK private medical insurers (Bupa, AXA Health, Aviva, Vitality and the rest) work from when they process specialist claims.

Code 0135B sits on the pathology side of that schedule. A CCSD code lookup on the current schedule, or a search in an insurer’s own CCSD code finder, returns the live narrative for the code.

Since that wording can be revised between editions, the description below tells you what the test is, while the precise schedule text and unit value should always be read from the current source. The full schedule search sits behind the CCSD login.

Why a clinic orders a thiocyanate test

Most thiocyanate requests come down to one of two questions.

The first is a safety question, and it usually shows up in acute or inpatient settings.

Sodium nitroprusside (an intravenous drug used to bring dangerously high blood pressure down fast) breaks down in the body and releases small amounts of cyanide. The body clears that cyanide by converting it into thiocyanate.

On a short infusion, that is a non-event. On a long one, or in a patient whose kidneys clear thiocyanate slowly, the level can climb, so the team tracks thiocyanate rather than chasing cyanide directly – cyanide readings are notoriously misleading in these patients.

The second question is about smoking.

Thiocyanate is a long-standing marker of tobacco-smoke exposure (it lingers for a week or two after someone smokes and rises with the number of cigarettes), so it is used to sense-check what a patient reports, whether that is ahead of a procedure or inside a cessation programme.

It is not a perfect signal: diet nudges it up (cruciferous vegetables such as cabbage and broccoli are a dietary source), and it won’t reliably catch the occasional cigarette, which is why it is often read alongside an exhaled carbon monoxide reading. Still, as an objective check against self-reported smoking, it earns its place.

Picture a consultant with a patient on a multi-day nitroprusside infusion in a private critical-care bed. Rather than wait for symptoms, they order serial thiocyanate levels to catch any accumulation early. Every one of those tests is a separate billable event, and every one has to trace back to the authorised episode of care, or the claim stalls.

The clinical reason for ordering the test is exactly what the insurer expects to see behind the code.

How a thiocyanate claim actually moves?

A lab-test claim travels a different road from a surgical one, and the handoffs are where money goes missing. Here is the path 0135B usually takes:

1. The request. A consultant, or a GP with private practising rights, requests the test as part of an authorised consultation or investigation. The request captures who ordered it and the clinical reason.
2. Sample and analysis. Blood is drawn and sent to the laboratory, which runs the assay and returns a result. In UK private care the analysis is frequently done by a dedicated pathology laboratory rather than the requesting practice itself.
3. Who bills – the fork people miss. Sometimes the performing lab invoices the insurer directly under the code. Other times the requesting practice bills, and the lab charges the practice. Settle which model you are in before the first claim, because two parties billing the same code for the same patient is a fast route to a rejection.
4. Submission. The claim goes to the insurer – in most cases through Healthcode, the electronic clearing service the major PMIs use – carrying the CCSD code, the patient’s membership details, and the authorisation reference.
5. Adjudication and remittance. The insurer checks eligibility, authorisation, and the fee against its own schedule, then pays, queries, or declines. A queried claim is not a dead claim, but it is a delayed one.

Notice what is not on that list: there is no operating-theatre paperwork, no anaesthetic record, no assistant to account for. A pathology claim lives or dies on the request, the authorisation, and the result – keep those three tidy and most of the work is done.

Fee and rules by insurer

There is no single fixed price for 0135B. Reimbursement is negotiated between each insurer and provider representatives, and it moves year to year, so the only reliable number is the one on the insurer’s current fee finder.

Each of the major PMIs works from the CCSD Schedule and publishes its own lookup – start here, and confirm the fee for this specific test before you invoice:

Other insurers – WPA, Healix, Allianz Care, Cigna – use the CCSD Schedule too, but their fees and any unbundling rules come from their own provider portals. When in doubt, ask the insurer directly rather than assuming a figure carries across.

Where these claims go wrong

• Billing it like surgery. Reaching for a bilateral or assistant-surgeon modifier because that is how operative codes work. This is a laboratory analyte – those modifiers do not belong on it, and appending one invites a rejection. If any modifier is genuinely relevant, it will be on the schedule entry for the code. Don’t carry one over from surgical billing out of habit.
• A test with no thread back to an authorised episode. A lab result floating free of the consultation or investigation the insurer authorised. The claim needs to point clearly at that episode of care.
• Thin clinical justification. The record doesn’t say why the test was clinically needed. For a monitoring test especially, the reason for ordering it is the thing an insurer looks for.
• Duplicate billing. The practice and the lab both invoicing the insurer for the same test – the fork from the walkthrough above, left unresolved.
• Stale fee assumptions. Invoicing last year’s amount, or a figure a colleague quoted from a different insurer. Fees are negotiated and they move, so read the current one.
• Missing the window. Every insurer sets a deadline for submission after the date of service. Miss it and even a flawless claim is declined.

Before you submit: A quick checklist

Run through this before the claim leaves your desk. It takes a minute and catches most of what gets 0135B queried:

• The code matches the test actually performed – a thiocyanate level – checked against the current CCSD Schedule.
• The test links to an authorised consultation or investigation, and you have the authorisation reference to hand.
• The requesting clinician is named, and the clinical reason for the test is in the record.
• You know who is billing the insurer – your practice or the lab – and only one of you is.
• No surgical modifiers have crept on out of habit.
• The patient’s cover and eligibility are current.
• The fee is the one on the insurer’s current fee finder, not last year’s.
• You are inside the insurer’s submission window.

Look back at that checklist and you will see the pattern: almost nothing on it is about the code. It is about the trail around the code – the authorisation, the requesting clinician, the clinical note, the current fee.

Keeping that trail in one place is where practice management software like Pabau earns its keep. Because the clinical record and the claim live in the same system, the note that justifies a test sits right next to the invoice that bills it, so claims tend to go out complete the first time, and chasing a queried one is far less of a scramble.

Keep every claim and its paperwork in one place

Pabau brings the clinical note, the authorisation, and the claim into one system for UK private practices – so investigations like this go out with the record that justifies them attached. Fewer rejections, less chasing.

Book a demo

Continue your research

Need the wider Bupa picture? Bupa CCSD codes and billing guide walks through the Bupa procedure code framework for UK private practices.

Tightening up the business side? Private practice management covers the operational systems, billing workflows, and insurer relationships behind a well-run independent clinic.

Want fewer rejected claims across the board? Claims management software from Pabau handles CCSD billing end to end, from recording the test against the patient record to tracking the claim with the insurer.

Frequently asked questions