source: FOIAVistA/trunk/r/IMAGING-MAG-ZMAG/MAGDQR00.m@ 1484

Last change on this file since 1484 was 628, checked in by George Lilly, 16 years ago

initial load of FOIAVistA 6/30/08 version
File size: 6.4 KB
Line 
1MAGDQR00 ;WOIFO/EdM - Imaging RPCs for Query/Retrieve ; 06/06/2005 09:27
2 ;;3.0;IMAGING;**51**;26-August-2005
3 ;; +---------------------------------------------------------------+
4 ;; | Property of the US Government. |
5 ;; | No permission to copy or redistribute this software is given. |
6 ;; | Use of unreleased versions of this software requires the user |
7 ;; | to execute a written test agreement with the VistA Imaging |
8 ;; | Development Office of the Department of Veterans Affairs, |
9 ;; | telephone (301) 734-0100. |
10 ;; | |
11 ;; | The Food and Drug Administration classifies this software as |
12 ;; | a medical device. As such, it may not be changed in any way. |
13 ;; | Modifications to this software may result in an adulterated |
14 ;; | medical device under 21CFR820, the use of which is considered |
15 ;; | to be a violation of US Federal Statutes. |
16 ;; +---------------------------------------------------------------+
17 ;;
18 Q
19 ;
20 ; Query/Retrieve
21 ;
22 ; Step 1: The application (Java system) receives a C-FIND request
23 ;
24 ; Step 2: The application interprets the DICOM message and
25 ; calls an RPC on traditional VistA
26 ;
27 ; RPC name: MAG CFIND QUERY
28 ; input: array of: tag | VR | flag | value
29 ; input: scalar: batch-identifier, see below
30 ; input: scalar: max # entities in response
31 ; output: array of: header = # entities total | # in current batch
32 ; followed by tag | VR | flag | value
33 ; or <start sequence>
34 ; or <end sequence>
35 ;
36 ; Batch-identifier:
37 ; There are four kinds of calls:
38 ; 1. initial call
39 ; value of this parameter is "0"
40 ; RPC will create result-set and start a background process to
41 ; perform the query
42 ; 2. "are you ready" call
43 ; value of this parameter is "n|0"
44 ; where 'n' identifies the result-set
45 ; RPC will check if the query is ready and, when available, will
46 ; return "initial batch" of responses
47 ; 3. continuation call
48 ; value of this parameter is "n|m"
49 ; where 'n' identifies the result-set
50 ; where 'm' identifies the sequence
51 ; number of the first item to be returned RPC will return
52 ; next batch of responses
53 ; 4. final call
54 ; value of this parameter is "n|-1"
55 ; where 'n' identifies the result-set
56 ; RPC will not return any responses but clean-up any storage used
57 ; for result-set
58 ;
59 ; Suggested values for second parameter:
60 ; 0 for initial call
61 ; -1 for final call
62 ; >0 (sequence number of first entity to be returned)
63 ; for continuation call
64 ; Result-set will also have a "time stamp of last access"
65 ; so that an overall clean-up process can get rid of
66 ; obsolete result-sets.
67 ;
68 ; Step 3: The application interprets the results from the RPC
69 ; and will ask VistA which images belong to a
70 ; study-UID:
71 ;
72 ; RPC name: MAG STUDY UID QUERY
73 ; input: scalar study uid
74 ; input: scalar flag: include routed copies in result
75 ; input: scalar "my location" identifier
76 ; output: array of: header = # of entities in response
77 ; image# | path+file name | username | password
78 ;
79 ; Do we want to return the username and password in each
80 ; result, or do we want two separate RPC calls: one to
81 ; get path+filename for each file, and one that returns
82 ; the username and password given a path?
83 ;
84 ; Step 4: The application will create new DICOM entities to transmit
85 ; to its client. It has the information to access the
86 ; image files that exist on VistA (either .dcm files or
87 ; .txt + .tga pairs). It needs to ask VistA for the
88 ; current and correct information to place in the headers
89 ; of the DICOM entities to be transmitted:
90 ;
91 ; RPC name: MAG IMAGE CURRENT INFO
92 ; input: scalar image #
93 ; output: array of: header = # of entities in response
94 ; tag | VS | flag | value
95 ;
96 ; Do we need an additional input array to specify the
97 ; list of data-fields to be returned?
98 ;
99 ; Non-supported tags for Query/Retrieve
100 ; 0008,1110 O Referenced Study Sequence
101 ; 0008,1150 O >Referenced SOP Class UID
102 ; 0008,1155 O >Referenced SOP Instance UID
103 ; 0008,1120 O Referenced Patient Sequence
104 ; 0008,1150 O >Referenced SOP Class UID
105 ; 0008,1155 O >Referenced SOP Instance UID
106 ; 0010,1020 O Patient's Size [field not populated]
107 ; 0010,1030 O Patient's Weight [field not populated]
108 ; 0020,1070 O Other Study Numbers
109 ; 0020,1200 O Number of Patient Related Studies
110 ; 0020,1202 O Number of Patient Related Series
111 ; 0020,1204 O Number of Patient Related Instances
112 ;
113 ; Supported tags
114 ; 0008,0020 R Study Date
115 ; 0008,0030 R Study Time
116 ; 0008,0050 R Accession Number
117 ; 0010,0010 R Patient's Name
118 ; 0010,0020 R Patient ID
119 ; 0020,0010 R Study ID
120 ; 0020,000D U Study Instance UID
121 ;
122 ; 0008,0061 O Modalities in Study
123 ; 0008,0090 O Referring Physician's Name
124 ; 0008,1030 O Study Description
125 ; 0008,1032 O Procedure Code Sequence
126 ; 0008,0100 O >Code Value
127 ; 0008,0102 O >Coding Scheme Designator
128 ; 0008,0103 O >Coding Scheme Version
129 ; 0008,0104 O >Code Meaning
130 ; 0008,1060 O Name of Physician(s) Reading Study
131 ; 0010,0030 O Patient's Birth Date
132 ; 0010,0032 O Patient's Birth Time [probably always blank]
133 ; 0010,0040 O Patient's Sex
134 ; 0010,1000 O Other Patient IDs
135 ; 0010,1001 O Other Patient Names
136 ; 0010,1010 O Patient's Age
137 ; 0010,2160 O Ethnic Group
138 ; 0010,2180 O Occupation
139 ; 0010,21B0 O Additional Patient History
140 ; 0020,1206 O Number of Study Related Series
141 ; 0020,1208 O Number of Study Related Instances
142 ; 4008,010C O Interpretation Author
143 ;
144 ; Problem cases left over:
145 ; 0008,0062 O SOP Classes in Study [supported?]
146 ; 0008,1080 O Admitting Diagnoses Description
147 ; 0010,4000 O Patient Comments
148 ;
Note: See TracBrowser for help on using the repository browser.