X12 835 QTY Segment Guide: Fields, Format, and Testing Gotchas
QTY is easy to overlook because most claims never send it — but the institutional claims that do send it are usually the ones where a discharge date, a length of stay, or a covered-day count decides whether a downstream system calculates the right patient liability. Leave QTY out of your test files and that logic never gets exercised until a real inpatient remittance breaks it.
QTY (Quantity Information) is an optional claim-level segment in Loop 2100 of the X12 835 that reports a supplemental count tied to a specific unit type — most commonly the number of covered or non-covered days on an institutional stay, but it can also carry other quantity types a payer wants to communicate outside the service-line detail. A claim can carry zero, one, or several QTY segments depending on how many distinct quantities the payer needs to report.
The elements that actually matter in practice
Example
A synthetic QTY reporting 5 covered days on an institutional claim.
Where this trips people up
Because QTY is optional and absent from the vast majority of professional claims, teams building test suites tend to write generators that never emit it at all — and then discover during an inpatient pilot that their parser silently drops the segment instead of mapping it to a length-of-stay field. The other common miss is treating QTY02 as self-describing: it is a bare number, so a test file with QTY*NA*2 and no matching CAS or claim-level context gives a reconciliation engine nothing to validate against, and bugs in how that count gets attached to the claim go unnoticed until production.