A remote critical-care review
The local team prepares the case so a remote specialist can review the supported context.
TeleICU
One bedside. Connected expertise.
Bring local critical-care context and remote specialist review together, with defined interfaces and clear clinical responsibility.
6Capabilities in the starting scope
4Workflow case studies
360° SOLUTION COVERAGE
Local care team
Prepare the supported case context for remote review.
MANSOQ IN PRACTICE
See the whole journey at work.
Four complete operational cases. Read each one here.
END-TO-END WORKFLOW CASE
A remote critical-care review
The local team prepares the case so a remote specialist can review the supported context.
The situation
A local ICU team requests a remote specialist review. The specialist needs the agreed clinical record, while bedside care stays with the local team.
What MANSOQ connects
Remote expertise needs clinical context and a clear return path to the bedside.
The people involvedLocal care teamIntegration & IT teamRemote specialist
The complete journey
Prepare the local case
Local care teamConfirm the patient encounter and document the question for specialist review.
Encounter · Review questionBring the supported context
Integration & IT teamMake the agreed notes and observations available through the selected source-system connection.
Source · Notes · ObservationsPerform the remote review
Remote specialistReview the available information and record the specialist’s assessment within the agreed service.
Review · Specialist noteReturn documented recommendations
Remote specialistDocument recommendations and the points requiring local clinical review.
Recommendations · Local reviewRecord the bedside decision
Local care teamReview the specialist note and record the local clinician’s care decision and responsibilities.
Local decision · Care responsibilityComplete the review handover
Local care teamDocument completed review work and any further specialist or bedside follow-up.
Review record · Follow-up owner
The factors that make it work
Starting information
Encounter · Review question
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.
Local clinical information is missing
Missing source information is referred back to the local team. Video, device data and live monitoring are separate connections, not assumed features of this scenario.
Responsible team · Local care teamInsufficient clinical context
The specialist records what is missing and asks the local clinical team to provide or clarify the source information.
Responsible team · Local care teamA connection is interrupted
The source and interface owners follow the agreed fallback. Bedside care and clinical decisions remain with the responsible local team.
Responsible team · Integration & IT teamScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
TeleICUNative operationConfirm deployment scope
System & Device InterfacesNative operation · Agreed connectionConfirm 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.
END-TO-END WORKFLOW CASE
A handover between care teams
The next team receives the documented review, care-plan context and assigned responsibilities.
The situation
A remote ICU specialist hands an ongoing review to the next specialist. The local team needs consistent context and explicit follow-up responsibility.
What MANSOQ connects
A change of specialist must not erase the review history.
The people involvedRemote specialistLocal care teamIntegration & IT team
The complete journey
Identify active review work
Remote specialistConfirm the patient case and the current documented specialist review.
Patient · Active reviewReview the local update
Local care teamProvide the documented clinical update within the agreed information-sharing scope.
Local update · Source contextRecord the specialist handover
Remote specialistDocument the previous review, open questions and next specialist responsibility.
Review history · Open questions · OwnerReview as the receiving specialist
Remote specialistRead the prior context and document the receiving specialist’s assessment.
Receiving review · AssessmentConnect back to local care
Local care teamReview the updated recommendations and retain local clinical decision responsibility.
Recommendations · Local decisionSet the next review action
Remote specialistRecord whether further review is required and which service owns it.
Next review · Responsible service
The factors that make it work
Starting information
Patient · Active review
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.
Local and remote records differ
If local and remote records differ, identify the source and ask the responsible clinician to reconcile the information before relying on it.
Responsible team · Local care teamInsufficient clinical context
The specialist records what is missing and asks the local clinical team to provide or clarify the source information.
Responsible team · Local care teamA connection is interrupted
The source and interface owners follow the agreed fallback. Bedside care and clinical decisions remain with the responsible local team.
Responsible team · Integration & IT teamScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
TeleICUNative operationConfirm deployment scope
Clinical Documentation & Care PlanningNative operationConfirm deployment scope
System & Device InterfacesNative operation · Agreed connectionConfirm 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.
END-TO-END WORKFLOW CASE
Orders and results in the review
Specialists review the supported order, result and medication context attached to the case.
The situation
A TeleICU review needs notes and results held in a local source system. The teams agree exactly which information is available for the review.
What MANSOQ connects
A remote record should show its source and permitted scope.
The people involvedLocal care teamIntegration & IT teamRemote specialist
The complete journey
Define the review dataset
Local care teamIdentify the clinical notes, observations and results required for this service.
Required information · Review scopeConfirm source ownership
Integration & IT teamDocument the source system, identity mapping and team responsible for the connection.
Source system · Mapping · OwnerMake agreed information available
Integration & IT teamCarry supported source information through the selected, tested interface.
Interface · Source referencesReview the source context
Remote specialistCheck the available context and identify any missing information for local follow-up.
Available notes · Missing contextDocument the professional review
Remote specialistRecord the review against the correct case and identify the information used.
Review note · Case · Source contextReturn the next action
Local care teamReview the specialist record and document the local care or information follow-up.
Local response · Follow-up
The factors that make it work
Starting information
Required information · Review scope
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.
Source data is unavailable
Unavailable data is made explicit in the review. An interface agreement determines what can be exchanged; no universal device compatibility is implied.
Responsible team · Integration & IT teamInsufficient clinical context
The specialist records what is missing and asks the local clinical team to provide or clarify the source information.
Responsible team · Local care teamA connection is interrupted
The source and interface owners follow the agreed fallback. Bedside care and clinical decisions remain with the responsible local team.
Responsible team · Integration & IT teamScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
Orders, Results & MedicationNative operationConfirm deployment scope
Clinical Documentation & Care PlanningNative operationConfirm deployment scope
System & Device InterfacesNative 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
An interface with clear ownership
The delivery team defines what is exchanged and who operates each side of the connection.
The situation
A hospital introduces a TeleICU connection alongside its existing clinical system. IT, clinicians and service leads need clear delivery and operating responsibilities.
What MANSOQ connects
A usable connection joins technical delivery to a real clinical handover.
The people involvedService leadershipIntegration & IT teamLocal care teamRemote specialist
The complete journey
Define the service boundary
Service leadershipAgree the local and remote teams, systems and information needed for the review service.
Teams · Systems · Information scopeSpecify the interface
Integration & IT teamDocument the agreed protocol, identity mapping, licenses and delivery owners.
Protocol · Mapping · Delivery ownerRehearse a supported case
Local care teamPrepare an authorized demonstration case and confirm the intended source information.
Demonstration case · Source recordVerify the exchange and access
Integration & IT teamReview the exchanged context, permitted access and agreed failure handling.
Exchange trace · Access · FallbackRehearse the review handover
Remote specialistDocument the review and demonstrate its return to the responsible local clinician.
Specialist review · Local handoverAccept the operating scope
Service leadershipAgree acceptance, support ownership and the activated service boundary.
Acceptance · Support · Activation
The factors that make it work
Starting information
Teams · Systems · Information scope
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.
An acceptance test fails
A failed test returns to the named interface owner. Activation follows agreed acceptance; connectivity does not grant unrestricted record access.
Responsible team · Integration & IT teamInsufficient clinical context
The specialist records what is missing and asks the local clinical team to provide or clarify the source information.
Responsible team · Local care teamA connection is interrupted
The source and interface owners follow the agreed fallback. Bedside care and clinical decisions remain with the responsible local team.
Responsible team · Integration & IT teamScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
System & Device InterfacesNative operation · Agreed connectionConfirm deployment scope
TeleICUNative 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.
Make it your TeleICU service.
Your solution is already selected. Adjust the services and review your proposal.
SOFTWARE + MANAGED OPERATIONS
A clear plan for every stage.
More capacity. More support. Choose how your care team grows.
Yearly prepayment · 10% off base software only
All prices are SAR before VAT. The setup and migration budget range is indicative; the final price follows the statement of work. Bespoke additions are quoted separately.
Select a feature or capacity label to learn more.
Essential
The essentials to run daily care.
SAR 6,500/ monthYearly: 10% off base software only; managed operations are not discounted.
50
1 site included
Your care foundation
Premium
For growthConnect your team and automate more.
SAR 12,500/ monthYearly: 10% off base software only; managed operations are not discounted.
150
1 site included
Everything in Essential, plus
Diamond
More controlManaged follow-through. Your data, your choice.
SAR 22,000/ monthYearly: 10% off base software only; managed operations are not discounted.
250
1 site included
Everything in Premium, plus
Enterprise
Built around your organisation.
Tailored to youA proposal from our sales team
550+
Custom capacity & sites
Everything in Diamond, plus
Diamond & Enterprise: keep the database and files in your own cloud, Spaces or server-hosted storage. Deployment and recovery are verified before launch.
RCM RaaS is additional to your subscription and is billed on approved eligible cleared collections. Enterprise requires an approved exact rate within its published range.
Included in every plan
Care workflows · secure access · audit trails · backups · patient and family communication · required NPHIES and ZATCA workflows · onboarding and support
Required NPHIES and ZATCA workflows are included in every plan. Live transmission is activated after your organisation’s NPHIES and ZATCA credentials and external acceptance.
Compare service scope, fees & additions
| Included / additional | Essential | Premium | Diamond | Enterprise |
|---|---|---|---|---|
| Base software / month | SAR 4,500 | SAR 8,500 | SAR 14,000 | Agreed with sales |
| Managed operations / month | SAR 2,000 | SAR 4,000 | SAR 8,000 | Agreed with sales |
| Extra care unit / month | SAR 200 | SAR 350 | SAR 500 | Agreed with sales |
| Extra site / month | SAR 1,500 | SAR 2,500 | SAR 4,000 | Agreed with sales |
| Extra managed hour | SAR 280 | SAR 280 | SAR 280 | Agreed with sales |
| Setup & migration budget (indicative) | SAR 10,000–SAR 20,000 | SAR 20,000–SAR 50,000 | SAR 40,000–SAR 100,000 | Agreed with sales |
| Your own database & storage | MANSOQ-managed storage | MANSOQ-managed storage | Available · scope agreed | Available · scope agreed |
VAT is additional where applicable. Annual prepayment discounts base software only. Customer infrastructure and bespoke integrations follow an agreed statement of work. The setup and migration budget range is indicative; the final price follows the statement of work.
Optional additions · quoted to your scope
AI documentation assistant
Opt-in; clinician review, consent, intended-use and supplier review required.
Branded patient / family app
Branding, distribution and app maintenance scoped separately.
Additional or bespoke interfaces
Each connector has an acceptance specification and supplier cost.
Devices, telepresence & connectivity
Customer-owned devices or separately quoted hardware, carrier and vendor fees.
On-site training
Travel, delivery days and attendance agreed in advance.
Dedicated hosting & continuity design
Architecture, recovery objectives and infrastructure require an Enterprise proposal.
RCM RaaS managed revenue service
The selected plan’s configured percentage of eligible cleared collections, additional to the package subscription. Enterprise requires an approved exact rate within its configured range and an accepted operating scope.
Messaging & video usage
Third-party usage budget and consent agreed; no unlimited carrier charges.
Responsibility and service boundaries
Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.
Routine service window and commissioning
Routine managed operations: Sunday–Thursday, 08:00–18:00 Arabia Standard Time, excluding agreed holidays. Critical technical incident cover is separately commissioned; operational hours are not 24/7 clinical coverage.
Included hours cover configuration, specialist review and agreed queue work; recorded in 15-minute increments. Review preparation counts. Additional care units and sites do not increase the included hours or interfaces. No rollover unless agreed. Notify at 80% / 100%; obtain approval before extra work. Product defects and critical support do not consume this allowance. Standard maintained interfaces exclude applicable national foundation connectors; bespoke connector build and vendor fees are separately scoped.
Prices describe the commercial scope. Before clinical launch, agree the statement of work, hosting / data terms, accepted interfaces, migration reconciliation, trained users, downtime and escalation tests, and commissioned support SLA. Availability and response targets require signed acceptance.