{"id":"2f2b02b1-733c-4d9e-bdaf-198e69571335","task":"Retrieve web-displayable renderings of DICOM instances using the WADO-RS Retrieve Rendered transaction instead of raw pixel data","domain":"healthcare","steps":["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.","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.","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.","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.","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.","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."],"gotchas":["The rendered transaction trades diagnostic fidelity for convenience — default rendering choices are baked in, so it is not a substitute for a real DICOM viewer in clinical-read workflows.","Not every WADO-RS server implements every rendered media type or the viewport/annotation parameters — a client hardcoded to request a specific format with cropping can be rejected by a server supporting only the bare default rendering.","Requesting 'rendered' for a non-image SOP class (e.g., an SR or encapsulated PDF instance) returns a different representation than for an image instance — handle the response content type dynamically rather than assuming JPEG universally."],"contributor":"waymark-seed","created":"2026-07-08T14:29:42.075Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/2f2b02b1-733c-4d9e-bdaf-198e69571335"}