| Troubleshooting | L37-L46 | Diagnosing and fixing Azure Health Data Services issues: FHIR access tokens, event delivery problems, $convert-data failures, identity provider setup, and known platform limitations. |
| Best Practices | L47-L55 | Best practices for securing and managing Azure Health Data Services: BCDR planning, CMK encryption for FHIR/DICOM, performance tuning, and safely running FHIR reindex jobs. |
| Decision Making | L56-L64 | Planning and executing migrations from Azure API for FHIR and SMART on FHIR proxy to Azure Health Data Services, plus answers to common Azure API for FHIR questions. |
| Architecture & Design Patterns | L65-L71 | Architectural patterns for FHIR, DICOM, and de-identification: disaster recovery setup, reliable anonymization services, DICOM + Data Lake integration, and digital pathology workflow design. |
| Limits & Quotas | L72-L77 | Scaling and performance limits for Azure API for FHIR and DICOM: autoscale setup, throughput and request caps, storage and size constraints, and service-specific behavior under load. |
| Security | L78-L117 | Configuring auth, RBAC, identities, keys, policies, network and client app security for Azure Health Data Services (FHIR, DICOM, de-identification) including tokens, CMK, Private Link, and SMART on FHIR. |
| Configuration | L118-L168 | Configuring Azure Health Data Services (FHIR and DICOM): CORS, logging, bulk import/export, de-identification, profiles, search, history/versioning, events, and standards-specific integrations. |
| Integrations & Coding Patterns | L169-L206 | Using FHIR and DICOM APIs with cURL/SDKs, bulk export/import, search, de-identification, events, and integrating with Synapse, ADF, Logic Apps, and Da Vinci/CARIN implementations |
| Deployment | L207-L220 | How to deploy and move Azure Health Data Services (FHIR, DICOM, de-identification, workspaces) using portal, ARM, Bicep, CLI, PowerShell, and check regional availability |
