Portfolio

The LynxMediq portfolio: one direction, shipped one product at a time

LynxMediq is the long-term direction for healthcare software at Pixbots: an archive, a read, a workflow, and AI that share one patient record and one audit trail. It is not a monolith you buy in one go. PixelMediq delivers the imaging core now, and the rest is labelled below.

Explore PixelMediq See the portfolio areas

Portfolio areas

Seven areas, three status labels

The labels are the same ones used on pixbots.com and on the roadmap, so the three never disagree.

Shipping in PixelMediq

Published as available on pixelmediq.com. Each area links to the PixelMediq page that covers it.

Shipping in PixelMediq

Cloud PACS

A cloud DICOM archive with an on-premise edge gateway and a zero-footprint diagnostic viewer, on storage from local disk to AWS HealthImaging.

Explore

Shipping in PixelMediq

RIS workflow

Patients, orders, scheduling, worklists, and templated reporting that carry an exam from the order to a finalized report.

Explore

Shipping in PixelMediq

Interoperability

DICOMweb, HL7 v2.5.1 report export, and FHIR R4 DiagnosticReport today. Inbound HL7 (ADT, ORM), more FHIR resources, and FHIRCast are in development.

Explore

In development

Engineering work is under way. No delivery date is promised.

In development

AI orchestration

AI-assisted findings brought into the read with a physician in the loop. Routing studies across many models is the longer-term goal.

Explore

Roadmap

Planned direction. Not available today, and sequencing can change.

Roadmap

Cardiology

Planned: ECG, echo, and structured cardiac reporting that share the same patient record as the rest of imaging.

Explore

Roadmap

AI marketplace

Planned: a catalog of diagnostic models you can validate on your own studies before you enable them.

Explore

Roadmap

Patient intelligence

Planned: priors, reports, and AI findings on one timeline, so every study is read in the context of the whole patient.

Explore

Current product

PixelMediq

The enterprise imaging product that ships today: a cloud PACS with an on-premise edge gateway, a zero-footprint diagnostic viewer, worklist and orders, reporting, and standards-based interoperability.

You buy, deploy, and run PixelMediq. LynxMediq is the portfolio it belongs to, and there is no second product to purchase alongside it.

See the PixelMediq platform Request a PixelMediq demo

Architecture

Six layers, one data model

The portfolio is designed so a study, its order, its report, and its AI findings stay connected from the moment the study arrives. Four of the six layers ship in PixelMediq today.

Imaging infrastructure

A DICOM archive with DICOMweb access, an on-premise edge gateway, and storage that runs from local disk to AWS HealthImaging. Shipping in PixelMediq

Clinical workflow

Orders, scheduling, worklists, hanging protocols, and templated reporting for radiology. Cardiology workflow is on the roadmap. Shipping in PixelMediq

Interoperability

DICOMweb, HL7 v2.5.1 ORU^R01, and FHIR R4 DiagnosticReport ship today. Inbound HL7 (ADT, ORM), more FHIR resources, and FHIRCast are in development. Shipping in PixelMediq

Enterprise administration

An organization hierarchy, scoped role assignments, tenant isolation, and an append-only audit log for multi-site networks. Shipping in PixelMediq

AI in the read

AI-assisted findings a physician accepts, ignores, or contradicts. Routing across multiple models is the longer-term goal. In development

Patient intelligence

Priors, reports, and findings assembled into a longitudinal record that follows each patient over time. Roadmap

Why one direction

One data model, not five integrations

When imaging, orders, reporting, and AI share a record, you stop paying the interface tax. There is less to break, less to reconcile, and far less context lost between systems. That is the design goal every product in the portfolio is held to.

Design goals for the portfolio

A single archive for radiology and, in time, cardiology imaging
One identity and one set of permissions across every area
Studies, orders, reports, and AI results joined by the accession number
A browser-based viewer with no client software to deploy
One audit trail across the whole patient record
New areas added without a migration project

FAQ

How LynxMediq and PixelMediq relate

What is LynxMediq?

LynxMediq is the healthcare technology portfolio and long-term platform direction of Pixbots Private Limited. It covers imaging, workflow, cardiology, AI, interoperability, and patient context on open standards, and it is delivered one focused product at a time.

What is the difference between LynxMediq and PixelMediq?

PixelMediq is the first focused enterprise product in the LynxMediq portfolio, and the product that ships today. You buy PixelMediq, deploy PixelMediq, and run PixelMediq. LynxMediq describes where the wider portfolio is going.

Can I buy or deploy LynxMediq?

No. LynxMediq is not a second product to purchase alongside PixelMediq, and PixelMediq does not require it. For a product demonstration, pricing, or deployment questions, go to pixelmediq.com.

What do the status labels mean?

Every portfolio area carries one of three labels. "Shipping in PixelMediq" means the capability is published as available on pixelmediq.com. "In development" means engineering work is under way and nothing is promised by a date. "Roadmap" means it is planned direction and is not available today.

Who is behind LynxMediq?

Pixbots Private Limited owns both LynxMediq and PixelMediq. The same team and the same engineering standards sit behind the portfolio and the product.

Evaluate the product, or talk to us about the direction

Product demonstrations, pricing, and deployment questions belong with PixelMediq. Portfolio, roadmap, and partnership conversations come to us here.

Explore PixelMediq Talk to us