DICOM PS3.18 2025a - Web Services

12 Non-Patient Instance Service and Resources

12.1 Overview

The Non-Patient Instance (NPI) Storage Service enables a user agent to retrieve, store, and search an origin server for Instances that are not related to an individual patient.

Note

  1. Non-Patient Instances adhere to a Composite Instance IOD Information Model that does not have at its root the Patient Information Entity representing an individual Patient.

  2. "Non-patient" does not imply that there is no patient-related identifiable information in the Instances. E.g., the Inventory IOD does include Attributes of the patient, but it does not have a Patient IE at the root of its information model.

An NPI Storage Service manages a collection of resources belonging to the categories specified in Table 12.1.1-1.

All NPI Storage Service origin servers shall support the Retrieve Capabilities, Retrieve, and Search transactions. Support for the Store transaction is optional. All NPI Storage Service user agents support one or more of the Retrieve Capabilities, Retrieve, Store, or Search transactions.

12.1.1 Resource Descriptions

An NPI Service manages resources from the same NPI Category. Target URIs have the following templates:

/{npi-name}
/{npi-name}/{uid}

Where

npi-name    = "color-palettes"
            / "defined-procedure-protocols"
            / "hanging-protocols"
            / "implant-templates"
            / "inventories"
uid         ; is the Unique Identifier of an NPI Instance

Table 12.1.1-1 contains the templates for the NPI Resource Categories.


The NPI SOP Classes are listed in Table GG.3-1 “Standard SOP Classes” in PS3.4.

12.1.2 Common Query Parameters

The origin server shall support Query Parameters as required in Table 12.1.2-1.

The user agent shall supply in the request Query Parameters as required in Table 12.1.2-1.

Table 12.1.2-1. Common Query Parameters

Name

Value

Usage

Section

User Agent

Origin Server

Accept

media-type

M

M

Section 8.3.3.1

Accept-Charset

charset

O

M

Section 8.3.3.2


See also Section 8.4.

12.1.3 Common Media Types

The origin server shall support the Media Types listed as Default or Required in Table 12.1.3-1 for all NPI transactions.

Table 12.1.3-1. Default, Required, and Optional Media Types

Media Type

Usage

Section

application/dicom

Required

Section 8.7.3.1

application/dicom+json

Default

Section 8.7.3.2

multipart/related; type="application/dicom+xml"

Required

Section 8.7.3.2


DICOM PS3.18 2025a - Web Services