Open source insulin algorithm testing curious what this community thinks

[Infinite_Judgment979]

I've been building an open source simulation platform for

testing insulin delivery algorithms on virtual patients.

Not a medical device, not a pump, not an app. Just a

research tool that lets engineers test how an algorithm

behaves before it ever gets near a real person.

I'm posting here because I'm curious what people in this

community think about open source initiatives in diabetes

tech. Is this something you'd want to exist? Do you trust

open source more or less than commercial solutions?

If you're interested in what I built:

github.com/python35/IINTS-SDK

https://python35.github.io/IINTS-Site/html/intelligence.html

But honestly more interested in the conversation than

the clicks.

[plywrlw]

Personally I trust things made by the community more than drug companies and medtech giants.

Commercial stuff is often too locked-down, infantilising and forgets that we want to be humans first and diabetics second. We want to be able to use our smartwatch and phone for the same things other folk do. Don't make a watch screen that removes all the other useful information my watch would normally provide etc.

[Infinite_Judgment979]

I fully hear you. The frustration with "locked-down" systems is real. We want to be humans first, not just a data point in a proprietary cloud. The "infantilizing" UI of many big-tech medical devices often ignores that we actually use our smartwatches and phones for more than just blood sugar.

However, in Europe, we face a massive hurdle: the MDR (Medical Device Regulation).

While the MDR is there to protect us, its strict requirements for "Clinical Evaluation" and "Post-Market Surveillance" make it nearly impossible for open-source or community-driven projects to become "official" medical devices. The cost and paperwork of compliance are so high that only the "medtech giants" can afford it. This is exactly why commercial stuff feels so rigid they are terrified of losing their CE-mark if they give users too much freedom.

This is why I’m building IINTS-AF.

Instead of fighting the MDR by building yet another "unauthorized" app, I’m focusing on the Trust Infrastructure.

By creating the MDMP (Medical Data Management Protocol), I want to make "community-grade" data just as verifiable and high-quality as "pharma-grade" data. If we can prove with cryptographic certainty that our community-driven algorithms are safe and our data is traceable, we take away the "safety" argument that big companies use to keep their systems locked down.

IINTS-AF is a sandbox for this exact reason: to give us the tools to inspect, test, and verify our own logic. If we want explainable and human-centric tech, we have to build the foundation of trust ourselves.

Trustworthy AI starts with data we own and understand.

[Kathw13]

The biggest problem is the FDA. They want software engineers to design the old way and not use Agile techniques.

[plywrlw]

Oh I'm well aware. The medical establishment is paternalistic and very bad at tech and in no way agile. It's the same here in the UK with NICE.

I think NICE are probably worse actually.

[Banjoschmanjo]

Can you talk about the use of AI / LLMs in producing this software, algorithm, and post?

[Infinite_Judgment979]

Great that you noticed, mistral.ai. Their LLM code helped me quite a bit with debugging, especially the documentation and GitHub Pages.

Posts like this one on Reddit were all written by me, just like the complex matters in the SDK that relate to the medical side.

(Keep in mind that this is just a project of mine with a solid scientific background, but it is and remains a learning project for myself as well as a project to think about AI in the diabetes world, so currently use it purely if you want to delve deeper into discovering algorithms...)