commvita
Connected care platform
Sexual health

A clinic where some people have no name

Anonymous and named attendances in the same queue, a safeguarding review that has to happen before the consultation, a cluster notified upward, and why none of this data is reachable from the rest of the platform.

Live vs demonstrated: Live — real, API-backed platform logic (wired end-to-end today) Demonstrated — representative control surface with seeded data / illustrative UI mock-up
© 2026 Commvita Digital Health Solutions Ltd. All rights reserved.

1 A clinic where some people have no name

Sexual health is the one service where a person can walk in, give no name, be treated, and be counted — and the record has to work for that. commvita’s clinic queue holds anonymous attendances alongside named ones, on a clinic number.

The sexual health clinic queue showing four attendances, one marked anonymous, with presenting complaint, flags, status and clinician
Four in the queue, one anonymous, one flagged for safeguardingCaptured from the running system, build B-592 · seeded clinic

The queue carries the presenting reason, the flags and who is treating. SH24002 has no name against it, an ANON marker, and a safeguarding flag. That combination is the hard case in this service and the screen handles it without asking anyone to break the anonymity to raise the concern.

2 Two alerts that stop the clinic

Two banners sit above the queue, and both name what has to happen before anything else does.

Two banners: a safeguarding flag requiring review with the safeguarding lead before consultation, and a UKHSA cluster alert for a syphilis cluster with linked cases
A safeguarding review before the consultation, and a cluster notified upwardCaptured from the running system, build B-592 · seeded alerts

The first says an anonymous patient presenting for emergency contraception needs reviewing with the safeguarding lead before the consultation. Not logged afterwards, not flagged for audit — before. The second says a syphilis cluster has been detected with a linked case, the health protection team has been notified, and enhanced partner notification is running.

That second one is the whole argument for holding sexual health in a connected record. A cluster is only visible if somebody can see across the cases, and partner notification only works if the links are held somewhere.

3 The rest of the service

Behind the queue sit STI screening, HIV and PrEP, contraception, partner notification and the GUMCAD return.

Each one is a genuinely different job. Screening is a pathway with results coming back. PrEP is ongoing prescribing with monitoring attached. Contraception runs to a review date, as the coil check on the queue shows. Partner notification is a set of links between people who mostly don’t know each other’s names. GUMCAD is the mandatory return that makes the national picture.

Where it lives in commvita

CapabilityRouteWhat it holdsStatus
Clinic queue (named and anonymous)/sexual-health-eprAttendance, complaint, flags, clinician● Live
STI screening/sexual-health-eprScreens ordered and results back● Live
HIV and PrEP/sexual-health-eprPrescribing with monitoring● Live
Contraception/sexual-health-eprMethod, fitting, review date● Live
Partner notification/sexual-health-eprLinks between contacts, cluster handling● Live
GUMCAD return/sexual-health-eprThe mandatory dataset and its analytics☉ Demonstrated
This data doesn’t leak into the rest of the platform. Sexual health sits under Article 9 and commvita treats it that way: there’s no patient-keyed sexual health register that population health or the communications engine can target, and a campaign can’t reach into this service to build a cohort. The clinical team can see their patients. Nothing else can.
© 2026 Commvita Digital Health Solutions Ltd. All rights reserved.GUMCAD STI surveillanceBASHH standardsUK GDPR Article 9Non-SaMD