← Back to connectors

Azure API for FHIR connector for Okou

Connect an existing Azure API for FHIR account to inspect its CapabilityStatement and search common FHIR resources through a read-only data-plane API.

Data & infrastructure · Microsoft Entra access token and account name

Sign up to use Azure API for FHIR

Use Azure API for FHIR in Okou

Use an existing Azure API for FHIR account to inspect its CapabilityStatement and search common FHIR resources with read-only GET requests.

Once connected, supported Azure API for FHIR actions can become steps in a reusable workflow alongside the other services your team uses. Run the workflow once, on a schedule, or when an event starts it.

What you can do with Azure API for FHIR

  • Read the Azure API for FHIR CapabilityStatement from /metadata to inspect supported FHIR capabilities and search parameters.
  • Search common FHIR resource collections with read-only GET requests. Results may contain protected health information and are not default-allowed.

How the Azure API for FHIR connector works

A connected service becomes one permissioned step in the work you hand off.

  1. 1

    Connect Azure API for FHIR

    Choose Microsoft Entra access token and account name.

  2. 2

    Choose the work

    Use only the supported actions your workflow needs.

  3. 3

    Run it your way

    Start it once, schedule it, or attach an event trigger.

Connect Azure API for FHIR securely

Use the connection method that fits your account and grant only the access the workflow needs.

  • Microsoft Entra access token and account name

Connector access is controlled per service and per action, so a workflow does not need broader access than the work you ask it to do.

Azure API for FHIR connector questions

What can Okou do with Azure API for FHIR?
Connect an existing Azure API for FHIR account to inspect its CapabilityStatement and search common FHIR resources through a read-only data-plane API. Documented actions include: Read the Azure API for FHIR CapabilityStatement from /metadata to inspect supported FHIR capabilities and search parameters. Search common FHIR resource collections with read-only GET requests. Results may contain protected health information and are not default-allowed.
How do I connect Azure API for FHIR to Okou?
Connect Azure API for FHIR using Microsoft Entra access token and account name. The connection controls which supported actions a workflow can use.
Can Azure API for FHIR run in an automated workflow?
Yes. After it is connected, supported Azure API for FHIR actions can run in reusable Okou workflows on demand, on a schedule, or from an event trigger.

More data & infrastructure connectors

Explore other connectors in the same product category.

Azure Cosmos DB

Connect Azure Cosmos DB for NoSQL to read databases, containers, and documents through the SQL API REST endpoint.

Azure Active Directory

Connect Azure Active Directory, now Microsoft Entra ID, to inspect users, groups, applications, service principals, devices, relationships, and Conditional Access policies through Microsoft Graph.

Azure File Storage

Connect Azure File Storage to inspect, create, update, and delete Azure file shares, directories, and files through the FileREST data-plane API.

View all connectors