Care home software in Belgium: managing MR and MRS facilities without fragmentation, from the resident record to INAMI billing
How a Belgian-native suite, built on Odoo, unifies the resident record, Katz assessments and compliance (MDA, eAgreement, INAMI, GDPR) into a single source of truth
Recevoir le guideRunning a care home in Belgium means arbitrating every day between quality of care and an administrative burden that keeps growing. Between INAMI requirements, AVIQ inspections or GDPR obligations and the mechanics of the health insurance funds, vital information too often ends up scattered: Excel spreadsheets, paper files, disconnected external portals. This fragmentation has a real, measurable cost — double data entry, billing rejections, payment delays, manual tracking of settlement statements, and hours lost reconstructing what should have been available in a single click. This white paper is aimed at the directors of MR, MRS and short-stay facilities who want to regain control. It presents Resthome, the software suite developed by LPLG, a Belgian Odoo integrator based in Louvain-la-Neuve, in Walloon Brabant, in direct collaboration with on-the-ground facilities. The guiding principle is simple: a single system, a single source of truth, with no double data entry — from the resident record to INAMI billing, by way of care planning, Katz assessments and communication with families. Built on Odoo (open source) and hosted in Europe with encryption, the suite was designed to meet the Belgian requirements of the sector. The pages that follow detail, without overselling, what the solution actually does, how it is accredited, and why the LPLG approach — local multilingual support, custom development and the absence of vendor lock-in — changes the game for a director keen to control both budget and compliance.
The challenge facing Belgian care homes and the hidden cost of fragmentation
Running a care home (MR), a nursing care home (MRS) or a short-stay centre (CSJ) in Belgium means managing day to day an organisation where quality of care and administrative rigour are inseparable. Each resident has a record that combines medical data, health insurance fund status, dependency assessments and billing commitments. Yet in many facilities this information does not live in a single place. It is scattered across Excel sheets for tracking settlement statements, paper binders for assessments, and several external portals for communicating with the health insurance funds. This fragmentation is not a technical detail: it constitutes a real burden that weighs, day after day, on your care and administrative teams.
The symptoms of this dispersion are concrete. Double data entry is the first of them: the same piece of data — an admission, a change of dependency category, an insurability update — is re-entered several times into systems that do not talk to one another. Then comes the chain of rejections and payment delays: an INAMI billing submission sent without the resident's insurability having been confirmed ends in a rejection, hence a manual correction, hence cash flow left waiting. The tracking of settlement statements and acknowledgements of receipt is then done by hand, in spreadsheets that no one truly masters. To this is added the calculation of the Katz scale, which determines each resident's INAMI flat-rate funding: six activities of daily living and two psychological criteria, scored from 1 to 4, leading to categories O, A, B, C, Cd, D or Ccoma. Managed on paper, this cycle exposes you to a forgotten renewal and therefore to a loss of funding.
The most visible burden remains that of families. Take a facility with 60 residents: at the rate of one to two calls per family per week — to find out what was eaten, how the day went, when the next visit takes place — you reach on the order of 15 to 20 hours per week devoted to the telephone alone. This time is taken away from care and from administration. These are not superfluous calls: they are legitimately worried families, to whom staff provide information that already exists somewhere in the facility, but that is not accessible other than through the voice of a member of staff.
Beyond the time lost, this dispersion weakens your compliance. The requirements of INAMI, of AVIQ in Wallonia and in Brussels presuppose flawless traceability: who accessed which data, when, and with what modification. The GDPR framework, combined with the obligations of the care sector, presupposes an immutable audit trail kept for 7 years and a retention of care data that can reach 30 years. When information is fragmented across Excel, paper and portals, this traceability becomes illusory: an AVIQ audit is then prepared in a rush, reconstructing after the fact what should have been logged from the outset. Each parallel source is a potential breach, a place where a piece of sensitive data escapes access control and where a regulatory requirement is no longer easily demonstrable.
The thesis of this book is simple. The answer to this friction is not to add yet another piece of software to an already cluttered landscape. It is, on the contrary, to reduce the number of systems: to move towards a single source of truth, where the resident record, care planning, Katz assessments, insurability verification, INAMI billing and communication with families share the same base, with no double data entry. This is precisely the approach of a care home software designed for the Belgian reality of MR, MRS and CSJ facilities — not one more tool, but the foundation that drives back fragmentation. The following chapters detail how.
- Double data entry eliminated: an admission, a change of dependency category or an insurability update entered just once, shared by every module
- Billing safeguard: a billing period cannot be sent as long as insurability (MDA) is not confirmed for each resident — fewer rejections, controlled cash flow
- Katz cycle under control: 6 ADLs + 2 psychological criteria, scoring from 1 to 4, categories O to Ccoma calculated automatically, with renewal alerts 60 and 30 days before expiry
- Lighter burden on families: a 24/7 portal giving access to menus and meal history, where the telephone alone can represent 15 to 20 hours per week in a facility of 60 residents
- Demonstrable compliance: immutable 7-year audit trail, care data kept for 30 years, encrypted European hosting — designed to meet AVIQ/INAMI and GDPR requirements
- End of dispersion: replacing Excel, paper and external portals with a single base, where every piece of sensitive data remains under access control
The resident record, foundation of the single source of truth
In a care home, everything begins with and comes back to the resident record. It is what carries the person's identity, their level of dependency, their health insurance fund coverage, their family contacts and their end-of-life wishes. Yet in most facilities this information lives scattered across Excel files, paper binders and several external portals: the same data is entered three or four times, at different moments, by different people, with the discrepancies and omissions that this entails. Resthome reverses this logic. The resident record is the single point of entry: information is entered once, as close as possible to the field, then it feeds care planning, Katz assessments, insurability verification and INAMI billing. This is the concrete meaning of the promise of "a single source of truth, with no double data entry".
The resident's identity is centralised in a structured way: national number (NISS), health insurance fund, BIM status, family contacts, attending physician, DNR status and advance directives appear in a single record, accessible according to each person's rights. To make this data entry more reliable and to save time, Resthome reads the Belgian electronic identity card (eID): the system creates or updates the record automatically from the official data on the card, which eliminates typos on a NISS or a name and speeds up the welcoming of a newcomer. This same identity, verified once, then serves everywhere in the suite without re-entry.
The admission itself is treated as a genuine process, not as an isolated form. Resthome offers a six-stage admission pipeline, presented in a kanban view, that management follows at a glance: first contact, visit scheduled, visit completed, file complete, admitted, then refused or withdrawn. Each file visibly moves from one column to the next, which gives the director an immediate reading of the upcoming intake book and the places to be filled. When an application reaches the admission stage, a guided admission assistant takes over and proposes the assignment of a room based on the capacity actually available — not on a theoretical list, but on the effective occupancy at that moment.
The management of rooms and stays rests on this same demand for reality. The facility is modelled by sectors, floors and buildings, with real-time capacity: you see what is free, occupied or in transfer. A room change is carried out in a single click, and the history of stays is kept — useful for regulatory traceability as well as for answering a family's or an auditor's question. This traceability is part of the suite's GDPR framework, which provides an automatic document space per resident, an immutable audit trail kept for 7 years and access rights organised by sector, so that a caregiver only sees the residents in their charge.
The real difference for a Belgian facility lies in the preloaded business integrations. The resident record embeds the Katz scale and the INAMI daily flat-rate funding, the MDA module for insurability verification, eAgreement Light, and the codes of the health insurance fund federations already loaded. Above all, the events of the journey automatically trigger the expected eAgreement procedures: admission, extension, change of category, discharge and short stay. The director no longer has to wonder which request to send or when: the record knows, because the information was entered there once and then serves everything. Resthome is designed to meet AVIQ, INAMI and GDPR requirements, and relies on eHealth connectors approved by the CIN for the MDA (approval signed on 8 May 2026) and for eAgreement Light (WalCareNet, 17 June 2026).
- Identity entered just once: NISS, health insurance fund, BIM status, family contacts, attending physician, DNR status and advance directives in a single record, updated automatically by reading the eID.
- 6-stage admission pipeline (first contact, visit scheduled, visit completed, file complete, admitted, refused/withdrawn) tracked in kanban, with a guided assistant that assigns a room according to the capacity actually available.
- Management of stays by sectors, floors and buildings: real-time capacity, one-click transfers, history of every stay kept.
- Preloaded Belgian integrations: Katz and INAMI daily flat-rate funding, MDA module, eAgreement Light, health insurance fund federation codes.
- Automatic eAgreement triggers on the events of the journey: admission, extension, change of category, discharge and short stay.
- Integrated GDPR framework: automatic document file per resident, immutable 7-year audit trail, access rights by sector — all without an external portal.
Care and assessments: Katz, clinical scales and individualised planning
At the heart of your facility is care. And at the heart of the funding of that care is a grid: the Katz scale. In an MRS as in an MR, it is what determines each resident's dependency category and, consequently, the daily flat-rate funding paid by INAMI. An imprecise score, a forgotten renewal or a poorly formatted submission, and your home's cash flow wavers. Resthome was designed to make these two requirements converge — clinical quality and administrative rigour — into a single system, with no double data entry. The care planning module structures all of the daily work around a simple cycle that teams can read easily: "Plan, Administer, Document, Track". Every care action enters this mechanism, from its prescription through to its traceability.
Concretely, planning covers eleven types of care endowed with automatic recurrence: vital signs, wound care, medication, hygiene, mobility, nutrition, physician visit, specialist visit, therapies, examinations and miscellaneous care. No more need to manually reschedule every dressing or every set of vital signs. On the medication side, the system relies on the SAM database (Source Authentique des Médicaments) and exercises a three-level allergy check — critical, moderate and cross-reaction — so that the alert is issued before the error, not after. At the resident's bedside, administration is optimised for tablet, with five tracking statuses that make visible, in real time, what has been given, refused or postponed. Vital signs are tracked with out-of-range alerts and trend curves, so that a slow deterioration can be read on a graph rather than lost across scattered sheets. Finally, care notes are structured into eleven categories, which transforms a fragile oral handover into a usable written record.
It is also at this level that the individualised care plan is built. For each resident, Resthome makes it possible to identify the major risks — falls, pressure sores, undernutrition, dehydration —, to set care objectives and to associate a suitable diet. You thus move from reactive monitoring to a documented preventive approach, the very one that your head nurse and the inspectors expect. This preventive logic is not isolated: it is articulated directly with the clinical assessments that feed it, starting with Katz.
The Katz assessment is the pivot. Resthome manages its complete cycle. The grid rests on six activities of daily living (ADLs) — washing, dressing, transfers and movement, going to the toilet, continence and eating — to which are added two psychological criteria: orientation in time and orientation in space. Each item is scored from 1 (autonomous) to 4 (totally dependent). From these scores, the system automatically calculates the dependency category — O, A, B, C, Cd, D or Ccoma —, reducing the risk of a classification error that would directly affect the INAMI flat-rate funding. The whole follows a workflow validated in four stages: Draft, Confirmation, then Validation by the head nurse or the physician, and finally Submission to the health insurance fund via eAgreement. This separation of roles is not a bureaucratic detail: it is your guarantee of traceability, in a solution designed to meet the requirements of AVIQ and of INAMI.
Where many facilities lose funding is on deadlines. An expired Katz assessment means suspended funding. Resthome triggers early renewal alerts at three levels: 60 days before expiry, then at 30 days (urgent), and after expiry (critical, with a pre-filled assessment to speed up the regularisation). Beyond Katz, the module provides five complementary clinical scales that objectify the risks identified in the care plan: the MMSE for cognition (out of 30), the Braden scale for pressure sore risk (out of 23), the MNA for nutrition (out of 14), the OHAT for oral health (out of 16) and the Tinetti for balance and fall risk (out of 28). You thus have a standardised clinical language, readable by all your teams and defensible in the event of an audit, knowing that care data is kept for 30 years and the GDPR audit trail for 7 years.
- Eleven types of care with automatic recurrence and notes structured into eleven categories: the planning of the daily routine ceases to be re-entered by hand and becomes a usable framework.
- Native medication safety: integration of the SAM database and a three-level allergy check (critical, moderate, cross-reaction), with bedside administration on tablet and five tracking statuses.
- Preventive care plan: risks of falls, pressure sores, undernutrition and dehydration identified, objectives set and a suitable diet for each resident.
- Automatic calculation of the Katz category (O, A, B, C, Cd, D, Ccoma) from the 6 ADLs and 2 psychological criteria scored from 1 to 4 — fewer classification errors on the INAMI flat-rate funding.
- Katz workflow validated in four stages (Draft, Confirmation, Validation by head nurse or physician, Submission to the health insurance fund via eAgreement): traceability designed to meet AVIQ/INAMI requirements.
- Five complementary clinical scales integrated (MMSE /30, Braden /23, MNA /14, OHAT /16, Tinetti /28) to objectify risks and standardise monitoring.
Native Belgian compliance: eFact, MDA, eAgreement, INAMI and GDPR
In Belgium, the billing of a care home does not come down to issuing invoices: it requires dialogue, in precise regulatory formats, with the health insurance funds and INAMI. This is precisely what Resthome's eFact module handles. From the INAMI daily flat-rate funding calculated on the basis of the Katz assessments, the system automatically generates the billing batches grouped by health insurance fund, complying with the 920000 regulatory message specific to MR and MRS facilities. Each submission is electronically signed (XAdES signature) and transmitted via the GenAsync mechanism; acknowledgements of receipt are tracked, and the returns from the health insurance funds — settlement statements and rejections — are decoded automatically thanks to the parsing of the 931000 and 920999 messages. Concretely, an accepted settlement statement, a rejection or a credit note request no longer translates into a manual re-entry in an external portal: everything flows back into the same tool, where the resident's record is already kept up to date. For a director, this aims at fewer rejections, better-controlled cash flow and the end of manual tracking of settlement statements on a spreadsheet.
The insurability module (MDA, Member Data Administration) constitutes the most important business lock in the chain. It queries each resident's health insurance fund to verify their coverage, in synchronous mode (real-time response) or asynchronous mode (batch processing), and automatically updates the BIM status (beneficiary of increased reimbursement), the CT1/CT2 health insurance fund codes, the member number and the status date. The rule is unambiguous and appears in the product: "a billing period cannot be sent as long as insurability is not confirmed for each resident". This safeguard mechanically avoids one of the main causes of rejections — billing a resident whose situation with their health insurance fund is not in order. Verification can be done individually or in batch, with a scheduled monthly refresh, a targeted follow-up of failures only and reinstatement alerts. Connectivity covers the three networks: MyCareNet at the federal level, WalCareNet in Wallonia and IrisCareNet in Brussels, for MR, MRS and short-stay centres. Within this scope, LPLG is CIN-approved (Collège Intermutualiste National) for the MDA, in synchronous and asynchronous modes, approval signed on 8 May 2026.
The eAgreement Light module addresses a distinct need, which it is important not to confuse with the MDA. Where the MDA verifies whether a resident is in order with their health insurance fund, eAgreement Light manages the request for prior agreement itself — that agreement on which the financial intervention of the health insurance fund depends and which historically passed through paper mail. From the resident record, the request leaves in a single click, in the form of a timestamped PDF sent securely via WalCareNet or IrisCareNet, with no connection to an external portal. The status (pending, approved, refused) and the validity dates are tracked and archived digitally, and the whole integrates directly with eFact. It is necessary, however, to be precise about the state of maturity: deployment is carried out in phases. Phase 1, the current one, digitises the sending of the request, the health insurance fund's return remaining on paper; phase 2, planned for January 2027, aims at the complete digitisation of the return. On this module, LPLG is CIN-approved on WalCareNet, approval dated 17 June 2026, with the support of AViQ. These two approvals — MDA and eAgreement Light — are substantiated and dated facts; on the other hand, LPLG is not presented as listed or approved on the public MyCareNet list, a distinction that a director has every interest in requiring of any supplier.
The GDPR dimension is not a decorative argument: it is a heavy legal requirement in a sector that handles health data. Resthome logs all accesses and modifications of sensitive data — who, timestamp, before/after values, IP address — in an immutable audit trail kept for 7 years, with an automatic monthly clean-up. Care data, for its part, is subject to a 30-year retention and is non-deletable, in accordance with the obligations applicable to medical records. Hosting is European and encrypted, access rights are granular (12 hierarchical security groups, 8 categories of data classified by sensitivity), and the families portal exposes no medical data. Across this entire chain, the honest formulation is not "100% compliant": Resthome is designed to meet the requirements of AViQ, of INAMI and of the GDPR. Real compliance always depends on the facility's configuration and on regulatory developments — hence the value of the INAMI/AViQ compliance monitoring integrated into the maintenance service.
- eFact: batches generated automatically by health insurance fund in the 920000 regulatory format, XAdES signature, GenAsync submission, automatic parsing of 931000/920999 returns, management of settlement statements, rejections and credit notes without re-entry
- MDA: synchronous and asynchronous modes, automatic update of the BIM status, the CT1/CT2 codes, the member number and the status date, with a monthly refresh and follow-up of failures only
- Decisive safeguard: no billing period can be sent as long as insurability is not confirmed for each resident — one of the main causes of rejections is blocked at the source
- eAgreement Light: paperless sending of the agreement request (timestamped PDF via WalCareNet/IrisCareNet), status tracking and validity dates, direct integration with eFact; phase 1 active, phase 2 (digitised return) planned for January 2027
- Regional connectivity: MyCareNet (federal), WalCareNet (Wallonia) and IrisCareNet (Brussels) for MR, MRS and short stay
- GDPR: immutable 7-year audit trail (who, timestamp, before/after, IP), care data kept for 30 years and non-deletable, encrypted EU hosting, 12 security groups and 8 categories of data by sensitivity
The operational day-to-day: meals, staff scheduling and communication with families
A care home does not come down to the care record and INAMI billing. It lives to the rhythm of the meals served each day, the team schedules to be finalised each week and the families who want to know how their loved one is doing. Resthome is designed to cover this operational day-to-day as well, in the same single base as the rest of the suite: the same source of truth feeds the resident record, the Katz assessment, billing and, here, the kitchen, scheduling management and the families portal. This is precisely the suite's anti-fragmentation argument: replacing the scattering across spreadsheets, paper and external portals with a single system, with no double data entry.
On the meals side, the module manages five types of meals and diet plans, with a built-in safety logic rather than one left to individual vigilance. Nutritional calculation relies on the CIQUAL 2025 reference database, which covers 3,484 foods, and returns for each dish the calories, the proteins, the carbohydrates and sugars, the fats and the salt. Common diets are supported — salt-free, sugar-free, vegetarian, halal, gluten-free, modified texture — with a suggestion based on the resident's diagnoses, which reduces the risk of omission when composing the menu. The most structuring point for a director is the safeguard: a dish containing a serious allergen quite simply cannot be marked "served". It is not an alert that can be ignored, it is a block, in the same spirit as the billing safeguard that prevents sending a period as long as insurability is not confirmed for each resident.
The kitchen's work follows a simple four-stage sequence: building the menu, confirming (with the surfacing of dietary alerts), distributing via tablet by sector, then analysing on a real-time kitchen dashboard. Distribution by sector aims to limit tray errors and gives a record of what was actually served, where and to whom — information that then feeds, without re-entry, the history that families can consult.
Staff scheduling responds to a requirement that is both HR-related and regulatory. The suite distinguishes 14 functions distributed across 5 families — Care, Paramedical, Support, Administration and Management — which makes it possible to assign each person according to their profession. Assignment is done by sector, with a native confidentiality rule: caregivers only see the residents of their sectors, whereas head nurses and physicians have an overall view. For accredited care staff, the 11-digit INAMI number is validated at entry, which secures consistency with billing. The module also manages qualifications and diplomas, schedule preferences and availability declarations, a maximum number of hours set by default at 38 hours per week but adjustable, replacements and differentiated rights by role. The whole fits within the suite's compliance framework — designed to meet INAMI requirements, the AVIQ audit and the GDPR — with an immutable audit trail kept for 7 years and care data kept for 30 years.
Communication with families, finally, aims to lighten a very real burden. The suite quantifies the example: for 60 residents with one to two calls per family per week, it is 15 to 20 hours of telephone per week that weigh on the teams. The families portal, accessible 24/7, displays the menus of the day and of the week, and gives authorised families a 30-day meal history with the consumption percentage and the place of service. The point of vigilance that every director must be able to guarantee is here held by the architecture: no medical data is exposed. Medication, pathologies and care notes are excluded from the portal. Accounts are controlled by the administrator, access is restricted by role, and each consultation leaves a trace in the audit trail kept for 7 years. Families are informed without ever opening the medical record.
- Non-circumventable allergen safety: a dish containing a serious allergen cannot be marked "served" — a block, not a mere alert.
- Nutrition documented on the CIQUAL 2025 database (3,484 foods): calories, proteins, carbohydrates and sugars, fats and salt calculated for each dish.
- Diets supported (salt-free, sugar-free, vegetarian, halal, gluten-free, modified texture), with a suggestion based on diagnoses and a build, confirm, distribute, analyse workflow.
- Scheduling structured across 14 functions in 5 families, assignment by sector (caregivers only see their residents; head nurses and physicians see everything) and 11-digit INAMI number validated at entry.
- Maximum of 38 hours/week by default and adjustable, management of qualifications, schedule preferences, replacements and rights by role.
- Families portal 24/7: menus of the day and of the week, 30-day meal history, consumption percentage — and the equivalent of 15 to 20 hours of telephone per week targeted as a burden to lighten for 60 residents.
Management, data security and the LPLG/Odoo approach
At the end of this journey, one thing becomes obvious for the director: the value of a care home software is not measured by its list of features, but by the peace of mind it provides on the day of an inspection, a billing dispute or a data access request. This is precisely where management and security take on their full meaning. Resthome's dashboard and reporting rest on three pillars that respond directly to the obligations of a Belgian facility. First pillar, a GDPR audit trail that logs each access and each modification of sensitive data — who consulted or modified what, at what timestamp, with the before and after values and the IP address — kept immutably for 7 years, with an automatic monthly clean-up. Second pillar, document management that automatically creates a space per resident, classified into three categories: Medical, Administrative and Billing. Third pillar, granular access rights organised into 12 hierarchical security groups, so that a caregiver only sees the residents of their sectors whereas a head nurse or a physician has a complete view.
This architecture relies on a clear retention policy calibrated to the care sector: 7 years for the immutable logs, and 30 years for care data, which cannot be deleted. Information is moreover distributed across 8 categories according to its level of sensitivity, which makes it possible to apply the right level of protection to each piece of data rather than a uniform treatment. Beyond compliance, management becomes a concrete steering tool: real-time occupancy monitoring and AVIQ-oriented indicators give the director a snapshot of their facility without re-entry or a parallel spreadsheet. Business safeguards reinforce this reliability day to day: a billing period cannot be sent as long as insurability is not confirmed for each resident, and a dish containing a serious allergen cannot be marked "served". Compliance is no longer a box to tick after the fact; it is integrated into the business action itself.
The strength of this approach lies in the fact that each role has the tool suited to its responsibility, on one and the same source of truth. The director manages from a real-time dashboard — financial monitoring, compliance deadlines, growth planning and automated reporting for the authorities and the board. The head nurse has a readable schedule, complete traceability with history, the management of absences and replacements, and integrated Katz assessments with their renewal alerts (60 days before expiry, then 30 days as urgent). The administration, finally, sees its billing work considerably lightened: eFact and health insurance funds, centralised files and automated bank reconciliation, without the double data entry that eats away at the teams' time. Let us recall that Resthome manages the complete Katz cycle — the 6 activities of daily living and the 2 psychological criteria, scored from 1 to 4, up to the categories O, A, B, C, Cd, D or Ccoma — and relies on real references such as the 11 types of care, the 5 complementary clinical scales (MMSE, Braden, MNA, OHAT, Tinetti) or the CIQUAL 2025 database and its 3,484 foods for nutrition.
There remains the decisive question: to whom to entrust all of this. LPLG is a Belgian Odoo integrator, founded by Louis-Philippe Lalou and based in Louvain-la-Neuve, in Walloon Brabant, with an assumed footing in the care sector. The Resthome suite was not designed in a laboratory: it was co-built in the field, in direct collaboration with Belgian facilities — among the partnerships cited, Les Jardins de Scailmont and SA Cabau. On the regulatory front, one must be precise: LPLG is accredited by the CIN (Collège Intermutualiste National) for the MDA, in synchronous and asynchronous modes, accreditation signed on 8 May 2026, as well as for eAgreement Light on WalCareNet, dated 17 June 2026. The suite is designed to meet AVIQ, INAMI and GDPR requirements, with encrypted European hosting. On the operational front, the commitment is local and transparent: FR, NL and EN support with a dedicated contact and a hotline from 9 a.m. to 6 p.m. on weekdays, email response within 24 hours, a Resthome.sh hosting platform with a 99.5% SLA, annual Odoo upgrades and compliance monitoring, and custom development whose modules are versioned separately with a 90-day warranty.
This is where the real difference plays out for a director: buying software, or choosing a lasting Belgian partner. Because Resthome is built on Odoo open source, the facility escapes vendor lock-in and benefits from per-facility pricing rather than per-headquarters — in other words, its tool does not hold it hostage and grows with it. Where a classic software vendor sells a licence and a support number abroad, LPLG offers a contract, a team and a point of contact, with an assumed roadmap: Phase 2, announced for January 2027, provides for the complete digitisation of the eAgreement return. For a care home, this choice amounts to leaning on a player that speaks the language of the field, knows the Belgian regulatory formats and remains reachable when a settlement statement is rejected or an inspection approaches. It is less a purchase than a long-term partnership.
- Immutable GDPR audit trail logging each access and modification (who, when, before/after values, IP), kept for 7 years with an automatic monthly clean-up
- Retention calibrated for care: 7 years for the immutable logs, 30 years for non-deletable care data, and 8 categories of data according to their sensitivity
- 12 hierarchical security groups and automatic document management per resident in three categories (Medical, Administrative, Billing)
- A tool per role: real-time dashboard for the director, scheduling and traceability for the head nurse, simplified billing for the administration — on a single source of truth
- Dated CIN accreditations: MDA (synchronous and asynchronous) signed on 8 May 2026, eAgreement Light on WalCareNet on 17 June 2026; designed to meet AVIQ, INAMI and GDPR requirements
- Belgian partner in Louvain-la-Neuve, built on Odoo open source (no vendor lock-in, per-facility pricing), FR/NL/EN support, Resthome.sh hosting with a 99.5% SLA and custom development guaranteed for 90 days
Checklist: is your facility ready to break out of fragmentation?
- Map your current sources of truth: how many times is the same resident information (NISS, health insurance fund, BIM status, Katz category) entered in Excel, on paper and in separate external portals?
- Measure your billing friction: track over a quarter the eFact rejection rate, the payment delays of the health insurance funds and the time spent on manual tracking of settlement statements.
- Check your Katz cycle: do you have early alerts (60 and 30 days) before expiry, and a validation workflow tracked through to submission to the health insurance fund via eAgreement?
- Check your business safeguards: can you technically prevent the sending of a billing submission without confirmed MDA insurability, and the serving of a meal containing a serious allergen?
- Audit your GDPR compliance: do you have an immutable audit trail of accesses to sensitive data, controlled retention (7 years logs, 30 years care data) and encrypted EU hosting?
- Assess the families burden: estimate the weekly hours devoted to repetitive calls and the potential of a 24/7 portal without exposure of medical data.
- Question your supplier dependency: does your current solution rest on an open source foundation without vendor lock-in, with multilingual local Belgian support and a dedicated contact?
Fragmentation is not an inevitability of the sector: it is the symptom of tools that were never designed together. By bringing together the resident record, care, Katz assessments, INAMI billing and communication with families into a single source of truth, Resthome eliminates double data entry at the root and gives time back to the teams — from the caregiver to the director. The suite was designed to meet Belgian requirements (INAMI, AVIQ, GDPR) and relies on real CIN accreditations for the MDA and eAgreement Light, official reference databases (SAM, CIQUAL 2025) and business safeguards that protect both cash flow and the resident. Built on Odoo, hosted in Europe and supported by a Belgian team in Louvain-la-Neuve, it offers what few solutions can claim: the robustness of an open standard, the expertise of a local partner and the absence of vendor lock-in. For a director of an MR, MRS or short-stay centre, the choice is no longer between caring and administering: it is to do both better, with a single system.