Custom RIS software development
A radiology information system (RIS) drives the administrative and logistical side of medical imaging: the request, scheduling by modality and time slot, the technologist's worklist and the report. Appfront builds software for radiology departments and imaging institutes. Usually that is not a complete RIS, but a module or integration around your existing package, at the point where your process differs from what the supplier delivers. Where an off-the-shelf package is a better fit, we will say so.
What a RIS does, and where it stops
The RIS is the administrative and logistical system of the radiology department. A request arrives from the HIS or EHR, receives an accession number, is scheduled on a machine and time slot, appears on the radiographer's worklist and ends in an authorised report. The PACS manages the images themselves and the viewer in which the radiologist reads them. These are separate systems under separate contracts. In the Netherlands, the RIS is often a module within the EHR, for example in ChipSoft's HiX, or a standalone package from a supplier such as NEXUS.
This page is about software for the radiology process: scheduling, worklists, integrations and reporting. If you are looking for software for a healthcare organisation more broadly, such as a client portal or a record-keeping system outside radiology, see building healthcare software. If your software itself performs a clinical function, such as image analysis, the Medical Device Regulation applies and you belong under medical device software. Software around the RIS usually falls outside that scope, but the line is thin.
The RIS: process and administration
Orders, scheduling, accession numbers, worklists and the reporting flow. Everything around the examination, except the images themselves.
The PACS: the images
Storage, distribution and presentation of DICOM images, with the diagnostic viewer. The PACS knows nothing about scheduling.
The HIS or EHR: the patient
Identity and the request itself. It delivers the order to the RIS and receives the report back via HL7 messages.
Where it goes wrong in practice
The questions departments bring to us are rarely about a missing feature, but about the places where process and system drift apart.
Scheduling with several scarce resources at once
Scheduling a radiology appointment is not a single choice but a set of conditions that must all hold at the same time. The examination requires a specific modality, and sometimes a specific machine within it, because a protocol cannot run on every MRI scanner. It requires a time slot that suits the type of examination: an MRI typically occupies the machine for half an hour or longer, a chest X-ray takes only a few minutes, and the same examination with contrast takes longer than without. Sometimes the patient needs preparation, such as fasting or a lab result that has to be in first. And for some examinations, someone with the right qualifications must be available, for example for contrast administration or an intervention.
A schedule is therefore only valid when machine, time, staff and preparation all line up at once. Software that treats these as separate fields shifts the puzzle onto the scheduler, who then keeps their own overview alongside it. That overview becomes the real scheduling system.
No-shows and emergencies break every schedule
No radiology schedule survives the day unscathed. A patient doesn't show up, an emergency from the ED has to be fitted in, a machine breaks down, or an examination overruns because the images aren't good enough. A system that only plans forwards but cannot reschedule is unusable in practice. Seeing which slots become free, knowing who can step in and contacting that patient without a round of phone calls is at least as valuable as the scheduling itself. In an emergency, it must be immediately visible what knocks over the rest of the day.
The modality worklist is not a technical detail
The integration between the RIS and the modality runs via the DICOM modality worklist. The device queries the RIS with a C-FIND and receives the scheduled examinations back: patient details, accession number and the description of the procedure. The radiographer selects the patient from that list, and that data ends up unchanged in the images.
If the integration fails, nothing changes in the waiting room: the patient is standing at the machine and the examination goes ahead. The radiographer then types the details into the console by hand, and that is where the damage happens. A mistyped patient number, an accession number that is off by one digit or a different spelling of the name produces images that are administratively attached to the wrong patient. The PACS accepts those images without complaint; the error only comes to light when the report cannot be linked to anything, and sometimes not even then.
Fixing errors afterwards is laborious and undermines the integrity of the record. The worklist is not just a list: it is where the identity of the examination is established. The IHE Scheduled Workflow profile describes how that chain should run, from order to worklist to storage in the PACS.
Reporting is the bottleneck, not imaging
Turnaround time is determined mainly by how long the image waits for review. A worklist that shows examinations in order of arrival leaves the radiologist to hunt for what is urgent. Sorting then happens by gut feeling, or by whoever calls the loudest.
Prioritising takes more than copying an urgency flag from the request. It is about the combination of clinical urgency, the department that is waiting, the subspecialty of the radiologist available, whether the examination follows on from earlier imaging, and whether a deadline is about to pass. Often the gain lies not in a smarter algorithm but in visibility: what has been open for too long, and how incoming volume compares with review capacity. In its guidance on capacity planning, the Dutch Society of Radiology points out that radiology is often overlooked in hospital-wide capacity agreements.
The honest trade-off: don't build a complete RIS
We build custom software, and yet our advice is this: don't build a complete RIS. The process is highly standardised, the packages are deeply intertwined with PACS vendors and with the hospital information system or EHR, and there is no competitive advantage in your own version of something that works the same everywhere. You would also be taking on the maintenance and continuity of a core system, in an environment where your auditor will check it.
An off-the-shelf package is the better choice when your process is broadly the standard one, when you want to keep the chain with a single supplier, and when you have no organisation to take on functional management. That applies to most departments, and it is not a sign of weakness.
Custom software earns its keep at the edges: where your package stops, or where you deliberately work differently. Such outer layers are smaller and less risky, and you can switch them off without radiology grinding to a halt.
Situations where custom development is the sensible choice
- No appointment module that fits your patient population
- Two systems with no interface that the supplier is willing to build
- Management information that the RIS does not deliver in the form you need
- A missing registry for quality, research or dose
- A referral flow that deviates from the standard model
- An essential function that is not on the roadmap
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Where custom software around the RIS pays off
Four solutions come up most often. They don't replace the RIS, but complement it.
An appointment module for patients
Booking or rescheduling themselves, but only within the department's rules: slots that match the examination type, with the right preparation instructions. When an appointment is cancelled, the slot is freed up immediately.
An integration between systems that don't know each other
A referrer, an independent institute or a research database outside your chain. We build the interface on the HL7 and DICOM services your suppliers support, with logging that shows when a message fails to arrive.
Management information on turnaround time and utilisation
Waiting time per examination type, utilisation per scanner, overrun, no-shows and the time to an authorised report. Built on what the RIS and PACS already record, so that every figure stays traceable.
A registry that the package doesn't support
Dose data to check against the diagnostic reference levels, a quality or complication registry, or a dataset for research. The information is often there, but not in the form in which you have to submit it.
Standards, norms and integrations
In radiology, orders and reports travel via HL7 v2. A request arrives as an ORM or OMI message, the report goes back as an ORU message, and the accession number in the OBR segment keeps order, performance, image and report together. Towards the modalities it is DICOM: the modality worklist for scheduled examinations, Modality Performed Procedure Step to report that an examination has started or finished, and storage commitment for the handover to the PACS.
On the Dutch side, NEN 7510 is the sector standard for information security in healthcare, in the form of NEN 7510-1:2024 and NEN 7510-2:2024 since December 2024. NEN 7513 covers logging of record access. Under the Dutch Electronic Data Exchange in Healthcare Act (Wegiz), image availability is being made mandatory in stages: images and reports must be digitally available to the next practitioner, with NEN 7541 as the detailed specification.
If your software goes beyond storing and searching, for example by prioritising examinations on clinical grounds, the Medical Device Regulation comes into play. Ask that question at the start: see our page on medical device software.
Frequently asked questions about RIS software
The RIS manages the process and the administration: the order from the HIS or EHR, scheduling by modality and time slot, the accession number, the status of the procedure and the report. The PACS manages the images themselves and the viewer in which the radiologist reviews them. They are connected via HL7 and DICOM, but remain separate systems.
Usually not. The domain is highly standardised, the packages are deeply integrated with PACS vendors and with the hospital information system or EHR, and a department gains little from its own version of something that works the same everywhere. What does pay off is custom work around the existing RIS: an appointment module, an integration that is missing, management information or a registration that the package doesn't offer.
That is the starting point of almost every project. Orders and reports usually run via HL7 v2, with ORM or OMI messages carrying the request and ORU messages sending the report back, using the accession number in the OBR segment as the key. Towards the modalities it is a matter of DICOM: modality worklist, Modality Performed Procedure Step and storage commitment.
That depends on what the software does. Storing, forwarding, archiving and searching fall outside Regulation (EU) 2017/745. As soon as software goes further, for example by prioritising examinations on clinical grounds, qualification as a medical device comes into play. If a healthcare institution builds a device itself for its own use, the in-house exemption of Article 5(5) applies.
Radiology data is special category personal data. NEN 7510 is the sector standard for information security in healthcare; NEN 7510-1:2024 and NEN 7510-2:2024 were published in December 2024, aligned with ISO/IEC 27001:2023. Certification against the previous version remains possible under accreditation until 20 February 2027. NEN 7513 covers logging of record access.
You own the source code, the documentation and the environment. We document interfaces, message formats and configuration so that another party can take it over. That matters even more here: your RIS and PACS suppliers have their own release calendars, and the layer around them has to stay maintained.
Related services
Custom healthcare software development
Custom software for healthcare organisations beyond radiology: portals, intake and treatment processes, planning and registrations, with the same NEN 7510 requirements.
Custom medical device software development
For software that performs a clinical function itself and therefore qualifies as a medical device under Regulation (EU) 2017/745, including the documentation obligations.
Discuss your RIS question
Tell us which part of the radiology process is getting stuck: scheduling, the worklist, the report flow or accountability afterwards. We first check whether your current package can solve it. If not, we outline which layer around it makes sense and what maintenance it requires.