Материал: part02

Внимание! Если размещение файла нарушает Ваши авторские права, то обязательно сообщите нам

Page 176​

DICOM PS3.2 2020a - Conformance​

 

Name​

Tag​

Types of Matching​

Body Part Examined​

(0018,0015)​

S,*,U​

Manufacturer​

(0008,0070)​

S,*,U​

Manufacturer's Model Name​

(0008,1090)​

S,*,U​

Station Name​

(0008,1010)​

S,*,U​

Institution Name​

(0008,0080)​

S,*,U​

Institutional Department Name​

(0008,1040)​

S,*,U​

Series Instance UID​

(0020,000E)​

UNIQUE​

IMAGE Level​

 

 

Instance Number​

(0020,0013)​

S,*,U​

Image Comments​

(0020,4000)​

S,*,U​

Content Date​

(0008,0023)​

S,*,U,R​

Content Time​

(0008,0033)​

S,*,U,R​

Image Type​

(0008,0008)​

S,*,U​

Acquisition Number​

(0020,0012)​

S,*,U​

Acquisition Date​

(0008,0022)​

S,*,U,R​

Acquisition Time​

(0008,0032)​

S,*,U,R​

Acquisition Date Time​

(0008,002A)​

S,*,U,R​

Derivation Description​

(0008,2111)​

S,*,U​

Contrast/Bolus Agent​

(0018,0010)​

S,*,U​

Quality Control Image​

(0028,0300)​

S,*,U​

Burned In Annotation​

(0028,0301)​

S,*,U​

Lossy Image Compression​

(0028,2110)​

S,*,U​

Lossy Image Compression Ratio​

(0028,2112)​

S,*,U​

Number of Frames​

(0028,0008)​

S,*,U​

SOP Instance UID​

(0008,0018)​

UNIQUE​

SOP Class UID​

(0008,0016)​

NONE​

Common to all query levels​

 

 

Specific Character Set​

(0008,0005)​

S,*,U​

Types of Matching:​

The types of Matching supported by the C-FIND SCU. An "S" indicates the identifier attribute uses Single Value Matching, an "R" in-​ dicates Range Matching, a n"*"indicates wild card matching, a 'U' indicates Universal Matching, and an 'L' indicates that UID lists are​ sent. "NONE" indicates that no matching is supported, but that values for this Element are requested to be returned (i.e., universal​ matching), and "UNIQUE" indicates that this is the Unique Key for that query level, in which case Universal Matching or Single Value​ Matching is used depending on the query level.​

D.4.2.4.3.1.3.2 Presentation Context Acceptance Criterion​

FIND-SCU does not accept associations.​

D.4.2.4.3.1.3.3 Transfer Syntax Selection Policies​

FIND-SCU prefers explicit Transfer Syntaxes. If offered a choice of Transfer Syntaxes in the accepted Presentation Contexts, it will​ apply the following priority to the choice of Presentation Context to use for the C-STORE operation:​

a.​first encountered explicit Transfer Syntax,​

- Standard -​

DICOM PS3.2 2020a - Conformance​

Page 177​

b.​default Transfer Syntax.​

D.4.2.4.3.1.3.4 Response Status​

FIND-SCUwillbehaveasdescribedinTableD.4.2-24inresponsetothestatusreturnedintheC-FINDresponsecommandmessage(s).​

Table D.4.2-24. Response Status for FIND-SCU and Query Remote AE Request​

Service Status​

Further Meaning​

Status Codes​

Behavior​

Refused​

Out of Resources​

A700​

Current query is terminated; remaining queries​

 

 

 

 

continue​

 

Error​

Identifier does not match SOP Class​

A900​

Current query is terminated; remaining queries​

 

 

 

 

continue​

 

 

Unable to process​

Cxxx​

Current query is terminated; remaining queries​

 

 

 

 

continue​

 

Cancel​

Matching terminated due to Cancel request​

FE00​

Ignored (should never occur, since cancels​

 

 

 

 

never issued)​

 

Success​

Matching is complete - No final Identifier is​

0000​

 

supplied​

 

Pending​

Matches are continuing - Current Match is​

FF00​

 

suppliedandanyOptionalKeysweresupported​

 

in the same manner as Required Keys​

 

Current query is terminated; remaining queries​ continue​

Identifier used to populate browser and trigger​ recursive lower level queries​

Matches are continuing - Warning that one or​ FF01​ more Optional Keys were not supported for​ existence and/or matching for this Identifier​

Identifier used to populate browser and trigger​ recursive lower level queries​

D.4.2.4.4 Association Acceptance Policy​

FIND-SCU does not accept associations.​

D.4.2.5 MOVE-SCU​

D.4.2.5.1 SOP Classes​

MOVE-SCU provide Standard Conformance to the following SOP Class(es) :​

Table D.4.2-25. SOP Classes Supported By MOVE-SCU​

SOP Class Name​

SOP Class UID​

SCU​

SCP​

Study Root Query/Retrieve Information Model -​

1.2.840.10008.5.1.4.1.2.2.2​

Yes​

No​

MOVE​

 

 

 

D.4.2.5.2 Association Policies​

D.4.2.5.2.1 General​

MOVE-SCU initiates but never accepts associations.​

Table D.4.2-26. Maximum PDU Size Received as a SCP for MOVE-SCU​

Maximum PDU size received​

Unlimited​

- Standard -​

Page 178​

DICOM PS3.2 2020a - Conformance​

 

D.4.2.5.2.2 Number of Associations​

 

 

Table D.4.2-27. Number of Associations as a SCP for MOVE-SCU​

 

Maximum number of simultaneous associations​

1​

D.4.2.5.2.3 Asynchronous Nature​

MOVE-SCU will only allow a single outstanding operation on an Association. Therefore, MOVE-SCU will not perform asynchronous​ operations window negotiation.​

D.4.2.5.2.4 Implementation Identifying Information​

Table D.4.2-28. DICOM Implementation Class and Version for MOVE-SCU​

Implementation Class UID​

xxxxxxxxxxx.yy.etc.ad.inf.usw​

Implementation Version Name​

Viewer1.0​

D.4.2.5.3 Association Initiation Policy​

MOVE-SCU attempts to initiate a new association when the user performs the retrieve action from the user interface.​

D.4.2.5.3.1 Activity - Retrieve From Remote AE​

D.4.2.5.3.1.1 Description and Sequencing of Activities​

For the entity (study, series or instance) selected from the user interface to be retrieved, a single attempt will be made to retrieve it​ from the selected remote AE. If the retrieve fails, for whatever reason, no retry will be performed.​

D.4.2.5.3.1.2 Proposed Presentation Contexts​

Table D.4.2-29. Proposed Presentation Contexts for MOVE-SCU and Retrieve From Remote AE​

 

 

Presentation Context Table​

 

 

Abstract Syntax​

Transfer Syntax​

Role​

Extended​

Name​

UID​

Name List​

UID List​

 

Negotiation​

 

 

See Table D.4.2-25​SeeTableD.4.2-25​Implicit VR Little Endian​

1.2.840.10008.1.2​

SCP​

None​

 

 

Explicit VR Little Endian​

1.2.840.10008.1.2.1​

 

 

MOVE-SCU will propose multiple Presentation Contexts, one for each of the supported Transfer Syntaxes, and an additional​ Presentation Context with all of the supported Transfer Syntaxes, in order to determine which Transfer Syntaxes the remote SCP​ supports, and which it prefers.​

D.4.2.5.3.1.2.1 Extended Negotiation​

No extended negotiation is performed.​

In particular, relational retrievals are not supported.​

D.4.2.5.3.1.3 SOP Specific Conformance​

D.4.2.5.3.1.3.1 SOP Specific Conformance to C-FIND SOP Classes​

MOVE-SCU provides standard conformance to the supported C-MOVE SOP Classes.​

Only a single information model, Study Root, is supported.​

A retrieval will be performed at the STUDY, SERIES or IMAGE level depending on what level of entity has been selected by the user​ in the browser.​

- Standard -​

DICOM PS3.2 2020a - Conformance​

Page 179​

No CANCEL requests are ever issued.​

The retrieval is performed from the AE that was specified in the Retrieve AE attribute returned from the query performed by FIND-​ SCU.Theinstancesareretrievedtothecurrentapplication'slocaldatabasebyspecifyingthedestinationastheAETitleoftheSTORE-​ SCP AE of the local application. This implies that the remote C-MOVE SCP must be preconfigured to determine the presentation​ address corresponding to the STORE-SCP AE. The STORE-SCP AE will accept storage requests addressed to it from anywhere,​ so no pre-configuration of the local application to accept from the remote AE is necessary (except in so far as it was necessary to​ configure FIND-SCU).​

Table D.4.2-30. Study Root Request Identifier for MOVE-SCU​

Name​

Tag​

Unique, Matching or Return Key​

STUDY level​

 

 

Study Instance UID​

(0020,000D)​

U​

SERIES level​

 

 

Series Instance UID​

(0020,000E)​

U​

IMAGE level​

 

 

SOP Instance UID​

(0008,0018)​

U​

D.4.2.5.3.1.3.2 Presentation Context Acceptance Criterion​

MOVE-SCU does not accept associations.​

D.4.2.5.3.1.3.3 Transfer Syntax Selection Policies​

MOVE-SCU prefers explicit Transfer Syntaxes. If offered a choice of Transfer Syntaxes in the accepted Presentation Contexts, it will​ apply the following priority to the choice of Presentation Context to use for the C-STORE operation:​

a.​first encountered explicit Transfer Syntax,​

D.4.2.5.3.1.3.4 Response Status​

MOVE-SCU will behave as described in the Table below in response to the status returned in the C-MOVE response command​ message(s).​

Table D.4.2-31. Response Status for MOVE-SCU and Retrieve From Remote AE Request​

Service​

Further Meaning​

Status Codes​

Related Fields​

Behavior​

Status​

 

 

 

 

Refused​

Out of Resources - Unable to​

A701​

(0000,0902)​

Retrieval is terminated​

 

calculate number of matches​

 

 

 

 

Out of Resources - Unable to​

A702​

(0000,1020)​

Retrieval is terminated​

 

perform sub-operations​

 

(0000,1021)​

 

 

 

 

 

 

 

 

(0000,1022)​

 

 

 

 

(0000,1023)​

 

 

Move Destination unknown​

A801​

(0000,0902)​

Retrieval is terminated​

Failed​

IdentifierdoesnotmatchSOPClass​A900​

(0000,0901)​

Retrieval is terminated​

 

 

 

(0000,0902)​

 

 

Unable to process​

Cxxx​

(0000,0901)​

Retrieval is terminated​

 

 

 

(0000,0902)​

 

- Standard -​

Page 180​

DICOM PS3.2 2020a - Conformance​

 

Service​

Further Meaning​

Status Codes​

Related Fields​

Behavior​

Status​

 

 

 

 

Cancel​

Sub-operations terminated due to​FE00​

(0000,1020)​

Retrieval is terminated​

 

Cancel Indication​

 

(0000,1021)​

(should never occur, since​

 

 

 

cancels never issued)​

 

 

 

(0000,1022)​

 

 

 

 

(0000,1023)​

 

Warning​

Sub-operations Complete - One or​B000​

(0000,1020)​

Retrieval is terminated​

 

more Failures​

 

(0000,1022)​

 

 

 

 

 

 

 

 

(0000,1023)​

 

Success​

Sub-operations Complete - No​

0000​

(0000,1020)​

Retrieval is terminated​

 

Failures​

 

(0000,1021)​

 

 

 

 

 

 

 

 

(0000,1022)​

 

 

 

 

(0000,1023)​

 

Pending​

Sub-operations are continuing​

FF00​

(0000,1020)​

Retrieval continues​

(0000,1021)​

(0000,1022)​

(0000,1023)​

D.4.2.5.3.1.3.5 Sub-Operation Dependent Behavior​

Since the C-MOVE operation is dependent on completion of C-STORE sub-operations that are occurring on a separate association,​ the question of failure of operations on the other association(s) must be considered.​

MOVE-SCUcompletelyignoreswhateveractivitiesaretakingplaceinrelationtotheSTORAGE-SCPAEthatisreceivingtheretrieved​ instances. Once the C-MOVE has been initiated it runs to completion (or failure) as described in the C-MOVE response command​ message(s). There is no attempt by MOVE-SCU to confirm that instances have actually been successfully received or locally stored.​

Whether or not completely or partially successfully retrievals are made available in the local database to the user is purely dependent​ on the success or failure of the C-STORE sub-operations, not on any explicit action by MOVE-SCU.​

Whether or not the remote AE attempts to retry any failed C-STORE sub-operations is beyond the control of MOVE-SCU.​

If the association on which the C-MOVE was issued is aborted for any reason, whether or not the C-STORE sub-operations continue​ is dependent on the remote AE; the local STORAGE-SCP will continue to accept associations and storage operations regardless.​

D.4.2.5.4 Association Acceptance Policy​

MOVE-SCU does not accept associations.​

D.4.3 Network Interfaces​

D.4.3.1 Physical Network Interface​

The application is indifferent to the physical medium over which TCP/IP executes, which is dependent on the underlying operating​ system and hardware.​

- Standard -​