Interoperability
Shipping in PixelMediqInteroperability, standard by standard, with a status on each
An imaging system is only as good as its connections. The LynxMediq portfolio is built on open standards, and PixelMediq ships the first set today. This page lists each standard with its status, so an integration plan is never written around something that is not there yet.
Available today
What PixelMediq speaks now
A summary of the surface PixelMediq publishes as available. Query and retrieve run over DICOMweb, and report export produces HL7 and FHIR output for a downstream system to collect.
DICOM
Storage and verification from the modality: C-STORE SCP and C-ECHO at the on-premise edge gateway.
Shipping in PixelMediqDICOMweb
QIDO-RS, WADO-RS, and STOW-RS for web-native query, retrieve, and store.
Shipping in PixelMediqHL7 v2.5.1 ORU^R01
Finalized reports exported as HL7 v2 result messages.
Shipping in PixelMediqFHIR R4 DiagnosticReport
Finalized reports exported as FHIR R4 DiagnosticReport resources.
Shipping in PixelMediqDICOM SR
Structured report rendering and TID 1500 measurement reports.
Shipping in PixelMediqPixelMediq
PixelMediq lists every protocol with its status, names the services it does not provide, and publishes its DICOM conformance statement in full.
You buy, deploy, and run PixelMediq. LynxMediq is the portfolio it belongs to, and there is no second product to purchase alongside it.
Next
Full HL7, FHIR, and FHIRCast support is being built
The goal is a complete two-way surface: orders and patient administration coming in over HL7 v2, imaging and patient resources over FHIR R4, and FHIRCast keeping applications in the same patient context. Engineering work is under way. Until PixelMediq publishes each one as available, plan integrations against the list above.
Inbound HL7 v2 (ADT, ORM)
Receiving orders and patient administration messages from hospital systems.
In developmentFHIR R4 ImagingStudy and Patient
Imaging and patient resources for EHR exchange beyond report export.
In developmentFHIRCast
Keeping the viewer, reporting, and EHR in the same patient context in real time.
In developmentPortfolio direction
What the portfolio plans to add after that
These are planned direction for LynxMediq. They are not available today, and no IHE integration statement is published.
IHE AI Results
Returning AI findings as DICOM SR, SEG, and presentation states for clinical review.
RoadmapSMART on FHIR
Launching the viewer from inside the EHR with OAuth2 single sign-on.
RoadmapIHE profiles
XDS-I.b, PIX, PDQ, and Scheduled Workflow for cross-enterprise imaging.
RoadmapAPI-first
An open platform, not a walled garden
The principle holds across the portfolio: your archive is yours. Studies stay in open formats, and a compliant viewer or system can read them through DICOMweb without going through us.
Shipping in PixelMediq
- DICOMweb access for any compliant viewer or application
- Versioned REST APIs over JSON for integrators
- Finalized reports as HL7 v2.5.1 ORU^R01 and FHIR R4 DiagnosticReport
In development
- Inbound HL7 v2 interfaces for orders (ORM) and ADT
- FHIR R4 ImagingStudy and Patient resources
- FHIRCast to keep applications in the same patient context
Plan the integration against what ships
PixelMediq publishes the full protocol surface and its limits. Tell us which roadmap standard matters to your sites and we will share where it sits.