Does a shared summary replace the full clinical record?

No. It is a derived document written for a specific reader. The full record stays with the practitioner who created it, and the summary should say that a fuller record exists and how it can be requested.

How long should records be kept?

It depends on your jurisdiction and sometimes on the patient's age, with longer periods often applied to records involving minors. Confirm the requirement with your professional body or regulator instead of adopting a figure from another country.

Can records be shared by ordinary email?

Only if the channel meets the confidentiality requirements that apply to you. Many practices use encrypted email or a secure portal, and note in the file which route was used and on what date.

What if the other practitioner does not reply?

Record the attempt with the date, time and channel, escalate to the named deputy, and note the escalation in the patient's file. An unanswered message is worth documenting, because it shows what was known and when.

Documentation Standards for Shared Patient Care: Records and Communication Protocols

What has to be in the record before anyone else can use it?

A record is usable by another clinician when it answers four questions without guesswork: who the patient is, why they are being seen, what they are already taking or receiving, and what has changed since the previous entry. Everything else is supporting detail, and the supporting detail should be arranged so it can be skimmed.

Readers arrive with different needs. A general practitioner scanning a summary is usually checking for interactions, duplicated treatment or a shift in the patient's condition. A specialist reading the same page wants chronology — when a symptom began, what was tried, what happened next. A record that only makes sense to its author fails both of them, and the cost usually shows up later as a phone call that could have been avoided.

Keep observation and interpretation visibly separate. 'Reports waking at three in the morning for six weeks' is an observation. 'Sleep disturbance consistent with the indicated picture' is an interpretation and should be labelled as one. Blended together, the next reader cannot tell which parts are facts to rely on and which are a working hypothesis likely to change at the next appointment.

Patient identifiers, date of birth, and a contact number that is current.
Date of the entry, plus the name and role of the person writing it.
Reason for the consultation, in the patient's own words where possible.
Current conventional diagnoses and all medicines, with dose and prescriber.
Relevant history, including other therapies being used now or previously.
Examination findings, if any were taken, with the method noted.
Working assessment, labelled as such, plus the plan and the review date.
Anything declined or stopped, and the reason it was declined or stopped.

How do you write up a consultation so a non-homeopath can follow it?

Write in full sentences, spell out every abbreviation the first time it appears, and describe the prescription in words rather than symbols. Assume the next reader has no training in this approach and no access to your shorthand.

Homeopathic notes are often built for speed. Remedy names get shortened, strength is written in a notation that only carries meaning inside the tradition, and follow-up impressions are compressed into a phrase. That is efficient within one practice and opaque outside it. The fix is not longer notes but more explicit ones: name the substance, say how it is supplied, and state plainly what the patient is expected to do with it.

Record the prescription as a pharmacist would need it. That means the substance name as printed on the dispensed product, the form (tablet, granule, liquid), the strength as labelled by the manufacturer or pharmacy, the dose and frequency, the start date, and who supplied it. Strength notation varies between makers and countries, so write it out rather than assuming it is universally understood.

What does a working communication protocol between practitioners look like?

A protocol is a short written agreement naming who contacts whom, through which channel, about what, and how quickly. It does not need to be long. It needs to be specific enough that two practitioners who have never met can follow it without asking a colleague what the arrangement was.

Vague arrangements fail exactly when they matter, which is usually the moment a patient's situation changes and neither practitioner is certain whether the other knows. Naming a single contact person on each side, plus a deputy for absences, removes most of that ambiguity before it becomes a problem.

The protocol itself is a document. Keep a dated copy, review it when staff change, and note in the patient's file when it was invoked. A protocol nobody can produce on request is not doing any work.

Question the protocol must answer	What a workable answer looks like
Who initiates contact?	A named clinician or administrator on each side, with a deputy for cover.
Through which channel?	One agreed route for routine matters and one for urgent ones, with the address or number written down.
What triggers contact?	A defined short list: new diagnosis, new medicine, change in condition, decision to stop treatment, hospital admission.
What response time is expected?	Stated in working days, with a separate and shorter figure for urgent matters.
What is recorded afterwards?	Date, who spoke to whom, what was decided, and where that note is kept.

Consent should name the recipients or the category of recipients, describe what will be shared, state how long the permission lasts, and record how the patient can withdraw it. A signature on a form saying 'share with other practitioners' is far weaker than one naming the cardiologist and the general practitioner by role.

Many jurisdictions give extra protection to particular categories of information, including mental health, reproductive health, substance use, genetic data and records about minors. The practical consequence is that a blanket consent may not cover everything in the file. The safer default is to send a summary of what the other clinician needs rather than a copy of the whole record.

Record the consent itself: who signed, on what date, and which version of the form. Requirements differ between countries and between professional regulators, so confirm the rule that applies to your practice with your registering body or a lawyer rather than relying on a template borrowed from elsewhere.

How do you record patient-reported change so it means something to the next reader?

Use a named instrument or a fixed set of questions, record the score and the date, and note who collected it. 'Doing much better' cannot be compared with anything. A score on a defined scale, taken at defined intervals, can be plotted, questioned and repeated by someone else.

Baseline matters more than follow-up. If the first measurement is taken after treatment has already started, there is nothing to compare against. Record the starting point before the first prescription, then note confounders alongside each later score: other treatments started or stopped, life events, seasonal change, and anything else the patient changed at the same time.

Keep what the patient reports separate from what the clinician concludes. A single patient's trajectory describes that patient and nothing wider. Writing it as though it demonstrated something about a treatment misleads the next reader and weakens the record's value as a clinical document.

What goes wrong when records move between different systems?

Structured summaries travel better than file dumps. Send a short document with headed sections, plain dates and no unexplained codes, keep the full working record in your own system, and state on the summary that a fuller record exists and how to request it.

Losses happen at the joins. Strength notation gets read as free text and dropped. Dates in different orders are misread. Units are assumed rather than stated. Attachments fail to open. Medication lists merge into a single column with duplicates and no indication of who prescribes what. Check what actually arrived rather than assuming the transfer worked, and keep a dated copy of what you sent.

Medication reconciliation deserves its own pass. The shared record should list everything the patient takes, including supplements and over-the-counter items, with the person who prescribes or recommends each one. An incomplete list here is the most likely source of real harm when two clinicians are both treating the same person.

Who holds the record, and what happens when it needs correcting?

The practitioner or service that made an entry holds that record. When two practices are involved, neither holds the complete picture, which is precisely why a shared summary has to exist and be kept current. Patients generally have rights of access and correction under local law, and requests should be logged with the date they were received.

Never delete an entry to fix it. Add an amendment that states the date, the author and the reason for the change, and leave the original visible. Retention periods vary by jurisdiction and are often longer for records involving minors; confirm the figure that applies to you rather than assuming a round number.

Review the documentation standard itself on a schedule — annually, and after any episode where information failed to reach the right person. The useful questions are narrow: did the summary arrive, was it read, and was anything in it ambiguous? Answers to those three tend to improve the next version more than a general rewrite.