Skip to Content

How Resthome by LPLG transforms MR/MRS management in Belgium

From admission to eFact, 5 systems replaced by an Odoo suite — step by step
24 May 2026 by
How Resthome by LPLG transforms MR/MRS management in Belgium
LPLG

Resthome · LPLG · Odoo 19

How Resthome by LPLG transforms MR/MRS management in Belgium

From admission application to the eFact file sent to health insurers, Resthome by LPLG replaces half a dozen scattered tools with a single Odoo suite, designed for the Belgian field. Here is the step-by-step transformation.

Caregiver accompanying a resident in a wheelchair during a walk

An average Belgian nursing home in 2026 juggles 5 to 8 tools: INAMI invoicing software, computerised care records, an Excel sheet for Katz assessments, a paper binder for restraint logs, accounting software, an HR planner, a separate insurer portal for eFact and MyCareNet, sometimes an admissions CRM… Every tool has its login, its exports, its incompatible formats.

The cost of this dispersion is real: 8 to 12 hours per week lost to duplicate admin entry, INAMI invoicing errors (1-3% of flat-fees rejected depending on the facility), lost Katz categories from expired assessments going unnoticed, family complaints about poor communication. And a non-quantifiable but recurring AVIQ risk.

Resthome, developed by LPLG in Wavre (Walloon Brabant), tackles the problem at the root: one single system covering the entire Belgian MR/MRS business, from resident enrolment to monthly invoicing to health insurers.

1. The diagnosis: 5 tools to do what one should

Take a typical case. In an 80-bed MRS in Wallonia today:

FunctionTypical toolManual entry
Administrative resident recordProprietary "legacy" softwareIdentity, insurer, contacts, contract
Katz assessmentsExcel + paper6 ADL + MMSE, copied from the care record
Care recordDedicated nursing software (often Care-X)Care, notes, drugs — copied from the admin record
INAMI / eFact invoicingSeparate insurer softwareFlat-fees, days, codes, copied from Katz and care
Insurability MDAMyCareNet web portalChecked by hand, resident by resident
AccountingBOB50, Sage, or othereFact invoices re-keyed into accounting
Family communicationPhone, paper, sometimes SMSNo trace, no history

Every arrow between these tools is a friction point. And every friction costs caregiver time diverted from bedside to admin.

2. The Resthome promise: one system, one source of truth

Resthome starts from a simple principle: the resident record is the single root. Whatever is entered elsewhere attaches to it, and whatever you need flows from it. No more duplicate entry, no more "you also need to update it in the other tool".

Concrete consequence: when the nurse validates a care act on her tablet at the resident's bedside, that data is immediately available for INAMI invoicing, the care plan, family communication and the director's dashboard. No re-entry.

3. The 9 modules that cover the entire MR/MRS business

Resthome is modular: only the useful pieces are activated. But the whole sketches complete coverage:

4. Concrete case: a resident's journey from first contact to invoicing

To make the transformation tangible, let us follow a fictional applicant — Mrs M., 84, partially dependent.

Step 1: first contact (day 0)

Mrs M.'s son calls the MRS. The secretary opens the Resthome admissions CRM and creates a prospect card in 30 seconds: name, family contact, reason (post-stroke), current situation (home + carer). The card appears in the "First contact" column of the visual kanban.

Step 2: visit (D+3)

The visit is scheduled from the same card. At the end, the director drags the application into "Medical file" and attaches the received documents. The coordinating doctor gets an automatic notification.

Step 3: Katz assessment (D+5)

The head nurse fills in the Katz assessment directly inside Resthome (structured form, automatic category computation). Mrs M. is rated category B. The card moves to "Waitlist" with an availability date.

Step 4: admission (D+15)

On day 15, a room frees up. The application moves to "Admission". In one click, Resthome:

  • Creates the resident (full card, NISS, insurer, family contacts, GP)
  • Creates the stay (entry date, assigned room, bed)
  • Initialises the care record (reference caregiver, category-B care plan)
  • Triggers MDA verification via MyCareNet
  • Provisions the month's INAMI invoicing
Before Resthome: these 5 actions were 5 separate entries in 4 different tools, with desync risk.

Step 5: daily care (D+15 onwards)

The nurse does her rounds with a tablet. At Mrs M.'s bedside, she validates the blood-pressure reading, notes mild oedema, administers the prescribed drugs (scanning the box automatically checks allergy and cross-reactivity with other treatments). All of it feeds the care record, the director's dashboard, and — if billable — the INAMI invoicing.

Step 6: INAMI invoicing (end of month)

The admin director opens the invoicing module. Resthome has already:

  • Computed presence days by resident and Katz category
  • Verified each resident's MDA insurability (potential rejections already flagged)
  • Prepared the compliant 920000 eFact file

One click, and the file is XAdES-signed, sent via GenAsync to WalCareNet. The status of each invoice comes back in real time (931000 ACK or 920999 error). The director sees, at a glance, what is validated, pending or to fix.

Step 7: family communication (ongoing)

Mrs M.'s son logs into the GDPR family portal. He sees: this week's menus, his mother's meal history, MRS news, the reference caregiver's contact. He no longer calls. The admin team gets its day back.

5. Why Odoo rather than a "nursing-home-only" tool?

Fair question. Three substantive reasons:

5.1 Native modularity

Odoo lets you activate only the bricks useful to your MR/MRS. Resthome plugs into the standard Odoo base, which already covers Belgian accounting (PCMN, VAT returns, CODA), HR, purchasing, inventory. No second tool needed for accounting: it is included.

5.2 Open source, no lock-in

Resthome ships under a free licence. The code is auditable. Your data is yours. If tomorrow you want to change provider, you can. No technical captivity, no "per-resident-per-month" pricing that explodes at scale.

5.3 Responsive roadmap

Odoo ships a major version each year (currently Odoo 19). LPLG follows that cadence. When INAMI publishes a new eFact format, when the CIN updates its specs, or when AVIQ changes its inspection criteria, we integrate the changes before the enforcement date.

6. Belgian compliance built in

Belgian requirementResthome coverage
INAMI Katz assessmentFull form, auto-compute, head-nurse + doctor validation
eFact invoicing (920000)Full POST/GET/CONFIRM flow + 931000/920999 parsing
eAgreement (C/Cd insurer agreements)ETEE triple-layer encryption, GenAsync sending, validity tracking
MemberData (MDA)Synchronous and asynchronous modes — CIN accredited
eHealth signatureWS-Security, NIHII certificate, SAML HoK
Medical-data retention30 years, deletion blocked by business rule
Audit trailEvery change traced (who, when, what)
GDPR & AVGRole- and care-sector-based access, logging
NetworksMyCareNet (federal), WalCareNet (Wallonia), IrisCareNet (Brussels)
Belgian accountingPCMN, CODA, VAT returns, SEPA

7. LPLG's role: integrator, not box-shifter

LPLG is a Belgian Odoo integrator based in Wavre. Our trade is not to sell a packaged licence — it is to understand your processes, configure Resthome to fit your way of working, train your teams, and stay present over time.

In practice, a Resthome rollout runs in four phases:

1
Scoping (2-4 days) — Workshops with direction, head nurse, admin team. We map your current processes, the modules needed, the integrations to plan.
2
Configuration & migration (4-8 weeks) — Module configuration, migration of existing data (residents, contracts, care history), tests on pre-production.
3
Training & rollout (2 weeks) — On-site team training, in French and Dutch. Daily support during the first production week.
4
Ongoing support — Application maintenance, FR/NL/EN support, follow-up on INAMI/AVIQ regulatory changes. See our services.

FAQ — Resthome and the MR/MRS transformation

How much does a Resthome rollout cost?

Per-facility pricing (not per user nor per resident), including Odoo.sh EU hosting and LPLG support. The quote depends on size, activated modules and migration complexity. See our pricing or request a quote.

How long until ROI?

ROI is usually achieved in 6-12 months, by removing third-party licences (insurer invoicing, care records, etc.) and time saved on data entry. Typical gain: 5-8 hours per week for the admin team.

Is Resthome accredited for INAMI flows?

Yes. Resthome is accredited by the National Intermutualistic College (CIN) for MDA, eFact and eAgreement services, in synchronous and asynchronous modes, on the WalCareNet network — with the retwalodoo package and a certified NIHII.

What if INAMI or AVIQ change their rules?

Included in LPLG application maintenance. We track INAMI/CIN/AVIQ publications and adapt Resthome before the enforcement date. Your teams have nothing to do.

Can Resthome be rolled out module by module?

Yes. It is even recommended. Many facilities start with the resident record + Katz + eFact, then add the family portal, staff planning and reporting quarter by quarter. The progressive rollout minimises disruption for teams.

Let's see Resthome together for your facility.

A guided 30-minute demo, tailored for your MR, MRS or CSJ. No commitment — just your real questions and our real answers.

Schedule a demo

LPLG — Courbevoie 13 · 1348 Louvain-la-Neuve, Brabant wallon · www.lplg.eu · info@lplg.eu · +32 473 48 81 00

How Resthome by LPLG transforms MR/MRS management in Belgium
LPLG 24 May 2026
Share this post
Our blogs
Archive