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 26-50 of 302 flagged pages
Healthcare Apis Register a client application in Microsoft Entra ID using CLI and REST API - Azure Health Data Services ...icles/healthcare-apis/register-application-cli-rest.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 subtle Windows bias. It references running scripts in Visual Studio Code and PowerShell, mentioning the need to add the `$` symbol for variables in PowerShell, but does not provide explicit Linux shell (bash/zsh) examples or guidance. All CLI examples use `$` variable syntax, which is compatible with bash, but the only environment-specific advice is for PowerShell users. There is no mention of Linux tools, shells, or platform-specific considerations, and the documentation does not clarify cross-platform compatibility or provide Linux-specific troubleshooting or examples.
Recommendations
  • Explicitly state that all CLI examples are compatible with bash/zsh on Linux and macOS, as well as PowerShell on Windows.
  • Provide example commands for both bash (Linux/macOS) and PowerShell (Windows), highlighting any syntax differences.
  • Include troubleshooting notes for common issues on Linux (e.g., permissions, environment variables, use of jq).
  • Mention Linux/macOS environments alongside Windows/PowerShell when discussing where scripts can be run.
  • Add a section or note about installing Azure CLI and dependencies (like jq) on Linux and macOS.
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-10 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 on creating self-signed certificates, where only the PowerShell command 'New-SelfSignedCertificate' is mentioned as a tool for certificate creation. No equivalent Linux or cross-platform methods (such as OpenSSL) are provided or referenced. This omission may hinder Linux users or those working in cross-platform environments.
Recommendations
  • Include Linux and cross-platform alternatives for certificate creation, such as OpenSSL commands.
  • Provide examples or references for performing key steps (e.g., certificate generation) on Linux/macOS systems.
  • Avoid referencing Windows-specific tools exclusively; mention platform-agnostic or widely available tools where possible.
  • Consider adding a section or note on platform differences for common tasks, ensuring parity for Linux users.
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-10 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. No Linux or cross-platform command-line examples are given, and the only tool referenced for advanced configuration 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.
  • Mention both PowerShell and CLI options when referencing automation or scripting, and link to equivalent documentation for each.
  • Add explicit notes or sections for Linux/macOS users, ensuring parity in instructions and tooling.
  • Where screenshots or UI instructions are given, clarify that these steps are platform-agnostic, and supplement with command-line alternatives for users who prefer scripts.
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-10 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 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). The guidance implicitly assumes a Windows environment and does not mention cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI (az) commands for configuring the storage account, which work on Linux, macOS, and Windows.
  • Explicitly mention that the workaround can be performed on any OS and provide Bash or shell script examples.
  • Where PowerShell is referenced, add a note or section for Linux/macOS users, describing how to achieve the same result.
  • Review future documentation to ensure parity between Windows and Linux tooling and examples, presenting cross-platform solutions side-by-side or in parallel sections.
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-10 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 Windows bias by listing PowerShell as the first deployment option and mentioning it explicitly before CLI, Terraform, or SDK alternatives. There are no Linux-specific examples, nor is there any mention of Linux shell commands or tools. The deployment instructions and tooling references are generic but prioritize Windows-centric tools and patterns, which may make it less approachable for Linux users.
Recommendations
  • Provide explicit Linux shell (bash) examples alongside PowerShell, especially for deployment and scripting tasks.
  • List cross-platform tools (Azure CLI, Terraform) before Windows-specific tools (PowerShell) to avoid implying Windows primacy.
  • Clarify that all deployment options (PowerShell, CLI, Terraform, SDK) are available and supported on Linux, macOS, and Windows.
  • Include links or references to Linux-specific documentation or quickstarts where relevant.
  • Add screenshots or walkthroughs using Linux environments in addition to Windows.
GitHub Create Pull Request
Healthcare Apis Authentication and authorization in Azure Health Data Services ...ticles/healthcare-apis/authentication-authorization.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily through its mention of Windows-centric tools (PowerShell, Visual Studio Code REST Client) before cross-platform or Linux-native alternatives. While 'curl' and 'CLI' are mentioned, there are no explicit Linux or bash examples, and the order of tool listing places Windows tools first. No Linux-specific authentication or token acquisition patterns are described, and no sample commands for Linux environments are provided.
Recommendations
  • Provide explicit Linux/bash examples for token acquisition (e.g., using curl or Azure CLI on Linux).
  • List cross-platform tools (curl, CLI) before Windows-specific tools (PowerShell, VS Code REST Client) to avoid implicit prioritization.
  • Include sample commands for both Windows (PowerShell) and Linux (bash/curl) environments.
  • Mention any platform-specific considerations for authentication flows, if applicable.
  • Clarify that all described flows and tools are supported on Linux, and link to relevant Linux documentation where available.
GitHub Create Pull Request
Healthcare Apis Configure local role-based access control (local RBAC) for Azure API for FHIR ...thcare-apis/azure-api-for-fhir/configure-local-rbac.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias by providing PowerShell examples first, referencing Visual Studio Code (commonly associated with Windows), and omitting explicit Linux/macOS shell examples. While Azure CLI commands are included, they are not shown in a Linux shell context (e.g., bash), and there is no discussion of platform-specific considerations or parity.
Recommendations
  • Provide explicit bash/Linux/macOS shell examples for Azure CLI commands, including environment variable syntax differences.
  • Clarify that Azure CLI commands work cross-platform and note any differences in usage or prerequisites for Linux/macOS users.
  • Avoid referencing Visual Studio Code as the only tested environment; mention that scripts are validated on multiple platforms (Windows, Linux, macOS) and editors.
  • Consider adding troubleshooting notes or tips for Linux/macOS users, such as authentication or path issues.
  • List Azure CLI examples before PowerShell, or present them side-by-side to avoid 'Windows first' bias.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation exhibits a Windows bias by primarily referencing Azure Portal (a GUI, most commonly used on Windows), Visual Studio Code (with no mention of Linux alternatives or parity), and Azure PowerShell/CLI commands without explicit Linux/Bash examples. There is no mention of Linux-specific tools, shell commands, or cross-platform considerations for CLI usage. All screenshots and step-by-step instructions are oriented toward the Azure Portal, which is most familiar to Windows users, and there are no examples or notes for Linux users (e.g., using Bash, shell scripting, or alternative editors).
Recommendations
  • Include explicit Linux/Bash shell examples for CLI commands, showing usage in a Linux terminal.
  • Mention that Azure CLI is cross-platform and provide instructions for installing and using it on Linux and macOS.
  • Add references to alternative editors for customizing templates (e.g., Vim, Emacs, or VS Code on Linux), and clarify that the VS Code extension works on Linux/macOS.
  • Provide screenshots or instructions for using Azure CLI exclusively, avoiding reliance on Azure Portal GUI steps.
  • Add troubleshooting notes or tips for Linux users (e.g., file permissions, networking/firewall configuration differences).
  • Ensure that all steps and tools mentioned are clearly marked as cross-platform or provide platform-specific guidance where necessary.
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-10 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 alongside the Azure portal and CLI, with detailed PowerShell examples and instructions. In the CLI prerequisites, Git Bash (a Windows-focused Bash shell) is mentioned first, and Linux-native shells are not referenced. The structure and examples assume familiarity with Windows tools and patterns, with PowerShell presented before CLI in most sections.
Recommendations
  • In CLI prerequisites, mention Linux/macOS native Bash shells before or alongside Git Bash, and clarify that Azure CLI works natively on Linux/macOS.
  • Add explicit instructions or notes for running Azure CLI commands on Linux/macOS, including shell differences if any.
  • Where PowerShell is referenced, clarify that Azure PowerShell is cross-platform and provide installation links for Linux/macOS.
  • Consider providing examples for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) in parallel, or clarify platform parity.
  • Avoid implying that Git Bash is required for CLI usage; note that any Bash shell is suitable.
  • Review ordering of sections to avoid consistently listing Windows/PowerShell before Linux/CLI options.
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-10 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 by providing PowerShell examples for key operations (including ARM template deployment), listing PowerShell before Azure CLI, and omitting any Linux-specific shell (e.g., Bash) or cross-platform scripting examples. There is no mention of Linux tools or guidance for Linux users, and PowerShell is used as the default scripting language for deployment, which may not be familiar or available to many Linux users.
Recommendations
  • Add Bash shell examples for ARM template deployment using Azure CLI (e.g., az deployment group create) to complement PowerShell scripts.
  • Explicitly mention that Azure CLI commands work cross-platform and provide sample commands in Bash syntax.
  • Reorder examples so that Azure CLI (cross-platform) appears before PowerShell, or present them side-by-side.
  • Include notes or links for Linux users on installing and using Azure CLI and alternatives to PowerShell.
  • Avoid assuming PowerShell is the default scripting environment; clarify platform requirements for each example.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell commands and examples for key steps such as reply URL encoding, repository cloning, and application configuration. There are no equivalent Linux shell (bash) or cross-platform instructions. The use of PowerShell and .NET tooling is assumed, and Windows-centric tools and patterns (e.g., PowerShell scripts, dotnet user-secrets) are presented without alternatives or parity for Linux/macOS users.
Recommendations
  • Provide equivalent bash shell scripts for reply URL encoding and other scripting steps, alongside PowerShell examples.
  • Explicitly mention cross-platform compatibility for tools (e.g., .NET SDK, git) and provide installation instructions for Linux/macOS.
  • Add notes or sections for Linux/macOS users, including how to run the sample app launcher and configure appsettings.json.
  • Where PowerShell is used, offer bash/zsh alternatives and clarify any platform-specific differences.
  • Review screenshots and UI instructions to ensure they are not Windows-specific, or add Linux/macOS variants if needed.
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-10 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 a bias towards Windows environments by referencing PowerShell as the method for creating custom roles, without mentioning Azure CLI or Bash alternatives. There are no Linux-specific examples or cross-platform command-line instructions for role assignment or verification. The documentation assumes use of the Azure portal (browser-based, cross-platform), but command-line tooling is only referenced for PowerShell, which is traditionally associated with Windows.
Recommendations
  • Include instructions and examples for creating custom roles using Azure CLI, which is cross-platform and widely used on Linux.
  • Add explicit references to Bash or shell scripting alternatives for role assignment and verification.
  • Where PowerShell is mentioned, provide equivalent Azure CLI commands side-by-side.
  • Ensure that screenshots and instructions do not imply a Windows-only environment, and clarify that all steps can be performed on Linux and macOS as well as Windows.
  • Add a section on command-line automation that covers both PowerShell and Azure CLI usage.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell syntax and variables, indicating a strong Windows bias. All command-line examples are presented in PowerShell, with no Bash or Linux shell equivalents. The tutorial explicitly states 'we're using PowerShell' and uses Windows-style variable assignment and command substitution, which may not work on Linux/macOS terminals. There is no mention of Linux or cross-platform usage, and no alternative examples for non-Windows users.
Recommendations
  • Provide equivalent Bash/Linux shell examples alongside PowerShell commands, especially for variable assignment and command substitution.
  • Clarify that Azure CLI works on multiple platforms and show how to run commands in Bash or zsh.
  • Avoid language like 'we're using PowerShell' or make it clear that other shells are supported.
  • Add a note or section for Linux/macOS users, highlighting any differences in syntax or environment setup.
  • Use cross-platform variable assignment and command substitution in examples, or show both styles.
GitHub Create Pull Request
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-10 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 commands for Azure CLI operations, stating that PowerShell is used for the tutorial, and using Windows-style variable assignment and scripting patterns. There are no Bash or Linux shell equivalents for key steps such as resource group setup, storage account creation, role assignment, and cleanup, even though Azure CLI is cross-platform. The only Bash example is for the Python SDK usage and job status retrieval, which is not sufficient for full Linux parity.
Recommendations
  • Provide Bash/Linux shell equivalents for all Azure CLI commands, especially for resource setup, role assignment, and cleanup.
  • Clarify that Azure CLI commands work on both Windows and Linux, and avoid stating that PowerShell is the default unless necessary.
  • Present both PowerShell and Bash examples side-by-side, or allow users to select their preferred shell in the documentation.
  • Avoid using Windows-specific variable assignment syntax (e.g., $Variable) without offering the Linux alternative (e.g., export VARIABLE=value).
  • Include a note or section for Linux/macOS users to ensure inclusivity and usability across platforms.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, Azure PowerShell is a Windows-centric tool and its inclusion alongside Azure CLI (which is cross-platform) may suggest a Windows bias, especially since no Linux-specific shell examples (e.g., Bash) or platform notes are given. The prerequisites mention both Azure CLI and Azure PowerShell, but do not clarify platform differences or recommend CLI for Linux/macOS users. There are no explicit Linux or macOS instructions, nor are there references to platform-specific considerations.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users, while Azure PowerShell is primarily for Windows.
  • Add explicit Bash shell examples or notes for Linux/macOS users, such as using Bash with Azure CLI.
  • Include a section or note on platform compatibility for each tool, helping users choose the best option for their OS.
  • Consider listing Azure CLI examples first, as it is cross-platform, to reduce perceived Windows bias.
  • If PowerShell is included, mention that it is available on Linux/macOS but is more commonly used on Windows.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently referencing PowerShell and Visual Studio Code for local execution, and by suggesting PowerShell as the first example in code tabs. There is no mention of Linux-specific shell environments (e.g., bash, zsh) or alternative editors (e.g., Vim, nano), nor are there instructions or troubleshooting tips for Linux users. The Azure CLI examples are cross-platform, but the narrative and instructions are oriented toward Windows tools and workflows.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide guidance for running them in native Linux/macOS terminals.
  • Include examples or notes for Linux/macOS users, such as running Azure CLI in bash/zsh, and using editors like Vim or nano instead of Visual Studio Code.
  • Avoid suggesting PowerShell as the default local scripting environment; present Azure CLI first, as it is cross-platform.
  • Add troubleshooting steps or environment setup instructions for Linux/macOS users (e.g., installing Azure CLI on Ubuntu, using curl for REST calls).
  • Where screenshots or UI instructions are given, clarify any OS-specific differences, or provide alternative instructions for Linux/macOS users.
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-10 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 bias towards Windows environments by exclusively providing PowerShell commands for configuring Azure Storage networking and trusted services. There are no equivalent examples or instructions for Linux users (e.g., using Azure CLI, Bash, or cross-platform tools). The use of PowerShell is presented as the default method, and no alternatives are mentioned, which may disadvantage users on Linux or macOS systems.
Recommendations
  • Provide equivalent Azure CLI commands for all PowerShell examples, ensuring Linux and macOS users can follow along without installing PowerShell.
  • Explicitly mention that both PowerShell and Azure CLI can be used, and link to cross-platform documentation.
  • Add Bash script examples where appropriate, especially for steps that involve scripting or automation.
  • Clarify that the instructions are not limited to Windows environments, and provide guidance for users on Linux/macOS regarding prerequisites and tool installation.
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-10 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 both PowerShell and Azure CLI, but PowerShell is presented first and is referenced as the primary method for running scripts locally (specifically mentioning Visual Studio Code, which is most commonly used on Windows). There are no explicit Linux-specific examples, nor is there mention of Linux-native tools or shell environments. The instructions and screenshots focus on Azure Portal and Microsoft tools, which are cross-platform, but the scripting examples and workflow favor Windows users by default.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to avoid implying Windows-first workflows.
  • Explicitly mention that Azure CLI commands can be run natively on Linux/macOS terminals, and provide example shell environments (e.g., bash, zsh).
  • Include notes or examples for running deployment scripts on Linux (e.g., using bash scripts, or running Azure CLI in Linux containers).
  • Reference Linux-native editors (such as Vim, Nano, or VS Code on Linux) when suggesting where to run scripts.
  • Clarify that all steps can be performed on Linux, macOS, or Windows, and provide troubleshooting tips for non-Windows environments if needed.
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-10 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 trusted resources, referencing the Az.Storage PowerShell module exclusively, and omitting equivalent Linux/Unix command-line instructions (such as Azure CLI or Bash). The page assumes a Windows environment for local administration tasks and does not mention or prioritize cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI (az) commands for all PowerShell examples, especially for configuring storage account network rules and trusted resources.
  • Explicitly mention that administrative steps can be performed from Linux, macOS, or Windows, and provide Bash/CLI instructions alongside PowerShell.
  • Reference cross-platform tools (Azure CLI, REST API) before or alongside Windows-specific tools like PowerShell.
  • Include notes or sections for Linux/macOS users, clarifying any differences in procedure or tool installation.
  • Avoid assuming a Windows environment for local administration; use neutral language and examples.
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-10 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 by consistently listing PowerShell instructions and tools before their Linux equivalents, referencing Git Bash (a Windows-focused Bash shell) as the example for Bash, and providing detailed PowerShell examples alongside CLI. There is a tendency to assume Windows environments, especially in the prerequisites and tool recommendations.
Recommendations
  • Present CLI/Bash instructions before PowerShell in all tabbed sections to avoid implicit prioritization of Windows.
  • In prerequisites, recommend Bash shells available natively on Linux/macOS (e.g., Ubuntu Terminal, macOS Terminal) instead of or alongside Git Bash.
  • Explicitly mention cross-platform compatibility for Azure CLI and PowerShell, clarifying that both can be used on Windows, Linux, and macOS.
  • Add notes or examples for Linux/macOS environments where relevant, such as file path conventions or shell usage.
  • Ensure that tool installation links and instructions are platform-neutral or provide platform-specific guidance for Linux/macOS users.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by frequently referencing PowerShell as a primary automation tool, listing it before Azure CLI and REST API in multiple steps. Windows-centric tools and patterns (PowerShell, .NET SDK, Power BI) are mentioned more prominently, and Linux-native equivalents (such as bash scripting or Linux-specific authentication flows) are not highlighted. While cURL is mentioned, there are no explicit Linux shell examples or guidance for Linux users.
Recommendations
  • Provide explicit bash/Linux shell examples alongside PowerShell for all command-line instructions.
  • Ensure Azure CLI is listed before or equally with PowerShell, as it is cross-platform.
  • Include Linux-specific guidance for authentication (e.g., using Azure CLI on Linux, environment variables for tokens).
  • Mention open-source, cross-platform data visualization tools alongside Power BI.
  • Add notes or links for Linux users regarding installation and usage of required tools.
  • Where .NET SDK is referenced, also mention Python or Java SDKs that are cross-platform.
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-10 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 prioritizing PowerShell instructions, referencing Windows-specific tools (such as Git Bash for CLI usage), and providing examples and guidance that assume a Windows environment. Linux-native shells and workflows are not discussed, and the CLI instructions reuse Windows-centric file paths and context. There is a lack of explicit Linux or macOS examples, and the documentation does not address cross-platform differences in detail.
Recommendations
  • Add explicit Linux/macOS instructions and examples, including native Bash shell usage and file path conventions.
  • Avoid recommending Windows-specific tools (e.g., Git Bash) as the default for CLI usage; mention standard Bash shells available on Linux/macOS.
  • Provide guidance for running Azure CLI commands in Linux/macOS terminals, including differences in environment variables and file paths.
  • Ensure that CLI examples use forward slashes (/) for file paths and avoid Windows-style backslashes (\\) unless specifically targeting Windows.
  • Include troubleshooting notes for common cross-platform issues (e.g., permission errors, shell differences).
  • Balance the prominence of PowerShell and CLI instructions, and consider listing CLI (cross-platform) instructions before PowerShell (Windows-centric) ones.
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-10 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 several signs of Windows bias. All command-line examples are provided exclusively in PowerShell, with no equivalent bash or Linux shell commands. The instructions and tooling references (e.g., dotnet user-secrets, git commands) are presented in a way that assumes a Windows environment, and there is no mention of Linux-specific setup or alternative commands. The use of localhost:5001 and reliance on PowerShell scripts further reinforce a Windows-centric approach. There are no examples or guidance for Linux or macOS users, nor any mention of cross-platform considerations.
Recommendations
  • Provide equivalent bash or shell script examples alongside PowerShell commands for steps such as reply URL encoding and running the app.
  • Explicitly state cross-platform compatibility for tools like .NET SDK and git, and provide installation/setup instructions for Linux/macOS.
  • Include Linux/macOS-specific instructions for running the SMART on FHIR app launcher, including environment setup and configuration.
  • Mention that localhost:5001 works on all platforms, but clarify any platform-specific caveats (e.g., firewall, permissions).
  • Where PowerShell is used, offer bash alternatives and clarify which commands are platform-agnostic.
  • Add a section or notes on troubleshooting and running the samples on Linux and macOS environments.
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-10 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 demonstrates a Windows bias by prioritizing PowerShell in prerequisites and examples, referencing Windows-specific tools (PowerShell, Visual Studio Code, Git Bash), and lacking explicit Linux shell examples. The CLI section mentions Bash only as an option for Windows users, and there are no native Linux shell instructions or examples. The overall structure and language assume a Windows-centric workflow.
Recommendations
  • Add explicit Linux shell (bash/zsh) examples for all steps, including token acquisition and environment setup.
  • Include installation instructions for cURL and Azure CLI on Linux and macOS, not just Windows.
  • Present CLI/bash examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Remove or supplement references to Windows-only tools (e.g., PowerShell, Git Bash) with cross-platform alternatives.
  • Clarify that Visual Studio Code and REST Client extension are cross-platform, and mention Linux/macOS compatibility.
  • Provide troubleshooting notes for common Linux/macOS issues (e.g., environment variables, shell quoting).
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-10 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. PowerShell and Azure CLI are repeatedly mentioned as scripting options for client application registration and access token retrieval, with PowerShell listed first. There is no mention of Bash or Linux-specific shell usage, nor are Linux-native tools or workflows described. Examples and instructions for using REST clients, cURL, and Python are present, but only in secondary contexts. No explicit Linux setup or parity guidance is provided, and screenshots and UI references are Azure Portal-centric, which is platform-agnostic but often used on Windows.
Recommendations
  • Include explicit Bash and Linux shell examples alongside PowerShell and Azure CLI instructions.
  • Add guidance for Linux users on registering applications and managing identities, including sample commands.
  • List scripting options in a neutral order (e.g., 'using PowerShell, Bash, or Azure CLI scripts') rather than Windows-first.
  • Highlight cross-platform tools (e.g., cURL, Python, REST client) earlier and provide full examples for Linux environments.
  • Where screenshots or UI instructions are given, clarify platform compatibility and mention Linux-friendly alternatives if available.
GitHub Create Pull Request
← Previous Page 2 of 13 Next →