Care workflows

Continuity through every stay.

Admissions, bedside care and discharge around one person.

Admit & locate

Create the admission encounter and assign the patient to an appropriate ward and bed location. Confirm the responsible team and retain the referral or emergency context.

  • Admissions and ward team
  • Admission encounter, location and care-team assignment
View the full workflow
01 / 04
01

Inpatient Care

From the first action to the final record.

01

Admit & locate

Create the admission encounter and assign the patient to an appropriate ward and bed location. Confirm the responsible team and retain the referral or emergency context.

Responsible team
Admissions and ward team
Data & records
Admission encounter, location and care-team assignment
02

Coordinate care

Record assessments and observations, maintain the care plan and track service requests. Keep clinical notes, results and outstanding actions available to authorized ward staff.

Responsible team
Ward nurses and clinicians
Data & records
Observations, care documentation, orders and reports
03

Medication & transfers

Connect medication requests, administration records and pharmacy dispensing. On a ward or team transfer, review the current plan, location and unresolved tasks with the receiving team.

Responsible team
Ward, pharmacy and receiving team
Data & records
Medication administrations, dispense records and transfer context
04

Discharge & reconcile

Complete the discharge record, medication instructions and follow-up responsibility. Review documented service activity and open financial items through billing and the selected revenue-cycle workflow.

Responsible team
Discharge coordinator and finance
Data & records
Discharge summary, follow-up plan and financial account
02

Your configuration

The data that makes this module yours.

  1. Download the template for your account’s selected release.
  2. Use the sample to understand formats; replace every example with approved data.
  3. Load parent records first, then use their exact identifiers in dependent files.
  4. Upload in the named setup step, fix validation errors and review the preview.
  5. Apply and save; test the workflow and record approval before activation.
Your organizationorganization.csvAccount configuration

Use the registered details of your organization. Do not enter patient records here.

Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.

Columns, formats and example values
ColumnRequiredFormatExample
Registered organization namelegal_nameYestextExample Healthcare Organization
Commercial registration numberregistration_numberYestextEXAMPLE-CR-001
CountrycountryYesSA / AE / BH / KW / QA / OM / EG / OTHERSA
Tax registration numbervat_numberOptionaltext—
Facilitiesfacilities.csvAccount configuration

Add every facility included in your subscription. These become real, separate facilities in your app.

Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.

Load / review first: Your organization

Columns, formats and example values
ColumnRequiredFormatExample
Facility namenameYestextExample Facility
Facility typetypeYeshospital / clinic / polyclinic / laboratory / otherclinic
Facility licenselicense_numberYestextEXAMPLE-LICENSE-001
AddressaddressYestextExample training address
PhonephoneYestext+966500000000
Time zonetimezoneYesAsia/Riyadh / Asia/Dubai / Asia/Qatar / Africa/Cairo / UTCAsia/Riyadh
Departmentsdepartments.csvAccount configuration

Create departments, consultation rooms, wards and beds. You can add more inside your app.

Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.

Load / review first: Facilities

Columns, formats and example values
ColumnRequiredFormatExample
Facility number (starting at 1)facilityYesinteger 1–10001
Department namenameYestextExample Department
Rooms, wards and bedslocations.csvAccount configuration

Create departments, consultation rooms, wards and beds. You can add more inside your app.

Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.

Load / review first: Facilities

Columns, formats and example values
ColumnRequiredFormatExample
Facility numberfacilityYesinteger 1–10001
Location namenameYestextExample Room
TypekindYesroom / ward / bedroom
Inside location (optional)parentOptionaltext—
Planned teamstaff.csvAccount configuration

Your verified account becomes the facility administrator. Invite staff in the account portal; staff seats are enforced.

Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.

Columns, formats and example values
ColumnRequiredFormatExample
NamenameYestextExample Staff
Work emailemailYesemailstaff@example.invalid
Clinical roleroleYesfacility_admin / doctor / nurse / pharmacist / reception / billing / memberdoctor
Roles & permissionsroles.csvAccount configuration

Security roles and explicit permissions

Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.

Columns, formats and example values
ColumnRequiredFormatExample
Role namerole_nameYestextExample scheduling role
Permission identifierpermission_slugYestextcan_list_schedule
Users & department accessuser_access.csvAccount configuration

Facility organization memberships

Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.

Load / review first: Planned team · Departments · Roles & permissions

Columns, formats and example values
ColumnRequiredFormatExample
Staff emailstaff_emailYesemailstaff@example.invalid
Facility numberfacilityYesinteger 1–10001
Department namedepartmentYestextExample Department
Approved role namerole_nameYestextDoctor
Doctors & operational clinicsdoctors.csvAccount configuration

User clinician profile and clinic affiliation

Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.

Load / review first: Planned team · Departments · Rooms, wards and beds · Users & department access

Columns, formats and example values
ColumnRequiredFormatExample
Doctor emailstaff_emailYesemailstaff@example.invalid
Facility numberfacilityYesinteger 1–10001
DepartmentdepartmentYestextExample Department
Clinic locationclinic_locationYestextExample Room
QualificationqualificationYestextTO-CONFIRM
Practitioner licencelicense_numberYestextEXAMPLE-LICENSE-001
Primary clinicprimary_clinicOptionalcheckboxtrue
Inventory & medication itemsstock_items.csvAccount configuration

Product knowledge catalogue

Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.

Load / review first: Facilities

Columns, formats and example values
ColumnRequiredFormatExample
Unique item codeitem_codeYestextEXAMPLE-ITEM-001
Facility numberfacilityYesinteger 1–10001
Item namenameYestextTraining consumable
Typeproduct_typeYesmedication / consumable / nutritional_productconsumable
UCUM unit codeunit_codeYestext1
Terminology systemcode_systemOptionaltext—
External codeexternal_codeOptionaltext—
Assets, devices & hardwareassets_devices.csvAccount configuration

Device register, location and department assignment

Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.

Load / review first: Departments · Rooms, wards and beds

Columns, formats and example values
ColumnRequiredFormatExample
Unique asset codeasset_codeYestextEXAMPLE-LAB-001
Facility numberfacilityYesinteger 1–10001
DepartmentdepartmentYestextExample Department
LocationlocationYestextExample Room
Device namenameYestextTraining laboratory analyser
ManufacturermanufacturerYestextExample manufacturer
ModelmodelYestextEXAMPLE-MODEL
Serial numberserial_numberYestextEXAMPLE-SERIAL
Product / department purposecare_typeYestextlaboratory
Interface protocol and versionprotocolOptionaltextTO-CONFIRM
Maintenance duemaintenance_dueOptionalYYYY-MM-DD2027-10-09
Function settings · scheduling closuresproduct_settings.csvAccount configuration

Registry function settings applied to native scheduling closures with readback

Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.

Load / review first: Rooms, wards and beds

Columns, formats and example values
ColumnRequiredFormatExample
Facility numberfacilityYesinteger 1–10001
Selected feature IDfeatureYesschedulingscheduling
Function settingfunction_keyYesscheduling.closuresscheduling.closures
Closure namenameYestextExample closure
First closed datevalid_fromYesYYYY-MM-DD2026-12-01
Last closed datevalid_toYesYYYY-MM-DD2026-12-01
Closed fromstart_timeYesHH:MM08:00
Closed untilend_timeYesHH:MM17:00
Room (blank closes the whole facility)locationOptionaltextExample Room
Project scopeproject_scope.csvImplementation record

Freeze products, versions, facilities, delivery mode and acceptance scope.

Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.

Columns, formats and example values
ColumnRequiredFormatExample
Catalogue product IDproduct_idYestextoutpatient
Agreed releasereleaseYestextTO-CONFIRM
Operating modemodeYesnative / connectednative
Facility scopefacility_scopeYestextall
Included in this projectincludedYestrue / falsetrue
Accountable roleowner_roleYestextProject owner
Acceptance evidenceacceptance_testYestextApproved end-to-end test
Approval referenceapproval_referenceYestextEXAMPLE-REF-001
Access & approvalsaccess_matrix.csvImplementation record

Map roles to permitted actions and verify access across facility boundaries.

Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.

Load / review first: Facilities · Planned team

Columns, formats and example values
ColumnRequiredFormatExample
RoleroleYestextdoctor
Facility scopefacility_scopeYestextEXAMPLE-FACILITY-001
ResourceresourceYestextPatient record
ActionactionYestextread
AllowedallowedYestrue / falsetrue
Approverapprover_roleYestextSecurity owner
Test evidenceevidence_referenceYestextEXAMPLE-REF-001
Clinical workflow configurationclinical_workflows.csvImplementation record

Record locally approved pathways, responsibilities and exception handling.

Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.

Load / review first: Departments · Access & approvals

Columns, formats and example values
ColumnRequiredFormatExample
Workflow IDworkflow_idYestextEXAMPLE-WF-001
Product IDproduct_idYestextoutpatient
Entry evententry_eventYestextPatient arrival
Responsible roleresponsible_roleYestextNurse
Required informationrequired_informationYestextVerified identity and visit context
Next eventnext_eventYestextClinical consultation
Handover ownerhandover_ownerYestextDoctor
Exception pathexception_pathYestextIdentity mismatch to review
Workflow approvalapproval_referenceYestextEXAMPLE-REF-001
Acceptance testsuat_cases.csvImplementation record

Record complete positive, negative, boundary, access and failure tests per product.

Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.

Load / review first: Project scope · Clinical workflow configuration

Columns, formats and example values
ColumnRequiredFormatExample
Test IDtest_idYestextUAT-001
Product IDproduct_idYestextoutpatient
ScenarioscenarioYestextVisit from arrival to financial follow-up
PreconditionspreconditionsYestextApproved setup and synthetic data
Exact actionsactionsYestextTO-CONFIRM
Expected resultexpected_resultYestextTO-CONFIRM
Actual resultactual_resultYestextNOT-RUN
StatusstatusYesnot_run / pass / fail / blockednot_run
Evidence referenceevidence_referenceYestextEXAMPLE-REF-001
Approverapprover_roleYestextProduct owner
Open the full implementation handbook: assumptions, migration, interfaces, acceptance and cutover
03

Illustrative operating cases

Two cases. Every handover explained.

01Illustrative scenario

Admission through planned discharge

A patient enters a ward, receives daily care and leaves with a follow-up plan.

Prepare first
Ward and bed locations, care roles, medication and departmental services, discharge documentation.
  1. Admissions opens the stay and assigns the ward and responsible team.
  2. Ward staff document observations, care and orders; pharmacy and departments fulfil the selected requests.
  3. At each handover the receiving team reviews current treatment and outstanding work.
  4. The discharge team completes the summary, medication instructions and follow-up, then finance reconciles recorded services.

Acceptance evidence

The stay, care records, medication activity and discharge responsibility remain connected.

02Illustrative scenario

Ward transfer with a pending investigation

A patient changes ward before a requested diagnostic report is complete.

Prepare first
Receiving location, permitted care team and unresolved request list.
  1. Record the destination and receiving responsibility without creating an unrelated patient.
  2. Review active medication and care documentation at transfer.
  3. Carry the pending request and name the clinician who will review its result.
  4. Reconcile the returned report and discharge actions with the receiving team.

Acceptance evidence

The report remains linked to the original request and has an explicit follow-up owner after transfer.

04

Worked operating scenarios

When the normal path changes.

Bed or team changes during admission

Update the destination and responsibility, then verify medication, orders and unresolved tasks at handover.

Discharge with a pending result

Record the outstanding request, the reviewing clinician and the patient communication plan before closing the pathway.

05

Delivery boundary

Know what connects, and what needs approval.

An inpatient encounter brings the stay together. ICU, surgery, pharmacy and departmental interfaces retain their own configuration, access and acceptance requirements.

Operating modes
Native
Product readiness
Scope review required for your release
Supported release
Confirm in the accepted scope

Your questions, answered.

What does MANSOQ Inpatient Care cover?

Admission, transfer and discharge, wards, beds, nursing, orders and medication in a complete admitted-care workflow. Admit & locate: Create the admission encounter and assign the patient to an appropriate ward and bed location. Confirm the responsible team and retain the referral or emergency context. Coordinate care: Record assessments and observations, maintain the care plan and track service requests. Keep clinical notes, results and outstanding actions available to authorized ward staff. Medication & transfers: Connect medication requests, administration records and pharmacy dispensing. On a ward or team transfer, review the current plan, location and unresolved tasks with the receiving team. Discharge & reconcile: Complete the discharge record, medication instructions and follow-up responsibility. Review documented service activity and open financial items through billing and the selected revenue-cycle workflow.

Explore the details
What setup data does Inpatient Care need?

Configure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Rooms, wards and beds (locations.csv); Users & department access (user_access.csv); Doctors & operational clinics (doctors.csv); Clinical workflow configuration (clinical_workflows.csv); Assets, devices & hardware (assets_devices.csv); Inventory & medication items (stock_items.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.

Explore the details
How does Inpatient Care handle exceptions?

Bed or team changes during admission Update the destination and responsibility, then verify medication, orders and unresolved tasks at handover. Discharge with a pending result Record the outstanding request, the reviewing clinician and the patient communication plan before closing the pathway.

Explore the details
How does Inpatient Care connect with other systems?

An inpatient encounter brings the stay together. ICU, surgery, pharmacy and departmental interfaces retain their own configuration, access and acceptance requirements.

Explore the details
Explore all frequently asked questions