Document Details
Azure Api Fhir Resource Manager Template
❌
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
powershell_heavy
⚠️
windows_tools
Summary:
The documentation demonstrates a mild Windows bias by listing PowerShell instructions and prerequisites before CLI/Bash equivalents, and by recommending Git Bash (from Git for Windows) as the Bash shell for CLI users. PowerShell is presented as a primary automation method, and the CLI section assumes a Bash shell but specifically references a Windows-centric tool (Git Bash) rather than native Linux/macOS terminals. However, Linux CLI parity is generally maintained in the examples.
Recommendations:
- In the CLI prerequisites, mention native Bash shells on Linux and macOS first, then mention Git Bash for Windows users as an alternative.
- Reorder the sections so that CLI (cross-platform) instructions appear before PowerShell (Windows-centric) instructions, or clarify that both are equally supported.
- In the prerequisites and instructions, avoid phrasing that implies PowerShell is the default or preferred automation tool.
- Explicitly state that all CLI examples work natively on Linux and macOS terminals, and provide any necessary notes for Windows users.
- Where possible, provide links or notes for installing Bash on all platforms, not just Git Bash for Windows.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-09-11 00:00 | #108 | completed | ✅ Clean |
| 2025-08-11 00:00 | #77 | completed | ✅ Clean |
| 2025-08-10 00:00 | #76 | completed | ✅ Clean |
| 2025-08-09 00:00 | #75 | completed | ✅ Clean |
| 2025-08-08 00:00 | #74 | completed | ✅ Clean |
| 2025-08-07 00:00 | #73 | completed | ✅ Clean |
| 2025-08-06 00:00 | #72 | completed | ✅ Clean |
| 2025-08-05 00:00 | #71 | completed | ✅ Clean |
| 2025-08-03 00:00 | #69 | completed | ✅ Clean |
| 2025-08-01 00:00 | #67 | completed | ✅ Clean |
| 2025-07-31 00:00 | #66 | completed | ✅ Clean |
| 2025-07-30 00:00 | #65 | completed | ✅ Clean |
| 2025-07-29 00:01 | #64 | completed | ✅ Clean |
| 2025-07-28 00:00 | #63 | completed | ✅ Clean |
| 2025-07-27 00:00 | #62 | completed | ✅ Clean |
| 2025-07-26 00:01 | #61 | completed | ✅ Clean |
| 2025-07-25 00:00 | #60 | completed | ✅ Clean |
| 2025-07-13 21:37 | #48 | completed | ❌ Biased |
| 2025-07-12 23:44 | #41 | in_progress | ❌ Biased |
Flagged Code Snippets
---
> [!NOTE]
> The deployment takes a few minutes to complete. Note the names for the Azure API for FHIR service and the resource group, for use in reviewing deployed resources.
## Review deployed resources
# [Portal](#tab/azure-portal)
Follow these steps to see an overview of your new Azure API for FHIR service:
1. In the [Azure portal](https://portal.azure.com), search for and select **Azure API for FHIR**.
2. In the FHIR list, select your new service. The **Overview** page for the new Azure API for FHIR service appears.
3. To validate that the new FHIR API account is provisioned, select the link next to **FHIR metadata endpoint** to fetch the FHIR API capability statement. The link has a format of `https://<service-name>.azurehealthcareapis.com/metadata`. If the account is provisioned, a JSON file is displayed.
# [PowerShell](#tab/PowerShell)
Run the following interactive code to view details about your Azure API for FHIR service. You have to enter the name and resource group of the new service.