One foundation for care, relationships and facility operations
Care, Engage and Flow work from shared records. Choose the products your organisation needs, then review how patient, staff and facility information carries into the next task without building a separate record for every team.
How shared records behave
Each example is a supported connection between products. Whether it is active depends on the products and licences selected, and on the permissions each person holds.
- From enquiry to patient
- An enquiry in Engage can become a registered patient in Care without retyping. Review existing patient matches where human confirmation is required.
- From care to follow-up
- A clinical event in Care can raise an incident or complaint in Flow. The selected operational workflow then supports investigation and the recorded response.
- From charge to campaign
- A charge raised in Care reaches the linked Engage client, so its revenue can be reviewed beside the client’s recorded source.
- From staff record to care
- Staff licences in Flow sit on the same person record used in Care. The facility remains responsible for credential review and treatment authorisation.
- From one facility to the group
- Care supports a patient record across branches, while facility price lists and group reporting retain the local context needed to interpret the work.
- From one product to another
- Staff can sign in from Care to Engage without a second password. Organisation-wide identity federation, such as SAML, OIDC or SCIM, is a separate requirement to confirm with our team before it enters your scope.
Choose the products around the work
Care handles the patient and clinical encounter. Engage handles the commercial relationship before and after a visit. Flow handles facility records, investigations and operational review. NXH One is all three sold together as one package and connected on the shared foundation; it is not a fourth application to install.
You can begin with the product scope your facility needs and evaluate the connected workflows that matter next. Care plans, Engage add-ons and separately selected Flow modules still define what is available. Sharing a foundation does not mean every function is included in every purchase or every staff member can see every record.
Illustrative example: a handover that respects permissions
This example uses synthetic data. A clinician signs the visit of a synthetic patient, Layla Haddad, in Care. If the Engage connection is licensed for the facility and Layla has consented to sharing with Engage, Care sends Engage a signed-visit event. The event carries a hashed patient reference, a visit reference and the time of signing. It does not carry the clinical note. When the booking began in Engage, Engage can complete that visit against the booking it already holds, without holding Layla’s clinical record.
The same discipline applies inside Care. Each view of a patient’s chart is recorded with who opened it, which page and whether the person is in the care team. Where a group requires it, a person outside the care team is asked for a clinical access grant before the chart opens. Changes to audited records are recorded as well.
Both connections follow entitlement and consent, so an event is the result of settings your organisation chooses, not an automatic copy of the record.
NextHealth is Alpha Health Group’s health technology division, shaped by healthcare operating and regulatory consulting experience.
Review the platform from each angle
Interfaces, security, hosting, implementation and standards each have a page of their own. Take them in the order your technology and procurement teams ask the questions.
-
Interoperability
Care supports HL7 and FHIR exchange with acknowledgements retained. Review the relevant clinical exchange, claims route and coding scope for your facility before agreeing the connection and its implementation responsibilities.
-
Security and privacy
Roles, permissions, two-factor sign-in and audit trails support accountable access. Review those controls against your staff responsibilities, then agree the technical and privacy details required for the deployment.
-
Hosting and data residency
NextHealth hosts data in the UAE. For other markets, the hosting approach uses a country’s own cloud region where required, with deployment details, continuity arrangements and exit scope reviewed before agreement.
-
Implementation and support
Start with the workflows your teams need to run. Agree product scope, configuration and readiness checks before go-live, with migration, training and support arrangements made explicit in the implementation plan.
-
Standards library
See where NextHealth implements a format or control, where it records evidence your team can review, and where capability still needs confirmation. A listing here is not a certification: no entry means NextHealth, or a facility that uses it, holds an accreditation, certificate or regulator approval.
Common questions
-
No. Select the Care plan, Engage core and add-ons, and Flow modules that match your requirements. Shared architecture does not make every capability part of every purchase.
-
No. NXH One describes the connected use of Care, Engage and Flow on the shared foundation, rather than a separate fourth application.
-
No. Roles and permissions remain part of the platform. Review access arrangements against the responsibilities of your staff and the scope of the deployment.
-
No. The described Care connection includes human confirmation of patient matches. Carrying information forward without retyping does not remove that identity review.
-
Bring a patient journey or operational handover that currently crosses teams. Review the relevant products, the shared context and the responsibilities at each step.
Not answered here? Contact the team
NXH Flow