Industries · Healthcare
Genesys Cloud CX for healthcare contact centres
Patients, members and clinicians call about things that matter to them: a delivery of medicine, a nursing visit, a claim, a system they rely on at work. Healthcare contact centres handle some of the most sensitive data there is. We design Genesys Cloud CX contact centres that protect it, meet the standards that apply on each side of the Atlantic, and let people help themselves safely.
What matters most
- Health data is special category data under UK GDPR, and protected health information under HIPAA in the United States, so where it flows is designed, not assumed.
- In the US, Genesys signs a business associate agreement for HIPAA organisations in its US regions; what you connect to it needs the same care.
- NHS-connected organisations have their own assurance and accessibility standards that shape how the contact centre works.
- Self-service must identify people safely and always leave a clear way to a person.
01
Health data needs a designed path
In the UK, data concerning health is special category data under UK GDPR, which the ICO explains carries significant risks to people's fundamental rights and freedoms if misused. The ICO notes that its guidance is under review following the Data (Use and Access) Act, so we check the current position with your data protection team at the start of every project. In a contact centre, health data appears in more places than people expect: what callers say, what an IVR collects, what an agent's script shows, what a recording keeps, what an analytics tool transcribes and what an integration sends to another system.
We map that path in discovery and design each step on purpose. Data actions fetch only the fields a journey needs, scripts show only what the agent needs, recordings follow agreed policies, and integrations are documented as contracts so your information governance team can see exactly what crosses each boundary. Genesys Cloud CX can be deployed in its London region for UK organisations, and in US regions for US organisations, so data stays where your obligations say it should.
02
HIPAA and the business associate agreement
In the United States, the HIPAA Privacy Rule sets national standards for protecting certain health information, and the Security Rule sets the administrative, physical and technical safeguards that covered entities and their business associates must put in place for electronic protected health information. HHS explains that a covered entity needs satisfactory assurances, in a written contract known as a business associate agreement, from any business associate that creates, receives, maintains or transmits protected health information on its behalf.
Genesys states that every HIPAA Genesys Cloud organisation requires a valid business associate agreement with Genesys, that HIPAA compliance is available in its AWS US East and US West regions, and that there is no HIPAA certification for a cloud services provider. Genesys also notes that its agreement does not extend beyond Genesys Cloud, and that some channels, such as ACD email and SMS, are excluded. We design around those boundaries: which channels carry protected health information, which integrations need their own agreements, and how the contact centre is configured once the HIPAA setting is enabled.
03
NHS assurance and accessible communication
In England, all organisations that have access to NHS patient data and systems must use the Data Security and Protection Toolkit to provide assurance that they handle that data well. A contact centre that supports NHS-funded services, or a supplier's service desk that handles NHS patient information, is part of that picture, so its access controls, recording, retention and integrations are designed with the toolkit's expectations in mind and documented for your next submission.
The Accessible Information Standard requires providers of NHS and publicly funded adult social care to identify, record, flag, share and meet people's information and communication needs, and to review them. A contact centre can make that real: data actions can read a recorded communication need so the IVR offers a different route and the agent's script shows it before the conversation starts, and messaging and callbacks give people alternatives to waiting on the phone.
| Obligation | Where it comes from | How we address it |
|---|---|---|
| Protect special category data | UK GDPR, ICO guidance | Mapped data paths, minimal data actions and agreed recording policies |
| Safeguard protected health information | HIPAA Privacy and Security Rules | US region, business associate agreement and HIPAA configuration |
| Assure NHS patient data handling | NHS Data Security and Protection Toolkit | Access control, retention and integration contracts documented for assurance |
| Meet communication needs | NHS Accessible Information Standard | Needs read from your records, shown to agents and used in routing |
| Keep data in the right country | Your obligations and contracts | London or US regions chosen in design |
04
Self-service that patients and members can rely on
Many healthcare calls follow a pattern: when is my delivery, can I book it, what does my plan cover, where is my claim. Self-service that answers them safely frees clinical and support teams for the conversations that need a person. The design challenge is identifying people securely, using only the data each journey needs, and handing over gracefully, with context, whenever the caller needs help.
For a UK healthcare services provider, our Phase 1 lets patients be identified from their number, check their prescription and order, choose from up to three delivery dates and book the order in the IVR, with a two-hour delivery window for orders already on their way. For a US health benefits provider, we rebuilt an immense IVR on Genesys Cloud CX with eight voice bots and 17 back-end APIs, so members and providers check eligibility, benefits and claims and receive summaries by fax or email.
05
How QVCCS works with healthcare organisations
We muster a multidisciplinary team from our own bench, with leadership in contact centre technology since 1984, and every delivery team member holds, or is completing, Genesys Cloud certification. Discovery brings in your clinical leads, information governance, data protection and security teams alongside operations, so requirements reflect how care is actually delivered. We are comfortable working in phases: going live with a minimum viable product when integrations are late, then adding self-service once the systems behind it are ready.
Every release is built and tested in a development organisation before it reaches patients or members, and every go-live follows a written method statement. We work directly with healthcare organisations and through global systems integrators and reseller partners, and we are a Genesys referral partner, not a reseller.
In practice
Our healthcare case studies
A US health benefits provider: Avaya to Genesys Cloud CX, with an immense self-service IVR
- Users
- 172
- Licence
- Genesys Cloud CX 1
A UK healthcare services provider: live on Genesys Cloud first, then delivery self-service
- Users
- About 55, including an outsourced partner's agents
- Licence
- Genesys Cloud CX 3
A global healthcare software company: one support design on Genesys Cloud CX and Zendesk
- Users
- 80
- Licence
- Genesys Cloud CX 2
Questions
Common questions
Will Genesys sign a business associate agreement?
Yes. Genesys states that every HIPAA Genesys Cloud organisation requires a valid business associate agreement with Genesys, and that HIPAA compliance is available in its AWS US East and US West regions. The agreement does not extend beyond Genesys Cloud, so the systems you connect need their own arrangements.
Is Genesys Cloud CX HIPAA certified?
Genesys explains that there is no HIPAA certification for a cloud services provider such as Genesys Cloud. Instead, Genesys signs a business associate agreement and enables HIPAA settings for the organisation. Genesys separately lists HITRUST among the standards Genesys Cloud is certified against in the Americas.
Can patient data stay in the UK?
Genesys Cloud CX has a core region in London, and a UK organisation's contact centre can be deployed there. Where data goes beyond Genesys Cloud, for example to analytics, CRM or other integrated systems, we document each flow so your information governance team can confirm where it is processed.
Do we need to complete the NHS Data Security and Protection Toolkit?
NHS England says that all organisations that have access to NHS patient data and systems must use the toolkit. If your contact centre supports NHS-funded services or handles NHS patient information, its design should support your submission, and we document access, retention and integrations with that in mind.
Genesys Cloud CX capabilities we bring to healthcare
Sources
- What is special category data? – ICOico.org.uk
- Summary of the HIPAA Privacy Rule – HHShhs.gov
- Summary of the HIPAA Security Rule – HHShhs.gov
- Business associates – HHShhs.gov
- Data Security and Protection Toolkit – NHS England Digitaldigital.nhs.uk
- Accessible Information Standard: requirements – NHS Englandengland.nhs.uk
- HIPAA compliance – Genesys Cloud Resource Centerhelp.genesys.cloud
- Supported security, privacy and AI standards – Genesys Cloud Resource Centerhelp.genesys.cloud
- AWS regions for Genesys Cloud deployment – Genesys Cloud Resource Centerhelp.genesys.cloud
Regulatory summaries are for orientation, not legal advice; the sources above are authoritative and your own compliance and legal teams decide how they apply.