Clinical care · VERSION 3dfb7c9f

Copy a reported medication statement into a new demonstration prescription

Inspect the source reported statement, copy it into a fresh Doctor request, enter separate prescribing fields and notes, then verify the new prescription and unchanged source after reload.

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.

Saved new prescription card in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:26:04.083Z · 1728 × 921**
Saved new prescription card
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `8c9056874cbac6dbb67cc974e0a165084b9bb1737a51fc032405170ded8fb2c6`
**Select the new 20/10/2026 12:25 PM card**: This is the newly created prescription, separate from the older 10:55 AM source prescription.
**Read the Doctor prescriber**: The saved card identifies MANSOQ E2E Doctor.
**Read the complete shared prescription Note**: The software-only shared Note is above the medicine table.
**Read count, QD and one day**: The saved structured instruction is 1.00 count, QD (Once a day), 1 day.
**Read the complete row note**: The Instructions cell retains the DEMO RECONCILIATION note copied from the statement.

19 of 19 content blocks have reviewed image alignment.

Before you begin

Use an authorised Doctor account, the assigned fictional patient and the intended ongoing encounter. This example uses the synthetic Inpatient encounter shown.
1234
Recorded release 3dfb7c9f · 2026-10-20T09:18:45.831Z · 1728 × 921
Doctor identity
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 d414ce48df010e64341de3c2e46ae41e468799d9c4caa69b1dca08330adf4be8
1. Check the Doctor account: The open account menu identifies MANSOQ E2E Doctor and qa-doctor.
2. Check the fictional patient: Use the assigned synthetic patient, not a real patient record.
3. Check the selected In Progress encounter: The selected Inpatient encounter remains ongoing.
4. Open Medicines: The prescribing and reported-statement tabs are separate within Medicines.
12345
Recorded release 3dfb7c9f · 2026-10-20T09:19:33.217Z · 1728 × 921
Source statement table
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 d34d76501a793fe1083c410880972e192d523057fbada38c816e48bd83360892
1. Select Medication Statements: Read the saved reported statement separately from Prescriptions.
2. Read the reported dosage text: This free text is reported information, not a new prescription dosage.
3. Read the reported period: Both local dates are 20/10/2026.
4. Read Logged by MANSOQ E2E Nurse: The Nurse is the saved statement author.
5. Open See Note: Inspect the source statement note before copying.
The illustrated Nurse-reported HYMOX statement already exists with its fictional dosage text, local 20 October period and reconciliation note. Copying reported information does not establish a prescribing decision or verify medication taking.
12345
Recorded release 3dfb7c9f · 2026-10-20T09:19:33.217Z · 1728 × 921
Source statement table
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 d34d76501a793fe1083c410880972e192d523057fbada38c816e48bd83360892
1. Select Medication Statements: Read the saved reported statement separately from Prescriptions.
2. Read the reported dosage text: This free text is reported information, not a new prescription dosage.
3. Read the reported period: Both local dates are 20/10/2026.
4. Read Logged by MANSOQ E2E Nurse: The Nurse is the saved statement author.
5. Open See Note: Inspect the source statement note before copying.
12
Recorded release 3dfb7c9f · 2026-10-20T09:19:42.223Z · 1728 × 921
Source statement note
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 9a89f21dfd4312afb3489e77819627472e408d80bd27126f167cf303e6a67f85
1. Locate the source See Note control: This popover belongs to the reported statement.
2. Read the complete source note: The DEMO RECONCILIATION note is the text carried into the new medication row.
1234567
Recorded release 3dfb7c9f · 2026-10-20T09:20:37.061Z · 1728 × 921
Statement history zero selection
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 6e970863864eae93db4da31a53b2ad2cc4b21f661be6d60d8479bf6c90111870
1. Select Medication Statements in history: Use this history tab rather than Past Prescriptions.
2. Read the 20 Oct, 2026 group: The statement is grouped by its creation day.
3. Identify HYMOX 500MG CAPS: Match the medicine to the reported statement you inspected.
4. Read the source reported text: It describes the earlier software exercise, not a new prescribing instruction.
5. Read the Nurse author under Prescribed by: In this Medication Statements tab the heading is Prescribed by, but the name shown is the statement creator, MANSOQ E2E Nurse.
6. Open the source row information: Expand the information icon to read its note.
7. Check zero selected: Before selection, the counter reads 0 Medication Statements Selected and Add Selected is disabled.
All entered dose, frequency, duration and notes are fictional software-training values. Do not dispense or administer them. Create a new request; do not edit the earlier source prescription or reported statement.
123
Recorded release 3dfb7c9f · 2026-10-20T09:25:37.514Z · 1728 × 921
Review before single submit
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 94fc3aa23ad734c8afb9e72081d26f0eba6ac79682b91806d187bde4dba68277
1. Keep the copied row Note: The row note still contains the source reconciliation text.
2. Enter the separate shared prescription Note: The complete software-only text below the table has a different scope from the row note.
3. Choose Submit once after reviewing the new request: This saves the new Doctor prescription, not the Nurse source statement.
12345
Recorded release 3dfb7c9f · 2026-10-20T09:26:04.083Z · 1728 × 921
Saved new prescription card
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 8c9056874cbac6dbb67cc974e0a165084b9bb1737a51fc032405170ded8fb2c6
1. Select the new 20/10/2026 12:25 PM card: This is the newly created prescription, separate from the older 10:55 AM source prescription.
2. Read the Doctor prescriber: The saved card identifies MANSOQ E2E Doctor.
3. Read the complete shared prescription Note: The software-only shared Note is above the medicine table.
4. Read count, QD and one day: The saved structured instruction is 1.00 count, QD (Once a day), 1 day.
5. Read the complete row note: The Instructions cell retains the DEMO RECONCILIATION note copied from the statement.

1. Inspect the reported source and its note

In the selected encounter open Medicines, then Medication Statements. Read the HYMOX 500MG CAPS row, its complete reported Dosage text, Active software status, local 20/10/2026 – 20/10/2026 period, Reason and Logged by MANSOQ E2E Nurse. Select See Note and read the full DEMO RECONCILIATION text. Close the popover before continuing.

Doctor identity in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:18:45.831Z · 1728 × 921**
Doctor identity
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `d414ce48df010e64341de3c2e46ae41e468799d9c4caa69b1dca08330adf4be8`
**Check the Doctor account**: The open account menu identifies MANSOQ E2E Doctor and qa-doctor.
**Check the fictional patient**: Use the assigned synthetic patient, not a real patient record.
**Check the selected In Progress encounter**: The selected Inpatient encounter remains ongoing.
**Open Medicines**: The prescribing and reported-statement tabs are separate within Medicines.

Source statement table in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:19:33.217Z · 1728 × 921**
Source statement table
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `d34d76501a793fe1083c410880972e192d523057fbada38c816e48bd83360892`
**Select Medication Statements**: Read the saved reported statement separately from Prescriptions.
**Read the reported dosage text**: This free text is reported information, not a new prescription dosage.
**Read the reported period**: Both local dates are 20/10/2026.
**Read Logged by MANSOQ E2E Nurse**: The Nurse is the saved statement author.
**Open See Note**: Inspect the source statement note before copying.

Source statement note in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:19:42.223Z · 1728 × 921**
Source statement note
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `9a89f21dfd4312afb3489e77819627472e408d80bd27126f167cf303e6a67f85`
**Locate the source See Note control**: This popover belongs to the reported statement.
**Read the complete source note**: The DEMO RECONCILIATION note is the text carried into the new medication row.

2. Create a new request and open history

Select Prescriptions, then Create. Use the fresh empty Medication Request rather than an earlier prescription card’s Edit control. Select Medication History, then the Medication Statements tab in the drawer.

New request entry in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:19:56.946Z · 1728 × 921**
New request entry
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `03df32e5f50fa03ab1ea1a27d0fcc15d5f69e192c620393d7486dc0e0a2b0c8a`
**Select Prescriptions**: Return to the prescribing tab, without editing the earlier prescription cards.
**Choose Create**: Open a fresh Medication Request instead of an existing card’s Edit control.

Empty new request in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:20:16.393Z · 1728 × 921**
Empty new request
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `23c2b1feea5944c2a6b87cc37691cb09e3ebe4044657137e648116cf7ac8d8ac`
**Open Medication History**: The new request is empty; use history to choose a source statement.
**Check the new request is empty**: No medicine row has been added yet.

Statement history zero selection in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:20:37.061Z · 1728 × 921**
Statement history zero selection
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `6e970863864eae93db4da31a53b2ad2cc4b21f661be6d60d8479bf6c90111870`
**Select Medication Statements in history**: Use this history tab rather than Past Prescriptions.
**Read the 20 Oct, 2026 group**: The statement is grouped by its creation day.
**Identify HYMOX 500MG CAPS**: Match the medicine to the reported statement you inspected.
**Read the source reported text**: It describes the earlier software exercise, not a new prescribing instruction.
**Read the Nurse author under Prescribed by**: In this Medication Statements tab the heading is Prescribed by, but the name shown is the statement creator, MANSOQ E2E Nurse.
**Open the source row information**: Expand the information icon to read its note.
**Check zero selected**: Before selection, the counter reads 0 Medication Statements Selected and Add Selected is disabled.

3. Read the statement before selecting it

In the 20 Oct, 2026 group identify the illustrated HYMOX statement and read its reported text and Active status. The column is labelled Prescribed by, but in this Medication Statements tab it shows the statement creator, MANSOQ E2E Nurse. Do not interpret that label as a Nurse prescription. Open the information icon to read the complete note. Before selection the counter is 0 and Add Selected is disabled.

Statement history source note in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:20:45.045Z · 1728 × 921**
Statement history source note
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `3d323094430250f0c7610c3f2fd3a782732771c25751c1c4b4164c33aa642669`
**Read the full source note in history**: This is the same DEMO RECONCILIATION note shown in the statement table.
**Select only the illustrated statement row**: Use its individual row checkbox; this example has one source row.

4. Select one statement and add a draft row

Select only the illustrated row checkbox and check 1 Medication Statements Selected. Because this example has one row, the group checkbox also appears selected. Choose Add Selected once. This adds an unsaved medicine request row; it does not save a prescription or change the original statement.

One statement selected in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:20:53.876Z · 1728 × 921**
One statement selected
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `cb85890545d7b33ce2043c611e78da5251a82b59e7005a8729fe930d08aac4ca`
**Check the selected source row**: Only the illustrated HYMOX statement is selected.
**Check one selected statement**: The counter reads 1 Medication Statements Selected.
**Choose Add Selected once**: This creates a new unsaved request row; it does not submit a prescription.

Fresh imported request draft in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:21:14.767Z · 1728 × 921**
Fresh imported request draft
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `3836b729963565cde8d2f023e98d259ab11f6dee384aa3f1ad4307dff67b5a8a`
**Inspect the blank Dosage**: The statement’s reported dosage text has not filled a prescribing dose.
**Inspect the blank Frequency**: A structured frequency still needs to be chosen.
**Inspect the blank Duration**: The reported period has not filled a prescribing duration.
**Read the copied row Note**: The narrow input shows the beginning of the retained source note; the full saved Instructions cell provides readback.
**Inspect the empty shared Note**: This separate prescription-level Note starts blank.
**Expand the advanced columns**: Use this header control, then scroll the medication table right to review the new request metadata.

5. Check the fresh prescribing fields

The copied row retains the medicine and its reconciliation Note. Dosage, Frequency and Duration are initially blank; the reported free text and period were not converted into prescribing instructions. The shared Note below the table also starts empty. Review what was copied before entering the separate prescribing fields.

6. Check the new requester and authored date

Expand the table’s advanced columns using the header control, then scroll the table horizontally right. Check Order, October 20th, 2026 and requester MANSOQ E2E Doctor. These belong to the new request, separately from the Nurse source statement and its reported-use period. Scroll left and collapse the advanced columns using the same header control illustrated in the earlier draft view.

Settled fresh doctor requester date in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:24:42.526Z · 1728 × 921**
Settled fresh doctor requester date
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `1797414baea85124c225f7e819d4be5c5c250d96bc36e01aa7384e3260a6a89b`
**Review the new Order intent**: This is a new medication request, not a change to the source reported statement.
**Review the new authored date**: The fresh draft shows October 20th, 2026, separately from the source reported-use period.
**Review the Doctor requester**: MANSOQ E2E Doctor is the new requester, distinct from the Nurse statement author.
**Scroll the table back to the left**: Use the horizontal table scrollbar to return to Dosage and Frequency, then collapse the advanced columns with the same header control shown in the earlier draft view.

7. Enter the fictional quantity with an explicit unit

In Dosage enter 1. The selector initially suggests tablets; choose the visible 1 count option explicitly for this software example. Do not infer the unit from the number alone.

Dose count choice in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:25:04.265Z · 1728 × 921**
Dose count choice
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `baa652ca8b72bd9d1b5e51501ad330e1cc2cc0d6c307ca1c731ca7577d58a7b5`
**Enter the fictional quantity 1**: Entering the number initially suggests tablets; choose the unit explicitly.
**Choose 1 count**: For this software-only exercise select count, not the initial tablets suggestion.

Selected count qd one day in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:25:32.366Z · 1728 × 921**
Selected count qd one day
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `73054a6bc5dca837089f5647babd25e5d603d48ff55ee6cedb508a067c8c8544`
**Review 1 count**: The count unit is now explicit.
**Review QD (Once a day)**: Frequency was selected independently of the reported statement text.
**Review the preset 1 day**: The QD preset supplied this duration; review it as a separate prescribing field.

8. Choose a separate frequency and review duration

Open Frequency, search QD and choose QD (Once a day). Review the selected 1 count, QD and preset 1 day duration in the current row. The frequency preset supplies this initial duration; it was not imported from the reported statement’s dates. These values are fictional interface examples.

Frequency search qd in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:25:13.301Z · 1728 × 921**
Frequency search qd
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `949604a3358b26361072ad18d3dfa7a43efae1651847f8b5139836ce754aab10`
**Open Frequency**: This actual current medicine row has its Frequency selector open.
**Search QD**: The frequency search contains QD.
**Choose QD (Once a day)**: Choose the visible QD result for this fictional interface example.

9. Keep the copied note and enter a separate shared note

Keep the row Note unchanged: DEMO RECONCILIATION — fictional reported-use example. Do not dispense or administer. Reconcile reported dosage and period separately. The narrow field clips this text; the saved Instructions cell later shows it in full. In the shared Note below the table enter: SYNTHETIC SOFTWARE TRAINING ONLY — medication statement to new prescription interface demonstration. The source reported information is not an approved prescribing instruction. All example values are fictional; do not dispense or administer. Read the two notes in their separate scopes.

Review before single submit in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:25:37.514Z · 1728 × 921**
Review before single submit
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `94fc3aa23ad734c8afb9e72081d26f0eba6ac79682b91806d187bde4dba68277`
**Keep the copied row Note**: The row note still contains the source reconciliation text.
**Enter the separate shared prescription Note**: The complete software-only text below the table has a different scope from the row note.
**Choose Submit once after reviewing the new request**: This saves the new Doctor prescription, not the Nurse source statement.

10. Review and submit the new prescription once

Review the one HYMOX row, explicit 1 count, QD, 1 day, Doctor requester and both note scopes. Choose Submit once and wait for the return to Overview. Open Medicines, keep Prescriptions selected and select the new 20/10/2026 12:25 PM card. This is separate from the earlier 10:55 AM prescription.

Returned overview after one submit in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:25:56.506Z · 1728 × 921**
Returned overview after one submit
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `b1dd1e75496c9c59e92486a3125b6997138eacd4e9832f6bd04f41a5d394588b`
**Open Medicines after the return**: Wait for the form to return to Overview before opening the saved result. No success-toast is pictured here.

11. Read the saved result and verify it after reload

Read the Doctor prescriber, complete shared Note, 1.00 count, QD (Once a day), 1 day and complete copied note in Instructions. Use the browser’s Reload command once, wait for Medicines to load and select the same 12:25 PM card again. Check the same saved contents. Do not repeat Submit to refresh the display.

Reloaded same new prescription in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:26:37.850Z · 1728 × 921**
Reloaded same new prescription
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `8c9056874cbac6dbb67cc974e0a165084b9bb1737a51fc032405170ded8fb2c6`
**Reselect the same card after browser Reload**: The 12:25 PM prescription remains after one normal browser reload.
**Recheck both saved note scopes**: The shared Note remains above the table and the copied row note remains in Instructions.
**Select Medication Statements to recheck the source**: This separate tab returns to the original reported statement without editing it.

12. Recheck the original reported statement

Select Medication Statements. Read the original Nurse-reported row again: its free-text Dosage, Active status, local 20/10/2026 – 20/10/2026 dates, Reason and Nurse author remain. Open See Note and read its original full reconciliation text. The new Doctor prescription and this reported statement remain separate records.

Original nurse statement retained in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:26:43.455Z · 1728 × 921**
Original nurse statement retained
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `d34d76501a793fe1083c410880972e192d523057fbada38c816e48bd83360892`
**Recheck the original reported dosage text**: The Nurse’s complete reported text remains unchanged.
**Recheck the local reported dates**: The source still shows 20/10/2026 – 20/10/2026.
**Recheck the Nurse author**: Logged by remains MANSOQ E2E Nurse.
**Open the retained source See Note**: Read the original statement’s note without changing it.

Original nurse note retained in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:26:43.865Z · 1728 × 921**
Original nurse note retained
Capture details
Observed 3dfb software on 20 October 2026. One new Doctor prescription copied from a reported medication statement; all prescribing values are fictional software examples. Original pixels and capture times preserved.
Image SHA-256 `9a89f21dfd4312afb3489e77819627472e408d80bd27126f167cf303e6a67f85`
**Read the unchanged source note**: The original statement retains its full DEMO RECONCILIATION note after the separate new prescription was saved.

Copying is a starting point, not a prescribing decision

The history action carries the coded medicine and row Note into a fresh request. It does not carry the statement’s reported dosage text, period, information-source choice, Reason or author into prescribing fields. Review the source, then enter the new prescription’s required dose and frequency separately. This demonstration gives no treatment or medication-taking advice.

Keep authors, dates and note scopes distinct

The source table’s Logged by Nurse and the history drawer’s Prescribed by Nurse identify the statement creator in these views. The fresh request instead shows the Doctor requester and a new authored date. Its saved prescription card displays its creation time, 12:25 PM. The copied row note appears under Instructions; the separate shared Note appears above the saved table.

Verify a new prescription without replacing the source

The saved new 12:25 PM card persists after reload, while the original reported statement and complete Note remain available in their own tab. This lesson creates one new synthetic prescription and does not edit the earlier prescription, rewrite the Nurse statement, dispense or administer anything.

Source evidence

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

repositories/platform/mansoq-core/mansoq/emr/resources/medication/statement/spec.py:25 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
542258fe317d93cd03fc4b0efe7fe5704069be9e99e172a63ece6d39f6f2920e
repositories/platform/mansoq-web/src/components/HistoricalRecordSelector/index.tsx:119 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
0ab03afa6a5954112061e0bf07b15cd3f4c901444f3c3de8a8e194524ef1f0c2
repositories/platform/mansoq-web/src/components/Patient/MedicationStatementList.tsx:39 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
4dd254b2d7ab8c46c4178ec9962ed631b863a602450378050dc329bbac82a1e5
repositories/platform/mansoq-web/src/components/Patient/MedicationStatementTable.tsx:61 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
24093db90d546211a702299533d012a8c28883c7ac936971c6fde01a1b8bce21
repositories/platform/mansoq-web/src/components/Questionnaire/MedicationValueSetSelect.tsx:318 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
bb8d5d5f1595778be9e9ad260296e8f43e5696fe9d19fb608e27a33a6a739610
repositories/platform/mansoq-web/src/components/Questionnaire/QuestionTypes/MedicationRequestQuestion.tsx:674 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
561259e73b1752c9844e31b798ad676878af5f4caf6be5fbd130cd31fcfc89cc
repositories/platform/mansoq-web/src/components/Questionnaire/QuestionTypes/MedicationStatementQuestion.tsx:91 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
aa6bfad3dcb6e4315c58908fe9fffdc4ea47cb84f8c2596cb3db30fe640c19d7
repositories/platform/mansoq-web/src/components/Questionnaire/QuestionnaireForm.tsx:421 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
ee6c2195f13e48f0896a2d3da566c2f2a67910adad08894df6b77862f9cfdeec
repositories/platform/mansoq-web/src/components/Questionnaire/ValueSetSearchContent.tsx:118 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
d6adc1b84f5956cd554042aa8579a0a83b9a13c5337c64bd0ee6b7f9af5b8019
repositories/platform/mansoq-web/src/components/Questionnaire/structured/handlers.ts:65 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
459ade48f77316279ab2978dc7b4466cb96acb8223c61b9a1f87ca9973be7c7f
repositories/platform/mansoq-web/src/types/emr/medicationRequest/medicationRequest.ts:977 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
a39df63f9b7f2d976d4379511d7a2d4c8e3e284fd1e9b67c28e59392e8545b2b
repositories/platform/mansoq-web/src/types/emr/medicationStatement.ts:7 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
5784010754caa19b544f2db2f1a374d7739d76518159a239b73a3a8c9fb5a091