How should maternity clinics use digital identity to improve continuity of care for undocumented patients?

Clinics should register each patient once, capture core identity details plus a biometric such as fingerprint or face, and require the same patient to authenticate on return visits. That creates a persistent record for antenatal checks, class attendance, and follow-up care. The key is continuity, so staff can recognise missed appointments, maintain treatment history, and coordinate support across pregnancy and postnatal visits.

Why digital identity changes continuity of care

For maternity services, digital identity is not just a login mechanism, it is a continuity mechanism. When a clinic can recognise the same patient across visits, it can preserve antenatal history, test results, appointment patterns, referrals and follow-up tasks even when the patient lacks stable paperwork. That matters most where the care journey spans months and where missed handoffs can affect both maternal and newborn outcomes.

A practical identity record should be built around persistent, low-friction recognition. The strongest models combine a unique patient record with a repeatable authenticator, so the clinic can link a return visit to the same history without forcing the patient to re-prove everything from scratch. In cross-border or portable identity contexts, eIDAS 2.0, the EU Digital Identity Framework shows how reusable digital identity can support repeated verification and service continuity at scale.

In practice, the value comes from reducing identity fragmentation. If one clinic writes “unknown,” another writes a different name spelling, and a third has no way to match the same patient, the care record becomes unreliable. A durable digital identity layer helps staff connect visits, preserve longitudinal notes and avoid treating follow-up as a first-time encounter every time.

What clinics should capture and how authentication should work

The identity data captured should be enough to support safe re-identification, but no more than the care workflow needs. Clinics usually need a core demographic record, a stable clinic identifier, and a repeatable factor such as fingerprint or face so returning patients can authenticate quickly. For undocumented patients, the practical design goal is to make recall easy without making the process dependent on documents the patient may not have.

That means the clinic should distinguish between identity proofing and repeat authentication. Initial registration may rely on lighter assurance than a bank account opening process, but the clinic still needs enough confidence that the same person is linked to the same record on future visits. The repeated check should be fast, reliable and usable at the front desk, in antenatal classes and in postnatal follow-up.

Where biometrics are used, they should support continuity rather than become a barrier. A face or fingerprint can help clinics retrieve the right record, but staff still need a fallback path for failed scans, changed appearance or sensor problems. The identity system should therefore be designed as a clinical workflow tool, not as a perfect gate that blocks care when technology fails.

How continuity improves follow-up, referrals and care coordination

Once the same patient can be recognised across encounters, the clinic can do more than store a chart. It can flag missed appointments, carry forward antenatal risk factors, coordinate referrals and keep track of education, screening and postnatal review. That continuity is especially important when undocumented patients move between locations, return irregularly or rely on multiple community touchpoints for care.

This is where identity lifecycle thinking matters. Lifecycle management is a useful model even in a patient-care setting, because continuity depends on registration, updating, re-identification and clean closure of stale records. Clinics also benefit from healthcare identity security practices that reduce record duplication, shared access and patient-matching errors.

For patients, the benefit is practical: fewer repeated questions, fewer lost results and a better chance that the clinic notices when care is drifting. For staff, the benefit is operational: one longitudinal view instead of a series of disconnected visits. That improves triage decisions, outreach and handoff quality across pregnancy and the postnatal period.

Risk and Threat Considerations

Digital identity only helps continuity if the matching process is accurate and resilient. The main risks are duplicate records, false merges, biometric failure, coercion, and over-collection of sensitive data. In a maternity setting, those failures can lead to missed treatment history, wrong-patient follow-up or unnecessary exposure of a patient’s immigration status.

Failure mechanism: If registration is weak or matching rules are too loose, the clinic may link the wrong visit to the wrong patient, or create multiple records for the same person. If biometric fallback is poor, the patient may be unable to re-enter care when recognition fails.

Impact: That breaks continuity, increases clinical error, and can discourage undocumented patients from returning. It can also create privacy harm if identity data is broader than the care need or accessible to too many staff.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 sets the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

Framework	Control / Reference	Relevance
NIST SP 800-53 Rev 5	IA-8 — Identification and Authentication (Non-Organizational Users)	Undocumented patients are external users whose identity must be re-recognized across visits.
	IA-12 — Identity Proofing	Initial enrolment needs enough assurance to bind the patient to a persistent record.
	IA-5 — Authenticator Management	Biometrics and other authenticators need lifecycle handling and fallback planning.
Recommendation — Use IA-8 to support repeat patient authentication without relying on documents at every visit. Use IA-12 to establish a durable patient record before follow-up authentication. Manage authenticators so returning patients can authenticate reliably and recover when a factor fails.
ISO/IEC 27001:2022	A.5.15 — Access control	Clinic records must limit who can retrieve or update linked patient identity data.
	A.5.12 — Classification of information	Patient identity and biometric data require handling rules based on sensitivity.
Recommendation — Apply access control so only authorised staff can resolve and edit patient identity records. Classify patient identity data so clinics apply tighter handling to biometric and contact attributes.

Practitioner Guidance

What to prioritise: Design the identity workflow around re-identification at the next visit, not just first-time enrolment. The operational question is whether staff can retrieve the right record quickly when a patient returns after weeks or months.

What to verify: Test the fallback path before trusting the system. If a biometric scan fails, staff should still be able to confirm the patient and continue care without restarting registration or escalating to a manual exception that delays treatment.

What good looks like: A returning patient is matched to the same longitudinal record, the clinic sees prior antenatal notes immediately, and missed visits can trigger outreach rather than data loss.

Practitioner takeaway: The right design is one that preserves the care history with minimal friction, while keeping identity matching accurate enough that continuity does not come at the cost of patient safety or privacy.