Linking photos, X-rays, and files to patient records

An advisor forwards an evening intraoral photo to the clinician but does not add it to the record. When the patient calls the next morning, no screen shows which conversation contains the image, so the patient is directed to take another photo. The problem is larger than a file remaining on a phone. Zoho separates its location from the basis of missing-image control.

During a shift handover, the image remains on one person's phone. The incoming employee sees the patient's name and number but cannot tell whether the panoramic X-ray arrived. Instead of placing the case in the clinician's queue, they call the absent advisor. A sound setup keeps the image relationship while tracking absence through a status the team can read together.

An evaluation image is a decision input, not merely a stored file

An intraoral photo, panoramic X-ray, or assessment document is more than an object to retain. It informs the clinician's review, the advisor's understanding of pending work, and the status of the answer owed to the patient. Finding the file is insufficient unless its relationship to the correct record and the need for evaluation also remain clear to the team.

When an image remains in a messaging conversation, its context depends on personal memory. The patient record carries the question while the assessment input stays elsewhere, leaving the next employee unable to identify what is awaited. The setup fixes where the clinical answer belongs and treats the file and evaluation status as connected elements that do not replace each other.

Attachment lists and named upload fields serve different operational purposes

Zoho supports File Upload and Image Upload fields for named images. These fields are completed manually; a rule does not fill them by itself. Each file is limited to 20 MB and scanned before acceptance. Per-module limits are 2 fields in Standard, 5 in Professional, 10 in Enterprise, and 15 in Ultimate. Free provides no custom fields for this structure.

The attachments related list is separate and receives uploads from record detail. It has no field name, so meaning remains in the filename. The owner alone sees attachments in Documents and WorkDrive. Users with whom the record is shared can see them on its detail page, but not in Documents. WorkDrive cannot add, edit, or delete them. Ownership changes move their folder.

Questions the attachment list can answer, and those it cannot answer

Advanced filters can test whether related items such as notes or attachments exist. Records without attachments can therefore be filtered, but the filter cannot identify whether an attachment is a panoramic X-ray, intraoral photo, or another file. A saved advanced filter is personal and is not shared with the team. A shared screen requires a custom view with sharing selected.

Adding one file separately to five records consumes storage five times, so a 10 MB file uses 50 MB. A file uploaded once to Documents and linked to several records counts once. WorkDrive Free Essentials provides 5 GB per organization. Per-user capacity is 512 MB in Standard and Professional and 1 GB in Enterprise and Ultimate. Upload fields, note attachments, and templates still consume CRM file storage.

Track missing clinical images through a separate shared status field

A separate Image status picklist can support missing-image control. Values can describe no image, a missing image, ready for evaluation, an insufficient image, or another request. A custom view fills with records matching that field. Because using File Upload fields in custom-view criteria or reports remains unverified, the control does not depend directly on the file field or an unknown filtering behavior.

A custom view is a worklist, not an automation engine. Zoho shows matching records, but the view itself does not notify anyone, create tasks, or assign owners. Automation does not move a record into the view; the record appears because its field value matches the criteria. Bulk actions are separate tools and wait for a user's click before they run from the list.

The clinician queue follows the verified field and assignment design

When Image status becomes ready for evaluation, the next action needs separate design. A workflow task goes to the fixed user selected in the rule, or to the record owner when Assigned To is blank. Distribution by clinician requires separate rules, one Assign Owner action using the user field, or a custom function that creates the task. Each rule permits one Assign Owner action.

Custom functions require Enterprise or above. Workflow criteria support 5 conditions in Standard and Professional and 10 in Enterprise and Ultimate. If a task owner is inactive, assignment falls back to the record owner and then, if needed, the super administrator. Workflows neither make fields mandatory nor stop records. Automatic image-arrival timestamps remain unverified, so the setup cannot create that ordering basis itself.

Enable health-data marking at the start of the CRM implementation

Under Setup > Security Control > Compliance Settings > HIPAA Compliance, up to 10 modules and 25 health-data fields per module can be selected. File Upload and Image Upload are supported. Separate switches restrict API access, exports, transfers to Zoho applications, and third parties. Supported modules are Leads, Contacts, Vendors, and custom modules. Management requires the Manage Compliance Settings profile permission.

This product setting does not replace assessment of Turkey's health-data regime, notice duties, or explicit consent. That assessment belongs to the institution's legal team and rests on legislation itself. Disabling compliance removes all health-data markings; marked fields appear under Data Privacy > Personal Data > Health. GDPR marking uses Normal and Sensitive grades and permits 30 fields per module. Edition thresholds require pre-proposal verification.

Separate profile-based field permissions from access-based record visibility rules

Set Field Permission hides a field or makes it read-only by profile across all module layouts. Field-level permission requires Professional or above. Record visibility separately depends on ownership, role hierarchy, sharing rules, territory management, and user-field access. Territory management requires Enterprise. Profile permissions treat viewing, creating, editing, and deleting attachments as separate items. Hiding a field and controlling record access are therefore different operations.

Changing a departing employee's role does not alone remove access to records they own. Disable the account and transfer open records. The Zoho audit log records additions, updates, deletions, bulk actions, imports, exports, conversions, restorations, and merges, but not who viewed a record. It is not an optional switch. Conflicting retention references prevent stating one duration; long-term retention needs can be evaluated through export.

Attachment destination during lead conversion is one irreversible operational choice

Standard is the minimum because Free lacks the custom field needed for Image status. Standard allows 2 named file fields and 5 workflow conditions. Professional allows 5 fields and adds field-level permission. Clinician-based task creation through a custom function and territory management require Enterprise. Enterprise allows 10 fields, Ultimate 15, and both allow 10 workflow conditions. Unknown compliance edition thresholds require pre-proposal verification.

During lead conversion, choose whether attachments move to the Contact, Account, or Deal. Without a Deal, only Contact and Account remain. Mass conversion requires the same destination choice, while tag transfer is selected separately. An attachment is absent from unselected records, and the decision cannot be reversed afterward. A wrong destination can leave the evaluation input outside the record where the team seeks the patient context.

Zoho CRM for clinics