Talk to sales
Integrations

What connects to Nedhara today.

Nedhara is one system for the clinic day, so most of the work happens inside it. Where a clinic needs to reach outside, these are the connections the platform is built with, and the standards behind them.

Built into the platform

These connections are part of the product. A clinic switches them on and enters its own account details in Settings.

Built in

WhatsApp

Appointment booking, automated reminders and report delivery through the clinic’s own WhatsApp Business account. Five message templates, each with its own switch and preview.

Built in

Voice calls

A voice assistant that books appointments and sends reminders by phone, with transcription. The clinic connects its own provider, such as Twilio or Vonage.

Built in

Hospital information systems

A HIS integration layer for records, billing, laboratory, pharmacy and imaging, standardised on HL7 v2 and FHIR R4 and routed through one integration engine.

Built in

External laboratories

Tests the clinic does not run in-house are referred out, and the referral stays on the patient’s record.

Built in

Documents and prescriptions

Uploaded documents and paper prescriptions are read by OCR, and proposed record updates wait for a person to confirm them.

Built in

Data export

Patient records, appointments, invoices and clinical documents export in standard formats, including CSV and JSON for the activity log.

Standards and formats

The integration layer uses widely adopted healthcare standards, so a connection is configuration rather than custom code.

HL7 v2 and FHIR R4

Messages between Nedhara and a hospital information system, laboratory system or pharmacy system.

DICOM

Inbound imaging connectivity through the HIS layer.

ICD-10 and CPT

Diagnosis and procedure codes drafted from the signed note, each verified by staff before billing.

CSV and JSON

Exports of records, invoices and logs for reporting, accounting or moving systems.

Currencies and time zones

USD, EUR, GBP, AED, SAR, INR, CAD and AUD; time zones and date formats set per clinic.

Ask us about

These depend on your country, your existing systems or your plan. We will give you a straight answer for your setup.

Ask us

API access

Connections for Enterprise customers are set up with our team. Ask us what your use case needs.

Ask us

Payment gateways

Billing records several payment methods. Ask us whether a card-payment gateway is available in your region.

Ask us

Insurance claim submission

Codes are drafted and verified inside Nedhara. Electronic claim submission depends on the HIS connection in your country.

Have a system we should connect to?

Tell us what your clinic runs today. We will say clearly whether Nedhara connects to it, and how.