Trace forwards
Start with the donation. Find the processing batch, the bottles created from it, remaining stock and each recorded destination. The receiving teams locate the relevant recipient records.
A practical guide for milk banks and hospital teams
Understand what the EU SoHO Regulation means for milk banks, milk kitchens and neonatal intensive care units (NICUs). Learn which activities are covered, what teams should record and how to prepare.
Find out what applies to your team, follow a practical tracing example and see how connected records can support your daily work.
SoHO stands for substances of human origin: substances collected from the human body for use in healthcare, including blood, tissues, cells and human milk. Regulation (EU) 2024/1938 sets quality and safety requirements to protect donors and recipients.
For human milk, this means considering how milk is collected, tested, processed, stored, distributed and administered. The regulation covers more than traceability: it also addresses quality management, registration, authorisation and the reporting of safety incidents.
Most provisions apply from 7 August 2027. Some provisions have different application dates, and transitional arrangements apply to certain existing organisations and activities.
Regulation: Article 87 and transitional provisionsScope and responsibilities
Not all human milk activities fall within the regulation. The distinction between donor human milk (DHM) and mother’s own milk (MOM) matters.
For example, a mother’s milk stored in a hospital refrigerator for her own child, without further processing, falls outside the SoHO Regulation. Other healthcare, hygiene and patient-safety requirements still apply.
MilkTrail supports donor milk and mothers’ own milk workflows, including workflows outside the regulation’s scope.
Processing is broader than pasteurisation. The regulation’s definition includes handling operations such as separation, preservation and packaging.
Not every activity involving milk is processing. Receiving, storage and distribution are distinct activities. Processing must follow appropriate procedures to maintain milk quality, safety and traceability.
A milk kitchen might thaw milk, measure the prescribed quantity or transfer milk into a feeding container. Assess these steps in the context of the actual workflow. Routine preparation immediately before feeding should not automatically be equated with milk-bank processing or used alone to conclude that establishment authorisation is required.
Feeding milk to an infant is called human application. It is a separate SoHO activity from processing.
Regulation: Article 3(19) and (23) — human application and processingMilk banks and hospital teams
Yes. Hospitals that carry out covered SoHO activities are included. A hospital that stores donor milk and feeds it to infants has a role under the regulation, even if it does not operate a milk bank. Feeding the milk is called “human application” in the regulation.
The activities an organisation carries out determine its responsibilities. Two terms explain the difference:
For example, a milk bank that pasteurises and stores donor milk meets the establishment definition. A hospital that stores and uses milk already released by that bank is an entity; those activities alone do not make it an establishment.
Every establishment is also an entity. A hospital can include a milk bank that is an establishment. Agree the registration and authorisation arrangements for your organisation with your national regulator, who can also require establishment authorisation for other activities based on risk.
Regulation: Articles 3, 24, 35 and 45 — entities, establishments and authorisationWhat to plan for
Traceability means being able to follow human milk and its relevant records through the regulated chain in both directions. A concern about a donation should lead to the linked milk and recipients. A concern about milk given to an infant should lead back to its source.
Protect confidential donor and recipient information through appropriate access controls and data-protection arrangements. Other documents may have different retention periods from the necessary traceability data.
For your project, agree how identifiers, access, exports and long-term record availability will work in practice. Confirm coding compatibility and retention arrangements explicitly with each supplier.
An illustrative workflow
Three donations are combined into one processing batch and divided into 40 bottles. Twenty go to Hospital A, ten to Hospital B and ten remain in the milk bank’s freezer. Later, a question arises about one donation. Can the teams find the linked batch, bottles, remaining stock and recorded recipients?
Start with the donation. Find the processing batch, the bottles created from it, remaining stock and each recorded destination. The receiving teams locate the relevant recipient records.
Start with a fictional feeding record. Find the milk used, the batch it came from and the contributing donations.
Use fictional records for this preparation exercise. Note gaps and unclear responsibilities. For a real incident, follow your organisation’s approved procedures; this example is not a recall protocol.
A hospital that gives donor milk to infants has responsibilities even when it does not process the milk. EDQM calls it an organisation responsible for human application (ORHA).
EDQM Good Practice Guideline G32.43 says the receiving hospital should document when and how milk was used and to whom it was administered. This is EDQM good-practice guidance; the underlying traceability responsibilities also come from the regulation.
Receiving teams should also check labels and accompanying information, maintain suitable storage conditions and follow the milk’s handling instructions.
Regulation: Chapter IV, including Article 42 — entity responsibilities and traceabilityEDQM Guide, 6th edition — Chapters 14, 17 and 32, including G32.43
Explore MilkTrail for hospital teamsWhen milk moves between a milk bank, milk kitchen and neonatal ward, its records need to stay connected. Digital traceability helps teams follow that journey and retrieve the information they need for daily work, reviews and investigations.
MilkTrail brings these links into your team’s workflow. We agree the setup, access, training and connections with you, so the software supports the way your organisation handles milk.
EDQM Guide, 6th edition — Chapters 2, 16 and 17 — quality management, documentation and traceability
Connected records in daily work
MilkTrail is human milk traceability software for milk banks and hospital teams. It connects records across donation, processing, storage, distribution, preparation and administration. We review your current routines and agree the setup with you.
| Workflow need | How MilkTrail helps | What your team agrees |
|---|---|---|
| Identify milk | Use scanning to identify milk and find its linked records. | Agree labels, equipment compatibility and staff checks. |
| Connect donation and processing | Link donor and bottle records with processing batches. | Define local procedures and the checks staff must record. |
| Coordinate stock and deliveries | Find milk by status and location and connect dispatch with receipt. | Agree responsibilities for release, transport and discrepancies. |
| Connect preparation and care | Keep milk records connected across preparation teams and receiving wards. | Define how milk and recipient records are linked in your workflow. |
| Work across sites and systems | Coordinate participating organisations; scope API connections with your IT team. | Agree access, data exchange, retention and supplier responsibilities. |
We agree responsibilities, capabilities and implementation steps before your project starts. MilkTrail supports your traceability workflow; your organisation remains responsible for its regulatory arrangements.
Explore MilkTrail for milk banksA practical starting point
Review your human milk workflow, identify areas to follow up and create a practical action plan. These prompts support team discussion; they do not determine regulatory compliance.
Legal references link to Regulation (EU) 2024/1938. Suggested checks and actions are practical preparation prompts, not additional legal obligations. For EDQM Standards, Good Practice Guidelines and Recommendations, see how to use EDQM guidance.
The regulation sets the legal framework. The EDQM Guide provides technical guidance for putting quality and safety into practice. Its sixth edition distinguishes three types of statement:
The regulation gives technical guidelines a role in meeting its standards. Apply the relevant guidance alongside national requirements and decisions from your national regulator.
EDQM Guide, 6th edition — standards, good-practice guidelines and recommendations
Yes. Donor human milk intended for another person's infant falls within the framework of Regulation (EU) 2024/1938. The specific obligations depend on the activities performed.
Milk used exclusively for a mother's own child is excluded when it is not processed by a SoHO entity. Processing by a SoHO entity can bring it within the Regulation.
A NICU administering regulated donor human milk carries out human application, a covered SoHO activity. Registration arrangements must be established with the national competent authority, including whether registration is organised at hospital or other legal-entity level.
No. Storage and processing are distinct SoHO activities. Storing released donor milk before administering it does not, by itself, mean the hospital performs processing.
EDQM distinguishes routine preparation immediately before clinical application from processing. The precise workflow matters; thawing immediately before use should not automatically be classified as milk-bank processing.
Aliquoting is discussed within EDQM's human milk processing guidance. However, context matters, especially when milk is portioned immediately before feeding. Not every bedside handling step should automatically be classified as regulated processing.
No. Feeding an infant is human application, which is a separate activity under the Regulation.
Not solely because it feeds released donor milk to infants. That hospital carries out a covered activity and is a SoHO entity, but those activities alone do not make it a SoHO establishment.
Necessary traceability data must be kept for at least 30 years from distribution or, where applicable, disposal or export, under Article 42(6). Other records may have different retention requirements.
The Regulation contains identification and coding obligations, but this does not mean every organisation must buy a particular barcode system. The applicable coding requirements, including SEC provisions and exceptions, must be assessed.
Yes, provided the records meet applicable requirements. The practical question is how reliably your team can keep records connected, retrieve them and follow milk across handovers. Digital traceability can help as the number of bottles, teams and sites grows.
The SoHO traceability system must support identification of recipients and the relevant SoHO preparations. EDQM G32.43 specifically addresses documenting how milk was used and to whom it was administered.
MilkTrail helps connect milk identification, processing, stock, handovers and recipient-linked records. We work with your team to agree the setup and responsibilities. Compliance depends on your complete processes and applicable requirements; software alone cannot guarantee it.
Check the current text and guidance relevant to your activities with your national competent authority. This guide provides general information, not legal advice.
Article 2: scope. Article 3: definitions. Articles 24, 35 and 45: authorisation and registration. Articles 42–43: traceability and coding. Articles 81–83: transitional provisions. Article 87: application.
Chapters 2, 10, 14, 16, 17 and 32: quality management, processing, clinical application, documentation, traceability and human milk.
A practical next step
Tell us how milk and records move through your organisation. We’ll show you relevant MilkTrail workflows and discuss equipment, connections, training and implementation.
Talk through your workflowBring your questions. No preparation needed.