DICOM PS3.7 2016d - Message Exchange

A.2.2 Privately Defined Application Context Names
Prev | A.2 DICOM Application Context Name Encoding and Registration | Next

### A.2.2 Privately Defined Application Context Names

Privately defined Application Context Names may also be used, but they will not be registered by ACR-NEMA. Organizations that define private Application Context Names are responsible to obtain their proper registration as defined for OSI Object Identifiers. National Standards Organizations representing a number of countries (e.g., UK, France, Germany, Japan, USA, etc.) to the International Standards Organization act as a registration authority as defined by ISO 9834-1.

### Note

For example, in the USA, ANSI assigns Organization Identifiers to any requesting organization. This identifier is made of a series of four numeric elements; 1 (identifies ISO), 2 (identifies the ISO member bodies branch), 840 (identifies ANSI as the ISO member body representing the USA), and xxxxxx (identifies a specific organization and is issued by ANSI). Such an identifier may be used by the identified organization as a root to which it may add a suffix made of one or more numeric elements. The identified organization accepts the responsibility to properly register these suffixes to ensure uniqueness.

Privately defined Application Context Names shall be encoded as defined in PS3.8. The Organization identifier "1.2.840.10008" is reserved for DICOM and shall not be used for privately defined Application Context Names.

Prev | Up | Next
A.2 DICOM Application Context Name Encoding and Registration | Home | A.3 Association Initialization for DICOM Application Entity

DICOM PS3.7 2016d - Message Exchange