I turn technical decisions into working, transferable systems.
From the technical foundation of a new product to existing-system integration and reliable release workflows, I bring business goals, engineering decisions and operational reality into one framework.
Service areas
Technical support from decision to working system.
Product and solution architecture
Defining workflows, user roles, security boundaries and integration points to create an actionable architecture and delivery roadmap.
Technical discovery and risk analysis
Component, data and access design
Implementation and delivery plan
Systems integration
Connecting enterprise databases, third-party services, clinical systems and device protocols through traceable, failure-aware flows.
Oracle · PostgreSQL · MySQL · MSSQL
REST · WebSocket · HL7 · DICOM · OCPP
Logging, failure and retry behaviour
Software modernisation
Improving code, interface, security, data access and packaging layers without disrupting the working system.
Source and dependency review
Narrow, safe transformation
Compatibility and regression checks
DevOps and release reliability
Project-based delivery that makes software observable, recoverable and transferable in its target environment—not merely buildable.
CI/CD · Nginx · systemd
Health checks, logging and backups
PyInstaller · EXE · Inno Setup
Servers and virtualisation
Designing and implementing physical and virtual server resources, service dependencies and backup targets around operational continuity.
Linux · Windows Server
Microsoft Hyper-V · Proxmox VE
Veeam Backup & Replication
Mail and web servers
Building domain, DNS, SSL, web publishing and enterprise email components as a secure, observable and manageable platform.
Visible outputs and clear responsibility at every stage.
01Discovery
Current flow, goals, boundaries and risks.
02Architecture
Components, data flow and delivery plan.
03Implementation
Focused, verifiable engineering.
04Verification
Tests, packages and target-environment checks.
05Release and handover
Documentation, rollback and operating knowledge.
Delivery approach
The production environment is part of the product’s technical scope.
Service configuration, environment variables, access boundaries, health checks, logs, virtualisation, backups and rollback steps are handled with the project. Delivery is complete when source, runnable package and operational knowledge agree.
Frequently asked questions
What people ask before we start.
What kinds of software consulting do you provide?
I provide project-based consulting and technical delivery across six areas: product and solution architecture, systems integration, software modernisation, DevOps and release reliability, servers and virtualisation, and mail and web servers.
Which healthcare IT standards do you work with?
I work with HL7 messaging, DICOM, PACS, KOS/XDS, WADO and DICOMweb. These standards are used in the Web PACS, HL7 / Healthcare Transfer, MediScopy Endoscopy and DICOM CD Writer projects.
Which database and infrastructure technologies do you use?
For data: Oracle, PostgreSQL, MySQL, Microsoft SQL Server, SQLite and Redis. For infrastructure: Linux, Windows Server, Microsoft Hyper-V, Proxmox VE, Veeam Backup & Replication, Nginx, Apache and Hestia.
Can a system be modernised without taking it offline?
Yes. Work starts with a source and dependency review, then improves code, interface, security, data access and packaging layers in narrow steps, with compatibility and regression checks at each step.
What stages does a project go through?
Five stages: discovery, architecture, implementation, verification, and release and handover. Each stage has a visible output and a clear owner.
What is included in a delivery?
Source code, a runnable package, installation knowledge, acceptance criteria, a rollback plan and technical documentation. Delivery is complete when source, package and operational knowledge agree.
How do I start a project with you?
Use the contact form to briefly share the goal, current technology or process, the present constraint and the expected outcome. That is enough for an initial technical review.
Initial review
Let’s review your current system or the product you want to build.
Share the goal, the current system and the expected outcome; we’ll do the initial technical review together.