CCSD code 0081H: Selenium level test billing guide

Key Takeaways

CCSD code 0081H identifies a Selenium level test in the Biochemistry category of the CCSD Schedule.

It’s a pathology code, not a surgical or clinical procedure code. A Selenium test involves a blood specimen and a lab report, not an operation, so there’s no anaesthetic charge, no assistant-surgeon fee, and no theatre time attached to it.

Bupa, AXA Health, Aviva, Vitality Health, and WPA all recognise CCSD codes for pathology claims, with submission running mainly through Healthcode or the insurer’s own portal. Fees aren’t fixed: each insurer sets its own tariff, and the CCSD Schedule itself doesn’t set a price.

Practice management software like Pabau integrates natively with Healthcode, which helps practices attach the correct CCSD code, the ordering clinician’s detail, and the specimen date to a Selenium test claim before it’s submitted.

CCSD code 0081H is the code UK private medical insurers use to bill a Selenium level test. It’s a blood test that measures how much selenium, a trace mineral, is circulating in a patient’s blood, and sits in the Biochemistry category of the CCSD Schedule, alongside the other single-analyte blood tests insurers process every day.

This guide covers what 0081H actually pays for, how a Selenium test moves from a clinician’s request through to a paid claim, the insurer and pre-authorisation quirks that are specific to pathology billing, and a before-you-submit checklist for keeping a Selenium claim out of the query pile.

If you’re new to running a private practice in the UK, pathology billing is one of the areas where the rules genuinely differ from surgical or consultation billing, so it’s worth getting right from the first invoice.

What CCSD code 0081H covers

0081H identifies a Selenium level test on the CCSD Schedule, which is the number a lab or provider puts on an invoice line to tell an insurer exactly what was checked.

Selenium is a trace mineral the body needs in tiny amounts. It supports thyroid hormone metabolism and forms part of the antioxidant enzymes that protect cells from oxidative damage.

Clinicians request a Selenium level most often when they suspect a deficiency, such as in patients on long-term parenteral or enteral feeding, those with malabsorption conditions such as Crohn’s disease or coeliac disease, or those on heavily restrictive diets, and, less commonly, to investigate suspected overexposure from high-dose supplementation.

Unlike an electrolyte panel, a Selenium level is typically requested as a standalone test rather than bundled into a routine group of results, though a clinician may order it alongside other trace-element or micronutrient tests depending on the clinical picture.

As a pathology test, 0081H sits in the CCSD Schedule’s Biochemistry category, alongside other single-analyte blood chemistry codes such as potassium (0048C) and thallium (0132B).

Two companion codes, 0081T and 0081U, sit in the same Selenium test family; the exact distinction between them, whether that’s a different specimen type, a repeat test, or a different billing context, is confirmed in the licensed CCSD Schedule, so check your own CCSD access or Healthcode portal for the precise scope of each rather than assuming it from the code number alone.

A note on the code itself: CCSD codes pair a numeric family with a trailing letter, and public sources disagree on what any individual suffix is supposed to denote. The Schedule’s full narrative sits behind a registered login, so this guide sticks to what can be confirmed: 0081H identifies a Selenium level test, without asserting what the letter on its own is supposed to mean.

What CCSD is, and why UK private billing runs on it

CCSD stands for Clinical Coding and Schedule Development. It’s both the name of the schedule and the group that governs it. Representatives from Bupa, AXA Health, Aviva, and Vitality Health, alongside several private hospital groups, oversee what codes exist and what they cover, while Grant Thornton UK LLP administers the schedule day to day.

For clinicians moving from the NHS into private practice, this is one of the first practical differences to learn. There’s no equivalent governing body on the NHS side, because NHS activity isn’t billed code-by-code to a payer the way private care is.

The Schedule splits into a Procedural Schedule and a Diagnostic Schedule, covering everything from surgical procedures to consultations to lab-based diagnostic tests like 0081H. Crucially, the CCSD Group doesn’t set fees. Bupa, AXA Health, Aviva, and every other insurer that recognises the Schedule sets its own reimbursement rate for each code, and a code existing on the Schedule is no guarantee that a specific insurer will pay for it under a specific policy.

Treat any fee figure you see quoted online as indicative at best, and confirm the number with the insurer directly.

How CCSD differs from NHS coding

The NHS doesn’t use CCSD at all. NHS procedure activity is classified using OPCS-4, officially the OPCS Classification of Interventions and Procedures, maintained by NHS England, which absorbed NHS Digital’s classification functions when the two organisations merged in February 2023. Diagnoses use ICD-10 alongside it.

Private billing runs on CCSD, so a clinician working across both settings is, in effect, working in two coding languages: one for what the NHS records for activity and outcomes data, and a different one entirely for what gets invoiced to a private insurer.

How a Selenium test actually gets billed to insurers

Here’s the sequence, from the clinician’s request to the insurer’s remittance:

1. The clinician requests the test. A GP, dietitian, or consultant orders a Selenium level, usually to investigate a suspected deficiency — unexplained fatigue, hair or skin changes, or a known malabsorption condition. Occasionally, to check for overexposure in a patient on high-dose supplements.
2. A blood sample is taken. A single venous blood draw is all that’s needed. Trace-element testing is more particular about the collection tube than a routine chemistry panel — many labs specify a trace-element-free or “royal blue-top” tube, because the rubber stoppers on standard tubes can leach trace metals and skew the result.
3. The sample is sent to the lab. Selenium analysis typically runs through a specialist biochemistry or trace-element laboratory rather than the practice’s in-house point-of-care testing.
4. The lab analyses the sample and issues a pathology report. The report states the Selenium level against the lab’s reference range.
5. The lab or provider codes and bills the claim through Healthcode. 0081H goes out referencing the ordering clinician’s provider number and the specimen date.
6. The insurer adjudicates the claim, and the practice reconciles the payment against the pathology report.

The second friction point sits earlier, at the referral itself. Selenium testing has become a fixture of wellness and longevity-style health screens, and insurers are increasingly alert to that.

A claim for 0081H that’s clearly tied to a documented clinical indication moves through in the same way as any other routine pathology test. A claim where the referral letter reads more like a general wellness check, with no diagnosis or symptom driving it, is far more likely to be queried or declined outright as not medically necessary, regardless of whether the code itself is correct.

Take a practical case: a private GP orders a Selenium level for a patient with unexplained fatigue and a restrictive diet following bariatric surgery. The lab bills 0081H, referencing the GP’s provider number and the specimen date. Because the referral letter states the bariatric history and the specific symptom prompting the test, the claim clears without a query.

Had the same test been ordered as part of a general “nutrient panel” with no stated clinical reason, it’s a claim insurers are far more likely to hold pending clarification.

Documentation requirements for pathology claims

Three things are worth having on record before you bill, not after a query letter shows up.

• The clinical indication. Why the Selenium level was requested needs to trace back to the patient’s notes, even if it’s only a line.
• The ordering clinician’s detail and the specimen collection date. The GP or consultant who requested the test, their provider number, and the date the sample was taken should match what’s on the claim and the lab report. A mismatch here is one of the most common reasons a pathology claim bounces.
• The lab report itself. Keep the pathology report on file against the patient record, not just the invoice line, as it’s the document that actually shows what was tested and when.

Before you submit a 0081H claim

Turn that documentation habit into a broader pre-submit check, and most of the queries a Selenium claim attracts never get the chance to happen. Run through this before the claim goes out, not after a rejection lands:

• Correct code for what actually ran. Confirm 0081H is the right code for a standalone Selenium level, rather than one of its companion codes (0081T, 0081U), which may apply to a different specimen type or billing scenario.
• Clinical indication documented, and distinguishable from wellness screening. A line in the notes that ties the test to a diagnosis, symptom, or monitoring plan, not just “nutrient check.”
• Ordering clinician’s provider number current. Checked against what’s on file, not what was there at the last recognition renewal.
• Pre-authorisation confirmed where the insurer asks for it. Don’t assume a single blood test is automatically folded into a wider authorisation the way a routine electrolyte panel often is.
• Specimen collection date and tube type logged. Matching what’s on the lab report, so a query about the sample doesn’t turn into a query about the whole claim.
• Documentation retained under the practice’s normal retention policy. No separate Selenium-specific rule to invent here.

Which insurers recognise CCSD pathology codes

Bupa, AXA Health, Aviva, Vitality Health, and WPA all recognise CCSD codes, including pathology codes like 0081H, and process the majority of these claims through Healthcode’s clearing service. Healix recognises and processes CCSD-coded claims too, though it works as a healthcare trust and claims administrator rather than a traditional insurer.

Reimbursement rates and pre-authorisation requirements still vary by payer and by policy, so confirm both before you bill rather than assuming last quarter’s answer still holds. For Bupa specifically, the Bupa CCSD codes guide covers how to use its code search portal to confirm a code before an appointment.

The Selenium test family: 0081T and 0081U

0081H isn’t the only code that covers Selenium testing. Two companion codes, 0081T and 0081U, sit in the same Selenium test family on the CCSD Schedule. What separates them, whether that’s a different specimen type, a repeat or confirmatory test, or a different billing pathway, is confirmed in the licensed Schedule rather than something you can work out from the code itself.

If your lab or biller returns one of these companion codes instead of 0081H, don’t treat it as an error before checking. Confirm the exact scope of each code against your practice’s own CCSD access, your Healthcode portal, or the insurer’s code lookup, rather than assuming it carries over from a different context.

Common billing mistakes with pathology claims like 0081H

• Wrong or mismatched code. Billing 0081H when the lab actually ran a test that falls under one of its companion codes (0081T, 0081U), or the reverse, is one of the most frequent code-level errors on Selenium claims.
• Missing or assumed pre-authorisation. Assuming a Selenium test is automatically folded into a wider authorisation, without confirming it with the insurer, is a common reason claims stall, particularly where the referral looks more like screening than a diagnostic work-up.
• Specimen or lab documentation gaps. A missing specimen collection date, an unlogged tube type, or a pathology report that isn’t filed against the patient record all show up at audit even when the original invoice was correct.
• Unit or quantity errors. Billing more than one unit for a single blood draw, or duplicating the line when a repeat draw was actually a retest rather than a second charge, both attract queries.
• Outdated code or fee reference. Billing software that hasn’t been updated against the current CCSD Schedule can carry a superseded description or fee reference, which triggers a query even when the clinical work was correct.
• Thin documentation trail. Skipping the clinical indication or ordering clinician detail covered above still shows up regularly in insurer audits, even when the invoice itself was accurate.

How practice management software like Pabau supports CCSD pathology billing

Practices that manage CCSD billing manually, across spreadsheets and separate insurer portals, carry compounding administrative risk. Every manual step is a chance for a mismatched provider number, a missing specimen date, or a claim raised under the wrong code in the Selenium family.

Practice management software like Pabau helps by keeping the clinical record and the billing record in one system, rather than splitting them across a separate spreadsheet for codes. Pabau also integrates natively with Healthcode, so a Selenium test claim, the CCSD code, the ordering clinician’s provider number, and the specimen date, can be submitted, validated, and tracked without re-keying it into a separate portal.

Practices can hold CCSD codes like 0081H inside a saved investigation template, so a Selenium test gets coded the same way every time a claim goes out, instead of re-typed from memory on each invoice.

Keep pathology claims moving

Pabau supports UK private practices with a CCSD code library, native Healthcode claim submission, and structured documentation that ties the clinical indication, provider number, and specimen detail to every pathology claim. See how it works for your practice.

Book a demo

Conclusion

CCSD code 0081H is straightforward once the premise is right. It’s how UK private insurers bill for a Selenium level test, a blood test, not a procedure, with a lab report behind it rather than an operative note. Most of the claim problems that come up with it aren’t clinical at all. They’re a mismatched provider number, a missing clinical indication that would separate it from wellness screening, or a specimen that didn’t meet the lab’s own collection requirements.

The bigger job is building a pathology billing process that still holds up as the practice takes on more of these tests: one where the ordering clinician’s detail and the specimen date don’t depend on one person remembering the rule, and where a stalled claim gets caught before it turns into a three-month-old unpaid invoice.

Pabau’s claims management software helps UK private practices keep pathology claims like this one moving, from code validation through to Healthcode submission. To see how it handles a Selenium test claim end to end, book a demo.

Continue your research

Need another single-analyte pathology code walked through end to end? 0048C covers billing and insurer recognition for the potassium level test.

Billing a different trace-element test? 0132B walks through the thallium level test on the same Diagnostic Schedule.

Want the Bupa-specific view of CCSD codes? Bupa CCSD codes guide covers Bupa’s code search portal and billing rules.

Frequently asked questions