EDI Analyst Interview Questions for Healthcare X12 Roles

What EDI analyst interview questions should test

The best EDI analyst interview questions ask the candidate to follow one claim through the files, from the 837 that leaves the provider to the 999, the 277CA and finally the 835 that pays or denies it. A healthcare EDI analyst who has done the work can name the loops and segments, explain what each acknowledgment proves, and say what they would check first when something breaks. Someone who learned the terms from a glossary cannot.

The catch is that X12 knowledge is easy to list on a resume and hard to fake in a live conversation, so do not screen this role with a keyword search and a general technical interview. Use questions with exact answers. Interface roles are close cousins of this one, and we cover the HL7 and FHIR side in how to hire interface analysts.

Start with the version. The CMS table of adopted standards and operating rules lists ASC X12 version 5010 for the 837 claim, the 270/271 eligibility, the 276/277 claim status, the 278 authorization and the 835 payment and remittance transactions, with a standard compliance date of January 1, 2012, and NCPDP formats for retail pharmacy. If a candidate talks about 4010 as the working version, ask when they last touched a live file.

Then ask about the rules on top of the standard. CAQH CORE describes its operating rules as a floor for how transactions behave, and three sets are federally mandated under HIPAA, eligibility and benefits, claim status, and payment and remittance. Payers also publish companion guides. The CMS page on Medicare fee for service companion guides says these guides clarify and supplement the X12 implementation guides and are used with them, not in place of them, and it lists the guides each Medicare Administrative Contractor publishes. A strong X12 EDI analyst opens the companion guide before writing a single map.

Interview questions on the 837 and 835

These are the questions I would ask for any 837 835 EDI role, with the shape of a good answer.

1. Walk me through the main loops of an 837P. A good answer moves from the submitter and receiver in Loops 1000A and 1000B, to the billing provider in 2000A, the subscriber in 2000B, the patient in 2000C when the patient is not the subscriber, the claim in 2300 and the service lines in 2400. They should mention that the 837P service line uses SV1 and the 837I uses SV2.
2. What does the CLM segment carry? Expect the patient control number, the total claim charge, the place of service or facility code, and the claim frequency code, where 1 is an original claim, 7 a replacement and 8 a void.
3. Where do you find the payment for one service line in an 835? The claim sits in Loop 2100 with the CLP segment, and each service line sits in Loop 2110 with the SVC segment, followed by CAS adjustments and remark codes.
4. Read this segment for me, CAS*CO*45*120. A good candidate says it is a 120 dollar adjustment, the group code CO means contractual obligation, and CARC 45 means the charge exceeds the fee schedule or contracted amount. The X12 claim adjustment reason code list confirms both meanings and notes that the CR group code is not used in 005010 and later. Then ask what changes if the group code is PR and the CARC is 1. That is a deductible the patient owes.
5. How do CARCs and RARCs differ? CARCs explain why a claim or line was paid differently than billed. The X12 remittance advice remark code list explains that supplemental RARCs add detail to an adjustment a CARC already describes, while informational RARCs, the ones that start with the word Alert, are not tied to any adjustment. A good answer adds that both lists of CARC and RARC codes change, so the analyst checks the current list instead of an old spreadsheet.
6. Does this 835 balance? The candidate should explain that the billed charge minus all adjustments equals the paid amount at the claim and line level, and that the total payment in the BPR segment equals the sum of the claim payments less any provider level adjustments in PLB.

The last question separates people quickly. Analysts who have posted remittances or built a posting map answer it at once. Analysts who only routed files tend to guess.

Questions on eligibility, claim status and acknowledgments

Eligibility and claim status show whether the candidate understands the front and the middle of the revenue cycle as well as claims and payments.

• What do you look for first in a 271? A good answer mentions the EB segments with benefit details by service type, and the AAA segment when the request was rejected, such as a subscriber not found.
• What is the difference between a 999 and a 277CA? The 999 confirms the file was received and whether it passed syntax checks. A CGS Medicare EDI page explains that the contractor returns a 999 to the submitter, that a 277CA is generated only if the 999 was accepted, and that the 277CA carries the ICN or DCN for accepted claims. Neither one proves payment. Only the 835 does.
• How do you read a 277CA rejection? The candidate should go to the STC segment and name its parts, the claim status category code, the claim status code and the entity code. The CGS 277CA edit lookup tool uses exactly this layout, with A7 as a category code, 562 as a status code and 85 as an entity code in its example.
• A file was accepted on the 999 but some claims never show a 277CA. What do you check? Look for a good process here, trading partner IDs, the correct receiver, the clearinghouse report, and whether those claims were split into another file.

What a strong healthcare EDI analyst sounds like

A strong candidate talks in segments and codes, and then explains what they mean for the billing office. They can tell you why a rejected claim never reached adjudication, why a denied claim did, and why those two need different fixes. They mention the payer companion guide without being asked. And they treat test files as patient data, which is what HIPAA aware habits look like day to day.

The warning signs are just as clear. A candidate who only names translator software, cannot explain balancing, or calls every CARC a denial code has probably watched EDI work rather than done it. Identity checks still apply on remote interviews, and our article on proxy interviews and fake candidates covers that side.

EDI analysts often work next to business analysts on the same revenue cycle project, and the two roles should agree on who owns which rule. We explain the analyst side in the business analyst role in RCM and EHR projects. If you are a prime vendor or MSP filling these roles, our supplier information for vendors lists how we work as a sub-vendor.

For the full list of healthcare roles we support, see our healthcare IT and revenue cycle staffing page.

Written by

Israr Kazmi

Israr Kazmi is the founder of Wanware Technologies, the IT staffing, recruitment and consulting division of iCareBilling LLC, an American health tech company based in Chicago, Illinois. He writes about technology, healthcare, health tech and AI automation, with a forward-looking view of where these fields are heading. He also covers recruitment, talent placement, vendor partnerships and careers on the corporate side of technology and healthcare.

More about the author