Healthcare Apis

246
Total Pages
187
Linux-Friendly Pages
59
Pages with Bias
24.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

302 issues found
Showing 1-25 of 302 flagged pages
Healthcare Apis De-identify multiple documents with the de-identification service in python ...pis/deidentification/quickstart-asynchronous-python.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively providing PowerShell examples for Azure CLI commands and resource management tasks. There are no Bash or Linux shell equivalents for these steps, and PowerShell is explicitly mentioned as the terminal of choice. This may disadvantage Linux or macOS users, who typically use Bash or other Unix shells.
Recommendations
  • Provide Bash equivalents for all Azure CLI and resource management commands alongside PowerShell examples.
  • Use cross-platform, shell-agnostic syntax for Azure CLI commands where possible (e.g., avoid PowerShell variable assignment and interpolation).
  • Explicitly mention that Azure CLI commands can be run in Bash, PowerShell, or other supported shells.
  • Include a note or section for Linux/macOS users, highlighting any differences or considerations.
  • When introducing command-line examples, alternate between Windows and Linux shells, or present both together.
GitHub Create Pull Request
Healthcare Apis Quickstart: deploy the Azure Health Data Services de-identification service with Bicep ...s/healthcare-apis/deidentification/quickstart-bicep.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and PowerShell requirements are listed in the prerequisites. There is no mention of Linux-specific considerations, nor are there examples using Bash or shell scripting, which are common on Linux. The documentation assumes familiarity with PowerShell and does not clarify cross-platform compatibility, potentially leading to Windows bias.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and highlight its use for Linux/macOS users.
  • Move Azure CLI examples before PowerShell examples to emphasize platform neutrality.
  • Remove or de-emphasize PowerShell prerequisites for users on non-Windows platforms.
  • Add notes or sections for Linux/macOS users, including any environment-specific setup tips.
  • Include Bash or shell script examples where appropriate.
  • Explicitly state that all steps can be performed on Linux/macOS using Azure CLI.
GitHub Create Pull Request
Healthcare Apis Register a client application for the DICOM service in Microsoft Entra ID ...es/healthcare-apis/dicom/dicom-register-application.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the section about creating self-signed certificates, where only the PowerShell command 'New-SelfSignedCertificate' is mentioned as a tool for certificate creation. No Linux or cross-platform alternatives (such as OpenSSL) are provided, and the example is specific to Windows environments. The rest of the documentation is largely platform-neutral, focusing on Azure portal UI steps, but the certificate creation step is Windows-centric.
Recommendations
  • Add instructions and examples for creating self-signed certificates on Linux and macOS using OpenSSL.
  • Mention cross-platform tools for certificate management, not just PowerShell.
  • Where command-line tools are referenced, provide equivalent commands for both Windows and Linux/macOS.
  • Explicitly state that the process can be completed on any OS, and link to relevant cross-platform documentation.
GitHub Create Pull Request
Healthcare Apis Configure Azure RBAC role for the FHIR service in Azure Health Data Services .../main/articles/healthcare-apis/configure-azure-rbac.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates bias toward Windows environments by referencing PowerShell as the exclusive method for creating custom roles, without mentioning cross-platform alternatives such as Azure CLI or REST API. No Linux-specific or platform-neutral examples are provided for command-line operations, and the only tool for advanced role management is Windows-centric.
Recommendations
  • Include Azure CLI examples for creating custom roles, as CLI is cross-platform and widely used on Linux and macOS.
  • Reference REST API methods for role management, providing platform-neutral instructions.
  • Explicitly mention that PowerShell is available on Linux and macOS, or clarify when instructions are Windows-specific.
  • Add cURL or Bash script examples for common tasks to improve parity for Linux users.
  • Ensure that any screenshots or step-by-step instructions do not assume a Windows environment unless necessary, and provide alternatives where possible.
GitHub Create Pull Request
Healthcare Apis Quickstart: Deploy Azure API for FHIR using an ARM template ...i-for-fhir/azure-api-fhir-resource-manager-template.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as a primary automation option, with detailed, interactive PowerShell scripts and instructions. In the CLI prerequisites, Bash is mentioned, but the example suggests Git Bash (a Windows-oriented tool) as the default, rather than native Bash on Linux/macOS. The order of tabs and examples generally places Windows-centric tools (Portal, PowerShell) before CLI, and the CLI instructions reference Bash only in the context of Windows. There are no explicit Linux/macOS examples or notes about running commands natively on those platforms.
Recommendations
  • Explicitly mention that Azure CLI commands work natively on Linux and macOS terminals, not just Bash on Windows.
  • Provide examples or notes for running CLI commands on Linux/macOS, including shell differences if relevant.
  • Avoid suggesting Windows-specific tools (e.g., Git Bash) as the default Bash environment; mention alternatives for Linux/macOS.
  • Consider reordering tabs or examples so that CLI (cross-platform) is presented before PowerShell (Windows-centric).
  • Add a note clarifying platform compatibility for all tools, and ensure parity in troubleshooting steps for Linux/macOS users.
GitHub Create Pull Request
Healthcare Apis Data conversion for Azure API for FHIR ...les/healthcare-apis/azure-api-for-fhir/convert-data.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by primarily referencing Windows-centric tools and workflows. The instructions for enabling Managed Identity, assigning roles, and registering ACR servers are focused on the Azure portal (a GUI, most commonly used on Windows) and Azure CLI, but do not provide explicit Linux shell or cross-platform command examples. The mention of installing the Azure Health Data Services CLI from Azure PowerShell further reinforces a Windows-first approach. There are no Linux-specific instructions, nor are there examples for Bash or other Linux-native tools. The Visual Studio Code extension is referenced without mention of Linux support, and screenshots are Windows-centric.
Recommendations
  • Include explicit Linux/Bash shell command examples for CLI steps, such as registering ACR servers and managing identities.
  • Clarify that Azure CLI is cross-platform and provide installation instructions for Linux and macOS.
  • Add notes or screenshots showing the Azure portal experience on non-Windows platforms, or clarify that the portal is web-based and OS-agnostic.
  • Mention that the Visual Studio Code extension is available on Linux and macOS, and provide installation instructions for those platforms.
  • Avoid referencing Azure PowerShell as the primary method for CLI installation; instead, highlight Azure CLI, which is cross-platform.
  • Where possible, provide parity in examples and troubleshooting steps for both Windows and Linux users.
GitHub Create Pull Request
Healthcare Apis Configure customer-managed keys for Azure API for FHIR ...thcare-apis/azure-api-for-fhir/customer-managed-key.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides configuration instructions for customer-managed keys in Azure API for FHIR, with examples using Azure Portal, PowerShell, Azure CLI, and ARM templates. However, PowerShell is featured prominently, both as a dedicated section and as the only example for ARM template deployment. There are no explicit Linux shell (bash) or cross-platform scripting examples, and PowerShell deployment is shown before CLI. This may create a perception that Windows or PowerShell is preferred or required, despite Azure CLI being cross-platform.
Recommendations
  • Add bash (Linux shell) examples for ARM template deployment, e.g., using 'az deployment group create' or 'az resource group deployment'.
  • Ensure Azure CLI examples are given equal prominence and shown before or alongside PowerShell examples.
  • Clarify that both PowerShell and CLI are cross-platform, and explicitly mention Linux/macOS compatibility.
  • Where possible, provide instructions for using bash scripts or Linux-native tools for deployment.
  • Review and balance the order of examples so that Windows-specific tools (PowerShell) do not appear before cross-platform alternatives.
GitHub Create Pull Request
Healthcare Apis SMART on FHIR - Azure API for FHIR ...es/healthcare-apis/azure-api-for-fhir/smart-on-fhir.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use PowerShell syntax, and there are no equivalent bash or Linux shell commands provided. The workflow assumes use of Windows tools (PowerShell, dotnet user-secrets) and local development patterns typical of Windows environments (e.g., localhost:5001, dotnet run). There is no mention of Linux-specific instructions, nor are cross-platform considerations addressed. Windows-centric tools and patterns are presented exclusively and before any alternatives.
Recommendations
  • Provide equivalent bash or Linux shell command examples alongside PowerShell commands.
  • Explicitly state cross-platform compatibility for all steps, especially for .NET SDK and app launcher usage.
  • Include instructions for Linux/macOS users, such as using terminal/bash, installing prerequisites, and running the app.
  • Mention any platform-specific caveats or requirements (e.g., file paths, environment variables) for Linux/macOS.
  • Where possible, use platform-agnostic commands (e.g., git, dotnet) and clarify any differences in usage.
  • Add screenshots or notes showing the process on Linux/macOS environments.
GitHub Create Pull Request
Healthcare Apis Learn how to configure Azure Storage to de-identify documents with the de-identification service .../healthcare-apis/deidentification/configure-storage.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using PowerShell syntax for all Azure CLI commands, stating 'we're using PowerShell' without offering Bash or Linux shell alternatives. Variable assignment and command chaining use PowerShell-specific patterns, which may not work in Bash or other Unix shells. No Linux or macOS terminal instructions or examples are provided, potentially hindering users on non-Windows platforms.
Recommendations
  • Provide parallel examples using Bash syntax for variable assignment and command execution, especially for Azure CLI commands.
  • Clarify that Azure CLI works cross-platform and explicitly mention support for Linux/macOS terminals.
  • Avoid PowerShell-specific constructs (e.g., $Variable, $(...)) in generic CLI documentation, or offer both PowerShell and Bash alternatives.
  • Add a note or section for Linux/macOS users, with instructions tailored to their environments.
  • Use neutral language such as 'open your terminal of choice' and show both PowerShell and Bash examples side by side.
GitHub Create Pull Request
Healthcare Apis Configure Azure RBAC for the DICOM service - Azure Health Data Services ...es/healthcare-apis/dicom/dicom-configure-azure-rbac.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing Azure PowerShell for creating custom roles, without mentioning or providing examples for Linux-friendly alternatives such as Azure CLI. There are no Linux-specific instructions or examples, and the only automation tool referenced is PowerShell, which is primarily associated with Windows environments.
Recommendations
  • Include Azure CLI examples for creating custom roles, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that both PowerShell and CLI can be used, and provide links to equivalent CLI documentation.
  • Add notes or sections for Linux/macOS users, clarifying that all steps can be performed on non-Windows platforms using CLI or portal.
  • Avoid implying PowerShell is the only option for automation or scripting; present CLI and PowerShell options side-by-side.
GitHub Create Pull Request
Healthcare Apis Get started with the FHIR service in Azure Health Data Services ...articles/healthcare-apis/fhir/get-started-with-fhir.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation frequently references PowerShell as a primary scripting tool and often lists it before Azure CLI or REST API, suggesting a Windows-first approach. There are multiple mentions of PowerShell for creating resources, registering applications, and obtaining access tokens, with no explicit Linux shell (bash) or macOS examples. Windows-centric tools like Power BI are highlighted for data visualization, and there is no mention of Linux-specific alternatives or guidance for non-Windows environments.
Recommendations
  • Ensure that Azure CLI (bash) examples are provided alongside or before PowerShell examples, especially for resource creation and management.
  • Include explicit Linux/macOS shell command examples for common tasks (e.g., using Azure CLI in bash, using curl for API calls).
  • Mention cross-platform tools for data visualization, such as Jupyter Notebooks or open-source BI tools, alongside Power BI.
  • Clarify that all steps can be performed on Linux/macOS and provide links to platform-specific guidance where available.
  • Review sample scripts and documentation links to ensure Linux parity and highlight any platform-specific requirements or differences.
GitHub Create Pull Request
Healthcare Apis What is the workspace? - Azure Health Data Services ...ob/main/articles/healthcare-apis/workspace-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by mentioning PowerShell as a deployment option before CLI, Terraform, and .NET SDK, and by not providing explicit Linux or cross-platform examples. The deployment instructions and tooling references lean toward Windows-centric tools and patterns, with no mention of Bash, Linux shell, or platform-specific considerations for non-Windows users.
Recommendations
  • Provide explicit Linux and macOS examples alongside PowerShell, such as Bash or Azure CLI commands.
  • List cross-platform tools (Azure CLI, Terraform) before Windows-specific tools (PowerShell) to avoid Windows-first ordering.
  • Clarify that all deployment methods (PowerShell, CLI, Terraform, .NET SDK) are available on Linux and macOS, not just Windows.
  • Include notes or links to platform-specific setup guides for Linux and macOS users.
  • Ensure screenshots and UI references do not assume a Windows environment unless necessary.
GitHub Create Pull Request
Healthcare Apis Use Microsoft Entra External ID to grant access to the FHIR service in Azure Health Data Services .../healthcare-apis/fhir/azure-entra-external-id-setup.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides deployment instructions using PowerShell and Azure CLI, with explicit references to running PowerShell locally in Visual Studio Code and Azure Cloud Shell. PowerShell is a Windows-centric tool, and its examples are given before Azure CLI in each section. There are no Linux-specific shell examples (e.g., bash scripts outside Azure CLI), nor are there references to Linux-native tools or environments. The instructions for running scripts locally assume a Windows environment (PowerShell, Visual Studio Code), and there is no mention of Linux terminal usage or alternative Linux workflows.
Recommendations
  • Add explicit instructions and examples for running Azure CLI commands in native Linux terminals, including any required environment setup.
  • Provide bash script equivalents for PowerShell examples, especially for variable assignment and resource deployment.
  • Clarify that Azure CLI can be run natively on Linux and macOS, not just in Azure Cloud Shell.
  • Remove or balance references to 'PowerShell locally in Visual Studio Code' with 'bash in Linux terminal' or 'macOS Terminal'.
  • Include troubleshooting notes for common Linux-specific issues (e.g., authentication, environment variables, file paths).
  • Where screenshots or UI instructions are given, note any differences for Linux/macOS users (e.g., browser, file dialogs).
GitHub Create Pull Request
Healthcare Apis Configure export settings in FHIR service - Azure Health Data Services ...articles/healthcare-apis/fhir/configure-export-data.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell commands for configuring Azure Storage networking, with no equivalent examples for Linux users (e.g., Bash, Azure CLI). The use of PowerShell as the sole automation tool and the absence of cross-platform command-line instructions make it less accessible for Linux or macOS users.
Recommendations
  • Provide Azure CLI (az) command equivalents for all PowerShell instructions, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Include Bash script examples for relevant automation steps, especially for Linux environments.
  • Explicitly mention that PowerShell commands can be run on Linux/macOS with PowerShell Core, or provide links to installation instructions.
  • Add a section or note clarifying platform compatibility and offering guidance for non-Windows users.
  • Ensure screenshots and UI instructions do not assume a Windows-only environment (e.g., avoid referencing Windows-specific UI elements unless necessary).
GitHub Create Pull Request
Healthcare Apis Deploy Azure Health Data Services FHIR service using Bicep ...in/articles/healthcare-apis/fhir/fhir-service-bicep.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias. PowerShell examples and references are presented alongside Azure CLI, but Windows-specific tools (like Git Bash for Windows) are mentioned before native Linux options. The prerequisites and examples often reference Windows-first patterns, such as recommending Git Bash (a Windows solution) for Bash shells and listing Azure PowerShell as a primary option. There is no explicit mention of Linux-native shells or tools, and the CLI instructions do not clarify that they work natively on Linux/macOS. The documentation does not provide Linux-specific troubleshooting or environment setup guidance.
Recommendations
  • Explicitly mention that Azure CLI commands work natively on Linux and macOS terminals, not just in Git Bash for Windows.
  • In prerequisites, recommend standard Bash shells available on Linux/macOS (e.g., GNOME Terminal, macOS Terminal) before or alongside Git Bash for Windows.
  • Add notes or sections for Linux/macOS users, including package installation commands for Azure CLI and Bicep on those platforms.
  • Ensure parity in troubleshooting and environment setup instructions for Linux/macOS users.
  • Consider providing examples of using Azure CLI in Linux/macOS environments, and clarify that PowerShell is optional for those platforms.
GitHub Create Pull Request
Healthcare Apis Azure Health Data Services known issues ...ocs/blob/main/articles/healthcare-apis/known-issues.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page provides a workaround for configuring the storage account for FHIR export using only PowerShell commands and the Az PowerShell module, which are Windows-centric tools. There are no equivalent examples or instructions for Linux users (e.g., using Azure CLI or Bash), nor is there mention of cross-platform alternatives. This demonstrates a bias towards Windows environments and tools, potentially making it harder for Linux users to follow the guidance.
Recommendations
  • Add equivalent Azure CLI (az) commands for configuring the storage account for export, which work on both Linux and Windows.
  • Explicitly mention that the workaround can be performed on Linux/macOS using Azure CLI or Bash, and provide those examples.
  • Where PowerShell is used, clarify platform requirements and offer guidance for non-Windows users.
  • Review future documentation for parity in examples and tooling, ensuring Linux users are not excluded.
GitHub Create Pull Request
Healthcare Apis Use Azure Active Directory B2C to grant access to the FHIR service in Azure Health Data Services ...in/articles/healthcare-apis/fhir/azure-ad-b2c-setup.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides deployment instructions primarily using PowerShell and Azure CLI, with explicit recommendations to run PowerShell locally in Visual Studio Code—a Windows-centric workflow. PowerShell examples are presented first in each code section. There are no Linux-specific shell examples (e.g., bash scripts outside Azure CLI), nor is there mention of Linux-native tools or workflows. The guidance assumes familiarity with Windows tools and environments, and does not address Linux-specific considerations (such as package installation, authentication issues, or shell differences).
Recommendations
  • Add explicit Linux shell (bash) examples for all deployment steps, including ARM template deployment and resource group creation.
  • Clarify that Azure CLI commands work on both Windows and Linux, and provide any necessary Linux-specific setup instructions (e.g., installation, authentication differences).
  • Remove or balance references to running PowerShell locally in Visual Studio Code with equivalent instructions for Linux users (e.g., running Azure CLI in a native terminal).
  • Mention cross-platform compatibility for all tools, and provide troubleshooting notes for common Linux issues (such as permission errors, environment variables, etc.).
  • Consider adding screenshots or instructions for Linux environments where relevant, especially for steps involving local execution.
GitHub Create Pull Request
Healthcare Apis Configure import settings in the FHIR service - Azure Health Data Services ...articles/healthcare-apis/fhir/configure-import-data.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by providing PowerShell-only examples for configuring Azure Storage networking and permissions, referencing the Az.Storage PowerShell module, and omitting equivalent Linux or cross-platform CLI instructions. The use of PowerShell commands is presented as the default method, with no mention of Azure CLI, Bash, or other Linux-native tools. This may disadvantage users working on Linux or macOS environments.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, especially for configuring storage account network rules and permissions.
  • Explicitly mention cross-platform alternatives (e.g., Azure CLI, Bash scripts) alongside PowerShell, and clarify which tools are available on Linux/macOS.
  • Reorder sections so that cross-platform or OS-neutral methods (such as REST API or Azure CLI) are presented before or alongside Windows/PowerShell methods.
  • Include notes or links to installation instructions for Azure CLI and other relevant tools for Linux/macOS users.
  • Review screenshots and UI instructions to ensure they are not Windows-centric, and add clarifications for any OS-specific steps.
GitHub Create Pull Request
Healthcare Apis Deploy Azure Health Data Services FHIR service using ARM template ...re-apis/fhir/fhir-service-resource-manager-template.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently presenting PowerShell instructions and references before CLI/Bash alternatives. It suggests using PowerShell locally and mentions Windows-specific tools (e.g., Git Bash for Windows) as the default Bash shell. There is a lack of explicit Linux-native examples, and the CLI instructions reuse Windows-style file paths (e.g., 'src\templates\fhirtemplate.json'), which are not standard on Linux. The overall structure and language assume a Windows environment as the primary context.
Recommendations
  • Present CLI/Bash instructions before or alongside PowerShell to avoid Windows-first ordering.
  • Include explicit Linux-native examples, such as running Azure CLI in a standard Linux terminal and using Linux file paths (e.g., 'src/templates/fhirtemplate.json').
  • Mention Linux and macOS compatibility for Azure CLI and provide installation links for those platforms.
  • Avoid recommending Windows-specific Bash shells (like Git Bash for Windows) as the default; instead, reference native Bash on Linux/macOS.
  • Clarify that both PowerShell and CLI can be used on Windows, Linux, and macOS, and provide guidance for each OS where relevant.
  • Review all code samples for OS-specific syntax (e.g., path separators, environment variable usage) and provide alternatives or notes for cross-platform usage.
GitHub Create Pull Request
Healthcare Apis Access Azure Health Data Services with cURL .../blob/main/articles/healthcare-apis/fhir/using-curl.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell in prerequisites and examples, referencing Windows tools (PowerShell, Visual Studio Code, Git Bash), and lacking explicit Linux shell examples. The CLI section mentions Bash only as an optional install for Windows users, and does not provide native Linux instructions or address Linux-specific environments.
Recommendations
  • Add explicit Linux prerequisites, such as instructions for using native Bash/Zsh shells and package managers (apt, yum, etc.) for installing Azure CLI and cURL.
  • Provide example commands for Linux/macOS environments, including shell syntax (e.g., export, $(), etc.) and environment setup.
  • Reorder sections so that CLI/Bash examples are presented before or alongside PowerShell, to avoid Windows-first impression.
  • Mention Linux and macOS compatibility for all tools and commands, and clarify any platform-specific differences.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., permissions, path differences) when using cURL and Azure CLI.
GitHub Create Pull Request
Healthcare Apis SMART on FHIR - Azure Health Data Services ...ob/main/articles/healthcare-apis/fhir/smart-on-fhir.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by providing only PowerShell scripts and commands for key setup steps (e.g., reply URL encoding, running the app launcher, setting secrets), and by referencing Windows-centric tools and patterns (PowerShell, dotnet user-secrets) without Linux or cross-platform alternatives. There are no Bash or Linux shell equivalents, nor any mention of how to perform these steps on Linux or macOS. The examples and instructions assume a Windows environment, potentially excluding or confusing Linux users.
Recommendations
  • Provide equivalent Bash/Linux shell scripts for reply URL encoding and other scripting steps.
  • Explicitly mention cross-platform compatibility for .NET commands and clarify any OS-specific requirements.
  • Include instructions for installing and running the SMART on FHIR app launcher on Linux/macOS, including any necessary environment setup.
  • Reference Linux tools (e.g., curl, openssl) where appropriate, and offer alternative commands for common tasks.
  • Add notes or sections highlighting differences or considerations for Linux/macOS users, especially for authentication, file paths, and permissions.
GitHub Create Pull Request
Healthcare Apis Introduction to Azure Health Data Services ...es/healthcare-apis/health-data-services-get-started.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It repeatedly references PowerShell and Azure CLI scripts for client application registration and access token retrieval, with no mention of Bash or Linux-specific shell usage. Windows tools (PowerShell, .NET C#) are listed before cross-platform or Linux-friendly tools (cURL, Python), and there are no explicit Linux examples or instructions. The documentation assumes familiarity with Windows-centric patterns and does not provide parity for Linux users.
Recommendations
  • Include explicit Bash and Linux shell examples alongside PowerShell for all command-line instructions.
  • List cross-platform tools (cURL, Python, REST client) before Windows-specific tools (PowerShell, .NET C#) when enumerating options.
  • Add step-by-step instructions for Linux users, including authentication and resource management using Bash and Azure CLI.
  • Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux (Bash).
  • Ensure screenshots and UI references do not assume a Windows environment unless necessary.
  • Review all tool mentions to ensure Linux equivalents are provided and described.
GitHub Create Pull Request
Healthcare Apis Choose a deployment method for the MedTech service - Azure Health Data Services ...n/articles/healthcare-apis/iot/deploy-choose-method.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently mentioning Azure PowerShell before Azure CLI in deployment method descriptions, and by referencing PowerShell as a primary automation tool. There are no explicit Linux-specific examples or references to Linux-native tools, and no mention of Bash or shell scripting. The documentation does not provide parity for Linux users in terms of examples or tool recommendations.
Recommendations
  • Alternate the order of Azure PowerShell and Azure CLI mentions, or mention Azure CLI first to reflect its cross-platform nature.
  • Include explicit examples or references for Linux users, such as Bash scripts or instructions for using Azure CLI on Linux.
  • Clarify that Azure CLI is cross-platform and highlight its suitability for Linux and macOS environments.
  • Add notes or sections for Linux users, including troubleshooting tips or environment setup guidance.
  • Avoid implying PowerShell is the default or preferred automation tool; present CLI and PowerShell as equal options.
GitHub Create Pull Request
Healthcare Apis Register a client application in Microsoft Entra ID for the Azure Health Data Services .../main/articles/healthcare-apis/register-application.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the section about creating self-signed certificates, where only the PowerShell command (`New-SelfSignedCertificate`) is mentioned as a tool for certificate creation. No Linux or cross-platform alternatives (such as OpenSSL) are referenced, and no Linux-specific instructions or examples are provided. This may hinder users on non-Windows platforms from following the tutorial seamlessly.
Recommendations
  • Include Linux and cross-platform instructions for creating self-signed certificates, such as using OpenSSL.
  • Provide example commands for both PowerShell (Windows) and Bash (Linux/macOS) where relevant.
  • Mention platform-agnostic tools or clarify that the process can be performed on any OS, not just Windows.
  • Add notes or links to external resources for Linux/macOS users to perform equivalent tasks.
GitHub Create Pull Request
Healthcare Apis Release notes for 2021 Azure Health Data Services monthly releases ...ob/main/articles/healthcare-apis/release-notes-2021.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the 'Deploy and configure Azure Health Data Services using scripts' section, where PowerShell is mentioned first and exclusively, with no explicit mention of Bash or Linux shell scripts. While Azure CLI and ARM templates are also referenced, PowerShell is the only scripting language called out by name, and there are no examples or references to Linux-native tools or workflows. No Linux-specific instructions or parity are provided for deployment or configuration tasks.
Recommendations
  • Explicitly mention and provide Bash or Linux shell script equivalents alongside PowerShell scripts.
  • Ensure that deployment and configuration instructions include both Windows and Linux workflows, with examples for each.
  • Reference Linux-native tools (e.g., bash, curl, jq) where appropriate, and clarify cross-platform compatibility for Azure CLI and ARM templates.
  • Order tool mentions in a neutral or alternating fashion (e.g., 'PowerShell and Bash scripts'), rather than listing Windows tools first.
  • Add a note on platform compatibility for all scripts and tools, and provide troubleshooting tips for Linux users.
GitHub Create Pull Request
← Previous Page 1 of 13 Next →