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 276-300 of 302 flagged pages
Healthcare Apis Get started with Azure API for FHIR .../azure-api-for-fhir/get-started-with-azure-api-fhir.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation references PowerShell as a deployment method before mentioning Azure CLI and ARM templates, and links to a PowerShell-specific quickstart. There are no explicit Linux/macOS examples or mentions of Bash, and the order of presentation favors Windows tooling. However, Azure CLI and ARM templates are also referenced, which are cross-platform.
Recommendations
  • Present Azure CLI and ARM template deployment options before or alongside PowerShell, emphasizing their cross-platform compatibility.
  • Include explicit Bash/Linux/macOS command examples where relevant.
  • Add notes clarifying that Azure CLI and ARM templates work on Linux/macOS, and provide links to platform-specific setup guides.
  • Avoid listing Windows-centric tools (like PowerShell) first unless there is a technical reason.
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
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation presents PowerShell as the primary method for importing the Azure API for FHIR resource application, with the Azure CLI mentioned as an alternative. PowerShell is typically associated with Windows environments, and its example is given before the cross-platform Azure CLI. No Linux/macOS-specific instructions or considerations are provided.
Recommendations
  • Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and works natively on Linux/macOS.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide installation links or prerequisites for those platforms.
  • If PowerShell is required, clarify how to use PowerShell Core on Linux/macOS, or provide equivalent bash commands if possible.
  • Add a note or section addressing Linux/macOS users to ensure parity and reduce friction.
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
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure PowerShell and Azure CLI, with PowerShell (commonly associated with Windows) presented before CLI. The PowerShell section is more detailed, including output examples, while the CLI section is less comprehensive. No Linux-specific tools or shell examples (e.g., Bash) are provided, but the CLI example is cross-platform. There is a slight Windows bias in tool ordering and example depth.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Provide equally detailed output examples for Azure CLI, not just PowerShell.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide any relevant shell usage tips (e.g., Bash syntax).
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, if relevant, or link to cross-platform installation guides.
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
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for deploying resources, but consistently lists PowerShell (a Windows-centric tool) first and recommends running scripts in PowerShell locally in Visual Studio Code. There is a subtle Windows-first bias in ordering and tool recommendations, but Azure CLI examples (cross-platform) are present throughout. No critical steps are Windows-only, and Linux/macOS users can complete all tasks using Azure CLI.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or list Azure CLI first to emphasize cross-platform support.
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows, and recommend it for non-Windows users.
  • Add notes or sections highlighting Linux/macOS usage, such as running Azure CLI in native terminals.
  • Avoid recommending PowerShell in Visual Studio Code as the default local environment; mention Bash or other shells for Linux/macOS.
  • Consider including screenshots or references for Linux/macOS environments where appropriate.
GitHub Create Pull Request
Healthcare Apis Access Azure Health Data Services using REST Client ...ain/articles/healthcare-apis/fhir/using-rest-client.md
Low Priority View Details →
Scanned: 2026-01-14 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 mentioning PowerShell before Bash in the section about running scripts in Visual Studio Code. The example and screenshot for PowerShell are shown first, followed by CLI (which is ambiguous and could refer to Bash or other shells). There are no explicit Linux/macOS examples, but the instructions are generally cross-platform due to VS Code's support for multiple terminals.
Recommendations
  • Explicitly mention Bash or other Linux/macOS shells alongside PowerShell, and provide example screenshots for both.
  • Clarify that the REST Client extension and .http files work identically on Windows, Linux, and macOS.
  • Where 'CLI' is referenced, specify which shell (e.g., Bash, zsh) and provide a sample command for Linux/macOS users.
  • Consider alternating the order of PowerShell and Bash examples, or present them side-by-side to avoid implicit prioritization.
GitHub Create Pull Request
Healthcare Apis Deploy Azure Health Data Services FHIR service using Bicep ...in/articles/healthcare-apis/fhir/fhir-service-bicep.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for all deployment steps, but PowerShell (a Windows-centric tool) is consistently presented first in prerequisites and code tabs. The CLI instructions mention Bash and Git Bash, but the Bash example is secondary to PowerShell, and Linux/macOS tooling is not discussed in detail. There is a subtle Windows bias in the ordering and tool emphasis, though Linux users can complete all tasks using Azure CLI.
Recommendations
  • Present CLI/Bash examples before PowerShell to reflect cross-platform parity.
  • Explicitly mention Linux/macOS compatibility and native shells (e.g., Terminal, zsh, bash) in prerequisites, not just Git Bash for Windows.
  • Add a note clarifying that Azure CLI works natively on Linux/macOS and provide installation links for those platforms.
  • Ensure that instructions do not assume Windows as the default environment.
  • Consider adding screenshots or references for Linux/macOS terminal usage.
GitHub Create Pull Request
Healthcare Apis Get started with the MedTech service - Azure Health Data Services .../blob/main/articles/healthcare-apis/iot/get-started.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation references Azure PowerShell, Azure CLI, and REST API as options for deployment, but does not provide any concrete examples or command snippets for any platform. However, it lists 'Azure PowerShell' before 'Azure CLI', which can subtly suggest a Windows-first approach. There are no explicit Linux/macOS examples or guidance, and the only tool with a strong Windows association (PowerShell) is mentioned first.
Recommendations
  • Provide explicit, step-by-step examples for both Azure CLI (cross-platform) and Azure PowerShell (Windows/macOS/Linux).
  • When listing tools, alternate the order or mention Azure CLI first, as it is cross-platform and widely used on Linux/macOS.
  • Include example commands for each deployment step using both Azure CLI and PowerShell.
  • Add a note clarifying that all tools are available cross-platform, and link to installation guides for each OS.
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
Low 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 presents PowerShell (a Windows-centric tool) as the first method for registering the resource application, with Azure CLI as an alternative. No explicit Linux/macOS examples or guidance are provided, and the PowerShell example is shown before the cross-platform Azure CLI example.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell examples to avoid Windows-first bias.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide installation or usage notes for those platforms.
  • If PowerShell is required, clarify how to use PowerShell Core on Linux/macOS, or provide equivalent bash commands if possible.
  • Include a note or section for Linux/macOS users to ensure parity and clarity.
GitHub Create Pull Request
Healthcare Apis Deploy Azure Health Data Services FHIR service using Bicep ...in/articles/healthcare-apis/fhir/fhir-service-bicep.md
Low 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 presents both Azure CLI and Azure PowerShell examples for all deployment steps, but consistently lists PowerShell (a Windows-centric tool) first in prerequisites and code tabs. The CLI instructions mention Bash shells, but recommend Git Bash (a Windows tool) rather than native Linux/macOS terminals. There are no explicit Linux/macOS-specific instructions or screenshots, and the overall structure subtly prioritizes Windows tooling and patterns.
Recommendations
  • Alternate the order of CLI and PowerShell tabs so that CLI (cross-platform) is shown first.
  • Explicitly mention native Bash shells for Linux/macOS users in prerequisites, not just Git Bash for Windows.
  • Add notes or sections clarifying that all CLI commands work natively on Linux and macOS terminals.
  • Include screenshots or terminal examples from Linux/macOS environments.
  • Avoid referring to Windows-specific tools (like Git Bash) as the default Bash shell option.
GitHub Create Pull Request
Healthcare Apis Authentication and authorization in Azure Health Data Services ...ticles/healthcare-apis/authentication-authorization.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page shows mild Windows bias by referencing Windows-specific tools (PowerShell) and endpoints (sts.windows.net) before or alongside cross-platform alternatives. The list of tools for obtaining access tokens mentions PowerShell and REST Client in Visual Studio Code before CLI and curl, which are more platform-neutral. No Linux/macOS-specific examples or instructions are provided, but the content is generally applicable across platforms.
Recommendations
  • Provide explicit Linux/macOS examples for obtaining access tokens, such as using curl or Azure CLI.
  • List cross-platform tools (curl, Azure CLI) before Windows-specific ones (PowerShell, Visual Studio Code REST Client).
  • Include sample commands for both Windows (PowerShell) and Linux/macOS (bash/curl) where relevant.
  • Clarify that the instructions and tools are applicable to all platforms, and highlight any platform-specific differences if they exist.
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
Low 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 displays a mild Windows bias by listing PowerShell instructions before CLI, referencing Git Bash for Windows as the Bash shell example, and using PowerShell as the primary scripting language for non-portal automation. While Linux/macOS users can use Azure CLI and Bash, the examples and tool recommendations tend to favor Windows environments and tools first.
Recommendations
  • Present CLI/Bash examples before or alongside PowerShell to avoid Windows-first ordering.
  • Mention native Bash shells on Linux/macOS (e.g., Terminal, GNOME Terminal) in addition to Git Bash for Windows.
  • Provide explicit notes or examples for macOS/Linux users, such as verifying Azure CLI installation on those platforms.
  • Balance references to PowerShell and CLI, ensuring both are treated as first-class options.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and highlight cross-platform compatibility.
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
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Azure PowerShell (a Windows-centric tool) before Azure CLI in the tab order, and provides a detailed PowerShell example with output, while the Azure CLI example is less detailed and lacks output. This ordering and emphasis may subtly favor Windows users and PowerShell workflows, although Azure CLI is cross-platform and preferred by many Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell, or alternate tab order based on detected OS.
  • Provide equally detailed examples and sample outputs for both Azure CLI and PowerShell.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, if relevant.
  • Ensure all referenced tools and commands are available on Linux/macOS, and link to installation guides for both platforms.
GitHub Create Pull Request
Healthcare Apis Data conversion for Azure API for FHIR ...les/healthcare-apis/azure-api-for-fhir/convert-data.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by exclusively referencing the Azure portal (a web UI often associated with Windows workflows) for configuration steps and showing screenshots that appear to be from Windows environments. CLI instructions use the Azure CLI, which is cross-platform, but there are no explicit Linux/macOS-specific instructions, examples, or screenshots. There is no mention of Linux-specific tools, shell commands, or considerations for Linux/macOS users. The Visual Studio Code extension is cross-platform, but the documentation does not clarify this. No PowerShell-specific commands are present, and the CLI examples are not Windows-only.
Recommendations
  • Add explicit Linux/macOS instructions or notes where relevant (e.g., CLI installation, file paths, environment variables).
  • Include screenshots or examples from Linux/macOS environments to demonstrate parity.
  • Clarify that Azure CLI and Visual Studio Code extension are cross-platform.
  • Mention any OS-specific considerations for template management, registry access, or firewall configuration.
  • Where portal navigation is described, note that it is accessible from any OS via browser.
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
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for deploying resources, but PowerShell instructions and terminology (e.g., 'Run the code in PowerShell locally in Visual Studio Code') are presented first and more prominently. There is a subtle preference for Windows-centric tools and workflows, such as PowerShell and Visual Studio Code, which may create friction for Linux/macOS users. However, Azure CLI examples are included and are cross-platform.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly note that Azure CLI commands can be run natively on Linux/macOS and in Azure Cloud Shell, while PowerShell is more Windows-centric.
  • Remove or clarify references to 'PowerShell locally in Visual Studio Code' to avoid implying Windows-only workflows.
  • Add a brief section or note highlighting Linux/macOS compatibility and any required setup for those platforms.
  • Ensure screenshots and instructions for Azure Portal are not Windows-specific (e.g., avoid references to Windows UI conventions).
GitHub Create Pull Request
Healthcare Apis Access Azure Health Data Services using REST Client ...ain/articles/healthcare-apis/fhir/using-rest-client.md
Low Priority View Details →
Scanned: 2026-01-13 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 mentioning PowerShell before Bash when discussing integrated terminal usage in Visual Studio Code. The PowerShell example and screenshot are presented first, followed by CLI/Bash, which may subtly prioritize Windows workflows. However, the main tutorial is platform-agnostic, focusing on VS Code and the REST Client extension, which are cross-platform.
Recommendations
  • Present Bash and PowerShell examples side-by-side or alternate their order to avoid implying preference.
  • Explicitly state that all steps work identically on Windows, Linux, and macOS.
  • Include screenshots of Bash terminal usage alongside PowerShell to visually reinforce Linux parity.
  • Add a note clarifying that the REST Client extension and .http files are fully supported on Linux/macOS.
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
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation consistently mentions Azure PowerShell before Azure CLI when describing deployment methods, and references to PowerShell are present in every advanced deployment section. This ordering and emphasis may subtly prioritize Windows-centric tooling, as PowerShell is most commonly associated with Windows environments, even though it is cross-platform. No Linux-specific tools, shell examples, or platform notes are provided, and the 'Deploy to Azure' button relies on the Azure portal, which is platform-neutral but often associated with Windows workflows.
Recommendations
  • Alternate the order of Azure CLI and PowerShell mentions, or list Azure CLI first to reflect its popularity among Linux/macOS users.
  • Explicitly state that both Azure CLI and PowerShell are cross-platform, and provide links to installation guides for Linux/macOS.
  • Include example commands for both Azure CLI and PowerShell in referenced deployment guides, or clarify parity.
  • Add a note that all deployment methods are supported on Linux/macOS, and mention any platform-specific caveats if present.
  • Consider including a section or quick note for Linux/macOS users to reassure them of full support.
GitHub Create Pull Request
Healthcare Apis Get started with the MedTech service - Azure Health Data Services .../blob/main/articles/healthcare-apis/iot/get-started.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation references Azure PowerShell before Azure CLI and REST API, and does not provide any explicit Linux/macOS-specific instructions or examples. All deployment steps are described in a platform-neutral way, but the mention of PowerShell first may subtly prioritize Windows workflows. No command-line examples are given, so there is no overt Windows-only content, but Linux users may perceive a slight bias.
Recommendations
  • When listing deployment tools, alternate the order or explicitly mention that Azure CLI and REST API are cross-platform and suitable for Linux/macOS users.
  • Provide example commands for both Azure PowerShell and Azure CLI, or indicate which instructions are platform-agnostic.
  • Add notes or links to documentation for using Azure CLI on Linux/macOS.
  • Ensure that any referenced scripts or tools are available and documented for all major platforms.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/fhir/convert-data-configuration.md ...les/healthcare-apis/fhir/convert-data-configuration.md
Low Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display overt Windows bias in terms of command-line examples or tool recommendations. However, it lacks any mention of Linux-specific workflows, tools, or command-line instructions, and does not provide parity for users who may be operating outside of the Azure Portal or Visual Studio Code environments (which are cross-platform but often perceived as Windows-centric). There are no CLI, shell, or scripting examples for Linux users, nor is there guidance for using non-GUI or non-Microsoft tooling.
Recommendations
  • Add examples for managing templates using Azure CLI or Azure PowerShell, and ensure that CLI examples are provided for both Windows (PowerShell) and Linux (Bash).
  • Explicitly mention that Visual Studio Code and the FHIR Converter extension are available on Linux and macOS, not just Windows.
  • Provide alternative instructions for pushing templates to Azure Container Registry using Docker CLI commands (which are platform-agnostic), including sample Bash scripts.
  • Include troubleshooting or verification steps that can be performed from Linux environments, such as using curl or wget for API calls.
  • Where screenshots or UI navigation are shown, note any differences (if any) for users on non-Windows platforms.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/davinci-pdex-tutorial.md ...hcare-apis/azure-api-for-fhir/davinci-pdex-tutorial.md
Low Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific instructions or examples, but it also does not include any Windows- or PowerShell-specific commands, tools, or patterns. However, there is a lack of explicit Linux (or cross-platform) command-line examples or instructions, which could leave Linux users unsure about how to perform certain actions, such as loading sample data or interacting with the API.
Recommendations
  • Add explicit instructions or examples for loading sample data using cross-platform tools such as curl or HTTPie, with command-line snippets that work on both Windows and Linux.
  • If any sample .http files are intended for use with a specific tool (e.g., VS Code REST Client, Postman), clarify this and provide cross-platform usage notes.
  • Include a section or callout noting that all examples are platform-agnostic and can be run from any OS with appropriate tools.
  • If there are any scripts or automation steps, provide both PowerShell and Bash (or generic shell) equivalents.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/pull-dicom-changes-from-change-feed.md ...care-apis/dicom/pull-dicom-changes-from-change-feed.md
Low Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only a C# example for accessing DICOM Change Feed logs, with no mention of Linux-specific tools, patterns, or alternative languages/platforms (such as Python or Bash) that are commonly used on Linux. There is no explicit Windows bias in terms of tools or PowerShell, but the lack of Linux-oriented examples or cross-platform guidance may disadvantage Linux users.
Recommendations
  • Add code examples in additional languages popular on Linux, such as Python (using requests or pydicom) or Bash (using curl).
  • Explicitly mention that the REST API can be accessed from any platform, and provide generic HTTP request examples.
  • Include instructions or notes on how to run the C# example on Linux (e.g., using .NET Core/SDK on Linux).
  • Where possible, provide parity in tooling and setup instructions for both Windows and Linux environments.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/davinci-pdex-tutorial.md ...hcare-apis/azure-api-for-fhir/davinci-pdex-tutorial.md
Low Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific command-line examples, but it references sample HTTP files and REST requests without specifying how to execute them. There are no explicit instructions or examples for either Windows (e.g., PowerShell, Windows tools) or Linux (e.g., curl, bash). However, the lack of any mention of Linux tools or command-line usage may disadvantage Linux users who are looking for parity or clear instructions.
Recommendations
  • Add explicit examples for loading sample HTTP files using cross-platform tools such as curl or HTTPie, with command-line snippets for both Windows (PowerShell/cmd) and Linux/macOS (bash).
  • If any sample files are intended to be used with specific tools (e.g., REST clients, Postman, curl), clarify this and provide instructions for both Windows and Linux users.
  • Include a section or note on how to execute the provided .http files on different platforms, mentioning any platform-agnostic tools (e.g., VS Code REST Client extension, Postman) and how to use them.
  • Ensure that any future additions of command-line or scripting examples are provided for both Windows and Linux environments, or use platform-neutral syntax where possible.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/azure-api-for-fhir/tutorial-web-app-test-postman.md ...is/azure-api-for-fhir/tutorial-web-app-test-postman.md
Low Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or instructions, but it also fails to mention or demonstrate any tools or commands for either Windows or Linux. This omission can be considered a bias of omission, as Linux users are not given guidance or parity in testing the FHIR API connection.
Recommendations
  • Add explicit examples for both Windows (e.g., using PowerShell or curl in Command Prompt) and Linux (e.g., using curl or httpie in a terminal) to demonstrate how to test the FHIR API connection.
  • Mention cross-platform tools and provide sample commands for each platform.
  • Clarify that the instructions are platform-agnostic if no platform-specific steps are needed, or explicitly state which tools are recommended for each OS.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/deidentification/configure-private-endpoints.md ...e-apis/deidentification/configure-private-endpoints.md
Low Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively describes how to configure private endpoint network access using the Azure portal, with no command-line examples or automation guidance. There are no references to Windows-specific tools or PowerShell, but there is also a lack of parity for Linux users: no CLI (Azure CLI), Bash, or cross-platform automation examples are provided. This omission can disadvantage users who prefer or require non-GUI, scriptable, or Linux-based workflows.
Recommendations
  • Add Azure CLI examples for all major steps (creating private endpoints, configuring network access, approving/rejecting/removing connections), as the CLI is cross-platform and widely used on Linux.
  • Include Bash script snippets where appropriate to demonstrate automation.
  • Reference both portal and CLI documentation links where available.
  • Explicitly mention that all operations can be performed via the Azure CLI or PowerShell, and provide links or examples for both.
  • Ensure that any future updates include parity between portal, PowerShell, and CLI/Bash instructions to support both Windows and Linux users.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicomweb-standard-apis-python.md ...healthcare-apis/dicom/dicomweb-standard-apis-python.md
Low Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page is largely cross-platform, as it uses Python and avoids OS-specific commands or tools. However, there is a subtle 'windows_first' bias in the authentication section, where the instructions for obtaining an Azure access token reference the Azure CLI without clarifying its cross-platform availability or mentioning alternatives (such as Azure Cloud Shell, Bash, or PowerShell). The documentation assumes familiarity with the Azure CLI and does not explicitly reassure Linux/macOS users that all steps and tools are supported on their platforms.
Recommendations
  • Explicitly state that the Azure CLI is cross-platform and works on Windows, Linux, and macOS.
  • Mention that authentication can be performed using Azure Cloud Shell (browser-based, OS-agnostic) or Bash, not just the Azure CLI.
  • If referencing the Azure CLI, provide a link to installation instructions for all platforms.
  • Add a note confirming that all code examples are OS-independent and tested on both Windows and Linux.
  • If any file path examples are shown, use POSIX-style paths or clarify path conventions for both Windows and Linux.
  • If any troubleshooting steps are needed for authentication, mention platform-specific nuances if they exist.
GitHub Create Pull Request
Healthcare Apis https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/pull-dicom-changes-from-change-feed.md ...care-apis/dicom/pull-dicom-changes-from-change-feed.md
Low Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only a C# example for accessing DICOM Change Feed logs, with no mention of Linux-specific tools, environments, or alternative languages commonly used on Linux (such as Python or Bash). There are no references to Windows-specific tools, but the lack of Linux-oriented examples or cross-platform guidance may disadvantage Linux users.
Recommendations
  • Add code examples in additional languages popular on Linux, such as Python (using requests or pydicom) or Bash (using curl).
  • Explicitly mention that the C# example can be run cross-platform using .NET Core/.NET 6+, and provide instructions for doing so on Linux.
  • Include sample REST API calls using curl or httpie to demonstrate platform-agnostic access.
  • Clarify any platform dependencies or prerequisites for the DICOM client package, and provide installation instructions for both Windows and Linux.
GitHub Create Pull Request
← Previous Page 12 of 13 Next →