Clinical care · VERSION 3dfb7c9f

Create two different medicine rows in one demonstration prescription

Choose an inventory product and a coded medicine through their separate selector tabs, review each row independently, then save both together and verify the single prescription after reload.

Doctor

Recorded product version 3dfb7c9f

These lessons apply to their recorded version and observed role. Check local permissions and configuration. A qualified lesson does not establish complete product or facility coverage.

Version, screenshot scope and limits

Full product version: 3dfb7c9f519fb5b4cd4452439f3c12346bf58319

Exact committed 3dfb7c9f source/tree, ordinary existing Doctor in one explicitly fictional Polyclinic Inpatient encounter. All 12 original raw form schemas/subjects and separate BP form matched under ordinary Doctor/Nurse reads before native UI. One four-answer ordinary response with optional note saved once, native single PDF saved/viewed, neutral warning Cancel proved unchanged, then same new source corrected once. Existing clinical and Admin estates preserved; no new form, code, grants or external transport. Genuine 25-photo public subset from 29 retained original frames; exclusions and pixel/geometry qualifications are private. Ordinary existing Pharmacist companion adds fully visible services pagination, prescription medicine filters, completed-order history and saved prescription PDF. Existing scoped stock and financial records verified unchanged. No new dispensing or financial actions are qualified by these lessons. Ordinary existing Billing Officer companion adds account/status/search, saved Balanced invoice and actuallocalinvoicePDF.273scopedstoredrows verifiedunchanged;4nestedrelatedPharmacistlast_login responsevalues separatelyqualified. Nocharge/invoice/payment/tax/electronicfiling businessaction is claimed. Exact committed3dfb source/tree, ordinary existing Doctor on one separate explicitly fictional Polyclinic Ambulatory case. Normal API patient/encounter prerequisites are separated from native teaching. Four installed leaves retain schema/provenance. One actual invalid-Time attempt refused database writes; one recovered mixed submission saved two Conditions/two structured logs/one ordinary source, genuine one-page PDF saved/viewed, neutral correction Cancel verified, then only that new ordinary source corrected once. Scoped ordinary Doctor/Nurse readbacks preserve all measured prior clinical records in the two retained cases; Admin rows are outside those clinical collection comparisons; no grants, source, form, term or runtime changes. Forty-three actual wide originals retained for public teaching from46 unchanged raw frames. Exact committed 3dfb source/tree, existing ordinary Nurse on one already-established clearly fictional Polyclinic Ambulatory case. IPD is transparently the installed title. One unchanged-form Cancel; explicit No/0/None with three optional notes; exactly one ordinary source saved; actual one-page local PDF saved/viewed; neutral warning Cancel and then source-only Error verified after reload. Existing target and older-main clinical collections compare exactly in 24 scoped comparisons per stage under ordinary Nurse/Doctor. This does not claim global Admin-table verification, all roles/facilities or clinical respiratory-policy coverage. No grants, config, terminology, source or runtime changes. Twenty-six genuine public originals from27 retained raw frames; one incomplete-footer attempt excluded. Exact committed 3dfb source/tree, existing ordinary Nurse on one previously established fictional Polyclinic Ambulatory case. One unchanged-form Cancel; fictional multiline Text, actual temporary one-unit relative-date examples, restored absolute Date and two optional field notes; exactly one ordinary response saved at 11:04 AM; actual one-page local PDF saved and viewed; neutral warning Cancel then source-only Error verified after reload. Existing target and older-main clinical collections compare exactly in 24 scoped comparisons per stage under ordinary Nurse and Doctor, with the four older target response/log records additionally compared by UUID. No claim of global Admin-table preservation, all roles/facilities, all Date branches or clinical medication-history coverage. No grants, configuration, terminology, source or runtime changes. All 30 retained genuine originals are public candidates; no image edits. Two distinct fictional patients through ordinary existing Staff UI, native field validation, contact/address/geography/optional controls, birth-year verification and honest full-profile404, duplicate choices and actual native unsaved confirmation. No care/grants/configuration/old-patient edit. Exact committed 3dfb source/tree, existing ordinary Nurse on one already-established fictional Polyclinic Ambulatory case. Unchanged Cancel; three fictional Integer values 1/2/3 and explicit fictional Text; four optional field notes; exactly one ordinary response saved at 11:22 AM; one genuine 41,791-byte single-page PDF saved/viewed; warning Cancel then source-only Error verified after reload. Both ordinary roles confirm 24 scoped clinical comparisons at each of five stages plus the five older target response/log UUIDs. No global Admin-table claim, patient-portal/actual teleconsultation or real quality-rating assertion, all-role/facility claim, range-enforcement claim or enterprise-complete claim. No prerequisites/grants/config/terminology/source/runtime edits. Twenty-six public originals from 28 retained raw frames; two incomplete-footer native attempts excluded. One saved Booked appointment for the existing synthetic A patient, ordinary Staff and Doctor actors, and the existing public no-charge template; genuine wide captures. No later care, token, grant or configuration change is included. One later read-only Administration-option illustration is included on the same committed source; its dated metadata and no-save scope remain explicit. One previously saved synthetic Staff Check-In and its fresh post-USB readback, plus ordinary Doctor open/default review/Cancel without encounter submission. Existing appointments, patient/identifier state and source remain preserved under scoped receipts. Exact unchanged committed 3dfb on restored physical-USB training profile. Existing ordinary Nurse on an existing fictional Ambulatory case. One blank Cancel with unexpected small native unsaved warning retained privately; one thirteen-required client demonstration and one unexpected automation DOMfill-Time client check retained privately, not attributed as a product bug. One definite Invalid url backend refusal followed by no-new-source readback. One successful ordinary response with fifteen answer leaves, seventeen values and four notes. Actual 50,387-byte two-A4-page PDF Save, Preview and complete independent renders. Own-source warning Cancel then Confirm Error and reload. Six normal Nurse/Doctor readback stages preserve twenty-four scoped collections and twelve older target response/log comparisons per stage. No global Admin audit claim. No extra clinical destination, grant, configuration, schema, terminology, favourite, source or runtime changes. Existing mg unit and expected recent cache only; no enterprise-complete claim. One normal existing Doctor creates a synthetic Ambulatory encounter from the exact saved Checked-In appointment, with independent reconciliation of encounter POST and separate appointment status update; then reloads and navigates between the saved records. No clinical findings, account, charge or token is created. Exact unchanged committed 3dfb on the restored physical-USB profile. A separate explicitly fictional patient and Ambulatory encounter were created once through the ordinary authorized Doctor API as a distinct prerequisite. Actual native Doctor flow: one blank Cancel, one definite before-DOB refusal, one corrected Patient deceased_datetime Submit and normal reload. Fifteen genuine 1728x921 originals. Four approved GET/SELECT-only stages each passed twenty-six protected clinical collection comparisons, exact other Patient/Encounter/identifier rows, target Encounter conservation and all308 sequences. Only target deceased_datetime/Doctor updater/modifieddate and source-backed instance identifier maintenance allowed; actual phone identifier199 modified_date refreshed, name200 remained exact, both NULL creators retained. No ordinary/structured QR, derived observation, PDF, certificate, discharge, undo, new grant/config/runtime/source changes or full audit-history/enterprise-complete claim. Native segmented-key operator recovery remained private and was not attributed as a product defect. PRIVATE candidate: existing genuine 19 October 2026 ordinary Staff no-save department/practitioner review and Close; three original wide frames, no new capture or business action. Published status is release-schema metadata only; this package has not been imported or promoted. PRIVATE initial-only future-date/schedule-filter teaching candidate: existing fictional Clinic patient/practitioner and materialized slots, one Booked appointment saved normally. No reschedule, cancellation, Check-In, token, clinical care, configuration or grant change. Published status is release-schema metadata; no Site import/promotion performed. PRIVATE candidate: historical safe Cancel reviews, one actual reschedule and one later cancellation of its distinct replacement; retained original history. Published status is schema metadata only; no Site import. Exact unchanged3dfb synthetic physical-USB profile. Existing ordinary Nurse on MedicineHybrid case. One actual client required refusal/no Statement or QR/allocator change; one native CREATE of reportedHYMOX250MGCAPS/NotTaken/Practitioner/date19Oct; saved summary/fullNote; locked create-only fields; history selector zero-selected Cancel; own Remove-warning neutralCancel; later one localEnteredInError then oneSubmit; same UUID/fields/creator/time retained with oneUPDATE structuredQR. Seven finite approved normal-role GET/SELECT stages passed, including independent Doctor readback and117 existing raw scoped rows; only two relevant clinical allocator transitions. Not all-database or unrelated concurrent Admin preservation. OriginalV2 preflight numeric rowhash equality remains precision-limited; separate fresh raw-native baseline and all subsequent scoped raw rows preserve exact PostgreSQL text.35originals retained,30public unchanged1728x921frames,5private excluded honestly. No ordinaryQR/PDF, prescription/MAR/dispense, clinical qualification, newgrant/config/source/service or A3 UI claim. Exact committed3dfb, physical-USB guarded synthetic runtime. One existing ordinary Nurse on existing Medicine case, one supplied2552B inertPDF/one complete FileUpload5/one exact-byte localobject. Five actual no-save stages, one valid native Submit, saved/reloaded finite Nurse+Doctor readbacks; old scoped clinical/file rows and11oldobjects preserved, relevant FileUpload allocator4→5. Not unrelated concurrent Admin/global database preservation.24raw originals retained;14public originals unchanged, including genuine compactnativeconfirmation and varied originalwide dimensions. No ordinaryQR/responsePDF, actual clinical content/consent, rename/archive/restore or laterA3 claim. Metadata/prose V2 adds the genuine native-file-chooser17, truthful chooser surface/caption and organization-approved-file wording. Supplied rawPDF remains private proof, not a published downloadable artifact. Three narrow no-save lessons from the actual ordinary Staff P1b sequence. Eleven original records, ten unique image hashes, including one unmodified native macOS confirmation. Private schema-ready package only; no Site import or publication. Private root-review following-batch candidate: exact committed3dfb product and separately qualified Clinical transport profile/PID23511. Seven genuine clean task-tab715 viewport originals (actual1728×977) show the existing savedPDF preview1/1/normalClose, unchangedRenameCancel and emptyArchiveCancel. Root recaptured only these neutral states with zero business submissions. Prior accepted conservation verifiers retain original earlier times; no new SQL/API/object readback is claimed. V1 native-window originals/loading02 remain private unchanged. No real rename/archive/restore/upload/Print/Download/OpenInBrowser or later-product-source claim. status published is export eligibility only; no Site import/publication. Tax-rule teaching covers the observed Staff access boundary and an existing Clinic administrator completing the fifteen fields, saving one fictional unresolved Draft, then reloading and opening View details. The fourteen stored values persist; the new-edit explanation starts blank. Review, approval, publication and activation are separate workflows. Nurse teaching covers the configured Diagnosis practice form: leave an existing diagnosis unchanged, save ordinary Text and Integer answers with separate notes, review a one-page PDF, and mark only the ordinary response as entered in error. Screenshots show saved values, Cancel, correction and reload. The structured diagnosis remains separate. Staff teaching covers one saved patient-profile update: use the segmented birth date, keep separate contact numbers and addresses, review geography and PIN Code, save once, then reload and inspect the clean form. Screenshots show the saved values, disabled Update button and Back without further changes. Nurse Respiratory Status teaching covers every configured thirteen input, all twelve literal choices, six Decimal and two Integer controls, narrative and all thirteen note controls. The final four fictional answers and two notes were saved and reloaded; one genuine A4 PDF was saved/viewed; own-source entered-in-error Cancel, Confirm and reload retained the answers. A separate later unsaved Text-clear illustration is clearly distinguished. Values are software samples, not respiratory measurements or treatment settings. Native Nurse is pictured; Doctor evidence is normal read-only API only. Facility Admin teaching covers one empty required change-reason refusal, unsent fictional reason Cancel/reopen/Cancel, and the separate Row lifecycle Validate for the same unresolved Tax draft. The actual negative result lists illegal transition, evidence not activation grade, source document missing, overlap check not performed and config package missing. No filled-reason Confirm, saved lifecycle move, approval, activation, qualification or financial-readiness result is claimed. Ordinary Nurse structured Allergy teaching on the same fictional active encounter covers untouched Cancel, a required-field refusal, local catalogue selection, unsaved category/criticality/verification/clinical-state controls, occurrence calendar and Quick Finder, row notes, one create and same-row Inactive and Entered in Error updates with reloads. Filtered Overview/History messages are distinguished from the retained disabled Error entry. Doctor evidence is normal read access only. No ordinary questionnaire PDF, deletion, restore or full clinical allergy assessment is claimed. Existing ordinary Nurse teaching adds one display-name Rename and saved reload for a synthetic encounter attachment, a neutral Archive-warning Cancel, one reasoned Archive, and Active/Archived filters with retained reason/author/time and Close. The document bytes and original upload metadata remain retained; this inspected source provides no Restore/unarchive action. No physical deletion, new upload, complete-role/module or global-database invariance is claimed. Additive ordinary-role teaching: Nurse encounter Notes thread/message creation and retained read-only patient context; existing Facility Admin encounter-filtered claims, separate claim/encounter/invoice identities, same-encounter sibling detail, Refresh and All claims. These are bounded synthetic workflows with their own measured scopes, not complete role/module coverage, a separate Executive RBAC qualification, external payer/submission/settlement success or global database invariance. Additional bounded existing Clinic Facility Admin TaxRule status teaching: one explicit Draft to InReview transition and one explicit return to Draft, fictional reasons, genuine reloads and own status history. These two synthetic status changes do not approve, activate, publish or legally qualify a tax rate, clear claim/invoice holds or establish a least-privilege finance role. Additional ordinary Doctor copies a medication history item into a separately saved prescription request and inspects the retained reload; ordinary Staff uses an existing patient name identifier to find the synthetic patient. These narrowly measured synthetic flows are not prescribing-policy, payer, global role or full curriculum qualification. Additional bounded ordinary Doctor teaching stops exactly one existing copied medication request, preserves the other requests, and checks the settled reload. Expanded mixed active/ended product groups can still show an Ended child with Show Discontinued unchecked; the pictured footer hidden count is not proof that this child is hidden. No group discontinue, administration, prescription policy, persisted end-time, global state or complete module qualification is implied. Additional bounded ordinary Facility Admin teaching creates two inert administrative Patient-resource parent and child tag configs, recovers from a required Display name refusal, verifies inherited child resource and parent navigation, uses neutral Archive Cancel, and confirms one own-child status archive with retained details after reload. No tag applications, grants, patient or encounter changes, financial action, deletion or reactivation are demonstrated. Configuration status changes are explicit; no whole database or global allocator qualification is implied. Additional ordinary Doctor guides demonstrate one explicitly fictional Consent metadata Draft with Privacy category and Deny decision, its dates, period, note, card, details, reload and retained Entered in Error correction. They preserve the observed date-validation and optional-period clear limitation, unsaved choice review, neutral Cancel and attachment-name search. No real legal consent, signature, verification, treatment or disclosure authority is represented. Additional Emergency guides demonstrate the unconfigured triage board, its row scope, columns, Refresh and encounter Notes link; one separate synthetic Emergency encounter; an untouched update Cancel and native confirmation; one On Hold update and one return to In Progress with reload and Status History. The older Ambulatory encounter remains separate. No triage level, clinical handover, admission, discharge, class conversion or terminal-state save is claimed. Supporting files, print, deletion, restoration and full-module completion remain separate. Additional Facility Admin guides inspect the fictional SET-11 Draft/test certificate-rotation dialog without rotating. They show initially disabled Rotate, a harmless reference warning, a reason that does not remove that warning, Close, retained unsent text on reopening, clearing the reference and reason, Close again and a normal browser Reload. No credential bytes, certificate rotation, connection test, exchange, dispatch, endpoint change or additional record save is represented. Additional Facility Admin guides create one empty Team under an existing department, review its saved details, close its Remove warning with Cancel, remove the empty Team and reload the parent list. No membership, access, service assignment or restoration is shown. Additional ordinary Nurse guides select two existing medication requests, cancel an unsaved selection, reset only one draft, save one Not Done and one In Progress entry together, then reload and inspect both entries through unchanged Cancel. The recorded parameters and notes are fictional software examples; clinical administration, printing and other medication workflows are outside this scope. Additional Doctor guides cancel an unsaved discharge draft, choose Other and enter fictional advice and a reviewed end time, save once and reload, then cancel a separate completion warning before confirming completion once. They read the five-entry status history and observe one refused Restart under the measured zero-hour policy; the notice expired before the retained outcome image. One native unsaved warning retains its compact original dimensions. No successful restart, clinical advice, bed or device release, or restoration is demonstrated. Additional Doctor and Nurse guides follow one fictional laboratory request through specimen drafts, required-field refusals, collection, an Unsatisfactory specimen and recollection, preliminary results and correction, Final report approval, the original report PDF, request completion and reload. Separate later history-menu and saved-report printing demonstrations retain their actual chronology. The observed collection-time display discrepancy is described without interpreting it as a different collection. No specimen-processing save, physical test, clinical interpretation, payer exchange or complete laboratory curriculum is demonstrated. Additional ordinary Nurse and Doctor guides use three explicitly fictional, software-only DEMO substances for Food, Environment and Biologic category examples. They teach new-row Remove and draft Cancel, one three-entry Nurse save with separate dates and notes, Doctor preview Cancel and a two-entry update, persisted Remove Cancel and one Entered in Error correction, history, reporting, return navigation and retained disabled fields. A separate read-only guide compares an older Completed encounter with patient-level current Allergy history and the actual return to the active case. Blank panels and filtered summary badges are not clinical no-allergy findings or backend write-permission tests. The three terminology labels do not represent real allergens, clinical interpretation or a reaction interface. No additional patient, clinical encounter, grants, reaction control, closed-encounter write qualification or complete Allergy curriculum is claimed. Additional read-only Nurse guides inspect sparse vital-sign rows, observation details and the existing Pulse tooltip and retained history. Three ordinary Doctor guides practise diagnosis-history group selection and cancellation, change an existing diagnosis to Inactive and then Recurrence, and change verification on an existing symptom to Refuted while checking current views and retained history. These fictional software demonstrations do not establish clinical recommendations, new permission grants or completed competence. Two ordinary Doctor guides follow one fictional product through separate dosage instructions, duration and dose-range controls, one final prescription submission and saved readback. A Nurse guide demonstrates a refused history copy when an inventory-backed prescription lacks a medication code, checks the empty statement draft and retained history, then leaves without submitting. These software examples do not establish treatment instructions, a successful coded statement copy, dispensing or administration, new permission grants or completed competence. A further Doctor and Nurse pair follows a separately saved code-backed demonstration prescription into a reported medication statement, explicitly reconciles its dosage text, information source and dates, and verifies saved notes and authorship after reload. Copying does not verify actual medication taking. The full clinical curriculum remains in progress. One ordinary Doctor copies a synthetic Nurse-reported medication statement into a fresh prescription request, reviews the initially blank prescribing fields and new Doctor requester, enters separate fictional dose, frequency and duration plus a shared software-only note, and verifies one saved prescription after reload while retaining the original reported statement. This is software teaching, not a prescribing recommendation, dispensing, administration or a claim that all clinical teaching is complete. An ordinary Nurse changes only the status of one existing synthetic reported medication statement to On Hold and back to Active with separate saves and reloads, retaining its original details and reading its current patient-history entry by creation date. An ordinary Doctor creates one patient-only synthetic Notes discussion, sends one fictional message, and verifies its author, time and counts after reload. This Notes discussion has no encounter association. These bounded software exercises do not establish a treatment decision, actual medication use, delivery or read acknowledgement, dispensing, administration, permission grants or completed competence. An ordinary Doctor adds two different synthetic medicine rows using the separate Product and Medication selectors, reviews each row and the shared prescription note, revises the first fictional quantity before one Submit, and verifies the resulting single prescription after a normal reload. These are software teaching examples, not prescribing, dispensing or administration recommendations; the retained saved-result proof is bounded to its historical capture interval. An ordinary Pharmacist locates the assigned queue and synthetic patient, recognises the patient-home encounter-list access boundary, previews and cancels an unsaved original billing draft, then selects one new Doctor prescription. The operator observes one client refusal for a selected coded medicine without an inventory product link, excludes that row and saves only one partial stock-backed quantity as a Preparation row in an In Progress order with a Draft invoice. The lesson distinguishes All Given, selection-driven prescription Mark Complete and later order completion, configured final invoice rounding, reload and a retained Draft readback after one refused Issue action. The insurance-readiness explanation is source-and-scoped-state inference, not a captured response body or toast. Four additional later individual Services footer views picture the pagination clicks, ordered logically by visible page state rather than capture chronology. No payment, successful issuance, physical handover, administration, substitution, permission grant or completed competence is demonstrated.

Saved one prescription two rows in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:53:32.587Z · 1728 × 921**
Saved one prescription two rows
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `9ba1629a4643a98c8f5d02ee9d4d5e03a9d67e7d086e75b530731f5fe94a85dc`
**Select the new 20/10/2026 12:53 PM card**: The older 18/10/2026 06:01 PM Furosemide card remains separate below.
**Read the Doctor prescriber**: The selected new card identifies MANSOQ E2E Doctor.
**Read the one shared Note**: The full shared prescription Note appears above both rows.
**Read the first medicine row**: The selected card contains Synthetic Training — Paracetamol 500mg.
**Read saved 2.00 count**: Its first structured dose is 2 count.
**Read first QD and 1 day**: Frequency and duration are separate saved fields.
**Read complete row Note A**: The Instructions cell shows the inventory-product software example note.
**Read the second HYMOX row**: This same selected prescription also contains HYMOX 500MG CAPS.
**Read saved 1.00 count**: The second medicine retains its separate 1 count dose.
**Read second QD and 1 day**: Read this row’s own frequency and duration.
**Read complete row Note B**: The second Instructions cell contains the coded-medicine software example note.

19 of 19 content blocks have reviewed image alignment.

Before you begin

Use an authorised Doctor account and the assigned fictional Pharmacy-Prescribed patient. Verify the selected Ambulatory encounter is In Progress before opening a new request.
1234
Recorded release 3dfb7c9f · 2026-10-20T09:49:44.564Z · 1728 × 921
Doctor case identity
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 f9d6911d772ebc6044b62b38d280542c0253d18b68e16ca7c9f9e22a37131e41
1. Check the Doctor account: The open account menu identifies MANSOQ E2E Doctor and qa-doctor.
2. Check the fictional Pharmacy-Prescribed patient: Use the assigned synthetic patient shown in the banner.
3. Check the selected ongoing Ambulatory encounter: The selected encounter is In Progress.
4. Open Medicines: Use the prescribing tab for this Doctor exercise.
12
Recorded release 3dfb7c9f · 2026-10-20T09:50:04.204Z · 1728 × 921
Fresh create entry
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 af6a41f753a8d976d54fd1db378146cf310c665261d06f868198068587d1d5c6
1. Keep Prescriptions selected: The earlier Furosemide prescription is a separate existing card.
2. Choose Create: Start a fresh request rather than editing the original prescription.
This exercise uses two existing configured sources: the illustrated Synthetic Training — Paracetamol 500mg inventory product and the illustrated HYMOX 500MG CAPS Medication-tab result. Do not edit the older Furosemide prescription.
12
Recorded release 3dfb7c9f · 2026-10-20T09:50:52.964Z · 1728 × 921
Synthetic product search result
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 264a0546b13221c2e7603e27b6f07d348b31a86d87fefb4d6894e5af606e0e4c
1. Search Synthetic Training: The Product search is populated with this text.
2. Choose Synthetic Training — Paracetamol 500mg: Select this illustrated product, with 06281086104491 displayed below its name, rather than the other synthetic results.
123
Recorded release 3dfb7c9f · 2026-10-20T09:51:53.956Z · 1728 × 921
Medication hymox search result
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 ea44faf7e39bc1fed9cd8fb6ec611f65a4e2d2a820d148d13eab8549fdf3b55c
1. Check Medication is selected: This is separate from the Product source used for the first row.
2. Search HYMOX: The current medication search is populated with HYMOX.
3. Choose the first illustrated HYMOX 500MG CAPS result: Several display names repeat. Use the illustrated same configured source; its first result does not print a terminology code alongside the name. Do not choose a star button.
Every dose, frequency, duration and note here is a fictional software example, not a clinical recommendation. Do not dispense or administer these values. This lesson creates one new demonstration prescription only.
123456
Recorded release 3dfb7c9f · 2026-10-20T09:53:11.323Z · 1728 × 921
Final two count one count review
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 37b64600e7cdf02f35f5b6dfbe824a8263c0e669293c4475d8a7522c3e67c1fd
1. Review the revised first 2 count: The first row is now 2 count, separately from its QD and 1 day.
2. Review the second 1 count: HYMOX remains 1 count, QD and 1 day.
3. Check distinct row Note A: Its narrow input shows the start; use the saved Instructions cell for full readback.
4. Check distinct row Note B: The second row keeps its own software-only note.
5. Read the complete shared Note: This remains one prescription-level note for both rows.
6. Choose Submit once after review: One Submit saves both new medicine rows into one prescription. Do not submit the rows separately.
1234567891011
Recorded release 3dfb7c9f · 2026-10-20T09:53:32.587Z · 1728 × 921
Saved one prescription two rows
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 9ba1629a4643a98c8f5d02ee9d4d5e03a9d67e7d086e75b530731f5fe94a85dc
1. Select the new 20/10/2026 12:53 PM card: The older 18/10/2026 06:01 PM Furosemide card remains separate below.
2. Read the Doctor prescriber: The selected new card identifies MANSOQ E2E Doctor.
3. Read the one shared Note: The full shared prescription Note appears above both rows.
4. Read the first medicine row: The selected card contains Synthetic Training — Paracetamol 500mg.
5. Read saved 2.00 count: Its first structured dose is 2 count.
6. Read first QD and 1 day: Frequency and duration are separate saved fields.
7. Read complete row Note A: The Instructions cell shows the inventory-product software example note.
8. Read the second HYMOX row: This same selected prescription also contains HYMOX 500MG CAPS.
9. Read saved 1.00 count: The second medicine retains its separate 1 count dose.
10. Read second QD and 1 day: Read this row’s own frequency and duration.
11. Read complete row Note B: The second Instructions cell contains the coded-medicine software example note.

1. Verify the case and create a fresh request

Check the Doctor account, fictional patient banner and selected ongoing Ambulatory encounter. Under Medicines keep Prescriptions selected and choose Create. Do not select Edit on the older Furosemide card. The new request should initially have no medicine rows.

Doctor case identity in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:49:44.564Z · 1728 × 921**
Doctor case identity
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `f9d6911d772ebc6044b62b38d280542c0253d18b68e16ca7c9f9e22a37131e41`
**Check the Doctor account**: The open account menu identifies MANSOQ E2E Doctor and qa-doctor.
**Check the fictional Pharmacy-Prescribed patient**: Use the assigned synthetic patient shown in the banner.
**Check the selected ongoing Ambulatory encounter**: The selected encounter is In Progress.
**Open Medicines**: Use the prescribing tab for this Doctor exercise.

Fresh create entry in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:50:04.204Z · 1728 × 921**
Fresh create entry
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `af6a41f753a8d976d54fd1db378146cf310c665261d06f868198068587d1d5c6`
**Keep Prescriptions selected**: The earlier Furosemide prescription is a separate existing card.
**Choose Create**: Start a fresh request rather than editing the original prescription.

Empty new medication request in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:50:09.311Z · 1728 × 921**
Empty new medication request
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `30b455c7486243fac713ab04f82b12241c5206550cd34046bffd4765f668e245`
**Open Add Medication**: The new request initially has no medicine rows.

2. Choose the first inventory product

Open Add Medication. Keep Product selected and choose the illustrated Demo Medications category. Search Synthetic Training, then select Synthetic Training — Paracetamol 500mg, with 06281086104491 displayed below its name in this picker. Leave the other synthetic search results alone.

Product demo category in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:50:17.173Z · 1728 × 921**
Product demo category
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `cebed08870f610bd421084530b939b3f11f0fb2014280814f489c723b9a154fb`
**Choose Product for the first medicine**: This tab searches configured inventory products, separate from the Medication terminology tab.
**Locate product search**: Enter the synthetic product search here.
**Choose Demo Medications**: This category was opened before the illustrated search.

Synthetic product search result in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:50:52.964Z · 1728 × 921**
Synthetic product search result
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `264a0546b13221c2e7603e27b6f07d348b31a86d87fefb4d6894e5af606e0e4c`
**Search Synthetic Training**: The Product search is populated with this text.
**Choose Synthetic Training — Paracetamol 500mg**: Select this illustrated product, with 06281086104491 displayed below its name, rather than the other synthetic results.

3. Review the first row’s starting quantity and frequency

The configured inventory product starts with 1 count. Review that unit explicitly; Frequency and Duration are still blank. Open its Frequency, search QD and choose QD (Once a day). Review the resulting QD and preset 1 day as separate fields. This is an initial draft; the first quantity will be revised before the final submission.

First product defaults in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:51:08.821Z · 1728 × 921**
First product defaults
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `b3c611b3f74ceeaccb21434bf98c332ecd16a8736c2f8da9ba002e2f858b2b0c`
**Read the first product row**: This is the selected Synthetic Training — Paracetamol 500mg product.
**Review the initial 1 count**: The configured product supplies this starting quantity and count unit.
**Open the first row’s Frequency**: Frequency starts blank and must be selected separately.
**Read the initially blank Duration**: Duration has not yet been selected.
**Locate the first row Note**: This narrow field belongs only to the first medicine.

First row qd choice in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:51:15.116Z · 1728 × 921**
First row qd choice
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `30ef21f5b0b83f5c91f0d399a9265db641be762e4bc4b9df5b1592900f9cd341`
**Search QD for the first row**: The actual Frequency search contains QD.
**Choose QD (Once a day)**: This is the first row’s frequency choice for the fictional software exercise.

First row complete before second in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:51:27.008Z · 1728 × 921**
First row complete before second
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `8b2d16364da01b5177fd3e72dcea6ee9e9cc972cb16c6572c901ecca6d832e12`
**Review the first row QD**: The selected frequency remains separate from dose.
**Review the preset 1 day**: The QD preset supplied this initial duration.
**Enter row Note A**: This narrow input clips its longer software-only text; the saved card later shows the complete note.
**Choose Add another Medication**: Use this selector for a second different medicine, rather than the small dosage-step plus inside the first row.

4. Enter a note for the first medicine

In the first row’s Note enter: SYNTHETIC SOFTWARE TRAINING ONLY — two-row prescription example A, inventory product. This is not treatment advice; do not dispense or administer. The input shows only its beginning; the complete saved Instructions cell will provide readback. Keep this row note separate from the shared prescription Note below the table.

5. Add a second different medicine

Select Add another Medication below the first row. This adds another medicine; the small plus inside an existing medicine adds a dosage step instead. In the new selector switch from Product to Medication, search HYMOX and choose the first illustrated HYMOX 500MG CAPS result. Several names repeat and the first result does not print its terminology code here. Do not select the star control.

Add another medication tabs in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:51:32.983Z · 1728 × 921**
Add another medication tabs
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `3102e237092e95650bef059f6147fdc6537cf6c0f134e7db5ff5e8d3b5a0df11`
**Locate Add another Medication**: The selector opens beneath the completed first row.
**Switch the new selection to Medication**: Use the terminology-backed tab for the second source; the first product row remains above.

Medication hymox search result in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:51:53.956Z · 1728 × 921**
Medication hymox search result
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `ea44faf7e39bc1fed9cd8fb6ec611f65a4e2d2a820d148d13eab8549fdf3b55c`
**Check Medication is selected**: This is separate from the Product source used for the first row.
**Search HYMOX**: The current medication search is populated with HYMOX.
**Choose the first illustrated HYMOX 500MG CAPS result**: Several display names repeat. Use the illustrated same configured source; its first result does not print a terminology code alongside the name. Do not choose a star button.

6. Inspect the independent second row

The first product row retains its quantity, QD, 1 day and note. The new HYMOX row has separate blank Dosage, Frequency, Duration and Note fields. Enter 1 in this second Dosage and explicitly choose 1 count rather than the initially suggested tablets. Open its Frequency, search QD and choose QD (Once a day), then review the preset 1 day.

Two distinct rows second empty in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:51:59.505Z · 1728 × 921**
Two distinct rows second empty
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `bcfa66bb71e21dcb7e197dba85ba694be629797177aeb22644d23e542636cb6d`
**Check the first row is retained**: Its 1 count, QD, 1 day and Note A remain while adding the second medicine.
**Read the second HYMOX row**: This is a different medicine row, not an additional dosage instruction under Paracetamol.
**Enter the second row’s quantity**: The code-backed medicine’s prescribing dose starts blank.
**Locate the blank second Frequency**: The first row’s QD has not been copied into this row.
**Locate the blank second Duration**: The first row’s duration has not been copied here.

Second row count choice in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:52:06.717Z · 1728 × 921**
Second row count choice
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `d6117abb1f8c5b3291c3e9eace5e3313a6a01f2116c58054e8b5ea32917167c1`
**Enter 1 for the second row**: The unit suggestions initially offer tablets.
**Choose 1 count explicitly**: Select count for this fictional software example rather than accepting tablets.

Second row qd choice in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:52:12.778Z · 1728 × 921**
Second row qd choice
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `731d5ed66f794a80cd0f83cef9876ffcf8de1c27dd84afd956399f836083f959`
**Search QD for the second row**: This open selector belongs to HYMOX.
**Choose QD (Once a day)**: Choose frequency separately for this medicine; the first row remains unchanged.

Both rows independent values in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:52:20.174Z · 1728 × 921**
Both rows independent values
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `dbe8eb3766010997d445eccbe5b9932a9c1e99d060ed44cb740df8f0f6828269`
**Review second-row 1 day**: Review the preset duration separately from its 1 count dose and QD frequency.
**Enter row Note B**: This is a separate row-specific software note from Note A above.
**Expand the advanced columns**: Use the header control, then scroll the medicine table horizontally right to inspect both requesters and authored dates.

7. Enter the second row note and check requesters

In the second Note enter: SYNTHETIC SOFTWARE TRAINING ONLY — two-row prescription example B, coded medicine. This is not treatment advice; do not dispense or administer. Expand the advanced columns using the header control and scroll the table right. Check Order, October 20th, 2026 and requester MANSOQ E2E Doctor for each row. Scroll left and collapse the advanced columns using the same header control shown before expansion. The notes and requesters belong to each medicine separately.

Both rows doctor authored date in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:52:33.464Z · 1728 × 921**
Both rows doctor authored date
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `120beae010852cd46284ad32b01c8783578d854b06594fe853684e745f170f01`
**Read first-row Order intent**: This belongs to the first new request.
**Read the first authored date**: The draft shows October 20th, 2026.
**Read the first Doctor requester**: The first request is assigned to MANSOQ E2E Doctor.
**Read second-row Order intent**: The second medicine has its own request metadata.
**Read the second authored date**: The second draft also shows October 20th, 2026.
**Read the second Doctor requester**: The second request also identifies MANSOQ E2E Doctor.
**Scroll the table horizontally left**: This is a horizontal scrolling gesture within the table. Return to the earlier illustrated header control and collapse the advanced columns.

8. Enter one shared prescription note

In the Note below the table enter: SYNTHETIC SOFTWARE TRAINING ONLY — two different medicine rows grouped in one demonstration prescription. All values are fictional interface examples. No clinical recommendation, dispensing or administration. This is one shared note for the grouped prescription, in addition to the separate row Notes A and B. The illustrated draft at this stage still has 1 count in each row; do not submit it yet. The next step makes the deliberate final quantity revision.

Review two rows shared note before submit in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:52:47.101Z · 1728 × 921**
Review two rows shared note before submit
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `fb1c58232da397227b971cc2a91d0f1543d478bc564ba1e9b959c72b12d98742`
**Enter one shared prescription Note**: This full software-only Note applies to the grouped prescription, separately from row Notes A and B.
**Read the earlier first-row quantity**: This earlier draft still has 1 count in the first row; the next step deliberately revises it before submission.
**Check second-row quantity remains 1 count**: The second row stays at 1 count through the final review.

9. Revise and review the final quantities

In the unsaved first product row change the quantity from 1 to 2 and explicitly choose 2 count. Keep the second HYMOX row at 1 count. Review the final first 2 count and second 1 count, each with its own QD and 1 day. Recheck both distinct row notes and the complete shared software-only Note. This revision occurs before the only Submit.

First row unsaved correction two count in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:53:10.768Z · 1728 × 921**
First row unsaved correction two count
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `aafe1e494738c3f0b047d1c77be0c93952b401dcfbf0f188954c0922fb336b70`
**Revise the unsaved first quantity to 2**: This changes only the first row before any Submit.
**Choose 2 count explicitly**: Keep count as the unit; the suggestion list also contains 2 tablets, which is not the illustrated selection.

Final two count one count review in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:53:11.323Z · 1728 × 921**
Final two count one count review
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `37b64600e7cdf02f35f5b6dfbe824a8263c0e669293c4475d8a7522c3e67c1fd`
**Review the revised first 2 count**: The first row is now 2 count, separately from its QD and 1 day.
**Review the second 1 count**: HYMOX remains 1 count, QD and 1 day.
**Check distinct row Note A**: Its narrow input shows the start; use the saved Instructions cell for full readback.
**Check distinct row Note B**: The second row keeps its own software-only note.
**Read the complete shared Note**: This remains one prescription-level note for both rows.
**Choose Submit once after review**: One Submit saves both new medicine rows into one prescription. Do not submit the rows separately.

10. Submit both rows together once

After reviewing both different medicine rows and their note scopes, choose Submit once. Wait for the form to return to Overview. Open Medicines, keep Prescriptions selected and choose the new 20/10/2026 12:53 PM Doctor card. Do not submit the two rows separately or edit the older Furosemide prescription.

Return overview after single submit in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:53:24.186Z · 1728 × 921**
Return overview after single submit
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `5d1e1cdbb1df37531baaa50c184095ff1fa7ad55c5ca8e4a6c1d05f6e89b08b6`
**Open Medicines after the return**: Wait for Overview before opening the saved result. This picture does not contain a success toast.

11. Read the single saved prescription

The selected 12:53 PM card identifies MANSOQ E2E Doctor and shows one shared Note above two medicine rows. Read Synthetic Training — Paracetamol 500mg with 2.00 count, QD and 1 day, then HYMOX 500MG CAPS with 1.00 count, QD and 1 day. Read the complete separate Instructions notes A and B. Both rows belong to this selected prescription, while the older Furosemide card remains separate.

12. Reload and verify the same grouped result

Use the browser’s Reload command once, wait for Medicines to load and select the same 12:53 PM Doctor card again. Verify both medicine rows, their different saved quantities, separate QD and 1 day fields, the shared Note and both complete row notes. Do not repeat Submit to refresh the display.

Reloaded same two row prescription in a fictional software-training example — **Recorded release 3dfb7c9f · 2026-10-20T09:54:15.227Z · 1728 × 921**
Reloaded same two row prescription
Capture details
Observed 3dfb software on 20 October 2026. Two different new medicine requests grouped in one fictional demonstration prescription. Earlier draft1count each is explicitly revised before the sole Submit to product2count/codedmedicine1count. Original pixels/times preserved; no physical dispensing or administration.
Image SHA-256 `9ba1629a4643a98c8f5d02ee9d4d5e03a9d67e7d086e75b530731f5fe94a85dc`
**Reselect the same card after browser Reload**: The same 12:53 PM prescription still contains both rows after one normal reload.
**Recheck the first 2.00 count**: The revised first quantity persists.
**Recheck the second 1.00 count**: The separate second quantity persists.
**Recheck both distinct row notes**: The shared Note and both complete Instructions cells remain visible; no second Submit is needed.

A second medicine differs from a second dosage step

Add another Medication produces a new row with a different medicine name and independent prescribing fields. A dosage-step plus inside a row instead adds an instruction for that same medicine. In this exercise the final prescription contains two different medicine rows, each with one instruction.

Review product defaults and coded-medicine blanks separately

The configured inventory product supplies an initial 1 count. The Medication-tab HYMOX row instead starts with a blank dose and separate blank frequency and duration. Neither starting state is a prescribing recommendation. Review each row independently and choose explicit units rather than carrying assumptions from the neighbouring medicine.

Notes and saved grouping have separate scopes

Each medicine has its own row Note, shown in its saved Instructions cell. The shared Note appears once above the selected prescription’s medicine table. One final Submit groups the two new rows into the one new card. This lesson does not demonstrate billing, physical stock issue, dispensing, administration or a care decision.

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:281 · 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:598 · 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