Interim CTO · Case
Architecture ownership in a regulated domain
drd is Austria’s first telemedicine GP platform: video consultations, e-prescriptions, sick notes. As interim CTO I owned the architecture, including the connection to the Austrian social insurance system.
- e-card
- connection to the social insurance system
- e-prescription
- incl. medication catalog and approvals
- QES
- qualified electronic signature
- Generali, Drei
- cooperation partners
Starting point
Telemedicine means health data, signature requirements and interfaces to government systems. If you build a GP platform, you cannot launch first and think about compliance later: regulation shapes the architecture from day one.
On top of that came partners like Generali and Drei, who expect reliability: defined interfaces, commitments that hold, and a technical counterpart who delivers.
What I was responsible for
- Owned the platform architecture: Angular, Django, Google Cloud
- Connected the e-card infrastructure of the social insurance system: e-prescriptions, medication catalog, approvals
- Introduced the qualified electronic signature (QES), legally valid and workable for doctors
- Owned the go-lives: accompanied into production as a forward deployed engineer
- Technical counterpart for the partnerships with Generali and Drei
Regulation as an architecture question
In regulated domains, speed is not decided while coding but when the architecture is cut: which data lives where, who signs what, which audit trails the regulator needs. Cut this right early and you deliver fast afterwards. Postpone it and you build twice.
This experience transfers directly to mandates close to insurance, health and other industries where an interface to the state or a regulator is part of the job.
“Telemedicine with an e-card connection is demanding, technically and in terms of regulation. As interim CTO, Marc owned the architecture and reliably guided the platform through these requirements.”
Dr. Clemens Billek Board member Kontron, founder drd.at
Proof
Angular Django Google Cloud QES e-card
A good fit if
- your product lives in a regulated industry (health, insurance, finance)
- you need interfaces to government or public-sector systems
- your partners expect a technical counterpart at eye level
No pitch, no slides.