Skip to content
Help centre

Sending a copy to another profession

A copy is sent once, on the patient's recorded consent: the other clinician holds the patient's details and the signed entries you chose, read-only, and nothing written afterwards reaches them.

To let a clinician of another profession read a patient's record, send them a copy from the patient's Who can see this record, on your computer. Only the clinician who treats the patient, or a practice owner, can send one.

The patient's consent to sharing comes first, recorded in the app — given on paper and signed, or electronically. Every copy is logged against it: what was sent, to whom, when.

You choose which signed entries go; a draft can still change, so it never goes. A copy always carries the patient's identity details and never the money side. The receiver gets the entries sealed for them, read-only, labelled with your practice's name and the date they were sent.

A copy is sent once. Nothing written afterwards reaches the receiver unless you send another copy. There is no live link, no end date and nothing to withdraw on the sync server: what was sent was sent, as with paper. A withdrawal of the patient's consent, or a discharge, only refuses the next copy, on your computer; a copy already sent stays with its receiver.

A copy goes to a clinician outside your practice — a practice owner or an associate elsewhere. A colleague of your own practice is given a patient by a change of treating clinician or a cover, never a copy.

On the receiver's side the patient is labelled A copy sent to you. The copy is read-only history; once they have a practice of their own it is placed there as history, and they add their own entries after it. They keep it under their own retention period, and their Delete removes their copy alone. Copies sent, under Who can see this record, lists each copy and the day the receiver deleted it or it lapsed.

Related

  • Who sees whatA patient file has three layers — identity, money and clinical — and your hat in the practice decides which reach you; a grant adds patients, never layers.
  • Handing over a patientA patient moves to a clinician at another practice with their history: the earlier entries are read-only for the receiver, who adds their own after them.
  • Changing the treating clinicianInside the practice a patient passes to a colleague by naming them the treating clinician: they receive every key of the file and continue it, with the earlier entries underneath.
  • Keepers and retentionEvery copy of a record has one keeper, who types their own number of years; when a record passes it, the keeper chooses Keep or Delete, and the app never deletes on its own.
  • Consent and data requestsWhat each patient has agreed to, purpose by purpose; what needs consent; and the requests patients make about their own records.
  • The lapse ruleThe one deletion the sync server does by itself: a person's own copies, a set time after they stop holding a seat.

Still stuck? support@sideclick.io reaches the people who build the product.

Try SideClick free for 30 days

Full capability, no card required. Your data is sealed on our server and we cannot read it.