Picture a small practice that has grown without ever deciding how to manage patient information. There is an Excel file with patient names, phone numbers and notes, kept on the secretary's computer. There is a second copy on a USB stick "just in case." Appointments are confirmed over WhatsApp, and sometimes a photo of a lab result or a prescription goes the same way. Nobody chose this. It grew, because each step was easy and free.
Then one day a phone is lost, someone leaves the practice, or a message goes to the wrong person, and the question comes up: who had access to what?
Why this setup is risky
The problem isn't Excel or WhatsApp as such. They are good tools for what they were built for. The problem is that they were not built to protect sensitive records, and the practice ends up relying on habit instead:
- No real access control. Unless it is protected, anyone who gets the file can open all of it. You can't give the receptionist access to appointments but not to clinical notes, because the file is one block.
- No audit trail. In a plain spreadsheet, nothing usually records who changed or deleted a row, or when. If a patient asks who looked at their information, there is no answer.
- Copies everywhere. Every time the file is emailed, saved to a USB stick or opened on a home computer, there is another copy that nobody tracks and nobody updates.
- Personal phones. Chats and photos sit on devices that belong to staff, not the practice. When the person leaves or changes phone, the practice's data leaves with them.
- Lost or stolen devices. A phone or laptop without a strong lock turns into an open drawer of patient information.
- Wrong-recipient mistakes. One tap sends a patient's details to the wrong contact or the wrong group. It often can't be fully taken back.
- No retention rules. Nobody decides how long things are kept or when they are deleted. They tend to stay indefinitely, which grows the risk with time.
- Version confusion. Two people edit two copies, and now there are two truths. A phone number is corrected in one and not in the other.
Each of these is small on a normal day. The risk is that they all depend on nothing going wrong.
What the law generally asks for
Health data is treated as sensitive in many places, and the rules are about protecting it, not about which program you use. Two examples I could check in the official text:
- Argentina's Ley 25.326 (personal data protection) counts information about health as sensitive data, and requires whoever holds a data file to adopt the technical and organisational measures needed to guarantee the security and confidentiality of the data, including avoiding unauthorised consultation or processing and detecting deviations.
- The US HIPAA Security Rule includes technical safeguards on access control and on audit controls, meaning mechanisms that record and examine activity in systems holding health information.
Both point in the same direction as the list above: control who can see what, and keep a record of what happened. What exactly applies to you depends on where you operate and what kind of practice you run, so ask a qualified professional to confirm it.
What to move first
You don't have to replace everything at once. Move in this order:
- The master list of patients. One place, with one version, instead of Excel files on several machines. This removes the copies problem and gives you a base to build on.
- Access by role. Reception sees appointments and contact details. Clinical staff see clinical notes. The owner sees reports. Each person signs in with their own account.
- Appointment reminders and confirmations. Move them out of personal chats into messages sent by the system, from the practice's own number or address. The patient still gets a message on their phone, but it leaves a record and doesn't depend on any one person's phone.
- Documents and results. Instead of photos going back and forth, patients receive a link to a secure page, and the document stays attached to their record.
- The history. Start recording who created, viewed and changed each record, so you can answer the question that began this article.
How a proper system replaces the old habits
A web application built for the practice does what the spreadsheet and the chat did, but with the protections around it. Each person has their own login and permissions. Every change is logged. Data is stored in one place, with backups, instead of scattered across devices. Messages to patients go out through the system. And if someone leaves, you remove their access in one step, without hunting for the file on their laptop.
It also keeps what people liked about Excel: it is fast to search, easy to filter and simple to export when someone needs a list.
A practical first step
Make an honest inventory. Where does patient information live today: which files, which phones, which chats? Who has a copy? Who could open it right now? Write it on one page. The gaps you find are the first things to move, and that page is the best brief you can hand to a developer.