MANSOQ Core
Identity, the shared record, governed access, audit and common configuration. A possible duplicate is reviewed before another patient is created, and each team member works under their own assigned identity.
Explore MANSOQ CoreTHE MANSOQ PLATFORM
Connect care, departments and revenue around one shared record.
HOW THE PLATFORM FITS TOGETHER
MANSOQ is composed in layers. MANSOQ Core holds the person’s identity and record, and every other layer builds on it, so registration, clinical work, departments and revenue follow the same context instead of copying it between systems. You select only the layers your organization needs and agree their exact scope before activation.
Identity, the shared record, governed access, audit and common configuration. A possible duplicate is reviewed before another patient is created, and each team member works under their own assigned identity.
Explore MANSOQ CoreWorkflows for outpatient, inpatient, emergency, TeleICU and home & palliative care. Each carries the care context from arrival or referral through every handover to the next step.
Explore Care settingsClinical documentation and care planning; orders, results and medication; and departmental operation for the operating room, intensive care, pharmacy, laboratory, radiology and inventory.
Explore Clinical modules and departmentsEligibility, preauthorization, payer contracts, charge capture, claims, denials and resubmission, remittance and reconciliation, with NPHIES exchange and ZATCA e-invoicing in the agreed scope. Managed revenue services can take on agreed worklists.
Explore Revenue cycleSystem and device interfaces, HL7 FHIR resources and supported APIs. Each maintained interface names its source, target, message types, version and owner, and is commissioned before use.
Explore IntegrationsOperational and financial views built from agreed sources, with a named data owner, a reporting boundary and completeness checks, so each team sees the work it is responsible for.
Explore AnalyticsReviewed AI assistance for approved text or image tasks. Each use case has permitted data, a responsible reviewer, evaluation criteria and a manual fallback agreed before activation.
Explore AINot sure where to start? Build a configuration from your care setting, or read the implementation guide to see how migration, interfaces and training are agreed.