Your patient's X-ray is real. Finding it again is the hard part.

A patient calls asking for a copy of the panoramic X-ray from two years ago, for a specialist referral. The front desk knows it exists. What follows is usually a hunt: the imaging software's own folder on the X-ray computer, a shared drive that three different assistants have reorganized since, an old email thread to a lab, maybe a phone that left the practice with the hygienist who took it. The X-ray is real. Finding it again is the actual problem.

This is not a rare afternoon. Most small clinics never sat down and decided where clinical images live. It happened by accident, one workflow at a time. The panoramic and periapical films save wherever the sensor's software defaults to. Intraoral camera shots get pulled onto a laptop desktop before an appointment and forgotten. Before-and-after photos for a cosmetic case get taken on someone's phone because it was faster than finding the intraoral camera, then sent to whoever needed them that day. Every one of those images is real, clinically relevant, and completely disconnected from the patient chart that is supposed to be the record of what happened.

The fix people reach for first is a shared cloud folder: Dropbox, Google Drive, OneDrive. It solves the "which computer is it on" problem, but it creates two new ones. First, whoever owns that account now controls the only copy of every patient's imaging, personally, on a consumer account that has nothing to do with the clinic's legal identity, protected by whatever password that one person is using for a dozen other things too. When that assistant leaves, the folder access question becomes a real, awkward conversation. Second, a folder is not a record. A patient's X-ray sitting in a dated subfolder is not linked to their chart, their treatment plan, or the consent form for the procedure it documents. Someone still has to remember the patient's name, guess which subfolder, and hope nobody renamed it.

The actual requirement is narrower than cloud versus local, even though that is the argument most software vendors have with each other. What a clinic needs is for the image to be attached to the same record as everything else about that patient, findable by searching the patient rather than the folder structure, and to have exactly one authoritative copy rather than five approximate ones scattered across phones and drives. Whether that copy sits on a server in another country or on the machine in the front office is a second, separate decision, and reasonable practices land on different answers for it, usually driven by data residency rules and how much they trust someone else's infrastructure.

This is one of the more mechanical problems the Documents module in HM Praxis exists to close: an X-ray or clinical photo attaches directly to the patient's record, on the clinic's own machine, indexed by patient rather than by folder. There is no separate photo app to remember to open, no personal Drive account holding the only copy, and the data stays local instead of routing through a third party's servers by default. It does not solve every step of a practice's imaging workflow (the sensor software still has its own export step), but it closes the part that actually costs time: the record and the image living in the same place, so "where is it" stops being a question anyone has to ask.


Learn more