Physicians Fail to Detect Flawed AI Treatment Recommendations Even When Evidence Contradicts Them, New Study Finds
A new study has demonstrated that physicians often fail to notice when artificial intelligence systems provide flawed treatment recommendations, even when clear evidence of the error is presented directly to them. The research highlights a persistent problem known as automation bias, in which humans tend to place excessive trust in algorithmic outputs that appear objective and computationally derived.
In the experiment, 223 physicians anonymously participated in a series of online scenarios. They were asked to imagine treating patients with a rare disease and to decide whether to administer an experimental therapy whose effectiveness had not yet been confirmed. Before making their decisions, participants received recommendations from an AI system that divided patients into groups based on predicted likelihood of benefit. After selecting patients for treatment, the doctors reviewed actual treatment outcomes and were asked to evaluate the reliability of the AI suggestions.
Researchers deliberately designed the experiments so that the AI predictions would conflict with real results. In the first series, the therapy produced a uniform moderate effect across all patients, yet the algorithm created the false impression that certain groups benefited more than others. In the second series, the treatment was completely ineffective for everyone, but the majority of participants still did not conclude that the therapy offered no benefit at all.
Even after reviewing the outcome data, most doctors continued to view the AI as a reliable source of guidance. They found it difficult to change their initial opinions when new evidence contradicted the algorithm’s conclusions. This effect persisted regardless of the physicians’ level of medical experience, showing that human oversight alone does not automatically catch AI mistakes.
The study carries important implications for the growing use of AI tools in medicine. Such systems are already being deployed or tested to assess complication risks, select treatment strategies, and identify patients requiring closer monitoring. While these tools are intended only as decision-support aids, the research shows that flawed recommendations can still influence clinical choices, potentially leading doctors to withhold effective treatments or administer ineffective ones.
Because the study was conducted in a simulated environment rather than real clinical settings, researchers could precisely control conditions and know exactly where the algorithm was wrong. The authors conclude that simply warning users about possible errors is insufficient. They recommend implementing structured procedures such as requiring an independent evaluation of each case before the AI suggestion is shown, mandating written explanations for agreement with the algorithm, and conducting regular reviews of cases where AI predictions were not confirmed by actual outcomes.
Related articles
OAuth Authorization Server Built Without Storing User Profiles
The article details the evolution of an OAuth Authorization Server that deliberately avoids storing user profiles, relying instead on external identity providers for authentication. It addresses three core constraints: hundreds of dynamically created isolated APIs, a public SPA client without a BFF, and the inability of resources to query the AS on every request. The design separates concerns so the AS handles only clients, tenants, grants, audiences, scopes, keys, sessions, and token issuance while the Main API owns profiles and roles. Tokens are managed securely inside a Service Worker using a custom FedCM grant, eliminating races across tabs and reducing XSS exposure. The approach minimizes blast radius, simplifies compliance, and keeps the AS replaceable without affecting product domain logic.
Why a 202-Character License Key Uses ECDSA P-256 Instead of Ed25519 or RSA
A developer building offline license verification for a .NET desktop application evaluated Ed25519, RSA, and ECDSA P-256 before selecting the last option. The decision was driven by the requirement for zero external dependencies, keys short enough for manual entry from email, and support for key rotation without breaking existing licenses. Although Ed25519 offers faster verification and a smaller public key, it is absent from System.Security.Cryptography in both .NET 8 and .NET 10, with API approval only targeted for version 11. RSA-2048 produces signatures too long for practical use, resulting in a 571-character Base32 string that users would find cumbersome. ECDSA P-256 with SHA-256 delivers a fixed 64-byte signature that becomes a manageable 202-character key when encoded in Base32, while remaining fully available in the runtime. The article also covers performance measurements, the risks of ECDSA nonce generation, and the deliberate choice of the IEEE P1363 signature format to guarantee fixed-length output.
Pilcrow Publishes Free Comprehensive Guide on Web Authentication
Author Pilcrow has released a detailed, ad-free handbook covering authentication and authorization practices for web applications. The resource draws on personal experience and includes practical examples in JavaScript and Go. It examines password-based methods, email verification, multi-factor authentication, passwordless flows, and passkeys while highlighting associated risks and usability trade-offs. The book also provides in-depth guidance on session management, token security, expiration policies, and email address handling as account identifiers. Recommendations emphasize choosing methods that match application security requirements and user expectations. Additional context is given on OWASP resources and community support channels.
redb 3.4.0 Adds Replay Checkpoints, Shared Runtime Layer and Declarative Secrets Handling for .NET Ecosystem
redb 3.4.0 delivers operational improvements for the .NET integration platform that includes typed storage over Postgres, MSSQL and SQLite, the redb.Route engine modeled after Apache Camel, the Tsak runtime with dashboard and clustering, and redb.Identity for OIDC and OAuth 2.1. The release focuses on post-deployment resilience with replay checkpoints that capture message state at named points inside routes, allowing safe re-execution of downstream steps without duplicating side effects. A shared runtime layer moves framework assemblies into a separate Libs/shared directory so that individual DLLs can be replaced without rebuilding or redeploying the entire Tsak or Identity packages. Secrets are now declared with a [Sensitive] attribute on endpoint options, ensuring URIs containing passwords or keys are sanitized before they reach logs, metrics or health checks. Additional controls include role-based access to management APIs, persistent audit trails and cryptographic signing of dynamically loaded modules. All Pro features remain free on the entire 3.x line with no licensing server required.