RUN NHIF · XML file per dentist

The monthly NHIF report from your visits.

DentaFlow builds XML from real visits — a separate file for each dentist under the contract — and checks required data against the NHIF XSD schema. You upload the file in the NHIF portal.

  • Ordinance №42 · Jan 2025
  • 403 KSMP codes
  • XML per the NHIF XSD
  • In the base subscription · no extra price
  • Submits to NHIS · base subscription

What's in the NHIF module.

Six capability cards. No marketing language — just what DentaFlow actually does today.

403 codes · Jan 2025

403 KSMP codes

The catalogue contains 403 KSMP codes under Ordinance №42; a service without one is flagged "No code." You choose the NRD code when recording the activity, with the NRD 2026–2028 prices in euro from 1 Sep 2026 and the 103xx codes for the extra pregnancy exam.

XSD check

Check on generation

Before you generate, "NHIF claims" lists every patient missing data the claim needs — EGN/LNCh, RHIF and health region of residence, health booklet no. On generation the data is checked against the NHIF XSD rules; if a required field is missing, the message names the patient, visit or field.

Monthly report

Monthly draft

The report collects NHIF activities with an NRD code from visits, with reimbursement and co-pay amounts. The "Reporting time (НРД Art. 89)" card compares hours under the time norms with the ceiling — 6 h a day on average for primary care, 8 h for pediatric and surgical care from 1 Oct 2026 — and warns as you get close. If data is incomplete, it stays a draft.

AMB_DENT

An XML file for each dentist

"Download" saves the AMB_DENT file for the selected dentist and month. A file with test NRNs is marked in its name and inside the XML, so it is never submitted by mistake.

Statuses

A status for every month

The report has a status: draft, generated, submitted, accepted or rejected. The last three are recorded manually and are not NHIF confirmation. Once generated, the month cannot be regenerated; contact support if you find an error.

Submits to NHIS

NHIS ambulatory sheet

Operations D001, D003 and D007 (open, supplement, cancel) are submitted to NHIS and get an NRN, with the dentist's QES through DentaFlow Bridge. With several QES devices on one computer, DentaFlow asks once for the certificate and remembers it for that dentist.

In the app

Every month and its status on one screen

Months on the left, the claim on the right: reimbursement and copay totals, reporting time, and every activity with its НРД code.

Why we exist

The monthly NHIF report by hand — from scratch every month.

"Column mismatch." Invalid structure. Re-upload. A lost day of work — because of formatting, not treatment.

Without DentaFlow
  • Manual code lookup against Ordinance №42 PDFs

  • Excel sheet with manual entry — error-prone

  • Rejected XML in the NHIF portal — wrong structure

  • Rework, re-upload, lose a working day

  • No history — you never know which month was submitted

With DentaFlow
  • Activities with an NRD code enter the report from recorded visits

  • Checks against XSD rules identify missing data during generation

  • XML generated in one click, structured per the official XSD

  • A status for each month — draft, generated and manually recorded outcome

  • Separate XML per reporting dentist — test files are clearly marked

Workflow

From the visit. To XML per dentist.

Four steps from the recorded visit to the file you upload in the NHIF portal.

  1. 01
    01 · During the visit

    Record the treatment

    When recording the visit, select the services and the NRD code for each NHIF activity; amounts come from the NRD prices for the visit date. The "NHIF package" counter also counts the fourth activity for insured adults from 1 Nov to 31 Dec 2026.

  2. 02
    02 · One click

    Generate the draft

    Pick the month and click "Generate draft." DentaFlow collects NHIF activities with an NRD code and attempts to build separate XML for each reporting dentist. Activities without an NRD code are listed separately and excluded from the report.

  3. 03
    03 · DentaFlow checks

    Check and XML

    If required data is missing, the message names the patient, the visit or the field. With complete data you see the files per dentist and a "Download" button.

  4. 04
    In the NHIF portal

    You sign and upload

    Each dentist signs their own file with a QES and uploads it in the NHIF portal. The result is marked in DentaFlow; this does not replace the NHIF confirmation.

Coming: sending the file to NHIF straight from DentaFlow, with the dentist's QES via DentaFlow Bridge — it is built and in testing. Until then you upload the file in the NHIF portal. The financial document and the monthly notice stay outside DentaFlow.
04.5 · NHIS scope

The NHIS documents. Submitted live.

Ministry of Health Ordinance № H-6 mandates real-time submission for every clinician — private and NHIF-contracted. DentaFlow builds the documents from the same visit, without a separate form.

AMBULATORY SHEET · D001

The visit's procedures — tooth, surfaces, code, ICD-10 diagnosis — in the NHIS document, with the doctor's QES through DentaFlow Bridge. The patient signs on a tablet, later ("Awaiting patient signature", "No pad" setting) or on paper.

AMEND AND CANCEL · D003 / D007

A change to a submitted sheet goes in as an amendment (D003) — the NRN stays the same. Cancellation (D007) is final.

E-PRESCRIPTION

The prescription is issued from the patient record and signed with the doctor's QES through DentaFlow Bridge. It can be printed and emailed to the patient.

Regulatory framework

Regulatory framework — and current limitations.

Codes, file format and real submission are separate checks. Valid XML does not mean approved payment.

Ordinance №42

403 codes

All 403 procedure codes per Ordinance №42, Ministry of Health, Annex 1a, Chapter 6. Effective Jan 1, 2025 (State Gazette №69, Aug 16, 2024). Verified against the official PDF.

NHIF XSD

XSD format

The XML structure follows the official NHIF XSD schema for dentists, valid for activity from 01.08.2024. Passing the schema check does not mean the activity will be paid.

GDPR EU

EU hosting

Data is stored in the EU (Ireland). The list of subprocessors is public. The AI features (Anthropic) process data outside the EU — details in the AI policy.

Status and history

Statuses

The month keeps its status and files per dentist. Once generated, the report cannot be regenerated. The NHIF outcome is recorded manually; rejected activities and their reasons are not automatically recorded.

NHIS: D001, D003 and D007 are submitted live and get an NRN, signed with a QES through DentaFlow Bridge. When the bridge is out of date, DentaFlow offers the new version to download.
Comparisons

Comparing with another system?

Each vendor has its own page with the date we checked it and a source for every fact.

Frequently asked

Frequently asked questions.

The questions we always get. If yours isn't here, write to us.

Do you support all KSMP codes from Ordinance №42 (Jan 2025)?

Yes — all 403 procedure codes from Ordinance №42, effective Jan 1, 2025 (State Gazette №69/2024), with names checked against the State Gazette text. ICD-10 diagnoses carry the official names from the NHIS nomenclature, and expired CL110 codes are no longer offered. When the next revision lands, the update is in DentaFlow — not on your side.

How does the XML file get to NHIF?

Each dentist signs their XML with a QES and uploads it in the NHIF portal. The result is then marked in DentaFlow. Sending directly via DentaFlow Bridge is in testing.

How does DentaFlow's XML differ from Hipokrat / Medentic?

The file format is set by NHIF. DentaFlow builds the XML from visits and checks required data against the XSD rules. When comparing, ask to see the whole path — from the visit to the file for each dentist.

Does it work for clinics with more than one doctor?

Yes. The report contains a separate AMB_DENT file for each dentist with a UIN and "Reports under the clinic's NHIF contract" ticked (Settings → Team). If a dentist with NHIF visits is not ticked, the "Who reports under the NHIF contract" panel lists them with "Include in the claim"; then click "Generate again".

Does DentaFlow submit the report to NHIF for us?

Not yet. DentaFlow generates the XML file you upload in the NHIF portal — one per contracted dentist. Sending it straight from DentaFlow with the dentist's QES via DentaFlow Bridge is built and in testing; we will switch it on once it works live. The NHIF financial document and the monthly notice stay outside DentaFlow.

Next step

Ready to see the NHIF module in action?

15 minutes with sample data — from a recorded visit to test XML per dentist. We show the checks and what is not yet ready for real reporting. No contract.