Zum Hauptinhalt springen

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​

NameTypeRequiredDescription
x12_texttextNoPre-built X12 276/277 text
claim_datajsonNoStructured claim data for building a 276 inquiry

Output ports​

NameTypeRequiredDescription
resultjsonNoMain result data from the claim status operation
statustextNoSubmission or claim status
successbooleanNoWhether the operation succeeded

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
OperationoperationenumYesinquiryinquiry, generate_276, parse_277Claim status 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 276 generation
Receiver IDreceiver_idstringNoRECEIVERISA receiver identifier for 276 generation

Errors​

CodeDescription
CLAIM_DATA_REQUIREDClaim data required for inquiry/generate operations
X12_TEXT_REQUIREDX12 text required for parse_277 operation
CLEARINGHOUSE_URL_REQUIREDClearinghouse URL required for inquiry operation
INQUIRY_FAILEDHTTP 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.

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