6.1 Overview of Networking Section for Conformance Statements

The networking section of a Conformance Statement consists of the following major parts:

— a functional overview containing the Application Data Flow Diagram that shows all the Application Entities, including any sequencing constraints among them. It also shows how they relate to both local and remote Real World Activities;

— a more detailed specification of each Application Entity, listing the SOP Classes supported and outlining the policies with which it initiates or accepts associations;

— for each Application Entity and Real-World Activity combination, a description of proposed (for Association Initiation) and acceptable (for Association Acceptance) Presentation Contexts;

Note: A Presentation Context consists of an Abstract Syntax plus a list of acceptable Transfer Syntaxes. The Abstract Syntax identifies one SOP Class or Meta SOP Class (a collection of related SOP Classes identified by a single Abstract Syntax UID). By listing the Application Entities with their proposed and accepted Presentation Contexts, the Conformance Statement is identifying the set of Information Objects and Service Classes which are recognized by this implementation;

— for each SOP Class related to an Abstract Syntax, a list of any SOP options supported;

— a set of communications protocols which this implementation supports;

— a description of any extensions, specializations, and publicly disclosed privatizations in this implementation;

— a section describing DICOM related configuration details;

— a description of any implementation details which may be related to DICOM conformance or interoperability;

— a description of what codes and controlled terminology mechanisms are used.