X12 835 Reference

X12 835 SVC01-1 (Product/Service ID Qualifier): Format, Values, and Testing Notes

Jul 27, 2026 · 4 min read

SVC01-1 is a single two-character code, but it decides how every downstream system interprets the procedure code sitting right next to it. Get the qualifier wrong in test data and you get a parser that quietly misreads real production files.

Quick answer

SVC01-1 is the first component of the SVC01 composite and identifies the code set used in SVC01-2. HC means the value is a HCPCS or CPT procedure code, NU signals a revenue-code-only line with no procedure, and N4 marks an NDC drug code. A parser that hardcodes HC instead of reading this qualifier will misparse any revenue-code-only or drug-billed line.

What this element contains

HCPCS/CPT — the overwhelming majority of professional and outpatient claim lines use this qualifier

National Uniform Billing Committee Revenue Code — used when the line has no procedure code, common on institutional room-and-board or ancillary charges

National Drug Code — appears when the line is reporting payment for a billed drug identified by NDC rather than a CPT code

Jurisdiction Specific Procedure and Supply Codes — rare in general commercial data; shows up mostly in workers-comp or state-specific payer files

Example

Synthetic example Generated by Synthibase

SVC*HC:99213:25*125.00*100.00**1*HC:99212*1*

The HC before the first colon in SVC01 is SVC01-1 — it tells the parser that 99213 is a CPT code, not a revenue code or NDC.

Where this trips people up

A lot of homegrown 835 parsers assume every SVC01 composite starts with HC and slice the string accordingly, because that is true in almost all of their sample files. The first NU or N4 line that shows up in production either gets silently mis-mapped as a procedure code or throws an unhandled exception. If your synthetic test data only ever generates HC-qualified lines, this bug stays invisible until a real revenue-code-only institutional remit hits the pipeline.

→

X12 835 SVC Segment Guide: Fields, Format, and Testing Gotchas

→

EDI 835 Remittance Advice: Complete Guide for Healthcare IT

→

How to Validate X12 EDI Files Before Payer Submission

Test every SVC01-1 qualifier your parser will ever see

Synthibase mixes HC, NU, and N4 qualified lines into generated 835 files automatically, so parsing gaps surface in testing instead of in production.

Start free trial →

This page is written independently by Synthibase for testing and informational purposes. It is not an official publication of HL7 International or X12/Washington Publishing Company, and is not a substitute for reviewing the official standard or your trading partner's companion guide. See our Terms of Service for full legal terms.