A useful universal viewer combines a broad capability surface with disciplined workflow choices
“Universal” does not mean every user should see the same tools. It means one platform can support multiple user groups while still respecting their different jobs, datasets, and navigation patterns.
Capabilities that matter more than marketing labels
| Capability | Why it matters | Failure mode if weak |
|---|---|---|
| Multi-viewport comparison and priors | Clinicians need side-by-side context across current and prior studies | Users fall back to opening multiple disconnected applications |
| Measurements and annotations | Clinical decisions often depend on repeatable marks, lengths, or regions of interest | Findings stay trapped in narrative memory or screenshots |
| Hanging protocols | Opening the right layout automatically reduces friction and error | Every case starts with manual layout and tool setup |
| Role-specific modules | Reviewing images from the chart is not the same as reading in a specialist workflow | One interface becomes mediocre for everyone |
OHIF extension platform
Official OHIF documentation describing extensions and modular viewer behavior, which is directly relevant to specialty-specific universal-viewer workflows.
Read the OHIF extension modelHangingProtocolService
Official OHIF service documentation for protocol matching and layout behavior based on study context.
Read the hanging protocol service guideWorkflow fit matters more than claiming one viewer can do everything
A strong enterprise viewer allows one shared platform to express different workflows cleanly. That means chart review can stay simple, while advanced reading or specialty modules can expose more complex behavior only when the user and context require it.
Study context driving viewer behavior
Loading diagram...
When selections or findings need to move beyond the active session, the platform should not rely on screenshots alone. Clinical artifacts need identifiers and relationships that downstream systems can reference later.
FHIR ImagingSelection
Official HL7 resource for referencing selected imaging content and regions in a structured way that can survive outside one viewing session.
Read the ImagingSelection resourceFHIR DiagnosticReport
Official HL7 resource showing how imaging interpretation can be linked into broader clinical reporting workflows.
Read the DiagnosticReport resourceMeasurements need a lifecycle from interactive tool state to portable clinical artifact
A universal viewer should distinguish between something a user is sketching temporarily and something the organization expects to survive into follow-up review, reporting, or collaboration. That is where measurement tracking, export, and artifact identity become part of viewer design rather than afterthoughts.
Lifecycle of a viewer-derived finding
Loading diagram...
Representative ImagingSelection for a portable finding
A simplified ImagingSelection payload showing the study, endpoint, instance, and geometry details a downstream app needs to reopen the same finding context.
Click on an annotation to highlight it in the JSON
Portability test
If a finding cannot be reopened to the same study, instance, and region outside the originating viewport, it is still mostly a screen effect rather than an interoperable artifact.
OHIF MeasurementService
Official OHIF service documentation for tracked measurements and the viewer-side lifecycle of measurement objects.
Read the MeasurementService guideFHIR ImagingSelection
Official HL7 resource for preserving selected imaging content and geometry outside one active viewing session.
Read the ImagingSelection resourceIHE Interactive Multimedia Report (Volume 1)
Official IHE profile discussing advanced measurement viewing and report-linked interactive image display as a workflow target.
Read the IMR workflow overviewKnowledge Check
Test your understanding with this quiz. You need to answer all questions correctly to mark this section as complete.