Home / Resources
The POCT connectivity field guide.
Plain-English explainers on the standards, systems and quality practices behind connected point-of-care testing (POCT). Written by the people who build the integrations.
Integration guides
The standards, explained plainly.
Every device connection guide and the standards behind them, in one place.
ASTM messaging for point-of-care testing, explainedASTM E1381 and E1394 are an older, serial-oriented way analysers send results. See how it works and how Catenix brings serial devices into one workspace.
HL7 v2 for POCT: a plain-English field guideA plain-English guide to HL7 v2 result messaging for point-of-care testing: what it carries, how it travels, why device dialects differ, and how Catenix helps.
Sending POCT results into your LIS or EHRLearn how Catenix forwards captured point-of-care results to your LIS or EHR over HL7 or FHIR, tracks every message, and keeps quality-control runs separate.
POCT1-A2 explainedPOCT1-A2 is a connectivity standard for point-of-care analysers. Learn how it works in plain terms and how Catenix captures results while keeping QC separate.
Foundations
What is POCT connectivity?
Why point-of-care results so often get stranded, and what a connectivity layer actually does about it.
FoundationsWhat is POCT middleware?
The category, explained: what sits between your analysers and your records, and what it should be doing for you.
FoundationsCatenix vs other platforms
Honest, side-by-side comparisons against TELCOR QML, Relaymed, Abbott AegisPOC and Siemens POCcelerator, plus a map of the alternatives.
Buyer guidesComparing POCT middleware
A factual framework for weighing platforms: deployment model, protocol coverage, quality workflows and data residency.
Buying guideBuying & how-to guides
Point-of-care testing software
A buyer's guide: what POCT software does, what to look for, and the questions worth asking any vendor.
Buying guidePOCT software for private clinics
From booking to result to invoice: what one connected workflow looks like in a private clinic day.
ClinicsQC software for POCT devices
Automatic QC capture, Levey-Jennings charts, Westgard rules and lockout: QC off paper and audit-ready.
QualityConnect an analyser to your LIS
The options, the protocols in plain English, what to check before you start, and honest timelines.
How-toOccupational health screening software
High volumes, corporate clients and chain of custody: screening from booking to the corporate report.
Occupational healthManaging POCT across sites
One central view of every site, device, operator and QC record, for coordinators covering several locations.
Multi-siteStandards & quality
HL7 vs POCT1-A2 vs ASTM
The three protocols that move diagnostic results, what each is for, and how to tell which your analyser speaks.
StandardsISO 15189 and POCT
What the medical-laboratory quality standard asks of point-of-care testing, and where connected data carries the evidence.
ComplianceLevey-Jennings & Westgard rules
The statistics behind QC monitoring: how control charts and multi-rule criteria make drift and outliers visible.
QualityDownloads
The POCT Connectivity Buyer's Guide
Nine pages on how results actually reach the record, the standards in plain English, and eight questions to ask any supplier. PDF, no form.
Free PDFConnectivity & quality readiness checklist
Six sections from devices to governance, each item naming the evidence an assessor tends to ask for. Print it and work through it as a team.
Free PDFWhat disconnected POCT costs you
Four inputs, one number: re-keying time, error rework, QC admin and tests that never reach an invoice. Fill in your own figures.
Free PDFAll three open straight from the downloads page. No email address, no gate.
Reference
The cost of disconnected POCT
Building the business case: where transcription, paper-chasing and re-keying quietly consume staff time.
OperationsThe POCT & connectivity glossary
From accession number to Westgard rules: the vocabulary of connected point-of-care testing, defined.
GlossaryThe Catenix API
A developer-facing overview of integrating with the platform programmatically.
DevelopersWant us to cover a specific device, standard or workflow? Tell us.