So, true story - https://www.hhs.gov/sites/default/files/ocr-resolution-agreement-shen-smiles.pdf. It started with one patient asking for her records. The records could not be provided. Then they could not be found. The doctor reportedly told federal investigators that an employee had stolen them. That explanation did not end the problem. It made the problem bigger According to the U.S. Department of Health and Human Services’ Office for Civil Rights, the employee was not properly disciplined and little was done to stop the alleged conduct. Investigators then looked further. They alleged that patient records were not properly maintained, employees had not received formal HIPAA Privacy Rule training, and the doctor could not produce evidence of compliant privacy, breach-notification and safeguarding procedures. Id.
Snowball effect. One missing chart became a records-access complaint. The complaint became a federal investigation. The investigation expanded into questions about employee theft, record security, HIPAA policies, breach procedures and staff training. The price tag: $140,000, plus attorney fees.
To be fair—and we always should be—the resolution agreement expressly states that it is not an admission of liability by the doctor. Government allegations are not necessarily gospel. The doctor appealed OCR’s findings and the proposed penalty. Id. However, this fact pattern cannot be dismissed as merely an accusation. The doctor signed a resolution agreement that recites the factual background and covered conduct, agreed not to contest the payment obligation, and agreed to pay HHS $140,000 in one lump sum. Id.
The Lesson: A patient’s request for records is not a nuisance. It is a compliance event. If you cannot produce the record, you need to know why. If an employee took records, you need to investigate, document what happened, secure the remaining information and determine whether breach notification is required. And if the government asks for your HIPAA policies and training records, “we can’t find them” is not the answer. One unresolved problem leads to the next. Then the next. That is how a missing patient record snowballs into a $140,000 settlement.
A comprehensive approach to HIPAA - policies, training, maintaining, is an operational/compliance requirement. Need help with your program, training, or just to get started? Let us know. Tis the season for compliance, and, pretty soon, breach reporting... More to follow...
Snowball effect. One missing chart became a records-access complaint. The complaint became a federal investigation. The investigation expanded into questions about employee theft, record security, HIPAA policies, breach procedures and staff training. The price tag: $140,000, plus attorney fees.
To be fair—and we always should be—the resolution agreement expressly states that it is not an admission of liability by the doctor. Government allegations are not necessarily gospel. The doctor appealed OCR’s findings and the proposed penalty. Id. However, this fact pattern cannot be dismissed as merely an accusation. The doctor signed a resolution agreement that recites the factual background and covered conduct, agreed not to contest the payment obligation, and agreed to pay HHS $140,000 in one lump sum. Id.
The Lesson: A patient’s request for records is not a nuisance. It is a compliance event. If you cannot produce the record, you need to know why. If an employee took records, you need to investigate, document what happened, secure the remaining information and determine whether breach notification is required. And if the government asks for your HIPAA policies and training records, “we can’t find them” is not the answer. One unresolved problem leads to the next. Then the next. That is how a missing patient record snowballs into a $140,000 settlement.
A comprehensive approach to HIPAA - policies, training, maintaining, is an operational/compliance requirement. Need help with your program, training, or just to get started? Let us know. Tis the season for compliance, and, pretty soon, breach reporting... More to follow...
