Talk to a specialist
Home / Resources / PCI DSS guides / United States

PCI DSS · US implementation decisions

PCI DSS boundaries for US healthcare payment workflows

Map healthcare payment channels, telephone handling and provider responsibilities. Keep PCI DSS validation and HIPAA decisions distinct while coordinating evidence.

In this guide
Start with two information questionsMap channels and exception pathsExamine telephone handling as a complete workflowBuild a responsibility matrix around actual servicesExample: a US clinic group introduces online balancesExample: a hospital billing office changes call recordingTurn findings into separate, coordinated work packagesConfirm the validation request with the accepting organisationQuestions about healthcare payment boundariesReference basisScope the payment journey before commissioning remediation

A healthcare payment journey can begin at a reception desk, continue through a patient portal and finish with a telephone query about a statement. Clinical and payment information may travel through different systems, yet staff often use the same workstations and support tools to resolve the enquiry. That combination deserves a clear scope map.

For a US healthcare organisation, the practical aim is to identify payment channels, information fields and responsibilities before selecting remediation or validation work. Keep PCI DSS and HIPAA decisions separate, while using a coordinated view of shared workflows. This guide develops that view without assuming that a hosted payment page or a healthcare privacy programme settles the whole payment-security question.

Start with two information questions

For the payment workstream, identify where payment account data is stored, processed or transmitted and which systems or services affect its security. For the healthcare workstream, identify relevant PHI and the actual organisational relationships. Do not label every field on a payment screen as PHI, or every health-related record as card data, without examining the facts.

Write separate conclusions and link the common evidence. A workstation access review may support both workstreams; the legal and validation decisions remain distinct. A HIPAA agreement is not PCI validation, and a payment-provider assurance document does not determine every healthcare information obligation.

HHS guidance distinguishes ordinary financial transaction services from other functions that can create business-associate responsibilities. Apply that distinction to the service actually performed, rather than treating every payment-related vendor as either automatically included or automatically excluded. Reference basis: HHS Business Associates guidance.

The PCI DSS scope guide provides the general boundary method. Here, apply it to the way patients, staff, payment providers and billing teams interact.

Map channels and exception paths

Create one row for each payment channel: in-person terminal, portal, telephone, payment link or another actual route. Identify the entity and merchant arrangement, collection point, processing provider, staff interaction, connected systems and evidence owner. Avoid using the name of a single platform as a substitute for this map.

Follow exceptions as carefully as normal payments. Ask what happens when a transaction fails, a patient requests a refund, a terminal is unavailable or a staff member needs to reconcile an unexplained amount. Workarounds may introduce records and access paths absent from the standard process.

Include statements and support tickets. Determine what fields appear in messages, attachments, printed records and exports. Record whether information is generated by the healthcare system, payment provider or staff. Identify who can correct a misleading field description before making a scope decision. The aim is to understand actual handling and remove unnecessary exposure, not to collect sensitive examples in an unrestricted project folder.

Use sanitised walkthroughs and system descriptions wherever possible. If sensitive evidence is necessary, agree a controlled collection method and access rules. A scoping workshop should not become another repository of patient and card information.

If portal, telephone and billing workflows cross several teams, talk through the payment-scope and responsibility map before commissioning separate technical fixes.

Examine telephone handling as a complete workflow

PCI SSC’s VoIP guidance explains that payment account data carried through an organisation’s voice infrastructure can bring applicable systems and transmissions into scope. A telephone payment is therefore not simply a terminal transaction with a different user interface. Reference basis: PCI SSC FAQ 1153.

Map the call route, staff device, payment entry method, recording, transcription, quality review and remote support. Ask what happens before and after the payment portion of the call, including transfers and failed transactions. Do not assume that a pause function works in every path because it appears in a product brochure.

Test the intended workflow with appropriate nonproduction material. Check what is recorded, what is displayed to staff and what reaches supporting tools. If the method depends on employee action, evaluate whether the instruction is clear and whether exceptions are detected.

PCI SSC states that sensitive authentication data must not be retained after authorisation, even when encrypted. Treat any proposed storage of card verification codes as a specific issue to resolve, not an acceptable consequence of healthcare recordkeeping. Reference basis: PCI SSC FAQ 1533.

Build a responsibility matrix around actual services

Separate the healthcare organisation’s tasks from those performed by payment processors, portal suppliers, billing companies and technical administrators. For each relevant control or service commitment, identify who implements it, who supplies evidence and who reviews changes.

A provider’s general assurance statement may not cover the particular service being used. Ask which integration, location, system and period the evidence addresses. Keep unanswered questions visible. If a supplier operates an important control on your behalf, the assessment needs evidence relevant to that service.

PCI SSC’s third-party guidance emphasises oversight and the effect of provider-operated controls on the customer’s assessment. Outsourcing does not eliminate the need to understand retained responsibilities. Reference basis: PCI SSC FAQ 1312. The third-party PCI DSS guide develops the practical evidence request.

Give finance and clinical operations a role in the matrix. They often control refunds, reconciliation and communications even when IT administers the systems. An action assigned only to the infrastructure team may leave the actual payment workflow unchanged.

Example: a US clinic group introduces online balances

In this hypothetical example, a clinic group introduces a portal through which patients can view balances and make payments. The payment form is provided by a specialist supplier, while the clinic controls the surrounding website, account access and billing exports. The initial project plan assumes the supplier handles all payment-security work.

The channel map distinguishes collection from the systems and staff that can affect the journey. It identifies who can change the website, how payment status returns to the billing system and which records finance exports for reconciliation. The team asks the accepting organisation to confirm the validation expectations for the actual arrangement.

A walkthrough finds that staff copy failed-payment details into general support tickets. The organisation reviews which fields are needed, changes the instruction and tests the revised escalation route. The supplier-hosted form remains part of the solution, but it does not explain this separate support practice.

The project finishes with a defined boundary, assigned controls and an evidence plan. The team does not describe the whole healthcare environment as validated merely because one provider supplied a compliant service.

Example: a hospital billing office changes call recording

A second hypothetical US organisation centralises billing calls. Its new recording platform supports quality review and transcription. Staff also handle payment queries during calls, and some agents work through remotely managed devices. The system replacement appears operationally straightforward until the payment flow is examined.

The review maps where account data can be spoken, entered, recorded or included in a transcript. It tests call transfers and failure paths, not only a scripted successful transaction. The team identifies who configures the recording behaviour and who checks whether the intended controls operate after updates.

Healthcare privacy reviewers separately examine the information and relationship questions for the recording and transcription services. Payment reviewers address the card-data path and validation dependencies. Shared records support both reviews, but each records its own scope and conclusion.

The rollout plan assigns training, configuration checks and escalation. Staff receive a clear alternative when the approved payment path is unavailable. The organisation preserves test results and unresolved conditions instead of claiming that one platform setting removes every responsibility.

Turn findings into separate, coordinated work packages

Group remediation by the team that can implement it: payment integration, website administration, endpoint and network configuration, billing operations, supplier management and healthcare information governance. Link each action to the risk or requirement it addresses and the evidence needed for closure.

Keep dependencies explicit. A recording change may require the provider’s configuration, local staff instructions and a test across call transfers. A refund restriction may require finance approval as well as an application change. Closing only the technical ticket does not demonstrate that the full workflow works.

Use a verification record showing the deployed version, test conditions, observed result and limitations. If a safeguard fails, retain the failure and correction. Do not replace the original evidence with a clean summary that obscures the issue.

Where testing or formal assessment requires a particular qualified provider, identify that dependency in the project plan and verify the relevant status when commissioning it. Readiness consulting and implementation support should not be described as an assessor appointment or a completed validation.

Confirm the validation request with the accepting organisation

Prepare a concise brief for the relevant acquirer, payment brand or other compliance-accepting organisation. Include the entities, merchant arrangements, channels, providers and intended changes. Ask for the reporting expectations that apply to the actual environment; do not choose a questionnaire solely because another healthcare organisation used it.

PCI SSC explains that payment brands manage their compliance programmes, including validation expectations. The precise request therefore needs confirmation with the responsible organisation. Reference basis: PCI SSC FAQ 1212. A consulting plan can prepare evidence, but it does not dictate the recipient’s acceptance decision.

Keep the requested submission date separate from the implementation plan. Work backwards through supplier answers, configuration changes, operating evidence and any required specialist assessment. If a dependency is unresolved, communicate its effect rather than promising a result based only on a target date.

Maintain the boundary after launch. New locations, payment methods, support tools and integrations should reach the scope owner. A previously accurate map can become misleading if the organisation changes the payment journey without updating the evidence and responsibilities.

To plan remediation effort against the recipient's request, discuss scope, sequencing and assessment dependencies while keeping HIPAA role questions and PCI validation decisions distinct.

Questions about healthcare payment boundaries

Does HIPAA compliance establish PCI DSS compliance?

No. The requirements, information and assurance decisions differ. Some safeguards and records may be useful to both programmes, but each needs its own scope and assessment.

Does a hosted payment form remove all local responsibilities?

No automatic conclusion follows. Review the integration, surrounding systems, staff handling and provider responsibilities, then confirm the validation route for the actual environment.

Should recorded billing calls be included in discovery?

Yes. Determine whether account data can enter recordings, transcripts or quality-review tools and examine the relevant paths and safeguards. Do not assume a feature prevents exposure without testing its configured behaviour.

Can clinical retention rules justify keeping verification codes?

Do not use a general retention policy to justify prohibited payment-data storage. Identify the specific fields and resolve the payment-security and healthcare-record questions with the appropriate owners.

What is the most useful initial project input?

A sanitised channel and responsibility map, the recipient’s validation request and the planned operational changes. Avoid sending card values, patient records or production credentials in an initial enquiry.

Reference basis

PCI SSC FAQs 1153, 1212, 1312 and 1533; HHS Business Associates guidance, checked 13 October 2026. Use the channel map to coordinate payment and healthcare reviews while preserving their distinct conclusions. Confirm scope, provider responsibilities and reporting expectations for the actual services before commissioning the next work package.

Scope the payment journey before commissioning remediation

Bring the channels, provider arrangements and validation request to our US PCI DSS consulting service. A focused initial discussion can identify which teams, evidence and separate healthcare-information decisions the project needs.