Clinical care · VERSION 3dfb7c9f

Create an encounter discussion and recover from title errors

Use discussion title suggestions, recognise disabled and refused titles, and keep one saved thread.

Nurse

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.

Notes empty encounter on the synthetic training case — **Recorded release 3dfb7c9f · 2026-10-19T22:06:51.297Z · 1728 × 921**
Notes empty encounter
Capture details
Observed committed 3dfb software and the Clinical profile qualified for 20 October 2026. One valid thread create and one message send are distinguished from unsaved exercises and refusals.
Image SHA-256 `d7ff4b3f4a3b8c5655bed1e3056ab4a0a60b58c76ea41fcd551d5772a4314f2f`
**Open Notes**: Select the encounter Notes tab.
**Select New**: Open the new discussion dialog.
**Read Start New Discussion**: This is another visible entry to the same new discussion dialog.

13 of 13 content blocks have reviewed image alignment. Missing overview or prerequisite images remain open.

Before you begin

Use an authorised Nurse session with access to the assigned active synthetic encounter and its patient profile.
123
Recorded release 3dfb7c9f · 2026-10-19T22:06:51.297Z · 1728 × 921
Notes empty encounter
Capture details
Observed committed 3dfb software and the Clinical profile qualified for 20 October 2026. One valid thread create and one message send are distinguished from unsaved exercises and refusals.
Image SHA-256 d7ff4b3f4a3b8c5655bed1e3056ab4a0a60b58c76ea41fcd551d5772a4314f2f
1. Open Notes: Select the encounter Notes tab.
2. Select New: Open the new discussion dialog.
3. Read Start New Discussion: This is another visible entry to the same new discussion dialog.
Use only the fictional software examples. A discussion title or message here is not a clinical plan, handover or patient-care decision.
123
Recorded release 3dfb7c9f · 2026-10-19T22:06:51.297Z · 1728 × 921
Notes empty encounter
Capture details
Observed committed 3dfb software and the Clinical profile qualified for 20 October 2026. One valid thread create and one message send are distinguished from unsaved exercises and refusals.
Image SHA-256 d7ff4b3f4a3b8c5655bed1e3056ab4a0a60b58c76ea41fcd551d5772a4314f2f
1. Open Notes: Select the encounter Notes tab.
2. Select New: Open the new discussion dialog.
3. Read Start New Discussion: This is another visible entry to the same new discussion dialog.

1. Check the intended encounter and open Notes

Confirm the assigned synthetic patient and In Progress encounter, then select Notes. The example starts with No discussions yet. This is software training, not a clinical handover.

2. Open New and read the title suggestions

Select New. The seven suggestions are Treatment Plan, Medication Notes, Care Coordination, General Notes, Patient History, Referral Notes and Lab Results Discussion. They populate a discussion title; they do not supply message content.

New thread templates required title on the synthetic training case — **Recorded release 3dfb7c9f · 2026-10-19T22:06:55.734Z · 1728 × 921**
New thread templates required title
Capture details
Observed committed 3dfb software and the Clinical profile qualified for 20 October 2026. One valid thread create and one message send are distinguished from unsaved exercises and refusals.
Image SHA-256 `21b530f6bf38bb1ad97cfd0969bf27bb0c0c5919dfd233a04d39c55660117df2`
**Read Treatment Plan**: A suggested discussion title.
**Read Medication Notes**: A suggested discussion title.
**Read Care Coordination**: A suggested discussion title.
**Select General Notes**: This example uses the General Notes title suggestion.
**Read Patient History**: A suggested discussion title.
**Read Referral Notes**: A suggested discussion title.
**Read Lab Results Discussion**: A suggested discussion title.
**Read the blank title field**: Enter a title or use a suggestion.
**Read disabled Create**: A blank title cannot be created.

3. Try the General Notes suggestion

Select General Notes. Its text appears in the discussion title field. You can replace the suggested title with a custom one before creating the thread.

Template populates title unsaved on the synthetic training case — **Recorded release 3dfb7c9f · 2026-10-19T22:06:56.087Z · 1728 × 921**
Template populates title unsaved
Capture details
Observed committed 3dfb software and the Clinical profile qualified for 20 October 2026. One valid thread create and one message send are distinguished from unsaved exercises and refusals.
Image SHA-256 `9c5c25381d066b3a9455f371604f708686d949599410c6688f8fb19d225447aa`
**Select General Notes**: Its text populates the title field.
**Read General Notes**: The title is still unsaved.

4. Clear the title and inspect the disabled Create button

Clear the title. Blank or whitespace-only text leaves Create disabled. The pictured spaces do not form a usable discussion title.

Whitespace title create disabled on the synthetic training case — **Recorded release 3dfb7c9f · 2026-10-19T22:06:56.171Z · 1728 × 921**
Whitespace title create disabled
Capture details
Observed committed 3dfb software and the Clinical profile qualified for 20 October 2026. One valid thread create and one message send are distinguished from unsaved exercises and refusals.
Image SHA-256 `36509b23576afc2e76b5bf7b43a9f237bbbb40d79a4a2e7c1f2e87e609e215ca`
**Read the whitespace-only title**: Spaces alone do not enable creation.
**Read disabled Create**: Complete a nonblank title to continue.
**Cancel this draft**: Close without creating a discussion.

5. Cancel the unsaved title exercise

Select Cancel. The dialog closes and the example still has no discussions.

Cancel keeps no discussions on the synthetic training case — **Recorded release 3dfb7c9f · 2026-10-19T22:06:59.719Z · 1728 × 921**
Cancel keeps no discussions
Capture details
Observed committed 3dfb software and the Clinical profile qualified for 20 October 2026. One valid thread create and one message send are distinguished from unsaved exercises and refusals.
Image SHA-256 `638350a862327bc321e3b8dfd0fe9bf17cfb33f8173d4677d2f0ea5e94ee0a50`
**Read No discussions yet**: The unsaved title exercise has been cancelled.

6. Read the 255-character title limit

The fictional 256-character X title in this exercise is refused. Read String should have at most 255 characters. Shorten a title to 255 characters or fewer before trying the intended valid title.

256 character title before create on the synthetic training case — **Recorded release 3dfb7c9f · 2026-10-19T22:15:15.844Z · 1728 × 921**
256 character title before create
Capture details
Observed committed 3dfb software and the Clinical profile qualified for 20 October 2026. One valid thread create and one message send are distinguished from unsaved exercises and refusals.
Image SHA-256 `f8be2fcc257e325e802b08e0e48add703efe5730260232f69011165f51ece350`
**Read the oversized training title**: This exercise uses 256 X characters.
**Select Create for the title-limit exercise**: The following image shows the refusal.

Overlong title refused 255 limit on the synthetic training case — **Recorded release 3dfb7c9f · 2026-10-19T22:16:12.840Z · 1728 × 921**
Overlong title refused 255 limit
Capture details
Observed committed 3dfb software and the Clinical profile qualified for 20 October 2026. One valid thread create and one message send are distinguished from unsaved exercises and refusals.
Image SHA-256 `8879a4bcbd537d8d018091571e0b8aa89089801a1332a3f47e7617a9389ce6a5`
**Read the title-length message**: The visible message says at most 255 characters.
**Correct the title**: Replace the oversized example before the valid create.

7. Review the fixed training title and create once

Replace the oversized value with: SYNTHETIC SOFTWARE TRAINING ONLY - Encounter discussion. The example includes two leading and trailing spaces to demonstrate trimming. The earlier title-limit toast remains visible in this ready screenshot; it belongs to the previous attempt. Select Create once after checking the title.

Valid title with spaces before create on the synthetic training case — **Recorded release 3dfb7c9f · 2026-10-19T22:16:12.931Z · 1728 × 921**
Valid title with spaces before create
Capture details
Observed committed 3dfb software and the Clinical profile qualified for 20 October 2026. One valid thread create and one message send are distinguished from unsaved exercises and refusals.
Image SHA-256 `fa594d6a07f226bc3d8e69f60b0be2886d600b47f56972e6c20f6e3296947464`
**Review the intended training title**: The single-line field displays the beginning of the title; the old 255-character toast is from the earlier attempt.
**Create the reviewed thread once**: Use the intended trimmed title.

Created thread zero messages on the synthetic training case — **Recorded release 3dfb7c9f · 2026-10-19T22:16:17.160Z · 1728 × 921**
Created thread zero messages
Capture details
Observed committed 3dfb software and the Clinical profile qualified for 20 October 2026. One valid thread create and one message send are distinguished from unsaved exercises and refusals.
Image SHA-256 `fddf4bc67a0873dc52f123d76aa08883cad78f8efe206ec04c319d311d9758fb`
**Read the full saved title**: The full header identifies the new discussion.
**Find the selected thread**: Only this new thread is listed in the example.
**Read zero participants**: No message author is counted yet.
**Read zero messages**: The new discussion is empty.

8. Read the created thread and its zero counts

Read the full discussion title in the header and find its selected sidebar entry. The new thread has zero participants and zero messages before a message is sent.

9. Recognise a duplicate title and cancel

Open New after the saved title appears in the loaded discussion list. Enter that same title and select Create. The client refuses the duplicate. Cancel the dialog; the single existing thread remains with zero messages.

Existing title before duplicate create on the synthetic training case — **Recorded release 3dfb7c9f · 2026-10-19T22:16:20.952Z · 1728 × 921**
Existing title before duplicate create
Capture details
Observed committed 3dfb software and the Clinical profile qualified for 20 October 2026. One valid thread create and one message send are distinguished from unsaved exercises and refusals.
Image SHA-256 `b75d634c8dd2784a52e430761fa13b2ad0e2e65367d23d3f6d31c661d0b92880`
**Read the same existing title**: The duplicate check uses this exact trimmed title.
**Select Create for the duplicate check**: This client check refuses another thread with the same loaded title.

Single created thread after duplicate cancel on the synthetic training case — **Recorded release 3dfb7c9f · 2026-10-19T22:16:32.225Z · 1728 × 921**
Single created thread after duplicate cancel
Capture details
Observed committed 3dfb software and the Clinical profile qualified for 20 October 2026. One valid thread create and one message send are distinguished from unsaved exercises and refusals.
Image SHA-256 `21e08b85d9eb6368ab2a511d625bd548a886ab1752735a14d8312b98984e19d8`
**Read the same single discussion**: The original saved thread remains selected.
**Read zero messages**: No message has been sent during the duplicate-title exercise.

Read the clearer duplicate notice in a later illustration

A later illustration repeats only the same duplicate-title check after the message has already been saved. Enter the existing title in New, select Create, then Cancel. Read Thread with this title already exists in the returned view. This later image therefore shows one participant and one message; it is not the earlier empty-thread checkpoint.

Post final client duplicate dialog on the synthetic training case — **Recorded release 3dfb7c9f · 2026-10-19T22:24:14.088Z · 1728 × 921**
Post final client duplicate dialog
Capture details
Observed committed 3dfb software and the Clinical profile qualified for 20 October 2026. Later read-only UI illustration after the four-stage SQL cutoff; no fresh SQL or HTTP measurement is claimed.
Image SHA-256 `67e9f228ab7cfa96b3f7ec6716881223f929f3d829b8f4d17472d4f3a2f1e779`
**Read the existing title**: This later duplicate example uses the same saved title.
**Select Create for the duplicate check**: The loaded exact title is refused locally.
**Cancel the duplicate dialog**: Return without another valid discussion create.

Duplicate notice readable after cancel on the synthetic training case — **Recorded release 3dfb7c9f · 2026-10-19T22:24:15.192Z · 1728 × 921**
Duplicate notice readable after cancel
Capture details
Observed committed 3dfb software and the Clinical profile qualified for 20 October 2026. Later read-only UI illustration after the four-stage SQL cutoff; no fresh SQL or HTTP measurement is claimed.
Image SHA-256 `490b2b4779f60a76d8d43ba1234bd674bae3aa7e99c06843c2092b4b7254d4ad`
**Read the duplicate notice**: Thread with this title already exists is clearly visible.
**Read the existing discussion**: The same thread remains selected.
**Read the later counts**: This later illustration follows the saved message and shows one participant and one message.

Source evidence

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

repositories/platform/mansoq-web/src/components/Notes/NoteManager.tsx:186 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
b54f71e2de82d823798c2d704758b7c41c057b0a9709fed81690f8f6fac9522e
repositories/platform/mansoq-web/src/pages/Encounters/tabs/notes.tsx:18 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
eb1bb24734ab4329e6b7997aa4fd7eaa694920731d439343494dbb713f263c98
repositories/platform/mansoq-web/src/components/Patient/PatientDetailsTab/PatientNotes.tsx:13 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
7e6b14f7e73e37e090a19aa083e847797b865e30f10287adec6e28febdd0c3e9
repositories/platform/mansoq-web/src/types/notes/threadApi.ts:5 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
e76339114d95217b9c3dbd80f75be24fa02262d70359404b0d84d709b1bc3a5c
repositories/platform/mansoq-web/src/types/notes/thread.ts:19 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
3accfa762fc1733b1dcfce0dacb599afdd8c3622b873556074752977d75a9bac
repositories/platform/mansoq-web/src/types/notes/messages.ts:1 · 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:14 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
a5e07f034f951b494380ffd0306aceafd41d8929c1868a7d45e1e4786e7f8fac
repositories/platform/mansoq-core/mansoq/emr/resources/notes/notes_spec.py:8 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
f4b36a59ffc7840efe22bcb51d28521fabd45dde49f21a345c025dc06493f86b
repositories/platform/mansoq-core/mansoq/emr/api/viewsets/notes.py:6 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
b774fba7e44e354fa6e39471b42f8d846ab16588dc6fc07728abe195e6e1129b
repositories/platform/mansoq-core/mansoq/emr/api/viewsets/encounter_authz_base.py:1 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
852c308f990e192a1003e286be7dd57ddcc78840d218da1b90c1fab2eebec4f7
repositories/platform/mansoq-core/mansoq/emr/api/viewsets/base.py:1 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
6a287dd315b8a4957b29c58e4bbc1bef7b8d9d257f9149f93045ff0adbdcae6c
repositories/platform/mansoq-core/mansoq/emr/models/base.py:1 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
61f50a19078c8a6435398e6b3e9174326038e9047129382c0d882f1e8f367b4c
repositories/platform/mansoq-core/mansoq/utils/models/base.py:1 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
1a5270f50188d1e0b044210773ca86a483b904f3a9724bb7b321d4ea463acfaf
repositories/platform/mansoq-core/config/api_router.py:1 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
36bd0555423f9dd86b0586dac6de8782c32f10017c954587a0c7dd65d0e608db
repositories/platform/mansoq-core/mansoq/security/authorization/encounter.py:1 · 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