Connected Device Log Anonymization with anonym.plus

Strip patient and serial IDs from device telemetry that holds health data.

Log anonymization is the removal of personal data from the telemetry a connected medical device records. Those readings are health data under GDPR Art. 9. anonym.plus does this on a local machine and keeps the telemetry for engineering work.

When this applies

An infusion pump or monitor writes events tagged with the patient, a serial number, and a network address. For fault analysis, those tags go.

How anonym.plus handles it

  1. Open the telemetry in anonym.plus on a local machine.
  2. It finds the patient key, serial, and network address.
  3. Event codes and sensor values stay in place.
  4. Swap the personal parts with the map switched off.
  5. Save the anonymous file on your machine.

What you need to provide

PHI entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONpatient tag → [PATIENT]
IdentifiersIDserial 22F-0931 → [SERIAL]
NetworkIP_ADDRESS10.0.0.42 → [IP]
IdentifiersIDMAC address → [MAC]
DatesDATE_TIMEevent time → shifted [TIME]
LocationLOCATIONward tag → [PLACE]

Compliance achieved

Anonymize connected device logs offline — see plans & start free →

Limitations & cautions

A serial or MAC address is unique, so it must go for true anonymity. A rare event sequence at a known site can still narrow identity after the tags are gone. Shift the timestamps and keep no re-link key.

Frequently asked questions

Why treat a serial or MAC as personal data?

Each one maps to one device and so to one patient. Under GDPR that is personal data, so the tool flags and swaps it.

Do the sensor values stay?

Yes. Event codes and readings remain, so fault analysis runs while the identifying tags are gone.

Can I run this without the vendor cloud?

Yes. Work on the exported telemetry directly on your machine, with no vendor account.