...
Being HIPPA certified has challenges for us as an Email processor /sender, we need PII PHI (Email Addresses) for core functionality. We don’t specifically ‘know’ what data you store, so can’t specifically ‘redact’. We are not HIPPA certified at this point. The following would be seen as the ‘technical measures’ our app has that could be applied for HIPPA compliance.
The JSM notification templates we use include a limited subset of fields that notifications include, so overall JEMHC meausres measures in place that support HIPPA could be viewed as:
We limit what field we send in notifications (not all changed fields would be sent), you can add more fields specifically.
You can enable/disable inline images and attachments to be sent (at all)
You can enable/disable email-user support (that stores email addresses in custom fields where no portal user / Jira user is desired), Email Addresses are PIIPHI, are a HIPPA data category, for HIPPA compliance, you’d probably have to not use this feature
You can enable/disable attachment of the raw Email to the issue, again for HIPPA compliance you’d probably have to not use this feature.
If an inbound mail is not processed, a ‘fwd’ mail is sent to the Profile > Forward Users, linking to the Audit record involved. If you have disabled auditing the full mail is attached to avoid data loss. The full mail obviously contains IP addresses, recipient addresses, full content etc.
If you flag a mail for support in auditing, an issue is created in our support system referring the audit record. Only such flagged mails (its processing Report, your Profile) are available to all our support staff via a back-office app, through which data downloads can occur, such data is burned when support tickets are closed out.
...