Fam Pract Manag. 2001 Jul-Aug;8(7):10.
Underneath all its legal language, the Health Insurance Portability and Accountability Act (HIPAA) is really a challenge to you to live up to one of the cherished ideals of medicine: patient confidentiality.
Sure, you never breach confidentiality. But do you leave messages about test results on a patient’s answering machine? Does anyone in your practice ever fax confidential information to the wrong fax machine? Is your chart room cleaned regularly by an unsupervised cleaning crew made up of people you don’t know? Do you ever see patient charts lying open on an unattended work station in some public area of your practice? Does your billing clerk keep a sticky note on his computer monitor to remind him of his password? You see what I mean.
As David C. Kibbe, MD, MBA, suggests in this issue’s cover story, it’s easy to overreact to HIPAA and the flood of new regulations it is pouring into the health care system. After all, HIPAA is likely to produce sweeping changes in the way health information is managed. Moreover, the line of consultants and lawyers ready to help you rebuild your practice is already forming outside your door – and some of them are sure to use alarmist warnings as a way of drumming up business.
In the words of the late Douglas Adams, “Don’t panic.” As Kibbe explains in the article, HIPAA requires “reasonable and appropriate” safeguards, not foolproof, airtight, paralyzingly expensive safeguards. This is a time to learn about HIPAA regulations and to begin to respond to them as it makes sense to you. Think about the ways you protect patient confidentiality in your practice as well as the ways you don’t. Make a list of loopholes you see in the protection your practice provides patient information. Mark the ones you feel uncomfortable about – the ones that bother you as a physician – and forget the rest for now. Then start fixing the ones you’ve marked. You’re on your way to HIPAA compliance.
Kibbe’s article lays out a reasonable plan for ensuring that your practice does a good job protecting patient information from unauthorized disclosure and from loss. You won’t go wrong if you start there and work systematically. And you have some time to work. The final HIPAA security regulations aren’t expected until the end of 2001, and you’ll have two years to comply after that. As far as regulatory compliance is concerned, consider the time between now and the end of the year a head start. As far as your patients are concerned, consider it an opportunity to improve the privacy and peace of mind you afford them.
JOIN THE FPM PANEL OF READER REPRESENTATIVES
As I said in this space last month, FPM is recruiting readers who are willing to spend a minute or two from time to time responding to questions about what we might cover in the journal and how we could best present it. This is volunteer work that can parlay a minuscule time commitment into disproportionately large benefits for the readers of FPM. If you are interested in participating, please let me know by completing and returning the form below or sending me the requested information by fax or e-mail as described below. Thank you!
If you would like to join, please provide all the information requested below:
Please mail to Robert L. Edsall, FPM, 11400 Tomahawk Creek Pkwy., Leawood, KS 66211–2672; fax to his attention at 913–906–6010; or provide the information requested in an e-mail message to him at firstname.lastname@example.org. Please title your e-mail message FPM Reader. Thank you!
Robert Edsall is editor-in-chief of Family Practice Management. Conflicts of interest: none reported.
Copyright © 2001 by the American Academy of Family Physicians.
This content is owned by the AAFP. A person viewing it online may make one printout of the material and may use that printout only for his or her personal, non-commercial reference. This material may not otherwise be downloaded, copied, printed, stored, transmitted or reproduced in any medium, whether now known or later invented, except as authorized in writing by the AAFP. Contact email@example.com for copyright questions and/or permission requests.
Want to use this article elsewhere? Get Permissions