One system, three products
Three places got the same Inora and made three products of it: a handbook, a writing assistant and the go-to source for evenings and weekends. What that says about a knowledge system, and why we keep building one.
Written by
Founder and CEO
Essay5 min read
A week ago I wrote that Inora is one product, set up for each organisation: one codebase, one knowledge model, and for each organisation its own sources, its own order, its own answer policy and its own formats (One product, set up for each organisation). That is true of what we build. It is not true of what the organisations did with it. Three places got the same Inora and made three different products of it.
Three products
At Vitala+, Inora became the handbook. 86% of conversations pulled up one of Vitala+’s own documents: a work agreement, a procedure, a form, whom to call. The answer came from its own quality handbook, with the passage one tap away.
In South Limburg, Inora became a writing assistant. In the network, in September 2026, 62% of conversations were writing: the report, the handover, the email, in the care worker’s own words. Among those who used Inora often, it grew from 40% to 59%.
In South-East Brabant, Inora became the go-to source for evenings and weekends. There, 83% of conversations were a clinical question, about professional knowledge or the situation at hand, often when no physician was in the building. Writing was 14%.
One system, three products
Vitala+: its own documents, the handbook86%
South Limburg: writing, the writing assistant62%
South-East Brabant: a clinical question, the go-to source83%
The same Inora, the same codebase, started in the same month. Three products.
Why
Three things explain it, and all three say something about what a knowledge system is.
What an organisation puts in becomes what its people ask for. At Vitala+ the whole quality handbook was in Inora, document by document. There Inora became the handbook, because the handbook was in it. In South Limburg ten organisations built one library of the profession together, and in Brabant the region’s agreements for acute care came first. A knowledge system becomes an organisation’s system through its own layer: its protocols, work agreements and handbook. That is why every implementation of ours starts with the quality handbook.
What a region is shown at the start becomes the product it thinks it has. Brabant began at night, with the question at three in the morning: do I call the physician, and what do I say? That became the product. Among those who used Inora often in Brabant, writing did not grow: 15% of conversations at first, 12% later. In South Limburg it grew in the same group from 40% to 59%, at Vitala+ from 14% to 42%. The start made the difference.
The work that comes back wins. In all three places, the work that recurs on every shift grew. In South Limburg and at Vitala+ it was the report, in Brabant the clinical question of the evening. A knowledge system becomes what the work asks of it every day. Zohaad wrote last week why that is decided in the first three weeks.
One system
Should we then make three products? A handbook, a writing assistant, a product for the night? No. The three are one system, seen from three moments.
The handbook is the organisation’s knowledge, read at the moment of work. The writing assistant is what the work writes back: the report, in the care worker’s own words, under the organisation’s headings. The go-to source is the moment the two meet, when there is no one else. They are the two directions in which knowledge moves in a care organisation, and the place where they meet.
Build only one of the three and you have built a product, and each of the three fails on its own. A handbook no one writes back to goes out of date. A writing assistant without the handbook writes under headings no one has set. A go-to source without either guesses. Only together are they an organisation’s knowledge.
So we keep building one system. Every organisation starts where its need is greatest: one with the handbook, another with the report, a third with the night. We bring the other two team by team, and at the start every team sees all three sides: looking up what the organisation knows, writing what the shift saw, and the question without an answer. What an organisation makes of Inora is up to the organisation. What Inora is remains up to us.
One line in all three products
Of the three, the go-to source for the night comes closest to the line of what software in care may do. A clinical question in the evening, with no physician in the building, is exactly the question where software most easily goes a step too far. So for a question about one client, Inora puts the organisation’s own protocol beside the professional and flags what is missing: on medication, on calling or waiting, and on scores and calculations, each source marked and the decision left with the professional. Inora never suggests what might be wrong with a client and reads no photo of skin or a wound (Where Inora stops). That line is the same in all three products, because it is one system.
Postscript, 2 November 2026
Inora is not a medical device. Inora supports triage: the professional triages, scores and decides. Inora puts the organisation’s own protocol beside the professional, flags what is missing and records the source and version of every answer; it does not diagnose or decide on treatment. Its intended use keeps it outside the medical device rules (The professional decides).