Protected Health Information (PHI) is data identifying a patient including personal information, health condition(s), diagnosis, and treatment received. HL7® messages contain such data and HIPAA requires that PHI is protected.
HIPAA requires 18 data elements (identifiers and quasi-identifiers) to be protected. Those 18 PHI data elements include patient identifiers, names, addresses, phone numbers, dates and others.
How to De-Identify PHI?
To remove PHI data, the application provides a set of rules to replace patient identity with another identity while keeping the data history. Messages can still be analyzed. Customize rules to cover specific business rules.
Removing PHI data, keeps the patient data history but links it to a fictional patient. De-identification rules can be adapted to specific needs. Even Z-segment and free text fields (OBX.5, NTE.3, etc) can be managed.
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 [...]