FREQUENTLY ASKED QUESTIONS
Answers to the questions milk banks usually ask first
Here you will find a concise introduction to the product, workflow, traceability, different milk bank practices, rollout and next steps.
- Product
- Traceability
- Integration
- Rollout
Genitus Milkbank is a digital tool for human milk banks, developed in close collaboration with milk bank teams and hospital clinicians.
The solution brings the operational workflow, traceability and quality management together in one system.
It supports work from the receipt and registration of donor human milk, through processing, storage and ordering, to delivery and documented use for the recipient.
The aim is to make it easier to see which milk is being handled, what has happened to it and where it is, without having to manage the information across several separate systems and manual records.
Yes. Genitus Milkbank is designed to handle both raw and pasteurised milk.
Each physical milk unit is given a unique identity and a documented history.
When milk is pasteurised and a new batch is created, the link to the milk units included in that batch is retained.
The human milk bank can therefore follow both the operational workflow and the relationship between the original milk units, processing, storage, delivery and use.
This supports different processing paths without losing traceability between them.
Traceability is built around the unique identity of each milk unit and the documented relationships between events in the human milk bank.
The system records what has happened to the milk, which physical unit or batch it concerns, where it is and which other items or recipients it is linked to.
This makes it possible to trace backwards to the origin and history, and forwards to identify any units or recipients that may be affected.
Traceability therefore follows the milk through the workflow instead of being recorded separately.
Genitus Milkbank links quality management to what actually happens in the operational milk flow.
Deviations, CAPA, vigilance, recalls, the audit trail and reporting can be linked to relevant events, milk units, batches and recipients.
This provides a better documented basis for assessments, actions and follow-up while preserving traceability.
The solution is being developed with the new European SoHO requirements as an important consideration. It is intended to support needs including traceability, documentation, quality management and follow-up.
System support does not replace the milk bank’s own responsibility for regulatory compliance.
The rollout of Genitus Milkbank is planned with each milk bank and adapted to its existing workflows, organisation and needs.
We review the current milk flow and agree how the solution should be configured, which roles and access rights are required, and what training and testing are needed.
Before the solution enters routine use, the necessary reviews and tests are completed with the milk bank.
The aim is a safe and controlled rollout with as little disruption as possible to day-to-day operations, and with users properly prepared before the solution is introduced.
Yes. Genitus Milkbank is designed so that several human milk banks or hospitals within the same organisation or region can use the solution.
A shared solution can provide a more consistent basis for workflows, traceability and quality management across the milk banks.
Access rights, roles and organisational structure can still be adapted so that each milk bank retains control of its own workflows and data.
For healthcare organisations or regions with several milk banks, a shared platform can also simplify administration and further development, reducing the need for separate solutions for each milk bank.