Particle Health · Arazzo Workflow

Particle Health ADT Event Subscription

Version 1.0.0

Register a patient, subscribe to encounter (ADT) notifications, trigger a sandbox event, and retrieve the resulting HL7 v2 messages.

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

Provider

particle-health

Workflows

adt-event-subscription
Subscribe a patient to ADT notifications and retrieve the resulting HL7 v2 messages.
Registers a patient, creates an ADT subscription, triggers a sandbox event, and collects the HL7 v2 messages generated for that patient.
5 steps inputs: clientId, clientSecret, demographics, subscription outputs: messages, patientId
1
authenticate
Exchange the client credentials for a bearer token used by every subsequent call.
2
registerPatient
Register the patient that the ADT subscription will watch.
3
createSubscription
Subscribe the patient to ADT / encounter notifications across the networks.
4
triggerSandboxEvent
Fire a sandbox workflow event so the subscription produces a test notification.
5
collectHl7v2
Retrieve the HL7 v2 messages generated for the patient by the ADT event.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Particle Health ADT Event Subscription
  summary: Register a patient, subscribe to encounter (ADT) notifications, trigger a sandbox event, and retrieve the resulting HL7 v2 messages.
  description: >-
    Implements an event-notification flow aligned with the HL7 Da Vinci Alerts /
    Notifications pattern. After registering a patient, the caller subscribes to
    network ADT (admit / discharge / transfer) events, fires a sandbox event to
    exercise the subscription, and then pulls the resulting HL7 v2 messages for
    the patient. This is the basis for care-coordination alerting and event-driven
    follow-up. Each step inlines its request so the flow is self-contained.
  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-hl7v2-api-openapi.yml
      confidence: 0.82
    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: hl7v2Api
  url: ../openapi/particle-health-hl7v2-api-openapi.yml
  type: openapi
- name: patientsApi
  url: ../openapi/particle-health-patients-api-openapi.yml
  type: openapi
- name: subscriptionsApi
  url: ../openapi/particle-health-subscriptions-api-openapi.yml
  type: openapi
workflows:
- workflowId: adt-event-subscription
  summary: Subscribe a patient to ADT notifications and retrieve the resulting HL7 v2 messages.
  description: >-
    Registers a patient, creates an ADT subscription, triggers a sandbox event,
    and collects the HL7 v2 messages generated for that patient.
  inputs:
    type: object
    required:
    - clientId
    - clientSecret
    - demographics
    - subscription
    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 used to register the patient.
      subscription:
        type: object
        description: Subscription definition selecting the ADT / encounter event types to be notified about.
  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: Register the patient that the ADT subscription will watch.
    operationId: submitPatient
    requestBody:
      contentType: application/json
      payload: $inputs.demographics
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      patientId: $response.body#/id
  - stepId: createSubscription
    description: Subscribe the patient to ADT / encounter notifications across the networks.
    operationId: createPatientSubscriptions
    parameters:
    - name: particle_patient_id
      in: path
      value: $steps.registerPatient.outputs.patientId
    requestBody:
      contentType: application/json
      payload: $inputs.subscription
    successCriteria:
    - condition: $statusCode == 200
  - stepId: triggerSandboxEvent
    description: Fire a sandbox workflow event so the subscription produces a test notification.
    operationId: triggerSandboxWorkflow
    parameters:
    - name: particle_patient_id
      in: path
      value: $steps.registerPatient.outputs.patientId
    successCriteria:
    - condition: $statusCode == 200
  - stepId: collectHl7v2
    description: Retrieve the HL7 v2 messages generated for the patient by the ADT event.
    operationId: getHl7v2Messages
    parameters:
    - name: particle_patient_id
      in: path
      value: $steps.registerPatient.outputs.patientId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      messages: $response.body
  outputs:
    patientId: $steps.registerPatient.outputs.patientId
    messages: $steps.collectHl7v2.outputs.messages

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-adt-subscription-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.