Pull last month's charge detail and count how many times CPT 82947 appeared on your claims. In a primary care office running point-of-care glucose testing plus a reference lab interface, three or four hundred lines is unremarkable. That volume matters for two reasons: high-frequency lab codes attract payer edits and audit sampling, and every one of those results is a piece of protected health information that moved through a device, an interface, a portal, and possibly a fax machine.

This guide walks the operational path of a quantitative blood glucose test from order to paid claim, then makes the privacy, records-handling, and vendor obligations explicit at each stop. It is administrative guidance for administrators, billers, and privacy officers — not clinical or coding advice for a specific patient encounter.

What CPT 82947 Describes, and the Codes Staff Confuse With It

CPT 82947 is the code for glucose; quantitative, blood (except reagent strip). It sits in the chemistry section of the pathology and laboratory family, and it is billed under the Clinical Laboratory Fee Schedule rather than the physician fee schedule.

Four neighbors cause most of the internal confusion your billing lead will field:

  • 82948 — glucose, blood, reagent strip.
  • 82962 — glucose, blood, by glucose monitoring device cleared by the FDA specifically for home use.
  • 82950 — glucose, post-glucose dose.
  • 82951 — glucose tolerance test, three specimens.

Add 36415 for routine venipuncture, which is a separate collection service with its own payer rules. Your practice does not decide which of these is "right" in the abstract. Your coding policy should describe how the determination gets made: the ordering provider documents the test performed, the method, and the specimen source; the coder or the charge-capture rule maps that documentation to a descriptor; and anything ambiguous goes back to the provider rather than to a guess. Document that escalation path in writing, because it is the first thing an auditor asks about.

CPT 82947 reports a quantitative blood glucose measurement performed by a method other than a reagent strip. It is distinct from 82948 (reagent strip), 82962 (FDA-cleared home-use monitoring device), 82950 (post-glucose dose), and 82951 (tolerance test, three specimens). Code selection depends on the documented method and specimen, not on the diagnosis. When a glucose measurement is included in a broader panel such as a basic or comprehensive metabolic panel, National Correct Coding Initiative procedure-to-procedure edits generally prevent separate reporting of the component.

Where the Order, the Specimen, and the Claim Diverge

Most glucose billing problems are not coding problems. They are workflow gaps between three systems that do not talk to each other cleanly.

The requisition is a PHI document, not scratch paper

A lab requisition carries the patient's name, date of birth, account number, ordering provider, and diagnosis codes. In practices I have reviewed, requisitions accumulate in a tray at the phlebotomy station, get carried into the break room, and go home in a courier bag with a driver nobody has vetted.

Assign one person ownership of the requisition lifecycle: printed, matched to specimen, released to courier, and the office copy filed or scanned same day. Requisition trays belong behind a locked door, not on a counter facing the waiting room. That is a minimum-necessary and physical-safeguard issue, and it is trivially fixable.

Panels, edits, and the reconciliation nobody schedules

If a provider orders a metabolic panel and a separate glucose, your charge capture may push both. NCCI edits will typically deny the component, and if your biller reflexively appends a bypass modifier to clear the denial, you have created a pattern that looks like unbundling on a retrospective review.

Build a weekly reconciliation: every claim line containing 82947 gets matched against the lab report in the chart. Ten minutes with a work queue beats a records request eighteen months later. Log who ran it and what they found — the log is your evidence of good-faith internal auditing.

Screening versus diagnostic, and the ABN conversation

Medicare covers diabetes screening as a preventive benefit with frequency limits and specific diagnosis coding requirements; coverage for a diagnostic glucose test follows different rules. Verify current parameters against CMS guidance before you set a charge-capture rule, and confirm your Advance Beneficiary Notice process for tests that fall outside covered frequency. Front-desk staff should never be the ones deciding coverage on the fly at check-in.

The CLIA Layer Your Billing Staff Cannot Ignore

Every laboratory test performed in your office falls under the Clinical Laboratory Improvement Amendments, and the complexity category of the test must match the certificate you hold. A practice operating under a Certificate of Waiver may only perform waived tests. Some glucose testing methods are waived; others are not.

This has a direct billing consequence: waived tests performed under a Certificate of Waiver are generally reported with modifier QW, and Medicare claims editing will reject lab lines that do not align with the CLIA certificate on file. Check your certificate number, certificate type, and expiration in the billing system today — expired certificates produce claim-wide rejections that take weeks to unwind. CMS maintains the authoritative reference material on CLIA certificates and waived test lists.

Practical role assignment: your lab supervisor owns certificate renewal and the waived-test list; your billing lead owns the certificate data in the claim scrubber; your compliance lead owns the annual check that those two agree. Write those names down. "The office manager handles it" is not a control.

Result Release: The Cures Act Clock Meets the Right of Access

A glucose result is one of the fastest-moving pieces of clinical data in your practice. It also sits squarely in the middle of two obligations that practices still get wrong.

First, the HIPAA right of access. A patient — or their personal representative — who requests lab results in the designated record set must receive them generally within 30 days, with one 30-day extension available if you notify the patient in writing of the reason and the new date. Fees are limited to a reasonable, cost-based amount. HHS has published detailed guidance on individuals' right of access that your records staff should have bookmarked, not paraphrased from memory.

Second, information blocking. Under the Cures Act rules, practices and their IT vendors may not engage in practices that interfere with the access, exchange, or use of electronic health information, subject to defined exceptions. Deliberately holding portal release of a glucose result for several days so a nurse can call first is a policy decision that needs to be examined against those exceptions, not made by default. ONC's information blocking resources explain the exception framework.

Note also that since 2014, patients have had the right to obtain completed test reports directly from a CLIA-certified laboratory. If your practice sends specimens to a reference lab, patients may request results from that lab independently. Your staff should know that and stop telling patients the lab "isn't allowed" to release anything.

Every Vendor Attached to a Single Glucose Result

Trace one 82947 result through your environment and list who touches it. A typical small practice inventory looks like this:

  1. The point-of-care analyzer vendor, if the device uploads results, phones home for diagnostics, or supports remote service access.
  2. Lab middleware or interface engine that maps results into the chart.
  3. The reference laboratory performing testing you refer out.
  4. The specimen courier handling labeled tubes and requisitions.
  5. Your clearinghouse, which transmits the claim carrying the diagnosis and the code.
  6. Your patient portal or messaging vendor, which delivers the result.
  7. Any billing or coding outsourcer reviewing lab charges.

Business associate status is not uniform across that list. A reference laboratory performing testing you ordered is generally acting as a covered entity providing treatment, and disclosure to it for treatment purposes does not require a business associate agreement. A device vendor with remote access to result data, a middleware provider, a clearinghouse, and a billing outsourcer are performing functions on your behalf and require executed agreements. Couriers who handle labeled specimens fall into a gray zone that HHS's narrow conduit interpretation does not comfortably cover — most practices execute an agreement rather than argue the point.

This is where the paperwork usually collapses. The analyzer was purchased by the clinical side four years ago, the service contract renewed automatically, and nobody ever asked whether the vendor's remote support tool touches PHI. If your vendor list and risk analysis are stale, tools that automate HIPAA risk analysis, policies, and the supporting document set will get you to a defensible baseline faster than rebuilding spreadsheets from scratch. And if you find an unsigned relationship, you can produce a signature-ready business associate agreement the same afternoon rather than waiting on counsel for a routine form.

Two Retention Clocks Run on the Same Result

CLIA requires laboratories to retain test requisitions and test reports for a defined minimum period — generally two years for most nonwaived testing. Your state medical records statute and your payer contracts almost always require longer, and Medicare-related documentation carries its own retention expectations.

Retain to the longest applicable requirement and write that number into your retention schedule. Then confirm the actual behavior of your systems: instrument memory that auto-purges after 500 results, a middleware log that rotates at 90 days, and a portal message archive with its own deletion policy are all places where the record you would need for an audit quietly disappears.

Worked example: the audit trail you want to be able to produce

A payer requests documentation for twelve claim lines containing CPT 82947 from a date eleven months ago. A practice with clean operations produces, for each line: the signed order or standing-order protocol with the provider's authentication, the requisition, the instrument result report with date, time, and operator ID, the quality-control record for that instrument on that date, the chart note documenting review of the result, and the claim with its diagnosis codes and CLIA certificate data.

If you cannot assemble that set for a random sample within two business days, you have a documentation problem, not a coding problem. Run that drill once a quarter with three claim lines chosen at random and record the outcome.

An Internal Control Checklist for Glucose Testing

  • Named owner for CLIA certificate renewal, with a calendar reminder 90 days out.
  • CLIA certificate number and type verified in the billing system, checked annually.
  • Written escalation path for ambiguous lab documentation, back to the provider.
  • Weekly reconciliation of lab claim lines against chart results, logged.
  • Modifier bypass usage reviewed monthly by someone other than the person applying it.
  • Requisitions stored in a locked location; same-day filing or scanning.
  • Point-of-care instruments listed in your asset inventory as ePHI systems.
  • Vendor list reconciled against executed agreements, including device service contracts.
  • Portal release timing documented with a stated rationale against information blocking exceptions.
  • Retention schedule set to the longest applicable requirement, with system purge settings verified.

Ten controls, none of them expensive. What makes them work is that each has a name attached and a record that shows the check happened.

Start With the Vendor Gap

Pick the piece you can finish this week. Open your device service agreements, find the ones with remote access, and check whether a business associate agreement exists. Then update your risk analysis to reflect the point-of-care instruments and interfaces that actually carry results today. If that documentation set is out of date — and for most practices running lab testing, it is — generate your risk analysis and policy set and get the vendor inventory current before someone else asks to see it.