Clinical care · VERSION 3dfb7c9f

Create a coded demonstration prescription for a reported-medication exercise

Use the Medication tab to create one fictional coded prescription, keep its row and shared notes distinct, and verify the saved card after reload before the Nurse reconciliation lesson.

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 coded prescription in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:56:16.584Z · 1728 × 921**
Saved coded prescription
Capture details
Observed committed 3dfb software on 20 October 2026. One Doctor prescription and one Nurse reported statement; software-only values, no dispensing or administration. Original pixels and capture times preserved.
Image SHA-256 `0f904563539f3b47f2b795caaaf5dfd191175fbb117b3550a5c88aff54ed011a`
**Verify the selected new card**: The selected prescription is 20/10/2026 10:55 AM.
**Read the Doctor prescriber**: The header identifies MANSOQ E2E Doctor.
**Read the shared prescription Note**: This complete Note is the prescription-level training text.
**Review 1.00 count, QD and 1 day**: The selected prescription’s dosage controls remain separate.
**Read the complete row-specific note**: The row note appears in the Instructions cell below the dash; this is the note copied into the later statement.

12 of 12 content blocks have reviewed image alignment.

Before you begin

Use an authorised Doctor account and verify the assigned fictional patient and intended ongoing encounter. This example uses the synthetic Inpatient encounter shown.
123
Recorded release 3dfb7c9f · 2026-10-20T07:50:28.689Z · 1728 × 921
Doctor overview
Capture details
Observed committed 3dfb software on 20 October 2026. One Doctor prescription and one Nurse reported statement; software-only values, no dispensing or administration. Original pixels and capture times preserved.
Image SHA-256 692c8c158e8c23dbb79cd6ceded9cf49ab8a4e1cc92b0aae6444cc4a0986ccef
1. Verify the fictional patient: Check the synthetic patient banner.
2. Verify the selected ongoing encounter: The selected Inpatient encounter is In Progress.
3. Open Add Medication: The Doctor opens the prescribing form for this software-only example.
All quantities, frequency, duration and notes are software-training examples. They are not a clinical order, recommendation or treatment. Do not dispense or administer them.
123456
Recorded release 3dfb7c9f · 2026-10-20T07:55:12.709Z · 1728 × 921
Draft code note review
Capture details
Observed committed 3dfb software on 20 October 2026. One Doctor prescription and one Nurse reported statement; software-only values, no dispensing or administration. Original pixels and capture times preserved.
Image SHA-256 6ce22a103b1f31b55c07022ffa70893e29a76749fd6eec663636bc6288d74df4
1. Review 1 count: The code-backed draft uses the explicitly chosen count unit.
2. Review QD (Once a day): QD is selected in the current HYMOX draft.
3. Review the automatic 1 day bound: The QD preset supplied this initial duration; review it as a separate field.
4. Enter the row-specific Note: This short input clips its long text. The saved prescription later shows the complete row note.
5. Enter the shared prescription Note: The complete shared software-only note is separate from the row Note.
6. Choose Submit once after review: Submit saves this Doctor prescription; it is not the Nurse statement save.
12345
Recorded release 3dfb7c9f · 2026-10-20T07:56:16.584Z · 1728 × 921
Saved coded prescription
Capture details
Observed committed 3dfb software on 20 October 2026. One Doctor prescription and one Nurse reported statement; software-only values, no dispensing or administration. Original pixels and capture times preserved.
Image SHA-256 0f904563539f3b47f2b795caaaf5dfd191175fbb117b3550a5c88aff54ed011a
1. Verify the selected new card: The selected prescription is 20/10/2026 10:55 AM.
2. Read the Doctor prescriber: The header identifies MANSOQ E2E Doctor.
3. Read the shared prescription Note: This complete Note is the prescription-level training text.
4. Review 1.00 count, QD and 1 day: The selected prescription’s dosage controls remain separate.
5. Read the complete row-specific note: The row note appears in the Instructions cell below the dash; this is the note copied into the later statement.
This lesson creates one demonstration prescription as the source for the separate Nurse reported-medication lesson. Do not copy or alter the earlier inventory-product prescriptions.
12
Recorded release 3dfb7c9f · 2026-10-20T07:56:04.038Z · 1728 × 921
New prescription list
Capture details
Observed committed 3dfb software on 20 October 2026. One Doctor prescription and one Nurse reported statement; software-only values, no dispensing or administration. Original pixels and capture times preserved.
Image SHA-256 03df32e5f50fa03ab1ea1a27d0fcc15d5f69e192c620393d7486dc0e0a2b0c8a
1. Keep Prescriptions selected: This tab contains the Doctor’s saved prescriptions.
2. Select 20/10/2026 10:55 AM: Choose the new HYMOX prescription card rather than the earlier product examples.
12345
Recorded release 3dfb7c9f · 2026-10-20T07:56:16.584Z · 1728 × 921
Saved coded prescription
Capture details
Observed committed 3dfb software on 20 October 2026. One Doctor prescription and one Nurse reported statement; software-only values, no dispensing or administration. Original pixels and capture times preserved.
Image SHA-256 0f904563539f3b47f2b795caaaf5dfd191175fbb117b3550a5c88aff54ed011a
1. Verify the selected new card: The selected prescription is 20/10/2026 10:55 AM.
2. Read the Doctor prescriber: The header identifies MANSOQ E2E Doctor.
3. Read the shared prescription Note: This complete Note is the prescription-level training text.
4. Review 1.00 count, QD and 1 day: The selected prescription’s dosage controls remain separate.
5. Read the complete row-specific note: The row note appears in the Instructions cell below the dash; this is the note copied into the later statement.

1. Open Add Medication for the selected encounter

Check the patient banner and selected In Progress encounter, select Add Medication, and open the empty request form’s Add Medication selector.

Doctor overview in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:50:28.689Z · 1728 × 921**
Doctor overview
Capture details
Observed committed 3dfb software on 20 October 2026. One Doctor prescription and one Nurse reported statement; software-only values, no dispensing or administration. Original pixels and capture times preserved.
Image SHA-256 `692c8c158e8c23dbb79cd6ceded9cf49ab8a4e1cc92b0aae6444cc4a0986ccef`
**Verify the fictional patient**: Check the synthetic patient banner.
**Verify the selected ongoing encounter**: The selected Inpatient encounter is In Progress.
**Open Add Medication**: The Doctor opens the prescribing form for this software-only example.

Empty request in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:50:32.232Z · 1728 × 921**
Empty request
Capture details
Observed committed 3dfb software on 20 October 2026. One Doctor prescription and one Nurse reported statement; software-only values, no dispensing or administration. Original pixels and capture times preserved.
Image SHA-256 `dbec120f1f3e0c1a7f7d0daee43c3c1d17f8de469be7f746f79dfe682ebd8ea8`
**Open the medication selector**: Open Add Medication in the empty request form.

2. Switch to Medication and choose the illustrated training source

Select the Medication tab, separate from Product. Search HYMOX. For this configured software exercise choose the first illustrated HYMOX 500MG CAPS result. The results include repeated display names; the selected first row does not print its terminology code here. Keep this demonstrated Medication-tab source distinct from the earlier Product-tab inventory example.

Selector tabs in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:50:36.260Z · 1728 × 921**
Selector tabs
Capture details
Observed committed 3dfb software on 20 October 2026. One Doctor prescription and one Nurse reported statement; software-only values, no dispensing or administration. Original pixels and capture times preserved.
Image SHA-256 `67b52e3cbcfb518a3dfc21489fc00f52cb68153c4825aec3f249478461dcbf07`
**Choose the Medication tab**: Use the terminology-backed Medication tab, distinct from Product.

Code search results in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:51:01.790Z · 1728 × 921**
Code search results
Capture details
Observed committed 3dfb software on 20 October 2026. One Doctor prescription and one Nurse reported statement; software-only values, no dispensing or administration. Original pixels and capture times preserved.
Image SHA-256 `acfa4c6d423ebd19173ac5074bc614aace5f349d6833f3fd8a0cd5d0b4c1e776`
**Check that Medication is selected**: The search is in the Medication tab.
**Search HYMOX**: The search field is already populated in this view.
**Choose the first illustrated HYMOX 500MG CAPS result**: For this software exercise use this first result. Several entries share display text; no code is printed beside this selected result.

3. Enter the quantity and choose QD

Enter 1 in Dosage and explicitly select 1 count from the unit choices. Open Frequency and search QD, then choose QD (Once a day). The earlier Doctor control illustration shows the Frequency search and QD result on a different synthetic product; use it only to locate that unchanged control. In the current HYMOX draft verify 1 count, QD and the preset 1 day duration. These are fictional interface values.

Explicit count unit in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:54:43.870Z · 1728 × 921**
Explicit count unit
Capture details
Observed committed 3dfb software on 20 October 2026. One Doctor prescription and one Nurse reported statement; software-only values, no dispensing or administration. Original pixels and capture times preserved.
Image SHA-256 `b4a44616ebbef8dc1263907d4eb15ef57e4884271346d3d000fb292d4800fbf5`
**Enter the fictional quantity 1**: The number initially appears with a suggested unit; select the intended unit explicitly.
**Choose 1 count**: Use count for this fictional interface exercise, not the initially suggested tablets.

Frequency options in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:54:54.155Z · 1728 × 921**
Frequency options
Capture details
Observed committed 3dfb software on 20 October 2026. One Doctor prescription and one Nurse reported statement; software-only values, no dispensing or administration. Original pixels and capture times preserved.
Image SHA-256 `090f937e6066378c24e30b7fa1e7332b2245cf47bd5e4d5c956538fc13a0fc44`
**Open Frequency**: This current HYMOX draft has its Frequency menu open.
**Search for QD**: Use the frequency search field. The earlier separate-product reference shows the resulting QD choice.

Earlier Doctor Frequency search and QD choice — separate training product in the same-release fictional software context — **Recorded release 3dfb7c9f · 2026-10-20T07:19:12.686Z · 1728 × 921**
Earlier Doctor Frequency search and QD choice — separate training product
Capture details
Earlier Doctor image from the same release and patient. It illustrates the Frequency search and QD choice only; its separate synthetic product is not the coded HYMOX prescription.
Image SHA-256 `80f9a90b724013a224e2c26d7c698bc2587a1a4cdda332c74e32912b78c94967`
**Open first-step Frequency**: Choose the first dosage line’s frequency control.
**Search QD**: Type QD in this open frequency search.
**Choose QD (Once a day)**: Select the result for this fictional interface example.

Draft code note review in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:55:12.709Z · 1728 × 921**
Draft code note review
Capture details
Observed committed 3dfb software on 20 October 2026. One Doctor prescription and one Nurse reported statement; software-only values, no dispensing or administration. Original pixels and capture times preserved.
Image SHA-256 `6ce22a103b1f31b55c07022ffa70893e29a76749fd6eec663636bc6288d74df4`
**Review 1 count**: The code-backed draft uses the explicitly chosen count unit.
**Review QD (Once a day)**: QD is selected in the current HYMOX draft.
**Review the automatic 1 day bound**: The QD preset supplied this initial duration; review it as a separate field.
**Enter the row-specific Note**: This short input clips its long text. The saved prescription later shows the complete row note.
**Enter the shared prescription Note**: The complete shared software-only note is separate from the row Note.
**Choose Submit once after review**: Submit saves this Doctor prescription; it is not the Nurse statement save.

4. Enter the row note and separate shared note

In the product row’s Note enter: DEMO RECONCILIATION — fictional reported-use example. Do not dispense or administer. Reconcile reported dosage and period separately. The narrow input shows only the beginning; the saved detail later shows the complete text. In the shared Note below the table enter: SYNTHETIC SOFTWARE TRAINING ONLY — coded prescription to medication statement reconciliation. Values are fictional interface examples, not a clinical order, recommendation or treatment. Do not dispense or administer. The two notes have different scopes; do not treat the shared prescription Note as the source row note.

5. Review and submit the Doctor prescription once

Review the selected HYMOX 500MG CAPS, explicit 1 count, QD, 1 day and both training notes. Choose Submit once and wait for the return to Overview. Open Medicines, keep Prescriptions selected, then select the new 20/10/2026 10:55 AM card prescribed by MANSOQ E2E Doctor.

Returned overview in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:55:42.931Z · 1728 × 921**
Returned overview
Capture details
Observed committed 3dfb software on 20 October 2026. One Doctor prescription and one Nurse reported statement; software-only values, no dispensing or administration. Original pixels and capture times preserved.
Image SHA-256 `f8d1d02947ee77977f85771111338357df053f539006fef569dfe5b3b7567964`
**Open Medicines after the return**: Wait for Overview, then inspect the newly saved prescription under Medicines.

New prescription list in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:56:04.038Z · 1728 × 921**
New prescription list
Capture details
Observed committed 3dfb software on 20 October 2026. One Doctor prescription and one Nurse reported statement; software-only values, no dispensing or administration. Original pixels and capture times preserved.
Image SHA-256 `03df32e5f50fa03ab1ea1a27d0fcc15d5f69e192c620393d7486dc0e0a2b0c8a`
**Keep Prescriptions selected**: This tab contains the Doctor’s saved prescriptions.
**Select 20/10/2026 10:55 AM**: Choose the new HYMOX prescription card rather than the earlier product examples.

6. Read the saved card, reload and verify it again

On the selected card check HYMOX 500MG CAPS, 1.00 count, QD and 1 day. Read the shared Note above the table and the different row note displayed in the Instructions cell. Use the browser’s Reload command once, wait for Medicines, and reselect the same 10:55 AM card. Verify the same values and notes without another Submit. This saved code-backed source is used in the next Nurse lesson.

Prescription after reload in a fictional software training example — **Recorded release 3dfb7c9f · 2026-10-20T07:56:56.065Z · 1728 × 921**
Prescription after reload
Capture details
Observed committed 3dfb software on 20 October 2026. One Doctor prescription and one Nurse reported statement; software-only values, no dispensing or administration. Original pixels and capture times preserved.
Image SHA-256 `0f904563539f3b47f2b795caaaf5dfd191175fbb117b3550a5c88aff54ed011a`
**Reselect the same prescription after Reload**: The same 10:55 AM card and contents remain after ordinary browser Reload.
**Recheck the retained row note**: The saved notes and dosage are unchanged in this readback.

Keep the two notes separate

The shared prescription Note begins SYNTHETIC SOFTWARE TRAINING ONLY. The request row Note begins DEMO RECONCILIATION and appears with that row’s instructions after saving. The later statement-copy action carries the request row Note, not the shared prescription Note.

Read the Medication-tab example in context

The shown medicine is a terminology-backed source for this software exercise. The selected result and saved card show its display name, not the underlying code number. Choosing a result with the same name from Product would be a different source path. This demonstration does not establish medication use, dispensing, administration or an external exchange.

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:421 · 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:661 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
a39df63f9b7f2d976d4379511d7a2d4c8e3e284fd1e9b67c28e59392e8545b2b
repositories/platform/mansoq-web/src/types/emr/medicationStatement.ts:7 · 3dfb7c9f519fb5b4cd4452439f3c12346bf58319
Source file checksum
5784010754caa19b544f2db2f1a374d7739d76518159a239b73a3a8c9fb5a091