RegMon, hands on: the public demo
RegMon can now be looked at before you talk to us. At regmon.rh-advisory.de the dashboard runs as it does at a customer’s site: the three standard sources of German healthcare IT, refreshed daily from our reference instance, plus a button that explains every element. This note says what the demo shows, what it deliberately is not, and why we prefer real data to a drawn mockup. The demo’s interface is in German, like the sources it watches; the explanations are available in English.
What the demo shows
The demo is not a replica. It is the same page that runs in an installation, with the same stylesheet and the same script. Only the data comes from files instead of the database: the feed of G-BA, Gematik and KBV for the last 180 days, as the aggregator prepared it last night. Every event carries source, date, subject areas and deadlines, plus the short summary of the local language model, labelled as AI text.
What a customer gets beyond that is visible and available in the full version: classification by their own experts, deep analysis of the linked documents, the chained audit trail, the coverage book, custom sources, administration. A click on any of them explains what is behind it instead of leading nowhere.
Explain instead of guess
The red Erklären button at the top marks every element of the interface. A hover or a tap shows a card: what the element does, whether it belongs to the core or to a module, and what the module includes. Neu in … lists the changes of the current release with a jump to the element concerned. Next to the standard sources sit greyed-out tiles for custom sources: professional societies, state authorities, standards portals. They are ordered as plugins and fall under the same capture guarantee as the standard sources.
The texts of the cards live next to the code, not in an agency deck. They are generated from the same catalogue that delimits core and modules in the product. A release without an explanation of its changes is a build error for us. That keeps the demo in step with the product.
Why real data instead of a mockup
We considered whether a drawn mockup with tooltips would be the better way. The answer was no, for three reasons. A mockup shows invented data; last night’s feed from an authority shows what the tool can do. A mockup is out of date after two releases; the demo is regenerated from the reference instance every morning. And a mockup cannot be checked against the product; the demo breaks in our test suite as soon as the dashboard changes at a point the demo relies on.
What the demo is not
Not a reachable instance and not an API host, but a static export. There is no account, no cookies, no tracking. User names from the reference instance do not appear, customer-specific sources never get in; a check before every publication refuses the push if it finds anything private. The page is hosted on GitHub Pages, the export is replaced daily.
What comes next
If you would like to see what coverage and evidence would look like for your own sources: intro call, 30 minutes, bookable online. The product page describes core and modules. And the demo itself: straight to the explanation of coverage.