Cloud-native universal viewers work best when the control planes are explicit
A cloud-hosted universal viewer is not just a browser app placed behind a load balancer. It is usually a collection of separately scaling layers: identity, web delivery, imaging metadata, image retrieval, and sometimes remote rendering or AI services.
Cloud-native viewer reference path
Loading diagram...
The official AWS diagram is broader than a viewer-only architecture, which is exactly why it is a good audit artifact. It shows the viewer sitting inside identity, workflow, storage, and audit planes instead of pretending the browser tier is the whole system.
Medical imaging system architecture
AWS healthcare architecture guidance for designing imaging platforms with separate viewer, metadata, storage, and resilience layers.
Read the cloud reference architectureAWS HealthImaging concepts
Official AWS explanation of how HealthImaging separates image-set metadata from image frames, which is the exact architectural split viewer teams need to understand.
Read the HealthImaging concepts guidePlatform decisions and AI extensions are operating-model decisions, not just technical features
Some teams want to own the full viewer application, data source configuration, and retrieval path. Others prefer a managed imaging platform that absorbs more infrastructure burden. In both cases, AI overlays and derived results still need lifecycle, provenance, and user-review controls.
Common cloud viewer operating models
| Model | Team owns most directly | Tradeoff |
|---|---|---|
| Self-managed web viewer stack | Viewer code, retrieval path, deployment, and performance tuning | Maximum control, maximum platform burden |
| Managed imaging data service plus viewer app | Viewer workflow and UX, while the platform absorbs more image-service behavior | Lower platform burden, but tighter dependence on service fit and roadmap |
| Remote-render or application-streamed tier | Session brokering, remote compute, and operational user experience | Useful for heavy workloads, but changes networking and desktop operations |
AI extension rule
If an AI service or segmentation layer changes what the clinician sees, the viewer must preserve provenance and reviewability. “It is just an overlay” is not a valid governance strategy.
AWS HealthImaging reference libraries
Official AWS guidance for client-side libraries and helper components used when integrating imaging applications with HealthImaging.
Read the reference-libraries guideUse OpenID Connect with DICOMweb
Official AWS guidance for protecting DICOMweb-style access with OIDC, relevant to secure cloud viewer delivery.
Read the DICOMweb OIDC guideCloud viewer programs fail when platform ownership and clinical ownership split without a contract
The recurring failure mode in cloud viewer projects is not simply “the cloud was slow.” It is usually an ownership gap: one team owns the browser app, another owns image delivery, another owns identity, and nobody owns the end-to-end clinical experience during failure.
Operational gaps that become clinical experience problems
| Gap | What it looks like to users | Needed control |
|---|---|---|
| Identity and token handoff mismatch | Viewer launches but retrieval calls fail or over-authorize | One explicit contract for launch, scopes, and downstream API access |
| Managed service fit assumptions | The platform is live, but the needed workflow or study shape is not well served | Validate service fit against real workflows before locking the operating model |
| Ungoverned AI or overlay lifecycle | Users see derived content without versioning or review context | Treat overlays and AI results as governed clinical artifacts |
Medical imaging system architecture
AWS guidance on designing operationally coherent imaging architectures rather than isolated viewer components.
Read the operational architecture guidanceUse OpenID Connect with DICOMweb
Official AWS guidance for keeping downstream DICOMweb access aligned with enterprise identity controls.
Read the OIDC handoff guidanceKnowledge Check
Test your understanding with this quiz. You need to answer all questions correctly to mark this section as complete.