Clinical care · VERSION 3dfb7c9f

Practise dose-range Save and Clear, then submit and verify one prescription

Continue the same two-instruction draft through a temporary dose range, Clear, quantity restoration, extra-step removal, advanced-field review, one Submit and saved readback 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.

Exact saved prescription in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:27:24.955Z · 1728 × 921**
Exact saved prescription
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `9132d07574c6f90753cbce21de324006df741a821e21038daa749467fa557db7`
**Verify the selected new prescription**: The selected card is 20/10/2026 10:26 AM.
**Read the prescriber**: The detail header names MANSOQ E2E Doctor.
**Read the complete shared note**: The note explicitly identifies fictional software controls and says not to dispense or administer.
**Read first saved dose 1.00 count**: The temporary dose range was cleared and restored before submission.
**Read first saved QD**: Frequency is shown separately from dose.
**Read the saved 2–3 days**: The first duration is a range of days.
**Read second saved dose 2.00 count**: The second instruction is a separate row.
**Read October 21, 2026 → October 22, 2026**: The saved summary shows the full fixed-date range.
**Locate Edit for later inspection**: Use this only after checking the normal reload in the next step.

17 of 17 content blocks have reviewed image alignment.

Before you begin

Continue the same unsaved draft from Build two dosage instructions with different duration controls. It contains the synthetic product, two QD instructions, the 2–3 day range, fixed October 21–22 dates and the shared software-only note.
12
Recorded release 3dfb7c9f · 2026-10-20T07:22:14.582Z · 1728 × 921
Two duration bound types
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 b9e9e897509764c86a8abb3311a6c2eb2e91e23207d8c018ab54a40d65b274be
1. Review the first duration type: The first instruction remains a 2–3 day range.
2. Review the second duration type: The second instruction is a fixed-date range; the end is clipped here, so use the full calendar or saved summary to read it.
Use the assigned fictional patient and intended ongoing encounter. Only the ordinary Doctor prescribing flow is demonstrated. All quantities, frequency and dates are interface examples; do not dispense or administer them.
123
Recorded release 3dfb7c9f · 2026-10-20T07:17:32.402Z · 1728 × 921
Overview entry
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 d650b8a5d767db16ce75c818083ab54347162e3ea678ff47df31c4a30f30df0c
1. Verify the fictional patient: Check the synthetic patient banner before opening the form.
2. Verify the selected ongoing encounter: The selected Inpatient encounter is In Progress.
3. Open Add Medication: Use this encounter action to open Medication Request.
123456
Recorded release 3dfb7c9f · 2026-10-20T07:26:18.423Z · 1728 × 921
Final two step submit review
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 d4e7bfd35b46657eefa26f996706fe47d39e0779bdec15847cf6de7a92dcad47
1. Review final first dose: The saved example will use the restored 1 count, not the temporary range.
2. Review final second dose: The second instruction remains 2 count.
3. Check first-step QD: Check frequency independently on both lines.
4. Check the 2–3 day duration: The first line uses a range of days.
5. Read the complete software-only note: Review the shared prescription note before submission.
6. Choose Submit once: This saves the reviewed prescription; it is distinct from earlier popup Save and Done.
Popup Save and Done update the draft. The whole prescription is saved only by the final Submit. After that save, use the new prescription card for inspection rather than creating or submitting a second copy.
123
Recorded release 3dfb7c9f · 2026-10-20T07:22:43.293Z · 1728 × 921
Range popup review
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 c87f9521a03622caad8ba17ba561914aef49c6cf840bf9d85dc95c1a70ec86a7
1. Check Start Dose 1 count: Review the first endpoint.
2. Check End Dose 2 count: Review the second endpoint.
3. Choose popup Save: Apply the range to the draft instruction.
123456
Recorded release 3dfb7c9f · 2026-10-20T07:26:18.423Z · 1728 × 921
Final two step submit review
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 d4e7bfd35b46657eefa26f996706fe47d39e0779bdec15847cf6de7a92dcad47
1. Review final first dose: The saved example will use the restored 1 count, not the temporary range.
2. Review final second dose: The second instruction remains 2 count.
3. Check first-step QD: Check frequency independently on both lines.
4. Check the 2–3 day duration: The first line uses a range of days.
5. Read the complete software-only note: Review the shared prescription note before submission.
6. Choose Submit once: This saves the reviewed prescription; it is distinct from earlier popup Save and Done.
123456789
Recorded release 3dfb7c9f · 2026-10-20T07:27:24.955Z · 1728 × 921
Exact saved prescription
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 9132d07574c6f90753cbce21de324006df741a821e21038daa749467fa557db7
1. Verify the selected new prescription: The selected card is 20/10/2026 10:26 AM.
2. Read the prescriber: The detail header names MANSOQ E2E Doctor.
3. Read the complete shared note: The note explicitly identifies fictional software controls and says not to dispense or administer.
4. Read first saved dose 1.00 count: The temporary dose range was cleared and restored before submission.
5. Read first saved QD: Frequency is shown separately from dose.
6. Read the saved 2–3 days: The first duration is a range of days.
7. Read second saved dose 2.00 count: The second instruction is a separate row.
8. Read October 21, 2026 → October 22, 2026: The saved summary shows the full fixed-date range.
9. Locate Edit for later inspection: Use this only after checking the normal reload in the next step.

1. Open the first dose’s range editor

On the first dosage line select the pipette beside 1 count. The Taper & Titrate Dosage popup opens with Start Dose 1 count and End Dose 1 count. In this release opening the popup already converts the quantity to an equal-endpoint range in the draft. The popup title does not make these fictional values a clinical taper plan.

Two duration bound types in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:22:14.582Z · 1728 × 921**
Two duration bound types
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `b9e9e897509764c86a8abb3311a6c2eb2e91e23207d8c018ab54a40d65b274be`
**Review the first duration type**: The first instruction remains a 2–3 day range.
**Review the second duration type**: The second instruction is a fixed-date range; the end is clipped here, so use the full calendar or saved summary to read it.

Pipette range editor in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:22:25.674Z · 1728 × 921**
Pipette range editor
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `72a7627bd208f2b3a41629735769106e55ea1848dfa857f0dc989ab33cafe53e`
**Open the first-step pipette**: This earlier quantity is converted to a range in the draft when the popup opens.
**Read Start Dose 1 count**: The popup is initially seeded from the existing single quantity.
**Read End Dose 1 count**: The initial range has equal endpoints before you change the end.
**Locate popup Save**: This applies dose-range popup values to the draft, not the entire prescription.

2. Apply a temporary 1-to-2 count range

Keep Start Dose 1 count. Enter 2 in End Dose and explicitly select 2 count. Review both endpoints, then choose the popup Save. The first line now shows 1.00 → 2.00 count. This has changed the draft only; do not select the form’s Submit yet.

Range end unit options in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:22:35.823Z · 1728 × 921**
Range end unit options
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `0be43d01d931f2ff541964aa3298f30aa02a09a7e1314828ad7495d855f7fda3`
**Enter End Dose 2**: Edit the End Dose field in the popup.
**Choose 2 count for End Dose**: Select the count option explicitly; Start Dose remains 1 count.

Range applied draft in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:23:20.551Z · 1728 × 921**
Range applied draft
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `d521102fad90406439c3db0188f3c14264013497526fd9943afd3957c8279a3c`
**Read the applied 1.00 → 2.00 count range**: This is a temporary draft dose-range exercise.
**Reopen the range popup**: Use the pipette again to inspect or clear it.

3. Reopen and clear the temporary dose range

Use the first line’s pipette again. Check that Start Dose is 1 count and End Dose is 2 count, then choose Clear. The first dosage field becomes empty. QD and the 2–3 day duration remain. Clear removes the dose value; it does not restore the old single quantity.

Reopened dose range clear in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:23:30.368Z · 1728 × 921**
Reopened dose range clear
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `c43dec666d39f37555be031a8fb20a9b802bed99d1636754351f062352ba54cb`
**Read the reopened Start Dose**: The applied range is retained in the popup.
**Read the reopened End Dose**: The end remains 2 count.
**Choose Clear**: Clear removes the entire dose value; it does not restore the previous single quantity.

Clear leaves dose empty in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:23:38.162Z · 1728 × 921**
Clear leaves dose empty
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `5fb5eddd832e8ee4d9f5850dbd8fee8bcb29b18176c96a13026e462bd48532c8`
**Observe the empty first dose**: Clear has left the first dosage input blank.
**Check retained first frequency**: QD remains despite clearing the dose.
**Check retained first duration**: The 2–3 day range remains.
**Restore 1 count before continuing**: Enter 1 again and explicitly retain count; the next view shows the restored quantity.
**Locate the add-step plus before the extra line**: After restoring the first dose to 1 count, use this plus to add the extra empty instruction. This earlier clear-state view shows the same control before that addition.

4. Restore the single dose and remove an extra empty step

Enter 1 in the now-empty first Dosage field and explicitly retain count. Use the small plus beneath the product once more to add a third empty instruction. Select that third line’s trash icon to remove only the empty step. Check that exactly the two intended instructions remain. Do not use the product action menu at the far right.

Third empty dosage step in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:24:07.677Z · 1728 × 921**
Third empty dosage step
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `a711f990c1b44647b627cf67c16ca558a0b5254753abeb975dd5cac15ba7c5a2`
**Verify restored 1 count**: The first instruction is restored to a single quantity.
**Locate the step plus**: The same plus has added a third empty instruction for this exercise.
**Remove only the third empty step**: Use this blank line’s trash control, not the product action menu at the right.

Two steps after removal in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:24:56.232Z · 1728 × 921**
Two steps after removal
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `8211883f8758d42b5742e259cd858c3b70944cefcd8a7b94d215e0045c43eff7`
**Verify the first remaining instruction**: First dose is 1 count with QD and a 2–3 day range.
**Verify the second remaining instruction**: Second dose is 2 count with QD and fixed dates.
**Expand advanced columns**: Use the header chevrons to reveal additional fields.

5. Expand and read the advanced request fields

Select the table header’s chevrons to expand the advanced columns. Scroll the table horizontally to the right. Review Intent Order, Authored On October 20th, 2026 and Requester MANSOQ E2E Doctor without changing them. The right-scrolled picture is a separate view of the same draft. Scroll back left and use the header chevrons, illustrated in the earlier left view, to collapse the advanced columns.

Expand advanced fields in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:25:03.137Z · 1728 × 921**
Expand advanced fields
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `31f03f417d243aff9679fa82d29754c32cb95591d43b3af22fc4a648ee7adaba`
**Locate the header chevrons**: The header control expands or collapses advanced columns.
**Read the advanced instruction column**: Additional columns are visible in this left view.
**Scroll the table horizontally to the right**: Use a horizontal scroll within the table to reach Requester and Authored On; this is a separate view, not a stitched image.

Advanced requester authored date in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:25:34.609Z · 1728 × 921**
Advanced requester authored date
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `58e5ac21b170c319d5afd72164010312129450c255dc7b533b941a48cf0f1580`
**Read Intent Order**: The request intent is Order in this example.
**Review Authored On October 20th, 2026**: Review this displayed date without changing it.
**Review Requester MANSOQ E2E Doctor**: Verify the intended prescriber before the final submission.
**Scroll back to the dosage columns**: Return left within this table, then use the earlier header chevron reference to collapse the advanced columns.

Final two step submit review in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:26:18.423Z · 1728 × 921**
Final two step submit review
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `d4e7bfd35b46657eefa26f996706fe47d39e0779bdec15847cf6de7a92dcad47`
**Review final first dose**: The saved example will use the restored 1 count, not the temporary range.
**Review final second dose**: The second instruction remains 2 count.
**Check first-step QD**: Check frequency independently on both lines.
**Check the 2–3 day duration**: The first line uses a range of days.
**Read the complete software-only note**: Review the shared prescription note before submission.
**Choose Submit once**: This saves the reviewed prescription; it is distinct from earlier popup Save and Done.

6. Review the final draft and Submit once

Review the restored first dose 1 count with QD and 2–3 days, and the second dose 2 count with QD and fixed October 21–22 dates. Use the earlier full calendar picture to check both fixed dates because the draft cell clips its end. Recheck the shared software-only note and the reviewed requester. Select the form’s Submit once, then wait for the return to Overview.

Fixed date range pending done in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:20:44.213Z · 1728 × 921**
Fixed date range pending done
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `a123506108c6a0667893b5d60d66b2c35259df02be65b523abf6560c74128fce`
**Read the selected October 21 start**: The calendar shows the start of the selected fixed range.
**Read the selected October 22 end**: The full calendar makes both dates visible.
**Choose Done for fixed dates**: Apply the selected calendar range to the second draft instruction.

Returned overview after submit in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:26:39.209Z · 1728 × 921**
Returned overview after submit
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `82d7901359080bd9bf1f8bcfddc0c959711bda5219446cc9f957d0f5c9a87259`
**Open Medicines after returning**: Wait for the return to Overview, then use Medicines to inspect the saved prescription.
**Verify the same encounter**: The selected Inpatient encounter remains In Progress.

7. Select the newly saved prescription

On the returned Overview select Medicines, keep Prescriptions selected, and inspect All Prescriptions. Select the new 20/10/2026 10:26 AM card prescribed by MANSOQ E2E Doctor. The older cards below are separate prescriptions. The selected card shows the shared note and both saved dosage instructions.

All prescriptions saved two steps in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:27:03.628Z · 1728 × 921**
All prescriptions saved two steps
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `e096e039e94ac67f8658c70ad011f2cf09d39b896a81ea7c979e47d2fb8b6e0a`
**Keep Prescriptions selected**: Medicines opens the prescriptions area in this flow.
**Read All Prescriptions**: This combines entries from separate saved prescription cards.
**Select the new 20/10/2026 10:26 AM card**: Choose the exact new card, not an older prescription below.
**Read the two saved instruction rows**: The new product has two dosage lines; older entries remain separate below.

8. Reload and verify the same saved values

Use the browser’s Reload command once and wait for Medicines to load. Reselect the same 20/10/2026 10:26 AM prescription. Check 1.00 count / QD / 2–3 days on the first line and 2.00 count / QD / October 21, 2026 → October 22, 2026 on the second. Read the complete software-only note and Doctor prescriber. The temporary dose range is not the saved first dose.

Saved prescription after reload in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:28:09.939Z · 1728 × 921**
Saved prescription after reload
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `9132d07574c6f90753cbce21de324006df741a821e21038daa749467fa557db7`
**Reselect the same card after browser Reload**: The same 10:26 AM prescription is selected after the ordinary reload.
**Verify the full fixed-date range again**: Both dates remain visible after the reload.
**Choose Edit to inspect saved fields**: Open the saved prescription without changing it.

9. Inspect the saved fields through Edit

From that same selected prescription choose Edit. Read the two saved instructions. In this release the saved dosage, frequency and duration controls are disabled, and the shared prescription note is read-only. Do not force a value into them or submit this inspection. Choose Cancel.

Reopened saved two step fields in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:28:25.489Z · 1728 × 921**
Reopened saved two step fields
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `c8cc86f1718ddfc71850d2069fac7db5e9e96f4113dd28d9efb28857c37f18fa`
**Read the disabled first dose**: Saved dosage fields are disabled in this release.
**Read the disabled first frequency**: This inspection does not make a new draft prescription.
**Read the disabled fixed-date duration**: Its end remains clipped in the input; the saved detail view provides both dates.
**Read the disabled shared note**: The prescription note is also read-only here.
**Choose Cancel after unchanged inspection**: The actual app asks for leave confirmation even after this unchanged inspection.

10. Leave through the actual confirmation and recheck the card

After Cancel, this app can show You have unsaved changes. Are you sure you want to leave? even after the unchanged saved-field inspection. Cancel in that browser dialog keeps the editor open; choose the right-hand OK button to leave. The picture shows the actual Chrome confirmation; the pointer partly covers the OK label. After leaving, verify the same saved card and both instructions. No second Submit is needed.

Native Chrome unsaved-change confirmation in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:29:58.102Z · 896 × 328**
Native Chrome unsaved-change confirmation
Native macOS confirmation dialog, shown in its original proportions.
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `cb3505584902efcbadf95b26cc9b35e96492d832899a82b8e6fad5094b9865a7`
**Read the unsaved-change confirmation**: This is Chrome’s leave confirmation for the medication form.
**Locate Cancel to stay**: Cancel would keep the editor open; it was not selected in this captured exit.
**Choose the right-hand OK button to leave**: The pointer partly covers its label in this image; the accompanying native accessibility text identifies OK.

Final prescription after cancel confirmations in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:33:17.635Z · 1728 × 921**
Final prescription after cancel confirmations
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `80debe6083552f5502ee663b1b12b790804522ff7d68725b126ab49c13160ea2`
**Verify the same saved card after leaving**: The same 10:26 AM prescription remains selected.
**Recheck 1.00 count**: The unchanged inspection did not replace the first instruction.
**Recheck both full fixed dates**: The second instruction and its dates remain retained.
**Recheck the retained software-only note**: Leaving through the browser confirmation did not submit a second prescription.

Different save controls have different scope

The range popup’s Save applies its endpoints to the draft; Clear removes the dose; duration Done applies that duration. None of those controls is the form’s final Submit. This walkthrough saves one new prescription only after restoring the first dose to 1 count and removing the extra empty step.

Valid day range pending done in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:20:17.602Z · 1728 × 921**
Valid day range pending done
Capture details
Observed committed 3dfb software on 20 October 2026. Software-only examples; no dispensing or administration. Original pixels and actual capture times retained.
Image SHA-256 `0e8c288fd805264ba301801a9a71f391080add308c955d99fc971c86186834ce`
**Set Start to 2**: Replace the deliberate invalid start with 2.
**Set End to 3**: The explanatory line below confirms Between 2 and 3 days.
**Keep days as the unit**: Check the range unit before applying it.
**Choose Done**: Done applies the duration to this draft dosage step; it does not submit the prescription.

Read complete dates and the correct note

The narrow draft and Edit inputs clip the fixed end date. The calendar and selected saved prescription show the full October 21–22 range. The complete software-only text is in the shared prescription Note, not the separate blank product Note cell. These fictional controls do not establish a treatment sequence or authorise dispensing or administration.

Understand the leave confirmation

The compact Chrome confirmation belongs to an unchanged saved-field inspection. Its warning does not, by itself, mean that the disabled dosage controls were edited. Leave through OK and check the same saved prescription afterward. This exit does not submit another order.

Source evidence

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

repositories/platform/mansoq-core/mansoq/emr/api/viewsets/base.py:98 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
6a287dd315b8a4957b29c58e4bbc1bef7b8d9d257f9149f93045ff0adbdcae6c
repositories/platform/mansoq-core/mansoq/emr/api/viewsets/medication_request.py:39 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
a3f3ae8042fb8134112c5d04fe8b060e68bce11dae682d138aafaae64119c215
repositories/platform/mansoq-core/mansoq/emr/resources/medication/request/spec.py:113 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
9f9e929369e186f88af131f2a1ccc3a773d9bfe9648f92a98f6a4935c09a7ade
repositories/platform/mansoq-web/src/components/Common/BackButton.tsx:18 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
56a741eff730a7b18a5fae594374068bab2d5413993c32dbbaf3625e14743ca3
repositories/platform/mansoq-web/src/components/Common/ComboboxQuantityInput.tsx:33 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
dc2b42f282136e2c1f71318d93aa69af3935286de87176a4c1c8c093127f97a3
repositories/platform/mansoq-web/src/components/Medicine/DosageFrequencyInput.tsx:88 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
25dd21fd48a38c46bc40f2fb8b8586e89ed72eb97451fadd29c3d54591a5e420
repositories/platform/mansoq-web/src/components/Medicine/DurationInput.tsx:129 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
c271b7c60fd93d91bb97ce8ab38644b1999b0a1115db3db9d5c0626557eb0c11
repositories/platform/mansoq-web/src/components/Medicine/MedicationsTable.tsx:96 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
8bdf0ac1770dc1423e4534f9ed0f75f51bda5be717ef7bd0aa345edc79244830
repositories/platform/mansoq-web/src/components/Medicine/PrescriptionListSelector.tsx:62 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
d440785347dcc3045dea0d4d5c81052a9e3c7de074405fc4de87dea79cd4b083
repositories/platform/mansoq-web/src/components/Medicine/PrescriptionView.tsx:37 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
af1781d51d3dd511231a79e034a7f98412434dfa4603b91dce6676c4474fad96
repositories/platform/mansoq-web/src/components/Medicine/utils.ts:20 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
3cd9c9563e68a8ff18ac581c422477ddab664733f4c85a4b596403bf9cf87aa8
repositories/platform/mansoq-web/src/components/Questionnaire/MedicationValueSetSelect.tsx:98 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
bb8d5d5f1595778be9e9ad260296e8f43e5696fe9d19fb608e27a33a6a739610
repositories/platform/mansoq-web/src/components/Questionnaire/QuestionTypes/MedicationRequestQuestion.tsx:224 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
561259e73b1752c9844e31b798ad676878af5f4caf6be5fbd130cd31fcfc89cc
repositories/platform/mansoq-web/src/components/Questionnaire/QuestionnaireForm.tsx:380 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
ee6c2195f13e48f0896a2d3da566c2f2a67910adad08894df6b77862f9cfdeec
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:23 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
a39df63f9b7f2d976d4379511d7a2d4c8e3e284fd1e9b67c28e59392e8545b2b