Healthcare Grapples with Unseen AI Tools Handling Patient Data
A Paubox survey reveals a significant governance gap in healthcare, with 70% of organizations finding unapproved AI tools processing patient data, despite 90% claiming to review AI-generated code.

A recent survey by Paubox has exposed a critical blind spot in healthcare's adoption of artificial intelligence: a widespread lack of oversight over AI-generated tools that handle sensitive patient data. The findings indicate that a staggering 70% of healthcare organizations have discovered AI-built applications, scripts, or automations processing protected health information (ePHI) without the explicit knowledge or approval of their IT or security departments. This "shadow AI" phenomenon poses a significant risk to patient privacy and regulatory compliance.
Compounding this issue, 90% of healthcare leaders surveyed reported that their security or compliance teams regularly review AI-generated code before it is deployed. However, this review process appears to be failing to capture tools that are developed and used outside of official channels. The survey highlights a fundamental disconnect: code reviews are limited to what is submitted for inspection, and checks for necessary business associate agreements (BAAs) – a HIPAA requirement for vendors handling patient data – only occur if the existence of the tool is reported. This means that even rigorously reviewed code can be part of an unmanaged, unvetted AI tool.
The survey also sheds light on the concerning frequency with which real patient information is exposed to AI coding assistants during the development lifecycle. A substantial 93% of respondents admitted that patient data is accessed by these assistants at least some of the time during building, testing, or debugging phases. For 70% of them, this occurs frequently or usually, meaning sensitive data is being transmitted to third-party AI vendors before the final tool is even completed or approved.
This lack of governance is not merely theoretical. More than half of the healthcare leaders surveyed reported that AI-generated code has contributed to security vulnerabilities such as hardcoded credentials (passwords or API keys embedded directly in the code). Additionally, about half indicated that AI-generated code has led to the exposure of patient data or the implementation of insecure data storage practices. These findings underscore the tangible security risks introduced by unmonitored AI tool usage.
The concept of "shadow IT" – software adopted by employees without IT department approval – is a known concern, but the survey reveals its amplified presence with AI tools. One in four respondents identified shadow IT as a worry, with seven in ten discovering AI-built tools handling patient data outside of IT's purview. The dual threats of patient data exposure and insecure code are major concerns for these organizations.
In response to these challenges, Paubox recommends a stringent policy: enforce the use of synthetic data for all testing and development work involving AI coding assistants. This rule, they advise, should be embedded within the tools themselves, as training alone has proven insufficient to prevent the accidental use of real patient data.
Paula M. Stannard, Director at the HHS Office for Civil Rights, emphasized the critical importance of robust HIPAA risk analyses. "If a HIPAA regulated entity doesn’t know what threats and vulnerabilities exist to its electronic protected health information (ePHI), they will often learn the hard way when their systems are hacked," she stated, highlighting the legal and practical necessity of comprehensive security oversight.
Ultimately, the Paubox survey reveals a critical gap between the perceived control over AI tools and the reality on the ground in healthcare. The findings serve as a stark warning that without a proactive and comprehensive governance strategy, healthcare organizations risk significant data breaches, compliance failures, and erosion of patient trust as AI adoption continues to accelerate.