Metriport · Arazzo Workflow

Metriport Patient Matching

Version 1.0.0

Create a facility, register a patient under it, then run an MPI demographic match to resolve an existing patient record.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub HealthcareMedical RecordsFHIRHealth DataWearablesOpen-SourceArazzoWorkflows

Provider

metriport

Workflows

patient-matching
Create a facility, register a patient, then run an MPI demographic match.
Implements the Metriport MPI sequence end to end: facility creation, patient registration, and demographic patient matching.
3 steps inputs: demographics, facility, patient outputs: facilityId, matchedPatient, patientId
1
createFacility
Create the facility that scopes subsequent patient registration.
2
createPatient
Register the patient under the newly created facility.
3
matchPatient
Submit a demographic packet to the MPI match endpoint to resolve an existing patient without creating a duplicate.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Metriport Patient Matching
  summary: Create a facility, register a patient under it, then run an MPI demographic match to resolve an existing patient record.
  description: >-
    The canonical Metriport master patient index (MPI) flow. A facility is created
    to scope patient registration, a patient is created under that facility, and a
    demographic packet is submitted to the MPI match endpoint to resolve an
    existing patient without creating a duplicate. Every step inlines its request
    so the flow is self-contained.
  version: 1.0.0
sourceDescriptions:
- name: facilityApi
  url: ../openapi/metriport-facility-api-openapi.yml
  type: openapi
- name: patientApi
  url: ../openapi/metriport-patient-api-openapi.yml
  type: openapi
workflows:
- workflowId: patient-matching
  summary: Create a facility, register a patient, then run an MPI demographic match.
  description: >-
    Implements the Metriport MPI sequence end to end: facility creation, patient
    registration, and demographic patient matching.
  inputs:
    type: object
    required:
    - facility
    - patient
    - demographics
    properties:
      facility:
        type: object
        description: Facility packet used to create the Metriport facility.
      patient:
        type: object
        description: Patient demographic packet used to create the Metriport patient.
      demographics:
        type: object
        description: Demographic packet submitted to the MPI match endpoint to resolve an existing patient.
  steps:
  - stepId: createFacility
    description: Create the facility that scopes subsequent patient registration.
    operationId: createFacility
    requestBody:
      contentType: application/json
      payload: $inputs.facility
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      facilityId: $response.body#/id
  - stepId: createPatient
    description: Register the patient under the newly created facility.
    operationId: createPatient
    parameters:
    - name: facilityId
      in: query
      value: $steps.createFacility.outputs.facilityId
    requestBody:
      contentType: application/json
      payload: $inputs.patient
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      patientId: $response.body#/id
  - stepId: matchPatient
    description: Submit a demographic packet to the MPI match endpoint to resolve an existing patient without creating a duplicate.
    operationId: matchPatient
    requestBody:
      contentType: application/json
      payload: $inputs.demographics
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      matchedPatient: $response.body
  outputs:
    facilityId: $steps.createFacility.outputs.facilityId
    patientId: $steps.createPatient.outputs.patientId
    matchedPatient: $steps.matchPatient.outputs.matchedPatient

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/metriport-patient-matching-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.