Skip to content

LIS and Laboratory Systems

Status 11.09.2026. The LIS connection is built and in use, per site — CLSI LIS 1-A and LIS 2-A over TCP/IP, implemented per laboratory; there is not yet one shared implementation across laboratories. What is still missing is this page: the protocol description on the portal is planned and not written. The authoritative line is Laboratory — LIS connection on Integration Status.

What is built, what is planned

State on 11.09.2026
Protocol family CLSI LIS 1-A and LIS 2-A over TCP/IP — built
Implementation Per laboratory. Each site has its own connection; a second site cannot simply point at the first one. Not yet one shared implementation.
Reachable through uGo+ Yes, per site (Integration Status)
Interface specification Exists as a document, uGo LIS Connection, EN, for tenders and integration projects — see uGo+ — Documents. One common base document; site-specific parts are hooked in per site and are not published.
Which parts of LIS 1-A / LIS 2-A are implemented (message types, mandatory fields, character set) to be confirmed — not described in any source read for this portal
Who opens and holds the connection, what happens on a break to be confirmed
What is actually identical between the laboratories to be confirmed — never laid side by side
A test path against a LIS without live operation to be confirmed — not documented
This page: the protocol description (three message types, segment structure, sequence diagrams) planned, stage 3 — needs agreement with the ugo-plus teams first

Nothing on this page names a protocol beyond the two the platform is documented to speak. A sentence such as "we speak LIS 2-A" is enough to start a conversation with a partner; it is not yet enough to build against — the open lines above say why.

In preparation

This section has a page and no protocol content yet. That is deliberate: an empty page in the navigation shows the gap, a missing page hides it.

What will go here: the CLSI LIS 1-A and LIS 2-A message protocol over TCP/IP: the three message types, the segment structure, and the sequence diagrams. The protocol, not any laboratory's field layout — see Contributing.

Where the material is today: two documents that have drifted apart: ugo-plus/control/lis-specification (LaTeX, Rev. 03, authoritative for the field structure) and ugo-plus/middleware-connectivity (MkDocs, unchanged since 14.11.2024, but holds 15 sequence scenarios and four coding tables the other one lacks).

Planned for: stage 3 — and it needs agreement with the ugo-plus teams first.