Stedi · Arazzo Workflow

Stedi X12 837 Professional Claim Lifecycle

Version 1.0.0

Submit an X12 837 professional claim, check its 277 status, and retrieve the converted X12 835 remittance.

1 workflow 3 source APIs 1 provider
View Spec View on GitHub EDIElectronic Data InterchangeHealthcareClearinghouseX12ClaimsEligibilityHIPAARevenue Cycle ManagementB2B IntegrationArazzoWorkflows

Provider

stedi

Workflows

professional-claim-lifecycle
Submit an X12 837 claim, inquire 277 status, and convert the X12 835 remittance.
Implements the professional claim revenue cycle end to end: X12 837 submission, X12 277 status inquiry, and X12 835 remittance conversion.
3 steps inputs: claim, statusRequest outputs: claimTransactionId, remittance, statusTransactionId
1
submitClaim
Submit the X12 837 professional claim to the payer through the Stedi network.
2
checkClaimStatus
Run the X12 276 claim-status inquiry and read the 277 status response for the submitted claim.
3
getRemittance
Convert the resulting transaction into a human-readable X12 835 electronic remittance advice.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Stedi X12 837 Professional Claim Lifecycle
  summary: Submit an X12 837 professional claim, check its 277 status, and retrieve the converted X12 835 remittance.
  description: >-
    The canonical Stedi professional claim lifecycle, encoding the X12 837 claim
    submission, the X12 276/277 claim-status inquiry, and the X12 835 remittance
    advice for a single revenue-cycle episode. A claim is submitted to the payer,
    its status is inquired, and the resulting transaction is converted to a
    human-readable 835 electronic remittance advice. Every step inlines its request
    so the flow is self-contained.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-2870.30
  - BC-2870.50
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-2870.30
      capability_name: Claim Production & Submission
      spec: stedi-real-time-claim-status-api-openapi.yml
      confidence: 0.85
    - capability_id: BC-2870.50
      capability_name: Cash Posting & Payer Reconciliation
      spec: stedi-remittances-api-openapi.yml
      confidence: 0.8
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: claimSubmissionApi
  url: ../openapi/stedi-claim-submission-api-openapi.yml
  type: openapi
- name: realTimeClaimStatusApi
  url: ../openapi/stedi-real-time-claim-status-api-openapi.yml
  type: openapi
- name: remittancesApi
  url: ../openapi/stedi-remittances-api-openapi.yml
  type: openapi
workflows:
- workflowId: professional-claim-lifecycle
  summary: Submit an X12 837 claim, inquire 277 status, and convert the X12 835 remittance.
  description: >-
    Implements the professional claim revenue cycle end to end: X12 837 submission,
    X12 277 status inquiry, and X12 835 remittance conversion.
  inputs:
    type: object
    required:
    - claim
    - statusRequest
    properties:
      claim:
        type: object
        description: X12 837 professional claim packet (controlNumber, tradingPartnerServiceId, billing provider, subscriber, claim information).
      statusRequest:
        type: object
        description: X12 276 claim-status inquiry packet referencing the submitted claim.
  steps:
  - stepId: submitClaim
    description: Submit the X12 837 professional claim to the payer through the Stedi network.
    operationId: ClaimsSubmission
    requestBody:
      contentType: application/json
      payload: $inputs.claim
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      claimTransactionId: $response.body#/transactionId
  - stepId: checkClaimStatus
    description: Run the X12 276 claim-status inquiry and read the 277 status response for the submitted claim.
    operationId: ClaimStatus
    requestBody:
      contentType: application/json
      payload: $inputs.statusRequest
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      statusTransactionId: $response.body#/transactionId
  - stepId: getRemittance
    description: Convert the resulting transaction into a human-readable X12 835 electronic remittance advice.
    operationId: ConvertReport835
    parameters:
    - name: transactionId
      in: path
      value: $steps.checkClaimStatus.outputs.statusTransactionId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      remittance: $response.body
  outputs:
    claimTransactionId: $steps.submitClaim.outputs.claimTransactionId
    statusTransactionId: $steps.checkClaimStatus.outputs.statusTransactionId
    remittance: $steps.getRemittance.outputs.remittance

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/stedi-professional-claim-lifecycle-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.