EKLIS.CLIENT REPORT
04 · CONNECTIVITY

Connected in every direction

Analyzers, EHRs, reference labs, public health, and payers — all through one interface engine that keeps receiving even while the application deploys.

EKLIS secure multi-tenant cloud · US-hosted every access audited Physicians & clinics Patients & consumers Analyzers EHR / EMR systems Reference labs Payers & clearinghouse portal · orders · reports results · self-ordering chemistry · heme · coag HL7 v2 · FHIR R4 two-way send-outs eligibility · clean claims orders in / results back results / DTC orders direct interface standard feeds route & repatriate verify & submit
Standards, not toll booths. Analyzer connections use the protocols instruments already speak (ASTM, HL7). EHR connections use HL7 v2 today and a FHIR R4 API as it rolls out — integrations are configuration, not custom projects. Reference-lab send-outs work in both directions.

Standards & protocols

ChannelStandardUsePhase
AnalyzersASTM E1381 / E1394 (CLSI LIS1/LIS2)Bench chemistry, hematology, coagulation — TCP and serial-over-TCP; host-query and batch-download modesP2
Analyzers (newer)HL7 v2 ORU over MLLPInstruments that speak HL7 nativelyP2
Point-of-carePOCT1-AGlucose meters, blood gas deviceslater
EHR / EMRHL7 v2.5.1 — ORM/OML in, ORU out, ADT in, ACKOrder and result feeds with practice systems (the industry workhorse)P2
Public APIFHIR R4 (US Core: ServiceRequest, Specimen, Observation, DiagnosticReport) + SMART-on-FHIR OAuth2Modern integrations, apps, EHR marketplacesP4
Reference labsHL7 v2 + PDFSend-outs in both directions — route tests out, or receive orders as the performing labP2–P3
Public healthELR — HL7 v2.5.1 ORU with LOINC + SNOMEDReportable-condition feeds to state health departmentsP4
DocumentsPDF · fax · printFirst-class delivery — lab clients still live on paper reports and faxed requisitionsP1

Coding standards

LOINC

Orders and results — the test compendium is LOINC-coded from day one.

SNOMED CT

Organisms, specimen types, coded pathology values.

CPT / HCPCS · ICD-10-CM

Billing codes and diagnoses for medical-necessity checking.

UCUM

Units of measure, so results exchange without ambiguity.

Interface engine guarantees

Never down during deploys

The engine runs as its own process: application releases ship continuously while analyzer and EHR connections stay up.

No message ever dropped

Inbound traffic is acknowledged into a durable message log before processing, with replay tooling for recovery and interface validation evidence.

Authenticated machine channels

Every analyzer, feed, and partner connection authenticates with per-interface credentials; an unset credential means the interface is disabled — never open.