Answers to Common WeHub Integration Questions.

WeHub is an enterprise-grade, healthcare-native integration platform (iPaaS), built to run integrations at organisational scale. More than a workflow tool, it is a suite of products that build, automate, transform, validate and store healthcare data across clinical and operational systems, with HL7, FHIR, ESR and terminology standards as first-class citizens. Adopt one product or the whole platform, hosted by us, in your own tenant, or fully self-hosted.

WeHub is an enterprise solution, built for organisations integrating at scale, with the governance, multi-tenant isolation and access control that scale requires. It suits any healthcare team that needs to connect systems, manage terminology, or work with FHIR: health and care providers, health-tech vendors, and workforce and staffing platforms. Non-specialists can use it directly and engineers can extend it, and it deploys to fit your hosting and data-sovereignty needs.

No. General-purpose tools connect apps but do not understand clinical data. WeHub treats the healthcare standards general tools ignore, such as HL7 v2, FHIR, MLLP and ESR, as first-class, with the transformation, terminology and governance clinical integration needs.

WeHub is built on open standards, so it stays compatible with the systems you already use. WeHub Studio sits between them and works alongside them, so your existing estate keeps running. WeHub Term, WeHub Records and WeHub Proof can upgrade the older tools when you are ready, adopted one at a time, at your own pace.

You do not need to be a developer or a professional to use WeHub. Its products are visual and built to be used without writing code, so what matters most is understanding your own data and systems. Some background knowledge of healthcare data and standards is recommended, and any engineer on your team will pick it up in a blink. WeGuide is on hand to help you get started and as you grow.

One platform, four products. WeHub Studio (visual workflow builder) and WeHub Term (terminology server) are available now; WeHub Proof (healthcare message validator) and WeHub Records (FHIR server) are coming soon. Use the whole stack or just the part you need.

WeHub Studio is the visual, low-code workflow builder at the core of the platform: a drag-and-drop canvas where you chain plugin nodes into data pipelines, with versioning, sub-workflows, import/export and per-workflow alerts. Explore WeHub Studio.

WeHub Term is the terminology server. It manages code systems, value sets and concept maps, including SNOMED CT and ICD-10, so codes stay consistent as data moves between systems. Explore WeHub Term.

WeHub Proof is the healthcare message validator. It validates messages and records against the Implementation Guides, StructureDefinitions, profiles and terminology they must conform to, catching non-conformant data before it reaches a live system. Run it from its own dashboard, via its validation endpoint, or as a gate inside a WeHub Studio workflow.

WeHub Records is the FHIR server. It is a managed FHIR repository with a RESTful API that stores, retrieves, updates and searches FHIR resources, so your systems and apps have one interoperable place to exchange healthcare data.

Today WeHub moves and transforms data rather than storing it. That changes with WeHub Records, our FHIR server: a managed repository that stores and serves FHIR resources, so when you need to persist records, not just route them, you can. Coming soon.

HL7 v2 (parse and produce), FHIR (HL7 v2 to FHIR, C-CDA to FHIR, STU3 to R4), MLLP as a transport for HL7, and ESR for workforce files. ICD-10 and SNOMED CT are handled through WeHub Term.

On the WeHub Studio canvas you chain processor plugins: FHIR conversion, HL7 parsing, JSON handling, conditional routing, string and date operations, and a JavaScript runner for custom logic. Terminology mapping keeps codes consistent. You compose these into pipelines instead of hand-coding each transformation.

HTTP, SFTP and MLLP, plus a Connections module that stores reusable credentials for databases, REST APIs and cloud services. It also ships deep connectors for UK health systems, including ESR, Spine, PDS, e-RS and EPS. Cloud and on-premises both.

Yes. The designer runs test executions against a node’s configuration, and the platform validates schema and data before a workflow touches a live environment. Workflows are versioned (draft versus published), so you validate a version before promoting it live. A dedicated message validator, WeHub Proof, is coming soon.

Failed records are caught, not lost. Monitoring gives you execution history, error drill-down with stack traces and plugin-run tracking. Per-workflow alerts notify the people you choose, so a blocked record does not sit unnoticed.

In a limited way today: AI-assisted summarisation, generation and classification you can use inside a workflow. AI is not the core of the platform. Broader AI capabilities are planned in upcoming updates.

Hosted in the UK (UK South region), with secrets in a managed key vault and each organisation isolated in a multi-tenant model with role-based access. It moves and transforms data rather than storing records, so its data footprint is small. For detail, see the Trust Centre.

It depends how you use it. Data flowing through a workflow is not kept: it passes to its destination and is not retained. If you use WeHub Records, our FHIR server, as a data store, then yes, we hold that data and keep it safe. And with deployment options like WeHub Runner or WeHub Private, your data can stay entirely within your own tenant and infrastructure.

Yes. WeHub Runner is built for exactly this: you design and manage workflows in our cloud, but your data and the processing run inside your own tenant and never leave your infrastructure. It is available on the Azure Marketplace. If you need to go further, WeHub Private is fully self-hosted, so nothing sits outside your environment.

In most deployments WeHub is a data processor, handling data on your instructions while you remain the controller. A DPA is available: see the Trust Centre.

Role-based user management and per-organisation isolation are available today. Single sign-on and enhanced role controls are on the roadmap. For current status, talk to us.

In the UK, in the UK South region. The platform is not multi-region today, so any data it handles stays within UK infrastructure.

WeHub holds Cyber Essentials Plus (certified 17/12/2025, whole-organisation). DSPT, DCB 0129/0160 and ISO 27001 are the target posture. See the Trust Centre for current status.

Three options, all available now. WeHub Cloud is fully hosted by WeHub, the fastest way to start with nothing to maintain. WeHub Runner lets you design in our cloud while it runs in your own environment, so your data never leaves your infrastructure; it deploys from the Azure Marketplace. WeHub Private is fully self-hosted, with nothing leaving your infrastructure and the strongest data sovereignty.

To find out what WeHub would cost for your use, contact us and we will scope pricing around your volumes and setup.

WeHub helps you design and stand up workflows, onboard your team, and keep things running with ongoing support. The team can also scope and deliver integrations alongside you. See the WeDo service or contact us.

Book a call and we will run WeHub against a real integration scenario of yours, then scope the right setup.