Difference between revisions of "VistA Imaging Issues"
From VistApedia
| Line 99: | Line 99: | ||
| + | [[MAGGADDIMAGE]] This is the RPC call used by VistA Imaging to add an image. | ||
[[MAG3 CPRS TIU NOTE]] Returns a list of all images for a TIU document | [[MAG3 CPRS TIU NOTE]] Returns a list of all images for a TIU document | ||
[[MAG3 TIU DATA FROM DA]] Get TIU data from the TIUDA. | [[MAG3 TIU DATA FROM DA]] Get TIU data from the TIUDA. | ||
| Line 121: | Line 122: | ||
Imaging BackGround Processor will be calling the Status Callback | Imaging BackGround Processor will be calling the Status Callback | ||
routine of CP. | routine of CP. | ||
| − | |||
From the VistA Imaging technical manual (edited)... | From the VistA Imaging technical manual (edited)... | ||
Revision as of 12:58, 26 September 2005
Back to Programming VistA Issues
Here are some points I have learned about VistA imaging.
TIU EXTERNAL DATA LINK (file 8925.91) 1 0;1 .01 DOCUMENT <-Pntr [RP8925'] 2 0;2 .02 IMAGE <-Pntr [P2005'] 3 1;1 1 LINKED DATA OBJECT [F] field .01 will point to a specific TIU document field .02 can link to an entry in the IMAGE file field 1 can hold the path to a fileserver (e.g. i:\images\jr042696.bmp, etc.)
IMAGE (file 2005) Holds metadata about stored images
If there in an entry in TIU EXTERNAL DATA LINK (file #8925.91), then the corresponding document in CPRS will show a picture icon beside it.
Entry in IMAGE file will point to TIU EXTERNAL DATA LINK file, like this:
Here are NOTES about IMAGE file: PARENT GLOBAL ROOT D0 <-- contain IEN of TIU document this links to (E.G. 14321) PARENT DATA FILE# <-- 8925 (for images linked to notes) PARENT DATA FILE IMAGE POINTER <-- should hold IEN of entry in TIU EXTERNAL DATA LINK used to check existence of ^TIU(8925.91,IEN,0)
Here is a sample successful record in the IMAGE file NUMBER: 1 OBJECT NAME: test1 FILEREF: triplegears.jpg DISK & VOLUME, MAGNETIC: TMGImageServer <-- link to record in NETWORK LOCATION DISK & VOLUME, ABSTRACT: TMGImageServer OBJECT TYPE: STILL IMAGE PATIENT: TEST,KILLME DON'T PROCEDURE: testproc DATE/TIME IMAGE SAVED: AUG 17, 2005 IMAGE SAVE BY: TOPPENBERG,KEVIN S SHORT DESCRIPTION: Here is a short description PROCEDURE/EXAM DATE/TIME: AUG 16, 2005 PARENT DATA FILE#: TIU PARENT GLOBAL ROOT D0: 14321 <-- TIU IEN# for document linked to image PARENT DATA FILE IMAGE POINTER: 1 <--- matches IEN of record below LONG DESCRIPTION: This is an entry for the long entry field TYPE INDEX: IMAGE PROC/EVENT INDEX: HOLTER SPEC/SUBSPEC INDEX: MEDICINE ORIGIN INDEX: NON-VA CLINIC: Laughlin_Office ACQUISITION SITE: Medical Group of Greeneville
Here is a corresponding entry in the TIU EXTERNAL DATA LINK file NUMBER: 1 DOCUMENT: PRESCRIPTION CALL IN IMAGE: test1 LINKED DATA OBJECT: c:\somepic.jpg
Here is record in file NETWORK LOCATION NUMBER: 1 NETWORK LOCATION: TMGImageServer PHYSICAL REFERENCE: / TOTAL SPACE: 9999999 SPACE USED: 0 FREE SPACE: 9999999 OPERATIONAL STATUS: On-Line STORAGE TYPE: MAGNETIC ABSTRACT: Yes FULL: Yes BIG: Yes TEXT: Yes DICOM: No MAINTAINCONNECTION: NO RETENTION PERIOD: 365 MAX # RETRY ON CONNECT: 8 MAX # RETRY ON TRANSMIT: 8 LAST PURGE DATE: SEP 17, 2005@14:01:54 SITE: TMG USER: MANAGER,SYSTEM
With the above setup, here is the results of a call to get images for document 14321
GTM>d IMAGES^MAGGNTI(.REF,14321)
GTM>ZWR REF(*)
REF(0)="1^1 Images for the selected TIU NOTE^14321^TEST,KILLME DON'T PRESCRIPTI
ON CALL IN 13 Jul 05@09:47:34^1"
REF(1)="B2^1^/triplegears.jpg^/triplegears.ABS^Here is a short description^30508
16^1^testproc^08/16/2005^1^M^A^^^1^^^^^^^^^^^"
Kevin Toppenberg
9-12-05
The main, top-level imaging menu option is: MAG SYS MENU It is locked with key: MAG SYSTEM
Here are some potentially relevant RPC calls
MAGGADDIMAGE This is the RPC call used by VistA Imaging to add an image. MAG3 CPRS TIU NOTE Returns a list of all images for a TIU document MAG3 TIU DATA FROM DA Get TIU data from the TIUDA. Returns Document Type, and Document Date/Time MAG3 TIU IMAGE Files the TIU pointer in Imaging and the Imaging Pointer in TIU. MAG4 ADD IMAGE Adds a new entry to the IMAGE File ^MAG(2005 MAG4 CP CONSULT TO TIUDA Imaging Capture workstation calls this RPC to get a TIU IEN to attach images to. This call simply calls a CP API, which accepts DFN, Consult #, Visit String (optional), Complete|Do not Complete the |transaction. MAG4 CP GET VISITS This RPC call simply call a CP Routine that lists visits for a patient. Imaging prompts the user with this list when a Visit String is needed by CP to create a Note. MAG4 DATA FROM IMPORT QUEUE This call returns the Array of Data from the Import Queue, given a QUEUE Number Called from Delphi and 'M' MAG4 REMOTE IMPORT Called from MS Windows Application. MAG4 STATUS CALLBACK This RPC is called from the Imaging Delphi component when an image/images have been imported via the Imaging Import API being developed for use by Clinical Procedures. This call is used in the test version of Import API, it will be replaced in the released version. In the released version the Imaging BackGround Processor will be calling the Status Callback routine of CP.
From the VistA Imaging technical manual (edited)...
7.2.4 Further Information Every individual object (i.e., an image, audio clip, waveform, or scanned document) is an entry in the Image file (2005), where the object's attributes are managed. In addition, three auxiliary files are used: • Object Type (2005.02) • Network Location (2005.2) • Parent Data (? 2005.03--PARENT DATA FILE ?)
The objects are then related to the patient's VISTA text data (medicine, surgery, laboratory, radiology reports or progress notes) through the use of pointers, both forward from the VISTA package file to the Image file, and backwards from the Image file to the VISTA package file.
Software allows new objects to be added and displayed. Several additional files are used by the system. These include: • Imaging Workstations file that contains information about every workstation on the network. • Image Histologic Stain file, and a Microscopic Objective file used by anatomic pathology. • Imaging Site Parameters file.
