Implementation: live in days, not quarters.

Connectivity projects earned their bad reputation honestly: bespoke interfaces, protocol consultants, quarters of calendar time. Catenix was built to make that whole category of project unnecessary. Here is the actual implementation, step by step.

The four-step implementation

1 — Install

The Catenix edge gateway installs on a standard clinic PC near the bench. It is signed and self-updating — once it is in, you never manage versions again. It runs quietly alongside everyday work and buffers results through brief network outages, so a flaky connection does not become a missing result.

2 — Point

Connect each analyser to the gateway over TCP or serial. The gateway auto-detects HL7, POCT-1A and ASTM on the wire, so there is no protocol configuration to hand-write and no interface specification to commission. Drivers for supported analysers are part of the platform — adding a device is configuration, not a project. The detail of how this works lives in the device connectivity module, and in our plain-English guide to HL7, POCT-1A and ASTM.

3 — Confirm

This is the step that replaces a sign-off meeting. Run a sample, then trace that first result end-to-end on the wire-level audit: the exact message the analyser transmitted, the normalised result, the operator it is attributed to, the record it landed in. When you can see your own result's full lineage on screen, the integration is not "probably working" — it is demonstrated.

4 — Go live

With the wire proven, the rest is setup, not engineering: enrol operators with their own logins, define QC schedules for statistical data-quality monitoring, and choose report templates for your service. Then start testing for real, on day one of go-live rather than month six.

How long it really takes

Honest time bands, not a project plan: most supported analysers connect within days, and a multi-site rollout is typically measured in weeks, not quarters. The variables are the ones you would expect — how many sites, how many device types, and how much rollout support you want — and they are scoped openly with your quote. See how pricing works for how implementation is costed.

What we need from you

The complete list, in full:

• A PC near the bench — a standard clinic machine for the edge gateway.
• Network details — how the bench PC reaches the analysers and the internet.
• Your device list — make and model of each analyser you want connected.
• An hour of a lead operator's time — to walk the workflow and confirm the first traced result.

Training and support

Training happens on your own bench, with your own devices and your first real results — not in a classroom against a demo dataset. We focus on the lead operator first, because a confident lead operator trains a clinic better than any manual; written guidance covers the rest of the team. After go-live, support is included in the subscription, and because the gateway is self-updating, improvements arrive without another visit or another invoice.