Skilled nursing product in development

Ease currently serves behavioral health organizations and is planning a skilled nursing product. Discuss planned scope and availability.

SNF billing managers and EDI implementation leads

SNF Electronic Claim Testing: Trace the 837I Through 999 and 277CA Responses

Evaluate SNF billing-system claim tests using submission identity, 999 and 277CA response reconciliation, payer-specific onboarding and a worked exception ledger.

Quick answer

Test electronic SNF claims as a chain of evidence: the intended 837I file, its transaction acknowledgments, claim-level acceptance or rejection, and the route into production. Reconcile every test claim to its response and owner. A successful 999 is not a payment determination, and one trading partner’s approval does not establish readiness for every payer, provider identity or submission route.

Treat a test as a submission-and-response chain

A billing application can create a file that looks complete while the receiver rejects its structure, one claim fails a data check or staff never retrieve the response. Before go-live, prove the entire chain for the proposed provider, submitter and receiving route.

The CGS 837I Companion Guide, version 10.0, August 2026, identifies the institutional claim transaction and describes CGS Medicare trading-partner testing and production steps. This is a concrete Medicare example, not an all-payer onboarding specification. Establish the current instructions for each actual receiver rather than copying another payer's sample identifiers or approval process.

The worked ledger below is synthetic. It is an original internal acceptance exercise and is not a replacement for a receiver's required test volume, cases or approval.

Keep the evidence stages distinct

Evidence Question it can help answer What it does not establish
Retained 837I file What institutional claim data and control identifiers left the sender? Receiver acceptance
Transport receipt Did the designated endpoint receive a transmission? Transaction or claim acceptance
999 Was the transaction implementation accepted or rejected at that stage? Adjudication or payment
277CA Which claims were acknowledged as accepted or rejected? Final coverage/payment determination
276/277 status exchange What status does the queried Medicare claim have? A replacement for missing submission acknowledgments
Remittance evidence What adjudication/payment information was reported? Matching bank cash without reconciliation

The CGS 999/277CA job aid, revised September 2013, distinguishes technical errors addressed through 999 handling from specific-claim corrections and returned claim numbers in the 277CA. Use its examples to understand the distinction, not as current field-by-field instructions. The newer companion guide supplies the relevant CGS context.

CMS describes Medicare 276 inquiries and 277 responses. That exchange serves a different purpose from a 277CA claim acknowledgment. A generic “277 received” label is insufficient for the acceptance record.

Define the identity that travels with each test

Before generating the file, document the billing provider, submitter, receiver, clearinghouse or direct route, test/production designation, companion-guide version and expected responses. Use only data and identifiers authorized for that receiver's testing process.

Retain original interchange, group, transaction and claim references, their translated display values, and the acknowledgment source. A clearinghouse's acceptance of its inbound file can precede a payer's separate response. Show both origins when both exist; the presence of an upstream acknowledgment should not close a downstream missing-response exception.

Specify who retrieves responses when the primary biller is unavailable. Test that ordinary billing staff can see the relevant results and route technical failures to the responsible team. A successful connection managed only through the vendor's administrative console is incomplete operational evidence.

Work a fictional batch without hiding the rejected claim

Assume this internal specimen contains four claims totaling $10,000. Amounts are invented charges, not reimbursement estimates. The simulated transaction receives an accepted 999. Its subsequent claim acknowledgment contains three acceptances and one rejection.

Claim Submitted amount Simulated 277CA disposition Required local action
A $4,000 Accepted Preserve returned reference and stage
B $3,000 Accepted Preserve returned reference and stage
C $2,000 Rejected Assign correction to reviewed data error
D $1,000 Accepted Preserve returned reference and stage
Total $10,000 3 accepted; 1 rejected Reconcile every claim

Acknowledged accepted amounts total $8,000; rejected amounts total $2,000. Together they account for all four claims and $10,000. Reporting the entire batch as accepted because its 999 passed fails this exercise.

Correct C using the authorized process and retain its earlier rejected version. If C's corrected attempt is accepted, there are four unique business claims and five claim attempts in the history. Do not count the extra attempt as another $2,000 receivable. Link the response to the correct attempt rather than overwriting the original rejection.

Add failures that an orderly batch will not reveal

Replay the same response file. Expected result: evidence of the retrieval/import attempt, with no duplicate claim disposition or financial event. Then remove D's claim-level response from a copy of the fixture. The result is three accounted-for claims and one missing response, not an implied rejection or success.

Inject a transaction-level rejection and verify that the team follows the actual response hierarchy. Do not manufacture a complete claim-level disposition when the receiver did not process that far. Test a lost connection after transmission: investigate available receipt and response evidence before resending, so uncertainty does not automatically become duplicate submission.

Finally, route the same synthetic case through the proposed backup staff role. That person should locate the transmitted version, response source, open issue and next action. Record unresolved cases with an owner and a follow-up expectation based on the actual trading-partner arrangement, rather than an invented universal turnaround time.

Approve production scope separately from expected payment

In CGS's companion guide, testing includes accepted acknowledgment evidence and a production-movement step involving its EDI helpdesk. Preserve the actual approval applicable to the submitter and route. A vendor screenshot is not the receiver's approval record.

CGS also explains that clients using approved vendor or clearinghouse software may not need separate testing before production migration. Establish whether that arrangement actually covers your product, route and provider. Preserve its evidence; do not infer either an exemption or a new testing obligation from this article.

Keep a readiness matrix for each in-scope payer/provider arrangement: enrollment or association prerequisites, connectivity, accepted test evidence, response retrieval, correction/retest result and production authorization where required. Mark untested arrangements explicitly. A successful Medicare path does not establish a Medicaid or Medicare Advantage path.

CMS Medicare remittance guidance describes final adjudication and payment information conveyed after processing. Continue reconciliation into that later stage once live claims begin. Pre-go-live test success demonstrates the tested submission and handling capabilities; it cannot guarantee coverage, payment amount or deposit timing.

Questions & answers

Does an accepted 999 mean the payer will pay?

No. The 999 addresses implementation-level acceptance of transmitted transactions. Claim-level acknowledgment, adjudication and remittance are separate stages; coverage and payment are not established by a technical acknowledgment.

Is a 277CA the same as a 277 claim-status response?

No. A 277CA is a claim acknowledgment in the submission path. The 276/277 exchange asks for and returns claim status. Preserve the transaction type, origin and associated submission instead of grouping every response under a generic status label.

Can one successful test authorize every SNF payer route?

No. Establish the actual receiver, provider/submitter relationships, clearinghouse route, current companion instructions and required production approval for each in-scope arrangement. Reuse technical work only where its applicability is verified.

Primary sources

Use the cited source and its applicable version when making a facility-specific decision. These guides explain operational evaluation methods; they are not individualized clinical, coding, or legal advice.