HIPAA vs PCI DSS: A Compliance Guide for Software Teams

HIPAA vs PCI DSS for teams building health and payment apps: what each rule covers, PCI DSS v4.0.1 dates, a control map and a launch checklist.

Ketan PatelCodesClue Updated 10 min read

Your app books a therapy session, stores the clinician’s notes and then takes a card payment for the copay. That one flow now sits under two separate sets of rules. This guide explains HIPAA vs PCI DSS for the people who design and build the software. You will see what each rule covers, where they overlap and how to keep card data out of scope.

Key Takeaways

  • HIPAA is a federal law in the United States about health information. PCI DSS is an industry standard about payment card data.
  • A health product that takes card payments usually answers to both, and each one has its own proof of compliance.
  • The cheapest PCI DSS control is not touching card numbers at all. Let a payment processor’s hosted fields or page collect them.
  • Your cloud host is a HIPAA business associate even when it only stores encrypted data, so you need a signed agreement.
  • PCI DSS v4.0.1 is the only active version, and its 51 future-dated requirements have applied since 31 March 2025.

HIPAA vs PCI DSS: the short answer

The main difference in HIPAA vs PCI DSS is the data each one guards. HIPAA protects health information held by health plans, clearinghouses, many providers and their business associates. The US government enforces it. PCI DSS protects payment card data for anyone who stores, processes or transmits it. The card brands enforce it through banks and contracts.

So HIPAA follows the patient record wherever it goes. PCI DSS follows the card number. A clinic app, a billing tool or a telehealth platform can hold both, and then both apply at once.

Question HIPAA PCI DSS
What it protects Protected health information (PHI), including the electronic kind (ePHI) Cardholder data and sensitive authentication data, such as card verification codes
Who must follow it Covered entities (health plans, clearinghouses, providers who bill electronically) and their business associates Any merchant or service provider that stores, processes or transmits card data
Who writes the rules US Department of Health and Human Services (HHS) PCI Security Standards Council (PCI SSC), set up by five card brands
Who enforces it HHS Office for Civil Rights (OCR) Card brands and acquiring banks, through merchant contracts
How detailed it is Flexible. You pick controls that fit your size and your risk analysis. Prescriptive. 12 core requirements, each with detailed sub-requirements and test steps.
Proof of compliance No official certificate. You keep your own risk analysis, policies and records. A self-assessment questionnaire or an assessor’s report, as your bank or the card brands ask
Breach reporting Tell affected people within 60 days of discovery. Report to HHS, and to the media above 500 residents of a state. Follow the card brand and acquirer rules in your merchant agreement

What HIPAA expects from a software product

The HIPAA Security Rule groups its safeguards into three types. Administrative ones cover people and process, physical ones cover sites and devices, and technical ones cover systems. Together they keep ePHI confidential, intact and available. HHS sets out the rule on its Security Rule page (opens in a new tab). It names outcomes and leaves most of the tools to you.

For a product team, those safeguards turn into concrete work:

  • Risk analysis. List every place ePHI lives, who can reach it and what could go wrong. Update it when the product changes.
  • Access control. Give each user a unique login and only the records their role needs. A front desk user rarely needs session notes.
  • Audit logs. Record who viewed, changed or exported a record, and review those logs.
  • Encryption. Encrypt ePHI in transit and at rest. Under the HHS Breach Notification Rule (opens in a new tab), data you encrypt properly counts as secured PHI, and losing it does not trigger notices.
  • Business associate agreements. Sign one with every vendor that touches ePHI for you.

That last point catches many teams. HHS states in its cloud computing guidance (opens in a new tab) that a cloud provider storing ePHI is a business associate. That holds even when the provider only keeps encrypted data and has no key.

The stakes are real. In its Change Healthcare FAQ (opens in a new tab), HHS reports that Change Healthcare told it about 192.7 million people had their data affected. Change Healthcare is a business associate, not a hospital. Vendors carry real HIPAA duties.

Pro tip: HHS proposed a stricter Security Rule on 27 December 2024. Its proposed rule page (opens in a new tab) says the current rule stays in effect during the rulemaking. Build to the current rule, and treat multi-factor login and full encryption as defaults anyway.

What PCI DSS expects from a software product

PCI DSS applies to any entity that stores, processes or transmits cardholder data, as the PCI SSC overview (opens in a new tab) puts it. The card brands enforce it, so your bank or payment processor tells you which form of proof to file.

The version matters. The PCI SSC published PCI DSS v4.0.1 in June 2024 (opens in a new tab) and retired v4.0 on 31 December 2024. The council’s note on future-dated requirements (opens in a new tab) says 51 of the 64 new requirements took effect on 31 March 2025.

Three parts of the standard land directly on developers:

  1. Never keep sensitive authentication data. The PCI SSC answers plainly (opens in a new tab) that card verification codes must not stay in storage after authorization. That includes recurring billing.
  2. Control scripts on payment pages. Requirements 6.4.3 and 11.6.1 target e-skimming. You must authorize each script on the payment page, check its integrity and watch for tampering, as the council’s e-commerce guidance (opens in a new tab) explains.
  3. Prove your scope every year. Requirement 12.5.2 asks for a yearly check of which systems sit in scope. Your architecture diagram becomes audit evidence.

Pro tip: Let your processor collect the card number in its own hosted page or embedded fields. Your servers then see a token, never the card number. Most card data controls then sit with the processor, not with you.

Where HIPAA and PCI DSS overlap, and where they split

Most technical controls serve both rules. The difference lies in how much detail each one demands and what proof it accepts. Use this map to build a control once and file the evidence twice.

Control HIPAA PCI DSS Build once?
Risk analysis An accurate and thorough risk assessment, revisited over time Targeted risk analyses for named requirements Yes, one register with both data types
Unique user IDs and least access Policies that limit who can open ePHI A unique ID per person, access on a need-to-know basis Yes
Login checks Verify each person is who they claim to be Multi-factor login (opens in a new tab) for all access into card data systems Yes, use multi-factor login everywhere
Encryption in transit Transmission security safeguard. Encryption is the usual way to meet it. Encrypt card data across open, public networks Yes, TLS on every connection
Encryption at rest Encrypted PHI counts as secured under the breach rule Protect any stored card data Yes, with separate keys per data type
Audit logging Record and examine activity in systems with ePHI Track and monitor all access to card data Yes, one log platform
Vendor contracts Business associate agreement Written agreement and the provider’s compliance proof No, two different documents
Security testing Regular reviews of your risks and safeguards Regular tests of security systems and processes Yes, one test plan for both
Breach response 60-day notice clock, HHS reporting Card brand and bank rules One plan, two notice paths

One honest warning: passing one review never proves the other. A HIPAA risk analysis will not satisfy a PCI assessor, and a PCI report says nothing about PHI.

Does your product need HIPAA, PCI DSS or both?

Start from the data, not the industry label. Ask two questions. Do you handle health information for a covered entity? Do card numbers pass through anything you run?

Your product HIPAA PCI DSS
Patient portal for a clinic that also collects copays Yes Both apply. Hosted payment fields keep your scope small.
Clinical notes tool sold to therapists, no payments Yes, as a business associate No
Medical billing service that takes card payments by phone Yes Applies, and call recordings need care
Payment gateway with no health data No Yes, as a service provider
Online store selling supplements Usually no Yes

Not sure where your product lands? Our team can map your data flows and tell you which rules apply before you write the first line of code. Talk to us about your product.

How to build for both rules at the same time

This is the order we use on regulated builds. It keeps scope small and makes the audit work lighter later.

  1. Draw the data flow. Trace patient data and card data from the first form field to backups, logs and analytics tools. Every box on that drawing is in scope until you prove otherwise.
  2. Keep card numbers out. Use your processor’s hosted page or fields and store only tokens. Then confirm the processor’s own PCI DSS status in writing.
  3. Split the two data types. Put PHI and payment records in separate databases with separate keys and separate administrator roles.
  4. Sign agreements before data moves. Get a business associate agreement from your cloud host, email provider, AI model provider and support desk tool.
  5. Encrypt and manage keys. Our guide to encryption and decryption covers key rotation and the gaps teams skip.
  6. Harden logins. Add multi-factor login for staff and administrators. Our passkeys implementation guide shows a phishing-resistant way to do it.
  7. Test, log and rehearse. Run scans and pen tests, monitor payment page scripts and run a timed drill of your breach plan against the 60-day clock.

Pro tip: Scrub logs before they leave the app. A stack trace with a patient name or a full card number turns your log tool into regulated storage overnight.

Running a wider SaaS platform? Our SaaS security best practices cover vendor reviews, single sign-on and offboarding, so we will not repeat them here.

A real example: Therapix.AI clinical notes

Therapix.AI turns therapy session input into structured clinical notes and SOAP reports. We built it on React, Node.js, PostgreSQL and AWS, with web, iOS and Android apps. Session content is health data, so access control and secure storage shaped the design.

One choice mattered more than any tool. Clinicians review, edit and approve each AI-written note before it goes into final storage. That keeps a human in charge of the record and gives a clear trail of who approved what. The case study records a 62% drop in documentation time.

On the payment side, our EmberPay build shows the other half. It uses role-based access and keeps an audit-ready record of every transaction. It has five core modules: payments, transactions, accounts, alerts and reports.

Checklist before launch for regulated health and payment apps

Run through this list before your first real patient or card goes into production:

  • A current data flow diagram that shows every system touching PHI or card data
  • A written risk analysis covering both data types, with owners and dates
  • Signed business associate agreements with every vendor that sees ePHI
  • Written proof of your payment processor’s PCI DSS status
  • No card verification codes in any database, log, queue or backup
  • Tokens, not card numbers, in your own tables
  • Multi-factor login for every administrator and staff account
  • Audit logs that record views, edits and exports, with a named reviewer
  • An inventory of scripts on the payment page, with integrity checks
  • Test data that contains no real patient or card details
  • A breach plan that names who calls the bank and who files with HHS

Common mistakes to avoid

  • Trusting a “HIPAA certified” badge. HHS says in its certification FAQ (opens in a new tab) that it does not endorse or recognize private certifications for the Security Rule. Ask vendors for a signed agreement and real controls instead.
  • Skipping the agreement because you encrypt the data. HHS still treats the cloud host as a business associate.
  • Storing the CVV “just for renewals”. PCI DSS forbids it after authorization, even for card-on-file billing.
  • Sending PHI to analytics or AI tools. Page titles, URLs and prompts can carry patient details. Each of those vendors then needs an agreement, or the data must stay out.
  • Copying production data into test. Developers then hold real records on laptops with weaker controls.
  • Forgetting third-party scripts. One chat widget or tag on the checkout page can bring the page into scope for script monitoring.

Pro tip: Before each release, search your code for logging calls near payment and patient features. Debug lines written in a hurry are a common way records slip into logs.

Where AI helps, and where this guide stops

AI tools can read logs at a scale people cannot. They flag odd login patterns, unusual exports and settings drift faster than a weekly review. They do not replace the risk analysis, the agreements or the assessor.

Be honest about limits too. This guide covers US rules for software teams. It is not legal advice, and it does not cover state privacy laws or rules outside the US, such as GDPR. At higher card volumes, the card brands may require a qualified security assessor.

Building a new health product? Have healthcare counsel confirm your HIPAA role early.

HIPAA vs PCI DSS: what to do next

The HIPAA vs PCI DSS question has a practical answer. Shrink card scope with tokens, protect health data with access control and encryption, and keep separate proof for each rule. Deciding this in the first sprint costs less than fixing it after launch.

For deeper planning, see our healthcare software development and fintech software development services.

Our data security services and software security and governance teams handle reviews and control design. Our banking software development cost guide breaks down what compliance adds to a payments budget.

If you are naming owners and setting access reviews for patient or payment data, our 90-day data governance plan shows where to start.

CodesClue is an AI-first engineering company with its core team in Ahmedabad and offices in India, the USA and Germany. We take regulated products from proof of concept to MVP to production in short Agile sprints.

Need extra hands? You can hire DevSecOps engineers, and development starts within 48 hours once we agree on requirements and you approve the developer.

Have a health or payments product on the table? Send us your data flow or your idea, and we will show you where HIPAA and PCI DSS touch it. You get a clear scope before you commit to a build.

FAQs on HIPAA & PCI DSS Compliance

What is the HIPAA Security Rule, and why is it important?

The HIPAA security rule sets standards to protect electronic protected health information (ePHI) through administrative, physical, and technical safeguards. It is crucial for preventing data breaches and ensuring patient privacy.

What is PCI DSS, and who needs to comply with it?

PCI DSS (Payment Card Industry Data Security Standard) applies to any organization that processes, stores, or transmits cardholder data. It helps prevent payment fraud and ensures secure financial transactions.

Can a business be required to comply with both HIPAA and PCI DSS?

Yes, organizations like healthcare apps with payment features must follow both HIPAA compliance and payment card industry data security standards to protect patient and payment data simultaneously.

What are the common causes of compliance failures?

Most failures occur due to misconfigured systems, weak passwords, a lack of encryption, and the absence of continuous monitoring. Human error remains a leading factor in security breaches.

How does AI help in achieving compliance?

AI enhances compliance by detecting threats in real-time, automating audits, predicting vulnerabilities, and improving response times. It enables organizations to move from reactive to proactive security.

What are the best practices for maintaining HIPAA and PCI DSS compliance?

Regular audits, strong encryption, role-based access control, continuous monitoring, employee training, and proper documentation are key to maintaining effective and ongoing compliance.

  • Security and compliance

Written by Ketan Patel for CodesClue, a software development company with teams in India, the USA and Germany that designs, builds and supports web, mobile and AI products. About CodesClue

Want this done for your product?

Tell us what you are planning. An engineer replies within one business day with honest next steps, and we sign an NDA before any engagement.

  1. Answer two quick questions and tell us about the project.
  2. We read it and reply with questions or a plan.
  3. You get a written estimate with milestones before anything is signed.
See what we have built

    Build together with CodesClue