Clinical use case
We match the model to the clinical question, protocol and output the radiologist needs. The department’s needs are the starting point.
We are developing a platform that gives a department access to AI models from several vendors through a single PACS/RIS connection. The model is matched to the clinical use case, while integration, billing and support stay with one partner.
01
Model choice
02
One integration
03
Shared billing
04
One point of support
01Why a platform
One connection instead of a separate integration for every model.
Every model bought separately means a separate integration, a separate contract, separate support and separate billing. The platform brings these together and leaves the choice of tool with the department.
No dependence on a single model vendor
A model can be replaced by another, or two can run in parallel and be compared on the same material.
Migration without a new integration
A model change reuses the existing PACS/RIS connection. We verify the new model's compatibility and how its result is presented.
One invoice and one view of cost
Models covered by the service are billed together. The facility sees the cost of its whole AI portfolio in one place instead of settling separately with each vendor.
One point of support
Tickets, integration and escalation sit with QuantumMed. The facility does not coordinate several vendors to establish who handles a problem.
The freedom of choice concerns the model vendor within the platform. We do not promise migrating the integration away from QuantumMed.
02Workflow
The study leaves PACS and returns to PACS.
Department environmentPACS/RISThe same connection
One integrationQuantumMedSelection and result checks
Selected model A
Changing the model reuses the same PACS/RIS connection. Model compatibility and result presentation must be verified.
The radiologist works in their own environment. The platform routes the study to the selected model and the result returns to the department's workflow. Every stage has execution conditions and error handling.
Workflow
- Input
- The team agrees the study type, protocol and data scope. The selected data must match the model's intended purpose.
- Analysis and check
- The selected model returns annotations, measurements or a report in an agreed format, carrying the study identifier.
- Result returned
- The result lands where the radiologist reports the study. An incomplete result or a mismatched identifier stops it from being attached.
The team is notified when an analysis was not performed or the model vendor is unavailable.
X-ray
Orthopaedics
Measurements on the image
Angles and distances prepared for the radiologist to review.
CT
Lungs
Marked findings
Areas flagged for attention when reporting the study.
MRI
Neuro-oncology
Quantitative maps
Perfusion parameters shown alongside the anatomical image.
03Model selection
Selection starts with the use case.
We are building a portfolio around the needs of the department. Selection considers the model’s intended purpose, the vendor’s documentation, data processing conditions and review of the output in the radiologist’s environment.
Vendor documentation
We check the CE marking, intended purpose and vendor documentation for the specific model. QuantumMed does not certify models.
Processing conditions
Before a pilot we agree the data scope, processing location, responsibilities and rules for returning the result.
Department assessment
We agree the evaluation criteria and material with the team. We check the completeness of the result, its readability in PACS/RIS and exception handling.
05The next step
Let's start with one use case.
For a first conversation we need one study type, what the team needs and which PACS/RIS is in place. Together we will define which result is worth checking, which conditions must be met and who should take part in the assessment.
info@quantummed.euMaterials for your team
You can email us to request a short scope overview or sources for a discussion of regulations.
Request a scope overviewRequest sources: GDPR and EHDS06Team
Two founders. One team.
QuantumMed sp. z o.o. is a Polish company founded by Sylwester Cyrwus and Krzysztof Bokiej. We connect discussions about applications with responsibility for the technical scope.
Sylwester Cyrwus
CEO and co-founder
Leads conversations about healthcare organisations, technology use cases and collaboration. Connects organisational needs with a practical scope of work.
Krzysztof Bokiej
CTO and co-founder
Responsible for architecture and technical evaluation. Defines integration boundaries, dependencies and the evidence needed to establish how a solution works.