15 entries. Every entry is checked against primary sources before it is published; entries not yet verified are marked.
The guide that defines what a professional 837P looks like for the X12 HIPAA transaction set.
- What it does
- Companion guide to the X12 837 Professional claim: syntax rules, segment ordering, and the CMS-1500 data elements.
- Who it's for
- Anyone writing or validating an 837P by hand.
- Why a sponsor would care
- Anchor reference page for high-intent search traffic from implementers.
Verify before publishing
Standards, Reference Free
Normative transaction-set guides for 837, 835, 270/271, 276/277, and the rest of the claim lifecycle.
- What it does
- The authoritative syntax rules for every HIPAA transaction set used in claims and remittance.
- Who it's for
- Integrators and mapping engineers who need the actual spec, not a blog post.
- Why a sponsor would care
- High-quality inbound links from engineers; anchors all '837 vs 837I' comparison pages.
Verify before publishing
Standards, Reference Free / member access for some artifacts
Long-standing free clearinghouse for small practices submitting 837P claims.
- What it does
- Claim submission, remittance/835 handling, and payer enrollment assistance at no monthly fee.
- Who it's for
- Independent practices and billers with a handful of payers.
- Why a sponsor would care
- First-party sponsor candidate: clearinghouse vendors want this audience.
Verify before publishing
Clearinghouse, Free tier Free clearinghouse; paid support options
API-first clearinghouse with a JSON-based 837P submit and 835 ingest model.
- What it does
- Submit and parse 837/835 via APIs plus a web UI; aimed at developers and mid-market providers.
- Who it's for
- Engineering teams that want claim submission as an API call, not a portal and a fax machine.
- Why a sponsor would care
- Direct sponsor candidate: their ICP is exactly this directory's audience.
Verify before publishing
Clearinghouse, API-first Free tier + paid plans
API layer that turns 837P generation and ERA/835 posting into integration work, not a desktop app.
- What it does
- APIs for claim submission, eligibility, and remittance posting for provider and RCM platforms.
- Who it's for
- RCM software vendors and billing teams automating submission pipelines.
- Why a sponsor would care
- Sponsor candidate plus integration-partner referral traffic.
Verify before publishing
Submitter API, Automation Usage-based
Provider-side EDI and remittance automation aimed at reducing manual claim handling.
- What it does
- 837 submission and 835 posting with automated reconciliation for provider revenue-cycle workflows.
- Who it's for
- Provider groups that still live in a clearinghouse portal.
- Why a sponsor would care
- Sponsor candidate; comparison content against legacy portals.
Verify before publishing
Submitter API, Automation Subscription
Multi-payer clearinghouse and payer-connectivity platform used by providers and payers alike.
- What it does
- 837 submission, 835/ERA, 270/271 eligibility, and payer API connectivity in one portal.
- Who it's for
- Practices and MSOs that need broad payer coverage.
- Why a sponsor would care
- Premium sponsor slot; also a reference page for payer-by-payer submission guides.
Verify before publishing
Clearinghouse, Payer connectivity Free tier + paid plans
Revenue-cycle platform with claim creation, scrubbers, and denial analytics.
- What it does
- End-to-end RCM software: claim edit/scrub, submission, remittance, and denial management.
- Who it's for
- Multi-provider groups and hospitals modernizing the claim pipeline.
- Why a sponsor would care
- Sponsor candidate; 'where to scrub before you submit' content cluster.
Verify before publishing
RCM platform, Claims Enterprise subscription
The payer-side claims engine behind a large share of US health plan adjudication.
- What it does
- Enterprise claims adjudication, benefits, and payment integrity across payer networks.
- Who it's for
- Readers who need to understand what happens after they submit.
- Why a sponsor would care
- Context content for enterprise buyers; drives newsletter signups from vendor-side staff.
Verify before publishing
Payer claims, Enterprise Enterprise
Large clearinghouse and payment network; the reference point for market structure.
- What it does
- Claims, payment rails, and analytics across a national provider network.
- Who it's for
- Anyone benchmarking clearinghouse options at scale.
- Why a sponsor would care
- Comparison content; rarely a sponsor candidate.
Verify before publishing
Clearinghouse, Enterprise Enterprise
AI clinical documentation that produces structured notes feeding the coding layer.
- What it does
- Ambient documentation and structured note generation that reduces manual coding input.
- Who it's for
- Physician practices under documentation pressure and RCM teams.
- Why a sponsor would care
- Sponsor candidate for the AI-assisted-coding track of the directory.
Verify before publishing
AI + coding, Documentation Subscription / enterprise
AI agents aimed at revenue-cycle tasks: eligibility, coding support, payment posting.
- What it does
- AI agents for RCM workflows including claim status, payment posting, and coding assistance.
- Who it's for
- RCM leaders evaluating AI against clearinghouse and portal work.
- Why a sponsor would care
- Sponsor candidate; 'what agents can and cannot do in RCM' essay.
Verify before publishing
AI + coding, Automation Subscription
The paper form that the 837P mirrors, item-for-item, for professional claims.
- What it does
- The 1500 claim form fields and their mapping into the 837P segment structure.
- Who it's for
- Billers learning 837P without reading the whole implementation guide.
- Why a sponsor would care
- Top-of-funnel entry point; links into the deeper standards pages.
Verify before publishing
Standards, Reference Free
AI agents for phone-based eligibility, claim status, and payment follow-up.
- What it does
- Voice AI agents that call payers for eligibility, claim status, and payment chasing.
- Who it's for
- RCM teams chasing stuck claims and stuck money.
- Why a sponsor would care
- Sponsor candidate for the 'AI in the RCM loop' content cluster.
Verify before publishing
AI + coding, Automation Subscription / enterprise
Tracks which revision of the CMS-1500 each payer expects.
- What it does
- A maintained table of payer-specific 1500 revisions and their effective dates.
- Who it's for
- Billers whose claims reject for a stale form revision.
- Why a sponsor would care
- High-intent page; links into standards content.
Verify before publishing
Standards, Reference Free
Get the weekly EDI/837 update
One email a week: clearinghouse changes, 835 surprises, and one tool worth testing.
Subscriptions are not being accepted yet. No data leaves this page.