Admission to discharge
A patient moves from admission to the ward, then leaves with a connected discharge record.
Hospitals
Hospitals. The complete journey.
Explore the people, decisions and connected records from the first action to the final handover.
5complete operational cases.Workflow illustrations
END-TO-END WORKFLOW CASE
Admission to discharge
A patient moves from admission to the ward, then leaves with a connected discharge record.
The situation
A patient arrives for a planned inpatient stay. Reception, the ward, diagnostics and finance must work from the same encounter through discharge.
What MANSOQ connects
An admission is one journey, even when responsibility changes between several teams.
The people involvedAccess & coordinationNursing teamTreating clinicianDepartment teamFinance team
The complete journey
Establish the encounter
Access & coordinationConfirm the patient identity, admission details and responsible service against the shared record.
Identity · Admission · ServiceReceive the patient on the ward
Nursing teamDocument the ward handover, observations and care responsibilities for the incoming team.
Ward · Observations · Responsible teamDocument and request
Treating clinicianRecord the assessment and connect medication and departmental requests to this inpatient encounter.
Clinical notes · Orders · MedicationBring department work back
Department teamComplete the selected laboratory or pharmacy work and return its documented result to the care context.
Request · Department activity · ResultPrepare the next care step
Treating clinicianRecord the discharge summary, medication plan and follow-up responsibility for the next team.
Discharge summary · Follow-upClose the financial encounter
Finance teamReview encounter-linked charges, patient liability and payments; assign any outstanding balance for follow-up.
Charges · Invoice · Balance
The factors that make it work
Starting information
Identity · Admission · Service
Responsibility at every step
Each stage identifies the team, the action and the record carried forward.
An agreed operating scope
Confirm the selected capabilities, required companions and external connections during configuration.
Exceptions. A clear next responsibility.
Outstanding discharge work
If a result or discharge task is outstanding, keep it attached to the encounter with a named owner; the clinical team decides the care action.
Responsible team · Treating clinicianAn incomplete handover
Keep missing notes or results attached to the encounter. The receiving team identifies the responsible service and records the follow-up.
Responsible team · Nursing teamA service or account discrepancy
Return the disputed item to its source activity. Review the charge or record correction with the responsible team before financial closure.
Responsible team · Finance teamScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
Inpatient CareNative operationConfirm deployment scope
Clinical Documentation & Care PlanningNative operationConfirm deployment scope
Orders, Results & MedicationNative operationConfirm deployment scope
Billing & FinanceNative operation · Agreed connectionConfirm deployment scope
Patient AccessNative operationConfirm deployment scope
LaboratoryNative operationConfirm deployment scope
PharmacyNative operationConfirm deployment scope
InventoryNative operationConfirm deployment scope
External systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Day surgery, end to end
The clinical and operating-room teams work through preparation, procedure and recovery.
The situation
A patient attends a scheduled day-surgery service. Booking, theatre preparation, the procedure, recovery and billing must remain connected.
What MANSOQ connects
Theatre readiness and the recovery handover need more than a booking on a calendar.
The people involvedAccess & coordinationTreating clinicianDepartment teamNursing teamFinance team
The complete journey
Book the surgical case
Access & coordinationLink the scheduled case, patient and responsible surgical service to the encounter.
Booking · Encounter · ServicePrepare the case
Treating clinicianDocument the agreed preoperative assessment and preparation requirements for the surgical team.
Assessment · Preparation recordCoordinate theatre resources
Department teamConnect the case to selected theatre resources and required consumables within the agreed operating-room scope.
Theatre · Resources · ConsumablesDocument the procedure
Treating clinicianRecord perioperative activity and the procedure against the patient’s case rather than a separate account.
Procedure · Perioperative notesHand over to recovery
Nursing teamCarry the procedure record, observations and next responsibilities into recovery and discharge documentation.
Recovery · Handover · DischargeReview case-linked charges
Finance teamReconcile recorded services and consumables with the case bill and assign financial follow-up.
Services · Consumables · Bill
The factors that make it work
Starting information
Booking · Encounter · Service
Responsibility at every step
Each stage identifies the team, the action and the record carried forward.
An agreed operating scope
Confirm the selected capabilities, required companions and external connections during configuration.
Exceptions. A clear next responsibility.
A rescheduled surgical case
When a case is rescheduled, update the booking and resource responsibility while retaining the preparation record for review.
Responsible team · Access & coordinationAn incomplete handover
Keep missing notes or results attached to the encounter. The receiving team identifies the responsible service and records the follow-up.
Responsible team · Nursing teamA service or account discrepancy
Return the disputed item to its source activity. Review the charge or record correction with the responsible team before financial closure.
Responsible team · Finance teamScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
Outpatient CareNative operationConfirm deployment scope
Operating RoomNative operationConfirm deployment scope
InventoryNative operationConfirm deployment scope
Billing & FinanceNative operation · Agreed connectionConfirm deployment scope
Clinical Documentation & Care PlanningNative operationConfirm deployment scope
Orders, Results & MedicationNative operationConfirm deployment scope
Patient AccessNative operationConfirm deployment scope
External systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Critical-care handover
The next ICU team reviews the observations, medication and responsibilities it needs.
The situation
An ICU patient’s care is handed from one shift to the next. The incoming team needs the documented observations, medication and pending work together.
What MANSOQ connects
A handover must transfer responsibility as well as information.
The people involvedNursing teamTreating clinicianDepartment teamFinance team
The complete journey
Confirm the care context
Nursing teamOpen the correct inpatient encounter and confirm the current ICU team and location.
Identity · Encounter · ICU locationReview documented observations
Treating clinicianReview recorded observations and clinical notes with their encounter context; assess care professionally.
Observations · Clinical notesCarry medication context
Nursing teamBring the documented medication and order context into the handover for the responsible clinical team.
Medication · Current ordersReview department follow-up
Department teamLink available results and outstanding departmental work to the same encounter.
Results · Pending requestsRecord the shift handover
Nursing teamDocument the care handover and identify who takes responsibility for each next action.
Handover note · Next ownerContinue or transfer care
Treating clinicianUpdate the next care plan or documented ward transfer while preserving the ICU encounter history.
Care plan · Transfer record
The factors that make it work
Starting information
Identity · Encounter · ICU location
Responsibility at every step
Each stage identifies the team, the action and the record carried forward.
An agreed operating scope
Confirm the selected capabilities, required companions and external connections during configuration.
Exceptions. A clear next responsibility.
Missing handover information
If information is missing, identify its source and responsible team in the handover instead of treating an absent result as a completed task.
Responsible team · Nursing teamAn incomplete handover
Keep missing notes or results attached to the encounter. The receiving team identifies the responsible service and records the follow-up.
Responsible team · Nursing teamA service or account discrepancy
Return the disputed item to its source activity. Review the charge or record correction with the responsible team before financial closure.
Responsible team · Finance teamScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
Inpatient CareNative operationConfirm deployment scope
Intensive CareNative operationConfirm deployment scope
Clinical Documentation & Care PlanningNative operationConfirm deployment scope
Orders, Results & MedicationNative operationConfirm deployment scope
LaboratoryNative operationConfirm deployment scope
Billing & FinanceNative operation · Agreed connectionConfirm deployment scope
External systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Care delivered. Revenue followed.
Revenue teams follow service activity through billing, payer responses and reconciliation.
The situation
A hospital encounter includes ward care, departmental services and patient payments. Finance needs to explain every charge and remaining balance.
What MANSOQ connects
Revenue follow-up starts with the services actually recorded in the encounter.
The people involvedAccess & coordinationDepartment teamRevenue teamFinance teamNursing team
The complete journey
Establish financial responsibility
Access & coordinationRecord the patient, encounter and payer or self-pay context before financial follow-up.
Encounter · Payer · Patient accountCapture delivered activity
Department teamLink recorded departmental and care services to accountable encounter charges.
Service activity · Charge referenceReview prices and contribution
Revenue teamCheck the agreed tariffs and patient contribution against the recorded services and coverage.
Tariff · Coverage · ContributionIssue the invoice
Finance teamReview the invoice and use the selected ZATCA exchange scope where configured and activated.
Invoice · E-invoice responseAllocate payments
Finance teamMatch recorded payments or payer financial responses to the relevant account and invoice.
Payment · Allocation · BalanceResolve the remaining balance
Revenue teamAssign unresolved differences for review and record the reconciliation decision and next action.
Difference · Owner · Reconciliation
The factors that make it work
Starting information
Encounter · Payer · Patient account
Responsibility at every step
Each stage identifies the team, the action and the record carried forward.
An agreed operating scope
Confirm the selected capabilities, required companions and external connections during configuration.
Exceptions. A clear next responsibility.
A disputed charge
A disputed charge returns to its service reference for review; a corrected financial record keeps the original encounter trace.
Responsible team · Finance teamAn incomplete handover
Keep missing notes or results attached to the encounter. The receiving team identifies the responsible service and records the follow-up.
Responsible team · Nursing teamA service or account discrepancy
Return the disputed item to its source activity. Review the charge or record correction with the responsible team before financial closure.
Responsible team · Finance teamScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
Revenue Cycle ManagementNative operation · Agreed connectionConfirm deployment scope
Billing & FinanceNative operation · Agreed connectionConfirm deployment scope
ClaimsNative operation · Agreed connectionConfirm deployment scope
ReconciliationNative operation · Agreed connectionConfirm deployment scope
Tariffs & Price ListsNative operation · Agreed connectionConfirm deployment scope
Benefits & Cost SharingNative operation · Agreed connectionConfirm deployment scope
Charge CaptureNative operation · Agreed connectionConfirm deployment scope
ZATCA E-invoicingNative operation · Agreed connectionConfirm deployment scope
EligibilityNative operation · Agreed connectionConfirm deployment scope
PreauthorizationNative operation · Agreed connectionConfirm deployment scope
Payer ContractsNative operation · Agreed connectionConfirm deployment scope
NetworksNative operation · Agreed connectionConfirm deployment scope
Denials & ResubmissionNative operation · Agreed connectionConfirm deployment scope
RemittanceNative operation · Agreed connectionConfirm deployment scope
RCM ReportingNative operation · Agreed connectionConfirm deployment scope
External systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
From emergency arrival to ward care.
Keep the emergency assessment, admitted-care handover and financial encounter connected.
The situation
Following emergency assessment, the treating team decides a patient needs admission. The ward receives the documented care context and responsibility.
What MANSOQ connects
The ward needs the emergency story, not only a new admission record.
The people involvedAccess & coordinationTreating clinicianNursing teamFinance team
The complete journey
Register the emergency encounter
Access & coordinationConfirm identity and establish the emergency encounter.
Identity · Emergency encounterDocument the assessment
Treating clinicianRecord observations, assessment and the treating clinician’s care decisions.
Assessment · Observations · DecisionsConnect urgent requests
Treating clinicianLink documented medication and department requests to the emergency encounter.
Orders · Medication · ResultsRecord the admission decision
Treating clinicianDocument the admission decision and receiving service responsibility.
Admission decision · Receiving serviceHand over to the ward
Nursing teamCarry the emergency context and pending work into the ward handover.
Emergency note · Ward handoverContinue care and account review
Finance teamReview encounter-linked service charges while the ward documents continued care.
Ward record · Encounter charges
The factors that make it work
Starting information
Identity · Emergency encounter
Responsibility at every step
Each stage identifies the team, the action and the record carried forward.
An agreed operating scope
Confirm the selected capabilities, required companions and external connections during configuration.
Exceptions. A clear next responsibility.
The transfer or pending work changes
A changed destination or outstanding result remains part of the documented transfer and is assigned to the responsible care team.
Responsible team · Nursing teamAn incomplete handover
Keep missing notes or results attached to the encounter. The receiving team identifies the responsible service and records the follow-up.
Responsible team · Nursing teamA service or account discrepancy
Return the disputed item to its source activity. Review the charge or record correction with the responsible team before financial closure.
Responsible team · Finance teamScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
Emergency CareNative operationConfirm deployment scope
Inpatient CareNative operationConfirm deployment scope
Clinical Documentation & Care PlanningNative operationConfirm deployment scope
Orders, Results & MedicationNative operationConfirm deployment scope
Billing & FinanceNative operation · Agreed connectionConfirm deployment scope
External systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.