A venepuncture is a venepuncture. The vein, the needle and the underlying anatomy do not change when you cross a border. So it is tempting to assume that a training programme built for one country can simply be translated and dropped into another: same slides, different language.

It cannot, and the reason is bigger than language. Almost everything around the clinical skill differs from one health system to the next: who is allowed to perform a procedure, what supervision looks like, how competence is signed off, what records are kept, and who is accountable when something goes wrong. Translating the words on a page does not touch any of that. It is one small part of a much larger job.

This article sets out how VeinTrain actually approaches that larger job: not as a translation exercise, and not as an export business, but as the deliberate work of building clinical capability with local partners, using architecture VeinTrain has already developed, adapted to the place it is going to live.

The skill travels. The system around it has to be rebuilt locally.

It helps to separate two things that get bundled together.

The first is the procedure itself: the technique, the safety principles, the sequence of steps. Much of this is genuinely portable, because it rests on anatomy, infection prevention and good clinical practice that do not respect borders.

The second is everything that makes the procedure safe and accountable in a given place: scope of practice, supervision, sign-off, record-keeping, governance, language, context. This part is local by nature. It is shaped by regulation, professional bodies, employer policy and the realities of the health system a learner works in. It is exactly the part a translated course leaves behind, because translating a document changes its words, not its fit.

VeinTrain certificates confirm completion of the stated training. Clinical competency, scope of practice, supervision and authorisation to practise remain with the employer, the local professional body and the relevant governance arrangements in each setting. That principle does not change wherever the training is delivered, and it becomes more important, not less, when a programme crosses into a health system VeinTrain has not worked in before.

Transplantation and transformation are not the same thing

There are two ways to move a training programme into a new setting.

Transplantation takes something built for one health system and drops it into another largely unchanged, translated at most. It is fast, and it is where a lot of international training starts. It also tends to break at exactly the point described above: the skill arrives, the governance it needs to sit inside does not.

Transformation is different. It takes a robust core, something already built, tested and refined, and works with local professionals to make it fit their environment: their regulation, their scope of practice, their language, their patients. The architecture does the heavy lifting. The local partner does the fitting.

VeinTrain works to a sequence for this, and it matters that the sequence has a shape rather than being a single leap from "we have a course" to "you have a course":

Listen. Understand the setting from the people who work in it: the regulatory framework, the scope of practice, the workforce pressures, what has already been tried.

Localise. Adapt materials, language and examples to fit that context, with local clinicians and, where language is a genuine barrier, local speakers reviewing anything that has been translated before it is used.

Co-design. Build the specific programme with local faculty and leadership, not for them. Decisions about supervision, sign-off and delivery sit with people who understand the local governance framework.

Deploy. Deliver the programme, with VeinTrain's architecture doing the structural work and local ownership sitting where it needs to sit: with local competency sign-off.

Observe. Watch what actually happens once people are learning and practising, rather than assuming the plan was right.

Adapt. Change what is not working, based on what was observed, not what was assumed at the start.

Scale. Only once a model has been tested and adapted locally does it make sense to grow it, whether that means more learners, more sites, or handing more of the delivery to local trainers.

This sequence is deliberately cautious about the early stages. VeinTrain does not assume it can design an entire local training system remotely from Nottingham. It assumes the opposite: that a programme has to earn its way into a setting by listening first and scaling last.

What VeinTrain actually builds, and why some of it can be reused

VeinTrain's core asset is not a single course. It is a set of reusable clinical-learning architecture: simulation design, structured learning pathways, e-learning infrastructure, faculty development models, implementation and evaluation tools, and increasingly, a growing body of knowledge about what makes training land safely in a new system.

Some of that development happens because one specific project needs it. A UK trust asks for a dashboard to manage a multi-site rollout. A product partner commissions simulation work around a new device. A digital platform gets rebuilt to support a particular delivery model.

Once that work exists, it does not automatically disappear back into the project that paid for it. A dashboard built for a complex UK rollout may be genuinely useful to a partner managing its own international programme. A piece of simulation development built around one product programme may generate teaching material that works well somewhere else entirely. An improvement to VeinTrain's digital learning platform benefits every learner who uses that platform afterwards, not only the ones the improvement was originally built for.

VeinTrain calls the practical version of this idea development matching: when one project funds something genuinely useful, VeinTrain considers, deliberately and case by case, whether that development can also be adapted or extended to benefit another partner or community. It is not a promise, a scheme, or an automatic transfer. Reuse only happens where VeinTrain has the right and the governance clearance to do it, and it is assessed project by project against contractual and intellectual property constraints, not assumed by default.

It is worth being precise about what this is not. VeinTrain is a specialist training company, not a charitable foundation. It does not operate a grant scheme, and commercial revenue from one client does not automatically become funding for another organisation. Where development matching has actually happened, it happens because a specific piece of reusable infrastructure exists and a specific, governed decision has been made to extend it. Nothing here should be read as implying a particular corporate partner has funded another organisation, unless that has been explicitly agreed and confirmed.

Edna Adan University Hospital: building with, not exporting to

The clearest working example of this model in practice is VeinTrain's partnership with Edna Adan University Hospital in Somaliland (Horn of Africa).

This did not start as an export of a UK course. It started with listening: to Dr Edna Adan Ismail, to the hospital's Dean of Nursing and Dean of Medicine, and to the local team on the ground, about what the hospital actually needed and what its own clinicians already knew. What followed was a blended programme, delivered locally in Hargeisa from December 2025, combining structured e-learning with in-person practical training, built around VeinTrain's HALO architecture and adapted for the setting rather than dropped into it unchanged.

The programme has grown from an initial group of around twenty participants to a wider reach of roughly a hundred clinicians, of whom around two-thirds have been actively supported through a combination of in-person workshops and ongoing digital learning access. Each learner received an individual take-home vein simulator alongside their course access: a small piece of physical infrastructure that learners rated, in follow-up evaluation, as one of the things that mattered most to their confidence and their ability to keep practising after the formal sessions ended.

Twenty-five participants completed a structured evaluation, offered in both English and Somali, at the end of the first delivery phase. The results are worth reporting honestly, including the parts that are not simply positive. The overwhelming majority rated the programme highly and said they would recommend it, and hands-on practical sessions were consistently identified as the most valuable part of the learning. But the same evaluation surfaced a genuine localisation lesson: some participants found the English-language video content difficult to follow. That is not a translation footnote. It is exactly the kind of signal the Listen and Observe stages of this model exist to catch, and VeinTrain's response has been to prioritise Somali-language support for the most-used resources, with any translated material checked by clinicians and Somali speakers before it goes anywhere near a learner.

Participants also described what the training changed in practice. As one put it, hands-on practice was what "helped my confidence the most", and another noted that the programme "helped us correct the mistakes we were making before." That kind of feedback is a better test of whether a programme has transformed rather than simply transplanted than any completion rate on its own.

Faculty development is the next stage of this partnership, and it is honest to say it has not yet begun in earnest. A pathway exists for identifying and supporting local trainers from among the clinicians already trained: confirming baseline skills, working through supervised practice, and building towards a locally authorised trainer role, with assessment and sign-off resting with Edna Adan University Hospital's own clinical leadership throughout. That is deliberate. Capability that is going to last has to end up owned locally, not delivered indefinitely from outside.

Ambitions for the next phase are real but not yet confirmed. VeinTrain and its partners have discussed scaling the programme significantly further as funding and contracting allow, and there is active interest in what a locally led professional network around vascular access practice might look like in time. None of that is a commitment, and none of it should be read as one. What is confirmed is that Edna Adan University Hospital is not a training market VeinTrain has entered. It is a partner VeinTrain is building with, and a partner whose own clinicians are, increasingly, the people best placed to decide what happens next.

Corporate investment, specialist capability, local knowledge

Three kinds of organisation tend to show up around a partnership like this, and each brings something the others do not have.

Large corporates and health systems often have investment capability, products, market reach and social value objectives, alongside their own training requirements. What they typically lack is the specialist clinical-learning architecture to turn intent into a safe, working programme, and the on-the-ground relationships to make sure it fits.

VeinTrain, as a specialist SME, has clinical learning architecture, simulation design, implementation capability and the agility to adapt quickly. What it lacks, deliberately, is local authority: VeinTrain does not run Edna Adan University Hospital's clinical governance, and it should not.

Grassroots and local organisations have exactly what the other two do not: contextual knowledge, trusted relationships, local faculty, and a direct, first-hand understanding of local need. That knowledge does not arrive as a gap to be filled by outsiders. It is the thing that makes the whole model work, because it is what turns architecture into something that actually fits.

The value in connecting these three is not a corporate social responsibility story. It is practical systems design: investment capability, technical architecture and contextual knowledge each doing the part only they can do, coordinated deliberately rather than left to overlap or duplicate each other.

Equity, without overclaiming

Access to clinical education is not evenly distributed, and infrastructure like simulation equipment, structured e-learning platforms and evaluation tools is expensive to build from scratch. Organisations that could not necessarily commission that infrastructure independently should not, on that basis alone, be shut out of using it well.

That is the practical case for connecting development across projects: not because VeinTrain is trying to give something away, but because infrastructure that already exists and could sensibly be reused, is not automatically reused, unless someone is deliberately looking for the connection. Making that connection strengthens local professionals rather than replacing them, avoids VeinTrain quietly rebuilding the same thing three times for three different partners, and leaves capability in the place it was built for, rather than only in VeinTrain's own systems.

None of this is one-directional. VeinTrain's understanding of localisation, and of what "good enough to scale" actually means, has been shaped as much by what Edna Adan University Hospital's clinicians and evaluation data have shown as by anything VeinTrain brought with it. Two-way learning is not a courtesy line here. It is where the language lesson above came from.

One health community, differently placed

Clinicians in very different health systems, from a UK NHS trust to a hospital in Hargeisa, are dealing with a shared set of pressures: patient safety, workforce capability, fast-moving clinical technology, and the ongoing question of how learning is kept current and trusted. The systems around them differ enormously. The underlying challenges rhyme more than they differ.

That is a modest claim, deliberately. It is not a statement about a single global health system, and it is not a claim that VeinTrain, or anyone, has solved unequal access to training. It is a working assumption that shapes how VeinTrain builds: that architecture developed to solve a UK problem is often, with real local adaptation, relevant to a very different setting, and that the traffic runs both ways.

What this means in practice

For a partner considering working with VeinTrain on a programme outside its existing markets, that means asking different questions from "can you deliver our course here?" Useful questions include: what governance framework will local competency sign-off sit inside? Who owns the trainer pathway once the initial delivery ends? What existing VeinTrain architecture could be adapted here rather than built from nothing, and on what terms? And what would VeinTrain, and the partner's own clinicians, need to observe before either side talks about scaling?

VeinTrain is a specialist provider of venepuncture, IV Cannulation and phlebotomy training. What it is building, project by project, is reusable clinical-learning architecture that local partners can adapt, own and eventually lead themselves, rather than a course to be translated and handed over.

Related reading

• Listening to Leadership: Edna Adan, Somaliland and the context behind partnership
• From Goodwill to Structure: What Global Health Partnerships Need to Last
• Why Safe Scale Needs More Than Access to Training Videos

Contact: This email address is being protected from spambots. You need JavaScript enabled to view it.