Ribbon Health · Arazzo Workflow

Ribbon Health Provider Directory Search

Version 1.0.0

Resolve an insurance carrier, find in-network providers by specialty and location, then read the matched provider's detail record.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub HealthcareProvider DirectoryInsuranceClinical DataCare NavigationEligibilityPrice TransparencyProvider SearchHealth PlansDigital HealthArazzoWorkflows

Provider

ribbon-health

Workflows

provider-search
Find an in-network provider by insurance, specialty, and location, then read the directory record.
Resolves the insurance carrier, searches the provider directory by specialty, location, and carrier, and reads the first matched provider by NPI.
3 steps inputs: insuranceCarrier, location, specialty outputs: insuranceId, provider, providerNpi
1
searchInsurances
Resolve the insurance carrier to confirm the plan is recognized in the directory.
2
findProviders
Query the provider directory for practitioners matching the specialty, location, and carrier.
3
getProviderDetail
Read the first matched provider by NPI for the full directory record.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Ribbon Health Provider Directory Search
  summary: Resolve an insurance carrier, find in-network providers by specialty and location, then read the matched provider's detail record.
  description: >-
    A provider-directory search flow aligned with the HL7 Da Vinci Payer Data
    Exchange (PDex) Plan-Net intent, where a consumer locates an in-network
    practitioner by insurance, specialty, and geography. The carrier is resolved
    first to confirm the plan is recognized, the provider directory is then
    queried with the specialty, location, and carrier filters, and the first
    matching provider is read by NPI for the full directory record. Every step
    inlines its request so the flow is self-contained.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-610.20
  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-610.20
      capability_name: Master Data Management
      spec: ribbon-health-providers-api-openapi.yml
      confidence: 0.7
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: providersApi
  url: ../openapi/ribbon-health-providers-api-openapi.yml
  type: openapi
- name: referenceEndpointsApi
  url: ../openapi/ribbon-health-reference-endpoints-api-openapi.yml
  type: openapi
workflows:
- workflowId: provider-search
  summary: Find an in-network provider by insurance, specialty, and location, then read the directory record.
  description: >-
    Resolves the insurance carrier, searches the provider directory by specialty,
    location, and carrier, and reads the first matched provider by NPI.
  inputs:
    type: object
    required:
    - insuranceCarrier
    - specialty
    - location
    properties:
      insuranceCarrier:
        type: string
        description: Insurance carrier name used to confirm the plan and filter the provider directory.
      specialty:
        type: string
        description: Provider specialty to search the directory on.
      location:
        type: string
        description: Geographic location (city, state, or coordinates) used to scope the directory search.
  steps:
  - stepId: searchInsurances
    description: Resolve the insurance carrier to confirm the plan is recognized in the directory.
    operationId: getInsurances
    parameters:
    - name: carrier_name
      in: query
      value: $inputs.insuranceCarrier
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      insuranceId: $response.body#/data/0/uuid
  - stepId: findProviders
    description: Query the provider directory for practitioners matching the specialty, location, and carrier.
    operationId: getCustomProviders
    parameters:
    - name: specialty
      in: query
      value: $inputs.specialty
    - name: location
      in: query
      value: $inputs.location
    - name: insurance_carrier_name
      in: query
      value: $inputs.insuranceCarrier
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      providerNpi: $response.body#/data/0/npi
  - stepId: getProviderDetail
    description: Read the first matched provider by NPI for the full directory record.
    operationId: getCustomProvider
    parameters:
    - name: npi
      in: path
      value: $steps.findProviders.outputs.providerNpi
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      provider: $response.body
  outputs:
    insuranceId: $steps.searchInsurances.outputs.insuranceId
    providerNpi: $steps.findProviders.outputs.providerNpi
    provider: $steps.getProviderDetail.outputs.provider

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/ribbon-health-provider-search-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.