Software-Engineering on Oliseus Blog

Doseframe: Making Perfusor Calculations Easier to Check

simon.bernbeck@gmail.com (Simon Bernbeck) — Mon, 05 Oct 2026 00:00:00 +0000

A syringe pump delivers medication continuously. Preparing one can involve a prescription, a stock solution, a dilution, a final concentration and a pump rate. Each value has a unit. A calculation may be short on paper, yet the handover between prescribing, preparing and setting the pump gives mistakes several places to enter.

Doseframe is a project I am developing during my computer science master’s studies. The idea came from conversations with physicians in neonatal care about perfusor preparation and the work around it. Their feedback has changed the design: the handover of a spoken prescription matters, clinicians need to see the entered dose clearly, and the staff who prepare syringes must still test whether the proposed workflow fits their practice. The project is currently a design and prototype, not a clinical calculator ready for patient care.

PrivDev: What a Code Scanner Can Tell Us About Privacy

simon.bernbeck@gmail.com (Simon Bernbeck) — Mon, 05 Oct 2026 00:00:00 +0000

A developer can search a codebase for personal data and still miss the question that matters: what should the team do with the finding? A scanner may report an email address or a storage pattern. It cannot see the full purpose of processing, the people involved, every technical safeguard, or the organisation’s legal decisions. PrivDev began with that gap between a technical observation and a responsible privacy review.

PrivDev is my research project at PUC-Rio’s AISE Laboratory. Its working idea is a security-to-privacy bridge: preserve what a scanner actually observed, connect it to a shared vocabulary, and make the reasoning available for inspection. I want developers to receive a useful starting point while leaving decisions that require context with the people who have it.

PrivDev: Turning Static-Analysis Findings into Privacy Knowledge

simon.bernbeck@gmail.com (Simon Bernbeck) — Wed, 29 Jul 2026 00:00:00 +0000

The first PrivDev study connects data-type labels from a code scanner to a privacy vocabulary. That sounds straightforward until a label is ambiguous, the vocabulary has no close match, or a graph asserts more than the scanner could know. This article records what the first implementation accomplished and what later review changed. For the wider research programme, see the PrivDev introduction.

From a scanner label to a category
#

Bearer CLI provides the 122 input data-type labels used in this study. The pipeline relates them to personal-data categories in the Data Privacy Vocabulary’s PD extension. The output is an RDF/Turtle graph that can be queried with SPARQL. It records a proposed interpretation of each scanner label, not a description of every real processing activity in which that label might occur.

Software-Engineering on Oliseus Blog

Doseframe: Making Perfusor Calculations Easier to Check

PrivDev: What a Code Scanner Can Tell Us About Privacy

PrivDev: Turning Static-Analysis Findings into Privacy Knowledge

From a scanner label to a category #

From a scanner label to a category
#