De-identification tool to scrub HL7 messages and protect patient data at the source. Remove PHI data while keeping the data history.
No need to work with production data. De-identify or scrub HL7 messages so you can work with production like messages without putting PHI at risk. Produce auditable reports after each de-identification of PHI. Generate clinically valid data for interface development, testing, and analytics — and remain compliant with your HIPAA PHI policies and procedures.
Cloak not only removes PHI, the software also lets you insert realistic replacement data.
Patient Names and Addresses
Pull names and address from Excel lists that come built into Cloak. Or use your own.
Dates and Times for Workflows
Change dates of birth, admission times, med admin times, and more. Date/time settings allow you to set realistic ranges.
Phone Numbers and SSNs
Remove them altogether. And if needed, insert markers to indicate removal.
Free Text and Unstructured Data
Cover all your bases. Remove patient names from HL7 fields that include physician narratives.
Multiple Data Sources
When you’re de-identifying HL7 data, you need options. Cloak lets you generate replacement data in multiple formats, including strings and Boolean characters. Also, pull replacement data from databases through SQL queries.
HL7 Integration: From Trial and Error to Predictable Project Outcomes
Learn how Interface Lifecycle Management can cut complexity and costs.
Hello HL7 community, we’ve decided to give the old HL7-Definition reference website its well-deserved retirement. We’re now proud to introduce the new and improved HL7-Definition V2 website.
We’ve been asking for [...]