A patient arrives at 8:10 a.m. for a scheduled breath test, having eaten a breakfast sandwich in the parking lot. Your medical assistant has already opened the kit. Twenty minutes later you have a wasted single-use kit, a patient who has to come back, and a charge sitting in your billing queue that nobody is sure how to code.

That is the practical reality behind the 83013 CPT code description. This guide is for the administrator, biller, or privacy officer who owns that workflow — scheduling scripts, CLIA paperwork, specimen handoffs, result delivery, and the vendor contracts underneath all of it. It is administrative guidance on how practices structure and document the process, not clinical direction on when testing is appropriate.

What the 83013 CPT Code Description Actually Covers

In the AMA's CPT laboratory section, 83013 describes the analysis of a breath sample for urease activity related to Helicobacter pylori, using a non-radioactive isotope such as carbon-13. The companion code, 83014, describes the drug administration component — the urea dose the patient ingests before samples are collected.

Two operational facts follow from that split, and both drive money and privacy decisions:

  • 83013 is the analytic service. Whoever actually performs the analysis is the entity that reports it. If your in-office analyzer runs the sample, that is your practice. If you collect and ship, that is the reference laboratory.
  • 83014 is the administration component. It is reported separately from the analysis and follows its own payer rules.

Radioactive-isotope breath testing, stool antigen testing, and serology each carry different CPT codes entirely. Do not let a scheduling template or an order set collapse them into one line item. Your charge description master should mirror the actual method and the actual performing entity, and your coding staff should be working from a current CPT reference plus the payer's own policy — not from a legacy superbill someone built in 2019.

83013 vs. 83014: Where Denials Come From

The most common administrative failure is not choosing the wrong code. It is billing both components when your practice only performed one, or billing the analysis when the sample was analyzed elsewhere.

Medicare's general rule is that the entity performing a diagnostic test bills for it, with narrow exceptions for reference-lab and purchased-service arrangements that require specific modifiers and documentation. Commercial payers vary. Before your first claim goes out, put in writing: who performs the analysis, who bills each component, and what modifier convention your clearinghouse expects. Verify that against the payer's published lab policy and the Medicare Clinical Laboratory Fee Schedule rather than relying on what a kit manufacturer's rep told a physician.

Before You Bill 83013, Confirm Your CLIA Certificate Covers It

This is the single most expensive item on the list to get wrong, and it has nothing to do with coding skill.

Any facility that examines human specimens for health assessment purposes needs a CLIA certificate appropriate to the complexity of the testing performed. Some point-of-care tests are waived; many analytic procedures are moderate or high complexity and require a Certificate of Compliance or Accreditation, personnel qualifications, proficiency testing, and quality control records.

Do three things this week:

  1. Pull your current CLIA certificate and note its exact type and expiration.
  2. Pull the manufacturer's package insert for the specific kit and analyzer in your building, and identify the complexity categorization for that device and that intended use.
  3. Confirm against the CMS Clinical Laboratory Improvement Amendments resources whether the test is waived — which determines whether a QW-type modifier applies on claims — or whether it requires a higher certificate level your site may not hold.

If your certificate does not cover the complexity level, the fix is not a coding adjustment. It is either a certificate upgrade or a decision to collect and refer instead of analyze. Make that decision at the administrator level, document it, and tell the clinical staff before the next kit is opened.

The Two-Hour Front-Desk Workflow Nobody Writes Down

Breath testing is preparation-dependent. That makes it a scheduling and communication problem long before it is a laboratory problem.

Scheduling and Prep Instructions

Your scheduler needs a single script and a single handout, both stored where they cannot be edited casually. The script covers fasting expectations, medication timing questions routed back to the ordering clinician, appointment duration, and what happens if the patient arrives unprepared. Assign one owner for that script — usually the clinical supervisor — and review it whenever the kit or vendor changes.

Now the privacy layer. Reminder calls, texts, and emails that reference a specific test are protected health information. HIPAA permits appointment reminders as treatment and healthcare operations communications, but the operational obligations still apply: verify the phone number and email on file, honor requests for confidential communications by alternate means, keep voicemail content minimal, and document that you warned patients about the risks of unencrypted email if they asked you to use it. HHS guidance on email communications with patients is the reference to keep in your policy binder.

Sample Collection and Chain of Custody

Label at the point of collection. Log the collection time, the staff member's initials, the lot number, and the storage location. If samples are batched for a courier pickup, the log needs a pickup timestamp and a courier signature. When a patient later disputes a result or a payer audits the claim, that log is the only thing standing between you and a refund request.

Where the Specimen Goes — and Who Becomes a Business Associate

Map every hand that touches the sample or the result. In a typical practice running this test, the list looks like this:

  • The reference laboratory. A lab is itself a covered health care provider. Sending a specimen and the accompanying patient identifiers for treatment purposes is a permitted provider-to-provider disclosure; that relationship does not require a business associate agreement.
  • The courier or logistics company. This one does. A courier transporting labeled specimens and requisitions handles PHI on your behalf. Get the BAA, and confirm what happens to a misdelivered package.
  • The analyzer vendor with remote access. If a connected device uploads results to a manufacturer cloud, syncs patient identifiers, or allows vendor technicians to log in remotely for support, that vendor is a business associate. Ask specifically whether service sessions can view patient data and whether those sessions are logged.
  • Your interface or integration vendor. Whoever moves the HL7 or API result into the chart is holding PHI in transit and often in a queue.
  • Your billing company or RCM partner. They receive diagnosis codes, dates of service, and the procedure line itself.
  • Patient communication and reminder platforms. Texting or email vendors that see appointment types are in scope.
  • Document destruction and IT support. Requisition copies, printed result sheets, and workstation access all count.

Most practices can name the lab and forget the other six. Run the list against your executed agreements. If a vendor on that list has no signed BAA in your file — or has one signed by a manager who left in 2022 and never refreshed after the vendor changed subprocessors — close the gap before your next claim batch. You can generate a signature-ready Business Associate Agreement through a six-step wizard with PDF and DOCX export, as a one-time purchase, which is usually faster than waiting three weeks for a vendor's legal team to send their own template. HHS maintains the baseline sample business associate agreement provisions if you want to compare required elements line by line.

Documenting Code Selection Without Guessing

Your coders should not be interpreting the 83013 CPT code description from memory. Build a one-page internal reference that names the following, and date it:

  • The exact test method and device in use at each site of service.
  • Which entity performs the analysis and which entity performs the administration.
  • The CPT code your practice reports for each component, sourced from the current-year CPT book or licensed data file.
  • Applicable modifiers by payer.
  • Frequency and medical-necessity documentation the payer requires, including any post-treatment testing limits.
  • Your Advance Beneficiary Notice process when a Medicare patient requests a test the practice expects to be non-covered.

Review that sheet annually when CPT updates publish, and whenever you change kits, labs, or analyzers. Coding staff document what the record supports; clinicians document the clinical rationale. Keep those two responsibilities separate in writing so an auditor can see the boundary.

Breath Test Results Are in the Designated Record Set

Once a result lands in the chart, the HIPAA right of access applies. A patient — or their personal representative — can request the result, and your practice generally has 30 days to respond, with one 30-day extension available if you notify the patient in writing of the reason and the new date. Fees must be limited to the reasonable, cost-based charges HIPAA permits.

Two failure modes show up repeatedly in this workflow. First, the result sits in a device or a lab portal and never posts to the chart, so the records clerk truthfully says "we don't have it" and the request goes unfulfilled. Second, staff route the request to the reference lab and consider the matter closed. If the result is in your designated record set, the obligation is yours. Review the OCR guidance on individuals' right of access to their health information with your front desk, not just your privacy officer.

Right-of-access complaints have driven a long run of OCR enforcement activity, and the OCR breach portal is a useful reminder that vendor-side incidents involving lab and billing partners are a recurring category. Both risks live inside this one small workflow.

A 30-Day Cleanup Plan

Week 1. Confirm your CLIA certificate type against the device complexity for every testing site. Document who performs the analysis.

Week 2. Rebuild the scheduling script and prep handout. Verify appointment reminder content does not disclose more than necessary, and check that confidential-communication requests are actually honored in your system.

Week 3. Build the vendor map for this workflow. Match every entry to an executed, current BAA. Note subcontractor and cloud-hosting questions you need answered.

Week 4. Write the internal coding reference sheet, run a five-claim self-audit against it, and confirm results are posting to the chart within your stated turnaround so records requests can be answered on time.

The 83013 CPT code description is three lines of text. The operational tail behind it — certificate scope, prep instructions, chain of custody, six vendor relationships, and a 30-day records clock — is where practices actually get into trouble.

Start with the vendor map, because it is the gap most likely to be open right now. When you find a courier, analyzer vendor, or billing partner without a current agreement, draft and export the BAA in one sitting instead of adding it to a list you will revisit next quarter. If your broader policy set and risk analysis documentation are also overdue, automated HIPAA risk analysis and policy generation will get the paperwork current faster than a manual rebuild.