News for hackers. Stuff that matters.

A comment on Exploring PostgreSQL 18's new UUIDv7 support. Parent comment

Re:Exploring PostgreSQL 18's new UUIDv7 support by tyre on Friday October 17, 2025 @06:16PM (#45622781)
Email is not secure but sending an email with a link to "Information about your appointment" is fine. If that link goes to `/appointments/sjdhfaskfhjaksdjf`, there is no leaked data. If it goes to `/appointments/20251017lkafjdslfjalsdkjfa`, then the link itself contains PHI.

Whether creation date is PHI…I could see the argument being yes, since it correlates to medical information (when someone sought treatment, which could be when symptoms present.)

[ Parent | on HN ]
Re:Exploring PostgreSQL 18's new UUIDv7 support by ensignavenger on Saturday October 18, 2025 @12:11AM (#45624826)
Email may not be secure, but neither are faces and phones, and yet medical professionals use those all the time.
[ Parent | on HN ]
Re:Exploring PostgreSQL 18's new UUIDv7 support by ensignavenger on Saturday October 18, 2025 @09:54AM (#45627411)
Fat fingered fax... faxes, not faces!
[ Parent | on HN ]
Re:Exploring PostgreSQL 18's new UUIDv7 support by lazide on Saturday October 18, 2025 @09:32AM (#45627233)
Notably, this is an absurd argument. Every system I’ve dealt with right now sends the date/time/location/practitioner clear text in the email (or some variant thereof).

The only thing that seems to be protected is ‘reason for appointment’, and not all systems do that.

Everyone signs paperwork to authorize this when they first engage with the medical providers!

[ Parent | on HN ]