X12 Claim Status
Category: Healthcare Standards
Node id: x12-claim-status
Standards: HIPAA, SOC2
Handles 276/277 claim status inquiry and response processing
What it does
- 276 claim status inquiry generation and submission
- 277 claim status response parsing
- Clearinghouse integration for real-time status checks
- Structured claim status extraction from EDI responses
Use cases
- Check claim adjudication status with payers
- Automate claim follow-up workflows
- Parse incoming 277 responses for revenue cycle dashboards
Runtime
- Performance tier:
variable
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
x12_text | text | No | Pre-built X12 276/277 text |
claim_data | json | No | Structured claim data for building a 276 inquiry |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Main result data from the claim status operation |
status | text | No | Submission or claim status |
success | boolean | No | Whether the operation succeeded |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Operation | operation | enum | Yes | inquiry | inquiry, generate_276, parse_277 | Claim status operation to perform |
| Clearinghouse URL | clearinghouse_url | string | No | Base URL of the clearinghouse endpoint (required for inquiry) |
Auth
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Auth Token | auth_token | secret | No | Bearer token for clearinghouse authentication |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Sender ID | sender_id | string | No | SENDER | ISA sender identifier for 276 generation | |
| Receiver ID | receiver_id | string | No | RECEIVER | ISA receiver identifier for 276 generation |
Errors
| Code | Description |
|---|---|
CLAIM_DATA_REQUIRED | Claim data required for inquiry/generate operations |
X12_TEXT_REQUIRED | X12 text required for parse_277 operation |
CLEARINGHOUSE_URL_REQUIRED | Clearinghouse URL required for inquiry operation |
INQUIRY_FAILED | HTTP request to clearinghouse failed |
Runtime notes
- Result shape varies: inquiry returns trace_number+response+http_status, generate_276 returns x12_text+transaction_type, parse_277 returns patient_name+claim_status+status_details
- For inquiry, either x12_text or claim_data must be provided — claim_data is used to auto-build the 276
- parse_277 extracts STC segments for status codes and NM1*QC for patient name
- Status output is 'submitted' for inquiry, 'generated' for generate_276, or the parsed claim status code for parse_277
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
Something unclear? Send documentation feedback by email.