GDPR/compliance notifications on record update

**Purpose**

1.1 To ensure acupuncturists maintain compliance with GDPR or other regulations by alerting practitioners/staff when patient records are updated or accessed, supporting robust audit trails, privacy policy adherence, and immediate staff action on potential data risks.
1.2 Automates real-time or batched notifications (via email, SMS, in-app, or ticketing) to compliance officers and relevant personnel upon sensitive data modification, fulfilling legal documentation and accountability measures.

**Trigger Conditions**

2.1 Patient record is created, updated, or deleted in EMR/EHR or CRM system.
2.2 Fields containing personal health information (PHI) or personally identifiable information (PII) are edited.
2.3 Practitioner or admin role accesses or exports compliance-tagged patient data.
2.4 System detects a failed access or unauthorized modification attempt.

**Platform Variants**

3.1 Salesforce Health Cloud
• Feature/Setting: Use Change Data Capture & Platform Events to trigger Process Builder/Flow; notify via email alert to compliance team.
• Configuration: Enable Change Data Capture on Patient__c; set Flow for "Field update detected" → Send Email.

3.2 HubSpot CRM
• Feature/Setting: Workflow Automation on Contact Property Change.
• Configuration: Create workflow "If Contact’s Sensitive Info changes" → Send internal notification/email.

3.3 Microsoft Power Automate (with Dynamics 365)
• Feature/Setting: Record modification trigger in Dynamics 365 to flow; configure compliance notifications via Teams, email, or adaptive card.
• Configuration: Set Dynamics record update as trigger → Send Teams message to compliance group.

3.4 Google Workspace (Sheets & Gmail)
• Feature/Setting: App Script on Google Sheet edit; trigger email via Gmail API.
• Configuration: “OnEdit” script monitoring PHI columns → send email via Gmail API.

3.5 Slack
• Feature/Setting: Incoming Webhooks to a compliance channel.
• Configuration: Webhook receives data on update events → Post alert in #compliance-alerts.

3.6 AWS SNS
• Feature/Setting: Publish notification via API call on patient-data Lambda trigger.
• Configuration: Lambda watches DynamoDB for updates → SNS topic publishes to compliance email/SMS.

3.7 Twilio SMS
• Feature/Setting: Send SMS alert via REST API on record update webhook.
• Configuration: HTTP request to Twilio SMS endpoint with customizable compliance alert text.

3.8 SendGrid
• Feature/Setting: Send transactional email on compliance event using API.
• Configuration: Use /mail/send endpoint, including patient record details in alert to compliance officer.

3.9 Zendesk
• Feature/Setting: Create compliance ticket via API when PHI is updated.
• Configuration: Use create ticket endpoint, categorize as “GDPR Update Notification”.

3.10 ServiceNow
• Feature/Setting: Incident creation using REST API on EMR update.
• Configuration: API integration creates incident categorized under “Compliance”.

3.11 Google Chat
• Feature/Setting: Post message to compliance room via Chat API.
• Configuration: Outbound webhook posts summary of change event.

3.12 Microsoft Teams
• Feature/Setting: Incoming Webhook configured to compliance channel.
• Configuration: Post compliance alert on patient data changes.

3.13 Okta
• Feature/Setting: System Log API filters for PII record changes; push alerts.
• Configuration: Event hook to call endpoint on log event.

3.14 PagerDuty
• Feature/Setting: Create incident via Events API for urgent compliance breaches.
• Configuration: API event sent from EMR or log monitoring trigger.

3.15 Zapier
• Feature/Setting: Catch webhook and send email/SMS/in-app chat.
• Configuration: Triggered via webhook from CRM/EMR, Zap routes to compliance contacts.

3.16 Monday.com
• Feature/Setting: Automation recipe for item update; notify stakeholders.
• Configuration: “When column changes” recipe triggers email/Slack alert.

3.17 Jira Service Management
• Feature/Setting: Automation rule to create compliance issue/ticket.
• Configuration: Webhook triggers “New GDPR Notification” issue.

3.18 Trello
• Feature/Setting: Butler automation to create a card in compliance board.
• Configuration: Card titled "GDPR Alert: Patient X Record Updated" auto-created.

3.19 Freshservice
• Feature/Setting: Create alert/ticket using webhook or API.
• Configuration: Endpoint called on record update creates ticket labeled “GDPR”.

3.20 Pipedrive
• Feature/Setting: Workflow automation on contact update; notify via email.
• Configuration: Set workflow for “When field changes in contact”, send compliance email.

3.21 DocuSign
• Feature/Setting: Event Notification via Connect webhook on envelope/document change.
• Configuration: Connect triggers HTTP POST to compliance endpoint.

3.22 Dropbox
• Feature/Setting: File update webhook sends alert to compliance.
• Configuration: Webhook monitors record PDFs for access/update events.

**Benefits**

4.1 Enhances audit readiness and supports regulatory inspections.
4.2 Reduces the risk of non-compliance penalties through proactive alerts.
4.3 Streamlines practitioner focus on core tasks by minimizing manual compliance checks.
4.4 Enables timely investigation and remediation of potential data incidents.
4.5 Builds trust and transparency with patients regarding data protection.