Urgent.News

What's breaking now, across thousands of outlets.

Tech

Can a Vibe-Coded Healthcare App Be HIPAA-Compliant?

Vibe coding tools can generate a working healthcare application, but that doesn't mean the application is ready to handle protected health information (PHI). Authentication, record-level authorization, audit logging, data storage, and third-party integrations all need to meet the applicable HIPAA requirements. The tools differ significantly in how they handle sensitive data and whether they offer…

Vibe coding tools can produce a functioning healthcare application, but that does not automatically ensure the app meets HIPAA compliance standards. HIPAA compliance requirements encompass more than just the AI-generated code; they also involve the organizations, vendors, systems, and processes that interact with protected health information (PHI).

Three key areas demand careful attention:

1. Business Associate Agreements (BAAs): When vendors handle PHI on behalf of HIPAA-covered entities, BAAs may be necessary. This becomes pertinent early in the AI-assisted development process. For instance, if a developer copies patient information (e.g., names and diagnoses) into an AI coding tool, that data is transmitted to another service. Before incorporating patient data, developers must verify whether the vendor permits such usage, if a BAA covers the service, and how the data will be processed and stored.

2. Server-side authorization: Even if an application includes login functionality, it could still allow authenticated users to access unauthorized records. For instance, an endpoint that fetches a patient's clinical record based on a patient ID might allow unauthorized access if it merely checks if the requester is logged in. The authorization process must occur on the backend before returning the record, validating the user's permissions, organization, site, and permitted patient records.

3. Patient-level auditability: Healthcare applications must maintain detailed audit logs to track access and modifications to electronic PHI. Under HIPAA regulations, systems containing or using electronic PHI must have mechanisms to record and review activity. This includes logging patient-record access and changes, along with user identifiers, timestamps, and the affected records. The application should also provide a method for accessing and reviewing this audit history.

When it comes to vibe coding tools, each has unique architectures and data-handling approaches. Some tools generate and host applications, while others function as coding assistants within a developer's environment. The distinction is crucial when dealing with PHI. Some tools, like Replit and Base44, do not provide BAAs for PHI on applications hosted on their platforms.

In contrast, others, like Cursor and Claude Code, offer BAA support for qualifying Enterprise customers, with specific provisions on data retention and processing.

While vibe coding tools can be part of a HIPAA-compliant healthcare application, developers must still implement additional safeguards such as encryption, access controls, and regular security reviews. Before introducing patient information into any development tool, it is essential to confirm that the vendor permits its use, that a BAA covers the relevant service, and how the data will be managed.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

DNS Change Audit Logs: 5 Custody Checks for Gaming Company Mail

A gaming company's mail migration needs DNS change auditing that preserves who changed each record in searchable logs. It also has two clocks: the moment an authorized engineer changes the MX records…

  • Gaming company migrating mail system
  • 5 custody checks for DNS changes
  • Separate evidence: application events, zone listings, cutover records

Migrating per-machine keys to floating licensing

A floating license pool looks like a server setting: "allow 25 concurrent users instead of 25 named machines." It is not.

  • Floating license pool allows 25 concurrent users without named machines.
  • Dual-mode SDK reads per-key seat.model claim to transition smoothly.
  • Server reconciles old activations into new pool atomically to maintain capacity.

When one agent should become several specialists

Keep one agent on the whole task until the work breaks into specialties that need separate context and instructions. Mikiko Chandrasekhar put a practical size on that split: small agents equipped for…

  • Split a single agent into several specialized agents when it becomes too complex.
  • Log every handoff between agents for debugging and system inspection.
  • Measure quantifiable metrics like accuracy and runtime efficiency for coding agents.

Arize Phoenix CVE-2026-53998: un fallo de cadena de formato con CVSS 10.0 filtra PHOENIX_SECRET sin iniciar sesión

Un fallo de cadena de formato en la consulta applyChatTemplate de Arize Phoenix (CVE-2026-53998, CVSS 10.0, del 16 de noviembre de 2026) permite a cualquiera que alcance una instalación por defecto…

  • Arize Phoenix vulnerability CVE-2026-53998 due to format string injection
  • Allows unauthorized access to PHOENIXSECRET without login
  • CVSS 10.0 rating classifies as critical threat

How to get a software engineering internship

Software engineering internships are some of the most competitive roles students apply for. Big tech companies get thousands of applications for each opening, and most of them open early.

  • Apply to major tech firms early (July-August), then pursue startups (Feb-April)
  • Develop 1-2 substantial projects, host on GitHub with clear README
  • Practice coding problems (50-100) and verbal explanations, apply to diverse employers

More from Wednesday 18 November →