Healthcare Apis

490
Total Pages
455
Linux-Friendly Pages
35
Pages with Bias
7.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

66 issues found
Showing 1-25 of 66 flagged pages
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by presenting PowerShell as the primary method for registering the resource app, with the Azure CLI alternative mentioned second. The use of PowerShell (a Windows-centric tool) and the ordering of examples suggest a preference for Windows environments. There are no explicit Linux/macOS examples or notes about platform compatibility for the commands.
Recommendations
  • Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform.
  • Explicitly state that both PowerShell and Azure CLI commands work on Linux/macOS, or provide platform-specific instructions if necessary.
  • Include a table or section comparing command usage across Windows, Linux, and macOS.
  • Avoid language that implies PowerShell is the default or preferred method unless it is truly required.
GitHub Create Pull Request
Healthcare Apis Private link for Azure API for FHIR ...care-apis/azure-api-for-fhir/configure-private-link.md
Medium Priority View Details →
Scanned: 2026-01-12 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 moderate Windows bias. While it mentions both Azure PowerShell and Azure CLI as options for creating private endpoints, the only command-line example shown is a Windows-style nslookup output (with a C:\ prompt), and remote access instructions specify RDP (Remote Desktop Protocol), which is Windows-centric. There are no explicit Linux/macOS command-line examples, nor are SSH or Linux-native tools mentioned for VM access or troubleshooting. Windows tools and patterns are referenced first or exclusively in several sections.
Recommendations
  • Provide Linux/macOS equivalents for command-line examples, such as showing nslookup or dig output from a Bash shell.
  • Mention SSH as an alternative to RDP for VM access, especially for Linux VMs.
  • Clarify that Azure CLI and PowerShell are cross-platform, and provide example commands for both environments.
  • Include troubleshooting steps and screenshots for Linux/macOS users where applicable.
  • Avoid using Windows-specific paths or prompts (e.g., C:\Users\testuser>) in examples unless also showing Unix-style equivalents.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell and Azure CLI examples for creating service principals, but PowerShell is presented first and the CLI example uses syntax that is not fully cross-platform (e.g., variable assignment without 'export' for bash). There are no explicit Linux/macOS shell examples, and the PowerShell module is highlighted, which may lead Linux users to feel secondary or confused. The documentation does not mention Linux-specific considerations or tools, and the CLI example assumes familiarity with bash but does not clarify shell compatibility.
Recommendations
  • Present Azure CLI (bash) examples before PowerShell, or side-by-side, to avoid Windows-first bias.
  • Explicitly state that Azure CLI commands work on Linux/macOS and provide tested bash/zsh syntax (e.g., use 'export' for environment variables).
  • Add a note clarifying that PowerShell is available on Linux/macOS, or provide links to installation instructions.
  • Include troubleshooting or tips for Linux/macOS users, such as shell compatibility or authentication nuances.
  • Avoid referencing Visual Studio Code as the only tested environment; mention alternatives or clarify cross-platform support.
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-12 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, with no equivalent bash or Linux/macOS instructions. Git and .NET commands are shown in PowerShell, and the script for generating reply URLs is PowerShell-only. There is no mention of Linux/macOS workflows, nor are cross-platform alternatives or considerations discussed. This may create friction for users on non-Windows platforms attempting to follow the tutorial.
Recommendations
  • Provide bash/zsh equivalents for all PowerShell scripts and commands, especially for reply URL generation and .NET operations.
  • Explicitly mention that the steps can be performed on Linux/macOS, and note any platform-specific differences.
  • Include screenshots or instructions for Linux/macOS environments where applicable.
  • Clarify prerequisites for non-Windows users (e.g., installing .NET SDK on Linux/macOS).
  • Use neutral command-line syntax (e.g., 'git clone', 'dotnet run') outside of PowerShell blocks.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page shows a moderate Windows bias. While the main instructions use the Azure portal (which is cross-platform), the only CLI tool mentioned for creating custom roles is Azure PowerShell, with no reference to Azure CLI or other Linux-friendly alternatives. Additionally, the link for custom role creation points exclusively to a PowerShell-based guide, which is primarily used on Windows. There are no Linux/macOS-specific instructions or examples, and Windows tools are mentioned before any cross-platform equivalents.
Recommendations
  • Add instructions and links for creating custom roles using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that the Azure portal is accessible from any OS/browser.
  • Provide parity in examples by including both PowerShell and Azure CLI commands where applicable.
  • Clarify that PowerShell Core is available on Linux/macOS, if PowerShell must be used.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for both direct configuration and ARM template deployment, with PowerShell shown before Azure CLI. There are no explicit Linux/macOS shell examples (e.g., Bash), nor are there instructions for deploying ARM templates using Azure CLI or Bash. The focus on PowerShell and lack of Linux-specific guidance may create friction for non-Windows users.
Recommendations
  • Add Bash or shell examples for ARM template deployment using Azure CLI (e.g., az deployment group create).
  • Present Azure CLI examples before or alongside PowerShell to avoid Windows-first impression.
  • Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS).
  • Include notes or links for Linux/macOS users regarding prerequisites and environment setup.
  • Where PowerShell is used for deployment, provide equivalent Bash/CLI commands.
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-12 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 all CLI examples, with no mention of Linux/macOS shell equivalents (e.g., Bash). This may create friction for users on non-Windows platforms, as PowerShell variable assignment and command substitution differ from Bash and other Unix shells. The tutorial states 'open your terminal of choice' but immediately defaults to PowerShell, implicitly prioritizing Windows users.
Recommendations
  • Provide parallel Bash examples for all CLI commands, especially variable assignment and command substitution.
  • Explicitly state that both PowerShell and Bash are supported, and clarify any differences in syntax.
  • Consider showing Bash examples first or side-by-side with PowerShell to avoid implicit Windows prioritization.
  • Add notes or links for Linux/macOS users on installing and using Azure CLI in their environments.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page predominantly uses PowerShell for command-line examples, with no Bash or Linux shell equivalents provided for Azure CLI commands. The tutorial explicitly states PowerShell is used, and all variable assignments and scripting patterns are PowerShell-specific, which may not work as written on Linux/macOS terminals. This creates friction for non-Windows users, who must translate examples to Bash syntax themselves.
Recommendations
  • Provide Bash/Linux shell equivalents for all Azure CLI commands and scripting steps.
  • Clarify that Azure CLI works cross-platform and show examples for both PowerShell and Bash where scripting differs.
  • Reorder or parallelize examples so Linux/macOS users do not feel secondary.
  • Add a note or section for Linux/macOS users on adapting variable assignment and scripting patterns.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates bias towards Windows by exclusively mentioning the PowerShell 'New-SelfSignedCertificate' command for creating self-signed certificates, without providing Linux/macOS alternatives. No Linux or cross-platform command-line examples (such as OpenSSL) are given, and Windows tools are referenced without parity.
Recommendations
  • Include Linux/macOS instructions for creating self-signed certificates, such as using OpenSSL.
  • Provide cross-platform command-line examples wherever Windows-specific tools are mentioned.
  • Explicitly state that steps can be performed on any OS and link to platform-specific guidance where appropriate.
  • Add screenshots or notes relevant to Linux/macOS environments if UI or workflow differs.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently presents PowerShell as the primary scripting example and recommends running scripts in PowerShell locally using Visual Studio Code, which is a Windows-centric workflow. Although Azure CLI examples are provided (which are cross-platform), PowerShell is always mentioned first and with more detail, and there are no explicit Linux/macOS shell examples or guidance for those environments. The instructions for running scripts locally focus on Windows tools and do not mention Linux/macOS alternatives, which may create friction for non-Windows users.
Recommendations
  • Present Azure CLI examples before PowerShell, or alternate the order to avoid Windows-first bias.
  • Explicitly mention that Azure CLI can be run natively on Linux/macOS and provide guidance for those platforms.
  • Add Bash shell examples for ARM template deployment and other tasks, especially where PowerShell syntax is used.
  • Avoid recommending Visual Studio Code with PowerShell as the default local environment; suggest alternatives like VS Code with Bash or native terminal for Linux/macOS.
  • Include troubleshooting notes or tips for Linux/macOS users where workflows may differ.
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-12 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 the first option for deployment, and instructions reference running code in PowerShell locally, Visual Studio Code, or Azure Cloud Shell before mentioning CLI. The CLI instructions also mention running in PowerShell, which is a Windows-centric shell, and the example path separator in the CLI deployment command uses Windows-style backslashes ('src\templates\fhirtemplate.json'), which may confuse Linux/macOS users. Additionally, the Bash prerequisite suggests 'Git Bash' (a Windows tool) before mentioning Bash shells more generally.
Recommendations
  • Present CLI and PowerShell instructions in parallel, or list CLI first to avoid Windows-first bias.
  • In CLI instructions, use POSIX-style forward slashes for file paths (e.g., 'src/templates/fhirtemplate.json') and note that Windows users may need to adjust paths.
  • Clarify that Bash is available natively on Linux/macOS and that Git Bash is only needed for Windows users.
  • Remove references to running CLI commands in PowerShell for non-Windows platforms; instead, mention native terminals for Linux/macOS.
  • Explicitly state that all steps are cross-platform and provide any platform-specific caveats.
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-12 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 option, often listing it before Azure CLI and REST API. Windows-centric tools and patterns (PowerShell, .NET SDK) are mentioned throughout, sometimes without explicit Linux/macOS alternatives or parity in example ordering. While Azure CLI and REST/cURL are referenced, the overall tone and example order suggest a Windows-first approach.
Recommendations
  • Ensure that Azure CLI and cURL examples are presented before or alongside PowerShell examples, especially in step-by-step instructions.
  • Explicitly mention Linux/macOS compatibility and provide example commands for those platforms where possible.
  • Include Bash shell and Linux/macOS terminal screenshots or walkthroughs in addition to PowerShell.
  • Highlight cross-platform tools (e.g., cURL, REST Client) more prominently, and clarify when .NET SDK or PowerShell are Windows-specific.
  • Add notes or sections for Linux/macOS users, addressing any platform-specific setup or troubleshooting.
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
Medium Priority View Details →
Scanned: 2026-01-12 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/macOS alternatives such as Azure CLI or REST API. No Linux/macOS-specific instructions or parity are offered for critical tasks.
Recommendations
  • Add equivalent instructions and examples for creating custom roles using Azure CLI and REST API, which are cross-platform.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide links or examples.
  • Reorder or balance tool recommendations so that Windows and Linux/macOS options are presented equally.
  • Include a note clarifying platform compatibility for each tool mentioned.
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-12 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. Only PowerShell commands are provided for critical configuration steps, with no equivalent Bash, Azure CLI, or cross-platform instructions. The use of PowerShell and references to installing PowerShell modules assume a Windows environment or require Linux/macOS users to install and configure PowerShell separately. No Linux/macOS-specific guidance or CLI examples are given, and Windows-centric tools and patterns are presented first and exclusively.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell commands, as Azure CLI is cross-platform and natively available on Linux/macOS.
  • Include Bash script examples for configuration steps, or at least reference how to run PowerShell on Linux/macOS if PowerShell is required.
  • Add explicit notes or sections for Linux/macOS users, outlining any prerequisites or alternative steps.
  • Present cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools.
  • Review all screenshots and UI instructions to ensure they are not Windows-only (e.g., referencing portal features that look/behave differently on other platforms).
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-12 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 FHIR import. PowerShell is the only command-line tool provided for scripting, with no mention of Linux/macOS alternatives such as Azure CLI, Bash, or REST API examples. The use of PowerShell modules and commands is presented as the default method, and there are no instructions or code samples for Linux/macOS users. This may create friction for non-Windows users attempting to automate or script these steps.
Recommendations
  • Provide equivalent Azure CLI commands for all PowerShell examples, especially for storage account network rule configuration.
  • Include REST API or ARM template examples for platform-agnostic automation.
  • Explicitly mention Linux/macOS compatibility and provide Bash or shell script alternatives where possible.
  • Reorder examples so that platform-neutral methods (e.g., Azure CLI, REST API) are presented before platform-specific ones like PowerShell.
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-12 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, especially in the SMART on FHIR Proxy section. All command-line examples use PowerShell syntax, and there are no equivalent examples for Bash or Linux/macOS terminals. The instructions for cloning repositories, running scripts, and configuring secrets are presented in PowerShell, which may create friction for Linux/macOS users. No explicit mention is made of Linux or cross-platform alternatives, and Windows tools/patterns are shown first and exclusively.
Recommendations
  • Provide Bash equivalents for all PowerShell command-line examples, including repository cloning, base64 encoding, and dotnet user-secrets commands.
  • Explicitly state cross-platform compatibility for the SMART on FHIR app launcher and related tooling.
  • Add notes or sections for Linux/macOS users, including any required dependencies or differences in setup.
  • Where possible, use generic commands (e.g., 'git clone', 'dotnet run') in a way that is platform-neutral, or show both Windows and Linux/macOS variants.
  • Clarify that the tutorial is not Windows-specific and highlight any platform-specific caveats.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation frequently references PowerShell and Windows-centric tools/scripts for critical tasks such as client application registration, access token retrieval, and role assignment. While Azure CLI is mentioned, PowerShell is consistently listed first, and there are no explicit Linux/macOS shell examples or guidance. This creates friction for Linux/macOS users, who may need to adapt instructions or seek additional resources.
Recommendations
  • Provide explicit bash/Linux/macOS shell examples alongside PowerShell, especially for client registration, token retrieval, and role assignment.
  • List Azure CLI and REST API methods before or alongside PowerShell, clarifying cross-platform compatibility.
  • Add a section or note highlighting Linux/macOS support and linking to platform-specific guides.
  • Ensure all code snippets and tool references include Linux/macOS alternatives where possible.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation repeatedly references Azure PowerShell as a primary deployment tool alongside Azure CLI, and lists PowerShell before CLI in multiple sections. There are no explicit Linux/macOS-specific instructions or examples, nor is there mention of Bash or shell scripting alternatives. The 'Deploy to Azure' button and Azure portal methods are platform-neutral, but advanced automation options are described in a way that may imply a Windows-centric workflow.
Recommendations
  • Provide explicit Bash or shell script examples for ARM and Bicep deployments using Azure CLI, demonstrating Linux/macOS workflows.
  • When listing deployment methods, alternate or randomize the order of PowerShell and CLI, or list CLI first to avoid implicit Windows-first bias.
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux/macOS, and link to installation guides for those platforms.
  • Add notes or sections highlighting any platform-specific considerations, such as differences in script execution or environment setup.
  • Where PowerShell is mentioned, also mention alternatives (e.g., Bash) for non-Windows users.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page displays a moderate Windows bias. PowerShell is featured prominently in prerequisites and examples, appearing before CLI/Bash alternatives. Windows tools (PowerShell, Visual Studio Code, Git Bash) are mentioned first or exclusively, and Linux/macOS-specific shell environments are not discussed. While Azure CLI examples are present, the overall structure and language favor Windows users, potentially creating friction for Linux/macOS users.
Recommendations
  • Add explicit instructions and examples for Bash/zsh on Linux/macOS, including native shell commands for token acquisition.
  • Reorder sections so that CLI/Bash examples appear before or alongside PowerShell, not after.
  • Mention native Linux/macOS terminal environments in prerequisites, not just Git Bash (which is Windows-centric).
  • Clarify that cURL is available natively on Linux/macOS and provide installation guidance for those platforms.
  • Ensure all steps can be completed without PowerShell, and highlight cross-platform compatibility.
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-12 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 provides a workaround for configuring the storage account using only PowerShell commands and Windows-centric Az module tooling. There are no equivalent examples or instructions for Linux/macOS users (e.g., Azure CLI, Bash), and PowerShell is presented as the sole method, implying a Windows-first approach.
Recommendations
  • Add Azure CLI (az) command examples for configuring the storage account, which work cross-platform (Linux, macOS, Windows).
  • Explicitly mention that PowerShell commands can be run on Linux/macOS if PowerShell Core is installed, or provide Bash alternatives.
  • Reorder or parallelize examples so that Linux/macOS-friendly methods (Azure CLI, REST API) are presented alongside or before Windows/PowerShell solutions.
  • Clarify tool prerequisites for all platforms, not just Windows.
GitHub Create Pull Request
Healthcare Apis What is the workspace? - Azure Health Data Services ...ob/main/articles/healthcare-apis/workspace-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions PowerShell as a deployment option before CLI, Terraform, or .NET SDK, and does not provide explicit Linux/macOS examples or guidance. There is an implicit bias toward Windows tooling, with no mention of Bash, Linux-specific CLI usage, or cross-platform considerations. This may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Explicitly mention Bash and Linux/macOS CLI usage alongside PowerShell.
  • Provide example deployment scripts for both Windows (PowerShell) and Linux/macOS (Bash/CLI).
  • List cross-platform tools (e.g., Azure CLI, Terraform) before Windows-specific tools like PowerShell.
  • Clarify that all deployment options are available on Linux/macOS, and link to platform-specific setup guides.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias by exclusively recommending Visual Studio Code with the Azure IoT Tools extension for device creation and message sending, without mentioning or providing alternatives for Linux/macOS users (such as CLI tools or cross-platform SDKs). All step-by-step instructions and screenshots are based on Visual Studio Code, a tool most commonly used on Windows, and there is no reference to Linux-native workflows or command-line alternatives. This creates friction for users on Linux/macOS who may prefer or require non-GUI or platform-native solutions.
Recommendations
  • Add instructions for using Azure CLI or Azure IoT CLI extensions to create devices and send messages, which are cross-platform.
  • Mention and provide examples for using platform-agnostic SDKs (e.g., Python, Node.js) to interact with Azure IoT Hub.
  • Include notes or links for Linux/macOS users on how to install and use Visual Studio Code and the Azure IoT Tools extension, or suggest alternative workflows.
  • Provide screenshots or terminal examples for Linux/macOS environments where relevant.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation 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 referenced. This omission may hinder Linux/macOS users who need to generate certificates for confidential client applications.
Recommendations
  • Include instructions and examples for creating self-signed certificates using OpenSSL, which is available on Linux, macOS, and Windows.
  • Explicitly mention that certificate creation can be performed on any platform, and provide platform-agnostic guidance.
  • Where PowerShell commands are given, offer equivalent commands for Bash or other common shells.
  • Add a note or section listing recommended tools for certificate management on Linux/macOS.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation frequently references PowerShell and Windows-centric tools/scripts for managing Azure Health Data Services, often listing them before or alongside Azure CLI. There is a notable emphasis on PowerShell for tasks such as registering client applications, managing permissions, and obtaining access tokens. Linux/macOS equivalents (such as Bash scripting or direct Azure CLI usage) are not explicitly mentioned, and examples or guidance for those platforms are missing.
Recommendations
  • Add explicit examples using Azure CLI and Bash for all tasks currently described with PowerShell.
  • Clarify that Azure CLI is cross-platform and provide instructions for Linux/macOS users.
  • Include sample commands for cURL, Python, and REST client where applicable, especially for authentication and API access.
  • Avoid listing PowerShell before Azure CLI unless there is a technical reason; consider grouping examples by platform.
  • Add a section or note addressing Linux/macOS usage and parity.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page displays a moderate Windows bias. PowerShell is presented as the primary prerequisite and example, with CLI/Bash as a secondary option. Windows tools (PowerShell, Visual Studio Code, Git Bash) are mentioned first or exclusively, and Linux/macOS equivalents (native Bash, Terminal) are not referenced. There are no explicit Linux/macOS examples or instructions, and the CLI section assumes familiarity with Windows-centric tools.
Recommendations
  • Add explicit Linux/macOS prerequisites, such as mentioning native Bash or Terminal.
  • Provide examples using native Bash shell commands, not just PowerShell and Azure CLI.
  • List Linux/macOS installation steps for cURL and Azure CLI.
  • Present CLI/Bash examples before or alongside PowerShell examples.
  • Reference Linux/macOS tools (e.g., Terminal, zsh, bash) and avoid assuming Git Bash is the only Bash option.
GitHub Create Pull Request
← Previous Page 1 of 3 Next →