Moxe Health · Arazzo Workflow

Request a claim-supporting chart and poll for status

Version 1.0.0

Initiate a claim-management request to retrieve the clinical chart supporting a specific claim, then poll the status endpoint with the returned moxeRequestId.

1 workflow 1 source API 1 provider
View Spec View on GitHub HealthcareUnited StatesInteroperabilityClinical DataPayerProviderEHRHealth Data ExchangeClaimsRisk AdjustmentArazzoWorkflows

Provider

moxe-health

Workflows

requestClaimChart
Initiate a claim-management request and read its status.
Requires a Moxe-issued OAuth2 client-credentials bearer token and x-api-key. Submits subscriber/patient identifiers, a VisitId, ClaimId, and DenialRemarkCode, then reads status.
2 steps inputs: AdministrativeGender, ClaimId, DateOfBirth, DenialRemarkCode, EndDate, FirstName, LastName, PatientId, PatientIdType, ProviderOrganizationId, PurposeOfUse, RequestId, RequestSourceId, StartDate, SubscriberId, VisitId outputs: moxeRequestId, requestStatusCode
1
initiate
Submit the claim-management request.
2
checkStatus
Poll the status of the claim-management request using the moxeRequestId.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Request a claim-supporting chart and poll for status
  version: 1.0.0
  summary: >-
    Initiate a claim-management request to retrieve the clinical chart supporting a specific
    claim, then poll the status endpoint with the returned moxeRequestId.
sourceDescriptions:
- name: claimsApi
  url: ../openapi/moxe-health-claims-api-openapi.yml
  type: openapi
workflows:
- workflowId: requestClaimChart
  summary: Initiate a claim-management request and read its status.
  description: >-
    Requires a Moxe-issued OAuth2 client-credentials bearer token and x-api-key. Submits
    subscriber/patient identifiers, a VisitId, ClaimId, and DenialRemarkCode, then reads status.
  inputs:
    type: object
    required:
    - RequestId
    - SubscriberId
    - PatientId
    - PatientIdType
    - DateOfBirth
    - FirstName
    - LastName
    - AdministrativeGender
    - VisitId
    - PurposeOfUse
    - RequestSourceId
    - StartDate
    - EndDate
    - ClaimId
    - DenialRemarkCode
    - ProviderOrganizationId
    properties:
      RequestId: {type: string}
      SubscriberId: {type: string}
      PatientId: {type: string}
      PatientIdType: {type: string}
      DateOfBirth: {type: string}
      FirstName: {type: string}
      LastName: {type: string}
      AdministrativeGender: {type: string}
      VisitId: {type: string}
      PurposeOfUse: {type: string}
      RequestSourceId: {type: string}
      StartDate: {type: string}
      EndDate: {type: string}
      ClaimId: {type: string}
      DenialRemarkCode: {type: string}
      ProviderOrganizationId: {type: string}
  steps:
  - stepId: initiate
    description: Submit the claim-management request.
    operationId: initiateClaimManagementRequest
    requestBody:
      contentType: application/json
      payload:
        RequestId: $inputs.RequestId
        SubscriberId: $inputs.SubscriberId
        PatientId: $inputs.PatientId
        PatientIdType: $inputs.PatientIdType
        DateOfBirth: $inputs.DateOfBirth
        FirstName: $inputs.FirstName
        LastName: $inputs.LastName
        AdministrativeGender: $inputs.AdministrativeGender
        VisitId: $inputs.VisitId
        PurposeOfUse: $inputs.PurposeOfUse
        RequestSourceId: $inputs.RequestSourceId
        StartDate: $inputs.StartDate
        EndDate: $inputs.EndDate
        ClaimId: $inputs.ClaimId
        DenialRemarkCode: $inputs.DenialRemarkCode
        ProviderOrganizationId: $inputs.ProviderOrganizationId
    successCriteria:
    - condition: $statusCode == 202
    outputs:
      moxeRequestId: $response.body#/data/moxeRequestId
  - stepId: checkStatus
    description: Poll the status of the claim-management request using the moxeRequestId.
    operationId: getClaimManagementRequestStatus
    parameters:
    - name: moxeRequestId
      in: path
      value: $steps.initiate.outputs.moxeRequestId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      requestStatusCode: $response.body#/data/requestStatusCode
  outputs:
    moxeRequestId: $steps.initiate.outputs.moxeRequestId
    requestStatusCode: $steps.checkStatus.outputs.requestStatusCode

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/moxe-health-request-claim-chart"
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 email required.

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