Visit reason sent to a third-party analytics SDK
Every booking sends the patient's stated reason for the visit as an event property. DAST saw it leave the device in the analytics request. The vendor now holds health data you never meant to share.
56 analytics.track("appointment_booked", mapOf( 57 "reason" to visit.reason, 58 "provider" to visit.providerName))
"migraine follow-up", in someone else's database.
56 analytics.track("appointment_booked", mapOf( 57 "specialty" to visit.specialtyCode))
No diagnosis, no names. The funnel still works.