Catenix: Lab Analyzer & EHR Connectivity
Server Details
Check if a lab or point-of-care analyzer connects to your EHR or LIS, how, and plan the lab setup.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 13 tools
Most tools have clearly distinct jobs (decode a message, check Westgard rules, estimate time saved, fetch an inspection checklist). There is real overlap in the advisory cluster — check_connectivity, get_ehr_integration, plan_lab_setup and recommend_lab_setup all answer 'how do I connect X to Y', distinguished mainly by single-vs-multi analyzer and analyzer-vs-software framing. compare_options, vendor_questions and recommend_lab_setup also shade into each other, but the example phrasings in each description give an agent enough cues to choose correctly.
The dominant pattern is verb_noun (check_connectivity, decode_lab_message, estimate_time_saved, get_ehr_integration, plan_lab_setup, recommend_lab_setup, search_analyzers, request_demo). Two names break the pattern by being noun-only (inspection_checklist, vendor_questions), and check_qc_westgard mixes a domain term into the verb_noun form, but overall the set reads consistently.
13 tools is squarely in the well-scoped range for a lab-connectivity advisory server. Each tool maps to a distinct user intent (discovery, connectivity, planning, QC, message decoding, compliance, comparison, estimation, contact), and none looks like filler.
The surface covers discovery (search_analyzers), point and plan connectivity, EHR routing, QC statistics, message decoding, platform capability, competitive comparison, inspection readiness and vendor due diligence, plus a demo handoff — a coherent end-to-end advisory lifecycle. Minor gaps remain: no per-analyzer detail/protocol lookup beyond search results, no way to follow up on an ambiguous or unmatched analyzer/system pair, and no result-interpretation or troubleshooting-escalation path beyond decoding.
Available Tools
13 toolscheck_connectivityCheck if a lab analyzer connects to an EHR or LISARead-onlyIdempotentInspect
Use when someone asks whether a lab or point-of-care analyzer will connect to their EHR, LIS or practice system, or how to get analyzer results into the patient record without retyping (e.g. 'will my Sysmex XP-300 work with athenahealth?', 'connect Abbott i-STAT to Epic', 'Roche cobas b 101 to SystmOne', 'Siemens CLINITEK to EMIS', 'Tosoh AIA-900 to eClinicalWorks'). Fuzzy-matches the analyzer and the record system and returns: connection status (live, driver built, connectable via standard protocol with a published guide, or custom driver needed), the analyzer protocol (HL7 v2, ASTM, POCT1-A2), the physical link, how results pass through an on-site gateway, the record-system route, what is needed on site, questions to ask any vendor, and page links. Works for unknown analyzers too. Does not interpret results.
Inputs: analyzer (required), ehr, country.
check_qc_westgardCheck lab QC values against Westgard rulesARead-onlyIdempotentInspect
Use when someone has quality control (QC) results for a lab or point-of-care test and wants to know whether they break Westgard rules or how they look on a Levey-Jennings chart (e.g. 'do these control values fail any Westgard rules?', 'check my QC: mean 5.0, SD 0.1, values ...', 'is this a 2-2s or 4-1s violation?'). Takes control values in run order plus the target mean and SD (or computes them from the values if the user asks) and evaluates 1-2s (warning), 1-3s, 2-2s, R-4s, 4-1s and 10x. Returns z-scores, the rule hits for each point and a plain summary, and draws a Levey-Jennings chart in ChatGPT and Claude. Up to 500 values. QC statistics only: not a clinical interpretation of any patient result.
Inputs: values (required), sd, mean, level, +3 more.
compare_optionsCompare LIS vs POCT middleware, or Catenix vs another productARead-onlyIdempotentInspect
Use when someone asks whether they need a LIS or POCT middleware, the difference between them, or how Catenix compares with another point-of-care data manager or results connector (Relaymed, TELCOR QML, Abbott RALS or AegisPOC, Siemens POCcelerator, Radiometer AQURE, Roche navify POC Operations, Clinisys POCT, paper or spreadsheet lab logs). Returns only what the published comparison pages say. Allowed values: catenix_vs_abbott_aegispoc, catenix_vs_abbott_rals, catenix_vs_clinisys_poct, catenix_vs_lab_logs, catenix_vs_radiometer_aqure, catenix_vs_relaymed, catenix_vs_roche_navify_poc_operations, catenix_vs_siemens_poccelerator, catenix_vs_telcor_qml, poct_middleware_alternatives, lis_vs_middleware.
Inputs: kind (required).
decode_lab_messageDecode an HL7, ASTM or POCT1-A2 lab messageARead-onlyIdempotentInspect
Use when someone pastes a message from a lab analyzer, LIS, middleware or EHR interface and wants to know what it says, what a field means, or why the receiving system rejects it (e.g. 'what does this HL7 ORU mean?', 'why is my EHR rejecting this result message?', 'decode this ASTM output from my analyzer', 'is this POCT1-A2 OBS message valid?'). Accepts HL7 v2 (ORU, ORM, ACK, ADT and others), ASTM E1394 / LIS2-A2 records (H, P, O, R, C, Q, L, with or without E1381 framing and checksums) and POCT1-A2 XML. Returns a field-by-field breakdown (segment or record, field number, name, value, meaning, what an EHR or LIS usually expects) and flags common problems: wrong delimiters or segment terminators, missing MSH-9 or OBX-3 codes, numeric results without units, non-standard abnormal flags, non-LOINC codes, bad checksums. Likely patient identifiers (HL7 PID-3, PID-5, PID-7, PID-11, PID-13 and similar, ASTM patient ID, name and birthdate, POCT1-A2 patient elements) are masked in the output. Tell the user to paste only test or de-identified messages. Nothing is stored or logged. Does not interpret results.
Inputs: message (required), format.
estimate_time_savedEstimate time spent retyping lab resultsARead-onlyIdempotentInspect
Use when someone wants to know how much staff time manual entry of analyzer results costs them, or would be saved by connecting analyzers to the EHR or LIS (e.g. 'we run 80 tests a day and typing each result takes 2 minutes, how much time is that?', 'is it worth interfacing our analyzers?'). Uses only the user's own numbers (tests per day, minutes of manual entry per result, sites, optionally results per test, working days and their own error rate) and returns hours per day, month and year and entries not retyped. Adds no benchmarks, prices or error statistics; without an error rate from the user it makes no error estimate.
Inputs: tests_per_day (required), minutes_per_result (required), sites, results_per_test, +3 more.
get_ehr_integrationHow lab results get into an EHR or practice systemARead-onlyIdempotentInspect
Use when someone asks how in-house lab or point-of-care results can be sent into a specific EHR, EMR, EPR, LIS or practice-management system, or whether a lab interface exists for it (e.g. athenahealth, eClinicalWorks, Epic, Oracle Health/Cerner, NextGen, Experity, Tebra/Kareo, SystmOne, EMIS Web, MEDITECH). Returns the route (HL7 v2, FHIR R4 or vendor API), how far that route is proven, what the practice must request from its vendor, and the guide link.
Inputs: ehr (required), country.
get_platform_capabilityLab QC, compliance and clinic software featuresARead-onlyIdempotentInspect
Use when someone asks about software for lab quality control and compliance or running a testing clinic: QC with Westgard rules and Levey-Jennings charts, QC lockout, operator competency, EQA or proficiency testing, audit trail, CLIA, CAP or ISO 15189 readiness, reagent lot tracking, equipment maintenance and temperature logs, multi-site oversight, patient registration, reports, billing, or HL7/ASTM/POCT1-A2 interfaces. Returns the matching modules, whether each is included or an add-on, and links.
Inputs: topic (required).
inspection_checklistLab inspection readiness checklist (CLIA, CAP, ISO 15189, UK POCT)ARead-onlyIdempotentInspect
Use when someone is preparing a lab or point-of-care testing service for an inspection or accreditation and wants to know what inspectors look for (e.g. 'what do I need for a CLIA inspection?', 'CAP checklist for QC and competency', 'ISO 15189:2022 readiness', 'UK POCT governance checklist'). Returns a practical checklist (quality control, competency, EQA or proficiency testing, document control, audit trail, result reporting, equipment) with the evidence usually asked for, and which Catenix module keeps those records. General guidance, not legal or regulatory advice.
Inputs: framework (required).
plan_lab_setupPlan connecting several lab analyzers to an EHR or LISARead-onlyIdempotentInspect
Use when someone lists the analyzers in their lab or clinic and wants a plan for getting all their results into their EHR, LIS or practice system (e.g. 'we have a Sysmex XP-300, an i-STAT and an Afinion 2, how do we connect them to athenahealth?', 'plan the interfaces for our new urgent care lab', 'what do I need on site to connect these analyzers?'). Returns one plan: per analyzer the connection status (Driver built, Connection guide, or Catenix builds the driver, usually within a couple of days), the physical link (serial, network, USB or vendor software), protocol and what is needed on site; the on-site gateway and record-system route; patient matching; and a step-by-step go-live checklist. Renders an interactive Lab Map in ChatGPT and Claude. Does not interpret results.
Inputs: analyzers (required), ehr, country, setting.
recommend_lab_setupRecommend lab or clinic testing software setupARead-onlyIdempotentInspect
Use when someone asks what LIS, LIMS or point-of-care testing software a small lab, clinic, urgent care, occupational health provider, pharmacy, GP practice, physician office or wellness clinic should use, or how to set up analyzer connectivity, QC and reporting for their setting (e.g. 'what LIS should my small lab use?', 'do I need a LIS to get analyzer results into my EHR?', 'software for a clinic that tests blood on site'). Returns the usual architecture for that setting, the modules that fit (connectivity, QC with Westgard rules and lockout, operator competency, EQA, audit trail, reports, billing, multi-site), status of each listed analyzer, the record-system route, how setup works, what is needed on site, the pricing model (no prices are quoted), and questions to ask any vendor.
Inputs: setting (required), ehr, country, analyzers.
request_demoRequest a Catenix demoAInspect
Sends the user's demo request to the Catenix team by email; the team replies to the address the user gives. This is the only tool that shares the user's personal details. Before calling it you MUST show the user every field you will send (name, email, organisation, country, analyzers, record system, message) and get their explicit confirmation in this conversation; then set user_confirmed to true. Never call it on your own initiative. The Catenix widget may call it only after it has shown the user every field and the user pressed Confirm and send. Do not guess missing fields: ask for them.
Inputs: ehr (required), name (required), email (required), country (required), +4 more.
search_analyzersSearch connectable lab and point-of-care analyzersARead-onlyIdempotentInspect
Use when someone wants to know which lab or point-of-care analyzers can be interfaced, or browses by maker or test type (e.g. 'which HbA1c analyzers can connect to an EHR?', 'Abbott analyzers with an HL7 interface', 'blood gas analyzers with LIS connectivity', 'Sysmex hematology', 'Roche cobas', 'Siemens', 'Tosoh'). Returns matching analyzers with connection status, protocol and guide links. Categories: chemistry, immunoassay, blood gas, molecular, haematology, urinalysis, coagulation, HbA1c.
Inputs: limit, query, status, category, +1 more.
vendor_questionsQuestions to ask when buying a LIS, middleware or lab interfaceARead-onlyIdempotentInspect
Use when someone is choosing or buying a LIS, LIMS, POCT middleware or an analyzer-to-EHR interface and wants an RFP or a list of questions to ask vendors (e.g. 'what should I ask LIS vendors?', 'RFP questions for lab middleware', 'checklist for buying an HL7 interface'). Returns a copyable, vendor-neutral checklist grouped by connectivity, QC and compliance, security and privacy, data and audit trail, implementation and support, pricing, and contract and exit.
Inputs: buying, groups.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Telehealth support for Claude, Codex and Cursor: investigate cases and connect your tools.
Read-only U.S. lab-test catalog, collection-site search, and reference-range context.
Turn any LLM into your lab assistant: search samples, track experiments, analyze data with AI.
Your labs, wearables, DNA and notes as one health record your AI agent can read (OAuth 2.1).
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables ingestion of HL7 v2, ASTM, and JSON control results, Westgard multirule evaluation, automatic patient-result holds, explainable root-cause investigation, and supervisor-approved CAPA workflows for clinical laboratories. Agents can also establish targets, compute Levey-Jennings and sigma statistics, and verify corrective actions before a supervisor lifts a hold.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceIntegrates with EMRs like Cerner and Epic via FHIR to retrieve patient data, and provides medical research tools (PubMed, clinical trials, FDA) for clinical analysis.1MIT
- FlicenseAqualityCmaintenanceEnables an MCP host to search patients, review latest laboratory results, compare values over time, record new results, and manage pending exams using a local SQLite database with synthetic clinic data.6-
- FlicenseNot gradedqualityAmaintenanceEnables LLM-based agents to connect to a FHIR-compliant healthcare backend and query or manipulate clinical data with natural-language prompts. Provides full CRUD operations on FHIR resources, AI-powered document ingestion and semantic search, RAG-ready retrieval, and LOINC terminology lookup.-
Glama MCP Gateway
Add one secure layer between your agents and this server.