POCT1-A2 explained

If your clinic runs point-of-care analysers, you already know the daily friction. A result appears on the device screen, and someone has to read it, write it down, and key it into another system. That manual step is slow, it is easy to mis-key, and it makes a clean audit trail hard to keep. Quality control adds another wrinkle, because if QC results are typed in alongside patient results, the line between a test on a control sample and a test on a person can blur.

POCT1-A2 is the connectivity standard designed to remove that manual step for point-of-care testing. This guide explains, in plain terms, what the standard sets out to do and how Catenix uses it so results flow automatically while quality control stays where it belongs.

Quick answer

POCT1-A2 is a CLSI connectivity standard for point-of-care testing devices. It lets an analyser send its results over the network to a collecting system, identify itself, and receive confirmation that each result was received. It also separates patient results from quality-control results. Catenix speaks this standard through a small on-site gateway, so results are captured automatically, QC is kept separate, and results can be forwarded to the systems your site already runs.

Why point-of-care testing has its own connectivity standard

Central laboratory analysers have used general clinical messaging for years, and those formats work well when a large instrument sits on a network next to a laboratory information system. Point-of-care testing is different. The devices are small, they are often run by clinical staff rather than laboratory scientists, and they may sit in a treatment room, a ward, or a pharmacy rather than a lab. A connectivity approach for these settings needs to handle the device introducing itself, the operator who ran the test, and the difference between a real patient sample and a control sample, all without asking busy staff to configure anything technical.

POCT1-A2 is a standard from CLSI written for exactly this situation. Rather than repurpose messaging built for large lab instruments, it describes a common way for point-of-care devices and the systems that collect their data to talk to one another, so that a device from one manufacturer and a data system from another can be connected without a bespoke integration for every pairing.

How a POCT1-A2 conversation works, in plain terms

At a conceptual level, a POCT1-A2 exchange is a short, structured conversation over the site network. The device starts the conversation. When it has results ready, it reaches out to the receiving system rather than waiting to be polled. Early in that exchange the device identifies itself, so the receiving system knows which analyser, and often which operator, the results came from.

The device then sends its observations, the individual measurements from the test. The receiving system takes them in and acknowledges them, confirming back to the device that each result arrived safely. That acknowledgement matters, because it means the device and the collecting system agree on what was captured, which is the foundation of a reliable record. None of this requires a member of staff to read a screen and type anything by hand.

Patient results and quality control

One useful idea the standard draws out is the distinction between a patient observation and a quality-control observation. A test run on a control sample, to check that the device is working correctly, is not the same thing as a test run on a person, even though the measurement looks similar. The standard provides for a device to signal which kind of observation it is reporting.

This matters for records and for compliance. Quality-control results belong in your QC record, where you can review them, spot trends, and evidence that the device was performing as expected. They do not belong in a patient's clinical record. Keeping the two apart automatically, rather than relying on someone to remember the difference while transcribing, protects both the patient record and your quality documentation.

How Catenix uses POCT1-A2

Catenix speaks POCT1-A2 through a small gateway that runs on-site on your own network. The analyser is pointed at the gateway as its destination, and from then on results are captured as they are produced. There is no screen to read and no figure to key in by hand, so the common source of transcription error is removed.

Because the standard distinguishes control observations from patient observations, Catenix keeps quality control separate from patient results as it captures them. QC data flows into the quality side of the workspace, and patient results are held ready for review. Once captured, results can be forwarded to the systems your site already runs, such as a laboratory information system or an electronic patient record, so the information reaches the right place without a second round of manual entry. A record of what was received and when is kept as part of that flow. You can read more about how information is protected on our security and trust pages.

Getting a device connected

Connecting a point-of-care device that supports POCT1-A2 usually needs three things: an analyser that can send over the network, a place on your local network for the Catenix gateway to run, and agreement on where captured results should be forwarded. Most sites already have the first two. From there the work is configuration rather than custom development, because the point of a shared standard is that connection does not need to be reinvented for each device.

If you are not sure whether a particular analyser offers a POCT1-A2 network interface, its manufacturer's data sheet or connectivity statement is the place to check, and we are happy to help you read it. To talk through connecting your devices, see contact. For a general guide to what a connection costs, see pricing.

Questions clinics ask

Can I connect a POCT1-A2 analyser to my LIS?

Yes, in most cases. Catenix captures results from a POCT1-A2 device through its on-site gateway and can forward them to a laboratory information system or electronic patient record. The exact fit depends on your systems, so it is worth a short conversation. See /contact/ to talk it through.

Do I need to change anything on the analyser itself?

Usually the device just needs to be pointed at the Catenix gateway as its network destination, which is a configuration step rather than a change to how it tests. Most sites keep their existing device settings otherwise. We can help you check what a given analyser supports.

Will quality control results end up in patient records?

No. The standard lets a device flag whether an observation is from a patient or a control sample, and Catenix uses that signal to keep QC data on the quality side, separate from patient results. Your QC record and your patient record stay distinct.

What is the difference between POCT1-A2 and HL7?

HL7 v2 is a broad clinical messaging standard used widely across hospital systems, while POCT1-A2 is written specifically for point-of-care testing devices and how they report results. A site often uses both: the device speaks POCT1-A2 to the gateway, and results are forwarded onward in the format the receiving system expects.

How do we keep an audit trail of results?

Catenix records what was received and when as results are captured, so there is a trail from the device to the workspace. You can read more on our /security/ and /trust/ pages.

How much does it cost to connect our devices?

Pricing depends on your site and how many devices you connect. See /pricing/ for a general guide, or /contact/ to discuss your setup.

Product and company names mentioned are the trademarks of their respective owners. Reference to them is for identification only and does not imply any affiliation with, endorsement by, or certification from those owners. This page describes connectivity and data handling only and is not clinical advice.

Reviewed July 2026. Back to integrations.