Product announcements
NEXCRM now comes embedded in NEXMAS
Schemes that choose NEXMAS now get the relationship layer inside it, so membership, claims and interaction history sit on one member profile without a second deployment.
Published by Nexcool IT Systems
NEXCRM has always been able to read membership and claims activity from the medical administration backend a scheme runs. What changes now is packaging: if you choose NEXMAS, NEXCRM is embedded in it.
What that means in practice
The service team works from the administration record instead of a parallel system. Member identity, claim history and interaction history sit on one profile, and there is no second platform to rent, run or keep in step.
NEXCRM still stands on its own
Not every team needs NEXMAS. NEXCRM connects to the health insurance backend medical administration system an organisation already runs, whether that system is NEXMAS or another medical administration backend, and it works from the member, claim and benefit records that backend holds. The embedded arrangement is a convenience for schemes that are already running NEXMAS, not a requirement.
What does not change
- NEXPHARM remains a standalone pharmacy system, with no dependency on NEXMAS or NEXCRM
- The chronic register remains part of NEXMAS and NEXPHARM
- The NEXMAS rules engine remains the decision layer for claims and membership processing
- Commercial terms are unchanged; the embedded arrangement is included in the NEXMAS rental scope rather than charged as a separate subscription line
For existing NEXMAS customers
Embedding is a configuration change rather than a migration. Member and claim records already in NEXMAS become the profile that NEXCRM reads, and interaction history begins accumulating from the point the module is switched on.
