Services · Full-stack
Custom medical device & clinical-software integration
Medical devices, clinical software, and electronic health records rarely speak the same language. We build the HL7 / FHIR / DICOM bridges, device firmware integrations, and audit-ready middleware that ties them together.
- healthcare custom software
- HL7 integration
- FHIR bridge
- medical device firmware
- egészségügyi egyedi szoftver
Where it lands in this industry
- HL7 v2 / FHIR bridge between EHR and ancillary systems
- Medical-device firmware with regulatory sign-off paths
- DICOM pipeline for imaging data + cloud archival
- Clinical-trial data collection + audit trail
- E-prescription bridge to national NEAK / eHealth
What you get
The work that does not fit a category: an internal tool that replaces a spreadsheet nobody understands any more, a Telegram bot that quotes prices, a portal your clients log into, an API two systems talk through. We write it so the next developer can read it, and we leave you the repository, the deployment and the documentation.
- A working application, deployed, with the repository in your organisation
- A database schema that will survive the next two features
- CI that runs the tests and blocks a broken deploy
- A README a new developer can follow without calling us
Work from this bench
DIMOP Plusz · GINOP Plusz · Vállalkozz Digitálisan
Buying this with a digitalisation grant
DField Kft. is an accredited IT supplier in the Hungarian Chamber of Commerce and Industry's Modern Vállalkozások Programja (Vállalkozz Digitálisan). Hungarian SMEs can order this work through the programme's grant calls, currently DIMOP Plusz 1.2.6 and earlier GINOP Plusz, with the formal quote issued on the programme portal.
How a grant-funded order worksStraight answers
- How long does a first version take?
- Most are four to eight weeks. If something can be useful in two, we will say so and build that first.
- Can you take over an existing codebase?
- Often yes. We start with a short read-through and tell you honestly whether continuing or rewriting is cheaper.
- Who owns the code?
- You do, from the first commit. The repository lives in your organisation, not ours.
- Can we pay for this with a digitalisation grant?
- Yes. DField Kft. is an accredited IT supplier in MKIK's Vállalkozz Digitálisan programme, so a Hungarian SME can buy custom software, integrations, AI automation and security work through the DIMOP Plusz calls, as it could under GINOP Plusz. The formal quote is issued on the programme portal; the scope, fixed price and hand-over are the same as for any other project.
- Can you take over a codebase somebody else wrote?
- Yes, and it is a normal starting point. The first job is reading what is actually there rather than what the documentation claims, which is why the early weeks are discovery — inheriting a codebase blind is how a rewrite gets proposed for something that needed three fixes.
- Will you rewrite everything?
- Only if the honest answer is that a rewrite is cheaper than the repair, and that is rarer than it sounds. A rewrite discards working behaviour nobody wrote down, including the edge cases somebody fixed at two in the morning two years ago.
- What does the stack depend on?
- What the thing has to do and what your team can maintain after we leave. Next.js, Python, FastAPI, Node and PostgreSQL cover most of it, and picking something exotic that only we can operate would be optimising for the wrong party.
By industry
Tell us the problem in plain words.Book the intro call
