Azure Health Insights

66
Total Pages
64
Linux-Friendly Pages
2
Pages with Bias
3.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (2)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-health-insights/includes/example-inference-follow-up-communication-json-request.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Powershell Heavy Missing Linux Example
Summary:
The documentation page references 'Powerscribe', a tool that is primarily Windows-based, and includes a sample document with Windows-style line endings (\r\n). There are no Linux or cross-platform equivalents mentioned, nor are there examples or references to Linux tools or patterns. The documentation does not provide parity for Linux users.
Recommendations:
  • Include examples or references to Linux-compatible tools for radiology report distribution or dictation (e.g., open-source alternatives or cross-platform solutions).
  • Ensure sample data uses platform-neutral line endings (\n) or clarify that the API is agnostic to line ending style.
  • Add a note or section describing how Linux users can interact with or process the data, including any relevant command-line tools or scripts.
  • If Powerscribe is required, clarify its platform limitations and suggest alternatives for non-Windows environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-health-insights/use-containers.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation exhibits mild Windows bias by mentioning Windows-specific Docker configuration before Linux, specifically noting that 'On Windows, Docker must also be configured to support Linux containers.' Additionally, PowerShell and Windows tools are referenced as automation options before Azure CLI, and there is an implicit assumption of familiarity with Windows conventions (e.g., line continuation character guidance). However, the majority of examples and commands are cross-platform (bash/curl/Docker), and Linux is not excluded from any instructions.
Recommendations:
  • Explicitly provide Linux-specific guidance alongside Windows notes, such as clarifying Docker installation and configuration steps for both platforms.
  • When mentioning automation options, list cross-platform tools (e.g., Azure CLI, bash scripts) before or alongside Windows-specific tools like PowerShell.
  • Where line continuation characters are discussed, provide both Windows (^) and Linux (\) examples, or link to platform-specific documentation.
  • Consider adding a short section or callout confirming that all commands are intended to work on both Linux and Windows (with Docker configured for Linux containers), and provide troubleshooting tips for both environments.