Access by responsibility
Role-based access and facility context limit what each team can view and change.
MANSOQ Platform
Security & trust
Evaluate access controls, auditability, hosting and integration requirements with evidence for the specific MANSOQ deployment.
Trust comes from controls you can examine.
Audit and evidence
Clinical and financial actions carry traceability; revenue controls preserve the evidence behind decisions.
Deployment review
Hosting, residency, backups, retention and incident responsibilities are agreed for each implementation.
Certification evidence
MANSOQ does not inherit OHC certifications, endorsements or deployment counts. Ask for MANSOQ-specific evidence during evaluation.
Open interfaces. Explicit boundaries.
Clinical interoperability
The clinical core uses FHIR-aligned resources and APIs. National exchanges use their own governed profiles.
Saudi revenue exchange
NPHIES adapters prepare and validate exchange payloads. Production access depends on credentials, testing and regulator approval.
Terminology ownership
Terminology releases, file hashes and licence references are recorded. Licensed coding data is supplied through authorized sources.
Modular deployment
Clinical, web, remote care, revenue and intelligence components retain clear runtime and release boundaries.