Services · Digitalisation and workflow automation

Less retyping, more time for patients.

Hospitals, clinic groups and laboratories run booking, record, laboratory and imaging systems from different suppliers, and staff carry the data between them. Silurus Software builds the missing pieces and connects them to the systems you already run: online booking that reaches the record, intake before the visit, scheduling, documentation drafts for signature and follow up, under GDPR, and under HIPAA where we handle protected health information for a US covered entity.

Systems
HIS · LIS · PACS · national records
Standards
HL7 v2 · FHIR R4
Data protection
GDPR · HIPAA
Start
Free first consultation
What we cover

From booking to follow up

01

Online booking and reminders

Booking that writes into the scheduling system and the record, with confirmations, preparation instructions and reminders sent automatically.

02

Intake before the visit

Patients answer at home, the answers are scored before the visit, and the doctor opens a summary in the record.

03

Scheduling

One plan for staff, rooms, devices and laboratory runs, with the constraints of each.

05

Laboratory reports

Values read into the record as drafts, each with its source line. A draft value is not shown as a final result and feeds no rule or alert until staff confirm it.

06

Follow up

Follow up questionnaires at set intervals, with the results returned to the record and shown per procedure.

07

Reporting across sites

Dashboards and reports across sites, fed from the systems already in use.

08

Interfaces and data protection

An integration layer to the HIS, LIS and PACS you run, with access by role and logging, under GDPR or HIPAA.

Interoperability →
Use cases

Automation and AI around the patient

Use cases our AI research team follows, tests and extends in its own research and with clients. Each one starts small, in one department, with measures agreed in advance.

01

Patient questions in chat

A chat assistant answers from the institution's approved content, such as preparation, opening hours and directions, tells the patient that it is an AI and hands over to a person when needed.

02

Booking by phone and chat

An assistant books, moves and cancels appointments in the scheduling system, with every booking action logged. How it identifies the patient, and what it may change or tell after that, is fixed in the specification.

03

Patient reported outcomes

PROMs such as EQ-5D or the Oxford knee score, used under the licence each instrument requires, sent at set intervals after a procedure, scored, and the results shown per procedure, and per surgeon only with the case mix and the number of cases beside each figure.

04

Remote follow up with alerts

Questionnaires and home measurements after discharge, with values over a threshold flagged. Alerts on measured values can make software a medical device, so the intended purpose (what the manufacturer states the software is for) is fixed in the specification before an alert is sent to the responsible nurse. Thresholds, delay and behaviour when a link fails are verified before use.

05

Referral triage

Referrals read, sorted by specialty and suggested urgency, and missing information requested. A named clinician confirms the suggested urgency before the appointment is set. Alerting and urgency sorting can make software a medical device, so the intended purpose is fixed in the specification first.

06

Document intake

Incoming documents classified, indexed to the right patient and filed into the record, with uncertain cases sent to staff.

07

No shows and waiting lists

Patients likely to miss an appointment get an extra reminder, and freed slots are offered to the waiting list.

08

Patient information in several languages

Preparation and discharge instructions translated by AI and checked by staff before they are sent.

09

A knowledge assistant for staff

Staff ask in plain language, and the answer cites the institution's own protocol and its version.

10

Nursing handover summaries

A summary per patient drafted from the record for the handover, checked by the nurse.

11

Management questions in plain language

Questions about volumes, waiting times and capacity answered from read only data, with the query shown.

AI research

A team that tests the tools first

Silurus Software has a dedicated internal AI research team. It follows the AI tools that reach the market, uses them in its own work and measures them on defined tasks before we propose them to a hospital or clinic. New use cases come from client projects and from our own research, and each is judged by whether it gives the patient better care, takes administrative work off doctors and nurses and lowers the cost per patient.

In our own research, a laboratory report reader built on a language model running on local hardware read all 104 values from 24 synthetic laboratory reports correctly, with the source line quoted for each value and no data sent to an external service. The values go into the record as drafts, and a member of staff confirms them before they count. This was a first test on synthetic data. Before clinical use the reader is measured on the institution's own reports.

In practice

Situations we are asked to solve

Situation

Overloaded phone lines at a hospital contact centre

Booking and rescheduling calls overload the phone lines of a hospital group.

How we approach it

We can build a telephone and chat assistant, in Hungarian, German or English, that books, moves and cancels appointments in the scheduling system, identifies the patient, answers practical questions and hands the call to a person when needed. Patients are told at the start that they talk to an AI, as the EU AI Act (the EU regulation on artificial intelligence) requires. Every booking action is logged. Whether the content of a conversation is kept, and for how long, is decided with your data protection officer and written into the data protection file.

Situation

An AI scribe pilot in a clinic group

A clinic group wants to try an AI scribe that drafts consultation notes, and worries about data protection and note quality.

How we approach it

A pilot in one department measures doctor minutes per note, the share of notes that need editing and the errors found in review: omissions, invented content, negations, medication details and notes attached to the wrong patient. The data protection impact assessment and the processing contracts are checked first.

Situation

Systems that do not talk to each other

Booking, record, laboratory and imaging systems come from different suppliers, and staff retype data.

How we approach it

An integration layer connects them, with access by role and logging. The specification covers patient matching, duplicate messages, retries and what happens when a message fails, and the first module goes live in one department.

How it runs

Small steps, each with a written result

Step 1

Review

Current processes, systems and data flows, with a ranked list of changes and the effort for each.

Step 2

Specification

Requirements, interfaces and data protection agreed in writing, the interface effort stated before the contract.

Step 3

Build

Modules delivered in increments the staff can try, connected to the systems in use.

Step 4

Go live

Documented verification against the specification in a test environment, then tests on the live interfaces, training, and four weeks of stabilisation support after go live. Longer term maintenance, security updates and incident handling are agreed as a separate written support scope before go live.

What you receive

Results of each step

D-01

Process and system review

A written report on processes and data flows, with the changes ranked.

D-02

Data protection file

Access by role, retention, the data processing agreement and input to your data protection impact assessment.

D-03

Connected modules

Booking, intake, scheduling or documentation, connected to your systems.

D-04

Runbook and support

Instructions for the staff, and support after go live.

EU and US

Patient data in both markets

European Union

Europe

Health data under GDPR, with Silurus Software as processor under a data processing agreement where we process patient data, and the national record connection kept.

United States

United States

The same work under HIPAA. Where we handle protected health information on behalf of a covered entity, a business associate agreement applies.

Technologies and standards

What we work with

Technologies and tools

TypeScriptReactAngularVueNode.jsPythonC#ASP.NET CorePostgreSQLSQL ServerDockerKubernetesHL7 v2FHIR R4OpenID ConnectSAML 2.0Playwright

Standards, regulations and practices

IEC 81001-5-1MDCG 2019-11 Rev.1EU AI ActTelematikinfrastrukturELGAEPDEESZTGDPRHIPAAData processing agreementBusiness associate agreementDPIAEU MDRFDA

Silurus Software

  • Silurus Software, founded in 2017, offices in Budapest, Hungary, and Singapore
  • More than 40 engineers, EU MDR regulatory specialists and FDA consultants
  • Multi-year engineering partner of a European MedTech manufacturer
  • Founder and CTO Péter Török, in medical technology software since 1999, formerly software development director at Siemens Healthcare (syngo.via) and head of R&D at Mediso Medical Imaging Systems
  • ISO 9001:2015 (NQA, certificate 171041, valid until March 2027) and ISO/IEC 27001:2022 (NQA, certificate 728872, valid until August 2029)
  • Awarded AAA, Highest Creditworthiness, by Dun & Bradstreet in 2025
  • Research partner of ELTE Eötvös Loránd University, Budapest
  • Industrial partner of the University of Bologna, the University of Pisa, the University of Amsterdam and Masaryk University, Brno, in the EU Horizon Europe project LOGOS from 2027
  • Female Business Leader of the Year 2025 and The Pioneer Award 2026, awarded to CEO Dr. Linda Szántó
How we work →Quality and standards →Sample deliverables →Case studies →
FAQ

Frequently asked questions

01

Can online booking write straight into our record system?

Yes, where both systems offer an interface. We state the effort before the contract and test the connection, including what the front desk sees when one side is down.

02

Do you sell a booking system or a record system?

We build the missing pieces and connect the products you choose, and help select a product where one fits.

03

Where does our patient data go?

Patient data stays in your systems unless the task needs it to leave, and each such case is listed in the data protection file before use. Where data has to leave, the data flow is documented, data is minimised or pseudonymised where the task allows, and processing is covered by a data processing agreement, or a business associate agreement in the US. Where an assistant uses a speech or language model service outside your systems, the provider, where it runs and any transfer outside the EU are named in the data protection file before use. Pseudonymised data remains personal data under the GDPR.

04

When does a workflow tool become a medical device?

Software that triages patients, interprets results for a diagnosis or recommends a treatment can be a medical device. Whether it is follows from its intended purpose and function. We write the intended purpose into the specification and qualify the software before the build, under the EU MDR or, for laboratory software, the IVDR (the EU regulation for in vitro diagnostic devices), with MDCG 2019-11 (guidance from the EU Medical Device Coordination Group), or under the FDA device rules and clinical decision support guidance in the US. A function that is a device stays one whatever the wording of the specification. Software a health institution builds for use only within itself may fall under the in house provisions of Article 5(5) of the MDR, and we check them with you. If it is, it is built under IEC 62304 and ISO 14971 inside the manufacturer's quality system, and the risk class follows from the classification rules.

05

What does a first project cost?

The first consultation is free. Each step after it is quoted individually and agreed in writing.

06

In which languages do you work?

English, German and Hungarian.

Talk to us

Tell us what you would like to improve.

The process and the systems you run today. Write a few lines, or book a free call.

Book a 30 minute technical call
We reply within one working day.