Page 146 |
DICOM PS3.2 2020a - Conformance |
|
|
Description/Module |
|
Tag |
Remark |
>Requested Contrast Agent |
|
(0032,1070) |
|
Requested Procedure |
|
|
|
Reason for the Requested Procedure |
|
(0040,1002) |
|
Requested Procedure Comments |
|
(0040,1400) |
|
Imaging Service Request |
|
|
|
Reason for the Imaging Service Request |
|
(0040,2001) |
|
Imaging Service Request Comments |
|
(0040,2400) |
|
Requesting Service |
|
(0032,1033) |
|
Issuing Date of Imaging Service Request |
|
(0040,2004) |
|
Issuing Time of Imaging Service Request |
|
(0040,2005) |
|
Placer Order Number / Imaging Service Request |
(0040,2016) |
|
|
Filler Order Number / Imaging Service Request |
(0040,2017) |
|
|
Order entered by |
|
(0040,2008) |
|
Order Enterer's Location |
|
(0040,2009) |
|
Visit Status |
|
|
|
Patient's Institution Residence |
|
(0038,0400) |
|
Visit Admission |
|
|
|
Referring Physician's |
|
(0008,0090) |
|
Referring Physician's Address |
|
(0008,0092) |
|
Referring Physician's Phone Numbers |
|
(0008,0094) |
|
Admitting Diagnosis Description |
|
(0008,1080) |
|
Admitting Date |
|
(0038,0020) |
|
Admitting Time |
|
(0038,0021) |
|
Patient Identification |
|
|
|
Issuer of Patient ID |
|
(0010,0021) |
|
Patient Demographic |
|
|
|
Occupation |
|
(0010,2180) |
|
Patient's Address |
|
(0010,1040) |
|
Country of Residence |
|
(0010,2150) |
|
Patient's Telephone Numbers |
|
(0010,2154) |
|
Ethnic Group |
|
(0010,2160) |
|
Patient's Religious Preference |
|
(0010,21F0) |
|
Patient Comments |
|
(0010,4000) |
|
Patient Medical |
|
|
|
Smoking Status |
|
(0010,21A0) |
|
Last Menstrual Date |
|
(0010,21D0) |
|
DICOMSRV returns C-FIND response statuses as specified below.
- Standard -
|
|
DICOM PS3.2 2020a - Conformance |
Page 147 |
|
|
Table C.4.2-8. MWL C-FIND Response Status Reasons |
|||
Service |
Further Meaning |
Error Code |
Reasons |
|
Status |
|
|
|
|
Success |
Matching is complete |
0000 |
The response status code and meaning are logged in the job log file. |
|
Failure |
Out of resources |
A700 |
Ifthenumberofmatchesexceedsaconfigurablemaximumthiserror |
|
|
|
|
code is returned. An error comment describing the error is also |
|
returned. The response status code and meaning are logged in the job log file.
Identifier does not match SOP A900 class
ThisstatusisreturnediftheC-FINDrequestspecifiesqueryorReturn keysthatarenotspecifiedaspartoftheModalityWorklistInformation Model - FIND SOP Class. The response status code and meaning are logged in the job log file.
Unable to process |
C001 |
This status is returned due to internal errors within DICOMSRV such |
|
|
as a processing failure response on a query of the DICOMRis |
|
|
database. The response status code and meaning are logged in the |
|
|
job log file. |
Canceled MatchingterminatedduetocancelFE00
request
Pending Matching is continuing |
FF00 |
Matching is continuing - CurrentFF01 matchissuppliedandanyoptional keys were supported in the same matter as required keys
This status is returned if a Cancel Request is received from the SCU during the processing of a Modality Worklist request. The response status code and meaning are logged in the job log file.
The status is returned with each matching response. A message is logged for each pending response.
The status is returned with each matching response if one or more optional matching or return keys are not supported for existence. A message is logged for each pending response.
C.4.2.1.4.2 Activity - Configured AE Makes Procedure Step Request
When a configured remote AE sends a conformant association request including one of the Modality Performed Procedure Step Presentation Contexts in the table below then DICOMSRV will accept the Association.
C.4.2.1.4.2.1 Description and Sequencing of Activities
As mentioned above, DICOMSRV is started at system boot time and is thus ready to process MPPS messages at any time thereafter. The sequencing diagram below specifies a common flow of messages related to this activity. Prior to this sequence of messages it is necessary that orders have been received from the HIS interface or created via DICOMRis Ordering and Scheduling application. Attributes from the orders and created procedures, usually queried using MWL, will be included in the MPPS messages the Modality sendstoDICOMSRV.KeyattributesintheMPPSN-CREATEandN-SET,specifiedbelow,areextractedandmatchedagainstvalues in the DICOMRis database. A match allows full update of all applicable DICOMRis database tables.
Modality |
|
DICOMSRV |
|
|
|
1.Open Association
2.MPPS N-CREATE Request
3.Perform all/part of Request Procedure(s)
4.Perform matching. Update MPPS and other applicable tables
5.MPPS N-SET Request setting status to COMPLETED
6.Update MPPS and other applicable tables
7. Close Association
Figure C.4.2-2. Sequencing Diagram for Activity: Configured AE Makes Procedure Step Request
- Standard -
Page 148 |
DICOM PS3.2 2020a - Conformance |
The figure above is a possible sequence of messages and events for the Configured AE Makes Procedure Step Request activity.
1.The Modality opens an Association to update DICOMSRV using MPPS
2.The Modality sends an N-CREATE Request to indicate that it is performing one or more Requested Procedures
3.The Modality performs all or part of the procedure(s)
4.DICOMSRV stores the MPPS and executes the matching algorithm described in the conformance section below. If a successful match is found, then updates to various tables per the N-CREATE are performed. See Table C.4.2-10 for additional detail. In the matching case, the procedure state of the procedure(s) referenced in the MPPS is updated if so configured
5.The Modality sends an N-SET setting the status of the MPPS to COMPLETED
6.DICOMSRV stores the MPPS. If the N-CREATE for this step matched then updates are performed as specified in step 4
7.The Modality closes the Association
DICOMSRV also supports the 5 IHE Unidentified Patient Use Cases. Cases 1, 2 and 4 are transparent to the MPPS SCU and follow the normal flow. In case 3, the patient upon whom a given procedure must be immediately performed has been registered on the HIS and has a valid Patient ID but has no order specifying the applicable procedure. DICOMSRV recognizes this case when an MPPS N-CREATE is received with a matching Patient ID, zero-length Accession Number (0008,0050) and Requested Procedure ID (0040,1001). If the MPPS SCU is configured for support of IHE Trauma cases, DICOMSRV will order a procedure corresponding to the code contained in the Procedure Code Sequence (0008,1032), if this code is recognized, or will order a default procedure based on configuration. If the default procedure is ordered then a user may modify the procedure using DICOMRis Ordering and Scheduling application.
In case 5, there is no existing registration or order for a patient on whom a procedure must be immediately performed. Values are enteredontheModalityidentifyingthepatientandprocedure.DICOMSRVrecognizesthiscasewhenanMPPSN-CREATEisreceived containing a Patient ID within a configured range. This range will never contain Patient IDs created in the normal flow. If the MPPS SCU is configured for support of IHE Trauma cases, DICOMSRV will register the patient with the Patient ID provided and will order a procedure as described above.
C.4.2.1.4.2.2 Accepted Presentation Contexts
TableC.4.2-9.AcceptablePresentationContextsforAEDICOMSRVandReal-WorldActivity"Configured
AE Makes Procedure Step Request"
|
|
Presentation Context Table |
|
|
|
Abstract Syntax |
Transfer Syntax |
Role |
Extended |
||
Name |
UID |
Name List |
UID List |
|
Negotiation |
|
|
||||
Modality Performed 1.2.840.10008.3.1.2.3.3Implicit VR Little Endian |
1.2.840.10008.1.2.1 |
SCP |
None |
||
Procedure Step SOP |
|
Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
|
|
Class |
|
|
|
||
|
|
|
|
|
|
DICOMSRV's preferred Transfer Syntax is Explicit VR Little Endian and this will be selected if offered.
C.4.2.1.4.2.3 SOP Specific Conformance for MPPS SOP Class
The table below lists all Modality Performed Procedure Step attributes, whether they may be created by N-CREATE and updated by N-SET and what parts of the DICOMRis database they are used to update. All MPPS messages and thus their attributes are stored for the configurable Purge Period described below. The 'Database Updates' column considers updates separate from the storage of MPPS messages. If no value is present this indicates that there are is no update to the database associated with the given element.
Table C.4.2-10. Supported N-SET/N-CREATE Attributes for MPPS
Attribute Name |
Tag |
N-Create |
N-Set Database Updates |
SOP Common Module |
|
|
|
Specific Character Set |
(0008,0005) |
Y |
N |
- Standard -
|
DICOM PS3.2 2020a - Conformance |
|
Page 149 |
|
Attribute Name |
Tag |
N-Create |
N-Set |
Database Updates |
Performed Procedure Step Relationship Module |
|
|
|
|
Scheduled Step Attribute Sequence |
(0040,0270) |
Y |
N |
Y |
>Study Instance UID |
(0020,000D) |
Y |
N |
Overwrite existing |
|
|
|
|
value if different from |
|
|
|
|
received value |
>Referenced Study Sequence |
(0008,1110) |
Y |
N |
|
>>Referenced SOP Class UID |
(0008,1150) |
Y |
N |
|
>>Referenced SOP Instance UID |
(0008,1155) |
Y |
N |
|
>Accession Number |
(0008,0050) |
Y |
N |
|
>Placer Order Number/Imaging Service |
(0040,2006) |
Y |
N |
|
Request |
|
|
|
|
>Filler Order Number/Imaging Service |
(0040,2007) |
Y |
N |
|
Request |
|
|
|
|
>Requested Procedure ID |
(0040,1001) |
Y |
N |
|
>Requested Procedure Description |
(0032,1060) |
Y |
N |
|
>Scheduled Procedure Step ID |
(0040,0009) |
Y |
N |
|
>Scheduled Procedure Step Description |
(0040,0007) |
Y |
N |
|
>Scheduled Protocol Code Sequence |
(0040,0008) |
Y |
N |
|
>>Code Value |
(0008,0100) |
Y |
N |
|
>>Coding Scheme designator |
(0008,0102) |
Y |
N |
|
>>Code Meaning |
(0008,0104) |
Y |
N |
|
Patient Name |
(0010,0010) |
Y |
N |
|
Patient ID |
(0010,0020) |
Y |
N |
|
Patient's Birth Date |
(0010,0030) |
Y |
N |
|
Patient's Sex |
(0010,0040) |
Y |
N |
|
Referenced Patient Sequence |
(0008,1120) |
Y |
N |
|
>Referenced SOP Class UID |
(0008,1150) |
Y |
N |
|
>Referenced SOP Instance UID |
(0008,1155) |
Y |
N |
|
Performed Procedure Step Information |
|
|
|
|
Performed Procedure Step ID |
(0040,0253) |
Y |
N |
|
Performed Station AE Title |
(0040,0241) |
Y |
N |
|
Performed Station Name |
(0040,0242) |
Y |
N |
|
Performed Location |
(0040,0243) |
Y |
N |
|
Performed Procedure Step Start Date |
(0040,0244) |
Y |
N |
|
Performed Procedure Step Start Time |
(0040,0245) |
Y |
N |
|
Performed Procedure Step Status |
(0040,0252) |
Y |
Y |
|
Performed Procedure Step Description |
(0040,0254) |
Y |
Y |
|
Performed Procedure Type Description |
(0040,0255) |
Y |
Y |
|
Procedure Code Sequence |
(0008,1032) |
Y |
Y |
|
>Code Value |
(0008,0100) |
Y |
Y |
|
>Coding Scheme Designator |
(0008,0102) |
Y |
Y |
|
>Code Meaning |
(0008,0104) |
Y |
Y |
|
Performed Procedure Step End Date |
(0040,0250) |
Y |
Y |
|
- Standard -
Page 150 |
DICOM PS3.2 2020a - Conformance |
|
|
||
Attribute Name |
|
Tag |
N-Create |
N-Set |
Database Updates |
Performed Procedure Step End Time |
|
(0040,0251) |
Y |
Y |
|
CommentsonthePerformedProcedureStep |
(0040,0280) |
Y |
Y |
|
|
Image Acquisition Results |
|
|
|
|
|
Modality |
|
(0008,0060) |
Y |
N |
|
Study ID |
|
(0020,0010) |
Y |
N |
|
Performed Protocol Code Sequence |
|
(0040,0260) |
Y |
Y |
If valued, stored with |
>Code Value |
|
(0008,0100) |
Y |
Y |
current and historical |
|
procedure records |
||||
>Coding Scheme Designator |
|
(0008,0102) |
Y |
Y |
|
|
|
||||
>Code Meaning |
|
(0008,0104) |
Y |
Y |
|
Performed Series Sequence |
|
(0040,0340) |
Y |
Y |
Y |
>Performing Physician's Name |
|
(0008,1050) |
Y |
Y |
Y |
>Protocol Name |
|
(0018,1030) |
Y |
Y |
Stored with current |
|
|
|
|
|
and historical tables |
>Operator's Name |
|
(0008,1070) |
Y |
Y |
If automatic setting of |
|
|
|
|
|
procedure states is |
|
|
|
|
|
enabled, stored in |
|
|
|
|
|
current and historical |
|
|
|
|
|
procedure tables to |
|
|
|
|
|
indicatewhomodified |
|
|
|
|
|
the state of the |
|
|
|
|
|
procedure |
>Series Instance UID |
|
(0020,000E) |
Y |
Y |
|
>Series Description |
|
(0008,103E) |
Y |
Y |
|
>Retrieve AE Title |
|
(0008,0054) |
Y |
Y |
|
Referenced Image Sequence |
|
(0008,1140) |
Y |
Y |
|
>>Referenced SOP Class UID |
|
(0008,1150) |
Y |
Y |
|
>>Referenced SOP Instance UID |
|
(0008,1155) |
Y |
Y |
|
>Referenced Standalone SOP Instance |
|
(0040,0220) |
Y |
Y |
|
Sequence |
|
|
|
|
|
>>Referenced SOP Class UID |
|
(0008,1150) |
Y |
Y |
|
>>Referenced SOP Instance UID |
|
(0008,1155) |
Y |
Y |
|
Billing and Material Management Code |
|
|
|
|
|
Billing Procedure Step Sequence |
|
|
|
|
|
>Code Value |
|
(0008,0100) |
Y |
Y |
|
>Coding Scheme Designator |
|
(0008,0102) |
Y |
Y |
|
>Code Meaning |
|
(0008,0104) |
Y |
Y |
|
Film Consumption Sequence |
|
(0040,0321) |
Y |
Y |
|
> Number of Films |
|
(2100,0170) |
Y |
Y |
Updates Supply and |
> Medium Type |
|
(2000,0030) |
Y |
Y |
Film-Procedure |
|
Tables |
||||
> Film Size ID |
|
(2010,0050) |
Y |
Y |
|
|
|
||||
Billing Supplies and Devices Sequence |
|
(0040,0384) |
Y |
Y |
|
>Billing Item Sequence |
|
(0040,0296) |
Y |
Y |
|
- Standard -