Particle Health · Arazzo Workflow

Particle Health National Patient Record Retrieval

Version 1.0.0

Authenticate, register a patient demographic, run a national query across the health information networks, poll until the query completes, then collect the aggregated clinical record.

1 workflow 5 source APIs 1 provider
View Spec View on GitHub ADTC-CDACare CoordinationCarequalityClinical DataCommonWellDeltaseHealth ExchangeEHRFHIRHealth DataHealth Information ExchangeHealthcareHIEHL7HL7v2InteroperabilityMedical RecordsPatientsPharmacyQHINSurescriptsTEFCAUSCDIArazzoWorkflows

Provider

particle-health

Workflows

national-patient-record-retrieval
Register a patient, query the national networks, and collect the consolidated clinical record.
Implements the Da Vinci PDex national record-retrieval sequence end to end: token, patient registration, network query, status polling, and record collection as C-CDA and FHIR R4.
6 steps inputs: clientId, clientSecret, demographics outputs: ccda, fhir, patientId
1
authenticate
Exchange the client credentials for a bearer token used by every subsequent call.
2
registerPatient
Submit the patient demographic to create a Particle patient record that the network query will resolve against.
3
launchNetworkQuery
Launch a national query that fans the demographic out to the connected health information networks.
4
pollQueryStatus
Poll the query until the networks have finished returning records (status COMPLETE).
5
collectCcda
Retrieve the consolidated record as C-CDA documents once the query is complete.
6
collectFhir
Retrieve the same consolidated record as a FHIR R4 dataset for structured processing.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Particle Health National Patient Record Retrieval
  summary: Authenticate, register a patient demographic, run a national query across the health information networks, poll until the query completes, then collect the aggregated clinical record.
  description: >-
    The canonical Particle Health record-retrieval flow, modeled on the HL7 Da
    Vinci Payer Data Exchange (PDex) and patient-access pattern. A demographic is
    submitted to create a Particle patient, a network query is launched to gather
    records from connected exchanges (Carequality / eHealth Exchange / CommonWell),
    the query is polled to completion, and the consolidated record is retrieved as
    a C-CDA package and as a FHIR R4 $everything bundle. Every step inlines its
    request so the flow can be read and executed without opening the underlying
    OpenAPI description.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-2900.60
  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-2900.60
      capability_name: Healthcare Interoperability Operations
      spec: particle-health-queries-api-openapi.yml
      confidence: 0.85
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: authenticationApi
  url: ../openapi/particle-health-authentication-api-openapi.yml
  type: openapi
- name: ccdaApi
  url: ../openapi/particle-health-ccda-api-openapi.yml
  type: openapi
- name: fhirApi
  url: ../openapi/particle-health-fhir-api-openapi.yml
  type: openapi
- name: patientsApi
  url: ../openapi/particle-health-patients-api-openapi.yml
  type: openapi
- name: queriesApi
  url: ../openapi/particle-health-queries-api-openapi.yml
  type: openapi
workflows:
- workflowId: national-patient-record-retrieval
  summary: Register a patient, query the national networks, and collect the consolidated clinical record.
  description: >-
    Implements the Da Vinci PDex national record-retrieval sequence end to end:
    token, patient registration, network query, status polling, and record
    collection as C-CDA and FHIR R4.
  inputs:
    type: object
    required:
    - clientId
    - clientSecret
    - demographics
    properties:
      clientId:
        type: string
        description: Particle client id used to obtain a bearer token.
      clientSecret:
        type: string
        description: Particle client secret used to obtain a bearer token.
      demographics:
        type: object
        description: Patient demographic packet (name, dob, gender, address, ssn) used to match records across the networks.
  steps:
  - stepId: authenticate
    description: Exchange the client credentials for a bearer token used by every subsequent call.
    operationId: getAuthToken
    parameters:
    - name: client_id
      in: header
      value: $inputs.clientId
    - name: client_secret
      in: header
      value: $inputs.clientSecret
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      token: $response.body#/token
  - stepId: registerPatient
    description: Submit the patient demographic to create a Particle patient record that the network query will resolve against.
    operationId: submitPatient
    requestBody:
      contentType: application/json
      payload: $inputs.demographics
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      patientId: $response.body#/id
  - stepId: launchNetworkQuery
    description: Launch a national query that fans the demographic out to the connected health information networks.
    operationId: createPatientQuery
    parameters:
    - name: particle_patient_id
      in: path
      value: $steps.registerPatient.outputs.patientId
    successCriteria:
    - condition: $statusCode == 200
  - stepId: pollQueryStatus
    description: Poll the query until the networks have finished returning records (status COMPLETE).
    operationId: getPatientQueryStatus
    parameters:
    - name: particle_patient_id
      in: path
      value: $steps.registerPatient.outputs.patientId
    successCriteria:
    - context: $response.body
      condition: $.status == "COMPLETE"
      type: jsonpath
    outputs:
      status: $response.body#/status
  - stepId: collectCcda
    description: Retrieve the consolidated record as C-CDA documents once the query is complete.
    operationId: getCcdaFiles
    parameters:
    - name: particle_patient_id
      in: path
      value: $steps.registerPatient.outputs.patientId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      ccda: $response.body
  - stepId: collectFhir
    description: Retrieve the same consolidated record as a FHIR R4 dataset for structured processing.
    operationId: getFhirDatasets
    parameters:
    - name: particle_patient_id
      in: path
      value: $steps.registerPatient.outputs.patientId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      fhir: $response.body
  outputs:
    patientId: $steps.registerPatient.outputs.patientId
    ccda: $steps.collectCcda.outputs.ccda
    fhir: $steps.collectFhir.outputs.fhir

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/particle-health-patient-record-retrieval-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.