Creation of Clinical Research Databases in the 21st Century: A Practical Algorithm for HIPAA Compliance
- 1 February 2006
- journal article
- research article
- Published by SAGE Publications in Surgical Infections
- Vol. 7 (1) , 37-44
Abstract
Background: Enforcement of the Health Insurance Portability and Accountability Act (HIPAA) began in April, 2003. Designed as a law mandating health insurance availability when coverage was lost, HIPAA imposed sweeping and broad-reaching protections of patient privacy. These changes dramatically altered clinical research by placing sizeable regulatory burdens upon investigators with threat of severe and costly federal and civil penalties. This report describes development of an algorithmic approach to clinical research database design based upon a central key–shared data (CK-SD) model allowing researchers to easily analyze, distribute, and publish clinical research without disclosure of HIPAA Protected Health Information (PHI). Methods: Three clinical database formats (small clinical trial, operating room performance, and genetic microchip array datasets) were modeled using standard structured query language (SQL)–compliant databases. The CK database was created to contain PHI data, whereas a shareable SD database was generated in real-time containing relevant clinical outcome information while protecting PHI items. Small (8 records) model databases were created, and the resultant data models were evaluated in consultation with an HIPAA compliance officer. Results: The SD database models complied fully with HIPAA regulations, and resulting "shared" data could be distributed freely. Unique patient identifiers were not required for treatment or outcome analysis. Age data were resolved to single-integer years, grouping patients aged >89 years. Admission, discharge, treatment, and follow-up dates were replaced with enrollment year, and follow-up/outcome intervals calculated eliminating original data. Two additional data fields identified as PHI (treating physician and facility) were replaced with integer values, and the original data corresponding to these values were stored in the CK database. Use of the algorithm at the time of database design did not increase cost or design effort. Conclusions: The CK-SD model for clinical database design provides an algorithm for investigators to create, maintain, and share clinical research data compliant with HIPAA regulations. This model is applicable to new projects and large institutional datasets, and should decrease regulatory efforts required for conduct of clinical research. Application of the design algorithm early in the clinical research enterprise does not increase cost or the effort of data collection.Keywords
This publication has 15 references indexed in Scilit:
- Protecting patient privacy by quantifiable control of disclosures in disseminated databasesInternational Journal of Medical Informatics, 2004
- Privacy Rule Creates Bottleneck for U.S. Biomedical ResearchersScience, 2004
- Cross sectional survey of multicentre clinical databases in the United KingdomBMJ, 2004
- Health Insurance Portability Accountability Act (HIPAA) RegulationsAnnals of Surgery, 2004
- How (not) to protect genomic data privacy in a distributed network: using trail re-identification to evaluate and design anonymity protection systemsJournal of Biomedical Informatics, 2004
- Data Resources in the Department of Veterans AffairsDiabetes Care, 2004
- Security Middleware Infrastructure for DICOM Images in Health Information SystemsJournal of Digital Imaging, 2003
- Complying with the Health Insurance Portability and Accountability ActAAOHN Journal, 2001
- The zipper: a method for using personal identifiers to link data while preserving confidentialityChild Abuse & Neglect, 2001
- Large Medical Databases, Population-Based Research, and Patient ConfidentialityAmerican Journal of Psychiatry, 2000