Zum Hauptinhalt springen

X12 Prior Auth

Category: Healthcare Standards
Node id: x12-prior-auth

Standards: HIPAA, SOC2

Handles 278 prior authorization request and response processing

What it does​

  • 278 prior authorization request generation and submission
  • 278 prior authorization response parsing
  • Clearinghouse integration for authorization workflows
  • Structured authorization decision extraction

Use cases​

  • Submit prior authorization requests to payers electronically
  • Automate prior auth workflows for scheduled procedures
  • Parse authorization responses for approval/denial status

Runtime​

  • Performance tier: variable

Input ports​

NameTypeRequiredDescription
x12_texttextNoPre-built X12 278 text
auth_datajsonNoAuthorization request data (payer, provider, patient, diagnosis, procedure info)

Output ports​

NameTypeRequiredDescription
resultjsonNoMain result data from the prior authorization operation
statustextNoAuthorization or submission status
successbooleanNoWhether the operation succeeded

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
OperationoperationenumYesrequestrequest, generate_278, parse_responsePrior authorization operation to perform
Clearinghouse URLclearinghouse_urlstringNoBase URL of the clearinghouse endpoint (required for request)

Auth​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Auth Tokenauth_tokensecretNoBearer token for clearinghouse authentication

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Sender IDsender_idstringNoSENDERISA sender identifier for 278 generation
Receiver IDreceiver_idstringNoRECEIVERISA receiver identifier for 278 generation

Errors​

CodeDescription
AUTH_DATA_REQUIREDAuthorization request data required
X12_TEXT_REQUIREDX12 text required for parse_response operation
CLEARINGHOUSE_URL_REQUIREDClearinghouse URL required for request operation
REQUEST_FAILEDHTTP request to clearinghouse failed

Runtime notes​

  • Result shape varies: request returns trace_number+response, generate_278 returns x12_text, parse_response returns auth_number+status_description+certification_type
  • For request, either x12_text or auth_data must be provided — auth_data auto-builds the 278 transaction
  • parse_response extracts HCR segment for auth status (A1=certified, A3=not certified, A4=pended) and UM for review actions
  • Status output is 'submitted' for request, 'generated' for generate_278, or the HCR status code for parse_response

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..