Custom healthcare logistics software development
Healthcare logistics is the flow of goods through hospitals and care institutions: medical devices, implants, instrument sets, medicines and consumables, from the warehouse to the cabinet on the ward and the operating theatre. What sets it apart from ordinary logistics is that an item can end up attached to a patient. Appfront builds software for exactly that part: recording at the point of use, stock close to care, and integrations between systems that don't know about each other.
Stock management where an item becomes linked to a patient
In a distribution centre, an item ends with an order line; in a hospital, with a procedure, and sometimes in a patient. For implants and many other medical devices, it must remain traceable which unit was used on which patient, with the lot or serial number and expiry date. The last stage of the chain is no longer a stock movement, but a registration attached to the patient record.
That stage also has the least system support. The warehouse is usually well organised: an ERP module, scanning on receipt, fixed reorder points. Once a box reaches the ward or the operating theatre, the flow of goods disappears from the system and later resurfaces in a report or on a sheet of stickers.
This page covers that flow of goods. If you're looking for software for the clinical process itself, such as record-keeping or treatment plans, see building custom healthcare software. If the focus is procurement, distribution and the warehouse in a broader sense, supply chain management software is a better fit. If your software has a medical purpose of its own, medical device software is the starting point.
What goes wrong when registration in theatre is manual
An operating theatre is no place for administration: time pressure, sterile gloves, a team focused on the patient. If registering materials there means sticking labels on and typing them up later, you can expect what follows. Stickers get lost, a sticker lands on the wrong form, and the item that was pulled from another cupboard at the last minute appears nowhere.
You notice the consequences later on. Procurement receives an invoice for an implant that the system still shows as in stock. The procedure is recorded without material lines, so the cost price misses the most expensive component. And the serial number is on the patient's implant card, but not in a system you can search.
The problem is rarely carelessness; it is the time gap between use and registration. Software that solves this moves the registration to the moment of use and makes that action shorter than what it replaces. If it does not manage that, the system gets bypassed.
- Material use without a procedure, so no cost price per intervention
- Cupboard stock whose discrepancy only shows up at a stock count
- Consignment invoices that cannot be matched to recorded use
- Expired items discovered only when picking
- In a recall: investigation per patient instead of a single search
UDI, the MDR and the implant register
Since 26 May 2021, Regulation (EU) 2017/745, the Medical Device Regulation, has applied across the EU. It comes with UDI, the unique device identification, which consists of two parts. The UDI-DI identifies the product, in practice usually via the GTIN. The UDI-PI contains the production data: production and expiry date, batch or lot number and serial number. In healthcare, GS1-128 and GS1 DataMatrix are the two barcodes permitted worldwide. That distinction is the key point: the UDI-DI tells you what it is, the UDI-PI tells you which specific unit it is.
GS1 standards are standard practice in Dutch healthcare, including on the data side: suppliers share item data with care institutions via GS1 Data Source. So you are reading a structured code rather than a free-text field. Things go wrong with items that lack a usable barcode and with suppliers whose data is not in order. That is a procurement conversation, not a software problem.
There is also a national obligation: care providers must record implant data in the patient record and supply it to the National Implant Register. The Implant Registration Decree sets out which implants and data are involved, the submission deadline is one month, and an implant must be traceable quickly to the patient. The register does not contain personal data itself; that link stays in your own record-keeping.
In practice, scanning at the point of use therefore serves three recipients: the patient record, the submission to the register, and the cost of the procedure.
What such a system needs to do in practice
The order is deliberate: whoever starts with the reports builds something that gets bypassed on the shop floor.
Scanning at the point of use
A single scan records the item, lot or serial number and expiry date, and attaches the usage to the procedure. It keeps working when the network goes down.
Cupboard management by department
Reorder points per cupboard rather than per warehouse, with count and restock rounds that match how the department works. Visibility of the cupboard without having to walk over to it.
Monitoring expiry and sterility
Alerts on expiry dates and sterilisation deadlines, including sets that have been opened but not used. So that expired stock does not come to light only when someone picks it up.
Managing consignment stock
Keep supplier-owned stock separately, convert usage into an order or invoice line, and trigger replenishment. So that invoices and recorded usage match.
Recalls as a search
Search by lot or serial number across all locations: what is still in stock, what has been issued, what has been used and for whom. With an export as proof.
Connecting to what is already running
Consumption to the hospital information system or EHR, item data from the ERP, procedures from the operating theatre scheduling system. The interfaces are where the real work lies, not the screens.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →When custom is not the answer
The honest answer is that most hospitals should not procure this as a new system. Large institutions run an ERP with a healthcare or warehouse module in which purchasing, item management, contracts and the warehouse are already housed. You do not replace that: the financial administration and supplier flows depend on it. Starting with a replacement question means buying a problem you did not have.
The same applies at department level more often than suppliers admit. If your package can handle cupboard management with reorder points and your suppliers deliver usable item data, configuring is faster than building. For a smaller institution with a manageable range, a standard package is usually the right choice.
Custom software pays off in the layer in between, and we see three situations there. The first is recording in the operating theatre: no off-the-shelf package does this well, because at heart it is a workplace problem rather than a stock problem. The second is integrations between systems that don't know about each other, where the ERP, hospital information system and operating theatre system each hold part of the truth. The third is stock management at ward level, where the central package stops. In all three, you build something alongside the existing systems that feeds them.
Factor in what you take on yourself. With a package, responsibility for documentation, change management and demonstrable functioning lies with the supplier. If you build it yourself, that responsibility falls to your own organisation. That is manageable, but it is work you schedule in advance rather than discover during an audit.
Frequently asked questions about healthcare logistics software
The questions buyers, logistics managers and information managers ask before anything is signed.
Often that is also necessary. Large hospitals run an ERP with a care or warehouse module, and you don't replace that for a partial problem. The benefit of custom software lies in the layer around it: recording at the point of use, integrations between systems that don't know about each other, or stock management at ward level. Start by asking which part of the chain is genuinely unsolved.
Healthcare providers are legally required to record implant data in the patient file and to submit it to the National Implant Register. The Implant Registration Decree sets out which implants and data are covered, and the submission deadline is one month. Registration must be structured so that the implant can be quickly traced back to the patient.
Consignment stock is physically held by you but remains the supplier's property until it is used. The moment of use is therefore also the moment of purchase. A system designed for this records the used item by lot or serial number, generates the order or invoice line from that record, and triggers the replenishment. Otherwise the supplier invoice, shelf stock and patient file drift apart.
Stock and registration software without a medical purpose generally falls outside the definition of a medical device in Regulation (EU) 2017/745. The line is not always sharp: once software makes statements that steer clinical decisions, that assessment changes. Have the classification checked in advance. If the software does have a medical purpose, its own requirements for risk management and documentation apply.
Settle this before you start. Agree that the source code, the data model documentation and the interface specifications are held by you, that the repository sits on your own account, and that the environment can be rebuilt reproducibly. Ask for a handover file that a third party can read without the original builders. In healthcare logistics this weighs heavily, because it contains records you will still consult years later.
That depends on how granularly you record. If you only capture at article level, manual work remains: checking shelves, reading reports, comparing receipts side by side. If you record lot and serial numbers at issue and use, the question of which items are still on the shelves and which have already been used becomes a search query.
Related services
Healthcare logistics borders three domains. If your question falls within one of them, this is your starting point.
Building custom healthcare software
Software for the clinical process itself: patient records, treatment plans and scheduling. The domain where usage registration needs to land.
Supply chain management software
The wider supply chain: procurement, distribution, warehousing and supplier integration. Without the patient link that makes healthcare logistics specific.
Medical device software
Software that has a medical purpose of its own and therefore falls under a medical device as defined in Regulation (EU) 2017/745, with its own requirements for documentation and assessment.
If your healthcare organisation receives medication in weekly rolls and changes must reach the pharmacy on time, see our app for Baxter rolls and weekly medication preparation.
Taking on healthcare logistics?
Tell us where it currently gets stuck: recording in the operating theatre, consignment stock, ward cabinets, or the integration between your ERP and your hospital information system. We'll first look at what your current systems can already handle, and tell you if building isn't the sensible step. Connecting to the client record runs through an EHR integration.