Retrieve web-displayable renderings of DICOM instances using the WADO-RS Retrieve Rendered transaction instead of raw pixel data

Steps

1. Distinguish the WADO-RS Retrieve Rendered Transaction (DICOM PS3.18), which returns a viewer-ready rendering such as JPEG/JPEG2000 (or a rendered representation appropriate to the source instance type), from standard WADO-RS instance/frame retrieval, which returns raw or transfer-syntax-encoded DICOM pixel data.
2. Call the '/rendered' sub-resource path under the instance (or frame) resource rather than the base instance resource when the client only needs a displayable image, not full DICOM fidelity.
3. Set the Accept header to one of the server's supported Rendered Media Types, since a conformant server may support only a subset of rendered formats — check its conformance statement rather than assuming all formats are available.
4. Use the optional viewport query parameter to request a cropped region and target display size when building thumbnails or region-of-interest views, avoiding full-resolution downloads for simple previews.
5. Use the annotation parameter only when the rendered image should be burned in with patient/procedure information for print or screenshot contexts, understanding this alters the pixel content itself rather than adding a separate overlay layer.
6. Fall back to full WADO-RS instance retrieval, or QIDO-RS metadata plus client-side rendering, when consumers need windowing/LUT control or diagnostic-quality fidelity that a pre-rendered image cannot provide.