Bring imaging into the clinical conversation.
A planned imaging pathway connecting requests, scheduling, reporting and access to the right study.
Explore the story
Medrella roadmap. This experience is being planned; scope and readiness will be demonstrated before implementation.
What this workflow connects.
The scope below guides discovery and demonstration. This capability is on the Medrella roadmap.
- 01
Imaging requests and appointment preparation
- 02
Modality worklists and study identity
- 03
Reporting, review and amendments
- 04
PACS and image-viewing integration scope
- 05
Report release and clinician access
Images need a dependable clinical context
An imaging study becomes useful when the requesting clinician can find the correct report and understand the context in which it was produced. Scheduling, image storage and reporting often belong to different systems.
Medrella's imaging direction is to connect that journey while respecting the specialist tools already in use. A radiology information workflow and a picture archive are related but distinct capabilities. The website does not imply that a PACS is already included or that every imaging device can connect automatically. The first step is to understand the hospital's existing study identifiers, reporting process and access requirements.
Coordinate the appointment and preparation
Imaging requests may need resource scheduling, patient preparation and checks performed by authorised staff. Those requirements differ by examination and should be defined with the radiology department.
The operational system should show whether the request has been accepted, scheduled, performed and reported, without using one status to stand in for another. A reschedule or cancellation needs to reach the patient and the teams responsible for preparation. Requests from external referrers may require different identity and billing arrangements. The workflow should preserve the clinical question while giving staff a clear way to resolve incomplete information before the next step.
Link the report and study deliberately
A reliable connection must associate the patient, encounter, order, accession and study correctly. A viewer link that opens an archive is not sufficient evidence of that association.
Access rules should reflect the user's role and the intended care relationship, and a report amendment should remain visible as an amendment. DICOM and other interface requirements need to be assessed against the actual systems and versions involved. The integration design should include unmatched studies, duplicate identifiers and downtime. A specialist viewer may remain the best place to examine images while Medrella provides the clinical context and route into the correct study.
Close the loop with the requesting team
The release of a radiology report does not establish that it has been reviewed by the responsible clinician.
The hospital should define how important findings are communicated, who acknowledges them and what happens when the original requester is unavailable. These are operational and clinical responsibilities, not merely messaging features. Patient-facing access should follow the agreed release policy and avoid presenting an automated interpretation as a clinician's explanation. Planned AI document assistance may help organise report information, but any summary must retain its source and be reviewed. The report itself remains part of the authoritative diagnostic workflow.
Agree a bounded imaging integration
A useful pilot chooses a specific modality or reporting pathway and follows several studies end to end. Include an amended report, an incorrect demographic detail and an interrupted interface.
Ask whether the clinical user reaches the correct study, whether access is appropriate and how failures become visible to support staff. Define which system owns each identifier and which team reconciles exceptions. The acceptance criteria should cover clinical access and operational recovery, not only a successful connection test. Radiology and PACS remain planned Medrella capabilities until the selected workflow and integration are demonstrated in the intended hospital environment.
Connected thinking.
What would more time
for care make possible?
Let's explore it together