HCPCS Code M1005: TB screening not performed / results not interpreted

Key takeaways

HCPCS code M1005 is a CMS quality data code, not a payable service code. Its full descriptor is “Tb screening not performed or results not interpreted, reason not given.”

M1005 belongs to MIPS quality measure 176, tuberculosis screening before a first course of biologic or immune response modifier therapy. It is not a HEDIS code and not a general preventive screening code.

The code only applies to a patient starting a biologic or immune response modifier for the first time. Latent TB can reactivate once that therapy suppresses the immune system.

Report M1003 when screening was done and the results were interpreted within the prior twelve months. Report M1004 for a documented medical reason, and M1005 when no reason is given.

M1005 pays nothing and records performance not met, which pulls down your score on measure 176. Practice management software like Pabau helps your team capture the interpreted result at the point of care, so the right code goes out.

HCPCS code M1005 reports that tuberculosis screening was not performed before a patient’s first course of biologic therapy, and that no reason was documented. It covers a second situation too. The screening may have happened while nobody ever interpreted or recorded the result.

The full CMS descriptor is Tb screening not performed or results not interpreted, reason not given.

That second half of the descriptor gets dropped often, and it changes what the code means. An ordered test with no interpretation in the chart still lands on M1005. So does a test that was never ordered at all.

M1005 is a quality data code, or QDC. It reports performance on quality measure 176 in the Merit-based Incentive Payment System, known as MIPS.

The measure’s full name is Tuberculosis Screening Prior to First Course of Biologic and/or Immune Response Modifier Therapy. CMS maintains M1005 in the HCPCS Level II M-code range, next to M1003 and M1004.

This is not a general preventive screening code, and no HEDIS measure uses it. It applies only when a patient is starting a biologic or an immune response modifier for the first time. That trigger decides whether the code belongs on the claim at all.

M1005 code details at a glance

The table below covers the administrative attributes of HCPCS code M1005. Verify active status against the latest CMS HCPCS annual release files. Check the measure itself against the current-year specification, which CMS publishes through its quality measures resources and the Quality Payment Program resource library.

Why measure 176 screens for TB before a biologic

Biologics and immune response modifiers suppress the immune response that keeps a latent TB infection dormant. Once that suppression starts, a dormant infection can reactivate. Research has documented a higher incidence of TB after therapy that blocks tumor necrosis factor alpha. That is why the labels on those drugs carry a reactivation warning.

Measure 176 turns that warning into a reportable step. If a clinician newly prescribes one of these drugs, the record should show TB testing in the preceding twelve months. Most of that work sits with rheumatology, dermatology, and gastroenterology, where TNF inhibitors are routine.

Measure guidance is deliberately broad on who gets tested. Every patient being considered for a biologic or immune response modifier should be screened, including patients who previously received the BCG vaccination. A prior BCG shot is not a reason to skip the test, and it is not a documented exception under M1004.

Which patients fall into the measure 176 denominator

You only report M1003, M1004, or M1005 for a patient the measure actually counts. Three conditions have to line up: age, an eligible encounter, and a first-time biologic prescription. Miss one and the patient is outside the denominator, so no QDC is due.

A patient who has been on a TNF inhibitor for three years is not a measure 176 case. Neither is a patient who gets a TB test at an annual physical with no biologic in sight. The prescription is what opens the denominator.

M1003, M1004, and M1005: Which code to report

Picking the wrong code in this range is the most common measure 176 reporting error. Each code maps to one performance outcome, and the scoring engine treats them very differently. The table below carries the full CMS descriptors, not the shortened versions that circulate in billing notes.

M1004 is narrower than it looks. A patient refusal is not one of the two examples in its descriptor. Neither is a scheduling problem, a lab backlog, or a patient who simply never came back for the test.

So M1005 is the code you report when the chart is silent. It is also the code when the only documented reason is one the measure does not accept. Read the current-year specification before you treat any other note as an exception. The chart below puts the denominator gate and the code choice on one path.

What the chart has to show before you report M1003

Measure 176 asks for two entries in the chart, the test and its interpretation. A lab order alone does not satisfy it. Before a coder reports M1003 instead of M1005, the record should carry each of the items below.

• The test and its date. A tuberculin skin test or an interferon gamma release assay, dated within the twelve months before the first dose of therapy.
• The interpreted result. A recorded reading of positive or negative, with the interpreting clinician identified. An unread result is exactly what M1005 describes.
• The therapy start date. The date of the first biologic or immune response modifier dose, so the twelve-month window can be checked against it.
• Evidence this is first-time therapy. A medication history showing no earlier course of the same class of drug.
• Any medical reason, in the chart. If screening was skipped, the note has to state a reason the measure recognizes. Otherwise the case reports as M1005.
• Follow-up on a positive result. A positive screen is not a measure failure. Document the result, the treatment decision, and the plan before therapy starts.

Structured documentation keeps these fields in one place. A free-text note buried in a scanned PDF is technically documentation, but no coder will find it in time.

How to report HCPCS code M1005 on a claim

Reporting the code correctly starts with the submission mechanics. The rules below apply to Medicare claims-based reporting of measure 176. Registry submission follows the same clinical logic through a different pipe.

• Attach the QDC to an eligible encounter. M1005 is never a standalone service. It rides on a claim that already carries a billable encounter code from the measure’s denominator list.
• Report a nominal charge. Submit the QDC line at $0.00. If your system rejects a zero charge, use $0.01, which is the long-standing CMS workaround.
• Expect the line to deny. QDC lines commonly come back with claim adjustment code CO 246 and remark code N620. Together those say the code was valid for reporting and is not payable.
• Report only one code per patient, per period. M1003, M1004, and M1005 are mutually exclusive for the same eligible patient in the same performance period.
• Confirm your collection type. Measure 176 is reported as a MIPS clinical quality measure through a qualified registry, or through a qualified clinical data registry known as a QCDR. Medicare Part B claims reporting is also an option where it is still available to you.
• Watch the case minimum. A measure needs enough eligible cases to score, and the threshold is set each performance year. Verify it before you rely on measure 176 in your quality category.
• Send a complete claim. A QDC on an incomplete claim delays the whole thing. Work your clean claim submission checklist first, then append the quality code.

What M1005 pays, and what it costs you

HCPCS code M1005 pays nothing. Quality data codes carry no relative value units and no payment amount on the CMS Physician Fee Schedule. All three codes in the range behave the same way.

The money shows up one step later. Your performance rate on measure 176 feeds the MIPS quality category. The final MIPS score then sets a positive, neutral, or negative adjustment on future Medicare payments. So M1005 is a scoring event rather than an accounts receivable event.

Because the line is non-payable, it should never reach a patient statement as a balance. If M1005 shows up on a patient ledger, fix the posting rule that put it there.

ICD-10 codes that appear on a claim with M1005

Measure 176 is not defined by diagnosis, so there is no official ICD-10 crosswalk for M1005. The diagnosis on the claim is whatever condition the biologic is being prescribed for. These are the codes that turn up most often on those encounters.

One code that does not belong here is Z11.1, encounter for screening for respiratory tuberculosis. It describes a preventive screening visit, which is a different scenario from measure 176. Pairing it with M1005 signals a screening encounter that the measure never asked for.

Accurate diagnosis pairing keeps the claim consistent with the note behind it. Confirm every code against the current fiscal year tabular list before you submit, using the CMS ICD-10-CM code files.

Five mistakes that turn a screened patient into an M1005

Most M1005 lines land on patients who were screened. The care happened, and the chart failed to record it in the way the measure asks for. These five patterns account for the bulk of them.

• The result was never interpreted. The lab value sits in the chart with no reading attached. The descriptor covers this case, so it reports as M1005 even though the test happened.
• The test predates the window. A TB test from eighteen months ago does not count. The measure wants the test and the interpretation inside the twelve months before the first dose.
• A refusal was coded as M1004. Patient refusal is not one of the medical reasons the descriptor names. Coding it as an exception misstates the case.
• The reason lives outside the chart. An outside pulmonology letter or a scanned PDF that was never abstracted leaves the coder no reason to cite.
• The QDC was dropped for paying zero. Some billers strip $0.00 lines to keep claims clean. That removes the measure data and leaves the case unreported.

Reviewing these patterns belongs in the same routine as your denial review. Both look for a repeatable process defect, then close it before the next reporting cycle.

Quality programs that use HCPCS code M1005

M1005 belongs to one measure, and that measure sits inside the Medicare quality programs listed below. Knowing which one applies to you tells you where the code actually lands.

• Traditional MIPS, quality category. Measure 176 is a process measure that eligible clinicians may select for the quality performance category. Your performance rate on it contributes to the quality score, which contributes to the final MIPS score.
• MIPS Value Pathways. Some MVPs include measure 176 in their quality measure set, including pathways built for dermatological care. Check the current measure list for the MVP you have registered for.
• Specialty measure sets. Rheumatology, dermatology, and gastroenterology sets have carried this measure, because those specialties prescribe most first-time biologics. Confirm inclusion in the current performance year specification.
• Value-based arrangements built on MIPS scoring. Some payer contracts and alternative payment models, known as APMs, read your MIPS quality performance directly. A high M1005 rate then follows you into that arrangement.

M1005 is not a HEDIS code. The Healthcare Effectiveness Data and Information Set, known as HEDIS, holds no latent TB screening measure that uses the M1003 to M1005 range. That set belongs to the National Committee for Quality Assurance, not to CMS. If a payer asks you for HEDIS TB screening data, ask which measure they mean.

How Pabau keeps measure 176 out of the M1005 column

The M1005 problem is a timing problem. The prescription, the test, and the interpretation happen at three separate moments, and the patient record is the only place they can meet. Practice management software like Pabau closes that loop at each step.

• A rule that fires on the prescription, not the visit. When a first-time biologic is prescribed, the record should immediately ask for a TB result dated inside the last twelve months. That is the moment the measure starts running.
• A structured field for the interpretation. A required positive or negative reading, with the interpreting clinician and date, is the difference between M1003 and M1005. Free text cannot carry that reliably.
• A reason field with the accepted options. Offering the two medical reasons the descriptor names, and nothing else, stops a refusal being logged as an exception.
• A measure view before the deadline. A report of G2182 patients with their M1003, M1004, and M1005 status shows the performance rate while the quarter is still open.
• Screening history collected before the visit. Pabau’s digital intake forms ask for the patient’s TB testing history before the appointment starts. Nobody has to chase it after the prescription is written.
• Codes that reach the claim. Pabau’s software for billing teams carries the quality data code onto the claim with the encounter. A $0.00 line then survives the cleanup pass instead of being stripped.

The outcome is a measure 176 rate you can stand behind. The interpreted result sits in the record, and the reason field offers only what the descriptor accepts. The code that goes out then matches the care that happened.

Report measure 176 without chasing charts at the deadline

Pabau’s claims management software helps your team capture the TB screening result and record who interpreted it. The right quality data code then goes out with the claim. Book a demo to see it on your own workflow.

Book a demo

Conclusion

HCPCS code M1005 reports one specific failure, and it is narrower than its reputation. A patient was starting a first course of biologic or immune response modifier therapy.

TB screening was not performed, or the results were never interpreted, and no accepted reason was documented. That is MIPS quality measure 176, not a general preventive screen and not a HEDIS measure.

Report the code honestly when it applies, then work on the reason it applied. Most M1005 lines trace back to an uninterpreted result or a reason nobody wrote down.

Keep the screening result, the interpretation, and the quality data code in one workflow, and your measure 176 rate reflects the care you gave. To see how that works for your team, book a demo.

Continue your research

Need a medical billing compliance framework? Medical billing compliance covers the rules and documentation standards practices need to meet CMS and payer requirements.

Tracking why claims and quality data come back wrong? Denial management in healthcare explains how to spot, track, and resolve the recurring defects behind both.

Frequently asked questions