Skip to main content

Keep discharge notes and client messages linked to the right record automatically [Early Access]

How discharge notes, messages, and files connect to a patient's medical record without extra steps.


What is record and communication linking?

Record and communication linking connects the discharge notes and messages you send to a client with the medical record they belong to. Send discharges, or log a message while a record is open, and it links itself. No extra step to remember mid-consult. Once linked, you can read the full message right on the record instead of leaving it to go find it.


How this helps your daily work

Vets & Vet Techs. A discharge note you send from a medical record (SOAP) logs and links itself automatically. Linked messages preview right on the SOAP, so you can check what was already said without leaving the record.


Front Desk / CSR. Logging a communication while a record is open links it automatically, no separate step afterward. A toggle in the communication log lets you hide automated reminders so real conversations are easier to spot.


Practice Managers. A record share now includes an auto-linked discharge note by default, one less box for the team to remember. Reviewing how a case was communicated takes one look at the record instead of a search through the log.



Where to find it

You don't need to turn anything on. Discharge notes sent from a medical record (SOAP) link automatically; see Generate Discharge Notes. To link a communication yourself, use the Record field while creating it or the Health Card; see Send a Direct Message to a Client. Every communication, linked or not, is in the Communication Log.

How automatic linking works

  1. Send a discharge note from a medical record (SOAP), or log a communication while a record is open, through Digitail.

  2. Digitail logs it as a new entry in the client's communication log.

  3. Digitail links it back to the record it belongs to.

No manual action is needed for either case. Discharge-note auto-linking only covers notes sent through the platform; a printed or externally generated note isn't logged automatically.

Other things you can do

Link a record from inside the Communications module

Add a communication and pick the record it belongs to right there, instead of linking it afterward from the Health Card.

Preview a linked message without leaving the record

Linked messages show as a short preview (subject, date, snippet) on the SOAP or Timeline. Click to expand to read the whole message and any attachments in a window over the record. Multiple linked messages stack most recent first.

Records shared with a discharge note included by default

When a record includes discharges or communications, sharing it includes those automatically. Using the 'Record content settings' checkboxes allows you to uncheck if needed.

Hide automated reminders in the communication log

A toggle to show only direct communications is available in the Communications Timeline, so scanning for a real conversation doesn't mean scrolling past reminders. This only changes what's displayed; reminders still send and log as usual.

Tips & best practices

  • Discharge notes only auto-link when sent through Digitail; printing or sending outside the platform won't log them.

  • Auto-linking applies going forward; older communications keep their current link status.

  • The linked-message preview is read-only; edit a communication from Client Communications, not from inside a record.

Frequently Asked Questions (FAQs)

Will this change how I currently link a communication manually?

No. You can still link from the Health Card, or now from the communication itself when you create it, see Send a Direct Message to a Client.

Do I need to turn discharge note auto-linking on?

No. It works automatically for notes sent through Digitail.

Will my older messages get linked automatically?

No. Auto-linking applies to new communications and discharge notes going forward.

Can I edit a communication from inside the linked-message preview?

No. The preview is read-only. Edit it from Client Communications instead.

Did this answer your question?