Microsoft Azure Health Data Services

Microsoft Azure Health Data Services is a cloud-based suite of managed API services built on open healthcare standards (FHIR R4, DICOM, HL7) that enables healthcare organizations to collect, store, analyze, and exchange protected health information (PHI) at scale. The platform includes a FHIR service for structured clinical data exchange, a DICOM service for medical imaging workflows, a MedTech service for IoMT device data ingestion, and a de-identification service for HIPAA-compliant PHI removal from unstructured text. All services run within a HIPAA/HITRUST compliance boundary in an Azure workspace and authenticate via Microsoft Entra ID OAuth 2.0 bearer tokens.

Microsoft Azure Health Data Services publishes 13 API contracts indexed on the APIs.io network, including Collection API, Deid API, DicomServices API, and 10 more. Tagged areas include Healthcare, FHIR, DICOM, IoMT, and Health Data.

The Microsoft Azure Health Data Services catalog on APIs.io includes 1 event-driven AsyncAPI specification, 2 JSON-LD contexts, and 2 Spectral governance rulesets.

Microsoft Azure Health Data Services’ developer surface includes CLI, authentication, documentation, pricing, signup flow, changelog, status page, and 50 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

75.2/100 exemplar ▲ 22.7 Agent 37/100 agent ready open core · MIT Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

2 published contracts 2 Agent Skills

Healthcare FHIR DICOM IoMT Health Data HIPAA HITRUST Cloud Microsoft Azure Microsoft

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Information Technology Management

BC-600

ResourceWorkspaces

PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HealthcareApis/services/{resourceName} PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HealthcareApis/workspaces/{workspaceName}

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 75.2/100 · exemplar

Contract Quality 9.9 / 16

Developer Ergonomics 8.7 / 13

Access Clarity 10.9 / 13

Operational Transparency 6.4 / 8

Contract Governance 1.7 / 8

Discoverability 4.3 / 7

Regulatory Posture 6.2 / 15

Open Source Surface 10.0 / 10

Create-or-Update Ergonomics 3.3 / 10

Agent readiness — 37/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 65 points between them, because both conditional facets apply and carry 35 points together. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 65% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/azure-health/"><img src="https://apis.io/badge/azure-health/card.svg" alt="Microsoft Azure Health Data Services on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Protected Resource Metadata +5 pts — a served /.well-known/oauth-protected-resource carrying `resource` (documented), and naming its authorization_servers (verified)
Agentic Commerce Well-Known Document +5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's

3 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 60.8 — up to +9.8 composite points
Contract Governance scores 22.0 — up to +9.4 composite points
Developer Ergonomics scores 67.3 — up to +6.5 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/azure-health/apis.yml: open an issue on github.com/api-evangelist/azure-health to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Medical Imaging & IHE Interoperability Profiles	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 4

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

DICOM

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

HL7 FHIR

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 13

Individual APIs this provider publishes, each with its own machine-readable definition.

Microsoft Azure Health Data Services Collection API

The Collection API from Microsoft Azure Health Data Services — 2 operation(s) for collection.

Microsoft Azure Health Data Services Deid API

The Deid API from Microsoft Azure Health Data Services — 1 operation(s) for deid.

Microsoft Azure Health Data Services DicomServices API

The DicomServices API from Microsoft Azure Health Data Services — 2 operation(s) for dicomservices.

Microsoft Azure Health Data Services FhirServices API

The FhirServices API from Microsoft Azure Health Data Services — 2 operation(s) for fhirservices.

Microsoft Azure Health Data Services IotConnectors API

The IotConnectors API from Microsoft Azure Health Data Services — 4 operation(s) for iotconnectors.

Microsoft Azure Health Data Services Jobs API

The Jobs API from Microsoft Azure Health Data Services — 4 operation(s) for jobs.

Microsoft Azure Health Data Services PrivateLinkResources API

The PrivateLinkResources API from Microsoft Azure Health Data Services — 2 operation(s) for privatelinkresources.

Microsoft Azure Health Data Services Proxy API

The Proxy API from Microsoft Azure Health Data Services — 3 operation(s) for proxy.

Microsoft Azure Health Data Services Resource API

The Resource API from Microsoft Azure Health Data Services — 1 operation(s) for resource.

Microsoft Azure Health Data Services WorkspacePrivateEndpointConnections API

The WorkspacePrivateEndpointConnections API from Microsoft Azure Health Data Services — 2 operation(s) for workspaceprivateendpointconnections.

Microsoft Azure Health Data Services WorkspacePrivateLinkResources API

The WorkspacePrivateLinkResources API from Microsoft Azure Health Data Services — 2 operation(s) for workspaceprivatelinkresources.

Microsoft Azure Health Data Services Workspaces API

The Workspaces API from Microsoft Azure Health Data Services — 3 operation(s) for workspaces.

Microsoft Azure Health Data Services Private Endpoint Connections API

The Private Endpoint Connections API from Microsoft Azure Health Data Services — 2 operation(s) for private endpoint connections.

POSTMAN

OPEN COLLECTION

Scroll for all 13

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

azure-health-deidentify-documents

AGENT SKILL

azure-health-provision-fhir-service

AGENT SKILL

Microsoft Azure Health Data Services API pricing

Prices published by Microsoft Azure Health Data Services.

Plan	Price
De-Id	0.0
De-Id (tier from 50.0)	0.05
Notifications	0.59
Export Batch	0.19
Export Batch (tier from 1.0)	0.139992
Export Streaming	0.34
Export Streaming (tier from 1.0)	0.289986
Transcode DICOM	0.004

All 15 plans, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

Microsoft Azure Health Data Services Plans

15 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Microsoft Azure Health Data Services Rate Limits

4 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Microsoft Azure Health Data Services Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Azure Health Events

ASYNCAPI

Semantic Vocabularies 2

JSON-LD contexts and semantic vocabularies used across these APIs.

Azure Health Context

0 classes · 33 properties

JSON-LD

Azure Health Graph Context

0 classes · 0 properties

JSON-LD

Spectral Rules 2

Spectral governance rulesets for linting and validating these APIs.

Microsoft Azure Health Data Services — jsonschema rules

5 rules · 3 warnings 2 info

SPECTRAL

Microsoft Azure Health Data Services API Rules

55 rules · 42 errors 9 warnings 4 info

SPECTRAL

8 properties

JSON SCHEMA

Scroll for all 36

3 fields

EXAMPLE

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Azure Health Authentication

oauth2 · 2 schemes

SECURITY

Azure Health Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Azure Health Vulnerability Disclosure

security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Azure Health Scopes

2 scopes · implicit/authorizationCode

2 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Azure Health Agentic Access

53 operations · 26 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

Signup

Signup

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 3

Reference material describing how the API behaves

ContributionGuide

ContributionGuide

Documentation

Documentation

REST API Reference

REST API Reference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

AgenticAccess

AgenticAccess

Design & Contract 10

Pagination, idempotency, versioning, errors, and events

Spectral

Spectral

JSONLD

Vocabulary

DataModel

Idempotency

Conventions

Lifecycle

ErrorCatalog

Conformance

Scroll for all 10

Build 9

SDKs, sample code, and the tooling you integrate with

CLI

Packages

CodeOfConduct

PostmanWorkspace

GitHubOrganization

GitHubRepository

GitHubRepository

GitHubRepository

SDKs

Scroll for all 9

Access & Security 7

Authentication, authorization, and security posture

SecurityPolicy

SecurityPolicy

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

Authentication

OAuthScopes

Compliance

Authentication

Scroll for all 7

Operate 8

Status, limits, changes, and where to get help

StatusPage

RateLimits

IssueTracker

Releases

ChangeLog

Status

Support

ChangeLog

Scroll for all 8

Commercial 7

Pricing, plans, and the legal terms of use

Plans

FinOps

License

Pricing

PricingCalculator

PricingCalculator

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Scroll for all 7

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 5

Properties that don't map to a standard resource type

Hosts

Vendors

CapabilityMap

ServiceHealth

PrivateLink

Source (apis.yml)

aid: azure-health
name: Microsoft Azure Health Data Services
description: Microsoft Azure Health Data Services is a cloud-based suite of managed API services built on open healthcare
  standards (FHIR R4, DICOM, HL7) that enables healthcare organizations to collect, store, analyze, and exchange protected
  health information (PHI) at scale. The platform includes a FHIR service for structured clinical data exchange, a DICOM service
  for medical imaging workflows, a MedTech service for IoMT device data ingestion, and a de-identification service for HIPAA-compliant
  PHI removal from unstructured text. All services run within a HIPAA/HITRUST compliance boundary in an Azure workspace and
  authenticate via Microsoft Entra ID OAuth 2.0 bearer tokens.
type: Index
deliveryModel:
  model: open-core
  license: MIT
  open_source: true
  commercial: true
  callable_host: false
  label: Open core · an OSS project plus a commercial hosted product
  confidence: high
  source:
  - license
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/azure-health.png
tags:
- Healthcare
- FHIR
- DICOM
- IoMT
- Health Data
- HIPAA
- HITRUST
- Cloud
- Microsoft Azure
- Microsoft
tags_raw:
- Healthcare
- FHIR
- DICOM
- IoMT
- Health Data
- HIPAA
- HITRUST
- Cloud
- Azure
- Microsoft
url: https://raw.githubusercontent.com/api-evangelist/azure-health/refs/heads/main/apis.yml
created: '2026-06-13'
modified: '2026-11-05'
specificationVersion: '0.23'
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
common:
- type: Spectral
  url: rules/azure-health-rules.yml
- type: Spectral
  url: rules/azure-health-jsonschema-spectral-rules.yml
- type: JSONLD
  url: json-ld/azure-health-context.jsonld
- type: Vocabulary
  url: vocabulary/azure-health-vocabulary.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DataModel
  url: data-model/azure-health-data-model.yml
- type: CLI
  url: cli/azure-health-cli.yml
- type: Idempotency
  url: conventions/azure-health-conventions.yml
- type: Conventions
  url: conventions/azure-health-conventions.yml
- type: StatusPage
  url: https://azure.status.microsoft/en-us/status
- type: Lifecycle
  url: lifecycle/azure-health-lifecycle.yml
- type: ErrorCatalog
  url: errors/azure-health-problem-types.yml
- type: Conformance
  url: conformance/azure-health-conformance.yml
- type: LLMsTxt
  url: llms/azure-health-llms.txt
- type: Hosts
  url: hosts/azure-health-hosts.yml
- type: Vendors
  url: vendors/azure-health-vendors.yml
- type: Packages
  url: packages/azure-health-packages.yml
- type: CapabilityMap
  url: capabilities/azure-health-capability-edges.yml
  name: Microsoft Azure Health Data Services Business Capability Map
- type: Plans
  url: plans/microsoft-azure-health-data-services-plans.yml
- type: RateLimits
  url: rate-limits/microsoft-azure-health-data-services-rate-limits.yml
- type: FinOps
  url: finops/microsoft-azure-health-data-services-finops.yml
- type: IssueTracker
  url: https://github.com/Azure/azure-rest-api-specs/issues
- type: Releases
  url: https://github.com/Azure/azure-rest-api-specs/releases
- type: SecurityPolicy
  url: https://github.com/Azure/azure-rest-api-specs/blob/main/SECURITY.md
- type: CodeOfConduct
  url: https://github.com/Azure/.github/blob/main/CODE_OF_CONDUCT.md
- type: ContributionGuide
  url: https://github.com/Azure/azure-rest-api-specs/blob/main/.github/CONTRIBUTING.md
- type: License
  name: MIT
  url: https://github.com/Azure/azure-rest-api-specs/blob/main/LICENSE
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/microsoft-azure-health-data-services/overview
- type: AgenticAccess
  url: agentic-access/azure-health-agentic-access.yml
- type: VulnerabilityDisclosure
  url: security/azure-health-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/azure-health-domain-security.yml
- type: Authentication
  url: authentication/azure-health-authentication.yml
- type: OAuthScopes
  url: scopes/azure-health-scopes.yml
- type: Website
  url: https://azure.microsoft.com/en-us/products/health-data-services
- type: Documentation
  url: https://learn.microsoft.com/en-us/azure/healthcare-apis/
- type: REST API Reference
  url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/
- type: GitHubOrganization
  url: https://github.com/Azure
- type: GitHubRepository
  url: https://github.com/Azure/azure-rest-api-specs
- type: GitHubRepository
  url: https://github.com/microsoft/fhir-server
- type: GitHubRepository
  url: https://learn.microsoft.com/en-us/azure/healthcare-apis/github-projects
- type: Pricing
  url: https://azure.microsoft.com/en-us/pricing/details/health-data-services/
- type: PricingCalculator
  url: https://azure.microsoft.com/en-us/pricing/calculator/
- type: Signup
  url: https://azure.microsoft.com/en-us/free/
- type: ChangeLog
  url: https://learn.microsoft.com/en-us/azure/healthcare-apis/release-notes-2024
- type: Status
  url: https://azure.status.microsoft/en-us/status
- type: ServiceHealth
  url: https://azure.microsoft.com/en-us/get-started/azure-portal/service-health
- type: Support
  url: https://learn.microsoft.com/en-us/answers/tags/389/azure-health-data-services/
- type: Compliance
  url: https://learn.microsoft.com/en-us/azure/healthcare-apis/healthcare-apis-overview#services-in-azure-health-data-services
- type: Authentication
  url: https://learn.microsoft.com/en-us/azure/healthcare-apis/authentication-authorization
- type: PrivateLink
  url: https://learn.microsoft.com/en-us/azure/healthcare-apis/healthcare-apis-overview
- type: SDKs
  url: https://learn.microsoft.com/en-us/azure/healthcare-apis/github-projects
- url: https://techcommunity.microsoft.com/t5/s/gxcuf89792/rss/board?board.id=HealthcareAndLifeSciencesBlog
  type: Blog
- type: DeveloperPortal
  url: https://developer.microsoft.com/en-us
- type: GettingStarted
  url: https://learn.microsoft.com/en-us/azure/healthcare-apis/healthcare-apis-quickstart
- type: ChangeLog
  url: https://learn.microsoft.com/en-us/azure/healthcare-apis/release-notes-2025
- type: TermsOfService
  url: https://azure.microsoft.com/en-us/support/legal/
- type: PrivacyPolicy
  url: https://privacy.microsoft.com/en-us/privacystatement
apis:
- aid: azure-health:azure-health-collection-api
  name: Microsoft Azure Health Data Services Collection API
  description: The Collection API from Microsoft Azure Health Data Services — 2 operation(s) for collection.
  humanURL: https://learn.microsoft.com/en-us/rest/api/healthcareapis/
  baseURL: https://management.azure.com
  tags:
  - Collection
  properties:
  - type: OpenAPI
    url: openapi/azure-health-collection-api-openapi.yml
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/fhir-services
  - type: Authentication
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/authentication-authorization
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/get-started-with-fhir
  - type: SMART on FHIR
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/smart-on-fhir
  - type: Search Reference
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/overview-of-search
  - type: ChangeLog
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/release-notes-2024
  - type: Pricing
    url: https://azure.microsoft.com/en-us/pricing/details/health-data-services/
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/dicom-services
  - type: DICOMweb Standard APIs Guide
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicomweb-standard-apis-with-dicom-services
  - type: Conformance Statement
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicom-services-conformance-statement-v2
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/deploy-dicom-services-in-azure
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/iot-connector-overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/iot-connector
  - type: Device Mapping Guide
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/how-to-use-device-mappings
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/get-started-with-iot
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/health-dataplane/deidentify-text/deidentify-text
  - type: SDK Overview
    url: https://learn.microsoft.com/dotnet/api/overview/azure/Health.Deidentification-readme
  - type: Service Limits
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/overview#input-requirements-and-service-limits
  - type: Documentation
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/workspaces
  - type: Workspace Overview
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/workspace-overview
  - type: JSONSchema
    url: json-schema/azure-health-services-description-list-result-schema.json
- aid: azure-health:azure-health-deid-api
  name: Microsoft Azure Health Data Services Deid API
  description: The Deid API from Microsoft Azure Health Data Services — 1 operation(s) for deid.
  humanURL: https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/overview
  baseURL: https://{endpoint}
  tags:
  - Deid
  properties:
  - type: OpenAPI
    url: openapi/azure-health-deid-api-openapi.yml
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/fhir-services
  - type: Authentication
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/authentication-authorization
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/get-started-with-fhir
  - type: SMART on FHIR
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/smart-on-fhir
  - type: Search Reference
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/overview-of-search
  - type: ChangeLog
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/release-notes-2024
  - type: Pricing
    url: https://azure.microsoft.com/en-us/pricing/details/health-data-services/
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/dicom-services
  - type: DICOMweb Standard APIs Guide
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicomweb-standard-apis-with-dicom-services
  - type: Conformance Statement
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicom-services-conformance-statement-v2
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/deploy-dicom-services-in-azure
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/iot-connector-overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/iot-connector
  - type: Device Mapping Guide
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/how-to-use-device-mappings
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/get-started-with-iot
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/health-dataplane/deidentify-text/deidentify-text
  - type: SDK Overview
    url: https://learn.microsoft.com/dotnet/api/overview/azure/Health.Deidentification-readme
  - type: Service Limits
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/overview#input-requirements-and-service-limits
  - type: Documentation
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/workspaces
  - type: Workspace Overview
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/workspace-overview
  - type: JSONSchema
    url: json-schema/azure-health-deidentification-content-schema.json
  - type: JSONSchema
    url: json-schema/azure-health-deidentification-result-schema.json
- aid: azure-health:azure-health-dicomservices-api
  name: Microsoft Azure Health Data Services DicomServices API
  description: The DicomServices API from Microsoft Azure Health Data Services — 2 operation(s) for dicomservices.
  humanURL: https://learn.microsoft.com/en-us/rest/api/healthcareapis/
  baseURL: https://management.azure.com
  tags:
  - DicomServices
  properties:
  - type: OpenAPI
    url: openapi/azure-health-dicomservices-api-openapi.yml
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/fhir-services
  - type: Authentication
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/authentication-authorization
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/get-started-with-fhir
  - type: SMART on FHIR
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/smart-on-fhir
  - type: Search Reference
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/overview-of-search
  - type: ChangeLog
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/release-notes-2024
  - type: Pricing
    url: https://azure.microsoft.com/en-us/pricing/details/health-data-services/
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/dicom-services
  - type: DICOMweb Standard APIs Guide
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicomweb-standard-apis-with-dicom-services
  - type: Conformance Statement
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicom-services-conformance-statement-v2
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/deploy-dicom-services-in-azure
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/iot-connector-overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/iot-connector
  - type: Device Mapping Guide
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/how-to-use-device-mappings
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/get-started-with-iot
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/health-dataplane/deidentify-text/deidentify-text
  - type: SDK Overview
    url: https://learn.microsoft.com/dotnet/api/overview/azure/Health.Deidentification-readme
  - type: Service Limits
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/overview#input-requirements-and-service-limits
  - type: Documentation
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/workspaces
  - type: Workspace Overview
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/workspace-overview
  - type: JSONSchema
    url: json-schema/azure-health-dicom-service-schema.json
  - type: JSONSchema
    url: json-schema/azure-health-dicom-service-collection-schema.json
  - type: JSONSchema
    url: json-schema/azure-health-dicom-service-patch-resource-schema.json
- aid: azure-health:azure-health-fhirservices-api
  name: Microsoft Azure Health Data Services FhirServices API
  description: The FhirServices API from Microsoft Azure Health Data Services — 2 operation(s) for fhirservices.
  humanURL: https://learn.microsoft.com/en-us/rest/api/healthcareapis/
  baseURL: https://management.azure.com
  tags:
  - FhirServices
  properties:
  - type: OpenAPI
    url: openapi/azure-health-fhirservices-api-openapi.yml
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/fhir-services
  - type: Authentication
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/authentication-authorization
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/get-started-with-fhir
  - type: SMART on FHIR
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/smart-on-fhir
  - type: Search Reference
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/overview-of-search
  - type: ChangeLog
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/release-notes-2024
  - type: Pricing
    url: https://azure.microsoft.com/en-us/pricing/details/health-data-services/
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/dicom-services
  - type: DICOMweb Standard APIs Guide
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicomweb-standard-apis-with-dicom-services
  - type: Conformance Statement
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicom-services-conformance-statement-v2
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/deploy-dicom-services-in-azure
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/iot-connector-overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/iot-connector
  - type: Device Mapping Guide
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/how-to-use-device-mappings
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/get-started-with-iot
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/health-dataplane/deidentify-text/deidentify-text
  - type: SDK Overview
    url: https://learn.microsoft.com/dotnet/api/overview/azure/Health.Deidentification-readme
  - type: Service Limits
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/overview#input-requirements-and-service-limits
  - type: Documentation
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/workspaces
  - type: Workspace Overview
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/workspace-overview
  - type: JSONSchema
    url: json-schema/azure-health-fhir-service-schema.json
  - type: JSONSchema
    url: json-schema/azure-health-fhir-service-collection-schema.json
  - type: JSONSchema
    url: json-schema/azure-health-fhir-service-patch-resource-schema.json
- aid: azure-health:azure-health-iotconnectors-api
  name: Microsoft Azure Health Data Services IotConnectors API
  description: The IotConnectors API from Microsoft Azure Health Data Services — 4 operation(s) for iotconnectors.
  humanURL: https://learn.microsoft.com/en-us/rest/api/healthcareapis/
  baseURL: https://management.azure.com
  tags:
  - IotConnectors
  properties:
  - type: OpenAPI
    url: openapi/azure-health-iotconnectors-api-openapi.yml
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/fhir-services
  - type: Authentication
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/authentication-authorization
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/get-started-with-fhir
  - type: SMART on FHIR
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/smart-on-fhir
  - type: Search Reference
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/overview-of-search
  - type: ChangeLog
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/release-notes-2024
  - type: Pricing
    url: https://azure.microsoft.com/en-us/pricing/details/health-data-services/
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/dicom-services
  - type: DICOMweb Standard APIs Guide
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicomweb-standard-apis-with-dicom-services
  - type: Conformance Statement
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicom-services-conformance-statement-v2
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/deploy-dicom-services-in-azure
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/iot-connector-overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/iot-connector
  - type: Device Mapping Guide
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/how-to-use-device-mappings
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/get-started-with-iot
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/health-dataplane/deidentify-text/deidentify-text
  - type: SDK Overview
    url: https://learn.microsoft.com/dotnet/api/overview/azure/Health.Deidentification-readme
  - type: Service Limits
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/overview#input-requirements-and-service-limits
  - type: Documentation
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/workspaces
  - type: Workspace Overview
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/workspace-overview
  - type: JSONSchema
    url: json-schema/azure-health-iot-fhir-destination-schema.json
  - type: JSONSchema
    url: json-schema/azure-health-iot-connector-schema.json
  - type: JSONSchema
    url: json-schema/azure-health-iot-fhir-destination-collection-schema.json
  - type: JSONSchema
    url: json-schema/azure-health-iot-connector-collection-schema.json
  - type: JSONSchema
    url: json-schema/azure-health-iot-connector-patch-resource-schema.json
- aid: azure-health:azure-health-jobs-api
  name: Microsoft Azure Health Data Services Jobs API
  description: The Jobs API from Microsoft Azure Health Data Services — 4 operation(s) for jobs.
  humanURL: https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/overview
  baseURL: https://{endpoint}
  tags:
  - Job
  tags_raw:
  - Jobs
  properties:
  - type: OpenAPI
    url: openapi/azure-health-jobs-api-openapi.yml
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/fhir-services
  - type: Authentication
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/authentication-authorization
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/get-started-with-fhir
  - type: SMART on FHIR
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/smart-on-fhir
  - type: Search Reference
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/overview-of-search
  - type: ChangeLog
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/release-notes-2024
  - type: Pricing
    url: https://azure.microsoft.com/en-us/pricing/details/health-data-services/
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/dicom-services
  - type: DICOMweb Standard APIs Guide
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicomweb-standard-apis-with-dicom-services
  - type: Conformance Statement
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicom-services-conformance-statement-v2
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/deploy-dicom-services-in-azure
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/iot-connector-overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/iot-connector
  - type: Device Mapping Guide
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/how-to-use-device-mappings
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/get-started-with-iot
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/health-dataplane/deidentify-text/deidentify-text
  - type: SDK Overview
    url: https://learn.microsoft.com/dotnet/api/overview/azure/Health.Deidentification-readme
  - type: Service Limits
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/overview#input-requirements-and-service-limits
  - type: Documentation
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/workspaces
  - type: Workspace Overview
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/workspace-overview
  - type: JSONSchema
    url: json-schema/azure-health-deidentification-job-schema.json
  - type: JSONSchema
    url: json-schema/azure-health-paged-deidentification-document-details-schema.json
  - type: JSONSchema
    url: json-schema/azure-health-paged-deidentification-job-schema.json
- aid: azure-health:azure-health-privatelinkresources-api
  name: Microsoft Azure Health Data Services PrivateLinkResources API
  description: The PrivateLinkResources API from Microsoft Azure Health Data Services — 2 operation(s) for privatelinkresources.
  humanURL: https://learn.microsoft.com/en-us/rest/api/healthcareapis/
  baseURL: https://management.azure.com
  tags:
  - PrivateLinkResources
  properties:
  - type: OpenAPI
    url: openapi/azure-health-privatelinkresources-api-openapi.yml
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/fhir-services
  - type: Authentication
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/authentication-authorization
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/get-started-with-fhir
  - type: SMART on FHIR
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/smart-on-fhir
  - type: Search Reference
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/overview-of-search
  - type: ChangeLog
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/release-notes-2024
  - type: Pricing
    url: https://azure.microsoft.com/en-us/pricing/details/health-data-services/
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/dicom-services
  - type: DICOMweb Standard APIs Guide
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicomweb-standard-apis-with-dicom-services
  - type: Conformance Statement
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicom-services-conformance-statement-v2
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/deploy-dicom-services-in-azure
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/iot-connector-overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/iot-connector
  - type: Device Mapping Guide
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/how-to-use-device-mappings
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/iot/get-started-with-iot
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/health-dataplane/deidentify-text/deidentify-text
  - type: SDK Overview
    url: https://learn.microsoft.com/dotnet/api/overview/azure/Health.Deidentification-readme
  - type: Service Limits
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/overview#input-requirements-and-service-limits
  - type: Documentation
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/workspaces
  - type: Workspace Overview
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/workspace-overview
  - type: JSONSchema
    url: json-schema/azure-health-private-link-resource-description-schema.json
  - type: JSONSchema
    url: json-schema/azure-health-private-link-resource-list-result-description-schema.json
- aid: azure-health:azure-health-proxy-api
  name: Microsoft Azure Health Data Services Proxy API
  description: The Proxy API from Microsoft Azure Health Data Services — 3 operation(s) for proxy.
  humanURL: https://learn.microsoft.com/en-us/rest/api/healthcareapis/
  baseURL: https://management.azure.com
  tags:
  - Proxy
  properties:
  - type: OpenAPI
    url: openapi/azure-health-proxy-api-openapi.yml
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/fhir-services
  - type: Authentication
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/authentication-authorization
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/get-started-with-fhir
  - type: SMART on FHIR
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/smart-on-fhir
  - type: Search Reference
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/overview-of-search
  - type: ChangeLog
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/release-notes-2024
  - type: Pricing
    url: https://azure.microsoft.com/en-us/pricing/details/health-data-services/
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/overview
  - type: REST API Reference
    url: https://learn.microsoft.com/en-us/rest/api/healthcareapis/dicom-services


# --- truncated at 32 KB (51 KB total) ---
# Full source: https://artifacts.apis.io/azure-health/apis.yml

Microsoft Azure Health Data Services API — frequently asked questions

Does Microsoft Azure Health Data Services have an API?

Yes. APIs.io lists 13 APIs from Microsoft Azure Health Data Services, including Microsoft Azure Health Data Services Collection API, Microsoft Azure Health Data Services Deid API and Microsoft Azure Health Data Services DicomServices API, and 10 more.

Is there an OpenAPI specification for the Microsoft Azure Health Data Services API?

Yes. APIs.io indexes 13 OpenAPI specifications for Microsoft Azure Health Data Services, each linked for download from this page.

How do I authenticate with the Microsoft Azure Health Data Services API?

Microsoft Azure Health Data Services documents its authentication (oauth2 · 2 schemes). The details are profiled on APIs.io as Azure Health Authentication.

How much does the Microsoft Azure Health Data Services API cost?

Microsoft Azure Health Data Services publishes its prices; its De-Id plan is 0.0 as of 2026-11-05. APIs.io lists 15 pricing plans for Microsoft Azure Health Data Services, with each plan's price, limits and inclusions under Pricing on this page.

Is the Microsoft Azure Health Data Services API ready for AI agents?

Microsoft Azure Health Data Services has a Kin Score of 75.2 out of 100 (exemplar) and an Agent Readiness score of 37.1 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/azure-health"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/azure-health/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/azure-health/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.