Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
AI is not automatically HIPAA compliant. A healthcare organization can use an AI system with protected health information (PHI) only after evaluating the specific workflow, completing and documenting a risk analysis, applying reasonable and appropriate safeguards, training users, and putting a HIPAA-compliant business associate agreement (BAA) in place when a vendor handles PHI for the organization. The current HIPAA Security Rule remains enforceable while the Department of Health and Human Services (HHS) considers proposed cybersecurity changes.
Whether an AI deployment is permissible depends on who is using it, what data enters the system, what the vendor does with that data, and how the organization controls access, retention, logging, incidents, and model behavior. A product page or “HIPAA-ready” label cannot answer those questions by itself.
What does HIPAA require when an organization uses AI?
HIPAA obligations follow the covered entity or business associate, the data, and the activity—not the marketing label attached to an AI product. The Security Rule establishes national standards for protecting electronic protected health information (ePHI) created, received, used, or maintained by a covered entity or its business associate. See the HHS Security Rule overview.
For an AI workflow, that means documenting the parties and data flows, assessing threats and vulnerabilities, applying administrative, physical, and technical safeguards, and maintaining evidence that controls are reviewed and updated. A workflow that uses only non-sensitive information may fall outside HIPAA, while the same tool connected to a clinical record system can create extensive HIPAA duties.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Who is subject to the rules?
- Covered entities: health plans, health care clearinghouses, and health care providers that conduct covered electronic transactions.
- Business associates: organizations that perform services involving PHI for a covered entity, such as hosting, analytics, billing, or technology services.
- Business-associate subcontractors: downstream vendors that receive PHI from a business associate to provide those services.
HHS explains the covered-entity and business-associate relationships in its Covered Entities and Business Associates guidance. Your privacy or security officer should classify every participant in the proposed AI workflow before approval.
How can we tell whether a particular AI use case involves PHI?
Start with the information that enters, leaves, or is retained by the system. PHI can be present in an obvious prompt, but it can also appear in uploaded files, generated outputs, application logs, support tickets, backups, telemetry, or a vendor’s review queue.
Map the complete data flow
- List every input: prompts, documents, images, audio, structured fields, API payloads, and data pulled from an electronic health record.
- List every output: answers shown to staff, text returned to an application, generated reports, alerts, and files exported to another system.
- Identify persistence: conversation history, prompt and response logs, caches, backups, model-improvement datasets, and disaster-recovery copies.
- Identify people and systems with access: users, administrators, vendor support staff, subprocessors, application service accounts, and integrations.
- Record locations and transfers: cloud regions, data centers, cross-border transfers, and movement between the organization, vendor, and subprocessors.
Document the map in a system inventory or data-flow diagram. If you cannot state where a prompt, output, or log is stored and who can retrieve it, the workflow is not ready for PHI.
Separate PHI handling from general experimentation
Teams often prototype with public or synthetic data and later connect the same tool to real records. Treat that connection as a new use case requiring its own review. A setting that is acceptable for de-identified demonstrations does not establish that the production configuration protects ePHI.
What risk analysis is required before deployment?
Risk analysis is the foundation of Security Rule compliance. HHS describes it as “the first step in an organization’s Security Rule compliance efforts” and calls for an accurate and thorough assessment of threats and vulnerabilities to ePHI. Use the HHS risk-analysis guidance as the starting point.
Build a use-case-specific assessment
- Define the purpose and boundary: name the clinical, administrative, or research task, the users, the systems involved, and the data categories.
- Inventory assets: applications, endpoints, identities, APIs, storage, model endpoints, logs, backups, and administrative consoles.
- Identify threats and vulnerabilities: unauthorized access, excessive privileges, prompt injection, malicious files, insecure integrations, accidental disclosure, weak deletion, vendor compromise, and unsafe or misleading outputs.
- Estimate likelihood and impact: consider how a failure could expose ePHI, disrupt care, produce an incorrect decision, or impair availability.
- Select mitigations: access restrictions, authentication, encryption, logging, human review, output filtering, retention limits, contractual restrictions, and incident procedures.
- Record residual risk and approval: state what remains, who accepted it, and the conditions for use.
- Set review triggers: reassess after a model change, new integration, new subprocessor, material security incident, change in data type, or change in the intended purpose.
The assessment should be specific enough that an auditor can connect each identified risk to an owner, a control, and evidence that the control operates. A generic vendor questionnaire or a one-time checklist is not a substitute for evaluating your own workflow.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
When do we need a business associate agreement for an AI vendor?
If a vendor creates, receives, maintains, or transmits PHI to perform a service for a covered entity or business associate, the vendor may be a business associate and a written BAA is generally required. The agreement must define permitted uses and disclosures and require appropriate safeguards; the HHS Security Rule summary explains the contractual framework.
What the BAA should address
- The exact services and categories of PHI the AI system may handle.
- Permitted uses and disclosures, including whether prompts and outputs may be used for analytics, service improvement, or model training.
- Required safeguards for confidentiality, integrity, and availability.
- How the vendor reports suspected breaches and security incidents, including timing and required information.
- Whether subcontractors may access PHI, how they are approved, and how the vendor flows down obligations.
- Retention, return, and destruction of PHI, including backups and residual copies.
- Available audit evidence, cooperation with investigations, and assistance with individual rights or regulatory requests where applicable.
A BAA is necessary when the relationship meets the business-associate definition, but it does not make an unsafe product compliant. Contract terms must match the technical configuration and the actual way staff use the service.
What safeguards should an AI deployment implement?
The Security Rule calls for reasonable and appropriate administrative, physical, and technical safeguards. The right controls depend on the organization’s size, capabilities, environment, and risks, but the following baseline is appropriate for most PHI-enabled AI workflows.
Identity and access
- Use unique user accounts rather than shared logins.
- Apply least privilege to prompts, records, administration, exports, and support functions.
- Use strong authentication appropriate to the risk, and protect API keys and service accounts.
- Review access regularly and deprovision staff promptly when their role changes or employment ends.
- Separate development, testing, and production environments.
Encryption and infrastructure
- Confirm encryption in transit and at rest, including logs, backups, and exported files.
- Understand key-management responsibilities and who can decrypt stored data.
- Restrict administrative interfaces and monitor unusual access or data movement.
- Verify backup, availability, and recovery arrangements for systems that support care or operations.
Auditability
Retain logs needed to investigate access and misuse: user identity, time, source, prompts, outputs, administrative actions, exports, model or policy changes, and relevant security events. Define retention and access rules for those logs because they may themselves contain sensitive information.
Human review and model behavior
Test for leakage, memorization, prompt injection, unsafe or fabricated outputs, and failures caused by model or system changes. Define when a qualified person must review an output before it affects a patient, record, communication, or operational decision. Keep test methods, results, exceptions, and remediation decisions with the risk-analysis record.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallHow should we evaluate and compare AI vendors?
Ask for current contractual language and security documentation, then have the privacy officer, security officer, and counsel approve the specific use case. Compare vendors on the same evidence rather than relying on badges, sales statements, or a generic compliance page.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
| Evaluation area | Questions to document | Evidence to request |
|---|---|---|
| PHI collection and retention | What data is collected? How long are prompts, outputs, logs, and backups retained? | Data-flow diagram, retention schedule, product configuration |
| BAA scope | Does the BAA cover the product, support channels, APIs, and every relevant subprocessor? | Current BAA and service terms |
| Permitted uses | Can the vendor use PHI for training, analytics, human review, or advertising? | Contract clauses and privacy terms |
| Access controls | Are role-based access, unique users, strong authentication, and administrative separation available? | Configuration guide and access-control documentation |
| Logging | Which user, prompt, output, export, and administrative events are logged, and can the customer export them? | Sample audit-log fields and retention options |
| Deletion and export | Can the organization retrieve and delete data, including backups and derived datasets? | Deletion procedure, export format, and backup terms |
| Subprocessors and geography | Who can access the data and where is it processed or stored? | Subprocessor list, locations, and change-notification process |
| Incident notification | How and when will the vendor notify the organization of a suspected breach or compromise? | Incident-response and notification commitments |
| Change management | How are model updates, new features, and policy changes announced and tested? | Release process, notice terms, and customer controls |
| Risk-analysis support | Can the vendor provide architecture, control descriptions, testing information, and answers needed for your assessment? | Security documentation and assessment responses |
Do not accept “not applicable” without an explanation. If a required control is unavailable, record the gap, compensating control, residual risk, and approving authority—or select a different workflow.
What should a healthcare organization’s AI policy include?
An AI policy should translate the risk analysis into rules that staff can follow at the moment they use a tool. It should cover both approved systems and unsanctioned experimentation.
- Purpose and scope: covered entities, business associates, workforce members, contractors, devices, applications, and data types.
- Approved tools and use cases: named services, approved configurations, prohibited features, and the owner for each workflow.
- Data-handling rules: what may be entered, what must be removed or minimized, and how uploads, exports, screenshots, and copied outputs are handled.
- Access and authentication: account issuance, least privilege, service accounts, and deprovisioning.
- Output verification: required human review, clinical escalation, source checking, and prohibition on treating generated text as an independent medical judgment.
- Logging and monitoring: events retained, review responsibilities, alert thresholds, and protection of log data.
- Vendor management: BAA requirements, subprocessor review, retention and deletion terms, and reassessment triggers.
- Training: approved prompts, prohibited data, phishing and prompt-injection awareness, verification, and incident reporting.
- Incident response: who detects, contains, investigates, documents, and reports suspected breaches or unsafe outputs.
- Enforcement and exceptions: how violations are handled and who can authorize a documented exception.
Can employees put PHI into ChatGPT or another public AI platform?
Not unless the organization has specifically approved that service and configuration for the intended PHI, completed its risk analysis, and satisfied contractual and safeguard requirements. A free or consumer account generally does not establish the controls, retention restrictions, auditability, or BAA coverage required for a PHI workflow.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Block unapproved uploads and browser extensions where appropriate, publish an approved-tool list, and provide a safe alternative for legitimate work. Training should show realistic examples: a pasted patient note, an image containing identifiers, a copied support ticket, or a prompt that causes an AI system to reveal information from its context.
How should we manage AI-specific security and safety risks?
Traditional access and infrastructure controls do not address every model risk. Add tests and operating procedures for the ways generative systems can expose information or produce harmful results.
Prompt injection and malicious content
Test whether instructions embedded in an uploaded document or web page can override system rules, cause unauthorized retrieval, or induce an unsafe action. Limit the model’s tools and permissions, isolate untrusted content, and require human confirmation before consequential actions.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Leakage and memorization
Check whether prompts, outputs, fine-tuning data, logs, or support processes could expose one patient’s information to another user. Use tenant isolation, access controls, minimization, and retention limits, and document the tests and their results.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsIncorrect or unsafe output
Define what the system may draft or summarize and what requires qualified review. Test representative cases, document known failure modes, and provide an escalation path when an output is incomplete, biased, or inconsistent with the source record.
Model and integration changes
Require change review when the vendor changes a model, system prompt, connector, subprocessor, or retention behavior. Re-run relevant tests and update training, documentation, and the risk assessment before expanding use.
What happens if the AI vendor has a security incident?
Your incident-response plan should identify the vendor contact, internal owner, decision authority, evidence requirements, containment steps, and notification workflow before an incident occurs. A suspected disclosure may require disabling an integration, preserving logs, rotating credentials, restricting accounts, and determining which records and individuals were affected.
- Detect and report: staff and monitoring systems send suspected incidents to the designated security or privacy team.
- Contain: suspend exposed credentials, integrations, or data paths while preserving evidence.
- Investigate: correlate identity, prompt, output, access, export, and vendor records.
- Assess: determine whether PHI was accessed, acquired, used, or disclosed and whether the event meets applicable breach criteria.
- Notify and remediate: follow the BAA, organizational policy, and applicable HIPAA notification obligations; correct the control gap and record lessons learned.
Contracts should give the organization enough information and cooperation to perform this investigation. If a vendor cannot explain what happened or cannot provide relevant logs, that limitation belongs in the risk decision before deployment.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →What is the status of the HIPAA Security Rule in 2026?
The current Security Rule is the enforceable baseline. HHS has proposed stronger, more specific cybersecurity requirements, including more detailed written, reviewed, tested, and updated policies and procedures. However, the proposal is not automatically law: HHS states that “while the Department is undertaking this rulemaking, the current Security Rule remains in effect.” Check the HHS Security Rule NPRM page for its current status before treating a proposed safeguard as mandatory.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Organizations should still design durable controls—documented risk analysis, tested safeguards, reliable logging, incident readiness, and regular review—rather than waiting for a final rule. When requirements change, map the final text to the existing control inventory and update policies, contracts, training, and technical configurations.
What is the practical approval workflow for an AI project?
Use a gated process so a promising pilot cannot quietly become an unreviewed production system.
- Submit a use-case record: purpose, users, systems, data types, expected outputs, and business owner.
- Classify the data and roles: identify PHI/ePHI, covered entities, business associates, subcontractors, and any parties outside HIPAA.
- Complete the data-flow map and risk analysis: include prompts, outputs, logs, storage, backups, subprocessors, transfers, model behavior, and residual risk.
- Review vendor terms: obtain the BAA when required and resolve retention, training, deletion, incident, subprocessor, and audit questions.
- Configure safeguards: identity, least privilege, authentication, encryption, logging, network restrictions, retention, and human review.
- Test before production: use representative synthetic or approved data to test leakage, injection, unsafe outputs, access boundaries, and failure recovery.
- Train and launch narrowly: give users approved prompts, prohibited-use examples, verification duties, and an escalation channel.
- Monitor and reassess: review logs and incidents, track model and vendor changes, and repeat the assessment when the workflow changes.
Approval should be recorded by the people accountable for privacy, security, legal review, and the operational outcome. Keep the decision, evidence, exceptions, and review date together so the organization can demonstrate why the deployment was considered reasonable and appropriate.
Free tools Windows power users keep installed
One-click scans. No signup required.
Why is this control work urgent?
HHS reported that large-breach reports increased 102% from 2018 to 2023, while the number of individuals affected increased 1002%; more than 167 million individuals were affected by large breaches in 2023. These figures describe breach trends, not the percentage of AI deployments that are HIPAA compliant. They do show why an AI workflow should be treated as another path into sensitive systems rather than as a harmless productivity add-on. See HHS’s Regulatory Initiatives page for the cited figures.
Frequently Asked Questions
Is signing a BAA enough to make an AI tool HIPAA compliant?
No. A BAA addresses the contractual relationship, but the organization still has to configure access, retention, logging, workforce procedures, and other safeguards for its specific workflow. The contract also cannot eliminate risks created by an unsafe integration or unverified model output.
How often should an AI risk assessment be reviewed?
There is no single calendar interval that fits every deployment. Set a documented cadence and trigger an earlier review after a model or connector change, a new subprocessor, a security incident, a new data type, or a change in the system’s purpose.
What evidence should we keep to demonstrate responsible AI use?
Retain the approved use-case record, data-flow map, risk analysis, vendor and BAA documents, configuration decisions, test results, training records, access reviews, relevant logs, incidents, and reassessment approvals. Organize the evidence so each important risk can be tied to an owner and a mitigation.
Can a vendor use PHI to improve its model if the BAA allows it?
Only if that use is permitted by the applicable HIPAA relationship, contract, privacy commitments, and your approved risk decision. Ask exactly what data is used, whether it is isolated from other customers, how long derived data remains, and how you can stop or delete that use.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
