azure-health-data-services
About azure-health-data-services
azure-health-data-services is a guidance skill for teams using Azure Health Data Services. It combines local references with remote documentation retrieval across FHIR, DICOM, security, integration, and deployment topics.
Key features
- 01FHIR and DICOM troubleshooting
- 02Architecture and migration guidance
- 03Security and access configuration
- 04Limits, performance, and scaling
- 05Integration and deployment patterns
Use cases
- 01Diagnosing FHIR token or event delivery issues
- 02Planning a migration to Health Data Services
- 03Configuring secure FHIR or DICOM access
MCP support
The skill can fetch Microsoft documentation using the mcp_microsoftdocs microsoft_docs_fetch tool, with webpage fetching as a fallback.
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ microsoftdocs/ agent-skills --skill azure-health-data-servicesAfter installing, type/azure-health-data-servicesin Claude Code to confirm it loaded.
Details
From the project READMEAzure Health Data Services Skill
This skill provides expert guidance for Azure Health Data Services. Covers troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. It combines local quick-reference content with remote documentation fetching capabilities.
How to Use This Skill
IMPORTANT for Agent: Use the Category Index below to locate relevant sections. For categories with line ranges (e.g.,
L35-L120), useread_filewith the specified lines. For categories with file links (e.g.,[security.md](security.md)), useread_fileon the linked reference file
IMPORTANT for Agent: If
metadata.generated_atis more than 3 months old, suggest the user pull the latest version from the repository. Ifmcp_microsoftdocstools are not available, suggest the user install it: Installation Guide
This skill requires network access to fetch documentation content:
- Preferred: Use
mcp_microsoftdocs:microsoft_docs_fetchwith query stringfrom=learn-agent-skill. Returns Markdown. - Fallback: Use
fetch_webpagewith query stringfrom=learn-agent-skill&accept=text/markdown. Returns Markdown.
Category Index
| Category | Lines | Description |
|---|---|---|
| Troubleshooting | L37-L46 | Diagnosing and fixing Azure Health Data Services issues: FHIR token validation, event delivery, $convert-data errors/performance, identity provider setup, and known service limitations. |
| Best Practices | L47-L54 | BCDR planning, CMK encryption for FHIR/DICOM, FHIR performance tuning, and safe configuration/operation of FHIR reindex jobs |
| Decision Making | L55-L60 | Guidance for planning and executing migrations from Azure API for FHIR to Azure Health Data Services, including architecture, data, and operational considerations. |
| Architecture & Design Patterns | L61-L67 | Designing resilient Azure Health Data Services solutions, including BCDR planning, DICOM architecture with Data Lake, and digital pathology workflows using the DICOM service. |
| Limits & Quotas | L68-L75 | Scaling, capacity, DR, and deprecation behavior for Azure API for FHIR, plus DICOM service performance, storage, and operational limits and requirements. |
| Security | L76-L116 | Securing Azure Health Data Services: Entra app registration, auth tokens, RBAC, CMK encryption, Private Link/network lockdown, SMART on FHIR, B2C/External ID, and policy/compliance setup. |
| Configuration | L117-L165 | Configuring Azure FHIR and DICOM services: CORS, logging, events, profiles, search, import/export (incl. bulk, de-identified), versioning, and de-identification monitoring and formats. |
| Integrations & Coding Patterns | L166-L203 | Patterns and code samples for calling FHIR/DICOM APIs, bulk import/export, de-identification, events, and standards (CARIN/Da Vinci), plus integration with Synapse, ADF, Logic Apps, and tools like cURL/SDKs. |
| Deployment | L204-L220 | Deploying Azure Health Data Services components (FHIR, DICOM, de-identification, workspaces) using portal, ARM, Bicep, CLI, PowerShell, and moving FHIR across subscriptions |
Troubleshooting
| Topic | URL |
|---|---|
| Troubleshoot Azure API for FHIR access token validation | https://learn.microsoft.com/en-us/azure/healthcare-apis/azure-api-for-fhir/azure-api-fhir-access-token-validation |
| Resolve common Azure Health Data Services event issues | https://learn.microsoft.com/en-us/azure/healthcare-apis/events/events-faqs |
| Troubleshoot event delivery in Azure Health Data Services | https://learn.microsoft.com/en-us/azure/healthcare-apis/events/events-troubleshooting-guide |
| Troubleshoot $convert-data errors and performance | https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/convert-data-troubleshoot |
| Troubleshoot FHIR service identity provider setup | https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/troubleshoot-identity-provider-configuration |
| Review known issues for Azure Health Data Services | https://learn.microsoft.com/en-us/azure/healthcare-apis/known-issues |
Best Practices
| Topic | URL |
|---|---|
| Apply customer-managed key best practices to DICOM service | https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/customer-managed-keys |
| Apply customer-managed key best practices for FHIR | https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/customer-managed-keys |
| Apply performance best practices for Azure FHIR service | https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/fhir-best-practices |
| Safely run and throttle FHIR reindex jobs | https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/how-to-run-a-reindex |
Decision Making
| Topic | URL |
|---|---|
| Plan and execute migration from Azure API for FHIR | https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/migration-faq |
| Plan and execute migration from Azure API for FHIR | https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/migration-strategies |
Architecture & Design Patterns
| Topic | URL |
|---|---|
| Plan BCDR for Azure Health Data Services | https://learn.microsoft.com/en-us/azure/healthcare-apis/business-continuity-disaster-recovery |
| Architect DICOM service with Azure Data Lake Storage | https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicom-data-lake |
| Implement digital pathology workflows with DICOM service | https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicom-digital-pathology |
Limits & Quotas
| Topic | URL |
|---|---|
| Configure autoscale and capacity for Azure API for FHIR | https://learn.microsoft.com/en-us/azure/healthcare-apis/azure-api-for-fhir/autoscale-azure-api-fhir |
| Configure disaster recovery for Azure API for FHIR | https://learn.microsoft.com/en-us/azure/healthcare-apis/azure-api-for-fhir/disaster-recovery |
| Understand Azure API for FHIR deprecation behavior | https://learn.microsoft.com/en-us/azure/healthcare-apis/azure-api-for-fhir/fhir-faq |
| Understand DICOM service requirements and limits | https://learn.microsoft.com/en-us/azure/healthcare-apis/dicom/dicom-services-faqs |