Overview
This document defines the shared X12 EDI technical design for all PM specs that generate, submit, or consume ANSI X12 transactions. It covers segment-level mapping, behavioral health-specific requirements, and the clearinghouse abstraction layer.Transaction Types
Envelope Structure
All X12 transactions follow ISA/GS/ST envelope structure:Envelope Field Sources
837P Professional Claim Mapping
Key Loops and Segments
Behavioral Health-Specific Segments
AHCCCS Timed Unit Calculation
835 ERA Mapping
Key Segments for Auto-Posting (PM-09)
ERA Auto-Posting Algorithm (PM-09)
270/271 Eligibility Mapping (PM-02)
270 Request Key Segments
271 Response Parsing
Clearinghouse Abstraction Layer (PM-15)
For recommended vendor implementation order (Waystar first) and claim-line-level requirements, see the supplementary spec: PM-15: Clearinghouse Vendor Selection & Waystar-First Integration.Adapter Interface
Configuration Table
AUTHORITATIVE SOURCE: The schema forpm_clearinghouse_configis defined inspecs/pm/specs/PM-15-clearinghouse-integration.md. The definition below is superseded by the spec. Implementers MUST use the spec definition which includesdeleted_at,site_id,custom_fields,username_vault_ref, andconnection_type.
Trading Partner Testing
Each payer/clearinghouse combination requires:- Enrollment: Register sender ID with clearinghouse
- Companion Guide Review: Payer-specific segment requirements
- Test Submission: Submit test 837P, verify acceptance
- ERA Testing: Verify 835 parsing with payer-specific CARC/RARC codes
- Go-Live: Switch from test to production mode
pm_clearinghouse_config.custom_fields.trading_partner_status.
References
- PM-15 Vendor selection: PM-15: Clearinghouse Vendor Selection & Waystar-First Integration — Waystar-first order, line-level requirements, Waystar connection details.