Clinical care · VERSION 3dfb7c9f

Doctor: create and verify a patient-only Notes discussion

Open Notes from Patient Details, practise cancelling an empty title, then create one fictional discussion and send one message. Check its author, time and saved content after a normal reload. This is a patient-level discussion, separate from encounter Notes.

Doctor

Recorded product version 3dfb7c9f

These lessons apply to their recorded version and observed role. Check local permissions and configuration. A qualified lesson does not establish complete product or facility coverage.

Version, screenshot scope and limits

Full product version: 3dfb7c9f519fb5b4cd4452439f3c12346bf58319

Exact committed 3dfb7c9f source/tree, ordinary existing Doctor in one explicitly fictional Polyclinic Inpatient encounter. All 12 original raw form schemas/subjects and separate BP form matched under ordinary Doctor/Nurse reads before native UI. One four-answer ordinary response with optional note saved once, native single PDF saved/viewed, neutral warning Cancel proved unchanged, then same new source corrected once. Existing clinical and Admin estates preserved; no new form, code, grants or external transport. Genuine 25-photo public subset from 29 retained original frames; exclusions and pixel/geometry qualifications are private. Ordinary existing Pharmacist companion adds fully visible services pagination, prescription medicine filters, completed-order history and saved prescription PDF. Existing scoped stock and financial records verified unchanged. No new dispensing or financial actions are qualified by these lessons. Ordinary existing Billing Officer companion adds account/status/search, saved Balanced invoice and actuallocalinvoicePDF.273scopedstoredrows verifiedunchanged;4nestedrelatedPharmacistlast_login responsevalues separatelyqualified. Nocharge/invoice/payment/tax/electronicfiling businessaction is claimed. Exact committed3dfb source/tree, ordinary existing Doctor on one separate explicitly fictional Polyclinic Ambulatory case. Normal API patient/encounter prerequisites are separated from native teaching. Four installed leaves retain schema/provenance. One actual invalid-Time attempt refused database writes; one recovered mixed submission saved two Conditions/two structured logs/one ordinary source, genuine one-page PDF saved/viewed, neutral correction Cancel verified, then only that new ordinary source corrected once. Scoped ordinary Doctor/Nurse readbacks preserve all measured prior clinical records in the two retained cases; Admin rows are outside those clinical collection comparisons; no grants, source, form, term or runtime changes. Forty-three actual wide originals retained for public teaching from46 unchanged raw frames. Exact committed 3dfb source/tree, existing ordinary Nurse on one already-established clearly fictional Polyclinic Ambulatory case. IPD is transparently the installed title. One unchanged-form Cancel; explicit No/0/None with three optional notes; exactly one ordinary source saved; actual one-page local PDF saved/viewed; neutral warning Cancel and then source-only Error verified after reload. Existing target and older-main clinical collections compare exactly in 24 scoped comparisons per stage under ordinary Nurse/Doctor. This does not claim global Admin-table verification, all roles/facilities or clinical respiratory-policy coverage. No grants, config, terminology, source or runtime changes. Twenty-six genuine public originals from27 retained raw frames; one incomplete-footer attempt excluded. Exact committed 3dfb source/tree, existing ordinary Nurse on one previously established fictional Polyclinic Ambulatory case. One unchanged-form Cancel; fictional multiline Text, actual temporary one-unit relative-date examples, restored absolute Date and two optional field notes; exactly one ordinary response saved at 11:04 AM; actual one-page local PDF saved and viewed; neutral warning Cancel then source-only Error verified after reload. Existing target and older-main clinical collections compare exactly in 24 scoped comparisons per stage under ordinary Nurse and Doctor, with the four older target response/log records additionally compared by UUID. No claim of global Admin-table preservation, all roles/facilities, all Date branches or clinical medication-history coverage. No grants, configuration, terminology, source or runtime changes. All 30 retained genuine originals are public candidates; no image edits. Two distinct fictional patients through ordinary existing Staff UI, native field validation, contact/address/geography/optional controls, birth-year verification and honest full-profile404, duplicate choices and actual native unsaved confirmation. No care/grants/configuration/old-patient edit. Exact committed 3dfb source/tree, existing ordinary Nurse on one already-established fictional Polyclinic Ambulatory case. Unchanged Cancel; three fictional Integer values 1/2/3 and explicit fictional Text; four optional field notes; exactly one ordinary response saved at 11:22 AM; one genuine 41,791-byte single-page PDF saved/viewed; warning Cancel then source-only Error verified after reload. Both ordinary roles confirm 24 scoped clinical comparisons at each of five stages plus the five older target response/log UUIDs. No global Admin-table claim, patient-portal/actual teleconsultation or real quality-rating assertion, all-role/facility claim, range-enforcement claim or enterprise-complete claim. No prerequisites/grants/config/terminology/source/runtime edits. Twenty-six public originals from 28 retained raw frames; two incomplete-footer native attempts excluded. One saved Booked appointment for the existing synthetic A patient, ordinary Staff and Doctor actors, and the existing public no-charge template; genuine wide captures. No later care, token, grant or configuration change is included. One later read-only Administration-option illustration is included on the same committed source; its dated metadata and no-save scope remain explicit. One previously saved synthetic Staff Check-In and its fresh post-USB readback, plus ordinary Doctor open/default review/Cancel without encounter submission. Existing appointments, patient/identifier state and source remain preserved under scoped receipts. Exact unchanged committed 3dfb on restored physical-USB training profile. Existing ordinary Nurse on an existing fictional Ambulatory case. One blank Cancel with unexpected small native unsaved warning retained privately; one thirteen-required client demonstration and one unexpected automation DOMfill-Time client check retained privately, not attributed as a product bug. One definite Invalid url backend refusal followed by no-new-source readback. One successful ordinary response with fifteen answer leaves, seventeen values and four notes. Actual 50,387-byte two-A4-page PDF Save, Preview and complete independent renders. Own-source warning Cancel then Confirm Error and reload. Six normal Nurse/Doctor readback stages preserve twenty-four scoped collections and twelve older target response/log comparisons per stage. No global Admin audit claim. No extra clinical destination, grant, configuration, schema, terminology, favourite, source or runtime changes. Existing mg unit and expected recent cache only; no enterprise-complete claim. One normal existing Doctor creates a synthetic Ambulatory encounter from the exact saved Checked-In appointment, with independent reconciliation of encounter POST and separate appointment status update; then reloads and navigates between the saved records. No clinical findings, account, charge or token is created. Exact unchanged committed 3dfb on the restored physical-USB profile. A separate explicitly fictional patient and Ambulatory encounter were created once through the ordinary authorized Doctor API as a distinct prerequisite. Actual native Doctor flow: one blank Cancel, one definite before-DOB refusal, one corrected Patient deceased_datetime Submit and normal reload. Fifteen genuine 1728x921 originals. Four approved GET/SELECT-only stages each passed twenty-six protected clinical collection comparisons, exact other Patient/Encounter/identifier rows, target Encounter conservation and all308 sequences. Only target deceased_datetime/Doctor updater/modifieddate and source-backed instance identifier maintenance allowed; actual phone identifier199 modified_date refreshed, name200 remained exact, both NULL creators retained. No ordinary/structured QR, derived observation, PDF, certificate, discharge, undo, new grant/config/runtime/source changes or full audit-history/enterprise-complete claim. Native segmented-key operator recovery remained private and was not attributed as a product defect. PRIVATE candidate: existing genuine 19 October 2026 ordinary Staff no-save department/practitioner review and Close; three original wide frames, no new capture or business action. Published status is release-schema metadata only; this package has not been imported or promoted. PRIVATE initial-only future-date/schedule-filter teaching candidate: existing fictional Clinic patient/practitioner and materialized slots, one Booked appointment saved normally. No reschedule, cancellation, Check-In, token, clinical care, configuration or grant change. Published status is release-schema metadata; no Site import/promotion performed. PRIVATE candidate: historical safe Cancel reviews, one actual reschedule and one later cancellation of its distinct replacement; retained original history. Published status is schema metadata only; no Site import. Exact unchanged3dfb synthetic physical-USB profile. Existing ordinary Nurse on MedicineHybrid case. One actual client required refusal/no Statement or QR/allocator change; one native CREATE of reportedHYMOX250MGCAPS/NotTaken/Practitioner/date19Oct; saved summary/fullNote; locked create-only fields; history selector zero-selected Cancel; own Remove-warning neutralCancel; later one localEnteredInError then oneSubmit; same UUID/fields/creator/time retained with oneUPDATE structuredQR. Seven finite approved normal-role GET/SELECT stages passed, including independent Doctor readback and117 existing raw scoped rows; only two relevant clinical allocator transitions. Not all-database or unrelated concurrent Admin preservation. OriginalV2 preflight numeric rowhash equality remains precision-limited; separate fresh raw-native baseline and all subsequent scoped raw rows preserve exact PostgreSQL text.35originals retained,30public unchanged1728x921frames,5private excluded honestly. No ordinaryQR/PDF, prescription/MAR/dispense, clinical qualification, newgrant/config/source/service or A3 UI claim. Exact committed3dfb, physical-USB guarded synthetic runtime. One existing ordinary Nurse on existing Medicine case, one supplied2552B inertPDF/one complete FileUpload5/one exact-byte localobject. Five actual no-save stages, one valid native Submit, saved/reloaded finite Nurse+Doctor readbacks; old scoped clinical/file rows and11oldobjects preserved, relevant FileUpload allocator4→5. Not unrelated concurrent Admin/global database preservation.24raw originals retained;14public originals unchanged, including genuine compactnativeconfirmation and varied originalwide dimensions. No ordinaryQR/responsePDF, actual clinical content/consent, rename/archive/restore or laterA3 claim. Metadata/prose V2 adds the genuine native-file-chooser17, truthful chooser surface/caption and organization-approved-file wording. Supplied rawPDF remains private proof, not a published downloadable artifact. Three narrow no-save lessons from the actual ordinary Staff P1b sequence. Eleven original records, ten unique image hashes, including one unmodified native macOS confirmation. Private schema-ready package only; no Site import or publication. Private root-review following-batch candidate: exact committed3dfb product and separately qualified Clinical transport profile/PID23511. Seven genuine clean task-tab715 viewport originals (actual1728×977) show the existing savedPDF preview1/1/normalClose, unchangedRenameCancel and emptyArchiveCancel. Root recaptured only these neutral states with zero business submissions. Prior accepted conservation verifiers retain original earlier times; no new SQL/API/object readback is claimed. V1 native-window originals/loading02 remain private unchanged. No real rename/archive/restore/upload/Print/Download/OpenInBrowser or later-product-source claim. status published is export eligibility only; no Site import/publication. Tax-rule teaching covers the observed Staff access boundary and an existing Clinic administrator completing the fifteen fields, saving one fictional unresolved Draft, then reloading and opening View details. The fourteen stored values persist; the new-edit explanation starts blank. Review, approval, publication and activation are separate workflows. Nurse teaching covers the configured Diagnosis practice form: leave an existing diagnosis unchanged, save ordinary Text and Integer answers with separate notes, review a one-page PDF, and mark only the ordinary response as entered in error. Screenshots show saved values, Cancel, correction and reload. The structured diagnosis remains separate. Staff teaching covers one saved patient-profile update: use the segmented birth date, keep separate contact numbers and addresses, review geography and PIN Code, save once, then reload and inspect the clean form. Screenshots show the saved values, disabled Update button and Back without further changes. Nurse Respiratory Status teaching covers every configured thirteen input, all twelve literal choices, six Decimal and two Integer controls, narrative and all thirteen note controls. The final four fictional answers and two notes were saved and reloaded; one genuine A4 PDF was saved/viewed; own-source entered-in-error Cancel, Confirm and reload retained the answers. A separate later unsaved Text-clear illustration is clearly distinguished. Values are software samples, not respiratory measurements or treatment settings. Native Nurse is pictured; Doctor evidence is normal read-only API only. Facility Admin teaching covers one empty required change-reason refusal, unsent fictional reason Cancel/reopen/Cancel, and the separate Row lifecycle Validate for the same unresolved Tax draft. The actual negative result lists illegal transition, evidence not activation grade, source document missing, overlap check not performed and config package missing. No filled-reason Confirm, saved lifecycle move, approval, activation, qualification or financial-readiness result is claimed. Ordinary Nurse structured Allergy teaching on the same fictional active encounter covers untouched Cancel, a required-field refusal, local catalogue selection, unsaved category/criticality/verification/clinical-state controls, occurrence calendar and Quick Finder, row notes, one create and same-row Inactive and Entered in Error updates with reloads. Filtered Overview/History messages are distinguished from the retained disabled Error entry. Doctor evidence is normal read access only. No ordinary questionnaire PDF, deletion, restore or full clinical allergy assessment is claimed. Existing ordinary Nurse teaching adds one display-name Rename and saved reload for a synthetic encounter attachment, a neutral Archive-warning Cancel, one reasoned Archive, and Active/Archived filters with retained reason/author/time and Close. The document bytes and original upload metadata remain retained; this inspected source provides no Restore/unarchive action. No physical deletion, new upload, complete-role/module or global-database invariance is claimed. Additive ordinary-role teaching: Nurse encounter Notes thread/message creation and retained read-only patient context; existing Facility Admin encounter-filtered claims, separate claim/encounter/invoice identities, same-encounter sibling detail, Refresh and All claims. These are bounded synthetic workflows with their own measured scopes, not complete role/module coverage, a separate Executive RBAC qualification, external payer/submission/settlement success or global database invariance. Additional bounded existing Clinic Facility Admin TaxRule status teaching: one explicit Draft to InReview transition and one explicit return to Draft, fictional reasons, genuine reloads and own status history. These two synthetic status changes do not approve, activate, publish or legally qualify a tax rate, clear claim/invoice holds or establish a least-privilege finance role. Additional ordinary Doctor copies a medication history item into a separately saved prescription request and inspects the retained reload; ordinary Staff uses an existing patient name identifier to find the synthetic patient. These narrowly measured synthetic flows are not prescribing-policy, payer, global role or full curriculum qualification. Additional bounded ordinary Doctor teaching stops exactly one existing copied medication request, preserves the other requests, and checks the settled reload. Expanded mixed active/ended product groups can still show an Ended child with Show Discontinued unchecked; the pictured footer hidden count is not proof that this child is hidden. No group discontinue, administration, prescription policy, persisted end-time, global state or complete module qualification is implied. Additional bounded ordinary Facility Admin teaching creates two inert administrative Patient-resource parent and child tag configs, recovers from a required Display name refusal, verifies inherited child resource and parent navigation, uses neutral Archive Cancel, and confirms one own-child status archive with retained details after reload. No tag applications, grants, patient or encounter changes, financial action, deletion or reactivation are demonstrated. Configuration status changes are explicit; no whole database or global allocator qualification is implied. Additional ordinary Doctor guides demonstrate one explicitly fictional Consent metadata Draft with Privacy category and Deny decision, its dates, period, note, card, details, reload and retained Entered in Error correction. They preserve the observed date-validation and optional-period clear limitation, unsaved choice review, neutral Cancel and attachment-name search. No real legal consent, signature, verification, treatment or disclosure authority is represented. Additional Emergency guides demonstrate the unconfigured triage board, its row scope, columns, Refresh and encounter Notes link; one separate synthetic Emergency encounter; an untouched update Cancel and native confirmation; one On Hold update and one return to In Progress with reload and Status History. The older Ambulatory encounter remains separate. No triage level, clinical handover, admission, discharge, class conversion or terminal-state save is claimed. Supporting files, print, deletion, restoration and full-module completion remain separate. Additional Facility Admin guides inspect the fictional SET-11 Draft/test certificate-rotation dialog without rotating. They show initially disabled Rotate, a harmless reference warning, a reason that does not remove that warning, Close, retained unsent text on reopening, clearing the reference and reason, Close again and a normal browser Reload. No credential bytes, certificate rotation, connection test, exchange, dispatch, endpoint change or additional record save is represented. Additional Facility Admin guides create one empty Team under an existing department, review its saved details, close its Remove warning with Cancel, remove the empty Team and reload the parent list. No membership, access, service assignment or restoration is shown. Additional ordinary Nurse guides select two existing medication requests, cancel an unsaved selection, reset only one draft, save one Not Done and one In Progress entry together, then reload and inspect both entries through unchanged Cancel. The recorded parameters and notes are fictional software examples; clinical administration, printing and other medication workflows are outside this scope. Additional Doctor guides cancel an unsaved discharge draft, choose Other and enter fictional advice and a reviewed end time, save once and reload, then cancel a separate completion warning before confirming completion once. They read the five-entry status history and observe one refused Restart under the measured zero-hour policy; the notice expired before the retained outcome image. One native unsaved warning retains its compact original dimensions. No successful restart, clinical advice, bed or device release, or restoration is demonstrated. Additional Doctor and Nurse guides follow one fictional laboratory request through specimen drafts, required-field refusals, collection, an Unsatisfactory specimen and recollection, preliminary results and correction, Final report approval, the original report PDF, request completion and reload. Separate later history-menu and saved-report printing demonstrations retain their actual chronology. The observed collection-time display discrepancy is described without interpreting it as a different collection. No specimen-processing save, physical test, clinical interpretation, payer exchange or complete laboratory curriculum is demonstrated. Additional ordinary Nurse and Doctor guides use three explicitly fictional, software-only DEMO substances for Food, Environment and Biologic category examples. They teach new-row Remove and draft Cancel, one three-entry Nurse save with separate dates and notes, Doctor preview Cancel and a two-entry update, persisted Remove Cancel and one Entered in Error correction, history, reporting, return navigation and retained disabled fields. A separate read-only guide compares an older Completed encounter with patient-level current Allergy history and the actual return to the active case. Blank panels and filtered summary badges are not clinical no-allergy findings or backend write-permission tests. The three terminology labels do not represent real allergens, clinical interpretation or a reaction interface. No additional patient, clinical encounter, grants, reaction control, closed-encounter write qualification or complete Allergy curriculum is claimed. Additional read-only Nurse guides inspect sparse vital-sign rows, observation details and the existing Pulse tooltip and retained history. Three ordinary Doctor guides practise diagnosis-history group selection and cancellation, change an existing diagnosis to Inactive and then Recurrence, and change verification on an existing symptom to Refuted while checking current views and retained history. These fictional software demonstrations do not establish clinical recommendations, new permission grants or completed competence. Two ordinary Doctor guides follow one fictional product through separate dosage instructions, duration and dose-range controls, one final prescription submission and saved readback. A Nurse guide demonstrates a refused history copy when an inventory-backed prescription lacks a medication code, checks the empty statement draft and retained history, then leaves without submitting. These software examples do not establish treatment instructions, a successful coded statement copy, dispensing or administration, new permission grants or completed competence. A further Doctor and Nurse pair follows a separately saved code-backed demonstration prescription into a reported medication statement, explicitly reconciles its dosage text, information source and dates, and verifies saved notes and authorship after reload. Copying does not verify actual medication taking. The full clinical curriculum remains in progress. One ordinary Doctor copies a synthetic Nurse-reported medication statement into a fresh prescription request, reviews the initially blank prescribing fields and new Doctor requester, enters separate fictional dose, frequency and duration plus a shared software-only note, and verifies one saved prescription after reload while retaining the original reported statement. This is software teaching, not a prescribing recommendation, dispensing, administration or a claim that all clinical teaching is complete. An ordinary Nurse changes only the status of one existing synthetic reported medication statement to On Hold and back to Active with separate saves and reloads, retaining its original details and reading its current patient-history entry by creation date. An ordinary Doctor creates one patient-only synthetic Notes discussion, sends one fictional message, and verifies its author, time and counts after reload. This Notes discussion has no encounter association. These bounded software exercises do not establish a treatment decision, actual medication use, delivery or read acknowledgement, dispensing, administration, permission grants or completed competence. An ordinary Doctor adds two different synthetic medicine rows using the separate Product and Medication selectors, reviews each row and the shared prescription note, revises the first fictional quantity before one Submit, and verifies the resulting single prescription after a normal reload. These are software teaching examples, not prescribing, dispensing or administration recommendations; the retained saved-result proof is bounded to its historical capture interval. An ordinary Pharmacist locates the assigned queue and synthetic patient, recognises the patient-home encounter-list access boundary, previews and cancels an unsaved original billing draft, then selects one new Doctor prescription. The operator observes one client refusal for a selected coded medicine without an inventory product link, excludes that row and saves only one partial stock-backed quantity as a Preparation row in an In Progress order with a Draft invoice. The lesson distinguishes All Given, selection-driven prescription Mark Complete and later order completion, configured final invoice rounding, reload and a retained Draft readback after one refused Issue action. The insurance-readiness explanation is source-and-scoped-state inference, not a captured response body or toast. Four additional later individual Services footer views picture the pagination clicks, ordered logically by visible page state rather than capture chronology. No payment, successful issuance, physical handover, administration, substitution, permission grant or completed competence is demonstrated.

Normal browser reload has finished; same patient-only thread, full message, Doctor author and timestamp retained, blank Send disabled. — **Recorded release 3dfb7c9f · 2026-10-20T09:43:30.428Z · 1728 × 921**
Normal reload retained message
Capture details
Observed installed committed 3dfb software on 20 October 2026. Patient-only Notes, with one fictional discussion and one message. Genuine natural wide viewport; no pixel edits.
Image SHA-256 `4a78ecc283df5372ae257575a2c4997ada24d1cbe8a1f6efa69e33b656a26bdd`
**Same patient**: The patient header remains the assigned synthetic patient.
**Patient Notes**: Notes remains selected after normal browser reload.
**Saved discussion retained**: The same discussion remains selected.
**Saved message retained**: The complete fictional message remains visible after reload.
**Author retained**: The saved message still shows the Doctor display name.
**Time retained**: The same actual displayed creation time remains.
**Counts retained**: One unique author and one message remain.
**Blank composer**: Reload has not created another message or left an unsent draft.

12 of 12 content blocks have reviewed image alignment.

Before you begin

Use an authorised Doctor account with access to the assigned synthetic patient. The observed account is MANSOQ E2E Doctor (qa-doctor). Patient access and write permission must already be available; this guide does not grant access.
1
Recorded release 3dfb7c9f · 2026-10-20T09:33:49.052Z · 1728 × 921
Ordinary doctor identity
Capture details
Observed installed committed 3dfb software on 20 October 2026. Patient-only Notes, with one fictional discussion and one message. Genuine natural wide viewport; no pixel edits.
Image SHA-256 0b9798b7f4764387c0af6cff9084120afe4c41458856503b43658ae280465484
1. Doctor account: The observed account is MANSOQ E2E Doctor, username qa-doctor.
Open the assigned synthetic patient profile. This example uses SYNTHETIC KB Registration DOB 3dfb 3301 (Patient A74). Use only explicitly fictional software-training text; it is not a clinical finding, treatment instruction or handover acknowledgement.
12
Recorded release 3dfb7c9f · 2026-10-20T09:34:19.017Z · 1728 × 921
Patient a74 profile and notes entry
Capture details
Observed installed committed 3dfb software on 20 October 2026. Patient-only Notes, with one fictional discussion and one message. Genuine natural wide viewport; no pixel edits.
Image SHA-256 0bd7aecbdb40e5f0d02d0fbb07f0a7562e91fc1ce200331fef02feabd8169af2
1. Assigned synthetic patient: Confirm the patient name before opening Notes.
2. Open patient Notes: Select Notes in Patient Details, outside an encounter.

1. Open Notes from the patient profile

Confirm the patient name in Patient Details, then select Notes. In this example the patient-level discussion list is empty and offers Start New Discussion. This is the Notes tab on the patient profile; no encounter has been opened for this discussion.

Recorded release 3dfb7c9f · 2026-10-20T09:34:19.017Z · 1728 × 921

Patient a74 profile and notes entry

Capture details

Observed installed committed 3dfb software on 20 October 2026. Patient-only Notes, with one fictional discussion and one message. Genuine natural wide viewport; no pixel edits.

Image SHA-256 0bd7aecbdb40e5f0d02d0fbb07f0a7562e91fc1ce200331fef02feabd8169af2

Assigned synthetic patient: Confirm the patient name before opening Notes.
Open patient Notes: Select Notes in Patient Details, outside an encounter.

Patient Details Notes is selected and shows No discussions yet. This is not an encounter Notes view. — **Recorded release 3dfb7c9f · 2026-10-20T09:36:36.659Z · 1728 × 921**
Patient only notes empty
Capture details
Observed installed committed 3dfb software on 20 October 2026. Patient-only Notes, with one fictional discussion and one message. Genuine natural wide viewport; no pixel edits.
Image SHA-256 `793ea13e357ca6d08ca03cc6fff59e8ba1b4ce9acf31cfa0730dabcc456fd420`
**Empty discussions**: This patient has no saved discussions at the start of this example.
**Start New Discussion**: Open the title dialog.
**New**: The header also offers a New discussion button.

2. Check the empty title and cancel

Select Start New Discussion. Leave the title blank and observe that Create is disabled. Select Cancel. The dialog closes and the discussion list remains empty. No blank-title save was attempted.

Actual new discussion dialog: empty custom title, visible suggested titles, Cancel and disabled Create. No server validation request. — **Recorded release 3dfb7c9f · 2026-10-20T09:36:46.514Z · 1728 × 921**
Empty title create disabled
Capture details
Observed installed committed 3dfb software on 20 October 2026. Patient-only Notes, with one fictional discussion and one message. Genuine natural wide viewport; no pixel edits.
Image SHA-256 `f6a997a15d2d75fc495d4b6f32f17a8db8a3e30cd651cf43b2162dc62075b165`
**Empty title**: Create stays disabled while the title is blank.
**Create disabled**: This is client-side disabling; no blank request was submitted.
**Cancel**: Close the empty title dialog without saving.

Cancel dismissed the empty title dialog without creating a discussion. — **Recorded release 3dfb7c9f · 2026-10-20T09:41:37.995Z · 1728 × 921**
Cancel returned empty notes
Capture details
Observed installed committed 3dfb software on 20 October 2026. Patient-only Notes, with one fictional discussion and one message. Genuine natural wide viewport; no pixel edits.
Image SHA-256 `793ea13e357ca6d08ca03cc6fff59e8ba1b4ce9acf31cfa0730dabcc456fd420`
**Still empty**: Cancel returned to the same empty discussion list.
**New**: Select New to start the actual fictional discussion.

3. Create one fictional discussion

Select New. Enter “SYNTHETIC Patient A74 - patient-only Notes” in the title field. Review the title, then select the enabled Create once and wait for the dialog to close. The saved discussion appears in the left list and opens on the right.

One exact fictional title is filled; Create is enabled, no create yet. — **Recorded release 3dfb7c9f · 2026-10-20T09:42:05.851Z · 1728 × 921**
Fictional title create ready
Capture details
Observed installed committed 3dfb software on 20 October 2026. Patient-only Notes, with one fictional discussion and one message. Genuine natural wide viewport; no pixel edits.
Image SHA-256 `2995f70cfcde9416236af260b0decea3829b8a8241aa43f3a43d1455cc833bc7`
**Fictional title**: Use an explicit synthetic title for this training example.
**Create once**: Create saves a discussion; select it once and wait.

The one created patient-only discussion is selected; zero authors and messages, blank Send disabled. — **Recorded release 3dfb7c9f · 2026-10-20T09:42:23.729Z · 1728 × 921**
Created thread empty composer
Capture details
Observed installed committed 3dfb software on 20 October 2026. Patient-only Notes, with one fictional discussion and one message. Genuine natural wide viewport; no pixel edits.
Image SHA-256 `5d15168c4e437b3ac7daa9425a51fa0e85fd4cc90fc643d75d9b33ad8ab06046`
**Saved discussion title**: The new discussion is open.
**Selected discussion**: The saved discussion also appears in the left list.
**Empty message box**: The composer is empty before writing the message.
**Send disabled**: The empty message box cannot send.
**Zero counts**: No author has sent a message yet, and the message count is zero.

4. Check the new discussion before composing

Match the selected discussion title. The message area is empty, the header shows zero authors and zero messages, and Send is disabled while the composer is blank. Creating the discussion has not yet sent a message.

5. Write and send the fictional message

Enter this complete fictional example in the message box: “SYNTHETIC SOFTWARE TRAINING ONLY - Patient A74. Demonstration note for longitudinal documentation practice. This is not a clinical finding, treatment instruction or handover acknowledgement.” Review it, then select the enabled Send arrow once. Wait for the message to appear before taking another action.

One fictional demonstration message is filled and Send enabled; no Send yet. — **Recorded release 3dfb7c9f · 2026-10-20T09:42:48.421Z · 1728 × 921**
Fictional message send ready
Capture details
Observed installed committed 3dfb software on 20 October 2026. Patient-only Notes, with one fictional discussion and one message. Genuine natural wide viewport; no pixel edits.
Image SHA-256 `eab95bcb4dd853c16bf1be5a846b0163ade626a3e5b8e0b285a1be2c8d1637dd`
**Fictional message**: Review the complete software-training message before sending.
**Send once**: Select the arrow once to save this message.

One saved fictional message with Doctor display name and actual local timestamp; header shows one author and one message. Composer cleared. — **Recorded release 3dfb7c9f · 2026-10-20T09:43:03.119Z · 1728 × 921**
Saved message author and counts
Capture details
Observed installed committed 3dfb software on 20 October 2026. Patient-only Notes, with one fictional discussion and one message. Genuine natural wide viewport; no pixel edits.
Image SHA-256 `4a78ecc283df5372ae257575a2c4997ada24d1cbe8a1f6efa69e33b656a26bdd`
**Message author**: The message identifies MANSOQ E2E Doctor.
**Displayed time**: The captured local display is today at 12:42 PM.
**Saved message**: Read the full fictional message in its saved bubble.
**One author and one message**: These are unique message-author and message totals, not recipients or read receipts.
**Composer cleared**: After saving, the composer is blank and Send is disabled.

6. Read the saved author, time and content

Read the saved message bubble. It shows MANSOQ E2E Doctor and the captured local creation display “today at 12:42 PM”. The header now shows one unique message author and one message. These counts do not identify recipients, delivery or acknowledgement. The message box clears after the save.

7. Reload once and verify retention

Use your browser’s Reload once (⌘R on macOS or Ctrl+R on Windows/Linux). Wait for Patient Details and Notes to finish loading. Match the same patient, discussion title, complete fictional message, Doctor author and displayed time. The one-author and one-message counts remain, and the composer is blank. Do not send the example again.

Keep patient Notes and encounter Notes distinct

This discussion was created through Notes in Patient Details and has no encounter association. An encounter has its own Notes entry; this example does not move or copy messages between those scopes. The existing patient details and other saved patient records were retained during this demonstration.

Recorded release 3dfb7c9f · 2026-10-20T09:34:19.017Z · 1728 × 921

Patient a74 profile and notes entry

Capture details

Observed installed committed 3dfb software on 20 October 2026. Patient-only Notes, with one fictional discussion and one message. Genuine natural wide viewport; no pixel edits.

Image SHA-256 0bd7aecbdb40e5f0d02d0fbb07f0a7562e91fc1ce200331fef02feabd8169af2

Assigned synthetic patient: Confirm the patient name before opening Notes.
Open patient Notes: Select Notes in Patient Details, outside an encounter.

Recognise the limits of this example

Blank Create and Send were visibly disabled, and Cancel was exercised before the save. No permission refusal or backend error was forced because this Doctor already had the required access. If your assigned patient is unavailable or a save fails, stop and use your normal support process instead of changing roles or submitting repeatedly. This guide does not demonstrate editing, deleting, exporting or acknowledging messages.

Source evidence

Every citation uses this exact committed version. The private source repository requires access.

repositories/platform/mansoq-web/src/components/Notes/NoteManager.tsx:198 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
b54f71e2de82d823798c2d704758b7c41c057b0a9709fed81690f8f6fac9522e
repositories/platform/mansoq-web/src/pages/Encounters/tabs/notes.tsx:5 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
eb1bb24734ab4329e6b7997aa4fd7eaa694920731d439343494dbb713f263c98
repositories/platform/mansoq-web/src/components/Patient/PatientDetailsTab/PatientNotes.tsx:7 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
7e6b14f7e73e37e090a19aa083e847797b865e30f10287adec6e28febdd0c3e9
repositories/platform/mansoq-web/src/types/notes/threadApi.ts:7 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
e76339114d95217b9c3dbd80f75be24fa02262d70359404b0d84d709b1bc3a5c
repositories/platform/mansoq-web/src/types/notes/thread.ts:7 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
3accfa762fc1733b1dcfce0dacb599afdd8c3622b873556074752977d75a9bac
repositories/platform/mansoq-web/src/types/notes/messages.ts:3 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
756582fccfcce2f4f1feb272acddf62bc2566ff01d00c7a6ca7332631e0f696f
repositories/platform/mansoq-web/src/components/ui/auto-expanding-textarea.tsx:1 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
70c4c815e68cb12a32192b1c981ffaf9f8de555d1f76efb19db41da99c5c6d98
repositories/platform/mansoq-web/src/pages/Encounters/utils/EncounterProvider.tsx:1 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
d2609fc0452c91c20104237bf02be40ecb3bf48225011aba1f4bca2d50620d75
repositories/platform/mansoq-web/src/Utils/utils.ts:1 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
42db3c7a21342795ae94608ded05958c34844fb0004399c4360b94b45bde2357
repositories/platform/mansoq-core/mansoq/emr/models/notes.py:6 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
af2ce458005a0bd051f28208de4db3b154933968ccd3fba13df42f5dffc6a906
repositories/platform/mansoq-core/mansoq/emr/resources/notes/thread_spec.py:10 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
a5e07f034f951b494380ffd0306aceafd41d8929c1868a7d45e1e4786e7f8fac
repositories/platform/mansoq-core/mansoq/emr/resources/notes/notes_spec.py:10 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
f4b36a59ffc7840efe22bcb51d28521fabd45dde49f21a345c025dc06493f86b
repositories/platform/mansoq-core/mansoq/emr/api/viewsets/notes.py:35 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
b774fba7e44e354fa6e39471b42f8d846ab16588dc6fc07728abe195e6e1129b
repositories/platform/mansoq-core/mansoq/emr/api/viewsets/encounter_authz_base.py:55 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
852c308f990e192a1003e286be7dd57ddcc78840d218da1b90c1fab2eebec4f7
repositories/platform/mansoq-core/mansoq/emr/api/viewsets/base.py:94 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
6a287dd315b8a4957b29c58e4bbc1bef7b8d9d257f9149f93045ff0adbdcae6c
repositories/platform/mansoq-core/mansoq/emr/models/base.py:8 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
61f50a19078c8a6435398e6b3e9174326038e9047129382c0d882f1e8f367b4c
repositories/platform/mansoq-core/mansoq/utils/models/base.py:15 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
1a5270f50188d1e0b044210773ca86a483b904f3a9724bb7b321d4ea463acfaf
repositories/platform/mansoq-core/config/api_router.py:590 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
36bd0555423f9dd86b0586dac6de8782c32f10017c954587a0c7dd65d0e608db
repositories/platform/mansoq-core/mansoq/security/authorization/encounter.py:97 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
0e7ff8afcfb57b2371201e16ee6fac26125d6e686af66ed7edd95e49bc07de78
repositories/platform/mansoq-core/mansoq/security/authorization/patient.py:1 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
45de75f24e42fa30316a96efb92b23c577e2c3831e17ec96e7ff2c73d0d1973d
repositories/platform/mansoq-web/public/locale/en.json:1 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
96498c8b964dce856d43c09e4241708efdd175d935e7ebbd14fa2f8d62efa507
repositories/platform/mansoq-web/src/components/ui/input.tsx:1 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
8a181820bcb1d94f9bd9fc6a6ca5872e772a29a3397667f657f3bdc23f34f9c9
repositories/platform/mansoq-web/src/components/Patient/PatientInfoHoverCard.tsx:77 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
5fab1fac78f542b1cb08d072a373f5e954e0975db97f3d3e935957bcb5a187d8
repositories/platform/mansoq-web/src/components/Patient/PatientDetailsTab/index.tsx:58 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
670a4110cfe5e8bea4d425997a61f36d098a9191281f792645e62aa806ddc7ad
repositories/platform/mansoq-web/src/components/Patient/PatientDetailsTab/EncounterHistory.tsx:150 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
a98c5ea91cd343d6212370c298a62a6297f7c6f998483d4d79f457fcbc7d14a8
repositories/platform/mansoq-web/src/components/Facility/EncounterCard.tsx:146 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
5e9572f88aba61bd917500b1cd0e6fbb8f46dde4123639d935ee0d80a5c71068
repositories/platform/mansoq-web/src/components/Patient/PatientDetailsTab/Demography.tsx:270 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
cd33fb513c56360e5b3c1c754507acf6fa6fbbff2e2249b66ae30ce498b84fd3