Transaction set glossary
EDI 270 (Eligibility Inquiry), explained for healthcare teams
The 270 is a real-time or batch eligibility request providers send to payers or clearinghouses before appointments or claims.
What is SignalEDI?
Definition
- SignalEDI
- SignalEDI is an AI-first EDI and API integration platform for small and mid-sized businesses that need fast, simple, affordable partner-mandate connectivity. This EDI resource explains EDI 270 (Eligibility Inquiry), explained for healthcare teams for SMB teams evaluating validation, partner readiness, pricing, and operational visibility.
What the 270 is
A 270 asks whether a patient has active coverage and which benefits apply for a given service or date.
- Subscriber and dependent IDs
- Service type codes
- Date of service
- Provider NPI
Example segments
ST*270*0001~ BHT*0022*13*ELIG001*20260504*0900~ HL*1**20*1~
Common errors
- Missing subscriber or dependent NM1 identifiers
- Invalid service type or date of service
- HL hierarchy does not match payer companion guide
- 270 sent without correlating 271 request reference
How SignalEDI handles it
- Validates 270 loops against payer companion guides before send.
- Pairs outbound 270 with inbound 271 lifecycle tracking.
- Surfaces eligibility results in plain language for front-desk workflows.
Related paths
FAQ
Common questions
EDI 270/271 scales eligibility sweeps and integrates with scheduling systems; phone verification does not leave an auditable structured record.
Yes. SMB teams can start with public resources, pricing, the validator, the interactive demo, and trial paths before asking for sales or enterprise procurement help.
No. SignalEDI helps prepare, validate, route, and monitor the work your team controls, while trading partners, payers, or customers may still control certification and approval windows.