Hospital information system in Jordan
We invite care teams in Jordan to review HIS software, with patient and quality needs assessed before we agree a proposed rollout for each site.
Best fit in Jordan
A specialist centre or private hospital in Jordan that needs continuity between the consultation, diagnostic work and the bill, and staff credentials, policies and investigation records that managers can examine when a question arises. The first step is to identify the systems already in use and the interfaces actually required, rather than assume a national programme can simply be replaced.
Local requirements and product support, side by side
- Local requirements to assess: Hakeem exchange, if any is proposed. Payer and insurer interfaces. HCAC accreditation evidence. Personal data protection and hosting.
- Can be reviewed now: Care through a consultation, a laboratory result and a billing record. Engage private-clinic booking, packages and patient relationships. Flow controlled documents, policy approvals, staff credentials, incidents, complaints and risk actions.
- Not confirmed: A live Hakeem connection and a universal insurer or TPA connection are not confirmed. No complete HCAC mapping or endorsement is claimed.
- Hosting: Hosting and access requirements are assessed before rollout. No local environment is stated as provisioned.
- Interface language: The current product interface is English. An Arabic interface or a Jordan office is not claimed.
The local workflow
Hakeem is the national digital-health programme operated by Electronic Health Solutions. Its existence does not establish a Care connection or unrestricted access to the records of enrolled institutions. Any proposed interaction needs an agreed technical and operational scope.
Jordan’s Health Care Accreditation Council, HCAC, provides accreditation context. Jordan’s Personal Data Protection Law No. 24 of 2023 and the Ministry of Digital Economy and Entrepreneurship’s guidance also belong in the deployment and processing review. Flow records may support the organisation’s own preparation. A clinical record or general claims module does not establish an accepted local transaction.
Confirm before scoping
- Which clinical, claims and accreditation-evidence needs come first?
- Which insurers or TPAs do you bill, and in what format?
- Is any Hakeem exchange proposed, and on what basis?
- Which local coding applies?
- Which Arabic-language, hosting, access and migration arrangements are needed?
Where the products fit
Care Clinics supports outpatient records and billing. Care Clinics Pro adds laboratory, radiology and claims. Care Hospitals adds inpatient, nursing, emergency and theatre workflows. Engage supports booking, packages and patient relationships. Flow supports the evidence your team reviews.
Flow Quality indicators is still being completed. Review its availability separately before a rollout depends on it.
A scoped demonstration
Bring a representative patient journey, a payer requirement and a quality-review topic. We will show current workflows against each requirement and list what needs separate confirmation.
Bring three things to your Jordan demo
A useful first conversation starts with your own work, not a feature list.
Book a demo-
A patient encounter
One representative visit, from registration to the signed clinical record.
-
A payer or payment workflow
The claim, invoice or package your team handles most, and the response it needs.
-
An evidence question
One licensing, quality or inspection requirement you need to be able to show.
What your teams can run in Jordan
Each product is selected and scoped on its own. These are the modules most relevant to Jordan, with how each one is bought.
NextHealth Care
Keep registration, clinical notes, prescriptions and billing on one patient record, with plans for outpatient clinics and hospitals.
2 modules most relevant to Jordan
-
Clinical Documentation & EMR Keep vitals, allergies, history and clinical notes together in the consultation workspace. NXH Care provides structured fields, templates, ICD-10 and CPT lookup, and optional dictation transcribed on the customer’s own infrastructure. The treating doctor signs the note, which is then frozen, and any later change is a signed addendum linked to the original. Included in all three Care plans. Explore -
Insurance Claims & Approvals Keep the insurance workflow attached to the patient visit. NXH Care checks eligibility where the payer’s service is connected, tracks prior authorisations, builds claims from the visit record for the payer’s gateway and checks them against payer rules. Submission, acknowledgement, decision and payment are separate statuses, and a rejection carries its coded reason into a correction and resubmission. Included in Care Clinics Pro and Care Hospitals; available as an add-on to Care Clinics. Explore
NextHealth Flow
Keep documents, workforce records, incidents and quality work organised across your facilities, starting with the modules you need.
3 modules most relevant to Jordan
-
Document hub Keep facility licences, contracts and documents with their dates, versions and signatures in NXH Flow. Review and expiry reminders help teams organise the next action. Outside parties can sign through a link confirmed with a one-time code. Choose Flow Documents separately or alongside Flow Quality when policy preparation and audits are also needed. Flow Documents is sold separately Explore -
Credentials and licences Keep professional licence numbers, authorities, expiry dates and copies on the staff record in Flow HR. Store passports and verification reports alongside them, remind staff before expiry and record renewal details. This supports credential administration while the facility remains responsible for checking eligibility and the validity of the evidence it holds. Flow HR is sold separately Explore -
Incident management Record incidents, harm levels, investigations and corrective and preventive actions in NXH Flow. Flag sentinel events, record root cause analysis and take each action through approval to closure. Flow Incidents is sold separately, or paired with Complaints. Flow Incidents is sold separately Explore
Running more than one product? NXH One connects their shared patient, staff and facility records. Explore NXH One
Common questions
-
A Hakeem connection is not confirmed. Identify the intended exchange and the responsible programme requirements, then review technical, testing and activation evidence before including it in a Jordan implementation.
-
No. Flow holds selected policies, credentials, investigations and actions for review. Accreditation concerns the facility and its assessed practice; no HCAC endorsement or complete product mapping is claimed.
-
No universal Jordanian insurer or TPA connection is confirmed. The actual payer workflow, coding and receiving format need separate review before operational submission is included in the proposed scope.
-
The product interface is currently English. Arabic is not claimed as a shipped interface. Assess staff language, patient documents and training needs before agreeing that the available workflows meet the facility’s requirements.
-
Agree the actual hosting region, backups and support access before implementation. NextHealth uses an in-country cloud region wherever regulation requires it; this page does not assert that a local environment is already provisioned.
Regulatory references 3
Official sources for the local context on this page, checked on 11 October 2026. They describe each programme, not a NextHealth connection.
Not answered here? Contact the team
