HIPAA Compliance - A Basic 3 Step Approach
For first timers trying to understand the voluminous HIPAA and its implications to their business, the following information may prove useful.
In a nutshell, HIPAA addresses privacy and security concerns with Electronic Patient Health Information (EPHI), and requires anyone involved in the generation, processing and managing of patient data to implement adequate security controls.
Examples of Systems where patient records are stored include (but are not limited to) Patient Admissions / Registrations; Laboratory Information Systems, Pathology Information Systems, Clinical Documentation Systems, Emergency Department Systems, Patient Safety Systems, Physician Practice Management Systems, Pharmacy Systems, Surgical Systems, Risk Management Systems, Data Warehouses, Medical Devices.
The next step is identifying who accesses the EPHI records from these systems.
Again, examples of personnel and entities accessing patient records are Unit Staff, Patient Care Staff, Physicians and Physicians’ Assistants, Laboratory and Radiology Staff, Quality Improvement Staff, Utilization Department Staff, Medical Records Staff, Medical Transcriptionists, Coders, Information Systems Staff and Revenue Function Staff.
EPHI records are transmitted to Reference Labs, Home Healthcare Providers, Physicians’ Offices, Pharmacies, Billing Administrators, Auditors and Consultants, Payers, Collection Agencies, Transcriptionists, Coding Firms, Information Systems Vendors, Regulatory Agencies and Physician / Patient Information Portals.
Now that the systems and personnel who access and process patient information have been identified, information controls - logical and physical, need to be developed and implemented.
HIPAA specifies 14 mandatory implementation specifications and 22 optional guidelines (depending on operating environment) - sections 308, 310 and 312 specifically deal with these specifications.
In brief, controls for Access Control, Physical Security, Incident Response, Disaster Recovery, Training and Monitoring will need to be designed, tested for compliance and finally implemented.
While HIPAA does not specifically nominate any technology solution, in practice several standard security solutions are used as part of any Defense in Depth approach towards Information Security, to be able to enforce and monitor the controls which have been developed.
This is a very basic description of a HIPAA compliance approach - suggested reading should include:
1. www.hipaa.org
2. www.hipaadvisory.com
Later, I will discuss a couple of real world scenarios as well as evaluate vendor solutions for HIPAA compliance.
Rion
