Welsh shared care records show why centralised patient data matters

At a glance

What this is: NHI Mgmt Group's analysis, drawing on Imprivata's blog post: Wales' shared care records use a central repository covering 3.1 million people and used by more than 45,000 clinicians.

Why it matters: It matters because health IAM has to support fast, secure access across mobile and cross-site clinical workflows without breaking the trust model around patient data.

By the numbers:

• The portal is used by over 45 thousand clinicians across all areas of Wales.

Context

Shared care records are a health information governance model that centralises patient information so clinicians can access a more complete record during direct care. In Wales, the article argues that this model reduces the fragmentation created by siloed records and supports safer decisions across care settings.

The identity question is not whether data should be shared, but how access is scoped, governed, and made usable for clinicians working across locations and devices. The article frames Wales as an example of how identity and access controls must support mobile, cross-site care without weakening confidentiality or accountability.

Key questions

Q: How should health systems govern shared care record access across multiple sites?

A: Health systems should govern shared care record access by combining role-based access, clinical context, and strong audit trails. The goal is to let authorised clinicians reach the right patient information quickly while preserving accountability across sites, devices, and temporary staffing models. Static local permissions are not enough when care moves across organisations.

Q: Why do central patient records improve clinical decision-making?

A: They reduce the delay and uncertainty created by siloed systems, giving clinicians a fuller picture of history, tests and treatment in one place. That improves continuity of care, but only when the identity layer makes access timely enough for real-world clinical use.

Q: What are the risks of giving clinicians mobile access to shared records?

A: The main risk is not mobility itself, but over-trusting devices and sessions that move across wards, sites and networks. If authentication, session control and audit are weak, mobile access can widen exposure while still looking operationally convenient.

Q: What should hospitals do when shared records span multiple care settings?

A: Standardise access workflows, entitlement review and audit handling across all settings so the record behaves like one governed system instead of several loosely connected ones. That keeps direct care fast while reducing the chance of policy drift between sites.

Technical breakdown

Central repositories and longitudinal patient records

A shared care record consolidates data from many care events into one longitudinal record so clinicians can see history, test results, imaging and care plans in context. Technically, the value comes from reducing fragmentation: the source system is no longer the only place where the current record exists. That changes governance because access decisions now apply to a central dataset rather than isolated departmental records. In practice, this raises the bar for authentication, authorisation, audit logging and device trust across the clinical estate.

Practical implication: Practitioners should treat central repositories as high-value identity targets and align access control, logging and device posture with the sensitivity of the unified record.

Mobile clinical access and identity assurance

When a shared record is available on iOS and Android, the access model must assume clinicians are moving between wards, sites and devices while still needing timely care data. That means identity assurance, session controls and entitlement design matter more than location-based trust. The portal is not just a convenience layer. It is the operational front door to patient information, so governance has to cover authentication strength, session timeout, role scoping and break-glass behaviour for urgent care.

Practical implication: Security teams should validate that mobile access policies preserve clinical speed without turning every device into a broadly trusted endpoint.

Cloud-hosted health data and shared responsibility

The Welsh National Data Repository illustrates the shift from local infrastructure to cloud-hosted patient data. That changes the control plane rather than removing it: availability, resilience, tenant separation, access governance and auditability become shared responsibility concerns. Central storage can improve consistency and reduce local infrastructure burden, but it also concentrates the blast radius if identity controls fail. The security challenge is to make the cloud repository easier to govern than a patchwork of local stores, not merely easier to reach.

Practical implication: IAM and cloud teams should align repository access with least privilege, strong audit trails and explicit administrative boundaries.

NHI Mgmt Group analysis

Shared care only works when access is governed as a clinical workflow, not a data warehouse problem. The article shows that Wales is using centralised patient data to support direct care, research and mobile working. That makes identity and access the control plane for clinical utility. When access policy is designed around the needs of care delivery, the record becomes usable; when it is designed around infrastructure convenience, the programme stalls.

The governance risk is not centralisation itself, but over-trusting the central record. A single repository reduces fragmentation, yet it also concentrates sensitivity and decision impact. That means identity proofing, role design and auditability have to be stronger than in a siloed environment. Practitioners should read this as a reminder that central access does not eliminate local governance, it intensifies it.

Health IAM has to reconcile speed, mobile use and accountability in the same access model. Clinicians need immediate access across devices and settings, but patient records cannot be treated like ordinary shared content. The practical lesson is that identity policy must preserve clinical flow while still proving who accessed what, when and why.

Useful, usable and used is an identity requirement, not just a product principle. The article’s change-management theme matters because clinicians will bypass systems that slow care or fragment the record again. That makes adoption a governance issue: access controls, workflows and training have to align or the organisation recreates shadow processes around the official record.

Shared care records reveal the importance of a governed patient-data fabric. Wales is showing that cross-site care depends on a record layer that is central, secure and operationally trusted. The implication for practitioners is that identity, audit and data-sharing policy must be designed as part of the care model, not added after deployment.

What this signals

Shared care records create a governed data fabric for clinical work. The programme value is not just central storage. It is the ability to make identity decisions once and have them hold across multiple care settings, devices and service lines. That is where identity governance becomes part of service delivery rather than a separate control activity.

Health systems that centralise patient data need stronger entitlement discipline, not looser access for convenience. The more complete the record, the more important it becomes to prove clinical need, limit scope and preserve auditability. In practice, that means shared care programmes should be designed around access assurance as carefully as around data consolidation.

For practitioners

• Map clinician roles to record scope Define which patient record elements each clinical role actually needs, then translate that into least-privilege access policies for shared care systems.
• Strengthen mobile access governance Review authentication strength, session duration and device trust for iOS and Android access to shared records so mobile use remains clinically fast and accountable.
• Align audit trails with direct care Ensure every access to the central repository can be traced to a user, purpose and care context so clinical visibility does not weaken accountability.
• Standardise access across care settings Use the shared record programme to reduce site-specific exceptions and make clinician onboarding consistent across hospitals, community services and locum working.

Key takeaways

• Centralised shared care records solve a real clinical fragmentation problem, but they also make identity and access governance the primary control plane for safe use.
• The Wales model shows that mobile, cross-site clinical work depends on timely access to a longitudinal record, not on isolated departmental systems.
• Practitioners should tighten role scoping, auditability and mobile access controls at the same time they expand shared data access.

Key terms

• Shared Care Record: A shared care record is a centralised view of patient information assembled from multiple care settings. It gives clinicians a longitudinal history rather than isolated episode data, which improves continuity of care but also raises the stakes for access governance, auditability, and lifecycle control across organisations.
• Longitudinal Patient Record: A longitudinal patient record is a combined view of a patient’s health information across time and care settings. It brings together clinical, demographic, social, and treatment data so providers can see patterns, outcomes, and context. In practice, it supports more informed decisions, better coordination, and a fuller understanding of the patient journey.
• Clinical Access Governance: Clinical access governance is the oversight of how healthcare staff, contractors, and affiliated providers receive and keep access to clinical systems. It combines policy, workflow, review, and audit requirements so security controls do not block patient care while still protecting sensitive health information and operational integrity.
• Mobile Clinical Identity: Mobile clinical identity is the identity and session model used when clinicians access patient systems from phones or tablets while moving across sites. It must balance convenience with assurance, because mobile access expands the number of devices and contexts that can legitimately reach the same sensitive record.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are building or maturing an IAM programme, it is worth exploring.