Clinical interoperability
The clinical core uses FHIR-aligned resources and APIs. National exchanges use their own governed profiles.
MANSOQ Platform
Develop with MANSOQ
Discuss component boundaries, FHIR resources and deployment requirements with the MANSOQ team.
Open interfaces. Explicit boundaries.
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.
Start with the source.
Technical documentation
Request architecture, integration guidance and component-level licence information from the MANSOQ team.
Integration planning
Describe your systems, data boundaries and workflow needs before building an adapter.