Zum Hauptinhalt springen

X12 Eligibility

Category: Healthcare Standards
Node id: x12-eligibility

Standards: HIPAA, SOC2

Handles 270/271 eligibility inquiry and response processing for insurance verification

What it does​

  • 270 eligibility inquiry generation and submission
  • 271 eligibility response parsing
  • Insurance coverage verification via clearinghouse
  • Structured benefit and eligibility extraction

Use cases​

  • Real-time insurance eligibility verification at registration
  • Automated patient coverage checks before appointments
  • Parse 271 responses for benefit details display

Runtime​

  • Performance tier: variable

Input ports​

NameTypeRequiredDescription
x12_texttextNoPre-built X12 270/271 text (used directly, skips patient_data)
patient_datajsonNoPatient data for building a 270 inquiry. Must be a flat object with top-level keys.

Output ports​

NameTypeRequiredDescription
resultjsonNoMain result data from the eligibility operation
eligiblebooleanNoWhether the patient is eligible
successbooleanNoWhether the operation succeeded

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
OperationoperationenumYesinquiryinquiry, generate_270, parse_271Eligibility operation to perform
Clearinghouse URLclearinghouse_urlstringNoBase URL of the clearinghouse endpoint (required for inquiry)

Auth​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Auth Tokenauth_tokensecretNoBearer token for clearinghouse authentication

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Sender IDsender_idstringNoSENDERISA sender identifier for 270 generation
Receiver IDreceiver_idstringNoRECEIVERISA receiver identifier for 270 generation
Service Type Codeservice_type_codestringNo30Service type code for eligibility inquiry (e.g. 30 for health benefit plan coverage)

Errors​

CodeDescription
PATIENT_DATA_REQUIREDPatient data required for eligibility inquiry
X12_TEXT_REQUIREDX12 text required for parse_271 operation
CLEARINGHOUSE_URL_REQUIREDClearinghouse URL required for inquiry operation
INQUIRY_FAILEDHTTP request to clearinghouse failed

Runtime notes​

  • Requires EITHER x12_text OR patient_data — if both are missing, throws 'x12_text or patient_data is required'.
  • x12_text is checked first. If present and non-empty, patient_data is ignored entirely.
  • patient_data MUST be a flat JSON object with top-level keys: last_name, first_name, member_id (required), date_of_birth (optional). Nested objects like {data:{last_name:...}} will NOT work — the node reads patient_data['last_name'] directly.
  • Do NOT wire a validator result directly to patient_data — validator outputs {valid,errors,data:{...}} which is not the flat structure this node expects. Use a transform/extract node to flatten it first.

See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.

Etwas unklar? Senden Sie Feedback zur Dokumentation per E-Mail..