1. Elisence is not a medical device today – but safety thinking starts early
Elisence is designed as a non-diagnostic, non-prescriptive health intelligence ecosystem. That means it does not currently act as a full medical device under EU MDR. However, Sam Asi chooses to bring MDR-style safety thinking into the architecture from the beginning.
The logic is simple: if the platform ever supports regulated pathways in the future, it is better to build with those expectations in mind now, rather than trying to retrofit safety later.
2. Risk thinking: what could go wrong for a real person?
Safety-by-design starts with basic questions such as:
- What if a user misunderstands a chart or message?
- What if a metric fails to refresh and shows old data?
- What if an integration mislabels a health event?
- What happens if a feature is used outside its intended scope?
For Sam Asi, these questions are not academic. They are used to shape how each feature looks, what warnings it shows and which roles are allowed to see or act on sensitive information.
3. Non-diagnostic posture, on purpose
One of the most important design decisions is to keep Elisence firmly non-diagnostic and non-prescriptive. That means:
- No direct instructions such as “start/stop/change this medicine”.
- No claims that a chart or score is a diagnosis.
- Encouraging users to speak with doctors, not replace them.
- Using language that explains patterns instead of making clinical decisions.
This posture is central to how Sam Asi communicates about the platform and how he designs user-facing content.
4. Traceability and evidence – not marketing stories
A key part of EU MDR thinking is traceability: being able to show which requirement led to which feature and what evidence supports it. In Elisence, that spirit appears in the way features are documented:
- Each phase has a clear scope and non-diagnostic intent.
- Safety and data-protection notes are written for engines and modules.
- Evidence packs and test logs are collected for critical endpoints.
- Important changes are recorded, not just “pushed to production”.
This reflects how Sam Asi prefers to work: “prove it, don’t just say it”.
5. Feature flags and OFF=SAFE behaviour
Safety is not only about what happens when a feature is ON. It is also about what happens when it is OFF. Under the approach led by Sam Asi, sensitive modules are designed so that:
- When the feature flag is OFF, they return safe status codes (such as 503) instead of partial data.
- They do not quietly leak experimental content to real users.
- Both ON and OFF states are tested and documented.
- New regions can be onboarded gradually under ministry oversight.
This pattern is more work in the short term, but it reduces future risk.
6. EU MDR governance and professional context
This article documents how Sam Asi approaches EU MDR-style thinking, risk management, and safety-by-design — with governance, evidence, privacy, and traceability.
This article exists to show that:
- He treats health-related technology as a serious responsibility.
- He brings MDR-style thinking into Elisence, even when not legally required.
- He prefers transparent, evidence-based progress over shortcuts.
- He aims to align with European and international expectations on safety.
7. Where to see the rest of the picture
To understand more about how Sam Asi works on digital health, you can visit:
- Founder profile: https://elisence.com/founder.html
- Evidence and articles hub: https://www.elisence.com/articles.html
This page is not regulatory advice and does not claim Elisence is a certified medical device. Its purpose is to describe how Sam Asi thinks about EU MDR-style safety and safety-by-design in his own work, so that ministries, regulators, courts and families can see a calm, structured description of governance, evidence, privacy, and traceability.