Provider Integration

Launch DN Viewer from your teleradiology website.

DN Viewer can be opened from an external webpage using the dnviewer:// protocol. Providers can pass a DICOMweb study directly, or send a short-lived manifest URL when credentials and launch policy should stay server-side.

Direct DICOMweb

Open one study with a direct URL

Use this format when your web application can safely generate the launch URL and the DICOMweb endpoint is reachable from the workstation.

dnviewer://dicomweb?baseUrl=https%3A%2F%2Fpacs.example.com%2Fdicom-web&studyUid=1.2.840.113619.2.55.3.604688435.781.1712859156.467

Supported query parameters

  • baseUrl - URL-encoded DICOMweb service root, without /studies.
  • studyUid - StudyInstanceUID to retrieve.
  • provider or label - Optional display name shown while loading.
  • replaceWorkspace - Optional. Defaults to true. Use false to add to the current workspace.

Bearer token example

dnviewer://dicomweb?baseUrl=https%3A%2F%2Fpacs.example.com%2Fdicom-web&studyUid=1.2.840...&auth=bearer&token=SHORT_LIVED_TOKEN

Custom header example

dnviewer://dicomweb?baseUrl=https%3A%2F%2Fpacs.example.com%2Fdicom-web&studyUid=1.2.840...&auth=header&headerName=Authorization&headerValue=Bearer%20SHORT_LIVED_TOKEN
Manifest Flow

Open a study from a launch manifest

Use a manifest when the provider portal should issue a short-lived launch ticket and keep auth details under server control.

dnviewer://open?manifest=https%3A%2F%2Fprovider.example.com%2Fdnviewer%2Flaunch%2Fabc123

Manifest JSON

{
  "type": "dicomweb-study",
  "baseUrl": "https://pacs.example.com/dicom-web",
  "studyUid": "1.2.840.113619.2.55.3.604688435.781.1712859156.467",
  "provider": "Provider Name",
  "replaceWorkspace": true,
  "auth": {
    "type": "bearer",
    "token": "short-lived-token"
  }
}

Custom header manifest auth

{
  "type": "dicomweb-study",
  "baseUrl": "https://pacs.example.com/dicom-web",
  "studyUid": "1.2.840...",
  "auth": {
    "type": "header",
    "name": "Authorization",
    "value": "Bearer short-lived-token"
  }
}
Web Button

Example launch link

In your provider portal, render a normal link or button. Browsers will ask the user to open DN Viewer when the protocol handler is installed.

<a href="dnviewer://open?manifest=https%3A%2F%2Fprovider.example.com%2Fdnviewer%2Flaunch%2Fabc123">
  Open in DN Viewer
</a>

If the app is not installed, show a fallback link to download DN Viewer.