Unmet needs

Today's neurosurgical operating suites are filled with technological advances - making surgery safe that was deemed too risky until recently.

Yet, the required devices often operate independently from one another, do not fit well in existing rooms and end up taking away focus from the surgical field.

Surgeon-driven

Our solution is surgeon-driven  - we're product owners not of a single device but the entire OR. This approach differs from what we have experienced with device manufacturers.

Prof. Regelsberger is a pioneer in exoscopic neurosurgery as the first person in Europe using the first device of its kind. As head of a neurosurgical department he is familiar with the decision-making process in purchasing decisions.

Our Approach

We're using commercial off the shelf components wherever possible to create a device that allows updating existing technology with new capabilities, fixing known ergonomic issues with multi-screen workflows and tackling problems that might not sound like features that we should have to implement.

In a first step we're bringing a modular system to the OR that can be enhanced in the future.

Core team

Jan Regelsberger, MD

Jan has been practicing as an academic neurosurgeon for 30 years and teaches as Professor at University Hospital Hamburg-Eppendorf (UKE) – Germany's 2nd largest department right after Charité Berlin.

There he was vice-chairman of the department prior to his current role as chairman at DIAKO Flensburg.

He has had major involvement in many devices, especially in exoscopic surgery as the first user of Orbeye in Europe.

Roman Rotermund, MD

Roman followed Jan from UKE Hamburg (he's an Associate Professor [PD] there) to Flensburg as senior physician, where he mainly focuses on cranial neurosurgery; he's a leading expert in the field of pituitary surgery.

On the flip side - working in a major trauma center means that his small son says "Daddy work" when he sees a helicopter.

Especially between cases when he's on call, is when Nils comes in or he goes over to our provisional lab to check out the latest progress and further customize it.

We're not entirely sure when he catches some sleep - as during the precious moments outside the hospital he's always either chopping up wood in his yard, keeping up with art, socializing or with his family.

Nils Hempel

Nils has a legal background but found that following his interests in technology more and more interesting than merely its intersection when advising on data privacy over time. He has alway been a tinkerer with a keen interest in the underlying technologies - a transferable skill to solving this challenge. As such he's in charge of the technical development.

Having been responsible for quality management, IT and Occupational Health and Safety in a previous role has sharpened Nils' eye for processes and systemic inefficiencies (my partner jokes about my joy in setting up a clean database as a single source of truth).

Having that view and trying to genuinely help (and not from a business consultant's perspective) made him a welcome guest in the OR.

That and he really tried not to get close to anything sterile or snack too much in the lounge.

What's the story behind FLENSS and could you elaborate on the name?

There are three parts to the name:

  • Flensburg City we're based in; somewhat common naming convention (e.g. Berlin Heart).
  • Exoscopic Neurosurgery Neurosurgery that uses a Video-Microscope in conjunction with a 3D-screen
  • System We want to create a device that both integrates into existing ORs / devices and is open to iterative and modular updates.

And to state the obvious: We have no affiliation with Flens, our local brew.

No worries: Roman and Nils's dogs were adequately compensated in treats for introducing them to one another.

After having talked quite a bit about surgery and the devices Roman uses, with the announcement of Apple's Vision Pro they started to think: Could this be useful? While we don't think pass-through video will widely be used in the OR in the future, it did open up the conversation about "what if".

Once we had something and discussed its merits, we were hoping that Jan wouldn't see major issues when we pitched the idea to him. See section above for your answer to this.

We started to get to work on more technical details, refined their unmet needs in the OR, looked at what avenues had been explored previously and why they might not have worked out. We went through lots and lots of papers (as anyone who has ever looked at the barrage of publications in MDPI etc. knows), discarded many ideas and approaches, thought about required effort and expected return, sorted needs in the OR, discussed details with subject-matter experts and finally landed on a solution.

That's what we're building now.

Support
We receive funding and support from various sources:
OE logoAriseHealth logoAriseHealth logo
Data PrivacyImprintStatement on Regulatory Approval