What's new in MoniDoseQMS: team chat, EU MDR classification, expert and notified-body collaboration, and a stronger security baseline

This month we added a way for your team to talk inside the platform, opened up our EU MDR classification tool, and completed a round of security work. This post covers each one in plain terms.

Team chat (rolling out)

Quality work involves a lot of quick questions. Team chat keeps them next to the records they are about, instead of in a separate app.

• A company-wide channel, topic channels, group chats and direct messages
• Rich text, emoji reactions, images and files. Files are virus-scanned like every other upload
• @mentions that notify the person you mention
• Share a record or a document from the libraries as a link card. The card respects each viewer's access rights
• Role tags next to names, so you can see who is who
• A chat button at the bottom right of every page, and "Team chat" in the side menu
• Each company sees only its own conversations

One note on scope. Chat is team communication. It is not a controlled QMS record. Decisions are recorded in the relevant module, not in the chat.

Coming next: experts and notified bodies

Next, we plan to add conversations with your external experts and your notified body, inside their existing engagement. Only the people in that engagement will be able to see them.

EU MDR device classification is now public

"Check your device class" now covers all 22 rules of MDR Annex VIII. For each rule, it shows the reason behind it. It is guidance only. The manufacturer remains responsible for the classification (MDR Article 51). The quick wizard remains available for IVDR and FDA.

Security work completed in October 2026

• Login is protected against automated bots
• Administrator accounts use two-step login. Two-step login for all users is being introduced
• Backups are encrypted so that the hosting server itself cannot read them. The keys are held offline
• Server access is restricted to company networks
• Scanners are blocked automatically
• Our e-mail domain is protected against spoofing (SPF and DMARC)
• Code and dependencies are scanned continuously
• Customer data separation is enforced in the database for every table that holds customer data

We are also commissioning an independent penetration test, planned for early 2027. We will say more when it is done. For the full picture, see our security page.