hello@sterling-grc.com +1 201 263 4443 New York ISO & GRC consulting in 60+ countries
SterlingInternational Consulting Talk to a consultantTalk to us
← All videos

Integrated programme

PCI DSS and HIPAA together: patient payments and health data, protected as one: video

A film on protecting patient payments and health data together, for healthcare providers, billing companies and patient-payment services.

  • Integrated programme
  • 3 min 14 s

Key takeaways

  • PCI DSS is validated annually; HIPAA is a law with no certificate.
  • One set of access, logging, encryption, vulnerability and incident controls meets both.
  • Segment card data and health data so each requirement applies only where it must.
  • HIPAA documentation is prepared alongside the PCI DSS evidence.
  • ISO/IEC 27001 or SOC 2 can be added later on the same controls.

Card data and health data, side by side

Healthcare providers, billing companies and patient-payment services handle payment card data and protected health information side by side. PCI DSS governs the cardholder data environment and is validated every year, by a Qualified Security Assessor or through the self-assessment questionnaire the acquirer accepts, depending on the level the card brands and the acquirer set. HIPAA's Security Rule sets the safeguards for electronic protected health information; HIPAA is a US law, and no government body certifies compliance with it.

Neither framework is a certification, which makes documented, demonstrable controls all the more important. This short film walks through how one set of controls serves both.

Healthcare providers, billing companies and patient-payment services are the organisations that most often handle both data types side by side.

Neither outcome is a certificate: PCI DSS compliance is validated at least annually by a QSA or a self-assessment questionnaire, and HHS does not recognise any private certification of HIPAA compliance. The business associate agreement sets out how protected health information is handled.

One set of controls, each data type scoped deliberately

Access, logging, encryption, vulnerability and incident controls are built once to meet both frameworks. Card data and health data are segmented so each requirement applies only where it must, which keeps the scope, and the effort, as small as possible. The HIPAA risk analysis, policies, training and business associate agreements are prepared alongside the PCI DSS evidence, ready for clients and assessors.

The PCI DSS assessment and the HIPAA risk reviews can then be planned together. Because the controls are written once, the organisation also has room to grow: ISO/IEC 27001 or SOC 2 can be added later on the same controls when clients ask for a certificate or an attestation report, without rebuilding what is already in place.

Sterling runs the programme with one consultant in Effivity in one all-inclusive proposal. The QSA or the acquirer's process validates PCI DSS, and HIPAA compliance is judged by the regulator and customers' auditors; Sterling prepares the controls and the evidence.

PCI DSS at a glance

Purpose
Protection of payment card account data wherever it is stored, processed or transmitted, through twelve requirements validated every year
Relevant to
Merchants, service providers, BPOs, payment facilitators, hosting and software providers: anyone who handles cardholder data or can affect its security
Version
PCI DSS v4.0.1 (June 2024); v4.0 was retired on 31 December 2024 and the formerly future-dated requirements have been mandatory since 31 March 2025
Validation
Assessed by a PCI SSC-qualified QSA (Report on Compliance and Attestation of Compliance), or by self-assessment questionnaire where your acquirer and the card brands allow it; quarterly ASV scans where they apply
Sterling's role
Scoping, gap analysis, remediation with your team, Effivity, training, internal assessment and QSA readiness, then Sustain™ through every annual cycle
Cost and timing
Total investment for PCI DSS compliance depends on the current maturity of your processes, the scope, locations and number of employees. The process typically takes 3 to 9 months

PCI DSS: the complete guide →

PCI DSS: questions people ask

Is PCI DSS a certification?

No. There is no PCI DSS certificate and no certification body. Compliance is validated at least annually, by a Qualified Security Assessor who produces a Report on Compliance and signs an Attestation of Compliance, or by a self-assessment questionnaire with its own AOC where your acquirer and the card brands allow it.

Do we need a QSA, or can we self-assess?

That depends on your merchant or service-provider level, which the card brands define by annual transaction volume, and on what your acquirer or customers require. The largest merchants and most service providers are assessed by a QSA; many smaller merchants and some service providers may self-assess. Some brands also accept a Report on Compliance completed by a trained Internal Security Assessor on your staff, where the acquirer permits it.

Which self-assessment questionnaire applies to us?

The PCI Security Standards Council publishes SAQs for different payment environments: SAQ A and SAQ A-EP for e-commerce and mail or telephone order merchants that outsource card data functions to differing degrees; SAQ B and SAQ B-IP for imprint and standalone terminal environments; SAQ C and SAQ C-VT for payment application and virtual terminal environments; SAQ P2PE for validated point-to-point encryption; SAQ SPoC for approved software-based PIN entry; SAQ D for merchants who fit none of the others; and SAQ D for service providers, the only SAQ open to them. Eligibility criteria are strict; your acquirer has the final word.

Are the PCI DSS v4.0 future-dated requirements now mandatory?

Yes. They were best practice until 31 March 2025 and have been required in every assessment since, under PCI DSS v4.0.1, the only active version since v4.0 was retired on 31 December 2024.

How can we reduce our PCI DSS scope?

By keeping card data out of your systems: hosted payment pages or redirects, tokenisation, validated point-to-point encryption, agent-assisted payment tools in the contact centre, and outsourcing to providers with a current AOC; what remains is isolated with tested segmentation. Reducing scope does not remove PCI DSS: an e-commerce merchant eligible for SAQ A still has requirements to meet, including quarterly ASV scans of the systems hosting its payment page or redirect.

More PCI DSS questions and answers →

The complete guide

Everything on PCI DSS

Start with the PCI DSS page · HIPAA, or go straight to the guide you need.

Talk to a consultant

Plan your PCI DSS compliance with confidence.

Tell us your goals, locations and target date. We’ll help you define the scope, timeline and next steps.

hello@sterling-grc.com

+1 201 263 4443 (global headquarters) · your nearest office and its number are at the top of this page

What would you like to achieve?

Choose a starting point. The enquiry form takes about a minute.

Your goal
Book my free discovery call

Continue to the enquiry form to share your details. Please do not include passwords, sensitive personal information or confidential files. A Sterling consultant replies within one working day. Privacy notice