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 51-66 of 66 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-12 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 option before mentioning Azure CLI and ARM templates, and links to a PowerShell-specific quickstart. This ordering and emphasis may subtly prioritize Windows tooling. However, Azure CLI is also mentioned, and no examples or instructions are exclusively Windows-specific; screenshots and portal instructions are cross-platform.
Recommendations
  • List deployment options in a neutral or alphabetical order (e.g., 'using Azure CLI, PowerShell, or ARM template') to avoid implicit prioritization.
  • Ensure that Linux/macOS equivalents (such as Bash/CLI) are given equal prominence and example coverage in linked quickstarts.
  • Explicitly state that all deployment methods (CLI, PowerShell, ARM templates) are cross-platform where applicable.
  • Add a note clarifying that Azure CLI works on Windows, Linux, and macOS.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Azure PowerShell (commonly associated with Windows) before Azure CLI (cross-platform), and provides a detailed PowerShell example with output, while the CLI example is less detailed. There is no explicit mention of Linux/macOS-specific considerations, nor are Linux shell examples (e.g., Bash) provided. However, the CLI instructions are present, and no steps are strictly Windows-only.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Provide example output for Azure CLI commands, matching the detail given for PowerShell.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide links to installation guides for those platforms.
  • Add notes or examples for Bash scripting or automation on Linux.
  • Ensure parity in troubleshooting steps for both PowerShell and CLI.
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-12 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 are presented first in each section. The instructions suggest running code in PowerShell locally in Visual Studio Code, which is a Windows-centric workflow. There is no explicit mention of Linux/macOS compatibility for PowerShell, nor are Bash shell or Linux-specific instructions prioritized or highlighted. The use of screenshots and UI walkthroughs is platform-neutral, but command-line guidance leans toward Windows-first patterns.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to reflect cross-platform parity.
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows, and clarify that PowerShell Core is available cross-platform if relevant.
  • Include Bash shell examples for common tasks, especially for resource deployment, to better support Linux users.
  • Add notes or callouts for Linux/macOS users regarding any platform-specific considerations (e.g., authentication, environment setup).
  • Where Visual Studio Code is mentioned, clarify that it is available on Linux/macOS and Windows.
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-12 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 (cross-platform) and Azure PowerShell (Windows-centric) instructions in parallel tabs throughout. However, Windows/PowerShell is consistently listed first in prerequisites and code sections. The prerequisites for CLI mention Git Bash (a Windows workaround for Bash), which may confuse Linux/macOS users. There is a slight emphasis on Windows tools and patterns, but Linux/macOS users can complete all tasks using Azure CLI.
Recommendations
  • Alternate the order of CLI and PowerShell tabs so CLI is presented first in some sections.
  • Clarify that Bash is natively available on Linux/macOS and only needs Git Bash on Windows.
  • Add explicit notes that all CLI instructions work on Linux and macOS without modification.
  • Consider including a short section or callout for Linux/macOS users to confirm parity.
  • Reduce references to Windows-specific tools (e.g., Git Bash) when describing CLI prerequisites.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates a mild Windows bias by highlighting PowerShell usage in Visual Studio Code before mentioning Bash, and by providing a screenshot specifically for PowerShell. While CLI/Bash is mentioned, the PowerShell example and screenshot are presented first, and there are no explicit Linux/macOS-specific instructions or screenshots. However, the main workflow using the REST Client extension is cross-platform and does not depend on Windows-only tools.
Recommendations
  • Present Bash and PowerShell examples/screenshots side-by-side, or alternate their order in the documentation.
  • Explicitly mention that all steps work on Linux/macOS as well as Windows.
  • Include screenshots of Bash terminal usage in VS Code on Linux/macOS.
  • Add a note clarifying that the REST Client extension and .http files are platform-independent.
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
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation mentions the provision of PowerShell, CLI scripts, and ARM templates for deployment and configuration, with PowerShell listed first. There is a slight Windows-first bias in the order of tools mentioned, but CLI and ARM templates are also referenced, which are cross-platform. No explicit Windows-only examples or tools are present, and Linux/macOS users are not excluded from performing the described tasks.
Recommendations
  • List CLI and ARM template options before PowerShell, or present all options equally.
  • Explicitly state that CLI and ARM templates are cross-platform and provide example usage for Linux/macOS.
  • If scripts are provided, ensure Linux/macOS shell script equivalents are available and documented.
  • Add a note clarifying platform compatibility for all deployment/configuration tools.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation refers to Azure PowerShell, Azure CLI, and REST API scripts as options for completing deployment steps, but does not provide any concrete examples or instructions for any platform. However, the mention of Azure PowerShell before Azure CLI and REST API, and the absence of explicit Linux/macOS guidance or examples, suggests a subtle Windows-first bias. All deployment instructions reference the Azure portal, which is cross-platform, but there are no command-line examples for either Windows or Linux.
Recommendations
  • Provide explicit examples for both Azure CLI and Azure PowerShell, noting platform compatibility.
  • Ensure that Linux/macOS users are guided to use Azure CLI and REST API methods, with step-by-step instructions.
  • Add notes clarifying which tools are available on which platforms, and link to installation guides for Azure CLI on Linux/macOS.
  • Consider including sample bash scripts for Linux users alongside PowerShell scripts for Windows users.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily references Azure Portal (a web interface, but often associated with Windows workflows) and Azure CLI, but does not provide explicit Linux/macOS-specific examples or mention platform differences. There is no mention of PowerShell, but the CLI examples and instructions are generic and could apply to any OS. However, the documentation does not clarify Linux/macOS compatibility, nor does it provide parity examples for Linux shell usage or highlight cross-platform considerations. The use of Visual Studio Code extension is cross-platform, but the workflow descriptions and screenshots are Windows-centric (Azure Portal UI).
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS and provide example shell commands (e.g., bash) where relevant.
  • Include screenshots or instructions for Linux/macOS environments, especially for steps that involve file paths, shell commands, or installing CLI tools.
  • Mention any platform-specific requirements or differences (e.g., authentication, file system paths) if applicable.
  • Add a note clarifying that the Visual Studio Code extension and Azure CLI are supported on Linux/macOS, and provide links to installation guides for those platforms.
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
Low Priority View Details →
Scanned: 2026-01-11 06:20
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 identity object ID lookup tasks. PowerShell is primarily associated with Windows, and the use of PowerShell-centric commands may create friction for Linux/macOS users. However, Azure CLI examples are provided for each task, which are cross-platform.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is natively cross-platform.
  • Explicitly state that Azure CLI works on Windows, Linux, and macOS, and link to installation instructions for non-Windows platforms.
  • Add a short note clarifying that PowerShell Core is available on Linux/macOS, or provide Bash script alternatives where relevant.
  • Consider grouping examples by platform or providing tabs labeled 'Windows (PowerShell)' and 'Cross-platform (Azure CLI)'.
GitHub Create Pull Request
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions deployment via PowerShell before CLI and ARM templates, and references PowerShell in the context of quickstart guides. This ordering and emphasis can be interpreted as a mild Windows bias, as PowerShell is traditionally associated with Windows environments, even though it is now cross-platform. No explicit Linux/macOS examples or tools are provided, and the CLI is mentioned after PowerShell.
Recommendations
  • Present deployment options in a neutral order (e.g., CLI, PowerShell, ARM template) or group them together without prioritizing Windows-centric tools.
  • Explicitly mention that Azure CLI and PowerShell are available on Linux/macOS, and provide links or notes for installation on those platforms.
  • Include example commands for both Azure CLI and PowerShell, or clarify which examples are cross-platform.
  • Add a brief section or note for Linux/macOS users to ensure parity and clarity.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides detailed examples for Azure PowerShell before Azure CLI, with PowerShell commands and output shown first. This ordering can subtly favor Windows users, as PowerShell is native to Windows, while CLI is more cross-platform. However, CLI instructions are present and complete, and no critical functionality is missing for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more universally available across platforms.
  • Explicitly note that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and link to installation guides for each.
  • Add a short section clarifying tool parity and platform support, reassuring Linux/macOS users.
  • Ensure that all command outputs and examples are shown for both CLI and PowerShell, if they differ.
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-11 06:20
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 consistently presented first and with more detail. There is a subtle Windows bias in the ordering and language, as PowerShell is traditionally associated with Windows environments, and the instructions assume familiarity with Windows-centric tools. However, Azure CLI examples are present and usable on Linux/macOS, and no critical steps are Windows-only.
Recommendations
  • Present Azure CLI examples before PowerShell, or side-by-side, to signal equal support for Linux/macOS users.
  • Explicitly mention that Azure CLI works on Linux/macOS and can be run in native terminals, not just Azure Cloud Shell.
  • Add notes or links for installing Azure CLI and PowerShell on Linux/macOS, if needed.
  • Avoid language that assumes Visual Studio Code or PowerShell as the default local environment.
  • Include screenshots or instructions for Linux/macOS environments where relevant (e.g., terminal usage, file paths).
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-11 06:20
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 deployment, resource review, and cleanup. However, PowerShell (a Windows-centric tool) is consistently listed first in prerequisites and example tabs, and Windows-specific tools (e.g., Git Bash for Windows) are mentioned before native Linux/macOS shells. There is a subtle but consistent preference for Windows/PowerShell workflows, which may create friction for Linux/macOS users.
Recommendations
  • List CLI (cross-platform) examples before PowerShell examples in all sections.
  • In prerequisites, mention Bash shells generically before referencing Git Bash for Windows.
  • Explicitly state that Azure CLI commands work natively on Linux/macOS terminals.
  • Add notes clarifying that PowerShell is available cross-platform, but CLI is often preferred on Linux/macOS.
  • Ensure parity in troubleshooting and tips for Linux/macOS users, not just Windows/PowerShell.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates minor Windows bias by mentioning PowerShell before Bash when discussing integrated terminal usage in VS Code. PowerShell is shown first in both text and imagery, which may subtly prioritize Windows users. However, the main workflow (using REST Client in VS Code) is fully cross-platform, and Linux/macOS users are not blocked from following the instructions.
Recommendations
  • Alternate the order of PowerShell and Bash/CLI examples, or present them side-by-side to emphasize parity.
  • Include explicit references to Linux/macOS environments when discussing terminal usage (e.g., 'You can use PowerShell, Bash, or other shells depending on your OS').
  • Add screenshots or examples showing Bash or other non-Windows terminals in use.
  • Clarify that all steps are applicable on Linux/macOS as well as Windows.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation mentions Azure PowerShell as a deployment option before Azure CLI and REST API, which may suggest a Windows-first approach. There are no explicit Linux/macOS-specific examples or guidance, and no mention of platform-specific considerations. All referenced deployment guides point to Azure Portal or general Azure tools, but PowerShell is listed first, and there are no Linux shell or macOS terminal examples.
Recommendations
  • List Azure CLI before Azure PowerShell when mentioning cross-platform deployment options, as CLI is natively supported on Linux/macOS.
  • Provide explicit Linux/macOS terminal examples (e.g., bash commands) alongside PowerShell examples.
  • Add notes clarifying that all deployment steps can be completed on Linux/macOS using Azure CLI or REST API.
  • Include links to platform-specific setup guides for Azure CLI and REST API usage on Linux/macOS.
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
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation mentions the provision of PowerShell, CLI scripts, and ARM templates for deployment and configuration, listing PowerShell first. There is a slight bias towards Windows tooling and patterns, as PowerShell is a Windows-centric technology and is mentioned before CLI (which is cross-platform). No explicit Linux/macOS examples or tools are provided, and there is no indication that Linux-specific instructions or parity are considered.
Recommendations
  • Ensure that CLI (az CLI) examples are provided and prioritized alongside or before PowerShell, as CLI is cross-platform.
  • Explicitly mention Linux/macOS compatibility for deployment scripts and tools.
  • Provide Bash script examples or instructions for common Linux/macOS scenarios.
  • Clarify that ARM templates and CLI can be used on any platform, not just Windows.
  • If PowerShell is required, note that PowerShell Core is available cross-platform and provide installation guidance for Linux/macOS.
GitHub Create Pull Request
← Previous Page 3 of 3 Next →