RIS workflow
Shipping in PixelMediqRIS workflow: from the order to the finalized report
The operational side of imaging is the second LynxMediq portfolio area to ship. PixelMediq covers it today as a RIS-lite: patients, orders, scheduling, worklists, and reporting. This page summarises what ships and what the portfolio still plans to add.
Available today
The operational backbone of imaging
A summary of what PixelMediq publishes as available for worklists, orders, and reporting. It is a RIS-lite by design, not a hospital information system.
Patients and orders
Patients, orders, and requested procedures are managed in one place, with procedure codes and clinical catalogues.
Scheduling
Exams are scheduled against the order, so the worklist reflects what is booked and what has arrived.
Worklists and assignment
Worklists and assignments put the right studies in front of the right readers, with sub-statuses each tenant can configure.
Matching and reconciliation
Study matching rules tie arriving images to their order, and a reconciliation queue handles the ones that arrive unmatched.
Templated reporting
Versioned report templates, an editor, a finalization lifecycle, a critical result flag, and reproducible PDF export.
Report export
Finalized reports export as HL7 v2.5.1 ORU^R01 and FHIR R4 DiagnosticReport for downstream systems to collect.
From order to report
One workflow, five clear steps
Because the worklist and the archive are the same product, nothing is handed across a seam between systems.
Order
The order is created and carries the accession that ties everything together.
Schedule
The exam is scheduled and appears on the worklist.
Acquire
Images arrive through the edge gateway and are matched to the order by rule.
Read and report
Radiologists read from the worklist and report against a versioned template.
Export
The finalized report exports as HL7 ORU^R01 or FHIR DiagnosticReport.
All five steps ship in PixelMediq. Report export produces the message or resource for a downstream system to collect. PixelMediq does not push it over MLLP or to a FHIR server today, so plan an integration engine where you need delivery.
PixelMediq
Worklists, orders, reconciliation, and structured reporting are documented in full on pixelmediq.com, along with the limits worth knowing before you plan an integration.
You buy, deploy, and run PixelMediq. LynxMediq is the portfolio it belongs to, and there is no second product to purchase alongside it.
Next
Orders and ADT arriving from the EHR
Today orders are created in the worklist. Inbound HL7 v2 is being built so the EHR can place the order and keep the patient record in step. Until PixelMediq publishes it as available, plan around manual or API order entry.
- Inbound HL7 v2 orders (ORM) that create the accession
- Inbound ADT, so patient demographics and merges stay in step
- FHIR R4 Patient and ImagingStudy resources for EHR exchange
Portfolio direction
What the portfolio plans to add to the workflow
These are planned direction for LynxMediq. They are not available in PixelMediq today, and sequencing can change.
- A DICOM modality worklist that drives acquisition
- A portal where referring physicians track status and read reports
- Billing-ready metadata captured without re-keying
- Voice reporting, and LOINC, SNOMED, and CPT coded content
Evaluate the workflow on your own exams
PixelMediq is the product to test. For questions about where the LynxMediq workflow direction goes next, talk to us.