Knowledge library

Browse all published medical, non-medical and technical teaching guides. Enable JavaScript for search and role filters.

Access & administration

Maintain custom value-set metadata and distinguish lookup success from a valid concept — Recover real name/slug/concept validation, recognize the current lookup-display contract issue, save an unlinked Draft skeleton and verify its retirement.
Build a report template, preview sample data and control its lifecycle — Recover required metadata, choose a matching report context, save a Draft, inspect HTML/PDF previews and verify Active or Retired state.
Generate an encounter report, verify its PDF and use viewing, download and print controls — Confirm the correct encounter, choose an Active template, verify the stored artifact and distinguish actual resource values from template sample previews.
Disassociate and reassociate a device location while preserving its history — Review current storage, close its open interval, select the authorized location and verify the new interval without losing prior history.

Access & roles

Resolve missing buttons and read-only encounter views — Check context, active record state and assigned permissions before escalating a missing clinical action.
View the permissions matrix — Read the role-permission matrix before assigning access and distinguish this view from role editing.
Upload and independently verify source evidence — Create private, traceable evidence for insurance contracts, tariffs, policies and configuration.
Review, simulate and publish configuration safely — Move source-backed rules through explicit approval and preserve historical decisions.
Explain why a financial decision was made — Read the configuration package, selected rules, rejected candidates and evidence behind an amount.
Assign RCM permissions by responsibility — Separate master-data editing, publication, claims, bank cash and treasury confirmation.
Protect credentials, patient payloads and private evidence — Keep operational secrets and clinical material out of public knowledge content and exports.
Evaluate enterprise go-live readiness — Use the evidence-backed setup worklist before treating a configuration package as production-ready.
Assign a role to a user — Link an existing user to a facility or organizational group and assign an allowed role at the correct scope.
Clone and revise an unassigned custom role without changing the System definition — Inspect the copied role, replace its permissions with one synthetic read permission, save the custom definition and revise only its description.
Read the role-permission matrix without assuming effective user access — Compare exact permission rows and role columns, including Billing Officer payment limits and the broad Staff fallback used for Reception.
Inspect built-in roles and the System role actions boundary — Read role contexts and permission counts, and understand why a built-in System role offers Clone rather than Edit.
Roles and Permission — Definition A role in MANSOQ is a named set of permissions. A permission allows one action, for example to register a patient. MANSOQ builds every permission into the product, so you cannot create or change a permission. You group permissions…
Facility Organization — A facility organization is a department, team, or group inside a single facility — Cardiology, the Emergency Ward, the night-shift nursing team. It is how one facility is divided internally so that staff, patients, and resources can be grouped,…
Organisation — Definition An organization in MANSOQ is a government or administrative area, for example a state or a district. MANSOQ arranges these areas in a hierarchy, from the country down to the ward. To open the hierarchy, select Organizations in the…
Responsibility — Definition A responsibility in MANSOQ is a group that gives a person a designation or a duty across MANSOQ. A responsibility applies across MANSOQ. It does not belong to one facility. For example, you create a responsibility for the people who…
Supplier — Definition A supplier in MANSOQ is a vendor or distributor that you order supplies from. MANSOQ stores a supplier as one type of organization. MANSOQ shows suppliers in their own list, separate from Governance organizations and from…
User — Definition A user in MANSOQ is the staff account of a person who works in your organization. Doctors, nurses, and administrators sign in to MANSOQ with this account. A user account is separate from a patient record. A user is closest to two…
Assign a role to a user — This flow describes how to link a user to an Organization, a Supplier, a Responsibility, or a Department, and give that user a role. The link and the role together grant the user access. Note: To create a user account, see Create a user. This…
Change or remove a user's role — This flow describes how to change the role of a user in an Organization, a Supplier, a Responsibility, or a Department. It also describes how to remove the user from there. Pre-requisites - The user is already linked there. See Assign a role to…
Create a role — This flow describes how to create a new role in MANSOQ. A role groups the permissions that you give to a user. Pre-requisites - You are a super administrator in MANSOQ. Permissions MANSOQ does not control role management with a permission. Only…
Edit or clone a role — This flow describes how to change a custom role in MANSOQ. It also describes how to clone a role. MANSOQ includes system roles, such as Doctor. You cannot change a system role. Clone the system role, then adjust the permissions of the copy. The…
View the permissions matrix — This flow describes how to view the permissions matrix in MANSOQ. The matrix shows which permissions each role holds. Pre-requisites - You can open the Admin sidebar in MANSOQ. Permissions MANSOQ does not control this page with a permission.…
Create an organization — This flow describes how to create a government organization in MANSOQ. You create the organization under a parent organization in the Governance hierarchy. Pre-requisites - You are a MANSOQ superuser. - The parent organization for the new…
Delete an organization — This flow describes how to delete a government organization in MANSOQ. MANSOQ deletes only an organization that has no child organizations. Pre-requisites - You are a MANSOQ superuser. - The organization has no child organizations. If the…
Update an organization — This flow describes how to change the name and the description of a government organization in MANSOQ. Pre-requisites - You are a MANSOQ superuser. - The organization exists in the Governance hierarchy. Permissions MANSOQ does not grant this…
View the organization hierarchy — This flow describes how to browse the hierarchy of government organizations in MANSOQ. The hierarchy shows each organization and the organizations below it. Pre-requisites - You have access to at least one government organization. - You have…
Create a responsibility — This flow describes how to add a new responsibility in MANSOQ. Only a super administrator creates a responsibility. Pre-requisites - You are a super administrator in MANSOQ. The Admin sidebar opens only for a super administrator. Permissions No…
Link responsibilities to each other — This flow describes how to link one responsibility to another in MANSOQ. A link records which responsibility oversees another responsibility. Pre-requisites - You are a super administrator in MANSOQ. The Admin sidebar opens only for a super…
Add or manage users in a responsibility — This flow describes how to add people to a responsibility in MANSOQ. It also describes how to change or remove the designation of a person. Pre-requisites - A super administrator created the responsibility. See Create a responsibility. - You…
View your responsibilities — This flow describes how to open the responsibilities that you belong to from your dashboard in MANSOQ. Pre-requisites - You belong to at least one responsibility. See Add or manage users in a responsibility. Permissions You need no extra…
Create a supplier — This flow describes how to add a new supplier in MANSOQ. After you create the supplier, you can select it as the vendor on a purchase order. Pre-requisites - You have the permission listed below. Permissions Permission Access --- --- Can Create…
Update a supplier — This flow describes how to change the name and the description of a supplier in MANSOQ. Pre-requisites - The supplier is in the Suppliers list. - You have the permission listed below. Permissions Permission Access --- --- Can Manage…
Change your password — This flow describes how you change your own password in MANSOQ. It covers a change from your user profile, and a reset when you forget your password. Note: MANSOQ has no option for an administrator to reset the password of another user. Only…
Create a user — This flow describes how to create a new user account in MANSOQ. You create the user from the Users tab of an organization, a responsibility, or a department. Pre-requisites - You have the permission listed below. Permissions Permission Access…
Edit a user's profile — This flow describes how to change the profile details of a user in MANSOQ. You can edit your own profile, or any profile if you are a MANSOQ superuser. Pre-requisites - You view your own profile, or you are a MANSOQ superuser. Permissions…
Search for a user — This flow describes how to find a user in MANSOQ. You can search inside an organization, a responsibility, or a department. You can also search the users list of a facility. Pre-requisites - You are signed in to MANSOQ. - You have the…
Turn on two-factor authentication — This flow describes how you add two-factor authentication to your own user account in MANSOQ. Two-factor authentication uses a time-based one-time password from an authenticator app. Pre-requisites - You are signed in as yourself. - You have an…
Manage organizations for a questionnaire — This flow describes how to control which organizations can see and use a questionnaire in MANSOQ. Pre-requisites - The questionnaire is saved in MANSOQ, and you open it to change it. See Create a questionnaire. - You have the permissions listed…
Add users to a department — This flow describes how to manage the members of a department in MANSOQ. You can add a user, change a member's role, and remove a member. Pre-requisites - The department is set up in the facility. - The user has an account in MANSOQ. If the…
Manage a location's organizations — This flow describes how to link facility departments to a location. The linked departments control which members can access the location. Pre-requisites - The location is set up in the facility. See View locations. - The facility department…
Organization — Organizations are MANSOQ's FHIR-aligned grouping primitive: a nested tree that groups permissions and resources. A node might represent all doctors, a Cardiology sub-team, or a governance unit, and permissions attached to a parent flow…
Permission Association — RoleAssociation grants a RoleModel to a User inside a specific context — an organization or facility. A role is a named collection of permissions; the association scopes that collection to one user in one context. A user can hold many roles…
Permission — A permission is the ability to perform one action in one context — read it as "Action on Resource", like "Can Create Patient" in the PATIENT context. Permissions are the atoms of MANSOQ's access control: code declares them, the sync command…
Role — A role is a flat set of permissions granted to a user inside one organizational boundary. It carries no semantics of its own — "Doctor", "Doctor Read Only" and "Doctor Scheduler" are three unrelated permission sets, not variations on a job…
User & Skills — A User is a MANSOQ account — authentication, profile, clinician credentials, and notification/MFA data. The Django model is the storage layer. The Pydantic resource specs in care/emr/resources/user/ and care/emr/resources/mfa/ are the API…

Appointments & queues

Check in as Staff and start the consultation as Doctor — Follow one appointment from Staff booking and check-in through the assigned Doctor’s saved ambulatory encounter, with the correct record, time and actor at each handoff.
Review the populated appointment document — Open the actual appointment print preview and verify facility, patient, time, practitioner, note and Staff/Doctor audit names before output.
Reschedule an appointment and verify both records — Record the previous-appointment reason, review a replacement slot, and distinguish the new Booked record from the retained Rescheduled record.
Cancel an appointment and verify its retained history — Use the required cancellation reason, confirm the intended action, and verify Cancelled without deleting the appointment.
Book an existing patient with a scheduled practitioner — Verify the existing patient, choose a department and practitioner, review available dates and the selected time, and confirm the saved appointment.
Book a patient appointment through the public portal — Find a configured facility and practitioner, choose an offered time and confirm the correct patient.
Read, reschedule and cancel patient appointments — Distinguish time-based appointment tabs from status and verify the final result after each change.
Book an appointment and start consultation — Choose a scheduled resource, date and slot, confirm a patient booking and continue through the appointment detail page.
Create a schedule template — Create a resource schedule with a validity period, weekly sessions, slot settings and visibility.
Create or generate a queue token — Create a patient token for a scheduled resource and category with optional supporting notes.
Manage a token queue — Open a resource queue, follow token progress, serve the next patient and manage service points.
Create and verify private recurring practitioner availability — Use the linked practitioner’s Availability tab, validate required fields and save an actual Monday schedule with independently verified dates and capacity.
Appointment Booking — A booking claims a specific time slot on a practitioner, location, or service's calendar for one patient, and tracks that appointment from the moment it is requested until the patient is seen or the slot is released. It is how published…
Schedule Exception — Definition A schedule exception in MANSOQ records a period when a resource is not available, even though a schedule makes it available. The resource is a practitioner, a location, or a healthcare service. An exception overrides the regular…
Schedule & Availability — Definition A schedule in MANSOQ records when a resource can be booked at a facility. The resource is a practitioner, a location, or a healthcare service. Each schedule holds one or more availability sessions. A session states the days of the…
Token — Definition A token in MANSOQ is a numbered place in a queue. MANSOQ gives a token to a patient so that staff call the patient in order. A token belongs to one token queue. The queue holds the tokens for one resource on one date. The resource is…
View a patient's appointments and tokens — This flow describes how to open Patient Home and view the appointments and queue tokens of a patient in MANSOQ. Pre-requisites - The patient is registered in MANSOQ. - You verified the patient's identity from search, or you opened the patient's…
Create a schedule exception — This flow describes how to record a period when a resource is not available in MANSOQ. The exception overrides the regular schedule, and MANSOQ does not offer slots during that period. See Schedule Exception. Pre-requisites - The resource is…
Remove a schedule exception — This flow describes how to remove a period of unavailability from a resource in MANSOQ. Use it when the resource becomes available again. See Schedule Exception. Pre-requisites - The schedule exception is created in MANSOQ. - You can open the…
View schedule exceptions — This flow describes how to see the periods when a resource is not available in MANSOQ. See Schedule Exception. Pre-requisites - The resource is available in the facility. - You have the permission listed below. Permissions Permission Access ---…
Create a schedule template — This flow describes how to create a schedule template for a resource in MANSOQ. The template states when the resource is available, and MANSOQ creates bookable slots from it. See Schedule & Availability. Pre-requisites - The facility is created…
Delete a schedule template — This flow describes how to remove a schedule template from a resource in MANSOQ. Use it when the template is no longer correct. See Schedule & Availability. Pre-requisites - The schedule template is created in MANSOQ. - You can open the…
Edit a schedule template — This flow describes how to change a schedule template in MANSOQ. Use it when the availability of a resource changes. See Schedule & Availability. Pre-requisites - The schedule template is created in MANSOQ. - You can open the schedule of the…
View schedule templates — This flow describes how to see the schedule templates of a resource in MANSOQ. Use it to check when a practitioner, a location, or a healthcare service is available. See Schedule & Availability. Pre-requisites - The facility is created in…
Cancel a token — This flow describes how to cancel a token in MANSOQ. Use it when the patient leaves, or when staff do not serve the token. See Token. Pre-requisites - The token is in a queue. - You have the permissions listed below. Permissions Permission…
Create a token category — This flow describes how to create a token category for a facility in MANSOQ. A category groups tokens, for example by the kind of visit. See Token. Pre-requisites - The facility is created in MANSOQ. - You have the permissions listed below.…
Create a token — This flow describes how to give a token to a patient in MANSOQ. The token places the patient in a queue, and staff call the patient in order. See Token. Pre-requisites - The patient is registered in MANSOQ. - A token category is created for the…
Manage a token queue — This flow describes how to work through a token queue in MANSOQ. Staff serve patients in order and record when each patient is finished. See Token. Pre-requisites - A token queue holds at least one token. - You have the permissions listed…
Booking — A booking puts a patient into a concrete time slot generated from a Schedule. TokenSlot is a bookable unit of availability; TokenBooking is a patient's appointment against that slot, carrying its status through the lifecycle. You touch both…
Schedule & Availability — A schedule is a repeatable block of time during which a resource — a practitioner, location, or healthcare service — can be booked. You attach availabilities to it and exceptions that block out specific dates. Source: - Model:…
Token — A Token is a numbered ticket a patient holds in a walk-in queue — use it when scheduling runs on first-come flow rather than fixed appointment slots. The patient gets a number against a schedulable resource , optionally routed to a sub-queue or…

Billing

Create an invoice — Select charge items for an account and create an invoice with the required invoice details.
Record a payment — Record a payment, advance or credit note with the correct amount, method, account and date.
View an account — Read account details, financial totals, billing lifecycle and transaction tabs for the selected patient.
Follow a complete synthetic self-pay billing example — Walk through a real saved charge, draft, issue, receipt, status-only API continuation and completed account closure, with the current UI defect made explicit.
Resolve a fully paid invoice that refuses UI balancing — Recognize the audited finalized-invoice payload mismatch and the separately tested, authorized status-only API continuation.
Record an account advance and return it in separate credit entries — Follow the actual saved 100 SAR advance, 30 SAR partial return, remaining 70 SAR return, printable receipt and completed account closure.
Account — Definition An account in MANSOQ groups the charge items, invoices, and payments of one patient at one facility. Every charge item, invoice, and payment belongs to exactly one account. The account shows what the patient owes and what the patient…
Charge Item — Definition A charge item in MANSOQ records one billable service or item against a patient's account. A consultation, a procedure, or a dispensed medicine is each a charge item. Charge items are the building blocks that MANSOQ bundles into…
Invoice — Definition An invoice in MANSOQ groups one or more billable charge items from an account and bills them to the patient or payer. MANSOQ uses the invoice to track the amount that is owed and whether the payer has paid it. Every invoice belongs…
Payment Reconciliation — Definition A payment reconciliation in MANSOQ records a payment that a patient or an insurer makes against an account. You can also record a credit note, which returns money to the payer and subtracts the amount from the balance. A payment can…
Charge Item Definition — Definition A charge item definition in MANSOQ is a reusable pricing template. It holds the price, the taxes, and the discounts for one billable service or item in your facility. When you apply a charge item definition, MANSOQ creates an actual…
Deactivate a user account — This flow describes how to deactivate a user account in MANSOQ. MANSOQ archives the account, or removes it, and the person can no longer sign in. MANSOQ names this action Delete Account. Pre-requisites - You are a MANSOQ superuser. - You know…
Advance the billing status of an account — This flow describes how to move an account forward in the billing cycle. The billing status shows where the account is in the billing cycle. It is separate from the Active or Inactive status of the account. Pre-requisites - Someone created the…
Create an account — This flow describes how to create an account for a patient at a facility. The account collects the charges and payments for that patient at that facility. Pre-requisites - The patient is registered in MANSOQ. - You are a member of the facility…
Edit an account — This flow describes how to change the details of an account in MANSOQ. You can update the name, description, status, billing status, and primary encounter. Pre-requisites - Someone created the account, and you open its account page. - If you…
Settle and close an account — This flow describes how to settle an account in MANSOQ and close it with a reason. Pre-requisites - Someone created the account, and you open its account page. - You have the permissions listed below. Permissions Permission Access --- --- Can…
View an account — This flow describes how to open an account in MANSOQ. The account page shows the financial summary, the billing progress, and the billing records of the patient. Pre-requisites - Someone created the account for the patient at the facility. -…
Add charge items — This flow describes how to add one or more charge items for a patient in MANSOQ. You add charge items to record the billable products and services that the patient receives. Pre-requisites - You have the permissions listed below. - The patient…
Cancel a charge item — This flow describes how to cancel a charge item in MANSOQ. You give a reason for the cancellation when you change the status. Pre-requisites - Someone added the charge item, and its status is Billable. - If the charge item is attached to an…
Edit a charge item — This flow describes how to change the details of a charge item in MANSOQ. You can edit a charge item only while its status is Billable. Pre-requisites - Someone added the charge item, and you open it from an appointment, a service request, or…
Move charge items to another account — This flow describes how to move one or more charge items from one account to a different account of the same patient. Use this flow when staff add charge items to the wrong account. Pre-requisites - The patient has the account that holds the…
Cancel an invoice or mark it entered in error — This flow describes how to cancel an invoice in MANSOQ, or how to mark it as Entered in Error. Pre-requisites - You open the page of the invoice that you want to cancel. - The invoice is not Balanced, Cancelled, or Entered in Error. - The…
Create an invoice — This flow describes how to create an invoice for an account in MANSOQ. The new invoice starts in the Draft state. Pre-requisites - You create the invoice for an account of the patient at your facility. - The account has Billable charge items,…
Edit an invoice — This flow describes how to change the details and the items of a draft invoice in MANSOQ. Pre-requisites - Someone created the invoice, and its status is Draft. - You have the permissions listed below. Permissions Permission Access --- --- Can…
Issue an invoice — This flow describes how to issue a draft invoice in MANSOQ. When you issue an invoice, MANSOQ fixes its line items and offers to record a payment. Pre-requisites - The invoice is in Draft status. - The invoice has at least one charge item. -…
Lock or unlock an invoice — This flow describes how to lock or unlock an invoice in MANSOQ. A lock prevents further changes to the invoice. A lock also hides the invoice totals from anyone without the Can Manage Locked Invoice permission. Pre-requisites - Someone created…
Mark an invoice as balanced — This flow describes how to mark an issued invoice as balanced in MANSOQ. MANSOQ checks the payments and credit notes recorded against the invoice, then closes it. Pre-requisites - The invoice is issued. See Issue an invoice. - You record the…
View an invoice — This flow describes how to open an invoice in MANSOQ and read its details. You can also print a copy of the invoice. Pre-requisites - Someone created the invoice at your facility. - You are a member of the facility that holds the invoice. - If…
Cancel a payment or mark it entered in error — This flow describes how to cancel a payment or mark it entered in error. MANSOQ recalculates the account balance after you confirm. Pre-requisites - You recorded the payment in MANSOQ, and you open its payment detail page. - You have the…
Move a payment to another account — This flow describes how to move one or more payments from one account to a different account of the same patient. Use this flow when you record a payment against the wrong account. Pre-requisites - You recorded the payments for the patient at…
Record a payment — This flow describes how to record a payment reconciliation in MANSOQ. You record a payment against an issued invoice, or as a general credit on an account. Pre-requisites - If you record a payment against an invoice, the invoice is issued. - If…
View a payment — This flow describes how to open a payment in MANSOQ and read its details. You can also print a receipt for the payment. Pre-requisites - You are a member of the facility. - Someone recorded the payment at your facility. - You have the…
Create a charge item definition — This flow describes how to create a charge item definition in MANSOQ. A charge item definition is a priced template for a service or an item. Pre-requisites - You are a member of the facility. - A category for charge item definitions is set up…
Update or retire a charge item definition — This flow describes how to change the details of a charge item definition in MANSOQ. It also describes how to retire a charge item definition that your facility no longer uses. Pre-requisites - You are a member of the facility. - The charge…
Account — An Account is the financial bucket that aggregates every transaction made against a patient within a facility. You touch it indirectly: charge items land on a patient's default account, and invoices and reconciliations settle against it.…
Charge Item — A ChargeItem is a single billable line for a service or product supplied to a patient — what was charged, the quantity, the unit and total price components, and any discounts or override reasons. You create one against a patient ; it always…
Invoice — An Invoice groups charge items raised against a single account into one billable document, with snapshotted line items, totals, and a lifecycle status. You touch it whenever you bill a patient, issue a refund, or reconcile payments. The data…
Payment Reconciliation — A PaymentReconciliation is a single payment recorded against an Account, and optionally allocated to one Invoice. It captures how much was paid, by what method, when, and by whom — mirroring the FHIR PaymentReconciliation resource. Reach for it…
Charge Item Definition — A charge item definition is a facility's pricing template for a billable resource: it answers "how much does resource X cost". It binds the resource to a set of price components — base rate, surcharges, discounts, and taxes — that get evaluated…

Catalogue & forms

Create an activity definition — Define an orderable activity with service details, requirements and catalogue categorization.
Create an observation definition — Define reportable observations, value details and components for configured tests.
Create a questionnaire — Create and organize a questionnaire with its slug, subject type, organizations and questions.

Clinical care

Update a saved symptom, avoid duplicates and retain an error correction — Review existing-row restrictions, save a status and note change, then understand entered-in-error correction and the filtered history display.
Record a coded symptom with onset, severity and verification — Create and verify a structured symptom entry while reviewing defaults, onset, clinical status, severity and verification separately.
Read symptom history, exact onset, author and source encounter — Distinguish a history creation-date group from symptom onset, inspect the saved note and author, and return to its source encounter.
Update a reported medication statement and correct an erroneous record — Save a status and note update, cancel a removal prompt, then retain an entered-in-error record while understanding normal list filtering.
Record and verify No, zero and date/time answers — Use configured form controls, verify conditional behavior and confirm saved values before interpreting an answer or printing.
Print one response or the questionnaire responses for this encounter — Choose the correct scope, inspect authors and values, and verify the actual saved browser PDF without treating it as a full clinical export.
Review and print a diagnostic report — Check the selected Final report, result/unit and requester, then verify the actual browser PDF and separate print attribution.
Record and verify reported medication information — Use the structured medication statement form, identify the reporter, validate the dates and verify a saved record separately from prescriptions and administrations.
Review historical medication sources before copying a statement — Understand historical prescription selection, required reported-use fields and the inventory-prescription import limitation before saving.
Upload, preview and download encounter files — Select and name separate files, correct validation, verify completed uploads, inspect image controls and download the actual stored document.
Rename, archive and find encounter files — Review name changes, cancel an archive, correct its reason, read the retained audit metadata and distinguish active, archived and filtered empty results.
Attach a file through a configured clinical form — Complete a required structured Files question, correct missing names, remove an unsaved selection and inspect the saved file with the original attribution limitation.
Record consent documentation with dates and supporting files — Review decision and status separately, correct date-period ordering and missing attachment names, then verify the saved record and exact supporting document.
Review consent documents and update status or note — Inspect exact saved documentation, preview/download the supporting file and use the limited Status/Note edit without changing the original decision or period.
Assign an encounter location — Assign a bed or other location, transfer between locations, and correct or close location stays.
Complete an encounter — Complete the encounter after required discharge work and understand which records become read-only.
Create an encounter — Start an encounter from a patient or appointment with the correct care setting, date, status and department.
Discharge a patient — Record discharge disposition, date and advice, then distinguish discharge from encounter completion and bed release.
Add and remove encounter department links — Distinguish pending department selections from saved encounter links, handle duplicate refusal and verify removal with its access-scope limitation.
Manage encounter care-team participants and the primary member — Select a department, add coded participants, change their primary order, handle duplicates and remove a participant with confirmation.
Record a consent — Record encounter consent details and category, then attach supporting documents.
Record a diagnosis — Find a coded diagnosis, check its clinical and verification status, and submit it to the correct encounter.
Record a symptom — Record coded symptoms with onset, clinical status and notes in an active encounter.
Record an allergy — Record a coded allergy or intolerance and review clinical status, verification and criticality before submission.
Restart an encounter — Reopen a completed encounter only within the deployment restart window and your assigned permissions.
Start a discussion — Start a titled patient or encounter discussion and keep the two communication contexts distinct.
Update encounter details — Update encounter details, priority and hospitalization information while respecting date and access controls.
Upload a file — Upload and name files in an intended clinical context; the current screenshot sequence demonstrates separate encounter uploads, preview and actual download.
Review patient clinical history and verify the source encounter — Review patient-wide forms, diagnoses, allergies and diagnostic reports; inspect their notes and source encounter before returning to current work.
Review and update an existing patient allergy — Distinguish clinical status from verification, update an existing allergy and verify the saved patient record.
Create a resource request and record coordination notes — Choose a public support facility, complete the required synthetic request details, verify the saved Pending record and review the posted note.
Update a resource request status and review its request letter — Review the available statuses, verify a saved Approved record and inspect the actual populated request-letter preview.
Allergy Intolerance — Definition An allergy or intolerance in MANSOQ is a substance that causes a reaction in a patient. The substance is a food, a medication, an environmental substance, or a biologic substance. Every allergy belongs to one patient. You record it…
Clinical - Care Team — Definition The care team lists the staff who look after a patient during one encounter. Each entry names a staff member and the clinical role that person holds on that encounter. MANSOQ keeps the team as a list on the encounter. MANSOQ does not…
Condition — Definition A condition in MANSOQ is a clinical problem that affects a patient. MANSOQ records a condition as a symptom or as a diagnosis. A symptom is what the patient reports or the clinician observes. A diagnosis is the clinician's…
Consent — Definition A consent in MANSOQ is a record of the permission or the refusal that a patient gives for a treatment, for a research study, or for the sharing of information. Each consent belongs to one encounter. MANSOQ shows the consents of an…
Encounter — Definition An encounter in MANSOQ records one interaction between a patient and your facility. The interaction is an outpatient visit, an admission, an observation stay, an emergency visit, a virtual consultation, or a home visit. The encounter…
Clinical - Files — Definition A file in MANSOQ is an attachment that you upload and link to another record. You can attach a file to a Patient, an Encounter, a Consent, a Diagnostic Report, or a Service Request. Files keep scans, photos, recordings, and documents…
Notes — Definition Clinical Notes is the space where staff record and exchange written notes about a patient. MANSOQ groups the messages into titled discussions, so different topics stay separate. You find Clinical Notes in the Notes tab, which shows a…
Observation — An observation is a single recorded fact about a patient — a blood pressure of 120/80, a body temperature, a coded answer to a screening question. It is the smallest unit of clinical data in MANSOQ: the structured building block that, gathered…
Questionnaire Response — Definition A questionnaire response in MANSOQ is the record of one submitted form. MANSOQ files a response each time a user submits a form for a patient. MANSOQ also files a response when a user saves a structured clinical record, such as an…
Activity Definition — Definition An activity definition in MANSOQ is a reusable template for a service, a procedure, or a test that clinicians order. A common example is a "CBC Test". The template holds the details that a clinician otherwise types each time. When a…
Observation Definition — Definition An observation definition in MANSOQ is a reusable template for one laboratory test or clinical test. The template records what the test measures and the type of value that a result holds. It also records the rules that MANSOQ uses to…
Questionnaire Response Template — Definition A questionnaire response template is a saved set of medications and service requests. You apply the template when you fill a questionnaire. The template prevents the entry of the same orders for each patient. You can change every…
Questionnaire — Definition A questionnaire in MANSOQ is the definition of a structured form. It holds the title of the form, the questions, and the order of those questions. A questionnaire is a template, not a submission. When staff fill in a questionnaire…
Valueset — Definition A valueset in MANSOQ is a named list of allowed codes that you can use again in many places. For example, a valueset holds all the codes for a type of allergy. Other parts of MANSOQ point to a valueset by name instead of listing each…
Report Template — Definition A report template in MANSOQ is a facility-level definition of a reusable, printable document, such as a discharge summary. A facility admin builds the template one time. Care team members then generate reports from the template for a…
Tag — Definition A tag in MANSOQ is a label that you define once and then attach to records such as encounters, service requests, and accounts. You define a tag for one facility, and staff at that facility can then apply it. A superuser can also…
Mark an allergy as entered in error — This flow describes how to retract an allergy that somebody recorded by mistake. Pre-requisites - The patient has a saved allergy. - The patient has an open encounter at the facility, and you retract the allergy from that encounter. - The…
Record an allergy — This flow describes how to record an allergy or intolerance for a patient during an encounter in MANSOQ. Pre-requisites - The patient has an open encounter at the facility, and you record the allergy from that encounter. - The encounter is not…
Update an allergy — This flow describes how to change the values of a saved allergy in MANSOQ. Pre-requisites - The patient has a saved allergy. - The patient has an open encounter at the facility, and you change the allergy from that encounter. - The encounter is…
View allergy history — This flow describes how to view a patient's allergy history across their encounters in MANSOQ. Pre-requisites - The patient is registered in MANSOQ. - You have the permission listed below. Permissions Permission Access --- --- Can view clinical…
Add care team members — This flow describes how to add a person to the care team of an encounter. You give each person a clinical role on the team. Pre-requisites - The patient has an encounter at the facility, and you open that encounter. - The person that you add is…
Modify the care team — This flow describes how to change the primary member of the care team, and how to remove a member from the care team. Pre-requisites - The patient has an encounter at the facility, and you open that encounter. - The care team has at least one…
View the care team — This flow describes how to see the members of the care team for an encounter in MANSOQ. Pre-requisites - The patient has an encounter at the facility, and you open that encounter. - You have the permissions listed below. Permissions Permission…
Add a symptom or diagnosis from past records — This flow describes how to bring the earlier symptoms or diagnoses of a patient into the current encounter. You select the records that you want, instead of searching for each term again. MANSOQ stores each of these records as a condition.…
Mark a symptom or diagnosis as entered in error — This flow describes how to retract a symptom or a diagnosis that you recorded by mistake. MANSOQ stores each of them as a condition. MANSOQ never deletes a saved clinical record. MANSOQ keeps the record and sets its Verification to Entered in…
Record a diagnosis — This flow describes how to record one or more diagnoses for a patient during an encounter. MANSOQ stores each diagnosis as a condition. Pre-requisites - The patient has an open encounter at the facility, and that encounter is the patient's…
Record a symptom — This flow describes how to record a symptom for a patient during an encounter. MANSOQ stores each symptom as a condition. Pre-requisites - The patient has an open encounter at the facility, and that encounter is the patient's active encounter.…
Update a symptom or diagnosis — This flow describes how to change a symptom or a diagnosis that you already recorded. MANSOQ stores each of them as a condition. Use this flow when the patient improves, or when a provisional finding becomes confirmed. Pre-requisites - You or a…
View the clinical history — This flow describes how to review the symptoms and the diagnoses of a patient. MANSOQ stores each of them as a condition. You can review the records of the current encounter, or the records of all past encounters. Pre-requisites - You have the…
Record a consent — This flow describes how to record a consent against an encounter of a patient. You can also attach the signed consent form and other supporting documents. Pre-requisites - The patient is registered in MANSOQ, and you open an encounter of that…
Update a consent — This flow describes how to change the status or the note of an existing consent in MANSOQ. Pre-requisites - A member of staff recorded the consent against an encounter of the patient. - You open the encounter from the facility, and the…
Verify a consent — This flow describes the verification of a consent. A verification is a second confirmation of a consent that a member of staff recorded for a patient. Note: The current version of MANSOQ has no screen for consent verification. You cannot add,…
View consents — This flow describes how to view the consents recorded for an encounter. You can review each consent as a card, or open its full record. Pre-requisites - The patient is registered in MANSOQ, and you open an encounter of that patient. - A member…
Complete an encounter — This flow describes how to mark an encounter as complete in MANSOQ. A completed encounter is closed for all further changes. Pre-requisites - The care team recorded everything for this interaction. - If the facility admits the patient,…
Create an encounter — This flow describes how to create an encounter for a patient at a facility. You can start the encounter from the patient page or from an appointment. Pre-requisites - The patient is registered in MANSOQ, and you have opened the patient at the…
Discharge a patient — This flow describes how to discharge a patient from an encounter in MANSOQ. The discharge records where the patient goes, and when the patient leaves the facility. Note: The discharge does not close the encounter. The encounter stays open until…
Manage the encounter care team — This flow describes how to manage the care team of an encounter in MANSOQ. The care team lists the staff who look after the patient, and the role of each person. Pre-requisites - The patient has an open encounter at your facility, and you…
Manage encounter tags — This flow describes how to apply and remove tags on an encounter in MANSOQ. A tag is a label your facility configures to mark an encounter. Staff use tags to find and filter encounters later. An administrator groups tags into these categories:…
Restart an encounter — This flow describes how to reopen a completed encounter in MANSOQ. MANSOQ sets the status back to In Progress, and the care team can record clinical data again. Pre-requisites - The encounter status is Completed. - You work within the facility…
Update encounter details — This flow describes how to change the details of an open encounter in MANSOQ. You can change the status, the class, the priority and the hospitalization details. Pre-requisites - The patient has an open encounter at your facility, and you…
Archive a file — This flow describes how to archive a file in MANSOQ. MANSOQ has no permanent delete for files. Archiving is the only way to remove a file from the active list. Note: Archiving is irreversible. You cannot restore an archived file. Pre-requisites…
Download a file — This flow describes how to download a file from MANSOQ to your device. Pre-requisites - The file is uploaded to the patient or the encounter that you work with. - You have the permissions listed below. Permissions Permission Access --- --- The…
Rename a file — This flow describes how to change the name of a file in MANSOQ. Pre-requisites - The file is uploaded to the patient or the encounter in MANSOQ. - You can edit files for that patient or that encounter. - You have the permissions listed below.…
Upload a file — This flow describes how to upload a file to a patient or to an encounter in MANSOQ. You can add a file from your device, from your camera, or from an audio recording. Pre-requisites - The patient is registered in MANSOQ, and you attach the file…
View or preview a file — This flow describes how to find a file in the Files tab and open its preview in MANSOQ. Some file types open a preview. Other file types need a download. Pre-requisites - The file is uploaded to the patient or the encounter that you work with.…
Find discussions for a patient or an encounter — This flow describes how to find Clinical Notes discussions in MANSOQ. MANSOQ keeps two separate lists. One list belongs to the encounter. The other list belongs to the patient alone. Watch the demo — the encounter Notes tab's discussion list,…
Post a message to a discussion — This flow describes how you select a discussion in Clinical Notes, read its messages, and post a new message. The screen is the same in the encounter Notes tab and in the patient profile Notes tab. Watch the demo — selecting a discussion and…
Start a discussion — Watch the demo — starting a discussion from the encounter Notes tab. This flow describes how to start a new discussion in Clinical Notes. A discussion groups related messages under one title. You can start a discussion in two contexts. A…
Mark a response as entered in error — This flow describes how to mark a questionnaire response as entered in error. MANSOQ then shows the response as invalid. Pre-requisites - A user filed at least one response for the patient. - You can read the responses of the patient, as…
Print a questionnaire response — This flow describes how to print a questionnaire response. You can print one response, or all the responses to the same form. Pre-requisites - A user filed at least one response for the patient. - You can read the responses of the patient, as…
View questionnaire responses — This flow describes how to read the questionnaire responses that users filed for a patient. MANSOQ shows the responses in three places. Pre-requisites - The patient is registered in MANSOQ. - A user filed at least one response for the patient.…
Create an activity definition — This flow describes how to create an activity definition for your facility in MANSOQ. An activity definition is a template for a service that your facility gives. Pre-requisites - You are a member of the facility. - You have the permission…
Link requirements to an activity definition — This flow describes how to link specimen, observation, and charge item requirements to an activity definition in MANSOQ. Pre-requisites - You create a new activity definition, or you edit an activity definition that exists. See Create an…
Update or retire an activity definition — This flow describes how to change the details of an activity definition in MANSOQ. It also describes how to retire an activity definition that the facility no longer uses. Pre-requisites - The facility has an activity definition that you want…
Use an activity definition to order a service — This flow describes how a clinician uses an activity definition template to order a service for a patient. The other flows in this module cover how an administrator builds the template. Pre-requisites - The patient is registered in MANSOQ and…
Create an observation definition — This flow describes how to create an observation definition for a facility in MANSOQ. An observation definition sets the template for a test or measurement. Pre-requisites - You are a member of the facility. - You have the permission listed…
Set up qualified ranges — This flow describes how to set up qualified ranges on an observation definition in MANSOQ. Qualified ranges are the rules that decide the interpretation that MANSOQ gives to a result. A rule can depend on the patient, such as age, gender, or…
Update or retire an observation definition — This flow describes how to change the details of an observation definition in a facility. It also describes how to retire an observation definition that staff must not use again. Pre-requisites - You are a member of the facility. - The…
Add and edit questions — This flow describes how to add questions to a questionnaire and how to change them. You set the type, the settings, and the answer options of each question. Pre-requisites - You create a questionnaire, or you open a saved questionnaire to…
Clone a questionnaire — This flow describes how to copy a saved questionnaire in MANSOQ. MANSOQ creates a new questionnaire with the same questions and layout. Pre-requisites - The questionnaire is saved in MANSOQ, and you open it to make a copy. - You have the…
Create a questionnaire — This flow describes how to create a new questionnaire in MANSOQ. You give the questionnaire a title, a slug, a subject type, a status, and one or more organizations. Pre-requisites - You are a MANSOQ superuser. MANSOQ shows the Admin Dashboard…
Apply a response template — This flow describes how to fill a questionnaire with a saved response template. A template adds its medications and its service requests to the form. Pre-requisites - You fill a questionnaire for a patient in a facility. - You can see at least…
Create a response template — This flow describes how to create a questionnaire response template. You create the template from the medications or the service requests that you enter on a questionnaire. Pre-requisites - You fill a questionnaire for a patient in a facility.…
Update or delete a response template — This flow describes how to change or remove a questionnaire response template in MANSOQ. Pre-requisites - You fill a questionnaire for a patient in a facility. - You can see the template. You created it, or another user shares it with you or…
Build include and exclude rules — This flow describes how to build the include and exclude rules of a valueset in MANSOQ. The rules decide which codes the valueset contains. Pre-requisites - You create a new valueset, or you change an existing valueset. See Create a valueset. -…
Create a valueset — This flow describes how to create a new valueset in MANSOQ. A valueset gives a named set of codes that MANSOQ shows to users in coded fields. Pre-requisites - You are a MANSOQ superuser. - You have the permissions listed below. Permissions…
Preview a valueset before saving — This flow describes how to test the rules of a new valueset in MANSOQ before you save it. MANSOQ runs your search against the include rules and the exclude rules that you set up. Pre-requisites - You are creating a new valueset. - You added a…
Update or retire a valueset — This flow describes how to change the details of a valueset in MANSOQ. It also describes how to retire a valueset that you no longer use. Pre-requisites - You are a MANSOQ superuser. - The valueset is already in MANSOQ. - You have the…
Create a report template — This flow describes how to create a new report template for a facility in MANSOQ. Pre-requisites - You are a member of the facility that you create the template for. - You know which data the report must show, so that you can pick the correct…
Edit a report template — This flow describes how to change an existing report template in MANSOQ. Use the same flow to retire a template. Pre-requisites - The facility has a report template that you want to change. - You are a member of that facility. - You have the…
Generate and view a report — This flow describes how to generate a report for an encounter from a report template. You can then view the report, download it, print it, or generate it again. Pre-requisites - The patient is registered in MANSOQ, and the patient has an…
Preview a template — This flow describes how to preview a report template in the template builder. MANSOQ renders a sample document, so you can check the layout before you make the template active. Pre-requisites - You create a new report template, or you edit an…
View report templates — This flow describes how to view the report templates of a facility in MANSOQ. You can search and filter the templates. Pre-requisites - You are a member of the facility. - The facility has at least one report template. - You have the…
Archive a child tag — This flow describes how to archive a child tag from the parent tag's detail page. MANSOQ sets the child tag's status to Archived. Pre-requisites - You or another administrator created the child tag under a root tag. - The tag that you archive…
Create a child tag — This flow describes how to add a child tag under a root tag in MANSOQ. A child tag gives users a fixed set of choices under one parent. When a user applies tags to a record, only one child tag from the same parent applies at a time. If the user…
Create a tag — This flow describes how to create a root tag in MANSOQ. A root tag has no parent tag. Pre-requisites - You are a member of the facility where you create the tag. - If you create a tag for the whole instance without a facility, you are a…
Edit a tag — This flow describes how to change the details of an existing tag in MANSOQ. Use this flow also to archive a root tag. Pre-requisites - You or another administrator created the tag at your facility. - You have the permissions listed below.…
View tags — This flow describes how to view the tags of a facility in MANSOQ. You can filter the list and open a tag to see its details. Pre-requisites - You are a member of the facility. - The facility has at least one tag. - You have the permissions…
Allergy Intolerance — AllergyIntolerance records a patient's allergy or intolerance to a substance, scoped to the encounter where it was captured. MANSOQ aligns it to FHIR AllergyIntolerance. You touch this resource when recording a known allergy during an encounter…
Care team — Technical reference for the encounter care team in MANSOQ EMR. See the care team concept for the plain-language view. Source: - Model: care/emr/models/encounter.py - Specs: care/emr/resources/encounter/spec.py · valueset.py - Viewset:…
Condition — A Condition records a clinical problem, diagnosis, or symptom against a patient. It maps to the FHIR Condition resource and shows up in the MANSOQ product UI as Symptoms. Source: - Model: care/emr/models/condition.py - Resource spec:…
Consent — A Consent records a patient's permit-or-deny decision for a category of activity, scoped to an encounter. You write one when capturing a patient's agreement to treatment, research, privacy disclosure, or an advance directive. The Django model…
Encounter — An Encounter records a single interaction between a patient and a facility — a visit, admission, or consultation — and maps to the FHIR Encounter resource. You create one when a patient presents, drive it through its status lifecycle, and read…
Notes — Notes are threaded discussions attached to a patient. A NoteThread groups messages; a NoteMessage is one message in that thread, carrying a server-maintained edit history. The Django models store the data: NoteThread holds the patient and…
Observation — An Observation is one named, coded data point about a subject — almost always a patient: a blood pressure reading, a temperature, a coded answer captured through a questionnaire. main_code records what was observed and value holds the result.…
Questionnaire Response — A QuestionnaireResponse is the set of answers a patient gives to a questionnaire; a FormSubmission is the envelope that carries that payload through a draft-to-finalised lifecycle. You touch these when reading back what was answered or when…
Activity Definition — An ActivityDefinition is a FHIR-aligned, facility-scoped template for a clinical activity. It stores the defaults needed to spin up a downstream resource — currently a Service Request — and you "apply" it against an encounter, which merges…
Observation Definition — An ObservationDefinition is master data describing how a particular observation is captured — its code, permitted data type, unit, method, body site, and reference ranges. You create one when you need a measurement collected consistently across…
Questionnaire Response Template — A QuestionnaireResponseTemplate is a clinician's saved "favourite" or order set: a reusable, shareable bundle that pre-fills a questionnaire response along with its medication requests and activity definitions. Reach for it when building…
Questionnaire — A Questionnaire is a versioned, FHIR-inspired form: a tree of questions answered about a patient or an encounter. You touch it whenever you define a data-collection form, render one for filling, or submit answers — which can flow back out as…
Value Set — A ValueSet is a FHIR-aligned composition of coded concepts drawn from one or more code systems. Reach for one when a questionnaire needs to constrain a coded answer to a fixed set of options. The Django model is only storage — compose is an…
Base models & conventions — Every MANSOQ EMR resource inherits a shared base that supplies opaque IDs, audit fields, soft-delete, history, slugs, and feature flags. A resource author writes domain fields and validation; the base handles the rest. It spans two layers: -…
Favorites — UserResourceFavorites lets a user pin resource IDs into named lists so the owning resource's list endpoint can surface them first. It's a MANSOQ-internal personalization feature, not a FHIR resource — you touch it when you add favoriting to a…
File Upload — A FileUpload is the metadata record for a file living in S3-compatible object storage. You touch it whenever a MANSOQ resource needs an attachment — a patient document, an X-ray on an encounter, a signed consent form. Two layers split the work.…
Meta Artifact — A MetaArtifact attaches a freeform metadata payload to any MANSOQ object without a dedicated foreign key. You reach for it when a feature needs to hang structured data — a drawing on a patient, say — off an existing record without adding a…
Report & Templates — A Template defines reusable report markup and render options; a ReportUpload is one generated file produced from that template and linked to a subject resource. You author templates through the API; report uploads are created for you by the…
Resource Category — ResourceCategory is a facility-scoped, self-nesting category tree that classifies resources — product_knowledge, activity_definition, and charge_item_definition — and carries charge-item monetary components that inherit down the tree. The…
Resource Request — ResourceRequest represents an inter-facility request for a resource and tracks it from the originating facility through approval and assignment. You touch it whenever a facility needs something another facility can provide. The Django model is…
Tagging — A TagConfig defines one tag: its label, category, scope, and place in a tag tree. Tags are hierarchical labels you attach to resources — patients, encounters, charge items — to classify and filter them. You manage the definitions through…

Executive analytics

Read the Revenue Cycle dashboard without confusing revenue and cash — Use financial totals, readiness and the episode worklist to direct operational attention.
Interpret receivable aging, denials and operational risk — Read payer cohorts and evidence states before making collection or provisioning decisions.
Read bed availability and understand its current calculation limits — Interpret an actual synthetic Hospital bed dashboard, filter ward cards and avoid treating unqualified counters as reservation or clinical readiness evidence.
Read the revenue command dashboard without mistaking empty data for readiness — Locate financial summaries, stage counters and the episode worklist in a verified empty synthetic Hospital; distinguish data health from zero values.

Facility administration

Choose the correct facility setup classification — Use the five canonical version-2 facility types and distinguish them from historical codes and advertised service features.
Apply shared workflows in a hospital — Use the canonical Hospital classification with the verified shared configuration and care workflows; identify specialist requirements that still need validation.
Apply shared workflows in a clinic — Use the canonical Clinic classification with the verified shared configuration and care workflows; identify specialist requirements that still need validation.
Apply shared workflows in a polyclinic — Use the canonical Polyclinic classification with the verified shared configuration and care workflows; identify specialist requirements that still need validation.
Apply shared workflows in a laboratory — Use the canonical Laboratory classification with the verified shared configuration and care workflows; identify specialist requirements that still need validation.
Use Other without assuming a specialist package — Use the canonical Other classification with the verified shared configuration and care workflows; identify specialist requirements that still need validation.
Set the facility business timezone — Configure a valid IANA timezone for financial service dates and distinguish it from the viewing device’s local clinical display.
Create a facility — Create a facility within an organization and complete its identity, contact details, features and directory visibility.
Create a department — Create the facility department hierarchy and respect naming, nesting and total-department limits.
Create a location — Create the location hierarchy or multiple beds using the correct permanent location form.
Manage a location's organizations — Link the responsible departments to locations with the required location and department permissions.
Configure and verify a Hospital facility — Follow a real synthetic Hospital setup edit with visible controls, validation and independent saved-record readback; configure clinical services separately.
Configure and verify a Clinic facility — Follow a real synthetic Clinic setup edit with visible controls, validation and independent saved-record readback; configure clinical services separately.
Configure and verify a Polyclinic facility — Follow a real synthetic Polyclinic setup edit with visible controls, validation and independent saved-record readback; configure clinical services separately.
Configure and verify a Laboratory facility — Follow a real synthetic Laboratory setup edit with visible controls, validation and independent saved-record readback; configure clinical services separately.
Configure and verify a Other facility — Follow a real synthetic Other setup edit with visible controls, validation and independent saved-record readback; configure clinical services separately.
Find Update Facility and review directory visibility — Locate the shared facility form’s save control and distinguish facility-directory visibility from knowledge-site access.
Maintain department metadata and distinguish browsing from administration — Compare actual Doctor browsing with authorized department editing, recognize disabled name/unchanged states, save notes and verify existing Staff/Doctor memberships separately.
View a facility — Find a facility through permitted directory, organization or administration views and inspect its available details.
Create a facility through its governance organization — Use the actual governance and Add Facility screens, review defaults, resolve required fields and verify a new synthetic Clinic.
Create an operational department in a new facility — Create and verify an actual synthetic Department through facility settings while preserving the reserved Administration root.
Understand user identity, invitation and responsibility fields — Read the actual blank identity form and distinguish credential setup, global responsibility assignments and facility membership.
Link an existing user to a department with an approved role — Select a real synthetic account, observe the required role guard, save a Staff membership and independently verify it.
Edit a healthcare service, recover validation and recognize denied facility access — Use the actual disabled/dirty form state, required-name rejection, notes-only update and saved detail, then distinguish an access denial from an empty service catalogue.
Create a healthcare service with the correct location and managing department — Follow the actual creation form, required-location validation, internal service type, hierarchical location selection, optional department and saved record verification.
Configure and verify facility print layouts, logo and watermark — Save an actual synthetic Default configuration with explicit paper, millimetre margins, local logo and training watermark, then reopen and independently verify its values.
Register a generic device and record its service and location history — Create an actual synthetic device inventory record, add a maintenance note and associate its storage Room with independent saved-record checks.
Create a Building and its child Room through location settings — Build and independently verify a real synthetic parent-child location hierarchy before using it for device storage.
Import a location hierarchy from CSV and verify every saved parent and child — Recover malformed CSV columns, inspect the full parsed hierarchy, save once and independently verify a new Wing with two Rooms.
Create an activity catalogue category as Laboratory Admin — Open the intended activity catalogue, correct required name and slug fields, and verify the saved category before adding definitions.
Create and verify a base laboratory activity definition — Complete the required catalogue information, select an actual installed code, save the base definition, and find it through search and its detail page.
Maintain device dates and contact points, recover validation and verify removal — Use valid date ordering and a unique contact, recover actual date/email/duplicate errors, then recognize the pinned product’s optional-field clearing limitation.
Maintain device lifecycle separately from availability and recover required-name errors — Read the two independent status fields, recover a required-name validation, save a synthetic Inactive lifecycle and restore Active with independent record verification.
Define an administrative location tag and apply it to a Room — Create a facility-scoped Admin/Location definition, apply it to the correct child Room and verify the saved tag separately from its definition.
Prepare, preview and save a Draft HTML report template — Create a static synthetic Account Report layout while keeping report type, data context, output format, preview and saved Draft status distinct.
Department — Definition A department in MANSOQ is a group inside a facility, such as a ward, a clinical team, or an administrative unit. A department can hold sub-departments, so the departments of a facility form a hierarchy. MANSOQ models a department on…
Device — A device in MANSOQ is a piece of equipment a facility owns and tracks — a ventilator, an infusion pump, a monitor, a camera. The record is the platform's durable answer to three questions: what equipment exists, where it sits right now, and…
Facility — Definition A facility in MANSOQ is a hospital, clinic, health center, or other place that provides care to patients. . The facility is the top-level unit that holds departments, users, patients, and encounters. Key Attributes Components What it…
Healthcare Service — A healthcare service is a named offering that a facility provides — cardiology, a laboratory, radiology, a pharmacy, an outpatient clinic. It is the "what we offer" catalog entry: the thing patients book into, the thing schedules attach to, and…
Locations — Definition A location in MANSOQ is a physical place inside a facility. A location can be a building, a ward, a room, or a bed. Locations sit inside one another and form a hierarchy. For example, a building contains wards, a ward contains rooms,…
Assign an encounter location — This flow describes how to record the bed or room that a patient occupies during an encounter. It also describes how to move the patient to another location and how to correct earlier stays. Pre-requisites - The patient has an open encounter at…
Manage encounter departments — This flow describes how to link departments to an encounter, and how to remove them. Departments decide who can see the encounter. Staff of a linked department can open the encounter. Every encounter has at least one department. You choose the…
Create a department — This flow describes how to create a new department in a facility in MANSOQ. Pre-requisites - You are a member of the facility. - If you create the department under an existing department , open that parent department first. - You have the…
Delete a department — This flow describes how to delete a department from a facility in MANSOQ. Pre-requisites - The department is set up in the facility. - The department has no sub-departments. If the department has sub-departments, delete them first. - The…
Update a department — This flow describes how to change the name, description, or type of an existing department in MANSOQ. Pre-requisites - The department is set up in the facility. - The department is not the facility's root department . MANSOQ does not let you…
Create a facility — This flow describes how to create a new facility in MANSOQ. Pre-requisites - You are signed in to MANSOQ. - You can access the organization that the facility belongs to. - You have the permission listed below. Permissions Permission Access ---…
Delete a facility — This flow describes how a system administrator deletes a facility in MANSOQ. Pre-requisites - The facility is registered in MANSOQ. - You are a system administrator in MANSOQ. Permissions Permission Access --- --- Super Admin Super admin access…
Update facility details — This flow describes how to change the details and the cover photo of a facility in MANSOQ. Pre-requisites - The facility is registered in MANSOQ, and you have access to it. - You have the permissions listed below. Permissions Permission Access…
View a facility — This flow describes how to browse facilities in MANSOQ and open one to see its details. MANSOQ gives you two ways to do this. You can browse the public directory without a sign-in. You can also open a facility from within an organization after…
Create a location — This flow describes how to add a new location to a facility in MANSOQ. Pre-requisites - You are a member of the facility. - If you create a Bed, select a parent location first. MANSOQ does not create a Bed without a parent location. - You have…
Delete a location — This flow describes how to delete a location from a facility in MANSOQ. Pre-requisites - The location is set up in the facility. - The location has no child locations. - No patient is assigned to the location. - You have the permissions listed…
Edit a location — This flow describes how to change the details of a location in a facility. Pre-requisites - The location is set up in the facility. - You have the permissions listed below. Permissions Permission Access --- --- Can Create/Update Facility…
Reorder locations — This flow describes how to change the order of a location among its sibling locations in MANSOQ. Pre-requisites - The location and its sibling locations are set up under the same parent location. - You have the permissions listed below.…
View locations — This flow describes how to browse the locations of a facility in MANSOQ. It also describes how to open one location and see its details. Pre-requisites - You are a member of the facility. - The facility has at least one location. - You have the…
Device — A Device tracks a physical or logical piece of equipment within a facility — from its lifecycle status to where it's placed and which encounter it's attached to. The Django model is only the storage layer; it types fields loosely — CharField…
Facility Config — Holds one facility's billing configuration: a discount-code catalog, discount component definitions, a discount-stacking rule, and the invoice-number template. The Django model FacilityMonetoryConfig stores all of it, but three fields are plain…
Facility Flag — FacilityFlag binds a registered flag name to a single Facility to gate server-side behaviour. It is not a FHIR resource and has no Pydantic spec — no endpoint, serializer, or ...CreateSpec/...ReadSpec — so everything below comes from the Django…
Facility — A Facility is a physical or virtual care site — hospital, clinic, lab, telemedicine endpoint — and the root of a deployment's administrative hierarchy. You create one before any patient, organization, or device can attach to it. A Facility…
Healthcare Service — A HealthcareService is a service a facility offers — cardiology, lab, radiology, pharmacy — scoped to one or more locations and to the facility organization that manages it. You touch it when modeling what a facility provides and where. The…
Location — FacilityLocation is a node in a facility's building/ward/room/bed tree — where resources sit and where care happens. You work with it when you place an encounter somewhere, scope organization access to part of a facility, or model a site's…

Finance & ZATCA

Review patient responsibility before billing — Establish a documented basis, responsibility and authorized disposition for each amount.
Reconcile payer remittance advice without inventing cash — Match payment-reconciliation lines to claims while keeping unmatched amounts in advice suspense.
Import, confirm and allocate a bank receipt — Establish actual bank cash before settlement changes claim paid balances.
Send a payment notice from evidenced cash — Notify the payer only after an actual provider bank receipt is confirmed.
Explain remittance variance, reversals and returned payments — Keep fees, deductions and compensating entries visible instead of disguising them as denials.
Review refunds, credits and bank-detail changes — Apply separate evidence and maker-checker controls to sensitive financial changes.
Export accounting evidence and assess period close — Freeze settlement inputs, acknowledge external posting and read close blockers.
Follow the ZATCA fiscal-document lifecycle — Distinguish tax determination, local fiscal preparation and actual regulator evidence.
Confirm a statement line and distinguish advice, cash and local notices — Follow actual wide treasury controls, reference refusal, saved audit evidence and separate financial identities using an expressly fictional local example.

Getting started

Sign out and sign in with an existing Staff account — Recognize the Staff login form, correct required fields, keep the password masked and confirm the signed-in identity and facility.
Use context-aware keyboard shortcuts — Find available actions and use verified shortcuts while respecting the active page, input focus and dialog state.
Use language, direction and accessible form feedback — Choose an enabled interface language and understand the supported form and dialog affordances without assuming a full accessibility certification.
Sign in to patient appointment self-service — Choose patient login, verify the correct phone and end the session safely.
Sign in to the staff workspace — Choose the staff login method, sign in with your assigned credentials and complete the authentication challenge shown by your deployment.
Navigate facilities, patients and services — Understand the changing sidebar and select the correct facility, patient and service context before acting.
Understand dates, times and workflow status — Check when an event happened, recognize local display behavior, and handle date restrictions in encounters, observations, medication and payments.
MANSOQ documentation — MANSOQ documentation is organized in four layers. Start with concepts to build mental models, follow flows when you need to do something in the product, use references for technical module detail, and use playbooks when a deployment combines…

IT & integrations

Inspect integration metadata, rotate a draft and investigate refused tests — Follow observed wide Clinic administrator controls, actual metadata persistence, structural-test failure and guarded replay without claiming a live connection.
Validate NPHIES FHIR messages and terminology — Understand structural validation, business checks and code-version checks before delivery.
Start an integration from the deployed API contract — Use the current schema, facility scope and documented pagination instead of guessing endpoints.
Authenticate API clients and recover from expiry — Use the documented bearer scheme and supported refresh/logout flow.
Understand backend plugins and frontend apps — Extend MANSOQ through the correct server or user-interface extension contract.
Operate a versioned deployment and verify recovery — Treat plugins, workers, database backups and readiness as part of the supported installation.
Integrate cash import, settlement and local notice records with exact guards — Use the source-defined finance operations, stable identities and independent readbacks without confusing a local notice record with external delivery.
Integrate eligibility interpretation, provenance and freshness without purpose promotion — Use exact request identity, typed scope, offline ownership and operation-specific readbacks; distinguish local interpreter results from real payer qualification.
Integrate preparation and exactly-once commitment before canonical claim construction — Use the scoped supported API handoff, stable keys, timezone-aware expiry and independent readback without inventing a missing UI control.
HMIS playbooks — Hospital management playbooks wire flows into real front-desk and ward scenarios. Each playbook lists the flows involved, the expected operator path, and edge cases specific to HMIS deployments. How playbooks relate to core docs Layer Location…
Outpatient registration — Register a walk-in or scheduled outpatient at the hospital front desk. This playbook combines the register patient flow with HMIS-specific edge cases your registration team will hit in production. Flows involved Order Flow Purpose --- --- --- 1…
Palliative playbooks — Palliative care playbooks wire flows into home-based and facility palliative programs. Each playbook lists the flows involved, the care team path, and edge cases specific to palliative deployments. How playbooks relate to core docs Layer…
Palliative patient enrollment — Enroll a patient into a community or facility-based palliative program. This playbook combines the register patient flow with palliative-specific intake, caregiver capture, and program assignment. Flows involved Order Flow Purpose --- --- --- 1…
Deploying MANSOQ — MANSOQ is self-hostable. You can run your own instance end to end, from the database and object store to the backend workers and the web frontend. This section is written for operators and SREs standing up and running their own MANSOQ instance…
Reference architecture — This page describes the reference deployment topology for MANSOQ: a self-contained, two-node Kubernetes cluster that runs the MANSOQ backend and frontend alongside every supporting datastore and platform service. It is the architecture…
Provisioning the cluster — This page describes how the Kubernetes cluster that hosts MANSOQ is brought up: installing the container runtime and Kubernetes packages on each node, initializing the control plane with kubeadm, labelling nodes, creating the application…
Deploying MANSOQ onto the cluster — With a Kubernetes cluster provisioned ), MANSOQ and its supporting services are rolled out module by module from the deployment-k8 repository. This page describes the deployer workflow and the order in which modules are applied. The exact…
Day-2 operations — Once MANSOQ is running on the cluster ), day-2 operations cover keeping it observable and recoverable: monitoring, log aggregation, and backups for every stateful component. This deployment is a work in progress. Some capabilities are running…
Requirements — This page lists what an operator needs in place before deploying MANSOQ. The reference deployment is a small, self-hosted Kubernetes cluster provisioned with kubeadm and managed as infrastructure-as-code with OpenTofu. Everything below is…
Deploying MANSOQ on AWS ECS — This guide walks through deploying MANSOQ on AWS using Elastic Container Service with the Fargate serverless launch type. ECS runs the backend, Celery, and Redis containers as serverless tasks, so there are no EC2 instances to provision or…
Deploying MANSOQ on AWS — MANSOQ runs on AWS as containers on ECS Fargate, backed by Amazon RDS for the PostgreSQL database, Amazon S3 for object storage, and an Application Load Balancer in front. Images are built and the service is deployed through GitHub Actions,…
Deploying MANSOQ on DigitalOcean — In this guide, we'll walk you through deploying MANSOQ on DigitalOcean. We'll keep things simple so you can follow along to get your instance up and running. Expect the process to take about an hour, depending on your familiarity with the…
Hosting the MANSOQ frontend on GCS — This guide covers hosting the MANSOQ static frontend on Google Cloud Storage , fronted by Cloud CDN and a global external load balancer with managed SSL/TLS, Cloud DNS, and Cloud Monitoring. GCS hosts only the static frontend — the compiled…
Deploying MANSOQ on GKE — This guide provides a step-by-step process for deploying the MANSOQ application on Google Cloud Platform using Google Kubernetes Engine . It combines the full infrastructure setup, the Cloud Build pipeline, and the deployment workflow into a…
Deploying MANSOQ on Google Cloud — Google Cloud Platform offers two distinct paths for deploying MANSOQ, depending on what you need to run. You can deploy the full MANSOQ application on a managed Kubernetes cluster, or host just the MANSOQ frontend as a globally distributed…
Cloud provider guides — MANSOQ can be deployed on a range of cloud providers, with different deployment options depending on your scale, budget, and operational preferences. This section collects provider-specific recipes that walk you through standing up a…
Data security — MANSOQ holds sensitive patient health data, so a production deployment should be hardened at every layer — the edge, the network, transport, data at rest, and the operational paths your team uses to manage it. This page lists the standard…
Privacy and data protection — The records MANSOQ holds — identities, diagnoses, medications, encounters — are among the most sensitive personal data there is. Data security keeps that data safe from attackers; privacy and data protection govern how you collect, use, share,…
Contributing to MANSOQ — MANSOQ is an open-source Electronic Medical Record platform for managing patients, health workers, and hospitals. It is built and maintained in the open, and contributions of every kind are welcome — code, documentation, bug reports, and…
Backend setup — This page walks you through running the MANSOQ backend ) on your machine. It is a Django application that exposes the MANSOQ REST API and depends on PostgreSQL, Redis, a Celery worker, and an S3-compatible object store . There are two supported…
Frontend setup — This guide walks you through running the MANSOQ frontend ) on your machine. The frontend is a React + TypeScript single-page app built with Vite. Prerequisites - Node.js — the repository pins the runtime to Node 22 via its .node-version file.…
Nix development environment — Nix is an alternative to Docker Compose for backend development. Instead of running PostgreSQL, Redis, and MinIO inside containers, the Nix dev shell installs pinned versions of those services from the Nix store and runs them directly on your…
Plugin system — MANSOQ is designed to be extended without forking the core. Functionality you do not want to maintain in the main codebase — a transcription service, a custom integration, a bespoke UI — ships as a plugin. There are two halves to the system: -…
Contribution workflow — This page walks through the end-to-end path a change takes — from finding an issue to getting your pull request merged. It applies to both the backend ) and the frontend ). If you haven't set up your environment yet, start with the…

Inventory

Create a consumable product definition — Configure a consumable identity, valid slug and base unit, then verify the saved definition before creating physical stock.
Receive the first batch of a configured product — Create a delivery draft, add a priced batch, receive its items, complete the delivery and independently verify the resulting location stock.
Request stock from another internal location — Choose the receiving location, create and approve a product request, and distinguish requested quantities from actual dispatched stock.
Dispatch an internal stock request from the source store — Create the separate delivery, load the intended request lines, select actual stock and handle an insufficient-stock refusal before approval.
Receive internal stock, complete the records and verify both stores — Receive the exact physical batch, complete the separate delivery and request, and verify that source plus destination stock balances.
Abandon an unfulfilled internal stock request — Close an intentionally unfulfilled request using its lifecycle action and verify that this did not create a delivery or change stock.
Receive and complete a purchase delivery — Approve a purchase delivery, receive goods and complete the delivery to update stock.
View stock levels at a location — Review stock by storage location and product and distinguish stock viewing from stock-changing transactions.
Product Knowledge — Product Knowledge is the master definition of a thing your facility stocks — a medication, a nutritional product, or a consumable — described once so every batch, shelf, and order can point back to it. It is the catalogue's source of truth for…
Inventory Item — Definition An inventory item in MANSOQ shows how much of one stocked batch is in stock at one location. MANSOQ calculates this count for you. You cannot create or edit an inventory item, and there is no manual stock adjustment. Key Attributes…
Product — Definition MANSOQ keeps two kinds of records for every item that a facility stocks or dispenses. A Product Knowledge entry is the catalog definition of a type of product, for example "Paracetamol 500mg tablet". A Product is one facility's…
Purchase Delivery — Definition A purchase delivery in MANSOQ records stock that arrives at your facility from an outside vendor. It bundles one or more delivered items under a single delivery. When you complete the delivery, MANSOQ updates the stock levels at the…
Purchase Order — Definition A purchase order in MANSOQ records a request to buy stock from an outside vendor for your facility. It bundles one or more requested items under a single order. Each requested item names a product and a quantity. MANSOQ uses one…
Supply Delivery — Definition A supply delivery in MANSOQ records stock that moves from one location to another location in the same facility. For example, the central store dispatches supplies to a ward. One supply delivery groups one or more delivered items…
Supply Order — Definition A supply order in MANSOQ records a request to move stock from one location to another location in the same facility. For example, a ward asks the central store to send more supplies. One supply order bundles one or more requested…
View stock levels at a location — This flow describes how to view the current stock levels of every inventory item at a storage location in a facility. Pre-requisites - You are a member of the facility. - The facility has a storage location that holds stock. - You have the…
Add a product instance — This flow describes how to add a product instance in MANSOQ. A product instance is one facility's stocked batch of a catalog entry, with its own lot number, expiration date, and purchase price. Pre-requisites - You are a member of the facility…
Add a product to the catalog — This flow describes how to add a product to the catalog of a facility in MANSOQ. A catalog entry defines a product that the facility can stock and use. Pre-requisites - You are a member of the facility. - You know the category that the product…
Edit a product instance — This flow describes how to change the details of a product instance at a facility. Pre-requisites - Someone added the product instance at the facility. - You are a member of the facility. - You have the permissions listed below. Permissions…
Edit or retire a catalog entry — This flow describes how to change the details of a product catalog entry, and how to retire an entry that your facility no longer uses. Pre-requisites - Someone added the catalog entry to the product catalog of your facility. - You have the…
Add delivered items to a purchase delivery — This flow describes how to add the delivered items to a purchase delivery in MANSOQ. Each item records the product, the quantity, and the condition of the goods. Pre-requisites - You created the purchase delivery at your facility. See Create a…
Create a purchase delivery — This flow describes how to create a purchase delivery for a location in a facility. The delivery starts as a Draft. Pre-requisites - You are a member of the facility that receives the delivery. - Your facility has the location that receives the…
Receive and complete a purchase delivery — This flow describes how to approve a purchase delivery, record the goods you receive, and complete the delivery in MANSOQ. When you complete the delivery, MANSOQ updates the stock counts of the inventory items at the destination location.…
View a purchase delivery — This flow describes how to open a purchase delivery in MANSOQ and read its details. You can also print a copy of the delivery. Pre-requisites - You are a member of the facility that receives the delivery. - Someone created the purchase delivery…
Add items to a purchase order — This flow describes how to add the products you request to a purchase order in MANSOQ. Each item records one product and the quantity you request. Pre-requisites - You created a purchase order at the facility. See Create a purchase order. - The…
Create a purchase order — This flow describes how to create a purchase order for a location in a facility. The new order starts as a Draft. Pre-requisites - You are a member of the facility that requests the supplies. - Your facility has the location that receives the…
Update the status of a purchase order — This flow describes how to move a purchase order forward in MANSOQ. You change the status of the order when the order progresses, or when you stop it. Pre-requisites - Someone created the purchase order at your facility, and you open that…
View a purchase order — This flow describes how to open a purchase order in MANSOQ and read its details. You can also print a copy of the order. Pre-requisites - You are a member of the facility that places the order. - Someone created a purchase order for a location…
Add delivered items to a supply delivery — This flow describes how to add the items that you move in a supply delivery. Each item names a batch in stock and the quantity to move. Pre-requisites - You created the supply delivery at your facility. See Create a supply delivery. - The…
Create a supply delivery — This flow describes how to create a supply delivery in MANSOQ. The delivery starts as a Draft, and you add the delivered items in a separate step. Pre-requisites - You are a member of the facility that sends the stock. - Your facility has the…
Receive and complete a supply delivery — This flow describes how to approve a supply delivery, confirm the delivered items at the receiving location, and complete the delivery in MANSOQ. Pre-requisites - You created the supply delivery, and it lists the items that you send. See Add…
View a supply delivery — This flow describes how to open a supply delivery in MANSOQ and read its details. You can also print a copy of the delivery. Pre-requisites - Someone created the supply delivery at your facility. - You are a member of the facility that…
Add items to a supply request — This flow describes how to add the products that you need to a supply request in MANSOQ. Pre-requisites - You raised the supply request at your facility. See Raise a supply request. - The supply request is not Completed, Abandoned, or Entered…
Raise a supply request — This flow describes how to raise a supply request from one location to another location in the same facility. MANSOQ creates the request as a draft order. Pre-requisites - You are a member of the facility. - The facility has more than one…
Update the status of a supply request — This flow describes how to move a supply request forward in MANSOQ. You change the status of the request when you edit it. Note: MANSOQ has no separate approve button or complete button. You change the Status field to move the request forward.…
View a supply request — This flow describes how to open a supply request in MANSOQ and read its details. You can also print a copy of the request. Pre-requisites - You are a member of the facility that raises or fulfills the supply request. - Someone raised the supply…
Product Knowledge — ProductKnowledge is the reusable definition of a product — its coding, base presentation unit, ingredients and nutrients, drug characteristics, and storage rules. Define it once and every concrete Product points back to it instead of carrying…
Inventory Item — InventoryItem records how much of one Product is on hand at one facility location. Deliveries move product in, dispenses move it out, and the server recomputes the balance into net_content. You never create these rows — the server does, and the…
Product — A Product is a concrete batch of stock at a facility — a single lot of a medication, nutritional product, or consumable, with its own expiry, lot number, and purchase price. It instantiates a catalogue entry: everything generic about the item…
Supply Delivery — A supply delivery records product moving into a destination location — either from another location or from an external supplier. Deliveries and dispensing together drive facility stock: supply delivered − supply dispensed = current stock. Each…
Supply Request — A SupplyRequest is a single line item: a quantity of one catalogue item that someone wants moved. Requests never stand alone — each belongs to a RequestOrder that groups them and describes the movement into a destination facility location,…

Laboratory & radiology

Collect a specimen — Create an order-linked draft specimen, identify it, validate quantity and unit, save collection, and select QR labels.
Create a service request — Order configured tests, procedures or services, set priority, and pass preparation instructions to the performing team.
Enter diagnostic report results — Create the configured preliminary report, enter observations with the correct units, handle validation and save results for review.
Process a specimen — Record the methods and descriptions of processing steps after a specimen has been collected.
Review, finalize and complete a laboratory request — Approve a saved preliminary result, verify finalization, complete the request with a note, and open its generated report.
Clinical - Diagnostic Report — Definition A diagnostic report in MANSOQ holds the result of a laboratory, imaging, or other diagnostic service request. Each diagnostic report answers one service request. MANSOQ takes the patient, the encounter, and the facility from that…
Clinical - Service Request — Definition A service request in MANSOQ is a request for a service for a patient. The service is a diagnostic test, a procedure, or a referral. You create a service request inside an encounter. MANSOQ takes the patient from that encounter.…
Clinical - Specimen — Definition A specimen in MANSOQ is a biological sample that a user collects from a patient for testing. MANSOQ always creates a specimen as part of a service request. You cannot create a specimen on its own. The specimen answers a specimen…
Specimen Definition — Definition A specimen definition in MANSOQ is a reusable template for one type of specimen, for example a blood draw. It describes how staff collect the specimen and how they handle it after collection. Each specimen definition belongs to one…
Enter diagnostic report results — This flow describes how to create a diagnostic report for a service request. You record the result of each observation, and you set the report status. Pre-requisites - The patient has a service request at the facility, and you record the…
Print a diagnostic report — This flow describes how to open the print-formatted version of a diagnostic report in MANSOQ and print it. Pre-requisites - A user entered the diagnostic report in MANSOQ, and you print that report. - You are a member of the facility that holds…
Update a diagnostic report — This flow describes how to change the details of a diagnostic report in MANSOQ. You update the report from its detail view. Pre-requisites - A user entered the diagnostic report in MANSOQ, and you update that report. - You have the permissions…
View a diagnostic report — This flow describes how to open and read a diagnostic report for an encounter in MANSOQ. Pre-requisites - The patient has an encounter at the facility, and you view the reports for that encounter. - A user entered a diagnostic report for the…
Cancel a service request — This flow describes how to cancel a service request that the care team no longer needs. Pre-requisites - You raised a service request for the patient, or another user raised it, and you can open its detail page. - The service request is not…
Complete a service request — This flow describes how to mark a service request as complete in MANSOQ. You complete the service request after the requested work is finished. Pre-requisites - You raised a service request for the patient, or another user raised it, and you…
Create a service request — This flow describes how to raise a new service request for a patient from an encounter in MANSOQ. A service request asks another team to do a test, a procedure, or another service for the patient. Pre-requisites - The patient is registered in…
View service requests — This flow describes how to find and open a service request in MANSOQ. You can view the requests for one encounter, or the requests for a facility location. Pre-requisites - The patient is registered in MANSOQ, and the patient has an encounter…
Collect a specimen — This flow describes how to collect a specimen for a service request in MANSOQ. You record the collection details and identify the specimen with a QR code or an accession identifier. Pre-requisites - A user created a service request for the…
Discard a specimen — This flow describes how to discard a specimen in MANSOQ and record the reason for the discard. Pre-requisites - You collected the specimen, and the specimen card shows on the service request page. - You have the permissions listed below.…
Process a specimen — This flow describes how to record a processing step for a collected specimen in MANSOQ. A processing step is work done on the specimen before testing, such as centrifuging or staining. Pre-requisites - You collected the specimen, and the…
View specimen history — This flow describes how to review earlier specimens for a service request in MANSOQ. The history shows specimens marked as Entered in Error or Unsatisfactory. Pre-requisites - You are a member of the facility that holds the service request. - A…
Create a specimen definition — This flow describes how to create a new specimen definition for your facility in MANSOQ. Pre-requisites - You are a member of the facility. - You have the permissions listed below. Permissions Permission Access --- --- Can Read Specimen…
Update or retire a specimen definition — This flow describes how to change the details of a specimen definition in a facility. It also describes how to retire a specimen definition that the facility no longer uses. Pre-requisites - The facility has a specimen definition that you want…
Diagnostic Report — A DiagnosticReport records the results and interpretation of a diagnostic test, tied to the ServiceRequest that ordered it. You create one to report on an investigation, then read it back with its observations, encounter, and requester…
Service Request — A ServiceRequest is an order or proposal to perform an action — clinical or otherwise — for a patient . It drives the creation of specimens, diagnostic reports, observations, and procedures, each of which links back to the originating request.…
Specimen — A Specimen is a physical sample — blood, tissue, swab — collected from a patient for laboratory analysis. You create one to fulfill a lab order, then update it as the specimen moves through collection, receipt, and processing. Several of the…
Specimen Definition — A SpecimenDefinition is a reusable, facility-scoped template for a kind of specimen: what material to collect, how to prepare the patient, how to collect it, and how it's held in a container for testing. A lab maintains a repository of these,…

NPHIES

Queue an NPHIES claim and confirm its eventual outcome — Distinguish a queued exchange from transport delivery, payer acceptance and adjudication.
Classify platform errors, payer errors and denials — Choose the correct recovery path before correcting or appealing a payer transaction.
Separate sandbox testing from production authorization — Check package, certification, certificate and routing evidence before live exchange.
Handle patient, episode and message identity correctly — Keep clinical identities and transport identities stable for the operation they represent.
Retry a transport failure without creating a duplicate — Replay the persisted NPHIES transaction only under the correct response and channel policy.
Poll safely and recover a partially processed response bundle — Persist retrieved messages before parsing and resume from durable state.

Nursing

Record a coded observation and verify repeated readings — Enter a configured coded measurement, inspect its saved time and author, review the vital summary and retain separate repeat readings.
Review observation graphs, recent values and encounter history — Navigate configured plot groups and verify the different scope of Graph, Recent Data and Full History in the audited release.
Complete bedside questionnaire fields and verify the saved response — Use configured form groups, text, templates, Boolean conditions, numbers, choices, repeated answers, units, dates and notes in an active encounter.
Administer a dose — Record an administered dose, verify prescription instructions, and document actual administration time and status.
Coordinate handover with encounter notes and care teams — Use the verified Clinical Notes and care-team features for a documented handover while following your facility’s approved nursing process.
Review vital signs, observations and clinical forms — Find the encounter’s configured vital-sign summary and review individual observation values, times and recorded-by details.
Correct an administration and retain its history — Change status or notes, mark an erroneous entry without deleting it, and record a separate corrected replacement when needed.

Patient administration

Register a patient as Staff and verify the saved identity — Search first, review required demographics and configured geography, register once and distinguish patient creation from an encounter.
Find an existing patient, recover identity verification and avoid duplicate registration — Reopen an existing patient with correct birth year, recover a mismatch, handle the duplicate-contact advisory and recognize the pre-encounter profile boundary.
Register a distinct person and switch phone-linked patient context — Check for an existing record, complete required demographics and verify whose appointments you are managing.
Manage patient identifiers — Understand required, optional and generated identifiers, their scope, and which values staff may edit.
Register a patient — Register a new patient after searching existing records, complete demographics, and check facility identifiers.
Search for a patient — Find the correct patient by a configured identifier and resolve identity verification before opening a record.
Update patient details — Correct patient demographics and save changes without creating a replacement patient record.
View a patient's profile — Read the patient profile and open permitted encounters, clinical history, appointments and account information.
Patient — Definition A Patient in MANSOQ is a person who receives care through your facility or program. The patient record holds the demographic and contact details of that person. MANSOQ ties every encounter, condition, note, appointment, and clinical…
Manage patient identifiers — This flow describes how to set, view, and change the identifiers of a patient in MANSOQ. Identifiers name a patient in a way that goes beyond the name and the phone number. A national ID and a facility-specific ID are two examples. An…
Manage patient tags — This flow describes how to add and remove tags on a patient in MANSOQ. Tags are labels that mark or categorize a patient, separate from clinical data. Pre-requisites - The patient is registered in MANSOQ. - You can access the patient's profile.…
Manage patient users — This flow describes how to assign a user to a patient in MANSOQ. The assigned user supports the patient in the field, separate from the patient's clinical encounters. Pre-requisites - The patient is registered in MANSOQ. - The user that you…
Mark a patient as deceased — This flow describes how to record that a patient is deceased. You record the status and the date and time of death from the patient's profile. Pre-requisites - The patient is registered in MANSOQ. - You can open the patient's profile. - You…
Register a patient — This flow describes how to register a new patient in MANSOQ. Use it when a person comes to your facility and MANSOQ holds no record for that person. Pre-requisites - You are signed in to MANSOQ. - You searched for the patient first, and MANSOQ…
Search for a patient — This flow describes how to search for an existing patient in MANSOQ. Search for the patient first, before you register a new patient. This prevents duplicate patient records. Pre-requisites - You are a member of the facility where you search…
Update patient details — This flow describes how to update the details of a patient in MANSOQ. You edit the details from the patient's profile. Pre-requisites - The patient is registered in MANSOQ. - You can open the patient's profile. - You have the permissions listed…
View a patient's profile — This flow describes how to open the profile of a patient in MANSOQ. The profile shows the patient's demographic, contact, and clinical information in tabs. Pre-requisites - The patient is registered in MANSOQ. - You find the patient through a…
Patient — Technical reference for the Patient module in MANSOQ EMR. For a product-oriented overview, see the Patient concept. Source: care/emr/models/patient.py Models Model Purpose --- --- Patient Core patient record PatientOrganization Links a patient…

Pharmacy

Review prescriptions, statements and administration history — Keep medication orders, reported histories and administered events separate while reviewing a patient’s medication history.
Dispense a medication — Find a prescription in the pharmacy queue, review stock lots and quantities, generate and settle its invoice, then complete and verify the dispense.
Manage a prescription — Group medication requests into prescriptions and switch between one prescription and All Prescriptions.
Prescribe a medication — Create an encounter medication request with a catalogued product, dose, frequency, scheduling bounds and optional route, then verify the saved prescription.
Return unused medication to pharmacy stock — Use the authorized inventory role to prepare, approve, receive and complete a medication return, then verify stock and the generated refund invoice.
Medication Administration — Definition A medicine administration in MANSOQ records a dose of medicine that staff gave to a patient. It is separate from the medication request, which is the order. You record an administration against a medicine that is already prescribed…
Medication Dispense — Definition A medicine dispense in MANSOQ is the record of a medicine or a supply item that the pharmacy gives to a patient. The pharmacy gives the item from the facility's stock. A medicine dispense is separate from the medication request,…
Medication Request — Definition A medication request in MANSOQ is an order or prescription for a specific medicine for a patient. You create a medication request during an encounter. MANSOQ groups one or more medication requests together under a named prescription.…
Medication Statement — Definition A medication statement in MANSOQ records a medicine that a patient reports taking, or has taken on an ongoing basis. Unlike a medication request, a medication statement is not an order. It records what the patient says they take, not…
Administer a dose — This flow describes how to record a dose of a prescribed medicine that staff gave to a patient during an encounter in MANSOQ. Pre-requisites - The patient is registered in MANSOQ, and you record the dose for that patient. - The medicine is…
Update an administration record — This flow describes how to change a recorded medicine administration in MANSOQ. For example, you can mark a dose as Not Done, Stopped, or Entered in Error. Pre-requisites - Staff recorded the dose on the encounter. See Administer a dose. - The…
View the medication administration record — This flow describes how to read the medicine administration record of an encounter in MANSOQ. Pre-requisites - The patient is registered in MANSOQ, and you read the record for that patient. - The encounter has at least one prescribed medicine.…
Dispense a medication — This flow describes how to dispense a medicine or a supply item to a patient from the facility's stock in MANSOQ. Pre-requisites - The patient has an encounter at the facility. - You belong to the location that holds the stock. - The item you…
View dispense history — This flow describes how to view the medicine dispense history for an encounter in MANSOQ. Pre-requisites - The patient has an encounter at the facility. - You have the permission listed below. Permissions Permission Access --- --- Medication…
Add medications from past records — This flow describes how to add medicines from a patient's past records into a new prescription in MANSOQ. You start from the same screen that you use to prescribe a medication request. Pre-requisites - The patient is registered in MANSOQ, and…
Manage a prescription — A prescription is a named batch that groups one or more medication requests for the same encounter. This flow describes how to create a prescription and how to see the prescriptions of an encounter. Pre-requisites - The patient is registered in…
Prescribe a medication — This flow describes how to prescribe a medication for a patient during an open encounter in MANSOQ. Pre-requisites - The patient is registered in MANSOQ, and you record the medication for that patient. - The encounter is open. You cannot…
Print a prescription — This flow describes how to print a prescription from an encounter in MANSOQ. You can print one prescription, or every prescription in the encounter. Pre-requisites - The patient is registered in MANSOQ, and you open the encounter for that…
Update a prescription — This flow describes how to update a saved prescription in MANSOQ. You can add new medicines, edit notes, and remove a medicine you no longer need. Pre-requisites - The encounter is open. You cannot update a prescription when the encounter…
View prescriptions and medications for an encounter — This flow describes how to view the prescriptions and the prescribed medicines for an encounter in MANSOQ. Pre-requisites - The patient is registered in MANSOQ, and you open the encounter for that patient. - You have the permissions listed…
Mark a medication statement as entered in error — This flow describes how to retract a medication statement that staff recorded by mistake. Pre-requisites - The patient has a medication statement in MANSOQ. - The encounter of the medication statement is open. MANSOQ blocks the change when the…
Record a medication statement — This flow describes how to record a medication statement for a patient in MANSOQ. Pre-requisites - The patient is registered in MANSOQ, and you record the statement for that patient. - The patient has an encounter at your facility. MANSOQ…
Update a medication statement — This flow describes how to change a medication statement that you saved in MANSOQ. Pre-requisites - The patient has a medication statement in MANSOQ. - The encounter of the medication statement is open. MANSOQ blocks the change when the…
View medication statements for an encounter — This flow describes how to view the medication statements of a patient from an encounter in MANSOQ. Pre-requisites - The patient is registered in MANSOQ, and you open the encounter for that patient. - You have the permissions listed below.…
Medication Administration — MedicationAdministration records that a medication was given to a patient — or that giving it was attempted — fulfilling a MedicationRequest. You write one each time a dose is administered against an order. The Django model is the storage…
Medication Dispense — MedicationDispense records products handed to a patient and draws down the location's inventory as it does so. It closes out the workflow a Medication Request opens: in inpatient settings, items are dispensed into the room and refilled as…
Medication Request — A MedicationRequest records a prescriber's intent to supply or administer a medication to a patient — the FHIR MedicationRequest resource. You create one whenever a drug is ordered during an encounter; it carries the medication, dosage…
Medication Statement — A MedicationStatement records a medication the patient is taking, has taken, or intends to take, as reported by the patient, a relative, or a clinician rather than actively prescribed or dispensed. Reach for it when you're capturing a…

RCM & insurance

Configure queue ownership and complete a local case follow-up — Use actual work-queue readbacks with supported API creation, owner changes and task completion while preserving unsourced silence-window and unsupported routing limits.
Follow an episode from registration to cash — Understand the front, middle and back office controls connecting patient, encounter, account, claim and payment.
Set up insurers, TPAs and their legal roles — Keep legal entities, role authority and routing identifiers distinct when configuring insurance.
Configure insurer–administrator delegation and routing — Record who may handle each transaction, for which insurer and on which dates.
Create a provider contract without losing amendment history — Attach signed commercial scope, sites, dates and tariff terms to an auditable contract.
Configure products, issued policies and benefit classes — Separate what an insurer sells from the specific policy and class a patient belongs to.
Resolve coverage, authorization, cost share and limits — Read the independent decisions behind a benefit outcome and a patient estimate.
Import and publish contracted tariffs — Map performed services to the correct contract price with a dry run and independent approval.
Check network membership by site, service and date — Avoid assuming every branch of a provider has the same direct-billing participation.
Capture and resolve patient insurance coverage — Retain real coverage evidence while policy, class or identity conflicts are being resolved.
Verify eligibility and interpret the response — Understand coverage verification, site outcomes, freshness and remaining denial risks.
Prepare an insured visit and understand benefit holds — Create a provisional, evidenced financial decision without confusing a reservation with a finalized charge.
Submit and follow a prior authorization — Follow the request, validity, line sufficiency and response without treating a queued status as approval.
Assess authorization timing and deemed approval evidence — Use configured turnaround rules and a complete evidence pack when a response is late.
Preserve performed charges and their correction chain — Follow a clinical event to charge capture, claim lines and later amendments.
Complete coding and review claim documentation — Check diagnosis, procedures, DRG metadata and required supporting information before claim construction.
Build a claim and inspect readiness before submission — Create a separate claim record and review charge, coding, attachment and authorization evidence.
Work a denial with the right owner and deadline — Separate correction, evidence, reconsideration and appeal while preserving patient-liability controls.
Choose correction, information response or appeal — Recover a rejected or disputed claim using the transaction that matches the problem.
Stage, dry-run and publish insurance setup imports — Use register templates and row-level reports while preserving draft and activation boundaries.
Work blockers, exceptions and stuck transactions — Assign an owner and corrective action to unresolved operational conditions.
Retain, independently review and recover insurance source evidence — Follow actual retained-file integrity, separate content review and the failure of a legacy placeholder source.
Create insurance parties, roles, identifiers and administration drafts — Separate legal identity, licence facts, environment-qualified identifiers, delegated functions and settlement responsibility.
Draft provider contracts and policies with explicit unresolved facts — Follow the actual contract UI, verified document chain, policy API continuation and remaining activation guards.
Validate a candidate, investigate refusal and read a non-posting simulation — Use the exact server qualification and explicit supplied-input simulation without replacing missing evidence with pass flags.
Publish a fully guarded fictional organization-master package — Follow the observed successful one-row Clinic package with retained source bytes, separate reviewers and a current server receipt.
Follow cash before advice, fees, disputed suspense and reversals — Use actual queue and ledger readbacks plus the supported API handoff, preserving original rows and the difference between local cash position, reported advice and real evidence.
Prepare an immutable accounting handoff and read real close blockers — Freeze exact signed source rows, prepare a deterministic local payload and verify deduplication without claiming ERP posting or inventing an acceptance.
Discover coverage, interpret separate answers and preserve unresolved enrollment facts — Use exact wide enrollment controls for discovery, current refusal, saved local interpretation, conflicting evidence and partial mapping without turning unknown information into insurance clearance.
Record and verify all four denial remedies in separate tracks — Follow actual wide forms for correction, information response, reconsideration and claim-level appeal, with required fields, saved histories and unresolved liability made explicit.
Handle denial payload, replay and unsupported-linkage refusals — Use the supported remedy contract, diagnose real refusals and confirm retry outcomes without duplicate history or invented external authority.
Attest a charge, prepare an insured visit and build the guarded local claim — Follow exact wide controls and independent records through performed charge, provisional pricing, immutable API commitment and a saved claim whose remaining checks stay visible.
Read authorization evidence and plan four distinct change intents — Follow wide list/detail controls and supported API plans while preserving requested/authorized separation, stable line identities and every unresolved external prerequisite.

Reports & printing

Generate and view a report — Generate an encounter report from an Active template, verify the saved output and use its history, download and print controls.
Create a report template — Create a facility report template, insert available data fields and preview the result before saving.
Print a prescription — Print one prescription or every prescription in an encounter from the available prescription view.
Print a diagnostic report — Open a diagnostic report’s print-formatted page, verify its content and print the result.
Print a questionnaire response — Choose the permitted questionnaire-response output and print it from the correct patient or encounter context.

Scheduling

Maintain a private practitioner template and add a separately reviewed session — Edit template metadata, recover reversed validity dates, preserve the existing session and use the slot-duration calculator when adding another availability.

Workforce and access

Maintain your workforce profile and distinguish identity from department access — Identify your own account, understand an unchanged edit form, recover required-name validation, save ordinary display information and keep department roles separate.