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 201-225 of 302 flagged pages
Healthcare Apis Configure customer-managed keys for Azure API for FHIR ...thcare-apis/azure-api-for-fhir/customer-managed-key.md
Medium Priority View Details →
Scanned: 2026-01-13 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 using the Azure portal, PowerShell, CLI, and ARM templates. However, PowerShell examples are given prominently, including for ARM template deployment, and there is no mention of Linux/macOS-specific shell commands (e.g., Bash). The PowerShell deployment script is shown without an equivalent Bash/Unix shell example, and PowerShell is referenced before CLI in several places. This creates friction for Linux/macOS users who may not use PowerShell.
Recommendations
  • Add Bash or shell script examples for ARM template deployment using Azure CLI (e.g., az deployment group create).
  • Present Azure CLI examples before PowerShell examples, or side-by-side, to emphasize cross-platform parity.
  • Explicitly state that all CLI commands work on Linux/macOS, and provide any necessary platform-specific notes.
  • If PowerShell is required for any step, clarify whether PowerShell Core is supported on Linux/macOS, or provide alternatives.
  • Review and update images/screenshots to ensure they are not Windows-specific where possible.
GitHub Create Pull Request
Healthcare Apis Get started with Azure API for FHIR .../azure-api-for-fhir/get-started-with-azure-api-fhir.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell as a deployment option before mentioning Azure CLI and ARM templates, which may suggest a Windows-first approach. The explicit mention of PowerShell as a primary method can create friction for Linux/macOS users, though CLI and ARM template alternatives are provided. No Linux/macOS-specific examples or tools are highlighted, and there are no screenshots or instructions tailored to non-Windows platforms.
Recommendations
  • Present Azure CLI and ARM template deployment options before or alongside PowerShell, emphasizing their cross-platform compatibility.
  • Include explicit Linux/macOS instructions or screenshots where relevant, such as CLI installation or usage.
  • Add a note clarifying that PowerShell Core is available cross-platform, or provide links to platform-specific setup guides.
  • Ensure that examples and tooling are balanced between Windows and Linux/macOS users.
GitHub Create Pull Request
Healthcare Apis SMART on FHIR - Azure API for FHIR ...es/healthcare-apis/azure-api-for-fhir/smart-on-fhir.md
Medium Priority View Details →
Scanned: 2026-01-13 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 notable Windows bias. All command-line examples use PowerShell syntax, with no equivalent bash or Linux/macOS shell commands provided. Git and .NET commands are shown in PowerShell blocks, and instructions for generating reply URLs rely exclusively on PowerShell scripting. There is no mention of Linux or macOS alternatives, nor any guidance for users on those platforms. The use of PowerShell and Windows-centric tooling is presented as the default, with no parity for non-Windows environments.
Recommendations
  • Provide equivalent bash shell scripts for generating reply URLs and other scripting tasks.
  • Include Linux/macOS command-line examples alongside PowerShell, especially for git cloning and dotnet commands.
  • Explicitly mention cross-platform compatibility of tools (e.g., .NET, git) and provide OS-specific instructions where needed.
  • Add notes or sections for Linux/macOS users, clarifying any differences in setup or usage.
  • Use generic code blocks for commands that are identical across platforms, and highlight OS-specific commands when necessary.
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
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell syntax and variable assignment patterns throughout, even though Azure CLI is cross-platform. There are no Bash or Linux/macOS shell examples, and the tutorial explicitly states 'we're using PowerShell,' which may confuse or hinder Linux/macOS users. All code samples use PowerShell variable syntax ($Variable), which does not work in Bash or other Unix shells.
Recommendations
  • Provide equivalent Bash/Linux shell examples for all CLI commands, using Bash variable syntax and patterns.
  • Clarify that Azure CLI works on all platforms and that examples are available for both PowerShell and Bash.
  • Avoid language like 'we're using PowerShell' unless alternatives are also provided.
  • Consider reordering or presenting examples in parallel (PowerShell and Bash side-by-side) to avoid Windows-first perception.
GitHub Create Pull Request
Healthcare Apis De-identify multiple documents with the de-identification service in python ...pis/deidentification/quickstart-asynchronous-python.md
Medium Priority View Details →
Scanned: 2026-01-13 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 notable Windows bias by exclusively using PowerShell syntax for all Azure CLI and scripting examples, even though Azure CLI is cross-platform. There are no Bash or Linux shell equivalents provided for common tasks such as variable assignment, resource creation, or role assignment. The page also explicitly states 'we're using PowerShell' in the tutorial setup, and Windows/PowerShell examples are presented first and exclusively. Only the Python SDK and a single curl command use Bash, but all Azure CLI usage is shown in PowerShell style.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell examples, especially for Azure CLI commands and variable assignment.
  • Clarify that Azure CLI works on all platforms and users can choose their preferred shell.
  • Present both Windows (PowerShell) and Linux/macOS (Bash) examples side by side, or default to Bash for CLI commands since it is more universally applicable.
  • Avoid using PowerShell-specific variable assignment ($Var = ...) in CLI examples, as this is not portable.
  • Add a note or section for Linux/macOS users outlining any differences or considerations.
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
Medium Priority View Details →
Scanned: 2026-01-13 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 moderate Windows bias. PowerShell is presented as a primary scripting option, with explicit instructions to run scripts in PowerShell locally using Visual Studio Code—a Windows-centric workflow. While Azure CLI examples are provided (which are cross-platform), PowerShell instructions are consistently shown first and referenced as a main method. There are no explicit Linux/macOS shell script examples, nor are Linux-specific tools or workflows mentioned. The guidance to use Visual Studio Code for PowerShell locally further reinforces a Windows-first approach. No Linux/macOS-specific troubleshooting or environment notes are present.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to emphasize cross-platform compatibility.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide example shell environments (e.g., bash, zsh).
  • Add notes or sections for Linux/macOS users, such as how to install Azure CLI and run scripts in their native terminals.
  • Remove or generalize references to 'PowerShell locally in Visual Studio Code' to include Linux/macOS terminal usage.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., authentication, path differences).
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
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a Windows-specific example for creating a self-signed certificate using PowerShell's New-SelfSignedCertificate command, but does not mention or provide equivalent instructions for Linux or macOS users (e.g., using OpenSSL). No other steps are platform-specific, but the certificate creation step lacks Linux parity.
Recommendations
  • Add instructions for creating a self-signed certificate on Linux/macOS using OpenSSL (e.g., openssl req -x509 ...).
  • Explicitly mention cross-platform alternatives wherever a Windows tool or command is referenced.
  • Where possible, provide examples for both Windows and Linux/macOS in parallel.
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
Medium Priority View Details →
Scanned: 2026-01-13 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 a notable Windows bias, especially in the section on configuring Azure Storage networking for secure import. PowerShell is the only CLI tool referenced for scripting, with no Bash, Azure CLI, or Linux/macOS alternatives provided. The instructions and examples for command-line configuration are exclusively Windows-centric, and Windows tools are mentioned before any cross-platform options. This creates friction for Linux/macOS users, who must find their own equivalents or workarounds.
Recommendations
  • Add equivalent Azure CLI or Bash examples for all PowerShell commands, especially for configuring storage account network rules.
  • Explicitly state that PowerShell commands are Windows-specific and provide guidance for Linux/macOS users.
  • Reference cross-platform tools (e.g., Azure CLI) before or alongside Windows tools.
  • Include links to documentation for Azure CLI and REST API usage for all steps currently covered only by PowerShell.
GitHub Create Pull Request
Healthcare Apis Configure export settings in FHIR service - Azure Health Data Services ...articles/healthcare-apis/fhir/configure-export-data.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides critical configuration steps using PowerShell commands, with no equivalent instructions or examples for Linux/macOS users (e.g., Bash, Azure CLI). The only automation example for configuring network rules and trusted services is Windows-centric, relying on PowerShell and the Az.Storage module. No mention is made of how to perform these tasks using cross-platform tools, and the documentation assumes a Windows environment for command-line steps.
Recommendations
  • Provide equivalent Azure CLI or REST API examples for all PowerShell commands, especially for configuring storage account network rules and trusted services.
  • Explicitly mention that PowerShell commands are Windows-specific and offer guidance for Linux/macOS users.
  • Add Bash or Azure CLI code blocks alongside PowerShell, and clarify which platforms each example supports.
  • Reference cross-platform tooling in introductory sections to set expectations for users on different operating systems.
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
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation shows a moderate Windows bias: PowerShell is presented first in all code tabs and deployment instructions, and Windows-centric tools (PowerShell, Visual Studio Code, Git Bash for Windows) are mentioned before or instead of native Linux/macOS alternatives. The CLI section is present and functional, but PowerShell is emphasized throughout, and Linux/macOS users may find the instructions less tailored to their environments.
Recommendations
  • Alternate the order of PowerShell and CLI tabs so that CLI is shown first in some sections, or default to CLI for cross-platform parity.
  • Explicitly mention native Bash shells for Linux/macOS in the prerequisites, not just 'Git Bash for Windows'.
  • Clarify that both Azure CLI and PowerShell are available in Azure Cloud Shell, which is OS-agnostic.
  • Provide example commands for macOS/Linux terminal environments (e.g., file paths, shell variable syntax) where appropriate.
  • Avoid language like 'run the code in PowerShell locally, in Visual Studio Code, or in Azure Cloud Shell' in the CLI section; tailor instructions to Bash/zsh environments.
GitHub Create Pull Request
Healthcare Apis Access Azure Health Data Services with cURL .../blob/main/articles/healthcare-apis/fhir/using-curl.md
Medium Priority View Details →
Scanned: 2026-01-13 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 exhibits a moderate Windows bias. PowerShell is featured prominently in prerequisites and examples, with installation instructions and code samples. Windows tools (PowerShell, Visual Studio Code) are mentioned before Linux equivalents, and Bash is only suggested as an optional install for Windows users. There are no explicit Linux/macOS-specific instructions or examples, and the CLI section assumes Bash but does not address native Linux environments directly.
Recommendations
  • Add explicit instructions for Linux/macOS users in the prerequisites, including native Bash shell usage and Azure CLI installation for those platforms.
  • Provide Linux/macOS-specific code samples, especially for environment setup and token retrieval, clarifying differences in shell syntax and environment variables.
  • Reorder examples so that CLI/Bash instructions are presented before or alongside PowerShell, to avoid Windows-first impression.
  • Mention platform-specific considerations (e.g., cURL installation on Linux/macOS, default shell differences) to ensure parity.
  • Clarify that PowerShell is available cross-platform, but highlight native Bash alternatives 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
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation consistently lists PowerShell as a primary method for performing tasks (e.g., creating resources, registering apps, obtaining tokens), often before Azure CLI or REST API. There is a general pattern of mentioning Windows-centric tools and workflows (PowerShell, .NET SDK) without explicit Linux/macOS alternatives or parity. While Azure CLI and REST API are mentioned, there are no Linux-specific examples, and PowerShell is frequently referenced first, suggesting a Windows-first approach.
Recommendations
  • Provide explicit Linux/macOS examples for all command-line steps, especially for Azure CLI and cURL.
  • List Azure CLI and REST API options before PowerShell, or present all options in parallel.
  • Include notes or sections clarifying cross-platform compatibility and any differences in command syntax or authentication flows.
  • Add sample scripts or links for Linux/macOS users in the referenced GitHub samples.
  • Mention alternative SDKs (e.g., Python, Java) alongside .NET SDK for token acquisition and API access.
GitHub Create Pull Request
Healthcare Apis SMART on FHIR - Azure Health Data Services ...ob/main/articles/healthcare-apis/fhir/smart-on-fhir.md
Medium Priority View Details →
Scanned: 2026-01-13 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 notable Windows bias. All command-line examples use PowerShell syntax, and instructions for running scripts and applications assume a Windows environment (e.g., PowerShell, dotnet user-secrets, localhost:5001). There are no Linux/macOS shell equivalents or guidance for non-Windows users. The use of Windows-centric tools and patterns (PowerShell, Windows-style paths) may create friction for Linux/macOS users attempting to follow the tutorial.
Recommendations
  • Provide equivalent bash/zsh shell script examples for generating reply URLs and running dotnet commands.
  • Explicitly mention cross-platform compatibility for .NET SDK and app launcher, including any OS-specific setup steps.
  • Add notes or sections for Linux/macOS users, such as using 'export' for environment variables, and using 'dotnet run' from a terminal.
  • Clarify that git and dotnet commands work on Linux/macOS, and provide troubleshooting tips for common platform-specific issues.
  • Avoid assuming PowerShell is available; offer alternatives or links to install PowerShell Core on Linux/macOS if needed.
GitHub Create Pull Request
Healthcare Apis Introduction to Azure Health Data Services ...es/healthcare-apis/health-data-services-get-started.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation repeatedly references PowerShell and .NET SDK as primary tools for managing Azure Health Data Services, often listing them before or alongside Azure CLI. There is a notable emphasis on Windows-centric tools and scripting environments, with no explicit Linux/macOS examples or mention of platform-specific considerations. While cURL and Python are mentioned as access tools, there are no concrete Linux/macOS instructions or examples, and PowerShell is consistently presented as a main automation method.
Recommendations
  • Add explicit Linux/macOS instructions and examples for all major tasks, especially for authentication and resource management.
  • Provide bash/Azure CLI scripts and usage examples, and clarify cross-platform compatibility for all command-line tools.
  • Ensure that cURL and Python examples are shown alongside PowerShell/.NET, and indicate which tools are available on all platforms.
  • Avoid listing PowerShell and .NET SDK first; alternate the order or group cross-platform tools together.
  • Include notes or links about installing and using Azure CLI, cURL, and Python on Linux/macOS.
GitHub Create Pull Request
Healthcare Apis Receive device messages through Azure IoT Hub - Azure Health Data Services ...healthcare-apis/iot/device-messages-through-iot-hub.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation relies exclusively on Visual Studio Code with the Azure IoT Tools extension for device creation and message sending, which is most commonly used on Windows and does not mention or provide alternatives for Linux/macOS users (such as Azure CLI, IoT CLI, or direct REST API usage). All step-by-step instructions and screenshots are based on this Windows-centric workflow, and no Linux-specific tools or command-line examples are provided.
Recommendations
  • Add instructions and examples for using Azure CLI or Azure IoT CLI to create devices and send messages, which work cross-platform.
  • Include references to platform-agnostic REST API methods for device management and message sending.
  • Explicitly mention that Visual Studio Code and the Azure IoT Tools extension are available on Linux/macOS, or provide alternative workflows for those platforms.
  • Provide screenshots or terminal examples for Linux/macOS environments.
  • List Linux/macOS prerequisites and installation steps alongside Windows.
GitHub Create Pull Request
Healthcare Apis Azure Health Data Services known issues ...ocs/blob/main/articles/healthcare-apis/known-issues.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a workaround for configuring the storage account for FHIR export using only PowerShell commands and the Az PowerShell module, which are Windows-centric. There are no equivalent CLI or Bash examples for Linux/macOS users, nor is there mention of cross-platform alternatives.
Recommendations
  • Add Azure CLI (az) command examples for configuring the storage account, as Azure CLI is cross-platform and works on Linux/macOS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, or provide Bash script equivalents.
  • When presenting command-line workarounds, show both Windows (PowerShell) and Linux/macOS (CLI/Bash) options side-by-side.
  • Include notes about tool compatibility for non-Windows users.
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
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias in the section on 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 or referenced. Other steps are platform-neutral, focusing on Azure Portal UI, but the lack of Linux/macOS guidance for certificate creation may create friction for non-Windows users.
Recommendations
  • Include Linux/macOS certificate creation instructions using OpenSSL (e.g., 'openssl req -x509 ...').
  • Explicitly mention that certificate creation can be performed on any OS and provide equivalent commands for each.
  • Add a note or table summarizing cross-platform options for all command-line steps.
  • Where PowerShell is referenced, provide Bash or shell alternatives.
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
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions the provision of PowerShell scripts and ARM templates for deployment and configuration, which are Windows-centric tools. While Azure CLI is also referenced, there is no explicit mention of Bash or Linux/macOS-specific instructions or examples. The documentation does not provide parity for Linux users in script examples or tooling guidance, and Windows tools are mentioned first and most prominently.
Recommendations
  • Explicitly provide Bash/Linux/macOS script examples alongside PowerShell, especially for deployment and configuration tasks.
  • Clarify which tools (PowerShell, CLI, ARM templates) are cross-platform and provide guidance for Linux/macOS users where applicable.
  • If Azure CLI is cross-platform, highlight its usage and provide sample commands for both Windows (PowerShell) and Linux/macOS (Bash).
  • Avoid mentioning Windows tools first unless they are the only supported option; strive for equal visibility for Linux/macOS workflows.
GitHub Create Pull Request
Healthcare Apis Manage access to the de-identification service with Azure role-based access control (RBAC) in Azure Health Data Services ...healthcare-apis/deidentification/manage-access-rbac.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Azure PowerShell instructions before Azure CLI, which may suggest a Windows-first bias. The PowerShell example is detailed and includes output, while the Azure CLI example is less emphasized and lacks output details. There is no explicit mention of Linux or cross-platform usage, and no Bash or Linux-specific notes are provided.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
  • Include sample output for Azure CLI commands to match the detail provided for PowerShell.
  • Add notes clarifying that Azure CLI works on Windows, Linux, and macOS, and provide installation links for each platform.
  • Mention that PowerShell Core is available on Linux and macOS, if relevant, and provide usage notes for non-Windows environments.
  • Consider adding Bash script examples for common tasks, or at least acknowledge Linux shell usage.
GitHub Create Pull Request
Healthcare Apis Register a resource app in Microsoft Entra ID - Azure API for FHIR ...-api-for-fhir/register-resource-azure-ad-client-app.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation demonstrates a Windows bias by presenting PowerShell as the first and primary method for registering the resource application, with Azure CLI as a secondary option. There are no explicit Linux-specific examples, and the use of PowerShell may alienate users on Linux or macOS platforms.
Recommendations
  • Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and works natively on Linux and macOS.
  • Explicitly mention that both Azure CLI and PowerShell are available on multiple platforms, and provide installation instructions or links for Linux users.
  • Add a note clarifying that PowerShell Core is available for Linux, if PowerShell usage is necessary.
  • Ensure that any referenced scripts or commands are tested and confirmed to work on Linux environments.
  • Consider adding bash or shell script equivalents for common tasks, where appropriate.
GitHub Create Pull Request
Healthcare Apis Find identity object IDs for authentication in Azure API for FHIR ...re-apis/azure-api-for-fhir/find-identity-object-ids.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation consistently presents Microsoft Graph PowerShell examples before Azure CLI examples for all tasks, indicating a Windows-first approach. PowerShell is a Windows-centric tool, and its prominence may disadvantage Linux users. However, Azure CLI examples are provided for each scenario, which are cross-platform compatible.
Recommendations
  • Present Azure CLI examples before PowerShell examples to prioritize cross-platform tools.
  • Explicitly state that Azure CLI works on Windows, Linux, and macOS, and recommend it for non-Windows environments.
  • Add Bash shell usage notes or examples where relevant, especially for scripting in Linux environments.
  • Consider including a table comparing PowerShell and Azure CLI usage, highlighting platform compatibility.
  • Review and update any language that implies PowerShell is the default or preferred method.
GitHub Create Pull Request
Healthcare Apis Get started with Azure API for FHIR .../azure-api-for-fhir/get-started-with-azure-api-fhir.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by listing PowerShell as a deployment option before CLI, and by referencing Windows-centric tools (PowerShell, ARM templates) without explicitly mentioning Linux alternatives or parity. The deployment section refers to PowerShell and CLI, but PowerShell is listed first, which may imply a preference for Windows environments. There are no explicit Linux examples or instructions, and the documentation does not clarify cross-platform compatibility for the CLI or ARM template methods.
Recommendations
  • Explicitly mention that Azure CLI and ARM templates are cross-platform and provide examples for both Windows and Linux environments.
  • Alternate the order of deployment options or list CLI first to avoid implicit Windows-first bias.
  • Add Linux-specific instructions or screenshots where relevant, especially for command-line deployment.
  • Include notes or links about using Azure CLI and ARM templates on Linux/macOS.
  • Ensure that any referenced scripts or commands are tested and documented for both Windows (PowerShell) and Linux (bash/CLI).
GitHub Create Pull Request
Healthcare Apis Access Azure Health Data Services using REST Client ...ain/articles/healthcare-apis/fhir/using-rest-client.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by mentioning PowerShell before Bash when discussing integrated terminal usage in Visual Studio Code. The troubleshooting and main workflow sections are platform-neutral, but the explicit highlighting of PowerShell and the ordering of examples may suggest a preference for Windows environments.
Recommendations
  • Present Bash and PowerShell examples in parallel, or mention Bash first to balance platform representation.
  • Include explicit Linux/macOS usage notes or screenshots alongside Windows/PowerShell examples.
  • Clarify that all steps and tools (REST Client, VS Code terminal) work identically on Linux/macOS, and provide links to relevant platform-specific documentation if available.
  • If showing terminal usage, provide example commands for both Bash and PowerShell, or use generic shell commands where possible.
GitHub Create Pull Request
Healthcare Apis Deploy the MedTech service using an Azure Resource Manager template - Azure Health Data Services ...in/articles/healthcare-apis/iot/deploy-arm-template.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes deployment using the Azure portal and the 'Deploy to Azure' button, which is platform-agnostic but visually and procedurally tailored to GUI workflows common on Windows. There are no examples or instructions for command-line deployment methods (such as Azure CLI, PowerShell, or Bash), nor are Linux-specific tools or patterns mentioned. This omission may disadvantage users who prefer or require automation or non-GUI workflows, which are more common in Linux environments.
Recommendations
  • Add instructions and examples for deploying the ARM template using Azure CLI (az deployment group create) and Bash scripts.
  • Include PowerShell examples for completeness, but ensure Azure CLI and Bash examples appear first or alongside them.
  • Mention cross-platform tools and workflows, such as Visual Studio Code with Azure extensions, and clarify that deployment can be performed from Linux, macOS, or Windows.
  • Provide explicit guidance for headless or automated deployments, which are common in Linux environments (e.g., CI/CD pipelines).
GitHub Create Pull Request
Healthcare Apis Receive device messages through Azure IoT Hub - Azure Health Data Services ...healthcare-apis/iot/device-messages-through-iot-hub.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively referencing Visual Studio Code and the Azure IoT Hub extension for device creation and message sending, without mentioning or providing alternatives for Linux users. There are no examples or instructions for using Linux-native tools (such as CLI, shell scripts, or open-source IoT utilities), nor is there guidance for performing these steps outside of the Visual Studio Code GUI, which is most commonly used on Windows. The documentation does not acknowledge Linux environments or provide parity in tooling or workflow.
Recommendations
  • Add instructions and examples for using Azure CLI, PowerShell Core (cross-platform), or REST API to create devices and send messages, suitable for Linux and macOS users.
  • Mention and provide guidance for open-source IoT tools (e.g., iotedge, mosquitto_pub) that can interact with Azure IoT Hub from Linux.
  • Clarify that Visual Studio Code and its extensions are available on Linux and macOS, and provide installation instructions for those platforms.
  • Include screenshots or terminal examples from Linux environments to illustrate cross-platform compatibility.
  • Explicitly state that all steps can be performed on Linux, and highlight any differences or prerequisites for Linux users.
GitHub Create Pull Request
← Previous Page 9 of 13 Next →