Clearinghouse1 input → 1 output

Realtime EBVB

Performs realtime eligibility verification via Stedi API.

Inputs

payload.ins object: Eligibility request data (required). Must include tradingPartnerId and subscriber information
customApiUrl string: Optional custom Stedi API URL. Overrides node configuration

Outputs

payload object

Eligibility response from Stedi containing:

controlNumber - Transaction control number
tradingPartnerId - Trading partner ID
eligibility - Eligibility information
benefits - Array of benefit details
errors - Array of errors if any

stedi object

Metadata about the Stedi operation:

controlNumber - Transaction control number
tradingPartnerId - Trading partner ID
hasErrors - Boolean indicating if errors exist
integrationId - Integration used
operation - Always "eligibility"
customApiUrl - Custom URL if used

Details

This node performs realtime eligibility verification using the Stedi API for X12 270/271 transactions.

The node requires a Stedi integration to be configured and selected. Only Stedi-type integrations will appear in the integration dropdown.

The eligibility request must be provided in msg.payload.ins and should include:

tradingPartnerId or tradingPartnerServiceId - Required trading partner identifier
subscriber.memberId - Required subscriber member ID
Additional optional fields for subscriber, dependent, provider, and encounter information

Example Request

Example of msg.payload.ins structure:

{
    "tradingPartnerServiceId": "60054",
    "provider": {
        "organizationName": "Provider Name",
        "npi": "1999999984"
    },
    "subscriber": {
        "firstName": "John",
        "lastName": "Doe",
        "memberId": "AETNA9wcSu"
    },
    "dependents": [
        {
            "firstName": "Jordan",
            "lastName": "Doe",
            "dateOfBirth": "20010714"
        }
    ],
    "encounter": {
        "serviceTypeCodes": ["30"]
    }
}

Field Descriptions

tradingPartnerServiceId - Trading partner identifier (required)
controlNumber - Unique control number for the transaction (optional)
submitterTransactionIdentifier - Submitter's transaction ID (optional)
externalPatientId - External patient identifier (optional)
subscriber.memberId - Member/subscriber ID (required)
subscriber.firstName - Subscriber first name (optional)
subscriber.lastName - Subscriber last name (optional)
subscriber.dateOfBirth - Date of birth in YYYYMMDD or YYYY-MM-DD format (optional)
provider.npi - Provider NPI number (optional)
provider.organizationName - Provider organization name (optional)
encounter.serviceTypeCodes - Array of service type codes (optional)

The node implements passthrough behavior, preserving all original message properties while adding the eligibility response to the configured output field (default: msg.payload).

Custom API URL

By default, the node uses the Stedi production URL. You can override this by:

Configuring a custom URL in the node settings
Providing msg.customApiUrl at runtime

The message-based URL takes priority over the node configuration.

{ "tradingPartnerServiceId": "60054", "provider": { "organizationName": "Provider Name", "npi": "1999999984" }, "subscriber": { "firstName": "John", "lastName": "Doe", "memberId": "AETNA9wcSu" }, "dependents": [ { "firstName": "Jordan", "lastName": "Doe", "dateOfBirth": "20010714" } ], "encounter": { "serviceTypeCodes": ["30"] } }