WeHub Studio

Design it, test it, ship it

The visual workflow builder for data integrations. Build a flow on a canvas, connect your systems, test it end to end, and ship it to production.

Get it onMicrosoft Marketplace

Design

Start on a blank canvas

Design the flow visually, version it safely, and carry it between environments.

Data modelling

Reusable, versioned models that validate inputs and outputs.

Release management

Draft, publish, and keep one version live at a time.

Portability

Export any workflow as a file and import it anywhere.

Triggers

Start with a trigger

Every workflow has one trigger: the entry point that starts a run the moment data arrives. Wire processors and integrations behind it, and the flow begins.

Plugins

Build the pipeline

Connect plugins on the canvas and watch a workflow take shape, no integration code.

Triggers

Start a workflow on an incoming event.

Processors

Transform and route data in flight.

Integrations

Read from and write to external systems.

Test

Test before it runs live

Send a sample payload through the workflow and check the output of every node success, failed or skipped before anything reaches a live system.

Monitor

Then watch it in production

Follow every live workflow from one view.

Execution history

Every run of every workflow, on record.

Failure diagnostics

Open any failed run for logs and stack traces.

Consumption tracking

Plugin-run usage against your daily quota.

Deploy

Go Live

Promote a workflow to a published version when it's ready one version live at a time and keep the right people informed.

Promote to live

Push a draft to a published version in one step.

Deployment flexibility

Run workflows on WeHub's environments or your own.

See WeHub Runner →

Alerts

Per-version alerts at the intervals you choose.

RunnerUK South · Private
Add your first pluginStart with a trigger, then wire processors and integrations onto the canvas.
HL7 ListenerLab Results (ORU_R01)
TRIGGER
LIS MLLP PROD2575
Ack by workflow successAA
Map HL7 → FHIRFlatten + Normalise
PROCESSOR
DiagnosticReportR4
Terminology mappedok
FHIR Push → EPRDiagnosticReport.create
INTEGRATION
EPR FHIR API PRODPUT
Retry on 5xx×3
Connection refused502
Notify MS TeamsPathology channel
APP
Adaptive cardon

Run History

Illustrative sample data

Lab Results Notifications · last 24 hours · 1,284 executions

99.4%
Success
312ms
p95
7
Failed
RunTriggerStatusDurationStarted
run_8f3a2cMLLPSucceeded286 ms2 min ago
run_8f3a1bMLLPRunningnow
run_8f39e7MLLPSucceeded301 ms6 min ago
run_8f39c0MLLPCompleted512 ms11 min ago
run_8f3942MLLPFailed1.2 s22 min ago
run_8f3901MLLPSucceeded268 ms28 min ago

Deploy

Run Studio where your data lives

Same canvas and the same plugins in each.

Your Azure tenant

Runner

Inside your own Azure tenant. Data never leaves.

See the footprint
Air-gapped · HSCN

Self Hosted

Your infrastructure, air-gapped or HSCN.

See the footprint

FAQ

Common questions

WeHub Studio is a visual, low-code workflow builder for healthcare data integrations. You build a flow on a canvas from a trigger, processors and integrations, connect your systems, test it end to end with a sample payload, then publish it to production.

For most workflows, no. You connect plugins on the canvas instead of writing integration code, and reusable data models validate the inputs and outputs. When a step needs custom logic, a JavaScript processor runs your own script inside the workflow.

Studio parses and produces HL7 v2, converts HL7 v2 and C-CDA to FHIR, and upgrades FHIR STU3 resources to R4. It also processes ESR files, CSV and JSON, and connects to external systems over HTTP and SFTP.

Send a sample payload through the workflow and check the output of every node. Each node is marked success, failed or skipped, so you can see exactly where a run stops and fix it before anything reaches a live system.

Each workflow has a draft and one published version. You edit and test the draft, then promote it to published in one step, and only one version is live at a time. Any workflow can be exported as a file and imported into another environment.

On WeHub’s environments or your own. Managed runs on Azure in the UK, with UK data residency (UK South) and per-customer tenant isolation. Runner deploys into your own Azure tenant from Microsoft Marketplace, so payloads stay within your boundary. Self Hosted runs on your own infrastructure.

More answers in the WeHub FAQ

Ready when you are

See Studio on your own systems.

We'll stand up a working Studio environment in the infrastructure your data has to stay in.