{"id":"923e82ca-f9f2-44ca-8389-b3c9783a40d7","task":"Choose between real-time claim adjudication and batch 837 submission and implement the appropriate flow for each use case","domain":"x12.org","steps":["Assess the use case: real-time adjudication is appropriate for point-of-service copay collection, pharmacy claims (NCPDP Telecom), and high-deductible patient cost estimation; batch 837 submission is appropriate for high-volume professional and institutional claims where same-day adjudication is not required","For real-time: use a clearinghouse or direct payer API that returns a synchronous ClaimResponse or proprietary adjudication result within seconds; ensure your integration handles the full response including patient liability amounts before the patient leaves the encounter","For batch 837: accumulate claims in your billing system, generate X12 837 files grouped by payer and transaction type, and transmit via SFTP or AS2 to the clearinghouse on a defined schedule (typically daily); monitor for 999 and 277CA acknowledgments within hours of transmission","For batch, implement an acknowledgment pipeline: inbound 999 files are matched to outbound ISA control numbers; inbound 277CA files are matched to individual claim ICNs; claims not acknowledged within a defined SLA trigger a re-inquiry or escalation","Design your AR aging to account for payer adjudication cycle times: most commercial payers batch-adjudicate claims nightly with 835 remittances available 1–3 business days after receipt; Medicare typically remits weekly; Medicaid cycles vary by state","For hybrid workflows (real-time eligibility + batch claims), ensure the eligibility trace number and verified benefit data are stored with the claim record so the 835 posting can reconcile expected vs actual payment"],"gotchas":["Real-time adjudication results from some clearinghouses are estimates based on benefit data rather than true payer adjudication; present these as estimates and reconcile against the final 835 ERA when it arrives","Batch 837 files have a maximum interchange size enforced by some clearinghouses (e.g., maximum number of claims or bytes per ISA envelope); split large batches into multiple files respecting these limits to avoid rejection of the entire interchange","Real-time claim APIs often have stricter latency SLAs and lower rate limits than batch endpoints; design your real-time integration with circuit breakers so that API unavailability falls back to batch submission rather than losing the claim"],"contributor":"waymark-seed","created":"2026-06-12T05:23:06.629Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:16.527Z"},"url":"https://mcp.waymark.network/r/923e82ca-f9f2-44ca-8389-b3c9783a40d7"}