| IA # | Name | Type | Custodial Package | Date Created | DBIC Approval Status | Status | Usage | File # | General Description | Remote Procedure | Routine | Date Activated |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| IA # | Name | Type | Custodial Package | Date Created | DBIC Approval Status | Status | Usage | File # | General Description | Remote Procedure | Routine | Date Activated |
| 458 | DBIA458 | Routine | IMAGING | 1994/04/25 | APPROVED | Active | Private |
MailMan 7.1 is permitted to the make calls to MAGAPI routine in the imaging package: |
MAGAPI | |||
| 459 | DBIA459 | File | IMAGING | 1994/04/25 | APPROVED | Active | Private | 2005 |
This agreement describes data that MailMan can access from the imaging package. |
|||
| 460 | DBIA460 | File | IMAGING | 1994/04/25 | APPROVED | Active | Private | 2005.2 |
MailMan has permission to access file 2005.2 so that it can find where images are and record their position appropriately. |
|||
| 461 | DBIA461 | File | IMAGING | 1994/04/25 | APPROVED | Active | Private | 2005.02 |
Before an image can be displayed, the type of file it is stored in must be known. |
|||
| 462 | DBIA462 | Routine | IMAGING | 1994/05/03 | APPROVED | Active | Private |
MailMan has permission to call MAGAPI for 3 purposes. |
MAGAPI | |||
| 463 | DBIA463 | Routine | IMAGING | 1994/05/03 | APPROVED | Active | Private | MailMan has permission to call MAGBAPI so that images that are imported can be moved into a permanent storage location. |
MAGBAPI | |||
| 464 | DBIA464 | Routine | IMAGING | 1994/04/25 | APPROVED | Active | Private |
MailMan has permission to call MAGOBJ in order to display an image on a screen while a user is reading a message. |
MAGOBJ | |||
| 466 | DBIA466 | Routine | IMAGING | 2003/10/20 | Retired | Private | The Medicine package has been given permission by the Imaging package to do the following: Make calls to the ^MAGMIM routine through the ^MCMAG routine. |
MAGMIM | ||||
| 467 | DBIA467 | Routine | IMAGING | 2003/10/20 | Retired | Private | The Medicine package has been given permission by the Imaging package to do the following: Make calls to the ^MAGDISP routine through the ^MCMAG routine. |
MAGDISP | ||||
| 468 | DBIA468 | Routine | IMAGING | 2003/10/20 | Retired | Private | The Medicine package has been given permission by the Imaging package to the following: Make calls to the ^MAGSUM routine through the ^MCMAG routine. |
MAGSUM | ||||
| 469 | DBIA469 | Other | IMAGING | 2003/10/20 | Retired | Private | The Medicine package has permission by the Imaging package to Kill the ^TMP("MAG",$J,"COL") and ^TMP("MAG",$J,"ROW") globals within the Medicine package upon exiting the Summary of Patient Procedures options. |
|||||
| 470 | DBIA470 | File | IMAGING | 2003/10/20 | APPROVED | Active | Private | 2005 | The Medicine package has been given permission by the Imaging package to do the following: Point to the Imaging File (#2005) to reference each Medicine Procedure that has images. |
|||
| 1196 | IMAGING/SURGERY MAGSRIC | Routine | IMAGING | 1995/04/13 | APPROVED | Active | Private | The Surgery Package is given permission to call IM^MAGSRIC to provide image capture capability to users of the operations options |
MAGSRIC | |||
| 1202 | MAGING/SURGERY CLEANUP | Routine | IMAGING | 1995/04/21 | APPROVED | Active | Private | The Surgery Package is given permission to call CLEAN^MAGSRIC to kill MAG namespaced local variables on exit from routine(s) using IM^MAGSRIC for image capture. |
MAGSRIC | |||
| 1324 | DBIA1324-A | File | IMAGING | 1995/08/25 | APPROVED | Active | Private | 2005 | This DBIA documents Radiology/Nuclear Medicine's use of a global node belonging to the Imaging package to determine whether the Imaging package has been installed at a given facility. |
|||
| 1325 | DBIA1324-B | File | IMAGING | 1995/08/25 | APPROVED | Active | Private | 2005 | This DBIA documents Radiology/Nuclear Medicine's use of a global node owned by the Imaging package to determine if images are scanned in before a reports are entered. |
|||
| 1326 | DBIA1324-C | Routine | IMAGING | 1995/08/25 | APPROVED | Active | Private | This DBIA documents a line label reference within the Radiology/Nuclear Medicine package to a routine in the Imaging package. |
MAGSET3 | |||
| 1328 | DBIA1324-E | Routine | IMAGING | 1995/08/25 | APPROVED | Active | Private | This DBIA documents a Radiology/Nuclear Medicine package reference to a line label within the Imaging package. |
MAGRIC | |||
| 1338 | DBIA1338 | Other | IMAGING | 1995/09/12 | APPROVED | Active | Private | This DBIA documents that Radiology/Nuclear Medicine kills two ^TMP( nodes for the Imaging package. The global nodes are: ^TMP("MAG",$J,"ROW") ^TMP("MAG",$J,"COL") This is necessary to reset the abstract display screen so the next abstract display will begin in the upper left hand corner of the screen. Only the Radiology/Nuclear Medicine package knows when the current case processing is finished, which is the point where these nodes must be killed. |
||||
| 2791 | DBIA2791 | File | IMAGING | 1999/03/31 | Withdrawn | Private | 2005 | Imaging gives permission to Health Summary to read from file 2005 for the purpose of displaying image descriptions. [MAGI] |
||||
| 2927 | POINTERS TO IMAGE FILE (#2005) | File | IMAGING | 1999/10/14 | APPROVED | Active | Controlled Subscription | 2005 | To support many-to-many linkages between Images (stored in file #2005) and other patient-oriented data (e.g., Documents, Orders, Reports, etc.) the subscribing packages may retain POINTERS to file 2005. |
|||
| 3567 | Imaging - MAGGSIUI | Routine | IMAGING | 2002/04/26 | APPROVED | Active | Controlled Subscription | Imaging v3.0 patch MAG*3.0*7 introduces an Image Import API that can be used to automatically import image files into VistA Imaging. The image files can be from a medical device (instrument) or a network or local drive. Once image files are imported, they are available for display from the VistA Imaging Clinical Display application. Importing image/report files is a two step process: Step 1: The calling program initiates the import proces by sending an input array to the Import API. The import API uses the input array to create an entry in the Import Queue file and returns a status array to the calling program. Step 2: After the entries in the Import Queue file are processed (by the Background Processor residing on the network), the Import API reports back to the calling program in a result array. Note: The Import API, as part of the VistA Imaging software, is regulated as a medical device. The Import API cannot be used without a written agreement between the VistA Imaging SD&D group and the party wishing to use the Import API. To secure an agreement for the use of the Import API, the following criteria must be met: 1) Any products built or interfaced using the VistA Imaging Import API must be tested with VistA Imaging. Testing will be performed by the VistA Imaging team with assistance from field sites and the calling package. This testing must demonstrate that there are no adverse interactions affecting the safety, efficacy or performance of the VistA Imaging software or the devices interfaced to VistA Imaging. 2) Any changes to packages/product(s) using the VistA Imaging Import API must be reported to the VistA Imaging Project Office for review and testing before release. Retesting of VistA Imaging with the product(s) is required with any change. 3) Documentation that imported reports/objects meet VHA, regulatory, and quality requirements must be on file with the Vista Imaging Project Office prior to any clinical use. Sample imported reports/objects shall be provided initially to the VistA Imaging Project Office by the package using the API. Sites installing the VistA Imaging API must comply with all VistA Imaging requirements and are responsible for filing all required documentation with the VistA Imaging Project Office, including image quality and data forms and sample reports/objects from any interfaced device. 4) Additional requirements may apply to non-VA software using the Import API. |
MAGGSIUI | |||
| 4009 | File 2005 | File | IMAGING | 2003/03/18 | Withdrawn | Private | 2005 | |||||
| 4526 | MAG4 REMOTE IMPORT | Remote Procedure | IMAGING | 2004/10/29 | APPROVED | Active | Controlled Subscription | MAG4 REMOTE IMPORT This RPC is used to QUEUE an image for storage by the VistA Imaging Import API. |
MAG4 REMOTE IMPORT | |||
| 4528 | MAG IMPORT CHECK STATUS | Remote Procedure | IMAGING | 2004/10/29 | APPROVED | Active | Controlled Subscription | MAG IMPORT CHECK STATUS This RPC is called to get a status record from the IMPORT STATUS file (2006.037) |
MAG IMPORT CHECK STATUS | |||
| 4529 | IMAGING RPC | Remote Procedure | IMAGING | 2004/10/26 | APPROVED | Active | Controlled Subscription | MAG IMPORT CLEAR STATUS This RPC call will remove a status record in the IMPORT STATUS file (2006.037). |
||||
| 4530 | MAG IMPORT CLEAR STATUS | Remote Procedure | IMAGING | 2004/10/29 | APPROVED | Active | Controlled Subscription | MAG IMPORT CLEAR STATUS This RPC will be used to clear a status record from the IMPORT STATUS file (2006.037). |
MAG IMPORT CLEAR STATUS | |||
| 4588 | Imaging's API for CP | Routine | IMAGING | 2005/01/11 | APPROVED | Active | Private | Imaging grants Clinical Procedures permission to call routine MAGMC2CP. |
MAGMC2CP | |||
| 4838 | 4838 MAGDTR01 | Routine | IMAGING | 2006/03/31 | APPROVED | Active | Controlled Subscription | Imaging has requested Consults to add a call, ORRIN^MAGDTR01 to the routine GMRCIMSG for use with patch MAG*3.0*46. This will allow Imaging to process Consult HL7 messages. |
MAGDTR01 | |||
| 4845 | Return NEW PERSON file phone number(s) | Routine | IMAGING | 2006/04/12 | APPROVED | Active | Private | The Vista Radiology/Nuclear Medicine application would like to utilize the existing VistA Imaging utility (NPFON^MAG7UFO) to return all phone number related information for a specific record in the NEW PERSON (#200) file. |
MAG7UFO | |||
| 4973 | Creation of a HL7 PID & PV1 segments (V2.4) | Routine | IMAGING | 2007/04/23 | Withdrawn | Private | The VistA Imaging development team will provide a function that creates both PID & PV1 segments that are backwards compatible to version 2.4 of Health Level Seven (HL7). The PID & PV1 segments are fixed segments; the Imaging development team will determine the fields to be defined for these segments in accordance with the 'Integrating the Healthcare Enterprise Radiology Technical Framework' specifications for order (ORM) transactions. |
MAGDHLS | ||||
| 4977 | Creation of a HL7 PID segment (V2.4) | Routine | IMAGING | 2007/02/15 | Withdrawn | Private | The VistA Imaging development team will provide a function that creates a PID segment that is backwards compatible to version 2.4 of Health Level Seven (HL7). The PID segment is a fixed segment; the Imaging development team will determine the fields to be defined for this segment in accordance with the 'Integrating the Healthcare Enterprise Radiology Technical Framework' specifications for order (ORM) transactions. |
MAGDHLS | ||||
| 5021 | Populate NEW PERSON phone(s) into a local array | Routine | IMAGING | 2007/08/01 | Active | Private | This function return the following NEW PERSON (#200) file fields into a local array: PHONE (HOME) (#.131), OFFICE PHONE (#.132), PHONE #3 (#.133), PHONE #4 (#.134), COMMERCIAL PHONE (#.135), FAX NUMBER (#.136), VOICE PAGER (#.137), and DIGITAL PAGER (#.138). |
MAG7UFO | ||||
| 5022 | Build the HL7 ZDS segment for Study Instance UID | Routine | IMAGING | 2007/08/01 | Active | Private | This function creates a DICOM Study Instance UID from three Radiology/Nuclear Medicine package variables: RADTI, RACNI, and RADTE. |
MAGDRAHL | ||||
| 5023 | Build the HL7 PID and PV1 segments | Routine | IMAGING | 2007/08/01 | Active | Private | MAGDHLS | |||||
| 5291 | DSIV IMAGING ACCESS | File | IMAGING | 2008/11/23 | APPROVED | Active | Private | 2005 | The DSIV package is requsting use of the "ATRKID" cross reference to get the image IEN in the Image file (#2005) of an image that is has imported using the Import API. The IEN is stored in an SQL database and also verifies that the scanned document, or other image, was successfully uploaded to imaging. The DocManager piece of DSIV has been tested by VistA Imaging. Note: DSIV also uses ICR 4526 (MAG4 REMOTE IMPORT) RPC from Imaging. The use of the MAG4 REMOTE IMPORT RPC and access to the "ATRKID" cross reference is limited to the DSS DocManager application only. Any other DSIV application will need approval before using the RPC or cross reference. |
2009/06/11 | ||
| 5450 | KERNEL BSE LOOKUP IN NETWORK LOCATION FILE | File | IMAGING | 2009/05/12 | APPROVED | Active | Private | 2005.2 | Kernel Broker Security Enhancement (BSE) requests the ability to do a lookup within the NETWORK LOCATION file (#2005.2) using FileManager and the command D FIND^DIC(2005.2,,"1","MO","VISTASITESERVICE",,,,,"XUSBSE") |
2010/06/16 | ||
| 5556 | MAG4 DATA FROM IMPORT QUEUE | Remote Procedure | IMAGING | 2010/08/27 | Pending | Controlled Subscription | This call returns the Array of Data from the Import Queue, given a QUEUE Number. Can be called from Delphi and 'M'. |
MAG4 DATA FROM IMPORT QUEUE | ||||
| 5557 | MAG4 INDEX GET EVENT | Remote Procedure | IMAGING | 2010/08/27 | Pending | Controlled Subscription | This call will return an array of entries from the IMAGE INDEX FOR PROCEDURE/EVENT (#2005.85) file based on the input parameters CLS (Class) and SPEC (Specialty/subspecialty). When images are displayed, it is desirable to limit the list of presented images to only those that are likely to be relevant in the current context. This procedure accepts an "image category" (either an IEN or the name of a category) and returns all "image events" that belong to that category. |
|||||
| 5558 | MAG4 INDEX GET ORIGIN | Remote Procedure | IMAGING | 2010/08/27 | Pending | Controlled Subscription | This call will return an array of the ORIGIN INDEX (field #45) from the IMAGE (#2005) file. The result array includes all ORIGIN codes and abbreviations. |
|||||
| 5559 | MAG4 INDEX GET SPECIALTY | Remote Procedure | IMAGING | 2010/08/27 | Pending | Controlled Subscription | This call will return an array of entries from the IMAGE INDEX FOR SPECIALTY/SUBSPECIALTY (#2005.84) file based on the input parameters CLS (Class) and EVENT (Procedure/Event). When images are displayed, it is desirable to limit the list of presented images to only those that are likely to be relevant in the current context. This procedure accepts an "image category" (either an IEN or the name of a category) and returns all "(sub)specialties" that generate images in that category. |
|||||
| 5560 | MAG4 INDEX GET TYPE | Remote Procedure | IMAGING | 2010/08/27 | Pending | Controlled Subscription | Used to filter out those image types that belong to a given image category (Class). When images are displayed, it is desirable to limit the list of presented images to only those that are likely to be relevant in the current context. This procedure accepts an "image class" (either an IEN or the name of a class) and returns all "image types" that belong to that class. |
|||||
| 5561 | MAGN PATIENT HAS PHOTO | Remote Procedure | IMAGING | 2010/08/27 | Pending | Controlled Subscription | Checks if photo image exists for a patient. Returns 0 if no photo or the date/time (Fileman format) of the most recent photo. |
|||||
| 5562 | MAG4 GET SUPPORTED EXTENSIONS | Remote Procedure | IMAGING | 2010/08/27 | Pending | Controlled Subscription | Returns a list of supported file extensions used in Imaging from the IMAGE FILE TYPES (#2005.021) file. |
MAG4 GET SUPPORTED EXTENSIONS | ||||
| 5563 | MAG3 CPRS TIU NOTE | Remote Procedure | IMAGING | 2010/08/27 | Pending | Controlled Subscription | Returns a list of all images for a TIU document. |
MAG3 CPRS TIU NOTE | ||||
| 5564 | MAGG CAPTURE USERS | Remote Procedure | IMAGING | 2010/08/27 | Pending | Controlled Subscription | This call will find users that have captured images in a date range. The list of users can be filtered by the FLAGS parameter. The Flags Parameter can contain 'C' for images captured on the Capture Workstation and/or 'I' for images captured throught the Import API. If the parameter is null it defaults to 'CI'. |
|||||
| 5565 | IMAGING QUEUE STATUS | Routine | IMAGING | 2010/08/27 | Pending | Controlled Subscription | This API will return the imaging queue status based on a Queue Number or Tracking ID. S X=$$STATUS^MAGQBUT3(Queue Number) S X=$$STATUS^MAGQBUT3(Tracking ID) |
MAGQBUT3 | ||||
| 5568 | IMAGE INDEX FOR CLASS file 2005.82 | File | IMAGING | 2010/09/08 | Pending | Controlled Subscription | 2005.82 | The MAG4 INDEX GET TYPE remote procedure requires a Class parameter. The IMAGE INDEX FOR CLASS file (#2005.82) contains the list of available class types for imaging and will be read using FileMan. ^MAG(2005.82,D0,0) .01 NAME 0;1 Read with Fileman |
||||
| 5628 | CHECK FOR MAGDISP CLIN KEY | File | IMAGING | 2011/04/15 | APPROVED | Active | Private | This ICR allows the subscribing package(s) to check for the MAGDISP CLIN key using the ^XUSEC global. Reference ICR 10076 for more information on the XUSEC global. |
2011/05/03 | |||
| 5730 | MAG RESCIND IMAGES | Routine | IMAGING | 2011/10/05 | APPROVED | Active | Private | This ICR will allow the TIU Package to set a Queue so that Images attached to a Rescinded Advance Directive will be Watermarked with the word 'RESCINDED'. |
MAGGSIU4 | 2011/10/14 | ||
| 5994 | DBIA5994 | Routine | IMAGING | 2013/07/29 | APPROVED | Active | Private | VistA Imaging gives permission to Laboratory Package to call CANCEL^MAGT7MA, EDIT^MAGT7MA, NEW^MAGT7MA, REPORT^MAGT7MA . These calls create VistA Imaging HL7 DICOM PACS messages pertain to Anatomic Pathology order updates. The messages are stored in PACS MESSAGE file (#2006.5) and are processed by VistA Imaging DICOM Text gateway. |
MAGT7MA | 2013/09/27 | ||
| 5997 | DBA5997 | Routine | IMAGING | 2013/07/30 | APPROVED | Active | Private | VistA Imaging gives permission to Laboratory Package to call ADD^MAGTP005 |
MAGTP005 | 2013/09/20 | ||
| 6000 | MAGV GET IRRADIATION DOSE | Routine | IMAGING | 2013/07/31 | APPROVED | Active | Private | The TAG^ROUTINE documented will return the attributes for the irradiation instance related to the patient and the procedure. |
MAGVRD03 | 2013/08/14 | ||
| 6159 | MAG4 ADD IMAGE | Remote Procedure | IMAGING | 2015/02/18 | Withdrawn | Controlled Subscription | MAG4 ADD IMAGE | |||||
| 6160 | MAG3 TIU IMAGE | Remote Procedure | IMAGING | 2015/02/18 | Withdrawn | Controlled Subscription | MAG3 TIU IMAGE | |||||
| 6161 | MAG4 IMAGE LIST | Remote Procedure | IMAGING | 2015/02/18 | Withdrawn | Controlled Subscription | ||||||
| 6162 | MAGBAPIP | Routine | IMAGING | 2015/02/18 | APPROVED | Active | Controlled Subscription | MAGBAPIP | 2015/04/03 | |||
| 6163 | MAGBAPI | Routine | IMAGING | 2015/02/18 | APPROVED | Active | Controlled Subscription | MAGBAPI | 2015/04/03 | |||
| 6192 | MAG 2005 READ | File | IMAGING | 2015/04/17 | APPROVED | Active | Controlled Subscription | 2005 | This ICR provides for the FileMan read of the ^MAG(2005, "ATRKID" index in the IMAGE FILE (#2005) and the PATIENT field #5 in the IMAGE FILE (#2005). These fields provide the ability to associate an image to a patient when a callback is execued by the Imaging Background Processor which passes only the Tracking ID and Queue ID to the callback routine. Once the IEN of the image entry in found using "ATRKID", the patient can be identified by reading fieled # in ^MAG(2005,D0,0). |
2015/04/21 | ||
| 6353 | SCHEDULING BSE LOOKUP IN NETWORK LOCATION FILE | File | IMAGING | 2016/02/08 | APPROVED | Active | Private | 2005.2 | VistA Scheduling GUI Enhancement (VS GUI) patch SD*5.3*642 requests the ability to do a lookup of the PHYSICAL REFERENCE field #1 within the NETWORK LOCATION file (#2005.2) using FileManager. This value will be passed back to VS GUI in order to obtain values to support Single Sign On (SSO) using the Broker Security Enhancement (BSE) lookup. |
2016/03/07 | ||
| 6379 | VA Community Care Access to Imaging | Other | IMAGING | 2016/03/01 | Withdrawn | Private | Responsibility for processing VA Community Care (VACC) claims has changed from the VISNs/VAMCs to the Chief Business Office for Purchased Care (CBOPC). As a national program, staff members often require access to multiple VistA systems in order to perform their duties. Four new menus are being created for use as a primary menu in accessing remote VistA systems via CAPRI. VACC staff need to be able to access Imaging in support of processing claims. |
|||||
| 6732 | VISTA IMAGING RAD DOSE DATABASE ACCESS | File | IMAGING | 2017/02/07 | APPROVED | Active | Private | 2005.632 | VistA Radiology/Nuclear Medicine requires VA FileMan (FM) read/with FM and direct global read access to the CT DOSE (#2005.632) file. The direct global read will be used to determine the presence of data in file 2005.632. |
2017/07/11 | ||
| 6733 | VISTA IMAGING RAD DOSE DATABASE ACCESS (2) | File | IMAGING | 2017/02/07 | APPROVED | Active | Private | 2005.633 | VistA Radiology/Nuclear Medicine requires VA FileMan (FM) read/with FM and direct global read access to the PROJECTION X-RAY DOSE (#2005.633) file. The direct global read will be used to determine the presence of data in file 2005.633. |
2017/07/11 | ||
| 6761 | Update patient demographics via HL7 w/VI | Routine | IMAGING | 2017/05/18 | APPROVED | Active | Private | VistA Imaging provides a routine type entry point that will build and broadcast HL7 ADT A08 Patient Information Update messages to subscribers of ADT messages. A HL7 ADT A47 Change Patient Identifier List message will also be built and broadcast for each SSN change. |
MAGDHLE | 2017/09/14 | ||
| 6860 | MAG IHE SWITCH FOR HL7 ADT MESSAGES | File | IMAGING | 2017/12/19 | Under Revision | Private | 2006.1 | Radiology requests access to the IMAGING SITE PARAMETERS file (#2006.1), field IHE PACS HL7 INTERFACE ACTIVE (#3.01) to determine if the broadcast of ADT messages are permitted at a facility. ADT messages can be broadcast by running the new RA ADT menu option that will be available with patch RA*5.0*137. |
2017/12/21 | |||
| 6910 | BUILD VI HL7 ORM MESSAGE FOR CP CHECK-IN OR CANCELLATION | Routine | IMAGING | 2018/04/30 | Pending | Private | VistA Imaging's (MAG) CLINPROC^MAGDHOWP is called by MDHL7BH to build and broadcast VistA Imaging HL7 ORM (order) messages for a check-in or cancellation events in the Clinical Procedure (MD) application. |
MAGDHOWP | ||||
| 6911 | SWAP CP INSTRUMENT ORDER # w/ IMAGING CONSULT ACCESSION # | Routine | IMAGING | 2018/04/30 | Pending | Private | VistA Imaging software has been enhanced to replace the CP Instrument Order Number with the VistA Imaging consults Accession Number. This greatly improves interoperability between Clinical Procedures and VistA Imaging CPRS Consult Request Tracking. |
MAGDFCNV | ||||
| 6931 | CP DICOM INTEROPERABILITY RETURN SSAN FOR CLIN SPEC | Routine | IMAGING | 2018/06/15 | APPROVED | Active | Private | This extrinsic function will return a site-specific accession number for clinical specialties. GMRCIEN is the CPRS Consult Request Tracking GMRC IEN from the REQUEST/CONSULTATION file (#123). |
MAGDFCNV | 2018/06/15 | ||
| 6932 | CP DICOM INTEROPERABILITY BUILD HL7 MESSAGE | Routine | IMAGING | 2018/06/15 | APPROVED | Active | Private | This API builds the VistA Imaging procedure HL7 ORM (order) message using the VistA Imaging formatted accession number. The API may conditionally return the HL7 ORM message body for Clinical Procedures' use. |
MAGDHOWP | 2018/06/15 | ||
| 6959 | CP CONVERSION UTILITY | File | IMAGING | 2018/09/07 | APPROVED | Active | Private | 2006.5831 | Clinical Procedures requires read access to the CLINICAL SPECIALTY DICOM & HL7 file (#2006.5831) to screen for consults or procedures setup in DICOM. The screen is on the interactive lookup for consults or procedures that are being selected to convert to Clinical Procedures. |
2018/12/03 | ||
| 7253 | OEHRM Imaging Migration - Access to file #2006.5839 | File | IMAGING | 2021/05/04 | Pending | Private | 2006.5839 | OEHRM is creating Imaging Migration software to facilitate the transfer of images from VistA to Millennium. The software will build a central accession number database that identifies all image-holding entities - consults and Radiology procedures - and will maintain that file throughout the conversion period. |
||||
| 7254 | OEHRM Imaging Migration - Access to file #2005 | File | IMAGING | 2021/05/04 | APPROVED | Active | Private | 2005 | OEHRM is creating Imaging Migration software to facilitate the transfer of images from VistA to Millennium. The software will build a central accession number database that identifies all image-holding entities - consults and Radiology procedures - and will maintain that file throughout the conversion period. Note: The patch - EHM*1*2 - will not be installed nationally. It will be installed only at sites that are being converted to Cerner. |
2021/06/15 | ||
| 7255 | OEHRM Imaging Migration - Access to file #2005.61 | File | IMAGING | 2021/05/04 | Pending | Private | 2005.61 | OEHRM is creating Imaging Migration software to facilitate the transfer of images from VistA to Millennium. The software will build a central accession number database that identifies all image-holding entities - consults and Radiology procedures - and will maintain that file throughout the conversion period. |
||||
| 7267 | OEHRM Imaging Migration - Access to file #2005.62 | File | IMAGING | 2021/06/01 | Pending | Private | 2005.62 | OEHRM is creating Imaging Migration software to facilitate the transfer of images from VistA to Millennium. The software will build a central accession number database that identifies all image-holding entities - consults and Radiology procedures - and will maintain that file throughout the conversion period. Note: The patch - EHM*1*2 - will not be installed nationally. It will be installed on at sites that are being converted to Cerner. |
||||
| 7270 | OEHRM Imaging Migration - Access to file #2005.63 | File | IMAGING | 2021/06/15 | Pending | Private | 2005.63 | OEHRM is creating Imaging Migration software to facilitate the transfer of images from VistA to Millennium. The software will build a central accession number database that identifies all image-holding entities - consults and Radiology procedures - and will maintain that file throughout the conversion period. |
||||
| 7408 | MAG RAD LIST DATA ELEMENTS (#2006.63) | File | IMAGING | 2023/01/05 | APPROVED | Active | Private | 2006.63 | The ISI Rad CLIENT application is a plug-in replacement for VistA Imaging's VistARad client. ISI Rad uses all of the existing VistA Imaging SERVER software (RPC calls, routines, files, etc.) in the same way as VistARad. In some cases, to support new features that VistARad does not have, new ISI SERVER software uses many of the same subroutines and files in the same manner as VistARad: session initialization; fetching Exam info and Image info; Exam Locking; Exam List data management; etc. VistA Imaging gives permission to ISI Rad to read and update file MAG RAD LIST DATA ELEMENTS (#2006.63), which contains data necessary for the exam list subsystem used by VistARad. |
2023/03/07 | ||
| 7409 | MAG RAD LISTS DEFINITION (#2006.631) | File | IMAGING | 2023/01/05 | APPROVED | Active | Private | 2006.631 | The ISI Rad CLIENT application is a plug-in replacement for VistA Imaging's VistARad client. ISI Rad uses all of the existing VistA Imaging SERVER software (RPC calls, routines, files, etc.) in the same way as VistARad. In some cases, to support new features that VistARad does not have, new ISI SERVER software uses many of the same subroutines and files in the same manner as VistARad: session initialization; fetching Exam info and Image info; Exam Locking; Exam List data management; etc. VistA Imaging gives permission to ISI Imaging to read and update file MAG RAD LISTS DEFINITION (#2006.631), which contains Exams List specification data for the exam list subsystem used by VistARad. |
2023/03/07 | ||
| 7410 | MAG VISTARAD SITE PARAMETERS (#2006.69) | File | IMAGING | 2023/01/05 | APPROVED | Active | Private | 2006.69 | The ISI Rad CLIENT application is a plug-in replacement for VistA Imaging's VistARad client. ISI Rad uses all of the existing VistA Imaging SERVER software (RPC calls, routines, files, etc.) in the same way as VistARad. In some cases, to support new features that VistARad does not have, new ISI SERVER software uses many of the same subroutines and files in the same manner as VistARad: session initialization; fetching Exam info and Image info; Exam Locking; Exam List data management; etc. VistA Imaging gives permission to ISI Imaging to read and update file MAG VISTARAD SITE PARAMETERS (#2006.69), which contains control data for managing various logic switches in VistARad (e.g., enable/disable a feature). |
2023/03/07 | ||
| 7497 | Call MAGT7MA For LAB Data From File 63 | Routine | IMAGING | 2024/09/27 | Active | Controlled Subscription | MEDICOM TECHNOLOGIES requests to call $$GETFILE^MAGT7MA to get LABORATORY TEST file (#60) data, determine the error status of the lab and return FILE("FIELD") fields for the LAB DATA file (#63). |
MAGT7MA | ||||
| 7501 | Get Lab Test Data | Routine | IMAGING | 2024/10/10 | Active | Controlled Subscription | The routine creates the OBR segment for HL7 message to DPS and provides a lookup for Lab Test |
MAGT7SB | ||||
| 7504 | DICOM Patient Lookup | Routine | IMAGING | 2024/10/22 | Active | Controlled Subscription | API's and RPC'S for VistA PATIENT lookup routine |
MAGDSTA3 | ||||
| 7505 | Setup Rad/Nuc Med HL7 Output Array Separators | Routine | IMAGING | 2024/11/04 | Active | Controlled Subscription | Patch MECH*1.0*1 gathers patient cases to send to the ImageX Application via HL7 messages. This patch calls $$OUTSEP^MAGVIM01 and $$STATSEP^MAGVIM01 to get the correct separators for the HL7 messages. |
MAGVIM01 |