MANSOQ Knowledge
← Knowledge library

Laboratory & radiology

Collect a specimen

Create an order-linked draft specimen, identify it, validate quantity and unit, save collection, and select QR labels.

Current source · Source reviewed; scoped synthetic Nurse and Doctor laboratory workflow observed · 6 min read

Before you begin

1. Open the required specimen card

Open the correct service request and confirm the patient, service and specimen requirement. In the configured example, Synthetic Training — Venous Blood is Collection Pending and report creation waits for collection.

Required specimen before report creation. Actual MANSOQ software with explicitly synthetic training records.
Required specimen before report creation · 2026-10-18. Audited production build with explicitly synthetic local Polyclinic data. No specimen tested, clinical interpretation, real care or external transaction.

2. Create the draft and identifier

Select Collect Specimen. MANSOQ creates an order-linked draft specimen and displays its accession identifier/QR under Generate QR Code. Wait for draft creation and QR generation to finish before proceeding.

Generated draft specimen identifier and QR. Actual MANSOQ software with explicitly synthetic training records.
Generated draft specimen identifier and QR · 2026-10-18. Audited production build with explicitly synthetic local Polyclinic data. No specimen tested, clinical interpretation, real care or external transaction.

3. Record collection details

Check Collection Date & Time, Quantity and its unit, optional Body Site, Fasting Status and Notes, plus any configured container requirements. MANSOQ records the signed-in user as collector. The example leaves specialist preparation fields unconfigured and explicitly labels every entry TRAINING ONLY.

Review collection details and save. Actual MANSOQ software with explicitly synthetic training records.
Review collection details and save · 2026-10-18. Audited production build with explicitly synthetic local Polyclinic data. No specimen tested, clinical interpretation, real care or external transaction. Quantity 2 mL is interface demo data, not a collection protocol. The collection time control displays the UTC clock in this build; saved UTC instant and Riyadh timeline were independently checked.

4. Resolve quantity and unit validation

If you enter a quantity, select its unit; if you select a unit, enter its quantity. Quantity without a unit shows This field is required and does not collect the draft. The example chooses milliliter after this validation.

Missing quantity unit is blocked. Actual MANSOQ software with explicitly synthetic training records.
Missing quantity unit is blocked · 2026-10-18. Audited production build with explicitly synthetic local Polyclinic data. No specimen tested, clinical interpretation, real care or external transaction. Quantity 2 mL is interface demo data, not a collection protocol. The collection time control displays the UTC clock in this build; saved UTC instant and Riyadh timeline were independently checked.
Review collection details and save. Actual MANSOQ software with explicitly synthetic training records.
Review collection details and save · 2026-10-18. Audited production build with explicitly synthetic local Polyclinic data. No specimen tested, clinical interpretation, real care or external transaction. Quantity 2 mL is interface demo data, not a collection protocol. The collection time control displays the UTC clock in this build; saved UTC instant and Riyadh timeline were independently checked.

5. Collect and verify

Select Collect. Confirm Available, Collected by the intended user, and the Workflow Progress collection entry. The synthetic example independently verifies the same specimen ID, Nurse collector and saved quantity.

Review collection details and save. Actual MANSOQ software with explicitly synthetic training records.
Review collection details and save · 2026-10-18. Audited production build with explicitly synthetic local Polyclinic data. No specimen tested, clinical interpretation, real care or external transaction. Quantity 2 mL is interface demo data, not a collection protocol. The collection time control displays the UTC clock in this build; saved UTC instant and Riyadh timeline were independently checked.
Available specimen recorded under Nurse. Actual MANSOQ software with explicitly synthetic training records.
Available specimen recorded under Nurse · 2026-10-18. Audited production build with explicitly synthetic local Polyclinic data. No specimen tested, clinical interpretation, real care or external transaction. Quantity 2 mL is interface demo data, not a collection protocol. The collection time control displays the UTC clock in this build; saved UTC instant and Riyadh timeline were independently checked.

6. Select and print specimen labels

Select Print All QR Codes. In Print QR Codes, check only the required specimen labels, use Select All or Clear Selection when appropriate, choose whether to show patient details and specimen ID, then Print Selected. Verify each identifier against the correct container. The screenshot establishes selection controls; no physical printing is claimed.

Select specimen QR labels for printing. Actual MANSOQ software with explicitly synthetic training records.
Select specimen QR labels for printing · 2026-10-18. Audited production build with explicitly synthetic local Polyclinic data. No specimen tested, clinical interpretation, real care or external transaction. Printing controls/view are shown; physical printing and PDF download were not tested.

Generate or scan an identifier

Generate QR Code is the illustrated path. Scan Existing is also exposed for an existing accession identifier; scanner hardware and that alternate workflow are not verified by this example.

Generated draft specimen identifier and QR. Actual MANSOQ software with explicitly synthetic training records.
Generated draft specimen identifier and QR · 2026-10-18. Audited production build with explicitly synthetic local Polyclinic data. No specimen tested, clinical interpretation, real care or external transaction.

Collection time display limitation

In this audited build, the datetime-local control uses the ISO UTC clock directly. In the Riyadh training example the default field showed 16:31 while the saved collection timeline correctly showed 19:31 local. The default instant was preserved and independently checked. Verify the intended instant and facility time zone; do not repeatedly adjust a valid saved time to compensate for its display.

Review collection details and save. Actual MANSOQ software with explicitly synthetic training records.
Review collection details and save · 2026-10-18. Audited production build with explicitly synthetic local Polyclinic data. No specimen tested, clinical interpretation, real care or external transaction. Quantity 2 mL is interface demo data, not a collection protocol. The collection time control displays the UTC clock in this build; saved UTC instant and Riyadh timeline were independently checked.
Available specimen recorded under Nurse. Actual MANSOQ software with explicitly synthetic training records.
Available specimen recorded under Nurse · 2026-10-18. Audited production build with explicitly synthetic local Polyclinic data. No specimen tested, clinical interpretation, real care or external transaction. Quantity 2 mL is interface demo data, not a collection protocol. The collection time control displays the UTC clock in this build; saved UTC instant and Riyadh timeline were independently checked.

Verified configuration and limits

This is a limited training configuration with HL7 venous-blood type, a source-backed quantity/unit and no configured clinical preparation, body-site protocol, reference range or interpretation. A transient QR placeholder resolved after draft creation and was not a persistent failure. No specimen was collected or tested in real life.

Available specimen recorded under Nurse. Actual MANSOQ software with explicitly synthetic training records.
Available specimen recorded under Nurse · 2026-10-18. Audited production build with explicitly synthetic local Polyclinic data. No specimen tested, clinical interpretation, real care or external transaction. Quantity 2 mL is interface demo data, not a collection protocol. The collection time control displays the UTC clock in this build; saved UTC instant and Riyadh timeline were independently checked.

Troubleshooting

This field is required beside quantity/unit

Complete both parts of the quantity or leave both empty when the approved procedure permits. Do not enter an arbitrary clinical quantity to pass validation.

Specimen requirements are missing

Ask the catalogue owner to configure approved specimen definitions on the activity definition. The configuration accepts same-facility resource slugs; a blank UI is not evidence of a specimen-free assay.

Collection time differs from the local clock

Check the known UTC display issue, the intended collection instant, and the saved workflow timeline with an authorized reviewer before changing data.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.