Session Notes vs the Client Profile: What Belongs Where
Educational, legal and safety note: This guide describes professional documentation structure. It is not medical, legal or regulatory advice and does not establish clinical efficacy. It does not replace diagnosis, emergency assessment, referral, consent, applicable record-keeping rules or practitioner judgment. Workflow software does not diagnose, prescribe automatically or replace professional decisions.
Quick answer: what belongs in the profile, and what belongs in the note?
Keep standing facts in the client profile and the visit in a dated session note. The profile answers who this person is, how to reach them, what consents and current medicines apply, and which relatively stable characteristics you still treat as current. The note answers what happened in this encounter: the person’s words, your observations, clarifications, safety actions and the working decision of that day.
The two layers must be connected and distinguishable. If a standing fact changes, write the change in the session and then update the profile with that session as provenance. Do not paste the whole case into a profile summary, and do not leave identity or consent only inside one visit file.
Key takeaways
- Profile = facts that must remain true between visits.
- Note = the visit layer; it stays with the session.
- Analysis is part of the visit record, not a trait on the profile.
- Unknown is better than a prompted or software-completed standing fact.
- Correct a current contact or medicine list without rewriting yesterday’s narrative.
- Label opinions as opinions; keep the source of each important standing field.
This is a field split, not a second interview guide
The case-taking and follow-up documentation guide covers how to take the interview, preserve the person’s language and compare later visits with a baseline. The practice-management workflow covers the whole operating path from enquiry to closure. This article answers a narrower question: which fields live on the standing profile, and which fields must remain attached to a session?
Hahnemann’s Organon §§83–90 asks the practitioner to write the person’s expressions accurately, add later clarifications on the same line, and record the physician’s own observations separately. That is a documentation sequence, not a software specification. It still explains why a later summary that “improves” the wording is a loss: the original picture is what later comparison needs.
Healthcare record models make a similar cut. In HL7 FHIR, a Patient resource holds “who” information for administrative and logistic use; an Encounter records an interaction between a person and a provider. CARE’s published-case checklist likewise separates patient information from the timeline of an episode. Those standards are not templates for a private homeopathic file. They show why identity and visit narrative are different objects.
What each layer is for
| Layer | Holds | Must not replace |
|---|---|---|
| Client profile | Identity, contacts, language/access needs, consent status, current medicines, relatively stable characteristics with the session that supports them | A rolling rewrite of the case |
| Dated session | Verbatim phrases, observations, chronology of this visit, concurrent care mentioned today, safety/referral actions | The standing identity record |
| Analysis attached to the session | Characteristic picture used today, rubric set, materia medica checks, uncertainties, working decision | A profile trait or an automatic prescription |
| Operational status | Current state, owner, next action, due date | Either the profile or the source note |
The case-analysis documentation guide describes the analysis note. The analysis still belongs to a session. Promoting “tends to be anxious” from one visit into a permanent profile label, without provenance, is the failure this guide is written to prevent.
The SPLIT model
Use SPLIT as a practical field map. It is a working model, not a school, legal standard or proof of effect.
- S — Standing identity
- P — Persistent picture
- L — Live session
- I — Interpretation of this visit
- T — Transfer with provenance
1. Standing identity
Store here the facts you need before any particular visit starts:
- legal name and the name the person uses;
- identifiers the practice actually uses;
- contacts and preferred channel, with limits;
- language, interpreter or accessibility needs;
- who may be contacted, and who may not;
- consent and information-notice status, with dates;
- current medicines and other concurrent care that must be visible for safe coordination;
- emergency or out-of-scope flags that the practice has actually documented.
These fields exist so the next session, a locum or an authorized colleague can act without rereading every note. They are not a biography. GDPR Article 5 still asks for purpose limitation, data minimisation and accuracy: collect what the defined purpose needs, keep it correct, and do not treat a historical address as if it were current.
If a contact detail changes, update the profile and record in the session that the change was reported. The old address can remain accurate as history. The UK ICO’s accuracy guidance makes that distinction: a record that someone once lived in a place can stay true after they move; a record that they currently live there cannot.
2. Persistent picture
Some homeopathic information is used across visits: thermal preference, usual sleep pattern, long-standing fears, food desires or aversions, typical energy, and other characteristics that the practitioner still treats as current. That material can live on the profile only if it remains linked to evidence.
A useful profile line looks like this:
| Profile field | Current value | Status | Provenance |
|---|---|---|---|
| Thermal preference | “I am cold in the office even when others are not.” | Standing; last confirmed 12 Mar | Session 12 Mar, client words |
| Usual waking | Wakes near 03:00 several nights weekly | Standing; last confirmed 12 Mar | Session 12 Mar |
| Work strain | Role change this winter | Episode, not standing | Leave in the session; do not promote |
Do not invent a second, cleaner wording for the profile. If the person said “cold in the office even when others are not,” that phrase is more useful than “chilly”. If the evidence is thin, leave the field empty or mark it unknown.
3. Live session
The session note is contemporaneous visit documentation. CQC Regulation 17, which applies to regulated providers in England and is not a universal rule for homeopaths, still states the transferable professional expectation: an accurate, complete, contemporaneous record of care and of decisions. NHS England’s guidance on high-quality records adds a practical cut: demographics, administration and the narrative of a consultation are different kinds of data, and amendments should leave an audit trail.
Write the session so another trained reader can see:
- date, duration, setting and who was present;
- the person’s opening account in their language;
- observations made in this encounter;
- clarifications that belong to this visit;
- concurrent care, investigations or life events mentioned today;
- safety, advice or referral actions taken today;
- what remains unknown.
Keep the note attached to the session object. If the session is moved, exported or reviewed, the note goes with it. A profile field is a pointer, not a vault for the visit.
4. Interpretation of this visit
Rubric choices, materia medica checks and the working decision are part of today’s work. They belong with the session, next to the source phrases they rest on. They do not belong as unlabeled traits on the profile.
“Possible time modality; not yet established” is an interpretation. “I wake at 3 a.m. with my thoughts racing” is a source phrase. Mixing them in a profile field called “constitution” makes later follow-up dishonest: the record no longer shows what was known on the day.
5. Transfer with provenance
A profile field may change only when all four conditions hold:
- the new value is a standing fact, not a visit-only observation;
- a dated session supports it;
- the previous value remains reconstructable;
- a practitioner, not a model, accepted the change.
If any condition fails, leave the material in the session. “Unknown” on the profile is more accurate than a confident guess.
Field map: where does this go?
| Information | Profile | Session note | Transfer? |
|---|---|---|---|
| Name, contacts, preferred channel | Yes | Note only if changed today | Update profile; keep the change event in the session |
| Consent / information notice | Current status and date | The conversation that produced the status | Status on profile; conversation in the session |
| Current medicines | Current list | Starts, stops and reported effects today | List on profile; events in the session |
| Opening complaint in the person’s words | No | Yes | Never replace the note with a profile summary |
| Practitioner observation this visit | No | Yes | Promote only if it becomes a confirmed standing characteristic |
| Relatively stable characteristic | Yes, with provenance | Original statement stays in the session | Yes, after review |
| Rubric set and analysis | Link, if useful | Yes | No: analysis is not a trait |
| Working decision and plan | Next review date may be operational | Yes | Plan history stays dated |
| AI-suggested profile update | Only after accept/edit/reject | Keep the suggestion and the decision | No silent write |
A compact documentation example
This is a style example, not a case, diagnosis or prescription.
Profile after review
- Contact: mobile, evenings only.
- Current medicines: as reported 12 Mar; no change recorded since.
- Thermal: “cold in the office even when others are not” — standing, session 12 Mar.
- Waking pattern: several nights weekly near 03:00 — standing, session 12 Mar.
Session 12 Mar (visit layer)
- Client words: “I wake at 3 a.m. with my thoughts racing.”
- Observation: speaks quickly; pauses when describing work.
- Clarification: began after a role change; about four nights weekly.
- Interpretation: possible time modality; relevance not yet established.
- Safety: no urgent pathway documented this visit.
- Working decision: gather missing occupational timing at follow-up; no profile change beyond the two standing lines above.
Session 9 Apr
- Client words: “The three o’clock waking is less often; the racing thoughts still come if I open email after ten.”
- Do not overwrite 12 Mar.
- Do not change the thermal profile line unless today’s evidence actually revises it.
- If the waking pattern is now treated as changed, update the profile with provenance “session 9 Apr” and keep 12 Mar readable.
The later visit can correct a current standing field. It must not pretend the first visit already contained the later wording.
Failure modes
- The rolling summary. A profile “case overview” is rewritten after every visit until the first picture disappears. Follow-up then compares the person with last week’s prose, not with a dated baseline.
- Identity trapped in visit one. Name, contacts or consent live only in the first PDF. A locum cannot start the next session safely.
- Mood promoted to constitution. One visit’s anxiety, anger or exhaustion becomes a standing label without provenance.
- Analysis stored as a trait. A rubric or a working hypothesis is copied onto the profile as if it were a fact about the person.
- Silent AI merge. A model extracts “facts” from notes and writes them into the profile. Source, uncertainty and rejection disappear.
- Twin records that drift. The same medicine list exists in the profile and in the latest note, then only one is updated.
ICO guidance on accuracy is useful here even outside the UK: a historical clinical opinion can remain an accurate record of what was thought at the time, provided it is labeled as an opinion and not silently replaced by later knowledge. The same logic applies to session notes. Accuracy of the current profile is a different job from preserving the historical visit.
What software should make easy
Use this as a test, not as a vendor claim.
| Test | Pass | Fail |
|---|---|---|
| Open the profile without opening a session | Standing facts are visible and dated | You only see the last note |
| Open a session | The visit narrative is complete without copying identity into the body | The note is a dump of the whole file |
| Change a phone number | Profile updates; the session records that it changed | Old number vanishes with no trace, or lives in six places |
| Propose a profile update from a note | Suggestion waits for accept, edit or reject | The field changes as soon as text is saved |
| Correct a standing fact | Current value changes; previous value and session remain readable | Yesterday’s note is rewritten |
| Export or hand over | Profile and dated sessions stay linked | Notes detach, or a single blob is called “the case” |
| AI draft | Source phrases remain; generated lines are marked | Generated wording replaces the person’s language |
The digital records and privacy guide covers access, retention, export and processor due diligence. Field separation does not replace that governance layer.
Checklist
Before the session
- Identity and contacts are on the profile, not only in an old email
- Consent or information-notice status has a date
- Current medicines are visible without opening every note
- Standing characteristics show provenance or are marked unknown
During and after the session
- The person’s words sit in the session, with quotation marks where wording matters
- Observations and interpretations are on separate lines
- Safety or referral actions taken today are in the session
- Analysis and rubric work are attached to this session
- Profile updates, if any, point back to this session
- Rejected AI suggestions remain visible as rejected, or are omitted rather than merged
- The previous session is still readable in its original wording
Frequently asked questions
Is the profile a shorter version of the case?
No. A summary that replaces the source notes is a different, weaker document. The profile is a standing-fact layer. The case lives in the dated sessions plus the analysis attached to them.
Should every consultation rewrite the profile?
No. Most visits should add a session and leave the profile alone. Rewrite a profile field when a standing fact has actually changed or was wrong, and keep the evidence.
Where do follow-up comparisons belong?
In the follow-up session, against the dated baseline. Do not update the first session so that it appears to have anticipated later change. The case-taking guide covers that comparison method; this guide only keeps the layers from collapsing.
Can intake forms fill the profile automatically?
They can pre-fill identity, contacts and questions the person already answered. They cannot become the interview, and unchecked boxes should not become standing characteristics. Review before anything becomes a profile fact.
What if the person disagrees with a profile line?
Treat it as an accuracy challenge. Check whether the line is a current fact, a historical fact or an opinion. Correct what is wrong, label opinions, and keep a dated note of the challenge. Do not erase a session that accurately recorded what was said at the time unless a legal or professional rule requires it.
Does this replace privacy or consent documentation?
No. Consent conversations and privacy notices still need their own process. This article only says: current status can live on the profile; the conversation that produced it belongs in a dated record.
Keep facts standing and visits dated
A useful homeopathic file is not one long document that gets tidier over time. It is a standing profile plus a chain of sessions. The profile makes the next visit possible. The notes make the next comparison possible. If software helps, it should keep those jobs separate and leave acceptance of standing facts with the practitioner.
Sources and further reading
- Samuel Hahnemann, Organon of Medicine, §§83–92 — writing the person’s expressions, adding clarifications, and recording the practitioner’s observations separately
- HL7 FHIR, Patient — “who” demographic and administrative information, used here as an analogy for a standing identity layer, not as a required implementation
- HL7 FHIR, Encounter — an interaction between a person and a provider; used here as an analogy for the visit layer
- CARE Case Report Guidelines and checklist — patient information, timeline and follow-up as distinct reporting elements; a publication standard, not a private-file template
- Teut M. et al. (2022), Case Reporting in Homeopathy—An Overview of Guidelines and Scientific Tools — CARE, HOM-CASE and distinct documentation areas
- European Union, General Data Protection Regulation (EU) 2016/679, Article 5 — purpose limitation, data minimisation and accuracy
- UK Information Commissioner’s Office, Principle (d): Accuracy — current versus historical records, and opinions labeled as opinions
- Care Quality Commission, Regulation 17: Good governance — contemporaneous records for regulated providers in England, not a universal rule for homeopaths
- NHS England, High quality patient records — demographics, consultation narrative and amendments with an audit trail, as transferable record-quality practice rather than a homeopathy standard
This HomeoStudio knowledge-base article supports professional education and documentation quality. It makes no claim about the clinical efficacy of homeopathy and does not encourage self-diagnosis, self-prescribing or changes to prescribed care.