Clinical care · VERSION 3dfb7c9f

Compare a completed encounter’s Allergy view with patient history

Inspect an older completed visit without editing it, compare the patient’s current Allergy history, and verify the encounter shown after returning.

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.

Active Inpatient context with two current fictional Allergy entries in the fictional training patient — **Recorded release 3dfb7c9f · 2026-10-20T05:21:03.145Z · 1728 × 921**
Active Inpatient context with two current fictional Allergy entries
Capture details
Observed committed 3dfb software on 20 October 2026. Separate read-only navigation after the accepted three-submit Allergy lifecycle; no new save or fresh SQL observation. Original pixels unchanged.
Image SHA-256 `a41fe06f03e5fc0ac6f86822920771396c2b4e26c046727ea7b05c8f6c875603`
**Verify the assigned synthetic patient**: Read the fictional training patient before changing the viewed encounter.
**Read active In Progress context**: The active primary case is Inpatient, 18 October to Ongoing.
**Read Environment verification**: The current Environment entry is Refuted, separately from clinical Active.
**Read Biologic verification**: Biologic remains Unconfirmed with High criticality; these are different columns.
**Select the older 16 October encounter**: Choose the distinct Ambulatory 16 Oct–16 Oct Completed card under Other Encounters.

12 of 12 content blocks have reviewed image alignment.

Before you begin

Use an authorised Doctor account and the assigned fictional training patient with an active encounter and an older Completed encounter.
12345
Recorded release 3dfb7c9f · 2026-10-20T05:21:03.145Z · 1728 × 921
Active Inpatient context with two current fictional Allergy entries
Capture details
Observed committed 3dfb software on 20 October 2026. Separate read-only navigation after the accepted three-submit Allergy lifecycle; no new save or fresh SQL observation. Original pixels unchanged.
Image SHA-256 a41fe06f03e5fc0ac6f86822920771396c2b4e26c046727ea7b05c8f6c875603
1. Verify the assigned synthetic patient: Read the fictional training patient before changing the viewed encounter.
2. Read active In Progress context: The active primary case is Inpatient, 18 October to Ongoing.
3. Read Environment verification: The current Environment entry is Refuted, separately from clinical Active.
4. Read Biologic verification: Biologic remains Unconfirmed with High criticality; these are different columns.
5. Select the older 16 October encounter: Choose the distinct Ambulatory 16 Oct–16 Oct Completed card under Other Encounters.
123
Recorded release 3dfb7c9f · 2026-10-20T05:21:19.585Z · 1728 × 921
Selected 16 October Completed Ambulatory encounter and date tooltip
Capture details
Observed committed 3dfb software on 20 October 2026. Separate read-only navigation after the accepted three-submit Allergy lifecycle; no new save or fresh SQL observation. Original pixels unchanged.
Image SHA-256 aaa1081d59fc91a15dff542cb751dbfbd9c15d40c510f9c76272ae8d600cd7c5
1. Review the selected historical card: The outlined 16 October Completed card is the viewed historical encounter; the Chosen Encounter above is still the primary active case.
2. Read the selected Completed header: Confirm Ambulatory and Completed in the content header.
3. Read the completed visit date: The details show a 16 October 2026 start at 09:00AM; the paired end is 10:00AM that day.
Keep this inspection read-only. Leave Allergy fields, Submit, encounter status and restart controls unchanged.
123
Recorded release 3dfb7c9f · 2026-10-20T05:21:40.335Z · 1728 × 921
Completed Overview without an Allergy panel
Capture details
Observed committed 3dfb software on 20 October 2026. Separate read-only navigation after the accepted three-submit Allergy lifecycle; no new save or fresh SQL observation. Original pixels unchanged.
Image SHA-256 78e616c077e5afb6e687fd0f9d3451a2bde76c8971ed9a67f4c75525281b226f
1. Confirm Overview is selected: Use the actual Overview tab, not the privately retained Diagnostic Reports detour.
2. Read No responses found precisely: This label describes questionnaire responses; it is not an Allergy finding.
3. Open See Clinical History: Use the visible patient Clinical History button from the historical Overview.
The pictured DEMO substances are fictional software examples, not real allergy, reaction or clinical assessment information.
12345
Recorded release 3dfb7c9f · 2026-10-20T05:24:29.659Z · 1728 × 921
Patient Allergy history with two current fictional entries
Capture details
Observed committed 3dfb software on 20 October 2026. Separate read-only navigation after the accepted three-submit Allergy lifecycle; no new save or fresh SQL observation. Original pixels unchanged.
Image SHA-256 1f807c4d1835f2a03af6723d94e0a07889e76b200c64f774c1409f9946b21c36
1. Confirm the Allergies history tab: The underline identifies the selected patient Allergy history.
2. Read Environment Refuted: Environment is still present with Active, Unable to Assess and Refuted.
3. Read Biologic Unconfirmed: Biologic is still present with Active, High and Unconfirmed.
4. Read the creation-date group: 20 October 2026 groups record creation, not the selected 16 October visit or occurrence dates.
5. Choose Back to Encounter: The arrow follows the supplied return path; recheck which encounter appears next.

1. Identify the active case and current entries

On Overview, verify the assigned synthetic patient and the active Inpatient case, shown here as 18 October to Ongoing and In Progress. Environment shows Refuted and Unable to Assess; Biologic shows Unconfirmed and High. Both clinical statuses are Active. Keep this context distinct from the older Completed cards.

2. Select the completed 16 October visit

Under Other Encounters, select the Ambulatory 16 Oct–16 Oct Completed card. Confirm the selected content header says Completed and the details show 16 October 2026, 09:00AM to 10:00AM. The outlined older card is the viewed encounter; Chosen Encounter above still identifies the active primary case. The first selected image includes its actual date tooltip.

Selected 16 October Completed Ambulatory encounter and date tooltip in the fictional training patient — **Recorded release 3dfb7c9f · 2026-10-20T05:21:19.585Z · 1728 × 921**
Selected 16 October Completed Ambulatory encounter and date tooltip
Capture details
Observed committed 3dfb software on 20 October 2026. Separate read-only navigation after the accepted three-submit Allergy lifecycle; no new save or fresh SQL observation. Original pixels unchanged.
Image SHA-256 `aaa1081d59fc91a15dff542cb751dbfbd9c15d40c510f9c76272ae8d600cd7c5`
**Review the selected historical card**: The outlined 16 October Completed card is the viewed historical encounter; the Chosen Encounter above is still the primary active case.
**Read the selected Completed header**: Confirm Ambulatory and Completed in the content header.
**Read the completed visit date**: The details show a 16 October 2026 start at 09:00AM; the paired end is 10:00AM that day.

Completed Overview without an Allergy panel in the fictional training patient — **Recorded release 3dfb7c9f · 2026-10-20T05:21:40.335Z · 1728 × 921**
Completed Overview without an Allergy panel
Capture details
Observed committed 3dfb software on 20 October 2026. Separate read-only navigation after the accepted three-submit Allergy lifecycle; no new save or fresh SQL observation. Original pixels unchanged.
Image SHA-256 `78e616c077e5afb6e687fd0f9d3451a2bde76c8971ed9a67f4c75525281b226f`
**Confirm Overview is selected**: Use the actual Overview tab, not the privately retained Diagnostic Reports detour.
**Read No responses found precisely**: This label describes questionnaire responses; it is not an Allergy finding.
**Open See Clinical History**: Use the visible patient Clinical History button from the historical Overview.

3. Read the completed Overview carefully

Stay on Overview. The active case’s quick-action tiles are absent. This selected visit has no Allergy panel in the example. No responses found describes questionnaire responses; it is not an Allergy status. Do not interpret this screen as evidence that all patient allergies were removed or that the patient has none.

4. Open patient Clinical History and Allergies

Select See Clinical History, then select the Allergies tab. Clinical History initially opens Responses in this example; changing tabs only changes the view.

Patient Clinical History initially on Responses in the fictional training patient — **Recorded release 3dfb7c9f · 2026-10-20T05:21:49.599Z · 1728 × 921**
Patient Clinical History initially on Responses
Capture details
Observed committed 3dfb software on 20 October 2026. Separate read-only navigation after the accepted three-submit Allergy lifecycle; no new save or fresh SQL observation. Original pixels unchanged.
Image SHA-256 `50600f74f2209d3a83a4c912598bac3ab2ab49a133f57f3626043da312c662ef`
**Verify the patient history heading**: This is the same synthetic patient’s clinical history, initially on Responses.
**Open the Allergies tab**: Select Allergies in the patient history navigation.

Patient Allergy history with two current fictional entries in the fictional training patient — **Recorded release 3dfb7c9f · 2026-10-20T05:24:29.659Z · 1728 × 921**
Patient Allergy history with two current fictional entries
Capture details
Observed committed 3dfb software on 20 October 2026. Separate read-only navigation after the accepted three-submit Allergy lifecycle; no new save or fresh SQL observation. Original pixels unchanged.
Image SHA-256 `1f807c4d1835f2a03af6723d94e0a07889e76b200c64f774c1409f9946b21c36`
**Confirm the Allergies history tab**: The underline identifies the selected patient Allergy history.
**Read Environment Refuted**: Environment is still present with Active, Unable to Assess and Refuted.
**Read Biologic Unconfirmed**: Biologic is still present with Active, High and Unconfirmed.
**Read the creation-date group**: 20 October 2026 groups record creation, not the selected 16 October visit or occurrence dates.
**Choose Back to Encounter**: The arrow follows the supplied return path; recheck which encounter appears next.

5. Compare the two current patient entries

Patient Allergy history still shows Environment as Active, Unable to Assess and Refuted, and Biologic as Active, High and Unconfirmed. The 20 October 2026 group is their creation date, not the selected 16 October visit or their occurrence dates. This current list excludes Entered in Error; the earlier Food correction remains outside this view rather than being deleted.

6. Return and verify the actual encounter

Choose the Back to Encounter arrow. The observed return is the active 18 October to Ongoing Inpatient case, with In Progress and the same two current entries. It does not retain the earlier 16 October historical selection. Recheck the header and Chosen Encounter before any later work; this walkthrough makes no field edit, Submit or restart.

Back to Encounter returns to active Inpatient context in the fictional training patient — **Recorded release 3dfb7c9f · 2026-10-20T05:24:43.191Z · 1728 × 921**
Back to Encounter returns to active Inpatient context
Capture details
Observed committed 3dfb software on 20 October 2026. Separate read-only navigation after the accepted three-submit Allergy lifecycle; no new save or fresh SQL observation. Original pixels unchanged.
Image SHA-256 `c74eb796b04014e5fcc64519e515b9404e534820a4aa8612770878c01780e484`
**Verify the returned Chosen Encounter**: The returned selection is the active primary Inpatient case.
**Recheck In Progress**: Back returned to 18 Oct–Ongoing Inpatient, not the earlier Completed selection.
**Recheck Environment retained**: The current Environment entry still shows Refuted after the read-only navigation.
**Recheck Biologic retained**: The current Biologic entry still shows High and Unconfirmed.

Understand the different filters

For a Completed encounter, its Overview Allergy list is narrowed to that selected visit. Patient Clinical History shows the current non-error patient list across encounters. The top clinical-history summary also uses a Confirmed-only Allergy query; an absent badge there is not a patient-wide no-allergy finding. Use the actual current list and the verified clinical record rather than treating a blank area as a clinical conclusion.

Keep the evidence within this read-only scope

These screens demonstrate historical viewing and normal history navigation. They do not test direct API write permissions, changing a closed encounter, or copying an Allergy into another encounter. The earlier guides separately demonstrate the fictional saved records and their retained correction; this inspection adds no clinical record.

Source evidence

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

repositories/platform/mansoq-web/src/pages/Encounters/utils/EncounterProvider.tsx:164 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
d2609fc0452c91c20104237bf02be40ecb3bf48225011aba1f4bca2d50620d75
repositories/platform/mansoq-web/src/pages/Encounters/EncounterHistorySelector.tsx:90 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
b02c8e66ae497608e32ffbe8ba7ea19234928b7ef7cf6c2440af327a1d34facf
repositories/platform/mansoq-web/src/pages/Encounters/tabs/overview.tsx:52 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
c085d98e3b4b6e6cb2e217faa57398e57fcd00ae5e4839fc7151567991b78e4a
repositories/platform/mansoq-web/src/pages/Encounters/tabs/overview/clinical-history-overview.tsx:30 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
e2cc1309001e96b38b1cd34c878188f3a56d29323ac3c3afeeb422274c19675b
repositories/platform/mansoq-web/src/components/Patient/allergy/list.tsx:83 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
bc8ef47eb25cf88a026260eb0bcd989b0f93cfae23acf9ecb7d35e5ffbb82fd7
repositories/platform/mansoq-web/src/components/Patient/allergy/AllergyTable.tsx:144 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
90ad547be1793fbd6b7341e9ffa497337ecb227a623c95444d85c9e980dd2a84
repositories/platform/mansoq-web/src/components/Patient/EncounterAccordionLayout.tsx:48 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
8bb99bd478feab4e8084ebadb54df2ea0ff73036f6de03ef67dca982fe068580
repositories/platform/mansoq-web/src/pages/Patient/History/AllergyHistory.tsx:15 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
b19e3433b2b4594118a01306bbe27631ffe22aefdd2d80209804b99cc9e749c2
repositories/platform/mansoq-web/src/pages/Patient/History/index.tsx:47 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
b434486d27a139467b3618a9bc8396c1eb7de96e5461ed7787e4c8c5de1aceb4
repositories/platform/mansoq-web/src/types/emr/encounter/encounter.ts:257 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
178ad4319d92bef379a78ed07c74d87d4c185774b3cdf989affc0f7e06ac08db
repositories/platform/mansoq-core/mansoq/emr/api/viewsets/allergy_intolerance.py:81 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
d9ae1ae9e05ebe02fa61b89e71d10b371c7ca07d020d74875f449d80ce85ed54
repositories/platform/mansoq-web/src/pages/Encounters/EncounterShow.tsx:281 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
dba481a8490fa06802648aae1791dc0d91668e6e231e223d6dc4a69369b344d8