INTEGRATION REFERENCES LIST MAR 18,2015 11:24 PAGE 1 -------------------------------------------------------------------------------- NUMBER: 1 IA #: 1 DATE CREATED: JUL 27, 1989 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA1 ORIGINAL NUMBER: 1 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: Protocol Menu VARIABLES: XQOR TYPE: Used VARIABLES DESCRIPTION: Set, when an option with type protocol menu is encountered, to the internal number of the option before execution is turned over to OE/RR. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City DATE ACTIVATED: JAN 01, 2000 NUMBER: 2 IA #: 2 DATE CREATED: JUL 27, 1989 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2 ORIGINAL NUMBER: 2 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: MENUMAN VARIABLES: XQUIT TYPE: Used VARIABLES DESCRIPTION: Tells menuman to quit if a premenu action failed. Since OE/RR also executes premenu actions for protocols, OE/RR needs to tell Menuman to quit when execution is returned. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3 IA #: 3 DATE CREATED: JUL 27, 1989 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA3 ORIGINAL NUMBER: 3 GENERAL DESCRIPTION: Using the following variables: DT= Date DTIME = Read timeout DUZ = User and paramaters in the DUZ array STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10501791 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 6 IA #: 6 DATE CREATED: JUL 27, 1989 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA6-A ORIGINAL NUMBER: 6 GENERAL DESCRIPTION: The following variables are killed only: D0,DI,DIG,DIH,DIU,DIV,& DIQ DIROUT - Is used as a quick exit when ^^ is entered at prompts. DLAYGO - is used for calls to Fileman. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 7 IA #: 7 GLOBAL ROOT: %ZOSF( DATE CREATED: JUL 27, 1989 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA7 ORIGINAL NUMBER: 7 ID: %ZOSF( GENERAL DESCRIPTION: Uses variables DX and DY to call %ZOSF and global %ZOSF to get system specific variables. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 10 IA #: 10 FILE NUMBER: 40.5 GLOBAL ROOT: HOLIDAY( DATE CREATED: MAR 12, 1990 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA10 ORIGINAL NUMBER: 10 ID: HOLIDAY( GENERAL DESCRIPTION: USE OF THE HOLIDAY FILE, ^HOLIDAY STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 11 IA #: 11 GLOBAL ROOT: DPT( & LRT(67, DATE CREATED: MAR 20, 1990 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA11 ORIGINAL NUMBER: 11 ID: DPT( & LRT(67, GLOBAL REFERENCE: DPT(dfn,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .02 FIELD NAME: SEX LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: .03 FIELD NAME: DATE OF BIRTH LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: .05 FIELD NAME: MARITAL STATUS LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: .06 FIELD NAME: RACE LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: .07 FIELD NAME: OCCUPATION LOCATION: 0;7 ACCESS: Read w/Fileman FIELD NUMBER: .08 FIELD NAME: RELIGIOUS PREFERENCE LOCATION: 0;8 ACCESS: Read w/Fileman FIELD NUMBER: .09 FIELD NAME: SOCIAL SECURITY NUMBER LOCATION: 0;9 ACCESS: Read w/Fileman FIELD NUMBER: .091 FIELD NAME: REMARKS LOCATION: 0;10 ACCESS: Read w/Fileman FIELD NUMBER: .092 FIELD NAME: PLACE OF BIRTH [CITY] LOCATION: 0;11 ACCESS: Read w/Fileman FIELD NUMBER: .093 FIELD NAME: PLACE OF BIRTH [STATE] LOCATION: 0;12 ACCESS: Read w/Fileman FIELD NUMBER: .14 FIELD NAME: CURRENT MEANS TEST STATUS LOCATION: 0;14 ACCESS: Read w/Fileman FIELD NUMBER: .096 FIELD NAME: WHO ENTERED PATIENT LOCATION: 0;15 ACCESS: Read w/Fileman FIELD NUMBER: .097 FIELD NAME: DATE ENTERED INTO FILE LOCATION: 0;16 ACCESS: Read w/Fileman FIELD NUMBER: .081 FIELD NAME: DUPLICATE STATUS LOCATION: 0;18 ACCESS: Read w/Fileman FIELD NUMBER: .082 FIELD NAME: PATIENT MERGED TO LOCATION: 0;19 ACCESS: Read w/Fileman FIELD NUMBER: .083 FIELD NAME: CHECK FOR DUPLICATE LOCATION: 0;20 ACCESS: Read w/Fileman GLOBAL REFERENCE: DPT(dfn,.11) FIELD NUMBER: .111 FIELD NAME: STREET ADDRESS [LINE 1] LOCATION: .11;1 ACCESS: Read w/Fileman FIELD NUMBER: .112 FIELD NAME: STREET ADDRESS [LINE 2] LOCATION: .11;2 ACCESS: Read w/Fileman FIELD NUMBER: .113 FIELD NAME: STREET ADDRESS [LINE 3] LOCATION: .11;3 ACCESS: Read w/Fileman FIELD NUMBER: .114 FIELD NAME: CITY LOCATION: .11;4 ACCESS: Read w/Fileman FIELD NUMBER: .115 FIELD NAME: STATE LOCATION: .11;5 ACCESS: Read w/Fileman FIELD NUMBER: .116 FIELD NAME: ZIP CODE LOCATION: .11;6 ACCESS: Read w/Fileman FIELD NUMBER: .117 FIELD NAME: COUNTY LOCATION: .11;7 ACCESS: Read w/Fileman FIELD NUMBER: .1112 FIELD NAME: ZIP+4 LOCATION: .11;12 ACCESS: Read w/Fileman GLOBAL REFERENCE: DPT(dfn,.13) FIELD NUMBER: .131 FIELD NAME: PHONE NUMBER [RESIDENCE] LOCATION: .13;1 ACCESS: Read w/Fileman FIELD NUMBER: .132 FIELD NAME: PHONE NUMBER [WORK] LOCATION: .13;2 ACCESS: Read w/Fileman GLOBAL REFERENCE: DPT(dfn,.01,D1,0) FIELD NUMBER: .01 FIELD NAME: ALIAS LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: ALIAS SSN LOCATION: 0;2 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Use of variable pointers to DPT & REFFERAL File. Uses following patient nodes: Address Node .11 Phone node .13 Field 1, Alias subfile 0 Node STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ONCOLOGY ISC: Washington/Silver Spring NUMBER: 12 IA #: 12 DATE CREATED: MAR 21, 1990 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA12 ORIGINAL NUMBER: 12 GENERAL DESCRIPTION: USE OF FILE 63 NODE "LR" AND ^LRDPT FOR DEATH INFORMATION STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ONCOLOGY ISC: Washington/Silver Spring NUMBER: 13 IA #: 13 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: MAR 21, 1990 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA13 ORIGINAL NUMBER: 13 ID: DPT( GLOBAL REFERENCE: DPT(dfn,.35) FIELD NUMBER: .351 FIELD NAME: DATE OF DEATH LOCATION: .35;1 ACCESS: Direct Global Write & w/Fileman FIELD NUMBER: .352 FIELD NAME: DEATH ENTERED BY LOCATION: .35;2 ACCESS: Direct Global Write & w/Fileman GENERAL DESCRIPTION: PATIENT NODE .35 - DEATH INFO USED TO STUFF ^LR( GLOBAL. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: LAB SERVICE ISC: Salt Lake City NUMBER: 15 IA #: 15 FILE NUMBER: 70 GLOBAL ROOT: RADPT( DATE CREATED: FEB 23, 1990 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA15-A ORIGINAL NUMBER: 15 ID: RADPT( GLOBAL REFERENCE: RAO(75.1,'AS', GENERAL DESCRIPTION: RADIOLOGY PATIENT FILE CROSS REFERENCE STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 16 IA #: 16 FILE NUMBER: 130 GLOBAL ROOT: SRF( DATE CREATED: FEB 26, 1990 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA16 ORIGINAL NUMBER: 16 ID: SRF( GLOBAL REFERENCE: SRF(D0,0) FIELD NUMBER: .04 FIELD NAME: SURGERY SPECIALTY LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: .09 FIELD NAME: DATE OF OPERATION LOCATION: 0;9 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,.1) FIELD NUMBER: .14 FIELD NAME: SURGEON LOCATION: .1;4 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,14,D1,0) FIELD NUMBER: .01 FIELD NAME: OTHER PREOP DIAGNOSIS LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: PAIRED ORGAN LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: DIAGNOSIS COMMENTS LOCATION: 1;0 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,15,D1,0) FIELD NUMBER: .01 FIELD NAME: OTHER POSTOP DIAG'S LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: PAIRED ORGANS LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: DIAGNOSIS COMMENTS LOCATION: 1;0 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,13,D1,0) FIELD NUMBER: .01 FIELD NAME: OTHER OPERATIVE PROCEDURES LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1.5 FIELD NAME: OP CODE COMMENTS LOCATION: 1;0 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: COMPLETED LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: PROCEDURE CODE LOCATION: 2;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,12,D1,0) FIELD NUMBER: 1.15 FIELD NAME: SURGEON'S DICTATION LOCATION: 12;0 ACCESS: Read w/Fileman FIELD DESCRIPTION: Word processing GLOBAL REFERENCE: SRF(D0,31) FIELD NUMBER: 15 FIELD NAME: DATE/TIME OF DICTATION LOCATION: 31;6 ACCESS: Read w/Fileman FIELD NUMBER: 39 FIELD NAME: DATE OF TRANSCRIPTION LOCATION: 31;7 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,'OP') FIELD NUMBER: 27 FIELD NAME: PRINCIPAL OP CODE LOCATION: OP;2 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,33) FIELD NUMBER: 32 FIELD NAME: PRINCIPAL PRE-OP DIAGNOSIS LOCATION: 33;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,34) FIELD NUMBER: 34 FIELD NAME: PRINCIPAL POST-OP DIAG LOCATION: 34;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,'VER') FIELD NUMBER: 43 FIELD NAME: CASE VERIFICATION LOCATION: VER;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,9,D1,0) FIELD NUMBER: 49 FIELD NAME: SPECIMENS AND CULTURES LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Multiple GLOBAL REFERENCE: SRF('B', GLOBAL DESCRIPTION: Used to access data. GENERAL DESCRIPTION: Surgery file (130). STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 17 IA #: 17 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: MAR 12, 1990 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA17-A ORIGINAL NUMBER: 17 ID: DGPM( GLOBAL REFERENCE: DGPM(D0, FIELD NUMBER: .05 FIELD NAME: TRANSFER FACILITY LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 99 FIELD NAME: DIAGNOSIS LOCATION: DX;D1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DGPM('ATID'_TT,DFN,INVERSE DT,DA) GLOBAL DESCRIPTION: Movement types will be determined by traversing the following cross-reference: ^DGPM("ATID"_TT,DFN,INVERSE DT,DA), where TT represents code for movement types: 1 - admissions 2 - transfers 3 - discharges 6 - treating speciality NOTE: DA is used to call ^VADPT GLOBAL REFERENCE: DGPM('APCA', GLOBAL DESCRIPTION: Direct Global Read of the APCA cross-reference on Patient, Admission/Check-In and Movement Date/Time, for sorting data for Health Summary reports. GLOBAL REFERENCE: DGPM('ATID1', GLOBAL DESCRIPTION: Direct Global Read of the ATID1 cross-reference on Transaction, Patient and Movement Date/Time, for sorting data for Health Summary reports. GLOBAL REFERENCE: DGPM('ATS', GLOBAL DESCRIPTION: Direct Global Read of the ATS cross-reference on Patient, Admission/Check-In, Movement Date/Time and Treating Specialty, for sorting data for Health Summary reports. GENERAL DESCRIPTION: PATIENT MOVEMENT FILE (405). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17805506 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 19 IA #: 19 FILE NUMBER: 40.7 GLOBAL ROOT: DIC(40.7, DATE CREATED: JAN 29, 1990 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA19 ORIGINAL NUMBER: 19 ID: DIC(40.7, GLOBAL REFERENCE: DIC(40.7,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Pointer to determine Stop Code. Stop Code name used on reports, bulletins. FIELD NUMBER: 1 FIELD NAME: AMIS REPORTING STOP CODE LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: Used on error-checking validation report to find 700 (non-credit) codes, used on bulletin, used to screen out '900' entries on look-up. FIELD NUMBER: 2 FIELD NAME: INACTIVE DATE LOCATION: 0;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: Used on error-checking validation report to find Radiology/Nuc Med procedures pointing to inactive stop codes. Used to screen out inactive selections on look-up. FIELD NUMBER: 4 FIELD NAME: COST DISTRIBUTION CENTER LOCATION: 0;5 ACCESS: Read w/Fileman FIELD DESCRIPTION: Used in sort criteria and heading on Radiology CDR report. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19427782 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 21 IA #: 21 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: DEC 08, 1989 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA21 ORIGINAL NUMBER: 21 ID: DPT( GLOBAL REFERENCE: DPT(D0,DENT) FIELD NUMBER: 220 FIELD NAME: DENTAL CLASSIFICATION LOCATION: DENT;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: A code indicating the level of elegibility for Dental Care. FIELD NUMBER: 220.1 FIELD NAME: DENTAL ELIGIBILITY EXPIRATION LOCATION: DENT;2 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: The exiration date of Dental eligibility, if there is one. GENERAL DESCRIPTION: Fields 220 and 220.1 of the Patient Files were established for Dental use and Dental will begin using them. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DENTAL ISC: Washington/Silver Spring NUMBER: 26 IA #: 26 GLOBAL ROOT: XUTL( DATE CREATED: MAY 08, 1989 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA26 ORIGINAL NUMBER: 26 ID: XUTL( GLOBAL REFERENCE: XUTL('OR',$J,'PSG', GLOBAL DESCRIPTION: Use of ^XUTL("OR",$J,"PSG", Even if OE/RR has not been installed. This makes the options for Inpatient Medications independently invokable. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTO REPLENISHMENT/WARD STOCK ISC: Birmingham NUMBER: 27 IA #: 27 FILE NUMBER: 45 GLOBAL ROOT: DGPT( DATE CREATED: JUL 17, 1989 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA27 ORIGINAL NUMBER: 27 ID: DGPT( GLOBAL REFERENCE: DGPT(D0,70) FIELD NUMBER: 79 FIELD NAME: DXLS LOCATION: 70;10 ACCESS: Read w/Fileman FIELD DESCRIPTION: Version 4.0 fo Mental Health references field 79, DXLS in the PTF File (^DGPT). The reference is read-only and used for display. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Salt Lake City NUMBER: 29 IA #: 29 GLOBAL ROOT: DD( DATE CREATED: FEB 13, 1990 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA29 ORIGINAL NUMBER: 29 ID: DD( GENERAL DESCRIPTION: Routines LRWU5 & LRWU7 Do direct sets to the Data Dictionary. The routines allow the user to add a new Data Name or Antibiotic without giving programmer access. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: LAB SERVICE ISC: Salt Lake City NUMBER: 31 IA #: 31 FILE NUMBER: 42 GLOBAL ROOT: DIC(42, DATE CREATED: NOV 14, 1989 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA31-A ORIGINAL NUMBER: 31 ID: DIC(42, GLOBAL REFERENCE: DIC(42,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .03 FIELD NAME: SERVICE LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 44 FIELD NAME: HOSPITAL LOCATION FILE POINTER LOCATION: 44;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTO REPLENISHMENT/WARD STOCK ISC: Birmingham NUMBER: 33 IA #: 33 FILE NUMBER: 42 GLOBAL ROOT: DIC(42, DATE CREATED: NOV 14, 1989 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA33 ORIGINAL NUMBER: 33 ID: DIC(42, GENERAL DESCRIPTION: Inpatient Medications will be referencing the following files & fields: FILE 42 2 ROOM subfile & all fields 2 BED " " X-REF "B" on ROOM-BED FILE 42.3 TRANSFER TYPE EXPIRED AS OF THE RELEASE OF MAS 5. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTO REPLENISHMENT/WARD STOCK ISC: Birmingham NUMBER: 36 IA #: 36 FILE NUMBER: 42 GLOBAL ROOT: DIC(42, DATE CREATED: MAR 22, 1989 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA36-A ORIGINAL NUMBER: 36 ID: DIC(42, GENERAL DESCRIPTION: ^DIC(42 Used to get link to file 44 for inpatients STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 38 IA #: 38 DATE CREATED: MAY 23, 1988 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA38 ORIGINAL NUMBER: 38 GENERAL DESCRIPTION: Cardiology package exports Lab Codes for Cardiology. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL PROCEDURES NUMBER: 41 IA #: 41 GLOBAL ROOT: DIBT( DATE CREATED: JUN 06, 1990 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA41 ORIGINAL NUMBER: 41 ID: DIBT( GENERAL DESCRIPTION: Routine DGABTP30 (background job) sets the ^DIBT global. The routine checks for sort templates, specifically [DGPMABSENCES] & [DGPMAB30], through the crossreference, and uses the template's IFN to set node ^DIBT(IFN,1,MOVEMENT IFN) for selected records. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 42 IA #: 42 FILE NUMBER: 4 GLOBAL ROOT: DIC(4, DATE CREATED: JUN 06, 1990 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA42 ORIGINAL NUMBER: 42 ID: DIC(4, GENERAL DESCRIPTION: LAYGO to the Institution File is allowed through an option in the MCCR module. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 43 IA #: 43 FILE NUMBER: 442 GLOBAL ROOT: PRC(442, DATE CREATED: JUN 18, 1990 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA43 ORIGINAL NUMBER: 43 ID: PRC(442, GLOBAL REFERENCE: PRC(442,'B',STATION #) GLOBAL DESCRIPTION: Gets - IFCAP station number with a call to ^PRCFSITE with PRCF("X") ="S" Uses - the IFCAP Station Number to determine whether an obligation number entered by the user exists in IFCAP. Done by doing $D(^PRC(442,"B",STATION NUMBER-OBLIGATION)). STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: FEE BASIS ISC: Albany NUMBER: 44 IA #: 44 FILE NUMBER: 43 GLOBAL ROOT: DG(43, DATE CREATED: JUN 26, 1990 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA44 ORIGINAL NUMBER: 44 ID: DG(43, GLOBAL REFERENCE: DG(43,1,'VERSION') FIELD NUMBER: 999 FIELD NAME: VERSION LOCATION: VERSION;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Checks ^DG(43,1,"VERSION") to determine which version of MAS is running. Migrate to the "VR" node of the DD when made available in Fileman (expected in version 18). STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ONCOLOGY ISC: Washington/Silver Spring NUMBER: 47 IA #: 47 FILE NUMBER: 41.9 GLOBAL ROOT: DG(41.9, DATE CREATED: JUL 25, 1990 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA47 ORIGINAL NUMBER: 47 ID: DG(41.9, GLOBAL REFERENCE: DG(41.9,D0,C,D1,1) FIELD NUMBER: 102 FIELD NAME: OPERATING BEDS LOCATION: 1;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Used for lookups. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Salt Lake City NUMBER: 51 IA #: 51 FILE NUMBER: 720 DATE CREATED: OCT 22, 1990 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA51 ORIGINAL NUMBER: 51 GENERAL DESCRIPTION: The .01 field of file 720, "B" crossreference has been modified to be 50 characters rather than the standard 30. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: EVENT CAPTURE ISC: Birmingham NUMBER: 54 IA #: 54 DATE CREATED: JUL 05, 1990 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA54 ORIGINAL NUMBER: 54 GENERAL DESCRIPTION: MAS version 4.7 will be exporting the following: Routine PRCASVC3 FILE 430.4 AR BILL NUMBER FILE wit input template PRCAF COMMON SERIES Following options make the indicated forgien calls: OPTION ACTION DGCR FILLING SUPERVISOR MENU calls COUNT^PRCAUT2 DGCR BILLING CLERK MENU calls COUNT^PRCAUT2 DGCR RETURNED BILL LIST calls RETN^PRCALST DGCR CANCEL BILL calls CANCEL^PRCASVC1 Return of edited bill calls REL^PRCASVC STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MCCR BACKBILLING ISC: Albany NUMBER: 55 IA #: 55 GLOBAL ROOT: DOPT( DATE CREATED: NOV 28, 1990 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA55 ORIGINAL NUMBER: 55 ID: DOPT( GENERAL DESCRIPTION: Since the use of ^DOPT has a long and honored history, it may be permitted to be used until further notice. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING DETAILS: The first subscript is the name of the routine (e.g., ^DOPT("IBCMENU", ...) The second subscript is a sequential number. The data is 0-node >> "Billing option^1N^16^16" Following sequential nodes >> only the first piece is filled in, and Fileman line-tags the entry points for the option based on the numerical subscript. NUMBER: 56 IA #: 56 GLOBAL ROOT: DOPT( DATE CREATED: NOV 28, 1990 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA56 ORIGINAL NUMBER: 56 ID: DOPT( GENERAL DESCRIPTION: Given the longstanding history of the use of ^DOPT, scheduling may continue to use it. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 57 IA #: 57 FILE NUMBER: 130 GLOBAL ROOT: SRF( DATE CREATED: DEC 04, 1990 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA57 ORIGINAL NUMBER: 57 ID: SRF( GLOBAL REFERENCE: SRF(D0,0) FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .04 FIELD NAME: SURGERY SPECIALTY LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: .011 FIELD NAME: IN/OUT-PATIENT STATUS LOCATION: 0;12 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,.1) FIELD NUMBER: .14 FIELD NAME: SURGEON LOCATION: .1,4 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,.2) FIELD NUMBER: .21 FIELD NAME: ANES CARE START TIME LOCATION: .2;1 ACCESS: Read w/Fileman FIELD NUMBER: .22 FIELD NAME: TIME OPERATION BEGAN LOCATION: .2;2 ACCESS: Read w/Fileman FIELD NUMBER: .23 FIELD NAME: TIME OPERATION ENDS LOCATION: .2;3 ACCESS: Read w/Fileman FIELD NUMBER: .24 FIELD NAME: ANES CARE END TIME LOCATION: .2;4 ACCESS: Read w/Fileman FIELD NUMBER: .205 FIELD NAME: TIME PAT IN OR LOCATION: .2;10 ACCESS: Read w/Fileman FIELD NUMBER: .232 FIELD NAME: TIME PAT OUT OR LOCATION: .2;12 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,6,D1,0) FIELD NUMBER: .01 FIELD NAME: ANESTHESIA TECHNIQUE LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .05 FIELD NAME: PRINCIPAL TECH LOCATION: 0;3 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,13,D1,0) FIELD NUMBER: .01 FIELD NAME: OTHER OPERATIVE PROCEDURES LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,13,D1,2) FIELD NUMBER: 3 FIELD NAME: PROCEDURE CODE (CPT) LOCATION: 2;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,OP) FIELD NUMBER: 26 FIELD NAME: PRIN OPERATIVE PROCEDURE LOCATION: OP;1 ACCESS: Read w/Fileman FIELD NUMBER: 27 FIELD NAME: PRINCIPAL OP CODE LOCATION: OP;2 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,8) FIELD NUMBER: 50 FIELD NAME: DIVISION LOCATION: 8;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF('AC', FIELD NUMBER: 9 FIELD NAME: DATE OF OPERATION FIELD DESCRIPTION: X-REF ON DATE OF OPERATION (FIELD 9) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTERIM MANAGEMENT SUPPORT ISC: Birmingham NUMBER: 58 IA #: 58 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: NOV 27, 1990 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA58 ORIGINAL NUMBER: 58 ID: VA(200, GLOBAL REFERENCE: VA(200,D0,.11) FIELD NUMBER: ALL FIELD DESCRIPTION: All address information FIELD NUMBER: VA(200,D0,.13) FIELD NAME: ALL FIELD DESCRIPTION: All phone information. GLOBAL REFERENCE: VA(200,D0,5) FIELD NUMBER: 29 FIELD NAME: SERVICE/SECTION LOCATION: 5;1 ACCESS: Read w/Fileman FIELD NUMBER: 28 FIELD NAME: MAIL CODE LOCATION: 5;2 ACCESS: Read w/Fileman GLOBAL REFERENCE: VA(200,D0,1) FIELD NUMBER: 5 FIELD NAME: DOB LOCATION: 1;3 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTERIM MANAGEMENT SUPPORT ISC: Birmingham NUMBER: 61 IA #: 61 FILE NUMBER: 36 GLOBAL ROOT: DIC(36, DATE CREATED: NOV 05, 1990 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA61 ORIGINAL NUMBER: 61 ID: DIC(36, GLOBAL REFERENCE: DIC(36,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: MAS may request Social Work to use an MAS supplied utility for future versions. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SOCIAL WORK ISC: Birmingham NUMBER: 62 IA #: 62 FILE NUMBER: 214.6 GLOBAL ROOT: NURSA(214.6, DATE CREATED: OCT 22, 1990 CUSTODIAL PACKAGE: NURSING SERVICE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA62 ORIGINAL NUMBER: 62 ID: NURSA(214.6, GLOBAL REFERENCE: NURSA(214.6,D0,0) FIELD NUMBER: .01 FIELD NAME: CLASSIFICATION DATE/TIME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .02 FIELD NAME: NAME LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: CATEGORY LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: ENTERED BY LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: CLASSIFIER LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 6 FIELD NAME: NURS LOCATION LOCATION: 0;8 ACCESS: Read w/Fileman FIELD NUMBER: 7 FIELD NAME: NURSING BED SECTION LOCATION: 0;9 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Subject to version 2.5 purge allowing 6 months data only. DSS uses the "B" cross reference on the CLASSIFICATION DATE/TIME field. Global: ^NURSA(214.6,"B",DATE,D0) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 63 IA #: 63 FILE NUMBER: 221 GLOBAL ROOT: DENT(221, DATE CREATED: OCT 22, 1990 CUSTODIAL PACKAGE: DENTAL CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA63 ORIGINAL NUMBER: 63 ID: DENT(221, GLOBAL REFERENCE: DENT(221,D0,0) FIELD NUMBER: .01 FIELD NAME: DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: PATIENT (POINTER) LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .5 FIELD NAME: DENTAL PROVIDER LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .3 FIELD NAME: STATION.DIVISION LOCATION: 0;40 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4.5 FIELD NAME: PATIENT CATEGORY LOCATION: 0;19 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6 FIELD NAME: SCREENING/COMPLETE EXAM LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6.2 FIELD NAME: INTERDISCIPLINARY CONSULT LOCATION: 0;42 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6.4 FIELD NAME: EVALUATION LOCATION: 0;43 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6.6 FIELD NAME: PRE AUTH/2ND OPINION EXAM LOCATION: 0;44 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6.7 FIELD NAME: SPOT CHECK EXAM LOCATION: 0;27 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6.8 FIELD NAME: SPOT CHECK DISCREPANCY # LOCATION: 0;45 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7 FIELD NAME: ADMIN PROCEDURE LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7.1 FIELD NAME: COMPLETIONS/TERMINATIONS LOCATION: 0;41 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 8 FIELD NAME: X-RAYS EXTRAORAL # LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 10 FIELD NAME: X-RAYS INTRAORAL # LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 11 FIELD NAME: PROPHY NATURAL DENTITION LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 12 FIELD NAME: PROPHY DENTURE LOCATION: 0;13 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 14 FIELD NAME: NEOPLASM CONFIRMED MALIGNANT # LOCATION: 0;15 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 15 FIELD NAME: NEWPLASM REMOVED # LOCATION: 0;16 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 16 FIELD NAME: BIOPSY/SMEAR # LOCATION: 0;17 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 17 FIELD NAME: FRACTURE # LOCATION: 0;18 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 19 FIELD NAME: OTHER SIGNIF. SURG. (CVT) LOCATION: 0;20 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 21 FIELD NAME: SURFACES RESTORED # LOCATION: 0;22 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 22 FIELD NAME: ROOT CANAL THERAPY # LOCATION: 0;23 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 23 FIELD NAME: PERIODONTAL QUADS (SURGICAL) # LOCATION: 0;24 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 24 FIELD NAME: PERIO QUADS (ROOT PLANE) # LOCATION: 0;25 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 25 FIELD NAME: PATIENT ED. (CTV) LOCATION: 0;26 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 27 FIELD NAME: INDIVIDUAL CROWNS # LOCATION: 0;28 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 28 FIELD NAME: POST & CORES # LOCATION: 0;29 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 29 FIELD NAME: FIXED PARTIALS (ABUT) # LOCATION: 0;30 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 30 FIELD NAME: FIXED PARTIALS (PONT ONLY) # LOCATION: 0;31 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 31 FIELD NAME: REMOVABLE PARTIALS # LOCATION: 0;32 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 32 FIELD NAME: COMPLETE DENTURES # LOCATION: 0;33 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 33 FIELD NAME: PROSTHETIC REPAIR # LOCATION: 0;34 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 34 FIELD NAME: SPLINTS & SPEC. PROCS. (CTV) LOCATION: 0;35 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 35 FIELD NAME: EXTRACTIONS # LOCATION: 0;36 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 36 FIELD NAME: SURGICAL EXTRACTIONS # LOCATION: 0;37 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 37 FIELD NAME: OTHER SIGNIFICANT TREAT (CTV) LOCATION: 0;38 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 38 FIELD NAME: OPERATING ROOM LOCATION: 0;14 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: In addition to the field references as indicated below, a direct global read of the 'B' Cross Reference may be made in the DENTAL TREATMENT (AMIS) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25450725 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany NUMBER: 64 IA #: 64 FILE NUMBER: 392.4 GLOBAL ROOT: DGBT(392.4, DATE CREATED: AUG 21, 1990 CUSTODIAL PACKAGE: BENEFICIARY TRAVEL CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA64 ORIGINAL NUMBER: 64 ID: DGBT(392.4, GLOBAL REFERENCE: DGBT(392.4,D0,0) FIELD NUMBER: .01 FIELD NAME: MODE OF TRANSPORTATION LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Fee Basis points to this file. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: FEE BASIS ISC: Albany NUMBER: 65 IA #: 65 FILE NUMBER: 70 GLOBAL ROOT: RADPT( DATE CREATED: OCT 22, 1990 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: RAD/NUC MED PATIENT file data extract ORIGINAL NUMBER: 65 ID: RADPT( CREATOR: CEBELINSKI,GREGORY GLOBAL REFERENCE: RADPT(D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: RADPT(D0,'DT',D1,0) FIELD NUMBER: .01 FIELD NAME: EXAM DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: HOSPITAL DIVISION LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: IMAGING LOCATION LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: TYPE OF IMAGING LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: RADPT(D0,'DT',D1,'P',D2,0) FIELD NUMBER: 2 FIELD NAME: RADIOLOGY PROCEDURE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6 FIELD NAME: WARD LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7 FIELD NAME: SERVICE LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 13 FIELD NAME: DIAGNOSTIC CODE LOCATION: 0;13 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 14 FIELD NAME: REQUESTING PHYSICIAN LOCATION: 0;14 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: EXAM STATUS LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 8 FIELD NAME: PRINCIPAL CLINIC LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 12 FIELD NAME: PRIMARY INTERPRETING RESIDENT LOCATION: 0;12 ACCESS: Pointed to FIELD NUMBER: 26 FIELD NAME: CREDIT METHOD LOCATION: 0;26 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field indicates the type of credit this location receives for examinations. This field is populated automatically by the system at the time an exam is registered based on the Credit Method entered for the Imaging Location where the exam is registered. If only the interpretation as done at this facility, code 1 should be used. If the exam was performed at this facility, but the interpretation was done elsewhere, code 3 should be used. If both the exam and interpretation were done at this facility, code 0 should be used. If the entire exam was done outside the facility and exam data is being entered for the purposes of record-keeping only, code 2 should be used. FIELD NUMBER: 27 FIELD NAME: VISIT LOCATION: 0;27 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field links the examination of a patient to a specific visit. The VISIT field points to the VISIT (#9000010) file which contains a record of all patient visits at health care facilities or by health care providers, including direct outpatient and clinic visits, as well as inpatient encounters. FIELD NUMBER: 17 FIELD NAME: REPORT TEXT LOCATION: 0;17 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The REPORT TEXT field is a pointer data type which links a radiology study to a radiology report record in the RAD/NUC MED REPORTS file (#74). GLOBAL REFERENCE: RADPT(D0,'DT',D1,'P',D2,'M',D3,0) FIELD NUMBER: .01 FIELD NAME: MODIFIERS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: RADPT(D0,'DT',D1,'P',D2,'CMOD',D3,0) FIELD NUMBER: 135 FIELD NAME: CPT MODIFIERS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: RADPT(D0,'DT',D1,'P',D2,'H', FIELD NUMBER: .01 FIELD NAME: CLINICAL HISTORY FOR EXAM LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: This Integration Agreement allows subscribers to read data from the NAME (#.01) field (top-level, DINUMed) and agreed to fields associated with the REGISTERED EXAMS (#70.02) and EXAMINATIONS (#70.03) sub-files. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 56562528 KEYWORDS: RAD - REGISTERED EXAMS KEYWORDS: RAD - EXAMINATIONS KEYWORDS: RAD - PROCEDURE MODIFIERS 70.1 KEYWORDS: RAD - CPT MODIFIERS 70.3135 KEYWORDS: RAD - CLINICAL HISTORY 70.13 KEYWORDS: RAD - PATIENT (file: #70) KEYWORDS: RAD - EXAM DATE 70.02 KEYWORDS: DSS RAD KEYWORDS: VPS RAD SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham SUBSCRIBING DETAILS: DSS uses the "AR" cross reference on the EXAM DATE field. Global: ^RADPT("AR",DATE,DFN,REV_DATE) DSS uses the "B" cross reference on the EXAM DATE field. Global: ^RADPT(DFN,"DT","B",DATE,REV_DATE) SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE ISC: Oakland SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: Patch # associated with change to ICR is ECX*3*136. It's scheduled to be released on 11/1/12. 06/24/13-MM-OPENED FOR EDITING. 7/19/13-MM: ICR was updated by Greg adding the Visit (#27) field in the Examinations (#70.03) multiple. New field was added for this year's DSS update. DSS is being asked to provide encounter related information (specifically whether or not the encounter is service connected). They will take the VISIT file pointer and make a call to PCE that will return the SC related indicator. Greg indicated it is not an issue for all subscribers to access the Visit field. Dave Naber concurred with the changes for DSS. Associated patch for this change is ECX*3*144. 10/9/14-MC: Added VPS as a subscriber at the request of Carolyn Wheless and approved by Greg Cebelinski for VPS*1*4. VPS needs to return a patient radiology/imaging request to VetLink, including fields 2,3,and 17 from file #70.03 and field 2 from file #70.02. 10/9/14-MC: Deactivated for editing and added Greg Cebelinski as the editor. Greg contacted me and said he needed to make edits to this ICR prior to VPS being added as a subscriber. VPS has been removed as a subscriber while Greg makes his modifications. 10/9/14-MC:Greg Cebelinski has completed his modifications to this ICR. He added a read w/FILEMAN for the REPORT TEXT (70.03-0 node; piece 17). Greg also added VPS as a subscriber to the ICR during his modifications. I have activated the ICR and removed Greg as the editor. DATE ACTIVATED: OCT 09, 2014 DATE/TIME EDITED: MAR 12, 2012@09:23 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CEBELINSKI,GREG WITH CONCURRENCE OF: HARVEY,JULIE DATE/TIME EDITED: APR 27, 2012@11:00 ACTION: APPROVED AT THE REQUEST OF: CEBELINSKI,GREG WITH CONCURRENCE OF: CEBELINSKI,GREG DATE/TIME EDITED: JUN 24, 2013@11:30 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CEBELINSKI,GREG WITH CONCURRENCE OF: CEBELINSKI,GREG DATE/TIME EDITED: JUL 19, 2013@15:06 ACTION: APPROVED AT THE REQUEST OF: CEBELINSKI,GREG WITH CONCURRENCE OF: CEBELINSKI,GREG DATE/TIME EDITED: JUL 19, 2013@15:21 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CEBELINSKI,GREG WITH CONCURRENCE OF: NABER,DAVE DATE/TIME EDITED: OCT 09, 2014@12:22 ACTION: APPROVED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: CEBELENSKI,GREG NUMBER: 71 IA #: 71 DATE CREATED: FEB 01, 1991 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA71 ORIGINAL NUMBER: 71 GENERAL DESCRIPTION: The Laboratory Package developers have granted the Health Summary team permission to add the application group "GMTS" to ^DIC(60, when file 60, the Laboratory test file, exists. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 73 IA #: 73 DATE CREATED: FEB 04, 1991 CUSTODIAL PACKAGE: DIETETICS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA73 ORIGINAL NUMBER: 73 GENERAL DESCRIPTION: Permission has been granted for Health Summary to export the routine: FHWHEA as GMTSFHWZ GMTSPOST, the Health Summary post-init, will rename GMTSFHWZ as FHWHEA, if and only if FHWHEA is not found in the UCI by execution of ^%ZOSF("TEST"). STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 75 IA #: 75 FILE NUMBER: 606 GLOBAL ROOT: YSP(606, DATE CREATED: FEB 04, 1991 CUSTODIAL PACKAGE: MENTAL HEALTH CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA75-A ORIGINAL NUMBER: 75 ID: YSP(606, GENERAL DESCRIPTION: Agreement has been made for Health Summary to access the following fields in the Mental Health Progress Notes files. - The cross-reference ^YSP(606,"AC", is traversed. - Globals accessed are: ^YSP(606, Progress Notes - The following fields are accessed: ^YSP(606, 606 .03 DATE/TIME OF PROGRESS NOTE 606 1 TYPE OF PROGRESS NOTE 606 2 AUTHOR 606.01 .01 TEXT 606.02 .01 SUBJECTIVE 606.021 .01 OBJECTIVE 606.022 .01 ASSESSMENT 606.023 .01 PLANS 606 30 DXLS 606 31 DISCHARGE BED SECTION 606.032A .01 OTHER DIAGNOSES 606.033 .01 OPERATIONS/PROCEDURES 606.034 .01 INSTRUCTIONS GIVEN TO PATIENT 606.04 .01 EMOTIONAL STATE 606.041 .01 BEHAVIORAL ASSESSMENT 606.042 .01 SOCIAL STATUS 606.043 .01 REHABILITATION POTENTIAL 606.044 .01 EMPLOYMENT POTENTIAL 606.045 .01 DEGREE OF DANGER - SELF/OTHERS 606.046 .01 ABNORMAL PHYSICAL FINDINGS 606.047 .01 INIT IMPRESSION/PROVISIONAL DX 606.048 .01 STATEMENT OF TREATMENT PLANNED 606.03 .01 COMMENTS/CORRECTIONS STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 77 IA #: 77 FILE NUMBER: 115 GLOBAL ROOT: FHPT( DATE CREATED: FEB 04, 1991 CUSTODIAL PACKAGE: DIETETICS CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA77 ORIGINAL NUMBER: 77 ID: FHPT( GENERAL DESCRIPTION: The following fields will be accessed to get patient food allergies: ^FHPT( 115 DIETETICS PATIENT .1 Food Allergies STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 78 IA #: 78 DATE CREATED: FEB 05, 1991 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA78 ORIGINAL NUMBER: 78 GENERAL DESCRIPTION: The Vitals Package developers have granted the Health Summary team permission to add the application group "GMTS" to ^DIC(120.51, when file 120.51, the Vital Type file, exists. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 80 IA #: 80 FILE NUMBER: 690 GLOBAL ROOT: MCAR(690, DATE CREATED: FEB 05, 1991 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA80-A ORIGINAL NUMBER: 80 ID: MCAR(690, GLOBAL REFERENCE: MCAR(690,'AC' GENERAL DESCRIPTION: This DBIA documents references to the MEDICAL PATIENT file (#690). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30446053 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: The Health Summary exports and calls the routine GMTSMCPS, which generates the output for the Health Summary Medicine component. The following fields and cross references are being referenced: ^MCAR(690, Medical Patient File Uses "AC" cross reference SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: SURGERY SUBSCRIBING DETAILS: ADDED 5/12/2011 DATE/TIME EDITED: MAY 12, 2011@11:36 NUMBER: 85 IA #: 85 FILE NUMBER: 195.4 GLOBAL ROOT: DIC(195.4, DATE CREATED: JUL 09, 1991 CUSTODIAL PACKAGE: RECORD TRACKING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA85-A ORIGINAL NUMBER: 85 ID: DIC(195.4, GENERAL DESCRIPTION: 1. Activation interface 2. Make an appointment Checkin/unscheduled visit 3. Cancel an appointment 4. Changing clinic names 1. Use of the Record Tracking System Parameter file # 195.4 SD calls RT if the field 'MAS INTERFACE STATUS' is 'UP' ^DIC(195.4,1,"UP")=1^ 2. When a clinic appointment is made if the appointment is 'today' or if the Record Tracking System Parameter 'Batch requests' is set to 'No' or if records are requested for an unscheduled visit. A. An entry is made in the Requested Records file #190.1 ^RTV(190.1,n) by a call from RT^SDUTL to a tasked job QUE^RTQ or RT^SDI B. After the entry is added to the Requested Records file #190.1 an entry is made in Parent Record Request field of the Patient subfield of the Hospital Location file #44 ^SC(n,"S",,,,"RTR")=n^ by a return call from CREATE+11^RTQ2 to RTSET^SDUTL 3. When a clinic appointment is canceled: If there is a Requested Records entry in file #190.1 the status is changed to 'canceled' by a call RTV(190.1,n)=^^^^^x^ from RT+2^SDUTL to CANCEL^RTQ2. 4. When the name of a clinic is changed the corresponding names of entries in the Pull List file #194.2 are changed by a trigger on the .01 field of the Hospital Location file #44. Clinic ^SC(1,0)=DJones Medical Clinic^ ^RTV(194.2,n)=Dr Jones Medical Clinic [04/01/91]^ Clinic names are changed in a compiled input template. To insure the use of this trigger the following action is taken: The Record Tracking package includes the .01 field of the Hospital Location file #44 so that the SDB template is re-compiled when the Record Tracking package is initialized. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 87 IA #: 87 FILE NUMBER: 41.1 GLOBAL ROOT: DGS(41.1, DATE CREATED: JUL 10, 1991 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA87-A ORIGINAL NUMBER: 87 ID: DGS(41.1, GENERAL DESCRIPTION: SCHEDULED ADMISSION FILE: Loops through ARSV x-ref and looks at RESERVATION DATE/TIME field. (routine YSCEN) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Salt Lake City NUMBER: 88 IA #: 88 DATE CREATED: AUG 06, 1991 CUSTODIAL PACKAGE: GRECC CUSTODIAL ISC: Washington USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA88-A ORIGINAL NUMBER: 88 GENERAL DESCRIPTION: 1. The 'DG' package for MAS v5.1 will be exporting the following Generic Code Sheet input templates: a. DG AMS1 AMIS from file 2100 b. DG AMS1 AMIS 334 from file 2100 c. DG AMS1 AMIS 336 from file 2100 d. DG AMS1 AMIS 345 from file 2100 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 89 IA #: 89 FILE NUMBER: 411 GLOBAL ROOT: PRC(411, DATE CREATED: AUG 08, 1991 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA89 ORIGINAL NUMBER: 89 ID: PRC(411, GENERAL DESCRIPTION: Read access to File 411, ADMIN. ACTIVITY SITE PARAMETER, following fields: field 15 HOSPITAL STREET ADDR.1 field 16 HOSPITAL STREET ADDR.2 field 17 HOSPITAL CITY field 18 HOSPITAL STATE field 19 HOSPITAL ZIP field 19.2 HOSPITAL PHONE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12037950 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham DBA Comments: MENTAL HEALTH REMOVED AS SUBSCRIBER 6.30.08 AS PER RANDY MORTON DATE/TIME EDITED: JUN 30, 2008@13:00 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: MORTON,RANDY NUMBER: 91 IA #: 91 FILE NUMBER: 60 GLOBAL ROOT: LAB(60, DATE CREATED: SEP 11, 1991 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA91-A ORIGINAL NUMBER: 91 ID: LAB(60, GLOBAL REFERENCE: LAB(60,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: TEST COST LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: SUBSCRIPT LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5 FIELD NAME: LOCATION (DATA NAME) LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LAB(60,'B', GLOBAL DESCRIPTION: The 'B' cross-reference is used to locate patient data by the specific Laboratory Test Name. GLOBAL REFERENCE: LAB(60,'C', GLOBAL DESCRIPTION: The 'C' cross-reference is used to locate the Laboratory Test Name when all data for a selected patient is being evaluated based on the Location (DATA NAME) for a particular result GLOBAL REFERENCE: LAB(60,D0,2) GLOBAL DESCRIPTION: This is a check used in DIC('S') for LAB TESTS INCLUDED IN PANEL in the following manner: S DIC("S")="I '$D(^LAB(60,+Y,2))" S DIC("?")="The lab test may not be a panel of tests." S DIC="60",DIC(0)="AEQMZ" F D ^DIC Q:Y=-1 D STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11757790 SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION ISC: Oakland SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS SUBSCRIBING DETAILS: ADDED 4/23/09 DATE/TIME EDITED: JUN 08, 2009@12:21 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MCDEARMON,JAMES NUMBER: 92 IA #: 92 FILE NUMBER: 45 GLOBAL ROOT: DGPT( DATE CREATED: SEP 11, 1991 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA92 ORIGINAL NUMBER: 92 ID: DGPT( GLOBAL REFERENCE: DGPT(D0,0) FIELD NUMBER: 2 FIELD NAME: ADMISSION DATE LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 5 FIELD NAME: SUFFIX LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 6 FIELD NAME: STATUS LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 11 FIELD NAME: TYPE OF RECORD LOCATION: 0;11 ACCESS: Read w/Fileman FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Field need added for CIRN GLOBAL REFERENCE: DGPT(D0,70) FIELD NUMBER: 70 FIELD NAME: DISCHARGE DATE LOCATION: 70;1 ACCESS: Read w/Fileman FIELD NUMBER: 71 FIELD NAME: DISCHARGE SPECIALTY LOCATION: 70;2 ACCESS: Read w/Fileman FIELD NUMBER: 72 FIELD NAME: TYPE OF DISPOSITION LOCATION: 70;3 ACCESS: Read w/Fileman FIELD NUMBER: 79 FIELD NAME: DXLS LOCATION: 70;10 ACCESS: Read w/Fileman FIELD NUMBER: 79.16 FIELD NAME: ICD 2 LOCATION: 70;16 ACCESS: Read w/Fileman FIELD NUMBER: 79.17 FIELD NAME: ICD 3 LOCATION: 70;17 ACCESS: Read w/Fileman FIELD NUMBER: 79.18 FIELD NAME: ICD 4 LOCATION: 70;18 ACCESS: Read w/Fileman FIELD NUMBER: 79.19 FIELD NAME: ICD 5 LOCATION: 70;19 ACCESS: Read w/Fileman FIELD NUMBER: 79.201 FIELD NAME: ICD 6 LOCATION: 70;20 ACCESS: Read w/Fileman FIELD NUMBER: 79.21 FIELD NAME: ICD 7 LOCATION: 70;21 ACCESS: Read w/Fileman FIELD NUMBER: 79.22 FIELD NAME: ICD 8 LOCATION: 70;22 ACCESS: Read w/Fileman FIELD NUMBER: 79.23 FIELD NAME: ICD 9 LOCATION: 70;23 ACCESS: Read w/Fileman FIELD NUMBER: 79.24 FIELD NAME: ICD 10 LOCATION: 70;24 ACCESS: Read w/Fileman FIELD NUMBER: 73 FIELD NAME: OUTPATIENT TREATMENT LOCATION: 70;4 ACCESS: Read w/Fileman FIELD NUMBER: 80 FIELD NAME: PRINCIPAL DIAGNOSIS LOCATION: 70;11 ACCESS: Read w/Fileman FIELD DESCRIPTION: Field need added for CIRN GLOBAL REFERENCE: DGPT(D0,'M',D1,0) FIELD NUMBER: 2 FIELD NAME: LOSING SPECIALTY LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 5 FIELD NAME: ICD 1 LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 6 FIELD NAME: ICD 2 LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 7 FIELD NAME: ICD 3 LOCATION: 0;7 ACCESS: Read w/Fileman FIELD NUMBER: 8 FIELD NAME: ICD 4 LOCATION: 0;8 ACCESS: Read w/Fileman FIELD NUMBER: 9 FIELD NAME: ICD 5 LOCATION: 0;9 ACCESS: Read w/Fileman FIELD NUMBER: 10 FIELD NAME: MOVEMENT DATE LOCATION: 0;10 ACCESS: Read w/Fileman FIELD DESCRIPTION: Accessed via 'AM' cross-reference FIELD NUMBER: 11 FIELD NAME: ICD 6 LOCATION: 0;11 ACCESS: Read w/Fileman FIELD NUMBER: 12 FIELD NAME: ICD 7 LOCATION: 0;12 ACCESS: Read w/Fileman FIELD NUMBER: 13 FIELD NAME: ICD 8 LOCATION: 0;13 ACCESS: Read w/Fileman FIELD NUMBER: 14 FIELD NAME: ICD 9 LOCATION: 0;14 ACCESS: Read w/Fileman FIELD NUMBER: 15 FIELD NAME: ICD 10 LOCATION: 0;15 ACCESS: Read w/Fileman GLOBAL REFERENCE: DGPT(D0,'P',D1,0) FIELD NUMBER: .01 FIELD NAME: PROCEDURE DATE LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: PROCEDURE CODE 1 LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 5 FIELD NAME: PROCEDURE CODE 2 LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 6 FIELD NAME: PROCEDURE CODE 3 LOCATION: 0;7 ACCESS: Read w/Fileman FIELD NUMBER: 7 FIELD NAME: PROCEDURE CODE 4 LOCATION: 0;8 ACCESS: Read w/Fileman FIELD NUMBER: 8 FIELD NAME: PROCEDURE CODE 5 LOCATION: 0;9 ACCESS: Read w/Fileman GLOBAL REFERENCE: DGPT(D0,'S',D1,0) FIELD NUMBER: .01 FIELD NAME: SURGERY/PROCEDURE DATE LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 8 FIELD NAME: OPERATION CODE 1 LOCATION: 0;8 ACCESS: Read w/Fileman FIELD NUMBER: 9 FIELD NAME: OPERATION CODE 2 LOCATION: 0;9 ACCESS: Read w/Fileman FIELD NUMBER: 10 FIELD NAME: OPERATION CODE 3 LOCATION: 0;10 ACCESS: Read w/Fileman FIELD NUMBER: 11 FIELD NAME: OPERATION CODE 4 LOCATION: 0;11 ACCESS: Read w/Fileman FIELD NUMBER: 12 FIELD NAME: OPERATION CODE 5 LOCATION: 0;12 ACCESS: Read w/Fileman GLOBAL REFERENCE: DGPT('B',X,DA) GLOBAL DESCRIPTION: Eligible records will be determined by using the 'b' cross reference to determine matches with patients. GENERAL DESCRIPTION: Amended October 28, 1997. fields DGPT(D0,0) .01 and DGPT(D0,70) 80 added for CIRN 11/24/98 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25328407 SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY ISC: Hines SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION ISC: Oakland SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: LEXICON UTILITY SUBSCRIBING DETAILS: The Lexicon Package needs to be able to query files 45 for the purpose of DRG calculation to verify that versioned data is correct. Effctive with LEX*2.0*80. DBA Comments: 07/10/13 DLT: Added LEXICON UTILITY as subscriber, effective with LEX*2.0*80. DATE/TIME EDITED: JUL 10, 2013@11:54 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: ROWE,KIMBALL WITH CONCURRENCE OF: VILLELLA,ROSS NUMBER: 93 IA #: 93 FILE NUMBER: 44 GLOBAL ROOT: SC( DATE CREATED: FEB 17, 2005 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA93-A ORIGINAL NUMBER: 93 ID: SC( GLOBAL REFERENCE: SC(D0,0) FIELD NUMBER: 8 FIELD NAME: STOP CODE NUMBER LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11757796 SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY ISC: Oakland SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION ISC: Oakland SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS SUBSCRIBING PACKAGE: MYHEALTHEVET SUBSCRIBING DETAILS: Added 2/15/13 for MHV*1.0*10. DBA Comments: 2/15/13 DT: MHV was added as subscriber. The MHV*1.0*10 patch introduces the new access. DATE/TIME EDITED: FEB 15, 2013@16:44 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MARRI,NAGARAJA WITH CONCURRENCE OF: SCHUSTER,BARBARA NUMBER: 94 IA #: 94 DATE CREATED: SEP 23, 1991 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA94 ORIGINAL NUMBER: 94 GENERAL DESCRIPTION: As a requirement for the AMIE C&P (phase III), Central Office requested that we report lab and X-ray results in conjunction with the examination. After speaking with Troy about such a venture and attempting to procure an agreement to make calls to the Radiology package, it was decided that it would be better for them to write a special routine for AMIE purposes. I have initially set this up under my DVBC national name space and will rename it (using Kernel tools) to RAUTL3 which is its true name. However, before doing this I check to see if it already exists. As the package cannot function without this and some sites may not have the latest Radiology package up (v 4.0, I think) by the time it is sent out nationally (probably 1/92), I have been advised by Troy to request an agreement to export this and rename it. This would be required just for the initial release. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 95 IA #: 95 FILE NUMBER: 63 GLOBAL ROOT: LR( DATE CREATED: SEP 24, 1991 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA95-A ORIGINAL NUMBER: 95 ID: LR( GLOBAL REFERENCE: LR(D0,'CH', GLOBAL REFERENCE: LR(D0,'MI', GENERAL DESCRIPTION: Request an agreement with the lab developers for usage of the following: Cross-references: CH xref in ^LR MI xref in ^LR STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: COMPENSATON AND PENSION ISC: Albany NUMBER: 97 IA #: 97 FILE NUMBER: 730 GLOBAL ROOT: ECC(730, DATE CREATED: AUG 26, 1991 CUSTODIAL PACKAGE: EVENT CAPTURE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA97-A ORIGINAL NUMBER: 97 ID: ECC(730, GENERAL DESCRIPTION: The DSS developers have agreed that the IMS developers may export file 730 (NATIONAL SERVICE) with data and field 730 (NATIONAL SERVICE) in file 49 (SERVICE/SECTION) with no data. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTERIM MANAGEMENT SUPPORT ISC: Birmingham NUMBER: 98 IA #: 98 DATE CREATED: MAR 20, 1991 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA98-A ORIGINAL NUMBER: 98 GENERAL DESCRIPTION: Version 5.1 of the laboratory package has a temporary agreement for the following: 1) To save system $Z variables in local variables for storage in our error trap. When Kernel release their error trapping system, Lab will convert to the Kernel supported methodology. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: LAB SERVICE ISC: Salt Lake City NUMBER: 99 IA #: 99 FILE NUMBER: 730 GLOBAL ROOT: ECC(730, DATE CREATED: JUL 27, 1991 CUSTODIAL PACKAGE: EVENT CAPTURE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA99 ORIGINAL NUMBER: 99 ID: ECC(730, GENERAL DESCRIPTION: The agreement consists of the following: 1) Credentials Tracking package will include the field GENERAL PRIVILEGE (#747) and associated data in the National Service fle (#730). 2) Credentials Tracking will export the National Service file (#730). This export will only install the data dictionary for file 730 if the dictionary does not exist on the system. If file 730 does exist, Credentials Tracking will not overwrite the data dictionary. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CREDENTIALS TRACKING ISC: Hines NUMBER: 100 IA #: 100 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: SEP 25, 1991 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA100 ORIGINAL NUMBER: 100 ID: VA(200, GENERAL DESCRIPTION: The agreement consists of the following: 1) The Credentials Tracking module will incorperate fields in the NEW PERSON file within the field number range of 747-747.999. Data node for these fields will be in the QAR namespace (ex. QAR1, QAR17, etc). Sub-data dictionary numbers will be within the 200.0747-200.074799999 range. The right is reserved to use the QAR and AQAR prefix for any cross-reference indicies. 2) The Credentials Tracking module will export a "clean" partial data dictionay for file 200. This partial will include only the 747 number spaced fields and the .01 name field. The partial was created in an environment that contained only the 747 numberspaced fields and a partial of the .01 name field. The .01 name field contains only the basic field definition, "B" cross- reference (only), and the input transform. All other fields and information were deleted. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CREDENTIALS TRACKING ISC: Hines NUMBER: 101 IA #: 101 FILE NUMBER: 453 GLOBAL ROOT: PRSP(453, DATE CREATED: AUG 26, 1991 CUSTODIAL PACKAGE: PAID CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA101 ORIGINAL NUMBER: 101 ID: PRSP(453, GENERAL DESCRIPTION: The agreement consists of the following: 1) Credentials Tracking module will include fields in the 747-747.999 number range. 2) Credentials Tracking will export the APPLICANT file (#453) partial data-dictionary. The partial will include only fields in the 747-747.999 number range, and those other fields in the APPLICANT file that Credentials Tracking is dependant upon. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CREDENTIALS TRACKING ISC: Hines NUMBER: 103 IA #: 103 FILE NUMBER: 130 GLOBAL ROOT: SRF( DATE CREATED: JUL 28, 1991 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: SURGERY file (#130) ORIGINAL NUMBER: 103 ID: SRF( CREATOR: MONOSKY,ALAN GLOBAL REFERENCE: SRF(D0,0) FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: OPERATING ROOM LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: SURGERY SPECIALTY LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .09 FIELD NAME: DATE OF OPERATION LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .011 FIELD NAME: IN/OUT-PATIENT STATUS LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: DSS reads the entire zero node into a local variable. The fields above are used. GLOBAL REFERENCE: SRF(D0,.1) FIELD NUMBER: .14 FIELD NAME: SURGEON LOCATION: .1;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .164 FIELD NAME: ATTEND SURG LOCATION: .1;13 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: DSS reads the entire .1 node into a local variable. The fields above are used. GLOBAL REFERENCE: SRF(D0,.2) FIELD NUMBER: .21 FIELD NAME: ANES CARE START TIME LOCATION: .2;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .22 FIELD NAME: TIME OPERATION BEGAN LOCATION: .2;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .23 FIELD NAME: TIME OPERATION ENDS LOCATION: .2;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .24 FIELD NAME: ANES CARE END TIME LOCATION: .2;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .205 FIELD NAME: TIME PAT IN OR LOCATION: .2;10 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .232 FIELD NAME: TIME PAT OUT OR LOCATION: .2;12 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .203 FIELD NAME: TIME PAT IN HOLD AREA LOCATION: .2;15 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .234 FIELD NAME: OR CLEAN START TIME LOCATION: .2;13 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .236 FIELD NAME: OR CLEAN END TIME LOCATION: .2;14 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: DSS reads the entire .2 node into a local variable. The fields above are used. GLOBAL REFERENCE: SRF(D0,.3) FIELD NUMBER: .34 FIELD NAME: ANESTHESIOLOGIST SUPVR LOCATION: .3;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .31 FIELD NAME: PRINCIPAL ANESTHETIST LOCATION: .3;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: PROSTHESIS ITEM LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: From the PROSTHESIS INSTALLED multiple (.47). GLOBAL REFERENCE: SRF(D0,1,D1,1) FIELD NUMBER: 7 FIELD NAME: QUANTITY LOCATION: 1;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: SRF(D0,1.1) FIELD NUMBER: 1.17 FIELD NAME: ADMIT PAC(U) TIME LOCATION: 1.1;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.18 FIELD NAME: PAC(U) DISCH TIME LOCATION: 1.1;8 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: SRF(D0,6,D1,0) FIELD NUMBER: .01 FIELD NAME: ANESTHESIA TECHNIQUE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .05 FIELD NAME: PRINCIPAL TECH LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: From the ANESTHESIA TECHNIQUE multiple (.37). GLOBAL REFERENCE: SRF(D0,8) FIELD NUMBER: 50 FIELD NAME: DIVISION LOCATION: 8;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: SRF(D0,13,D1,2) FIELD NUMBER: 3 FIELD NAME: OTHER PROCEDURE CPT CODE LOCATION: 2;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: From the OTHER PROCEDURES multiple (.42). GLOBAL REFERENCE: SRF(D0,30) FIELD NUMBER: 17 FIELD NAME: CANCEL DATE LOCATION: 30;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: SRF(D0,NON) FIELD NUMBER: 118 FIELD NAME: NON-OR PROCEDURE LOCATION: NON;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 119 FIELD NAME: NON-OR LOCATION LOCATION: NON;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 121 FIELD NAME: TIME PROCEDURE BEGAN LOCATION: NON;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 122 FIELD NAME: TIME PROCEDURE ENDED LOCATION: NON;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 123 FIELD NAME: PROVIDER LOCATION: NON;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 124 FIELD NAME: ATTEND PROVIDER LOCATION: NON;7 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: DSS reads the entire NON node into a local variable. The fields above are used. GLOBAL REFERENCE: SRF(D0,OP) FIELD NUMBER: 27 FIELD NAME: PRINCIPAL PROCEDURE CODE LOCATION: OP;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 26 FIELD NAME: PRINCIPAL PROCEDURE LOCATION: OP;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: DSS reads the entire OP node into a local variable. The field above is used. GLOBAL REFERENCE: SRF(D0,OPMOD,D1,0) FIELD NUMBER: 28 FIELD NAME: PRIN. PROCEDURE CPT MODIFIER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: SRF(D0,13,D1,MOD,D2,0) FIELD NUMBER: 4 FIELD NAME: OTHER PROCEDURE CPT MODIFIER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: SRF(D0,CON) FIELD NUMBER: 35 FIELD NAME: CONCURRENT CASE LOCATION: CON;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The CONCURRENT CASE (#35) field was added to this ICR in support of the FY14 Annual Sustainment patch ECX*3*144. Access to the CONCURRENT CASE field will not be reliable after a site has implemented Surgery Quality and Workflow Manager (SQWM), patch SR*3*180. The handling of concurrent cases is different in SQWM than in VistA Surgery. After SQWM implementation, concurrent case information must be accessed by other means yet to be determined as of the date of adding the CONCURRENT CASE field to this ICR. GENERAL DESCRIPTION: The DSS Extracts SURGERY EXTRACT file (#727.811) contains a field, CASE NUMBER, which is a pointer to the SURGERY file (#130). DSS Extracts has permission to execute direct global reads of the 'B' Cross Reference on the SURGERY file (#130). DSS uses the "ADT" and "AC" cross references on the DATE OF OPERATION field: Global: ^SRF("ADT",DFN,DATE) Global: ^SRF("AC",DATE,IEN)=DFN STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30358729 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham DBA Comments: 10/24/13 DT: Activated ICR, where the concurrent case field (#35) will be extracted for use in DSS, effective with the ECX*3*144 patch. The Surgery Quality and Workflow Manager (SQWM), patch SR*3*180 is under development at the time of this ICR activation, which could impact this ICR. The SQWM and DSS packages will work together in the future to ensure the extracts can access concurrence case data. Stakeholders on 10/24/13 are Danny Reed, Mike Montali, and David Naber. 10/17/13 DT: Added Alan as editor. DATE ACTIVATED: OCT 24, 2013 DATE/TIME EDITED: OCT 17, 2013@12:38 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: NABER,DAVID WITH CONCURRENCE OF: MONOSKY,ALAN DATE/TIME EDITED: OCT 24, 2013@16:17 ACTION: APPROVED AT THE REQUEST OF: NABER,DAVID WITH CONCURRENCE OF: MONOSKY,ALAN NUMBER: 111 IA #: 111 DATE CREATED: MAY 14, 1991 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGAINP3 NAME: DBIA111-A ORIGINAL NUMBER: 111 ID: DGAINP3 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: 1) AMIS Segments 334-341 This entry point prints the inpatient AMIS segments 334-341 for a select month/year. If the variable DGMYR is not defined, the user will be prompted for the AMIS month/year to print. SUBSCRIBING PACKAGE: INTERIM MANAGEMENT SUPPORT ISC: Birmingham NUMBER: 115 IA #: 115 FILE NUMBER: 195.4 GLOBAL ROOT: DIC(195.4, DATE CREATED: AUG 24, 1991 CUSTODIAL PACKAGE: RECORD TRACKING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA115-A ORIGINAL NUMBER: 115 ID: DIC(195.4, GENERAL DESCRIPTION: Use of the Record Tracking System Parameter file # 195.4. RA calls RT if the field 'RADIOLOGY INTERFACE STATUS' is 'UP', ^DIC(195.4,1,"UP")=^1, and checks if the record tracking radiology application is defined . $D(^DIC(195.4,1,"RAD")) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14682303 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Albany NUMBER: 116 IA #: 116 FILE NUMBER: 70 GLOBAL ROOT: RADPT( DATE CREATED: AUG 24, 1991 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA116 ORIGINAL NUMBER: 116 ID: RADPT( GENERAL DESCRIPTION: With Record Tracking implementaion, records may be created for for all the entries in Radiology Patient file. When using the Record Tracking (radiology application) the routines RTSM1 and RTSM3 look at the Radiology Patient file #70 ^RADPT(dfn,0) => ^RT(n,0)=dfn;DPT(^ to create entries in the Records file #190 for each radiology patient when initializing records. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: RECORD TRACKING ISC: Albany NUMBER: 118 IA #: 118 FILE NUMBER: 70 GLOBAL ROOT: RADPT( DATE CREATED: NOV 09, 2005 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA118-A ORIGINAL NUMBER: 118 ID: RADPT( GLOBAL REFERENCE: RADPT(D0,'DT',D1,0) FIELD NUMBER: .01 FIELD NAME: EXAM DATE LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: The ICR package may use a direct global read to get the EXAM DATE value. GLOBAL REFERENCE: RADPT(D0,'DT',D1,'P',D2,0) FIELD NUMBER: 2 FIELD NAME: RADIOLOGY PROCEDURE LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: EXAM STATUS LOCATION: 0;3 ACCESS: Read w/Fileman GLOBAL REFERENCE: RADPT(D0,'DT',D1,'P',D2,'M',D3,0) FIELD NUMBER: .01 FIELD NAME: MODIFIERS LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Amended October 28, 1997. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25328389 SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY ISC: Hines SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION ISC: Oakland NUMBER: 119 IA #: 119 GLOBAL ROOT: %ZTSCH( DATE CREATED: OCT 31, 1991 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA119 ORIGINAL NUMBER: 119 ID: %ZTSCH( GLOBAL REFERENCE: %ZTSCH('RUN') GENERAL DESCRIPTION: Routine PRCFQ uses the following extrinsic function to determine whether Taskman is runnig: TM() ;extrinsic function--is taskman running? N ZTH,ZTR S ZTH=$H,ZTR=$S(^%ZTSCH("RUN"))#2:^("RUN"),1:"") Q ZTH-ZTR*86400+$P(ZTH,",",2)-$P(ZTR,",",2)<500 Till otherwise agreed, or release of Kernel 8 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring NUMBER: 120 IA #: 120 FILE NUMBER: 195.4 GLOBAL ROOT: DIC(195.4, DATE CREATED: AUG 24, 1991 CUSTODIAL PACKAGE: RECORD TRACKING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA120-A ORIGINAL NUMBER: 120 ID: DIC(195.4, GLOBAL REFERENCE: DIC(195.4,1,'UP') GENERAL DESCRIPTION: 1. Use of the Record Tracking System Parameter file # 195.4: DG calls RT if the field 'MAS INTERFACE STATUS' is 'UP' ^DIC(195.4,1,"UP")=1^ STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 121 IA #: 121 FILE NUMBER: 2 GLOBAL ROOT: PATIENT FILE DATE CREATED: SEP 05, 1991 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA121 ORIGINAL NUMBER: 121 ID: PATIENT FILE GLOBAL REFERENCE: DD(2,.351,1,6, GENERAL DESCRIPTION: APSJD X-reference on field .351, DATE OF DEATH, of file 2, PATIENT not used for sorting or look up. The code is: set: S XX=X,X="PSJADT" X ^%ZOSF("TEST") I S X=XX D END^PSJADT kill: Q The event driver messages are not displayed. ^DD(2,.351,1,6,0) = 2^APSJD^MUMPS ^DD(2,.351,1,6,1) = S XX=X,X="PSJADT" X ^%ZOSF("TEST") I S X=XX D END^PSJ ADT ^DD(2,.351,1,6,2) = Q ^DD(2,.351,1,6,"%D",0) = ^^2^2^2910806^ ^DD(2,.351,1,6,"%D",1,0) = Pharmacy cross-reference for notification upon entry/deletion of date of ^DD(2,.351,1,6,"%D",2,0) = death information. ^DD(2,.351,1,6,"DT") = 2910806 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 124 IA #: 124 DATE CREATED: NOV 06, 1991 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOCPVW NAME: DBIA124-A ORIGINAL NUMBER: 124 ID: PSOCPVW GENERAL DESCRIPTION: Routine PSOCPVW is called by Integrated Billing to display information from the Prescription file (52) to provide a full profile of the prescription that caused the Co-Pay Charges. Input Variable: X $P1: RX Entry Number. The pointer to the Prescription file. $P2: Refill. The second piece is delimited by a colon is optional, if defined is expected to be the entry number of the refill multiple that caused the charges if the charges were created by a refill. Output Writes pertinent data from the prescription file for the requested entry in captioned format. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: PSOCPVW VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Requires X = "RXN^fill #" e.g. X="3007^2" means second refill of RX in ^PSRX(3007, . "3007^0" would mean oringinal fill. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 125 IA #: 125 DATE CREATED: NOV 06, 1991 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBARX NAME: DBIA125-A ORIGINAL NUMBER: 125 ID: IBARX GENERAL DESCRIPTION: This private agreement between PSO and IB will allow for PSO to notify IB when an Outpatient Medication Co-payment bill needs to be created, updated, or cancelled. It will also allow PSO to cancel or update a potential charge. There are also entry points for PSO to verify that a patient is subject to Pharmacy Co-payment and allow PSO to check the status of a Co-payment charge. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33578419 COMPONENT/ENTRY POINT: XTYPE COMPONENT DESCRIPTION: Supported for Outpatient Pharmacy for determining eligibility for Co-payment and correct IB ACTION TYPE. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: $P1: Service. Pointer to Service/Section file (49) for Pharmacy service $P2: Patient. Pointer to Patient file (2) (DFN) VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: $P1: Success. Returns 1 if successful or -1 if unsuccessful determination $P2: If unsuccessful error code VARIABLES: Y(action type,n) TYPE: Output VARIABLES DESCRIPTION: sub: First subscript. New Action Types for Service, pointer to IB ACTION TYPE file (350.1). sub: Second subscript. Value n (n = 0, 1, or 2) where 0 indicates this action type not billable, 1 indicates it is billable, 2 indicates that additional information is needed $P1: Action Type. Pointer to the IB ACTION TYPE file (350.1) $P2: Unit Cost. The dollar charge for one unit $P3: Service. Pointer to Service/Section file (49) for service that can use this action type COMPONENT/ENTRY POINT: NEW COMPONENT DESCRIPTION: Supported for Outpatient Pharmacy to process charges for new, renew, or refilled prescriptions VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: $P1: Service. Pointer to Service Section file (49) $P2: Patient. Pointer to the Patient File (2) (DFN) $P3: Action Type. Pointer to the IB Action Type file (350.1) $P4: User. Pointer to New Person file (200) (DUZ) VARIABLES: X(n) TYPE: Input VARIABLES DESCRIPTION: sub: First subscript. Any value, same value is returned in Y(n) $P1: Softlink. Link to prescription file for entry causing charges in the format of: file number:entry pointer;[node:sub-entry;node:sub-entry...] $P2: Units. The number of units to be charged VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: $P1: Success flag. Returns 1 if successful, -1 if unsuccessful $P2: Grand Total. Sum of total charges if successful, error code if unsuccessful VARIABLES: Y(n) TYPE: Output VARIABLES DESCRIPTION: sub: First subscript. Any value, same value as passed in X(n) $P1: IB Action Entry. Pointer to Integrated Billing file 350 $P2: Total Charges. Charges for this entry $P3: AR Charge ID. Accounts receivable Charge ID (Bill Number), name field from Accounts Receivable file (430) $P4: Cap met flag (1=yes,0=no) $P5: Full or Partial bill ("F", "P" or "") $P6: Exempt (1=exempt,0=non-exempt,-1=copay off) $P7: IEN from file 354.71 COMPONENT/ENTRY POINT: CANCEL COMPONENT DESCRIPTION: Supported for Outpatient Pharmacy to remove charges for one new, renewed, or refilled prescription. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: $P1: Service. Pointer to the Service/Section file for Pharmacy service $P2: Patient. Pointer to the Patient File (2) (DFN) $P3: Null $P4: User. Pointer to the New Person file (200) (DUZ) VARIABLES: X(n) TYPE: Input VARIABLES DESCRIPTION: sub: First subscript. Any value, same value as returned in Y(n) $P1: Integrated Billing Action. Action to be canceled, pointer to the Integrated Billing Action file (350) $P2: Charge Removal Reason. Reason for the cancellation pointer to the IB Charge Removal Reasons file (350.3) VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: $P1: Success flag. Returns 1 if successful, -1 if unsuccessful $P2: Error Code. Error code from IB Error file (350.8) if unsuccessful, Null if successful VARIABLES: Y(n) TYPE: Output VARIABLES DESCRIPTION: $P1: Integrated Billing Action. IB Action that is the result of the cancellation, pointer to Integrated Billing Action file (350) if successful or -1^error code if unsuccessful $P2: Error Code. Error code from IB Error file (350.8) if unsuccessful, Null if successful COMPONENT/ENTRY POINT: UPDATE COMPONENT DESCRIPTION: To update charges when the days supply has been edited to change the number of units to be charged. (Note: for audit purposes this call actually cancels the most recent charges and processes new charges for the current amount) VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: $P1: Service. Pointer to the Service/Section file for Pharmacy service $P2: Patient. Pointer to the Patient File (2) (DFN) $P3: Action Type. Pointer to the IB Action Type file (350.1) $P4: User. Pointer to the New Person file (200) (DUZ) VARIABLES: X(n) TYPE: Input VARIABLES DESCRIPTION: sub: First subscript. Any value, same value is returned in Y(n) $P1: Softlink. Link to prescription file for entry causing charges in the format of: file number:entry pointer;[node:sub-entry;node:sub-entry...] $P2: Units. The number of units to be charged $P3: Integrated Billing Action. Action to be canceled, pointer to the Integrated Billing Action file (350) $P4: Charge Removal Reason. Reason for the cancellation pointer to file 350.3 VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: $P1: Success flag. Returns 1 if successful, -1 if unsuccessful $P2: Error Code. Error code from IB Error file (350.8) if unsuccessful, Null if successful VARIABLES: Y(n) TYPE: Output VARIABLES DESCRIPTION: $P1: Integrated Billing Action. IB Action that is the result of the cancellation, pointer to Integrated Billing Action file (350) if successful or returns -1 if unsuccessful $P2: Total charge this entry $P3: AR bill number $P4: Cap met flag (1=yes,0=no) $P5: Full or Partial bill ("F", "P" or "") $P6: Exempt (1=exempt,0=non-exempt,-1=copay off) $P7: IEN from file 354.71 COMPONENT/ENTRY POINT: STATUS COMPONENT DESCRIPTION: This entry point will return the status of an entry in file 350. Call with $$STATUS^IBARX(ien from 350). Output will be: 0 = not a valid 350 ien 1 = Billed 2 = Cancelled 3 = Updated COMPONENT/ENTRY POINT: CANIBAM COMPONENT DESCRIPTION: This entry point will allow to cancel a potential charge that has not been charged. VARIABLES: X(n) TYPE: Input VARIABLES DESCRIPTION: sub: First subscript. Any value, same value as returned in Y(n) $P1: IEN from file 354.71 $P2: Charge Removal Reason. Reason for the cancellation pointer to the IB Charge Removal Reasons file (350.3) VARIABLES: Y(n) TYPE: Output VARIABLES DESCRIPTION: $P1: 0 or any positive number for OK or -1 for not accepted $P2: If not accepted, error message COMPONENT/ENTRY POINT: UPIBAM COMPONENT DESCRIPTION: This entry point will cancel current potential charge and create updated potential charge entry. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: $P1: Service. Pointer to Service Section file (49) $P2: Patient. Pointer to the Patient File (2) (DFN) $P3: Action Type. Pointer to the IB Action Type file (350.1) $P4: User. Pointer to New Person file (200) (DUZ) VARIABLES: X(n) TYPE: Input VARIABLES DESCRIPTION: sub: First subscript. Any value, same value is returned in Y(n) $P1: Softlink. Link to prescription file for entry causing charges in the format of: file number:entry pointer;[node:sub-entry;node:sub-entry...] $P2: Units. The number of units to be charged $P3: IEN from file 354.71 to be updated $P4: Charge Removal Reason. Reason for the cancellation pointer to the IB Charge Removal Reasons file (350.3) VARIABLES: Y TYPE: Input VARIABLES DESCRIPTION: $P1: 1 if success, -1 if error $P2: If error, error message VARIABLES: Y(n) TYPE: Output VARIABLES DESCRIPTION: $P1: New IEN from file 354.71 if success, -1 if error $P2: If error, error message SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 126 IA #: 126 DATE CREATED: NOV 06, 1991 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBOLK NAME: DBIA126 ORIGINAL NUMBER: 126 ID: IBOLK STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: ENB COMPONENT DESCRIPTION: Supported for Accounts Receivable to print a brief profile of prescription entries that caused the AR transaction. Input Variable: X $P1: AR Transaction Number. The AR Transaction number, the pointer to file 433. Output Writes one line profile for each Integrated Billing Action that caused the AR Transaction (may be more than one) VARIABLES: X TYPE: Input COMPONENT/ENTRY POINT: ENF COMPONENT DESCRIPTION: Supported for Accounts Receivable to print a full inquiry of prescription entries that caused the AR Transaction. Input Variable: X $P1: AR Transaction Number. The AR Transaction number, the pointer to file 433. Output Writes a full inquiry for each Integrated Billing Action that caused the AR Transaction (may be more than one). This will include the information from the brief profile plus the data printed by routine PSOCPVW from the prescription file VARIABLES: X TYPE: Input SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 127 IA #: 127 DATE CREATED: NOV 06, 1991 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCASER NAME: DBIA127-A ORIGINAL NUMBER: 127 ID: PRCASER GENERAL DESCRIPTION: PRCASER This routine is used for setting up or establishing a new charge (bill) for a debtor. When calling this routine, a new charge (pharmacy Co-Pay, etc, should be added to the patients account. Input Variable: X $P1: Site. This is the site number the charge is being created by. For example: 503, 516, etc. This is the station number field from the Institution file (4). $P2: Service. This is the service that is creating the bill. This is the pointer to the Service/Section file (49). $P3: Category Number. This is the AR Category that the charge should fall under. This is the pter to the AR Category file (430.2). $P4: Debtor. This is the debtor that the charge should fall under. This is a variable pointer to the following files: Vendor, Person, Insurance, Institution. For Pharmacy Co-Pay the debtor should be the patient in the format of "36;DPT(" whe re 36 is the internal number of the patient in the patient file. $P5: Fiscal Year. Fiscal Year charge should be charged to. $P6: Amount. Must be zero or greater and less than 9999999.99. $P7: User. The person who created the charge. Pointer to the User file (3). $P8: Date charge generated. This is the internal VA FileMan date the charge was issued. Output Variable: Y (if no error is encountered) P1: Internal Bill Number. This is the internal file number from the Accounts Receivable file (430). $P2: Charge ID. This is the .01 field from the Accounts Receivable file (430) and will be 10 characters in length. $P3: Transaction Number. Since an "OPEN" bill may already exist and can be used, it may be necessary to add this charge to an already existing bill as a transaction, then this would be the pointer value to the AR Transaction file (433). Howev er, if a new bill is set up for the current charges then this piece equals zero. Variable: Y (if error is encountered) $P1: Error Indicator. -1 . $P2: Error Code. This is the error code from the IB Action Error file. $P3: Additional Text. If additional text is required to describe the error it is in the third piece. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: PRCASER VARIABLES: X TYPE: Input VARIABLES: Y TYPE: Output SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 128 IA #: 128 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: NOV 20, 1991 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA128-A ORIGINAL NUMBER: 128 ID: VA(200, GENERAL DESCRIPTION: New Bill and Edit Bill options have been modified to prompt the user "Edit Debtor Address" after he/she has entered/edited the bill. This prompt as well as the Edit AR Debtor Address option allow edits to the NEW PERSON and INSTITUTION file. The fields edited include: for NEW PERSON file ^VA(200, 1) .111 - Street Address 1 2) .112 - Street Address 2 3) .113 - Street Address 3 4) .114 - City 5) .115 - State 6) .116 - Zip Code 7) .131 - Phone The edits would also be transposed in the PERSON file (^DIC(16)). Please keep in mind that "all users" with access to the Billing menu will be able to edit the debtor address fields (option 2). STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 129 IA #: 129 DATE CREATED: NOV 21, 1991 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOEXDT NAME: DBIA129 ORIGINAL NUMBER: 129 ID: PSOEXDT GENERAL DESCRIPTION: Call to STAT^PSOEXDT: The routine expects the 0 node of the prescription in RX0, the 2 node of the prescription in RX2 and returns the printable form of the prescription status in ST. The call will be abandonded when Health Summary provides the clinical information. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: STAT SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 130 IA #: 130 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: DEC 04, 1991 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA130-A ORIGINAL NUMBER: 130 ID: DPT( GENERAL DESCRIPTION: Read only access to the following Files, Fields, & X-References: FILE : Patient (2) FIELDS : Receiving A&A Benefits (.36205) Eligibility Status Date (.3612) Agerncy/Allied Country (.309) Receiving Housebound Benefits (.36215) Rated Disabilities (.3721) *stipulation* *this is being requested by other packages and may be incorporated into VADPT at which time we will ask packages to use the utility STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: REMOTE ORDER/ENTRY SYSTEM NUMBER: 131 IA #: 131 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: DEC 04, 1991 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA131-A ORIGINAL NUMBER: 131 ID: DPT( GENERAL DESCRIPTION: 'Status of the clinic appointment' field in ^DPT('S' node will be used to determine appointment status. If the status of the appointment is active and not an inpatient visit, it will be counted as an outpatient visit for social work totals. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SOCIAL WORK ISC: Birmingham NUMBER: 132 IA #: 132 DATE CREATED: DEC 05, 1991 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA132-A ORIGINAL NUMBER: 132 GENERAL DESCRIPTION: DGPM MOVEMENT EVENT DRIVER For movements other than 'death': The Inpatient inits send out the protocol 'PSJ OR PAT ADT' which is 'hooked' to the MAS protocol 'DGPM MOVEMENT EVENTS'. 'PSJ OR PAT ADT' uses the PSJADT routines to take the appropriate actions. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 136 IA #: 136 DATE CREATED: JAN 27, 2004 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSLROE NAME: DBIA136 ORIGINAL NUMBER: 136 ID: GMTSLROE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 37802529 COMPONENT/ENTRY POINT: XTRCT COMPONENT DESCRIPTION: The input variables are: DFN = IFN of patient in Patient file. SEX = Sex of patient. GMTS1 = Inverse end date of search for lab orders. GMTS2 = Inverse start date of search for lab orders. MAX = Maximum number of lab orders to be extracted The data is returned in the following array: ^UTILITY("LRO",$J,IDT,SN_FN)=CDT^TST^SPC^URG^OS^MD^ODT^ACC^RDT^COL^CD where: IDT = Inverse collection date/time of order. SN = IFN in Specimen # (1) multiple of Lab Order Entry (69) file. FN = IFN in Test (6) multiple of Specimen# (1) multiple of (69) Lab Order Entry(69) file. CDT = Collection date/time of order. TST = Lab test ordered. This variable has format A;B where A is the internal pointer and B is external printable form. SPC = Specimen for lab order. This variable has format A;B where A is the internal pointer and B is external printable form. URG = Urgency of lab order. OS = Status of lab order. MD = Provider. This variable has format A;B where A is the internal pointer and B is the external printable form. ODT = Date/Time lab ordered. ACC = Accession number of lab order. RDT = Date/Time results for this lab order available. COL = Lab or ward collect. CD = IFN in Lab Order Entry (69) file. VARIABLES: DFN TYPE: Input VARIABLES: SEX TYPE: Input VARIABLES: GMTS1 TYPE: Input VARIABLES: GMTS2 TYPE: Input VARIABLES: MAX TYPE: Input VARIABLES: ~TMP("LRO",$J, TYPE: Output VARIABLES DESCRIPTION: IA 532 permits setting this global. It's an output from XTRCT. It may be killed before calling and after use after the call. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 141 IA #: 141 DATE CREATED: JAN 07, 1992 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCSDIC NAME: DBIA141 ORIGINAL NUMBER: 141 ID: PRCSDIC GENERAL DESCRIPTION: ^PRCSDIC - Routine to perform lookup into File 410 (Control Point Activity). Variables: DIC DIC(0) DIC("A") STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: PRCSDIC VARIABLES: DIC TYPE: Input VARIABLES: DIC(0) TYPE: Input VARIABLES: DIC('A') TYPE: Input SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City NUMBER: 142 IA #: 142 FILE NUMBER: 31 GLOBAL ROOT: DIC(31, DATE CREATED: JAN 23, 1992 CUSTODIAL PACKAGE: HINQ CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA142-A ORIGINAL NUMBER: 142 ID: DIC(31, GLOBAL REFERENCE: DIC(31,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES NUMBER: 143 IA #: 143 DATE CREATED: FEB 05, 1992 CUSTODIAL PACKAGE: VETERANS ADMINISTRATION CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA143 ORIGINAL NUMBER: 143 GENERAL DESCRIPTION: HINQ v4 inits will transfer data from field 14.9 in File 3 to field 14.9 in File 200. STATUS: Active DURATION: Next Version SUBSCRIBING PACKAGE: HINQ ISC: Albany NUMBER: 144 IA #: 144 FILE NUMBER: 19.1 GLOBAL ROOT: DIC(19.1, DATE CREATED: FEB 18, 1992 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA144 ORIGINAL NUMBER: 144 ID: DIC(19.1, GENERAL DESCRIPTION: A patch (pre-release of Inpatient Meds V4) containing new keys will add the new keys to File #19.1, field .01 name. Then based on the present version, it will preload key holders for the new keys into the 'Holder' multiple (19.12) For Inpatient Medications V4 only. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 145 IA #: 145 DATE CREATED: MAR 05, 1992 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: OR2 NAME: DBIA145-A ORIGINAL NUMBER: 145 ID: OR2 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: In rtn GMRPNA, the user's input is accepted, if in the form ^^XXX, X is set equal to the requested protocol, N ORVP and set ORVP to the current patient in the usual form ("#;DPT("), and D EN^OR2. All GMRP variables required to be intact upon return.are newed. SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 146 IA #: 146 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: MAR 11, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA146 ORIGINAL NUMBER: 146 ID: DPT( GENERAL DESCRIPTION: This request is for permission to access some information from the DPT global directly. The data needed is the 'Other Income' field which is not returned from VADPT. This data is used by social work service with other monetary benefits information as an income screen for newly admitted patients. The data is accessed from piece 9 of the .362 DPT node. When the MB entry point of VADPT is restructed and this information included, it's agreed a patch will be issued to replace the direct access a VADPT entry point call. DURATION: Till otherwise agreed, and VADPT contains "other income". STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SOCIAL WORK ISC: Birmingham NUMBER: 147 IA #: 147 DATE CREATED: MAR 11, 1992 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Washington USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA147-A ORIGINAL NUMBER: 147 GENERAL DESCRIPTION: 1. The REQUEST/CONSULTATION file, 123, has a variable pointer field called "Results" which points to the following fields. 691 Echo Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 691.1 Cardiac Catheterization Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 691.5 Electrocardiogram (EKG/ECG) Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 691.6 Holter Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 691.7 Exercise Tolerance Test Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 691.8 Electrophysiology (EP) Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 694 Hematology Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 698 Generator Implant 698V1 V Lead Implant 698.2 A Lead Implant 698.3 Pacemaker Surveillance 699 Endoscopy/Consult Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 700 Pulmonary Function Tests Field 1506 RELEASE CODE Field 1511 MARK FOR DELETION 701 Rheumatology STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 148 IA #: 148 DATE CREATED: MAR 12, 1992 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORU1 NAME: DBIA148 ORIGINAL NUMBER: 148 ID: ORU1 GENERAL DESCRIPTION: Health Summary calls PATIENT^ORU1 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: PATIENT SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES NUMBER: 150 IA #: 150 DATE CREATED: MAR 26, 1992 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSNNGR NAME: PSNNGR ORIGINAL NUMBER: 150 ID: PSNNGR GENERAL DESCRIPTION: The Adverse Reaction Tracking (ART) package can use the PSONGR utility from the Outpatient Pharmacy package. This utility will return all of the primary ingredients to an entry in the Drug (50) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18469944 COMPONENT/ENTRY POINT: PSONGR VARIABLES: PSODA TYPE: Both VARIABLES DESCRIPTION: Input/Output = Internal entry number in File 50. VARIABLES: PSOID TYPE: Output VARIABLES DESCRIPTION: VA generic name pointer_"A"_VA product name pointer VARIABLES: TMP("PSO",$J,IFN) TYPE: Output VARIABLES DESCRIPTION: ^TMP("PSO",$J,IFN)=PI where: IFN = internal entry number in file 50.416 of primary ingredient. PI = Primary ingredient name. SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING ISC: Hines NUMBER: 151 IA #: 151 DATE CREATED: MAR 26, 1992 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSNNGR NAME: PSNNGR ORIGINAL NUMBER: 151 ID: PSNNGR GENERAL DESCRIPTION: The Adverse Reaction Tracking (ART) package can use the PSNNGR utility from the National Drug File package. This utility will return all of the primary ingredients to an entry in the National Drug (50.6) file. The ART package will use the DISPDRG entry point, if it exists, otherwise ART will call the routine from the top (i.e., D ^PSNNGR). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18469936 COMPONENT/ENTRY POINT: PSNNGR VARIABLES: PSNDA TYPE: Both VARIABLES DESCRIPTION: Input/Output = Internal entry number in File 50.6. VARIABLES: PSNID TYPE: Output VARIABLES DESCRIPTION: VA generic name pointer_"A"_VA product name pointer VARIABLES: TMP("PSN",$J,IFN) TYPE: Output VARIABLES DESCRIPTION: ^TMP("PSN",$J,IFN)=PI where: IFN = internal entry number in File 50.416 of primary ingredient. PI = Primary ingredient name. COMPONENT/ENTRY POINT: DISPDRG VARIABLES: PSNDA TYPE: Input VARIABLES DESCRIPTION: Internal entry number to File 50.6. VARIABLES: PSNVPN TYPE: Input VARIABLES DESCRIPTION: Internal entry number of the VA PRODUCT NAMES (#7) multiple in File 50.6. VARIABLES: TMP("PSNDD",$J,K) TYPE: Output VARIABLES DESCRIPTION: ^TMP("PSNDD",$J,K)=DI where: K = internal entry number to the Drug Ingredients (#50.416) file DI = the NAME of the File 50.416 entry SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING ISC: Hines NUMBER: 153 IA #: 153 FILE NUMBER: 741 GLOBAL ROOT: QA(741, DATE CREATED: APR 20, 1992 CUSTODIAL PACKAGE: QUALITY ASSURANCE INTEGRATION CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA153-A ORIGINAL NUMBER: 153 ID: QA(741, GENERAL DESCRIPTION: Read access to find patients who have had a QA occurrence which was refered to peer review associated with a particular admission. File 741 QA OCCURRENCE SCREEN The B cross reference Field 1 DATE REVIEWER (MULTIPLE) Field .01 REVIEW LEVEL Field 11 STATUS STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: EXTERNAL PEER REVIEW ISC: Birmingham NUMBER: 154 IA #: 154 DATE CREATED: APR 27, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGYEPRP NAME: DBIA154 ORIGINAL NUMBER: 154 ID: DGYEPRP GENERAL DESCRIPTION: 1. CallS EN^DGYEPRP and AUTO^DGYEPRP entry points.The EN entry point is used by a option to print an external peer review report and AUTO entry point is used to by an option to autoque the report. There are no input variables to the entry points. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN COMPONENT/ENTRY POINT: AUTO SUBSCRIBING PACKAGE: EXTERNAL PEER REVIEW ISC: Birmingham NUMBER: 155 IA #: 155 FILE NUMBER: 60 GLOBAL ROOT: LAB(60, DATE CREATED: APR 29, 1992 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA155 ORIGINAL NUMBER: 155 ID: LAB(60, GENERAL DESCRIPTION: A large number of users have requested that Health Summary's Chemistry and Hematology component appear in a manner analogous to the interim report. Health Summary has modified the code to look at: 1.) The PRINT ORDER field in file 60, and use it or the record number divided by 1000000, to determine the print sequence. 2.) The PRINT CODE FIELD (#53) of file 60 to format lab results STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 156 IA #: 156 DATE CREATED: MAY 21, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA156 ORIGINAL NUMBER: 156 GENERAL DESCRIPTION: Clinical Warnings hooks from within MAS are needed to call PN at an appropriate time in the patient lookup process to display any warnings that may exist. That code has been developed, but not released yet by the MAS pkg. In order to beta test PN along with OE/RR and for internal Verification, two routines,DGSEC and DPTLK, have been modified in the GMRP namespace and released to the test sites/ISCs. In the post-init, DGSEC and DPTLK will be renamed in lowercase, and then the GMRP hooks installed. Documentation for the editing of the Post-Selection Action field of file #2 will also be provided. AMENDMENT TO DBIA #156 DATED 10/7/93: This agreement was originally written to allow Progress Notes to export the routines DGSEC and DPTLK to its Beta test sites and to its verifying ISC; the MAS developers had added the hooks required to call the Clinical Warnings portion of Progress Notes at the appropriate time in a patient look-up, but this code was not in the field yet. It has since been verified and released. Version 5.2 of MAS and Progress Notes no longer exports them. This agreement is updated to simply provide maintenance of those hooks in the Registration pkg until otherwise agreed; Progress Notes will maintain the entry point ENPAT^GMRPNCW called from ^DGSEC. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 157 IA #: 157 DATE CREATED: MAY 21, 1992 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA157 ORIGINAL NUMBER: 157 GENERAL DESCRIPTION: As a standing integration agreement, the Progress Notes pkg (GMRP) will support the entry point ENPAT^GMRPNCW for the use of MAS in the Patient Warnings application. A line was inserted after Q^DGSEC to invoke this entry point if the rtn GMRPNCW is present in the system. Lines DGSEC+2 and CHKDFN+2^DPTLK were also modified somewhat to accomodate this call, as well as the Post-Selection Action of the Patient file (#2). The function of ENPAT^GMRPNCW sets flag (GMRPEN) which turns on Patient Warnings (CWAD) which lists directly under the patient's name on a ^DIC lookup the most recent Crisis Notes, Clinical Warning note, Allergy information, and/or Directive note in the form "C: date time"; a secondary menu option exists to allow users to view the text of these notes at their convenience. No variables are to be returned to MAS, and the only variable required to be received is the patient DFN in Y. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 160 IA #: 160 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: JUN 08, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA160-A ORIGINAL NUMBER: 160 ID: DPT( GLOBAL REFERENCE: DPT(D0,.21) FIELD NUMBER: .211 FIELD NAME: K-NAME OF PRIMARY NOK LOCATION: .21;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The name of the primary next-of-kin for this applicant. FIELD NUMBER: .212 FIELD NAME: K-RELATIONSHIP TO PATIENT LOCATION: .21;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: If a primary next-of-kin is specified, the relationship of that person to the applicant. FIELD NUMBER: .218 FIELD NAME: K-ZIP CODE LOCATION: .21;8 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: If a primary next-of-kin is specified, the zip code in which his/her city lies. FIELD NUMBER: .219 FIELD NAME: K-PHONE NUMBER LOCATION: .21;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: If a primary next-of-kin is specified, that person's telephone number. FIELD NUMBER: .2125 FIELD NAME: K-ADDRESS SAME AS PATIENT'S? LOCATION: .21;10 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: 'Y' if the next-of-kin should be contacted at the same address and phone number as the applicant, otherwise 'N'. GLOBAL REFERENCE: DPT(D0,.211) FIELD NUMBER: .2191 FIELD NAME: K2-NAME OF SECONDARY NOK LOCATION: .211;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: If a primary next-of-kin is specified, the secondary next-of-kin name. FIELD NUMBER: .2192 FIELD NAME: K2-RELATIONSHIP TO PATIENT LOCATION: .211;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: If a secondary next-of-kin is specified, the relationship of that person to the applicant. FIELD NUMBER: .2198 FIELD NAME: K2-ZIP CODE LOCATION: .211;8 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: If a secondary NOK is specified, the zip code for the city in which that person resides. FIELD NUMBER: .2199 FIELD NAME: K2-PHONE NUMBER LOCATION: .211;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: If a secondary NOK is specified, e telephone number at which that person may be reached. FIELD NUMBER: .21925 FIELD NAME: K2-ADDRESS SAME AS PATIENT'S? LOCATION: .211;10 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: 'Y' if the secondary NOK should be contacted at the same address and phone number as the applicant, otherwise 'N'. GLOBAL REFERENCE: DPT(D0,.34) FIELD NUMBER: .341 FIELD NAME: D-NAME OF DESIGNEE LOCATION: .34;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The name of the person designated by the applicant to receive his/her personal effects. FIELD NUMBER: .342 FIELD NAME: D-RELATIONSHIP TO PATIENT LOCATION: .34;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: If a designee is specified, the relationship of that person to the applicant. FIELD NUMBER: .348 FIELD NAME: D-ZIP CODE LOCATION: .34;8 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: If a designee is specified, the zip code for the city in which s/he resides. FIELD NUMBER: .349 FIELD NAME: D-PHONE NUMBER LOCATION: .34;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: If a designee is specified, the telephone number at which that person may be reached. FIELD NUMBER: .3405 FIELD NAME: D-DESIGNEE SAME AS NOK? LOCATION: .34;10 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: If a primary NOK is defined, 'Y' if that person is also the designee appointed by the applicant, otherwise 'N' for no. GLOBAL REFERENCE: DPT(D0,.321) FIELD NUMBER: .32102 FIELD NAME: AGENT ORANGE EXPOS. INDICATED? LOCATION: .321;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: For this veteran applicant, 'Y' if s/he was exposed to the chemical agent orange, 'N' if not, or 'U' if unknown. FIELD NUMBER: .32103 FIELD NAME: RADIATION EXPOSURE INDICATED? LOCATION: .321;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: For this veteran applicant, 'Y' if s/he was exposed to ionizing radiation while in the military, 'N' if not exposed, or 'U' if unknown. GLOBAL REFERENCE: DPT(D0,.322) FIELD NUMBER: .32201 FIELD NAME: PERSIAN GULF SERVICE? LOCATION: .322;10 ACCESS: Read w/Fileman FIELD DESCRIPTION: If the patient served in the Persian Gulf during the war (anytime after August 2, 1990), 'Y'. If the patient did not serve in the Persian Gulf during this timeframe, 'N'. 'U" if this information could not be obtained from the patient. GENERAL DESCRIPTION: Pulling over the following MAS data: PATIENT (#2) file: ^DPT(D0,.21) (#.211) K-NAME OF PRIMARY NOK Direct Global Read (#.212) K-RELATIONSHIP TO PATIENT Direct Global Read (#.218) K-ZIP CODE Direct Global Read (#.219) K-PHONE NUMBER Direct Global Read (#.2125) K-ADDRESS SAME AS PATIENT'S? Direct Global Read ^DPT(D0,.211) (#.2191) K2-NAME OF SECONDARY NOK Direct Global Read (#.2192) K2-RELATIONSHIP TO PATIENT Direct Global Read (#.2198) K2-ZIP CODE Direct Global Read (#.2199) K2-PHONE NUMBER Direct Global Read (#.21925) K2-ADDRESS SAME AS PATIENT'S? Direct Global Read ^DPT(D0,.34) (#.341) D-NAME OF DESIGNEE Direct Global Read (#.342) D-RELATIONSHIP TO PATIENT Direct Global Read (#.348) D-ZIP CODE Direct Global Read (#.349) D-PHONE NUMBER Direct Global Read (#.3405) D-DESIGNEE SAME AS NOK? Direct Global Read ^DPT(D0,.321) (#.32102) AGENT ORANGE EXPOS. INDICATED? Read w/FileMan (#.32103) RADIATION EXPOSURE INDICATED? Read w/FileMan ^DPT(D0,.322) (#.32201) PERSIAN GULF SERVICE? Read w/FileMan STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27335179 SUBSCRIBING PACKAGE: ONCOLOGY ISC: Hines NUMBER: 161 IA #: 161 DATE CREATED: JUN 08, 1992 CUSTODIAL PACKAGE: MENTAL HEALTH CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA161 ORIGINAL NUMBER: 161 GENERAL DESCRIPTION: 1.) A conversion rtn will copy the data found in ^YSP(606) into ^GMR(121) in the proper format. If pointers to file #16 still exist, they will be re-pointed to file #200. If version 5 is present, the codes for signature will also be converted. NO data will be automatically deleted by this process!! 2.) Documentation for the archive, purge the deletion, thru Fileman, of Files #606 & #606.5 will be provided. Also documentation for replacing the YSPN* options with GMRPN* options wherever they occur, to assure continued user access to the data. All YSPN*, GMRPN*, and YSMOVP (move Crisis Note to PN) options will be disabled for the duration of the conversion; when finished, the GMRPN* and YSMOVP options will be re-enabled and the YSPN* options will remain disabled with a message referencing the GMRPN options. Documentation will also be provided for deletion, at the sites disgression, of the old Mental Health options that will no longer be needed. 3.) When the conversion is completed, two Mental Health rtns will be updated to allow uninterrupted user access to the data: YSPP8 will be updated to check ^GMR(121) for the date of the most recent note on a given patient, and YSMV1 will be updated to transfer moving Mental Health Crisis Notes and Messages to the ^GMR(121) global from the ^YSP(606) global. These rtns will be exported as GMRPYSP8 and GMRPYSMV respectively, and renamed in the YS namespace 4.) Pointer to file #627.5, DSM-III-R Code.in field #30, DXLS, to ensure compatibility of this field in file 606. 5.) An optional tool to be run before the conversion, is a utility that will allow a site to edit the titles in the MH file (#606) before running the conversion. It has two entry points, one to generate a FileMan listing of all currently used MH titles and the other to edit the titles not desired in the new file. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 162 IA #: 162 FILE NUMBER: 63 GLOBAL ROOT: LR( DATE CREATED: JUN 08, 1992 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA162 ORIGINAL NUMBER: 162 ID: LR( GENERAL DESCRIPTION: Accessing the ^LR global as follows: 1) Searching the ^LR - cross references: "ASP","ACY","AEM","AAU" 2) Accessing the Topography and Morphology multiples: ^LR(D0,"SP",D1,0) - (0;1) "SP",D1,2,D2,0)) - (0;1) "SP",D1,2,D2,2,D3,0) - (0;1) 3) The same nodes for ^LR(D0,"CY") AND ^LR(D0,"EM") 4) Also the Autopsy nodes: ^LR(D0,"AU") - ("AU";1) "AU",D1,0) - (0;1) "AU",D1,2,D2,0) - (0;1) Accessing malignancies, AND the date of the test. This information is temporarily stored in the Oncology Patient file. The date of the test possibly being the date of diagnosis. In addition I should note that if the Casefinding Lab Report is printed all these nodes are accessed for the report data for each patient that has been previously "found" in a search. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ONCOLOGY ISC: Washington/Silver Spring NUMBER: 163 IA #: 163 FILE NUMBER: 78.3 GLOBAL ROOT: RA(78.3, DATE CREATED: JUN 08, 1992 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA163-A ORIGINAL NUMBER: 163 ID: RA(78.3, GENERAL DESCRIPTION: For Automatic Casefinding Radiology: Oncology looking at: ^RA(78.3 for a defined diagnostic code containing the word Malignancy... Check the ^RADPT("AR") cross-reference for date. Look at; ^RADPT(D0,"DT",D1,"P",D2,0) NODES for procedures which have the diagnostic code found above in ^RA(78.3 - we capture those patients and the date of the "suspicious procedures" STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ONCOLOGY ISC: Washington/Silver Spring NUMBER: 164 IA #: 164 DATE CREATED: JUN 04, 1992 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTS NAME: DBIA164 ORIGINAL NUMBER: 164 ID: GMTS GENERAL DESCRIPTION: In order to facilitate displaying Allergy alerts and data, a call is made to Health Summary to use components there for all the alerts -- Allergies, Crisis notes, Clinical Warning notes, and Advance Directive notes. In rtn GMRPNCW, GMTSPRM is set to the appropriate abbreviation, i.e. CN=Crisis Notes, CW=Clinical Warnings and Advance Directives, and ADR=Allergies; GMTSTITL is set to an appropriate heading for the HS report, depending on the value of GMTSPRM. A call is then made to D ENCWA^GMTS to print the report of alerts selected to view by the user. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: ENCWA VARIABLES: GMTSPRM TYPE: Input SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 165 IA #: 165 DATE CREATED: JUN 15, 1992 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: OR2 NAME: DBIA165-A ORIGINAL NUMBER: 165 ID: OR2 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: Consult/Request Tracking review screens use a "Select Action: " prompt at the bottom of each screen, similiar to OE/RR. Once a protocol item is selected at the "Select Action: " prompt, the response is analyzed by the GMRCUP routine to see if the response is prefixed with "^^" for navigation to protocols outside of the immediate protocol menu being provided. If "^^" was prefixed to a protocol name the GMRCUP1 routine will setup the following variables, ORVP and X=PROTOCOL TEXT and call EN^OR2. This entry point envokes the protocol jumped to. Upon completion of the protocol, the routine control is returned to the C/RT package. VARIABLES: ORVP TYPE: Input VARIABLES: X TYPE: Input SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 166 IA #: 166 DATE CREATED: JUN 10, 1992 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA166 ORIGINAL NUMBER: 166 GENERAL DESCRIPTION: Four components of the Health Summary package use data from the Progress Notes package -- Progress Notes, Brief Progress Notes, Crisis Notes and Clinical Warnings display components. There are structural changes to the Progress Notes global in the new version, they are reflected in changes to three Health Summary routines that access this data. Request permission to send these routines out with the tape containing the new global structure and routines for Progress Notes; they will be saved in the GMRP namespace, and in the post-init routine, using the code provided in the Kernel %ZOSF nodes, they will be saved at the site under the given Health Summary names. The routines are GMTSPN, GMTSPNE, GMTSCW. This agreement is for current release only. This release only. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 167 IA #: 167 FILE NUMBER: 19 GLOBAL ROOT: DIC(19, DATE CREATED: JUN 15, 1992 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA167 ORIGINAL NUMBER: 167 ID: DIC(19, GENERAL DESCRIPTION: 1. Agreement to point to the Option File from the Request Services File (123.5). This will be used to establish security for service updating based on the option entered. Two special options are distributed with the Consult/Request Package which are specific to the Packages users for Pharmacy and Medicine. The GMRC initialization process sets up the option/service relationships for IRM in the Request Services File (123.5). 2. Agreement to use the XQY and XQY0 variables to determine which option the user used to get to the "Select Action: " logic for a given service. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 170 IA #: 170 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: JUN 17, 1992 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA170 ORIGINAL NUMBER: 170 ID: VA(200, GENERAL DESCRIPTION: Agreement is made to allow the AMIE package to make references to ^VA(200,DA(1),2,DA) directly. Generally lookup into ^VA(200 is blessed. Any changes to security/access information is NOT blessed. Such items of concern are: NAME, FILEMANAGER ACCESS, ACCESS CODES, VERIFY CODES, PRIMARY & SECONDARY MENUS, SECURITY KEYS, and FILE ACCESS list. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 171 IA #: 171 GLOBAL ROOT: DD( DATE CREATED: JUN 17, 1992 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA171 ORIGINAL NUMBER: 171 ID: DD( GLOBAL REFERENCE: DD(133.028,.01,0) GLOBAL REFERENCE: DD(139.21,.01,0) GENERAL DESCRIPTION: 1.) The SURGERY SITE PARAMETERS file contains a multiple titled REQUIRED FIELDS FOR SCHEDULING which containg fields that must be entered prior to allowing a surgical case to be scheduled. This field points to the global ^DD(130, allowing selection of filed names. ^DD(133.028,.01,0) = REQUIRED FIELDS FOR SCHEDULING^P130'^DD(130,^0;1^Q 2.) The same concept is used in the RISK MODEL LAB TEST file excep we're pointing to the DDs for one of the lab files or sub-files. ^DD(139.21,.01,0) = LABORATORY DATA NAME^M*P63'X^DD(63.04,^0;1^S DIC("S")="I Y>1" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 172 IA #: 172 DATE CREATED: JUN 17, 1992 CUSTODIAL PACKAGE: DSS EXTRACTS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ECXUD1 NAME: DBIA172-A ORIGINAL NUMBER: 172 ID: ECXUD1 GENERAL DESCRIPTION: DSS Extracts needs data from the Inpatient Medications package which cannot be extracted from any file. The Inpatient Medications team has agreed to modify two routines (PSGPLF and PSGAMSA) to call, after executing %ZOSF("TEST"), routine ECXUD1 to place data into a DSS file for future extract by DSS. The requested data is placed in the ECUD variable, which the ECXUD1 routine uses to store the data in the UNIT DOSE EXTACTS file (#720.904). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34591057 COMPONENT/ENTRY POINT: ECXUD1 VARIABLES: ECUD TYPE: Input VARIABLES DESCRIPTION: Variable ECUD contains the following pieces of data: 1. DFN of the patient for whom the drug was dispensed. 2. Date drug was dispensed in FileMan format (no time). 3. The IEN of the drug dispensed. 4. Units dispensed. For example: number of tablets. 5. The IEN of the ward location for the patient. Pointer to file #42. 6. The IEN of the provider who placed the order. 7. Cost of the units dispensed. 8. Order Start Date/Time in FileMan format. 9. The IEN of the order number. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS NUMBER: 173 IA #: 173 DATE CREATED: JUN 17, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA173 ORIGINAL NUMBER: 173 GENERAL DESCRIPTION: The MAS package will carry along the HINQ mini inits when it installs MAS v5.2. The HINQ mini inits (DVBY*) are a collection of routines that will install a new edit template field into the HINQ edit template (DVBHINQ UPDATE) which is part of the patient file. The entry point to call is ^DVBYCHK . This routine will check to ensure the proper version of the HINQ package is installed (V4.0). If at least 4.0 is not installed the init will not be run. Installation notes will be provided to the MAS developers for inclusion into the MAS release notes. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HINQ ISC: Albany NUMBER: 174 IA #: 174 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: JUN 18, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA174 ORIGINAL NUMBER: 174 ID: DPT( GLOBAL REFERENCE: DPT(DFN,.372) FIELD NUMBER: .01 FIELD NAME: RATED DISABILITIES (VA) ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: DISABILITY % ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: SERVICE CONNECTED ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Direct global access to patient file, Field .3721--Rated Disabilities (VA). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33089108 SUBSCRIBING PACKAGE: QUASAR ISC: Birmingham SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: REMOTE ORDER/ENTRY SYSTEM SUBSCRIBING PACKAGE: CLINICAL PROCEDURES NUMBER: 175 IA #: 175 DATE CREATED: JUN 18, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA175 ORIGINAL NUMBER: 175 GENERAL DESCRIPTION: PDX routines will be exported with MAS 5.2. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 176 IA #: 176 GLOBAL ROOT: DG( DATE CREATED: JUN 18, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA176 ORIGINAL NUMBER: 176 ID: DG( GENERAL DESCRIPTION: PDX uses direct access to ^DG global. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 177 IA #: 177 DATE CREATED: JUN 18, 1992 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA177 ORIGINAL NUMBER: 177 GENERAL DESCRIPTION: Progress Notes has permission to place the XUSESIG option on one of its menus during export. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 178 IA #: 178 DATE CREATED: JUN 18, 1992 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA178 ORIGINAL NUMBER: 178 GENERAL DESCRIPTION: OR/RR has permission to place the XUSESIG option on one of its menus during export. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 180 IA #: 180 DATE CREATED: JUN 18, 1992 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIU NAME: DBIA180 ORIGINAL NUMBER: 180 ID: DIU GENERAL DESCRIPTION: Surgery uses the entry point DI^DIU as follows: Prior to entry, the following input variables must be supplied: DI = file number N = 0 X = null (or you can set it to any combination of "WC.01" where W" will screen out word-processing fields, "C" will screen out computed fields, and ".01" will screen out the .01 field at both top and subfile levels.) At the end, all variables set by Surgery will be killed, and in addition, %,C,DA,DDH,DI,DIC,DISYS,I,J and Y will be killed. After calling this routine, varible N will tell how many levels down you went into subfiles (0 is top level, 1 is 1 level down, etc.). The I array will tell the subscript for each multiple level at which the data is located (ex., I(1) for first level down, I(2) for second). The J array will tell the subfile number at each multiple level (ex.,J(1) for first level down, J(2) for second). STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: DI VARIABLES: DI TYPE: Input VARIABLES: N TYPE: Input VARIABLES: X TYPE: Input VARIABLES: I TYPE: Output VARIABLES: J TYPE: Output SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 181 IA #: 181 DATE CREATED: JUN 19, 1992 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORUHDR NAME: DBIA181-A ORIGINAL NUMBER: 181 ID: ORUHDR STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EXT COMPONENT DESCRIPTION: Displays a standard header for detailed order displays. If calling this from within OE/RR, it is not necessary to kill the returned variables. OE/RR will kill them. REQUIRED VARIABLES: ORIFN RETURNED VARIABLES: ORAGE,ORIO ORANSI,ORDOB, ORFT,ORHI,ORIFN, ORNP,ORL,ORPD, ORPNM,ORPV,ORSEQ, ORSEX,ORSSN,ORTIT, ORTS,ORVP,ORWARD VARIABLES: ORIFN TYPE: Both VARIABLES: ORAGE TYPE: Output VARIABLES: ORIO TYPE: Output VARIABLES: ORANSI TYPE: Output VARIABLES: ORDOB TYPE: Output VARIABLES: ORFT TYPE: Output VARIABLES: ORHI TYPE: Output VARIABLES: ORNP TYPE: Output VARIABLES: ORL TYPE: Output VARIABLES: ORPD TYPE: Output VARIABLES: ORPNM TYPE: Output VARIABLES: ORPV TYPE: Output VARIABLES: ORSEQ TYPE: Output VARIABLES: ORSEX TYPE: Output VARIABLES: ORSSN TYPE: Output VARIABLES: ORTIT TYPE: Output VARIABLES: ORTS TYPE: Output VARIABLES: ORVP TYPE: Output VARIABLES: ORWARD TYPE: Output COMPONENT/ENTRY POINT: PGBRK COMPONENT DESCRIPTION: Displays "Press return to continue or "^" to escape" at page breaks. REQUIRED VARIABLES none RETURNED VARIABLES: DIROUT,OREND VARIABLES: DIROUT TYPE: Output VARIABLES: OREND TYPE: Output SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 182 IA #: 182 DATE CREATED: JUL 14, 1992 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIP1 NAME: DBIA182 ORIGINAL NUMBER: 182 ID: DIP1 GENERAL DESCRIPTION: DGPTFMO1 AT LINE 17 ISSUES A CALL TO N^DIP1. This is currently being renegotiated to use a supported reference that will be available in version 21 of Fileman. V21 will still have the entry point N^DIP1, but it is recommended that the new supported reference be used when available. STATUS: Active DURATION: Next Version MAIL MESSAGE: 11021087 GOOD ONLY FOR VERSION: 5.3 COMPONENT/ENTRY POINT: N SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 185 IA #: 185 FILE NUMBER: 131.7 GLOBAL ROOT: SRS( DATE CREATED: JUL 16, 1992 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA185-A ORIGINAL NUMBER: 185 ID: SRS( GLOBAL REFERENCE: SRS('B',+LOC,ORLOC) GENERAL DESCRIPTION: An E3R has been issued, asking to modify the Health Summary Print by location option to allow selection of an Operating Room, and to queue the selected Health Summary Type to print for all patients scheduled for surgery in that OR on a user-specified date. To that end, the Print by Location driver has been modified to look at the "B" cross reference of the Operating Room File (i.e., ^SRS("B",+LOC,ORLOC)) to get the record number of the selected OR, and then traverse the "AOR" cross reference of the Surgery File (i.e., ^SRF("AOR",+ORLOC,SDT,SRN) to get the record number of each surgery. It then visits the zero-node of each Surgery record to get the patient, whom it adds to the list of patients for Health Summaries to be printed. Health Summary makes direct references to the above cited globals and cross references. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 186 IA #: 186 DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGINPW NAME: DBIA186-A ORIGINAL NUMBER: 186 ID: DGINPW GENERAL DESCRIPTION: Means Test Billing Conversion. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 187 IA #: 187 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA187-A ORIGINAL NUMBER: 187 ID: DPT( GENERAL DESCRIPTION: Integrated Billing uses the following functions, routines, files and fields: 2 DPT PATIENT FILE .01 NAME-- Used for sorting and printed on a patients Check-off Sheet and on the 'Unbilled BASC codes for insured Patients' report, returned by function PT, function created to replace DEM^VADPT call .363 PRIMARY LONG ID-- Returned by function PT, function created to replace DEM^VADPT call .364 PRIMARY SHORT ID-- Returned by function PT, function created to replace DEM^VADPT call 2.98 (1900) APPOINTMENT SUBFILE 3-- STATUS-- Used to determine if Check-off sheet should be printed 9.5-- APPOINTMENT TYPE Printed on a patients Check-off Sheet .3721(2.04) RATED DISABILITIES SUBFILE printed on a patients Check-off Sheet if SERVICE CONNECTED is true .01 RATED DISABILITIES 2 DISABILITY % 3 SERVICE CONNECTED ^DPT(patient file)-- "ADIS"-- ^IBOVOP1: xref on login date/time - "DIS"-- ^IBOVOP1: disposition node - 0;2 STATUS - 0;3 TYPE OF BENEFIT APPLIED FOR - 0;7 DISPOSITION - "S"-- ^IBECEA, ^IBOVOP, ^IBOVOP1 check appointments for a C&P - "ACS"-- ^IBOVOP: means test status - .311 node-- ^IBEHCFA: insured's info PATIENT, #2-- "CN" cross-reference Billing of all current Category C clients. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING DETAILS: added 5/14/09 DATE/TIME EDITED: MAY 14, 2009@14:03 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: REDINGTON,PATRICK WITH CONCURRENCE OF: MULLER,RICHARD NUMBER: 190 IA #: 190 DATE CREATED: AUG 06, 1992 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRAPEM0 NAME: DBIA190-A ORIGINAL NUMBER: 190 ID: GMRAPEM0 GENERAL DESCRIPTION: The Medicine package has the permission of the Allergy Tracking System developers to use the following items from ATS V2.2. EN2^GMRAPEM0: This entry point is to be used by the Medicine package to enter data into the Allergy Tracking System. The input variable is DFN (pointer to file 2). STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN2 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 193 IA #: 193 DATE CREATED: SEP 15, 1992 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCANRU NAME: DBIA193 ORIGINAL NUMBER: 193 ID: PRCANRU GENERAL DESCRIPTION: To activate the data extraction process of the Accounts Receivable package, the MCCR National Database - Field Component, using indirection, will issue the following call using parameter passing: D EN1^PRCANRU(PRQDAT,PRQSTR,PRQIDN,.PRQERR) Where: PRQDAT is a pieced variable, with ^ as the piece delimiter, as follows: site number ^ batch number ^ from date ^ to date PRQSTR is a variable which defines a global root where the package extraction routine will place the data according to the format below. PRQIDN is a unique identifier number PRQERR is an error flag which will be set to "1 DATA COLLECTION ABORTED". The extract routine must reset this variable so it evaluates to zero as an indicator that the extraction process ran to completion. Data is stored using the global root as follows: PRQSTR_","_criteria#1_"-"_criteria#2)=#count^$amount for example: ^TMP("PRQ","2020D611","1-1")=50^25000 The actual line of code in the MCCR National Database - Field Component will appear as: D @(extractor entry point) D DRIVER^PRQSD. Finally, the code for invoking the routine will exist as an entry in the MCCR Collections Routine file. The AR package may directly enter an extractor routine into the MCCR Collection Routines file (file #466), as part of its installation procedure. The entry must include routine name and status, and proper cross-references for these two fields. The routine name should include a "#" character to indicate the proper position of the "^". Status may be either active or inactive. Inactive extractors will not be invoked by the MCCR National Database software. The following extractor will be entered during installation of the MCCR National Database - Field Component: EN1#PRCANRU(PRQDAT,PRQSTR,PRQIDN,.PRQERR). This entry may be modified, or other entries added, in subsequent AR releases with prior notification to, and concurrence of, the San Francisco ISC. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN1 SUBSCRIBING PACKAGE: MCCR NATIONAL DATABASE ISC: Oakland NUMBER: 194 IA #: 194 FILE NUMBER: 63 GLOBAL ROOT: LR( DATE CREATED: SEP 15, 1992 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA194 ORIGINAL NUMBER: 194 ID: LR( GENERAL DESCRIPTION: The Risk Assessment module of the Surgery package contains options that locate and store lab test values for certain lab tests, which are later transmitted to the Surgery Risk Assessment database at Hines for eventual analysis. These options allow for the automatic input of pre-operative and post-operative lab test values into the Surgery file. Each lab test and its associated specimen is defined in one of the Surgery package files along with the site-specific 'Data Name(s)' associated with each test. The information in this file is used to locate the latest pre-operative test value within 30 days of the operation and the highest and/or the lowest test value within 30 days after the operation. The following files within the LABORATORY package are pointed to by Surgery: - File 61 (TOPOGRAPHY FIELD) - File 63 (LAB DATA) Sub-File 63.04 (CHEM, HEM, TOX, RIA, SER, etc.) Surgery reads data in the following fields within file 63 (LAB DATA): - 63.04,.01 - DATE/TIME SPECIMEN TAKEN Global Reference: ^LR(LRDFN,"CH",INVERSE DATE/TIME,0), piece #1 The INVERSE DATE/TIME subscript is determined by looping through ^LR(LRDFN,"CH",INVERSE DATE/TIME) for the inverse date/time range based on the date/time of operation and the date/time of operation +/- 30 days (minus 30 days for pre-operative data or plus 30 days for post-operative data). - 63.04,.03 - DATE REPORT COMPLETED Global Reference: ^LR(LRDFN,"CH",INVERSE DATE/TIME,0), piece #3 - 63.04,.05 - SPECIMEN TYPE Global Reference: ^LR(LRDFN,"CH",INVERSE DATE/TIME,0), piece #5 - 63.04,* All LAB TEST fields associated with Risk Assessment Global Reference: ^LR(LRDFN,"CH",INVERSE DATE/TIME,DATA NAME), piece #1 The DATA NAME subscript is determined by looping through ^LR(LRDFN,"CH",INVERSE DATE/TIME,DATA NAME) checking for a match with site specific Risk Assessment lab test data names stored in the Surgery package. Because the Surgery package will be making direct reference to data in the Laboratory namespace, we request a Database Integration Agreement with the developers of the Laboratory package permitting Surgery to reference the above mentioned Laboratory data structures. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 196 IA #: 196 FILE NUMBER: 62.5 GLOBAL ROOT: LAB(62.4, DATE CREATED: SEP 24, 1992 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA196-A ORIGINAL NUMBER: 196 ID: LAB(62.4, GENERAL DESCRIPTION: The Medicine Package has permission from the Lab developers for read and write access to the ^LA node for the purpose of LSI autoinstrument interfacing. The Medicine Package has permission from the Lab developers for creating entries in the Autoinstrument file for the purpose of LSI autoinstrument interfacing. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL PROCEDURES NUMBER: 197 IA #: 197 FILE NUMBER: 61.6 GLOBAL ROOT: LAB(61.6, DATE CREATED: OCT 07, 1992 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA197 ORIGINAL NUMBER: 197 ID: LAB(61.6, GENERAL DESCRIPTION: Oncology is granted LAYGO access to the SNOMED Occupational File in Laboratory. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ONCOLOGY ISC: Washington/Silver Spring NUMBER: 198 IA #: 198 FILE NUMBER: 410 GLOBAL ROOT: PRCS(410, DATE CREATED: NOV 24, 1992 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA198 ORIGINAL NUMBER: 198 ID: PRCS(410, GENERAL DESCRIPTION: In an effort to provide a receiving mechanism for Controlled Substances module, several look-ups and pointers are necessary for an interim interface. For Purchase Order receipts, a lookup to PROCUREMENT & ACCOUNTING TRANSACTIONS file 442, screened by cost center [822400] is used. For Issue Receipts, a lookup occurs, screened by cost center [822400], in CONTROL POINT ACTIVITY file 410. A connection between the DRUG file 50 and ITEM MASTER file 441 is crucial for posting receipt information. This may be a one-to-many relationship and therefore involves the creation of a multiple IFCAP ITEM NUMBER field (#50.0441) in the DRUG file 50 pointing to the ITEM MASTER file 441. This field includes an input transform similar to that found in the NDC field in the ITEM MASTER file 441 preventing the linking of the same item to more than one drug. It also includes an 'AB' whole file cross-reference. Pointer to CONTROL POINT ACTIVITY file 410 Pointer to ITEM MASTER file 441 Pointer to PROCUREMENT & ACCOUNTING TRANSACTIONS file 442 References information (Read only) from CONTROL POINT ACTIVITY file 410 .01 TRANSACTION NUMBER 10 ITEM .01 LINE ITEM NUMBER 1 DESCRIPTION 2 QUANTITY 3 UNIT OF PURCHASE 5 REPETITIVE (PR CARD) NO. 6 STOCK NUMBER 7 EST. ITEM (UNIT) COST 13 QUANTITY POSTED (WHSE) 14 QUANTITY REC'D (PRIMARY) IFCAP files are used solely to gather and display receipt information and so the Controlled Substances files 58.8 and 58.81 can accumulate a receipt history. DURATION: Till otherwise agreed, when the GIP & Drug Accountability interf ace is available STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham NUMBER: 200 IA #: 200 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: DEC 14, 1992 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA200 ORIGINAL NUMBER: 200 ID: VA(200, GENERAL DESCRIPTION: The ADP USER file 497.2 may have its top level .01 field DINUMed to the NEW PERSON file 200. The ADP USER file is limited to distribution to the ISCs. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ADP PLANNING (PLANMAN) ISC: Birmingham NUMBER: 201 IA #: 201 DATE CREATED: DEC 15, 1992 CUSTODIAL PACKAGE: EXTERNAL PEER REVIEW CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: QIEQA NAME: DBIA201 ORIGINAL NUMBER: 201 ID: QIEQA GENERAL DESCRIPTION: Routine DGYEPRN makes a call to $$QA^QIEQA($P(DGPT0,"^"),$P(DPT0,"^",2).$P(DGPT70,"^")). Resolving the $P functions it equates to $$QA^QIEQA(DFN,ADM,DIS). DFN=patient, ADM=admit date, DIS=discharge date. The function checks to see if the patient was referred to peer review in the QA application. (See DBIA # 153 for agreement between EPRP and QA for global access.) STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$QA SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 202 IA #: 202 DATE CREATED: JAN 21, 1993 CUSTODIAL PACKAGE: RECORD TRACKING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RTUTL3 NAME: DBIA202 ORIGINAL NUMBER: 202 ID: RTUTL3 GENERAL DESCRIPTION: IRT has permission to call in the following RT routines: MED^RTUTL3 calls LATEST^RTUTL3 where the doc is LATEST^RTUTL3 input variable is RTE entity DFN_";DPT(" output RTDATA=volume^borrower^phone/room#^date/time charged RT = internal record number. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: MED VARIABLES: RT TYPE: Output VARIABLES: RTE TYPE: Input VARIABLES: RTDATA TYPE: Output COMPONENT/ENTRY POINT: LATEST VARIABLES: RTE TYPE: Input VARIABLES: RTDATA TYPE: Output VARIABLES: RT TYPE: Output SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING ISC: Albany SUBSCRIBING PACKAGE: EXTERNAL PEER REVIEW ISC: Birmingham NUMBER: 205 IA #: 205 FILE NUMBER: 723 GLOBAL ROOT: ECC(723, DATE CREATED: JAN 29, 1993 CUSTODIAL PACKAGE: EVENT CAPTURE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA205 ORIGINAL NUMBER: 205 ID: ECC(723, GLOBAL REFERENCE: ECC(723, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Version 3.0 of the Surgery software had permission to export the MEDICAL SPECIALTY file (#723) with data in the inits. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 206 IA #: 206 DATE CREATED: JAN 29, 1993 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSIVACT NAME: DBIA206 ORIGINAL NUMBER: 206 ID: PSIVACT GENERAL DESCRIPTION: The Surgery package has permission to invoke the entry point DCOR^PSIVACT, which is exported as part of the Inpatient Meds package. This entry point allows surgery to discontinue all of a specific patient's IV orders, and is documented in the version 4.0 Inpatient Meds will continue to support this entry point until agreed. When DCOR^PSIVACT is invoked DFN, must be set to the IEN for the patient whose orders are to be discontinued. DCOR^PSIVACT uses the following variables: ON1, PSIVRES, PSIVREA, PSIVDFN,PSIVON, PSIVLN. These variables are killed upon exit from the utility. DFN is unchanged. In setting up the call to DCOR^PSIVACT, Surgery sets DFN and PSIVRES. The other variables mentioned are set within PSIVACT. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: DCOR VARIABLES: DFN TYPE: Input VARIABLES: ON1 TYPE: Used VARIABLES: PSIVRES TYPE: Input VARIABLES: PSIVREA TYPE: Used VARIABLES: PSIVDFN TYPE: Used VARIABLES: PSIVON TYPE: Used VARIABLES: PSIVLN TYPE: Used SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 207 IA #: 207 DATE CREATED: FEB 03, 1993 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LRRP2 NAME: DBIA207 ORIGINAL NUMBER: 207 ID: LRRP2 GENERAL DESCRIPTION: Surgery is granted a database integration agreement with Laboratory allowing Surgery to make a call to LRRP2 by executing %ZOSF("TEST"), then calling LRRP2. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 208 IA #: 208 DATE CREATED: FEB 18, 1993 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSSGIU NAME: PSSGIU ORIGINAL NUMBER: 208 ID: PSSGIU GENERAL DESCRIPTION: The Surgery package is given formal permission from Inpatient Medications to make calls to the routine PSGIU to mark and unmark entries in the DRUG file (#50) for anesthesia use. The entry points ENS^PSGIU and END^PSGIU are the same entry points Surgery Version 2.12 has been using and we want to continue using them in Version 3.0. Both entry points are documented in the Inpatient Medications Technical Manual for Version 4.0. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: ENS COMPONENT DESCRIPTION: Entry point to mark drug for anesthesia use Surgery package sets variables PSIUDA and PSIUX prior to calling ENS^PSIGU. VARIABLES: PSIUDA TYPE: Input VARIABLES: PSIUX TYPE: Input COMPONENT/ENTRY POINT: END COMPONENT DESCRIPTION: Entry point to unmark drug for anesthesia use. Surgery package sets variables PSIUDA and PSIUX prior to calling END^PGIGU. VARIABLES: PSIUDA TYPE: Input VARIABLES: PSIUX TYPE: Input SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 209 IA #: 209 FILE NUMBER: 50.6 GLOBAL ROOT: PSNDF( DATE CREATED: FEB 18, 1993 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA209 ORIGINAL NUMBER: 209 ID: PSNDF( GLOBAL REFERENCE: PSNDF(D0,0) FIELD NUMBER: .01 FIELD NAME: VA GENERIC NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the VA Generic name of drug 3-64 characters in length. GLOBAL DESCRIPTION: This file contains a list of available drug products. It includes specific information for each product, including trade name, NDC number, manufacturer , VA Drug Class code, dosage form, route of administration, strength, units, ingredients, ingredient strength and units, package code, package size, package type, VA Product Name, and VA Generic Name. The NDF software attempts to match products from this file with products in the local DRUG file. GLOBAL REFERENCE: PSNDF(D0,2,D1,3,D2,4,D3,5,D4,6,D5,7,D6,0) FIELD NUMBER: .01 FIELD NAME: NDC LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the NDC (National Drug Code) of this product. FIELD NUMBER: 3 FIELD NAME: VA PRODUCT NAME POINTER LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the entry number in the VA Product Name multiple of this product. GLOBAL DESCRIPTION: This is the NDC (National Drug Code) multiple. GLOBAL REFERENCE: PSNDF(D0,5,D1,0) FIELD NUMBER: .01 FIELD NAME: VA PRODUCT NAMES LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the VA Product Name. GLOBAL DESCRIPTION: This is the VA Product Name multiple. GENERAL DESCRIPTION: Drug Accountability is granted this agreement to connect the DRUG (#50) file to the ITEM MASTER (#441) file to make use of a look-up to the NATIONAL DRUG (#50.6) file. If a selected DRUG file entry has a NATIONAL DRUG FILE ENTRY (#20), a beloved path is followed to the NDC (#1) multiple in the NATIONAL DRUG (#50.6) file. The user is allowed to check as many of these NDCs as they choose for a match in the ITEM MASTER (#441) file. GLOBAL MAP DATA DICTIONARY #50 -- DRUG FILE STORED IN ^PSDRUG( SITE: BIRMINGHAM ISC (#14) (VERSION 6) ------------------------------------------------------------------------- ^PSDRUG(D0,0)=(#.01) GENERIC NAME [1F] ^ ^PSDRUG(D0,441,0)=^50.0441P^^ (#441) IFCAP ITEM NUMBER ^PSDRUG(D0,441,D1,0)= (#.01) ITEM NUMBER [1P] ^ ^PSDRUG(D0,ND)= (#20) NATIONAL DRUG FILE ENTRY [1P] ^ GLOBAL MAP DATA DICTIONARY #50.6 -- NATIONAL DRUG FILE 02/11/93 STORED IN ^PSNDF( (2269 ENTRIES) SITE: BIRMINGHAM ISC (#14) ------------------------------------------------------------------------- ^PSNDF(D0,0)= (#.01) VA GENERIC NAME [1F] ^ ^PSNDF(D0,2,D1,3,D2,4,D3,5,D4,6,D5,7,0)=^50.67^^ (#1) NDC ^PSNDF(D0,2,D1,3,D2,4,D3,5,D4,6,D5,7,D6,0)= (#.01) NDC [1F] ^ Drug Accountability/Inventory Interface v3.0 interfaces with the prime vendor invoice data. It uses the 12-digit NDC to match the invoice's line items to drugs in the DRUG file (#50) if the NDC is not in the DRUG file. If the NDC is found in the "NDC" cross-reference, the VA PRODUCT NAME POINTER field (#3) is read to locate the VA PRODUCT NAMES field (#7). The DRUG file's "VAPN" cross-reference is traversed to determine if any drugs have the same VA product name. If so, the drugs are used as a suggested possible match to the line item. GLOBAL MAP DATA DICTIONARY #50.6 -- NATIONAL DRUG FILE -------------------------------------------------------------------------- CROSS REFERENCED BY: NDC(NDC) ^PSNDF(D0,2,D1,3,D2,4,D3,5,D4,6,D5,7,D6,0)= (#.01) NDC [1F] ^^^ (#3) VA ==>PRODUCT NAME POINTER [4N] ^ ^PSNDF(D0,5,0)=^50.68A^^ (#7) VA PRODUCT NAMES ^PSNDF(D0,5,D1,0)= (#.01) VA PRODUCT NAMES [1F] ^ STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24917100 SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham EDITOR: RUZBACKI,RON T NUMBER: 210 IA #: 210 FILE NUMBER: 66 GLOBAL ROOT: LAB(66, DATE CREATED: FEB 18, 1993 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA210 ORIGINAL NUMBER: 210 ID: LAB(66, GENERAL DESCRIPTION: The Surgery package is granted permission from the Laboratory package to read from the BLOOD PRODUCT file (#66) for purposes of storing the blood components requested for surgical cases. Surgery will point to the BLOOD PRODUCT file (#66), using a screen which looks at the CAN BE REQUESTED field (#.15) to allow selection of only those blood products that have been flagged for patient use. In summary, Surgery will READ only, the NAME field (#.01) and the CAN BE REQUESTED field (#.15) of the BLOOD PRODUCT file (#66). The BLOOD PRODUCT file is stored in ^LAB(66). The NAME is stored in $P(^LAB(66,DA,0),"^") where DA is the internal entry number in the file for the blood product. The CAN BE REQUESTED information is stored in $P(^LAB(66,DA,0),"^",15). STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 211 IA #: 211 FILE NUMBER: 60 GLOBAL ROOT: LAB(60, DATE CREATED: FEB 18, 1993 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA211-A ORIGINAL NUMBER: 211 ID: LAB(60, GLOBAL REFERENCE: LAB(60,D0,0) FIELD NUMBER: 4 FIELD NAME: SUBSCRIPT LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5 FIELD NAME: LOCATION (DATA NAME) LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LAB(60,D0,10) FIELD NUMBER: 504 FIELD NAME: CIS TEST CODE LOCATION: 10;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Accessed to support CIS interface, e.g., EMTEK STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 212 IA #: 212 FILE NUMBER: 59 GLOBAL ROOT: PS(59, DATE CREATED: FEB 18, 1993 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA212 ORIGINAL NUMBER: 212 ID: PS(59, GLOBAL REFERENCE: PS(59, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33589377 SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham NUMBER: 213 IA #: 213 DATE CREATED: FEB 18, 1993 CUSTODIAL PACKAGE: AUTO REPLENISHMENT/WARD STOCK CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA213 ORIGINAL NUMBER: 213 GENERAL DESCRIPTION: Permission is granted for Controlled Substances to: Export AR/WS files 58.16 AOU INVENTORY TYPE 58.17 AOU ITEM LOCATION 58.2 AOU INVENTORY GROUP (partial file) .01 NAME 2 GROUP DESCRIPTION 3 NARCOTIC AREA OF USE (NAOU) .01 NARCOTIC AREA OF USE (NAOU) 1 INVENTORY TYPE .01 INVENTORY TYPE 2 SORT KEY "CS" X-REF ON NARCOTIC AREA OF USE (NAOU) Pointer to AOU INVENTORY TYPE file 58.16 Pointer to AOU ITEM LOCATION file 58.17 GLOBAL MAP DATA DICTIONARY #58.16 -- AOU INVENTORY TYPE FILE STORED IN ^PSI(58.16, (4 ENTRIES) SITE: BIRMINGHAM ISC (#14) ^PSI(58.16,D0,0)= (#.01) NAME [1F] ^ ^PSI(58.16,D0,1,0)=^58.18^^ (#1) TYPE DESCRIPTION ^PSI(58.16,D0,1,D1,0)= (#.01) TYPE DESCRIPTION [1W] ^ GLOBAL MAP DATA DICTIONARY #58.17 -- AOU ITEM LOCATION FILE STORED IN ^PSI(58.17, (2 ENTRIES) SITE: BIRMINGHAM ISC (#14) ------------------------------------------------------------------------ ^PSI(58.17,D0,0)= (#.01) ITEM ADDRESS CODE [1F] ^ ^ (#.5) CODE EXPANSION ==>[3F] ^ GLOBAL MAP DATA DICTIONARY #58.2 -- AOU INVENTORY GROUP FILE STORED IN ^PSI(58.2, (2 ENTRIES) SITE: BIRMINGHAM ISC (#14) ------------------------------------------------------------------------ ^PSI(58.2,D0,0)= (#.01) NAME [1F] ^ ^PSI(58.2,D0,2,0)=^58.23^^ (#2) GROUP DESCRIPTION ^PSI(58.2,D0,2,D1,0)= (#.01) GROUP DESCRIPTION [1W] ^ ^PSI(58.2,D0,3,0)=^58.29P^^ (#3) NARCOTIC AREA OF USE (NAOU) ^PSI(58.2,D0,3,D1,0)= (#.01)NARCOTIC AREA OF USE (NAOU)[1P]^(#2)SORT KEY ==>[2N] ^ ^PSI(58.2,D0,3,D1,1,0)=^58.291PA^^ (#1) INVENTORY TYPE ^PSI(58.2,D0,3,D1,1,D2,0)= (#.01) INVENTORY TYPE [1P] ^ STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 214 IA #: 214 DATE CREATED: FEB 22, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA214 ORIGINAL NUMBER: 214 GENERAL DESCRIPTION: The following is entered as DBIA until the next version of DA: All components indentified in this integration request involve reading from IFCAP files. Drug Accountability does not write to any IFCAP files. Looking toward an interface with the IFCAP Generic Inventory Package, Drug Accountability (PSA) begins the process with a Connection Menu. The PSAINIT creates in the DRUG file (#50) a multiple (#50.0441) pointing to the IFCAP ITEM MASTER file (#441), enabling a direct link between the DRUG file (#50) and the ITEM MASTER file (#441). The first connecting tool provided in the Connection Menu is a sub- menu using the National Drug Code (NDC) to attempt matching entries. In the ITEM MASTER file (#441), the NDC field (#4) is located in the VENDOR multiple (#6). This field has an input transform that prevents a user from using the same NDC for more than one ITEM MASTER file entry. In studying an ITEM MASTER file from a local site, it was discovered that there were several entries in their ITEM MASTER file that did possess the same NDC. Since this situation might lead a connector to link a drug to a potentially less active item, the first option in the NDC Menu is the NDC Duplicates Report (ITEM file). This report loops through the NDC ("F") x-ref in #441. If more than one item contains the same NDC and is not inactive (field #16, '$G(^PRC(441,D0,3))), the duplicates are listed. The report displays the NDC that has more than one item attached to it, the item numbers attached, their SHORT DESCRIPTION (#.05), and the VENDOR (#6) => VENDOR file (#440,#1) that contains the duplicated NDC. The second item on the NDC Menu is the Report Potential NDC Matches option. This report loops through the active, unlinked (to #441) entries in the DRUG file (#50) that have an NDC. If a corresponding NDC is found in the "F" x-ref in the ITEM MASTER file (#441), the NDC and drug name are listed from the DRUG file (#50) and the ITEM NUMBER (#.01) and DESCRIPTION (#.1) listed from the ITEM MASTER file (#441). Using the ITEM NUMBER ("AB") x-ref in the DRUG file (#50), a check is made to see if the matched ITEM MASTER file entry is already linked to another DRUG file entry. If so the user is informed of the existing connection. Using this same loop and display criteria, the Controlled Connection by NDC Match allows the user the opportunity to actually link matched entries. If the user approves the displayed match, a ^DIE stuff of the item number into the item multiple (#50.0441) in the DRUG file occurs. Likewise, the Automated DRUG/ITEM file link by NDC option uses the same loop and display criteria and the ^DIE stuff for all matches in the loop. In the event that the user requires more information about a selected drug from either the DRUG file or the ITEM MASTER file before linking, the Inquire/Compare DRUG file/ITEM file option is available. This option uses a FM inquire with a no-link pointer jump from the DRUG file to the ITEM MASTER file via the NDC "F" x-ref in #441. The user selects the drug from the DRUG file and along with corresponding info from the DRUG file the DESCRIPTION (#.1), NSN (#5), NDC (VENDOR (#6),#4) by which the jump occurred, and from that same VENDOR multiple the UNIT COST (#1), UNIT OF PURCHASE (#1.5), DATE OF UNIT PRICE (#2.5), PACKAGING MULTIPLE (#1.6), calculated unit cost = UNIT COST (#1)/DISPENSE UNITS PER ORDER UNIT from the DRUG file, VENDOR (#.01), CREATED BY (#15), and with a jump to #200 their OFFICE PHONE NUMBER. Using this same jump, the DRUG file/ITEM file Comparison Report displays the same data with the user selecting a range of drugs from the DRUG file. The FSN Menu functions similar to the NDC Menu. The Report Potential FSN Matches option loops through the active, unlinked (to #441) entries in the DRUG file that have an FSN. If a corresponding NSN is found in the "BA" x-ref in the ITEM MASTER file, the FSN and drug name are listed from the DRUG file and the ITEM NUMBER (#.01) and DESCRIPTION (#.1) listed from the ITEM MASTER file. Using the ITEM NUMBER ("AB") x-ref in the DRUG file, a check is made to see if the matched ITEM MASTER file entry is already linked to another DRUG file entry. If so the user is informed of the existing connection. Using this same loop and display criteria the Controlled Connection by FSN Match option allows the user to actually link matched entries. If the user approves the displayed match, a ^DIE stuff of the item number into the item multiple (#50.0441) in the DRUG file occurs. Likewise, the Automated DRUG/ITEM File Link by FSN option uses the same loop and display criteria and the ^DIE stuff for all matches in the loop. The Single Drug Match option uses both the NDC and FSN/NSN tools described previously to offer a connection for a single selection from the DRUG file. If a link to an ITEM MASTER file entry already exists, it is displayed to the user and they may edit the connection in the DRUG file. Using the ITEM NUMBER multiple pointer (#50.0441) in the DRUG file, the user can also do look-ups to the ITEM MASTER file via available x-refs (NSN (BA), SHORT DESCRIPTION (C), VENDOR STOCK # (D), or NDC (F)) in order to select additional connections. The Report of Unlinked DRUG/ITEM File Entries lists active drugs from the DRUG file which do not yet have any entries in the ITEM NUMBER multiple (#50.0441). The Connect Unlinked DRUG/ITEM file Entries option loops through these unlinked entries and offers all the tools described in the Single Drug Match option to perform the links. The Active, Unlinked Drugs in the ITEM File option allows the user to select a purchase date from which to consider an ITEM MASTER file drug active. It then loops through the ITEM MASTER file and when an entry's FSC (#2) = 6505 (Federal Supply Classification for drugs), is not an INACTIVATED ITEM? (#16), is not linked to a drug('$O(^PSDRUG,"AB",ITEM,"")), has an entry in the FCP (#1) multiple, and has within at least one FCP entry, an entry in the PURCHASE ORDER (#1) multiple, the P.O. DATE(s) (#442,#.1) are checked against the user selected purchase date. For entries that pass this criteria, the ITEM NUMBER (#.01), SHORT DESCRIPTION (#.05), NSN (#5), LAST VENDOR ORDERED (#9), NDC (#6,#4) (for the LAST VENDOR ORDERED), and the DESCRIPTION (#.1) are displayed. The Display Connected Drug option allows the user to print both a vendor catalog for a selected item as well as a procurement history. The user selects an entry from the DRUG file. If it is connected to more than one entry in the ITEM MASTER file the user is asked to select one of the connected entries from the ITEM NUMBER multiple (#50.0441). From the ITEM MASTER file, the ITEM NUMBER (#.01), SHORT DESCRIPTION (#.05),and NSN are displayed. If the selected ITEM MASTER file entry has only one VENDOR (#6) or has a MANDATORY SOURCE (#10), then that vendor is displayed along with the VENDOR STOCK # (#3), NDC (#4), PACKAGING MULTIPLE (#1.6), UNIT OF PURCHASE (#1.5), UNIT COST (#1), MINIMUM ORDER (#8), DATE OF UNIT PRICE (#2.5), and REQUIRED ORDER MULTIPLE (#9). If there is more than one vendor for the item, the LAST VENDOR ORDERED (#9) is displayed as well as each available vendor sorted by DATE OF UNIT PRICE (#2.5), beginning with the most recent date. For each vendor the PACKAGING MULTIPLE (#1.6), UNIT OF PURCHASE (#1.5), UNIT COST (#1), DATE OF UNIT PRICE(#2.5), and whether or not the vendor has a current contract is listed. The contract verification is made by looping through the CONTRACT NUMBER multiple (#6) in the VENDOR file (#440) and checking the EXPIRATION DATE (#1). If there is an entry in the FCP (#1) multiple for the selected item and any of the FCP entries have an entry in their PURCHASE ORDER (#1) multiple, the user is offered a procurement history. They can enter a date from which they wish to view the history. They must also select an FCP. For each purchase order that passes the criteria, the PURCHASE ORDER NUMBER (#.01), VENDOR (#5), P.O. DATE (#.1), QUANTITY (#40,#2) (LINE ITEM NUMBER located using the "AE" x-ref in the ITEM (#40) multiple), UNIT OF PURCHASE (#3), TOTAL COST(#15), and QUANTITY PREVIOUSLY RECEIVED (#11) are displayed. Average ordered/month, total ordered, and total cost are also listed. If the MANDATORY SOURCE (#10) for the selected item is flagged in the VENDOR file (#440) with an "S" in the SUPPLY WHSE. INDICATOR (#.05), then the user is informed that the Supply Warehouse is the mandatory source. Using the "AD" x-ref in the INVENTORY TRANSACTION file (#445.2) a check is made for any distribution by the warehouse of this item. If procurement history exists, the user is informed and allowed to enter a date from which to view the history. By looping through the "AD" x-ref in #445.2 and checking the TRANSACTION ID (#1)?1"R".N and the DATE POSTED (#2.5) is not less than the user entered date, a history is displayed. From the INVENTORY TRANSACTION file (#445.2), the DATE POSTED (#2.5), TRANSACTION/P.O. NUMBER (#410), -QUANTITY (#6), PACKAGING UNIT (#5), SELLING UNIT PRICE (#8), and OTHER INVENTORY POINT AFFECTED (#14) are displayed. The Unposted Procurement History and Posted Drug Procurement History options are an effort to restore some of the drug accountability lost with the disappearance of the LOG 036 report. For the Unposted Procurement History, the user is asked to select a month to review. A loop through the PROCUREMENT & ACCOUNTING TRANSACTION file (#442), using the P.O. DATE ("AB") x-ref collects PO's for the user selected month. If the COST CENTER (#2) = 822400 (Pharmacy) and the SUPPLY STATUS (#.5)>14 & <45 (basically ordered), the PO's are sorted into ^TMP by Station/FCP. For each Station/FCP the PO's are listed, displaying PURCHASE ORDER NUMBER (#.01), P.O. DATE (#.1), FCP(#1), VENDOR (#5), and TOTAL AMOUNT (#91). While looping through these PO's another ^TMP is created, sorted by the DESCRIPTION (#1) of each ITEM (#40) on each PO. The user is asked if they would like to print item totals. If so, an alphabetical listing occurs displaying each ITEM's (#40) DESCRIPTION (#1) and REPETITIVE (PR CARD) NO. (#1.5) and each PURCHASE ORDER NUMBER (#.01), P.O. DATE (#.1), FCP (#1), QUANTITY (#40,#2), ACTUAL UNIT COST (#40,#5), and TOTAL COST (#40,#15). Finally, the user is if they would like a list of high dollar items. They are invited to enter a cut-off dollar amount and each item exceeding that amount is listed beginning with the highest total cost. The total cost was determined by totaling the TOTAL COST (#40,#15) amounts for each item listed in the previous display and building a ^TMP to sort from high to low. Each ITEM's (#40) DESCRIPTION (#1), total TOTAL COST (#15), and Station/FCP is shown. The Posted Drug Procurement History option uses the TYPE OF INVENTORY POINT ("AC") x-ref in the GENERIC INVENTORY file (#445) to locate a "W" or the warehouse inventory. A loop through the INVENTORY ITEM (#1) multiple, using the ITEM NO. (#.01) to check in the ITEM MASTER (#441) file for a FSC (#2) = 6505 (Federal Supply Classification for drugs) isolates the warehouse drugs in ^TMP. Looping through ^TMP a check is made using the INVENTORY POINT ("AD") x-ref in the INVENTORY TRANSACTION (#445.2) file to isolate items that have had distribution (TRANSACTION ID (#1)?"R".N) and fall within the user selected month (DATE POSTED (#2.5)). These transactions are sorted by the OTHER INVENTORY POINT AFFECTED (#14) and the OTHER INVENTORY POINT AFFECTED (#14) , -QUANTITY (#6), QUANTITY (#410,#10,#2) obtained by using the TRANSACTION /P.O. NUMBER (#445.2,#410), PACKAGING UNIT (#5), SELLING UNIT PRICE (#8), total cost (-QUANTITY (#6) * SELLING UNIT PRICE (#8)), DATE POSTED (#2.5), and TRANSACTION/P.O. NUMBER (#410). Similar to the Unposted Procurement History, a high dollar sort is also offered. As stated in the opening paragraph, the Connection Menu lays the groundwork for an interface with the IFCAP Generic Inventory Package. Phase two of this process is contained in a Pharmacy Location Menu. With this menu the Pharmacy user will create and edit the parameters of a Drug Accountability location such as Inpatient, Outpatient, or a Combined (IP/OP) operation. The purpose of the interface is to allow the receiving that occurs in the Inventory Package to pass the converted dispensing unit quantity of a connected drug (ITEM/DRUG file) from a Generic Inventory point (#445) to a Drug Accountability location (#58.8). To establish a direct link between these two files, a PRIMARY INVENTORY POINT field exists in the DRUG ACCOUNTABILITY STATS file (#58.8). This field points to the GENERIC INVENTORY file (#445) uses the TYPE OF INVENTORY POINT (#.7) = "P" and COST CENTER (#.9) = 822400 (Pharmacy) fields as screens. The input transform also contains a call to ^PSAUTL where the "E" x-ref in #58.8 is checked to prevent the linking of one primary inventory point to more than one DA location. The Set up/edit a Pharmacy Location option allows the user to edit this link. If a DA location (#58.8)is linked to an Inventory point (#445), the INVENTORY ITEMS (#1) are checked both against the "AB" x-ref in the DRUG (#50) file and the "C" x-ref in the DA (#58.8) file to see if all Inventory items are tracked in DA. If not the user is given the ability (^DIE) to add Inventory items to the DA location. The Display Location option shows the PRIMARY INVENTORY POINT (#11) currently linked to the selected DA location. The Inventory Interface sub-menu contains three report options and a populate option. The Report of Inventory items' link to DRUG file displays from a selected GENERIC INVENTORY point (#445), selection screened by COST CENTER (#.9) = 822400 and TYPE OF INVENTORY POINT (#.7) = "P", the ITEM NO. (#445,#1,#.01), either the DESCRIPTION (#.7) or from the ITEM MASTER file (#441), the SHORT DESCRIPTION (#.05)and if connected the DRUG (#50) name. The Loadable Inventory Items Report operates exactly the same, however, only lists connected items. The Populate Pharmacy Location with Inventory items option uses the same criteria and if a connected drug within an inventory point does not yet exist in the DRUG (#10) multiple in the selected DA location (#58.8), a ^DIE stuff occurs with a list of drugs loaded displayed at a user selected device. The Display Drugs Not Loaded in Primary option loops through the DRUG (#10) multiple in a selected DA location (#58.8) and using the "AB" x-ref in the DRUG (#50) file, checks the "AE" x-ref in the GENERIC INVENTORY (#445) file for the existance of each drug in the linked Primary Inventory Point. Those drugs not found in the Inventory point are displayed along with their ITEM MASTER (#441) file NUMBER (#.01) and SHORT DESCRIPTION (#.05). CONDENSED DATA DICTIONARY---DRUG FILE (#50) VERSION: 6 STORED IN: ^PSDRUG( 01/26/93 -------------------------------------------------------------------------- CROSS REFERENCED BY: ITEM NUMBER(AB) FILE STRUCTURE FIELD FIELD NUMBER NAME .001 NUMBER (NJ5,0), [ ] .01 GENERIC NAME (RF), [0;1] 6 FSN (F), [0;6] 12 ORDER UNIT (P51.5'), [660;2] 13 PRICE PER ORDER UNIT (NJ7,2), [660;3] 14.5 DISPENSE UNIT (F), [660;8] 15 DISPENSE UNITS PER ORDER UNIT (NJ4,0), [660;5] 16 PRICE PER DISPENSE UNIT (NJ6,2), [660;6] 17 SOURCE OF SUPPLY (F), [660;7] 31 NDC (FX), [2;4] 100 INACTIVE DATE (D), [I;1] 441 IFCAP ITEM NUMBER (Multiple-50.0441), [441;0] .01 ITEM NUMBER (M*P441'X), [0;1] CONDENSED DATA DICTIONARY---ITEM MASTER FILE (#441)UCI: LTL,VAA STORED IN: ^PRC(441, 01/26/93 -------------------------------------------------------------------------- CROSS REFERENCED BY: SHORT DESCRIPTION(AC) INACTIVATED ITEM?(AD) NUMBER(B) NSN(BA) NSN(BB) SHORT DESCRIPTION(C) VENDOR STOCK #(D) NDC(F) NSN(G) FILE STRUCTURE FIELD FIELD NUMBER NAME .01 NUMBER (RNJ6,0X), [0;1] .05 SHORT DESCRIPTION (RFX), [0;2] .1 DESCRIPTION (Multiple-441.02), [1;0] .01 DESCRIPTION (W), [0;1] 1 FCP (Multiple-441.03), [4;0] .01 FCP (RFX), [0;1] 1 PURCHASE ORDER (Multiple-441.04), [1;0] .01 PURCHASE ORDER (P442'X), [0;1] 3 PREFERRED VENDOR (*P440'), [0;3] 2 FSC (RP441.2'), [0;3] 5 NSN (FX), [0;5] 6 VENDOR (Multiple-441.01), [2;0] .01 VENDOR (MP440X), [0;1] 1 UNIT COST (RNJ10,3), [0;2] 1.5 UNIT OF PURCHASE (RP420.5'), [0;7] 1.6 PACKAGING MULTIPLE (RNJ6,0), [0;8] 2 CONTRACT (NJ6,0XO), [0;3] 2.2 CONTRACT EXP. DATE (CJ8), [ ; ] 2.5 DATE OF UNIT PRICE (RD), [0;6] 3 VENDOR STOCK # (FX), [0;4] 4 NDC (FX), [0;5] 8 MINIMUM ORDER (NJ6,0), [0;12] 9 REQUIRED ORDER MULTIPLE (NJ6,0), [0;11] 9 LAST VENDOR ORDERED (P440'), [0;4] 10 MANDATORY SOURCE (*P440'), [0;8] 14 DATE ITEM CREATED (D), [0;9] 15 CREATED BY (P3'), [0;11] 16 INACTIVATED ITEM? (S), [3;1] CONDENSED DATA DICTIONARY---VENDOR FILE (#440) UCI: LTL,VAA STORED IN: ^PRC(440, 01/26/93 -------------------------------------------------------------------------- CROSS REFERENCED BY: SUPPLY WHSE. INDICATOR(AC) NAME(AD) INACTIVATED VENDOR(AE) NAME(B) SYNONYM(C) FILE STRUCTURE FIELD FIELD NUMBER NAME .001 NUMBER (NJ6,0), [ ] .01 NAME (RFX), [0;1] .05 SUPPLY WHSE. INDICATOR (SX), [0;11] 6 CONTRACT NUMBER (Multiple-440.03), [4;0] .01 CONTRACT NUMBER (MFX), [0;1] 1 EXPIRATION DATE (RD), [0;2] CONDENSED DATA DICTIONARY---NEW PERSON FILE (#200) VERSION: 6.5 STORED IN: ^VA(200, 01/27/93 -------------------------------------------------------------------------- FILE STRUCTURE FIELD FIELD NUMBER NAME .01 NAME (RFX), [0;1] .132 OFFICE PHONE (F), [.13;2] CONDENSED DATA DICTIONARY---PROCUREMENT & ACCOUNTING TRANSACTIONS FILE (#442) STORED IN: ^PRC(442, 01/27/93 -------------------------------------------------------------------------- CROSS REFERENCED BY: P.O. DATE(AB) FCP(AC) ISSUE VOUCHER NO.(SUPPLY)(AD) FILE STRUCTURE FIELD FIELD NUMBER NAME .01 PURCHASE ORDER NUMBER (RFX), [0;1] .1 P.O. DATE (RDX), [1;15] .5 SUPPLY STATUS (*P442.3'), [7;1] 1 FCP (RFX), [0;3] 2 COST CENTER (FX), [0;5] 5 VENDOR (R*P440X), [1;1] 40 ITEM (Multiple-442.01), [2;0] .01 LINE ITEM NUMBER (RMNJ2,0X), [0;1] 1 DESCRIPTION (Multiple-442.05), [1;0] .01 DESCRIPTION (W), [0;1] 1.5 REPETITIVE (PR CARD) NO. (*P441'X), [0;5] 2 QUANTITY (RNJ9,2), [0;2] 3 UNIT OF PURCHASE (RP420.5'X), [0;3] 5 ACTUAL UNIT COST (RNJ9,2X), [0;9] 11 QUANTITY PREVIOUSLY RECEIVED (NJ9,2), [2;8] 15 TOTAL COST (RNJ9,2), [2;1] 91 TOTAL AMOUNT (RNJ10,2), [0;15] CONDENSED DATA DICTIONARY---INVENTORY TRANSACTION FILE (#445.2) STORED IN: ^PRCP(445.2, 01/27/93 -------------------------------------------------------------------------- CROSS REFERENCED BY: DATE POSTED(ABEG) ITEM NO.(AC) INVENTORY POINT(AD) ITEM NO.(AE) INVENTORY POINT(ANXT) INVENTORY POINT(B) TRANSACTION/P.O. NUMBER(C) TRANSACTION ID(T) FILE STRUCTURE FIELD FIELD NUMBER NAME .01 INVENTORY POINT (RP445'), [0;1] 1 TRANSACTION ID (RF), [0;2] 2.5 DATE POSTED (D), [0;17] 5 PACKAGING UNIT (F), [0;6] 6 QUANTITY (NJ6,0), [0;7] 8 SELLING UNIT PRICE (NJ11,3), [0;9] 14 OTHER INVENTORY POINT AFFECTED (P445'), [0;18] 410 TRANSACTION/P.O. NUMBER (F), [0;19] CONDENSED DATA DICTIONARY---GENERIC INVENTORY FILE (#445) STORED IN: ^PRCP(445, 01/27/93 -------------------------------------------------------------------------- CROSS REFERENCED BY: DISTRIBUTION POINT(AB) TYPE OF INVENTORY POINT(AC) INVENTORY USER(AD) ITEM NO.(AE) ABBREVIATED NAME(AF) KEEP PERPETUAL INVENTORY?(AG) INVENTORY POINT(B) INVENTORY POINT(C) FILE STRUCTURE FIELD FIELD NUMBER NAME .01 INVENTORY POINT (RFX), [0;1] .7 TYPE OF INVENTORY POINT (R*SX), [0;3] .9 COST CENTER (P420.1'), [0;7] 1 INVENTORY ITEM (Multiple-445.01), [1;0] .01 ITEM NO. (MP441'X), [0;1] CONDENSED DATA DICTIONARY---DRUG ACCOUNTABILITY STATS FILE (#58.8) STORED IN: ^PSD(58.8, 01/27/93 -------------------------------------------------------------------------- CROSS REFERENCED BY: DRUG(C) PRIMARY INVENTORY POINT(E) FILE STRUCTURE FIELD FIELD NUMBER NAME .01 PHARMACY LOCATION (RF), [0;1] 10 DRUG (Multiple-58.8001), [1;0] .01 DRUG (MR*P50'X), [0;1] 11 PRIMARY INVENTORY POINT (*P445'X), [0;6] This DBIA is effective until 18 months following Drug Accountability V2.0. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT NUMBER: 215 IA #: 215 DATE CREATED: FEB 24, 1993 CUSTODIAL PACKAGE: CONTROLLED SUBSTANCES CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA215 ORIGINAL NUMBER: 215 GENERAL DESCRIPTION: Export Drug Accountability files 58.8 DRUG ACCOUNTABILITY STATS 58.81 DRUG ACCOUNTABILITY TRANSACTION 58.16 AOU INVENTORY TYPE 58.83 CS COMPLETION STATUS 58.82 CS ORDER STATUS 58.86 CS DESTRUCTION 58.84 DRUG ACCOUNTABILITY TRANSACTION TYPE TEMPORARY FOR V1.0. STATUS: Active DURATION: Next Version SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham NUMBER: 218 IA #: 218 FILE NUMBER: 45.3 GLOBAL ROOT: DIC(45.3, DATE CREATED: MAR 04, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA218-A ORIGINAL NUMBER: 218 ID: DIC(45.3, GLOBAL REFERENCE: DIC(45.3, FIELD NUMBER: .01 FIELD NAME: CODE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: SPECIALTY LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: DEPARTMENT CODE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham SUBSCRIBING PACKAGE: INTEGRATED BILLING EDITOR: PAJERSKI,JAN NUMBER: 219 IA #: 219 DATE CREATED: MAR 04, 1993 CUSTODIAL PACKAGE: INCOMPLETE RECORDS TRACKING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGJSUM NAME: DBIA219 ORIGINAL NUMBER: 219 ID: DGJSUM GENERAL DESCRIPTION: A DBIA with INCOMPLETE RECORD TRACKING is granted for the following: Purpose: To allow the IRT file to be updated automatically with data generated through the Discharge Summary or Test Integration Utilities Package whenever a discharge or other deficiency type summary is dictated, transcribed, signed or reviewed. Distribution of the IRT interface routine: DGJSUM. Responsibilities: It will be the Albany IRMFO's responsibility to maintain the interface routine DGJSUM and make sure that it functions properly to lookup, create and update IRT records. The Salt Lake IRMFO will be responsible to make sure that the entry points to DGJSUM are accessed in an appropriate manner with good data being passed. If any modification to either package is made that will affect the functionality of this interface, then it will be necessary for the IRMFO responsible for the change to communicate with the other IRMFO in order to resolve any issues. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22888248 COMPONENT/ENTRY POINT: CHECK COMPONENT DESCRIPTION: Access to CHECK^DGJSUM(DFN,DGJTDT,DGJPARM,DGJIRTDA,DGJT,DGJFLG,DJGSUM) to check to see if the IRT package is enabled. If it is enabled to find and return a pointer to the matching IRT record for the given Patient and Admission. When a matching IRT record isn't found, a new record will need to be created. This entry point will be passed the DFN, Discharge Date (DGJTDT), pointer to the IRT record (DGJIRTDA) if previously passed to the Discharge Summary file, and an array (DGJT) with Division (DGJT("DIV")), Admission IFN (DGJT("AD#")), Ward (DGJT("WARD")), and Treating Specialty (DGJT("TS")). In addition, the IRT TYPE OF DEFICIENCY may be passed in DGJTYP (parameter is optional.) The default value will be "DISCHARGE SUMMARGY". Parameter passing by reference will return the IRT parameter (DGJPARM) which contains a number greater than zero in the first piece if IRT is enabled and a number greater than zero in the 3rd piece if Review Discharge Summary Required is enabled, the pointer to the IRT record (DGJIRTDA) and a Flag (DGJFLG) equal to 1 if a new record is created. In all cases, this entry point will be accessed to check to see if the IRT package is enabled and if so retrieve the pointer to the IRT record. If the IRT package isn't enabled or a pointer to the IRT record isn't returned then no other entry points will be accessed to update the IRT file. COMPONENT/ENTRY POINT: EDIT COMPONENT DESCRIPTION: Access to EDIT^DGJSUM(DGJIRTDA,DGJVDD,DGJVDB,DGJVDT,DGJVTB,DGJPARM) to update the following fields in the IRT record: Date Dictated, Dictated By, Date Transcribed, and Transcribed by. This entry point will be passed Date Dictated (DGJVDD) , Dictated By (DGJVDB), Date Transcribed (DGJVDT) and Transcribed By (DGJVTB), as well as the following variables returned from the entry point described in item #1: the pointer to the IRT record (DGJIRTDA) and the IRT parameter (DGJPARM). Nothing needs to be returned. COMPONENT/ENTRY POINT: SIGUP COMPONENT DESCRIPTION: Access to SIGUP^DGJSUM(DGJIRTDA,DGJDS,DGJSB,DGJDR,DGJRB,DGJPARM) to update the following fields in the IRT record: Date Signed and Signed By, Date Reviewed and Reviewed By. This entry point will be passed Date Signed (DGJDS), Signed By (DGJSB), Date Reviewed (DGJDR) and Reviewed By (DGJRB). If the IRT package parameter is set to review Discharge Summaries (determine by 3rd field of DGJPARM being greater than 1, then Date Reviewed and Reviewed By will be passed with what is in the Discharge Summary record other wise the "@" will be passed. The following variables returned from the entry point described in item #1 will also be passed: the pointer to the IRT record (DGJIRTDA) and the IRT parameter (DGJPARM). Nothing is returned. COMPONENT/ENTRY POINT: DCSDEL COMPONENT DESCRIPTION: Access to DCSDEL^DGJSUM(DGJIRTDA,DGJPARM) to delete the following fields in the IRT file: Date Dictated, Dictated By, Date Transcribed, Transcribed by, Date Signed, Signed By, Date Reviewed, and Reviewed By. This entry point will be passed the pointer to the IRT record (DGJIRTDA) and the IRT parameter (DGJPARM) returned from the entry point described in item #1. Nothing is returned. This is necessary in case a Discharge Summary is accidently entered for the wrong admission or patient. SUBSCRIBING PACKAGE: DISCHARGE SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City EDITOR: RUBIN,ALICE NUMBER: 220 IA #: 220 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: MAR 24, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA220 ORIGINAL NUMBER: 220 ID: DPT( GENERAL DESCRIPTION: Outpatient Pharmacy has permission to edit fields in Patient File (#2): Outpatient Pharmacy has used two input templates, PSO OUTPT and PSO OUTPTA in the Patient File (#2) since about 1984. PSO OUTPT template edits the following fields: .03,.09,.111:.116, .131, 148, .172, .12105, .1211:.1213, .1219 and .091. PSO OUTPTA template edits the following fields: .12105, .1211:.1213, .1219 and .1214:.1218. The MAS developers have agreed to allow the Outpatient Pharmacy package to edit these fields using the above input templates under the following conditions: 1. Patch per ZIP+4. There will soon be two new zip+4 fields associated with Permanent and Temporary Address fields that should be used instead of the zip code fields listed above. 2. MAS developers will provide a utility to edit the above information and with the next release of Outpatient Pharmacy I will use their utility. Outpatient Pharmacy developers agree to the above stated conditions of use. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 221 IA #: 221 FILE NUMBER: 50 GLOBAL ROOT: PSDRUG( DATE CREATED: MAY 24, 1999 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA221-A ORIGINAL NUMBER: 221 ID: PSDRUG( GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. All fields and x-refs in file 50 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of June 1, 2006. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 25907838 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham SUBSCRIBING PACKAGE: BAR CODE MED ADMIN ISC: Birmingham SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: NATIONAL DRUG FILE SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE SUBSCRIBING PACKAGE: CLINICAL REMINDERS EDITOR: BLOCKER,DAVE EDITOR: RUZBACKI,RON T NUMBER: 223 IA #: 223 FILE NUMBER: 58.8 GLOBAL ROOT: PSD(58.8, DATE CREATED: APR 21, 1993 CUSTODIAL PACKAGE: DRUG ACCOUNTABILITY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA223 ORIGINAL NUMBER: 223 ID: PSD(58.8, GENERAL DESCRIPTION: Outpatient Pharmacy is given permission by Controlled Substances to make the following calls: GLOBAL MAP DATA DICTIONARY #58.8 -- DRUG ACCOUNTABILITY STATS FILE 2/26/93 --------------------------------------------- STORED IN ^PSD(58.8 SITE: ISC BIRMINGHAM -------------------------------------------------------------------------- ^PSD(58.8,D0,0)= (#20) OUTPATIENT SITE [10P] ^ STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 224 IA #: 224 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: APR 21, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA224 ORIGINAL NUMBER: 224 ID: VA(200, GENERAL DESCRIPTION: Outpatient Pharmacy is given permission by Kernel to make calls to the following: GLOBAL MAP DATA DICTINARY #200 -- NEW PERSON FILE 2/25/93 STORED IN ^VA(200, SITE: ISC BIRMINGHAM (VERSION 6.5) ---------------------------------------------------------------------- ^VA(200,D0,PS)= (#53.1) AUTHORIZED TO WRITE MED ORDERS [1S] ^ (#53.2) ==>DEA# [2F] ^ (#53.3) VA# [3F] ^ (#53.4) INACTIVE DATE [4D] ^ ==>(#53.5) PROVIDER CLASS [5P] ^ (#53.6) PROVIDER TYPE [6S] ^ ==>(#53.7) REQUIRES COSIGNER [7S] ^ (#53.8) USUAL COSIGNER ==>[8P] ^ (#53.9) REMARKS/COMMENTS [9F] ^ ^VA(200,D0,PS1,0)=^200.541P^^ (#54.1) LICENSING STATE ^VA(200,D0,PS1,D1,0)= (#.01) LICENSING STATE [1P] ^ ^VA(200,D0,PS2,0)=^200.55P^^ (#54.2) STATE ISSUING DEA NUMBER ^VA(200,D0,PS2,D1,0)= (#.01) STATE ISSUING DEA NUMBER [1P] ^ ^VA(200,D0,TPB)= (#53.91) NON-VA PRESCRIBER [1S] ^ (#53.92) EXCLUSIONARY ==>CHECK PERFORMED [2S] ^ (#53.93) DATE EXCLUSIONARY LIST ==>CHECKED [3D] ^ (#53.94) ON EXCLUSIONARY LIST [4S] ^ (#53.95) ==>TAX ID [5F] ^ (#53.96) EXCLUSIONARY CHECKED BY [6P:200] ^ STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham SUBSCRIBING PACKAGE: INTEGRATED BILLING NUMBER: 227 IA #: 227 FILE NUMBER: 445 GLOBAL ROOT: PRCP(445, DATE CREATED: MAY 05, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA227-A ORIGINAL NUMBER: 227 ID: PRCP(445, GENERAL DESCRIPTION: Prosthetics is granted permission to make the following calls to the IFCAP package (GIP and 1358 Modules). As stated below this is until the next version of either IFCAP or Prosthetics. For GIP (Items 1 - 3): Item 1 is needed so that we can check to see if an item that is being returned from loan is in an inventory point, so that it can be placed back into inventory. Item 2 is needed to so that we can do a lookup to make sure that the user returning a loaned item is an Inventory User. Item 3 is needed so that we can make sure that the user returning an item is an Inventory User for that particular Inventory Point. Item 1 Description: Read Only access to File #445, GENERIC INVENTORY, to look at the cross-referenced node ^PRCP(445,"AE",ITEM#,DA). Item 2 Description: Read Only access to File #445, GENERIC INVENTORY, so that we can look at the "AD" cross-reference in the file. Item 3 Description: Read Only access File #445, field 6, INVENTORY USER. Item 5 DIC lookup on File #445 Generic Inventory. Read access only to the .01 field. The variable PRCPPRIV may be set by Prosthetics. STATUS: Active DURATION: Next Version SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City NUMBER: 228 IA #: 228 FILE NUMBER: 353.1 GLOBAL ROOT: IBE(353.1, DATE CREATED: MAY 12, 1993 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA228-A ORIGINAL NUMBER: 228 ID: IBE(353.1, GLOBAL REFERENCE: IBE(353.1,D0,0) FIELD NUMBER: .01 FIELD NAME: CODE LOCATION: 0;1 ACCESS: Pointed to STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: FEE BASIS ISC: Albany NUMBER: 229 IA #: 229 DATE CREATED: MAY 18, 1993 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIWE NAME: DBIA229-A ORIGINAL NUMBER: 229 ID: DIWE GENERAL DESCRIPTION: MailMan V7 has permission to make the following calls to FileMan: 1. MailMan has a special way of calling the FileMan editor. It calls EN^DIWE and supplies DWPK, DWLW, DIA, DIC and DIA("P"). The way that MailMan calls DIWE allows a slightly different set of functionalities. The transfer command is defaulted to use the 3.9 (Message) file if no file is specified. DWPK forces automatic wrapping of text at DWLW number of characters. Because of this the variable DC must have the appropriate value and MailMan kills it to may sure it is undefined. DWLW and DWPK have recently been released along with EN^DIWE as a callable entry point, but the use of DIC and DIA together still provide to MailMan special functionality in the FileMan line editor, namely the ability to transfer lines of text in from other messages that the user is the sender or a recipient of. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN VARIABLES: DWPK TYPE: Input VARIABLES: DWLW TYPE: Input VARIABLES: DIA TYPE: Input VARIABLES: DIC TYPE: Input VARIABLES: DIA('P') TYPE: Input SUBSCRIBING PACKAGE: MAILMAN ISC: Washington/Silver Spring NUMBER: 230 IA #: 230 DATE CREATED: MAY 18, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA230 ORIGINAL NUMBER: 230 GENERAL DESCRIPTION: MailMan V7 has permission to make the following calls to Kernel: 1. The modules affected by this agreement are in the namespace: o Device Handler (ZIS* & %ZIS*, not ZISL* & %ZISL*) 2. REQ^%ZTLOAD is called in the following manner to ensure a back-up task exists if this one should fail: I $L(ION) S ZTIO(1)="D",ZTIO=ION D REQ^%ZTLOAD The result of this call leaves the task in the IO queue for the device it is running on (and no other, even if the device is a member of a hunt group). 3. The Kernel Site Parameters file contains fields that are used by modules in Kernel other than MailMan. The MailMan development team will maintain the file and will reserve fields and field numbers in the range of 3000 to 3999 for the use of this module. No alpha subscripts will be used by non-MailMan kernel packages without agreement from the MailMan development team except for those already in use and noted below. The exception to the above are nodes beginning with the Kernel namespace (ZI) which is reserved for this kernel packages and cross references beginning with any letter, but having the above namespace immediately follow that letter (EG. AZI5). Any changes to this file require the notification of the MailMan development team. A method for ensuring that the distribution of the file by MailMan will then be negotiated. The fields that are currently in use and are not *'ed for removal within 18 months are: (#=multiple) Field Number # Description node;piece 31.1 Max spool lines SPL;1 31.2 Max spool documents SPL;2 31.3 Max spool doc life SPL;3 4. By agreement files 3.51, Spool Document [in ^XMB(3.51,] and file 3.519, Spool Data [in ^XMBS(3.519,] can continue to exist in the MailMan namespaced globals. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MAILMAN ISC: Washington/Silver Spring NUMBER: 231 IA #: 231 DATE CREATED: MAY 18, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA231 ORIGINAL NUMBER: 231 GENERAL DESCRIPTION: MailMan V7 has permission to make the following calls from Kernel Task Manager V7: 1. The Kernel modules that this document refers to are: o Task Management (ZTM* and %ZTM*) 2. REQ^%ZTLOAD is called in the following manner to ensure a back-up task exists if this one should fail: I $L(ION) S ZTIO(1)="D",ZTIO=ION D REQ^%ZTLOAD The result of this call leaves the task in the IO queue for the device it is running on (and no other, even if the device is a member of a hunt group). 3. The routine XMS5 tries to confirm that tasks exist by looking at: $D(^%ZTSK(task,0)) ==> if the node exists the task exists $D(^%ZTSCH("TASK",task)) ==> If the node exists, the task is running "12345AG"[%ZTSCH("TASK",.1) $D(^%ZTSCH("IO",device,$h,task)) ==> The task is scheduled 4. MailMan 7 looks at ^%ZTSK(task,"C",0) for a count of the times the task has run. The next version will not use this any more. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MAILMAN ISC: Washington/Silver Spring NUMBER: 232 IA #: 232 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: MAY 18, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA232 ORIGINAL NUMBER: 232 ID: VA(200, GENERAL DESCRIPTION: The Inpatient Medications package requests a DBA exemption to allow the .01 field of the INPATIENT USER PARAMETERS file (53.45) to point to the NEW PERSON file (200). This file contains fields that are used by Inpatient Medications to store data used in the order entry process, and has been DINUMED to the NEW PERSON file as recommended in the peer review, to allow these fields to be more easily moved to 200 if necessary in a future release. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 233 IA #: 233 DATE CREATED: MAY 18, 1993 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA233 ORIGINAL NUMBER: 233 GENERAL DESCRIPTION: MAILMAN has permission to make the following calls to VA Fileman: 1. FileMan has a special way of using the XMD interface and it also has special calls into the XMP series of routines so that it can load INITs directly into a message during a DIFROM. As such the variable DIFROM effects that way some of these routines work so that the DIFROM procedure can use them to enter data and routines reiteratively into messages. o In the routine XMD, if $D(DIFROM) security keys are not ignored. o In the routine XMD, if $D(DIFROM) will cause a call to XMD at either tag EN1 or tag EN2 to quit after text is added to a message, but before the message is delivered. o In the routine XMD, if $D(DIFROM) before delivery, security will be added automatically by a call to XMASEC. o In the routine XMASEC, if $D(DIFROM) security is forced onto the message. o In the routine XMP, if $D(DIFROM) the string " (DIFROM)" is added to the 1st line of the PackMan message to show how it was created. o In the routine XMPH a special prompt is provided where DIFROM loading into a message causes special help for the programmer. 2. Kernel modules to which this document refers are (even if they are at some point separated from the Kernel and become independent modules of their own): FileMan (DI*) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MAILMAN ISC: Washington/Silver Spring NUMBER: 234 IA #: 234 DATE CREATED: MAY 18, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA234 ORIGINAL NUMBER: 234 GENERAL DESCRIPTION: Mailman is given permission to make the following calls to Kernel: 1. CHK^XM is an entry point set aside only for calls external from MailMan. It is used by KERNEL routines to notify users of new messages for a user during logon or as invoked from MenuMan. XMDUZ is used if supplied, otherwise DUZ is a pointer to the user's Mailbox. The symbol table of the caller is changed as the code currently stands. Y is output as a count of new messages. % and D are also used and not killed by MailMan. The Kernel security routine will continue to use this entry point, which also is necessary to make sure that ^TMP("XMY",$J) is cleaned out on login and ensures that when job numbers are reused after reboot, there is not data in ^TMP("XMY",$J) to include recipients from old mail sessions in currently generated bulletins that come from outside of MailMan. An example is the 'Dropping into Programmer Mode bulletin'. 2. ^XM may be called in order to offer MailMan as a service directly to users on logon. 3. The XMUSER and XMMGR menus may be used in high level menu structures. 4. Kernel modules to which this document refers are (even if they are at some point separated from the Kernel and become independent modules of their own) are System security (XU* and XT*). 5. Kernel security and user related modules currently can call NEW^XM to set up an new user's or reactivated user's mail box. The entry point uses the variables I, Y and K destructively. If it is called for a user who is being reactivated, that user will not receive responses to messages he is a recipient of and were created before his reinstatement, unless he is explicitly forwarded them, or he 'owns' the original message in one of his mail boxes. 6. XMPC is called by the Kernel routine comparer. All the proper set-up has been done and MailMan will coordinate any changes in this area with the programmer responsible for Kernel Utilities. 7. Kernel directly references the 5th piece of the Mail Basket multiple of the Mail Box file (3.7) to get the number of messages in a mail basket. 8. Kernel directly references the 6th piece of the zero node of the Mail Box file (3.7) to get the number of new messages in a mail box 9. There are some data fields in the Mail Box file (3.7) that are not used in MailMan. They are used by sign-on security and should be maintained by sign-on security routines also. field # Description node;piece 20 Last Sign-on Date/Time .1;1 21 Last Terminal Type Used .2;1 22 Already Signed On To Devices 100 (multiple) 10. The Kernel Site Parameters file contains fields that are used by modules in Kernel other than MailMan. The MailMan development team will maintain the file and will reserve fields and field numbers in the range of 1000 to 1999 for the use of this kernel module. No alpha subscripts will be used by non-MailMan kernel packages without agreement from the MailMan development team except for those already in use and noted below. The exception to the above are nodes beginning with the namespaces (XU amd XT) which are reserved for non-MailMan kernel packages and cross references beginning with any letter, but having the above namespaces immediately follow that letter (EG. AXT5). Any changes to this file require the notification of the MailMan development team. A method for ensuring that the distribution of the file by MailMan will then be negotiated. Field Number # Description node;piece 11 Auto-generate access codes 3;1 12 User char Template 3;2 202 Default number of attempts XUS;2 203 Default lock-out time XUS;3 204 Default Multiple sign-ons XUS;4 205 Ask device at sign-on XUS;5 209 Default type-ahead XUS;9 211 Bypass Device lock-out XUS;10 212.1 Device to audit 4.33 (subfile) 240 INTRO text INTRO STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MAILMAN ISC: Washington/Silver Spring NUMBER: 237 IA #: 237 DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOSD2 NAME: DBIA237-A ORIGINAL NUMBER: 237 ID: PSOSD2 GENERAL DESCRIPTION: Integrated Billing is given permission from Outpatient Pharmacy to call HD^PSOSD2 and PAT^PSOSD for the purpose of printing the Action Profile and the Information Profile in batch. CONDITIONS: The entry points may only be used in an approved fashion. The following subroutine uses the entry points in an acceptable manner: RXPROF ;For printing the Outpatient Pharmacy Action Profile or the ;Information Profile for a single patient whose DFN is defined. ;Does not ask for the device nor close the device. ;INPUTS: ;PSDAYS = number of days to print the medication profile for ;PSTYPE=1 for the Action Profile, =0 for the Information Profile ;DFN ; N IBDFN,ADDR,ADDRFL,CLASS,CNDT,DRUG,HDFL,I,II,J,L,LINE,P,PAGE, PSDOB,PSII X,PSNAME,PSOI,PSSN,PSIX,PGM,PRF,PSDATE,VAL,VAR,RX, RX0,RX2,ST,ST0,PSDAY,RF,RFS,PSOPRINT,X1,X2,ZTSK,X,Y,PSII,PSDT,LMI S IBDFN=DFN S X1=DT,X2=-PSDAYS D C^%DTC S (PSDATE,PSDAY)=X S LINE="" F I=1:1:132 S LINE=LINE_"-" S PAGE=1 D HD^PSOSD2,PAT^PSOSD W @IOF S DFN=IBDFN Q STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: HD SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany NUMBER: 238 IA #: 238 FILE NUMBER: 70 GLOBAL ROOT: RADPT( DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA238-A ORIGINAL NUMBER: 238 ID: RADPT( GLOBAL REFERENCE: RADPT(D0,0) GENERAL DESCRIPTION: Radiology has agreed for AMIE to make the following calls: GLOBAL REF. NODE;PIECE USAGE ^RADPT 0 Zero node check STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 239 IA #: 239 FILE NUMBER: 4.3 GLOBAL ROOT: XMB(1, DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA239-A ORIGINAL NUMBER: 239 ID: XMB(1, GLOBAL REFERENCE: XMB(1,D0,0) FIELD NUMBER: .01 FIELD NAME: DOMAIN NAME LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 240 IA #: 240 FILE NUMBER: 63 GLOBAL ROOT: LR( DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA240-A ORIGINAL NUMBER: 240 ID: LR( GLOBAL REFERENCE: LR(D0,'CH', GLOBAL REFERENCE: LR(D0,'MI', GENERAL DESCRIPTION: Laboratory Package has given permission to AMIE to make the following calls: GLOBAL REF. NODE;PIECE USAGE ^LR( "CH";11 Current Agreement number 95 "MI";11 Current Agreement number 95 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 241 IA #: 241 FILE NUMBER: 4 GLOBAL ROOT: DIC(4, DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA241-A ORIGINAL NUMBER: 241 ID: DIC(4, GLOBAL REFERENCE: DIC(4,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: DIC(4,D0,99) FIELD NUMBER: 99 FIELD NAME: STATION NUMBER LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 242 IA #: 242 DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSDVR NAME: DBIA242-A ORIGINAL NUMBER: 242 ID: GMTSDVR GENERAL DESCRIPTION: PIMS (MAS) users often have a need to print a Health Summary after printing the 10-10. PIMS, therefore, is given permission for a database integration agreement with Health Summary to allow PIMS to call the line tag ENXQ^GMTSDVR. This call allows tasked or non-tasked Health Summary printout. Prior to the call, the following two variables will be defined: STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: ENXQ VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: (the internal entry number for the Patient File) VARIABLES: GMTSTYP TYPE: Input VARIABLES DESCRIPTION: (the internal entry number for the desired Health Summary type) SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 244 IA #: 244 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: AMIE Access to Patient File Fields ORIGINAL NUMBER: 244 ID: DPT( CREATOR: FAIRBROTHER,EILEEN GENERAL DESCRIPTION: ALL FIELDS ACCESSIBLE TO AMIE THROUGH THIS AGREEMENT ARE BASED ON FILEMAN CALLS ONLY. AMIE has permission from PIMS to make the following calls: GLOBAL REF. NODE;PIECE USAGE ^DPT( .11;1 Street address line 1 .11;2 Street address line 2 .11;3 Street address line 3 .11;4 City .11;5 State .11;6 Zip Code .11;7 County .11;8 Province .11;9 Postal Code .11;10 Country .11;12 Zip+4 .13;1 Residence PhoneNumber .13;2 Work Phone Number .29;1 Date Ruled Incompetent (VA) .29;2 Date Ruled Incompetent(CIVIL) .29;12 Rated Incompetent .3;1 Service Connected .31;2 Claim Folder Location .31;3 Claim Number .32;4 Service Discharge Type [LAST] .32;5 Service Branch [LAST] .32;6 Service Entry Date [LAST] .32;7 Service Separation Date [LAST] .36;1 Primary Eligibility Code .36;2 Eligibility Status Date .361;1 Eligibility Status .362;12 Receiving A&A Benefits .372;1 Rated Disabilities VA .372;2 Disability Percentage .372;3 Service Connected "DIS"; Disposition Log-in Date "S";1 Appointment Clinic "S";16 Appointment Type Directly edits the following fields in the Patient file: .02 SEX .03 DOB .09 SSN .111 Street Address 1 .1112 ZIP+4 .112 Street Address 2 .113 Street Address 3 .114 City .115 State .116 Zip Code .117 County .1171 Province .1172 Postal Code .1173 Country .131 Phone Number Res. .132 Phone Number Work .301 Service Connected .302 Ser. Con. Percentage .313 Claim Number .312 Claim Folder Location .323 Period of Service .324 Service Discharge Type [LAST] .325 Service Branch [LAST] .326 Service Entry Date [LAST] .327 Service Separation Date [LAST] .3611 Eligibility Status .361 Primary Eligibility Code .525 POW Status Indicated .3612 Elig. Status Dat 1901 Veterab Yes/No -Editing of the permanent address information .111;.1112;.112;.113;.114;.115;.116; .1112;.117;.1171;.1172; .1173;.131; .132; - Fields .1171, .1172, .1173 (Province, Postal Code, Country) will be set using FM input template(s) -AMIE also has LAYGO access to the Patient file per agreement with the MAS SIUG. Following release of patch DG*5.3*797, AMIE/CAPRI will use FileMan to edit the following fields of File 2, Subfile .3216, Military Service Episode multiple: .01 Service Entry Date .02 Service Separation Date .03 Service Branch .06 Service Discharge Type STATUS: Active DURATION: Till Otherwise Agreed KEYWORDS: AMIE KEYWORDS: DPT KEYWORDS: FILE 2 KEYWORDS: PATIENT FILE SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany DATE ACTIVATED: DEC 08, 2010 DATE/TIME EDITED: OCT 19, 2010@14:30 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: FAIRBROTHER,EILEEN WITH CONCURRENCE OF: MULLER,RICHARD DATE/TIME EDITED: NOV 02, 2010@15:20 ACTION: APPROVED AT THE REQUEST OF: FAIRBROTHER,EILEEN WITH CONCURRENCE OF: MULLER,RICHARD DATE/TIME EDITED: NOV 18, 2010@12:31 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: FAIRBROTHER,EILEEN DATE/TIME EDITED: DEC 08, 2010@15:00 ACTION: APPROVED AT THE REQUEST OF: FAIRBROTHER,EILEEN NUMBER: 245 IA #: 245 DATE CREATED: JUN 28, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA245 ORIGINAL NUMBER: 245 GENERAL DESCRIPTION: Engineering version 7.0 has permission to export the following: FILE 446.4 BARCODE PROGRAM with two entries (ENNX and ENPM) FILE 446.6 SPECIALTY COMMANDS with one entry (TRAKKER 9440) These files and entries are necessary for uploading equipment data from portable bar code readers into the Engineering database. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring NUMBER: 246 IA #: 246 DATE CREATED: JUN 28, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA246 ORIGINAL NUMBER: 246 GENERAL DESCRIPTION: Version 4.0 of IFCAP will call an Engineering routine whenever an Engineering work order is entered into the SORT GROUP of a Control Point Activity Transaction (Field 49 of File 410). The effect of this call will be to enter a pointer to the Control Point Activity Transaction in the Work Order File and to update the work order status. MUMPS cross-reference AR on Field 49 of File 410 will call ACCX^ENLIB2. Before calling this foreign routine, the IFCAP cross-reference will make sure that ^ENG("VERSION") is greater than 6.4. This insures the existence of the foreign routine. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring NUMBER: 248 IA #: 248 FILE NUMBER: 4.2 GLOBAL ROOT: DIC(4.2, DATE CREATED: DEC 01, 1991 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA248 ORIGINAL NUMBER: 248 ID: DIC(4.2, GENERAL DESCRIPTION: ROES acesses the following entities in Kernel: 1) DOMAIN - DIC 4.2 ^DIC(4.2,i,0) Field .01 Name (Cross-reference) ^DIC(4.2,"B",NAME,i) Name 2) KERNEL SITE PARAMETERS - DIC 4.3 ^XMB(1,1,0) Field .01 Domain Name 3) SECURITY KEY - DIC 19.1 (Cross-reference) ^XUSEC(KEY,DUZ) Field 2 Holder STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: REMOTE ORDER/ENTRY SYSTEM SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE NUMBER: 249 IA #: 249 DATE CREATED: FEB 01, 1992 CUSTODIAL PACKAGE: EVENT CAPTURE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA249 ORIGINAL NUMBER: 249 GENERAL DESCRIPTION: Kernel is adding the field "COORDINATOR' to the Service/Section File. It will be field 16000 located at node 16000. The field will be exported with Kernel V7 in a post-init, and the entire file for a 'virgin' install. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 250 IA #: 250 FILE NUMBER: 130 GLOBAL ROOT: SRF( DATE CREATED: JUL 20, 1993 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA250 ORIGINAL NUMBER: 250 ID: SRF( GENERAL DESCRIPTION: Occurrence Screen has permission from Surgery to make the following calls: Cross References on file 130: AC - DATE OF OPERATION ADT - DATE OF OPERATION Fields: subscript;piece 130,.01 PATIENT 130,.011 IN/OUT-PATIENT STATUS (0;12) 130,.03 MAJOR/MINOR (0;3) 130,.09 DATE OF OPERATION (0;9) 130,10 SCHEDULED START TIME (31;4) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: OCCURRENCE SCREEN ISC: Hines NUMBER: 251 IA #: 251 FILE NUMBER: 3.5 GLOBAL ROOT: DIC(3.5, DATE CREATED: JUL 20, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA251-A ORIGINAL NUMBER: 251 ID: DIC(3.5, GENERAL DESCRIPTION: Clinical Monitoring System and Kernel have entered into an agreement for access to the following data: The "B" cross-reference of the device file. (To check that a free- text pointer value is still valid.) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM ISC: Hines NUMBER: 252 IA #: 252 FILE NUMBER: 69 GLOBAL ROOT: LRO(69, DATE CREATED: JUL 20, 1993 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA252-A ORIGINAL NUMBER: 252 ID: LRO(69, GENERAL DESCRIPTION: Cross References on file 69 - LAB ORDER ENTRY AN - DATE/TIME RESULTS AVAILABLE STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM ISC: Hines NUMBER: 253 IA #: 253 FILE NUMBER: 142 GLOBAL ROOT: GMT(142, DATE CREATED: JUL 26, 1993 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA253-A ORIGINAL NUMBER: 253 ID: GMT(142, GENERAL DESCRIPTION: Integrated Billing has permission from Health Summary to make the following calls: 1) Permission to do lookups on the HEALTH SUMMARY TYPE file (# 142) and to store the IEN in an Integrated Billing file. 2) If ENX^GMTSDVR does not exist (version 2.5 or latter not installed), permission to print Health Summaries by: a) Accessing the file HEALTH SUMMARY TYPE (# 142), fields NAME (# .01) and TITLE (# .02), to obtain the title to be used. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE NUMBER: 254 IA #: 254 FILE NUMBER: 52 GLOBAL ROOT: PSRX( DATE CREATED: JUL 26, 1993 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA254 ORIGINAL NUMBER: 254 ID: PSRX( GENERAL DESCRIPTION: Drug Accountability has permission from Outpatient Pharmacy for the following: To collect dispensing data, the Drug Accountability ^PSAOP* routines loop through the "AL" (original & refills), "AJ" (return to stock), "AM" & "AN" (partials), and "AR" (status) x-refs in the PRESCRIPTION (#52) file. A date/time is stored as a starting point for each drug. Using these x-refs, the 6th piece of ^PSRX(D0,0) is checked to see if the drug is stocked in a Drug Accountability location and the 9th piece of ^PSRX(D0,2) is checked for Outpatient site. Quantity for original prescriptions, the 7th piece of ^PSRX(D0,0) is used. For refills, the 4th piece of ^PSRX(D0,1,D1,0) is used. For partials, the 4th piece of ^PSRX(D0,P,D1,0) is used. GLOBAL MAP DATA DICTIONARY #52 -- PRESCRIPTION FILE STORED IN ^PSRX( (VERSION 6.0) -------------------------------------------------------------- CROSS REFERENCED BY: RETURNED TO STOCK(AJ),RETURNED TO STOCK(AJ1) RELEASED DATE/TIME(AL), RELEASED DATE/TIME(AL1), RELEASED DATE/TIME(AM), RETURNED TO STOCK(AN), ^PSRX(D0,0)= (#.01) RX # [1F] ^ (#6) DRUG [6P] ^ (#7) QTY [7N] ^PSRX(D0,1,0)=^52.1DA^^ (#52) REFILL ^PSRX(D0,1,D1,0)=^ (#1) QTY [4N] ^ (#14) RETURNED TO STOCK[16D] ==>^ (#17) RELEASED DATE/TIME [18D] ^PSRX(D0,2)=^(#20) DIVISION [9P] ^(#31) RELEASED DATE/TIME[13D] ==>^ (#32.1) RETURNED TO STOCK[15D] ^ ^PSRX(D0,P,0)=^52.2DA^^ (#60) PARTIAL DATE ^PSRX(D0,P,D1,0)=^(#.04) QTY [4N] ^(#5)RETURNED TO STOCK [16D] ==>^ (#8) RELEASED DATE/TIME [19D] ^ STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28390681 SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham NUMBER: 255 IA #: 255 GLOBAL ROOT: DD(301.5, DATE CREATED: JUL 28, 1993 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA255 ORIGINAL NUMBER: 255 ID: DD(301.5, GENERAL DESCRIPTION: IVM is granted permission from FM Integration to make the following calls: Permission to add cross-references to the PATIENT file. The cross- references have set and kill logic as follows: S IVMX=X,X="IVMPXFR" X ^%ZOSF("TEST") D:$T DPT^IVMPXFR S X=IVMX K IVMX The code in IVMPXFR looks as follows: DPT ; Update transmit status if patient file fields are updated ; N DFN S DFN=+DA I '$D(^DPT(DFN,0)) Q D IVM Q ; IVM ; check to see if patient needs to be retransmitted N DA,I,NODE,X Q:'$D(^IVM(301.5,"B",DFN)) F DA=0:0 S DA=$O(^IVM(301.5,"B",DFN,DA)) Q:'DA D .S X=$G(^IVM(301.5,DA,0)) .S $P(^IVM(301.5,DA,0),"^",3)=0 .F I=0:0 S I=$O(^DD(301.5,.03,1,I)) Q:'I I $G(^(I,0))'["TRIGGER" D ..S X=1 X ^DD(301.5,.03,1,I,2) ; kill xfr ..S X=0 X ^DD(301.5,.03,1,I,1) ; set xfr Q Permission is also given to execute the DD nodes. At this point, there is a single MUMPS cross-reference on the .03 field (TRANSMISSION STATUS) of the IVM PATIENT file (301.5). Its logic is: set I X=0 S ^IVM(301.5,"ATR",0,DA)="" kill I X=0 K ^IVM(301.5,"ATR",0,DA) The purpose is just to flag the record as needing to be transmitted and have the cross-reference only set for those that require transmission. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 256 IA #: 256 DATE CREATED: JUL 28, 1993 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA256 ORIGINAL NUMBER: 256 GENERAL DESCRIPTION: Health Summary has permission to add the "GMTS" application group to file 71, Radiology Procedures, in order to allow selection of specific procedures to be displayed by the Selected Radiology Component of Health Summary. Only verified results may be printed, although results with the report status Released/Unverified may be viewed through Health Summary. Unverified reports may not be viewed or printed through Health Summary, in compliance with the Radiology Package's specifications. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 257 IA #: 257 DATE CREATED: JUL 28, 1993 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBCNS NAME: DBIA257 ORIGINAL NUMBER: 257 ID: IBCNS GENERAL DESCRIPTION: IVM is given permission from IB to use the following code (routine IVMUFNC): N DGCRINDT,DGCRINS,IBINDT,IBINS,X S X="IBCNS" X ^%ZOSF("TEST") I $T S:$G(IVMDT) IBINDT=IVMDT D ^IBCNS G IN SQ ; for IB 2.0 and higher S X="DGCRNS" X ^%ZOSF("TEST") I $T S:$G(IVMDT) DGCRINDT=IVMDT D ^DGCRNS ; remove when IB 2.0 is required INSQ Q $S($D(IBINS):IBINS,$D(DGCRINS):DGCRINS,1:"") IVM needs this code to determine whether the patient has insurance. If he does not, he is automatically sent to IVM for verification. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 258 IA #: 258 DATE CREATED: JUL 28, 1993 CUSTODIAL PACKAGE: RECORD TRACKING CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA258 ORIGINAL NUMBER: 258 GENERAL DESCRIPTION: The Scheduling package of PIMS v5.3 is granted permission by the Record Tracking package for the following: 1. Permission to access following options: o RT MAS-CHART-PROFILE -- Profile of Charts o RT MAS-CHART-REQUEST -- Chart Request o RT MAS-FILL-NEXT -- Fill Next Clinic Request o RT MAS-RE-CHARGE -- Re-charge a Chart 2. The above options will be available under 'Appointment Management' option only if the MAS INTERFACE STATUS field of the OVERALL PARAMETERS entry in the RECORD TRACKING SYSTEM PARAMETERS file is set to 'UP'. The following check will be made: IF +$G(^DIC(195.4,1,"UP")... STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 259 IA #: 259 DATE CREATED: AUG 03, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCPUX1 NAME: DBIA259 ORIGINAL NUMBER: 259 ID: PRCPUX1 GENERAL DESCRIPTION: Drug Accountability, V2.0, has established agreement with IFCAP to make the following calls: IFCAP inventory provides a Primary Inventory Point with the SPECIAL INVENTORY POINT TYPE = "D" for Drug Accountability, the ability to update a Drug Accountability Location with all receiving activity. IFCAP has added two new fields to the INVENTORY ITEM multiple in the GENERIC INVENTORY file (#445), the DISPENSING UNIT and DISPENSING UNIT CONV FACTOR. Each item that a Primary Inventory Point receives, the IFCAP routines PRCPPOL1, PRCPWPL4, PRCPWPP3, and PRCPUUIW call EN^PSAGIP to update drug accountability. It is here that Drug Accountability is called (EN^PSAGIP) passing the Primary Inventory Point, the item, the quantity*dispensing unit conv factor, the PO#, the CP transaction #, the inventory transaction #, and the total price and in some cases the NDC. Drug Accountability adds each item received to a temporary global. After the receipt is processed, the IFCAP routines PRCPAWI1, PRCPPOL1, PRCPWPL5, and PRCPWPP3 call EX^PSAGIP to complete the drug accountability update. At this time a task is started, looping through the temporary global and either updating the Drug Accountability Location or building and sending a mailman message listing those items that could not be updated and why. In version 2.0 of Drug Accountability the cost center screen on the Primary Inventory pointer in the DRUG ACCOUNTABILITY STATS file (#58.8) has been replaced with the "D" for special inventory type. Also the IFCAP security variable, PRCPPRIV is used to enable this pointer. ^DD(58.8445,.01,0) = PRIMARY INVENTORY POINT(S)^M*P445'X ^PRCP(445,^0;1^S PRCPPRIV=1,DIC("S")="I $P(^(0),U,20)=""D""" D ^DIC K DIC S DIC=DIE,X=+Y K PRCPPRIV K:Y<0 X S:$D(X) DINUM=X Wherever available, calls to IFCAP extrinsics have replaced Drug Accountability version 1.0 look-ups to ^PRC globals. The IFCAP inventory routine PRCPUX1 is called extensively throughout the Drug Accountability package at the following line tags: UNITVAL(V1,V2,V3) ; unit per issue for values passed as follows ; v1=packaging multiple, v2=units da, ; v3=delimiter; UNITCODE(V1) ; get 2 character unit code from file 420.5 ; for entry v1; NSN(V1) ; return nsn for item v1; DESCR(V1,V2) ; description from inventory point or item ; master file for item v2 and inventory point ; v1; INVNAME(V1) ; inventory point name for inventory point v1; VENNAME(V1) ; return vendor name for da;global (445 or ; 440). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13824110 COMPONENT/ENTRY POINT: UNITVAL(V1,V2,V3) COMPONENT/ENTRY POINT: UNITCODE(V1) COMPONENT/ENTRY POINT: NSN(V1) COMPONENT/ENTRY POINT: DESCR(V1,V2) COMPONENT/ENTRY POINT: INVNAME(V1) COMPONENT/ENTRY POINT: VENNAME(V1) SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 260 IA #: 260 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: AUG 09, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA260 ORIGINAL NUMBER: 260 ID: DPT( GLOBAL REFERENCE: DPT('ARCDTH', GENERAL DESCRIPTION: REQUEST: "ARCDTH" CROSS-REFERENCE ON DATE OF DEATH FIELD IN PATIENT FILE FILE NUMBER: 2 FILE NAME: PATIENT FIELD NUMBER: .351 FIELD NAME: DATE OF DEATH CROSS REF NUM: 7 CROSS REF NAME: "ARCDTH" TYPE: MUMPS NOT USED FOR SORTING OR LOOKUP SET STATEMENT: S RCX=X,X="RCAMDTH" X ^%ZOSF("TEST") S X=RCX K RCX I D SET^RCAMDTH KILL STATEMENT: S RCX=X,X="RCAMDTH" X ^%ZOSF("TEST") S X=RCX K RCX I D ERR^RCAMDTH NO-DELETION MESSAGE: ACCOUNTS RECEIVABLE DEATH NOTIFICATION DESCRIPTION: This cross-reference is used to notify the Accounts Receivable package (v4 or higher) of a patient's death so that the patient's account may be reviewed for appropriate action. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 262 IA #: 262 DATE CREATED: AUG 09, 1993 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA262 ORIGINAL NUMBER: 262 GENERAL DESCRIPTION: DataBase Integration Agreement between IFCAP V4.0 package and FileMan V19.0 for the use of and the KILLing of a local FileMan variable in an Input Template. The IFCAP Input Template uses the FileMan local variable D1 in the input transform for field #40 in File #423, the CALM/LOG CODE SHEET file. The local variable D1 is used as a counter for the multiple field 423.05, subfield .01. IFCAP uses the counter within the Input Template to ensure that no more than 10 entries are made into the code sheet for this multiple. Prior to prompting the user for entries into this field, the FileMan variable D1 is KILLed. The reason or reasons for KILLing the FileMan local variable D1 and subsequently using D1 as a counter have been obscured in the history of IFCAP development. The variable D1 is the internal record number within the multiple; it is stored as piece 3 of the file or subfile header. It is not necessarily accurate as the count of entries within the multiple. For example, the user may make one or more deletions within the template, reducing the number of entries. The user could then add more entries to the multiple. This scenario could possibly increase the internal record number (D1) to a number greater than 9, when there may actually be fewer than 9 entries. Based on the input transform, the user would not be able to make the additional entries, although in reality, more entries should be allowed. In addition, piece 4 of the file or subfile header contains the number of records in the file and/or subfile. Once again, this number cannot be guaranteed as the accurate number of records in the file or subfile. The use of D1 is an existing convention that has been in place for several versions of IFCAP. We request the Integration Agreement with FileMan to continue this use for IFCAP V4.0. The Input Templates are used in the creation of CALM code sheets. Since FMS will be replacing CALM, the use of the FileMan local variable will be needed until all sites have converted from CALM to FMS. The next planned release of IFCAP V5.0 will replace this function. INTEGRATION POINT: 1. The IFCAP Input Template PRCFA TT982.00 FIRST EDIT FIELD: .1///CLM// THEN EDIT FIELD: S Y=4// THEN EDIT FIELD: STATION NUMBER// THEN EDIT FIELD: TRANSACTION TYPE// THEN EDIT FIELD: TRANSACTION DATE// THEN EDIT FIELD: REFERENCE NUMBER// THEN EDIT FIELD: YALD CODE// THEN EDIT FIELD: K D1// THEN EDIT FIELD: REC STA OR FCP// THEN EDIT FIELD: REC STA OR FCP// THEN EDIT FIELD: 1ST QTR AMOUNT// THEN EDIT FIELD: 2ND QTR AMOUNT// THEN EDIT FIELD: W !," "// THEN EDIT FIELD: 3RD QTR AMOUNT// THEN EDIT FIELD: I X="$" S Y=""// THEN EDIT FIELD: 4TH QTR AMOUNT// THEN EDIT FIELD: 998///$// 2. The Input Transform Using the FileMan Variable STANDARD DATA DICTIONARY #423.05 -- REC STA OR FCP SUB-FILE 05/20/93 PAGE 1 STORED IN ^PRCF(423, (811 ENTRIES) SITE: IFA UCI: DVA,IFA DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE ---------------------------------------------------------------- 423.05,.01 REC STA OR FCP 0;1 FREE TEXT (Multiply asked) INPUT TRANSFORM: K:$L(X)>3!($L(X)<3)!'(X?3N) X Q:'$D(X) I $D(D1),D1>9 W " ONLY 10 ENTRIES PER CODE SHEET ARE PERMITTED",*7 K X LAST EDITED: MAR 21, 1986 HELP-PROMPT: ANSWER MUST BE 3 CHARACTERS IN LENGTH DESCRIPTION: This is the 3 character receiving station or fund control point. NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER 3. FileMan Local Variable D1 When working below the main level of the file, DIE maintains the references to the file hierarchy being handled in the variables DA and Dn (D0, D1, etc) in which n varies according to the level of the file hierarchy. DA always contains the item number of the record being handled. Dn indicates the item numbers in the file hierarchy. D0 contains the main level record number; D1 contains the first sub-file level sub-record number and D2 contains the second sub-file level sub-record number. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring NUMBER: 263 IA #: 263 DATE CREATED: AUG 10, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFHLPID NAME: DBIA263-A ORIGINAL NUMBER: 263 ID: VAFHLPID STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34237578 KEYWORDS: HL7 KEYWORDS: PID COMPONENT/ENTRY POINT: $$EN(DFN,VAFSTR,VAFNUM,PTID) COMPONENT DESCRIPTION: Function call returns the standard HL7 PID segment for a given patient ** Warning ** This function makes external calls to VADPT. Non-namespaced variables may be altered. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to entry in PATIENT file (#2) VARIABLES: VAFSTR TYPE: Input VARIABLES DESCRIPTION: String of requested fields separated by commas (ex: 1,2,3) VARIABLES: VAFNUM TYPE: Input VARIABLES DESCRIPTION: Sequential number for SET ID (sequence 1). Default value is '1'. VARIABLES: PTID TYPE: Input VARIABLES DESCRIPTION: Flag denoting which Patient ID (sequence 3) to use 0 - Use DFN formatted as data type CK (default) 1 - Use ICN 2 - Use DFN formatted as data type CX 3 - Use SSN (with dashes) VARIABLES: VAFPID(1) TYPE: Output VARIABLES DESCRIPTION: If the returned string is longer than 245 characters, the remaining characters will be returned in VAFPID(1). VAFPID(1) will not be set if the returned string is less than 245 characters. VARIABLES: Assumed Variables TYPE: Input VARIABLES DESCRIPTION: Call assumes that all HL7 variables returned from INIT^HLTRANS are defined NUMBER: 264 IA #: 264 DATE CREATED: AUG 10, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA264 ORIGINAL NUMBER: 264 GENERAL DESCRIPTION: VA FileMan has permission to export the Package file and to update entries in the Package file for exporting and importing packages. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: VA FILEMAN ISC: Oakland NUMBER: 266 IA #: 266 FILE NUMBER: 409.61 GLOBAL ROOT: SD( DATE CREATED: AUG 25, 1993 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: LIST TEMPLATE FILE ORIGINAL NUMBER: 266 ID: SD( GLOBAL REFERENCE: SD(409.61, GENERAL DESCRIPTION: The List Template file 409.61 may be populated with entries that are namespaced (following the same principles as with the Option file). Refer to List Manager documentation for current export utilities. Entries should not be made to this file other than through VA FileMan and the export utilities. STATUS: Active DURATION: Till Otherwise Agreed NUMBER: 267 IA #: 267 DATE CREATED: AUG 25, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA267 ORIGINAL NUMBER: 267 GENERAL DESCRIPTION: The PDX team is granted permission to add the following protocols to the protocol file ^ORD(101. We also request permission to use all generic protocols as listed in the List Managers development guide. The protocol names are: 1 VAQ ADD PATIENT Add Patient 2 VAQ ADD/EDIT REQUEST Add/Edit Request 3 VAQ CHANGE PATIENT Change Patient 4 VAQ COPY REQUEST Copy Request 5 VAQ CREATE REATE REQUEST Create Request 6 VAQ DIS ALL SEGMENT Display all 7 VAQ DIS SELECTED SEG Display Selected 8 VAQ DIS1 (MENU) List Request Options 9 VAQ DISPLAY PDX Display PDX 10 VAQ DISPLAY SELECT Select Entry 11 VAQ DUPLICATE Select Entry 12 VAQ LOAD DATA Load Data (all) 13 VAQ LOAD EDIT Load/Edit 14 VAQ LOAD FIELD Load Field(s) 15 VAQ NEW PATIENT New Patient 16 VAQ PDX1 (MENU) CUSTOM ENTRIES FOR PDX1 17 VAQ PDX11 (MENU) MENU FOR DISPLAY SEGMENT 18 VAQ PDX12 (MENU) MENU OPTIONS FOR PDX DISPLAY 19 VAQ PDX2 (MENU) CUSTOM ENTRIES FOR PDX2 20 VAQ PDX3 (MENU) custom entries for PDX3 21 VAQ PDX4 (MENU) VAQ PDX4 MANUAANUAL PROCESS 22 VAQ PDX5 (MENU) VAQ LED STATUS MENU 23 VAQ PDX6 (MENU) VAQ LED DIFFERENCES MENU 24 VAQ PDX7 (MENU) VAQ LED ADD PT MENU 25 VAQ PDX8 (MENU) VAQ LED POSSIABLE MATCH MENU 26 VAQ PDX9 (MENU) OPTIONS MENU FOR PDX REQUEST 27 VAQ PROCESS MANUAL Procecess Manual 28 VAQ PROCESS REJECT Reject W/Comment 29 VAQ PROCESS RELEASE Release W/Comment 30 VAQ TRANSMIT REQUEST Transmit Request STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 268 IA #: 268 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: AUG 25, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA268-A ORIGINAL NUMBER: 268 ID: DPT( GLOBAL REFERENCE: SEE DESCRIPTION GENERAL DESCRIPTION: The PDX team has permission to access the MAS Duplicate Checker, DPTDUP. This routine will be used as a filter in adding new or selecting existing patients. The following fields are accessed by PDX for extract, display, edit and load. [ MINIMAL ] Following is a list of fields used when creating a new patient. Note: Temporary address is only filled in if active and dates valid. FILE NO. FIELD NO NONODE;PIECE DESCRIPT 2 .01 0;1 NAME .02 0;2 SEX .03 0;3 DATE OF BIRTH .05 0;5 MARITAL STATUS .08 0;8 RELIGIOUS PREFERENCE .09 0;9 SOCIAL SECURITY NUMBER .111 .11;1 STREET ADDRESS [LINE 1] .112 .11;2 STREET ADDRESS [LINE 2] .113 .11;3 STREET ADDRESS [LINE 3] .114 .11;4 CITY .115 .11;5 STATE .116 .11;6 ZIP CODE .117 .11;7 COUNTY .131 .13;1 PHONE NUMBER [RESIDENCE] .301 .3;1 SERVICE CONNECTED? .302 .3;2 SERVICE CONNECTED PERCENTAGE .323 .32;3 PERIOD OF SERVICE .361 .36;1 PRIMARY ELIGIBILITY CODE 391 TYPE;1 TYPE 1901 VET;1 VETERAN (Y/N)? .12105 .121;9 TEMPORARY ADDRESS ENTER/EDIT? .1211 .121;1 TEMPORARY STREET [LINE 1] .12111 .121;11 TEMPORARY ADDRESS COUNTY .12112 .121;12 TEMPORARY ZIP+4 .1212 .121;2 TEMPORARY STREET [LINE 2] .1213 .121;3 TEMPORARY STREET [LINE 3] .1214 .121;4 TEMPORARY CITY .1215 .121;5 TEMPORARY STATE .1216 .121;6 TEMPORARY ZIP CODE .1217 .121;7 TEMPORARY ADDRESS START DATE .1218 .121;8 TEMPORARY ADRESS END DATE .1219 .121;10 TEMPORARY PHONE NUMBER [ MAS ] Following is the list of the MAS fields PDX extracts. These fields are compared agianst the local database and the differences are displayed. The user is given the choice to update the local data with the PDX data. (Read/Write Access) FILE NO. FIELD NO NODE;PIECE DESCRIPT 2 .01 0;1 NAME .02 0;2 SEX .03 0;3 DATE OF BIRTH .05 0;5 MARITAL STATUS .07 0;7 OCCUPATION .08 0;8 RELIGIOUS PREFERENCE .09 0;9 SOCIAL SECURITY NUMBER .091 0;10 REMARKS .092 0;11 PLACE OF BIRTH [CITY] .093 0;12 PLACE OF BIRTH [STATE] .111 .11;1 STREET ADDRESS [LINE 1] .112 .11;2 STREET ADDRESS [LINE 2] .113 .11;3 STREET ADDRESS [LINE 3] .114 .11;4 CITY .115 .11;5 STATE .116 .11;6 ZIP CODE .117 .11;7 COUNTY .1211 .121;1 TEMPORARY STREET [LINE 1] .1212 .121;2 TEMPORARY STREET [LINE 2] .1213 .121;3 TEMPORARY STREET [LINE 3] .1217 .121;7 TEMPORARY ADDRESS START DATE .1218 .121;8 TEMPORARY ADDRESS END DATE .1219 .121;10 TEMPORARY PHONE NUMBER .131 .13;1 PHONE NUMBER [RESIDENCE] .132 .13;2 PHONE NUMBER [WORK] .152 .15;2 INELIGIBLE DATE .153 .15;3 MISSING PERSON DATE .1651 INE;1 INELIGIBLE TWX SOURCE .1653 INE;3 INELIGIBLE TWX CITY .1654 INE;4 INELIGIBLE TWX STATE .1656 INE;6 INELIGIBLE VARO DECISION .1657 INE;7 MISSING PERSON TWX SOURCE .1658 INE;8 MISSING PERSON TWX CICITY .1659 INE;9 MISSING PERSON TWX STATE .211 .21;1 K-NAME OF PRIMARY NOK .212 .21;2 K-RELATIONSHIP TO PATIENT .213 .21;3 K-STREET ADDRESS [LINE 1] .214 .21;4 K-STREET ADDRESS [LINE 2] .215 .21;5 K-STREET ADDRESS [LINE 3] .216 .21;6 K-CITY .217 .21;7 K-STATE .218 .21;8 K-ZIP CODE .219 .21;9 K-PHONE NUMBER .2191 .211;1 K2-NAME OF SECONDARY NOK .2192 .211;2 K2-RELATIONSHIP TO PATIENT .2193 .211;3 K2-STREET ADDRESS [LINE 1] .2194 .211;4 K2-STREET ADDRESS [LINE 2] .2195 .211;5 K2-STREET ADDRESS [LINE 3] .2196 .211;6 K2-CITY .2197 .211;7 K2-STATE .2198 .211;8 K2-ZIP CODE .2199 .211;9 K2-PHONE NUMBER .2401 .24;1 FATHER'S NAME .2402 .24;2 MOTHER'S NAME .2403 .24;3 MOTHER'S MAIDEN NAME .251 .25;1 SPOUSE'S EMPLOYER NAME .252 .25;2 SPOUSE'S EMP STREET [LINE 1] .253 .25;3 SPOUSE'S EMP STREET [LINE 2] .254 .25;4 SPOUSE'S EMP STREET [LINE 3] .255 .25;5 SPOUSE'S EMPLOYER'S CITY .256 .25;6 SPOUSE'S EMPLOYER'S STATE .257 .25;7 SPOUSE'S EMP ZIP CODE .258 .25;8 SPOUSE'S EMP PHONE NUMBER .301 .3;1 SERVICE CONNECTED? .302 .3;2 SERVICE CONNECTED PERCENTAGE .3025 .3;11 RECEIVING VA DISABILITY? .303 .3;3 AMOUNT OF VA DISABILITY .306 .3;6 MONETARY BEN. VERIFY DATE .307 .3;7 INELIGIBLE REASON .3111 .311;1 EMPLOYER NAME .31115 .311;15 EMPLOYMENT STATUS .3112 .311;2 GOVERNMENT AGENCY .3113 .311;3 EMPLOYER STREET [LINE 1] .3114 .311;4 EMPLOYER STREET [LINE 2] .3115 .311;5 EMPLOYER STREET [LINE 3] .3116 .311;6 EMPLOYER CITY .3117 .311;7 EMPLOYER STATE .3118 .311;8 EMPLOYER ZIP CODE .3119 .311;9 EMPLOYER PHONE NUMBER .312 .31;2 CLAIM FOLDER LOCATION .313 .31;3 CLAIM NUMBER .32101 .321;1 VIETNAM SERVICE INDICATED? .32102 .321;2 AGENT ORANGE EXPOS. INDICATED? .32103 .321;3 RADIATION EXPOSURE INDICATED? .32104 .321;4 VIETNAM FROM DATE .32105 .321;5 VIETNAM TO DATE .32107 .321;7 AGENT ORANGE REGISTRATION DATE .32109 .321;9 AGENT ORANGE EXAM DATE .3211 .321;10 AGENT ORANGE REGISTRATION # .32111 .321;11 RADIATION REGISTRATION DATE .3212 .321;12 RADIATION EXPOSURE METHOD .322 .32;2 SERVICE VERIFICATION DATE .323 .32;3 PERIOD OF SERVICE .324 .32;4 SERVICE DISCHARGE TYPE [LAST] .325 .32;5 SERVICE BRANCH [LAST] .326 .32;6 SERVICE ENTRY DATE [LAST] .327 .32;7 SERVICE SEPARATION DATE [LAST] .328 .32;8 SERVICE NUMBER [LAST] .329 .32;9 SERVICE DISCHARGE TYPE [NTL] .3291 .32;10 SERVICE BRANCH [NTL] .3292 .32;11 SERVICE ENTRY DATE [NTL] .3293 .32;12 SERVICE SEPARATION DATE [NTL] .3294 .32;13 SERVICE NUMBER [NTL] .3295 .32;14 SERVICE DISCHARGE TYPE [NNTL] .3296 .32;15 SERVICE BRANCH [NNTL] .3297 .32;16 SERVICE ENTRY DATE [NNTL] .3298 .32;17 SERVICE SEPARATION DATE [NNTL] .3299 .32;18 SERVICE NUMBER [NNTL] .331 .33;1 E-NAME .3311 .331;1 E2-NAME OF SECONDARY CONTACT .3312 .331;2 E2-RELATIONSHIP TO PATIENT .3313 .331;3 E2-STREET ADDRESS [LINE 1] .3314 .331;4 E2-STREET ADDRESS [LINE 2] .3315 .331;5 E2-STREET ADDRESS [LINE 3] .3316 .331;6 E2-CITY .3317 .331;7 E2-STATE .3318 .331;8 E2-ZIP CODE .3319 .331;9 E2-PHONE NUMBER .332 .33;2 E-RELATIONSHIP TO PATIENT .333 .33;3 E-STREET ADDRESS [LINE 1] .334 .33;4 E-STREET ADDRESS [LINE 2] .335 .33;5 E-STREET ADDRESS [LINE 3] .336 .33;6 E-CITY .337 .33;7 E-STATE .338 .33;8 E-ZIP CODE .339 .33;9 E-PHONE NUMBER .341 .34;1 D-NAME OF DESIGNEE .342 .34;2 D-RELATIONSHIP TO PATIENT .343 .34;3 D-STREET ADDRESS [LINE 1] .344 .34;4 D-STREET ADDRESS [LINE 2] .345 .34;5 D-STREET ADDRESS [LINE 3] .346 .34;6 D-CITY .347 .34;7 D-STATE .348 .34;8 D-ZIP CODE .349 .34;9 D-PHONE NUMBER .361 .36;1 PRIMARY ELIGIBILITY CODE .3611 .361;1 ELIGIBILITY STATUS .3612 .361;2 ELIGIBILITY STATUS DATE .3614 .361;4 ELIGIBILITY INTERIM RESPONSE .3615 .361;5 ELIGIBILITY VERIF. METHOD .3616 .361;6 ELIGIBILITY STATUS ENTERED BY .362 .36;2 DISABILITY RET. FROM MILITARY? .36205 .362;12 RECEIVING A&A BENEFITS? .3621 .362;1 AMOUNT OF AID & ATTENDANCE .36215 .362;13 RECEIVING HOUSEBOUND BENEFITS? .3622 .362;2 AMOUNT OF HOUSEBOUND .36225 .362;15 RECEIVING SOCIAL SECURITY? .3623 .362;3 AMOUNT OF SOCIAL SECURITY .36235 .362;14 RECEIVING A VA PENSION? .3624 .362;4 AMOUNT OF VA PENSION .3625 .362;5 AMOUNT OF MILITARY RETIREMENT .36255 .362;16 RECEIVING MILITARY RETIREMENT? .3626 .362;6 AMOUNT OF GI INSURANCE .36265 .362;17 GI INSURANCE POLICY? .3627 .362;7 AMOUNT OF SSI .36275 .362;19 RECEIVING SUP. SECURITY (SSI)? .3628 .362;8 AMOUNT OF OTHER RETIREMENT .36285 .362;18 TYPE OF OTHER RETIREMENT .3629 .362;9 AMOUNT OF OTHER INCOME .368 .36;8 SERVICE DENTAL INJURY? .369 .36;9 SERVICE TEETH EXTRACTED? .525 .52;5 POW STATUS INDICATED? .526 .52;6 POW CONFINEMENT LOCATION .527 .52;7 POW FROM DATE .528 .52;8 POW TO DATE .5291 .52;11 COMBAT SERVICE INDICATED? .5292 .52;12 COMBAT SERVICE LOCATION .5293 .52;13 COMBAT FROM DATE .5294 .52;14 COMBAT TO DATE 57.4 57;4 SPINAL CORD INJURY 391 TYPE;1 TYPE 1010.15 1010.15;5 RECEIVED VA CARE PREVIOUSLY? 1010.151 1010.15;1 MOST RECENT DATE OF CARE 1010.152 1010.15;2 MOST RECENT LOCATION OF CARE 1010.153 1010.15;3 2ND MOST RECENT DATE OF CARE .21011 .21;11 K-WORK PHONE NUMBER .211011 .211;11 K2-WORK PHONE NUMBER .381 .38;1 ELIGIBLE FOR MEDICAID? .3221 .322;1 LEBANON SERVICE INDICATED? .3222 .322;2 LEBANON FROM DATE .3223 .322;3 LEBANON TO DATE .3224 .322;4 GRENADA SERVICE INDICATED? .3225 .322;5 GRENADA FROM DATE .3226 .322;6 GRENADA TO DATE .3227 .322;7 PANAMA SERVICE INDICATED? .3228 .322;8 PANAMA FROM DATE .3229 .322;9 PANAMA TO DATE .32201 .322;10 PERSIAN GULF SERVICE? .322011 .322;11 PERSIAN GULF FROM DATE .322012 .322;12 PERSIAN GULF TO DATE .322013 .322;13 ENV CONTAM INDICATED? .322014 .322;14 REGISTRATION DATE .322015 .322;15 EXAM DATE .322016 .322;16 SOMALIA SERVICE INDICATED? .322017 .322;17 SOMALIA FROM DATE .322018 .322;18 SOMALIA TO DATE .304 .3;4 P&T .305 .3;5 UNEMPLOYABLE .3012 .3;12 SC AWARD DATE .293 .29;12 RATED INCOMPETENT? .292 .29;2 DATE RULED INCOMPETENT (CIVIL) .291 .29;1 DATE RULED INCOMPETENT (VA) .36205 .362;12 RECEIVING A&A BENEFITS? .36215 .362;13 RECEIVING HOUSEBOUND BENEFITS? .36235 .362;14 RECEIVING A VA PENSION? .3025 .3;11 RECEIVING VA DISABILITY? .36295 .36295;20 TOTAL ANNUAL VA CHECK AMOUNT .36265 .362;17 GI INSURANCE POLICY? .3626 .362;6 AMOUNT OF GI INSURANCE .34011 .34;11 D-WORK PHONE NUMBER .2514 .25;14 SPOUSE'S OCCUPATION .2515 .25;15 SPOUSE'S EMPLOYMENT STATUS 1010.154 1010.15;4 2ND MOST RECENT LOCATION 1901 VET;1 VETERAN (Y/N)? .33011 .33;11 E-WORK PHONE NUMBER .331011 .331;11 E2-WORK PHONE NUMBER .1112 .11;12 ZIP+4 .12105 .121;9 TEMPORARY ADDRESS ENTER/EDIT? .12111 .121;11 TEMPORARY ADDRESS COUNTY .12112 .121;12 TEMPORARY ZIP+4 .382 .38;2 DATE MEDICAID LAST ASKED FILE NO. FIELD NO NODE;PIECE DESCRIPT 2.04 .01 0;1 RATED DISABILITIES (VA) 2 0;2 DISABILITY % 3 0;3 SERVICE CONNECTED FILE NO. FIELD NO NODE;PIECE DESCRIPT 2.001 .01 0;1 ENROLLMENT CLINIC FILE NO. FIELD NO NODE;PIECE DESCRIPT 2.16 .01 0;1 MISSING OR INELIGIBLE FILE NO. FIELD NO NODE;PIECE DESCRIPT 2.01 .01 0;1 ALIAS 1 0;2 ALIAS SSN FILE NO. FIELD NO NODE;PIECE DESCRIPT 2.05 .01 0;1 SERVICE CONNECTED CONDITIONS .02 0;2 PERCENTAGE FILE NO. FIELD NO NODE;PIECE DESCRIPT 2.101 .01 0;1 LOG IN DATE/TIME 2 0;3 TYPE OF BENEFIT APPLIED FOR 3 0;4 FACILITY APPLYING TO 20 2;1 NEED RELATED TO OCCUPATION 23 2;4 NEED RELATED TO AN ACCIDENT [ ELIGIBILITY ] FILE NO. FIELD NO NODE;PIECE DESCRIPT 2.0361 .01 0;1 ELIGIBILITY [ DENTAL ] Extract the five most recent FILE NO. FIELD NO NODE;PIECE DESCRIPT 2.11 .01 0;1 DATE OF DENTAL TREATMENT 2 0;2 CONDITION 3 0;3 DATE CONDITION FIRST NOTICED [ APPOINTMENT ] Extract the five most recent FILE NO. FIELD NO NODE;PIECE DESCRIPT 2.98 .01 0;1 CLINIC 3 0;2 STATUS 9 0;7 PURPOSE OF VISIT 9.5 0;16 APPOINTMENT TYPE The PDX development team has permission to access ^DPT (directly) for the verification of a valid DFN. This is done extensively through out PDX. Other places ^DPT is accessed directly. a) $O thru eligibility multiple b) $O thru appointments multiple c) $O thru dental appointments multiple STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 269 IA #: 269 FILE NUMBER: 58.1 GLOBAL ROOT: PSI(58.1, DATE CREATED: AUG 26, 1993 CUSTODIAL PACKAGE: AUTO REPLENISHMENT/WARD STOCK CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA269 ORIGINAL NUMBER: 269 ID: PSI(58.1, GENERAL DESCRIPTION: Version 2.0 of Drug Accountability will require previous installation of Automatic Replenishment/Ward Stock version 2.3. The ^PSGWUAS routine contains a call to ^PSARWS. ^PSARWS will traverse the ^PSI(58.5,"AMIS") x-ref to update the AR/WS dispensing in Drug Accountability. Using the sixth subscript, a look-up is made to ^PSI(58.1,D0,"SITE") to determine the Inpatient Site. GLOBAL MAP DATA DICTIONARY #58.1 -- PHARMACY AOU STOCK FILE STORED IN ^PSI(58.1, (1 ENTRY) SITE: BIRMINGHAM ISC (#14) ------------------------------------------------------------ ^PSI(58.1,D0,SITE)= (#4) INPATIENT SITE [1P] ^ STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham NUMBER: 270 IA #: 270 FILE NUMBER: 52.6 GLOBAL ROOT: PS(52.6, DATE CREATED: AUG 26, 1993 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA270-A ORIGINAL NUMBER: 270 ID: PS(52.6, GENERAL DESCRIPTION: Drug Accountability will use the IV STATS (#50.8) file to update IV dispensing activity in a Drug Accountability Location. To correctly identify the DRUG (#50) file entry a look up is first made to the IV ADDITIVES (#52.6) and/or the IV SOLUTION (#52.7) files. Looping through ^PS(50.8,D0), all IV Rooms are checked. Looping through ^PS(50.8,D0,2,D1), dates are checked. Looping through ^PS(50.8,D0,2,D1,2,D2), drugs are checked with support from the "AC" x-ref. Looping through ^PS(50.8,D0,2,D1,2,D2,3,D3), ward is checked. It is here that, if a match occurs, $P($G(^PS(50.8,D0,2,D1,2,D2,3,D3,0)),U,2)-$P($G(^(0)),U,5) is used to update the balance in Drug Accountability. GLOBAL MAP DATA DICTIONARY #52.6 -- IV ADDITIVES FILE STORED IN ^PS(52.6, (1 ENTRY) SITE: BIRMINGHAM ISC ------------------------------------------------------------------------ CROSS REFERENCED BY: GENERIC DRUG(AC) ^PS(52.6,D0,0)= (#1) GENERIC DRUG [2P] STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham NUMBER: 271 IA #: 271 DATE CREATED: AUG 27, 1993 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA271-A ORIGINAL NUMBER: 271 GENERAL DESCRIPTION: The following routines and file entries will be exported by PDX with version 1.5: IBAPDX IBAPDX0 IBAPDX1 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 272 IA #: 272 FILE NUMBER: 394.61 GLOBAL ROOT: VAT(394.61, DATE CREATED: AUG 27, 1993 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA272-A ORIGINAL NUMBER: 272 ID: VAT(394.61, GENERAL DESCRIPTION: a) The following fields are referenced by the global directly, NOT by a fileman call. - PDX Transaction File (394.61) field # .03 Patient Name STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 274 IA #: 274 DATE CREATED: SEP 09, 1993 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSLTR NAME: DBIA274 ORIGINAL NUMBER: 274 ID: GMTSLTR GENERAL DESCRIPTION: Progress Note users have asked that notes printed for a given location begin the print with big letter identification of location. Since Health Summary has such lovely code for accomplishing this, and since PN already relies on HS routines (to display the text of patient warnings), PN is relying on HS code to print the big letters. Specifically, PN 2.5 is issuing a patch in which routine GMRPNP1 news GMTSLTR, and checks for the existence of routine GMTSLTR and calls it if exists, with GMTSLTR =a four letter string. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: GMTSLTR VARIABLES: GMTSLTR TYPE: Input SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 277 IA #: 277 FILE NUMBER: 13 GLOBAL ROOT: DIC(13, DATE CREATED: SEP 13, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA277-A ORIGINAL NUMBER: 277 ID: DIC(13, GENERAL DESCRIPTION: File #13 - Religion Field #.01 - Name - ^DIC(13,D0,0) piece 1 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas NUMBER: 278 IA #: 278 FILE NUMBER: 211.6 GLOBAL ROOT: NURSF(211.6, DATE CREATED: SEP 13, 1993 CUSTODIAL PACKAGE: NURSING SERVICE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA278 ORIGINAL NUMBER: 278 ID: NURSF(211.6, GENERAL DESCRIPTION: Mental Health V. 5.0 references the 'Nurs Tour of Duty' file: File #211.6 - Nurs Tour of Duty Field #.01 - Tour of Duty - ^NURSF(211.6,D0,0) piece 1 "B" X-Ref - Tour of Duty STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas NUMBER: 279 IA #: 279 DATE CREATED: SEP 13, 1993 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA279 ORIGINAL NUMBER: 279 GENERAL DESCRIPTION: Mental Health V. 5.0 no longer contains its own Progress Notes options, but references within two Mental Health options the newly released 'generic' Progress Notes Package. Verbal agreement with the Progress Notes developer has been made. Approval to include within the Mental Health menu options references to the Progress Notes package options have been agreed upon, these menu options replace the old MentalHealth Progress Notes option. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas NUMBER: 282 IA #: 282 DATE CREATED: SEP 20, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCS58 NAME: DBIA282-A ORIGINAL NUMBER: 282 ID: PRCS58 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN3 COMPONENT DESCRIPTION: Checks for Fund Control Point user authorization access. SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City NUMBER: 283 IA #: 283 DATE CREATED: OCT 05, 1993 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA283 ORIGINAL NUMBER: 283 GENERAL DESCRIPTION: The Electronic Signature encode created for IFCAP V4.0 for the Electronic Signature codes will work with AR V3.7 code sheet creator without having to modifiy any AR routines. The exception to the above is, the 'Forward IRS Offsets to Austin' option in the AR package. This option is used thru the 15th - 21st days of the month. Since this option generates code sheets in the background AR uses the PRCAOFF2 routine to create code sheets. This one routine is not compatible with IFCAP V4.0 AR plans to create a patch (not to be released till IFCAP V4.0 is released) to include the change. This patch was forwarded to the IFCAP V4.0 test sites and were considered as test sites for the AR patch. Since the sites have until the 21st of the month to send the IRS code sheets, this patch should not delay the implementation plans for IFCAP V4.0. The patch number is PRCA*3.7*17 IFCAP version 4 will export this routine in the IFCAP namespace as routine PRC4OFF2 and renamed back to PRCAOFF2 during the pre- initialization routine. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring NUMBER: 284 IA #: 284 FILE NUMBER: 340 GLOBAL ROOT: RCD(340, DATE CREATED: OCT 05, 1993 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA284 ORIGINAL NUMBER: 284 ID: RCD(340, GENERAL DESCRIPTION: Data Dictionary integration - IFCAP calls to AR IFCAP FILES FIELD - RELATION TO IFCAP CALM/LOG Code Sheet File 423 VA IDENT NO. Field 1005.17 (1005;17) - points to the AR Debtor File (#340) Procurement & Accounting Transaction File 442 Debtor Field 5.1 (1;16) - points to the AR Debtor File 340 Purchase Order Number Field .01 (0;1) - Executable Help checks for AR variable $D(PRCAREF) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring NUMBER: 286 IA #: 286 FILE NUMBER: 4.2 GLOBAL ROOT: DIC(4.2, DATE CREATED: OCT 05, 1993 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA286 ORIGINAL NUMBER: 286 ID: DIC(4.2, GENERAL DESCRIPTION: MailMan v 7.1 will invoke a QA conversion in MailMan's post init. It will manipulate the fields as follows: DBIA for MailMan with the QUALITY ASSURANCE SITE PARAMETERS file (#740). This DBIA is for the purpose of a post-init conversion of two free-text pointers to the DOMAIN file (#4.2). Read/write access to the following fields: 740,740.02 EWS DOMAIN (0;3) 740,740.04 NQADB DOMAIN (0;5) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: QUALITY ASSURANCE INTEGRATION ISC: Hines NUMBER: 287 IA #: 287 DATE CREATED: OCT 05, 1993 CUSTODIAL PACKAGE: FEE BASIS CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: FBAAUTL3 NAME: DBIA287 ORIGINAL NUMBER: 287 ID: FBAAUTL3 GENERAL DESCRIPTION: IFCAP needs to determine the appropriate header for FEE code sheets based on the version of Fee Basis. In the past the header was altered by a coordinated patch between the two packages. A new call has been added, in fee, which will eliminate the need for patches. IFCAP version 4 will be using the following function call to determine the codesheet header. If the routine FBAAUTL3 does not exist the header will be FEN. Otherwise the following call, being sent with version 3 of Fee Basis will return the appropriate header (FEE or FEN). $$HDR^FBAAUTL3() STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$HDR SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM SUBSCRIBING DETAILS: ADDED JUNE 2009 DATE/TIME EDITED: JUN 11, 2009@19:09 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: DEWAYNE,ROBERT WITH CONCURRENCE OF: BAUMANN,SCOTT NUMBER: 288 IA #: 288 DATE CREATED: OCT 05, 1993 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSLOAD NAME: DBIA288-A ORIGINAL NUMBER: 288 ID: GMTSLOAD GENERAL DESCRIPTION: Discharge Summary adds two new components to the HS Component file (#142.1), which present detailed and brief Discharge Summary information, while respecting Time and Occurrence limits. These are added by the Discharge Summary post-init as record #'s 57 and 58, and you can see them in either the SIUG or OE/RR accounts. The post-init also adds these components to the GMTS HS ADHOC OPTION Health Summary Type by calling the subroutine ENPOST^GMTSLOAD, and installs the routines GMRDHSDS as GMTSDS and GMRDHSDB as GMTSDSB (these are the driver routines for the respective components). STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: ENPOST SUBSCRIBING PACKAGE: DISCHARGE SUMMARY ISC: Salt Lake City NUMBER: 289 IA #: 289 DATE CREATED: OCT 12, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA289-A ORIGINAL NUMBER: 289 GENERAL DESCRIPTION: Manage Security Keys [GMRD KEY -------1 Allocation of Security Keys MANAGEMENT] [XUKEYALL] |---------------------------------2 De-allocation of Security Keys | [XUKEYDEALL] |---------------------------------3 Delegate keys [XQKEYDEL] |---------------------------------4 Remove delegated keys | [XQKEYRDEL] ------------------------------------------------------------------------ |---------------------------------5 List users holding a certain key [XQSHOKEY] Discharge Summary will export the above menu until a corresponding delegatable menu is provided in Kernel. Discharge Summary will indicate in its manuals (User, Technical, and Security), references to the appropriate Kernel chapters, and indicate that keys cannot be allocated (for end user use) until they are delegated to the person doing the allocating. And IRM must delegate individual keys before a delegated key can be delegated or allocated. DURATION: Till otherwise agreed--UNTIL KERNEL CHANGES MENU STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DISCHARGE SUMMARY ISC: Salt Lake City NUMBER: 290 IA #: 290 FILE NUMBER: 3.5 GLOBAL ROOT: %ZIS(1, DATE CREATED: OCT 12, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA290-A ORIGINAL NUMBER: 290 ID: %ZIS(1, GENERAL DESCRIPTION: ============================================================= Field 33, Unauthorized Claim Printer, in file 161.4 (Fee Basis Site Parameters file) references the device (%ZIS(1) and terminal type (%ZIS(2) files in the Input transform (extrinsic function), Executable help (routine call) and Screen. Fee routine is FBUCDD1. The Screen is: S DIC("S")= "S Z=$G(^%ZIS(1,+Y,""SUBTYPE"")),Z=$G(^%ZIS(2,Z,0)) I $E($P(Z,U),1)=""P""K Z" Global references in the routine calls are: %ZIS(1,"B" %ZIS(1,ien,0 (XHELP only) %ZIS(1,ien,"SUBTYPE" %ZIS(1,ien,1 (XHELP only) %ZIS(2,ien,0 where $E(0 node,1)="P" is checked STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: FEE BASIS ISC: Albany SUBSCRIBING PACKAGE: CMOP ISC: Birmingham SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM SUBSCRIBING DETAILS: ADDED 7/14/2009 DATE/TIME EDITED: JUL 14, 2009@18:04 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BAUMANN,SCOTT WITH CONCURRENCE OF: FORT,WALLY NUMBER: 294 IA #: 294 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: OCT 21, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA294 ORIGINAL NUMBER: 294 ID: DPT( GENERAL DESCRIPTION: A DBIA is established between the Hospital Based Home Care system and the Patient file (#2), for read access to the following. ***************************************************************** ********** FIELDS *********************************************** ***************************************************************** FIELD NODE PIECE TITLE ----------------------------------------------------------------- .01 0 1 Name .02 0 2 Sex .03 0 3 Date of Birth .05 0 5 Marital Status .06 0 6 Race .131 .13 1 Phone Number [Residence] .323 .32 3 Period of Service .361 .36 1 Primary Eligibility Code All seven fields in the .11 node (address information). **************************************************************** In addition reference is made to "^DPT(IEN,"S"," in the routine HBHCCAN. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HOSPITAL BASED HOME CARE ISC: Hines NUMBER: 295 IA #: 295 DATE CREATED: OCT 21, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA295 ORIGINAL NUMBER: 295 GENERAL DESCRIPTION: Integration Agreement Request between Toolkit (all versions) and Kernel (all versions). Toolkit and Kernel agree that both packages shall distribute all routines and data for M operating system interfaces (e.g. ZOSF, ZOSV*, ZTBK). These two packages also agree that both shall distribute the function library as designated by the routine namespace XLF. Toolkit and Kernel also agree that the menus, XUPROG, XTMENU, and XUCM MAIN, can be attached to the Kernel menu EVE. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 296 IA #: 296 FILE NUMBER: 50.8 GLOBAL ROOT: PS(50.8, DATE CREATED: OCT 21, 1993 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA296 ORIGINAL NUMBER: 296 ID: PS(50.8, GENERAL DESCRIPTION: Outpatient Pharmacy 6.0v will be printing a management report. In order to complete the report, we need to read ^PS(50.8 (IV STATS FILE). We are reporting the outpatient ward's number of dispensed units, average cost of the dispensed units, and the total costs of the dispensed units. To obtain this data, we need to read the 0 node in subfile 50.804, the Average Drug Cost Per Unit field (#4) on the 0 node piece 5 in subfile 50.805, the Dispensed Units (Ward) field (#2) on the 0 node piece 2 in the subfile 50.808, and the B cross-reference in subfile 50.808. GLOBAL MAP DATA DICTIONARY #50.8 -- IV STATS FILE STORED IN ^PS(50.8, SITE: BIRMINGHAM ISC -------------------------------------------------------------------------- ^PS(50.8 D0,2,D1,1,0)=^50.804P^^ (#1) WARD ^PS(50.8,D0,2,D1,2,D2,0)=^^^^ (#4) AVERAGE DRUG COST PER UNIT [5N] ^PS(50.8,D0,2,D1,2,D2,3,D3,0)=^ (#2) DISPENSED UNITS (WARD) [2N] ^ STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 297 IA #: 297 DATE CREATED: OCT 25, 1993 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA297-A ORIGINAL NUMBER: 297 GENERAL DESCRIPTION: The routine GMTSPDX will be exported by version 1.5 of PDX. Installation of GMTSPDX will only be done if the routine does not exist on the installing system. A partial data dictionary for the HEALTH SUMMARY PARAMETERS file (#142.99) will be exported by version 1.5 of PDX. The partial data dictionary will export the SPOOL DEVICE NAME field (#.04). The PDX application is grynted permission to include instructions for editing the GMTS IRM/ADPAC PARAMETER EDIT option. These instructions explain how to add the SPOOL DEVICE NAME field to the existing DR string contaioed in the DR {DIE} field (#51). The PDX application is granted pesmission to included instructions for editing the SPOOL DEVICE NAME field (#.04) of the HEALTH SUMMARY PARAMETERS file (#142.99) using the GMTS IRM/ADPAC PARAMETER EDIT option. These instructions explain how to enter the name of the spooling device used at the installing facility. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11803215 SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 298 IA #: 298 FILE NUMBER: 394.61 GLOBAL ROOT: VAT(394.61, DATE CREATED: OCT 25, 1993 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA298-A ORIGINAL NUMBER: 298 ID: VAT(394.61, GENERAL DESCRIPTION: The Health Summary application is granted read access to the following fields and, if listed, their associated cross references: File Field Node;Piece Description (Field name) X-Refs ------ ----- ---------- ------------------------------ ------ 394.61 .01 0;1 Transaction Number B .03 0;3 Patient Ptr STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 299 IA #: 299 GLOBAL ROOT: DD( DATE CREATED: OCT 25, 1993 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA299-A ORIGINAL NUMBER: 299 ID: DD( GENERAL DESCRIPTION: The PDX (V 1.5) application is granted read access to the DD and DIC globals to accomplish the following tasks: 1) See DBIA 821 2) Get node a field/multiple is stored on $P($P(^DD(FILE,FIELD,0),"^",4),";",1) 3) Get field name $P(^DD(FILE,FIELD,0),"^",1) 4) Determine if a field is date valued $P(^DD(FILE,FIELD,0),"^",2)["D" 5) Determine if a subfile is a word processing field $P(^DD(SUBFILE,.01,0),"^",2)["W" 6) Determine what file a field points to +$P($P(^DD(FILE,FIELD,0),"^",2),"P",2) 7) Determine if a file is a subfile $G(^DD(FILE,0,"UP"))'="" 8) Determine main file number for a subfile $G(^DD(SUBFILE,0,"UP")) 9) Determine main field number for a subfile $O(^DD(MAINFILE,"SB",SUBFILE,"")) 10) Determine subfile number +$P(^DD(FILE,FIELD,0),"^",2) 11) Check for valid file number $D(^DD(FILE)) 12) Check for valid field number $D(^DD(FILE,FIELD)) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 300 IA #: 300 DATE CREATED: OCT 25, 1993 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBRFN NAME: DBIA300 ORIGINAL NUMBER: 300 ID: IBRFN GENERAL DESCRIPTION: Routine call to SVDT^IBRFN returns service dates for a specific bill. Input Variable: BN, bill number (external form) VDT, name of array to hold outpatient visit dates, pass by value if needed. Output Variable: _________________________________________________________________ | Piece | Bill not found | Inpatient | Outpatient |-----------------------------------------------------------------| | 1 | 0 | 1 | 2 | 2 | -- | event Date | Event Date | 3 | -- | stmt from date | stmt from Date | 4 | -- | stmt to date | stmt to Date | 5 | -- | LOS (I) | LOS (I) | 6 | -- | # of visit date |# of visit date ----------------------------------------------------------------- all are internal form, any piece may be null if not defined for the bill array containing outpatient visit dates as subscripts/no data, if VDT passed by value. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: SVDT VARIABLES: BN TYPE: Input VARIABLES: VDT TYPE: Both SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 301 IA #: 301 DATE CREATED: OCT 25, 1993 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBRFN1 NAME: DBIA301 ORIGINAL NUMBER: 301 ID: IBRFN1 GENERAL DESCRIPTION: Routine Call to STMT^IBRFN1 to pass clinical data to AR for the patient statement. INPUT VARIABLE: TRAN, AR Transaction Number, the pointer file 433. OUTPUT VARIABLE: Returns ^TMP("IBRFN1",$J,n)=1^2^3^4^5^6^7^8, where _________________________________________________________________ | | Transaction Type |___________ |____________________________________________________ | Piece | Pharmacy |Outpatient | Inpatient |-----------------------------------------------------------------| | 1 | IB REF # | IB REF # | IB REF # | 2 | Rx # | Visit Date | Adm Date | 3 | Drug | -- | Bill From Date | 4 | Day Supply | -- | Bill To Date | 5 | Physician | -- | Disc Date | 6 | Quantity | -- | -- | 7 |Fill/Refill Date | -- | -- | 8 | Charge Amt | Charge Amt | Charge Amt ----------------------------------------------------------------- STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: STMT VARIABLES: TRAN TYPE: Input VARIABLES: AR TYPE: Input SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 302 IA #: 302 FILE NUMBER: 50 GLOBAL ROOT: PSDRUG( DATE CREATED: OCT 25, 1993 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA302-A ORIGINAL NUMBER: 302 ID: PSDRUG( GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of June 1, 2006. The PDX application is granted read access to the following fields and, if listed, their associated cross references: File Field Node;Piece Description (Field name) X-Refs ----- ----- ---------- ------------------------------ ------ 50 .01 0;1 GENERIC NAME B 20 ND;1 NATIONAL DRUG FILE ENTRY STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham EDITOR: BLOCKER,DAVE EDITOR: RUZBACKI,RON T NUMBER: 304 IA #: 304 DATE CREATED: OCT 27, 1993 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBRUTL NAME: DBIA304 ORIGINAL NUMBER: 304 ID: IBRUTL GENERAL DESCRIPTION: Call to routine IB^IBRUTL to find if there are any IB Actions on hold for this bill. Input Variables: IEN - internal entry number of bill (#399) internal entry number of bill (#430) RETN (OPT) - want array of IB Actions? 1=yes, 0=no if yes, returns IBA(num)=ibn Output Variable: 1=Yes, 0=N0 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: IB COMPONENT/ENTRY POINT: IB(IEN,RETN) SUBSCRIBING PACKAGE: AR (ACCOUNTS RECEIVABLE) ISC: Washington/Silver Spring NUMBER: 305 IA #: 305 FILE NUMBER: 4.281 GLOBAL ROOT: %ZISL(4.281, DATE CREATED: OCT 27, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA305 ORIGINAL NUMBER: 305 ID: %ZISL(4.281, GENERAL DESCRIPTION: MailMan should be allowed the use of the %ZISL file as follows: MailMan uses the 4.281 file whose global root is ^%ZISL(4.281, to facilitate InterUCI transfers. This file is part of the MailMan file set. MailMan may distribute and use this file. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MAILMAN ISC: Washington/Silver Spring NUMBER: 306 IA #: 306 DATE CREATED: OCT 27, 1993 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBRREL NAME: DBIA306 ORIGINAL NUMBER: 306 ID: IBRREL GENERAL DESCRIPTION: This option allows the agent cashier to release 'holds' on Means Test Bills. ENTRY ACTION: D ^IBRREL STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AR (ACCOUNTS RECEIVABLE) ISC: Washington/Silver Spring NUMBER: 307 IA #: 307 DATE CREATED: OCT 27, 1993 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBCF13 NAME: DBIA307 ORIGINAL NUMBER: 307 ID: IBCF13 GENERAL DESCRIPTION: Routine call to REPRNT^IBCF13 to print 2nd and 3rd notice UB-82's. INPUT VARIABLES: PRCASV("ARREC")=internal number of bill PRCASV("NOTICE")=number of notice OUTPUT VARIABLES: IBAR("ERR")=ERROR MESSAGE IBAR("OKAY")=1 normal finish, 0 not finished STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14033597 COMPONENT/ENTRY POINT: REPRNT VARIABLES: PRCASV() TYPE: Input VARIABLES: DGCRAR() TYPE: Output VARIABLES: IBAR() SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 308 IA #: 308 DATE CREATED: OCT 27, 1993 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBOAMS NAME: DBIA308 ORIGINAL NUMBER: 308 ID: IBOAMS GENERAL DESCRIPTION: This option prints totals of Revenue Code amounts by Rate Type to collect data for AMIS Segments 295 and 296. ENTRY ACTION: D ^IBOAMS K DTOUT STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14033597 SUBSCRIBING PACKAGE: AR (ACCOUNTS RECEIVABLE) ISC: Washington/Silver Spring NUMBER: 309 IA #: 309 DATE CREATED: OCT 27, 1993 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBCAMS NAME: DBIA309 ORIGINAL NUMBER: 309 ID: IBCAMS GENERAL DESCRIPTION: Routine call to IBCAMS to determine amis segment for reimbursable insurance bills. 249 = NSC - outpatient 292 = SC - inpatient 293 = SC - outpatient 297 = NSC - inpatient INPUT VARIABLE: X = internal entry number in #399. OUTPUT VARIABLE: Y= amis segment number or -1 if can't determine. (With the 1st release 18 months) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14033597 COMPONENT/ENTRY POINT: IBCAMS SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 310 IA #: 310 DATE CREATED: OCT 27, 1993 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBRFN NAME: DBIA310 ORIGINAL NUMBER: 310 ID: IBRFN GENERAL DESCRIPTION: Routine call to MESS^IBRFN to return an error message from File 350.8. INPUT VARIABLE: Y=error code - from File 350.8 (piece 3) OUTPUT: error message from piece 2 file 350.8. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: MESS(Y) SUBSCRIBING PACKAGE: AR (ACCOUNTS RECEIVABLE) ISC: Washington/Silver Spring NUMBER: 311 IA #: 311 FILE NUMBER: 45.7 GLOBAL ROOT: DIC(45.7, DATE CREATED: NOV 01, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA311-A ORIGINAL NUMBER: 311 ID: DIC(45.7, GENERAL DESCRIPTION: The Discharge Summary package has permission to access the Patient Information Management System package in the following ways: 1. The Discharge Summary contains a field which is a pointer to the Facility Treating Specialty File (#45.7), to keep track of the Treating Specialty from which a patient was discharged (for searches and sorts). This field value is set to the treating specialty returned by the IN5^VADPT call. 2. Discharge Summary allows the user to do a lookup to get all Discharge Summaries for a given treating specialty by signature status and dictation date. To do this query we need to identify the treating specialty, using a ^DIC call with DIC=45.7, DIC(0)="AEMQ", DIC("A")="TREATING SPECIALTY". STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DISCHARGE SUMMARY ISC: Salt Lake City NUMBER: 312 IA #: 312 FILE NUMBER: 45 GLOBAL ROOT: DGPT( DATE CREATED: NOV 01, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA312-A ORIGINAL NUMBER: 312 ID: DGPT( GENERAL DESCRIPTION: The Discharge Summary has permission to access the Patient Information Management System package in the following ways: 1. Upon record creation, Discharge Summary will perform a screened look-up on the PTF File to associate the new discharge summary with a valid admission. The screening logic will exclude Census PTF records. Discharge Summary also offers a site parameter to allow selection of Open PTF records only. To that end, the DIC("S") screen will make direct reference to the ^DGPT( global as follows: S DIC=45,DIC(0)=$S($D(GMRDBG):"MXZ",1:"IEZ") ; Exclude "Census" PTF records S DIC("S")="I +$P(^DGPT(+Y,0),U,11)=1" ; If an admission date has been specified, find the corresponding ; PTF record S:$D(GMRDADT) DIC("S")=DIC("S")_",($P($P(^DGPT(+Y,0),U,2),""."")=G MRDADT)" ; If site allows OPEN PTF selection only, then exclude closed or ; transmitted records S:+$P(GMRDPRM0,U,8) DIC("S")=DIC("S")_",'$P(^DGPT(+Y,0),U,6)" where GMRDBG is a boolean flag, indicating that the look-up is being called non-interactively, with a patient SSN and admission date, GMRDADT is the patient's admission date, as dictated by the physician, to be passed in by the non-interactive call, and GMRPRM0 is the zero-node of the GMRD PARAMETERS FILE (#128.99), the eighth piece of which specifies whether the site will allow selection of open PTF records only. Note that this screen will always refer to the 11th piece of the zero node of the PTF record to exclude non-PTF types, and will conditionally refer to the 2nd and 6th pieces, to match the admission date and exclude non-open records, as the site specifies. 2. The Discharge Summary database contains a field that is a pointer to the PTF file (#45), which is stored upon creation of the discharge summary record. 3. Discharge Summary calls the documented IN5^VADPT entry-point to get information on the patient. Using the PTF record number retained in our database, the input variable VAIP("E") is set to the value of field #2.1 (INTERNAL Admission #), which is obtained by a call to EN^DIQ1 after setting DIC=45, DR=2.1, and DA = PTF record number. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DISCHARGE SUMMARY ISC: Salt Lake City NUMBER: 313 IA #: 313 FILE NUMBER: 393 GLOBAL ROOT: VAS(393, DATE CREATED: NOV 01, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA313 ORIGINAL NUMBER: 313 ID: VAS(393, GENERAL DESCRIPTION: Discharge Summary has permission to reference the Incomplete Records File (#393), from the GMR REPORTS FILE (#128), IRT RECORD field (#.13). STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DISCHARGE SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 314 IA #: 314 GLOBAL ROOT: DD( DATE CREATED: NOV 01, 1993 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA314-A ORIGINAL NUMBER: 314 ID: DD( GENERAL DESCRIPTION: To support the table-driven upload of transcribed text to various DHCP files, the Discharge Summary application has permission to access the Data Dictionary and File of Files in the following ways: 1. In order to allow the site to specify the target file, fixed-field header elements, and word-processing field for each report type, Discharge Summary version 1 will make several references to either the File of Files or ^DD(. These are ONLY done in setting up a ^DIC call (to look-up a given field in the target file), or in screening logic (e.g., to exclude the programmer at the site from choosing a non-Word-Processing field in the target file as the destination for the body of a report). Needless to say, NO SETs or KILLs are ever executed on any of FileMan's supporting data structures (i.e., ^DD( or ^DIC(). All hard-coded references to ^DIC( or ^DD( are made from within the following code: GMRDUPAR ; SLC/JER - Upload Parameter Edit ;4/23/93 14:53 ;;1.0V2;Discharge Summary;;Sep 02, 1993 MAIN ; Controls branching N DIC,DA,DIE,DLAYGO,DR,GMRDPRM0,GMRDPRM1,GMRDPRM3,GMRDUSRC,GMRD1ST,X,Y D:'$D(GMRDPRM0) SETPARM^GMRDLIBE W !,"First edit Division-wide upload parameters:",! S (DIC,DLAYGO)=128.99,DIC(0)="AEMQL",DIC("A")="Select DIVISION: " D ^DIC K DLAYGO Q:+Y'>0 S DA=+Y S DIE=128.99,DR="[GMRD UPLOAD PARAMETER EDIT]" D ^DIE D SETPARM^GMRDLIBE W !!,"Now edit the REPORT TYPE file:",! F D Q:+$G(Y)'>0 . N GMRDREP,GMRDX . S DIC="^GMR(128.1,",DIC(0)="AEMQZ",DIC("A")="Select REPORT TYPE: " . I $D(^DISV(DUZ,DIC)),'$D(GMRD1ST) S DIC("B")=$G(^DISV(DUZ,DIC)), GMRD1ST=1 . D ^DIC K DIC Q:+Y'>0 S DA=+Y,GMRDREP=Y,GMRDREP(0)=Y(0) . S DIE=128.1,DR="[GMRD UPLOAD PARAMETER EDIT]" . D ^DIE S Y=1 . I $D(^GMR(128.1,+DA,"HEAD"))>9!($D(^GMR(128.1,+DA,"ITEM"))>9) D . . W !!,"The header for the ",$P(GMRDREP,U,2)," Report type is now defined as:" . . I $P(GMRDPRM0,U,16)="D" D DHDR^GMRDTHLP(.GMRDREP,GMRDPRM0,GMRDPRM1) . . I $P(GMRDPRM0,U,16)="C" D CHDR^GMRDTHLP(.GMRDREP,GMRDPRM0,GMRDPRM1) . . W ! Q TXTFLD(TFILE,GMRDFLT) ; Get Text Field # from ^DD(Target file #, N DIC,X,Y S DIC="^DD("_TFILE_",",DIC(0)="AEMQZ",DIC("A")="Select TARGET TEXT FIELD : " S DIC("S")="I +$$ISWP^GMRDUPAR(TFILE,+Y)" I $D(GMRDFLT) S DIC("B")=GMRDFLT D ^DIC G:+Y'>0 TXTFLDX S Y=+Y_";"_$P($P(Y(0),U,4),";") TXTFLDX Q Y ISWP(TFILE,TFLD) ; Is a given field a Word-processing type field N X,Y S Y=0 I +$P(^DD(TFILE,TFLD,0),U,2)>0 D . N SFILE S SFILE=+$P(^DD(TFILE,TFLD,0),U,2) . S Y=$S($P(^DD(SFILE,.01,0),U,2)="W":1,1:0) Q Y 2. The input transform for the TARGET FILE field (#.05) in the GMR REPORT TYPE file, which is a pointer to the File of Files, assures that only files which include the "GMRD" application group may be chosen for inclusion in the upload. This was done to assure that the site could not inadvertently choose an inappropriate target file (NOTE: the only file exported with this Application Group is the GMR REPORTS FILE (#128), where Discharge Summaries themselves are housed). The input transform looks like this: S DIC("S")="I $D(^DIC(+Y,""%"",""B"",""GMRD""))" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DISCHARGE SUMMARY ISC: Salt Lake City NUMBER: 315 IA #: 315 DATE CREATED: NOV 01, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCS58 NAME: DBIA315-A ORIGINAL NUMBER: 315 ID: PRCS58 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: Utility Call #1 entry point is EN1^PRCS58. Input variables: Required - None Optional - 'PRCS("X")' set to the full Obligation Number (3 character station number, a dash, 6 character obligation number. IE 503-C97211. - 'PRCS("A")' set to the prompt to be displayed to the user. (IE Select Obligation Number: ) - 'PRCS("TYPE")="FB"' Output variables: Y (Y=-1 no good) Piece Data ----------------------------------------------------------- 1 Internal Entry number of Obligation in IFCAP file 2 Obligation Number (full number, includes station number) 3 Control Point (3 numbers, space, description) 4 Appropriation symbol 5 Cost Center (number, space, description) 6 Sub-account 1 7 Sub-account 1 Amount 8 Sub-account 2 9 Sub-account 2 Amount Process: If PRCS("X") variable is defined, there will be NO user dialogue. The utility will use the variable as the lookup value (Obligation Number). If the variable is NOT defined, there will be user dialogue to determine the Obligation Number. VARIABLES: PRCS() TYPE: Input VARIABLES: Y TYPE: Output COMPONENT/ENTRY POINT: EN2 COMPONENT DESCRIPTION: Utility Call #2 entry point is EN2^PRCS58. Input variables: PRCS("TYPE")="FB" Required - 'X' will contain the following: Piece Data --------------------------------------------------------------- 1 Obligation Number (full) 2 Date/Time (Internal format) 3 Authorized Amount (If this is a commitment) 4 Payment Amount (If this is a Payment) 5 Reference Number (for Fee this will either be the batch number or the 7078 sequence number) 6 Comment (up to 78 characters) 7 Interface ID (free text) 8 Complete Payment Flag Output variables - 'Y' Process: If 'Y' is equal to 1, transaction was posted. If +Y=0 nothing was posted and 'Y' will contain the error message VARIABLES: PRCS() TYPE: Input VARIABLES: Y TYPE: Output COMPONENT/ENTRY POINT: EN3 COMPONENT DESCRIPTION: Input Variables: 'PRCS("X")' set equal to the full Obligation Number 'PRCS("TYPE")="FB"' Output Variables: 'Y' Process: If 'Y' is equal to 1, the 1358 is open and available for posting 0 If 'Y' is equal to -1, 1358 is not available for posting VARIABLES: PRCS() TYPE: Input VARIABLES: Y TYPE: Output SUBSCRIBING PACKAGE: FEE BASIS ISC: Albany SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM SUBSCRIBING DETAILS: ADDED 1/6/2009 DATE/TIME EDITED: JAN 06, 2009@13:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BAUMANN,SCOTT WITH CONCURRENCE OF: ANTHONY,MARY DATE/TIME EDITED: JAN 06, 2009@13:02 ACTION: USAGE CHOICE CHANGED AT THE REQUEST OF: BAUMANN,SCOTT WITH CONCURRENCE OF: ANTHONY,MARY NUMBER: 316 IA #: 316 GLOBAL ROOT: DD( DATE CREATED: NOV 01, 1993 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA316-A ORIGINAL NUMBER: 316 ID: DD( GLOBAL REFERENCE: DD(D0,.02,'V', GLOBAL REFERENCE: DD('KWIC') GENERAL DESCRIPTION: 1. When a new file is configured for use with MTLU, the variable-pointer 'ENTRY' field is automatically updated in the LOCAL KEYWORD and LOCAL SHORTCUT files to reflect the new file. This must be handled via DIC/DIE calls with DIC/DIE being set to ^DD(file,.02,"V", It is fully compatible with the interactive way of creating variable pointer type fields. 2. MTLU uses the string maintained in ^DD("KWIC"). There is currently no way of retrieving this information without directly referencing this node. As stated there is currently no way of extracting data stored in the node except by direct global hit. *Amendment 5/11/94* Toolkit DBIA 316 has been amended to include the $order of ^DD in line QU+5^XTLKEFOP. This code identifies the variable pointer prefix associated with the selected lookup file and was inadvertently ommitted. S XTLKY=Y,XTLKPF=+$O(^DD(8984.2,.02,"V","B",+Y,"")) G:'XTLKPF KL S XTLKPF=$P(^DD(8984.2,.02,"V",XTLKPF,0),U,4),XTLKUT=1 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 317 IA #: 317 DATE CREATED: NOV 02, 1993 CUSTODIAL PACKAGE: VETERANS ADMINISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VALM1 NAME: DBIA317-A ORIGINAL NUMBER: 317 ID: VALM1 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: PRTLQ COMPONENT DESCRIPTION: this was used so PDX output would format like printing from List manager COMPONENT/ENTRY POINT: PRTLS COMPONENT DESCRIPTION: same as PRTLQ COMPONENT/ENTRY POINT: SAVE COMPONENT DESCRIPTION: save variables for queue SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 318 IA #: 318 DATE CREATED: NOV 03, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA318 ORIGINAL NUMBER: 318 GENERAL DESCRIPTION: See DBIA #315. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City NUMBER: 319 IA #: 319 DATE CREATED: NOV 02, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCSP13 NAME: DBIA319 ORIGINAL NUMBER: 319 ID: PRCSP13 GENERAL DESCRIPTION: Version 7.0 of the Engineering Work Order Module will call IFCAP to display Control Point Activity information related to specific Engineering work orders. Routine ^ENWOD will call ^PRCSP13. Before calling this foreign routine, ^ENWOD will execute ^%ZOSF("TEST") to make sure that ^PRCSP13 exists. Upon entry into ^PRCSP13, local variable DA must contain the internal entry number of the Control Point Activity that is to be displayed. Local variable DA is not returned by ^PRCSP13. If local variables DIWL, DIWR, and/or DIWF are defined when the call to ^PRCSP13 is made, they will not be preserved. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: PRCSP13 VARIABLES: DA TYPE: Input VARIABLES: DIWL TYPE: Used VARIABLES: DIWR TYPE: Used VARIABLES: DIWF TYPE: Used SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring NUMBER: 322 IA #: 322 FILE NUMBER: 45.7 GLOBAL ROOT: DIC(45.7, DATE CREATED: DEC 07, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA322 ORIGINAL NUMBER: 322 ID: DIC(45.7, GENERAL DESCRIPTION: DSS is granted permission to make the following call: After callilng IN5^VADPT using the first ^ piece of VAIP(8) Read access to the following field. File Field Name Global Location ---- ----- ---- -------- 45.7 1 Specialty 0;2 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: EVENT CAPTURE ISC: Birmingham SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 323 IA #: 323 FILE NUMBER: 3.2 GLOBAL ROOT: %ZIS(2, DATE CREATED: DEC 16, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA323-A ORIGINAL NUMBER: 323 ID: %ZIS(2, GLOBAL REFERENCE: %ZIS(2,D0, FIELD NUMBER: 110 FIELD NAME: OPEN PRINTER PORT LOCATION: 10;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 111 FIELD NAME: CLOSE PRINTER PORT LOCATION: 11;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: To support bar code label printing and downloading/uploading, the Controlled Substances package has found it necessary to develop hardware specific parameters for the TERMINAL TYPE and DEVICE file. Centralized procurements of Hewlett Packard and Kyocera laser printers and Intermec trakkers have steered this package toward the use of these hardware types. As testing has proceeded, the need to accurately communicate complex strings for insertion into the TERMINAL TYPE file has proved difficult. An l misinterpreted as a 1, a 0 mininterpreted as a O, or an inadvertant space or lack thereof all can render a device inoperable. It is therefore agreed that IRM utility routines (PSDTER*) be exported which would allow ^DIC look-ups to the TERMINAL TYPE and DEVICE files, ^DIR verification of the selections, and ^DIE stuffs to the necessary fields identified as follows: GLOBAL MAP DATA DICTIONARY #3.2 -- TERMINAL TYPE FILE STORED IN ^%ZIS(2, (VERSION 7.1) -------------------------------------------------------------------------- ^%ZIS(2,D0,0)= (#.01) NAME [1F] ^ ^%ZIS(2,D0,1)= (#1) RIGHT MARGIN [1N] ^ (#2) FORM FEED [2F] ^ (#3) PAGE ==>LENGTH [3N] ^ ^%ZIS(2,D0,1)= (#4) BACK SPACE [4F] ^ ^%ZIS(2,D0,2)= (#6) OPEN EXECUTE [E1,245K] ^ ^%ZIS(2,D0,9)= (#99) DESCRIPTION [1F] ^ ^%ZIS(2,D0,10)= (#110) OPEN PRINTER PORT [E1,245K] ^ ^%ZIS(2,D0,11)= (#111) CLOSE PRINTER PORT [E1,245K] ^ ^%ZIS(2,D0,BAR0)= (#61) BAR CODE OFF [E1,245F] ^ ^%ZIS(2,D0,BAR1)= (#60) BAR CODE ON [E1,245F] ^ STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 324 IA #: 324 DATE CREATED: DEC 23, 1993 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBEFUNC NAME: DBIA324 ORIGINAL NUMBER: 324 ID: IBEFUNC GENERAL DESCRIPTION: IVM has permission to use the following routine call in the Integrated Billing (IB) package: Means Test Billing module: $$IGN^IBEFUNC(Appt Type, Visit Date) The call is being made to determine if a patient may be billed the Means Test Outpatient copayment, given the visit date and the appointment Type for the visit. Function Call: $$IGN^IBEFUNC(Appt Type, Visit Date) Input Parameters: Appt Type: Pointer to file #409.1, APPOINTMENT TYPE. For a specific patient appointment, this specifies the type of appointment (Regular, Research, Employee,.) Visit Date: Fileman date. For a specific patient appointment, this is the date of the appointment. Output from the call: 1 : On the specified date, for an appointment with the specified appointment type, Means Test billing should be IGNORED (so the Means Test copay should NOT be billed) 0 : On the specified date, for an appointment with the specified appointment type, Means Test billing should NOT be IGNORED (so the Means Test copay SHOULD be billed) STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$IGN(,) SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 325 IA #: 325 DATE CREATED: DEC 23, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VADPT2 NAME: DBIA325-A ORIGINAL NUMBER: 325 ID: VADPT2 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: ADM COMPONENT DESCRIPTION: Used to determine if a patient is an inpatient on a specified date. Input: variable VAINDT: The date being used to check if the patient was an inpatient. variable DFN: Pointer to the PATIENT in file #2. Output: variable VADMVT: if null (""), then the patient was not an inpatient on VAINDT. otherwise, VADMVT is positive and points to the patient's admission in the PATIENT MOVEMENT (#405) file, so the patient is an inpatient on VAINDT. VARIABLES: VAINDT TYPE: Input VARIABLES: DFN TYPE: Input VARIABLES: VADMVT TYPE: Output SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: VISIT TRACKING ISC: Albany SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING DETAILS: added 10/31/2011 SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES DBA Comments: 5/24/2012-VPR added as subscriber for patch VPR*1*1. 10/16/12-MM: Added Scheduling as a subscriber for SD*5.3*595. During development of SD*5.3*595, VMP team discovered a reference to VADPT2 that was not covered by an ICR. We also discovered the PIMS Technical Manual lists ADM~VADPT2 as a supported reference. 7/12/13-MM: Added Clinical Case Registries as a subscriber. Connie Ray was reviewing ICRs for CCR and noticed this reference was not covered by an ICR. No additional review was done. It is believed CCR has been using this API since 2006 and as noted in the DBA comments from 10/16/12, this API is listed as a supported reference in the PIMS Technical Manual. DATE/TIME EDITED: OCT 31, 2011@11:13 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: JUERGENSMEYER,BRIAN WITH CONCURRENCE OF: HARVEY,JULIE DATE/TIME EDITED: MAY 24, 2012@11:23 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: YORTY,BOB DATE/TIME EDITED: OCT 16, 2012@09:02 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CURTIS,RIC WITH CONCURRENCE OF: KOPECKY,STEVE DATE/TIME EDITED: JUL 12, 2013@13:48 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: RAY,CONNIE NUMBER: 326 IA #: 326 FILE NUMBER: 9000011 GLOBAL ROOT: AUPNPROB( DATE CREATED: JAN 11, 1994 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA326 ORIGINAL NUMBER: 326 ID: AUPNPROB( GENERAL DESCRIPTION: The following is the Problem File as it has been designed for the DHCP Problem List Application. STANDARD DATA DICTIONARY #9000011 -- PROBLEM FILE 2/9/94 STORED IN ^AUPNPROB( (VERSION 2.0V2) DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE ----------------------------------------------------------------- This file contains patient specific problems entered by the various providers of service. The PATIENT NAME field (.02) is a backward pointer to the IHS PATIENT file. This file contains one record for each problem for each patient, therefore, the KEY field (.01) is duplicated. As of March 17, 1986 the FACILITY must be entered prior to the NUMBER. If the NUMBER is entered without previously entering the FACILITY the "AA" index is created with no FACILITY pointer. DD ACCESS: @ DEL ACCESS: @ IDENTIFIED BY: PATIENT NAME (#.02),FACILITY (#.06),NMBR (#.07) POINTED TO BY: PROBLEM field (#.01) of the PROBLEM LIST AUDIT File (#125.8) CROSS REFERENCED BY: NMBR(AA), PATIENT NAME(AATOO), FACILITY(AATOO2), PATIENT NAME(AC), STATUS(ACTIVE), PATIENT NAME(ACTIVE1), FACILITY(AV1), DIAGNOSIS(AV9), DIAGNOSIS(B), PROBLEM(C) 9000011,.01 DIAGNOSIS 0;1 POINTER TO ICD DIAGNOSIS FILE (#80) (Required) INPUT TRANSFORM: S DIC("S")="I 1 Q:$G(DUZ(""AG""))=""V"" I $E(^(0))'="E", $P(^(0),U,9)="""" Q:$P(^(0),U,10)="""" I $P(^(0),U,10)=AUPNSEX" D ^DIC K DIC S DIC=DIE, X=+Y K:Y<0 X LAST EDITED: JAN 10, 1994 HELP-PROMPT: Enter the ICD Code for this problem. DESCRIPTION: This is the ICD coded diagnosis of the narrative entered describing this problem. TECHNICAL DESCR: The DHCP Problem List application derives its entries from a lookup into the Clinical Lexicon Utility rather than the ICD Diagnosis file. If the term selected from the CLU is not coded to ICD, then code 799.99 "Other Unknown or Unspecified Cause, NEC" will be used here in order to be able to create a new entry. This field may later be edited. SCREEN: S DIC("S")="I 1 Q:$G(DUZ(""AG""))=""V"" I $E(^(0))'="E", $P(^(0),U,9)="""" Q:$P(^(0),U,10)="""" I $P(^(0),U,10)=AUPNSEX" D ^DIC K DIC S DIC=DIE, X=+Y K:Y<0 X EXPLANATION: Cannot be an E code or an inactive code and must be appropriate for the sex of the Patient. CROSS-REFERENCE: 9000011^B 1)= S^AUPNPROB("B",$E(X,1,30),DA)="" 2)= K ^AUPNPROB("B",$E(X,1,30),DA) CROSS-REFERENCE: 9000011^AV9^MUMPS 1)= S:$D(APCDLOOK) DIC("DR")="" 2)= Q Controls the behaviour of the input templates used by IHS to populate and maintain this file. 9000011,.02 PATIENT NAME 0;2 POINTER TO PATIENT/IHS FILE (#9000001) (Required) LAST EDITED: SEP 9, 1993 HELP-PROMPT: Enter the name of the patient for whom this problem has been observed. DESCRIPTION: This is the patient for whom this problem has been observed and recorded. UNEDITABLE CROSS-REFERENCE: 9000011^AC 1)= S ^AUPNPROB("AC",$E(X,1,30),DA)="" 2)= K ^AUPNPROB("AC",$E(X,1,30),DA) CROSS-REFERENCE: 9000011^AATOO^MUMPS 1)= I $P(^AUPNPROB(DA,0),U,6)]"",$P(^(0),U,7)]" " S X1=$P($P(^(0),U,7),"."),X2=$P($P(^(0),U,7), ".",2),^AUPNPROB("AA",X,$P(^(0),U,6)," "_$E("00 0",1,4-$L(X1)-1)_X1_"."_X2_$E("00",1,3-$L(X2)-1 ),DA)="" K X1,X2 2)= I $P(^AUPNPROB(DA,0),U,6)]"",$P(^(0),U,7)]" " S X1=$P($P(^(0),U,7),"."),X2=$P($P(^(0),U,7), ".",2) K ^AUPNPROB("AA",X,$P(^(0),U,6)," "_$E(" 000",1,4-$L(X1)-1)_X1_"."_X2_$E("00",1,3-$L(X2) -1),DA),X1,X2 Allows problem retrieval by patient, facility, and problem number (Nmbr); the number is used as a string in " 000.00" format to assure a consistent ordering. CROSS-REFERENCE: 9000011^ACTIVE1^MUMPS 1)= S:$L($P(^AUPNPROB(DA,0),U,12)) ^AUPNPROB("ACTIVE",X,$P(^(0),U,12),DA)="" 2)= K:$L($P(^AUPNPROB(DA,0),U,12)) ^AUPNPROB("A CTIVE",X,$P(^(0),U,12),DA) Allows problem retrieval by patient and status, in order of entry. 9000011,.03 DATE LAST MODIFIED 0;3 DATE (Required) INPUT TRANSFORM: S %DT="EX" D ^%DT S X=Y K:DTX) X LAST EDITED: JUL 6, 1993 HELP-PROMPT: TYPE A DATE BETWEEN 1900 AND TODAY DESCRIPTION: This is the last date/time this problem was changed. SOURCE OF DATA: 018/PRCOND 9000011,.04 CLASS 0;4 SET 'P' FOR PERSONAL HISTORY; 'F' FOR FAMILY HISTORY; LAST EDITED: OCT 7, 1987 HELP-PROMPT: If this problem is historical, indicate if it is Personal or Family history. DESCRIPTION: This flag is used by the IHS Problem List to indicate if this problem is documented for historical purposes. TECHNICAL DESCR: VA sites using the DHCP Problem List application will not be prompted for this information. 9000011,.05 PROVIDER NARRATIVE 0;5 POINTER TO PROVIDER NARRATIVE FILE (#9999999.27) (Required) INPUT TRANSFORM: S DIC(0)=$S($D(APCDALVR):"LO",1:"EMQLO") D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X LAST EDITED: NOV 28, 1988 HELP-PROMPT: Enter a description of this patient's problem. DESCRIPTION: This contains the actual text used by the provider to describe this problem. SCREEN: S DIC(0)=$S($D(APCDALVR):"LO",1:"EMQLO") EXPLANATION: OLD LOOKUP 9000011,.06 FACILITY 0;6 POINTER TO LOCATION FILE (#9999999.06) (Required) LAST EDITED: JAN 10, 1994 HELP-PROMPT: Enter the location at which this problem was first observed and recorded. DESCRIPTION: This is the facility at which this problem was originally observed and documented. UNEDITABLE CROSS-REFERENCE: 9000011^AV1^MUMPS 1)= Q 2)= Q No longer in use. CROSS-REFERENCE: 9000011^AATOO2^MUMPS 1)= I $P(^AUPNPROB(DA,0),U,2)]"",$P(^(0),U,7)]" " S X1=$P($P(^(0),U,7),"."),X2=$P($P(^(0),U,7), ".",2),^AUPNPROB("AA",$P(^(0),U,2),X," "_$E("00 0",1,4-$L(X1)-1)_X1_"."_X2_$E("00",1,3-$L(X2)-1 ),DA)="" K X1,X2 2)= I $P(^AUPNPROB(DA,0),U,2)]"",$P(^(0),U,7)]" " S X1=$P($P(^(0),U,7),"."),X2=$P($P(^(0),U,7), ".",2) K ^AUPNPROB("AA",$P(^(0),U,2),X," "_$E(" 000",1,4-$L(X1)-1)_X1_"."_X2_$E("00",1,3-$L(X2) -1),DA),X1,X2 Allows problem retrieval by patient, facility, and problem number (Nmbr); the number is used as a string in " 000.00" format to assure a consistent ordering. 9000011,.07 NMBR 0;7 NUMBER (Required) INPUT TRANSFORM: K:+X'=X!(X>999.99)!(X<1)!(X?.E1"."3N.N) X Q:'$D (X) K:$D(^AUPNPROB("AA",$P(^AUPNPROB(DA,0),U,2 ),$P(^(0),U,6)," "_$E("000",1,4-$L($P(X,".",1)) -1)_$P(X,".",1)_"."_$P(X,".",2)_$E("00",1,3-$L( $P(X,".",2))-1))) X LAST EDITED: JUL 26, 1993 HELP-PROMPT: TYPE A NUMBER BETWEEN 1 AND 999.99 DESCRIPTION: This is a number which, together with the Patient (#.02) and Facility (#.06) fields, serves as a unique identifier for this problem. Up to 2 decimal places may be used to indicate that a problem is a result of, or related to, another problem. SOURCE OF DATA: 018/PRNUMB NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER CROSS-REFERENCE: 9000011^AA^MUMPS 1)= S ^AUPNPROB("AA",$P(^AUPNPROB(DA,0),U,2),$P (^(0),U,6)," "_$E("000",1,4-$L($P(X,".",1))-1)_ $P(X,".",1)_"."_$P(X,".",2)_$E("00",1,3-$L($P(X ,".",2))-1),DA)="" 2)= K ^AUPNPROB("AA",$P(^AUPNPROB(DA,0),U,2),$P (^(0),U,6)," "_$E("000",1,4-$L($P(X,".",1))-1)_ $P(X,".",1)_"."_$P(X,".",2)_$E("00",1,3-$L($P(X ,".",2))-1),DA) Allows problem retrieval by patient, facility, and problem number (Nmbr); the number is used as a string in " 000.00" format to assure a consistent ordering. 9000011,.08 DATE ENTERED 0;8 DATE (Required) INPUT TRANSFORM: S %DT="EX" D ^%DT S X=Y K:DTX) X LAST EDITED: MAR 7, 1988 HELP-PROMPT: TYPE A DATE BETWEEN 1900 AND TODAY DESCRIPTION: This is the date this problem was entered into this file. SOURCE OF DATA: 018/PREDAT UNEDITABLE 9000011,.12 STATUS 0;12 SET (Required) 'A' FOR ACTIVE; 'I' FOR INACTIVE; LAST EDITED: JUL 6, 1993 HELP-PROMPT: Enter the current status of this problem, active or inactive. DESCRIPTION: This is the current activity status of this problem, whether active or inactive; if more detail is needed, a notation may be filed with this problem. SOURCE OF DATA: 018/PRSTAT CROSS-REFERENCE: 9000011^ACTIVE^MUMPS 1)= S:$P(^AUPNPROB(DA,0),U,2) ^AUPNPROB("ACTIVE ",+$P(^(0),U,2),X,DA)="" 2)= K ^AUPNPROB("ACTIVE",+$P(^AUPNPROB(DA,0),U, 2),X,DA) Allows problem retrieval by patient and status, in order of entry. 9000011,.13 DATE OF ONSET 0;13 DATE INPUT TRANSFORM: S %DT="E" D ^%DT S X=Y K:DTX) X LAST EDITED: JUN 13, 1993 HELP-PROMPT: TYPE A DATE BETWEEN 1880 AND TODAY DESCRIPTION: This is the approximate date this problem appeared, as precisely as known. 9000011,1.01 PROBLEM 1;1 POINTER TO EXPRESSIONS FILE (#757.01) LAST EDITED: JUL 28, 1993 HELP-PROMPT: Enter the problem observed for this patient. DESCRIPTION: This field contains the standardized text stored in the Clinical Lexicon for this problem. CROSS-REFERENCE: 9000011^C 1)= S ^AUPNPROB("C",$E(X,1,30),DA)="" 2)= K ^AUPNPROB("C",$E(X,1,30),DA) 9000011,1.02 CONDITION 1;2 SET 'T' FOR TRANSCRIBED; 'P' FOR PERMANENT; 'H' FOR HIDDEN; LAST EDITED: JUL 26, 1993 DESCRIPTION: This reflects the current condition of this entry, whether transcribed by a clerk from the paper chart, entered or verified by a provider, or marked as removed from the patient's list. TECHNICAL DESCR: This flag is used internally by the DHCP Problem List; entries having an H in this field have been "deleted" and are maintained for historical use but are generally ignored. If the parameter "Verify Transcribed Entries" is turned on in File #125.99, entries made by a clerk will have a T here, and a flag will appear on the clinician's display of the list. P entries have been entered or verified by a provider. 9000011,1.03 ENTERED BY 1;3 POINTER TO NEW PERSON FILE (#200) LAST EDITED: JUL 26, 1993 HELP-PROMPT: Enter the name of the current user. DESCRIPTION: This is the user who actually entered this problem into this file. 9000011,1.04 RECORDING PROVIDER 1;4 POINTER TO NEW PERSON FILE (#200) LAST EDITED: JUL 26, 1993 HELP-PROMPT: Enter the name of the provider responsible for the recording of this data. DESCRIPTION: This is the provider who either directly entered this problem into the file or requested it be entered, and is initially responsible for this problem's inclusion on the problem list. 9000011,1.05 RESPONSIBLE PROVIDER 1;5 POINTER TO NEW PERSON FILE (#200) LAST EDITED: JUL 26, 1993 HELP-PROMPT: Enter the name of the local provider treating this problem. DESCRIPTION: This is the provider currently responsible for treating this problem. 9000011,1.06 SERVICE 1;6 POINTER TO SERVICE/SECTION FILE (#49) LAST EDITED: JUL 26, 1993 HELP-PROMPT: Enter the service to be associated with this problem. DESCRIPTION: This is the service primarily involved in the treatment of this problem; the DHCP Problem List defaults this field to the service defined in File #200 for the Recording Provider of this problem, upon entry of the problem. It may later be used to categorize problems for screening and sorting. 9000011,1.07 DATE RESOLVED 1;7 DATE INPUT TRANSFORM: S %DT="E" D ^%DT S X=Y K:Y<1 X LAST EDITED: JUL 26, 1993 HELP-PROMPT: Enter the date this problem became resolved or inactive, as precisely as known. DESCRIPTION: This is the date this problem was resolved or inactivated, as precisely as known. 9000011,1.08 CLINIC 1;8 POINTER TO HOSPITAL LOCATION FILE (#44) INPUT TRANSFORM: I $P(^(0),U,3)="C" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X LAST EDITED: DEC 23, 1993 HELP-PROMPT: Enter the clinic in which the patient is being seen for this problem. DESCRIPTION: This is the clinic in which this patient is being seen for this problem. The problem list may be screened based on this value, to change one's view of the list. SCREEN: I $P(^(0),U,3)="C" EXPLANATION: Only clinics are allowed here. 9000011,1.09 DATE RECORDED 1;9 DATE INPUT TRANSFORM: S %DT="E" D ^%DT S X=Y K:DTX) X LAST EDITED: JAN 11, 1994 HELP-PROMPT: TYPE A DATE BETWEEN 1900 AND TODAY DESCRIPTION: This is the date this problem was originally recorded, either online or in the paper chart; it may be the same as, or earlier than, the Date Entered. 9000011,1.1 SERVICE CONNECTED 1;10 SET '1' FOR YES; '0' FOR NO; LAST EDITED: JUL 26, 1993 HELP-PROMPT: If this problem is service connected, enter YES here. DESCRIPTION: If the patient has service connection on file in the DHCP Patient file #2, this problem specifically may be flagged as being service connected. TECHNICAL DESCR: This data will be prompted for in the DHCP Problem List only if the patient is indicated for service connection. Non-VA sites will not be prompted for this information. 9000011,1.11 AGENT ORANGE EXPOSURE 1;11 SET '1' FOR YES; '0' FOR NO; LAST EDITED: JUL 26, 1993 HELP-PROMPT: Enter YES if this problem is related to exposure to Agent Orange. DESCRIPTION: If this problem is related to a patient's exposure to Agent Orange, it may be flagged here. TECHNICAL DESCR: This data will be prompted for in the DHCP Problem List only if a patient has Agent Orange exposure indicated. Non-VA sites will not be prompted for this information. 9000011,1.12 IONIZING RADIATION EXPOSURE 1;12 SET '1' FOR YES; '0' FOR NO; LAST EDITED: JUL 26, 1993 HELP-PROMPT: Enter YES if this problem is related to exposure to ionizing radiation. DESCRIPTION: If this problem is related to a patient's exposure to ionizing radiation, it may be flagged here. TECHNICAL DESCR: This data will be prompted for in the DHCP Problem List only if the patient has ionizing radiation exposure indicated. Non-VA sites will not be prompted for this information. 9000011,1.13 PERSIAN GULF EXPOSURE 1;13 SET '1' FOR YES; '0' FOR NO; LAST EDITED: JUL 26, 1993 HELP-PROMPT: Enter YES if this problem is related to a Persian Gulf exposure. DESCRIPTION: If this problem is related to a patient's service in the Persian Gulf, it may be flagged here. TECHNICAL DESCR: This data will be prompted for only if a patient has Persian Gulf service indicated. Non-VA sites will not be prompted for this information. 9000011,1.14 PRIORITY 1;14 SET 'A' FOR ACUTE; 'C' FOR CHRONIC; LAST EDITED: FEB 1, 1994 HELP-PROMPT: You may further refine the status of this problem by assigning it a priority; acute problems will be flagged on the list display. DESCRIPTION: This is a flag to indicate how critical this problem is for this patient; problems marked as Acute will be flagged on the Problem List display. 9000011,1101 NOTE FACILITY 11;0 POINTER Multiple #9000011.11 (Add New Entry without Asking) DESCRIPTION: This is the location at which the notes in this multiple originated. 9000011.11,.01 NOTE FACILITY 0;1 POINTER TO LOCATION FILE (#9999999.06) (Multiply asked) LAST EDITED: SEP 9, 1993 HELP-PROMPT: Enter the location at which these notes originated. DESCRIPTION: This is the location at which the notes in this multiple originated. CROSS-REFERENCE: 9000011.11^B 1)= S ^AUPNPROB(DA(1),11,"B",$E(X,1,30),DA)=" " 2)= K ^AUPNPROB(DA(1),11,"B",$E(X,1,30),DA) 9000011.11,1101 NOTE 11;0 Multiple #9000011.1111 (Add New Entry without Asking) DESCRIPTION: Each entry in this multiple is a notation appended to a problem for further clarification or information. Data includes a note number and status, the date the note was added, the provider who added it, and the actual text of the note. IDENTIFIED BY: NOTE NARRATIVE(#.03), 9000011.1111,.01 NOTE NMBR 0;1 NUMBER (Required) INPUT TRANSFORM: K:+X'=X!(X>999)!(X<1)!(X?.E1"."1N.N) X LAST EDITED: JAN 25, 1994 HELP-PROMPT: Type a Number between 1 and 999, 0 Decimal Digits DESCRIPTION: This is the unique note identifier. CROSS-REFERENCE: 9000011.1111^B 1)= S ^AUPNPROB(DA(2),11,DA(1),11,"B",$E(X, 1,30),DA)="" 2)= K ^AUPNPROB(DA(2),11,DA(1),11,"B",$E(X, 1,30),DA) CROSS-REFERENCE: 9000011.1111^AV9^MUMPS 1)=S:$D(APCDLOOK) DIC("DR")="" 2)= Q Controls the behaviour of the input templates used by IHS to populate and maintain this file. 9000011.1111,.03 NOTE NARRATIVE 0;3 FREE TEXT (Required) INPUT TRANSFORM: K:$L(X)>60!($L(X)<3) X LAST EDITED: JUL 26, 1993 HELP-PROMPT: Answer must be 3-60 characters in length. DESCRIPTION: Additional comments may be entered here to further describe this problem. 9000011.1111,.04 STATUS 0;4 SET (Required) 'A' FOR ACTIVE; LAST EDITED: MAY 1, 1990 HELP-PROMPT: If this note is currently ACTIVE, indicate it here. DESCRIPTION: This flag indicates if this note is currently active. 9000011.1111,.05 DATE NOTE ADDED 0;5 DATE INPUT TRANSFORM: S %DT="EX" D ^%DT S X=Y K:DTX) X LAST EDITED: JUL 26, 1993 HELP-PROMPT: TYPE A DATE BETWEEN 1880 AND TODAY DESCRIPTION: This is the date this note was entered into this file. 9000011.1111,.06 AUTHOR 0;6 POINTER TO NEW PERSON FILE (#200) LAST EDITED: MAR 30, 1993 HELP-PROMPT: Enter the name of the provider who authored the text of this note. DESCRIPTION: This is the provider who authored the text of this note. FILES POINTED TO FIELDS EXPRESSIONS (#757.01) PROBLEM (#1.01) HOSPITAL LOCATION (#44) CLINIC (#1.08) ICD DIAGNOSIS (#80) DIAGNOSIS (#.01) LOCATION (#9999999.06) FACILITY (#.06) NOTE FACILITY:NOTE FACILITY (#.01) NEW PERSON (#200) ENTERED BY (#1.03) RECORDING PROVIDER (#1.04) RESPONSIBLE PROVIDER (#1.05) NOTE:AUTHOR (#.06) PATIENT/IHS (#9000001) PATIENT NAME (#.02) PROVIDER NARRATIVE (#9999999.27) PROVIDER NARRATIVE (#.05) SERVICE/SECTION (#49) SERVICE (#1.06) INPUT TEMPLATE(S): APCD FUD PROB OCT 23, 1987 USER #0 PCC Data Entry - Used to edit uncoded ICD diagnoses in the Problem file. PRINT TEMPLATE(S): SORT TEMPLATE(S): STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City NUMBER: 327 IA #: 327 FILE NUMBER: .401 GLOBAL ROOT: DIBT( DATE CREATED: JAN 11, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA327 ORIGINAL NUMBER: 327 ID: DIBT( GENERAL DESCRIPTION: Laboratory V5.2 (only V5.2) is granted the following exemption: The laboratory is supplying a pre release 5.2 patch. The patch will allow the site to mimic the conversion process required for V5.2 install. As a part of the process a FileMan sort template is created of all providers the software was unable to repoint to VA(200. The creation of the sort template is done with a DIC call and a DR string. We are not aware of a method to load the actual data. Therefore, this function is hard coded. The exemption is only required for the one time conversion process. Listed below is the actual code involved. Please advise of any suggestion you feel will be of benefit. EXCEPT(LRFILE,LRD0) ;- LOGS EXCEPTIONS FROM THE CONVERSIONS OF DATA FROM 6 A ND 16 ; exceptions are put into a SORT template so the the site can ; then use fileman enter edit to correct problems found. ; N DIC,LRSORT,X,Y I '$D(^DIBT("B",LRFILE_"-EXCEPTIONS")) D ADD I '$D(LRSORT) S LRSORT=$O(^DIBT("B",LRFILE_"-EXCEPTIONS",0)) S ^DIBT(LRSORT,1,LRD0)="" Q ; ADD ; add a new sort template to be used for exception logging and editing N X,Y S DIC="^DIBT(",DIC(0)="L",DIC("DR")="2///^S X=""T"";4///^S X=$P(LR FILE," "-"",2);5///^S X=0;" S X=LRFILE_"-EXCEPTIONS" D FILE^DICN S LRSORT=+Y Q STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 328 IA #: 328 DATE CREATED: JAN 11, 1994 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOCOPAY NAME: DBIA328 ORIGINAL NUMBER: 328 ID: PSOCOPAY GENERAL DESCRIPTION: Routine call to POT^PSOCOPAY to pass the DFN, the internal entry number for the patient and returns a number for 30 days Rx supplies. Input Variable: DFN-the patient's internal entry number Output Variable: X-a number, of 30 day supplies that a patient has for potential bills. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: POT VARIABLES: DFN TYPE: Input VARIABLES: X TYPE: Output SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 329 IA #: 329 DATE CREATED: JAN 12, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIP NAME: DBIA329-A ORIGINAL NUMBER: 329 ID: DIP STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: PRNT+1^ESPFM S L=1 G EN1^DIP SUBSCRIBING PACKAGE: POLICE & SECURITY ISC: Dallas NUMBER: 330 IA #: 330 DATE CREATED: JAN 12, 1994 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOHCSUM NAME: PSOHCSUM ORIGINAL NUMBER: 330 ID: PSOHCSUM CREATOR: MONTALI,MICHAEL GENERAL DESCRIPTION: Provides a list of active Rxs (Active/Non-Verified/Hold/Suspend/Provider Hold) and Non-VA MEDS (Not dispensed by VA) sorted in the reverse fill date order for a given DFN. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18469951 COMPONENT/ENTRY POINT: PSOHCSUM VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IFN of patient in Patient file. VARIABLES: PSOBEGIN TYPE: Both VARIABLES DESCRIPTION: The date/time to begin the search for prescriptions. VARIABLES: ~TMP("PSOO",$J, TYPE: Output VARIABLES DESCRIPTION: ^TMP("PSOO",$J) should be killed before and after data is extracted for use. ^TMP("PSOO",$J,IFD,0)=ID^FD^DR^PR^ST^RX^QT^RF^IF^CF^EX^ON^R ISSUE DATE^LAST FILL DATE^DRUG^PROVIDER^STATUS^RX#^QTY^#REFILLS^IFN^COST /FILL^QTY^#REFILLS^IFN^COST/FILL^EXP/CANC DATE^CPRS ORDER#^R where: IFD = Inverse last fill date of Rx. ID = Issue date of Rx. FD = Last fill date of Rx. DR = Drug in Rx. This variable has format A;B where A is the internal pointer and B is external printable form. PR = Provider. This variable has format A;B where A is the internal pointer and B is external printable form. ST = Status of Rx. This variable has format A;B where A is the internal representation and B is external printable form. RX = Rx number. QT = Quantity of DRG in Rx. RF = Number of refills remaining. IF = IFN.of Rx in Prescription (52) file. CF = Cost/Fill. EX = Expire/Cancel date of Rx. ON = Placer order # (CPRS) R = Letter "R" only when the original fill is returned to stock. NON-VA Meds: added with PSO*7*132 ^TMP("PSOO",$J,"NVA",n,0)=orderable item_" "_dose form^status (active or discontinued)^start date(fm format)^cprs order # (ptr to 100)^date/time documented (fm format)^documented by (ptr to 200_";"_.01)^dc date/time(fm format) ^TMP("PSOO",$J,"NVA",n,1,0)=dosage^med route^schedule^drug (file #50_";"_.01)^clinic (file #44_";"_.01) ^TMP("PSOO",$J,"NVA",n,"DSC",nn,0)=statement/explanation ^TMP("PSOO",$J,"NVA",n,"OCK",nn,0)=order checks^overriding provider (ptr to 200_";"_.01) ^TMP("PSOO",$J,"NVA",n,"OCK",nn,"OVR",nnn,0)=override reason VARIABLES: ~TMP("PSOO",$J,IFD,n,0) TYPE: Output VARIABLES DESCRIPTION: IFD = Inverse last fill date of Rx. SIG = Medication instruction for this Rx. The value of ^TMP("PSOO",$J,IFD,n,0) SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING ISC: Hines SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: MYHEALTHEVET SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: HEALTH SUMMARY SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING DETAILS: ADDED 8/26/2010 DBA Comments: JSHarvey/ 20070314 deactivated for edits DATE ACTIVATED: APR 02, 2007 DATE/TIME EDITED: MAR 14, 2007@17:02 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: ANWER,MOHAMED WITH CONCURRENCE OF: HARVEY,JULIE DATE/TIME EDITED: APR 02, 2007@23:25 ACTION: APPROVED AT THE REQUEST OF: ANWER,MOHAMED DATE/TIME EDITED: AUG 26, 2010@14:10 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: RIKARD,KENNETH WITH CONCURRENCE OF: ROCHA,MARCELO NUMBER: 331 IA #: 331 DATE CREATED: JAN 12, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA331 ORIGINAL NUMBER: 331 GENERAL DESCRIPTION: An enhancement patch will be issued to add the most recent lab results to the Action Profile. If the pharmacy supervisor wants the lab data printed, he/she selects the new option to select the drug, specimen type, and number of days back to search for lab test results. An option will be added to the pharmacy supervisor's menu. Since only one option and menu item need to be added to the OPTION (#19) file, we would like to add them by using DIC calls. We would prefer not to send inits only to add the option. Checks are made in the routine to assure that the site is running version 6.0, the option is installed only once, there are no other options with the same name, and the supervisor's menu exist. The user may run the routine many times and only install the option and menu item once. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 332 IA #: 332 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: JAN 14, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA332 ORIGINAL NUMBER: 332 ID: VA(200, GENERAL DESCRIPTION: The Radiology/Nuclear Medicine package is granted this DBIA to use field 53.4 of the New Person File(#200). STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 333 IA #: 333 FILE NUMBER: 60 GLOBAL ROOT: LAB(60, DATE CREATED: JAN 14, 1994 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA333-A ORIGINAL NUMBER: 333 ID: LAB(60, GENERAL DESCRIPTION: Outpatient Pharmacy is granted a temporary integration agreement with Laboratory to obtain results for a given lab test specimen type within a date range. This data may be used many different ways. Current uses are clozapine monitoring, printing on action profile, and drug usage evaluation. GLOBAL MAP DATA DICTIONARY #60 -- LABORATORY TEST FILE STORED IN ^LAB(60, SITE: BIRMINGHAM ISC ^-------------------------------------------------------------------------- ^LAB(60,D0,0)= (#.01) NAME [1F] ^^^^ (#5) LOCATION (DATA NAME) [5F] ^ ^LAB(60,D0,.2)= (#400) DATA NAME [1P] ^ ^LAB(60,D0,1,D1,0) = ^^^^^^ (#6) UNITS [7F] ^ DURATION: Till next version--LAB will incorporate an HL7 exchange STATUS: Active DURATION: Next Version SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas NUMBER: 334 IA #: 334 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: JAN 14, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA334 ORIGINAL NUMBER: 334 ID: VA(200, GENERAL DESCRIPTION: Outpatient Pharmacy is granted permission to enter/edit the following fields. File: New Person (#200) Field # Node;Piece Field Name .111 .11;1 STREET ADDRESS 1 .112 .11;2 STREET ADDRESS 2 .113 .11;3 STREET ADDRESS 3 .114 .11;4 CITY .115 .11;5 STATE .116 .11;6 ZIP CODE .131 .13;1 PHONE .132 .13;2 OFFICE PHONE .133 .13;3 PHONE #3 .134 .13;4 PHONE #4 .141 .14;1 ROOM STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 336 IA #: 336 DATE CREATED: JAN 18, 1994 CUSTODIAL PACKAGE: AUTOMATED INFO COLLECTION SYS CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBDF18 NAME: DBIA336 ORIGINAL NUMBER: 336 ID: IBDF18 GENERAL DESCRIPTION: The Problem List Application is granted permission to use the function calls, "$$GETFORM^IBDF18" and "$$COPYFORM^IBDF18". These calls are used to collect common problem lists defined under the Encounter Form Utility. By replicating the previously entered lists, the clinician is spared duplicate entry. $$GETFORM^IBDF18() Input: NONE Returned:
^ $$COPYFORM^IBDF18(FORM,ARY) Input: FORM= ien of form that has clinic common problem list ARY= Location where clinic common problem list should be copied to. ARY is accessed via indirection, as in @ARY@(1) for the first entry Returns: Length of the list STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$GETFORM COMPONENT/ENTRY POINT: $$COPYFORM(FORM,ARY) SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City NUMBER: 337 IA #: 337 DATE CREATED: JAN 18, 1994 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSLOAD NAME: DBIA337 ORIGINAL NUMBER: 337 ID: GMTSLOAD GENERAL DESCRIPTION: The Problem List Application will produce three (3) Problem List components for the Health Summary Application. These components are: ACTIVE PROBLEMS, INACTIVE PROBLEMS, and FULL PROBLEM LIST. In order to load the new components of the Ad Hoc Summary on to existing systems, the Problem List Application requests permission to use the entry point: ENPOST^GMTSLOAD Input: INCLUDE=0 Returned: Nothing STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: ENPOST VARIABLES: INCLUDE TYPE: Input SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City NUMBER: 338 IA #: 338 FILE NUMBER: 142.1 GLOBAL ROOT: GMT(142.1, DATE CREATED: JAN 18, 1994 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA338 ORIGINAL NUMBER: 338 ID: GMT(142.1, GENERAL DESCRIPTION: The Problem List Application is granted permission to add three (3) components to the Health Summary Application's Health Summary Component File (142.1). They are: ACTIVE PROBLEMS, INACTIVE PROBLEMS and FULL PROBLEM LIST. The new components will be added in a post-init using ^DIC. The components are installed using code provided to us by the Health Summary developers. FileMan variables DIC, DIC(0), DLAYGO, DINUM, and X are set to add each component to the Health Summary Component file if it's not already there; entry numbers 59-61 were given to the Problem List pkg to use for these components. Once entered into the file, DR is set and DIE called to stuff in the values of the other fields. The following was added on 4/12/94: To support the addition of new components to the Health Summary Application, the following actions are taken in the post-init. 1. Routine GMPLHSPL is renamed to GMTSPLST. 2. The post-init sets ^GMT(142.1,DA,3.5 nodes. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City NUMBER: 341 IA #: 341 DATE CREATED: JUN 25, 2003 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SDROUT2 NAME: DBIA341 ORIGINAL NUMBER: 341 ID: SDROUT2 GENERAL DESCRIPTION: The Problem List Application is granted permission from Scheduling to use the entry point "DIS^SDROUT2". This will display a patient's service connected data for the clinician. DIS^SDROUT2 Input: DFN Returned: Display of patient's service-connected data. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: DIS VARIABLES: DFN TYPE: Input SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City NUMBER: 342 IA #: 342 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: JAN 24, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA342 ORIGINAL NUMBER: 342 ID: VA(200, GENERAL DESCRIPTION: The Problem List Application is granted permission for the addition of the following fields to the NEW PERSON FILE (^VA(200,)). Also granted is permission to read and write to these fields as appropriate. These fields are used to tailor the Problem List Application for individual use. 125 PRIMARY VIEW 125.01 PROBLEM LIST SEARCH FILTER 125.02 PROBLEM LIST DISPLAY CODES 125.03 PROBLEM VOCABULARY 125.1 PROBLEM SELECTION LIST STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City NUMBER: 343 IA #: 343 DATE CREATED: JAN 25, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XQSRV NAME: DBIA343 ORIGINAL NUMBER: 343 ID: XQSRV GENERAL DESCRIPTION: It is agreed that MailMan can call XQSRV for servers. MailMan sends XQSRV: XMZ, XMXX, XMFROM, XMCHAN, XMSEN, XMREC & XMB("TYPE"). STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: XQSRV VARIABLES: XMZ TYPE: Input VARIABLES: XMXX TYPE: Input VARIABLES: XMFROM TYPE: Input VARIABLES: XMCHAN TYPE: Input VARIABLES: XMXEN TYPE: Input VARIABLES: XMREC TYPE: Input VARIABLES: XMB('TYPE') TYPE: Input SUBSCRIBING PACKAGE: MAILMAN ISC: Washington/Silver Spring NUMBER: 345 IA #: 345 GLOBAL ROOT: DD( DATE CREATED: FEB 02, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA345-A ORIGINAL NUMBER: 345 ID: DD( GENERAL DESCRIPTION: Read only access for the ^DD( Global Read ^DD(FN), where FN is a file number, to determine the existence of a file prior to initiating a look-up (GMPTA4). Read ^DD(757*,FLD in indexing routines to obtain the location (node/piece) of data in Clinical Lexicon files 757-757.3 prior to eXecuting Set/Kill logic (GMPTNDX2). STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: LEXICON UTILITY ISC: Salt Lake City NUMBER: 346 IA #: 346 FILE NUMBER: 8984.1 GLOBAL ROOT: XT(8984.1, DATE CREATED: FEB 04, 1994 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA346-A ORIGINAL NUMBER: 346 ID: XT(8984.1, GENERAL DESCRIPTION: Read only access to ^XT(8984.* globals for $D checks in the Environment Check routine prior to installing the Clinical Lexicon (GMPTIENV). i.e. I '$D(^XT(8984.1)) W !,"Multi-Term Look-Up Untility not found" K DIFQ Q Read/Write access to ^XT(8984.* global in Post-Init routines to setup the Multi-Term Look-Up Utility for the Clinical Lexicon (GMPTIPST). i.e., a. Seeding the Local Look-Up file #8984.4 with the Clinical Lexicon Expression file #757.01, the "AWRD" index and the XTLK^GMPTPRNT display routine. b. Seeding the Synonym file #8984.3 with Cancer as a sample synonym for Carcinoma c. Seeding the Short Cut file #8984.2 with DM II as a sample short cut for Diabetes Mellitus, Non-Insulin Dependent STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: LEXICON UTILITY ISC: Salt Lake City NUMBER: 347 IA #: 347 DATE CREATED: FEB 07, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORVP NAME: DBIA347 ORIGINAL NUMBER: 347 ID: ORVP GENERAL DESCRIPTION: The Problem List Application has permission to use of the entry point "IN^OR" for patient selection, using the OE/RR patient lookup engine and resetting of all needed OE/RR patient variables within the OE/RR context. The OE/RR variable ORVP is checked for (via $D) to see if PL was invoked from within OE/RR; if so, and the user wishes to switch to a different patient, this call will pass control to OE/RR to do the prompting and resetting of any important OE/RR patient variables. Problem List only references ORVP on return. It should be noted that the call to IN^OR is only made if the Problem list application is being selected from within the Order Entry application itself. Therefore the PL application simply has a screen to check for ORVP. If it exists it knows that it is within OE/RR and and only calls IN^OR if the SP (select Patient) action is selected before exiting the PL mode. This call updates the variables within OE so that it will not return to the previous patient when PL is exited. OE/RR is responsible for setting and killing all OR variables. IN^OR Input: ORVP Returned: ORVP STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: IN VARIABLES: ORVP TYPE: Both SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City NUMBER: 348 IA #: 348 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: FEB 11, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA348 ORIGINAL NUMBER: 348 ID: DPT( GENERAL DESCRIPTION: Problem List has permission to access File #2, Field #.32201. This will allow supported reference to draw Persian Gulf duty information from the Patient File. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City NUMBER: 349 IA #: 349 DATE CREATED: FEB 17, 1994 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSDVR NAME: DBIA349 ORIGINAL NUMBER: 349 ID: GMTSDVR STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: ENX COMPONENT DESCRIPTION: This entry point is called to print a pre-defined health summary. Radiology uses this call to print a site-defined health summary along with the Radiology Request form. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient file record number VARIABLES: GMTSTYP TYPE: Input VARIABLES DESCRIPTION: Health Summary Type file record number (142) VARIABLES: DIROUT TYPE: Output VARIABLES DESCRIPTION: =1 if '^^' is entered. COMPONENT/ENTRY POINT: ENXQ COMPONENT DESCRIPTION: This entry point is called to task the printing of a pre-defined health summary in the following manner: S ZTRTN="ENXQ^GMTSDVR",ZTSAVE("GMTSTYP")="",ZTSAVE("DFN")="" D ^%ZTLOAD VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient file record number VARIABLES: GMTSTYP TYPE: Input VARIABLES DESCRIPTION: Health summary Type file record number (142) SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Albany NUMBER: 350 IA #: 350 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: FEB 28, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA350 ORIGINAL NUMBER: 350 ID: DPT( GENERAL DESCRIPTION: I. Direct read access to the DPT global. A. ^DPT("SSN") -> Used to obtain a list of all patient SSN's currently on file. These SSN's are then compared to the SSN's on the MPD CDROM to check for visits to other hospitals. B. ^DPT(DFN) -> Used to verify that a patient is in the file. C. ^DPT(DFN,"S",DATE,0) -> Used to verify that a clinic appointment has not been canceled. II. The addition of a Mumps cross-reference to the SSN field for the purpose of setting the SSN in the PPP NEW SSN file. Any new SSN's will be checked at night for visits to other hospitals and then deleted from the PPP NEW SSN file. We suggest the Mumps cross-reference be implemented as follows: SET -> S PPP=X,X="PPPFMX" X ^%ZOSF("TEST") D:$T SNSSN^PPPFMX S X=PPP K PPP KILL -> S PPP=X,X="PPPFMX" X ^%ZOSF("TEST") D:$T KNSSN^PPPFMX S X=PPP K PPP The referenced routines are as follows: SNSSN ; N PPPNOD0,PPPTR N ZTRTN,ZTIO,ZTDTH,ZTDESC,ZTSAVE ; ; Check that this is either an edit or a new entry to avoid ; setting during a re-index of the Patient file. ; PPPOK is defined in the kill logic below if the new entry ; does not equal the old. ; DPTDFN is defined in the Patient Registration routines. ; I ($D(PPPOK))!($D(DPTDFN)) D .S PPPNOD0=$G(^PPP(1020.7,0)) .Q:PPPNOD0="" .; .; Get the File Descriptor Node for updating. .; .S PPPTR=$P(PPPNOD0,"^",4) .; .; Set the entry and the "B" Xref .; .S ^PPP(1020.7,DA,0)=X .S ^PPP(1020.7,"B",X,DA)="" .; .; Update the Descriptor node. .; .S $P(PPPNOD0,"^",3)=DA .S $P(PPPNOD0,"^",4)=PPPTR+1 .S ^PPP(1020.7,0)=PPPNOD0 .; .; Task out the MPD lookup. .; .S ZTRTN="NEWSSN^PPPBLD5" .S ZTIO="" .S ZTDTH=$H .S ZTDESC="NEW SSN/MPD ROUTINE" .S ZTSAVE("PPPSSN")=PPP .S ZTSAVE("PPPIFN")=DA .D ^%ZTLOAD ; K PPPOK Q KNSSN ; N PPPNOD0 ; ; Check that this is an edit and not a re-index. ; I X'=$P($G(^DPT(DA,0)),"^",9) D .S PPPOK=1 .; .; Check that the node currently exists, kill it if it does. .; .I $D(^PPP(1020.7,"B",PPP)) D ..K:$D(^PPP(1020.7,DA)) ^(DA) ..K:$D(^PPP(1020.7,"B",PPP,DA)) ^(DA) ..; ..; If the record count is alredy 0 then quit. ..; ..S PPPNOD0=^PPP(1020.7,0) ..Q:+$P(PPPNOD0,"^",4)=0 ..S $P(PPPNOD0,"^",4)=$P(PPPNOD0,"^",4)-1 ..S ^PPP(1020.7,0)=PPPNOD0 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14437025 SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE ISC: Albany NUMBER: 352 IA #: 352 GLOBAL ROOT: DD( DATE CREATED: FEB 28, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA352 ORIGINAL NUMBER: 352 ID: DD( GENERAL DESCRIPTION: PCE (PX) is granted permission to execute the DD nodes for completing cross-references in the 9000001 file from within cross-reference logic on the Social Security (.09) field in the Patient file. There is a Regular "B" cross-reference on the .01 field (NAME) of the PATIENT/IHS file (9000001). There is also a Regular "D" cross- reference on the .02 field of the 9000001.41 Health Record Number multiple. Since the fields in the 9000001 file are being populated from during the execution of the Patient File (2) PX09 cross- reference, the DD logic for setting these cross-references is being handled by executing the 9000001 and 9000001.41 DD nodes with the set and kill logic. Routine PXXDPT executes the set logic of the 'B' cross reference of file 9000001, (Patient/IHS File), field .01 (Name). It also executes the set and kill logic of the 'D' whole file cross reference of subfile 9000001.41, (Health Record Fac), field .02 (Health Record No.) In V21 of FileMan, the entry points in ^DIK that reindex cross references are reentrant. Thus, direct execution of set/kill logic will not be necessary. Also PCE's Debugging Utility does a Global Read in the form of '$D(^DD(2,.09,1,800)) to check that the cross reference to update the PATIENT/IHS file (#9000001) exists. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24853836 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany NUMBER: 353 IA #: 353 DATE CREATED: FEB 28, 1994 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCPUX1 NAME: DBIA353 ORIGINAL NUMBER: 353 ID: PRCPUX1 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$DESCR(X,Y) COMPONENT DESCRIPTION: Output: Short Description of the item from the ITEM MASTER file. Purpose: The short description describes the name of the Prosthetic device which is being billed on a claim to an Insurance company. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: pointer to an inventory point in the GENERIC INVENTORY (#445) file. The value of '0' is always passed as this parameter. VARIABLES: Y TYPE: Input VARIABLES DESCRIPTION: pointer to an item in the ITEM MASTER (#441) file. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 354 IA #: 354 DATE CREATED: FEB 28, 1994 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMPLENFM NAME: DBIA354 ORIGINAL NUMBER: 354 ID: GMPLENFM STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34250008 COMPONENT/ENTRY POINT: ACTIVE COMPONENT DESCRIPTION: 1) Permission granted to call ACTIVE^GMPLENFM for the purpose of obtaining a list of the patient's active problems. Requires DFN = ien of patient in File #2 Returns the data in the ^TMP global as follows, at the request of IB - ^TMP("IB",$J,"INTERFACES",DFN,"GMP PATIENT ACTIVE PROBLEMS",#) = Piece 1: Text of problem 2: ICD code of problem 3: Date of Onset in 00/00/00 format 4: "SC" or "NSC" or "", if problem is [not] related to a SC Cond. 5: "Y" or "N" or "", if problem is [not] related to a SC Condition (Pieces 4 and 5 give the same data, just in different formats.) 6: "A" or "I" or "P" or "H" or "M" or "", if problem is related to exposure to Agent Orange, Ionization, Persian Gulf, Head and/or Neck Cancer, Military Sexual Trauma or null respectively 7: Full text of the special exposure indicated in piece 6, if any where each # is a diffesent problem, 1 - n with n being the total number of active problems; the 0-node is also set to the total (n). COMPONENT/ENTRY POINT: SELECT COMPONENT DESCRIPTION: 2) Permission granted to call SELECT^GMPLENFM for the purpose of allowing users access to the EXPRESSIONS file to create lists of Clinic Common Problems. SELECT^GMPLENFM is used for the lookup rather than a simple ^DIC call in order to setup the Problem List context for searching the Lexicon. Requires no input values. Returns the entry in the Lexicon Utility selected to add to a form as a commonly selected problem in the ^TMP global as follows, as requested - ^TMP("IB",$J,"INTERFACES","GMP SELECT CLINIC COMMON PROBLEMS") = Piece 1: IEN of problem in Lexicon Utility's Expressions file (#757.01) 2: Text of problem 3: ICD Code of problem, if known SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 355 IA #: 355 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: MAR 03, 1994 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA355 ORIGINAL NUMBER: 355 ID: DPT( GENERAL DESCRIPTION: Read access to the following fields and cross-references: FIELDS: ELEMENT FILE DD LEVEL FIELD # DD NUMBER **APPOINTMENT DATE/TIME PATIENT 1 1900 2 2 .001 2.98 **APPOINTMENT STATUS PATIENT 1 1900 2 2 3 2.98 **APPOINTMENT TYPE PATIENT 1 1900 2 2 9.5 2.98 **APPT. CANCELLATION REASON PATIENT 1 1900 2 2 16 2.98 **CLINIC PATIENT 1 1900 2 2 .01 2.98 (The above fields related to field 1900 will be eliminated with the scheduling redesign.) **DATE OF ENROLLMENT PATIENT XREF: AEB STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM ISC: Hines NUMBER: 357 IA #: 357 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: MAR 03, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA357 ORIGINAL NUMBER: 357 ID: DPT( GENERAL DESCRIPTION: Read access to the following fields and cross-references. FIELDS: ELEMENT FILE DD LEVEL FIELD # DD NUMBER DATE OF DEATH PATIENT 1 .351 2 DISPOSITION PATIENT 1 1000 2 2 6 2.101 LOG IN DATE/TIME PATIENT 1 1000 2 2 .01 2.101 LOG IN STATUS PATIENT 1 1000 2 2 1 2.101 LOG OUT DATE/TIME PATIENT 1 1000 2 2 5 2.101 PURPOSE OF VISIT PATIENT 1 1900 2 2 9 2.98 REASON FOR LATE DISPOSITION PATIENT 1 1000 2 2 8 2.101 SERVICE CONNECTED PERCENTAGE PATIENT 1 .302 2 SERVICE CONNECTED? PATIENT 1 .301 2 SPINAL CORD INJURY PATIENT 1 $ 57.4 2 TYPE OF BENEFIT APPLIED FOR PATIENT 1 1000 2 2 2 2.101 TYPE OF CARE APPLIED FOR PATIENT 1 1000 2 2 2.1 2.101 CROSS REFERENCES: DATE OF BIRTH PATIENT XREF: ADOB SEX PATIENT XREF: ASX **DATE OF ENROLLMENT PATIENT XREF: AEB DATE OF DEATH PATIENT XREF: AEXP1 LOG IN DATE/TIME PATIENT XREF: ADIS STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM ISC: Hines NUMBER: 358 IA #: 358 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: MAR 03, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA358 ORIGINAL NUMBER: 358 ID: DGPM( GLOBAL REFERENCE: DGPM( FIELD NUMBER: 200 FIELD NAME: WARD AT DISCHARGE LOCATION: computed field ACCESS: Read w/Fileman GENERAL DESCRIPTION: Read access to the following fields and cross-references. FIELDS: ELEMENT FILE DD LEVEL FIELD # DD NUMBER TYPE OF MOVEMENT PATIENT MOVEMENT 1 .04 405 WARD LOCATION PATIENT MOVEMENT 1 .06 405 TRANSACTION TYPE PATIENT MOVEMENT 1 .02 405 ROOM-BED PATIENT MOVEMENT 1 .07 405 ADMITTED FOR SC CONDITION? PATIENT MOVEMENT 1 .11 405 ADMITTING REGULATION PATIENT MOVEMENT 1 .12 405 ATTENDING PHYSICIAN PATIENT MOVEMENT 1 .19 405 DIAGNOSIS [SHORT] PATIENT MOVEMENT 1 .1 405 FACILITY TREATING SPECIALTY PATIENT MOVEMENT 1 .09 405 MAS MOVEMENT TYPE PATIENT MOVEMENT 1 .18 405 MOVEMENT DATE/TIME PATIENT MOVEMENT 1 .01 405 PRIMARY CARE PHYSICIAN PATIENT MOVEMENT 1 .08 405 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM ISC: Hines SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES SUBSCRIBING PACKAGE: SCHEDULING NUMBER: 359 IA #: 359 FILE NUMBER: 45 GLOBAL ROOT: DGPT( DATE CREATED: MAR 03, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA359 ORIGINAL NUMBER: 359 ID: DGPT( GENERAL DESCRIPTION: FIELDS: ELEMENT FILE DD LEVEL FIELD # DD NUMBER PATIENT PTF 1 .01 & 45 PTF ADMISSION DATE PTF 1 2 45 PTF DISCHARGE DATE PTF 1 70 45 PTF DISCHARGE SPECIALTY PTF 1 71 45 PTF DRG PTF 1 9 45 PTF DXLS PTF 1 79 45 PTF ICD 10 PTF 1 79.24 45 PTF ICD 2 PTF 1 79.16 45 PTF ICD 3 PTF 1 79.17 45 PTF ICD 4 PTF 1 79.18 45 PTF ICD 5 PTF 1 79.19 45 PTF ICD 6 PTF 1 79.201 45 PTF ICD 7 PTF 1 79.21 45 PTF ICD 8 PTF 1 79.22 45 PTF ICD 9 PTF 1 79.23 45 PTF PROCEDURE 1 PTF 1 45.01 45 PTF PROCEDURE 2 PTF 1 45.02 45 PTF PROCEDURE 3 PTF 1 45.03 45 PTF PROCEDURE 4 PTF 1 45.04 45 PTF PROCEDURE 5 PTF 1 45.05 45 PTF TYPE OF DISPOSITION PTF 1 72 45 PTF WARD AT DISCHARGE PTF 1 2.2 45 SURGERY/PROCEDURE DATE PTF 1 401 45 2 .01 45.01 OPERATION CODE 1 PTF 1 401 45 2 8 45.01 OPERATION CODE 2 PTF 1 401 45 2 9 45.01 OPERATION CODE 3 PTF 1 401 45 2 10 45.01 OPERATION CODE 4 PTF 1 401 45 2 11 45.01 OPERATION CODE 5 PTF 1 401 45 2 12 45.01 CROSS REFERENCES: CLOSE OUT DATE PTF CLOSE OUT XREF: AC DATA GLOBAL PTF XREF: ^DGPT(D0,"S",D1,... ^ |-- SURGERY/PROCEDURE DATE STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM ISC: Hines NUMBER: 360 IA #: 360 FILE NUMBER: 405.3 GLOBAL ROOT: DG(405.3, DATE CREATED: MAR 03, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA360 ORIGINAL NUMBER: 360 ID: DG(405.3, GENERAL DESCRIPTION: Read access to the following fields: FIELDS: ELEMENT FILE DD LEVEL FIELD # DD NUMBER MAS MOVEMENT TRANSACTION TYPE MAS MOVEMENT TRANSACTION TYPE 1 .01 405.3 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM ISC: Hines NUMBER: 361 IA #: 361 FILE NUMBER: 37 GLOBAL ROOT: DIC(37, DATE CREATED: MAR 03, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA361 ORIGINAL NUMBER: 361 ID: DIC(37, GENERAL DESCRIPTION: Read access to the following fields: FIELDS: ELEMENT FILE DD LEVEL FIELD # DD NUMBER NAME DISPOSITION 1 .01 37 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM ISC: Hines NUMBER: 362 IA #: 362 FILE NUMBER: 45.7 GLOBAL ROOT: DIC(45.7, DATE CREATED: MAR 03, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA362 ORIGINAL NUMBER: 362 ID: DIC(45.7, GENERAL DESCRIPTION: Read access to the following fields: FIELDS: ELEMENT FILE DD LEVEL FIELD # DD NUMBER NAME FACILITY TREATING SPECIALTY 1 .01 45.7 FACILITY TREATING SPECIALTY SERVICE 1 2 45.7 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM ISC: Hines SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES NUMBER: 363 IA #: 363 FILE NUMBER: 405.2 GLOBAL ROOT: DG(405.2, DATE CREATED: MAR 03, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA363 ORIGINAL NUMBER: 363 ID: DG(405.2, GLOBAL REFERENCE: DG(405.2,D0,0) FIELD NUMBER: .02 FIELD NAME: TRANSACTION TYPE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains a pointer to the MAS MOVEMENT TRANSACTION TYPE file containing the allowable types of bed control movements (admissions, discharges, transfers, lodger movements, etc.). GLOBAL DESCRIPTION: This file holds all MAS accepted/approved movement types. GENERAL DESCRIPTION: Read access to the following fields: FIELDS: ELEMENT FILE DD LEVEL FIELD # DD NUMBER NAME MAS MOVEMENT TYPE 1 .01 405.2 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25456385 SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM ISC: Hines SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 366 IA #: 366 FILE NUMBER: 80.1 GLOBAL ROOT: ICD0( DATE CREATED: MAR 03, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA366 ORIGINAL NUMBER: 366 ID: ICD0( GENERAL DESCRIPTION: Read access to the following Fields: FIELDS: ELEMENT FILE DD LEVEL FIELD # DD NUMBER CODE NUMBER ICD OPERATION/PROCEDURE 1 .01 80.1 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM ISC: Hines NUMBER: 367 IA #: 367 DATE CREATED: MAR 09, 1994 CUSTODIAL PACKAGE: LIST MANAGER CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VALM NAME: DBIA367 ORIGINAL NUMBER: 367 ID: VALM GENERAL DESCRIPTION: Request: Use of the routine calls REFRESH^VALM and RESET^VALM4:VALMCC Input: none Output: none Purpose: These calls are used to refresh the screen and reset the scrolling area while program control remains within an action (as opposed to performing the same action when exiting an action, which is accomplished by setting VALMBCK="R"). Request permission to set the variable VALM("PROTOCOL"). The purpose of setting this variable is to be able to define the specific protocol to be executed for a list template, as opposed to defining three identical list templates, all with different protocol menus. Resetting VALM("PROTOCOL") resets the protocol menu. This allows having the same list manager definitions for a screen that may have different input capabilities, for example one with input and one just view only actions. RESET^VALM4 can ONLY be called if VALMCC is high(1) The context for these calls are as follows: The calls will be made within a List Manager application, specifically within various options of the Encounter Form Utilities. The reason for making the calls is that we want to be able to display an encounter form in the top part of the screen while having a dialogue with the user in the bottom part of the screen. The problem is that it is necessary to call FileMan at certain points within the dialogue. FileMan assumes it has the entire screen at its disposal, so when it communicates with the user the display#is likely to scroll out of the scrolling area on the bottom of the screen, so the user is unable to read what FileMan displays. To avoid that, what we do is: 1) Everywhere FileMan is called in the situation described above we call FULL^VALM1. That sets the scrolling area to the entire screen. 2) When the problem point is passed and we want to continue the dialogue with the encounter form displayed at the top we call REFRESH^VALM to redraw the screen. Then we call RESET^VALM4 to reset the scrolling area so that the dialogue can occur on the bottom of the screen with the form displayed at the top. VALMCC is an input variable to RESET^VALM4. VALMCC must test true or RESET^VALM4 should not be called. There are dozens of variables that are set by the List Manager, but those are part of the internal workings of the List Manager and are not the concern of this application. There are some List Manager variables that the application is responsible for setting, but those are well documented by the List Manager, i.e., they are not specific to calling these entry points. The context is that the List Manager has been called. Then, from within the List Manager, the user has selected an action, which invokes a protocol. The protocol invokes a routine, which is where those calls are made. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: REFRESH VARIABLES: VALMCC TYPE: Input SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 371 IA #: 371 DATE CREATED: MAR 09, 1994 CUSTODIAL PACKAGE: DRG GROUPER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ICDDRG NAME: DBIA371 ORIGINAL NUMBER: 371 ID: ICDDRG CREATOR: MARRI,NAGARAJA STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: ICDDRG COMPONENT DESCRIPTION: The routine call is made to calculate interim DRGs to determine the expected length of stay for a visit. Changes were made to this ICR to add the ICDDATE parameter in July 2014. The ICD-10 team's analysis did not find calls to the ICDDRG API in the YS* routine namespace. VARIABLES: ICDEXP TYPE: Input VARIABLES DESCRIPTION: Did patient expire during episode? VARIABLES: ICDTRS TYPE: Input VARIABLES DESCRIPTION: Patient transfer to acute facility? VARIABLES: ICDDMS TYPE: Input VARIABLES DESCRIPTION: Patient have irregular discharge? VARIABLES: ICDDX(1,2,..n)=X TYPE: Input VARIABLES DESCRIPTION: Set of pointers (X) to diagnosis codes in file #80. VARIABLES: ICDPRC(1,2,..n)=X TYPE: Input VARIABLES DESCRIPTION: Set of pointers (X) to procedures in file #80.1. VARIABLES: SEX TYPE: Input VARIABLES DESCRIPTION: Patient gender (M-Male|F-Female) VARIABLES: ICDPOA(1,2, TYPE: Input VARIABLES DESCRIPTION: Set of values (Y,N,W,U OR BLANK) corresponding to ICDDX input array to indicate Presence on Admission VARIABLES: ICDDRG TYPE: Output VARIABLES DESCRIPTION: Pointer to assigned DRG in file #80.2 VARIABLES: ICDDATE TYPE: Input VARIABLES DESCRIPTION: The date of service (optional parameter, the default value is DT - today's FileMan date). SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: LEXICON UTILITY SUBSCRIBING DETAILS: Lexicon queries files 80 and 80.1, and calculates DRG group to verify that versioned data is correct. Effective with LEX*2.0*80. DBA Comments: 07/26/12 DLT inactivated so Kumar Marri can add the new variable to the existing API. 07/27/12 DLT activated. The changes are from developers of the ICD-10 Class 1 Remediation Project and will be distributed in ICD*18.0*64. SQA testing required these API to be approved. 07/10/13 DLT added LEXICON UTILITY as a subscribing package effective with LEX*2.0*80. 1/22/14-MM: ICD-10 team is requesting to modify ICR #371 to add a new input parameter (ICDDRG). Shavat Shamukhamedov searched Mental Health (YS*) and Lexicon routines for references to the ICDDRG API. Frank Traxler searched his email messages for references to ICR #371, the YS* and YT* routines, DDs, input/print/sort templates, RPCs, options and help frames. He also confirmed the Behavioral Health Lab software is not using the API. It was agreed Mental Health should be removed as a subscriber. 1/28/14-MM: ICR #371 deactivated for editing. Shavkat will be adding a new parameter, ICDDATE. ICD-10 Project team is working on a DG and IB patch to work with the new parameter. Mental Health was deleted as a subscriber when it was determined the application is not using the API. They have tested their software in an account with Lexicon installed without errors. Kim Rowe included in the discussion but did not confirm Shavkat's findings. 7/18/14-DT: Shavkat Shamukhamedov made edits to ICR #371 to reference the optional input variable ICDDATE. This option has always been available to the developers, but was not officially documented in the ICR. The following subscriber package and developer concurred with the ICR changes: Registration Daniel Pendergrass DG*5.3*850 Integrated Billing Amy Harper Lexicon Kimball Rowe (new subscriber as of April 2013) Jeremy Gilmore represents DRG GROUPER. Shavkat is on the ICD10 team. DATE ACTIVATED: JUL 18, 2014 DATE/TIME EDITED: JUL 10, 2012@14:11 DATE/TIME EDITED: JUL 26, 2012@16:20 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: MARRI,NAGARAJA WITH CONCURRENCE OF: GILMORE,JEREMY DATE/TIME EDITED: JUL 27, 2012@17:12 ACTION: APPROVED AT THE REQUEST OF: MARRI,NAGARAJA WITH CONCURRENCE OF: GILMORE,JEREMY DATE/TIME EDITED: JUL 10, 2013@11:46 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: ROWE,KIMBALL WITH CONCURRENCE OF: VILLELLA,ROSS DATE/TIME EDITED: JAN 22, 2014@14:04 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: DAVIS,ROB WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: JAN 28, 2014@13:53 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: SHAMUKHAMEDOV,SHAVKAT DATE/TIME EDITED: JUL 18, 2014@17:46 ACTION: APPROVED AT THE REQUEST OF: GILMORE,JERRY WITH CONCURRENCE OF: ROWE,KIMBALL NUMBER: 372 IA #: 372 FILE NUMBER: 4 GLOBAL ROOT: DIC(4, DATE CREATED: MAR 09, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA372 ORIGINAL NUMBER: 372 ID: DIC(4, GENERAL DESCRIPTION: Integrated Billing requests permission to add entries to the INSTITUTION (#4) when creating bills. The user is required to hold the IB SUPERVISOR security key to add entries into file #4. STATUS: Active SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 373 IA #: 373 FILE NUMBER: 660 GLOBAL ROOT: RMPR(660, DATE CREATED: MAR 15, 1994 CUSTODIAL PACKAGE: PROSTHETICS CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA373 ORIGINAL NUMBER: 373 ID: RMPR(660, GLOBAL REFERENCE: RMPR(660, FIELD NUMBER: .01 FIELD NAME: ENTRY DATE LOCATION: 0;1 ACCESS: Pointed to FIELD NUMBER: .02 FIELD NAME: PATIENT NAME LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: ITEM LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 7 FIELD NAME: VENDOR LOCATION: 0;9 ACCESS: Read w/Fileman FIELD NUMBER: 10 FIELD NAME: DELIVERY DATE LOCATION: 0;12 ACCESS: Read w/Fileman FIELD NUMBER: 12 FIELD NAME: SOURCE LOCATION: 0;14 ACCESS: Read w/Fileman FIELD NUMBER: 14 FIELD NAME: TOTAL COST LOCATION: 0;16 ACCESS: Read w/Fileman FIELD NUMBER: 15 FIELD NAME: HISTORICAL DATA LOCATION: 0;15 ACCESS: Read w/Fileman FIELD NUMBER: 62 FIELD NAME: PATIENT CATEGORY LOCATION: AM;3 ACCESS: Read w/Fileman FIELD NUMBER: 30 FIELD NAME: PRIMARY ICD DIAGNOSIS CODE LOCATION: BA1;1 ACCESS: Read w/Fileman FIELD NUMBER: 30.1 FIELD NAME: PRIMARY AGENT ORANGE EXPOSURE LOCATION: BA1;2 ACCESS: Read w/Fileman FIELD NUMBER: 30.2 FIELD NAME: PRIMARY IONIZED RADIATION LOCATION: BA1;3 ACCESS: Read w/Fileman FIELD NUMBER: 30.3 FIELD NAME: PRIMARY SERVICE-CONNECTED LOCATION: BA1;4 ACCESS: Read w/Fileman FIELD NUMBER: 30.5 FIELD NAME: PRIMARY MST LOCATION: BA1;6 ACCESS: Read w/Fileman FIELD NUMBER: 30.4 FIELD NAME: PRIMARY ENVIRONMENTAL CONT. LOCATION: BA1;5 ACCESS: Read w/Fileman FIELD NUMBER: 30.6 FIELD NAME: PRIMARY HEAD/NECK CANCER LOCATION: BA1;7 ACCESS: Read w/Fileman FIELD NUMBER: 30.7 FIELD NAME: PRIMARY COMBAT VET LOCATION: BA1;8 ACCESS: Read w/Fileman FIELD NUMBER: 31 FIELD NAME: SECONDARY ICD DIAGNOSIS CODE 1 LOCATION: BA2;1 ACCESS: Read w/Fileman FIELD NUMBER: 31.1 FIELD NAME: SECONDARY AGENT ORANGE 1 LOCATION: BA2;2 ACCESS: Read w/Fileman FIELD NUMBER: 31.2 FIELD NAME: SECONDARY IONIZED RADIATION 1 LOCATION: BA2;3 ACCESS: Read w/Fileman FIELD NUMBER: 31.3 FIELD NAME: SECONDARY SERVICE-CONNECTED 1 LOCATION: BA2;4 ACCESS: Read w/Fileman FIELD NUMBER: 31.4 FIELD NAME: SECONDARY ENVIRONMENTAL CONT 1 LOCATION: BA2;5 ACCESS: Read w/Fileman FIELD NUMBER: 31.5 FIELD NAME: SECONDARY MST 1 LOCATION: BA2;6 ACCESS: Read w/Fileman FIELD NUMBER: 31.6 FIELD NAME: SECONDARY HEAD/NECK CANCER 1 LOCATION: BA2;7 ACCESS: Read w/Fileman FIELD NUMBER: 31.7 FIELD NAME: SECONDARY COMBAT VET 1 LOCATION: BA2;8 ACCESS: Read w/Fileman FIELD NUMBER: 32 FIELD NAME: SECONDARY ICD DIAGNOSIS 2 LOCATION: BA3;1 ACCESS: Read w/Fileman FIELD NUMBER: 32.1 FIELD NAME: SECONDARY AGENT ORANGE 2 LOCATION: BA3;2 ACCESS: Read w/Fileman FIELD NUMBER: 32.2 FIELD NAME: SECONDARY IONIZED RADIATION 2 LOCATION: BA3;3 ACCESS: Read w/Fileman FIELD NUMBER: 32.3 FIELD NAME: SECONDARY SERVICE-CONNECTED 2 LOCATION: BA3;4 ACCESS: Read w/Fileman FIELD NUMBER: 32.4 FIELD NAME: SECONDARY ENVIR. CONT. 2 LOCATION: BA3;5 ACCESS: Read w/Fileman FIELD NUMBER: 32.5 FIELD NAME: SECONDARY MST 2 LOCATION: BA3;6 ACCESS: Read w/Fileman FIELD NUMBER: 32.6 FIELD NAME: SECONDARY HEAD/NECK CANCER 2 LOCATION: BA3;7 ACCESS: Read w/Fileman FIELD NUMBER: 32.7 FIELD NAME: SECONDARY COMBAT VET 2 LOCATION: BA3;8 ACCESS: Read w/Fileman FIELD NUMBER: 33 FIELD NAME: SECONDARY ICD DIAGNOSIS 3 LOCATION: BA4;1 ACCESS: Read w/Fileman FIELD NUMBER: 33.1 FIELD NAME: SECONDARY AGENT ORANGE 3 LOCATION: BA4;2 ACCESS: Read w/Fileman FIELD NUMBER: 33.2 FIELD NAME: SECONDARY IONIZED RADIATION 3 LOCATION: BA4;3 ACCESS: Read w/Fileman FIELD NUMBER: 33.3 FIELD NAME: SECONDARY SERVICE-CONNECTED 3 LOCATION: BA4;4 ACCESS: Read w/Fileman FIELD NUMBER: 33.4 FIELD NAME: SECONDARY ENVIRON. CONT. 3 LOCATION: BA4;5 ACCESS: Read w/Fileman FIELD NUMBER: 33.5 FIELD NAME: SECONDARY MST 3 LOCATION: BA4;6 ACCESS: Read w/Fileman FIELD NUMBER: 33.6 FIELD NAME: SECONDARY HEAD/NECK CANCER 3 LOCATION: BA4;7 ACCESS: Read w/Fileman FIELD NUMBER: 33.7 FIELD NAME: SECONDARY COMBAT VET 3 LOCATION: BA4;8 ACCESS: Read w/Fileman GLOBAL REFERENCE: RMPR(660,'B',date) GLOBAL DESCRIPTION: $O through cross reference to find potentially billable prosthetic items. GLOBAL REFERENCE: RMPR(660,'CT',DATE) GLOBAL DESCRIPTION: $O through cross reference to find prosthetic items which may have been delivered to a patient within a specific date range. GLOBAL REFERENCE: RMPR(660,'C', GLOBAL DESCRIPTION: $O through the "C" x-ref. GLOBAL REFERENCE: RMPR(660,'AF', GLOBAL DESCRIPTION: $O through the "AF" x-ref by date. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 374 IA #: 374 FILE NUMBER: 661 GLOBAL ROOT: RMPR(661, DATE CREATED: MAR 15, 1994 CUSTODIAL PACKAGE: PROSTHETICS CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA374 ORIGINAL NUMBER: 374 ID: RMPR(661, GLOBAL REFERENCE: RMPR(661,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Field is also pointed to from IB files. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: IFCAP NUMBER: 376 IA #: 376 FILE NUMBER: 442.3 GLOBAL ROOT: PRCD(442.3, DATE CREATED: MAR 15, 1994 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA376 ORIGINAL NUMBER: 376 ID: PRCD(442.3, GLOBAL REFERENCE: PRCD(442.3,'AC', GLOBAL DESCRIPTION: Read acces to check if the Procurement and Accounting Transaction has already been completed. GENERAL DESCRIPTION: See DBIA375. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City NUMBER: 377 IA #: 377 FILE NUMBER: 424.1 GLOBAL ROOT: PRC(424.1, DATE CREATED: MAR 15, 1994 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA377 ORIGINAL NUMBER: 377 ID: PRC(424.1, GLOBAL REFERENCE: PRC(424.1,D0,0) FIELD NUMBER: .03 FIELD NAME: AUTHORIZATION AMOUNT LOCATION: 0;3 ACCESS: Write w/Fileman FIELD NUMBER: .04 FIELD NAME: DATE/TIME LOCATION: 0;4 ACCESS: Write w/Fileman FIELD NUMBER: .05 FIELD NAME: USER LOCATION: 0;5 ACCESS: Write w/Fileman FIELD NUMBER: .08 FIELD NAME: REFERENCE LOCATION: 0;8 ACCESS: Write w/Fileman FIELD NUMBER: .1 FIELD NAME: LAST EDITED BY LOCATION: 0;10 ACCESS: Write w/Fileman GENERAL DESCRIPTION: See DBIA375 STATUS: Active DURATION: Next Version GOOD ONLY FOR VERSION: pre-CoreFLS SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City NUMBER: 378 IA #: 378 FILE NUMBER: 442 GLOBAL ROOT: PRC(442, DATE CREATED: MAR 15, 1994 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCH58 NAME: DBIA378 ORIGINAL NUMBER: 378 ID: PRCH58 GENERAL DESCRIPTION: See DBIA375 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: BALUP COMPONENT DESCRIPTION: Updates field #96 (Estimated 1358 Balance) in file 442. VARIABLES: PODA TYPE: Input VARIABLES DESCRIPTION: ien of file 442 VARIABLES: BAL1 TYPE: Input VARIABLES DESCRIPTION: Authorization Amount. SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City NUMBER: 379 IA #: 379 DATE CREATED: MAR 15, 1994 CUSTODIAL PACKAGE: HINQ CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DVBHQZ4 NAME: DBIA379 ORIGINAL NUMBER: 379 ID: DVBHQZ4 GENERAL DESCRIPTION: This call allows billing clerks to place requests for HINQs for patients with unverified eligibility who are going to be billed. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Points to patient file. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 380 IA #: 380 DATE CREATED: MAR 15, 1994 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCAFN(X) NAME: DBIA380 ORIGINAL NUMBER: 380 ID: PRCAFN(X) GENERAL DESCRIPTION: The following function calls are made to the routine PRCAFN. The input X for each call is the internal entry number of an entry in the BILL/CLAIMS (#399) file, which is dinumed to the ACCOUNTS RECEIVABLE (#430) file. Each function will return -1 if a legitimate value cannot be returned. Also note that these functions only work for categories of receivables which are not PATIENT or MEANS TEST PATIENT (except for the PST, PUR, and CATN functions). STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$BN COMPONENT DESCRIPTION: This returns the receivable bill number. COMPONENT/ENTRY POINT: $$CAT COMPONENT DESCRIPTION: This function returns the receivable category (pointer to file #430.2). COMPONENT/ENTRY POINT: $$CLO COMPONENT DESCRIPTION: This function returns the date that a receivable was closed (or -1 if the receivable is not closed). COMPONENT/ENTRY POINT: $$ORI COMPONENT DESCRIPTION: This function returns the receivable Original Amount. COMPONENT/ENTRY POINT: $$PUR COMPONENT DESCRIPTION: This function is called by the IB purge routines and is used to determine the date that a receivable was closed out. COMPONENT/ENTRY POINT: $$RETN COMPONENT DESCRIPTION: This function determines whether a bill has the AR Status RETURNED FROM AR (NEW) in Accounts Receivable. The call is made to determine whether a bill has been returned to billing and is thus editable in Integrated Billing. COMPONENT/ENTRY POINT: $$STA COMPONENT DESCRIPTION: This function returns the receivable status. COMPONENT/ENTRY POINT: $$TPR COMPONENT DESCRIPTION: This function returns the total paid principal on the receivable. COMPONENT/ENTRY POINT: $$PST COMPONENT DESCRIPTION: This call is made to retrieve the day of the month that a patient's statement is generated. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Equals the string DFN_";DPT(" being the pointer to the patient in file #2) COMPONENT/ENTRY POINT: $$CATN COMPONENT DESCRIPTION: This call is made to retrieve the AR Category name. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Pointer to the category in file 430.2 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany NUMBER: 381 IA #: 381 DATE CREATED: MAR 15, 1994 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCALST NAME: DBIA381 ORIGINAL NUMBER: 381 ID: PRCALST GENERAL DESCRIPTION: This Accounts Receivable routine is the entry point for the Returned Bill List output. The routine is invoked by the Integrated Billing option IB RETURN BILL LIST. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: RETN SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 382 IA #: 382 DATE CREATED: MAR 15, 1994 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCAUT2 NAME: DBIA382 ORIGINAL NUMBER: 382 ID: PRCAUT2 GENERAL DESCRIPTION: This routine call displays the number of bills that have been returned to the service from Fiscal. There is no variable input required to make the call. This routine is invoked as an Entry Action of the following Integrated Billing menu options: IB BILLING CLERK MENU IB BILLING SUPERVISOR MENU IB RETURN BILL MENU STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: COUNT SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 383 IA #: 383 DATE CREATED: MAR 15, 1994 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCAX(DFN,BEG,END,.ERR) NAME: DBIA383 ORIGINAL NUMBER: 383 ID: PRCAX(DFN,BEG,END,.ERR) GENERAL DESCRIPTION: This call is used in Pharmacy copay exemption processing to cancel Pharmacy copay charges who become exempt from copay. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN1 VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient pointer VARIABLES: BEG TYPE: Input VARIABLES DESCRIPTION: Begin date to cancel Pharmacy copay charges. VARIABLES: END TYPE: Input VARIABLES DESCRIPTION: End date to cancel Pharmacy copay charges. VARIABLES: ERR TYPE: Input VARIABLES DESCRIPTION: Set to 0, used to return an error condition. VARIABLES: ERR TYPE: Output VARIABLES DESCRIPTION: Free-text error, if an error condition occurs. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 384 IA #: 384 DATE CREATED: MAR 15, 1994 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCASVC6 NAME: DBIA384 ORIGINAL NUMBER: 384 ID: PRCASVC6 GENERAL DESCRIPTION: This call is made just prior to passing a claim to the Accounts Receivable package. This routine call performs a check on all data required to establish a receivable and passes errors back to Integrated Billing. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: PRCASVC6 VARIABLES: PRCASV('BDT') TYPE: Input VARIABLES DESCRIPTION: Date bill generated (fileman date format) VARIABLES: PRCASV('ARREC') TYPE: Input VARIABLES DESCRIPTION: Record # of 430. VARIABLES: PRCASV('DEBTOR') TYPE: Input VARIABLES DESCRIPTION: Debtor (ex.'4;DPT(','3;DIC(36,' OR '3;DIC(4') VARIABLES: PRCASV('PAT') TYPE: Input VARIABLES DESCRIPTION: Patient pointer. VARIABLES: PRCASV('CAT') TYPE: Input VARIABLES DESCRIPTION: Category pointer to 430.2 VARIABLES: PRCASV('FY') TYPE: Input VARIABLES DESCRIPTION: Fiscal year,amount (multiple) (FY^AMOUNT^FY^AMOUNT) VARIABLES: PRCAXV('CARE') TYPE: Input VARIABLES DESCRIPTION: For only means test c-type of bill two digits: 1st digit :nursing home care 2nd digit :in or outpatient VARIABLES: PRCASV('APR') TYPE: Input VARIABLES DESCRIPTION: Person approved the bill, pointer to 200) VARIABLES: PRCSAV('2NDINS') TYPE: Input VARIABLES DESCRIPTION: 2nd insurance company (pointer to 36) VARIABLES: PRCASV('3RDINS') TYPE: Input VARIABLES DESCRIPTION: 3rd ins. company (pointer to 36) VARIABLES: PRCASV('IDNO') TYPE: Input VARIABLES DESCRIPTION: Primary ins. policy number. VARIABLES: PRCASV('GPNO') TYPE: Input VARIABLES DESCRIPTION: Prim. ins. group number. VARIABLES: PRCASV('GPNM') TYPE: Input VARIABLES DESCRIPTION: Prim. ins. group name. VARIABLES: PRCASV('INPA') TYPE: Input VARIABLES DESCRIPTION: Prim. ins. insured patient. VARIABLES: PRCASV('OKAY') TYPE: Output VARIABLES DESCRIPTION: Flag - bill passes checks. VARIABLES: PRCAERR TYPE: Output VARIABLES DESCRIPTION: -1^ERROR CODE to IB ERROR file. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 385 IA #: 385 DATE CREATED: MAR 15, 1994 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCASVC NAME: DBIA385 ORIGINAL NUMBER: 385 ID: PRCASVC GENERAL DESCRIPTION: This call is used to pass a new or returned bill to the Accounts Receivable package. This call is made right after the call D ^PRCASVC6, if that call returns PRCASV("OKAY") as a positive number. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: REL COMPONENT DESCRIPTION: Input: same as the call to D ^PRCASVC6 Output: same as the call to D ^PRCASVC6 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 386 IA #: 386 DATE CREATED: MAR 15, 1994 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCASVC3 NAME: DBIA386 ORIGINAL NUMBER: 386 ID: PRCASVC3 CREATOR: FIAMENGO,GRACE GENERAL DESCRIPTION: This call sets up a stub receivable in Accounts Receivable. The internal entry number for the receivable is used as the internal entry number of the bill in the BILL/CLAIMS (#399) file. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: SETUP VARIABLES: PRCASV('SER') TYPE: Input VARIABLES DESCRIPTION: MAS Service pointer in file 49 VARIABLES: PRCASV('SITE') TYPE: Input VARIABLES DESCRIPTION: Station Number VARIABLES: PRCASV('ARREC') TYPE: Both VARIABLES DESCRIPTION: Pointer to the receivable in file 430 With IB*2.0*433/PRCA*4.5*270 Preserve Claim # Patch, this variable was changed from Output to Both. If the user comes from the new CRD option, ARREC will be set to the internal bill# of the copied FROM claim/bill. VARIABLES: PRCASV('ARBIL') TYPE: Both VARIABLES DESCRIPTION: Bill number of the receivable. With IB*2.0*433/PRCA*4.5*270 Preserve Claim # Patch, this variable was changed from Output to Both. If the user comes from the new CRD option, ARBIL will be set to the external bill# of the copied FROM claim/bill. VARIABLES: PRCASV('ARCRD') TYPE: Input VARIABLES DESCRIPTION: This variable is a flag indicating that the user came from the new CRD option. CRD is the new Correct Rejected/Denied Claim option introduced with IB*2.0*433/PRCA*4.5*270 - Preserve Claim #. If the user came from CRD (PRCASV('ARCRD')=1),then the original claim/AR# will be assigned an iteration # (ie. -01), and the newly created claim/AR entry will retain the original claim#. VARIABLES: PRCASV('ARITN') TYPE: Input VARIABLES DESCRIPTION: This new variable was introduced w/IB*2.0*433/PRCA*4.5*270-Preserve Claim #. If the user came from the new CRD option (Correct/Reject Denied Claim), this variable will contain the original bill# PLUS the iteration # that needs to be added to the corrected FROM claim/bill# (ie. K00001-01). SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany DATE ACTIVATED: AUG 06, 2010 DATE/TIME EDITED: AUG 05, 2010@11:40 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: MULLER,RICHARD DATE/TIME EDITED: AUG 06, 2010@17:05 ACTION: APPROVED AT THE REQUEST OF: FIAMENGO,GRACE WITH CONCURRENCE OF: SIMONS,MARY NUMBER: 387 IA #: 387 DATE CREATED: MAR 15, 1994 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCASVC1 NAME: DBIA387 ORIGINAL NUMBER: 387 ID: PRCASVC1 GENERAL DESCRIPTION: These calls are made when a bill is cancelled in Integrated Billing. If the receivable has the AR Status of New Bill, Bill Incomplete, or Returned From AR (NEW), the bill is cancelled using the call D CANCEL^PRCASVC1; otherwise, the bill is amended using the call D AMEND^PRCASVC1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15779820 COMPONENT/ENTRY POINT: CANCEL VARIABLES: PRCASV('AMT') TYPE: Input VARIABLES DESCRIPTION: Amended Amount (difference between original amount and the amend ment total amount) VARIABLES: PRCASC('DATE') TYPE: Input VARIABLES DESCRIPTION: Date Bill Amended VARIABLES: PRCASC('BY') TYPE: Input VARIABLES DESCRIPTION: Amended by (points to 200) VARIABLES: PRCASV('ARREC') TYPE: Input VARIABLES DESCRIPTION: Pointer to the receivable in file 430 VARIABLES: PRCASV('COMMENT') TYPE: Input VARIABLES DESCRIPTION: Comments for the amendment COMPONENT/ENTRY POINT: AMEND COMPONENT DESCRIPTION: Same input variables as entry point CANCEL. COMPONENT/ENTRY POINT: STATUS COMPONENT DESCRIPTION: This call is used to set the Current Status (#8) of a receivable in the Accounts Receivable (#430) file when a CHAMPVA subsistence charge is being created. The Current Status is set to PENDING CALM CODE, if the site is running AR v4.0 (or lower). Otherwise, the Current Status is set to ACTIVE. VARIABLES: PRCASV('ARREC') TYPE: Input VARIABLES DESCRIPTION: This is a pointer to the receivable in file #430 which needs to have the Current Status updated. VARIABLES: PRCASV('STATUS') TYPE: Input VARIABLES DESCRIPTION: This is a pointer to the Current Status in the ACCOUNTS RECEIVABLE TRANS.TYPE (#430.3) file to which the receivable is being updated. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 388 IA #: 388 DATE CREATED: MAR 15, 1994 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RCFNO3(X) NAME: DBIA388 ORIGINAL NUMBER: 388 ID: RCFNO3(X) GENERAL DESCRIPTION: This call is used to find the internal entry number for a bill in file #430, so it may be used as input to the function $$PUR^PRCAFN(X). Note that a check is done to determine if the routine RCFN03 exists on the system before the call is made. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$BIEN COMPONENT DESCRIPTION: Returns the ien for the bill in file 430. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: AR Bill number. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 389 IA #: 389 FILE NUMBER: 430 GLOBAL ROOT: PRCA(430, DATE CREATED: MAR 15, 1994 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA389 ORIGINAL NUMBER: 389 ID: PRCA(430, GLOBAL REFERENCE: PRCA(430,'B',BN) GLOBAL DESCRIPTION: Request direct access to the "B" cross reference of the ACCOUNTS RECEIVABLE (#430) file to determine the internal entry number for a receivable [S IEN=$O(^PRCA(430,"B",BN,0))]. This call is made when purging Pharmacy copay charges, in order to determine the input for the function call $$PUR^PRCAFN(IEN). Integrated Billing will no longer need direct access to this cross reference once the routine RCFN03 is available. This routine is checked for and called to get the same information. GLOBAL REFERENCE: PRCA(430,'AC',STS,BN) GLOBAL DESCRIPTION: This cross-reference is used by various reports in the Diagnostic Measures module to retrieve receivables of a specific status, i.e. Active. Some examples of the reports that use this cross-reference are: First Party Follow-up Report, Repayment Plan Follow-up Report, AR Productivity Report, among others. GLOBAL REFERENCE: PRCA(430,BN,0) FIELD NUMBER: .01 FIELD NAME: BILL NO. LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 9 FIELD NAME: DEBTOR LOCATION: 0;9 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: CATEGORY LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 10 FIELD NAME: DATE BILL PREPARED LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: These fields are being displayed in various reports in the Diagnostic Measures module. Some examples of these reports are: Miscellaneous Bills Follow-up report, Repayment Plan report, among others. GLOBAL REFERENCE: PRCA(430,BN,7) FIELD NUMBER: 71 FIELD NAME: PRINCIPAL BALANCE LOCATION: 7;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 72 FIELD NAME: INTEREST BALANCE LOCATION: 7;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 73 FIELD NAME: ADMINISTRATIVE COST BALANCE LOCATION: 7;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 74 FIELD NAME: MARSHAL FEE LOCATION: 7;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 75 FIELD NAME: COURT COST LOCATION: 7;5 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: The fields 71-75 are being used in the calculation of the account balance for the patient in two Diagnostic Measures reports: First Party Follow-up and Repayment Plan Follow-up reports. GLOBAL REFERENCE: PRCA(430,BN,9) FIELD NUMBER: 97 FIELD NAME: PROCESSED BY (SERVICE) LOCATION: 9;8 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field is being displayed by the Miscellaneous Bills Follow-up report. This report belongs to the Diagnostic Measures module. GLOBAL REFERENCE: PRCA(430,BN,12) FIELD NUMBER: 121 FIELD NAME: DATE SENT TO DMC LOCATION: 12;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field is used by the First Party Follow-up report in the Diagnostic Measures module. It uses it to identify if a receivable has been referred to DMC. GLOBAL REFERENCE: PRCA(430,BN,14) FIELD NUMBER: 141 FIELD NAME: DATE BILL REFERRED TO TOP LOCATION: 14;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used by the First Party Follow-up report in the Diagnostic Measures module. It uses it to identify if a receivable has been referred to TOP. GLOBAL REFERENCE: PRCA(430,BN,6) FIELD NUMBER: 64 FIELD NAME: REFERRAL DATE LOCATION: 6;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used by the First Party Follow-up report in the Diagnostic Measures module. It uses it to identify if a receivable has been referred to RC. GENERAL DESCRIPTION: Integrated Billing has permission to reference this file in a ^DIC call to do a look-up on the bill number. It also has permission to access the following fields and cross-references: STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32843534 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 390 IA #: 390 FILE NUMBER: 442 GLOBAL ROOT: PRC(442, DATE CREATED: MAR 16, 1994 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA390 ORIGINAL NUMBER: 390 ID: PRC(442, GLOBAL REFERENCE: PRC(442,0) FIELD NUMBER: .07 FIELD NAME: PRIMARY 2237 LOCATION: 0;12 ACCESS: Read w/Fileman GLOBAL REFERENCE: PRC(442,7) FIELD NUMBER: .5 FIELD NAME: SUPPLY STATUS LOCATION: 7;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: See DBIA 375. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City NUMBER: 391 IA #: 391 FILE NUMBER: 8984.1 GLOBAL ROOT: XT(8984.1, DATE CREATED: MAR 16, 1994 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA391 ORIGINAL NUMBER: 391 ID: XT(8984.1, GLOBAL REFERENCE: XT(8984.1,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: ENTRY LOCATION: 0;2 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: XT(8984.1,'B', GENERAL DESCRIPTION: AMIE v2.6 will be using the MTLU functionality from the Kernel tool kit in order to do a look up on the Disability Condition file (#31). As part of the functionality provided to the users, there needs to be a set of distributed Keywords, Synonyms and short cuts. AMIE would like to distribute these lists in,a post init fashion with little to no user intervention. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 392 IA #: 392 FILE NUMBER: 8984.2 GLOBAL ROOT: XT(8984.2, DATE CREATED: MAR 16, 1994 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA392 ORIGINAL NUMBER: 392 ID: XT(8984.2, GLOBAL REFERENCE: XT(8984.2,D0,0) FIELD NUMBER: .01 FIELD NAME: FREQUENTLY USED NARRATIVE LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: ENTRY LOCATION: 0;2 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: XT(8984.2,'B', GENERAL DESCRIPTION: AMIE v2.6 will be using the MTLU functionality from the Kernel tool kit in order to do a look up on the Disability Condition file (#31). As part of the functionality provided to the users, there needs to be a set of distributed Keywords, Synonyms and short cuts. AMIE would like to distribute these lists in a post init fashion with little to no user intervention. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 393 IA #: 393 FILE NUMBER: 8984.3 GLOBAL ROOT: XT(8984.3, DATE CREATED: MAR 16, 1994 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA393 ORIGINAL NUMBER: 393 INTEGRATION REFERENCES LIST MAR 18, 2015@11:24 PAGE 2 -------------------------------------------------------------------------------- ID: XT(8984.3, GLOBAL REFERENCE: XT(8984.3,D0,0) FIELD NUMBER: .01 FIELD NAME: TERM LOCATION: 0;1 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: XT(8984.3,'B', GLOBAL REFERENCE: XT(8984.3,D0,1,'B', GENERAL DESCRIPTION: AMIE v2.6 will be using the MTLU functionality from the Kernel tool kit in order to do a look up on the Disability Condition file (#31). As part of the functionality provided to the users, there needs to be a set of distributed Keywords, Synonyms and short cuts. AMIE would like to distribute these lists in a post init fashion with little to no user intervention. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 394 IA #: 394 FILE NUMBER: 8984.4 GLOBAL ROOT: XT(8984.4, DATE CREATED: MAR 16, 1994 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA394 ORIGINAL NUMBER: 394 ID: XT(8984.4, GLOBAL REFERENCE: XT(8984.4,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: AMIE v2.6 will be using the MTLU functionality from the Kernel tool kit in order to do a look up on the Disability Condition file (#31). As part of the functionality provided to the users, there needs to be a set of distributed Keywords, Synonyms and short cuts. AMIE would like to distribute these lists in a post init fashion with little to no user intervention. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 395 IA #: 395 GLOBAL ROOT: DD( DATE CREATED: MAR 23, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA395 ORIGINAL NUMBER: 395 ID: DD( GLOBAL REFERENCE: DD(8984.1,.02,'V', GLOBAL REFERENCE: DD(8984.2,.02,'V', GENERAL DESCRIPTION: VA FileMan grants this integration request. The following calls are allowed within the AMIE package. CHK+13^DVBAPLL S DIC="^DD(8984.1,.02,""V"",",DIC(0)="Z",D="P",X=VAR1 D IX^DIC CHK+19^DVBAPLL S DIC="^DD(8984.2,.02,""V"",",DIC(0)="Z",D="P",X=VAR1 D IX^DIC ADDV+1^DVBAPLL Calls using ^DIC and ^DIE to update the variable pointer field in the Local Keyword and Local Synonym file for use with MTLU. The ^DIE call is fully compatible with the interactive way of creating variable pointer type fields. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 396 IA #: 396 DATE CREATED: APR 04, 1994 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBCNSP2 NAME: DBIA396 ORIGINAL NUMBER: 396 ID: IBCNSP2 GENERAL DESCRIPTION: This agreement was updated on 3/3/97 to convert it from an 'Other' type agreement (to support IB v2.0 installation requirements with Fee Basis) to a 'Routine' type agreement to support IB's callable routine IBCNSP2. Please note that this agreement also supercedes agreement DBIA226-C which Fee Basis held with the Registration package. The terms under which IB exported the Fee Basis patch FB*3*5 are listed below, so they are not lost: IB will transport routine FBUINS in routine IB20PT8C, and ZSave as FBUINS during the installation process if version 3 is running and patch 5 has not been installed. Patch 5 of Fee contains the following special instructions: - Do not apply if version 3 of Fee is installed but Version 2 has not been installed. - If version 3 of Fee has been installed, IB 2 will automatically apply this patch. There is no need to apply. - If you install version 2 of IB prior to installing version 3 of Fee, then this patch needs to be applied prior to allowing Fee users back on the system. Verification of FB*3*5 is pending this agreement. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23159831 COMPONENT/ENTRY POINT: FEE COMPONENT DESCRIPTION: This entry point is called from within the Fee Basis package to add patient insurance policy information for patients. Please note that new insurance policies may be added, but existing patient policy information cannot be edited. This call also allows Insurance Plan information in file #355.3 to be added and edited. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the patient in file #2 COMPONENT/ENTRY POINT: REG COMPONENT DESCRIPTION: This entry point is called from Screen 5 of the Registration process and the 10-10T Registration process to allow patient insurance policy information to be added and edited. This call also allows Insurance Plan information in file #355.3 to be added and edited. SUBSCRIBING PACKAGE: FEE BASIS ISC: Albany SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany EDITOR: MINARDI,CHRISTOPHER P NUMBER: 397 IA #: 397 FILE NUMBER: 409.95 GLOBAL ROOT: SD(409.95, DATE CREATED: APR 04, 1994 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA397 ORIGINAL NUMBER: 397 ID: SD(409.95, GENERAL DESCRIPTION: Request to export the following Scheduling files with the release of Integrated Billing v2.0: #409.95 PRINT MANAGER CLINIC SETUP Also request read and write access for all fields in these files. These files are used by the Print Manager to determine which forms should be printed for each clinic. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 398 IA #: 398 FILE NUMBER: 409.96 GLOBAL ROOT: SD(409.96, DATE CREATED: APR 04, 1994 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA398 ORIGINAL NUMBER: 398 ID: SD(409.96, GENERAL DESCRIPTION: Request to export the following Scheduling files with the release of Integrated Billing v2.0: #409.96 PRINT MANAGER DIVISION SETUP Also request read and write access for all fields in these files. These files are used by the Print Manager to determine which forms should be printed for each clinic. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany NUMBER: 399 IA #: 399 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: APR 04, 1994 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA399 ORIGINAL NUMBER: 399 ID: DPT( GLOBAL REFERENCE: DPT(D0,'S',D1,0) FIELD NUMBER: .01 FIELD NAME: CLINIC LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: The appointment clinic is listed on reports and encounter forms. FIELD NUMBER: 5 FIELD NAME: LAB DATE/TIME LOCATION: 0;3 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This field is used to determine if there was a lab stop associated with the appointment. FIELD NUMBER: 6 FIELD NAME: X-RAY DATE/TIME LOCATION: 0;4 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This field is used to determine if there was an X-RAY stop associated with the appointment. FIELD NUMBER: 7 FIELD NAME: EKG DATE/TIME LOCATION: 0;5 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This field is used to determine if there was an EKG stop associated with the appointment. FIELD NUMBER: 21 FIELD NAME: OUTPATIENT ENCOUNTER LOCATION: 0;21 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: The pointer to the outpatient encounter is used to determine the classification answers for the appointment. FIELD NUMBER: 22 FIELD NAME: ENOUNTER FORMS PRINTED LOCATION: 0;21 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This field is set by the Encounter Form utilities when a form is printed. FIELD NUMBER: 23 FIELD NAME: ENCOUNTER FORMS AS ADD-ONS LOCATION: 0;22 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This field is set by the Encounter Form utilities when the form and other reports where printed as add-ons GLOBAL DESCRIPTION: It is understood that these references will need to be changed when Scheduling's new APIs are available. GLOBAL REFERENCE: DPT(D0,'DIS',D1,0) FIELD NUMBER: 18 FIELD NAME: OUTPATIENT ENCOUNTER LOCATION: 0;18 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The pointer to the outpatient encounter is used to determine the classification answers for the registration. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 400 IA #: 400 FILE NUMBER: 40.7 GLOBAL ROOT: DIC(40.7, DATE CREATED: APR 04, 1994 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA400 ORIGINAL NUMBER: 400 ID: DIC(40.7, GLOBAL REFERENCE: DIC(40.7,D0,0) FIELD NUMBER: 1 FIELD NAME: AMIS REPORTING STOP CODE LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: The AMIS Reporting Stop Code is printed on several reports FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: This pointer is used to flag clinic stop codes as non-billable. STATUS: Active SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 402 IA #: 402 FILE NUMBER: 409.68 GLOBAL ROOT: SCE( DATE CREATED: APR 04, 1994 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA402 ORIGINAL NUMBER: 402 ID: SCE( GLOBAL REFERENCE: SCE(D0,0) FIELD NUMBER: .01 FIELD NAME: DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Determine date of encounter FIELD NUMBER: .02 FIELD NAME: PATIENT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Determine patient for encounter FIELD NUMBER: .03 FIELD NAME: CLINIC STOP CODE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Can't bill clinic stops related to dental FIELD NUMBER: .05 FIELD NAME: VISIT FILE ENTRY LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Stored for future use FIELD NUMBER: .06 FIELD NAME: PARENT ENCOUNTER LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Cannot bill child encounters FIELD NUMBER: .07 FIELD NAME: CHECK OUT PROCESS COMPLETION LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Make sure check out is complete FIELD NUMBER: .08 FIELD NAME: ORIGINATING PROCESS TYPE LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Determine type of encounter FIELD NUMBER: .09 FIELD NAME: EXTENDED REFERENCE LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Determine disposition for registrations FIELD NUMBER: .1 FIELD NAME: APPOINTMENT TYPE LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Must have billable appointment type FIELD NUMBER: .11 FIELD NAME: MEDICAL CENTER DIVISION LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Determine division of encounter FIELD NUMBER: .12 FIELD NAME: STATUS LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Only checked out encounters are billable GLOBAL REFERENCE: SCE('ADFN',DFN, GLOBAL DESCRIPTION: The "ADFN" cross-reference is used to look at all encounters for a patient on a specific date. GLOBAL REFERENCE: SCE('B', GLOBAL DESCRIPTION: The "B" cross-reference is used to find all outpatient encounters which occurred within a user-specified date range. GENERAL DESCRIPTION: This pointer is needed to retrieve data from this file when a claim is being generated. STATUS: Active MAIL MESSAGE: 23720883 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY SUBSCRIBING DETAILS: The variable SDDA will not be supported No direct references to appointments are allowed in the subscriber routine. NUMBER: 406 IA #: 406 DATE CREATED: JUN 30, 2003 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SDCO21 NAME: DBIA406 ORIGINAL NUMBER: 406 ID: SDCO21 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: CL(DFN,DATE,SDOE,.ARR) COMPONENT DESCRIPTION: This call is made to determine what classification questions should be asked for a specific patient. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: ptr to patient in file #2 VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: date to determine if classification is active. VARIABLES: SDOE TYPE: Input VARIABLES DESCRIPTION: encounter for which classification should be asked (optional - we will pass 'null' in all cases) VARIABLES: ARR(n) TYPE: Output VARIABLES DESCRIPTION: array of classifications that should be asked, where n equals the entry number in the OUTPATIENT CLASSIFICATION TYPE file (#409.41) SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: PROSTHETICS SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: EVENT CAPTURE SUBSCRIBING DETAILS: added 2/28/2012 DATE/TIME EDITED: FEB 29, 2012@13:44 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: NABER,DAVID WITH CONCURRENCE OF: HARVEY,JULIE NUMBER: 407 IA #: 407 DATE CREATED: APR 04, 1994 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SDCOU2 NAME: DBIA407 ORIGINAL NUMBER: 407 ID: SDCOU2 CREATOR: SCHLEHUBER,CAMERON STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$EX(X,Y) COMPONENT DESCRIPTION: Output: Is the clinic stop exempt from classification? [1-Yes|0-No] This call is made to determine if an individual clinic stop, which is being billed the Means Test copayment, is exempt from classification. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Pointer to clinic stop code in file #40.7 VARIABLES: Y TYPE: Input VARIABLES DESCRIPTION: Date on which clinic stop may be exempt. SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany DBA Comments: RESTORED FROM RETIRED AS PER ED WOLF DATE ACTIVATED: MAR 15, 2007 DATE/TIME EDITED: MAR 15, 2007@21:00 ACTION: APPROVED AT THE REQUEST OF: WOLF,ED NUMBER: 409 IA #: 409 FILE NUMBER: 409.42 GLOBAL ROOT: SDD(409.42, DATE CREATED: APR 04, 1994 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA409 ORIGINAL NUMBER: 409 ID: SDD(409.42, GLOBAL REFERENCE: SDD(409.42,D0,0) FIELD NUMBER: .01 FIELD NAME: TYPE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The type indicates the classification: 1 = Agent Orange 2 = Ionizing Radiation 3 = Service Connected 4 = Environmental Contaminants FIELD NUMBER: .03 FIELD NAME: VALUE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The value indicates whether care was related to the specified exposure: 1 = Yes otherwise, No STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 410 IA #: 410 FILE NUMBER: 409.72 GLOBAL ROOT: SD(409.72, DATE CREATED: APR 04, 1994 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA410 ORIGINAL NUMBER: 410 ID: SD(409.72, GLOBAL REFERENCE: SD(409.72,D0,0) FIELD NUMBER: .05 FIELD NAME: ACTIVE STATUS LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The status is used to determine if an ambulatory procedure is active GLOBAL REFERENCE: SD(409.72,'AIVDT', GLOBAL DESCRIPTION: The "AIVDT" cross reference is used to determine if an ambulatory procedure is active on a specific date. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 412 IA #: 412 FILE NUMBER: 31 GLOBAL ROOT: DIC(31, DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: HINQ CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA412 ORIGINAL NUMBER: 412 ID: DIC(31, GENERAL DESCRIPTION: AMIE v2.6 will use the Disability Condition file extensively in a portion of its new functionality. AMIE will need to change and access the file in various ways that will require an integration agreement. In order to use MTLU to its fullest extent AMIE would need to add a new field 'LONG DESCRIPTION' to the Disability Condition file (#31). This field would be a free text field 1-200 characters, on the '1' node. It would not be a multiple or used during lookup. There would be a MUMPS cross reference (ADVB) in order to enhance an MTLU look up. This MUMPS cross reference would be of the format defined in the Kernel 7.2 Tool Kit manual. Ability to carry the new field in the AMIE init. Ability to populate the LONG DESCRIPTION field during the AMIE post init. Access to the 'C' cross reference and LONG DESCRIPTION field for quick look up and comparison during the post init. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 413 IA #: 413 DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGRPU1 NAME: DBIA413 ORIGINAL NUMBER: 413 ID: DGRPU1 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 36478613 COMPONENT/ENTRY POINT: QUES(DFN,DGQCODE) COMPONENT DESCRIPTION: If DGQCODE="ADD1" then: The edit is to the patient's permanent address. QUES^DGRPU1 will edit the following fields as the patient's permanent address: Field Number Field Name ============ ========== .111 STREET ADDRESS [LINE 1] .112 STREET ADDRESS [LINE 2] .113 STREET ADDRESS [LINE 3] .114 CITY .115 STATE .1112 ZIP+4 .117 COUNTY .131 PHONE NUMBER [RESIDENCE] .132 PHONE NUMBER [WORK] The permanent address fields are those currently defined by the indicated MAS routines and are subject to change per the redefinition of those fields by that routine. 2) If DGQCODE= ADD4 then: The editing is of the patient's confidential address fields. Fee Basis will be calling QUES^DGRPU1 to allow user editing of the patient's confidential address information in the Patient (#2) file. QUES^DGRPU1(DFN, ADD4 ) will prompt the user for the following fields: Field # Field Name ====== ========= .1411 CONFIDENTIAL STREET [LINE 1] .1412 CONFIDENTIAL STREET [LINE 2] .1413 CONFIDENTIAL STREET [LINE 3] .1414 CONFIDENTIAL ADDRESS CITY .1415 CONFIDENTIAL ADDRESS STATE .1416 CONFIDENTIAL ADDRESS ZIP CODE .1417 CONFIDENTIAL START DATE .1418 CONFIDENTIAL END DATE .14105 CONFIDENTIAL ADDRESS ACTIVE? .14111 CONFIDENTIAL ADDRESS COUNTY CONFIDENTIAL ADDRESS CATEGORY Multiple (#2.141) .01 CONFIDENTIAL ADDRESS CATEGORY 1 CONFIDENTIAL CATEGORY ACTIVE VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the patyent in file #2 VARIABLES: DGQCODE TYPE: Input VARIABLES DESCRIPTION: Indicates that QUES^DGRPU1 is to edit the patient's permanent address. VARIABLES: DGCHANGE TYPE: Output VARIABLES DESCRIPTION: = 1 if data modified = 0 if data NOT modified To be killed after the call. VARIABLES: DGERR TYPE: Output VARIABLES DESCRIPTION: Error value. To be killed after the call. SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany SUBSCRIBING DETAILS: AMIE may only call with DGQCODE="ADD1" SUBSCRIBING PACKAGE: FEE BASIS SUBSCRIBING DETAILS: FEE BASIS may only call with DGQCODE="ADD4" SUBSCRIBING PACKAGE: SCHEDULING NUMBER: 414 IA #: 414 DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA414 ORIGINAL NUMBER: 414 GENERAL DESCRIPTION: Request to export the INSURANCE TYPE (#.3121) multiple of the PATIENT (#2) file with the release of Integrated Billing v2.0. This sub-dictionary is maintained in the PATIENT file for Integrated Billing, and may be addressed by Integrated Billing as needed. Integrated Billing agrees to maintain supported references to this data for other applications, as well as Registration. This would.include the "AB" cross reference on the .01 field of the sub-dictionary (^DPT("AB",). STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 415 IA #: 415 DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA415 ORIGINAL NUMBER: 415 GENERAL DESCRIPTION: The INSURANCE COMPANY (#36) file will now be released exclusively by Integrated Billing unless otherwise agreed upon. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 416 IA #: 416 FILE NUMBER: 37 GLOBAL ROOT: DIC(37, DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA416 ORIGINAL NUMBER: 416 ID: DIC(37, GLOBAL REFERENCE: DIC(37,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This pointer is used to flag dispositions as non-billable. The disposition name is printed on several outputs. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 417 IA #: 417 FILE NUMBER: 40.8 GLOBAL ROOT: DG(40.8, DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA417 ORIGINAL NUMBER: 417 ID: DG(40.8, GLOBAL REFERENCE: DG(40.8, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: Used to associate a charge or procedure with a location. FIELD NUMBER: .07 FIELD NAME: INSTITUTION FILE POINTER LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Display the institution associated with a division. FIELD NUMBER: 3 FIELD NAME: OUTPATIENT ONLY LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Determine if the location of care was in the hospital or clinic. FIELD NUMBER: .001 FIELD NAME: NUMBER LOCATION: ENTRY IEN ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: FACILITY NUMBER LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23720883 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Albany SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: ONCOLOGY SUBSCRIBING DETAILS: added 8/23/2010 SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING DETAILS: ADDED 5/15/2009 SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING DETAILS: ADDED 9/28/2009 DATE/TIME EDITED: AUG 23, 2010@11:50 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: RIKARD,KENNETH WITH CONCURRENCE OF: MULLER,RICHARD NUMBER: 418 IA #: 418 FILE NUMBER: 45 GLOBAL ROOT: DGPT( DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA418 ORIGINAL NUMBER: 418 ID: DGPT( GLOBAL REFERENCE: DGPT(D0,0) FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: This pointer is needed to find the associated PTF record for a claim and extract the required data. FIELD NUMBER: 2 FIELD NAME: ADMISSION DATE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The admission date is used to the end of the date range for a claim FIELD NUMBER: 4 FIELD NAME: FEE BASIS LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to determine if the PTF update routine must be called (not called for Fee admissions). FIELD NUMBER: 6 FIELD NAME: STATUS LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to determine if the PTF record has been closed. GLOBAL REFERENCE: DGPT(D0,70) FIELD NUMBER: 70 FIELD NAME: DISCHARGE DATE LOCATION: 70;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The discharge date is used to determine the end of the date range for the claim. FIELD NUMBER: 71 FIELD NAME: DISCHARGE SPECIALTY LOCATION: 70;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The discharge specialty is used to determine if the admission is billable. FIELD NUMBER: 72 FIELD NAME: TYPE OF DISPOSITION LOCATION: 70;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The type of disposition is used to determine the discharge status for the claim. FIELD NUMBER: 79 FIELD NAME: DXLS LOCATION: 70;10 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The DXLS is printed on the Amb Proc check off sheet. FIELD NUMBER: 79.16 FIELD NAME: ICD 2 LOCATION: 70;16 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The ICD 2 is printed on the Amb Proc check off sheet. FIELD NUMBER: 79.17 FIELD NAME: ICD 3 LOCATION: 70;17 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The ICD 3 is printed on the Amb Proc check off sheet. FIELD NUMBER: 79.1 FIELD NAME: PROVIDER LOCATION: 70;15 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.18 FIELD NAME: ICD 4 LOCATION: 70;18 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.19 FIELD NAME: ICD 5 LOCATION: 70;19 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.201 FIELD NAME: ICD 6 LOCATION: 70;20 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.21 FIELD NAME: ICD 7 LOCATION: 70;21 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.22 FIELD NAME: ICD 8 LOCATION: 70;22 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.23 FIELD NAME: ICD 9 LOCATION: 70;23 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.24 FIELD NAME: ICD 10 LOCATION: 70;24 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.25 FIELD NAME: TREATED FOR SC CONDITION LOCATION: 70;25 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DGPT('B', GLOBAL DESCRIPTION: The "B" cross-reference is used to find a specific PTF record for a patient. GLOBAL REFERENCE: DGPT('AAD', GLOBAL DESCRIPTION: The "AAD" cross reference is used to find all admissions for a patient within a specified date range. GLOBAL REFERENCE: DGPT('AFEE', GLOBAL DESCRIPTION: The "AFEE" cross reference is used to find all Fee admissions for a patient within a specified date range. GLOBAL REFERENCE: DGPT(D0,'M',D1,0) FIELD NUMBER: 2 FIELD NAME: LOSING SPECIALTY LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The specialty is used to determine if a 501 movement is billable. FIELD NUMBER: 3 FIELD NAME: LEAVE DAYS LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Leave days are used to determine the number of billable days of care. FIELD NUMBER: 4 FIELD NAME: PASS DAYS LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Pass days are used to determine the number of billable days of care. FIELD NUMBER: 5 FIELD NAME: ICD 1 LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This code is included on the claim. FIELD NUMBER: 6 FIELD NAME: ICD 2 LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This code is included on the claim. FIELD NUMBER: 7 FIELD NAME: ICD 3 LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This code is included on the claim. FIELD NUMBER: 8 FIELD NAME: ICD 4 LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This code is included on the claim. FIELD NUMBER: 9 FIELD NAME: ICD 5 LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This code is included on the claim. FIELD NUMBER: 10 FIELD NAME: MOVEMENT DATE LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The movement date is used to determine if the 501 movement is within the date range of the bill FIELD NUMBER: 18 FIELD NAME: TREATED FOR SC CONDITION LOCATION: 0;18 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This flag is used to determine if the 501 movement is billable. GLOBAL REFERENCE: DGPT(D0,'M','AM', GLOBAL DESCRIPTION: The "AM" cross reference is used to find all 501 movements based on a specified date range. GLOBAL REFERENCE: DGPT(D0,'P',D1,0) FIELD NUMBER: .01 FIELD NAME: PROCEDURE DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The procedure date is included on the claim. FIELD NUMBER: 4 FIELD NAME: PROCEDURE CODE 1 LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This code is included on the claim. FIELD NUMBER: 5 FIELD NAME: PROCEDURE CODE 2 LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This code is included on the claim FIELD NUMBER: 6 FIELD NAME: PROCEDURE CODE 3 LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This code is included on the claim FIELD NUMBER: 7 FIELD NAME: PROCEDURE CODE 4 LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This code is included on the claim FIELD NUMBER: 8 FIELD NAME: PROCEDURE CODE 5 LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This code is included on the claim GLOBAL REFERENCE: DGPT(D0,'S',D1,0) FIELD NUMBER: .01 FIELD NAME: SURGERY/PROCEDURE DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The surgery/procedure date is included on the claim. FIELD NUMBER: 8 FIELD NAME: OPERATION CODE 1 LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This code is included on the claim FIELD NUMBER: 9 FIELD NAME: OPERATION CODE 2 LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This code is included on the claim FIELD NUMBER: 10 FIELD NAME: OPERATION CODE 3 LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This code is included on the claim FIELD NUMBER: 11 FIELD NAME: OPERATION CODE 4 LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This code is included on the claim FIELD NUMBER: 12 FIELD NAME: OPERATION CODE 5 LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This code is included on the claim GLOBAL REFERENCE: DGPT(D0,300) FIELD NUMBER: 300.06 FIELD NAME: CURRENT FUNCTIONAL ASSESSMENT LOCATION: 300;6 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DGPT(D0,'M',D1,'P') FIELD NUMBER: 20 FIELD NAME: TRANSFER DRG LOCATION: P;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 24 FIELD NAME: PROVIDER LOCATION: P;5 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DGPT(D0,535,D1,0) FIELD NUMBER: 6 FIELD NAME: LOSING WARD LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 10 FIELD NAME: MOVEMENT DATE LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DGPT('AF', GLOBAL DESCRIPTION: Admission date cross-reference. GLOBAL REFERENCE: DGPT('ADS', GLOBAL DESCRIPTION: For discharge date ranges STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29756507 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: LAB SERVICE ISC: Birmingham SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE SUBSCRIBING DETAILS: AR references only the ADMISSION DATE and the DISCHARGE DATE. SUBSCRIBING PACKAGE: ONCOLOGY SUBSCRIBING DETAILS: added 2/25/09 EDITOR: LOUCK,KEVIN DBA Comments: 09/16/14 DT: Added Kevin Louck as editor.The ICD-10 PTF Modifications project (DG*5.3*884) will be expanding on the work originally done by Alan Skinner for released patch DG*5.3*850. The ICD-10 PTF Modifications project will also be making the changes in IB and Lab to consume and utilize the new fields. DATE/TIME EDITED: FEB 25, 2009@16:29 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: RIKARD,KEN WITH CONCURRENCE OF: MULLER,RICHARD DATE/TIME EDITED: SEP 16, 2014@11:48 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: LOUCK,KEVIN NUMBER: 419 IA #: 419 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA419 ORIGINAL NUMBER: 419 ID: DGPM( GLOBAL REFERENCE: DGPM(D0,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This pointer is needed to associate Claims Tracking and special inpatient billing case records with an admission. Movement date/time is displayed on several reports. FIELD NUMBER: .02 FIELD NAME: TRANSACTION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The transaction type is printed on several reports. FIELD NUMBER: .03 FIELD NAME: PATIENT LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Determine the patient for the movement FIELD NUMBER: .06 FIELD NAME: WARD LOCATION LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Ward location is printed on several reports. FIELD NUMBER: .09 FIELD NAME: FACILITY TREATING SPECIALTY LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Billing for the movement is dependent upon treating specialty. FIELD NUMBER: .11 FIELD NAME: ADMITTED FOR SC CONDITION? LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Determine if the admission is related to an SC condition. FIELD NUMBER: .16 FIELD NAME: PTF ENTRY LOCATION: 0;16 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Determine the associated PTF entry for an admission. FIELD NUMBER: .17 FIELD NAME: DISCHARGE/CHECK-OUT MOVEMENT LOCATION: 0;17 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Determine the discharge movement for an admission. FIELD NUMBER: .14 FIELD NAME: ADMISSION/CHECK-IN MOVEMENT LOCATION: 0;14 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The field is used to find the pointer to the admission movement that is associated with a discharge movement. GLOBAL REFERENCE: DGPM('AMV1', GLOBAL DESCRIPTION: The "AMV1" cross-reference is used to find all admissions within a specified date/time range. GLOBAL REFERENCE: DGPM('AMV2', GLOBAL DESCRIPTION: The "AMV2" cross-reference is used to find all transfers within a specified date/time range. GLOBAL REFERENCE: DGPM('AMV3', GLOBAL DESCRIPTION: The "AMV3" cross-reference is used to find all discharges within a specified date/time range. GLOBAL REFERENCE: DGPM('ATID1', GLOBAL DESCRIPTION: The "ATID1" cross-reference is used to find all admissions for a patient. GLOBAL REFERENCE: DGPM('ATS', GLOBAL DESCRIPTION: The "ATS" cross-reference is used to find the treating specialty for a patient for a given date/time. GLOBAL REFERENCE: DGPM('APTF', GLOBAL DESCRIPTION: The "APTF" cross-reference is used to find the pointer to the admission movement for a specific PTF entry. GLOBAL REFERENCE: DGPM('ATID3',DFN, GLOBAL DESCRIPTION: The "ATID3" cross-reference is used to find all discharges that are associated with a patient (where DFN is a pointer to the patient in file #2). GLOBAL REFERENCE: DGPM('ATT3', GLOBAL DESCRIPTION: The "ATT3" cross-reference is used to find all discharges which occurred during a user-specified date range. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23720883 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL SUBSCRIBING PACKAGE: SOCIAL WORK SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING DETAILS: LR ADDED 3/21/11 DBA Comments: 12/24/14-MM: Phil Burkhalter from Scheduling Calendar View said the MBAA PATIENT ADMISSIONS RPC is not included in this release of SCV or VAR2. Request can be withdrawn. DATE/TIME EDITED: APR 10, 2009@15:49 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MCDEARMON,JAMES WITH CONCURRENCE OF: MULLER,RICHARD DATE/TIME EDITED: MAR 21, 2011@09:05 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SMULLEN,GEOFFREY WITH CONCURRENCE OF: KOPECKY,STEVE NUMBER: 420 IA #: 420 DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTU NAME: DBIA420 ORIGINAL NUMBER: 420 ID: DGMTU STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: DIS COMPONENT DESCRIPTION: There is no varible output from this call. The call is used to display to the screen current Means Test information for a patient when creating a bill. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the patient in file #2 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 421 IA #: 421 DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGUTL2 NAME: DBIA421 ORIGINAL NUMBER: 421 ID: DGUTL2 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: PLASIH COMPONENT DESCRIPTION: This call is used to determine the number of days in an admission which are not billable on a claim. VARIABLES: DGBDT TYPE: Input VARIABLES DESCRIPTION: Begin date of date range VARIABLES: DGEDT TYPE: Input VARIABLES DESCRIPTION: End date of date range VARIABLES: DGADM TYPE: Input VARIABLES DESCRIPTION: Admission date VARIABLES: DGPMCA TYPE: Input VARIABLES DESCRIPTION: Pointer to corresponding admission in the Patient Movement (405) file. VARIABLES: DGREC TYPE: Output VARIABLES DESCRIPTION: Number of days on pass, leave and ASIH for a dage range within an admission. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 422 IA #: 422 DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGPTUTL NAME: DBIA422 ORIGINAL NUMBER: 422 ID: DGPTUTL STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: UPDT COMPONENT DESCRIPTION: There is no variable output from this call. The call is used to update the movements on the PTF record before the automatic bill calculator determines the charges for the admission. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the patient in file #2 VARIABLES: PTF TYPE: Input VARIABLES DESCRIPTION: Pointer to the PTF record in file 45. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 423 IA #: 423 DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTCOU1 NAME: DGMTCOU1 - Medication Copay Exemption API ORIGINAL NUMBER: 423 ID: DGMTCOU1 CREATOR: BRICKER,DENNIS STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 53912657 COMPONENT/ENTRY POINT: $$AUTOINFO(DFN) COMPONENT DESCRIPTION: Output: The following string of characteristics for a patient: 1^2^3^4^5^6^7^8^9^10, where 1 = Pt SC>50% [1-yes|0 or null-no] 2 = Receives Aid & Attendance [1-yes|0 or null-no] 3 = Receives Housebound benefits [1-yes|0 or null-no] 4 = Receives VA Pension [1-yes|0 or null-no] 5 = Receives Military Disability Retirement [1-yes|0 or null-no] 6 = Non-veteran [1-yes|0 or null-no] 7 = Inpatient [1-yes|0 or null-no] (not used by IB) 8 = Former POW veteran [1-yes|0 or null-no] 9 = Unemployable veteran [1-yes|0 or null-no] 10 = Catastrophically Disabled veteran [1-yes|0 or null-no] This call is used to determine if a patient is automatically exempt from Pharmacy copay. COMPONENT/ENTRY POINT: $$LST(DFN,DATE,IND) COMPONENT DESCRIPTION: Output: The following string of characteristics for a patient's Means Test: 1^2^3^4^5, where 1 = Pointer to the test in file #408.31 2 = Date of Test 3 = Test Status Name 4 = Test Status Code 5 = Type of Test used This call is used to determine which Means Test or Copay Test should be used to determine if a patient is exempt from Pharmacy copay based on reported income. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the patient in file #2. VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: Desired date to return Means test data VARIABLES: IND TYPE: Input VARIABLES DESCRIPTION: Indicator to determine what types of tests to use: 1 -> Means Tests only 2 -> Copay Tests only else -> both Means Tests and Copay Tests SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany DBA Comments: 20110303 JSHARVEY - Field " Catastrophically Disabled" veteran added to the returned data string. DATE ACTIVATED: MAR 04, 2011 DATE/TIME EDITED: MAR 03, 2011@14:25 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: BRICKER,DENNIS WITH CONCURRENCE OF: ZEIGLER,ED DATE/TIME EDITED: MAR 04, 2011@13:11 ACTION: APPROVED AT THE REQUEST OF: BRICKER,DENNIS WITH CONCURRENCE OF: ZEIGLER,ED NUMBER: 424 IA #: 424 DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTU11 NAME: DBIA424 ORIGINAL NUMBER: 424 ID: DGMTU11 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: GETREL(DFN,IND,DATE) COMPONENT DESCRIPTION: The call is used to determine the spouse relation so that the spouse name and SSN may be retrieved. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the patient in file 2 VARIABLES: IND TYPE: Input VARIABLES DESCRIPTION: Indicator to determine what types of dependents toeturn data for (input is always 's' for spouse). VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: Desired effective date to return relations data. VARIABLES: DGREL('S') TYPE: Output VARIABLES DESCRIPTION: Pointer to the spouse reference in the patient relation file (408.12) SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 425 IA #: 425 DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTU1 NAME: DBIA425 ORIGINAL NUMBER: 425 ID: DGMTU1 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$NAME(IND) COMPONENT DESCRIPTION: This function returns the spouse name, which is displayed on a report. VARIABLES: IND TYPE: Input VARIABLES DESCRIPTION: Pointer to the spouse reference in the patient relation file (408.12) COMPONENT/ENTRY POINT: $$SSN(IND) COMPONENT DESCRIPTION: This function returns the spouse Social Security Number, which is displayed on a report. VARIABLES: IND TYPE: Input VARIABLES DESCRIPTION: Pointer to the spouse reference in the patient relation file (408.12) SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 426 IA #: 426 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA426 ORIGINAL NUMBER: 426 ID: DPT( GLOBAL REFERENCE: DPT(D0,.11) FIELD NUMBER: .111 FIELD NAME: STREET ADDRESS [LINE 1] LOCATION: .11;1 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Printed on screens and bills FIELD NUMBER: .112 FIELD NAME: STREET ADDRESS [LINE 2] LOCATION: .11;2 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Printed on screens and bills FIELD NUMBER: .113 FIELD NAME: STREET ADDRESS [LINE 3] LOCATION: .11;3 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Printed on screens and bills FIELD NUMBER: .114 FIELD NAME: CITY LOCATION: .11;4 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Printed on screens and bills FIELD NUMBER: .115 FIELD NAME: STATE LOCATION: .11;5 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Printed on screens and bills FIELD NUMBER: .1112 FIELD NAME: ZIP+4 LOCATION: .11;12 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Printed on screens and bills FIELD NUMBER: .117 FIELD NAME: COUNTY LOCATION: .11;7 ACCESS: Write w/Fileman GLOBAL REFERENCE: DPT(D0,.13) FIELD NUMBER: .131 FIELD NAME: PHONE NUMBER [RESIDENCE] LOCATION: .13;1 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Printed on screens and bills FIELD NUMBER: .132 FIELD NAME: PHONE NUMBER [WORK] LOCATION: .13;2 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Printed on screens and bills GLOBAL REFERENCE: DPT(D0,.121) FIELD NUMBER: .12105 FIELD NAME: TEMPORARY ADDRESS ACTIVE? LOCATION: .121;9 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Used to determine if the patient's temporary address should be used on screens and bills. FIELD NUMBER: .1215 FIELD NAME: TEMPORARY STATE LOCATION: .121;5 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Used as an indicator that the temporary address exists. FIELD NUMBER: .1211 FIELD NAME: TEMPORARY STREET [LINE 1] LOCATION: .121;1 ACCESS: Write w/Fileman FIELD NUMBER: .1212 FIELD NAME: TEMPORARY STREET [LINE 2] LOCATION: .121;2 ACCESS: Write w/Fileman FIELD NUMBER: .1213 FIELD NAME: TEMPORARY STREET [LINE 3] LOCATION: .121;3 ACCESS: Write w/Fileman FIELD NUMBER: .1214 FIELD NAME: TEMPORARY CITY LOCATION: .121;4 ACCESS: Write w/Fileman FIELD NUMBER: .1217 FIELD NAME: TEMPORARY ADDRESS START DATE LOCATION: .121;7 ACCESS: Write w/Fileman FIELD NUMBER: .1218 FIELD NAME: TEMPORARY ADDRESS END DATE LOCATION: .121;8 ACCESS: Write w/Fileman FIELD NUMBER: .12112 FIELD NAME: TEMPORARY ZIP+4 LOCATION: .121;12 ACCESS: Write w/Fileman GLOBAL REFERENCE: DPT(D0,.22) FIELD NUMBER: .2205 FIELD NAME: EMPLOYER ZIP+4 LOCATION: .22;5 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Printed on screens and bills FIELD NUMBER: .2206 FIELD NAME: SPOUSE'S EMP ZIP+4 LOCATION: .22;5 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Printed on screens and bills GLOBAL REFERENCE: DPT(D0,.25) FIELD NUMBER: .251 FIELD NAME: SPOUSE'S EMPLOYER LOCATION: .25;1 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Printed on screens and bills FIELD NUMBER: .252 FIELD NAME: SPOUSE'S EMP STREET [LINE 1] LOCATION: 25;2 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Printed on screens and bills FIELD NUMBER: .256 FIELD NAME: SPOUSE'S EMPLOYER'S STATE LOCATION: 25;6 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Printed on screens and bills FIELD NUMBER: .258 FIELD NAME: SPOUSE'S EMP PHONE NUMBER LOCATION: 25;8 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Displayed on screens. FIELD NUMBER: .253 FIELD NAME: SPOUSE'S EMP STREET [LINE W] LOCATION: .25;3 ACCESS: Write w/Fileman FIELD NUMBER: .254 FIELD NAME: SPOUSE'S EMP STREET [LINE 3] LOCATION: .25;4 ACCESS: Write w/Fileman FIELD NUMBER: .255 FIELD NAME: SPOUSE'S EMPLOYER CITY LOCATION: .25;5 ACCESS: Write w/Fileman GLOBAL REFERENCE: DPT(D0,.3) FIELD NUMBER: .301 FIELD NAME: SERVICE CONNECTED? LOCATION: 3;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Used to determine whether to check for SC related movements for claims. GLOBAL REFERENCE: DPT(D0,.311) FIELD NUMBER: .3111 FIELD NAME: EMPLOYER NAME LOCATION: .311;1 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Printed on screens and bills FIELD NUMBER: .31115 FIELD NAME: EMPLOYMENT STATUS LOCATION: .311;15 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Printed on screens, and used to determine whether employer data is printed on a claim. FIELD NUMBER: .3116 FIELD NAME: EMPLOYER CITY LOCATION: .311;6 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Printed on screens and bills FIELD NUMBER: .3117 FIELD NAME: EMPLOYER STATE LOCATION: .311;7 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Printed on screens and bills FIELD NUMBER: .3119 FIELD NAME: EMPLOYER PHONE NUMBER LOCATION: .311;9 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Displayed on screens FIELD NUMBER: .3113 FIELD NAME: EMPLOYER STREET [LINE 1] LOCATION: .311;3 ACCESS: Write w/Fileman FIELD NUMBER: .3114 FIELD NAME: EMPLOYER STREET [LINE 2] LOCATION: .311;4 ACCESS: Write w/Fileman FIELD NUMBER: .3115 FIELD NAME: EMPLOYER STREET [LINE 3] LOCATION: .311;5 ACCESS: Write w/Fileman GLOBAL REFERENCE: DPT(D0,.36) FIELD NUMBER: .361 FIELD NAME: PRIMARY ELIGIBILITY CODE LOCATION: .36;1 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: This code is printed on several reports. GLOBAL REFERENCE: DPT(D0,.361) FIELD NUMBER: .3611 FIELD NAME: ELIGIBILITY STATUS LOCATION: .361;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This status is used to determine if a HINQ request should be made. GLOBAL REFERENCE: DPT(D0,.01,D1,0) FIELD NUMBER: .01 FIELD NAME: ALIAS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Displayed on screens. FIELD NUMBER: 1 FIELD NAME: ALIAS SSN LOCATION: 0;2 ACCESS: Write w/Fileman GLOBAL REFERENCE: DPT(D0,0) FIELD NUMBER: .02 FIELD NAME: SEX LOCATION: 0;2 ACCESS: Write w/Fileman FIELD NUMBER: .03 FIELD NAME: DATE OF BIRTH LOCATION: 0;3 ACCESS: Write w/Fileman FIELD NUMBER: .05 FIELD NAME: MARITAL STATUS LOCATION: 0;5 ACCESS: Write w/Fileman FIELD NUMBER: .07 FIELD NAME: OCCUPATION LOCATION: 0;7 ACCESS: Write w/Fileman GLOBAL REFERENCE: DPT(D0,'VET') FIELD NUMBER: 1901 FIELD NAME: VETERAN (Y/N)? LOCATION: VET;1 ACCESS: Write w/Fileman GLOBAL REFERENCE: DPT(D0,DIS,D1,0) FIELD NUMBER: 3 FIELD NAME: FACILITY APPLYING TO LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Used to place registration on correct report when printing by division. GLOBAL REFERENCE: DPT(D0,DIS,D1,2) FIELD NUMBER: 20 FIELD NAME: NEED RELATED TO OCCUPATION LOCATION: 2;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Used to determine if the registration may be claimed as a Worker's Compensation case. FIELD NUMBER: 23 FIELD NAME: NEED RELATED TO AN ACCIDENT LOCATION: 2;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Used to determine if the registration may be claimed as a Tort Feasor case. GLOBAL REFERENCE: DPT(D0 FIELD NUMBER: .001 FIELD NAME: NUMBER LOCATION: ENTRY IEN ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This global reference defines direct global access to the internal entry number of each entry in file #2. A full file scan of all entries in file #2 is required to find all patients who were entered into the file (using field #.097, DATE ENTERED INTO FILE) within a user-specified date range. GLOBAL REFERENCE: DPT(D0,.38) FIELD NUMBER: .381 FIELD NAME: ELIGIBLE FOR MEDICAID? LOCATION: .38;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field is displayed on the First Party Follow-Up Report [IBJD FOLLOW-UP FIRST PARTY] so that the Accounts Receivable clerk conducting follow-up activities knows that the patient has been covered under Medicaid. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32775542 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 427 IA #: 427 FILE NUMBER: 8 GLOBAL ROOT: DIC(8, DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA427 ORIGINAL NUMBER: 427 ID: DIC(8, GLOBAL REFERENCE: DIC(8,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Eligibility code name is printed on several reports. FIELD NUMBER: 3 FIELD NAME: VA CODE NUMBER LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The VA code number is printed in place of the eligibility code on one report FIELD NUMBER: 5 FIELD NAME: PRINT NAME LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Eligibility code print name is printed on several reports. FIELD NUMBER: 8 FIELD NAME: MAS ELIGIBILITY CODE LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The MAS eligibility code is used to determine if a patient is a CHAMPVA patient (code=12) FIELD NUMBER: 6 FIELD NAME: INACTIVE LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: TYPE LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The value of the TYPE field is required to determine if a patient is receiving care due to his Veteran or Non-Veteran eligibility. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32775545 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham SUBSCRIBING DETAILS: DSS EXTRACTS performs a FileMan read on MAS ELIGIBILITY CODE (#8) only. No other fields in the record are accessed. SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE SUBSCRIBING PACKAGE: EVENT CAPTURE SUBSCRIBING DETAILS: ADDED 2/28/2012 DATE/TIME EDITED: FEB 29, 2012@13:45 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: NABER,DAVID WITH CONCURRENCE OF: HARVEY,JULIE NUMBER: 428 IA #: 428 FILE NUMBER: 11 GLOBAL ROOT: DIC(11, DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA428 ORIGINAL NUMBER: 428 ID: DIC(11, GLOBAL REFERENCE: DIC(11,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Marital status name is printed on reports, screens, and bills. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 429 IA #: 429 FILE NUMBER: 41.1 GLOBAL ROOT: DGS(41.1, DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA429 ORIGINAL NUMBER: 429 ID: DGS(41.1, CREATOR: JUTZI,WILLIAM CHRISTOPHER GLOBAL REFERENCE: DGS(41.1,D0,0) FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Determine the patient who is scheduled for admission FIELD NUMBER: 2 FIELD NAME: RESERVATION DATE/TIME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Determine the scheduled admission date/time FIELD NUMBER: 13 FIELD NAME: DATE/TIME CANCELLED LOCATION: 0;13 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to determine if the scheduled admission has been canceled. FIELD NUMBER: 17 FIELD NAME: ADMITTED LOCATION: 0;17 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to determine if the patient is already admitted. FIELD NUMBER: 5 FIELD NAME: PROVIDER LOCATION: 0;5 ACCESS: Read w/Fileman GLOBAL REFERENCE: DGS(41.1,'C', GLOBAL DESCRIPTION: The "C" cross-reference is used to find all scheduled admissions within a specified date range. GLOBAL REFERENCE: DGS(41.1,'B', GLOBAL DESCRIPTION: The 'B' cross-reference is used to find all scheduled admissions associated with a patient. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23720883 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany EDITOR: JUTZI,WILLIAM CHRISTOPHER DBA Comments: 10/28/14-DT: Added William C. Jutzi as editor to add the ordering provider as an additional field in this existing ICR. DATE/TIME EDITED: OCT 28, 2014@13:31 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: JUTZI,WILLIAM NUMBER: 430 IA #: 430 FILE NUMBER: 42.4 GLOBAL ROOT: DIC(42.4, DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA430 ORIGINAL NUMBER: 430 ID: DIC(42.4, GLOBAL REFERENCE: DIC(42.4,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The specialty name is printed on several reports. FIELD NUMBER: 3 FIELD NAME: SERVICE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The service is used to track changes in jajor bed sections. FIELD NUMBER: 5 FIELD NAME: BILLING RATE BEDSECTION LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The billing rate bedsection is used to determine if a specialty is billable. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10505091 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany DBA Comments: 12/24/14-MM: Scheduling Calendar View asked to be added as a subscriber to this ICR but withdrew this request after it was determined the MBAA PATIENT ADMISSIONS RPC would not be included in the release of MBAA or VAR2 (MBAA*1.0*1). They may also have changed their code to use Fileman. NUMBER: 431 IA #: 431 FILE NUMBER: 43 GLOBAL ROOT: DG(43, DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA431 ORIGINAL NUMBER: 431 ID: DG(43, CREATOR: BRICKER,DENNIS GLOBAL REFERENCE: DG(43,D0,0) FIELD NUMBER: 76 FIELD NAME: USE HIGH INTENSITY ON SCREENS LOCATION: 0;36 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to determine if high intensity should be used on the billing screens. GLOBAL REFERENCE: DG(43,D0,'TERM',D1,0) FIELD NUMBER: .01 FIELD NAME: EXCLUDE WHICH TERMINAL TYPES LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to determine if high intensity should be used on the billing screens, based on the terminal type. GLOBAL REFERENCE: DG(43,D0,'VERSION) FIELD NUMBER: 999 FIELD NAME: VERSION LOCATION: VERSION;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used in the pre-init routine to determine if PIMS v5.3 has been installed. GLOBAL REFERENCE: DG(43,D0,'VFA') FIELD NUMBER: 1205 FIELD NAME: VFA START DATE LOCATION: VFA;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: The date, January 1,2013, that the Veteran Financial Assessment(VFA) project becomes operational. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 60974980 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH SUBSCRIBING DETAILS: Using VERSION(#999) field. SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM SUBSCRIBING DETAILS: Using Field (#76) -USE HIGH INTENSITY ON SCREENS Using Field (#77) - EXCLUDE WHICH TERMINAL TYPES DBA Comments: 4/5/13-MM: DG*5.3*858 will be released as a combined build containing DG*5.3*858, IVM*2*154 and EAS*1*106. The VFA Start Date (#1205) field is a new field in the MAS Parameter (#43) file approved by the DBA. The developers for these patches and for IB*2*385 have requested to add a new field to ICR #431 for this project. Integrated Billing is a current subscriber to ICR #431 and will be utilizing this field in IB*2*385. Without package level teams, it can be difficult to find resources to review ICR requests. At this time, we are not aware of a knowledgeable Registration resource to review this request but do not believe additional review by Registration is needed. The patch developers responsible for providing the solution for the Veteran Financial Application project are requesting the modification. 4/9/13-MM: Dennis Bricker (Registration developer) completed modifications to the ICR. Ed reviewed and concurred with the updates. ICR has been re-actived for DG*5.3*858, IVM*2*154, EAS*1*106 and IB*2*385. A release schedule for these patches is not known at this time. 7/15/13-MC: Beneficiary Travel added as subscriber in order to retrieve the new VFA start date needed for the Veterans Financial coding modifications to the B to the Beneficiary Travel package relating to the discontinuance of the Means Test expirations. Patch # DGBT*1.0*24. Part of host file DG*5.3*858 8/12/13-MC: Added IVM and EAS as subscribers to document existing access to those fiel to fields (#76) and (#77). DATE ACTIVATED: APR 09, 2013 DATE/TIME EDITED: APR 05, 2013@10:30 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: BRICKER,DENNIS WITH CONCURRENCE OF: BRICKER,DENNIS DATE/TIME EDITED: APR 09, 2013@15:37 ACTION: APPROVED AT THE REQUEST OF: ZEIGLER,ED WITH CONCURRENCE OF: BRICKER,DENNIS DATE/TIME EDITED: JUL 15, 2013@15:04 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: KOPECKY,STEVE DATE/TIME EDITED: AUG 12, 2013@15:06 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BRICKER,DENNIS NUMBER: 432 IA #: 432 FILE NUMBER: 49 GLOBAL ROOT: DIC(49, DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA432 ORIGINAL NUMBER: 432 ID: DIC(49, GLOBAL REFERENCE: DIC(49,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Service name is displayed n several screens. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES SUBSCRIBING PACKAGE: EVENT CAPTURE SUBSCRIBING DETAILS: ADDED 2/28/2012 DATE/TIME EDITED: FEB 29, 2012@13:48 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: NABER,DAVID WITH CONCURRENCE OF: BEUSCHEL,GARY NUMBER: 433 IA #: 433 FILE NUMBER: 405.3 GLOBAL ROOT: DG(405.3, DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA433 ORIGINAL NUMBER: 433 ID: DG(405.3, GLOBAL REFERENCE: DG(405.3,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The disposition name is printed on several outputs. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION DBA Comments: JSHARVEY/20070122 Original usage was Private. Inclusion of SCID made it Controlled. DATE/TIME EDITED: JAN 23, 2007@23:19 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SWESKY,JEFF WITH CONCURRENCE OF: HARRIS,DONNA DATE/TIME EDITED: JAN 23, 2007@23:20 ACTION: USAGE CHOICE CHANGED AT THE REQUEST OF: SWESKY,JEFF WITH CONCURRENCE OF: HARRIS,DONNA NUMBER: 434 IA #: 434 FILE NUMBER: 408.31 GLOBAL ROOT: DGMT(408.31, DATE CREATED: APR 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA434 ORIGINAL NUMBER: 434 ID: DGMT(408.31, GLOBAL REFERENCE: DGMT(408.31,D0,0) FIELD NUMBER: .01 FIELD NAME: DATE OF TEST LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The date/time is needed to determine the date/time of the RX copay exemption. FIELD NUMBER: .019 FIELD NAME: TYPE OF TEST LOCATION: 0;19 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The type is used to determine if the test is a copay test. FIELD NUMBER: .02 FIELD NAME: PATIENT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to determine the patient ofr the copay test. FIELD NUMBER: .03 FIELD NAME: STATUS LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The status of the copay test is used to determine RX copay exemption status. FIELD NUMBER: .04 FIELD NAME: INCOME LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The income is used to determine RX copay exemption status. FIELD NUMBER: .05 FIELD NAME: NET WORTH LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The net worth is used to determine RX copay exemption status FIELD NUMBER: .1 FIELD NAME: ADJUDICATION DATE/TIME LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The adjudication date/time is used to determine RX copay exemption hardships. FIELD NUMBER: .14 FIELD NAME: DECLINES TO GIVE INCOME INFO LOCATION: 0;14 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to determine is not exempt from rx copay based on no available income. FIELD NUMBER: .15 FIELD NAME: DEDUCTIBLE EXPENSES LOCATION: 0;15 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Deductible expenses is used to determine rx copay exemption status. FIELD NUMBER: .18 FIELD NAME: TOTAL DEPENDENTS LOCATION: 0;18 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Total Dependents is used to determine the appropriate pension threshold level for rx copay exemptions. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE NUMBER: 435 IA #: 435 FILE NUMBER: 50.8 GLOBAL ROOT: PS(50.8, DATE CREATED: APR 11, 1994 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA435 ORIGINAL NUMBER: 435 ID: PS(50.8, GLOBAL REFERENCE: PS(50.8,D0,2,D1,2,D2,0) FIELD NUMBER: .01 FIELD NAME: IV DRUG LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: DISPENSED UNITS (IV DRUG) LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: RETURNED UNITS (IV DRUG) LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: DESTROYED UNITS (IV DRUG) LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: AVERAGE DRUG COST PER UNIT LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 5 FIELD NAME: DRUG UNIT LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 6 FIELD NAME: TYPE LOCATION: 0;7 ACCESS: Read w/Fileman GLOBAL REFERENCE: PS(50.8,D0,0) FIELD NUMBER: .01 FIELD NAME: IV ROOM LOCATION: 0;1 ACCESS: Pointed to GLOBAL REFERENCE: PS(50.8,D0,2,D1,2,'AC', STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 436 IA #: 436 FILE NUMBER: 52.6 GLOBAL ROOT: PS(52.6, DATE CREATED: APR 11, 1994 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA436 ORIGINAL NUMBER: 436 ID: PS(52.6, GLOBAL REFERENCE: PS(52.6, FIELD NUMBER: .01 FIELD NAME: PRINT NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: GENERIC DRUG LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: DRUG UNIT LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 7 FIELD NAME: AVERAGE DRUG COST PER UNIT LOCATION: 0;7 ACCESS: Read w/Fileman FIELD NUMBER: 12 FIELD NAME: INACTIVATION DATE LOCATION: I;1 ACCESS: Read w/Fileman FIELD NUMBER: 15 FIELD NAME: PHARMACY ORDERABLE ITEM LOCATION: 0;11 ACCESS: Read w/Fileman FIELD NUMBER: X-REF FIELD NAME: AOI LOCATION: x-ref ACCESS: Read w/Fileman GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of June 1, 2006. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham SUBSCRIBING PACKAGE: BAR CODE MED ADMIN EDITOR: RUZBACKI,RON T NUMBER: 437 IA #: 437 FILE NUMBER: 52.7 GLOBAL ROOT: PS(52.7, DATE CREATED: APR 11, 1994 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA437 ORIGINAL NUMBER: 437 ID: PS(52.7, GLOBAL REFERENCE: PS(52.7, FIELD NUMBER: .01 FIELD NAME: PRINT NAME LOCATION: 0;1 ACCESS: Pointed to FIELD NUMBER: 1 FIELD NAME: GENERIC DRUG LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 7 FIELD NAME: AVERAGE DRUG COST LOCATION: 0;7 ACCESS: Read w/Fileman FIELD NUMBER: 8 FIELD NAME: INACTIVATION DATE LOCATION: I;1 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: VOLUME LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 9 FIELD NAME: PHARMACY ORDERABLE ITEM LOCATION: 0;11 ACCESS: Read w/Fileman FIELD NUMBER: X-REF FIELD NAME: AOI LOCATION: x-ref ACCESS: Read w/Fileman GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of June 1, 2006. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham SUBSCRIBING PACKAGE: BAR CODE MED ADMIN EDITOR: RUZBACKI,RON T NUMBER: 438 IA #: 438 FILE NUMBER: 57.6 GLOBAL ROOT: PS(57.6, DATE CREATED: APR 11, 1994 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA438 ORIGINAL NUMBER: 438 ID: PS(57.6, GLOBAL REFERENCE: PS(57.6,D0,0) FIELD NUMBER: .01 FIELD NAME: DATE LOCATION: 0;1 ACCESS: Pointed to GLOBAL REFERENCE: PS(57.6,D0,1,D1,1,D2,1,D3,0) FIELD NUMBER: .01 FIELD NAME: DRUG LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: DISPENSED AMOUNT LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: DISPENSED COST LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: RETURNED AMOUNT LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: RETURNED COST LOCATION: 0;5 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 439 IA #: 439 FILE NUMBER: 394.61 GLOBAL ROOT: VAT(394.61, DATE CREATED: APR 11, 1994 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA439-A ORIGINAL NUMBER: 439 ID: VAT(394.61, GLOBAL REFERENCE: VAT(394.61,'A1AY', GLOBAL DESCRIPTION: As the result of changing from a local name space (A1AY) and numbering sequence to a national name space (PPP) and numbering sequence, Pharmacy Prescription Practices v1.0 (PPP) will need to kill and directly set MUMPS cross references in the VAQ - TRANSACTION file. GLOBAL REFERENCE: VAT(394.61,D0,SEG,'A1AY2', GLOBAL DESCRIPTION: As the result of changing from a local name space (A1AY) and numbering sequence to a national name space (PPP) and numbering sequence, Pharmacy Prescription Practices v1.0 (PPP) will need to kill and directly set MUMPS cross references in the VAQ - TRANSACTION file. GLOBAL REFERENCE: VAT(394.61,'PPP', GLOBAL DESCRIPTION: The cross reference to create this is a MUMPS cross reference on the Current Status field (#.02) of the VAQ - TRANSACTION file (#394.61) This cross reference is used to update information in the PPP FOREIGN FACILITY XREF file (#1020.2). GLOBAL REFERENCE: VAT(394.61,D0,0) FIELD NUMBER: .01 FIELD NAME: Transaction Number LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE ISC: Albany NUMBER: 440 IA #: 440 DATE CREATED: APR 11, 1994 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAQUPD25 NAME: DBIA439-B ORIGINAL NUMBER: 439 ID: VAQUPD25 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EXTARR(...) COMPONENT DESCRIPTION: Output: 0 - Success (non-display ready) n - Number of lines in display (display ready format) -1^Error_Text - Error Notes: If the segment is not in display ready format ROOT("VALUE",File,Field,Seq)=Data ROOT("ID",File,Field,Seq)=Identifier If the segment is in display ready format ROOT("DISPLAY",LineNumber,0)=Line of display VARIABLES: TRAN TYPE: Input VARIABLES DESCRIPTION: Pointer to VAQ - Transaction file VARIABLES: SEG TYPE: Input VARIABLES DESCRIPTION: Pointer to VAQ - Data segment file VARIABLES: ROOT TYPE: Input VARIABLES DESCRIPTION: Where to store the extraction array (full global ref). VARIABLES: OFFSET TYPE: Input VARIABLES DESCRIPTION: Where to begin placing information (defaults to 0) (Only valid for extractions that are in Display Ready format). SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE ISC: Albany NUMBER: 441 IA #: 441 DATE CREATED: APR 11, 1994 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAQUIN01 NAME: DBIA439-C ORIGINAL NUMBER: 439 ID: VAQUIN01 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: PDX(.......) COMPONENT DESCRIPTION: Output: 0 - ok -1^error text VARIABLES: VAQOPT TYPE: Input VARIABLES DESCRIPTION: REQ=request, UNS=unsolicited VARIABLES: VAQDFN TYPE: Input VARIABLES DESCRIPTION: IFN of patient in patient file VARIABLES: VAQNM TYPE: Input VARIABLES DESCRIPTION: Name of patient VARIABLES: VAQISSN TYPE: Input VARIABLES DESCRIPTION: Patient SSN (no dashes) VARIABLES: VAQIDOB TYPE: Input VARIABLES DESCRIPTION: patients date of birth (external format) VARIABLES: DOMROOT TYPE: Input VARIABLES DESCRIPTION: array of domains (full global reference) (ie: PXB.ISC-ALBANY.VA.GOV)=Institution name or null) VARIABLES: SEGROOT TYPE: Input VARIABLES DESCRIPTION: array of segments (full globlobal reference) (ie: PDX*MIN)=P1^P2 P1 = TIME LIMIT P2 = OCCURRENCE LIMIT VARIABLES: NOTROOT TYPE: Input VARIABLES DESCRIPTION: array of who to notify (only used for request) VARIABLES: TLIMIT TYPE: Input VARIABLES DESCRIPTION: time limit for health summary (ie: 1D,12M,5Y) VARIABLES: OLIMIT TYPE: Input VARIABLES DESCRIPTION: occurrence limit for health summary, up to 5 digits NUMBER: 443 IA #: 443 FILE NUMBER: 394.71 GLOBAL ROOT: VAT(394.71, DATE CREATED: APR 11, 1994 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA439-E ORIGINAL NUMBER: 439 ID: VAT(394.71, GLOBAL REFERENCE: VAT(394.71,D0,0) FIELD NUMBER: .01 FIELD NAME: Data Segment Name LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: VAT(394.71,C,SEGMENT NAME, FIELD NUMBER: .01 FIELD NAME: Data Segement Name LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Used to extract segment pointer information STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14263120 SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE ISC: Albany NUMBER: 444 IA #: 444 FILE NUMBER: 394.62 GLOBAL ROOT: VAT(394.62, DATE CREATED: APR 11, 1994 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA439-F ORIGINAL NUMBER: 439 ID: VAT(394.62, GLOBAL REFERENCE: VAT(394.62,D0,0) FIELD NUMBER: .01 FIELD NAME: Data LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: VAT(394.62,A-SEGMENT, FIELD NUMBER: .01 FIELD NAME: Data LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: VAT(394.62,DATAPTR,VAL, FIELD NUMBER: 10 FIELD NAME: Value LOCATION: VAL;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: VAT(394.62,DATAPTR,SQNCE, FIELD NUMBER: 30 FIELD NAME: Sequence number LOCATION: SQNCE;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Used to extract segment data from data file STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14263120 SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE ISC: Albany NUMBER: 445 IA #: 445 FILE NUMBER: 394.85 GLOBAL ROOT: VAT(394.85, DATE CREATED: APR 11, 1994 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA439-G ORIGINAL NUMBER: 439 ID: VAT(394.85, GLOBAL REFERENCE: VAT(394.85,D0,0) FIELD NUMBER: .01 FIELD NAME: Code LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: Status LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Used to extract PDX status STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14263120 SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE ISC: Albany NUMBER: 446 IA #: 446 FILE NUMBER: 9999999.27 GLOBAL ROOT: AUTNPOV( DATE CREATED: APR 12, 1994 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA446 ORIGINAL NUMBER: 446 ID: AUTNPOV( GLOBAL REFERENCE: AUTNPOV(D0,0) FIELD NUMBER: .01 FIELD NAME: NARRATIVE LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman GENERAL DESCRIPTION: Access to the IHS Provider Narrative File (^AUTNPOV). Access is defined as the ability to READ to and WRITE from this file. The Problem List Application stores the original problem narrative entered by the clinician in ^AUTNPOV. The natural language narrative, along with the accompanying coded data, is displayed for use by the clinician. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City NUMBER: 447 IA #: 447 FILE NUMBER: 9000001 GLOBAL ROOT: AUPNPAT( DATE CREATED: APR 12, 1994 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA447 ORIGINAL NUMBER: 447 ID: AUPNPAT( GLOBAL REFERENCE: AUPNPAT(D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field points to the Patient File (#2) and has the same internal file number as that file. Thus, the patient's name is the Patient File (#2) name. GENERAL DESCRIPTION: READ only access to the Patient/IHS File (^AUPNPAT). This file is a subset of the IHS Patient File. It is required to be installed as all VAMCs wishing to use the Problem List Application. Use of this file assures backward compatibility with IHS software. The patient's name and IFN is initially selected from this file. Then used for look-up purposes with the VA's Patient File (^DPT). STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City NUMBER: 449 IA #: 449 DATE CREATED: APR 12, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA449 ORIGINAL NUMBER: 449 GENERAL DESCRIPTION: The CPT package currently has five table files which reside in the DIC global. These are as follows: o CPT CATEGORY (#81.1) data is in ^DIC(81.1, o CPT COPYRIGHT (#81.2) data is in ^DIC(81.2, o CPT MODIFIER (#81.3) data is in ^DIC(81.3, o CPT MODIFIER CATEGORY (#81.4) data is in ^DIC(81.4, o CPT SOURCE (#81.5) data is in ^DIC(81.5, STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CPT/HCPCS CODES ISC: Albany NUMBER: 452 IA #: 452 FILE NUMBER: 409.72 GLOBAL ROOT: SD(409.72, DATE CREATED: APR 12, 1994 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA452 ORIGINAL NUMBER: 452 ID: SD(409.72, GLOBAL REFERENCE: SD(409.72 GLOBAL DESCRIPTION: GENERAL DESCRIPTION: Reason: To populate the Ambulatory Procedure Time Sensitive file with current CPT codes. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13548805 SUBSCRIBING PACKAGE: CPT/HCPCS CODES ISC: Albany NUMBER: 456 IA #: 456 FILE NUMBER: 58.5 GLOBAL ROOT: PSI(58.5, DATE CREATED: APR 12, 1994 CUSTODIAL PACKAGE: AUTO REPLENISHMENT/WARD STOCK CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA456 ORIGINAL NUMBER: 456 ID: PSI(58.5, GLOBAL REFERENCE: PSI(58.5,D0,0) FIELD NUMBER: .01 FIELD NAME: DATE LOCATION: 0;1 ACCESS: Pointed to GLOBAL REFERENCE: PSI(58.5,D0,'S',D1,'AMIS',D2,0) FIELD NUMBER: .01 FIELD NAME: AMIS FIELD LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: DOSES DISPENSED LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: DISPENSED COST LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: DOSES RETURNED LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: RETURNS COST LOCATION: 0;5 ACCESS: Read w/Fileman GLOBAL REFERENCE: PSI(58.5,D0,'S',D1,0) FIELD NUMBER: .01 FIELD NAME: INPATIENT SITE LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: PSI(58.5,D0,'S',D1,'DRG',D2,0) FIELD NUMBER: .01 FIELD NAME: DRUG LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: MISSING DATA LOCATION: 0;2 ACCESS: Read w/Fileman GLOBAL REFERENCE: PSI(58.5,D0,'S',D1,'DRG',D2,'CAT',D3,0) FIELD NUMBER: .01 FIELD NAME: CATEGORY LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: QUANTITY DISPENSED LOCATION: 0;2 ACCESS: Read w/Fileman GLOBAL REFERENCE: PSI(58.5,'B', GLOBAL DESCRIPTION: to identify statistics for a selected time frame GENERAL DESCRIPTION: Used to extract the AR/WS statistics for a selected time frame. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 457 IA #: 457 FILE NUMBER: 757.01 GLOBAL ROOT: GMP(757.01, DATE CREATED: APR 26, 1994 CUSTODIAL PACKAGE: LEXICON UTILITY CUSTODIAL ISC: Salt Lake City USAGE: Supported TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: CLINICAL LEXICON EXPRESSIONS ORIGINAL NUMBER: 457 ID: GMP(757.01, GLOBAL REFERENCE: GMP(757.01,D0,0) FIELD NUMBER: .01 FIELD NAME: DISPLAY TEXT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The Display Text contained in the Clinical Lexicon is the text which will be used in all display/print routines. GENERAL DESCRIPTION: The Clinical Lexicon Utility will maintain static internal entry numbers (IENs) for the Expression file (#757.01). As a result, this file may be pointed to to retrieve the Display Text (.01) for both current Expressions and formerly used (deleted) Expressions. STATUS: Active DURATION: Next Version MAIL MESSAGE: 21276004 GOOD ONLY FOR VERSION: 1.0 NUMBER: 458 IA #: 458 DATE CREATED: APR 25, 1994 CUSTODIAL PACKAGE: IMAGING CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MAGAPI NAME: DBIA458 ORIGINAL NUMBER: 458 ID: MAGAPI GENERAL DESCRIPTION: MailMan 7.1 is permitted to the make calls to MAGAPI routine in the imaging package: STATUS: Active DURATION: Next Version MAIL MESSAGE: 10111211 COMPONENT/ENTRY POINT: MAGFILE COMPONENT DESCRIPTION: This entry point is used to get data about an image attached to a mail message. VARIABLES: MAGXX TYPE: Input VARIABLES DESCRIPTION: MAGXX is a pointer to the image file. VARIABLES: MAGFILE TYPE: Output VARIABLES DESCRIPTION: MAGFILE is an array containing data about the image passed to the MAGFILE routine. SUBSCRIBING PACKAGE: MAILMAN ISC: Washington/Silver Spring NUMBER: 459 IA #: 459 FILE NUMBER: 2005 GLOBAL ROOT: MAG(2005, DATE CREATED: APR 25, 1994 CUSTODIAL PACKAGE: IMAGING CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA459 ORIGINAL NUMBER: 459 ID: MAG(2005, GLOBAL REFERENCE: MAG(2005,0) GLOBAL DESCRIPTION: MailMan $ORDERs from here to test to see if there are images in the system and if there are none, assumes that imaging is not installed. GLOBAL REFERENCE: MAG(2005,entry,0) FIELD NUMBER: .01 FIELD NAME: Image Name LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: FIELD NUMBER: 2 FIELD NAME: DISK & VOL,MAGNETIC LOCATION: 0;3 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: FIELD NUMBER: 1 FIELD NAME: FILEREF LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: 3 FIELD NAME: OBJECT TYPE LOCATION: 0;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: 14 FIELD NAME: COLLECTION DATE LOCATION: 0;9 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: FIELD NUMBER: 2.1 FIELD NAME: DISK & VOLUME. - ABSTRACT LOCATION: 0;4 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: FIELD NUMBER: 2.2 FIELD NAME: DISK & VOL.: WORM LOCATION: 0;5 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: This agreement describes data that MailMan can access from the imaging package. STATUS: Active DURATION: Next Version MAIL MESSAGE: 36843935 SUBSCRIBING PACKAGE: MAILMAN ISC: Washington/Silver Spring NUMBER: 460 IA #: 460 FILE NUMBER: 2005.2 GLOBAL ROOT: MAG(2005.2, DATE CREATED: APR 25, 1994 CUSTODIAL PACKAGE: IMAGING CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA460 ORIGINAL NUMBER: 460 ID: MAG(2005.2, GLOBAL REFERENCE: MAG(2005.2,entry,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: FIELD NUMBER: 1 FIELD NAME: PHYSICAL REFERENCE LOCATION: 0;2 ACCESS: Both R/W w/Fileman GLOBAL DESCRIPTION: This file (NETWORK LOCATION) is used to store information about where an image may be found. GENERAL DESCRIPTION: MailMan has permission to access file 2005.2 so that it can find where images are and record their position appropriately. STATUS: Active DURATION: Next Version MAIL MESSAGE: 10111211 SUBSCRIBING PACKAGE: MAILMAN ISC: Washington/Silver Spring NUMBER: 461 IA #: 461 FILE NUMBER: 2005.02 GLOBAL ROOT: MAG(2005.02, DATE CREATED: APR 25, 1994 CUSTODIAL PACKAGE: IMAGING CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA461 ORIGINAL NUMBER: 461 ID: MAG(2005.02, GLOBAL REFERENCE: MAG(2005.02,entry,0) FIELD NUMBER: .01 FIELD NAME: OBJECT TYPE LOCATION: 0;1 ACCESS: Both R/W w/Fileman GLOBAL DESCRIPTION: The object type tells the software which software to use to display it. GENERAL DESCRIPTION: Before an image can be displayed, the type of file it is stored in must be known. STATUS: Active DURATION: Next Version MAIL MESSAGE: 10111211 SUBSCRIBING PACKAGE: MAILMAN ISC: Washington/Silver Spring NUMBER: 462 IA #: 462 DATE CREATED: MAY 03, 1994 CUSTODIAL PACKAGE: IMAGING CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MAGAPI NAME: DBIA462 ORIGINAL NUMBER: 462 ID: MAGAPI GENERAL DESCRIPTION: MailMan has permission to call MAGAPI for 3 purposes. STATUS: Active DURATION: Next Version MAIL MESSAGE: 10111211 COMPONENT/ENTRY POINT: SELIM COMPONENT DESCRIPTION: SELIM^MAGAPI(x) allows MailMan to select an image from the image file to attach to a message. VARIABLES: Parameter1 TYPE: Input VARIABLES DESCRIPTION: Pointer to the image file VARIABLES: y TYPE: Output VARIABLES DESCRIPTION: The pointer to the image chosen and its name (same as DIC output). COMPONENT/ENTRY POINT: ERASE COMPONENT DESCRIPTION: ERASE^MAGAPI(x) allows MailMan to erase an image from the screen. VARIABLES: Parameter1 TYPE: Input VARIABLES DESCRIPTION: Parameter1 is a pointer to the image. file. COMPONENT/ENTRY POINT: EXPORT(X,Y,Z) COMPONENT DESCRIPTION: Images must be in a special directory so that they can be transmitted across the network. This entry point creates a copy of the image file in that directory. VARIABLES: Parameter1 TYPE: Input VARIABLES DESCRIPTION: When this entry point is called Imaging will copy an image into the export directory. VARIABLES: x TYPE: Input VARIABLES DESCRIPTION: Pointer to the image file. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Directory to move an image into. VARIABLES: Y TYPE: Input VARIABLES DESCRIPTION: Pointer to the image file. VARIABLES: Z TYPE: Input VARIABLES DESCRIPTION: Wait flag if set to other than zero. COMPONENT/ENTRY POINT: $$EXPORT(X,Y,Z) SUBSCRIBING PACKAGE: MAILMAN ISC: Washington/Silver Spring NUMBER: 463 IA #: 463 DATE CREATED: MAY 03, 1994 CUSTODIAL PACKAGE: IMAGING CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MAGBAPI NAME: DBIA463 ORIGINAL NUMBER: 463 ID: MAGBAPI GENERAL DESCRIPTION: MailMan has permission to call MAGBAPI so that images that are imported can be moved into a permanent storage location. STATUS: Active MAIL MESSAGE: 10111211 COMPONENT/ENTRY POINT: $$IMPORT(X) COMPONENT DESCRIPTION: Causes image file to be moved to a permanent location from the import directory. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Pointer to the image file. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Returned because call is in the form of an extrinsic function. SUBSCRIBING PACKAGE: MAILMAN ISC: Washington/Silver Spring NUMBER: 464 IA #: 464 DATE CREATED: APR 25, 1994 CUSTODIAL PACKAGE: IMAGING CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MAGOBJ NAME: DBIA464 ORIGINAL NUMBER: 464 ID: MAGOBJ GENERAL DESCRIPTION: MailMan has permission to call MAGOBJ in order to display an image on a screen while a user is reading a message. STATUS: Active DURATION: Next Version MAIL MESSAGE: 10111211 COMPONENT/ENTRY POINT: ENTRY(X,Y,Z) COMPONENT DESCRIPTION: This entry point displays an image. E.G. ENTRY^MAGOBJ(X,Y,Z) VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Pointer to the image file. VARIABLES: Y TYPE: Input VARIABLES DESCRIPTION: "DISPLAY" is the hardcoded value that is sent. VARIABLES: Z TYPE: Input VARIABLES DESCRIPTION: "" is the hardcoded value that is sent. SUBSCRIBING PACKAGE: MAILMAN ISC: Washington/Silver Spring NUMBER: 465 IA #: 465 FILE NUMBER: 52 GLOBAL ROOT: PSRX( DATE CREATED: APR 26, 1994 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA465 ORIGINAL NUMBER: 465 ID: PSRX( GLOBAL REFERENCE: PSRX(D0,0) FIELD NUMBER: .01 FIELD NAME: RX # LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 6 FIELD NAME: DRUG LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 7 FIELD NAME: QTY LOCATION: 0;7 ACCESS: Read w/Fileman FIELD NUMBER: 17 FIELD NAME: UNIT PRICE OF DRUG LOCATION: 0;17 ACCESS: Read w/Fileman GLOBAL REFERENCE: PSRX(D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: REFILL DATE LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: QTY LOCATION: 0;4 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The Pharmacy Benefits Management software will use the prescription file to extract drug statistics for a selected time frame. STATUS: Active MAIL MESSAGE: 10171105 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 470 IA #: 470 FILE NUMBER: 2005 GLOBAL ROOT: MAG(2005 DATE CREATED: OCT 20, 2003 CUSTODIAL PACKAGE: IMAGING CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA470 ORIGINAL NUMBER: 470 ID: MAG(2005 GLOBAL REFERENCE: MAG(2005, GLOBAL DESCRIPTION: The Medicine package is pointing to File 2005 to reference each Medicine Procedure that has images. GENERAL DESCRIPTION: 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. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 9587178 SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring NUMBER: 472 IA #: 472 FILE NUMBER: 50.8 GLOBAL ROOT: PS(50.8, DATE CREATED: APR 26, 1994 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA472 ORIGINAL NUMBER: 472 ID: PS(50.8, GLOBAL REFERENCE: PS(50.8,D0,2,D1,2,D2,0) FIELD NUMBER: .01 FIELD NAME: IV DRUG LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: DISPENSED UNIT (IV DRUG) LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: RETURNED UNITS (IV DRUG) LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: DESTROYED UNITS (IV DRUG) LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: AVERAGE DRUG COST PER UNIT LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 5 FIELD NAME: DRUG UNIT LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 6 FIELD NAME: TYPE LOCATION: 0;7 ACCESS: Read w/Fileman GENERAL DESCRIPTION: D&PPM extracts drug data from the IV Statistics file for a selected time frame. STATUS: Active MAIL MESSAGE: 10170723 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 475 IA #: 475 FILE NUMBER: 57.6 GLOBAL ROOT: PS(57.6 DATE CREATED: APR 26, 1994 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA475 ORIGINAL NUMBER: 475 ID: PS(57.6 GLOBAL REFERENCE: PS(57.6,D0,1,D1,1,D2,1,D3,0) FIELD NUMBER: .01 FIELD NAME: DRUG LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: DISPENSED AMOUNT LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: DISPENSED COST LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: RETURNED AMOUNT LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: RETURNED COST LOCATION: 0;5 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Pharmacy Benefits Management extracts drug usage statistics for a selected time frame from the UNIT DOES PICK LIST STATS file. STATUS: Active MAIL MESSAGE: 10170778 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 479 IA #: 479 FILE NUMBER: 40.7 GLOBAL ROOT: DIC(40.7, DATE CREATED: MAY 02, 1994 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA479 ORIGINAL NUMBER: 479 ID: DIC(40.7, GLOBAL REFERENCE: DIC(40.7,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: AMIS REPORTING STOP CODE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Visit Tracking (PIMS/MAS) Entries used by Visit Tracking are passed by package developers making calls to the Visit Tracking package. The Visit Tracking package requests permission to read and point to the following file: Visit File Fields ----------------- #08 Clinic Pointer to the Clinic Stop File #40.7 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10255172 SUBSCRIBING PACKAGE: VISIT TRACKING ISC: Albany NUMBER: 480 IA #: 480 FILE NUMBER: 8 GLOBAL ROOT: DIC(8, DATE CREATED: MAY 02, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA480 ORIGINAL NUMBER: 480 ID: DIC(8, GLOBAL REFERENCE: DIC(8,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Visit File Field ---------------- #21 Eligibility Pointer to the Eligibility Code File #8 Visit Tracking software references the Eligibility Code file for the patient's eligibility. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10255182 SUBSCRIBING PACKAGE: VISIT TRACKING ISC: Albany NUMBER: 482 IA #: 482 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: MAY 02, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA482 ORIGINAL NUMBER: 482 ID: DGPM( GLOBAL REFERENCE: DGPM(D0,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .27 FIELD NAME: VT ENTRY ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: WARD LOCATION ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Visit Tracking (PIMS/MAS) Entries used by Visit Tracking are passed by package developers making calls to the Visit Tracking package. The Visit Tracking package requests permission to read the following file: File Field ------------------------------------------------ Patient Movement #405 Date/Time #.01 VT Entry #.27 Ward Location #.06 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10255204 SUBSCRIBING PACKAGE: VISIT TRACKING ISC: Albany NUMBER: 483 IA #: 483 FILE NUMBER: 43 GLOBAL ROOT: DG(43, DATE CREATED: MAY 02, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA483 ORIGINAL NUMBER: 483 ID: DG(43, GLOBAL REFERENCE: DG(43,D0,0) FIELD NUMBER: 16 FIELD NAME: DOMICILIARY WARDS ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Visit Tracking (PIMS/MAS) Entries used by Visit Tracking are passed by package developers making calls to the Visit Tracking package. The Visit Tracking package requests permission to read the following file: File Field ------------------------------------------------ MAS Parameter #43 Domiciliary Wards #16 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10255209 SUBSCRIBING PACKAGE: VISIT TRACKING ISC: Albany SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: SCHEDULING NUMBER: 484 IA #: 484 FILE NUMBER: 40.8 GLOBAL ROOT: DG(40.8, DATE CREATED: MAY 02, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA484 ORIGINAL NUMBER: 484 ID: DG(40.8, GLOBAL REFERENCE: DG(40.8,D0,0) FIELD NUMBER: .07 FIELD NAME: INSTITUTION FILE POINTER ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Visit Tracking (PIMS/MAS) Entries used by Visit Tracking are passed by package developers making calls to the Visit Tracking package. The Visit Tracking package requests permission to read the following file: File Field -------------------------------------------------------------- Medical Center Division #40.8 Institution File Pointer #.07 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10255219 SUBSCRIBING PACKAGE: VISIT TRACKING ISC: Albany NUMBER: 485 IA #: 485 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: MAY 02, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA485 ORIGINAL NUMBER: 485 ID: DPT( GLOBAL REFERENCE: DPT(D0,0) FIELD NUMBER: .01 FIELD NAME: NAME ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DPT(D0,.36) FIELD NUMBER: .361 FIELD NAME: PRIMARY ELIGIBILITY ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DPT(D0,E,0) FIELD NUMBER: .01 FIELD NAME: ELIGIBILITY ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Visit Tracking (PIMS/MAS) Entries used by Visit Tracking are passed by package developers making calls to the Visit Tracking package. The Visit Tracking package requests permission to read the following file: STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10255227 SUBSCRIBING PACKAGE: VISIT TRACKING ISC: Albany NUMBER: 486 IA #: 486 DATE CREATED: JUN 24, 1994 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJEEU0 NAME: PSJEEU0 ORIGINAL NUMBER: 486 ID: PSJEEU0 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23148159 COMPONENT/ENTRY POINT: ENHS COMPONENT DESCRIPTION: List a patient's IV and Unit Dose medications. The output variables for this entry point are: For each Unit Dose order: ^UTILITY("PSG",$J,S1)=P1^P2^P3^P4^P5^P6^P7^P8^P9 where: S1 = The inverse of the start date/time of the order. If this subscript already exists, .000001 is subtracted from the date until it does not equal an existing subscript. P1 = The start date/time of the order. P2 = The stop dat/time of the order. P3 = The drug in the form of: a) If there is more than one dispense drug or a dosage ordered entered for the order - pointer to Orderable Item_:PS(50.7,_;_Orderable Item name_Dose Form b) If there is only one dispense drug and no dosage ordered entered for the order - pointer to Dispense drug_:PSDRUG(_;_Dispense drug name P4 = The provider in the form of - pointer to the New Person file_VA(200_;_name of the provider. P5 = The status of the order in the form of - status code_;_status name. P6 = The dosage ordered in the form of: a) If Orderable Item was sent in P3 - Dosage ordered b) If Dispense Drug was sent in P3 - Units Per Dose entered P7 = The med route of the order in the form of - pointer to the med route file_:PS(51.2,;_med route abbreviation_;_med route name. P8 = The schedule of the order. P9 = The schedule type of the order in the form of - schedule type code_;_schedule type name. For each IV order: ^UTILITY("PSIV",$J,S1,0)=P1^P2^P3^P4^P5^P6 ^UTILITY("PSIV",$J,S1,"A",S2)=P7^P8 ^UTILITY("PSIV",$J,S1,"S",S2)=P9^P10 where: S1 = The inverse of the start date/time of the order. If this subscript already exists, .000001 is subtracted from the date until it does not equal an existing subscript. S2 = A sequential number. P1 = The start date/time of the order. P2 = The stop dat/time of the order. P3 = The provider in the form of - pointer to the New Person file_VA(200_;_name of the provider. P4 = The status of the order in the form of - status code_;_status name. P5 = The infusion rate of the order P6 = The schedule of the order. P7 = An additive of the order in the form of - pointer to the IV Additive file_;_additive name. P8 = The strength of the additive in P7. P9 = A solution of the order in the form of - pointer to the IV Solutions file_;_solution name. P10 = The volume of the solution in P9. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal entry number of the patient in the PATIENT file (2) for which orders are to be returned. VARIABLES: PSJEDT TYPE: Input VARIABLES DESCRIPTION: Internal VA Fileman date (opt). If PSJEDT is null, all Inpatient orders active on or after the current date/time are returned. If PSJEDT contains a date, all Inpatient orders active on or after that date are returned. SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING ISC: Hines SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 488 IA #: 488 GLOBAL ROOT: DD(8984.1 AND 8984.2 DATE CREATED: MAY 11, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA488 ORIGINAL NUMBER: 488 ID: DD(8984.1 AND 8984.2 GLOBAL REFERENCE: DD(8984.2,.02,'V','B',+Y GLOBAL REFERENCE: DD(8984.1,.02,'V','B',+Y GENERAL DESCRIPTION: 1. DLL^XTLKMGR: This procedure non-interactively removes an entry from file 8984.4 and the associated variable pointer in the DD of 8984.1 and 8984.2. Line DLL+7 $orders on the variable pointer node to set DA, then ^DIK is called to remove the entry. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10379102 COMPONENT/ENTRY POINT: DLL SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 489 IA #: 489 DATE CREATED: SEP 18, 1995 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VSIT NAME: DBIA489 ORIGINAL NUMBER: 489 ID: VSIT GENERAL DESCRIPTION: Interface with Visit Tracking to create Visits. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: VSIT COMPONENT DESCRIPTION: Entry Point to Find or Create a Visit. VARIABLES: VSIT(0) TYPE: Input VARIABLES DESCRIPTION: A string of characters that defines how the visit processor will function. F Force adding a new entry. I Interactive mode. E Use patients primary eligibility if not defined on call with VSIT("ELG"). N Allow creation of new visit. D Look back n number of days for match, defaults to one (1). D[] i.e., VSIT(0)="D7" e.g., VSIT(0)="D5" (visit date to visit date - 4) use "D0" to require exact match on visit date and time. M Impose criteria on matching/screening of visits. Uses the VSIT() array: Matching elements must equal their corresponding field. VARIABLES: VSIT(VDT) TYPE: Input VARIABLES DESCRIPTION: The date [and time] of the visit. VARIABLES: VSIT(IEN) TYPE: Input VARIABLES DESCRIPTION: NUMBER (visit internal entry number) VARIABLES: VSIT(CDT) TYPE: Input VARIABLES DESCRIPTION: DATE VISIT CREATED (date) VARIABLES: VSIT(TYP) TYPE: Input VARIABLES DESCRIPTION: TYPE (set) VARIABLES: VSIT(BIL) TYPE: Input VARIABLES DESCRIPTION: THIRD PARTY BILLED (set) VARIABLES: VSIT(PAT) TYPE: Input VARIABLES DESCRIPTION: PATIENT NAME (pointer PATIENT file #9000001) (IHS file DINUMed to PATIENT file #2) VARIABLES: VSIT(INS) TYPE: Input VARIABLES DESCRIPTION: LOC. OF ENCOUNTER (pointer LOCATION file #9999999.06) VARIABLES: VSIT(SVC) TYPE: Input VARIABLES DESCRIPTION: SERVICE CATEGORY (set) VARIABLES: VSIT(CLN) TYPE: Input VARIABLES DESCRIPTION: CLINIC (pointer to CLINIC STOP file) VARIABLES: VSIT(CTR) TYPE: Input VARIABLES DESCRIPTION: DEPENDENT ENTRY COUNTER (number) VARIABLES: VSIT(DEL) TYPE: Input VARIABLES DESCRIPTION: DELETE FLAG (set) VARIABLES: VSIT(LNK) TYPE: Input VARIABLES DESCRIPTION: PARENT VISIT LINK (pointer VISIT file #9000010) VARIABLES: VSIT(MDT) TYPE: Input VARIABLES DESCRIPTION: DATE LAST MODIFIED (date) VARIABLES: VSIT(XDT) TYPE: Input VARIABLES DESCRIPTION: DATE VISIT EXPORTED (date) VARIABLES: VSIT(MFI) TYPE: Input VARIABLES DESCRIPTION: MFI STATUS (set) VARIABLES: VSIT(LOS) TYPE: Input VARIABLES DESCRIPTION: Evaluation and Management code pointer to the Type of Visit file (#357.69) VARIABLES: VSIT(COD) TYPE: Input VARIABLES DESCRIPTION: CHECK OUT DATE&TIME (date) VARIABLES: VSIT(ELG) TYPE: Input VARIABLES DESCRIPTION: ELIGIBILITY (pointer ELIGIBILITY CODE file #8) VARIABLES: VSIT(LOC) TYPE: Input VARIABLES DESCRIPTION: HOSPITAL LOCATION (pointer HOSPITAL LOCATION file #44) VARIABLES: VSIT(USR) TYPE: Input VARIABLES DESCRIPTION: CREATED BY USER (pointer NEW PERSON file #200) VARIABLES: VSIT(OPT) TYPE: Input VARIABLES DESCRIPTION: OPTION USED TO CREATE (pointer OPTION file #19) VARIABLES: VSIT(AMT) TYPE: Input VARIABLES DESCRIPTION: AMOUNT BILLED (number) VARIABLES: VSIT(PRI) TYPE: Input VARIABLES DESCRIPTION: PRIMARY TYPE OF VISIT FLAG. VARIABLES: VSIT(OUT) TYPE: Input VARIABLES DESCRIPTION: OUTSIDE LOCATION (free text) VARIABLES: VSIT(AO) TYPE: Input VARIABLES DESCRIPTION: AGENT ORANGE EXPOSURE (set) VARIABLES: VSIT(SC) TYPE: Input VARIABLES DESCRIPTION: Service connected (set) VARIABLES: VSIT(EC) TYPE: Input VARIABLES DESCRIPTION: PERSIAN GULF EXPOSURE (set) VARIABLES: VSIT(SVP) TYPE: Input VARIABLES DESCRIPTION: SERVICE PROVIDED (pointer to the service provided file #150.1) VARIABLES: VSIT(IO) TYPE: Input VARIABLES DESCRIPTION: INPATIENT OUTPATIENT VARIABLES: VSIT(COM) TYPE: Input VARIABLES DESCRIPTION: COMMENTS (free text) VARIABLES: VSIT(IEN,PAT) TYPE: Output VARIABLES DESCRIPTION: PATIENT NAME (pointer PATIENT file #9000001) (IHS file DINUMed to PATIENT file #2) VARIABLES: VSIT() TYPE: Output VARIABLES DESCRIPTION: N^S[^1] where: -1 = -2 = N = S = 1 = VARIABLES: VSIT(,xxx) TYPE: Output VARIABLES DESCRIPTION: where: = IEN of visit. = Mnemonics for Zero node of visit. VARIABLES: VSIT(ien,BIL) TYPE: Output VARIABLES DESCRIPTION: THIRD PARTY BILLED (set) VARIABLES: VSIT(ien,CDT) TYPE: Output VARIABLES DESCRIPTION: DATE VISIT CREATED (date) VARIABLES: VSIT(ien,CLN) TYPE: Output VARIABLES DESCRIPTION: CLINIC (pointer to CLINIC STOP file) VARIABLES: VSIT(ien,COD) TYPE: Output VARIABLES DESCRIPTION: CHECKOUT DATE&TIME (date) VARIABLES: VSIT(ien,CTR) TYPE: Output VARIABLES DESCRIPTION: DEPENDENT ENTRY COUNTER (number) VARIABLES: VSIT(ien,DEL) TYPE: Output VARIABLES DESCRIPTION: DELETE FLAG (set) VARIABLES: VSIT(ien,ELG) TYPE: Output VARIABLES DESCRIPTION: ELIGIBILITY (pointer ELIGIBILITY CODE file #8) VARIABLES: VSIT(ien,INS) TYPE: Output VARIABLES DESCRIPTION: LOC. OF ENCOUNTER (pointer LOCATION file #9999999.06) VARIABLES: VSIT(ien,LNK) TYPE: Output VARIABLES DESCRIPTION: PARENT VISIT LINK (pointer VISIT file #9000010) VARIABLES: VSIT(ien,LOC) TYPE: Output VARIABLES DESCRIPTION: HOSPITAL LOCATION (pointer HOSPITAL LOCATION file #44) VARIABLES: VSIT(ien,LOS) TYPE: Output VARIABLES DESCRIPTION: EVALUATION AND MANAGEMENT CODE (pointer to the type of visit file (#357.69) VARIABLES: VSIT(ien,MDT) TYPE: Output VARIABLES DESCRIPTION: DATE LAST MODIFIED (date) VARIABLES: VSIT(ien,MFI) TYPE: Output VARIABLES DESCRIPTION: MFI STATUS (set) VARIABLES: VSIT(ien,OPT) TYPE: Output VARIABLES DESCRIPTION: OPTION USED TO CREATE (pointer OPTION file #19) VARIABLES: VSIT(ien,SVC TYPE: Output VARIABLES DESCRIPTION: SERVICE CATEGORY (set) VARIABLES: VSIT(ien,TYP) TYPE: Output VARIABLES DESCRIPTION: TYPE (set) VARIABLES: VSIT(ien,USR) TYPE: Output VARIABLES DESCRIPTION: CREATED BY USER (pointer NEW PERSON file #200) VARIABLES: VSIT(ien,VDT) TYPE: Output VARIABLES DESCRIPTION: The date [and time] of the visit. VARIABLES: VSIT(ien,WIA) TYPE: Output VARIABLES DESCRIPTION: WALK IN APPOINTMENT (set) VARIABLES: VSIT(WIA) TYPE: Input VARIABLES DESCRIPTION: WALK IN APPOINTMENT (set) VARIABLES: VSIT(ien,XDT) TYPE: Output VARIABLES DESCRIPTION: DATE VISIT EXPORTED (date) VARIABLES: VSIT(HNC) TYPE: Input VARIABLES DESCRIPTION: HEAD AND NECK CANCER (set) EDITOR: SEEGER,ANTHONY NUMBER: 491 IA #: 491 FILE NUMBER: 7 GLOBAL ROOT: DIC(7 DATE CREATED: JUN 13, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA491 ORIGINAL NUMBER: 491 ID: DIC(7 GLOBAL REFERENCE: DIC(7,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Read access to the .01 field of the provider class file for provider identification. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10191489 SUBSCRIBING PACKAGE: EVENT CAPTURE ISC: Birmingham SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 492 IA #: 492 FILE NUMBER: 420.1 GLOBAL ROOT: PRCD(420.1, DATE CREATED: JUN 13, 1994 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA492 ORIGINAL NUMBER: 492 ID: PRCD(420.1, GLOBAL REFERENCE: PRCD(420.1,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DMMS units must be associated with a cost center to make it possible associate the work for the unit as gathered in DHCP with financial data contained in reports from the AAC. To this end, we request read access to the COST CENTER file (420.1). Currently the CC field is a 6 digit code with the first 4 being Cost Center and the last two being Sub-cost center. Thats how it is broken up to pass to FMS for IFCAP V5.0. Current plans are to increase the code to 8 digits. There are discussions going on between OF&IRM and VAH's CFO's office. At some point IFCAP will be changing the content of the file. When that happens, this DBIA will have to be revisited. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10710527 SUBSCRIBING PACKAGE: EVENT CAPTURE ISC: Birmingham NUMBER: 500 IA #: 500 FILE NUMBER: 72 GLOBAL ROOT: RA( DATE CREATED: FEB 23, 1990 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA15-B ORIGINAL NUMBER: 15 ID: RA( GLOBAL REFERENCE: RA(72,0) FIELD NUMBER: .01 FIELD NAME: CURRENT EXAM STATUS LOCATION: 1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: EXAMINATION STATUS STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 501 IA #: 501 FILE NUMBER: 74 GLOBAL ROOT: RARPT( DATE CREATED: FEB 23, 1990 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA15-C ORIGINAL NUMBER: 15 ID: RARPT( GLOBAL REFERENCE: RARPT( FIELD NUMBER: 5 FIELD NAME: REPORT STATUS LOCATION: 0;5 ACCESS: Read w/Fileman GLOBAL REFERENCE: RARPT(D0,"R", FIELD NUMBER: .01 FIELD NAME: REPORT TEXT LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: RARPT(D0,"I", FIELD NUMBER: .01 FIELD NAME: IMPRESSION TEXT LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: RARPT(D0,"H", FIELD NUMBER: .01 FIELD NAME: ADDITIONAL CLINICAL HISTORY LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: RADIOLOGY REPORTS FILE STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES NUMBER: 502 IA #: 502 FILE NUMBER: 71 GLOBAL ROOT: RAMIS(71, DATE CREATED: FEB 23, 1990 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA15-D ORIGINAL NUMBER: 15 ID: RAMIS(71, GLOBAL REFERENCE: RAMIS(71,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 9 FIELD NAME: CPT CODE LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6 FIELD NAME: TYPE OF PROCEDURE LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: RADIOLOGY PROCEDURES FILE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30358687 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 503 IA #: 503 FILE NUMBER: 71.2 GLOBAL ROOT: RAMIS(71.2, DATE CREATED: FEB 23, 1990 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA15-E ORIGINAL NUMBER: 15 ID: RAMIS(71.2, GLOBAL REFERENCE: RAMIS(71.2,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: PROCEDURE MODIFIERS FILE STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 504 IA #: 504 FILE NUMBER: 75.1 GLOBAL ROOT: RAO(75.1, DATE CREATED: FEB 23, 1990 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA15-F ORIGINAL NUMBER: 15 ID: RAO(75.1, CREATOR: HARVEY,JULIE S GLOBAL REFERENCE: RAO(75.1,'AS', GLOBAL REFERENCE: RAO(75.1, FIELD NUMBER: 1.1 FIELD NAME: REASON FOR STUDY ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: PROCEDURE ACCESS: Read w/Fileman FIELD NUMBER: 5 FIELD NAME: REQUEST STATUS ACCESS: Read w/Fileman FIELD NUMBER: 14 FIELD NAME: REQUESTING PHYSICIAN ACCESS: Read w/Fileman FIELD NUMBER: 16 FIELD NAME: REQUEST ENTERED DATE/TIME ACCESS: Read w/Fileman FIELD NUMBER: 23 FIELD NAME: SCHEDULED DATE (TIME OPTIONAL) ACCESS: Read w/Fileman GENERAL DESCRIPTION: RADIOLOGY ORDERS FILE STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 507 IA #: 507 GLOBAL ROOT: XUTL( DATE CREATED: JUL 27, 1989 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA4-B ORIGINAL NUMBER: 4 ID: XUTL( GLOBAL REFERENCE: XUTL('OR',$J GLOBAL DESCRIPTION: Used to hold package defined parameters in ^XUTL("OR",$J,package namespace,... This node is killed by menuman when the terminal session ends. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 508 IA #: 508 GLOBAL ROOT: DD( DATE CREATED: JUL 27, 1989 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA6-B ORIGINAL NUMBER: 6 ID: DD( GLOBAL REFERENCE: DD('DD') GLOBAL DESCRIPTION: Used to format date. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 510 IA #: 510 GLOBAL ROOT: DISV( DATE CREATED: JUL 27, 1989 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DISV ORIGINAL NUMBER: 6 ID: DISV( CREATOR: BUESING,GEORGIA GENERAL DESCRIPTION: Used to process 'space-bar return' on user input. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 54147580 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: OE/RR requests the following access to the DISV global. All are ^DISV(DUZ,x where x is defined as follows: The only non-file reference we use is "ORDITM". Read and write. We save under "^DPT" to save the patient looked up through the GUI. Read and write. We retrieve "^GMT(142," to default the last health summary type the user referenced. Read only. There is also a utility routine ORUS which will end up doing a kill, set, or read in DISV. The called utility looks like it can be called in with "^XUTL("OR",$J,"ORLP",","^ORD(100.9,", or multiples from "^OR(100.21,n,sub," where sub is 1, 2, or 10. This one is a carryover from previous versions. Read, write, and delete. READ access allowed. WRITE access allowed in routines ORGUEM, and ORUS1. An example of a set is S ^DISV(DUZ,"^ORD(101,")=+ORGMENU DELETE access allowed in ORUS1. SUBSCRIBING PACKAGE: KERNEL ISC: Oakland SUBSCRIBING DETAILS: The Unwinder uses ^DISV(DUZ,"XQORM") to store the items that were selected for spacebar recall. READ and WRITE access to ^DISV(DUZ,"XQORM") allowed. SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING DETAILS: Laboratory V 5.2 uses ^DISV(DUZ,"LRACC") and ^DISV(DUZ,"LRAN") to store items. An example is in routine LRACC at line LRACC+4: S:$L(X)>2 ^DISV(DUZ,"LRACC")=X S:X=" " X=$S($D(^DISV(DUZ,"LRACC")): ^("LRACC"),1:"?") READ and WRITE access to ^DISV(DUZ,"LRACC") and ^DISV(DUZ,"LRAN" allowed. SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING DETAILS: READ access allowed. WRITE access allowed to ^DISV(DUZ,"VALMMENU", SUBSCRIBING PACKAGE: DISCHARGE SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: READ access allowed. SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: READ access allowed. SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring SUBSCRIBING DETAILS: READ access allowed. The inventory package V5 uses the global ^DISV(DUZ,"PRCProutine name", and ^DISV(DUZ,globalnode, to allow the user to press the space bar to select the last response. WRITE access allowed. The reference to ^DISV(DUZ,"PRCProutine", is used to store non-fileman responses to the reader. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING DETAILS: Read access "Till Otherwise Agreed". SUBSCRIBING PACKAGE: QUASAR ISC: Birmingham SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland SUBSCRIBING DETAILS: The parameter tools component of toolkit would like permission to use DISV to allow spacebar-return within the parameter tools edit option. This will allow the most recently selected parameters and entities to be recalled by a user when editing. This information is stored in ^DISV(DUZ,"XPAR01",... SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: WOMEN'S HEALTH ISC: Hines SUBSCRIBING PACKAGE: LEXICON UTILITY ISC: Birmingham SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: HEALTH SUMMARY SUBSCRIBING DETAILS: JSH/10-23-2006 Added per agreement between Skip Ormsby & Jason Hawsey. Health Summary reads global reference ^DISV(DUZ,"^GMT(142,") in order to get the last chosen Health Summary Type. It uses the value found here as the default in the prompt to choose a Health Summary Type. SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING DETAILS: ADDED 5/11/09 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY SUBSCRIBING DETAILS: 04/11/11 Outpatient Pharmacy is providing a standalone option, PSO HRC PROFILE/REFILL, to the Compensation and Pension Record Interchange (CAPRI) package. OP requests read and write access to ^DISV(DUZ,"VALMMENU",x) when the protocol x is PSO PENDING ORDER MENU. The node value for x will be temporarily set to 0 (if it is not, and reset after use to its original value) so as to turn off the display of actions associated with this protocol. SUBSCRIBING PACKAGE: EVENT CAPTURE SUBSCRIBING DETAILS: Event Capture patient data filer sets the following DISV nodes for recall when entering multiple patient records. ^DISV(DUZ,"^ICD9(") is set to recall the last ICD code ^DISV(DUZ,"^VA(200,") is set to recall the last provider SUBSCRIBING PACKAGE: DRG GROUPER SUBSCRIBING DETAILS: DRG Grouper READ and WRITE access to: ^DISV(DUZ,"^ICD9(")=IEN ^DISV(DUZ,"^ICD0(")=IEN DBA Comments: 20110411 JSHARVEY - reactivated after new option added. 20120229 JSHARVEY - reactivated after additional nodes added for Event Capture 12/30/13 - MM: Added DRG Grouper as a subscriber to ICR #510. Request from Kim: A special lookup routine was developed for ICD-9 (legacy) and ICD-10 which is similar to the Lexicon. Part of the special lookup requires the ability to capture and retrieve the last item referenced when a "space-bar-return" is detected in either file 80 or 80.1 using the ^DISV global. The special lookup routine is ICDEXLK, and the routine containing the reference to DISV is ICDEXLK2. DATE ACTIVATED: FEB 29, 2012 DATE/TIME EDITED: OCT 23, 2006@16:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HAWSEY,JASON WITH CONCURRENCE OF: ORMSBY,SKIP DATE/TIME EDITED: MAY 11, 2009@11:44 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CURTIS,RICHARD WITH CONCURRENCE OF: BEUSCHAL,GARY DATE/TIME EDITED: APR 11, 2011@13:24 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: MORRISON,JENNIFER DATE/TIME EDITED: APR 11, 2011@13:57 ACTION: APPROVED AT THE REQUEST OF: MORRISON,JENNIFER WITH CONCURRENCE OF: HARVEY,JULIE DATE/TIME EDITED: FEB 29, 2012@13:46 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: NABER,DAVID WITH CONCURRENCE OF: BEUSCHEL,GARY DATE/TIME EDITED: FEB 29, 2012@14:02 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: NABER,DAVID WITH CONCURRENCE OF: BEUSCHEL,GARY DATE/TIME EDITED: FEB 29, 2012@16:47 ACTION: APPROVED AT THE REQUEST OF: NABER,DAVID WITH CONCURRENCE OF: BEUSCHEL,GARY DATE/TIME EDITED: FEB 29, 2012@16:49 ACTION: CONTENT CORRECTED AT THE REQUEST OF: NABER,DAVID WITH CONCURRENCE OF: BEUSCHEL,GARY DATE/TIME EDITED: DEC 30, 2013@15:21 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: ROWE,KIMBALL WITH CONCURRENCE OF: BEUSCHEL,GARY NUMBER: 511 IA #: 511 GLOBAL ROOT: DIC( DATE CREATED: JUL 27, 1989 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA6-D ORIGINAL NUMBER: 6 ID: DIC( GLOBAL REFERENCE: DIC('AC',namespace, GENERAL DESCRIPTION: ^DIC("AC" - Screen lookup on files of a particular application group. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 512 IA #: 512 DATE CREATED: MAR 12, 1990 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGPMLOS NAME: DBIA17-B ORIGINAL NUMBER: 17 ID: DGPMLOS STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: DGPMLOS COMPONENT DESCRIPTION: Used to determine Length of Stay. SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 513 IA #: 513 FILE NUMBER: 45.7 GLOBAL ROOT: DIC(45.7, DATE CREATED: MAR 01, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA30-B ORIGINAL NUMBER: 30 ID: DIC(45.7, GLOBAL REFERENCE: DIC(45.7,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: SPECIALTY LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: Name of original agreement was BEDSECTION. It appears to be in error The correct name should be SPECIALTY. DCM STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTO REPLENISHMENT/WARD STOCK ISC: Birmingham NUMBER: 514 IA #: 514 FILE NUMBER: 42.5 GLOBAL ROOT: DGWAIT( DATE CREATED: NOV 14, 1989 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA31-B ORIGINAL NUMBER: 31 ID: DGWAIT( GLOBAL REFERENCE: DGWAIT(D0,0) FIELD NUMBER: .01 FIELD NAME: DIVISION LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTO REPLENISHMENT/WARD STOCK ISC: Birmingham NUMBER: 515 IA #: 515 FILE NUMBER: 44 GLOBAL ROOT: SC( DATE CREATED: NOV 14, 1989 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA31-C ORIGINAL NUMBER: 31 ID: SC( GLOBAL REFERENCE: SC(D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTO REPLENISHMENT/WARD STOCK ISC: Birmingham NUMBER: 519 IA #: 519 FILE NUMBER: 45.7 GLOBAL ROOT: DIC(45.7, DATE CREATED: MAR 22, 1989 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA36-C ORIGINAL NUMBER: 36 ID: DIC(45.7, GENERAL DESCRIPTION: ^DIC(45.7 Used to lookup treating specialty and print name STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 524 IA #: 524 FILE NUMBER: 61 GLOBAL ROOT: LAB(61, DATE CREATED: JAN 31, 1991 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA67-B ORIGINAL NUMBER: 67 ID: LAB(61, CREATOR: BUECHLER,MELANIE K GLOBAL REFERENCE: LAB(61,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: SNOMED CODE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4.1 FIELD NAME: COLLECTION SAMPLE LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD DBA Comments: 5/24/12-VPR added as a subscriber for VPR*1.0. Collection Sample (#4.1) field added to ICR. DATE ACTIVATED: MAY 24, 2012 DATE/TIME EDITED: AUG 01, 2011@22:36 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: BUECHLER,MELANIE DATE/TIME EDITED: MAY 24, 2012@15:03 ACTION: APPROVED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: ANZALDUA,CAROL NUMBER: 525 IA #: 525 FILE NUMBER: 63 GLOBAL ROOT: LR( DATE CREATED: JAN 31, 1991 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA67-C ORIGINAL NUMBER: 67 ID: LR( GLOBAL REFERENCE: LR(D0,'CH',D1,0) FIELD NUMBER: .03 FIELD NAME: DATE REPORT COMPLETED LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .01 FIELD NAME: DATE/TIME SPECIMEN TAKEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .05 FIELD NAME: SPECIMEN TYPE LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: ACCESSION LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .11 FIELD NAME: REQUESTING LOCATION LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'CH',D1,1,D2,0) FIELD NUMBER: .01 FIELD NAME: COMMENT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'CH',D1,2...x) FIELD NUMBER: x FIELD NAME: TEST RESULT ~ FLAG LOCATION: Piece 1,2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME SPECIMEN TAKEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: DATE REPORT COMPLETED LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .05 FIELD NAME: SITE/SPECIMEN LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: .06 FIELD NAME: MICROBIOLOGY ACCESSION LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .08 FIELD NAME: WARD LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .055 FIELD NAME: COLLECTION SAMPLE LOCATION: 0;11 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,1) FIELD NUMBER: 11.5 FIELD NAME: BACT RPT STATUS LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 11.58 FIELD NAME: SPATUM SCREEN LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 11.57 FIELD NAME: URINE SCREEN LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 11.51 FIELD NAME: STERILITY CONTROL LOCATION: 0;7 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,5) FIELD NUMBER: 15 FIELD NAME: PARASITE RPT STATUS LOCATION: 0;2 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,8) FIELD NUMBER: 19 FIELD NAME: MYCOLOGY RPT STATUS LOCATION: 0;2 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,11) FIELD NUMBER: 23 FIELD NAME: TB RPT STATUS LOCATION: 11;2 ACCESS: Read w/Fileman FIELD NUMBER: 24 FIELD NAME: ACID FAST STAIN LOCATION: 11;3 ACCESS: Read w/Fileman FIELD NUMBER: 25 FIELD NAME: QUANTITY LOCATION: 11;4 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,16) FIELD NUMBER: 34 FIELD NAME: VIROLOGY REPORT STATUS LOCATION: 0;2 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,2,D2,0) FIELD NUMBER: .01 FIELD NAME: GRAM STAIN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,3,D2,0) FIELD NUMBER: .01 FIELD NAME: ORGANISM LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: QUANTITY LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,3,D2,2.0001...x) FIELD NUMBER: x FIELD NAME: ANTIBIOTIC LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: x.1 FIELD NAME: INTERP LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: x.2 FIELD NAME: SCREEN LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,4,D2,0) FIELD NUMBER: .01 FIELD NAME: BACT RPT REMARK LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,6,D2,0) FIELD NUMBER: .01 FIELD NAME: PARASITE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,6,D2,1,D3,0) FIELD NUMBER: .01 FIELD NAME: STAGE LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: QUANTITY LOCATION: 0;2 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,7,D2,0) FIELD NUMBER: .01 FIELD NAME: PARASITE RPT REMARK LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,9,D2,0) FIELD NUMBER: .01 FIELD NAME: FUNGUS/YEAST LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: QUANTITY LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,10,D2,0) FIELD NUMBER: .01 FIELD NAME: MYCOLOGY RPT REMARK LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,12,D2,0) FIELD NUMBER: .01 FIELD NAME: MYCOBACTERIUM LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: QUANTITY LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,13,D2,0) FIELD NUMBER: .01 FIELD NAME: TB RPT REMARK LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,17,D2,0) FIELD NUMBER: .01 FIELD NAME: VIRUS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,18,D2,0) FIELD NUMBER: .01 FIELD NAME: VIROLOGY RPT REMARK LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,0) FIELD NUMBER: .05 FIELD NAME: ABO GROUP LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: RH TYPE LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,1.6,D1,0) FIELD NUMBER: .01 FIELD NAME: TRANSFUSION DATE/TIME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: COMPONENT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .07 FIELD NAME: UNITS POOLED LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'SP',D1,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME SPECIMEN TAKEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: SURGICAL PATH ACC # LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .11 FIELD NAME: REPORT RELEASE DATE/TIME LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'SP',D1,.1,D2,0) FIELD NUMBER: .01 FIELD NAME: SPECIMEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'SP',D1,1,D2,0) FIELD NUMBER: .01 FIELD NAME: GROSS DESCRIPTION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'SP',D1,1.1,D2,0) FIELD NUMBER: .01 FIELD NAME: MICROSCOPIC DESCRIPTION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'SP',D1,2,D2,0) FIELD NUMBER: .01 FIELD NAME: ORGAN/TISSUE LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'SP',D1,2,D2,2,D3,0) FIELD NUMBER: .01 FIELD NAME: MORPHOLOGY LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'SP',D1,2,D2,2,D3,1,D4,0) FIELD NUMBER: .01 FIELD NAME: ETIOLOGY LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'SP',D1,2,D2,4,D3,0) FIELD NUMBER: .01 FIELD NAME: PROCEDURE LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'SP',D1,3,D2,0) FIELD NUMBER: .01 FIELD NAME: ICD DIAGNOSIS LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'CY',D1,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME SPECIMEN TAKEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: ACCESSION # LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .11 FIELD NAME: REPORT RELEASE DATE/TIME LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'CY',D1,.1,0) FIELD NUMBER: .01 FIELD NAME: SPECIMEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'CY',D1,1,D2,0) FIELD NUMBER: .01 FIELD NAME: GROSS DESCRIPTION LOCATION: 1;0 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'CY',D1,1.1,D2,0) FIELD NUMBER: .01 FIELD NAME: MICROSCOPIC EXAMINATION LOCATION: 1;0 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'CY',D1,2,D2,0) FIELD NUMBER: .01 FIELD NAME: CYTOPATH ORGAN/TISSUE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'CY',D1,2,D2,1,D3,0) FIELD NUMBER: .01 FIELD NAME: DISEASE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'CY',D1,2,D2,2,D3,0) FIELD NUMBER: .01 FIELD NAME: MORPHOLOGY LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'CY',D1,2,D2,2,D3,1,D4,0) FIELD NUMBER: .01 FIELD NAME: ETIOLOGY LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'CY',D1,2,D2,4,D3,0) FIELD NUMBER: .01 FIELD NAME: PROCEDURE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'CY',D1,2,D2,3,D3,0) FIELD NUMBER: .01 FIELD NAME: ICD DIAGNOSIS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'CY',D1,1.4,0) FIELD NUMBER: .01 FIELD NAME: CYTOPATHOLOGY DIAGNOSIS LOCATION: 1.4;0 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'CY',D1,1.2,D2,0) FIELD NUMBER: .01 FIELD NAME: SUPPLEMENTARY REPORT DATE/TIME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: RELEASE SUPPLEMENTARY REPORT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'CY',D1,1.2,D2,1,0) FIELD NUMBER: 1 FIELD NAME: DESCRIPTION LOCATION: 1;0 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'CY',D1,3,D2,0) FIELD NUMBER: .01 FIELD NAME: ICD DIAGNOSIS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'CY',D1,.2,D2,0) FIELD NUMBER: .01 FIELD NAME: BRIEF CLINICAL HISTORY LOCATION: .2;0 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'SP',D1,.2,0) GLOBAL REFERENCE: LR(D0,'SP',D1,.2,D2,0) FIELD NUMBER: .01 FIELD NAME: BRIEF CLINICAL HISTORY LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'SP',D1,1.2,D2,0) FIELD NUMBER: .01 FIELD NAME: SUPPLEMENTARY REPORT DATE/TIME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'SP',D1,1.2,D2,1,D3,0) FIELD NUMBER: .01 FIELD NAME: DESCRIPTION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'SP',D1,1.3,D2,0) FIELD NUMBER: .01 FIELD NAME: FROZEN SECTION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'SP',D1,1.4,D2,D2,0) FIELD NUMBER: .01 FIELD NAME: SURGICAL PATH DIAGNOSIS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,6,D2,1,D3,1,D4,0) FIELD NUMBER: .01 FIELD NAME: COMMENT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,9,D2,1,D3,0) FIELD NUMBER: .01 FIELD NAME: COMMENT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,12,D2,1,0) FIELD NUMBER: .01 FIELD NAME: COMMENT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,12,D2,2.0001...X) FIELD NUMBER: X FIELD NAME: SUSCEPTABILITIES LOCATION: X;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,14,D2,0) FIELD NUMBER: .01 FIELD NAME: ANTIBIOTIC(for SERUM LEVEL) LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: DRAW TIME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: CONC(ug/ml) LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,15,D2,0) FIELD NUMBER: 19.6 FIELD NAME: MYCOLOGY SMEAR/PREP LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,24,D2,0) FIELD NUMBER: 15.51 FIELD NAME: PARASITOLOGY SMEAR/PREP LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,31,D2,0) FIELD NUMBER: 11.52 FIELD NAME: STERILITY RESULTS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,99) FIELD NUMBER: .99 FIELD NAME: COMMENT ON SPECIMEN LOCATION: 99;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,3,D2,1,D3,0) FIELD NUMBER: .01 FIELD NAME: COMMENT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,25,D2,0) FIELD NUMBER: 11.7 FIELD NAME: BACTERIOLOGY SMEAR/PREP LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'EM',D1,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME SPECIMEN TAKEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: ACCESSION # LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .11 FIELD NAME: REPORT RELEASE DATE LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'EM',D1,.1,D2,0) FIELD NUMBER: .01 FIELD NAME: SPECIMEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'EM',D1,.2,D2,0) FIELD NUMBER: .01 FIELD NAME: BRIEF CLINICAL HISTORY LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'EM',D1,1,D2,0) FIELD NUMBER: .01 FIELD NAME: GROSS DESCRIPTION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'EM',D1,1.1,D2,0) FIELD NUMBER: .01 FIELD NAME: MICROSCOPIC EXAMINATION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'EM',D1,1.2,D2,1,D3,0) FIELD NUMBER: .01 FIELD NAME: DESCRIPTION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'EM',D1,1.2,D2,0) FIELD NUMBER: .01 FIELD NAME: SUPPLEMENTARY REPORT DATE/TIME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'EM',D1,1.4,D2,0) FIELD NUMBER: .01 FIELD NAME: EM DIAGNOSIS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'EM',D1,2,D2,0) FIELD NUMBER: .01 FIELD NAME: EM ORGAN/TISSUE LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'EM',D1,2,D2,2,D3,0) FIELD NUMBER: .01 FIELD NAME: MORPHOLOGY LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'EM',D1,2,D2,2,D3,1,D4,0) FIELD NUMBER: .01 FIELD NAME: ETIOLOGY LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'EM',D1,2,D2,4,D3,0) FIELD NUMBER: .01 FIELD NAME: PROCEDURE LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'EM',D1,3,D2,0) FIELD NUMBER: .01 FIELD NAME: ICD9CM CODE LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'EM',D1,2,D2,1,D3,0) FIELD NUMBER: .01 FIELD NAME: DISEASE LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: LR(D0,'EM',D1,.2,0) FIELD NUMBER: .013 FIELD NAME: BRIEF CLINICAL HISTORY ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Check 3rd piece of Multiple header to see if data exists. GLOBAL REFERENCE: LR(D0,'EM',D1,1.1,0) FIELD NUMBER: 1.1 FIELD NAME: MICROSCOPIC EXAMINATION ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Check 3rd piece of Multiple header to see if data exists. GLOBAL REFERENCE: LR(D0,'EM',D1,1.2,0) FIELD NUMBER: 1.2 FIELD NAME: SUPPLEMENTARY REPORT ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Check 3rd piece of Multiple header to see if data exists. GLOBAL REFERENCE: LR(D0,'EM',D1,1.4,0) FIELD NUMBER: 1.4 FIELD NAME: EM DIAGNOSIS ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Check 3rd piece of Multiple header to see if data exists. GLOBAL REFERENCE: LR(D0,'SP',D1,.2,0) FIELD NUMBER: .013 FIELD NAME: BRIEF CLINICAL HISTORY ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Check 3rd piece of Multiple Header to see if data exists. GLOBAL REFERENCE: LR(D0,'SP',D1,1,0) FIELD NUMBER: 1 FIELD NAME: GROSS DESCRIPTION ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Check 3rd piece of Multiple header to see if data exists. GLOBAL REFERENCE: LR(D0,'SP',D1,1.2,0) FIELD NUMBER: 1.2 FIELD NAME: SUPPLEMENTARY REPORT ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Check 3rd piece of Multiple header to see if data exists. GLOBAL REFERENCE: LR(D0,'SP',D1,1.3,0) FIELD NUMBER: 1.3 FIELD NAME: FROZEN SECTION ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Check 3rd piece of multiple header to see if data exists. GLOBAL REFERENCE: LR(D0,'SP',D1,1.4,0) FIELD NUMBER: 1.4 FIELD NAME: SURGICAL PATH DIAGNOSIS ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Check 3rd piece of Multiple header to see if data exists. GLOBAL REFERENCE: LR(D0,'SP',D1,1.1,0) FIELD NUMBER: 1.1 FIELD NAME: MICROSCOPIC DESCRIPTION ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Check 3rd piece of Multiple header to see if data exists. GENERAL DESCRIPTION: This DBIA needed to be updated for HS 2.7 to include additional data for several of the HS components. This was done on June 12, 1995. For the next version of either Lab or Health Summary a LAB API will need to be set up to access this data. ^TMP("LRA",$J, may be Set and Killed during collection of field data. ditto ^TMP("LRCY",$J, ditto ^TMP("LRM",$J, STATUS: Active DURATION: Next Version MAIL MESSAGE: 13509026 GOOD ONLY FOR VERSION: LAB 5.2 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: WOMEN'S HEALTH SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: DSS EXTRACTS SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS SUBSCRIBING DETAILS: ADDED 4/23/09 SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD DBA Comments: 5/24/12-VPR added as subscriber for VPR*1.0. Left NHIN as subscriber. DATE/TIME EDITED: JUN 08, 2009@12:20 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MCDEARMON,JAMES DATE/TIME EDITED: SEP 16, 2010@11:02 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE DATE/TIME EDITED: MAY 24, 2012@15:36 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: ANZALDUA,CAROL NUMBER: 526 IA #: 526 FILE NUMBER: 61.2 GLOBAL ROOT: LAB(61.2, DATE CREATED: JAN 31, 1991 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA67-D ORIGINAL NUMBER: 67 ID: LAB(61.2, GLOBAL REFERENCE: LAB(61.2,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 527 IA #: 527 FILE NUMBER: 65 GLOBAL ROOT: LRD(65, DATE CREATED: JAN 31, 1991 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA67-E ORIGINAL NUMBER: 67 ID: LRD(65, GLOBAL REFERENCE: LRD(65,D0,0) FIELD NUMBER: .01 FIELD NAME: UNIT ID LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: EXPIRATION DATE/TIME LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .07 FIELD NAME: ABO GROUP LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .08 FIELD NAME: RH TYPE LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .11 FIELD NAME: VOLUME (ml) LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .16 FIELD NAME: DIVISION LOCATION: 0;16 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LRD(65,D0,4) FIELD NUMBER: 4.1 FIELD NAME: DISPOSITION LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: LRD(65,D0,8) FIELD NUMBER: 8.3 FIELD NAME: DONATION TYPE LOCATION: 0;3 ACCESS: Read w/Fileman GLOBAL REFERENCE: LRD(65,D0,2,D1,0) FIELD NUMBER: .02 FIELD NAME: DATE/TIME UNIT ASSIGNED LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LRD(65,D0,2,D1,1,D2,0) FIELD NUMBER: .04 FIELD NAME: XMATCH RESULT LOCATION: 0;4 ACCESS: Read w/Fileman GLOBAL REFERENCE: LRD(65,'AP', GLOBAL DESCRIPTION: PATIENT XMATCHED/ASSIGNED GENERAL DESCRIPTION: This agreement allows the Health Summary package to look at specified fields in the Lab Package in order to display Blood Bank related information on a patient. Amended 7-18-97 to include field .16, DIVISION on some reports. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City EDITOR: MURCH,CLAUDETTE NUMBER: 528 IA #: 528 FILE NUMBER: 66 GLOBAL ROOT: LAB(66, DATE CREATED: JAN 31, 1991 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA67-F ORIGINAL NUMBER: 67 ID: LAB(66, GLOBAL REFERENCE: LAB(66,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: ABBREVIATION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: BLOOD PRODUCT FILE GENERAL DESCRIPTION: Note: This IA will become void upon the release of VBECS. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 529 IA #: 529 FILE NUMBER: 61.1 GLOBAL ROOT: LAB(61.1, DATE CREATED: JAN 31, 1991 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA67-G ORIGINAL NUMBER: 67 ID: LAB(61.1, GLOBAL REFERENCE: LAB(61.1,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15935779 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 530 IA #: 530 FILE NUMBER: 62.05 GLOBAL ROOT: LAB(62.05, DATE CREATED: JAN 31, 1991 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA67-H ORIGINAL NUMBER: 67 ID: LAB(62.05, GLOBAL REFERENCE: LAB(62.05,D0,0) FIELD NUMBER: .01 FIELD NAME: URGENCY LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15935779 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 531 IA #: 531 FILE NUMBER: 68 GLOBAL ROOT: LRO(68, DATE CREATED: JAN 31, 1991 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA67-I ORIGINAL NUMBER: 67 ID: LRO(68, GLOBAL REFERENCE: LRO(68,D0,1,D1,1,D2,.2) FIELD NUMBER: 15 FIELD NAME: ACCESSION LOCATION: .2;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LRO(68,D0,1,D1,1,D2,4,D3,0) FIELD NUMBER: .01 FIELD NAME: TESTS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: COMPLETE DATE LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15935779 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 532 IA #: 532 FILE NUMBER: 69 GLOBAL ROOT: LRO(69, DATE CREATED: JAN 31, 1991 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA67-J ORIGINAL NUMBER: 67 ID: LRO(69, GLOBAL REFERENCE: LRO(69,D0,1,D1,0) FIELD NUMBER: 4 FIELD NAME: LAB,IMM OR WARD COLLECT LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5 FIELD NAME: DATE/TIME ORDERED LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7 FIELD NAME: PROVIDER LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 8 FIELD NAME: REPORT ROUTING LOCATION LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LRO(69,D0,1,D1,1) FIELD NUMBER: 10 FIELD NAME: DATE/TIME OF COLLECTION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LRO(69,D0,1,D1,3) FIELD NUMBER: 21 FIELD NAME: DATE/TIME RESULTS AVAILABLE LOCATION: 3;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LRO(69,D0,1,D1,2,D2,0) FIELD NUMBER: .01 FIELD NAME: TEST/PROCEDURE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: URGENCY LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: ACCESSION DATE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: ACCESSION AREA LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: ACCESSION NUMBER LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LRO(69,'D', GLOBAL DESCRIPTION: Get patient LRDFN. GENERAL DESCRIPTION: Data is passed in ^TMP("LRO",$J, which may be killed before and after its use. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15935779 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 534 IA #: 534 FILE NUMBER: 53.1 GLOBAL ROOT: PS(53.1, DATE CREATED: JAN 31, 1991 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA68-C ORIGINAL NUMBER: 68 ID: PS(53.1, GENERAL DESCRIPTION: For non-verified orders: ^PS( 53.1 1 Provider 3 Medicinal Route 7 Schedule Type 10 Start Date/Time 26 Schedule 28 Status 25 Stop Date/Time 53.11 .01 Drug 1 Dosage Ordered The following cross-references are used: ^PS( 53.1 "AC" Stop Date/Time STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 537 IA #: 537 FILE NUMBER: 52.7 GLOBAL ROOT: PS(52.7, DATE CREATED: JAN 31, 1991 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA69-D ORIGINAL NUMBER: 69 ID: PS(52.7, GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. ^PS(52.7, IV SOLUTION FILE 52.7 .01 Solution Name STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City EDITOR: BLOCKER,DAVE EDITOR: RUZBACKI,RON T NUMBER: 539 IA #: 539 FILE NUMBER: 606.5 GLOBAL ROOT: YSP(606.5, DATE CREATED: FEB 04, 1991 CUSTODIAL PACKAGE: MENTAL HEALTH CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA75-B ORIGINAL NUMBER: 75 ID: YSP(606.5, GENERAL DESCRIPTION: Agreement has been made for Health Summary to access the following fields in the Mental Health Progress Notes files. - Globals accessed are: ^YSP(606.5, Prgress Note Type - The following fields are accessed: ^YSP(606.5, 606.5 .01 TYPE STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 540 IA #: 540 FILE NUMBER: 699 GLOBAL ROOT: MCAR(699, DATE CREATED: FEB 05, 1991 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA80-B ORIGINAL NUMBER: 80 ID: MCAR(699, GENERAL DESCRIPTION: The Health Summary exports and calls the routine GMTSMCPS, which generates the output for the Health Summary Medicine component. The following fields and cross references are being referenced: ^MCAR(699, Endoscopy File Fields: 1 Procedure 20 Summary STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 541 IA #: 541 FILE NUMBER: 694 GLOBAL ROOT: MCAR(694, DATE CREATED: FEB 05, 1991 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA80-C ORIGINAL NUMBER: 80 ID: MCAR(694, GENERAL DESCRIPTION: The Health Summary exports and calls the routine GMTSMCPS, which generates the output for the Health Summary Medicine component. The following fields and cross references are being referenced: ^MCAR(694, Hematology File Fields: 2 Procedure 1.5 Summary STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 542 IA #: 542 FILE NUMBER: 697.2 GLOBAL ROOT: MCAR(697.2, DATE CREATED: FEB 05, 1991 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA80-D ORIGINAL NUMBER: 80 ID: MCAR(697.2, GENERAL DESCRIPTION: The Health Summary exports and calls the routine GMTSMCPS, which generates the output for the Health Summary Medicine component. The following fields and cross references are being referenced: ^MCAR(697.2, Procedure Location File Fields: .01 Name 1 Global Location Uses "C" cross reference on Global Location field. The "C" cross reference could result in pointing to global locations in the Global Location field which currently contains global roots for the range on files from ^MCAR(691, through ^MCAR(699,. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 543 IA #: 543 FILE NUMBER: 190.1 GLOBAL ROOT: RTV(190.1, DATE CREATED: JUL 09, 1991 CUSTODIAL PACKAGE: RECORD TRACKING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA85-B ORIGINAL NUMBER: 85 ID: RTV(190.1, GENERAL DESCRIPTION: 1. Activation interface 2. Make an appointment Checkin/unscheduled visit 3. Cancel an appointment 4. Changing clinic names 1. Use of the Record Tracking System Parameter file # 195.4 SD calls RT if the field 'MAS INTERFACE STATUS' is 'UP' ^DIC(195.4,1,"UP")=1^ 2. When a clinic appointment is made if the appointment is 'today' or if the Record Tracking System Parameter 'Batch requests' is set to 'No' or if records are requested for an unscheduled visit. A. An entry is made in the Requested Records file #190.1 ^RTV(190.1,n) by a call from RT^SDUTL to a tasked job QUE^RTQ or RT^SDI B. After the entry is added to the Requested Records file #190.1 an entry is made in Parent Record Request field of the Patient subfield of the Hospital Location file #44 ^SC(n,"S",,,,"RTR")=n^ by a return call from CREATE+11^RTQ2 to RTSET^SDUTL 3. When a clinic appointment is canceled: If there is a Requested Records entry in file #190.1 the status is changed to 'canceled' by a call RTV(190.1,n)=^^^^^x^ from RT+2^SDUTL to CANCEL^RTQ2. 4. When the name of a clinic is changed the corresponding names of entries in the Pull List file #194.2 are changed by a trigger on the .01 field of the Hospital Location file #44. Clinic ^SC(1,0)=DJones Medical Clinic^ ^RTV(194.2,n)=Dr Jones Medical Clinic [04/01/91]^ Clinic names are changed in a compiled input template. To insure the use of this trigger the following action is taken: The Record Tracking package includes the .01 field of the Hospital Location file #44 so that the SDB template is re-compiled when the Record Tracking package is initialized. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 544 IA #: 544 DATE CREATED: JUL 09, 1991 CUSTODIAL PACKAGE: RECORD TRACKING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RTQ NAME: DBIA85-C ORIGINAL NUMBER: 85 ID: RTQ GENERAL DESCRIPTION: 1. Activation interface 2. Make an appointment Checkin/unscheduled visit 3. Cancel an appointment 4. Changing clinic names 1. Use of the Record Tracking System Parameter file # 195.4 SD calls RT if the field 'MAS INTERFACE STATUS' is 'UP' ^DIC(195.4,1,"UP")=1^ 2. When a clinic appointment is made if the appointment is 'today' or if the Record Tracking System Parameter 'Batch requests' is set to 'No' or if records are requested for an unscheduled visit. A. An entry is made in the Requested Records file #190.1 ^RTV(190.1,n) by a call from RT^SDUTL to a tasked job QUE^RTQ or RT^SDI B. After the entry is added to the Requested Records file #190.1 an entry is made in Parent Record Request field of the Patient subfield of the Hospital Location file #44 ^SC(n,"S",,,,"RTR")=n^ by a return call from CREATE+11^RTQ2 to RTSET^SDUTL 3. When a clinic appointment is canceled: If there is a Requested Records entry in file #190.1 the status is changed to 'canceled' by a call RTV(190.1,n)=^^^^^x^ from RT+2^SDUTL to CANCEL^RTQ2. 4. When the name of a clinic is changed the corresponding names of entries in the Pull List file #194.2 are changed by a trigger on the .01 field of the Hospital Location file #44. Clinic ^SC(1,0)=DJones Medical Clinic^ ^RTV(194.2,n)=Dr Jones Medical Clinic [04/01/91]^ Clinic names are changed in a compiled input template. To insure the use of this trigger the following action is taken: The Record Tracking package includes the .01 field of the Hospital Location file #44 so that the SDB template is re-compiled when the Record Tracking package is initialized. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: QUE SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 545 IA #: 545 DATE CREATED: JUL 09, 1991 CUSTODIAL PACKAGE: RECORD TRACKING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RTQ2 NAME: DBIA85-D ORIGINAL NUMBER: 85 ID: RTQ2 GENERAL DESCRIPTION: 1. Activation interface 2. Make an appointment Checkin/unscheduled visit 3. Cancel an appointment 4. Changing clinic names 1. Use of the Record Tracking System Parameter file # 195.4 SD calls RT if the field 'MAS INTERFACE STATUS' is 'UP' ^DIC(195.4,1,"UP")=1^ 2. When a clinic appointment is made if the appointment is 'today' or if the Record Tracking System Parameter 'Batch requests' is set to 'No' or if records are requested for an unscheduled visit. A. An entry is made in the Requested Records file #190.1 ^RTV(190.1,n) by a call from RT^SDUTL to a tasked job QUE^RTQ or RT^SDI B. After the entry is added to the Requested Records file #190.1 an entry is made in Parent Record Request field of the Patient subfield of the Hospital Location file #44 ^SC(n,"S",,,,"RTR")=n^ by a return call from CREATE+11^RTQ2 to RTSET^SDUTL 3. When a clinic appointment is canceled: If there is a Requested Records entry in file #190.1 the status is changed to 'canceled' by a call RTV(190.1,n)=^^^^^x^ from RT+2^SDUTL to CANCEL^RTQ2. 4. When the name of a clinic is changed the corresponding names of entries in the Pull List file #194.2 are changed by a trigger on the .01 field of the Hospital Location file #44. Clinic ^SC(1,0)=DJones Medical Clinic^ ^RTV(194.2,n)=Dr Jones Medical Clinic [04/01/91]^ Clinic names are changed in a compiled input template. To insure the use of this trigger the following action is taken: The Record Tracking package includes the .01 field of the Hospital Location file #44 so that the SDB template is re-compiled when the Record Tracking package is initialized. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: CANCEL SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 546 IA #: 546 FILE NUMBER: 194.2 GLOBAL ROOT: RTV(194.2, DATE CREATED: JUL 09, 1991 CUSTODIAL PACKAGE: RECORD TRACKING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA85-E ORIGINAL NUMBER: 85 ID: RTV(194.2, GENERAL DESCRIPTION: 1. Activation interface 2. Make an appointment Checkin/unscheduled visit 3. Cancel an appointment 4. Changing clinic names 1. Use of the Record Tracking System Parameter file # 195.4 SD calls RT if the field 'MAS INTERFACE STATUS' is 'UP' ^DIC(195.4,1,"UP")=1^ 2. When a clinic appointment is made if the appointment is 'today' or if the Record Tracking System Parameter 'Batch requests' is set to 'No' or if records are requested for an unscheduled visit. A. An entry is made in the Requested Records file #190.1 ^RTV(190.1,n) by a call from RT^SDUTL to a tasked job QUE^RTQ or RT^SDI B. After the entry is added to the Requested Records file #190.1 an entry is made in Parent Record Request field of the Patient subfield of the Hospital Location file #44 ^SC(n,"S",,,,"RTR")=n^ by a return call from CREATE+11^RTQ2 to RTSET^SDUTL 3. When a clinic appointment is canceled: If there is a Requested Records entry in file #190.1 the status is changed to 'canceled' by a call RTV(190.1,n)=^^^^^x^ from RT+2^SDUTL to CANCEL^RTQ2. 4. When the name of a clinic is changed the corresponding names of entries in the Pull List file #194.2 are changed by a trigger on the .01 field of the Hospital Location file #44. Clinic ^SC(1,0)=DJones Medical Clinic^ ^RTV(194.2,n)=Dr Jones Medical Clinic [04/01/91]^ Clinic names are changed in a compiled input template. To insure the use of this trigger the following action is taken: The Record Tracking package includes the .01 field of the Hospital Location file #44 so that the SDB template is re-compiled when the Record Tracking package is initialized. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 547 IA #: 547 FILE NUMBER: 45 GLOBAL ROOT: DGPT( DATE CREATED: JUL 10, 1991 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA87-B ORIGINAL NUMBER: 87 ID: DGPT( GENERAL DESCRIPTION: PTF FILE: Looks at 70 node (Discharge and ICD diagnosis info) and M multiple (movement data) and its ICD 1 field. (routine YSCEN32) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Salt Lake City NUMBER: 548 IA #: 548 FILE NUMBER: 8 GLOBAL ROOT: DIC(8, DATE CREATED: JUL 10, 1991 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA87-C ORIGINAL NUMBER: 87 ID: DIC(8, GENERAL DESCRIPTION: ELIGIBILITY CODE: Looks at .01. (routines: YSCEN23, YSCEN54, YSDGDEM, YSPP1A) Quality: Audiology and Speech Pathology Audit and Review (QUASAR) Package, A&SP CLINIC VISIT File (#509850.6), VISIT ELIGIBILITY Field (#80) points to the ELIGIBILITY CODE File (#8) to accommodate recording, tracking and reporting workload by visit eligibility. Quality: Audiology and Speech Pathology Audit and Review (QUASAR) Package, A&SP CLINIC VISIT File (#509850.6), PATIENT ELIGIBILITY Field (#2) points to the ELIGIBILITY CODE File (#8) to accommodate recording, tracking and reporting workload by patient eligibility. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Salt Lake City SUBSCRIBING PACKAGE: QUASAR ISC: Hines SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING PACKAGE: WOMEN'S HEALTH ISC: Hines SUBSCRIBING PACKAGE: CLINICAL REMINDERS NUMBER: 549 IA #: 549 FILE NUMBER: 37 GLOBAL ROOT: DIC(37, DATE CREATED: JUL 10, 1991 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA87-D ORIGINAL NUMBER: 87 ID: DIC(37, GENERAL DESCRIPTION: DISPOSITION FILE: (routine: YSPP4) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Salt Lake City NUMBER: 550 IA #: 550 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: JUL 10, 1991 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA87-E ORIGINAL NUMBER: 87 ID: DPT( GENERAL DESCRIPTION: PATIENT FILE (listed by field or node referenced. If a node is referenced, it will follow in ()s): CLAIM NUMBER and CLAIM FOLDER LOCATION (YSCEN23, YSDGDEM,YSCEN54, and YSPP1) RELIGION (YSCEN23, YSDGDEM, and YSCEN54) ELIGIBILITY CODE (YSCEN23, YSDGDEM, YSCEN54, and YSPP1A) EMERGENCY CONTACT NODE (.33) (YSCEN23, YSCEN54, and YSPP) NEXT OF KIN NODE (.21) (YSPP1) DESIGNEE NODE (.34) (YSPP1) ADDRESS NODE (.11) (YSCEN23 and YSDGDEM) PHONE NODE (.13) (YSCEN23, YSDGDEM, and YSPP) TEMPORARY ADDRESS NODE (.121) (YSCEN23 and YSDGDEM) ELIGIBILITY STATUS NODE (.361) (YSCEN23, YSDGDEM, and YSPP1A) SERIOUSLY ILL (YSDGDEM0) ENROLLMENT MULTIPLE (YSDGDEM0) APPOINTMENT MULTIPLE (YSDGDEM0) DISPOSITION MULTIPLE (YSPP4) INELIGIBLE DATE (YSPP, YSPP1) EMPLOYER NODE (.311) (YSPP1) SERVICE CONNECTED? (YSPP1) SERVICE CONNECTED PERCENTAGE (YSPP1) PARENTS' NAMES NODE (.24) (YSPP1) PRIOR CARE RECIEVED NODE (1010.15) (YSPP2) SERVICE RECORD NODE (.32) (YSPP2) AGENCY/ALLIED COUNTRY (YSPP2) COMBAT DATA (.52) (YSPP2) POW DATA (.52) (YSPP2) IONIZING RADIATION DATA (.321) (YSPP2) VIETNAM SERVICE DATA (.321) (YSPP3) AGENT ORANGE DATA (.321) (YSPP3) SERVICE DENTAL INJURY (YSPP3) SERVICE TEETH EXTRACTED? (YSPP3) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Salt Lake City NUMBER: 551 IA #: 551 DATE CREATED: AUG 06, 1991 CUSTODIAL PACKAGE: GRECC CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GECSX5 NAME: DBIA88-B ORIGINAL NUMBER: 88 ID: GECSX5 GENERAL DESCRIPTION: 1. The 'DG' post-init for MAS v5.1 will be calling the Generic Code Sheet routine A^GECSX5 to re-build the template maps for the input templates listed above. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: A SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 554 IA #: 554 FILE NUMBER: 63 GLOBAL ROOT: LR( DATE CREATED: OCT 28, 1997 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA91-B ORIGINAL NUMBER: 91 ID: LR( GLOBAL REFERENCE: LR(D0,'CH',D1,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME SPECIMEN TAKEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2... FIELD NAME: TEST RESULT~FLAG LOCATION: 0;1-2 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Direct global read of DD(63.04 is used to determine laboratory test names. GLOBAL REFERENCE: LR(D0,'MI',D1,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME SPECIMEN TAKEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .05 FIELD NAME: SITE/SPECIMEN LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,3,D2,0) FIELD NUMBER: .01 FIELD NAME: ORGANISM LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Direct global read of DD(63.3 and DD(63.3,"GL" nodes [Organism Sub-field]. FIELD NUMBER: 1 FIELD NAME: QUANTITY LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,3,D2,IFN) FIELD NUMBER: 5... FIELD NAME: ANTIBIOTIC~INTERP LOCATION: IFN;1-2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,6,D2,0) FIELD NUMBER: .01 FIELD NAME: PARASITE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Direct global read of DD(63.34 and DD(63.34,"GL" nodes [Parasite Sub-field]. GLOBAL REFERENCE: LR(D0,'MI',D1,6,D2,1,D3,0) FIELD NUMBER: .01 FIELD NAME: STAGE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: QUANTITY LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,9,D2,0) FIELD NUMBER: .01 FIELD NAME: FUNGUS/YEAST LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Direct global read of DD(63.37 and DD(63.37,"GL" nodes [Fungus/Yeast Sub-field]. FIELD NUMBER: 1 FIELD NAME: QUANTITY LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,12,D2,0) FIELD NUMBER: .01 FIELD NAME: MYCOBACTERIUM LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Direct global read of DD(63.39 and DD(63.39,"GL" nodes [Mycobacterium Sub-field]. FIELD NUMBER: 1 FIELD NAME: QUANTITY LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,'MI',D1,17,D2,0) FIELD NUMBER: .01 FIELD NAME: VIRUS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Direct global read of DD(63.43 and DD(63.43,"GL" nodes [Virus Sub-field]. GENERAL DESCRIPTION: Amended October 28, 1997. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25328368 SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION ISC: Oakland SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING DETAILS: CCR added as a subscriber on 11/27/13 after developer review found reference to ICR in routine RORUTL10 and believes reference has been in the routine since 2006. EDITOR: TRAXLER,FRANK DBA Comments: 11/27/13 - MM: Clinical Case Registries was added as a subscriber on 11/27/13 when references to the ICR were found in the Technical Manuals and in routine RORUTL10. As of 11/27/13, RORUTL10 has not been patched and it is assumed the request to add CCR as a subscriber was done prior to the release of Clinical Case Registries Version 1.5 in February 2006. No further review - Documentation only processing. DATE/TIME EDITED: NOV 27, 2013@12:06 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: RAY,CONNIE WITH CONCURRENCE OF: RAY,CONNIE NUMBER: 555 IA #: 555 FILE NUMBER: 61 GLOBAL ROOT: LAB(61, DATE CREATED: OCT 28, 1997 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA91-C ORIGINAL NUMBER: 91 ID: LAB(61, GLOBAL REFERENCE: LAB(61,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Amended October 28, 1997. Data from the following fields are accessed for read only (Read w/FileMan or Direct Global Read): ^LAB(61 TOPOGRAPHY FIELD File .01 NAME STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25328622 SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION ISC: Oakland NUMBER: 557 IA #: 557 FILE NUMBER: 40.7 GLOBAL ROOT: DIC(40.7, DATE CREATED: SEP 11, 1991 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA93-C ORIGINAL NUMBER: 93 ID: DIC(40.7, GLOBAL REFERENCE: DIC(40.7,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: AMIS REPORTING STOP CODE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: INACTIVE DATE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DIC(40.7,'C',X,DA) GLOBAL DESCRIPTION: The C cross-reference is used to determine Stop Code, as a direct global read. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11757796 SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY ISC: Oakland SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION ISC: Oakland SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City SUBSCRIBING DETAILS: PCE is the only user of the 'INACTIVE DATE' field. SUBSCRIBING PACKAGE: QUASAR ISC: Birmingham SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS SUBSCRIBING PACKAGE: INTEGRATED BILLING SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE SUBSCRIBING PACKAGE: SURGERY SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING PACKAGE: MYHEALTHEVET DBA Comments: 2/15/13 DT: Kumar worked out an agreement with Barbara Schuster from Systems Redesign Scheduling, Access & OPT Services to display stop code number and name in MyHealtheVet patch MHV*1.0*10. Added MyHealtheVet as subscriber. VPR added as a subscriber on 5/18/12 for VPR*1.0. DATE/TIME EDITED: MAY 18, 2012@15:33 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: YORTY,BOB DATE/TIME EDITED: FEB 15, 2013@16:23 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MARRI,NAGARAJA WITH CONCURRENCE OF: SCHUSTER,BARBARA DATE/TIME EDITED: FEB 15, 2013@16:24 ACTION: SUBSCRIBER ADDED NUMBER: 558 IA #: 558 DATE CREATED: SEP 24, 1991 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LRX NAME: DBIA95-B ORIGINAL NUMBER: 95 ID: LRX GENERAL DESCRIPTION: Request an agreement with the lab developers for usage of the following: variables: Only those associated with the routines below Routines from indicated entry points: PT^LRX STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: PT SUBSCRIBING PACKAGE: COMPENSATON AND PENSION ISC: Albany SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 10/1/14-MC: Added VPS as a subscriber as requested by Carolyn Wheless and approved by Carol Anzaldua for patch VPS*1*4. VPS will be required to return stored patient specimen data and patient information to VetLink as part of the RPC to access implementation to the VistA Howdy Computerized Phlebotomy Login Process. NUMBER: 559 IA #: 559 DATE CREATED: SEP 24, 1991 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LRRP2 NAME: DBIA95-C ORIGINAL NUMBER: 95 ID: LRRP2 GENERAL DESCRIPTION: Request an agreement with the lab developers for usage of the following: variables: Only those associated with the routines below Routines from indicated entry points: SWITCH^LRRP2 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: SWITCH SUBSCRIBING PACKAGE: COMPENSATON AND PENSION ISC: Albany NUMBER: 560 IA #: 560 FILE NUMBER: 49 GLOBAL ROOT: DIC(49, DATE CREATED: AUG 26, 1991 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA97-B ORIGINAL NUMBER: 97 ID: DIC(49, GENERAL DESCRIPTION: The DSS developers have agreed that the IMS developers may export file 730 (NATIONAL SERVICE) with data and field 730 (NATIONAL SERVICE) in file 49 (SERVICE/SECTION) with no data. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTERIM MANAGEMENT SUPPORT ISC: Birmingham NUMBER: 561 IA #: 561 GLOBAL ROOT: %ZTSK( DATE CREATED: MAR 20, 1991 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA98-B ORIGINAL NUMBER: 98 ID: %ZTSK( GENERAL DESCRIPTION: Version 5.1 of the laboratory package has a temporary agreement for the following: 2) To reference the global %ZTSK directly to display the error trap data. (Rick has been notified of our usage of the %ZTSK global) When Kernel release their error trapping system, Lab will convert to the Kernel supported methodology. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: LAB SERVICE ISC: Salt Lake City NUMBER: 563 IA #: 563 FILE NUMBER: 131.9 GLOBAL ROOT: SRO(131.9, DATE CREATED: JUL 28, 1991 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA103-B ORIGINAL NUMBER: 103 ID: SRO(131.9, GLOBAL REFERENCE: SRO(131.9,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 565 IA #: 565 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: JUN 22, 2005 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA104-C ORIGINAL NUMBER: 104 ID: DGPM( GLOBAL REFERENCE: DGPM(D0,0) FIELD NUMBER: .06 FIELD NAME: WARD LOCATION LOCATION: 0;6 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The listed references will be made from the QIP1* & QIP3SR* routines which, while belonging to the QIP namespace, will be maintained by the PIMS developers (for QIP1*) and surgery developers (for QIP3SR*). Coordination of release and patches will be through the QIP custodial ISC. To determine the associated admission for perioperative extracts, the following cross-reference is used: ^DGPM("APTT1" STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12081724 SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham DBA Comments: 12/24/14-MM: Phil Burkhalter from Scheduling Calendar View said the MBAA PATIENT ADMISSIONS RPC is not included in this release of SCV or VAR2. Request can be withdrawn. NUMBER: 581 IA #: 581 DATE CREATED: MAY 14, 1991 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGANHD3 NAME: DBIA111-B ORIGINAL NUMBER: 111 ID: DGANHD3 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: 2) AMIS Segments 345-346 This entry point prints the inpatient AMIS segments 345-346 for a select month/year. If the variable DGMYR is not defined, the user will be prompted for the AMIS month/year to print. SUBSCRIBING PACKAGE: INTERIM MANAGEMENT SUPPORT ISC: Birmingham NUMBER: 583 IA #: 583 DATE CREATED: AUG 24, 1991 CUSTODIAL PACKAGE: RECORD TRACKING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RTPSET NAME: DBIA115-B ORIGINAL NUMBER: 115 ID: RTPSET GENERAL DESCRIPTION: Radiology uses a call to APL1^RTPSET to access the RTAPL variable (record tracking system wide application variable) to insure the radiology application of record tracking is set prior to making a record request or displaying record information STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: APL1 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Albany NUMBER: 584 IA #: 584 DATE CREATED: AUG 24, 1991 CUSTODIAL PACKAGE: RECORD TRACKING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RTQ5 NAME: DBIA115-C ORIGINAL NUMBER: 115 ID: RTQ5 GENERAL DESCRIPTION: When registering a patient exam, requests for records from the radiology application of Record Tracking can be made by a call from the Radiology/Nuclear Medicine package to ^RTQ5. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14682303 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 585 IA #: 585 DATE CREATED: AUG 24, 1991 CUSTODIAL PACKAGE: RECORD TRACKING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RTRD NAME: DBIA115-D ORIGINAL NUMBER: 115 ID: RTRD GENERAL DESCRIPTION: When displaying exam profiles, location and record information is displayed by a call from RT^RAPROQ to ^RTUTL2. Paging assistance is provided by variable RTESC from a call to ESC^RTRD. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: ESC SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Albany NUMBER: 586 IA #: 586 FILE NUMBER: 71 GLOBAL ROOT: RAMIS(71, DATE CREATED: OCT 30, 1991 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA118-B ORIGINAL NUMBER: 118 ID: RAMIS(71, GLOBAL REFERENCE: RAMIS(71,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 9 FIELD NAME: CPT CODE LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 10 FIELD NAME: COST OF PROCEDURE LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: RAMIS(71,'D',X,DA) FIELD NUMBER: 9 FIELD NAME: CPT CODE ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: D cross-reference is used to determine CPT code. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11757794 SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY ISC: Oakland SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION ISC: Oakland SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 10/9/14-MC: Added VPS as a subscriber at the request of Carolyn Wheless and approved by Greg Cebelinski for VPS*1*4. VPS needs to return patient radiology/imaging requests to VetLink, including fields 2,3, and 17 from file #70.03 and field 2 from file #70.02 NUMBER: 587 IA #: 587 FILE NUMBER: 71.2 GLOBAL ROOT: RAMIS(71.2, DATE CREATED: OCT 30, 1991 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA118-C ORIGINAL NUMBER: 118 ID: RAMIS(71.2, GLOBAL REFERENCE: RAMIS(71.2,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11757794 SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION ISC: Oakland NUMBER: 590 IA #: 590 FILE NUMBER: 50 GLOBAL ROOT: PSDRUG( DATE CREATED: NOV 06, 1991 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA124-C ORIGINAL NUMBER: 124 ID: PSDRUG( GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. C. Direct reference to ^PSRX(n,0) and ^PSDRUG(n,0) by Integrated Billing for use to determine prescription number and drug name when calculating the Brief Description field. The MUMPS code to do this is stored in the IB ACTION TYPE file. D. Direct reference to ^PSRX by Integrated Billing to determine if the link between Integrated Billing and the Prescription file is intact. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 592 IA #: 592 FILE NUMBER: 350.1 GLOBAL ROOT: IBE(350.1, DATE CREATED: NOV 06, 1991 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA125-B ORIGINAL NUMBER: 125 ID: IBE(350.1, GLOBAL REFERENCE: IBE(350.1,DA, FIELD NUMBER: .05 FIELD NAME: SEQUENCE LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: A check is done when deleting a refill of a prescription that has Copay charges to this field, and if this field is not equal to "Cancel", a warning is given to user when deleting the refill that Copay charges must be removed before deleting the refill. GENERAL DESCRIPTION: 5. Direct reference to ^IBE(350.1,"B" to automatically determine the IB CHARGE REMOVAL REASON of "RX DELETED" when a prescription is deleted. . 6. Look-up by Outpatient Pharmacy to the IB CHARGE REMOVAL REASON file, as this is passed back to Integrated Billing with cancel transactions. The OUTPATIENT SITE File (#59) has a pointer field to the SERVICE/SECTION File (#49). For Pharmacy Copay to work, this field must match the SERVICE Field (#.04) for pharmacy action types in the IB ACTION TYPE File (#350.1). This is done by checking the "ANEW" cross reference on the SERVICE Field (#.04) in File 350.1 with a Direct Global read: I '$D(^IBE(350.1,"ANEW",pharmacy pointer,1,1))... STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 593 IA #: 593 DATE CREATED: NOV 06, 1991 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCASER1 NAME: DBIA127-B ORIGINAL NUMBER: 127 ID: PRCASER1 GENERAL DESCRIPTION: This routine is used for making transactions to an already existing bill. This would be used, for example, if a Pharmacy Co-Pay was charged and later canceled because the patient did not receive the RX. INPUT Variable: X $P1: Transaction type. This is the pointer to the Accounts Receivable Trans.Type file (430.3. Currently this program will support two types of transactions: INCREASE ADJUSTMENT Number: 1 DECREASE ADJUSTMENT Number: 21 This piece should be set to the internal value for these types, this may be found by direct accessing the "AC" cross-reference on the Number to determine the internal value. $P2: Amount. This would be the amount of the transaction. This number must be greater than 0 and less than 9999999.99. $P3: Bill Number. This must be the .01 value of the bill from the Accounts Receivable file (430) and must be 10 characters in length. (ex: 503-K10001). $P4: User. this is the person who is making the adjustment. Pointer to the User file (3). $P5: Adjustment Date. This is the internal VA FileMan date when the adjustment occurred. $P6: Reason. This is the free text reason that the adjustment took place (optional). Output Variable: Y $P1: Success flag. Equals 1 if successful, -1 if unsuccessful $P2: Error Code. This is the error code from the IB Error file. $P3: Addition Text. If additional text is required to describe the error then it is in the third piece. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 594 IA #: 594 FILE NUMBER: 430.2 GLOBAL ROOT: PRCA(430.2, DATE CREATED: NOV 06, 1991 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA127-C ORIGINAL NUMBER: 127 ID: PRCA(430.2, GLOBAL REFERENCE: PRCA(430.2,CAT,0) FIELD NUMBER: .01 FIELD NAME: CATEGORY LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used by various reports in the Diagnostic Measures module. Some examples of these reports are: First Party Follow-up Report, Miscellaneous Bills Report, among others. FIELD NUMBER: 1 FIELD NAME: ABBREVIATION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used by various reports in the Diagnostic Measures module. Some examples of these reports are: First Party Follow-up Report, Miscellaneous Bills Report, among others. FIELD NUMBER: 5 FIELD NAME: TYPE LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used by IB in the Diagnostic Measures module. The value in this field is used to classify an AR Category as FIRST PARTY or THIRD PARTY category. Basically, categories of types PATIENT or MEANS TEST PATIENT are considered First Party categories and the others Third Party. Two exceptions to this are the categories EX-EMPLOYEE and CURRENT EMPLOYEE that are always FIRST PARTY categories, independent of their type. GENERAL DESCRIPTION: Integrated Billing has permission to access the following fields: STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32843560 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 596 IA #: 596 DATE CREATED: NOV 06, 1991 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA127-E ORIGINAL NUMBER: 127 GENERAL DESCRIPTION: Export of data, files, functions, options, routines, templates and security keys by Version 1 of Integrated Billing as necessary to successfully implement the Pharmacy Co-pay project as follows: File Data ACCOUNTS RECEIVABLE (partial) (430) NO ACCOUNTS RECEIVABLE CATEGORY (430.2) YES ACCOUNTS RECEIVABLE TRANS.TYPE (430.3) YES ACCOUNTS RECEIVABLE FORM LETTER (434) YES BATCH TRANSACTION (435) YES AR DEBTOR (412) NO VENDOR (partial) (440) NO Functions PRCADDR1, PRCADDR2, PRCACITY, PRCASTATE, PRCAZIP Security keys PRCAY PAYMENT SUP Options PRCAL LIST MENU Accounts Receivable Status Reports PRCAD REPORT MENU Report Menu for Accounts Receivable PRCA CLERK`MENU Clerk's AR Menu PRCAC TR PAYMENT Enter a Payment Transaction PRCAC PROFILE Profile of Accounts Receivable PRCAE FOLLOW-UP Follow-up Letter Menu PRCAC TRANSACTION Adjustment to Accounts Receivable PRCAC CHANGE Update Accounts Receivable PRCAA SET/AUDIT NEW BILL Audit/Set up a New Accounts Receivable PRCAD RECON CASHIER Agent Cashier Report PRCAL REFER DC DC Pending Referral AR Listing PRCAL REF DOJ DOJ Pending Referral AR Listing PRCAL STATUS LIST Status listing for Bills PRCAB PRINT BILLS New Bill Forms Print PRCAA OLD BILL Establish/Edit Old Bills PRCAC TRANS PROFILE Transaction Profile PRCAL MEANS LIST Means Test AR List PRCAL OTHER LIST Other Category AR List PRCA FORWARD IRS OFFSETS Forward IRS OFFSETs to Austin PRCAY CREATE/EDIT BATCH Create/Edit Payment Batch PRCAT CREATE CALM Create CALM Code Sheet for Other AR Transactions PRCAT LIST NEW TRANSACTION Other Bills pending CALM Transaction (Print) PRCAT PAT REF NUMBER AR (New) Processing PRCAT USER AR - Accounts Receivable Menu PRCAT PAT COMMON Establish PAT Common Number Series PRCAY APPROVE BATCH Approve Batch PRCAY POST TRANS Post an approved batch to A/R PRCAY MASTER Agent Cashier PRCAY BATCH STATUS Batch Status Report PRCAY ENTER A PAYMENT Enter a Payment (Agent Cashier) Routines PRCAAD, PRCABIL, PRCABD, PRCABP1, PRCABP2, PRCABP3, PRCABP31, PRCACLM, PRCADJ, PRCADR, PRCADR1, PRCALST, PRCALT, PRCALT1, PRCAOFF, PRCAOFF2, PRCAPAT, PRCAPAY, PRCAPAY1, PRCAPAY2, PRCAPCL, PRCAPRO, PRCAPTR, PRCAREPT, PRCARLT, PRCASER, PRCASER1 , PRCASTA, PRCASVC3, PRCASVC4, PRCASVC5, PRCAUDT, PRCAUT1, PRCAWO, PRCAY, PRCAYAPP, PRCAYE, PRCAYHLP, PRCAYPT, PRCAYUT, PRCFACX0 Templates Type File --------------------------------------- PRCABILLVEN Input VENDOR PRCA FY ADJ2 BATCH Input AR TRANSACTION PRCA FY ADJ1 Input AR TRANSACTION PRCA FY ADJ2 Input AR TRANSACTION PRCA BATCH PAYMENT Input AR TRANSACTION PRCA PAYMENT Input AR TRANSACTION PRCA OLD SET Input ACCOUNTS RECEIVABLE PRCA SET Input ACCOUNTS RECEIVABLE PRCASVC STATUS Input ACCOUNTS RECEIVABLE PRCASV REL Input ACCOUNTS RECIEVABLE PRCAE AUDIT Input ACCOUNTS RECEIVABLE PRCAC LOCATE DEBTOR Input ACCOUNTS RECEIVABLE PRCAY TRANSACTION EDIT Input BATCH TRANSACTION PRCAY BATCH STATUS Print BATCH TRANSACTION PRCAR CASH Print AR TRANSACTION STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 599 IA #: 599 FILE NUMBER: 430.6 GLOBAL ROOT: PRCA(430.6, DATE CREATED: NOV 06, 1991 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA127-H ORIGINAL NUMBER: 127 ID: PRCA(430.6, GENERAL DESCRIPTION: Direct reference to the global ^PRCA(430.6, to add a new entry in version 1 on the post initialization routine. Direct refe rence to global ^PRCA(430.6 to determine and set pointer values in the ACCOUNTS RECEIVABLE CATEGORY file and in the IB ACTION TYPE file in the post initialization routine. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 600 IA #: 600 FILE NUMBER: 430.3 GLOBAL ROOT: PRCA(430.3, DATE CREATED: NOV 06, 1991 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA127-I ORIGINAL NUMBER: 127 ID: PRCA(430.3, GENERAL DESCRIPTION: Direct reference to global ^PRCA(430.3, to determine the internal number of the decrease adjustment type when doing a decrease adjustment and to determing the internal number of the increase adjustment type when doing an increase adjustment type (required for input to supported call PRCASER1). STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 601 IA #: 601 FILE NUMBER: 4 GLOBAL ROOT: DIC(4, DATE CREATED: NOV 20, 1991 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA128-B ORIGINAL NUMBER: 128 ID: DIC(4, GENERAL DESCRIPTION: New Bill and Edit Bill options have been modified to prompt the user "Edit Debtor Address" after he/she has entered/edited the bill. This prompt as well as the Edit AR Debtor Address option allow edits to the NEW PERSON and INSTITUTION file. for the INSTITUTION file ^DIC(4, 1) 4,1.01 - Street Address 1 2) 4,1.02 - Street Address 2 3) 4,1.03 - City 4) 4,.02 - State 5) 4,1.04 - Zip Code 6) 4.03,.03 - Phone Please keep in mind that "all users" with access to the Billing menu will be able to edit the debtor address fields (option 2). STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 602 IA #: 602 FILE NUMBER: 8 GLOBAL ROOT: DIC(8, DATE CREATED: DEC 04, 1991 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA130-B ORIGINAL NUMBER: 130 ID: DIC(8, GENERAL DESCRIPTION: Read only access to the following Files, Fields, & X-References: FILE: Eligibility Code (DIC 8) FIELDS: Name (.01) ^DIC(8,i,0) Uses the "B" X-reference ^DIC(8,"B",NAME,i) *this is being requested by other packages and may be incorporated into VADPT at which time we will ask packages to use the utility STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25725771 SUBSCRIBING PACKAGE: REMOTE ORDER/ENTRY SYSTEM SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 603 IA #: 603 FILE NUMBER: 31 GLOBAL ROOT: DIC(31, DATE CREATED: DEC 04, 1991 CUSTODIAL PACKAGE: HINQ CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA130-C ORIGINAL NUMBER: 130 ID: DIC(31, GENERAL DESCRIPTION: Read only access to the following Files, Fields, & X-References: FILE: DISABILITY CONDITION (31) ^DIC(31,i,0) Field .01 Name "C" X-ref ^DIC(31,"C",DX CODE,i) Field 2 DX Code (The diagonostic codes that may be used for eligibility determinations for ROES are stored in ^RMPFL(791810.3,. ROES $O's through these disabilities and looks them up in ^DIC 31 using the "C" c ross-reference. The array RMPFL is built to hold the disability conditions found.) *this is being requested by other packages and may be incorporated into VADPT at which time we will ask packages to use the utility STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: REMOTE ORDER/ENTRY SYSTEM NUMBER: 604 IA #: 604 FILE NUMBER: 35 GLOBAL ROOT: DIC(35, DATE CREATED: DEC 04, 1991 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA130-D ORIGINAL NUMBER: 130 ID: DIC(35, GENERAL DESCRIPTION: Read only access to the following Files, Fields, & X-References: FILE: OTHER FEDERAL AGENCY (35) ^DIC(35,i,0) FIELD .01 NAME *this is being requested by other packages and may be incorporated into VADPT at which time we will ask packages to use the utility STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: REMOTE ORDER/ENTRY SYSTEM NUMBER: 606 IA #: 606 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: DEC 05, 1991 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA132-B ORIGINAL NUMBER: 132 ID: DPT( GENERAL DESCRIPTION: For a 'death' movement: Inpatient Meds has a MUMPS cross-reference (#6) under DATE OF DEATH field (#.351) of the PATIENT file. This cross-reference also uses the PSJADT routines, first checking for the existence of the routine PSJADT. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 612 IA #: 612 FILE NUMBER: 36 GLOBAL ROOT: DIC(36, DATE CREATED: JAN 23, 1992 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA142-B ORIGINAL NUMBER: 142 ID: DIC(36, GLOBAL REFERENCE: DIC(36,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City NUMBER: 613 IA #: 613 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: JAN 23, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA142-C ORIGINAL NUMBER: 142 ID: DPT( GLOBAL REFERENCE: DPT(D0,.372,D1,0) FIELD NUMBER: .01 FIELD NAME: RATED DISABILITIES (VA) LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City NUMBER: 614 IA #: 614 DATE CREATED: MAR 05, 1992 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: OR NAME: DBIA145-B ORIGINAL NUMBER: 145 ID: OR STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: IN COMPONENT DESCRIPTION: When a user selects to review progress notes through OE/RR, one possible action to take is to select a new patient to review notes for. Rather than have the user return to the original patient upon exiting to OE/RR, I am using a call to D IN^OR to handle selecting a new patient; this call selects a new patient and updates all needed OR variables as well. As this piece of code requires ORVP be defined, I have placed a screen on the selection of the protocol that invokes this code from the Progress Notes review screen: I +XQORNOD(0),$D(ORVP) This eliminates the potential for a user to "^^"-jump to the review screen and error out of the program because ORVP was not defined. (The first piece of XQORNOD(0) holds the IFN of the selected protocol unless it was "^^"-jumped to.) SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 615 IA #: 615 DATE CREATED: MAR 11, 1992 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MCOR NAME: DBIA147-B ORIGINAL NUMBER: 147 ID: MCOR GENERAL DESCRIPTION: 2. This results pointer is updated via calls from the Medicine options which enter/edit results to EN^GMRCR and RESULT^GMRCR, which are documented in the Consult/Request Tracking package. Once the results variable pointer is defined, the Medicine Package has provided Consult/Request Tracking with an entry point PRINT^MCOR which extracts results information and stores them in an ^TMP array for display purposes in OE/RR and Consult/Request Tracking. In order to call PRINT^MCOR the Consult/Request Tracking package must define the following variables. ORACTION=8 GMRCSR=variable pointer to results file GMRCPRNM=Name of procedure type, which should equal one of the Procedure Types in File 697.2, the eighth piece. The call to get the Medicine Results formats the results in ^TMP("MC",$J,... The ^TMP("MC",$J temporary global may be deleted upon completion of use. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: PRINT SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 616 IA #: 616 FILE NUMBER: 697.2 GLOBAL ROOT: MCAR(697.2, DATE CREATED: MAR 11, 1992 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA147-C ORIGINAL NUMBER: 147 ID: MCAR(697.2, GLOBAL REFERENCE: MCAR(697.2,D0, FIELD NUMBER: 1 FIELD NAME: GLOBAL LOCATION LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 7 FIELD NAME: PRINT NAME LOCATION: 0;8 ACCESS: Read w/Fileman GENERAL DESCRIPTION: 3. In addition to the interface the Medicine Package has provided, an alternative method for the Medicine Package Users is provided in a stand alone option provided by the Consult/Request Tracking Package. This option functions as follows: - The user selects the Medicine Procedure Type from a Protocol Menu - The service related to the Procedure Type defined in the FILE LINK field in Protocol File is determined - The patient is selected. - Consults/Request for the Service and Patient are displayed. - At the Select Action: prompt, the user may select "AR" for associate results - The PRINT NAME field, in the 8th piece of the ^MCAR(697.2,D0,0) node is the text that the Consults package uses to do a look up on the "BA" cross-reference. The consult package gets the text for the look-up from the Protocol name by removing the "GMRCR " prefix. The result of the "BA" lookup allows us to find the entry in 697.2 that represents the type of procedure that consults is processing. The GLOBAL LOCATION, the 2nd piece of the ^MCAR(697.2,D0,0) global node tells Consults what file to look for the results in. A look-up in the GLOBAL LOCATION file allows the user to "ASSOCIATE RESULTS" with a consult, and provide the Medicine package with the consult it is linked to. - The user is allowed to select from the list of Results in this results file for the Patient. (Using Medicine "C" cross-ref.) - Once a result entry is selected, it may be viewed using the PRINT^MCOR, to verify these are the correct results to associate with the request. - The user is asked if the order status should be updated to 'Completed' (default is yes, if no, ORSTS is incomplete) - The user is asked to enter the name of the clinician responsible for the results. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 617 IA #: 617 FILE NUMBER: 50.6 GLOBAL ROOT: PSNDF( DATE CREATED: FEB 27, 1995 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA149-B ORIGINAL NUMBER: 149 ID: PSNDF( GLOBAL REFERENCE: PSNDF(D0,2,D1,0) FIELD NUMBER: 3 FIELD NAME: VA DRUG CLASSIFICATION LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSNDF(D0,2,D1) GLOBAL DESCRIPTION: Direct global read used to $ORDER through the DOSAGE FORM subfield. GLOBAL REFERENCE: PSNDF('B', GLOBAL DESCRIPTION: Direct global read access to the "B" cross-reference will be used to get the internal entry number of the entry. GLOBAL REFERENCE: PSNDF('T', GLOBAL DESCRIPTION: Direct global read access to the "T" cross-reference will be used to look up a drug by its TRADE NAME. GLOBAL REFERENCE: PSNDF(D0,0) FIELD NUMBER: .01 FIELD NAME: VA GENERIC NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .01 FIELD NAME: VA GENERIC NAME LOCATION: 0;1 ACCESS: Pointed to FIELD NUMBER: .01 FIELD NAME: VA GENERIC NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSN*4*94. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of June 1, 2006. The Adverse Reaction Tracking (ART) package will point to the National Drug (50.6) file. The ART package will do a direct global read of the VA DRUG CLASSIFICATION (3) field of the DOSAGE FORM subfield (2) multiple of the NATIONAL DRUG (50.6) file to get all the VA Drug Classes for an entry, e.g., D0=$O(^PSNDF(DA,2,D0)) ;loop through DOSAGE FORM subfield Drug Class=$P(^PSNDF(DA,2,D0,0),"^",3) The ART package can loop through the "B" and "T" cross-references. The "T" cross-reference is on the TRADE NAME field which is field #2 on the subfile 50.67. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 13620387 SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING ISC: Hines SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham EDITOR: RUZBACKI,RON T NUMBER: 619 IA #: 619 FILE NUMBER: 50 GLOBAL ROOT: PSDRUG( DATE CREATED: FEB 27, 1995 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA149-D ORIGINAL NUMBER: 149 ID: PSDRUG( GLOBAL REFERENCE: PSDRUG(DA,0) FIELD NUMBER: .01 FIELD NAME: GENERIC NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: VA CLASSIFICATION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .01 FIELD NAME: GENERIC NAME LOCATION: 0;1 ACCESS: Pointed to FIELD NUMBER: .01 FIELD NAME: GENERIC NAME LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: PSDRUG(DA,'ND') FIELD NUMBER: 25 FIELD NAME: NATIONAL DRUG CLASS LOCATION: ND;6 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. The Adverse Reaction Tracking (ART) package will point to the Drug (50) file. The ART package will: a. Use a direct global read on the GENERIC NAME (.01) field of the DRUG (50) file to get the Name of an entry, e.g., Name=$P(^PSDRUG(DA,0),"^"). b. Use a direct global read on the VA CLASSIFICATION (2) field of the DRUG (50) file to get the VA Drug Class of an entry, e.g., VA Class=$P(^PSDRUG(DA,0),"^",2). c. Use a direct global read on the NATIONAL DRUG CLASS (25) field of the DRUG (50) file to get the VA Drug Class of an entry, e.g., Drug Class=$P(^PSDRUG(DA,"ND"),"^",6). In each of these examples DA is an entry in the DRUG (50) file. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 13620467 SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING ISC: Hines EDITOR: BLOCKER,DAVE NUMBER: 620 IA #: 620 FILE NUMBER: 741.2 GLOBAL ROOT: QA(741.2, DATE CREATED: APR 20, 1992 CUSTODIAL PACKAGE: QUALITY ASSURANCE INTEGRATION CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA153-B ORIGINAL NUMBER: 153 ID: QA(741.2, GENERAL DESCRIPTION: Read access to find patients who have had a QA occurrence which was refered to peer review associated with a particular admission. FILE 741.2 QA OCCURRENCE REVIEW LEVEL Field 1 REVIEW LEVEL NUMBER STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: EXTERNAL PEER REVIEW ISC: Birmingham NUMBER: 625 IA #: 625 FILE NUMBER: 45 GLOBAL ROOT: DGPT( DATE CREATED: JUN 08, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA160-B ORIGINAL NUMBER: 160 ID: DGPT( GENERAL DESCRIPTION: Pulling over the following MAS data: 2) Automatic Casefinding PTF file Oncology is looking at the ^DGPT("ADS") cross-reference and accessing the ^DGPT(D0,70) NODE to find the malignant ICD9 discharge codes. Accessing pieces 10,16-19 and 20-24 on node 70. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ONCOLOGY ISC: Washington/Silver Spring NUMBER: 626 IA #: 626 FILE NUMBER: 70 GLOBAL ROOT: RADPT( DATE CREATED: JUN 08, 1992 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA163-B ORIGINAL NUMBER: 163 ID: RADPT( GENERAL DESCRIPTION: For Automatic Casefinding Radiology: Oncology looking at: ^RA(78.3 for a defined diagnostic code containing the word Malignancy... Check the ^RADPT("AR") cross-reference for date. Look at; ^RADPT(D0,"DT",D1,"P",D2,0) NODES for procedures which have the diagnostic code found above in ^RA(78.3 - we capture those patients and the date of the "suspicious procedures" STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ONCOLOGY ISC: Washington/Silver Spring NUMBER: 627 IA #: 627 DATE CREATED: JUN 15, 1992 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORUHDR NAME: DBIA165-B ORIGINAL NUMBER: 165 ID: ORUHDR STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: TIT COMPONENT DESCRIPTION: The Detailed Display (DT) and Results Display (RT) actions available in OE/RR are also available via Consult/Request Tracking screens. The OE/RR DT and RT require an ORIFN (Order File internal entry number), but the Consult/Request Tracking DT and RT needs to be able to occur even after the Order in the Order File has been purged. The documented entry point in the OE/RR developers Guide EXT^ORUHDR, has been previous used which set ORDG (Display Group), and ORVP (Patient variable pointer), and then called TIT^ORUHDR. The EXT^ORUHDR depends on the ORIFN to be defined in order to print the headers. To enable printing of headers from the Consult/Request Tracking review screens, a GMRC routine sets variables that EXT^ORUHDR would have set and calls TIT^ORUHDR directly, eliminating the requirement for ORIFN (File 100 internal entry number) to exist. SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 628 IA #: 628 DATE CREATED: JUN 15, 1992 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: OR6 NAME: DBIA165-C ORIGINAL NUMBER: 165 ID: OR6 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: SERV COMPONENT DESCRIPTION: SERV^OR6 ;entry point to print service copy when order released As a result of the beta test at SALEM, the need came up to be able to print the Consult Form automatically at a "forwarded TO services" printer. Presently this entry point is called by OE/RR when the order is "RELEASED" from OE/RR so the Consult Form will print automatically at the "TO service" printer. When a Consult is "Forwarded " from one service to another, the following OR variables are set and then the SERV^OR6 entry point is called enabling the automatic print of the Consult Form at the Forwarded TO service: ORIFN=Order File internal entry number ORAL(PKG,ORIFN)="", where PKG is the "Consult/Request Tracking" Package File internal entry number and ORVP=Variable pointer format for Patient File internal entry number ORPRES="6;NEW/UNSIGNED ORDERS" ORCHART=1 ORPX="" SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 629 IA #: 629 DATE CREATED: JUN 15, 1992 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORX4 NAME: DBIA165-D ORIGINAL NUMBER: 165 ID: ORX4 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: SCOPY COMPONENT DESCRIPTION: SCOPY^ORX4(ORPKG,ORDERS) ; Print Service Copies of orders for a package The Consult Form is generated from the Print Format utilities created by OE/RR. This entry point allows the user to be in the Consult/Request Tracking Review screen and select PS (Print Service Copy), similiar to the PS action in OE/RR processing. The two variables it uses are the Package File internal entry number, and the Order File internal entry number. SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 630 IA #: 630 DATE CREATED: JUN 15, 1992 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA165-E ORIGINAL NUMBER: 165 GENERAL DESCRIPTION: PRINT TEMPLATES: GMRC PROTOCOL LIST - This template uses the following fields to print a list of GMRC protocols defined in the Protocol File NAME ITEM TEXT GMRC PROTOCOL RPT - This template(uses the following fields to print details about GMRC protocols defined in the Protocol File NAME ITEM TEXT TYPE PRINT NAME PACKAGE FILE LINK DESCRIPTION SYNONYM ITEM SEQUENCE MNEMONIC GMRC PROTOCOL RPT HDR - This template is the HEADING for the GMRC PROTOCOL RPT print template. It includes a namespaced key for users to understand the namespacing of Protocol file entries used by the Consult/ Request Tracking package. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 631 IA #: 631 DATE CREATED: JUN 15, 1992 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA165-F ORIGINAL NUMBER: 165 GENERAL DESCRIPTION: SORT TEMPLATE: GMRC PROTOCOLS - This sort template is used for printing the Print Templates GMRC PROTOCOL LIST, and GMRC PROTOCOL RPT. The NAME field is used to extract all Protocol entries with a Prefix of GMRC. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 633 IA #: 633 FILE NUMBER: 3 GLOBAL ROOT: DIC(3, DATE CREATED: JUN 17, 1992 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA170-B ORIGINAL NUMBER: 170 ID: DIC(3, GENERAL DESCRIPTION: In the AMIE package a direct reference is made to the USER file ^DIC(3,X,2,X1) to determine if a user has the division in question. When this code is run in a Kernel 7 account it will not work properly. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 635 IA #: 635 DATE CREATED: JUN 19, 1992 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORUPREF2 NAME: DBIA181-B ORIGINAL NUMBER: 181 ID: ORUPREF2 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN3 COMPONENT DESCRIPTION: Utility for "on-the-fly" protocol creation. A default protocol is defined in file 101 for this to work off. Parameters are set in 100.99 to allow Clinical Coordinators to create their own package-specific protocols. The entry in the PROTOCOL file has the format: LR 121 GLUCOSE (where LR=namespace, 121=internal #, and GLUCOSE=name) Packages may also identify their own independent code to manage the building of protocols. REQUIRED VARIABLES: ORPKG (Package pointer (9.4); ORDEF (Default protocol for setting up protocols (101).); ORFL (File link - variable pointer format for procedure file. May be equal to ""if a package can't use a specific procedure file.); ORDANM (Optional name of the protocol. Should be in the format: NAMESPACE_PROCEDURE); ORDA (internal number of an existing protocol to be updated.); OPTIONAL VARIABLES: ORDA (pointer to existing protocol to be modified.); ORDNM (new .01 protocol name.); OREA (action used in lieu of default defined in OROEF.); ORTXT (name of protocol; if not defined, the .01 field of the procedure referenced is used.) SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 636 IA #: 636 DATE CREATED: JUN 19, 1992 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORUTL NAME: DBIA181-C ORIGINAL NUMBER: 181 ID: ORUTL STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: READ COMPONENT DESCRIPTION: Displays "Press return to continue" and waits. REQUIRED VARIABLES: NONE RETURNED VARIABLES: NONE SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 637 IA #: 637 DATE CREATED: JUN 19, 1992 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORX NAME: DBIA181-D ORIGINAL NUMBER: 181 ID: ORX STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: FILE COMPONENT DESCRIPTION: Creates new order and sets fields in the ORDER file (100). This entry point includes a 'D ST^ORX' to update the status. REQUIRED VARIABLES; ORL,ORPCL,ORNP or ORPV, ORVP OPTIONAL VARIABLES: ORCOST,OREVENT,ORIT,ORLOG,ORPK,ORPURG,ORSTOP,ORSTRT,ORSTS,ORTO, ORTS,ORTX(i). RETURNED VARIABLES: ORIFN NOTE: a) ORSTRT updates both the CURRENT and ORIGINAL Start Date fields. b) ORNP/ORPV updates both the CURRENT and ORIGINAL Agent/ Provider fields. COMPONENT/ENTRY POINT: RETURN COMPONENT DESCRIPTION: Updates order information such as the start date/time, stop date/time, display text, or order status. Call RETURN^ORX with ORIFN to update order information. This entry point includes a 'D ST^ORX' to update the status, if the variable ORETURN ("ORSTS") is defined. The array ORETURN with the appropriate subscripts for updating the order must be defined prior to calling this entry point. For example, if you want to update the cost of the order to $10, then you would call RETURN^ORX with the variable ORETURN ("ORCOST")=10. REQUIRED VARIABLES: ORIFN OPTIONAL VARIABLES: ORETURN ORETURN subscripts: ORCOST,OREVENT,ORIT,ORPK,ORPURG,ORNP/ORPV,ORSTOP,ORSTRT,ORSTS, ORETURN(ORTX,i) RETURNED VARIABLES: NONE NOTE: ORETURN(ORSTRT) updates the CURRENT Start Date. ORETURN (ORPV) updates the CURRENT agent/Provider. COMPONENT/ENTRY POINT: ST COMPONENT DESCRIPTION: Updates status. Call ST^ORX where ORIFN is defined and ORSTS is the internal entry number of the status in the ORDER STATUS file (100.1). This will replace the status for this ORIFN with the status in ORSTS. REQUIRED VARIABLES: ORIFN,ORSTS RETURNED VARIABLES: NONE SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 638 IA #: 638 DATE CREATED: JUN 19, 1992 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORX3 NAME: DBIA181-E ORIGINAL NUMBER: 181 ID: ORX3 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: NOTE COMPONENT DESCRIPTION: This is an entry point that creates a notification for a package. If the variable ORIFN is defined, the notification will be linked to an order in the ORDER file (100); otherwise, just the notification will be generated for a patient. SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 639 IA #: 639 DATE CREATED: JUN 19, 1992 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORX8 NAME: DBIA181-F ORIGINAL NUMBER: 181 ID: ORX8 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: NOTIF COMPONENT DESCRIPTION: NOTIF^ORX8(ORIFN,ORNOTE) Used when cleaning up a notification that is linked to an order. REQUIRED VARIABLES: ORNOTE(notification entry #) - must be set to null - notification entry number is from File 100.9, field .001(IFN) ORVP - patient identifier in the formal "DFN;DPT(" (ORVP is also used by other OE/RR routines and may already be available in your package.) REUTNRED VARIABLES; None OPTIONAL VARIABLES: ORIFN - the order that you want this notification to be linked to. ORIFN - the order that you want this notification to be linked to. SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 640 IA #: 640 DATE CREATED: JUN 19, 1992 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORX5 NAME: DBIA181-G ORIGINAL NUMBER: 181 ID: ORX5 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: DC COMPONENT DESCRIPTION: DC^ORX5 This entry is called when a package needs to create a DC order for an ordered item. When the DC order is signed, the ordered item is discontinued or cancelled. REQUIRED VARIABLES: ORIFN SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 641 IA #: 641 FILE NUMBER: 130 GLOBAL ROOT: SRF( DATE CREATED: JUL 16, 1992 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA185-B ORIGINAL NUMBER: 185 ID: SRF( GLOBAL REFERENCE: SRF(D0,0) GLOBAL REFERENCE: SRF('AOR',+ORLOC,SDT,SRN) GENERAL DESCRIPTION: An E3R has been issued, asking to modify the Health Summary Print by location option to allow selection of an Operating Room, and to queue the selected Health Summary Type to print for all patients scheduled for surgery in that OR on a user-specified date. To that end, the Print by Location driver has been modified to look at the "B" cross reference of the Operating Room File (i.e., ^SRS("B",+LOC,ORLOC)) to get the record number of the selected OR, and then traverse the "AOR" cross reference of the Surgery File (i.e., ^SRF("AOR",+ORLOC,SDT,SRN) to get the record number of each surgery. It then visits the zero-node of each Surgery record to get the patient, whom it adds to the list of patients for Health Summaries to be printed. Health Summary makes direct references to the above cited globals and cross references. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 642 IA #: 642 DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTU NAME: DBIA186-B ORIGINAL NUMBER: 186 ID: DGMTU STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$LST COMPONENT DESCRIPTION: Retrieve last Means Test date and status. COMPONENT/ENTRY POINT: $$MTS COMPONENT DESCRIPTION: Needed to display the Means Test status description for a given code in the bulletins which are generated when a patient's billable status changes. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE NUMBER: 643 IA #: 643 DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTUB NAME: DBIA186-C ORIGINAL NUMBER: 186 ID: DGMTUB STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$BIL COMPONENT DESCRIPTION: Determine if a patient was Category C on a specified date. COMPONENT/ENTRY POINT: $$BILST COMPONENT DESCRIPTION: Determine the last date on which a patient was Category C. COMPONENT/ENTRY POINT: $$CK COMPONENT DESCRIPTION: Determine if a Means Test is Category C or Pending Adjudication, and patient agrees to pay deductible. COMPONENT/ENTRY POINT: $$GMT(DFN,DGDT) COMPONENT DESCRIPTION: GMT Copayment Status (or pending adjudication) VARIABLES: $$GMT TYPE: Output VARIABLES DESCRIPTION: 1 - If the patient had GMT Copayment Status (or pending adjudication) at the given moment of time 0 - If the patient did not have GMT Copayment Status at the given moment of time -1 - If the GMT Copayment Status is unknown because the conversion is not completed. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient's IEN VARIABLES: DGDT TYPE: Input VARIABLES DESCRIPTION: Date in FM format. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: FEE BASIS ISC: Albany SUBSCRIBING DETAILS: Fee Basis has an agreement only to call entry point $$BIL. SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING DETAILS: ADDED 9/27/07 DATE/TIME EDITED: SEP 27, 2007@17:34 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: FAIN,ZACH NUMBER: 644 IA #: 644 DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VADPT NAME: DBIA186-D ORIGINAL NUMBER: 186 ID: VADPT STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: ELIG COMPONENT DESCRIPTION: Patient eligibility data printed on the appointment Check-off Sheets SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 645 IA #: 645 FILE NUMBER: 36 GLOBAL ROOT: DIC(36, DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA186-E ORIGINAL NUMBER: 186 ID: DIC(36, GLOBAL REFERENCE: DIC(36,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany NUMBER: 646 IA #: 646 FILE NUMBER: 40.8 GLOBAL ROOT: DG(40.8, DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA186-F ORIGINAL NUMBER: 186 ID: DG(40.8, GENERAL DESCRIPTION: 40.8 DG(40.8, MEDICAL CENTER DIVISION FILE -- Printed as part of BASC Locality Modifier entry/edit, the user is allowed to specify which division Check-off Sheets will be printed for, the user is allowed to choose clinics by division in the 'Clinic CPT Usage'report, pointed to by DIVISION field in the BASC Locality Modifier file (350.5), division is used in the BASC charge calculation .01 NAME 45 DGPT PTF -- Printed on the patient appointment Check-off Sheet 70 DISCHARGE DATE 79 DXLS 79.16 ICD 2 79.17 ICD 3 X-REF: AAD STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 649 IA #: 649 FILE NUMBER: 391 GLOBAL ROOT: DG(391, DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA186-I ORIGINAL NUMBER: 186 ID: DG(391, GLOBAL REFERENCE: DG(391,D0,0) FIELD NUMBER: .02 FIELD NAME: IGNORE VETERAN CHECKS? LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: Used on a patients Check-off Sheet when determining veteran status STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING PACKAGE: CLINICAL PROCEDURES NUMBER: 651 IA #: 651 FILE NUMBER: 41.3 GLOBAL ROOT: DG(41.3, DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA186-K ORIGINAL NUMBER: 186 ID: DG(41.3, GENERAL DESCRIPTION: Date of Test multiple Conversion of Month/Year multiple MT billing data. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 652 IA #: 652 FILE NUMBER: 42 GLOBAL ROOT: DIC(42, DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA186-L ORIGINAL NUMBER: 186 ID: DIC(42, GENERAL DESCRIPTION: 0th node-- Determine ward type, division of ward. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 653 IA #: 653 FILE NUMBER: 45.7 GLOBAL ROOT: DIC(45.7, DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA186-M ORIGINAL NUMBER: 186 ID: DIC(45.7, GENERAL DESCRIPTION: 0th node-- Determine billable SPECIALTY, #42.4 0th node-- bedsection STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 654 IA #: 654 FILE NUMBER: 45 GLOBAL ROOT: DGPT( DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA186-N ORIGINAL NUMBER: 186 ID: DGPT( GENERAL DESCRIPTION: 101 node-- Determine if admitted VA ADM. REG., #43.4 "D" cross-reference for Observation & SOURCE OF ADM.,#45.1 "B" cross-reference Examination STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 655 IA #: 655 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA186-O ORIGINAL NUMBER: 186 ID: DGPM( GENERAL DESCRIPTION: PATIENT MOVEMENT, #405 0th nod-- Determine whether to bill patient. -- "ATT1" cross-reference Determine whether -- "APCA" cross-reference patients have been -- "APTT1" cross-reference cont. hospitalized STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 656 IA #: 656 FILE NUMBER: 405.1 GLOBAL ROOT: DG(405.1, DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA186-P ORIGINAL NUMBER: 186 ID: DG(405.1, GENERAL DESCRIPTION: FAC. MVMT TYPE, #405.1 0th node-- List movement type STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 657 IA #: 657 FILE NUMBER: 40 DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA186-Q ORIGINAL NUMBER: 186 GENERAL DESCRIPTION: IB DIVISION DISPLAY on file 40.-- Displays a division's billing fields: .01 NAME-- history STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 658 IA #: 658 FILE NUMBER: 31 GLOBAL ROOT: DIC(31, DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: HINQ CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA187-B ORIGINAL NUMBER: 187 ID: DIC(31, GLOBAL REFERENCE: DIC(31, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: SENSITIVE CONDITION PRINT NAME LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: QUASAR ISC: Birmingham SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE NUMBER: 664 IA #: 664 DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAUTOMA NAME: VA UTILITY ONE/MANY/ALL ORIGINAL NUMBER: 188 ID: VAUTOMA CREATOR: MULLER,RICHARD STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: CLINIC COMPONENT DESCRIPTION: Used to choose which clinics to search for the 'Clinic CPT Usage' report ^ COMPONENT/ENTRY POINT: DIVISION COMPONENT DESCRIPTION: Used to choose divisions to search for the 'Clinic CPT' report and Check Sheets COMPONENT/ENTRY POINT: FIRST COMPONENT DESCRIPTION: Used to choose clinics (limited to specific divisions) to search for Check-off Sheets COMPONENT/ENTRY POINT: WARD COMPONENT DESCRIPTION: Used to choose wards (limited to specific divisions) from the WARD LOCATION file (#42). (INPATIENT MEDICATION) Note: This tag will define variable DUOUT if the user selects the up-arrow ('^') to exit from its prompt, or when exiting from the question mark-generated ('?') list of selectable wards. In the latter case, if the user then selects the 'ALL' default response, DUOUT remains defined, but variable VAUTW will be set to 1 (one). SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS SUBSCRIBING DETAILS: added 6/3/09 SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING DETAILS: ADDED 11/6/08 SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE SUBSCRIBING DETAILS: AR ADDED 6/6/2011 DBA Comments: 11/6/08 - SCHEDULING ADDED AS SUBSCRIBER. 6/3/09 - INPT MEDS ADDED AS SUBSCRIBER, WARD COMPONENT ADDED AS ALLOWABLE, AND TITLE OF ICR CHANGED. 4/10/13-mm: SELDIV~TIULA calls DIVISION~VAUTOMA to prompt the user for one, many or all divisions. If the user selects one or more divisions, TIULPA modifies the array returned by DIVISION~VAUTOMA to return the IEN from the Institution (#4) file for the selected division(s). See ICR for those subscribers indirectly using DIVISION~VAUTOMA through the TIU API. DATE ACTIVATED: JUN 03, 2009 DATE/TIME EDITED: JUN 03, 2009@14:44 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: MULLER,RICHARD WITH CONCURRENCE OF: HARVEY,JULIE DATE/TIME EDITED: JUL 21, 2009@00:26 ACTION: APPROVED AT THE REQUEST OF: MULLER,RICHARD WITH CONCURRENCE OF: SILVERMAN,ROBERT DATE/TIME EDITED: JUN 03, 2009@15:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MULLER,RICHARD DATE/TIME EDITED: JUN 03, 2009@15:01 ACTION: CONTENT CORRECTED AT THE REQUEST OF: MULLER,RICHARD DATE/TIME EDITED: NOV 06, 2008@13:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CURTIS,RICHARD WITH CONCURRENCE OF: PRIETULA,LAURA DATE/TIME EDITED: JUL 21, 2009@15:20 ACTION: SUBSCRIBER ADDED DATE/TIME EDITED: DEC 07, 2011@15:10 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HARTLEY,PETER NUMBER: 668 IA #: 668 FILE NUMBER: 409.71 GLOBAL ROOT: SD(409.71, DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA188-K ORIGINAL NUMBER: 188 ID: SD(409.71, GENERAL DESCRIPTION: SD(409.71 AMBULATORY PROCEDURE--Pointed to by PROCEDURE field in the BILLABLE AMBULATORY SURGICAL CODE file (350.4), pointed to by PROCEDURE field in the AMBULATORY SURG.CHECK-OFF SHEET PRINT FIELDS file (350.71) 409.71 SD(409.71 AMBULATORY PROCEDURE .01 CODE-- When BASC codes are added to 350.4 the CPT is added to 409.71 if its not already there [SD-AMB-PROC-EDIT] Edit template used if new entry is added to file 409.71 during interactive edit of file 350.4 100 SYNONYMS SUBFILE (ALL) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany NUMBER: 669 IA #: 669 FILE NUMBER: 40.7 GLOBAL ROOT: DIC(40.7, DATE CREATED: JUL 22, 1992 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA188-L ORIGINAL NUMBER: 188 ID: DIC(40.7, GENERAL DESCRIPTION: ^DIC(40.7,Clinic Stop)-- ^IBOVOP1: get clinic name - 0;1 NAME STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 672 IA #: 672 FILE NUMBER: 120.8 GLOBAL ROOT: GMR(120.8, DATE CREATED: AUG 06, 1992 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA190-B ORIGINAL NUMBER: 190 ID: GMR(120.8, GENERAL DESCRIPTION: The Medicine package also needs to reference the following data elements: Patient Allergies (120.8) file: REACTION:REACTION (10,.01) and REACTION:OTHER REACTION (10,1) which is located in $P(^GMR(120.8,D0,10,D1,0),U,1,2). -D0 would be obtained from a call to ^GMRADPT, and D1 would be obtained by looping through the multiple. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 673 IA #: 673 FILE NUMBER: 120.83 GLOBAL ROOT: GMRD(120.83, DATE CREATED: AUG 06, 1992 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA190-C ORIGINAL NUMBER: 190 ID: GMRD(120.83, GLOBAL REFERENCE: GMRD(120.83,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: "B" xref on NAME (.01) field which is located in ^GMRD(120.83,"B") -This is used to determine if an entry in the REACTIONS multiple, described above, points to the entry "OTHER REACTION". STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 674 IA #: 674 DATE CREATED: AUG 18, 1992 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSODEM NAME: DBIA191-B ORIGINAL NUMBER: 191 ID: PSODEM GENERAL DESCRIPTION: ^PSODEM: This is Pharmacy's MAS patient demographic function which is used in conjunction with the Pharmacy Patient profile. The input variable is DA and is the internal entry number of the VA Patient file and is equivalent to the DFN. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring EDITOR: BLOCKER,DAVE NUMBER: 675 IA #: 675 DATE CREATED: AUG 18, 1992 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOFUNC NAME: DBIA191-C ORIGINAL NUMBER: 191 ID: PSOFUNC GENERAL DESCRIPTION: STAT^PSOFUNC: This is the Pharmacy treatment status function and is used in the Pharmacy patient profile. The required variables are RX0, RX2, and J. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: STAT SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring NUMBER: 676 IA #: 676 DATE CREATED: AUG 18, 1992 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOP NAME: DBIA191-D ORIGINAL NUMBER: 191 ID: PSOP GENERAL DESCRIPTION: DOIT^PSOP: This is the Pharmacy queue report entry point. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: DOIT SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring NUMBER: 679 IA #: 679 FILE NUMBER: 50 GLOBAL ROOT: PSDRUG( DATE CREATED: AUG 18, 1992 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA191-G ORIGINAL NUMBER: 191 ID: PSDRUG( GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. ^PSDRUG(DA, for drug data. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring NUMBER: 680 IA #: 680 FILE NUMBER: 61.5 GLOBAL ROOT: LAB(61.5, DATE CREATED: SEP 24, 1992 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA196-B ORIGINAL NUMBER: 196 ID: LAB(61.5, GENERAL DESCRIPTION: The Medicine package has permission from the Lab developers to correct the double entry (CARDIOASSIST, AORTIC BALLOON PUMP) in the Lab SNOMED file. The Medicine package has permission from the Lab developers to create pointer values to the Lab SNOMED code file entries. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring NUMBER: 681 IA #: 681 FILE NUMBER: 63 GLOBAL ROOT: LR( DATE CREATED: SEP 24, 1992 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA196-C ORIGINAL NUMBER: 196 ID: LR( GLOBAL REFERENCE: LR(D0,'CH', GENERAL DESCRIPTION: The Medicine package has permission from the Lab developers to use the following root for Fileman access to Lab chemistry values: ^LR(DFN,""CH"", (for display only) . STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring NUMBER: 682 IA #: 682 FILE NUMBER: 442 GLOBAL ROOT: PRC(442, DATE CREATED: NOV 24, 1992 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA198-B ORIGINAL NUMBER: 198 ID: PRC(442, GENERAL DESCRIPTION: In an effort to provide a receiving mechanism for Controlled Substances module, several look-ups and pointers are necessary for an interim interface. For Purchase Order receipts, a lookup to PROCUREMENT & ACCOUNTING TRANSACTIONS file 442, screened by cost center [822400] is used. For Issue Receipts, a lookup occurs, screened by cost center [822400], in CONTROL POINT ACTIVITY file 410. A connection between the DRUG file 50 and ITEM MASTER file 441 is crucial for posting receipt information. This may be a one-to-many relationship and therefore involves the creation of a multiple IFCAP ITEM NUMBER field (#50.0441) in the DRUG file 50 pointing to the ITEM MASTER file 441. This field includes an input transform similar to that found in the NDC field in the ITEM MASTER file 441 preventing the linking of the same item to more than one drug. It also includes an 'AB' whole file cross-reference. Pointer to CONTROL POINT ACTIVITY file 410 Pointer to ITEM MASTER file 441 Pointer to PROCUREMENT & ACCOUNTING TRANSACTIONS file 442 References information (Read only) from PROCUREMENT & ACCOUNTING TRANSACTIONS file 442 .01 PURCHASE ORDER NUMBER .6 PARTIAL 40 ITEM .01 LINE ITEM NUMBER 1 DESCRIPTION 1.5 REPETITIVE (PR CARD) NO. 3.1 PACKAGING MULTIPLE 9 VENDOR STOCK NUMBER 5 ACTUAL UNIT COST 20 DATE RECEIVED 1 QTY BEING RECEIVED "AB" X-REF ON P.O. DATE (FIELD .1) IFCAP files are used solely to gather and display receipt information and so the Controlled Substances files 58.8 and 58.81 can accumulate a receipt history. DURATION: Till otherwise agreed, when the GIP & Drug Accountability interf ace is available STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 684 IA #: 684 FILE NUMBER: 63 GLOBAL ROOT: LR( DATE CREATED: FEB 18, 1993 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA211-B ORIGINAL NUMBER: 211 ID: LR( CREATOR: SCHLEHUBER,CAMERON GENERAL DESCRIPTION: The current verification cycle of Health Summary (v2.5) has identified a number of references to fields in Laboratory files, most of which were present in our previous version (v1.2), but which were not documented in our DBIA's (#67, #71, or #155) with the LAB SERVICE Package. All Health Summary components which present Laboratory data have continued to function without incident at all sites where Health Summary is known to be in use, but we wanted to be sure that all of our external references were known to the developers of the custodial packages, if only to avoid the potential for future surprises. So, the previously undocumented references include: Global: ^LR( File #: 63 File Name: LAB DATA File In all cases, before calling the appropriate extract routine, we check for the existence of Laboratory data for the patient in question by evaluating the condition: I '$D(^LR(LRDFN)) D NOLABS Q, where LRDFN is derived from: S LRDFN=+^DPT(DFN,"LR"). These references were not expicitly documented in existing DBIA's. Node: "MI" Sub-file #: 63.05 Sub-File Name: MICROBIOLOGY Sub-node: 3 Sub-Sub-file: 63.3 Sub-Sub-file Name: ORGANISM Before extrancting antibiotic susceptibilities, we test for results using the condition: I $O(^LR(LRDFN,"MI",IX,3,ISO,1)). Reference to this multiple was not documented in existing DBIA's. Sub-nodes: 5 & 6 Sub-Sub-file: 63.34 Sub-Sub-file Name: PARASITE Before extracting parasitology data, we test for results using the condition: Q:'($D(^LR(LRDFN,"MI",IX,5))&($D(^(6)))). (i.e., we only proceed when data are available). Reference to these nodes was not documented in existing DBIA's. Sub-nodes: 8&9 Sub-Sub-file: 63.37 Sub-Sub-file Name: FUNGUS/YEAST Before extracting mycology data, we test for results using the condition: Q:'($D(^LR(LRDFN,"MI",IX,8))&($D(^(9)))). (i.e., we only proceed when data are available). Reference to these nodes was not documented in existing DBIA's. Sub-nodes: 11&12 Sub-Sub-file: 63.39 Sub-Sub-file Name: MYCOBACTERIUM Before extracting mycobacteriology data, we test for results using the condition: Q:'($D(^LR(LRDFN,"MI",IX,11))&($D(^(12)))). (i.e., we only proceed when data are available). Reference to these nodes was not documented in existing DBIA's. Sub-nodes: 16&17 Sub-Sub-file: 63.43 Sub-Sub-file Name: VIRUS Before extracting virology data, we test for results using the condition: Q:'($D(^LR(LRDFN,"MI",IX,16))&($D(^(17)))). (i.e., we only proceed when data are available). Reference to these nodes was not documented in existing DBIA's. Sub-node: 14 Sub-Sub-file: 63.42 Sub-Sub-file Name: ANTIBIOTIC LEVEL Sub-Sub-node piece Sub-Sub-fld Sub-Sub-Fld Name 0 1 .01 ANTIBIOTIC (for SERUM LEVEL) 0 2 1 DRAW TIME 0 3 2 CONC(ug/ml) Before checking for antibiotic serum levels under this multiple, we test for results using the condition: I $D(^LR(LRDFN,"MI",IX,14)). This was added to accommodate those sites which still store peak and trough antibiotic levels in this manner, rather than under the "CH" subscript (e.g., Hines VAMC). Node: "SP" Sub-file #: 63.08 Sub-File Name: SURGICAL PATHOLOGY Sub-node piece Sub-fld Sub-Fld Name 0 11 .11 REPORT RELEASE DATE (This sub-field was documented in DBIA #67, but was referred to under its old field name "RELEASE REPORT") STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING DBA Comments: 4/20/12 - LSPR project discovered with patch OR*3*315 that a routine was accessing these fields in the LR global but could not find an ICR granting access to CPRS. They requested OE/RR be added as a subscriber to this ICR. DEFERRED UNTIL: MAR 28, 2007 DATE/TIME EDITED: MAR 04, 2007@21:37 ACTION: POSTPONED UNTIL PATCH RELEASE AT THE REQUEST OF: ELLZEY,LINDA DATE/TIME EDITED: APR 20, 2012@14:15 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CRUMLEY,JAMIE WITH CONCURRENCE OF: CRUMLEY,JAMIE REMINDER: MAR 20, 2007 NUMBER: 685 IA #: 685 FILE NUMBER: 65 GLOBAL ROOT: LRD(65, DATE CREATED: FEB 18, 1993 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA211-C ORIGINAL NUMBER: 211 ID: LRD(65, GENERAL DESCRIPTION: The current verification cycle of Health Summary (v2.5) has identified a number of references to fields in Laboratory files, most of which were present in our previous version (v1.2), but which were not documented in our DBIA's (#67, #71, or #155) with the LAB SERVICE Package. All Health Summary components which present Laboratory data have continued to function without incident at all sites where Health Summary is known to be in use, but we wanted to be sure that all of our external references were known to the developers of the custodial packages, if only to avoid the potential for future surprises. So, the previously undocumented references include: Global: ^LRD(65, File #: 65 File Name: BLOOD INVENTORY File Node piece field # Field Name 0 4 .04 COMPONENT 8 3 8.3 DONATION TYPE (we check for the existence of the "8-node prior" to calling EN^DIQ1 to get the external format of the DONATION TYPE field) Node: 3 Sub-file #: 65.03 Sub-File Name: DATE/TIME UNIT RELOCATION Sub-node piece Sub-fld Sub-Fld Name 0 4 .04 LOCATION (this sub-field is accessed to determine the last known location of a given unit). STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 686 IA #: 686 FILE NUMBER: 69 GLOBAL ROOT: LRO(69, DATE CREATED: FEB 18, 1993 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA211-D ORIGINAL NUMBER: 211 ID: LRO(69, GENERAL DESCRIPTION: The current verification cycle of Health Summary (v2.5) has identified a number of references to fields in Laboratory files, most of which were present in our previous version (v1.2), but which were not documented in our DBIA's (#67, #71, or #155) with the LAB SERVICE Package. All Health Summary components which present Laboratory data have continued to function without incident at all sites where Health Summary is known to be in use, but we wanted to be sure that all of our external references were known to the developers of the custodial packages, if only to avoid the potential for future surprises. So, the previously undocumented references include: Global: ^LRO(69, File #: 69 File Name: LAB ORDER ENTRY File Node: 1 Sub-file #: 69.01 Sub-File Name: SPECIMEN # Sub-node piece Sub-fld Sub-Fld Name 3 1 .01 LAB ARRIVAL TIME 3 2 .02 DATE/TIME RESULTS AVAILABLE (these fields are accessed to determine the status of a given lab order). Sub-node: 4 Sub-sub-file #: 69.02 Sub-sub-file Name: SPECIMEN Sub-sub-node piece Sub-sub-fld Sub-sub-fld Name 0 1 .01 SPECIMEN STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 687 IA #: 687 FILE NUMBER: 68 GLOBAL ROOT: LRO(68, DATE CREATED: FEB 18, 1993 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA211-E ORIGINAL NUMBER: 211 ID: LRO(68, GENERAL DESCRIPTION: The current verification cycle of Health Summary (v2.5) has identified a number of references to fields in Laboratory files, most of which were present in our previous version (v1.2), but which were not documented in our DBIA's (#67, #71, or #155) with the LAB SERVICE Package. All Health Summary components which present Laboratory data have continued to function without incident at all sites where Health Summary is known to be in use, but we wanted to be sure that all of our external references were known to the developers of the custodial packages, if only to avoid the potential for future surprises. So, the previously undocumented references include: Global: ^LRO(68, File #: 68 File Name: ACCESSION File Node: 1 Sub-file #: 68.01 Sub-File Name: DATE Sub-node: 1 Sub-sub-file #: 68.02 Sub-sub-file Name: ACCESSION # Sub-sub-node piece Sub-sub-fld Sub-sub-fld Name .2 1 15 ACCESSION We determine the Accession number using the following code: S ACC=$S($D(^LRO(68,+ACCA,1,+ACCD,1,+ACCN,.2)):^(.2),1:"NONE") STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 688 IA #: 688 DATE CREATED: MAR 04, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VACPT NAME: DBIA218-B ORIGINAL NUMBER: 218 ID: VACPT GENERAL DESCRIPTION: The Surgery package has permission from the MAS package to do the following: Make a call to the routine VACPT. The call to ^VACPT is made upon entry into the Surgery package to display the CPT copyright message. Surgery executes ^%ZOSF("TEST") before calling ^VACPT. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 689 IA #: 689 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: MAR 04, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA218-C ORIGINAL NUMBER: 218 ID: DPT( GENERAL DESCRIPTION: Surgery is also granted permission from the MAS package to make the following references (READ only) to MAS data. The first two references listed are used in conjunction with the Surgery Mortality Report. ^DPT("AEXP1",DATE OF DEATH,DFN) The Surgery Mortality Report loops through the "AEXP1" cross reference to locate patients who expired within a selected date range. Surgery also has permission to call the following: The Surgery Waiting List reports include items from the PATIENT file (#2) almost all of which we are able to retrieve by means of supported calls to VADPT. One item that is not returned by VADPT is the patient's telephone number at work, which is stored in the PHONE NUMBER [WORK] field (#.132), located in $P(^DPT(DFN,.13),"^",2). Surgery has permission to READ only the second piece of the .13 node for the patient's work telephone number. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 690 IA #: 690 FILE NUMBER: 45 GLOBAL ROOT: DGPT( DATE CREATED: MAR 04, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA218-D ORIGINAL NUMBER: 218 ID: DGPT( GENERAL DESCRIPTION: Surgery is also granted permission from the MAS package to make the following references (READ only) to MAS data. 3rd piece of ^DGPT(INTERNAL ENTRY IN FILE 45,70) Once the patient's last admission is determined, the Mortality Report checks this piece, which stores the TYPE OF DISPOSITION, to determine whether an autopsy was performed. If the TYPE OF DISPOSITION is 6, an autopsy was performed; if 7, no autopsy was performed; if not 6 or 7, the autopsy information is not available. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 691 IA #: 691 FILE NUMBER: 41.1 GLOBAL ROOT: DGS(41.1, DATE CREATED: MAR 04, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA218-E ORIGINAL NUMBER: 218 ID: DGS(41.1, GENERAL DESCRIPTION: Surgery is also granted permission from the MAS package to make the following references (READ only) to MAS data. The following two items are used together on several reports. ^DGS(41.1,"B",DFN,INTERNAL ENTRY IN FILE 41.1) The various Surgery Schedule reports loop through the B cross reference to locate scheduled admissions for the patient if the patient is not an inpatient already. Second piece of ^DGS(41.1,INTERNAL ENTRY IN FILE 41.1,0) This piece, which holds the RESERVATION DATE/TIME of the scheduled admission, is checked for each scheduled admission found in the B cross reference to determine if the RESERVATION DATE/TIME is future. If there is a future scheduled admission, the report prints "ADM. PENDING" for the patient. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 692 IA #: 692 FILE NUMBER: 50.416 GLOBAL ROOT: PS(50.416, DATE CREATED: APR 21, 1993 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA221-B ORIGINAL NUMBER: 221 ID: PS(50.416, CREATOR: HERRING,VENESSA GLOBAL REFERENCE: PS(50.416,D0,1,0) FIELD NUMBER: 1 FIELD NAME: DRUG IDENTIFIER ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(50.416,D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: DRUG IDENTIFIER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(50.416,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Outpatient Pharmacy is given permission by Pharmacy to make the following calls: GLOBAL MAP DATA DICTIONARY #50.416 -- DRUG INGREDIENTS FILE 2/26/93 STORED IN ^PS(50.416, SITE: ISC BIRMINGHAM ----------------------------------------------------------------------- ^PS(50.416,D0,0)= (#.01) NAME [1F] ^ ^PS(50.416,D0,1,0)=^50.4161A^^ (#1) DRUG IDENTIFIER ^PS(50.416,D0,1,D1,0)= (#.01) DRUG IDENTIFIER [1F] ^ STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham DBA Comments: 07/30/13 DT: Add Venessa Herring as editor. This agreement is between to Pharmacy package - for which both packages agree to the change. 6/5/14 - Added Name (#.01) field to Global Referene section. It was listed in the ICR prior to the latest updates. Removed Venessa as editor. ICR already has a status of Active. Did not need to reactivate. DATE/TIME EDITED: JUL 30, 2013@12:49 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: HERRING,VANESSA WITH CONCURRENCE OF: TATUM,BILL DATE/TIME EDITED: JUN 05, 2014@14:42 ACTION: CONTENT CORRECTED AT THE REQUEST OF: MARKS,MARY NUMBER: 694 IA #: 694 FILE NUMBER: 59.7 GLOBAL ROOT: PS(59.7, DATE CREATED: APR 21, 1993 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: READ AND WRITE ACCESS TO FILE 59.7 ORIGINAL NUMBER: 221 ID: PS(59.7, CREATOR: ELLZEY,LINDA GLOBAL REFERENCE: PS(59.7,D0,47,0) FIELD NUMBER: 47 FIELD NAME: SCRIPTALK PRINT DEVICE MAPPING LOCATION: 47;0 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: PS(59.7,D0,0) FIELD NUMBER: .01 FIELD NAME: SITE NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(59.7,D0,40) FIELD NUMBER: 40 FIELD NAME: DEFAULT OUTPATIENT SITE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(59.7,D0,40.01) FIELD NUMBER: 42 FIELD NAME: DEFAULT OUTPATIENT SITE LOCATION: 40;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(59.7,D0,40.1) FIELD NUMBER: 40.1 FIELD NAME: ADMISSION CANCEL OF RXS LOCATION: 40.1;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 40.11 FIELD NAME: INTERDIVISIONAL PROCESSING LOCATION: 40.1;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 40.12 FIELD NAME: DIVISION PROMPT ASKED LOCATION: 40.1;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 40.13 FIELD NAME: REFILL/RENEW DIVISION LOCATION: 40.1;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 40.14 FIELD NAME: DAYS PRINTED RX STAYS IN 52.5 LOCATION: 40.1;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 40.16 FIELD NAME: POLYPHARMACY W/ACTION PROFILE LOCATION: 40.1;6 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(59.7,D0,49.19,0) FIELD NUMBER: 40.19 FIELD NAME: EXEMPT WARD FROM AUTOCANCEL LOCATION: 40.19;0 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(59.7,D0,40.19,D1,0) FIELD NUMBER: .01 FIELD NAME: EXEMPT WARD FROM AUTOCANCEL LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(59.7,D0,46) FIELD NUMBER: 46.1 FIELD NAME: TRANSMISSION START DATE LOCATION: 46;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 46.2 FIELD NAME: TRANSMISSION LOCATION: 46;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 46.3 FIELD NAME: BATCH CONTROL ID LOCATION: 46;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 46.4 FIELD NAME: NUMBER OF MSH COUNT LOCATION: 46;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 46.5 FIELD NAME: NUMBER OF LINES COUNT LOCATION: 46;5 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(59.7,D0,48) FIELD NUMBER: 48 FIELD NAME: OUTPATIENT ORDERS CONVERSION LOCATION: 48;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 48.1 FIELD NAME: LAST PATIENT CONVERTED LOCATION: 48;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(59.7,D0,49.99) FIELD NUMBER: 49.99 FIELD NAME: OUTPATIENT VERSION LOCATION: 49.99;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 49.98 FIELD NAME: DATE OP 6 INSTALLED LOCATION: 49.99;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 49.97 FIELD NAME: LAST RX CONVERTED LOCATION: 49.99;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 49.96 FIELD NAME: DATE V7 INSTALLED LOCATION: 49.99;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 41 FIELD NAME: LAST RX LOCATION: 49.99;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 49.982 FIELD NAME: V7 POST BACKGROUND STOP LOCATION: 49.99;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 49.981 FIELD NAME: V7 POST BACKGROUND START LOCATION: 49.99;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 49.983 FIELD NAME: V7 POST BACKFILL START LOCATION: 49.99;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 49.984 FIELD NAME: V7 POST BACKFILL LOCATION: 49.99;9 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Outpatient Pharmacy is given permission by Pharmacy Data Mgmt for direct global read/write access and read/write access with Fileman to the fields listed explicitly in this agreement which reside on the 47 multiple. CMOP and OPT PS are given read with FM/DGR access permission to all other fields listed explicitly in this agreement. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 45147036 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: CMOP DBA Comments: JSHARVEY 20070124/ DEACTIVATE TO ADD FIELDS BASED ON PATCH PSS*1*122 DATE ACTIVATED: APR 17, 2007 DATE/TIME EDITED: JAN 24, 2007@23:02 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: ELLZEY,LINDA DATE/TIME EDITED: APR 17, 2007@09:06 ACTION: APPROVED AT THE REQUEST OF: ELLZEY,LINDA NUMBER: 696 IA #: 696 FILE NUMBER: 50.605 GLOBAL ROOT: PS(50.605, DATE CREATED: APR 21, 1993 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA221-F ORIGINAL NUMBER: 221 ID: PS(50.605, GENERAL DESCRIPTION: Outpatient Pharmacy is given permission by Pharmacy to make the following calls: GLOBAL MAP DATA DICTIONARY #50.605 -- VA DRUG CLASS FILE STORED IN ^PS(50.605 SITE: ISC BIRMINGHAM ----------------------- All fields in the file. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 698 IA #: 698 FILE NUMBER: 445 GLOBAL ROOT: PRCP(445, DATE CREATED: APR 21, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA225-B ORIGINAL NUMBER: 225 ID: PRCP(445, GENERAL DESCRIPTION: Read only access to the .01 field of File 445 to get the IEN of the Inventory Point so that we can set it in variable PRCP("I") and use it to a call to routine PRCPUSA. The look-up to the .01 field would be through a Fileman call to ^DIC, and a successful lookup would return the IEN which would then be used in setting the above IFCAP variable. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City NUMBER: 699 IA #: 699 DATE CREATED: MAY 03, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGREG NAME: DBIA226-B ORIGINAL NUMBER: 226 ID: DGREG STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: FEE SUBSCRIBING PACKAGE: FEE BASIS ISC: Albany NUMBER: 700 IA #: 700 DATE CREATED: MAY 03, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGRPDB NAME: DBIA226-C ORIGINAL NUMBER: 226 ID: DGRPDB STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: DIS COMPONENT DESCRIPTION: Rated Disabilities SUBSCRIBING PACKAGE: FEE BASIS ISC: Albany SUBSCRIBING PACKAGE: PATIENT REPRESENTATIVE ISC: Hines SUBSCRIBING DETAILS: Patient Reps often respond to patient complaints about not receiving some type of care, such as dental, eyeglasses, etc. Most patient reps have been given options to pull up the rated disabilities data for a patient so they can make some quick assessments and take some action. The Patient Rep Work Group would like this information to be displayed when they enter a new contact or edit a contact on a patient so they don't have to exit one system and go into another to get the data. It would be displayed along with other patient data such as SSN, age, sex, eligibility status and means test category. SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: INTEGRATED BILLING SUBSCRIBING PACKAGE: SURGERY SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS NUMBER: 701 IA #: 701 DATE CREATED: MAY 03, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTU NAME: DBIA226-D ORIGINAL NUMBER: 226 ID: DGMTU STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$LST COMPONENT DESCRIPTION: Last means test for a patient Value returned is: Annual Means Test IEN^Date of Test^Status Name^Status Code VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of PATIENT file VARIABLES: DGDT TYPE: Input VARIABLES DESCRIPTION: Date/Time optional VARIABLES: DGMTYPT TYPE: Input VARIABLES DESCRIPTION: Type of Test (optional - if not defined "Means Test" will be assumed) SUBSCRIBING PACKAGE: FEE BASIS ISC: Albany SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 DATE/TIME EDITED: JUN 11, 2009@14:12 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: DOWNING,TODD NUMBER: 702 IA #: 702 FILE NUMBER: 21 GLOBAL ROOT: DIC(21, DATE CREATED: MAY 03, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA226-E ORIGINAL NUMBER: 226 ID: DIC(21, GENERAL DESCRIPTION: Point to the following file PERIOD OF SERVICE - 21 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: FEE BASIS ISC: Albany NUMBER: 703 IA #: 703 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: MAY 03, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA226-F ORIGINAL NUMBER: 226 ID: DPT( GENERAL DESCRIPTION: Input Template in file 2 for patient address [FBAA ADDRESS EDIT] Ability to add insurance company information into the patient file. This does NOT include the editing current insurance data on file. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: FEE BASIS ISC: Albany NUMBER: 704 IA #: 704 FILE NUMBER: 442 GLOBAL ROOT: PRC(442, DATE CREATED: MAY 05, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA227-B ORIGINAL NUMBER: 227 ID: PRC(442, GENERAL DESCRIPTION: Prosthetics is granted permission to make the following calls to the IFCAP package (GIP and 1358 Modules). As stated below this is until the next version of either IFCAP or Prosthetics. For the 1358 Module: Item 4 is needed so that Prosthetics can calculate the amount remaining on the original 1358 obligation by subtracting Field #94 from field #96. Item 4 Description: Read Only access to File #442, PROCUREMENT & TRANSACTIONS FILE, fields 94, ACTUAL 1358 BALANCE, and 96, ESTIMATED 1358 BALANCE. STATUS: Active DURATION: Next Version SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City NUMBER: 705 IA #: 705 FILE NUMBER: 353.2 GLOBAL ROOT: IBE(353.2, DATE CREATED: MAY 12, 1993 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA228-B ORIGINAL NUMBER: 228 ID: IBE(353.2, GLOBAL REFERENCE: IBE(353.2,D0,0) FIELD NUMBER: .01 FIELD NAME: CODE LOCATION: 0;1 ACCESS: Pointed to STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: FEE BASIS ISC: Albany NUMBER: 706 IA #: 706 DATE CREATED: MAY 18, 1993 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA229-B ORIGINAL NUMBER: 229 GENERAL DESCRIPTION: MailMan V7 has permission to make the following calls to FileMan: 2. MailMan has always used its text field such that non-integer nodes are not a problem to it. This is explicitly done for network mail headers, which are not expected to be in any way handled by FileMan. In this case the lines .001 through .999 are reserved for recording information passed by the network on message deliveries. 3. While editing the Message file users have a capability to 'transfer text' from other text processing fields. Currently they can reference the text fields of other messages that they either sent or are a recieient of and the responses to these messages. Other prospective files from which textual information may be extracted via this method include the Help Frame file. Security is kept for the privacy of each user by using the screen on the file during the look-up when transfering text from the Message file. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MAILMAN ISC: Washington/Silver Spring NUMBER: 707 IA #: 707 DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOSD NAME: DBIA237-B ORIGINAL NUMBER: 237 ID: PSOSD GENERAL DESCRIPTION: Integrated Billing is given permission from Outpatient Pharmacy to call HD^PSOSD2 and PAT^PSOSD for the purpose of printing the Action Profile and the Information Profile in batch. CONDITIONS: The entry points may only be used in an approved fashion. The following subroutine uses the entry points in an acceptable manner: RXPROF ;For printing the Outpatient Pharmacy Action Profile or the ;Information Profile for a single patient whose DFN is defined. ;Does not ask for the device nor close the device. ;INPUTS: ;PSDAYS = number of days to print the medication profile for ;PSTYPE=1 for the Action Profile, =0 for the Information Profile ;DFN ; N IBDFN,ADDR,ADDRFL,CLASS,CNDT,DRUG,HDFL,I,II,J,L,LINE,P,PAGE, PSDOB,PSII X,PSNAME,PSOI,PSSN,PSIX,PGM,PRF,PSDATE,VAL,VAR,RX, RX0,RX2,ST,ST0,PSDAY,RF,RFS,PSOPRINT,X1,X2,ZTSK,X,Y,PSII,PSDT,LMI S IBDFN=DFN S X1=DT,X2=-PSDAYS D C^%DTC S (PSDATE,PSDAY)=X S LINE="" F I=1:1:132 S LINE=LINE_"-" S PAGE=1 D HD^PSOSD2,PAT^PSOSD W @IOF S DFN=IBDFN Q STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: PAT SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany NUMBER: 708 IA #: 708 DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RAUTL3 NAME: DBIA238-B ORIGINAL NUMBER: 238 ID: RAUTL3 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 710 IA #: 710 DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LRRP2 NAME: DBIA240-B ORIGINAL NUMBER: 240 ID: LRRP2 GENERAL DESCRIPTION: Laboratory Package has given permission to AMIE to make the following calls: Routine Calls: CH^LRRP2 MI^LRRP2 PT^LRX Current Agreement number 95 Per our phone conversation on 6/7/93. No more setting of the ZTSK AND ZTQUEUED variables. Call the following entry points: D DT^LRX,EN^LRPARAM. This will work for any version of Lab. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: CH COMPONENT/ENTRY POINT: MI SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 711 IA #: 711 FILE NUMBER: 4.2 GLOBAL ROOT: DIC(4.2, DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA241-B ORIGINAL NUMBER: 241 ID: DIC(4.2, GLOBAL REFERENCE: DIC(4.2,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: RELAY DOMAIN LOCATION: 0;3 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 713 IA #: 713 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA241-D ORIGINAL NUMBER: 241 ID: VA(200, GLOBAL REFERENCE: VA(200,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 714 IA #: 714 DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: WPSEFM NAME: DBIA241-E ORIGINAL NUMBER: 241 ID: WPSEFM STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 715 IA #: 715 DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LRX NAME: DBIA240-C ORIGINAL NUMBER: 240 ID: LRX GENERAL DESCRIPTION: Laboratory Package has given permission to AMIE to make the following calls: Routine Calls: PT^LRX Current Agreement number 95 Per our phone conversation on 6/7/93. No more setting of the ZTSK AND ZTQUEUED variables. Call the following entry points: D DT^LRX,EN^LRPARAM. This will work for any version of Lab. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: PT COMPONENT/ENTRY POINT: DT SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 716 IA #: 716 DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LRPARAM NAME: DBIA240-D ORIGINAL NUMBER: 240 ID: LRPARAM GENERAL DESCRIPTION: Laboratory Package has given permission to AMIE to make the following calls: Per our phone conversation on 6/7/93. No more setting of the ZTSK AND ZTQUEUED variables. Call the following entry points: D DT^LRX,EN^LRPARAM. This will work for any version of Lab. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 717 IA #: 717 FILE NUMBER: 142 GLOBAL ROOT: GMT(142, DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA242-B ORIGINAL NUMBER: 242 ID: GMT(142, GLOBAL REFERENCE: GMT(142,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: PIMS will also store the DEFAULT HEALTH SUMMARY (Field #43) in the MAS PARAMETERS File (File #43) which will be a pointer to the HEALTH SUMMARY TYPE File (#142). Access to the .01 field of File #142 will be read- only. Data will be retrieved via KERNEL utilities. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: CLINICAL REMINDERS NUMBER: 723 IA #: 723 FILE NUMBER: 42 GLOBAL ROOT: DIC(42, DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA243-G ORIGINAL NUMBER: 243 ID: DIC(42, GENERAL DESCRIPTION: ^DIC(42,D0,0)= (#.03) SERVICE [3S] Direct Global Read STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD DBA Comments: VPR added as a subscriber for VPR*1.0 on 5/18/12. DATE/TIME EDITED: MAY 18, 2012@15:50 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: YORTY,BOB NUMBER: 728 IA #: 728 FILE NUMBER: 40.8 GLOBAL ROOT: DG(40.8, DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA244-B ORIGINAL NUMBER: 244 ID: DG(40.8, GLOBAL REFERENCE: DG(40.8,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Medical Center Division Name STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21287364 SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: POLICE & SECURITY ISC: Dallas SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS SUBSCRIBING DETAILS: added 4/23/09 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS SUBSCRIBING DETAILS: 20090710 - added Inpt Meds DATE/TIME EDITED: JUN 08, 2009@12:17 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MCDEARMON,JAMES DATE/TIME EDITED: JUL 10, 2009@12:50 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SILVERMAN,ROBERT WITH CONCURRENCE OF: ELLIS,DONNA NUMBER: 729 IA #: 729 FILE NUMBER: 405.2 GLOBAL ROOT: DG(405.2, DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA244-C ORIGINAL NUMBER: 244 ID: DG(405.2, GENERAL DESCRIPTION: ^DG(405.2, 0;1 MAS Movement Type STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING NUMBER: 730 IA #: 730 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA244-D ORIGINAL NUMBER: 244 ID: DGPM( GENERAL DESCRIPTION: ^DGPM( 0;1 Date/Time of Movement 0;2 Transaction 0;17 Discharge/Check out Movement 0;18 MAS Movement Type ^DGPM("AMV1" ^DGPM("APTT1" ^DGPM("APID" ^DGPM("AMV3" STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 731 IA #: 731 FILE NUMBER: 8 GLOBAL ROOT: DIC(8, DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA244-E ORIGINAL NUMBER: 244 ID: DIC(8, GENERAL DESCRIPTION: ^DIC(8, 0;6 Print Name of elig. code ^DIC(8,"D" STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING NUMBER: 732 IA #: 732 FILE NUMBER: 21 GLOBAL ROOT: DIC(21, DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA244-F ORIGINAL NUMBER: 244 ID: DIC(21, GENERAL DESCRIPTION: ^DIC(21, 0;1 Period Service name ^DIC(21,"D" STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 733 IA #: 733 FILE NUMBER: 31 GLOBAL ROOT: DIC(31, DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: HINQ CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: READ ACCESS TO ICD9 CODE INFORMATION ORIGINAL NUMBER: 244 ID: DIC(31, CREATOR: EKLUND,PETER GLOBAL REFERENCE: DIC(31 FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: DX CODE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 20;.01 FIELD NAME: RELATED ICD9 CODES LOCATION: ICD;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 20;.02 FIELD NAME: ICD9 MATCH LOCATION: ICD;2 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD DBA Comments: 20070927/ ADDED FIELD 20 TO READ ONLY ACCESS 5/18/12 - VPR added as a subscriber for VPR*1.0. DATE ACTIVATED: SEP 27, 2007 DATE/TIME EDITED: SEP 27, 2007@17:28 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: FAIN,ZACH DATE/TIME EDITED: SEP 27, 2007@17:30 ACTION: APPROVED AT THE REQUEST OF: FAIN,ZACH DATE/TIME EDITED: SEP 27, 2007@18:22 ACTION: CONTENT CORRECTED AT THE REQUEST OF: HARVEY,JULIE WITH CONCURRENCE OF: MORRISON,JENNIFER DATE/TIME EDITED: MAY 18, 2012@16:13 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: FREESE,JENNIFER NUMBER: 734 IA #: 734 FILE NUMBER: 42 GLOBAL ROOT: DIC(42, DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA244-H ORIGINAL NUMBER: 244 ID: DIC(42, GENERAL DESCRIPTION: ^DIC(42, 0;2 Bedsection STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 738 IA #: 738 FILE NUMBER: 40.5 GLOBAL ROOT: HOLIDAY( DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA244-L ORIGINAL NUMBER: 244 ID: HOLIDAY( GLOBAL REFERENCE: HOLIDAY(D0) FIELD NUMBER: .01 FIELD NAME: DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: NAME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: ^HOLIDAY Check if date is a holiday STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 740 IA #: 740 DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGRPD NAME: DBIA244-N ORIGINAL NUMBER: 244 ID: DGRPD STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 741 IA #: 741 DATE CREATED: JUN 15, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGRPE NAME: DBIA244-O ORIGINAL NUMBER: 244 ID: DGRPE GENERAL DESCRIPTION: Variables: MAS variables used: DGCHANGE 0 DGCODE DGDR DGERR DGNODE DGPC DGPTND DGPTND( DGQ DGQCODE DGQNODES DGRPS DGX The call to DGRPE and the DG variables are part of an PIMS routine and call to edit the patient address information. It will be under the AMIE namespace until which time the routine is released with PIMS. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 742 IA #: 742 FILE NUMBER: 19 GLOBAL ROOT: DIC(19, DATE CREATED: JUL 20, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA251-B ORIGINAL NUMBER: 251 ID: DIC(19, GENERAL DESCRIPTION: Read/write access to the following fields in the OPTION file (#19). (To save/restore these values upon an installation.) 200 QUEUED TO RUN AT WHAT TIME 201 DEVICE FOR QUEUED JOB OUTPUT 202 RESCHEDULING FREQUENCY 203 QUEUED TO RUN ON VOLUME SET STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM ISC: Hines NUMBER: 743 IA #: 743 FILE NUMBER: 63 GLOBAL ROOT: LR( DATE CREATED: JUL 20, 1993 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA252-B ORIGINAL NUMBER: 252 ID: LR( GENERAL DESCRIPTION: Fields: subscript;piece 63,.02 PARENT FILE 0;2 63,.03 NAME 0;3 The ^LR(D0,"CH",D1,Node) nodes for read access to the lab test results. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM ISC: Hines SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 744 IA #: 744 DATE CREATED: JUL 26, 1993 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSDVR NAME: DBIA253-B ORIGINAL NUMBER: 253 ID: GMTSDVR GENERAL DESCRIPTION: Integrated Billing has permission from Health Summary to make the following calls: 1) Permission to print Health Summaries by calling ENX^GMTSDVR if it exists. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34495066 COMPONENT/ENTRY POINT: ENX(DFN,GMTSTYP,GMTSPX2,GMTSPX1) VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Record # of patient in file 2 VARIABLES: GMTSTYP TYPE: Input VARIABLES DESCRIPTION: Record # of HS type in file 142 VARIABLES: GMTSPX2 TYPE: Input VARIABLES DESCRIPTION: Optional internal FM beginning date VARIABLES: GMTSPX1 TYPE: Input VARIABLES DESCRIPTION: Optional internal FM ending date SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES SUBSCRIBING PACKAGE: CLINICAL REMINDERS NUMBER: 745 IA #: 745 DATE CREATED: JUL 26, 1993 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTS NAME: DBIA253-C ORIGINAL NUMBER: 253 ID: GMTS GENERAL DESCRIPTION: Integrated Billing has permission from Health Summary to make the following calls: 1) If ENX^GMTSDVR does not exist (version 2.5 or latter not installed), permission to print Health Summaries by: b) Calling SELTYP1^GMTS and then EN^GMTS1 to print the Health Summary. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: SELTYP1 SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring NUMBER: 746 IA #: 746 DATE CREATED: JUL 26, 1993 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTS1 NAME: DBIA253-D ORIGINAL NUMBER: 253 ID: GMTS1 GENERAL DESCRIPTION: Integrated Billing has permission from Health Summary to make the following calls: 1) If ENX^GMTSDVR does not exist (version 2.5 or latter not installed), permission to print Health Summaries by: A) Calling SELTYP1^GMTS and then EN^GMTS1 to print the Health Summary. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 750 IA #: 750 DATE CREATED: AUG 10, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFHLZCT NAME: DBIA263-B ORIGINAL NUMBER: 263 ID: VAFHLZCT STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$EN SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Birmingham NUMBER: 751 IA #: 751 DATE CREATED: AUG 10, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFHLZDP NAME: DBIA263-C ORIGINAL NUMBER: 263 ID: VAFHLZDP STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$EN SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Birmingham NUMBER: 752 IA #: 752 DATE CREATED: AUG 10, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFHLZEL NAME: DBIA263-D ORIGINAL NUMBER: 263 ID: VAFHLZEL CREATOR: YORTY,M ROBERT GENERAL DESCRIPTION: Supported calls for building of HL7 ZPD segment (VA Specific Patient Demographics). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 52247603 KEYWORDS: ZEL COMPONENT/ENTRY POINT: $$EN(DFN,VAFSTR,VAFNUM) COMPONENT DESCRIPTION: This function call has been left for backwards compatability and is superceeded by EN1^VAFHLZEL. This function call is designed to build the HL7 ZEL segment. This segment contains VA-specific patient eligibility data. Because a patient can have more than eligibility, the ZEL segment for the patient's primary eligibility will be the output of the function call and all other eligibilities will be returned in the array VAFZEL. Because this call was not designed to accomodate a segment length greater than 245, sequence numbers 1 to 24 are the only fields supported. Notes: All fields will be returned with the primary eligibility : Eligibility Code, Long ID, and Short ID will be the only fields returned for other eligibilities : VAFZEL is initialized (KILLed) on entry VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to PATIENT file (#2) VARIABLES: VAFSTR TYPE: Input VARIABLES DESCRIPTION: String of fields requested separated by commas (Defaults to all fields) VARIABLES: VAFNUM TYPE: Input VARIABLES DESCRIPTION: Eligibility number to determine type of data returned 1 = primary eligibility only 2 = all eligibilities VARIABLES: HL7 variables TYPE: Input VARIABLES DESCRIPTION: Call assumes that all HL7 variables returned from INIT^HLFNC2 are defined. VARIABLES: VAFMSTDT TYPE: Input VARIABLES DESCRIPTION: Date to use when getting MST status (optional) VARIABLES: $$EN TYPE: Output VARIABLES DESCRIPTION: String of data forming the ZEL segment for the patient's primary eligibility. VARIABLES: VAFZEL(n) TYPE: Output VARIABLES DESCRIPTION: If all eligibilities are chosen, an array of string(s) forming the ZEL segments for the patient's other entitled eligibilities COMPONENT/ENTRY POINT: EN1(DFN,VAFSTR,FAFNUM,.VAFZEL) COMPONENT DESCRIPTION: This procedure call is designed to build the HL7 ZEL segment. This segment contains VA-specific patient eligibility data. Because a patient can have more than one eligibility, the ZEL segment(s) will be returned in the array VAFZEL. This call superceeds $$EN^VAFHLZEL because it accomodates a segment length greater than 245. Notes: VAFZEL(1) will be the primary eligibility : VAFZEL(2..n) will be other eligibilities : All fields will be returned with the primary eligibility : Eligibility Code, Long ID, and Short ID will be the only fields returned for other eligibilities : Fields will not be split across nodes in VAFZEL() : VAFZEL is initialized (KILLed) on entry VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to PATIENT file (#2) VARIABLES: VAFSTR TYPE: Input VARIABLES DESCRIPTION: String of fields requested separated by commas (Defaults to all fields) VARIABLES: VAFNUM TYPE: Input VARIABLES DESCRIPTION: Eligibility number to determine type of data teturned 1 = primary eligibility only 2 = all eligibilities VARIABLES: VAFZEL TYPE: Both VARIABLES DESCRIPTION: Array to return segment(s) in VAFZEL(X) = ZEL segment (first 245 characters) VAFZEL(X,Y) = Remaining portion of ZEL segment in chunks of 245 chars. VARIABLES: HL7 variables TYPE: Input VARIABLES DESCRIPTION: Call assumes that all HL7 variables returned from INIT^HLFNC2 are defined VARIABLES: VAFMSTDT TYPE: Input VARIABLES DESCRIPTION: Date to use when getting MST status (optional) SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Birmingham SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: SCHEDULING DATE ACTIVATED: JUN 20, 2010 DATE/TIME EDITED: JUN 16, 2010@12:06 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: YORTY,ROBERT WITH CONCURRENCE OF: MINARDI,CHRIS DATE/TIME EDITED: JUN 20, 2010@18:04 ACTION: APPROVED NUMBER: 753 IA #: 753 DATE CREATED: AUG 10, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFHLZEM NAME: DBIA263-E ORIGINAL NUMBER: 263 ID: VAFHLZEM STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$EN SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Birmingham NUMBER: 754 IA #: 754 DATE CREATED: AUG 10, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFHLZGD NAME: DBIA263-F ORIGINAL NUMBER: 263 ID: VAFHLZGD STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$EN SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Birmingham NUMBER: 755 IA #: 755 DATE CREATED: AUG 10, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFHLZIC NAME: DBIA263-G ORIGINAL NUMBER: 263 ID: VAFHLZIC STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$EN SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Birmingham NUMBER: 756 IA #: 756 DATE CREATED: AUG 10, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFHLZMT NAME: DBIA263-H ORIGINAL NUMBER: 263 ID: VAFHLZMT STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$EN SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Birmingham NUMBER: 758 IA #: 758 DATE CREATED: AUG 10, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFHLZTA NAME: DBIA263-J ORIGINAL NUMBER: 263 ID: VAFHLZTA STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$EN SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Birmingham SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY NUMBER: 760 IA #: 760 DATE CREATED: AUG 10, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTSCU1 NAME: DBIA263-L ORIGINAL NUMBER: 263 ID: DGMTSCU1 GENERAL DESCRIPTION: Means Test integration: IVM uses means test extensively as means test is the vehicle by which patients are determined to require income verification. We request the following integration with the means test module: Routines: $$LYR^DGMTSCU1 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$LYR SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Birmingham NUMBER: 761 IA #: 761 DATE CREATED: AUG 10, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTU NAME: DBIA263-M ORIGINAL NUMBER: 263 ID: DGMTU GENERAL DESCRIPTION: Means Test integration: IVM uses means test extensively as means test is the vehicle by which patients are determined to require income verification. We request the following integration with the means test module: Routines: $$LST^DGMTU STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$LST SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Birmingham NUMBER: 763 IA #: 763 FILE NUMBER: 408.31 GLOBAL ROOT: DGMT(408.31, DATE CREATED: AUG 10, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA263-O ORIGINAL NUMBER: 263 ID: DGMT(408.31, GENERAL DESCRIPTION: ^DGMT(408.31,: - "B" x-ref used to loop through means tests since January 1 in 2 places (one is a counter, one is the bulk transmission code). It then looks at piece 2 (DFN). These references will be removed after this version. - 0 node used to retrieve the following other fields: .03 STATUS - used in determining if pt meets IVM transmission criteria...checks for 4 or 6. .04 INCOME \ used to determine if .1 ADJUDICATION DATE/TIME > pts income changed .12 THRESHOLD A / from C to A STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Birmingham NUMBER: 764 IA #: 764 DATE CREATED: AUG 10, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA263-P ORIGINAL NUMBER: 263 GENERAL DESCRIPTION: IVM attaches a protocol to the event driver. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Birmingham NUMBER: 765 IA #: 765 DATE CREATED: AUG 10, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA263-Q ORIGINAL NUMBER: 263 GENERAL DESCRIPTION: IVM exports VAFHL* routines STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Birmingham NUMBER: 766 IA #: 766 FILE NUMBER: 36 GLOBAL ROOT: DIC(36, DATE CREATED: AUG 25, 1993 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA268-B ORIGINAL NUMBER: 268 ID: DIC(36, GLOBAL REFERENCE: SEE DESCRIPTION GENERAL DESCRIPTION: FILE NO. FIELD NO NODE;PIECE DESCRIPT 36 .111 .11;1 STREET ADDRESS [LINE 1] .112 .11;2 STREET ADDRESS [LINE 2] .113 .11;3 STREET ADDRESS [LINE 3] .114 .11;4 CITY .115 .11;5 STATE .116 .11;6 ZIP CODE .131 .13;1 PHONE NUMBER STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 767 IA #: 767 FILE NUMBER: 38.1 GLOBAL ROOT: DGSL(38.1, DATE CREATED: AUG 25, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA268-C ORIGINAL NUMBER: 268 ID: DGSL(38.1, GENERAL DESCRIPTION: This DBIA allows access to the DG SECURITY LOG file to determine whether a patient is considered sensitive. Since this file is DINUMed to the PATIENT file, security can be checked by ensuring that the 2nd piece of the 0 node is equal to 1: I $P($G(^DGSL(38.1,DFN,0)),"^",2) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE ISC: Oakland SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES SUBSCRIBING PACKAGE: REMOTE ORDER/ENTRY SYSTEM SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE SUBSCRIBING PACKAGE: INTEGRATED BILLING SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING DETAILS: ADDED 9/27/07 SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD DBA Comments: VPR added as a subscriber on 5/18/12 for VPR*1.0. DATE/TIME EDITED: SEP 27, 2007@17:33 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: FAIN,ZACH DATE/TIME EDITED: MAY 18, 2012@15:55 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: YORTY,BOB NUMBER: 768 IA #: 768 DATE CREATED: AUG 25, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SEE DESCRIPTION NAME: DBIA268-D ORIGINAL NUMBER: 268 ID: SEE DESCRIPTION GENERAL DESCRIPTION: Parts of the following routines have been copied and altered from DGMTSC* routines. This was done in order to include Means Test data for PDX. All DG variables are newed. The alterations mainly consist of changing writes to sets. The PDX routines are based on the following routines: a) HD^DGMTSCU b) DIS^DGMTSC1 c) CHILD^DGMTSC11 d) DIS^DGMTSC2 e) FLD^DGMTSC2 f) DIS^DGMTSC3 g) CHILD^DGMTSC31 h) DIS^GDMTSC4 i) FLD^DGMTSC4 Within these routines the following entry points are accessed: a) $$LST^DGMTU b) SETUP^DGMTSCU c) $$LYR^DGMTSCU1 d) ALL^DGMTU21 e) $$YN^DGMTSCU1 f) $$AMT^DGMTSCU1 g) $$NAME^DGMTU1 h) $$SSN^DGMTU1 i) $$DOB^DGMTU1 j) CHILD^DGMTSC11 k) DIS^DGMTSC2 l) DEP^DGMTSCU2 m) INC^DGMTSCU3 n) FLD^DGMTSC2 o) DIS^DGMTSCSC3 p) SET^DGMTSC31 q) CHILD^DGNTSC4 r) DIS^DGMTSC4 s) FLD^DGMTSC4 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 770 IA #: 770 FILE NUMBER: 52.7 GLOBAL ROOT: PS(52.7, DATE CREATED: AUG 26, 1993 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA270-B ORIGINAL NUMBER: 270 ID: PS(52.7, GENERAL DESCRIPTION: Drug Accountability will use the IV STATS (#50.8) file to update IV dispensing activity in a Drug Accountability Location. To correctly identify the DRUG (#50) file entry a look up is first made to the IV ADDITIVES (#52.6) and/or the IV SOLUTION (#52.7) files. Looping through ^PS(50.8,D0), all IV Rooms are checked. Looping through ^PS(50.8,D0,2,D1), dates are checked. Looping through ^PS(50.8,D0,2,D1,2,D2), drugs are checked with support from the "AC" x-ref. Looping through ^PS(50.8,D0,2,D1,2,D2,3,D3), ward is checked. It is here that, if a match occurs, $P($G(^PS(50.8,D0,2,D1,2,D2,3,D3,0)),U,2)-$P($G(^(0)),U,5) is used to update the balance in Drug Accountability. GLOBAL MAP DATA DICTIONARY #52.7 -- IV SOLUTIONS FILE STORED IN ^PS(52.7, *** NO DATA STORED YET *** SITE: BIRMINGHAM ISC ------------------------------------------------------------------------ CROSS REFERENCED BY: GENERIC DRUG(AC) ^PS(52.7,D0,0)= (#1) GENERIC DRUG [2P] STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham NUMBER: 771 IA #: 771 FILE NUMBER: 50.8 GLOBAL ROOT: PS(50.8, DATE CREATED: AUG 26, 1993 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA271-C ORIGINAL NUMBER: 271 ID: PS(50.8, GENERAL DESCRIPTION: Drug Accountability will use the IV STATS (#50.8) file to update IV dispensing activity in a Drug Accountability Location. To correctly identify the DRUG (#50) file entry a look up is first made to the IV ADDITIVES (#52.6) and/or the IV SOLUTION (#52.7) files. Looping through ^PS(50.8,D0), all IV Rooms are checked. Looping through ^PS(50.8,D0,2,D1), dates are checked. Looping through ^PS(50.8,D0,2,D1,2,D2), drugs are checked with support from the "AC" x-ref. Looping through ^PS(50.8,D0,2,D1,2,D2,3,D3), ward is checked. It is here that, if a match occurs, $P($G(^PS(50.8,D0,2,D1,2,D2,3,D3,0)),U,2)-$P($G(^(0)),U,5) is used to update the balance in Drug Accountability. GLOBAL MAP DATA DICTIONARY #50.8 -- IV STATS FILE STORED IN ^PS(50.8, (1 ENTRY) SITE: BIRMINGHAM ISC (#14) -------------------------------------------------------------------------- CROSS REFERENCED BY: IV DRUG(AC) ^PS(50.8,D0,0)= (#.01) IV ROOM [1P] ^ ^PS(50.8,D0,2,0)=^50.803D^^ (#2) DATE ^PS(50.8,D0,2,D1,0)= (#.01) DATE [1D] ^ ^PS(50.8,D0,2,D1,2,0)=^50.805A^^ (#2) IV DRUG ^PS(50.8,D0,2,D1,2,D2,0)= (#.01) IV DRUG [1F] CROSS-REFERENCE: 50.8^AC^MUMPS 1)= I '$D(PSIVV),$D(^PS(50.8)) D ^PSIVXREF Q 2)= Q ^PS(50.8,D0,2,D1,2,D2,3,0)=^50.808P^^ (#10) WARD ^PS(50.8,D0,2,D1,2,D2,3,D3,0)= (#.01) WARD [1P] ^ (#2) DISPENSED UNITS ==>(WARD) [2N] ^ (#5) CANCELED UNITS [5N] ^ STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham NUMBER: 772 IA #: 772 FILE NUMBER: 57.6 GLOBAL ROOT: PS(57.6, DATE CREATED: AUG 26, 1993 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA271-D ORIGINAL NUMBER: 271 ID: PS(57.6, GENERAL DESCRIPTION: Drug Accountability will use the UNIT DOSE PICK LIST STATS (#57.6) file to update UD dispensing activity in a Drug Accountability Location. Looping through ^PS(57.6,D0), each date since the last update is checked. Looping through ^PS(57.6,D0,1,D1), wards are checked. Looping through ^PS(57.6,D0,1,D1,1,D2), providers are checked. Looping through ^PS(57.6,D0,1,D1,1,D2,1,D3), drugs checked. It is here that, if a match occurs, $P($G(^PS(57.6,D0,1,D1,1,D2,1,D3,0)),U,2)-$P($G(^(0)),U,4) is used to update the balance in Drug Accountability. GLOBAL MAP DATA DICTIONARY #57.6 -- UNIT DOSE PICK LIST STATS FILE STORED IN ^PS(57.6, ------------------------------------------------------------------ Contains medication amounts and costs for the Unit Dose package. Data is entered into this file when pick lists are filed away, and when pre- exchange units, extra units dispensed, and returns are entered through the package. Most of the cost reports gather their data from this file. ^PS(57.6,D0,0)= (#.01) DATE [1D] ^ ^PS(57.6,D0,1,0)=^57.61PA^^ (#1) WARD ^PS(57.6,D0,1,D1,0)= (#.01) WARD [1P] ^ ^PS(57.6,D0,1,D1,1,0)=^57.62PA^^ (#1) PROVIDER ^PS(57.6,D0,1,D1,1,D2,0)= (#.01) PROVIDER [1P] ^ ^PS(57.6,D0,1,D1,1,D2,1,0)=^57.63PA^^ (#1) DRUG ^PS(57.6,D0,1,D1,1,D2,1,D3,0)=(#.01) DRUG [1P] ^ (#1) DISPENSED AMOUNT [2N] ==>^ (#2) DISPENSED COST [3N] ^ (#3) RETURNED ==>AMOUNT [4N] ^ (#4) RETURNED COST [5N] ^ STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham NUMBER: 773 IA #: 773 DATE CREATED: AUG 27, 1993 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBAPDX NAME: DBIA271-B ORIGINAL NUMBER: 271 ID: IBAPDX GENERAL DESCRIPTION: IBAPDX - Extraction means test billing data for PDX Entry: $$EXTR^IBAPDX(TRAN,DFN,ROOT) Input: TRAN -- pointer to transaction file 394.61 DFN -- pointer to patient file 2 ROOT -- root for the output extraction array Output: 0 -- extraction was successful, or -1^err -- if an error was encountered during extraction STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$EXTR(TRAN,DFN,ROOT) SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 774 IA #: 774 DATE CREATED: AUG 27, 1993 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBAPDX NAME: DBIA271-C ORIGINAL NUMBER: 271 ID: IBAPDX GENERAL DESCRIPTION: IBAPDX1 - Build display set for extracted PDX billing data Entry: $$DISP^IBAPDX(XTRACT,ROOT,SEGPTR,OFFSET) Input: XTRACT -- root for the input extract array ROOT -- root for the output display array SEGPTR -- pointer to extracted segment in file 394.71 OFFSET -- offset to begin line numbering Output: NUM -- number of lines in the output display array, or -1^ERR -- if an error was encountered STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: DISP(...) SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 775 IA #: 775 FILE NUMBER: 394.71 GLOBAL ROOT: VAT(394.71, DATE CREATED: AUG 27, 1993 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA272-B ORIGINAL NUMBER: 272 ID: VAT(394.71, GENERAL DESCRIPTION: a) The following fields are referenced by the global directly, NOT by a fileman call. - PDX Segment File (394,71) field # .01 Data Segment Name STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 776 IA #: 776 DATE CREATED: AUG 27, 1993 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAQULT3 NAME: DBIA272-C ORIGINAL NUMBER: 272 ID: VAQULT3 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: NAMEKEY COMPONENT/ENTRY POINT: DUZKEY COMPONENT/ENTRY POINT: TRANENC SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 777 IA #: 777 DATE CREATED: AUG 27, 1993 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAQUTL2 NAME: DBIA272-D ORIGINAL NUMBER: 272 ID: VAQUTL2 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: NCRPFLD SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 778 IA #: 778 DATE CREATED: AUG 27, 1993 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAQCON2 NAME: DBIA272-E ORIGINAL NUMBER: 272 ID: VAQCON2 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: SENDER SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 779 IA #: 779 DATE CREATED: AUG 27, 1993 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAQDIS20 NAME: DBIA272-F ORIGINAL NUMBER: 272 ID: VAQDIS20 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: CENTER SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 788 IA #: 788 FILE NUMBER: 22 GLOBAL ROOT: DIC(22, DATE CREATED: SEP 13, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA277-B ORIGINAL NUMBER: 277 ID: DIC(22, GENERAL DESCRIPTION: File #22 - POW Period Field #.01 - Name - ^DIC(22,D0,0) piece 1 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas NUMBER: 789 IA #: 789 FILE NUMBER: 23 GLOBAL ROOT: DIC(23, DATE CREATED: SEP 13, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA277-C ORIGINAL NUMBER: 277 ID: DIC(23, GENERAL DESCRIPTION: File #23 - Branch of Service Field #.01 - Name - ^DIC(23,D0,0) piece 1 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas NUMBER: 790 IA #: 790 FILE NUMBER: 24 GLOBAL ROOT: DIC(24, DATE CREATED: SEP 13, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA277-D ORIGINAL NUMBER: 277 ID: DIC(24, GENERAL DESCRIPTION: File #24 - Non-Veterans Class Field #.01 - Name - ^DIC(24,D0,0) piece 1 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas NUMBER: 791 IA #: 791 FILE NUMBER: 25 GLOBAL ROOT: DIC(25, DATE CREATED: SEP 13, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA277-E ORIGINAL NUMBER: 277 ID: DIC(25, GENERAL DESCRIPTION: File #25 - Type of Discharge Field #.01 - Name - ^DIC(25,D0,0) piece 1 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas NUMBER: 792 IA #: 792 FILE NUMBER: 31 GLOBAL ROOT: DIC(31, DATE CREATED: SEP 13, 1993 CUSTODIAL PACKAGE: HINQ CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA277-F ORIGINAL NUMBER: 277 ID: DIC(31, GENERAL DESCRIPTION: File #31 - Disability Condition Field #.01 - Name - ^DIC(31,D0,0) piece 1 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas NUMBER: 793 IA #: 793 FILE NUMBER: 35 GLOBAL ROOT: DIC(35, DATE CREATED: SEP 13, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA277-G ORIGINAL NUMBER: 277 ID: DIC(35, GENERAL DESCRIPTION: File #35 - Other Federal Agency Field #.01 - Name - ^DIC(35,D0,0) piece 1 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas NUMBER: 794 IA #: 794 FILE NUMBER: 36 GLOBAL ROOT: DIC(36, DATE CREATED: SEP 13, 1993 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA277-H ORIGINAL NUMBER: 277 ID: DIC(36, GLOBAL REFERENCE: DIC(36, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas SUBSCRIBING PACKAGE: HEALTH SUMMARY SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 795 IA #: 795 FILE NUMBER: 42.4 GLOBAL ROOT: DIC(42.4, DATE CREATED: SEP 13, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA277-I ORIGINAL NUMBER: 277 ID: DIC(42.4, GENERAL DESCRIPTION: File #42.4 - Specialty Field #.01 - Name - ^DIC(42.4,D0,0) piece 1 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas NUMBER: 796 IA #: 796 FILE NUMBER: 45.7 GLOBAL ROOT: DIC(45.7, DATE CREATED: SEP 13, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA277-J ORIGINAL NUMBER: 277 ID: DIC(45.7, GENERAL DESCRIPTION: File #45.7 - Treating Specialty Field #.01 - Name - ^DIC(45.7,D0,0) piece 1 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas NUMBER: 797 IA #: 797 DATE CREATED: SEP 20, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCS58 NAME: DBIA282-B ORIGINAL NUMBER: 282 ID: PRCS58 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: Ask for control Point and Obligation Number^ COMPONENT/ENTRY POINT: EN2 COMPONENT DESCRIPTION: Variables: PRCS("TYPE")="FB" or "COUNTER" X - 7 Piece variable delimited by "^" Piece 1 = Obligation Number Piece 2 = Date/Time (internal format) Piece 3 = estimated amount Piece 4 = actual amount Piece 5 = reference Piece 6 = comments(up to 78 characters) Piece 7 = interface id Y - one or two '^' - piece delimited variable where Piece 1 = (zero) or (one) Piece 2 = Internal entry number or free text error message. ^ SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City NUMBER: 798 IA #: 798 DATE CREATED: SEP 20, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCS58CC NAME: DBIA282-C ORIGINAL NUMBER: 282 ID: PRCS58CC STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: PRCS58CC COMPONENT DESCRIPTION: Support for the close/complete action on a 1358 daily record. Variables: PRCSX - 5-piece variable delimited by '^' piece 1 = Internal daily reference no. piece 2 = Date/Time (internal format) piece 3 = Amount of Payment piece 4 = Comments (limited to 78 characters) piece 5 = Completed flag Y - a one or two '^'-piece delimited variable where piece 1 = 0 (zero) or 1 (one) piece 2 = a free-text error message.^ SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City NUMBER: 799 IA #: 799 FILE NUMBER: 420.5 GLOBAL ROOT: PRCD(420.5, DATE CREATED: SEP 20, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA282-D ORIGINAL NUMBER: 282 ID: PRCD(420.5, GENERAL DESCRIPTION: Read access to file 420.5 (Unit of Issue) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City SUBSCRIBING PACKAGE: M DATA EXTRACTOR NUMBER: 800 IA #: 800 FILE NUMBER: 440 GLOBAL ROOT: PRC(440, DATE CREATED: SEP 20, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA282-E ORIGINAL NUMBER: 282 ID: PRC(440, GENERAL DESCRIPTION: Prosthetics to have Read, Write, and LAYGO access to files 440 (vendor) and 441 (Item Master), through options PRCHPC ITEM EDIT and PRCHRC VEN EDIT, restricted through assignment of the RMPRSUPERVISOR key. This key will be issued to a prosthetics clerk who has completed training by Supply Service on the IFCAP conventions and procedures for entering data into the above named files. Read access to file 440 VENDOR FILE - Field #.01 NAME and Field #6 CONTRACT NUMBER MULTIPLE, global node ^PRC(440,D0,4) and Global Node ^PRC(440,D0,4,D1,0). Display Vendor Name and check for valid or expired contract number. STATUS: Active DURATION: Next Version GOOD ONLY FOR VERSION: pre-CoreFLS SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City SUBSCRIBING PACKAGE: M DATA EXTRACTOR NUMBER: 801 IA #: 801 FILE NUMBER: 441 GLOBAL ROOT: PRC(441, DATE CREATED: SEP 20, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA282-F ORIGINAL NUMBER: 282 ID: PRC(441, GENERAL DESCRIPTION: Prosthetics to have Read, Write, and LAYGO access to files 440 (vendor) and 441 (Item Master), through options PRCHPC ITEM EDIT and PRCHRC VEN EDIT, restricted through assignment of the RMPRSUPERVISOR key. This key will be issued to a prosthetics clerk who has completed training by Supply Service on the IFCAP conventions and procedures for entering data into the above named files. Read access to file 441 IFCAP ITEM MASTER FILE Field #.05 SHORT DESCRIPTION, global node ^PRC(441,D0,0) and Index ^PRC(441,"C",X,DA). Display IFCAP ITEM MASTER Short Description. STATUS: Active DURATION: Next Version GOOD ONLY FOR VERSION: pre-CoreFLS SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City SUBSCRIBING PACKAGE: M DATA EXTRACTOR NUMBER: 802 IA #: 802 FILE NUMBER: 410 GLOBAL ROOT: PRCS(410, DATE CREATED: SEP 20, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA282-G ORIGINAL NUMBER: 282 ID: PRCS(410, GENERAL DESCRIPTION: Read access to file 410 (Control Point Activity) - Access required to check the status of 2237's. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City SUBSCRIBING PACKAGE: M DATA EXTRACTOR NUMBER: 803 IA #: 803 FILE NUMBER: 442 GLOBAL ROOT: PRC(442, DATE CREATED: SEP 20, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA282-H ORIGINAL NUMBER: 282 ID: PRC(442, GENERAL DESCRIPTION: Read access to file 442 PROCUREMENT & ACCOUNTING TRANSACTION To get Obligation number through a ^DIC lookup. Obligation # is returned in Y(0). STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City NUMBER: 804 IA #: 804 FILE NUMBER: 423 GLOBAL ROOT: PRCF(423, DATE CREATED: OCT 05, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA285-B ORIGINAL NUMBER: 285 ID: PRCF(423, GENERAL DESCRIPTION: CALM/LOG Code Sheet File (#423) of IFCAP sets and/or references to the entire file are under this agreement. Access to the CALM/LOG Code Sheet File 423 and the Procurement & Accounting Transaction File 442 is needed to repoint AR Debtor File 412 pointers to the AR V4.0 AR Debtor File 340. (included in inits) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 805 IA #: 805 FILE NUMBER: 440 GLOBAL ROOT: PRC(440, DATE CREATED: OCT 05, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA285-C ORIGINAL NUMBER: 285 ID: PRC(440, GENERAL DESCRIPTION: AR Debtor File 340 Debtor Field .01V5 (0;1) - variable pointer to the Vendor File (#440) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 806 IA #: 806 FILE NUMBER: 442 GLOBAL ROOT: PRC(442, DATE CREATED: OCT 05, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA285-D ORIGINAL NUMBER: 285 ID: PRC(442, GENERAL DESCRIPTION: AR File 430 Fiscal Year sub-file 430.01, Pat Ref. No. Field 430.01,2 (0;3) - points to Procurement & Accounting Transaction File (#442) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 807 IA #: 807 DATE CREATED: OCT 05, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCHPAT NAME: DBIA285-E ORIGINAL NUMBER: 285 ID: PRCHPAT GENERAL DESCRIPTION: Appropriation Symbol Field 430.01,3 (0;4) - input transform calls EN1^PRCHPAT STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN1 SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 808 IA #: 808 FILE NUMBER: 420.3 GLOBAL ROOT: PRCD(420.3, DATE CREATED: OCT 05, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA285-F ORIGINAL NUMBER: 285 ID: PRCD(420.3, GENERAL DESCRIPTION: Ald Code Field 430.01,4 (0;5) - points to the Ald Code File (#420.3) Ald Code Field 4 (0;5) - points to the Ald Code File (#420.3) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 809 IA #: 809 FILE NUMBER: 420.5 GLOBAL ROOT: PRCD(420.5, DATE CREATED: OCT 05, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA285-G ORIGINAL NUMBER: 285 ID: PRCD(420.5, GENERAL DESCRIPTION: Unit Field 430.02,5 (0;5) - points to the Unit of Issue File (#420.5) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 810 IA #: 810 FILE NUMBER: 411 GLOBAL ROOT: PRC(411, DATE CREATED: OCT 05, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA285-H ORIGINAL NUMBER: 285 ID: PRC(411, GENERAL DESCRIPTION: The AR V4.0 PRCACV* Conversion routines call to IFCAP. Access to the Admin. Activity Site Parameter File, #411, is needed to populate the AR V4.0 AR Site Parameter File 342. Admin. Activity Site Parameter File 411 Station Number Filed .01 (0;1) - Global reference Primary Station Field 21 (0;2) - "AC" Cross-reference global reference Admin. Activity Site Parameter File 411, Printer Location sub-file 411.02 Printer Location Field 411.02,.01 (0;1) - Global references UB for UB-82 and A for Accounts Receivable Device Field 411.02,1 (0;2) - Global reference STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 812 IA #: 812 FILE NUMBER: 3.2 GLOBAL ROOT: %ZIS(2, DATE CREATED: OCT 12, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA290-B ORIGINAL NUMBER: 290 ID: %ZIS(2, GENERAL DESCRIPTION: ============================================================= Unauthorized Claim Printer, field 33 in file 161.4 (Fee Basis Site Parameters file) references the device (%ZIS(1) and terminal type (%ZIS(2) files in the Input transform (extrinsic function), Executable help (routine call) and Screen. Fee routine is FBUCDD1. The Screen is: S DIC("S")= "S Z=$G(^%ZIS(1,+Y,""SUBTYPE"")),Z=$G(^%ZIS(2,Z,0)) I $E($P(Z,U),1)=""P""K Z" This IA grants the subscribing packages direct global read of %ZIS(1,"B" %ZIS(1,IEN,0 %ZIS(1,IEN,1 %ZIS(1,IEN,90 %ZIS(1,IEN,91 %ZIS(1,IEN,95 %ZIS(1,IEN,SUBTYPE %ZIS(1,IEN,TIME %ZIS(1,IEN,TYPE %ZIS(2,IEN,0 STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: FEE BASIS ISC: Albany SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: BAR CODE MED ADMIN NUMBER: 813 IA #: 813 FILE NUMBER: 142 GLOBAL ROOT: GMT(142, DATE CREATED: OCT 25, 1993 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA297-B ORIGINAL NUMBER: 297 ID: GMT(142, GENERAL DESCRIPTION: The PDX application is granted read access to the following fields and, if listed, their associated cross references: File Field Node;Piece Description (Field name) X-Refs ----- ----- ---------- ------------------------------ ------ 142 .01 0;1 NAME B 1 (multiple in STRUCTURE file 142.01) File Field Node;Piece Description (Field name) X-Refs ----- ----- ---------- ------------------------------ ------ 142.01 .01 0;1 SUMMARY ORDER B .02 0;2 COMPONENT NAME C 2 0;3 OCCURRENCE LIMIT 3 0;4 TIME LIMIT STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 814 IA #: 814 FILE NUMBER: 142.1 GLOBAL ROOT: GMT(142.1, DATE CREATED: OCT 25, 1993 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA297-C ORIGINAL NUMBER: 297 ID: GMT(142.1, GENERAL DESCRIPTION: File Field Node;Piece Description (Field name) X-Refs ----- ----- ---------- ------------------------------ ------ 142.1 .01 0;1 NAME B 3 0;4 ABBREVIATION C 2 0;3 TIME LIMITS APPLICABLE 4 0;5 MAXIMUM OCCURRENCES APPLICABLE STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 815 IA #: 815 DATE CREATED: OCT 25, 1993 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSPDX NAME: DBIA297-D ORIGINAL NUMBER: 297 ID: GMTSPDX GENERAL DESCRIPTION: The PDX application is granted permission to use the function call $$GET^GMTSPDX(TRAN,DFN,SEGPTR,ROOT,GMTSLCNT,GMTSDLM,GMTSNDM) in order to extrqct Health Summary Components. Input: TRAN - Pointer to the VAQ - TRANSACTION file. If passed, the patient referenced in the transaction will be used when extracting the Health Summary Component. DFN - Pointer to the PATIENT file. If TRAN is not passed, the patient referenced by this pointer will be used when extracting the Health Summary Component. SEGPTR - Pointer to the VAQ - DATA SEGMENT file. This is the PDX Data Segment being extracted. ROOT - Root for the output extraction array (full global reference) GMTSLCNT - Offset in ROOT to begin placing information into (defaults to 0) GMTSDLM - Time limit to use for extraction (if applicable) GMTSNDM - Occurrence limit to use for extraction (if applicable) Output: A^B - Health Summary Component successfully extracted. A - Total number of lines inserted into ROOT B - Last line number inserted into ROOT -1^Err - Error occurred while extracting Health Summary Component. Err - Printable error text (reason for failure) Notes: a) Currently, output begins with GMTSLCNT+1 b) If TRAN is passed The patient pointer of the transaction will be used Encryption will be based on the transaction If DFN is passed Encryption will be based on the site parameter c) Use of TRAN takes precedence over DFN. If TRAN>0 the extraction will be based on the patient contained in the transaction. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$GET(,,,,,,) SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 817 IA #: 817 DATE CREATED: OCT 25, 1993 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAQUTL3 NAME: DBIA298-B ORIGINAL NUMBER: 298 ID: VAQUTL3 GENERAL DESCRIPTION: The Health Summary application is granted permission to use the function call $$TRANENC^VAQUTL3(TRAN,0) in order to determine if encryption for a PDX Transaction has been turned on. Input: TRAN - Pointer to the VAQ - TRANSACTION file 0 - Input of 0 as second parameter will only be supported Output: 0 - Encryption for the transaction has been turned off 1 - Encryption for the transaction has been turned on Notes: a) Existence of VAQIGNC will be checked. If it exists and is set to 1 encryption will be ignored for this transaction. b) If encryption is on and the transaction does not include an encryption method, the default encryption method will be used. c) Encryption off will be returned on error. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$TRANENC(TRAN,0) SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 818 IA #: 818 DATE CREATED: OCT 25, 1993 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAQUTL2 NAME: DBIA298-C ORIGINAL NUMBER: 298 ID: VAQUTL2 GENERAL DESCRIPTION: The Health Summary application is granted permission to use the function call $$NCRYPTON^VAQUTL2(0) in order to determine the default encryption method for a facility. Input: 0 - Input of 0 (the default value) will only be supported Output: 0 - Encryption has been turned off at the facility X - Pointer to VAQ - ENCRYPTION METHOD file (#394.72) Notes: a) Existence of VAQIGNC will be checked. If it exists and is set to 1 encryption will be ignored. b) Encryption off will be returned on error. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$NCRYPTON(0) SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 819 IA #: 819 DATE CREATED: OCT 25, 1993 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAQHSH NAME: DBIA298-D ORIGINAL NUMBER: 298 ID: VAQHSH GENERAL DESCRIPTION: The Health Summary application is granted permission to use the function call $$ENCDSP^VAQHSH(TRAN,ROOT,ENCPTR,DSPOFF,DSPCNT) in order to encrypt a Health Summary component that has been extracted in display ready format. Input: TRAN - Pointer to VAQ - TRANSACTION file ROOT - Where the Display Array is (full global reference) ENCPTR - Pointer to VAQ - ENCRYPTION METHOD file DSPOFF - Offset into Display Array to begin at (defaults to 0) DSPCNT - Number of lines in Display Array (defaults to all lines) Output: 0 - Success -1^Text - Error Notes: a) If TRAN>0 Encryption will be based on the transaction Encryption keys will be based on the transaction Else Encryption will be based on ENCPTR Encryption keys based on current user b) Existence of TRAN takes precedence over ENCPTR STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$ENCDSP(,,,,) SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 820 IA #: 820 FILE NUMBER: 394.71 GLOBAL ROOT: VAT(394.71, DATE CREATED: OCT 25, 1993 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA298-E ORIGINAL NUMBER: 298 ID: VAT(394.71, GENERAL DESCRIPTION: The Health Summary application is granted read access to the following fields and, if listed, their associated cross references: File Field Node;Piece Description (Field name) X-Refs ----- ----- ---------- ------------------------------ ------ 394.71 .01 0;1 Data Segment Name B .04 0;4 Health Summary Component STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 821 IA #: 821 GLOBAL ROOT: DIC( DATE CREATED: OCT 25, 1993 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA299-B ORIGINAL NUMBER: 299 ID: DIC( GENERAL DESCRIPTION: The PDX (V 1.5) application is granted read access to the DD and DIC globals to accomplish the following tasks: 1) Get global location for a file ^DIC(FILE,0,"GL") STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 823 IA #: 823 FILE NUMBER: 51 GLOBAL ROOT: PS(51, DATE CREATED: OCT 25, 1993 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA302-C ORIGINAL NUMBER: 302 ID: PS(51, GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. File Field Node;Piece Description (Field name) X-Refs ----- ----- ---------- ------------------------------ ------ 51 .01 0;1 NAME B,A .5 0;3 SYNONYM AD 1 0;2 EXPANSION 0 AB 9 9;1 PLURAL AC STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany EDITOR: BLOCKER,DAVE NUMBER: 828 IA #: 828 FILE NUMBER: 42 GLOBAL ROOT: DIC(42, DATE CREATED: NOV 01, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA311-B ORIGINAL NUMBER: 311 ID: DIC(42, GENERAL DESCRIPTION: The Discharge Summary package has permission to access the Patient Information Management System package in the following ways: 3. When printing VA Form 10-1000 Discharge Summary uses the externally formatted name of the Division from which the patient was discharged, as found in field .015 of the Ward Location File (#42). The division is obtained by a call to EN^DIQ1 with DIC=42, DR=.015, and DA = WARD LOCATION record # returned from the IN5^VADPT call. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DISCHARGE SUMMARY ISC: Salt Lake City NUMBER: 829 IA #: 829 FILE NUMBER: 40.8 GLOBAL ROOT: DG(40.8, DATE CREATED: NOV 01, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA311-C ORIGINAL NUMBER: 311 ID: DG(40.8, STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DISCHARGE SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: In order to accommodate multi-divisional sites, where any of our package site parameters may vary by division, the .01 field of the GMRD SITE PARAMETERS file (#128.99) points to MEDICAL CENTER DIVISION file (#40.8). SUBSCRIBING PACKAGE: QUASAR ISC: Hines SUBSCRIBING DETAILS: 1. Quality: Audiology and Speech Pathology Audit and Review (QUASAR) Package, A&SP SITE PARAMETERS File (#509850.8), DIVISION Field Multiple (#3), DIVISION Field (#.01) points to the MEDICAL CENTER DIVISION File (#40.8) to accommodate recording, tracking and reporting workload by division. 2. Quality: Audiology and Speech Pathology Audit and Review (QUASAR) Package, A&SP CLINIC VISIT File (#509850.6), DIVISION Field (#60) points to the MEDICAL CENTER DIVISION File (#40.8) to accommodate recording, tracking and reporting workload by division. 3. Quality: Audiology and Speech Pathology Audit and Review (QUASAR) Package, A&SP DELETE VISIT File (#509850.9), DIVISION Field (#10) points to the MEDICAL CENTER DIVISION File (#40.8) to accommodate recording, tracking and reporting workload by division. NUMBER: 830 IA #: 830 GLOBAL ROOT: DIC( DATE CREATED: NOV 01, 1993 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA314-B ORIGINAL NUMBER: 314 ID: DIC( GENERAL DESCRIPTION: To support the table-driven upload of transcribed text to various DHCP files, the Discharge Summary application has permission to access the Data Dictionary and File of Files in the following ways: 1. In order to allow the site to specify the target file, fixed-field header elements, and word-processing field for each report type, Discharge Summary version 1 will make several references to either the File of Files or ^DD(. These are ONLY done in setting up a ^DIC call (to look-up a given field in the target file), or in screening logic (e.g., to exclude the programmer at the site from choosing a non-Word-Processing field in the target file as the destination for the body of a report). Needless to say, NO SETs or KILLs are ever executed on any of FileMan's supporting data structures (i.e., ^DD( or ^DIC(). All hard-coded references to ^DIC( or ^DD( are made from within the following code: GMRDUPAR ; SLC/JER - Upload Parameter Edit ;4/23/93 14:53 ;;1.0V2;Discharge Summary;;Sep 02, 1993 MAIN ; Controls branching N DIC,DA,DIE,DLAYGO,DR,GMRDPRM0,GMRDPRM1,GMRDPRM3,GMRDUSRC,GMRD1ST,X,Y D:'$D(GMRDPRM0) SETPARM^GMRDLIBE W !,"First edit Division-wide upload parameters:",! S (DIC,DLAYGO)=128.99,DIC(0)="AEMQL",DIC("A")="Select DIVISION: " D ^DIC K DLAYGO Q:+Y'>0 S DA=+Y S DIE=128.99,DR="[GMRD UPLOAD PARAMETER EDIT]" D ^DIE D SETPARM^GMRDLIBE W !!,"Now edit the REPORT TYPE file:",! F D Q:+$G(Y)'>0 . N GMRDREP,GMRDX . S DIC="^GMR(128.1,",DIC(0)="AEMQZ",DIC("A")="Select REPORT TYPE: " . I $D(^DISV(DUZ,DIC)),'$D(GMRD1ST) S DIC("B")=$G(^DISV(DUZ,DIC)), GMRD1ST=1 . D ^DIC K DIC Q:+Y'>0 S DA=+Y,GMRDREP=Y,GMRDREP(0)=Y(0) . S DIE=128.1,DR="[GMRD UPLOAD PARAMETER EDIT]" . D ^DIE S Y=1 . I $D(^GMR(128.1,+DA,"HEAD"))>9!($D(^GMR(128.1,+DA,"ITEM"))>9) D . . W !!,"The header for the ",$P(GMRDREP,U,2)," Report type is now defined as:" . . I $P(GMRDPRM0,U,16)="D" D DHDR^GMRDTHLP(.GMRDREP,GMRDPRM0,GMRDPRM1) . . I $P(GMRDPRM0,U,16)="C" D CHDR^GMRDTHLP(.GMRDREP,GMRDPRM0,GMRDPRM1) . . W ! Q TXTFLD(TFILE,GMRDFLT) ; Get Text Field # from ^DD(Target file #, N DIC,X,Y S DIC="^DD("_TFILE_",",DIC(0)="AEMQZ",DIC("A")="Select TARGET TEXT FIELD : " S DIC("S")="I +$$ISWP^GMRDUPAR(TFILE,+Y)" I $D(GMRDFLT) S DIC("B")=GMRDFLT D ^DIC G:+Y'>0 TXTFLDX S Y=+Y_";"_$P($P(Y(0),U,4),";") TXTFLDX Q Y ISWP(TFILE,TFLD) ; Is a given field a Word-processing type field N X,Y S Y=0 I +$P(^DD(TFILE,TFLD,0),U,2)>0 D . N SFILE S SFILE=+$P(^DD(TFILE,TFLD,0),U,2) . S Y=$S($P(^DD(SFILE,.01,0),U,2)="W":1,1:0) Q Y 2. The input transform for the TARGET FILE field (#.05) in the GMR REPORT TYPE file, which is a pointer to the File of Files, assures that only files which include the "GMRD" application group may be chosen for inclusion in the upload. This was done to assure that the site could not inadvertently choose an inappropriate target file (NOTE: the only file exported with this Application Group is the GMR REPORTS FILE (#128), where Discharge Summaries themselves are housed). The input transform looks like this: S DIC("S")="I $D(^DIC(+Y,""%"",""B"",""GMRD""))" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DISCHARGE SUMMARY ISC: Salt Lake City NUMBER: 831 IA #: 831 DATE CREATED: NOV 01, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCS58CC NAME: DBIA315-B ORIGINAL NUMBER: 315 ID: PRCS58CC CREATOR: BAUMANN,SCOTT A STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: PRCS58CC COMPONENT DESCRIPTION: Post a payment or credit amount to a 1358 authorization. VARIABLES: PRCSX TYPE: Input VARIABLES DESCRIPTION: String value consisting of pieces delimited by the caret (^). Piece Data --- -------------------------------------------- 1 IEN of Daily Reference # in 424 =$O(^PRC(424,"B","STA#-OBLIGATION#-REF#",0)) 2 INTERNAL DATE/TIME 3 AMOUNT of PAYMENT 4 COMMENTS 5 COMPLETE FLAG 6 INTERFACE ID 7 (optional) SKIP FCP CHECK FLAG, set = 1 to skip the fund control point access check (7th piece added by patch PRC*5.1*162) VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: If Y'=1 call failed and reason is in the second piece of Y SUBSCRIBING PACKAGE: FEE BASIS ISC: Albany SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM SUBSCRIBING DETAILS: ADDED 1/6/2009 DBA Comments: 4/25/12 - Opened for editing. Concurrence from IFCAP (Lyford Greene and Mavis McGaugh) and Prosthetics (Deven Atkinson). ICR reactivated on 4/26/12. Patch PRC*5.1*162 will modify IFCAP routine PRCS58CC by adding a new 7th piece to input variable PRCSX. Patch FB*3.5*132 will modify Fee Basis to set the 7th piece = 1 when a background job calls PRCS58CC during processing of new transactions sent by Central Fee (Austin). DATE ACTIVATED: APR 26, 2012 DATE/TIME EDITED: JAN 06, 2009@14:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BAUMANN,SCOTT WITH CONCURRENCE OF: ANTHONY,MARY DATE/TIME EDITED: JAN 06, 2009@14:03 ACTION: USAGE CHOICE CHANGED AT THE REQUEST OF: BAUMANN,SCOTT WITH CONCURRENCE OF: ANTHONY,MARY DATE/TIME EDITED: APR 25, 2012@15:41 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: BAUMANN,SCOTT WITH CONCURRENCE OF: GREENE,LYFORD DATE/TIME EDITED: APR 26, 2012@15:20 ACTION: APPROVED AT THE REQUEST OF: BAUMANN,SCOTT WITH CONCURRENCE OF: GREENE,LYFORD NUMBER: 832 IA #: 832 DATE CREATED: NOV 01, 1993 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCSUT31 NAME: DBIA315-C ORIGINAL NUMBER: 315 ID: PRCSUT31 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: Input variables: Required - 'X' equal to the full Obligation Number 'PRCS("TYPE")' equal to the namespace of the application. (For Fee it is 'FB') Output variables: 'Y' Process: If 'Y' equal null, invalid Obligation Number 'Y' equal the next sequence number SUBSCRIBING PACKAGE: FEE BASIS ISC: Albany NUMBER: 833 IA #: 833 DATE CREATED: NOV 01, 1993 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIC NAME: DBIA316-B ORIGINAL NUMBER: 316 ID: DIC GENERAL DESCRIPTION: 3. The lookup routine, XTLKDICL, is often executed recursively by Fileman. under some conditions, it is not appropriate to proceed with the lookup and processing must pass back to DIC at the appropriate entry point. MTLU therefore needs support for the entry points, ASK^DIC and RTN^DIC. Some of the variables that are used by the ASK^DIC and RTN^DIC calls are: Variables: Used in: DO(2 EN2+3,EN2+5 DIC TS+1 DIC(0 XTLKDICL+3,EN1+2 DIE XTLKDICL+3 DIPGM(0 XTLKDICL+3,XTLKDICL+5 DO TS DO(2 TS,TS+1,TS+2 X XTLKDICL+4,EN2+1,EN2+3,EN2+5,TS+1,TS+4,TS+8,TS+9 Y EN2+1,TS,TS+8,TS+9 Label References: EN1 TS+9 EN2 XTLKDICL+5,TS+8 External References: ASK^DIC EN1+2 RTN^DIC XTLKDICL+3,EN2+3,EN2+5 The calls to RTN^DIC and ASK^DIC are granted for the exclusive use of the Kernel's Toolkit package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10283412 COMPONENT/ENTRY POINT: ASK COMPONENT/ENTRY POINT: RTN SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 834 IA #: 834 DATE CREATED: NOV 02, 1993 CUSTODIAL PACKAGE: VETERANS ADMINISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VALM2 NAME: DBIA317-B ORIGINAL NUMBER: 317 ID: VALM2 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: SEL COMPONENT DESCRIPTION: This is what the selector was converted from SDUL SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany SUBSCRIBING PACKAGE: FEE BASIS SUBSCRIBING PACKAGE: SCHEDULING DBA Comments: MM/7-10-12: Added Scheduling as a subscriber. VistA Maintenance Team found a pre-existing reference to SEL~VALM2 during development of SD*5.3*597. DATE/TIME EDITED: JUL 10, 2012@10:15 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SPILLER,RICHARD WITH CONCURRENCE OF: DIMICELI,RON NUMBER: 835 IA #: 835 FILE NUMBER: 3.5 GLOBAL ROOT: %ZIS(1, DATE CREATED: DEC 16, 1993 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA323-B ORIGINAL NUMBER: 323 ID: %ZIS(1, GENERAL DESCRIPTION: To support bar code label printing and downloading/uploading, the Controlled Substances package has found it necessary to develop hardware specific parameters for the TERMINAL TYPE and DEVICE file. Centralized procurements of Hewlett Packard and Kyocera laser printers and Intermec trakkers have steered this package toward the use of these hardware types. As testing has proceeded, the need to accurately communicate complex strings for insertion into the TERMINAL TYPE file has proved difficult. An l misinterpreted as a 1, a 0 mininterpreted as a O, or an inadvertant space or lack thereof all can render a device inoperable. It is therefore agreed that IRM utility routines (PSDTER*) be exported which would allow ^DIC look-ups to the TERMINAL TYPE and DEVICE files, ^DIR verification of the selections, and ^DIE stuffs to the necessary fields identified as follows: GLOBAL MAP DATA DICTIONARY #3.5 -- DEVICE FILE STORED IN ^%ZIS(1, (VERSION 7.1) -------------------------------------------------------------------------- ^%ZIS(1,D0,0)= (#.01) NAME [1F] ^ (#1) $I [2F] ^ (#4) ASK DEVICE [3S] ^ ==>(#5) ASK PARAMETERS [4S] ^ ==> ^ (#1.95) SIGN-ON/SYSTEM DEVICE [11S] ^ ^%ZIS(1,D0,1)= (#.02) LOCATION OF TERMINAL [1F] ^ ^%ZIS(1,D0,91)= (#9) MARGIN WIDTH [1N] ^ (#10) FORM FEED [2F] ^ (#11) PAGE ==>LENGTH [3N] ^ (#12) BACK SPACE [4F] ^ ^%ZIS(1,D0,SUBTYPE)= (#3) SUBTYPE [1P] ^ ^%ZIS(1,D0,TYPE)= (#2) TYPE [1S] ^ ^%ZIS(1,D0,VMS)= (#61) LAT SERVER NODE [1F] ^ (#62) LAT SERVER PORT [2F] ^ ==>(#63) VMS DEVICE TYPE [3S] ^ (#64) LAT PORT SPEED [4S] ^ STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 836 IA #: 836 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: DEC 23, 1993 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA325-B ORIGINAL NUMBER: 325 ID: DGPM( GENERAL DESCRIPTION: Globals -- For the PATIENT MOVEMENT (#405) file: Zeroth node (^DGPM(ien,0)): Field Name/#/Piece on node Reason Needed ============================ ============= DATE/TIME (#.01) (1) Determine the movement date/time TRANSACTION (#.02) (2) Determine if the movement is an admission PATIENT (#.03) (3) Determine the pointer to the patient whose movement it is ADMISSION/CHECK-IN MOVEMENT (#.14) (14) Determine the pointer to the admission for a particular movement DISCHARGE/CHECK-OUT MOVEMENT (#.17) (17) Determine the pointer to the discharge for a particular movement MAS MOVEMENT TYPE (#.18) (18) Determine the movement type ASIH TRANSFER (#.21) (21) Determine if the movement was due to ASIH "APCA" cross reference (^DGPM("APCA",DFN,Adm Ptr,Mvmt Date,ien)): This cross-reference is used to find all of the movements, as of a specified date, for a specific admission for a patient. "ATID1" cross reference (^DGPM("ATID1",DFN,Inv Adm Date,ien)): This cross-reference is used to find all of a patient's admissions as of a specific date. Please note that all of these references may be found in the routine IVMUFNC1. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 837 IA #: 837 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: DEC 23, 1993 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA325-C ORIGINAL NUMBER: 325 ID: DPT( GENERAL DESCRIPTION: Globals -- For the APPOINTMENT (#1900) field (sub-file #2.98) of the PATIENT (#2) file: Zeroth node (^DPT(DFN,"S",Visit Date/Time,0)): Field Name/#/Piece on node Reason Needed ============================ ============= APPOINTMENT DATE/TIME (#.001) (ien) Determine the visit date CLINIC (#.01) (1) Need clinic to see of it is non-count STATUS (#3) (2) Need to see if visit was cancelled APPOINTMENT TYPE (#9.5) (16) Need to see if Appointment Type is billable OUTPATIENT ENCOUNTER (#21) (20) Need pointer to the Outpatient Encounter (if it exists) to see if visit was related to claimed exposures For the DISPOSITION LOG-IN DATE/TIME (#1000) field (sub-file #2.101) of the PATIENT (#2) file: Zeroth node (^DPT(DFN,"DIS",Inv Log-In Date/Time,0)): Field Name/#/Piece on node Reason Needed ============================ ============= STATUS (#1) (2) Make sure registration is not Application w/o Exam OUTPATIENT ENCOUNTER (#18) (18) Need pointer to the Outpatient Encounter (if it exists) to see if visit was related to claimed exposures STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 839 IA #: 839 FILE NUMBER: 209.42 GLOBAL ROOT: SDD(409.42, DATE CREATED: DEC 23, 1993 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA325-E ORIGINAL NUMBER: 325 ID: SDD(409.42, GENERAL DESCRIPTION: For the OUTPATIENT CLASSIFICATION (#409.42) file: Zeroth node (^SDD(409.42,ien,0)): Field Name/#/Piece on node Reason Needed ============================ ============= TYPE (#.01) (1) Determine whether question relates to AO, SC, IR, or EC VALUE (#.03) (3) Determine whether care was related to the claimed exposure. "OE" cross reference (^SDD(409.42,"OE",ptr to #409.68,ien)): This cross-reference is used to find all classification answers for a specific outpatient encounter. Please note that all of these references may be found in the routine IVMUFNC2. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 840 IA #: 840 DATE CREATED: JAN 12, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DII NAME: DBIA329-B ORIGINAL NUMBER: 329 ID: DII STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: B COMPONENT DESCRIPTION: INQ+1^ESPFM S DI=DIC,DPP(1)=+Y_"^^^@",DK=+Y G B^DII SUBSCRIBING PACKAGE: POLICE & SECURITY ISC: Dallas NUMBER: 842 IA #: 842 GLOBAL ROOT: DD( DATE CREATED: JAN 12, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA329-D ORIGINAL NUMBER: 329 ID: DD( GENERAL DESCRIPTION: 1. Read only: ^DD(910.2,.01,0) - ESP POLICE REGISTRATION LOG File - Displays an identifier. 2. Read only: ^DD(910.7,IEN,0,U,R) - ESP SELECTABLES file - Displays the color field as an identifier. 3. ^DD(912,.01,1,2,1.4) - ESP OFFENSE REPORT file - Executes a trigger to stuff institution information. 4. Read only: ^DD(914,.03,0) - ESP VIOLATIONS file - Displays if courtesy or violation identifier. 5. ^DD("SITE" - IEN - INSTITIUTION file read only. 6. Read only: ^DD(915,.01,0) ESP OFFENSE CODES file - Displays Offense Code as an identifier. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: POLICE & SECURITY ISC: Dallas NUMBER: 844 IA #: 844 FILE NUMBER: 63 GLOBAL ROOT: LR( DATE CREATED: JAN 14, 1994 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA333-C ORIGINAL NUMBER: 333 ID: LR( GENERAL DESCRIPTION: Outpatient Pharmacy is granted a temporary integration agreement with Laboratory to obtain results for a given lab test specimen type within a date range. This data may be used many different ways. Current uses are clozapine monitoring, printing on action profile, and drug usage evaluation. GLOBAL MAP DATA DICTIONARY #63 -- LAB DATA FILE STORED IN ^LR( SITE: BIRMINGHAM ISC -------------------------------------------------------------------------- ^LR(D0,"CH",D1,0)= (#.01) DATE/TIME SPECIMEN TAKEN [1D] ^^ (#.03) DATE REPORT COMPLETED [3D] ^^ (#.05) SPECIMEN TYPE [5P] ^ ^LR(D0,"CH",D1,data name#)= (data name#) results ^ STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 845 IA #: 845 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: JAN 18, 1994 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA335-B ORIGINAL NUMBER: 335 ID: DPT( GENERAL DESCRIPTION: Pharmacy Prescription Practices Prototype is granted this DBIA with Scheduling to make the following calls: C. ^DPT(DFN,"S",DATE,0) -> Used to verify that a clinic appointment has not been canceled. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE ISC: Albany NUMBER: 846 IA #: 846 DATE CREATED: JAN 31, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA344-B ORIGINAL NUMBER: 344 GENERAL DESCRIPTION: The Unwinder was originally written as part of OE/RR in the namespace OR. When the Unwinder functionality was separated into the XQOR routines, all the links to OE/RR were isolated into the routine, XQORO. This routine uses OE/RR variables, and calls into OE/RR entry points. The following integration agreements are needed to support this routine (XQORO). OE/RR Variables: The XQORO routine makes sure OE/RR variables are set to the proper values between each protocol that is executed. The following variables are killed between each protocol to protect the OE/RR environment - ORIFN,ORCOST,ORIT,ORSTRT,ORSTOP,ORTO,ORPURG,ORTX,ORSTS,ORPK,ORLOG, ORPCL,OR,ORZ,ORNS The following variables are reset between each protocol - ORVP,ORPV,ORL,ORTS,ORDUZ,ORNP,OROLOC,ORGY,ORACTION,OROLD,ORNS, ORTX,ORUP ORPRFRM is used in conjunction with response time monitoring. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 847 IA #: 847 FILE NUMBER: 100.99 GLOBAL ROOT: ORD(100.99, DATE CREATED: JAN 31, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA344-C ORIGINAL NUMBER: 344 ID: ORD(100.99, GENERAL DESCRIPTION: Read Access to File 100.99: The OE/RR Parameters file (100.99) is accessed in setting up some of the OE/RR variables and in determining if OE/RR is running. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 848 IA #: 848 DATE CREATED: JAN 31, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: OR1 NAME: DBIA344-D ORIGINAL NUMBER: 344 ID: OR1 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: ADD COMPONENT DESCRIPTION: Use of ADD^OR1: This is called to set up a context for adding orders. OREND and ORPTLK are checked after this call to see if the context was successfully established. This agreement, along with the one concerning the use of AFT^OR1, would replace DBIA #8 and DBIA #46. COMPONENT/ENTRY POINT: AFT COMPONENT DESCRIPTION: Use of AFT^OR1: This is called to present and OE/RR review screen and to clear the 'add orders' context. SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 849 IA #: 849 DATE CREATED: JAN 31, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORX2 NAME: DBIA344-E ORIGINAL NUMBER: 344 ID: ORX2 STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: PT1 COMPONENT DESCRIPTION: Use of PT1^ORX2: This unlocks the patient when exiting an 'add orders' context. SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 850 IA #: 850 DATE CREATED: JAN 31, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORUTL NAME: DBIA344-F ORIGINAL NUMBER: 344 ID: ORUTL STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: READ COMPONENT DESCRIPTION: Use of READ^ORUTL: This awaits user input in a manner consistant with OE/RR. SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 851 IA #: 851 DATE CREATED: JAN 31, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORGKEY NAME: DBIA344-G ORIGINAL NUMBER: 344 ID: ORGKEY STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: SET COMPONENT DESCRIPTION: Use of SET^ORGKEY: This sets up keywords that are allowed during the 'add orders' context. SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 852 IA #: 852 DATE CREATED: JAN 31, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORUHDR NAME: DBIA344-H ORIGINAL NUMBER: 344 ID: ORUHDR STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: OE COMPONENT DESCRIPTION: Use of OE^ORUHDR: This sets up the menu headers appropriate for OE/RR with the display of a protocol menu during an 'add orders' context. The variable ORUIEN, which identifies the menu, is set and killed. SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 854 IA #: 854 FILE NUMBER: 8984.2 GLOBAL ROOT: XT(8984.2, DATE CREATED: FEB 04, 1994 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA346-B ORIGINAL NUMBER: 346 ID: XT(8984.2, GENERAL DESCRIPTION: Read only access to ^XT(8984.2,"B" and the associated data node ^XT(8984.2,DA,0) If the user input is found in the "B" cross-reference, and it is a valid "Short Cut" for the Clinical Lexicon - ^XT(8984.2,DA,0)[GMP(757.01 - then the preprocessing of the input string is disabled and the Multi-Term Look-Up Utility (MTLU) is called directly (GMPTA2). Read only access to ^XT(8984.* globals for $D checks in the Environment Check routine prior to installing the Clinical Lexicon (GMPTIENV). i.e. I '$D(^XT(8984.1)) W !,"Multi-Term Look-Up Untility not found" K DIFQ Q Read/Write access to ^XT(8984.* global in Post-Init routines to setup the Multi-Term Look-Up Utility for the Clinical Lexicon (GMPTIPST). i.e., a. Seeding the Local Look-Up file #8984.4 with the Clinical Lexicon Expression file #757.01, the "AWRD" index and the XTLK^GMPTPRNT display routine. b. Seeding the Synonym file #8984.3 with Cancer as a sample synonym for Carcinoma c. Seeding the Short Cut file #8984.2 with DM II as a sample short cut for Diabetes Mellitus, Non-Insulin Dependent STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: LEXICON UTILITY ISC: Salt Lake City NUMBER: 855 IA #: 855 FILE NUMBER: 8984.3 GLOBAL ROOT: XT(8984.3, DATE CREATED: FEB 04, 1994 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA346-C ORIGINAL NUMBER: 346 ID: XT(8984.3, GENERAL DESCRIPTION: Read only access to ^XT(8984.* globals for $D checks in the Environment Check routine prior to installing the Clinical Lexicon (GMPTIENV). i.e. I '$D(^XT(8984.1)) W !,"Multi-Term Look-Up Untility not found" K DIFQ Q Read/Write access to ^XT(8984.* global in Post-Init routines to setup the Multi-Term Look-Up Utility for the Clinical Lexicon (GMPTIPST). i.e., a. Seeding the Local Look-Up file #8984.4 with the Clinical Lexicon Expression file #757.01, the "AWRD" index and the XTLK^GMPTPRNT display routine. b. Seeding the Synonym file #8984.3 with Cancer as a sample synonym for Carcinoma c. Seeding the Short Cut file #8984.2 with DM II as a sample short cut for Diabetes Mellitus, Non-Insulin Dependent STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: LEXICON UTILITY ISC: Salt Lake City NUMBER: 856 IA #: 856 FILE NUMBER: 8984.4 GLOBAL ROOT: XT(8984.4, DATE CREATED: FEB 04, 1994 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA346-D ORIGINAL NUMBER: 346 ID: XT(8984.4, GENERAL DESCRIPTION: Read only access to ^XT(8984.* globals for $D checks in the Environment Check routine prior to installing the Clinical Lexicon (GMPTIENV). i.e. I '$D(^XT(8984.1)) W !,"Multi-Term Look-Up Untility not found" K DIFQ Q Read/Write access to ^XT(8984.* global in Post-Init routines to setup the Multi-Term Look-Up Utility for the Clinical Lexicon (GMPTIPST). i.e., a. Seeding the Local Look-Up file #8984.4 with the Clinical Lexicon Expression file #757.01, the "AWRD" index and the XTLK^GMPTPRNT display routine. b. Seeding the Synonym file #8984.3 with Cancer as a sample synonym for Carcinoma c. Seeding the Short Cut file #8984.2 with DM II as a sample short cut for Diabetes Mellitus, Non-Insulin Dependent STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: LEXICON UTILITY ISC: Salt Lake City NUMBER: 861 IA #: 861 DATE CREATED: APR 21, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: OR NAME: OR ORIGINAL NUMBER: 861 ID: OR STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10212612 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: OE/RR Processor. This is the main entry point to run the OE/RR program. It is called with X set as a variable pointer to the initial protocol. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Variable pointer of the protocol. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany DBA Comments: VITALS REMOVED 5/23/08 DATE/TIME EDITED: MAY 23, 2008@13:27 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: TRAXLER,FRANK NUMBER: 862 IA #: 862 DATE CREATED: APR 21, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORUHDR NAME: ORUHDR ORIGINAL NUMBER: 862 ID: ORUHDR STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10212612 COMPONENT/ENTRY POINT: EXT COMPONENT DESCRIPTION: Displays a standard header for detailed order displays. If calling this from within OE/RR, it is not necessary to killthe returned variables. OE/RR will kill them. VARIABLES: ORIFN TYPE: Both VARIABLES DESCRIPTION: Internal number in file 100 of the order to display. VARIABLES: ORAGE TYPE: Output VARIABLES DESCRIPTION: Patient age. VARIABLES: ORIO TYPE: Output VARIABLES: ORANSI TYPE: Output VARIABLES: ORDOB TYPE: Output VARIABLES DESCRIPTION: Patient Date of Birth VARIABLES: ORFT TYPE: Output VARIABLES: ORHI TYPE: Output VARIABLES: ORNP TYPE: Output VARIABLES DESCRIPTION: Pointer to file 200 for Current Agent/Provider VARIABLES: ORL TYPE: Output VARIABLES DESCRIPTION: Variable pointer to the variable pointer. VARIABLES: ORPD TYPE: Output VARIABLES: ORPNM TYPE: Output VARIABLES DESCRIPTION: Patient name VARIABLES: ORPV TYPE: Output VARIABLES DESCRIPTION: Pointer to Provider file for the person requesting the order. VARIABLES: ORSEQ TYPE: Output VARIABLES: ORSEX TYPE: Output VARIABLES DESCRIPTION: Patient sex. VARIABLES: ORSSN TYPE: Output VARIABLES DESCRIPTION: Patient SSN VARIABLES: ORTIT TYPE: Output VARIABLES DESCRIPTION: Title VARIABLES: ORTS TYPE: Output VARIABLES DESCRIPTION: Pointer to Treating Specialty associated with the order. VARIABLES: ORVP TYPE: Output VARIABLES DESCRIPTION: Variable pointer toe object of an order. VARIABLES: ORWARD TYPE: Output VARIABLES DESCRIPTION: Inpatient Ward location COMPONENT/ENTRY POINT: PGBRK COMPONENT DESCRIPTION: Displays 'Press return to continue or "^" to escape' at page breaks. VARIABLES: DIROUT TYPE: Output VARIABLES DESCRIPTION: User entered a '^^' VARIABLES: OREND TYPE: Output VARIABLES DESCRIPTION: User entered a '^' SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany DBA Comments: VITALS REMOVED 5/23/08 DATE/TIME EDITED: MAY 23, 2008@13:28 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: TRAXLER,FRANK NUMBER: 864 IA #: 864 DATE CREATED: APR 21, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORUTL NAME: ORUTL ORIGINAL NUMBER: 864 ID: ORUTL STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10212612 COMPONENT/ENTRY POINT: READ SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany DBA Comments: VITALS REMOVED 5/23/08 DATE/TIME EDITED: MAY 23, 2008@13:28 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: TRAXLER,FRANK NUMBER: 865 IA #: 865 DATE CREATED: APR 21, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORVOM NAME: ORVOM ORIGINAL NUMBER: 865 ID: ORVOM STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10212612 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany DBA Comments: VITALS REMOVED 5/23/08 DATE/TIME EDITED: MAY 23, 2008@13:29 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: TRAXLER,FRANK NUMBER: 866 IA #: 866 DATE CREATED: APR 21, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORX NAME: ORX ORIGINAL NUMBER: 866 ID: ORX STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10212612 COMPONENT/ENTRY POINT: FILE VARIABLES: OREPDUZ TYPE: Input VARIABLES DESCRIPTION: DUZ of the person entering the order. VARIABLES: ORL TYPE: Input VARIABLES DESCRIPTION: Variable pointer to the variable pointer. VARIABLES: ORPCL TYPE: Input VARIABLES DESCRIPTION: Variable pointer to the protocol that created the order. VARIABLES: ORNP TYPE: Input VARIABLES DESCRIPTION: Pointer to file 200 for Current Agent/Provider VARIABLES: ORVP TYPE: Input VARIABLES DESCRIPTION: Variable pointer to the object of an order. VARIABLES: ORCOST TYPE: Input VARIABLES DESCRIPTION: Cost of the order VARIABLES: OREVENT TYPE: Input VARIABLES DESCRIPTION: Two piece variable delimited by a semicolon. The first piece is the time at which an event should occur. The second piece is a character that has meaning to a package. VARIABLES: ORIT TYPE: Input VARIABLES DESCRIPTION: Variable pointer to the item ordered. VARIABLES: ORLOG TYPE: Input VARIABLES DESCRIPTION: Time the order is entered. VARIABLES: ORPK TYPE: Input VARIABLES DESCRIPTION: Package reference defined by the package when an order is created. VARIABLES: ORPURG TYPE: Input VARIABLES DESCRIPTION: Grace days before an order is purged. VARIABLES: ORSTOP TYPE: Input VARIABLES DESCRIPTION: Order Stop Date VARIABLES: ORSTRT TYPE: Input VARIABLES DESCRIPTION: Order start date VARIABLES: ORSTS TYPE: Input VARIABLES DESCRIPTION: Order status VARIABLES: ORTO TYPE: Input VARIABLES DESCRIPTION: Pointer to Display Group file. Identifies the service receiving the order. VARIABLES: ORTS TYPE: Input VARIABLES DESCRIPTION: Pointer to Treating Specialty associated with the order. VARIABLES: ORTX(i) TYPE: Input VARIABLES DESCRIPTION: Order Text. VARIABLES: ORIFN TYPE: Output VARIABLES DESCRIPTION: Internal entry number of order in file 100 COMPONENT/ENTRY POINT: RETURN VARIABLES: ORIFN TYPE: Input VARIABLES DESCRIPTION: Internal entry number of order. VARIABLES: ORETURN(ORCOST) TYPE: Input VARIABLES DESCRIPTION: Cost of the order. VARIABLES: ORETURN(OREVENT) TYPE: Input VARIABLES DESCRIPTION: Two piece variable delimited by a semicolon. The first piece is the time at which an event should occur. The second piece is a character that has meaning to a package. VARIABLES: ORETURN(ORIT) TYPE: Input VARIABLES DESCRIPTION: Variable pointer to the item ordered. VARIABLES: ORETURN(ORPK) TYPE: Input VARIABLES DESCRIPTION: Free text, package defined reference. VARIABLES: ORETURN(ORPURG) TYPE: Input VARIABLES DESCRIPTION: Grace period before purging order. VARIABLES: ORETURN(ORNP) TYPE: Input VARIABLES DESCRIPTION: Pointer to file 200 for Current Agent/Provider VARIABLES: ORETURN(ORSTOP) TYPE: Input VARIABLES DESCRIPTION: Stop Date VARIABLES: ORETURN(ORSTRT) TYPE: Input VARIABLES DESCRIPTION: Start Date VARIABLES: ORETURN(ORSTS) TYPE: Input VARIABLES DESCRIPTION: Pointer to Order Status VARIABLES: ORETURN(ORTX,i) TYPE: Input VARIABLES DESCRIPTION: Order Text COMPONENT/ENTRY POINT: ST VARIABLES: ORIFN TYPE: Input VARIABLES DESCRIPTION: Internal entry number of the order. VARIABLES: ORSTS TYPE: Input VARIABLES DESCRIPTION: Order Status SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham DBA Comments: VITALS REMOVED 5/23/08 DATE/TIME EDITED: MAY 23, 2008@13:29 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: TRAXLER,FRANK NUMBER: 867 IA #: 867 DATE CREATED: JUN 29, 1999 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORX2 NAME: ORX2 ORIGINAL NUMBER: 867 ID: ORX2 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10212612 COMPONENT/ENTRY POINT: LK COMPONENT DESCRIPTION: This interactive call will attempt to lock a patient's "chart" when adding new orders; if the lock fails, a message will be displayed indicating who has the patient's chart locked currently. Applications using this entry point must also call ULK^ORX2 to unlock the chart when finished. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Variable pointer of patient. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Y=1 if lock is successful, 0 if failed. COMPONENT/ENTRY POINT: ULK COMPONENT DESCRIPTION: This silent call will unlock a patient's "chart" after adding new orders. Do not call this entry point unless you have already successfully locked the chart via LK^ORX2. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Variable pointer to the patient. COMPONENT/ENTRY POINT: LOCK COMPONENT DESCRIPTION: This silent call will attempt to lock a patient's "chart" when adding new orders. Applications using this entry point must also call UNLOCK^ORX2 to unlock the chart when finished. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This parameter is a pointer to the Patient file #2. VARIABLES: $$LOCK TYPE: Output VARIABLES DESCRIPTION: Function returns 1 if lock is successful or 0^message if failed. COMPONENT/ENTRY POINT: UNLOCK COMPONENT DESCRIPTION: This silent call will unlock a patient's "chart" after adding new orders. Do not call this entry point unless you have already successfully locked the chart via $$LOCK^ORX2(DFN). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This parameter is a pointer to the Patient file #2. COMPONENT/ENTRY POINT: LOCK1 COMPONENT DESCRIPTION: This silent call will attempt to lock an order in the Orders file #100 when it is updated. Applications using this entry point must also call UNLK1^ORX2 to unlock the order when finished. VARIABLES: ORIFN TYPE: Input VARIABLES DESCRIPTION: This parameter is a pointer to the Orders file #100. VARIABLES: $$LOCK1 TYPE: Output VARIABLES DESCRIPTION: Function returns 1 if lock is successful or 0^message if failed. COMPONENT/ENTRY POINT: UNLK1 COMPONENT DESCRIPTION: This silent call will unlock an order after updating it. Do not call this entry point unless you have already successfully locked the order via $$LOCK1^ORX2(ORIFN). VARIABLES: ORIFN TYPE: Input VARIABLES DESCRIPTION: This parameter is a pointer to the Orders file #100. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: CARE MANAGEMENT DBA Comments: VITALS REMOVED 5/23/08 DATE/TIME EDITED: MAY 23, 2008@13:30 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: TRAXLER,FRANK NUMBER: 868 IA #: 868 DATE CREATED: APR 21, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORX3 NAME: ORX3 ORIGINAL NUMBER: 868 ID: ORX3 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10212612 COMPONENT/ENTRY POINT: NOTE COMPONENT DESCRIPTION: This is an entry point that creates a notification for a package. VARIABLES: ORNOTE(i) TYPE: Input VARIABLES DESCRIPTION: i=internal # of the notification VARIABLES: ORVP TYPE: Input VARIABLES DESCRIPTION: Variable pointer to the patient. VARIABLES: ORIFN TYPE: Input VARIABLES DESCRIPTION: Order number that you want this notification to linked to. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City DBA Comments: VITALS REMOVED 5/23/08 DATE/TIME EDITED: MAY 23, 2008@13:30 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: TRAXLER,FRANK NUMBER: 869 IA #: 869 DATE CREATED: APR 21, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORX5 NAME: ORX5 ORIGINAL NUMBER: 869 ID: ORX5 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10212612 COMPONENT/ENTRY POINT: DC COMPONENT DESCRIPTION: This entry is called when a package needs to create a DC order. VARIABLES: ORIFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the order. COMPONENT/ENTRY POINT: HOLD COMPONENT DESCRIPTION: This entry is called when a package needs to place a HOLD on an ordered item. VARIABLES: ORIFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the order. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany DBA Comments: VITALS REMOVED 5/23/08 DATE/TIME EDITED: MAY 23, 2008@13:31 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: TRAXLER,FRANK NUMBER: 870 IA #: 870 DATE CREATED: APR 21, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORX7 NAME: ORX7 ORIGINAL NUMBER: 870 ID: ORX7 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10212612 COMPONENT/ENTRY POINT: DC COMPONENT DESCRIPTION: This entry point is provided for orders that are discontinued by the service. This creates a DC order for the order identified by ORIFN. VARIABLES: ORIFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the order. VARIABLES: ORNATR TYPE: Input VARIABLES DESCRIPTION: Identifies the Nature of Order. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany DBA Comments: VITALS REMOVED 5/23/08 DATE/TIME EDITED: MAY 23, 2008@13:31 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: TRAXLER,FRANK NUMBER: 871 IA #: 871 DATE CREATED: APR 21, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORX8 NAME: ORX8 ORIGINAL NUMBER: 871 ID: ORX8 CREATOR: MALMROSE,CARY STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10212612 COMPONENT/ENTRY POINT: EN(ORIFN) COMPONENT DESCRIPTION: This entry point returns data from the Order file (100) for a particular order. VARIABLES: ORIFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the order. VARIABLES: ORUPCHUK('ORDUZ') TYPE: Output VARIABLES DESCRIPTION: =WHO ENTERED^External Format VARIABLES: ORUPCHUK('ORL') TYPE: Output VARIABLES DESCRIPTION: =PATIENT LOCATION VARIABLES: ORUPCHUK('ORNP') TYPE: Output VARIABLES DESCRIPTION: =CURRENT AGENT/PROVIDER^External format VARIABLES: ORUPCHUK('ORODT') TYPE: Output VARIABLES DESCRIPTION: =WHEN ENTERED VARIABLES: ORUPCHUK('ORPCL') TYPE: Output VARIABLES DESCRIPTION: =PROTOCOL VARIABLES: ORUPCHUK('ORPV') TYPE: Output VARIABLES DESCRIPTION: =CURRENT AGENT/PROVIDER^External Format VARIABLES: ORUPCHUK('ORSTOP') TYPE: Output VARIABLES DESCRIPTION: =STOP DATE VARIABLES: ORUPCHUK('ORSTRT') TYPE: Output VARIABLES DESCRIPTION: =CURRENT START DATE VARIABLES: ORUPCHUK('ORSTS') TYPE: Output VARIABLES DESCRIPTION: =STATUS^External format VARIABLES: ORUPCHUK('ORTO') TYPE: Output VARIABLES DESCRIPTION: =TO (display group)^External Format VARIABLES: ORUPCHUK('ORTX',i) TYPE: Output VARIABLES DESCRIPTION: =ORDER TEXT (Multiple) VARIABLES: ORUPCHUK('ORVP') TYPE: Output VARIABLES DESCRIPTION: =OBJECT OF ORDER SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: 4/24/13 DT: Added for use with VPR*1*1 DBA Comments: 3/3/09 - removed NOTIF entry point as incorrect and not resident in program. VITALS REMOVED 5/23/08 4/24/13 DT - Added VPR as subscriber DATE ACTIVATED: MAR 03, 2009 DATE/TIME EDITED: MAY 23, 2008@13:32 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: TRAXLER,FRANK DATE/TIME EDITED: MAR 03, 2009@11:09 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: MCCORMACK,JOHN WITH CONCURRENCE OF: MALMROSE,CARY DATE/TIME EDITED: MAR 03, 2009@11:41 ACTION: CONTENT CORRECTED AT THE REQUEST OF: MALMROSE,CARY DATE/TIME EDITED: APR 10, 2009@15:43 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MCDEARMON,JAMES DATE/TIME EDITED: APR 24, 2013@11:09 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: BUECHLER,MELANIE NUMBER: 872 IA #: 872 FILE NUMBER: 101 GLOBAL ROOT: ORD(101, DATE CREATED: APR 28, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: File 101 ORIGINAL NUMBER: 872 ID: ORD(101, GENERAL DESCRIPTION: This file may be referenced by packages to maintain protocols within their namespace. This file may also be pointed to. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10212612 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING DETAILS: LAB ADDED 2/16/2011 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: VISIT TRACKING ISC: Dallas SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City SUBSCRIBING PACKAGE: DISCHARGE SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: To allow the user to get a detailed description of the actions that are executable from menu-type protocols, applications need to be able to $ORDER through the subscript ^ORD(101,DO,10,D1,0) to get sub-fields #1 (ITEM) and # 3 (SEQUENCE) of the 101.01 multiple for each ITEM. Then get field #1 (ITEM TEXT) and #3.5 (DESCRIPTION) for each PROTOCOL encountered in the ITEM MULTIPLE for a given menu. To allow the user to retrieve Discharge Summaries into the review screen based on Signature Status and Search Category (e.g., by PATIENT, PROVIDER, or TREATING SPECIALTY), we need to be able to execute a DIC call on file 101 to retrieve the zero node of a record and to reference field # 24 (SCREEN) in order to set up the local variables to be used to execute the ^XQORM call. SUBSCRIBING PACKAGE: KERNEL ISC: Oakland SUBSCRIBING PACKAGE: LEXICON UTILITY ISC: Salt Lake City SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING PACKAGE: AUTHORIZATION/SUBSCRIPTION ISC: Salt Lake City SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE DBA Comments: JSHARVEY 20061204/ ADDED LEXICON TO SUBSCRIBERS AS PER K. ROWE. JSHARVEY 20070124/ ADDED E CLAINS MGMT ENGINE TO SUBSCRIBERS. VITALS REMOVED 5/23/08 JSHARVEY 20110216/ ADDED LAB TO SUBSCRIBERS. DATE/TIME EDITED: JAN 24, 2007@23:18 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHITE,DARLENE WITH CONCURRENCE OF: FORT,WALLY DATE/TIME EDITED: DEC 04, 2006@14:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: ROWE,KIMBALL WITH CONCURRENCE OF: FORT,WALLY DATE/TIME EDITED: MAY 23, 2008@13:33 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: TRAXLER,FRANK DATE/TIME EDITED: FEB 16, 2011@12:58 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SMULLEN,GEOFF WITH CONCURRENCE OF: BEUSCHEL,GARY NUMBER: 873 IA #: 873 FILE NUMBER: 100.98 GLOBAL ROOT: ORD(100.98, DATE CREATED: APR 28, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: File 100.98 ORIGINAL NUMBER: 873 ID: ORD(100.98, GENERAL DESCRIPTION: This file may be referenced to determine an appropriate Display Group for an order in the manner: S ORTO=$O(^ORD(100.98,'B','OTHER HOSPITAL SERVICES',0)) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10212612 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING DETAILS: AMIE ADDED 4/13/2011 SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: Added for use with VPR*1*1 DBA Comments: VITALS REMOVED 5/23/08 AMIE ADDED 4/13/2011 4/24/13 DT: Added VPR as subscriber for use in VPR*1*1 DATE/TIME EDITED: MAY 23, 2008@13:33 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: TRAXLER,FRANK DATE/TIME EDITED: APR 13, 2011@16:22 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CRUMLEY,JAMIE WITH CONCURRENCE OF: MCGINNIS,RON DATE/TIME EDITED: APR 24, 2013@13:10 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: BUECHLER,MELANIE DATE/TIME EDITED: APR 24, 2013@13:12 NUMBER: 874 IA #: 874 FILE NUMBER: 100.99 GLOBAL ROOT: ORD(100.99, DATE CREATED: APR 28, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: File 100.99 ORIGINAL NUMBER: 874 ID: ORD(100.99, GENERAL DESCRIPTION: This file may be referenced by packages interfacing with OE/RR to see if OE/RR has been installed in the manner: I $D(^ORD(100.99)) ... Packages may also setup entries in the Package Parameters portion of this file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10212612 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham DBA Comments: VITALS REMOVED 5/23/08 DATE/TIME EDITED: MAY 23, 2008@13:34 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: TRAXLER,FRANK NUMBER: 875 IA #: 875 FILE NUMBER: 100.01 GLOBAL ROOT: ORD(100.01, DATE CREATED: APR 28, 1994 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: File 100.01 ORIGINAL NUMBER: 875 ID: ORD(100.01, GENERAL DESCRIPTION: This file may be pointed to. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10212612 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE DBA Comments: VITALS REMOVED 5/23/08 6/15/12-The CAPRI team is creating a new "FORM 28-8861" (#396.9) file for a Vocational Rehab enhancement. The new file contains a field that needs to point to the ORDER STATUS (#100.01) file. Patch # is DVBA*2.7*181 "CAPRI VIRTUAL VA, VOC. REHAB ENHANCEMENTS & DEFECT FIXES" and is scheduled for release in late August or early September, 2012. DATE/TIME EDITED: MAY 23, 2008@13:39 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: TRAXLER,FRANK DATE/TIME EDITED: JUN 15, 2012@14:26 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MCGINNIS,RON WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 886 IA #: 886 FILE NUMBER: 50 GLOBAL ROOT: PSDRUG( DATE CREATED: NOV 17, 1994 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA886 ORIGINAL NUMBER: 886 ID: PSDRUG( GLOBAL REFERENCE: PSDRUG(D0,0) FIELD NUMBER: 2 FIELD NAME: VA CLASSIFICATION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. As described in DBIA885, External Peer Review needs to identify patients receiving prescriptions in certain VA classes. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 10191489 SUBSCRIBING PACKAGE: EXTERNAL PEER REVIEW ISC: Albany EDITOR: BLOCKER,DAVE NUMBER: 887 IA #: 887 FILE NUMBER: 8984.4 GLOBAL ROOT: XT(8984.4, DATE CREATED: MAY 16, 1994 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: MTLU setup ORIGINAL NUMBER: 887 ID: XT(8984.4, GLOBAL REFERENCE: XT(8984.4,757.01,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .03 FIELD NAME: INDEX LOCATION: 0;3 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: XT(8984.4,757.01,1) FIELD NUMBER: .02 FIELD NAME: DISPLAY PROTOCOL LOCATION: 1;1 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: The Clinical Lexicon Utility needs to write to the Kernel Toolkit Multi-Term Look-up Utility's (MTLU) files/DDs during the Post-Init. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10417844 SUBSCRIBING PACKAGE: CLINICAL LEXICON UTILITY ISC: Salt Lake City NUMBER: 888 IA #: 888 FILE NUMBER: 8984.1 GLOBAL ROOT: DD(8984.1 DATE CREATED: MAY 16, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: MTLU setup ORIGINAL NUMBER: 888 ID: DD(8984.1 GLOBAL REFERENCE: DD(8984.1,.02,'V',D0,0) FIELD NUMBER: .01 FIELD NAME: FILE LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: MESSAGE LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .03 FIELD NAME: ORDER LOCATION: 0;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: .05 FIELD NAME: SHOULD ENTRIES BE SCREENED LOCATION: 0;5 ACCESS: Both R/W w/Fileman FIELD NUMBER: .06 FIELD NAME: SHOULD USER BE ALLOWED TO ADD A NEW ENTRY (LAYGO) LOCATION: 0;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: .04 FIELD NAME: PREFIX LOCATION: 0;4 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: The Clinical Lexicon Utility needs to write to the DD of the Kernel Toolkit Multi-Term Look-up Utility (MTLU) during the Post-Init. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10417865 SUBSCRIBING PACKAGE: LEXICON UTILITY ISC: Salt Lake City NUMBER: 889 IA #: 889 FILE NUMBER: 8984.2 GLOBAL ROOT: DD(8984.2, DATE CREATED: MAY 16, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: MTLU setup ORIGINAL NUMBER: 889 ID: DD(8984.2, GLOBAL REFERENCE: DD(8984.2,.02,'V',D0,0) FIELD NUMBER: .01 FIELD NAME: FILE LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: MESSAGE LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .03 FIELD NAME: ORDER LOCATION: 0;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: .05 FIELD NAME: SHOULD ENTRIES BE SCREENED LOCATION: 0;5 ACCESS: Both R/W w/Fileman FIELD NUMBER: .06 FIELD NAME: SHOULD USER BE ALLOWED TO ADD A NEW ENTRY (LAYGO) LOCATION: 0;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: .04 FIELD NAME: PREFIX LOCATION: 0;4 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: The Clinical Lexicon Utility needs to write to the DD of Kernel Toolkit Multi-Term Look-up Utility (MTLU) during the Post-Init. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10417881 SUBSCRIBING PACKAGE: LEXICON UTILITY ISC: Salt Lake City NUMBER: 890 IA #: 890 FILE NUMBER: 8984.2 GLOBAL ROOT: XT(8984.2, DATE CREATED: MAY 16, 1994 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: MTLU setup ORIGINAL NUMBER: 890 ID: XT(8984.2, GLOBAL REFERENCE: XT(8984.2,D0,0) FIELD NUMBER: .01 FIELD NAME: FREQUENTLY USED NARRATIVE LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: ENTRY LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .03 FIELD NAME: CODE LOCATION: 0;3 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: The Clinical Lexicon Utility needs to write to the Kernel Toolkit Multi-Term Look-up Utillity's (MTLU) files/DDs during the Post-Init. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10417891 SUBSCRIBING PACKAGE: LEXICON UTILITY ISC: Salt Lake City NUMBER: 891 IA #: 891 FILE NUMBER: 8984.3 GLOBAL ROOT: XT(8984.3, DATE CREATED: MAY 16, 1994 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: MTLU setup ORIGINAL NUMBER: 891 ID: XT(8984.3, GLOBAL REFERENCE: XT(8984.3,D0,0) FIELD NUMBER: .01 FIELD NAME: TERM LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: ASSOCIATED FILE LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .03 FIELD NAME: SYNONYM LOCATION: 1;0 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Multiple GLOBAL REFERENCE: XT(8984.3,D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: SYNONYM LOCATION: 0;1 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: The Clinical Lexicon Utility needs to write to the Kernel Toolkit Multi-Term Look-up Utility's (MTLU) files/DDs during the Post-Init. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10417902 SUBSCRIBING PACKAGE: LEXICON UTILITY ISC: Salt Lake City NUMBER: 892 IA #: 892 DATE CREATED: FEB 15, 1996 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSLRCE NAME: GMTSLRCE ORIGINAL NUMBER: 892 ID: GMTSLRCE GENERAL DESCRIPTION: The Adverse Reaction Tracking (ART) package uses a call to XTRCT^GMTSLRCE to extract lab results. A check is made for the existence of the routine i.e., $T(GMTSLRCE^GMTSLRCE). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19277455 COMPONENT/ENTRY POINT: XTRCT VARIABLES: LRDFN TYPE: Input VARIABLES DESCRIPTION: IFN of patient in Lab Data (63) file. VARIABLES: SEX TYPE: Input VARIABLES DESCRIPTION: Sex of patient, where F=female and M=male. VARIABLES: GMTS1 TYPE: Input VARIABLES DESCRIPTION: Inverse end date of search for lab data. VARIABLES: GMTS2 TYPE: Input VARIABLES DESCRIPTION: Inverse start date of search for lab data. VARIABLES: MAX TYPE: Input VARIABLES DESCRIPTION: Maximum number of lab orders to be extracted. VARIABLES: RETURN_GLOBAL TYPE: Output VARIABLES DESCRIPTION: The following global will be returned: @REF@("LRC",$J,IDT,SQN)=CDT^SPC^TST^RSL^FLG^UNT^LO^HI where: REF = "^UTILITY" if Health Summary V1.2, or "^TMP" if Health Summary V2.5+. IDT = Inverse collection date/time. SQN = Print order sequence number from file 60. CDT = Collection date and time. SPC = Specimen for lab order in an external printable form. TST = Lab test ordered in a external printable form. RSL = Numeric result of test. FLG = Reference flag (H,*H,L,*L). UNT = Unit of measure (external format). LO = Reference/Therapeutic Lower bound. HI0= Reference/Therapeutic Upper bound. SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING ISC: Hines SUBSCRIBING PACKAGE: MYHEALTHEVET SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 893 IA #: 893 DATE CREATED: DEC 07, 2000 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SROSPLG NAME: SURGERY Data Interface for LABORATORY SERVICE ORIGINAL NUMBER: 893 ID: SROSPLG GENERAL DESCRIPTION: SROSPLG was written as an interface to provide SURGERY data for LABORATORY SERVICE Surgical Pathology reports created during Anatomic Pathology Log-In. Entry point SROSPLG allows the LABORATORY SERVICE user to select from a list of surgeries performed in the last seven days for the given patient. Entry point DISP extracts the chosen surgery data and copies it into the corresponding Surgical Pathology report. STATUS: Active DURATION: Next Version MAIL MESSAGE: 32231861 COMPONENT/ENTRY POINT: SROSPLG COMPONENT DESCRIPTION: The purpose of this component/entry point is to lookup recent surgery data that may exist for this patient/specimen. For the given Surgical Pathology patient, this entry point searches the SURGERY file (#130) for any surgeries performed in the last seven days. If none are found, the user is informed of this. If only one surgery is found, the user is asked if the given surgery is the correct surgery for the specimen. If more than one is found, a surgery may be selected from a list presented to the user. VARIABLES: LRDFN TYPE: Input VARIABLES DESCRIPTION: (Required) This is the LRDFN (#.01) from the patient's record in the LAB DATA file (#63). Based on the provided LRDFN, the code checks the PARENT FILE field (#.02). This field should contain a value of 2, indicating the PATIENT file (#2). If not, program execution ends. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: (Optional) This is the patient's DFN from the PATIENT file (#2). If this variable is not already defined, the program sets it to the value stored in the NAME field (#.03) of the LAB DATA file (#63). VARIABLES: SRTN TYPE: Output VARIABLES DESCRIPTION: Based on the DFN for the patient, a list of surgeries from the last seven days is presented to the user. The IEN from the SURGERY file (#130) for the chosen surgery is return in variable SRTN. If no surgery was found or was selected by the user, SRTN will be undefined. VARIABLES: SRDOC TYPE: Output VARIABLES DESCRIPTION: If the chosen surgery is a non-OR procedure, the PROVIDER (#123) of the SURGERY file (#130) is returned in variable SRDOC. If it is an OR procedure, the SURGEON (#.14) of the SURGERY file (#130) is returned in variable SRDOC. The value in SRDOC will then be stored in field SURGEON/PHYSICIAN (sub-field #.07) of SURGICAL PATHOLOGY (#8) of the LAB DATA file (#63). COMPONENT/ENTRY POINT: DISP COMPONENT DESCRIPTION: This component/entry point is used to extract data from the SURGERY file (#130) for the surgery selected in component SROSPLG and store it in the corresponding sub-fields of SURGICAL PATHOLOGY (#8) of the LAB DATA file (#63). These fields include BRIEF CLINICAL HISTORY (#.013), PREOPERATIVE DIAGNOSIS (#.014), OPERATIVE FINDINGS (#.015), POSTOPERATIVE DIAGNOSIS (#.016). VARIABLES: SRTN TYPE: Input VARIABLES DESCRIPTION: (Required) The IEN from the SURGERY file (#130) for the surgery chosen in component SROSPLG. VARIABLES: LRDFN TYPE: Input VARIABLES DESCRIPTION: (Required) This is the LRDFN (#.01) from the patient's record in the LAB DATA file (#63). VARIABLES: LRSS TYPE: Input VARIABLES DESCRIPTION: (Required) The accession area for the record in the LAB DATA file (#63). It will always be "SP" for SURGICAL PATHOLOGY (#8). VARIABLES: LRI TYPE: Input VARIABLES DESCRIPTION: (Required) The inverse DATE/TIME SPECIMEN TAKEN (sub-field #.01) of SURGICAL PATHOLOGY (#8) of the LAB DATA file (#63). SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 894 IA #: 894 FILE NUMBER: 63 GLOBAL ROOT: LR( DATE CREATED: MAY 18, 1994 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA894 ORIGINAL NUMBER: 894 ID: LR( GLOBAL REFERENCE: LR(D0,0) FIELD NUMBER: .02 FIELD NAME: PARENT FILE LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: In determining the identity of the patient, this field is read to insure this lab record is for a patient in the PATIENT file (#2). FIELD NUMBER: .03 FIELD NAME: NAME LOCATION: 0;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field provides the internal entry number of the patient in File 2. This IEN is then used in the lookup in the SURGERY file (#130), so the proper surgical case can be displayed to the accessioning person for selection of a case. GLOBAL REFERENCE: LR(D0,'SP',D1,.2,0) FIELD NUMBER: 63.08,.013 FIELD NAME: BRIEF CLINICAL HISTORY LOCATION: .2;0 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: The reading is in the form: I '$O(^LR(D0,'SP',D1,.2,0)). If the read finds no existing data the write will occur. The writing is in the form of a call to %XY^%RCR which moves in the information stored in the matching word-processing field in File 130. GLOBAL REFERENCE: LR(D0,'SP',D1,.3,0) FIELD NUMBER: 63.08,.014 FIELD NAME: PREOPERATIVE DIAGNOSIS LOCATION: .3;0 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: The reading is in the form: I '$O(^LR(D0,'SP',D1,.3,0)). If the read finds no existing data, the write will occur. The writing is in the form of hard sets from ^UTILITY created by calls to DIWP and containing information from the matching fields in File 130. Another hard set updates the zero node of this word processing field. GLOBAL REFERENCE: LR(D0,'SP',D1,.4,0) FIELD NUMBER: 63.08,.015 FIELD NAME: OPERATIVE FINDINGS LOCATION: .4;0 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: The reading is in the form: I '$O(^LR(D0,'SP',D1,.4,0)). If the read finds no existing data, the write will occur. The writing is in the form of a call to %XY^%RCR which moves in the information stored in the matching word-processing field in File 130. GLOBAL REFERENCE: LR(D0,'SP',D1,.5,0) FIELD NUMBER: 63.08,.016 FIELD NAME: POSTOPERATIVE DIAGNOSIS LOCATION: .5;0 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: The reading is in the form: I '$O(^LR(D0,'SP',D1,.5,0)). If the read finds no existing data, the write will occur. The writing is in the form of hard sets from ^UTILITY created by calls to DIWP and containing information from the matching fields in File 130. Another hard set updates the zero node of this word processing field. GENERAL DESCRIPTION: The Surgery package has written routines to be used with the Surgical Pathology (SP) portion of the Laboratory package. When an SP specimen is accessioned, the Laboratory package will call the above mentioned Surgery routines. The Surgery routines will allow the accessioning person to associate the specimen with a surgical case and transfer certain information from the SURGERY file (#130) to the LAB DATA file (#63). The information (Brief Clinical History, Preoperative Diagnosis, Operative Findings and Postoperative Diagnosis) will be written to File 63. This agreement gives permission to Surgery to write this information to File 63 if the matching field in File 63 does not already contain data. Also, this agreement allows Surgery to read the PARENT FILE field (.02) and the NAME field (.03) of File 63 to establish the patient identity. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 895 IA #: 895 DATE CREATED: JUN 24, 1994 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSSGIU NAME: PSSGIU ORIGINAL NUMBER: 895 ID: PSSGIU GENERAL DESCRIPTION: Gives the ability to mark entries in the Drug file (50) for use with various packages. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10448501 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: Prompts users to mark or unmark drug entries for use by their package. VARIABLES: PSIUDA TYPE: Input VARIABLES DESCRIPTION: Internal entry number of the drug in the Drug file (50). The variable is not killed by this entry point. VARIABLES: PSIUX TYPE: Input VARIABLES DESCRIPTION: Package information => package code^package name where: Package code. The code used to mark the entry. This code is provided by the Birmingham ISC. Package name. The name of the package for which the item will be used. The variable is not killed by this entry point. COMPONENT/ENTRY POINT: ENS COMPONENT DESCRIPTION: Automatically marks drug entry for use with the package without any user interaction. VARIABLES: PSIUDA TYPE: Input VARIABLES DESCRIPTION: Internal entry number of the drug in the Drug file (50). The variable is not killed by this entry point. INTEGRATION REFERENCES LIST MAR 18,2015 11:24 PAGE 3 -------------------------------------------------------------------------------- VARIABLES: PSIUX TYPE: Input VARIABLES DESCRIPTION: Package information => package code^package name where: Package code. The code used to mark the entry. This code is provided by the Birmingham ISC. Package name. The name of the package for which the item will be used. The variable is not killed by this entry point. COMPONENT/ENTRY POINT: END COMPONENT DESCRIPTION: Automatically unmarks drug entry for use with package with no user interaction. VARIABLES: PSIUDA TYPE: Input VARIABLES DESCRIPTION: Internal entry number of the drug in the Drug file (50). The variable is not killed by this entry point. VARIABLES: PSIUX TYPE: Input VARIABLES DESCRIPTION: Package information => package code^package name where: Package code. The code used to mark the entry. This code is provided by the Birmingham ISC. Package name. The name of the package for which the item will be used. The package name is not required for the END entry point. This variable is not killed by this entry point. SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham EDITOR: BLOCKER,DAVE NUMBER: 896 IA #: 896 FILE NUMBER: 9000001 GLOBAL ROOT: AUPNPAT( DATE CREATED: SEP 06, 1994 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA896 ORIGINAL NUMBER: 896 ID: AUPNPAT( GLOBAL REFERENCE: AUPNPAT(D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: GLOBAL DESCRIPTION: GLOBAL REFERENCE: AUPNPAT(D0,12,0) FIELD NUMBER: 1201 FIELD NAME: LOCATION OF HOME ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: GLOBAL REFERENCE: AUPNPAT(D0,41,0) FIELD NUMBER: 4101 FIELD NAME: HEALTH RECORD NO. ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: GLOBAL REFERENCE: AUPNPAT(D0,41,D1,0) FIELD NUMBER: .01 FIELD NAME: HEALTH RECORD FAC LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: This is the institution using the Health Record No. in field .02. The DEFAULT INSTITUTION in the Kernel Site parameter file is forced into this field when a Patient is added to File 2. GENERAL DESCRIPTION: ** A DBIA agreement is being requested by the Patient/IHS Subset package (PXPT) with the Indian Health Service. This agreement would document the changes in the use of the Patient/IHS file in the VA. ** This description includes a comparison of the VA's Patient/IHS File (9000001) as distributed in the PXPT package and the IHS's Patient/IHS File (9000001). NOTE: Per discussions previously with IHS developers, George Huggins has agreed to have the file named "Patient" file (9000001) in IHS changed to the name "Patient/IHS" file. VA Patient/IHS File: ==================== The VA version of 9000001 has a subset of fields defined in the IHS version. The main consideration for determining what should be distributed in the VA was: "What is the minimal set of data required to have the Patient/IHS file defined and be useable by IHS tools, such as QMAN". Sending out the minimum set limits the confusion of sending out Patient/IHS fields and pointed to files that could cause confusion in the VA. Summary of differences in File and fields: File SPECIAL LOOKUP ROUTINE is sent out as DPTLK File POST SELECTION ACTION is sent out as D ^AUPNPAT The only fields destributed in VA nationally are NAME, LOCATION OF HOME, and HEALTH RECORD NO. multiple. The Health Record No. multiple has had a few changes. The .01 field is based on the Default institution in the Kernel Site Parameter file because the DUZ(2) upon adding a patient may not reflect the institution the patient should be related to. (e.g., Regional Office adding Patients) The .02 field has been changed to be a freetext field long enough for a SSN or pseudo-SSN or DOD PID with dependent counters. The following is the Standard List of Attributes for the VA version: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ STANDARD DATA DICTIONARY #9000001 -- PATIENT/IHS FILE 05/26/94 PAGE 1 STORED IN ^AUPNPAT( (406 ENTRIES) SITE: SLC UCI: DVA,DEV DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE ------------------------------------------------------------------------- This file is IHS's primary patient data file. The NAME (.01) field of this file is a pointer to the VA's patient file (#2). Fields in common between the two dictionaries actually exist only in the VA patient file and are referenced by the IHS patient file as computed fields. All other files containing patient data have backward pointers linking them to this file. The linkage is by patient name and the internal FileMan gener- ated number of the ancillary file is the same number used in this file. All applications developed for the RPMS which require patient data will point to this file. FILE SCREEN (SCR-node) : X "I '$P(^DPT(Y,0),U,19)" W $E(^AUPNPAT(Y,0),0) SPECIAL LOOKUP ROUTINE : DPTLK POST-SELECTION ACTION : D ^AUPNPAT DD ACCESS: @ DEL ACCESS: @ POINTED TO BY: PATIENT field (#.02) of the TIU DOCUMENT File (#8925) PATIENT NAME field (#.05) of the VISIT File (#9000010) PATIENT NAME field (#.02) of the V MEASUREMENT File (#9000010.01) PATIENT NAME field (#.02) of the V PROVIDER File (#9000010.06) PATIENT NAME field (#.02) of the V POV File (#9000010.07) PATIENT NAME field (#.02) of the V LAB File (#9000010.09) PATIENT NAME field (#.02) of the V IMMUNIZATION File (#9000010.11) PATIENT NAME field (#.02) of the V SKIN TEST File (#9000010.12) PATIENT NAME field (#.02) of the V EXAM File (#9000010.13) PATIENT NAME field (#.02) of the V MEDICATION File (#9000010.14) PATIENT NAME field (#.02) of the V TREATMENT File (#9000010.15) PATIENT NAME field (#.02) of the V PATIENT ED File (#9000010.16) PATIENT NAME field (#.02) of the V CPT File (#9000010.18) PATIENT NAME field (#.02) of the V HEALTH FACTORS File (#9000010.23) PATIENT NAME field (#.02) of the PROBLEM File (#9000011) CROSS REFERENCED BY: NAME(B), HEALTH RECORD NO.(D) 9000001,.01 NAME 0;1 POINTER TO PATIENT FILE (#2) (Required) INPUT TRANSFORM: S:$D(X) DINUM=X LAST EDITED: SEP 29, 1990 DESCRIPTION: This field points to the Patient file (#2) and has the same internal number as that file. Thus, the patient's name is the Patient file (#2) name. TECHNICAL DESCR: This field is populated in the VA when a new patient is added to the ^DPT file by the PX09 cross-reference on the Social Security Number (.09) field of ^DPT. Any merging of patients in ^DPT by a VAMC should include this PATIENT/IHS file in its merging process. SOURCE OF DATA: 011/PINAME NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMME R CROSS-REFERENCE: 9000001^B 1)= S ^AUPNPAT("B",$E(X,1,30),DA)="" 2)= K ^AUPNPAT("B",$E(X,1,30),DA) 9000001,1201 LOCATION OF HOME 12;0 WORD-PROCESSING #9000001.12 DESCRIPTION: This is the directions to get to the patients home. 9000001,4101 HEALTH RECORD NO. 41;0 POINTER Multiple #9000001.41 (Add New Entry without Asking) DESCRIPTION: This multiple contains the different health record identifiers by facility. IHS uses a 6 character identifier. The VA uses the social security number which may be up to 10 characters. TECHNICAL DESCR: This multiple is used for Multi-Facility Integration (MFI) processing at IHS facilities. IDENTIFIED BY: HEALTH RECORD NO.(#.02), 9000001.41,.01 HEALTH RECORD FAC 0;1 POINTER TO LOCATION FILE (#999 9999.06) INPUT TRANSFORM: S DINUM=X LAST EDITED: MAR 7, 1991 HELP-PROMPT: ENTER NAME OF FACILITY ASSOCIATED WITH THE HEALTH RECORD NUMBER YOU WISH TO ENTER. DESCRIPTION: This field is a pointer to the LOCATION file. The internal pointer is forced into the third subscript for the 9000001.41 subfile. This allows easy lookup by health record number for the logged on location (facility). The complete subscript for 9000001.41 will be (DFN,41,facility pointer,0). TECHNICAL DESCR: In the VA, the Kernel Site Parameters DEFAULT INSTITUTION field is used to populate this field. This was used instead of the users institution because of regional users ability to add patients to the VA. SOURCE OF DATA: 015/HRSUBR NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAM MER 9000001.41,.02 HEALTH RECORD NO. 0;2 FREE TEXT (Required) INPUT TRANSFORM: I $G(DUZ("AG"))="I" K:(X'?1.6N&(X'?1"T" 5N))!(X?1.6N&(X'=+X)) X LAST EDITED: MAY 24, 1988 HELP-PROMPT: ENTER TEXT FROM 1 TO 10 CHARACTERS. DESCRIPTION: This field is used to represent the health record number related to a facility. IHS uses a 6 character whole number. VA uses the patient SSN from the Patient File (2). TECHNICAL DESCR: In the VA, this field is populated by the PX09 cross-reference on the SSN (.09) field of the Patient File (2). SOURCE OF DATA: 015/HRNUMB NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAM MER CROSS-REFERENCE: 9000001^D 1)= S ^AUPNPAT("D",$E(X,1,30),DA(1),DA) ="" 2)= K ^AUPNPAT("D",$E(X,1,30),DA(1),DA) 9000001.41,.03 DATE INACTIVATED/DELETED 0;3 DATE INPUT TRANSFORM: S %DT="EX" D ^%DT S X=Y K:Y<1 X DESCRIPTION: This is date that the patients entry was inactivated. TECHNICAL DESCR: This is primarily used by IHS facilities for tracking patients. The VA currently is not maintaining this field. 9000001.41,.05 RECORD STATUS 0;5 SET 'D' FOR DELETED; 'I' FOR INACTIVATED; 'M' FOR MERGED; LAST EDITED: APR 19, 1990 HELP-PROMPT: Enter "D" if the record has been deleted. DESCRIPTION: This field is used by the IHS Multi-Facility Integration (MFI) package to determine whether to stop integrating data at a facility for a particular patient and location facility. 9000001.41,.06 STOP INTEGRATION 0;6 SET '0' FOR NO; '1' FOR YES; LAST EDITED: AUG 17, 1988 DESCRIPTION: This field is used by the Mult-Facility Integration (MFI) package, created by IHS, to indicate this patients data should no longer be integrated by MFI. FILES POINTED TO FIELDS LOCATION (#9999999.06) HEALTH RECORD NO.:HEALTH RECORD FAC (#.01) PATIENT (#2) NAME (#.01) =========================================================================== The following are two captures, one of the global map of the Patient File BEFORE VA changes, and the second is the Standard attribute list for the Health Record multiple. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - GLOBAL MAP DATA DICTIONARY #9000001 -- PATIENT FILE 05/26/94 PAGE 1 STORED IN ^AUPNPAT( (1 ENTRY) SITE: SALT LAKE CITY UCI: PCC,PCC ------------------------------------------------------------------------- This file is the primary patient data file. The NAME (.01) field of this file is a backward pointer to the VA's patient file (#2). Fields in common between the two dictionaries actually exist only in the VA patient file and are referenced by the IHS patient file as computed fields. All other files containing patient data have backward pointers linking them to this file. The linkage is by patient name and the internal FileMan gener- ated number of the ancillary file is the same number used in this file. All applications developed for the RPMS which require patient data will point to this file. CROSS REFERENCED BY: CURRENT COMMUNITY(AC), CLASSIFICATION/BENEFICIARY(AD), DATE ESTABLISHED(ADTE), TRIBE OF MEMBERSHIP(AE), EMPLOYER NAME(AF), SPOUSE'S EMPLOYER NAME(AG), TRIBE QUANTUM(AZ1), INDIAN BLOOD QUANTUM(AZ2), PCIS ID NO.(AZZ), NAME(B), HEALTH RECORD NO.(D) ^AUPNPAT(D0,0)= (#.01) NAME [1P] ^ (#.02) DATE ESTABLISHED [2D] ^ ==>(#.03) DATE OF LAST REG. UPDATE [3D] ^ (#.04) OUTPT ==>MED/RR RELEASE DATE [4D] ^ (#.05) MED/RR RELEASE ==>REVOKED DATE [5D] ^ (#.06) PCIS ID NO. [6F] ^ (#.07) ==>TRIBAL ENROLLMENT NO. [7F] ^ (#.08) MFI MEDICAL [8S] ^ ==>(#.09) CHS TRIBAL AFFILIATION [9P] ^ ^ (#.11) ==>ESTABLISHING USER [11P] ^ (#.12) USER-LAST UPDATE [12P] ==>^ (#.13) BLOOD TYPE [13S] ^ (#.14) PRIMARY PROVIDER ==>[14P] ^ (#.15) CHS TX DATE [15D] ^ (#.16) DATE OF LAST ==>UPDATE [16D] ^ (#.17) ASSIGN BENEFITS OBTAINED DATE ==>[17D] ^ (#.18) ASSIGN BENEFITS EXPIRED DATE [18D] ^ ==>(#.19) EMPLOYER NAME [19P] ^ ^ (#.21) EMPLOYMENT ==>STATUS [21S] ^ (#.22) SPOUSE'S EMPLOYER NAME [22P] ^ ==>(#.23) SSN VERIFICATION STATUS [23P] ^ (#.24) REASON ==>FOR NO SSN [24S] ^ ^AUPNPAT(D0,3)= (#.31) PRINTABLE NAME [1F] ^ ^AUPNPAT(D0,11)= ^ ^ ^ ^ (#1105) BIRTH CERTIFICATE NO. [5F] ^ ^ ^ ==>(#1108) TRIBE OF MEMBERSHIP [8P] ^ (#1109) TRIBE ==>QUANTUM [9F] ^ (#1110) INDIAN BLOOD QUANTUM [10F] ^ ==>(#1111) CLASSIFICATION/BENEFICIARY [11P] ^ (#1112) ==>ELIGIBILITY STATUS [12S] ^ ^ (#1114) UNDERLYING CAUSE ==>OF DEATH [14P] ^ (#1115) STATE OF DEATH [15P] ^ ==>(#1116) DEATH CERTIFICATE NO. [16F] ^ ^ (#1118) ==>CURRENT COMMUNITY [18F] ^ (#1119) TRIBE MEMBERSHIP ==>VERIFIED FLAG [19S] ^ ^ (#1121) RESIDENCE VERIFIED ==>FLAG [21S] ^ (#1122) PREV HSDA RES (VER) FLAG [22S] ^ ==>(#1123) DATE ELIGIBILITY DETERMINED [23D] ^ (#1124) ==>BIC ELIGIBILITY STATUS [24P] ^ (#1125) ELIGIBILE MINOR ==>CHILD [25S] ^ (#1126) BIC PRINTED FLAG [26S] ^ (#1127) ==>PRE-BIC TRIBE [27P] ^ ^AUPNPAT(D0,12,0)=^9000001.12^^ (#1201) LOCATION OF HOME ^AUPNPAT(D0,12,D1,0)= (#.01) LOCATION OF HOME [1W] ^ ^AUPNPAT(D0,13,0)=^9000001.13^^ (#1301) ADDITIONAL REGISTRATION INFO ^AUPNPAT(D0,13,D1,0)= (#.01) ADDITIONAL REGISTRATION INFO [1W] ^ ^AUPNPAT(D0,14,0)=^9000001.14^^ (#1401) REMARKS ^AUPNPAT(D0,14,D1,0)= (#.01) REMARKS [1W] ^ ^AUPNPAT(D0,15,0)=^9000001.15^^ (#1501) ALERTS ^AUPNPAT(D0,15,D1,0)= (#.01) ALERTS [1W] ^ ^AUPNPAT(D0,26)= ^ (#2602) FATHER'S CITY OF BIRTH [2F] ^ (#2603) ==>FATHER'S STATE OF BIRTH [3P] ^ ^ (#2605) MOTHER'S ==>CITY OF BIRTH [5F] ^ (#2606) MOTHER'S STATE OF BIRTH ==>[6P] ^ ^AUPNPAT(D0,28)= ^ (#2802) NOK RELATIONSHIP [2P] ^ ^AUPNPAT(D0,31)= ^ (#3102) EC RELATIONSHIP [2P] ^ ^AUPNPAT(D0,41,0)=^9000001.41IP^^ (#4101) HEALTH RECORD NO. ^AUPNPAT(D0,41,D1,0)= (#.01) HEALTH RECORD FAC [1P] ^ (#.02) HEALTH ==>RECORD NO. [2F] ^ (#.03) DATE INACTIVATED/DELETED ==>[3D] ^ (#.04) RECORD DISPOSITION [4P] ^ (#.05) ==>RECORD STATUS [5S] ^ (#.06) STOP INTEGRATION [6S] ==>^ ^AUPNPAT(D0,43,0)=^9000001.43P^^ (#4301) OTHER TRIBE ^AUPNPAT(D0,43,D1,0)= (#.01) OTHER TRIBE [1P] ^ (#.02) QUANTUM [2F] ^ ^AUPNPAT(D0,51,0)=^9000001.51D^^ (#5101) PREVIOUS COMMUNITY ^AUPNPAT(D0,51,D1,0)= (#.01) DATE MOVED [1D] ^ (#.02) DATE ADDED TO ==>FILE [2D] ^ (#.03) COMMUNITY OF RESIDENCE [3P] ^ ^AUPNPAT(D0,61,0)=^9000001.61P^^ (#6101) MFI SITE ^AUPNPAT(D0,61,D1,0)= (#.01) MFI SITE [1P] ^ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ The following is a standard list file attributes for the Health Record multiple BEFORE VA changes: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ STANDARD DATA DICTIONARY #9000001.41 -- HEALTH RECORD NO. SUB-FILE 05/26 /94 PAGE 1 STORED IN ^AUPNPAT( (1 ENTRY) SITE: SALT LAKE CITY UCI: PCC,PCC DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE ------------------------------------------------------------------------- IDENTIFIED BY: HEALTH RECORD NO. (#.02) 9000001.41,.01HEALTH RECORD FAC 0;1 POINTER TO LOCATION FILE (#99999 99.06) INPUT TRANSFORM: S DINUM=X LAST EDITED: MAR 7, 1991 HELP-PROMPT: ENTER NAME OF FACILITY ASSOCIATED WITH THE HEALTH RECORD NUMBER YOU WISH TO ENTER. DESCRIPTION: This field is a pointer to the FACILITY file. The internal pointer is forced into the third subscript for the 9000001.41 subfile. This allows easy lookup by health record number for the logged on facility. The complete subscript for 9000001.41 will be (DFN,41,facility pointer,0). SOURCE OF DATA: 015/HRSUBR NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMME 9000001.41,.02HEALTH RECORD NO. 0;2 FREE TEXT (Required) INPUT TRANSFORM: K:(X'?1.9N&(X'?1"T"5N))!(X?1.9N&(X'=+X)) X LAST EDITED: APR 6, 1994 HELP-PROMPT: ENTER A WHOLE NUMBER BETWEEN 1 AND 999999 SOURCE OF DATA: 015/HRNUMB NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMME CROSS-REFERENCE: 9000001^D 1)= S ^AUPNPAT("D",$E(X,1,30),DA(1),DA)=" " 2)= K ^AUPNPAT("D",$E(X,1,30),DA(1),DA) 9000001.41,.0299TERMINAL DIGITS ; COMPUTED MUMPS CODE: X ^DD(9000001.41,.0299,9.4) S X=$E(Y(9000 001.41,.0299,5),Y(9000001.41,.0299,6),X) S Y=+X,X=Y(9000001.41,.0299,4),X=X_Y 9.2 = S Y(9000001.41,.0299,1)=$S($D(^AUPN PAT(D0,41,D1,0)):^(0),1:"") S X=$P(Y(9000 001.41,.0299,1),U,2)+1000000,Y(9000001.41 ,.0299,2)=X S X=6 9.3 = X ^DD(9000001.41,.0299,9.2) S Y(900 0001.41,.0299,3)=X S X=7,X=$E(Y(9000001.4 1,.0299,2),Y(9000001.41,.0299,3),X)_"-",Y (9000001.41,.0299,4)=X 9.4 = X ^DD(9000001.41,.0299,9.3) S X=$P( Y(9000001.41,.0299,1),U,2)+1000000,Y(9000 001.41,.0299,5)=X S X=2,Y(9000001.41,.029 9,6)=X S X=7 9.5 = X ^DD(9000001.41,.0299,9.4) S Y(900 0001.41,.0299,7)=X S X=$P(Y(9000001.41,.0 299,3),U,2)+1000000,Y(9000001.41,.0299,8) =X S X=2,Y(9000001.41,.0299,9)=X S X=5 ALGORITHM: $E(#.02+1000000,6,7)_"-"_+$E(#.02+1000000 ,2,7) LAST EDITED: JUN 23, 1986 9000001.41,.03DATE INACTIVATED/DELETED 0;3 DATE INPUT TRANSFORM: S %DT="EX" D ^%DT S X=Y K:Y<1 X 9000001.41,.04RECORD DISPOSITION 0;4 POINTER TO PATIENT RECORD DISPOS ITION FILE (#9999999.02) LAST EDITED: DEC 10, 1985 9000001.41,.05RECORD STATUS 0;5 SET 'D' FOR DELETED; 'I' FOR INACTIVATED; 'M' FOR MERGED; LAST EDITED: APR 19, 1990 HELP-PROMPT: Enter "D" if the record has been deleted. 9000001.41,.06STOP INTEGRATION 0;6 SET '0' FOR NO; '1' FOR YES; LAST EDITED: AUG 17, 1988 FILES POINTED TO FIELDS LOCATION (#9999999.06) HEALTH RECORD FAC (#.01) PATIENT RECORD DISPOSITION (#9999999.02) RECORD DISPOSITION (#.04) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING DETAILS: The Patient/IHS file is distributed in the VA via the Patient/IHS Subset package. NUMBER: 898 IA #: 898 DATE CREATED: SEP 24, 1994 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: AUPNPAT NAME: DBIA898 ORIGINAL NUMBER: 898 ID: AUPNPAT GENERAL DESCRIPTION: The PCE Patient/IHS Subset package (namespaced PXPT) requests a DBIA with the Indian Health Service to distribute the AUPNPAT routine with the PXPT package. The PXPT package will distribute it as PXPTNPAT and use ZOSF to load and save the routine as AUPNPAT. There have been no coding changes to the AUPNPAT code by the VA. This is the same version that is at Tucson VAMC running as of September 4, 1994. This routine is defined in the POST-SELECTION ACTION field of the PATIENT/IHS file distributed with the PXPT package. AUPNPAT ; IHS/OHPRD/EDE - POST SELECTION SETS FOR PATIENT LOOKUP ; 24-MAY-1993 ;;93.2;IHS PATIENT DICTIONARIES.;;JUL 01, 1993 ; ; This routine sets standard patient variables ; START ; S:$D(X) AUPNPATX=X S AUPNPAT=+Y S AUPNSEX=$P(^DPT(AUPNPAT,0),U,2),AUPNDOB=$P(^(0),U,3),AUPNDOD="" S:$D(^(.35)) AUPNDOD=$P(^(.35),U,1) S X2=AUPNDOB,X1=$S('AUPNDOD:DT,AUPNDOD:AUPNDOD,1:DT) D ^%DTC S AUPNDAYS=X K X,X1,X2 S:$D(AUPNPATX) X=AUPNPATX K %T,%Y,AUPNPATX Q ; KILL ; KILL VARIABLES SET BY THIS ROUTINE K AUPNPAT,AUPNSEX,AUPNDOB,AUPNDOD,AUPNDAYS Q The following routine (PXPTNPAT) is a PXPT version of AUPNPAT that is being distributed to the field. When the ZOSF("SAVE") is completed, the AUPNPAT routine will appear as displayed above. PXPTNPAT ; SLC/DLT - Post selection sets for Patient Lookup EXPORT ;1/22/ 94 21:03 ;;1.0V1;PCE PATIENT/IHS SUBSET (PXPT);;Sept 7, 1994 AUPNPAT ; IHS/OHPRD/EDE - POST SELECTION SETS FOR PATIENT LOOKUP ; 24-MAY-1993 ;;93.2;IHS PATIENT DICTIONARIES.;;JUL 01, 1993 ; ; This routine sets standard patient variables ; START ; S:$D(X) AUPNPATX=X S AUPNPAT=+Y S AUPNSEX=$P(^DPT(AUPNPAT,0),U,2),AUPNDOB=$P(^(0),U,3),AUPNDOD="" S:$D(^(.35)) AUPNDOD=$P(^(.35),U,1) S X2=AUPNDOB,X1=$S('AUPNDOD:DT,AUPNDOD:AUPNDOD,1:DT) D ^%DTC S AUPNDAYS=X K X,X1,X2 S:$D(AUPNPATX) X=AUPNPATX K %T,%Y,AUPNPATX Q ; KILL ; KILL VARIABLES SET BY THIS ROUTINE K AUPNPAT,AUPNSEX,AUPNDOB,AUPNDOD,AUPNDAYS Q STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING DETAILS: This DBIA agreement allows the Patient/IHS Subset to distribute the AUPNPAT routine in the VA. NUMBER: 900 IA #: 900 DATE CREATED: JUN 24, 1994 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSIVACT NAME: PSIVACT ORIGINAL NUMBER: 900 ID: PSIVACT GENERAL DESCRIPTION: Provides the subscribing package the ability to discontinue all of a patient's IV orders. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10448501 COMPONENT/ENTRY POINT: DCOR COMPONENT DESCRIPTION: Provides the subscribing package the ability to discontinue all of a patient's IV orders. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal entry number of the patient in the PATIENT file (2) for which orders are to be discontinued. The variable is not killed by this entry point. SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 901 IA #: 901 DATE CREATED: JUN 24, 1994 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSSJEEU NAME: PSSJEEU ORIGINAL NUMBER: 901 ID: PSSJEEU GENERAL DESCRIPTION: This is a set of utilities that can be used to create, validate and process order timing schedules. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10448501 COMPONENT/ENTRY POINT: ENSE COMPONENT DESCRIPTION: Allows the editing of the ADMINISTRATION SCHEDULE file (51.1). VARIABLES: PSJPP TYPE: Input VARIABLES DESCRIPTION: This is the package prefix as found in the PACKAGE file (9.4). VARIABLES: PSJSHLS TYPE: Input VARIABLES DESCRIPTION: This is executable code that sets $T to be used to screen Hospital Locations when editing schedules and shifts. If PSJSHLS exists, DIC("S") is set to PSJSHLS. The scheduler will not try to validate PSJSHLS. COMPONENT/ENTRY POINT: ENSHE COMPONENT DESCRIPTION: Allows the editing of the ADMINISTRATION SHIFT file (51.15). VARIABLES: PSJPP TYPE: Input VARIABLES DESCRIPTION: This is the package prefix as found in the PACKAGE file (9.4). VARIABLES: PSJSHLS TYPE: Input VARIABLES DESCRIPTION: This is executable code that sets $T to be used to screen Hospital Locations when editing schedules and shifts. If PSJSHLS exists, DIC("S") is set to PSJSHLS. The scheduler will not try to validate PSJSHLS. COMPONENT/ENTRY POINT: ENSVI COMPONENT DESCRIPTION: View standard schedule information. VARIABLES: PSJPP TYPE: Input VARIABLES DESCRIPTION: This is the package prefix as found in the PACKAGE file (9.4). VARIABLES: PSJX TYPE: Input VARIABLES DESCRIPTION: This is the schdule to be viewed. If only the first few characters of the schedule name is entered, the user will be asked to select from all schedules in the ADMINISTRATION SCHEDULE file (51.1) beginning with these characters. If a valid schedule is selected, information pertaining to the schedule will be displayed. COMPONENT/ENTRY POINT: ENSV COMPONENT DESCRIPTION: Validates a schedule and gives the administration times or shifts and frequency (in minutes) of the schedule. VARIABLES: PSJX TYPE: Both VARIABLES DESCRIPTION: This is the schdule to be validated. If only the first few characters of the schedule name is entered, the user will be asked to select from all schedules in the ADMINISTRATION SCHEDULE file (51.1) beginning with these characters. If a valid schedule is selected, it's name will will be returned in PSJX. If a valid schedule is not selected, PSJX will be killed. VARIABLES: PSJPP TYPE: Input VARIABLES DESCRIPTION: This is the package prefix as found in the PACKAGE file (9.4). VARIABLES: PSJM TYPE: Output VARIABLES DESCRIPTION: This is the frequency in minutes that the action is to be taken. This will be null if PSGX is invalid. VARIABLES: PSJAT TYPE: Output VARIABLES DESCRIPTION: These are the administration times or shifts that are associated with the selected schedule. This will be null if PSGX is invalid. VARIABLES: PSJY TYPE: Output VARIABLES DESCRIPTION: This is a pointer to the ADMINISTRATION SCHEDULE file (51.1) if PSJX is found in the file. This will be null if PSJX is invalid or not found. VARIABLES: PSJTS TYPE: Output VARIABLES DESCRIPTION: This is a code representing the type of schedule. This will be null if the schedule is invalid. VARIABLES: PSJAX TYPE: Output VARIABLES DESCRIPTION: This is the maximum days continuous orders last for the selected schedule, or null if not found. VARIABLES: PSJW TYPE: Input VARIABLES DESCRIPTION: This is a pointer to the HOSPITAL LOCATION file (44). This is an optional variable that may be used to determine the administration times or shifts by location. VARIABLES: PSJNE TYPE: Input VARIABLES DESCRIPTION: If this optional variable is defined, there is no dialogue with the user. COMPONENT/ENTRY POINT: ENATV COMPONENT DESCRIPTION: Validates administration times. This may be used in an input transform. VARIABLES: X TYPE: Both VARIABLES DESCRIPTION: This contains the administration times to be validated. X will be killed if the administration times are invalid. COMPONENT/ENTRY POINT: ENSHV COMPONENT DESCRIPTION: Validates shifts. If the shift passed in X is invalid X will be killed. VARIABLES: X TYPE: Both VARIABLES DESCRIPTION: This should be set to the administration shift to be validated. If the administration shift passed in X is invalid, X will be killed. COMPONENT/ENTRY POINT: ENSPU COMPONENT DESCRIPTION: Calculates the number of times (and when) an action is to take place. VARIABLES: PSJSCH TYPE: Input VARIABLES DESCRIPTION: This is the schedule to be processed. VARIABLES: PSJM TYPE: Input VARIABLES DESCRIPTION: This is the frequency (in minutes) that an action is to take place. Used for continuous and range schedules. VARIABLES: PSJAT TYPE: Input VARIABLES DESCRIPTION: This is either a set of administration times or shifts, depending on the type of schedule. If it is administration times, it will be similar to: PSJAT="04-08-12-16-20". If it is shifts, it will be similar to: PSJAT="M-E",PSJAT("M")="05-11",PSJAT("E")="18-22". VARIABLES: PSJTS TYPE: Input VARIABLES DESCRIPTION: This is a code representing the type of schedule defined in PSJSCH. The codes are: C - CONTINUE; D - DAY OF THE WEEK; DR - DAY OF THE WEEK-RANGE; O - ONE-TIME; R - RANGE; and S - SHIFT. VARIABLES: PSJSD TYPE: Input VARIABLES DESCRIPTION: This is the start date/time of the order. VARIABLES: PSJFD TYPE: Input VARIABLES DESCRIPTION: This is the stop date/time of the period where the action is to take place. VARIABLES: PSJOSD TYPE: Input VARIABLES DESCRIPTION: This is the start date/time of the order. If PSJOSD is not found, PSJSD is used. VARIABLES: PSJOFD TYPE: Input VARIABLES DESCRIPTION: This is the stop date/time of the order (action to take place). If PSJOFD is not found, PSJFD is used. VARIABLES: PSJC TYPE: Output VARIABLES DESCRIPTION: This is the number of times (and when) an action is to take place. COMPONENT/ENTRY POINT: ENDSD COMPONENT DESCRIPTION: Provides a date/time that might be used as a default value for the start date of an order. VARIABLES: PSJSCH TYPE: Input VARIABLES DESCRIPTION: This is the name of the schedule to be used in determining the start date/time. VARIABLES: PSJAT TYPE: Input VARIABLES DESCRIPTION: This is either a set of administration times or shifts, depending on the type of schedule. If it is administration times, it will be similar to: PSJAT="04-08-12-16-20". If it is shifts, it will be similar to: PSJAT="M-E",PSJAT("M")="05-11",PSJAT("E")="18-22". VARIABLES: PSJTS TYPE: Input VARIABLES DESCRIPTION: This is a code representing the type of schedule defined in PSJSCH. The codes are: C - CONTINUE; D - DAY OF THE WEEK; DR - DAY OF THE WEEK-RANGE; O - ONE-TIME; R - RANGE; and S - SHIFT. VARIABLES: PSJX TYPE: Output VARIABLES DESCRIPTION: This will be returned as either a date/time in VA FileMan interal format, or null if the start date/time cannot be calculated. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 902 IA #: 902 DATE CREATED: JUN 24, 1994 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJSV0 NAME: PSJSV0 ORIGINAL NUMBER: 902 ID: PSJSV0 GENERAL DESCRIPTION: This displays help text for use when validating a schedule. This may be used as the executable help for a field. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10448501 COMPONENT/ENTRY POINT: ENSVH COMPONENT DESCRIPTION: Help text for use when validating a schedule. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Set to 1 or more "?" for help. This is supplied by VA FileMan if used as executable help. NUMBER: 905 IA #: 905 FILE NUMBER: 120.8 GLOBAL ROOT: GMR(120.8, DATE CREATED: JUL 07, 1994 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED ROUTINE: ?" NAME: DBIA905 ORIGINAL NUMBER: 905 ID: ?" GLOBAL REFERENCE: GMR(120.8,D0,0) FIELD NUMBER: 6 FIELD NAME: OBSERVED/HISTORICAL LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: ORIGINATION DATE/TIME LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5 FIELD NAME: ORIGINATOR LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 26 FIELD NAME: COMMENTS LOCATION: 26;0 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is a multiple. Health Summary will use the .01 field under subfile 120.8262, field number 2, location 2;0. FIELD NUMBER: ACCESS: Read w/Fileman FIELD NUMBER: 19 FIELD NAME: VERIFIED LOCATION: 0;16 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 21 FIELD NAME: VERIFIER LOCATION: 0;18 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: REACTANT LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 3.1 FIELD NAME: ALLERGY TYPE LOCATION: 0;20 ACCESS: Read w/Fileman FIELD NUMBER: 20 FIELD NAME: VERIFICATION DATE/TIME LOCATION: 0;17 ACCESS: Read w/Fileman FIELD NUMBER: 15 FIELD NAME: ORIGINATOR SIGN OFF LOCATION: 0;12 ACCESS: Read w/Fileman GLOBAL REFERENCE: GMR(120.8,D0,26,D1,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME COMMENT ENTERED LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: USER ENTERING LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 1.5 FIELD NAME: COMMENT TYPE LOCATION: 0;3 ACCESS: Read w/Fileman GLOBAL REFERENCE: GMR(120.8,D0,26,D1,2,D2,0) FIELD NUMBER: .01 FIELD NAME: COMMENTS LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: GMR(120.8,"AODT", GLOBAL DESCRIPTION: This x-ref may be used in a direct global read. GLOBAL REFERENCE: GMR(120.8,"API", GLOBAL DESCRIPTION: Direct global read access approved. GLOBAL REFERENCE: GMR(120.8,"APC", GLOBAL DESCRIPTION: Direct global read access approved. GENERAL DESCRIPTION: This DBIA grants access to specific fields in the PATIENT ALLERGIES FILE (120.8). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 35874939 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: Health Summary routine GMTSALG requires access to several fields in PATIENT ALLERGIES FILE #120.8 that are not available from the allergy API's contained in ^GMRADPT. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: OE/RR requires access to several fields in the PATIENT ALLERGIES FILE #120.8 that are not available from the allergy API's contained in ^GMRADPT. DIQ API calls are used to get the data. SUBSCRIBING PACKAGE: NATIONAL DRUG FILE SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING DETAILS: added Feb 29 2008 DATE/TIME EDITED: FEB 29, 2008@11:52 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: REDINGTON,PATRICK WITH CONCURRENCE OF: NABER,DAVID NUMBER: 907 IA #: 907 DATE CREATED: JUL 13, 1994 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: AUPNVSIT NAME: AUPNVSIT ORIGINAL NUMBER: 907 ID: AUPNVSIT GENERAL DESCRIPTION: Update dependent entry counter ------------------------------ Note: These calls are customarily done via a MUMPS cross reference on the pointer field. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11103069 COMPONENT/ENTRY POINT: ADD COMPONENT DESCRIPTION: Increase the dependent entry count by one. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: "X" equals the Internal Entry Number of the Visit. COMPONENT/ENTRY POINT: SUB COMPONENT DESCRIPTION: Decrease the dependent entry count by one. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: "X" equals the Internal Entry Number of the Visit. SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT SUBSCRIBING DETAILS: ADDED 10/10/2008 DATE/TIME EDITED: OCT 10, 2008@14:55 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: ELLIS,DONNA NUMBER: 909 IA #: 909 FILE NUMBER: 45.7 GLOBAL ROOT: DIC(45.7, DATE CREATED: JUL 14, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA909-A ORIGINAL NUMBER: 909 ID: DIC(45.7, GLOBAL REFERENCE: DIC(45.7,N,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Retrieve Facility Treating Specialty Name GENERAL DESCRIPTION: The laboratory LMIP reports require that workload data be collected based on Facility Treating Specialty #45.7 and Specialty #42.4. We determine this information by looking at the ordering location. We are asking permission to read the these files to obtain .01 field and the field #6 CDR ACCOUNT field for certain reports. The logic uses the ^SC(X,42) to determine if the location is a ward. If it is the n use the Facility Treating specialty pointers to navigate to the data. See DBIA909-B & DBIA909-C STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11246997 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 913 IA #: 913 FILE NUMBER: 21 GLOBAL ROOT: DIC(21 DATE CREATED: JUL 22, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA913 ORIGINAL NUMBER: 913 ID: DIC(21 GLOBAL REFERENCE: DIC(21, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11280545 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE NUMBER: 915 IA #: 915 DATE CREATED: AUG 11, 1994 CUSTODIAL PACKAGE: SOCIAL WORK CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SOWKHSUM NAME: DBIA915 ID: SOWKHSUM GENERAL DESCRIPTION: Health Summary requests the ability to execute the ^SOWKHSUM routine. Health Summary will have a patient DFN defined as the variable DFN upon calling ^SOWKHSUM. ^SOWKHSUM will output the ^TMP("SOWK",$J,line number) array which will include the Source of Referral, Source of Information, the Social/Family Relationship segment, The Current Substance Problems segment and the Psycho-Social Assessment segment. These segments will be formated like their display in the Social Work Service Reports with the exception that they will not be prefaced with a Roman Numeral. Health Summary will export this routine in the GMTS name space and if it doesn't exist when Health Summary is installed, the routine will be renamed to the SOWK name space. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11570639 COMPONENT/ENTRY POINT: SOWKHSUM VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient DFN from the patient file. VARIABLES: TMP("SOWK",$J,Line #) TYPE: Output VARIABLES DESCRIPTION: The global array ^TMP("SOWK",$J,Line #) will return the formated Social Work Service Data. SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 916 IA #: 916 GLOBAL ROOT: DIC( DATE CREATED: JUL 25, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA916 ORIGINAL NUMBER: 916 ID: DIC( GLOBAL REFERENCE: DIC(FILE_NO.,0,"GL") FIELD NUMBER: 1 FIELD NAME: GLOBAL NAME ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: A direct global read is performed on this node to determine the global root for a file. GENERAL DESCRIPTION: The current packages subscribing to this IA are expected to migrate to use DID calls. NO NEW FUTURE SUBSCRIBERS WILL BE ADDED. STATUS: Active MAIL MESSAGE: 18110501 GOOD ONLY FOR VERSION: Fileman 20 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING DETAILS: For duration of Lab Version 5.2: Blood Bank and Anatomic Pathology namespaced routines refer to ^DIC(FILE_NO.,0,"GL") to locate global nodes for data. SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany SUBSCRIBING DETAILS: IVM stores a pointer to the FILE (#1) file in order to reference multiple files for storing data. We are requesting permission to make a direct reference to ^DIC(FILE_NO.,0,"GL") to find the global root for that file. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING DETAILS: Nursing is granted READ access to ^DIC(file_number,0,"GL") in order to get the global root of a file. File_number is in the nursing package namespace. SUBSCRIBING PACKAGE: LEXICON UTILITY ISC: Salt Lake City SUBSCRIBING DETAILS: Read only access for ^DIC(FN,0,"GL"), where FN is a file number, to verify the value of DIC prior to initiating the lookup (GMPTA4). SUBSCRIBING PACKAGE: POLICE & SECURITY ISC: Dallas SUBSCRIBING DETAILS: DICRW+5^ESPFM, the reference to ^DIC(+Y,0,"GL") SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: Read only access for ^DIC(FN,0,"GL"), where FN is a file number, to determine the global root for a file. NUMBER: 918 IA #: 918 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: JUL 26, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA918 ORIGINAL NUMBER: 918 ID: DPT( GLOBAL REFERENCE: DPT( FIELD NUMBER: .525 FIELD NAME: POW STATUS INDICATED LOCATION: .52;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .526 FIELD NAME: POW CONFINEMENT LOCATION LOCATION: .52;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: FIELD NUMBER: .323 FIELD NAME: PERIOD OF SERVICE LOCATION: .32;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .32201 FIELD NAME: PERSIAN GULF SERVICE LOCATION: .322;10 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Read only access for the ^DPT( global to obtain Period of Service and POW information. Read ^DPT(dfn,.52) to obtain POW information. Read ^DPT(dfn,.32) to obtain Period of Service information. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11322567 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 921 IA #: 921 FILE NUMBER: 52.6 GLOBAL ROOT: PS(52.6, DATE CREATED: JUL 27, 1994 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA921 ORIGINAL NUMBER: 921 ID: PS(52.6, GLOBAL REFERENCE: PS(52.6,x,0) FIELD NUMBER: .01 FIELD NAME: PRINT NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. Read only access for the ^PS(52.6,X,0) node. In routines LRBLPE1 and LRBLPH: ...I $D(^PS(52.6,X,0)...W !,"IV DRUG: ",$P(^(0),"^") STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 923 IA #: 923 FILE NUMBER: 40.7 GLOBAL ROOT: DIC(40.7 DATE CREATED: JUL 28, 1994 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA923 ORIGINAL NUMBER: 923 ID: DIC(40.7 GENERAL DESCRIPTION: The following fields are accessed in a read-only manner: ^DIC( 40.7 STOP CODE file 1 AMIS REPORTING STOP CODE In routines LRCAPPH line LRCAPPH+8 SDC S SDC=$S($P(^("NITE"),U,3):$G(^DIC(40.7,+$P(^LAB(69.9,1,"NITE"), U,3),0)),1:"") S LRSDC=$S($P(SDC,U,2):+$P(SDC,U,2),1:108) LRSTOPC line LRSTOPC+3 S LRSDC=$S(+$P($G(^DIC(40.7,+$P($G(^LAB(69.9,1,"NITE")),U,3),0)),U,2): $P(^(0),U,2),1:108),CNT=0,LREND=0 Routine LRSTOPC manually records clinic stop codes for Lab. Routine LRCAPPH automatically records clinic stop codes for Lab. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 924 IA #: 924 FILE NUMBER: 11 GLOBAL ROOT: DIC(11, DATE CREATED: JUL 28, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA924 ORIGINAL NUMBER: 924 ID: DIC(11, CREATOR: KOPP,TERRY M GLOBAL REFERENCE: DIC(11,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: ABBREVIATION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Read only access for the ^DIC(11, global. In routine LRMIHDR line LRMIHDR+22: I LRMARST S LRMARST=$S($D(^DIC(11,LRMARST,0)):$P(^(0),U),1:"") LAB SERVICE will also use MARITAL STATUS fields in Fileman sort and print templates. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 52753904 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas DATE ACTIVATED: SEP 01, 2010 DATE/TIME EDITED: SEP 01, 2010@07:00 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: KOPP,TERRY DATE/TIME EDITED: SEP 01, 2010@09:41 ACTION: APPROVED AT THE REQUEST OF: KOPP,TERRY NUMBER: 925 IA #: 925 FILE NUMBER: 10 GLOBAL ROOT: DIC(10, DATE CREATED: JUL 28, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA925 ORIGINAL NUMBER: 925 ID: DIC(10, CREATOR: KOPP,TERRY M GLOBAL REFERENCE: DIC(10,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: HL7 VALUE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DIC(10,D0,.02) FIELD NUMBER: 200 FIELD NAME: INACTIVE LOCATION: .02;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Read only access to the ^DIC(10, global. In routine LRMIHDR line LRMIHDR+21: I LRRACE S LRRACE=$S($D(^DIC(10,LRRACE,0)):$P(^(0),U),1:"") LAB SERVICE will use the NAME (#.01), HL7 VALUE (#3) and INACTIVE (#200) fields in sort and print templates. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 52754335 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas DATE ACTIVATED: SEP 02, 2010 DATE/TIME EDITED: SEP 01, 2010@07:00 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: KOPP,TERRY DATE/TIME EDITED: SEP 02, 2010@08:30 ACTION: APPROVED AT THE REQUEST OF: KOPP,TERRY NUMBER: 927 IA #: 927 FILE NUMBER: 130 GLOBAL ROOT: SRF( DATE CREATED: AUG 01, 1994 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: LIST SURGICAL OPERATIONS SCHEDULED ORIGINAL NUMBER: 927 ID: SRF( CREATOR: MONTALI,MICHAEL GLOBAL REFERENCE: SRF('ADT',dfn,x,a) FIELD NUMBER: .09 FIELD NAME: DATE OF OPERATION LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Loop through this cross-reference to list operations scheduled. GLOBAL REFERENCE: SRF(DO,'OP') GLOBAL DESCRIPTION: Direct Read Access to print operation procedure and code. GENERAL DESCRIPTION: Read only access for the ^SRF global. Routine LRBLPCSS, blood bank routine, pre-op component selection, checks for pending operations by looping through the "ADT" Date of Operation cross reference then lists operations scheduled. The date, operation procedure, and planned principal procedure code is listed. STATUS: Active DURATION: Till Otherwise Agreed KEYWORDS: SURGERY KEYWORDS: OPERATION SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas DBA Comments: JSHARVEY/ 20070304 - RESEARCHED FROM OLD ENTRIES. APPROVED TO ACTIVATE. BACKDATED THE APPROVAL STATUS TO AVOID CONFUSION. DATE ACTIVATED: AUG 01, 1994 DATE/TIME EDITED: MAR 05, 2007@16:36 ACTION: CONTENT CORRECTED AT THE REQUEST OF: MONTALI,MIKE WITH CONCURRENCE OF: MONOSKY,ALAN DATE/TIME EDITED: MAR 05, 2007@16:39 ACTION: APPROVED AT THE REQUEST OF: MONTALI,MIKE WITH CONCURRENCE OF: MONOSKY,ALAN NUMBER: 928 IA #: 928 DATE CREATED: AUG 02, 1994 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMPLUTL NAME: DBIA928 ORIGINAL NUMBER: 928 ID: GMPLUTL CREATOR: CHUNG,TERESA L GENERAL DESCRIPTION: This agreement is to post the routine GMPLUTL as a supported reference by controlled subscription. There are 3 entry points to return currently active problems, add a new problem, or update an existing problem. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34250201 KEYWORDS: GMPLUTL KEYWORDS: ACTIVE KEYWORDS: CREATE KEYWORDS: UPDATE KEYWORDS: MAGDHLS COMPONENT/ENTRY POINT: ACTIVE(DFN,.PROBLEM) COMPONENT DESCRIPTION: This entry point will return the specified patient's currently active problems. Two parameters are required to be passed in, the first being the IEN of the patient in file #2, and the second is the array (passed by reference) in which the problems will be returned. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of patient in file #2 VARIABLES: PROBLEM TYPE: Output VARIABLES DESCRIPTION: Array which must be passed in by reference; returned with the following set: PROBLEM(0) = Total number of problems returned PROBLEM(#,0) = Problem file IEN PROBLEM(#,1) = internal^external values of problem description in the Lexicon Utility; note that external value may be a provider modification of the Lexicon Utility's text PROBLEM(#,2) = internal^external values of assigned ICD Diagnosis code PROBLEM(#,3) = internal^external values of Date of Onset PROBLEM(#,4) = abbreviated^full text of SC indicator, i.e. SC^SERVICE- CONNECTED, NSC^NOT SERVICE- CONNECTED, or null PROBLEM(#,5) = abbreviated^full text of Exposure indicator, i.e. AO^AGENT ORANGE, IR^RADIATION, EC^ENV CONTAMINANTS, HNC^HEAD AND/OR NECK CANCER, MST^MILITARY SEXUAL TRAUMA or null where each # is a sequence number per problem to group the data elements. COMPONENT/ENTRY POINT: CREATE(.PROBLEM,.RESULT) COMPONENT DESCRIPTION: This entry point will create a new problem entry based upon the values passed in the PROBLEM array. The RESULT array will be used to return the results of the call; if successful, RESULT will contain the new IEN, otherwise it will be set to -1 and RESULT(0) will contain an error message. VARIABLES: PROBLEM TYPE: Input VARIABLES DESCRIPTION: This array must be passed in by reference containing the following data elements to create a new problem entry: REQUIRED: PROBLEM("PATIENT") = IEN of patient in file #2 PROBLEM("NARRATIVE") = Text of the problem, as described by provider PROBLEM("PROVIDER") = IEN of provider in file #200 OPTIONAL: PROBLEM("DIAGNOSIS") = IEN of ICD Diagnosis code in file #80 PROBLEM("LEXICON") = IEN of problem description in the Lexicon Utility PROBLEM("STATUS") = Status of problem, either A (active) or I (inactive); problem is assumed to be active if not specified PROBLEM("ONSET") = Date of onset, in internal FileMan format PROBLEM("RECORDED") = Date problem was recorded, in internal FileMan format PROBLEM("RESOLVED") = Date problem was resolved, in internal FileMan format PROBLEM("COMMENT") = Up to 60 characters of additional text PROBLEM("LOCATION") = IEN of Hospital Location (clinic) in file #44 PROBLEM("SC") = 1 or 0, if problem is related to SC condition PROBLEM("AO") = 1 or 0, if problem is related to Agent Orange exp. PROBLEM("IR") = 1 or 0, if problem is related to Radiation exp. PROBLEM("EC") = 1 or 0, if problem is related to Environmental Contaminants (i.e. Persian Gulf) PROBLEM("HNC") = 1 or 0, if problem is related to Head and/or Neck Cancer PROBLEM("MST") = 1 or 0, if problem is related to Military Sexual Trauma PROBLEM("CV") = 1 or 0, if problem is related to Combat Veteran status PROBLEM("SHD") = 1 or 0, if problem is related to Shipboard Hazard and Defense (SHAD) PROBLEM("DX_DATE_OF_INTEREST") = Date of the patient's encounter or current date if historical encounter or if none defined. VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: Array which must be passed in by reference; returned with the following set: RESULT = IEN of new problem entry in Problem file #9000011, or -1 if unsuccessful RESULT(0) = Error message if unsuccessful, otherwise null VARIABLES: DUZ TYPE: Used VARIABLES DESCRIPTION: The values in the DUZ array are referenced in this routine; if tasked, the variables DUZ, DUZ(2), and DUZ("AG") must be set into the ZTSAVE array. VARIABLES: OUTPUT COMPONENT/ENTRY POINT: UPDATE(.PROBLEM,.RESULT) COMPONENT DESCRIPTION: This entry point will update an existing problem based upon the values passed in the PROBLEM array. The RESULT array will be used to return the results of the call; if successful, RESULT will equal the IEN of the problem, otherwise it will be set to -1 and RESULT(0) will contain an error message. VARIABLES: PROBLEM TYPE: Input VARIABLES DESCRIPTION: This array must be passed in by reference containing the following data elements to update an existing problem; only the items to be changed need to be set, as a null value will be assumed to mean "no change" and "@" to delete the current value: REQUIRED: PROBLEM("PROBLEM") = IEN of problem in file #9000011 PROBLEM("PROVIDER") = IEN of provider in file #200 OPTIONAL: PROBLEM("NARRATIVE") = Text of the problem, as described by provider PROBLEM("DIAGNOSIS") = IEN of ICD Diagnosis code in file #80 PROBLEM("LEXICON") = IEN of problem description in the Lexicon Utility PROBLEM("STATUS") = Status of problem, either A (active) or I (inactive) PROBLEM("ONSET") = Date of onset, in internal FileMan format PROBLEM("RECORDED") = Date problem was recorded, in internal FileMan format PROBLEM("RESOLVED") = Date problem was resolved, in internal FileMan format PROBLEM("COMMENT") = Up to 60 characters of additional text PROBLEM("LOCATION") = IEN of Hospital Location (clinic) in file #44 PROBLEM("SC") = 1 or 0, if problem is related to SC condition PROBLEM("AO") = 1 or 0, if problem is related to Agent Orange exp. PROBLEM("IR") = 1 or 0, if problem is related to Radiation exp. PROBLEM("EC") = 1 or 0, if problem is related to Environmental Contaminants (i.e. Persian Gulf) PROBLEM("HNC") = 1 or 0, if problem is related to Head and/or Neck Cancer PROBLEM("MST") = 1 or 0, if problem is related to Military Sexual Trauma PROBLEM("CV") = 1 or 0, if problem is related to Combat Veteran status PROBLEM("SHD") = 1 or 0, if problem is related to Shipboard Hazard and Defense (SHAD) PROBLEM("DX_DATE_OF_INTEREST") = Date of the patient's encounter or current date if historical encounter or if none defined. PROBLEM("SCTC") = SNOMED CT Concept Code PROBLEM("SCTD") = SNOMED CT Designation Code PROBLEM("CODEDT") = Date of interest for the primary ICD Diagnosis PROBLEM("CODESYS") = Coding system of the primary ICD Diagnosis VARIABLES: DUZ TYPE: Used VARIABLES DESCRIPTION: The values in the DUZ array are referenced in this routine; if tasked, the variables DUZ, DUZ(2), and DUZ("AG") must be set into the ZTSAVE array. SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI SUBSCRIBING PACKAGE: ONCOLOGY SUBSCRIBING PACKAGE: IMAGING DBA Comments: 2/4/12 DT: Change was requested to handle historical encounter creation of Problem List diagnosis. Developers indicated no other subscibers will be affected besides PCE. This change is to support the ICD10 Remediation effort. 3/7/13-MM: ICR was deactivated for edits on 2/4/13 but the status was not changed from active to Under Revision. Status updated to Under Revision. 3/21/13 DT: Activated ICR which will be in effect with OR*3*361, planned for release in Q2 or Q3 2013. 7/16/13-MC: Deactivated for edits. Vista Imaging Patch MAG*3.0*141. 7/16/13-MC: Activated after edits completed by Gregory Cebelinski for Vista Imaging patch MAG*3.0*141. Problem List developers Teresa Chung and Joel Russell approved change. 2/12/14 MM: Opened ICR for editing. GMPL*2*42 is adding new subscripts to the PROBLEM input parameter. It will be used with CPRS V30. Teresa provided concurrence for CPRS and obtained concurrence from PCE, Imaging and DSSI. Discussions with Clinical Case Registries, TIU and Oncology contacts in January 2013 indicated these applications do not use the UPDATE component. 6/3/14 DT: Teresa added the following optional use fields in the UPDATE component: PROBLEM("SCTC") = SNOMED CT Concept Code PROBLEM("SCTD") = SNOMED CT Designation Code PROBLEM("CODEDT") = Date of interest for the primary ICD Diagnosis PROBLEM("CODESYS") = Coding system of the primary ICD Diagnosis Teresa confirmed the current subscribers will not be impacted. Approved 6/13/14 for use with GMPL*2*42 v15. DATE ACTIVATED: JUN 03, 2014 DATE/TIME EDITED: FEB 04, 2013@15:05 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CHUNG,TERESA WITH CONCURRENCE OF: DAVIS,ROBERT DATE/TIME EDITED: MAR 07, 2013@13:38 ACTION: CONTENT CORRECTED DATE/TIME EDITED: MAR 22, 2013@11:51 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CEBELINSKI,GREGORY WITH CONCURRENCE OF: CHUNG,TERESA DATE/TIME EDITED: JUL 16, 2013@15:35 ACTION: APPROVED AT THE REQUEST OF: CEBELINSKI,GREGORY WITH CONCURRENCE OF: CHUNG,TERESA DATE/TIME EDITED: JUL 16, 2013@15:37 ACTION: APPROVED DATE/TIME EDITED: FEB 12, 2014@17:06 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CHUNG,TERESA WITH CONCURRENCE OF: CHUNG,TERESA DATE/TIME EDITED: JUN 03, 2014@15:27 ACTION: APPROVED AT THE REQUEST OF: CHUNG,TERESA WITH CONCURRENCE OF: CHUNG,TERESA NUMBER: 930 IA #: 930 FILE NUMBER: 9.4 DATE CREATED: SEP 20, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA930 GENERAL DESCRIPTION: The Laboratory package requests agreement from the VA FileMan package to edit the Package file (9.4) during the init process for Laboratory Version 5.2. There are two sets of inits distributed with Lab V 5.2. The LR inits are the primary inits for the release. The LA inits are for the Automated Instruments part of the release. The LA inits are only run when the site is installing this version in a virgin account. There are directions in the installation guide telling the site NOT to run the inits if they overlaying version 5.2 over version 5.1. The Package file entry for Automated Instruments needs to be updated to version 5.2, but because the inits are not run, the Package file will not get updated. We request permission to use ^DIE and ^DICN to update the following fields in the AUTOMATED LAB INSTRUMENTS entry in the PACKAGE file. VERSION (field #22, add a multiple entry) VERSION (field #.01, sub field of #22) DATE DISTRIBUTED (field #1, sub field of #22) DATE INSTALLED AT THIS SITE (field #2, sub field of #22) CURRENT VERSION (field #13) This is a one-time request for this release of Laboratory Version 5.2. STATUS: Active DURATION: Next Version GOOD ONLY FOR VERSION: 5.2 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 932 IA #: 932 FILE NUMBER: 3.2 GLOBAL ROOT: %ZIS(2, DATE CREATED: AUG 04, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA932 ID: %ZIS(2, GLOBAL REFERENCE: %ZIS(2,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to GENERAL DESCRIPTION: Permission to define a field in one of our files as a pointer to the Terminal File. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11335508 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 933 IA #: 933 DATE CREATED: AUG 04, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: %ZISS1 NAME: DBIA933 ID: %ZISS1 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11335508 COMPONENT/ENTRY POINT: CHECK COMPONENT DESCRIPTION: Call CHECK^%ZISS1 from input transforms to check that what is being entered is a valid argument to a WRITE statement for printer control. VARIABLES: X TYPE: Both SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany DATE/TIME EDITED: OCT 23, 2006@16:00 ACTION: RETIRED AT THE REQUEST OF: YORTY,ROBERT WITH CONCURRENCE OF: FAIN,ZACHARY NUMBER: 934 IA #: 934 DATE CREATED: AUG 05, 1994 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOP NAME: DBIA934 ID: PSOP GENERAL DESCRIPTION: This is for Pharmacy 6.0 and greater. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: PSOP COMPONENT DESCRIPTION: This entry point(and re-entry point) is the functional Pharmacy Patient profile. This tool is used for acquisition of display only data for use in Rheumatology reports. This supersedes DBIA191-A #191. VARIABLES: PLS TYPE: Input VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal Entry Number of the patient. SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring NUMBER: 935 IA #: 935 FILE NUMBER: 22 GLOBAL ROOT: DIC(22, DATE CREATED: AUG 09, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA935 ID: DIC(22, GLOBAL REFERENCE: DIC(22 FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: GENERAL DESCRIPTION: In Lab V 5.2 patient POW information is being obtained from inquiries to global locations. Routines LRAPPOW and LRAPDPT reference the global ^DIC(22, . STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11280545 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 936 IA #: 936 DATE CREATED: AUG 11, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUSESIG NAME: XUSESIG ID: XUSESIG GENERAL DESCRIPTION: This routine, when called from the top, allows the user to setup a personal electronic signature code. It is used within application code to allow the user immediate 'on-the-fly' access to setup the electronic signature, rather than force the user to leave the application and enter a different option to do the same. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 8376934 COMPONENT/ENTRY POINT: XUSESIG SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: ADP PLANNING ISC: Birmingham SUBSCRIBING PACKAGE: ASISTS ISC: Hines NUMBER: 937 IA #: 937 GLOBAL ROOT: DIBT( DATE CREATED: AUG 12, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: SEARCH TEMPLATE RESULTS ID: DIBT( GLOBAL REFERENCE: DIBT(SORT_TEMPLATE#,1,IEN) GENERAL DESCRIPTION: ^DIBT(SORT_TEMPLATE#,1,IEN)="" The 1 node indicates that the IEN list was created one of two ways: 1) The user was in FileMan INQUIRE mode, selected a number of records, and saved the list in a template. 2) The user ran the FileMan SEARCH, either through the interactive FileMan menu, or through the programmer entry point EN^DIS. In this case, the IEN list is the record numbers that met the search criteria. IEN - is the internal entry number of a record in the file indicated by the 4th piece of the 0 node of the template, ^DIBT(SORT_TEMPLATE#,0). Read, Write, Delete access allowed. STATUS: Active MAIL MESSAGE: 13344043 NUMBER: 938 IA #: 938 DATE CREATED: AUG 16, 1994 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSDVR NAME: DBIA938 ID: GMTSDVR GENERAL DESCRIPTION: Entry points to use the Health Summary routine GMTSDVR to allow users to print a Health Summary. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 35982911 COMPONENT/ENTRY POINT: ENX COMPONENT DESCRIPTION: This entry point allows for direct printing of a Health Summary for a programmer-specified patient and device, without prompting for additional information. This entry point uses parameter passing. The format is ENX^GMTSDVR(DFN,GMTSTYP,GMTSPX2,GMTSPX1). GMTSPX2 and GMTSPX1 are optional date range variables. They allow the time limits to be overridden for components that use time limits. Thus, beginning and ending dates can be specified in order to get only data within that time range. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Passes patient id. VARIABLES: GMTSTYP TYPE: Input VARIABLES DESCRIPTION: Defines the Health Summary report to be printed. VARIABLES: GMTSPX2 TYPE: Input VARIABLES DESCRIPTION: Optional internal FileMan date for beginning date range. VARIABLES: GMTSPX1 TYPE: Input VARIABLES DESCRIPTION: Optional internal FileMan date for ending date range. COMPONENT/ENTRY POINT: ENXQ COMPONENT DESCRIPTION: This call is for Queueing the Health Summary. GMTSPX1 and GMTSPX2 are optional date range variables. Both are required if a date range is desired. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient ID. VARIABLES: GMTSTYP TYPE: Input VARIABLES DESCRIPTION: Defines Health Summary to print. VARIABLES: GMTSPX1 TYPE: Input VARIABLES DESCRIPTION: Optional internal FileMan date for ending date range. VARIABLES: GMTSPX2 TYPE: Input VARIABLES DESCRIPTION: Optional internal FileMan date for begining date range. COMPONENT/ENTRY POINT: SELTYP COMPONENT DESCRIPTION: This entry point allows for a Health Summary type to be selected from file 142. VARIABLES: GMTYP(0) TYPE: Output VARIABLES DESCRIPTION: Will be set to 1 if a type is selected and it contains components. VARIABLES: GMTYP(1) TYPE: Output VARIABLES DESCRIPTION: The 1st piece will be set to the internal value of the health summary type. The 2nd piece will be set to the name of the health summary type. COMPONENT/ENTRY POINT: MAIN COMPONENT DESCRIPTION: This entry may be called from an Option with only the usual system variables. SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION ISC: Oakland SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 939 IA #: 939 FILE NUMBER: 142 GLOBAL ROOT: GMT(142, DATE CREATED: AUG 16, 1994 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA939 ID: GMT(142, GLOBAL REFERENCE: GMT(142,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: GMT(142,D0) GENERAL DESCRIPTION: Used to do a look-up to the Health Summary Type (#142) to select a template. This agreement is tied to DBIA938. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11200102 SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION ISC: Oakland NUMBER: 940 IA #: 940 FILE NUMBER: 772 GLOBAL ROOT: HL(772, DATE CREATED: AUG 19, 1994 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA940 ID: HL(772, GLOBAL REFERENCE: C x-ref GLOBAL DESCRIPTION: The purpose of using the C cross-reference is to find the internal entry number of a specific HL7 outgoing transmission, by using the Message Control ID. The Message Control ID of that transmission is stored in an IVM file. GLOBAL REFERENCE: HL(772,D0,0) FIELD NUMBER: .05 FIELD NAME: RELATED MAILMAN MESSAGE LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Directly read the field RELATED MAILMAN MESSAGE. GLOBAL DESCRIPTION: The purpose of accessing the associated Mailman message number for an outgoing HL7 transmission is to determine, using a function call to VA MailMan, if that message is Awaiting Transmission. GENERAL DESCRIPTION: The IVM package requests permission to use the HL7 TRANSMISSION (#772) file to find the mailman message number associated with an outgoing HL7 transmission. The purpose of this reference is to use that number to determine if the message is Awaiting Transmission. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11661792 SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 941 IA #: 941 FILE NUMBER: 771.3 GLOBAL ROOT: HL(771.3, DATE CREATED: AUG 19, 1994 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA941 ID: HL(771.3, GENERAL DESCRIPTION: The IVM package requests permission to store the pointer to an entry in the HL7 SEGMENT NAME (#771.3) file in an IVM file. Both the pointer and segment name will be stored, in the INCOMING SEGMENT (#.01) and SEGMENT NAME (#.02) fields of the QUERY TRANSMISSION DATE/TIME (#.05) multiple of the IVM PATIENT (#301.5) file, respectively. The pointer to the segment name will be determined using a DIC look-up call. The segment name will be extracted from an HL7 message segment. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11661792 SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 942 IA #: 942 DATE CREATED: AUG 19, 1994 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA942 GENERAL DESCRIPTION: The IVM requests permission to perform the following actions during the initialization process of IVM v2.0: 1. Add the following two new segments to the HL7 SEGMENT NAME (#771.3) file: A. ABBREVIATED NAME: ZIR FULL NAME: VA Specific Income Information VERSION: 2.1 B. ABBREVIATED NAME: ZIO FULL NAME: VA Spec. Patient Information VERSION: 2.1 2. Update the 'IVM' entry in the HL7 DHCP APPLICATION PARAMETER (#771) file with: A. New entries in the HL7 MESSAGE (#6) multiple B. New entries in the HL7 SEGMENT (#5) multiple STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11661792 SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 943 IA #: 943 DATE CREATED: AUG 19, 1994 CUSTODIAL PACKAGE: INCOME VERIFICATION MATCH CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IVMUFNC3 NAME: DBIA943 ID: IVMUFNC3 GENERAL DESCRIPTION: IB requests an integration agreement with the IVM package to pass billing and collections information to the IVM package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11662654 COMPONENT/ENTRY POINT: REV(REF,DFN,CLASS... COMPONENT DESCRIPTION: This entry point is called by the Integrated Billing package. It is used to pass billing information to the IVM package for Means Test charges which were pending review and were passed to the Accounts Receivables module using the option Release Charges 'Pending Review.' VARIABLES: REF TYPE: Input VARIABLES DESCRIPTION: Bill reference number from file #350, field #.01 VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the patient in file #2 VARIABLES: CLASS TYPE: Input VARIABLES DESCRIPTION: Bill Classification [ 1-Inpt, 2-Opt ] VARIABLES: TYPE TYPE: Input VARIABLES DESCRIPTION: Bill Classification [ 1-Inpt, 2-Opt ] VARIABLES: FROM TYPE: Input VARIABLES DESCRIPTION: Bill From Date in FM format VARIABLES: TO TYPE: Input VARIABLES DESCRIPTION: Bill To Date in FM format VARIABLES: AMOUNT TYPE: Input VARIABLES DESCRIPTION: Amount Billed VARIABLES: HOLD TYPE: Input VARIABLES DESCRIPTION: Charge placed on hold? [ 1-Yes, 0-No ] COMPONENT/ENTRY POINT: $$CHK(DFN) COMPONENT DESCRIPTION: This function is used by the IB package to determine if a specific patient is being monitored for billing and collections activity by the IVM package. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the patient in file #2 VARIABLES: OUT TYPE: Output VARIABLES DESCRIPTION: This function returns a 1 if IVM is monitoring this patient; otherwise a 0 is returned SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 944 IA #: 944 DATE CREATED: AUG 19, 1994 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBCNSU NAME: DBIA944 ID: IBCNSU GENERAL DESCRIPTION: IVM files patient insurance information into DHCP which has been received from the IVM Center. This call is used to identify a group plan for the policy when the policy is being filed. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11663505 COMPONENT/ENTRY POINT: $$HIP(I,G,NA,NU) COMPONENT DESCRIPTION: This call is used to return the pointer in file #355.3 for the group plan, if it exists, or the pointer of a new plan in #355.3 which is created by the call if the plan does not exist. VARIABLES: I TYPE: Input VARIABLES DESCRIPTION: This variable is a pointer to an Insurance Company in file #36 that is the holder of the group plan. VARIABLES: G TYPE: Input VARIABLES DESCRIPTION: This variable contains a 1 if the plan is a group plan, or a 0 if the plan is an individual plan. VARIABLES: NA TYPE: Input VARIABLES DESCRIPTION: This variable contains the group name of the plan received by the IVM Center. VARIABLES: NU TYPE: Input VARIABLES DESCRIPTION: This variable contains the group number of the paln received by the IVM Center. VARIABLES: POL TYPE: Output VARIABLES DESCRIPTION: This function call returns this output, which is the pointer to a group plan from file #355.3. This pointed-to plan is either an existing plan which was located by the function, or a new plan which was created by the call if a plan could not be found. SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 945 IA #: 945 DATE CREATED: AUG 19, 1994 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBCNSM31 NAME: DBIA945 ID: IBCNSM31 GENERAL DESCRIPTION: IVM files patient insurance information into DHCP which has been received from the IVM Center. This call is used to reconcile the field COVERED BY HEALTH INSURANCE? in the PATIENT (#2) file with the information stored in the INSURANCE TYPE multiple after the new policy received from the IVM Center has been filed. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11663505 COMPONENT/ENTRY POINT: $$COVERED(DFN,COVP) COMPONENT DESCRIPTION: This call is made to correctly set the field COVERED BY HEALTH INSURANCE? in the PATIENT (#2) file after a new policy has been filed through the IVM package. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This is a pointer to the patient in file #2. VARIABLES: COVP TYPE: Input VARIABLES DESCRIPTION: This is the value of the field COVERED BY HEALTH INSURANCE? in the PATIENT (#2) file prior to adding the new policy received from the IVM Center. SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 946 IA #: 946 DATE CREATED: AUG 19, 1994 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBCNSEVT NAME: DBIA946 ID: IBCNSEVT GENERAL DESCRIPTION: IVM files patient insurance information into DHCP which has been received from the IVM Center. This routine is used to invoke the IB Insurance Event Driver after a new patient policy which has been received from the IVM Center is filed. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11663505 COMPONENT/ENTRY POINT: AFTER COMPONENT DESCRIPTION: This call is made to set up the necessary input variables before calling the IB Insurance Event Driver. VARIABLES: IBCDFN TYPE: Input VARIABLES DESCRIPTION: This variable points to an entry in the INSURANCE TYPE multiple in the PATIENT (#2) file. VARIABLES: IBEVTP0 TYPE: Input VARIABLES DESCRIPTION: This variable contains the zeroth node of the previous value of an entry in the INSURANCE TYPE multiple in the PATIENT (#2) file. VARIABLES: IBEVTA0 TYPE: Output VARIABLES DESCRIPTION: This variable contains the zeroth node of the new value of an entry in the INSURANCE TYPE multiple in the PATIENT (#2) file. VARIABLES: IBEVTA1 TYPE: Output VARIABLES DESCRIPTION: This variable contains the 1 node of the new value of an entry in the INSURANCE TYPE multiple in the PATIENT (#2) file. VARIABLES: IBEVTACT TYPE: Output VARIABLES DESCRIPTION: This variable, defined by IB, describes the action taken (Add/Edit Delete) on an entry in the INSURANCE TYPE multiple in the PATIENT (#2) file. VARIABLES: IBEVTA2 TYPE: Output VARIABLES DESCRIPTION: This variable contains the 2 node of the new value of an entry in the INSURANCE TYPE multiple in the PATIENT (#2) file. COMPONENT/ENTRY POINT: (TOP of routine) COMPONENT DESCRIPTION: The call D ^IBCNSEVT is made to invoke the IB Insurance Event Driver after a new policy is filed in the IVM package. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the patient in file #2. VARIABLES: IBCDFN TYPE: Input VARIABLES DESCRIPTION: (Defined above) VARIABLES: IBEVTA0 TYPE: Input VARIABLES DESCRIPTION: (Defined above) VARIABLES: IBEVTA1 TYPE: Input VARIABLES DESCRIPTION: (Defined above) VARIABLES: IBEVTA2 TYPE: Input VARIABLES DESCRIPTION: (Defined above) VARIABLES: IBEVTP0 TYPE: Input VARIABLES DESCRIPTION: (Defined above) VARIABLES: IBEVTP1 TYPE: Input VARIABLES DESCRIPTION: This variable contains the 1 node of the previous value of an entry in the INSURANCE TYPE multiple in the PATIENT (#2) file. VARIABLES: IBEVTP2 TYPE: Input VARIABLES DESCRIPTION: This variable contains the 2 node of the previous value of an entry in the INSURANCE TYPE multiple in the PATIENT (#2) file. VARIABLES: IBEVTACT TYPE: Input VARIABLES DESCRIPTION: (Defined above) SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 947 IA #: 947 DATE CREATED: AUG 19, 1994 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBAMTV4 NAME: DBIA947 ID: IBAMTV4 GENERAL DESCRIPTION: These routine calls are used by the IVM package to retrieve IVM-related billing and collections information from IB to transmit to the IVM Center. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11663505 COMPONENT/ENTRY POINT: INS(ROOT) COMPONENT DESCRIPTION: This call is used to retrieve billing/collections information for patients stored in IB who have ever had an insurance policy identified by the IVM Center. The output array is defined as follows: @ROOT@(ref #)=1^2^3^4^5^6^7^8^9^10^11, where ref # - bill number or field #.01 to #350 1 - DFN 2 - Classification [1-Inpt,2-Opt,3-Refill,4-Pros] 3 - Type [1-Claim,2-Copay,3-Per Diem] 4 - Bill From Date 5 - Bill To Date 6 - Date Bill Created 7 - Amt Billed 8 - Amt Collected (Claims only) 9 - Date Bill Closed (Claims only) 10 - Cancelled? [0-No,1-Yes] 11 - On Hold? (Patient charges only) VARIABLES: ROOT TYPE: Input VARIABLES DESCRIPTION: This variable is used to denote the array root for IB to store the billing/collections information. The actual array is the output from the call. COMPONENT/ENTRY POINT: ALL(DFN,ROOT,ST,END) COMPONENT DESCRIPTION: This call is used to retrieve billing/collections information for patients who are being tracked by the IVM package. The output from this call is the same for the INS call, which was defined above. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the patient in file #2. VARIABLES: ROOT TYPE: Input VARIABLES DESCRIPTION: This variable is used to denote the array root for IB to store the billing/collections information. The actual array is the output from the call. VARIABLES: ST TYPE: Input VARIABLES DESCRIPTION: This variable tells IB the first date to begin to retrieve Means Test charges for a patient. VARIABLES: END TYPE: Input VARIABLES DESCRIPTION: This variable tells IB the last date to retrieve Means Test charges for a patient. SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 948 IA #: 948 DATE CREATED: AUG 19, 1994 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA948 GENERAL DESCRIPTION: This agreement is to request approval to perform the following activities when installing IVM v2.0: 1. Export the PATIENT (#.02) and STATUS (#.05) fields of the INTEGRATED BILLING ACTION (#350) file with the release. 2. Export the options IB MT ON HOLD MENU and IB MT REV PEND CHARGES with the release. 3. Export the List Templates (in file #409.61) IB MT REVIEW INDIV CHARGES and IB MT REVIEW PATIENT with the release. 4. Export the following IB protocols with this release: - IBAMTV REV PASS CHARGE - IBAMTV REV CANC CHARGE - IBAMTV REV IND CHARGES - IBAMTV SEL PATIENT - IBAMTV REV PATIENT 5. Attach the IVM protocol IVM INSURANCE EVENT to the IB protocol IBCN NEW INSURANCE EVENTS. 6. Add the new entry HOLD - REVIEW to the IB ACTION STATUS (#350.21) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11663505 SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 949 IA #: 949 FILE NUMBER: 36 GLOBAL ROOT: DIC(36, DATE CREATED: AUG 19, 1994 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA949 ID: DIC(36, GLOBAL REFERENCE: DIC(36,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Write w/Fileman FIELD DESCRIPTION: It may be necessary to add a new insurance company when filing a new patient policy. GLOBAL REFERENCE: DIC(36,D0,.11) FIELD NUMBER: .111 FIELD NAME: STREET ADDRESS [LINE 1] LOCATION: .11;1 ACCESS: Write w/Fileman FIELD NUMBER: .112 FIELD NAME: STREET ADDRESS [LINE 2] LOCATION: .11;2 ACCESS: Write w/Fileman FIELD NUMBER: .114 FIELD NAME: CITY LOCATION: .11;4 ACCESS: Write w/Fileman FIELD NUMBER: .115 FIELD NAME: STATE LOCATION: .11;5 ACCESS: Write w/Fileman FIELD NUMBER: .116 FIELD NAME: ZIP CODE LOCATION: .11;6 ACCESS: Write w/Fileman GLOBAL DESCRIPTION: Update of the insurance company address. GLOBAL REFERENCE: DIC(36,D0,.13) FIELD NUMBER: .131 FIELD NAME: PHONE NUMBER LOCATION: .13;1 ACCESS: Write w/Fileman FIELD DESCRIPTION: Update of the insurance company phone number. GENERAL DESCRIPTION: IVM files patient insurance information into DHCP which has been received from the IVM Center. To file a complete policy, it may be necessary to add entries to the INSURANCE COMPANY (#36) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11663505 SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 950 IA #: 950 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: AUG 19, 1994 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA950 ID: DPT( CREATOR: LEYVA,KATHRYN GLOBAL REFERENCE: DPT(D0,.31) FIELD NUMBER: .3192 FIELD NAME: COVERED BY HEALTH INSURANCE? LOCATION: .31;11 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The value of this field is needed as input to the call COVERED^IBCNSM31, which then possibly updates this field. GLOBAL REFERENCE: DPT(D0,.312,D1,0) FIELD NUMBER: .01 FIELD NAME: INSURANCE TYPE LOCATION: 0;1 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the insurance company for the new policy. FIELD NUMBER: .18 FIELD NAME: GROUP PLAN LOCATION: 0;18 ACCESS: Write w/Fileman FIELD DESCRIPTION: This a pointer to the group plan in file #355.3. FIELD NUMBER: 1 FIELD NAME: *SUBSCRIBER ID LOCATION: 0;2 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field identifies the patient to the insurance company. Note: IB*2*497 - replaced by SUBSCRIBER ID field (7.02) FIELD NUMBER: 3 FIELD NAME: INSURANCE EXPIRATION DATE LOCATION: 0;4 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the expiration date of the policy. FIELD NUMBER: 6 FIELD NAME: WHOSE INSURANCE LOCATION: 0;6 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field identifies who actually holds the policy. FIELD NUMBER: 8 FIELD NAME: EFFECTIVE DATE OF POLICY LOCATION: 0;8 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the effective date of the policy. FIELD NUMBER: 17 FIELD NAME: *NAME OF INSURED LOCATION: 0;17 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field contains the name of the person to which the policy was issued. Note: IB*2*497 - replaced by NAME OF INSURED field (7.01) GLOBAL DESCRIPTION: These are essential data elements which must be filed with the policy. GLOBAL REFERENCE: DPT(D0,.312,D1,1) FIELD NUMBER: 1.05 FIELD NAME: DATE LAST EDITED LOCATION: 1;5 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the date that the policy was last edited. FIELD NUMBER: 1.06 FIELD NAME: LAST EDITED BY LOCATION: 1;6 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the user who last edited the policy. FIELD NUMBER: 1.09 FIELD NAME: SOURCE OF INFORMATION LOCATION: 1;9 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the source of the policy. This value will always be IVM. GLOBAL DESCRIPTION: These are essential data elements which must be filed with the policy. GLOBAL REFERENCE: DPT(D0,.312,D1,7) FIELD NUMBER: 7.01 FIELD NAME: NAME OF INSURED LOCATION: 7;1 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field contains the name of the person to which the policy was issued. FIELD NUMBER: 7.02 FIELD NAME: SUBSCRIBER ID LOCATION: 7;2 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field identifies the patient to the insurance company. GENERAL DESCRIPTION: IVM files patient insurance information into DHCP which has been received from the IVM Center. The patient policy is filed in the PATIENT (#2) file. Update: IB*2*497 increased the length of the SUBSCRIBER ID field and the NAME OF INSURED field to support the EDI New Standards and Operating Rules for VHA providers. This required length increase made it necessary to move the location of these 2 fields to new Data Dictionary nodes in the INSURANCE TYPE sub-file. To support this implementation, all subscribers to this ICR will need to make the necessary changes in their applications to reference the new fields and remove the references to the old fields. When all subscribers have implemented the use of the new fields, the old fields will be deleted with a IB*2*518. Old and new fields are noted in the field list detail of this ICR. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11663505 SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany DBA Comments: 2/21/14-DT Approved. Note:IB*2*497 set up the infrastructure to allow subscribing packages to begin coding against. The future IB*2.0*518 will be distributed at the same time as subscribing packages which will use the longer length fields and delete the shorter fields. DEACTIVATED FOR EDITS BY IB*2*497 PROJECT TEAM(KATHRYN LEYVA). 2/21/14-MM: Added Bill Jutzi as editor to edit ICR in Kathryn's absence. DATE ACTIVATED: FEB 21, 2014 DATE/TIME EDITED: FEB 21, 2014@17:50 ACTION: APPROVED AT THE REQUEST OF: JUTZI,BILL WITH CONCURRENCE OF: PFEIL,CATHERINE NUMBER: 951 IA #: 951 FILE NUMBER: 355.1 GLOBAL ROOT: IBE(355.1 DATE CREATED: AUG 19, 1994 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA951 ID: IBE(355.1 GLOBAL REFERENCE: IBE(355.1,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: The NAME of the type of plan is directly read and displayed to the user when the entire IVM policy is displayed to the user for review. GENERAL DESCRIPTION: IVM files patient insurance information into DHCP which has been received from the IVM Center. The type of plan is received from the IVM Center with the policy. This value points to the TYPE OF PLAN (#355.1) file and must be filed in the GROUP INSURANCE PLAN (#355.3) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11663505 SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany SUBSCRIBING PACKAGE: HEALTH SUMMARY SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 952 IA #: 952 FILE NUMBER: 355.3 GLOBAL ROOT: IBA(355.3, DATE CREATED: AUG 19, 1994 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA952 ID: IBA(355.3, GLOBAL REFERENCE: IBA(355.3,D0,0) FIELD NUMBER: .06 FIELD NAME: IS PRE-CERTIFICATION REQUIRED? LOCATION: 0;6 ACCESS: Write w/Fileman FIELD DESCRIPTION: When the group plan is either added or retrieved, this field of the record is updated. FIELD NUMBER: .09 FIELD NAME: TYPE OF PLAN LOCATION: 0;9 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is a pointer to file #355.1. GENERAL DESCRIPTION: IVM files patient insurance information into DHCP which has been received from the IVM Center. This involves potentially filing a new entry in the GROUP INSURANCE PLAN (#355.3) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11663505 SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 954 IA #: 954 DATE CREATED: AUG 19, 1994 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCSREC2 NAME: DBIA954 ID: PRCSREC2 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11663866 COMPONENT/ENTRY POINT: $$COST(X,Y) COMPONENT DESCRIPTION: For a control point entered in Y, all cost centers are returned. If the control point is not found, null is returned. If no cost centers are found, null is returned. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: This is the 3 digit station number where the control point is entered. VARIABLES: Y TYPE: Input VARIABLES DESCRIPTION: This is the control point number. SUBSCRIBING PACKAGE: AR (ACCOUNTS RECEIVABLE) ISC: Washington/Silver Spring SUBSCRIBING DETAILS: The Accounts Receivable package requires the use of cost centers in association with financial transactions. Cost centers linked with a given control point are stored on the Fund Control Point file (420) of the IFCAP package. IFCAP has provided a call to AR which returns all cost centers for a given control point. SUBSCRIBING PACKAGE: EVENT CAPTURE ISC: Birmingham NUMBER: 955 IA #: 955 DATE CREATED: AUG 21, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA955 GENERAL DESCRIPTION: The IVM package requests permission to perform the following actions during the initialization of IVM v2.0: 1. Export the following fields/files: a. The SOCIAL SECURITY NUMBER (#.09) field of the INCOME PERSON (#408.13) file. b. The following fields in the ANNUAL MEANS TEST (#408.31) file: DATE/TIME COMPLETED (#.07) DATE VETERAN SIGNED TEST (#.24) HARDSHIP? (#.2) PRIMARY INCOME TEST FOR YEAR? (#2) SOURCE OF INCOME TEST (#.23) DATE IVM VERIFIED MT COMPLETED (#.25) REFUSED TO SIGN (#.26) c. The SOURCE OF INCOME TEST (#408.34) file, with data. d. The following fields of the MEANS TEST CHANGES (#408.41) file: OLD SOURCE OF INCOME TEST (#.08) NEW SOURCE OF INCOME TEST (#.09) 2. Export the input template DGMT UPDATE AUDIT. 3. Export the following PIMS routines: DGMTA DGMTAUD DGMTAUD1 DGMTCOU1 DGMTDD DGMTDD2 DGMTDEL DGMTE DGMTEO DGMTO1 DGMTOFA1 DGMTOPYT DGMTOREQ DGMTP4 DGMTSCC DGMTU DGMTU11 DGMTU2 DGMTU21 DGMTU22 DGMTU23 DGMTU3 DGMTUB DGMTV DGPTUTL1 DGRPU VAFHLFNC VAFHLZDP VAFHLZGD VAFHLZIR VAFHLZMT 4. Add the new entries 'MEANS TEST UPLOAD' and 'UPLOADED MEANS TEST DELETION' to the MEANS TEST CHANGES TYPE (#408.42) file. 5. Update the field SOURCE OF INCOME TEST (#.23) to 'VAMC' and the field PRIMARY INCOME TEST FOR YEAR? (#2) to 'YES' for every entry in the ANNUAL MEANS TEST (#408.31) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11699076 SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 957 IA #: 957 DATE CREATED: AUG 22, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTA NAME: DBIA957 ID: DGMTA GENERAL DESCRIPTION: The IVM package files new entries in the ANNUAL MEANS TEST (#408.31) file. This call is used to create a stub entry in that file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11699410 COMPONENT/ENTRY POINT: ADD COMPONENT DESCRIPTION: This call is made to add new entries to file #408.31. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The variable DFN points to the patient in file #2. VARIABLES: DGMTDT TYPE: Input VARIABLES DESCRIPTION: The variable DGMTDT is the Date of Test (#.01 field) of the new Means Test being added. VARIABLES: DGMTYPT TYPE: Input VARIABLES DESCRIPTION: The variable DGMTYPT is the type of test (Means Test) being added. VARIABLES: DGMTI TYPE: Output VARIABLES DESCRIPTION: The variable DGMTI is returned from the call. It is the ien for the new entry in file #408.31. SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 958 IA #: 958 DATE CREATED: AUG 22, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTEVT NAME: DBIA958 ID: DGMTEVT GENERAL DESCRIPTION: After IVM adds a new Means Test to the PIMS database, the Means Test Event Driver must be invoked. These calls to DGMTEVT are used to invoke that event driver. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11699410 COMPONENT/ENTRY POINT: AFTER COMPONENT DESCRIPTION: This call is made to define one of the variables needed before invoking the Means Test Event Driver. VARIABLES: DGMTACT TYPE: Input VARIABLES DESCRIPTION: The variable DGMTACT specifies the 'action' that is taking place. The action will be 'UPL' to designate the Upload of a Means Test. VARIABLES: DGMTI TYPE: Input VARIABLES DESCRIPTION: The variable DGMTI is the ien for the entry in the ANNUAL MEANS TEST (#408.31) file which is being uploaded. VARIABLES: DGMTA TYPE: Output VARIABLES DESCRIPTION: The output variable DGMTA contains the zeroth node of the entry specified by DGMTI. COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: This call is made to invoke the Means Test Event Driver. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The variable DFN points to the patient in file #2. VARIABLES: DGMTACT TYPE: Input VARIABLES DESCRIPTION: The variable DGMTACT specifies the action which is taking place (i.e., adding, editing, deleting the Means Test, etc.). VARIABLES: DGMTI TYPE: Input VARIABLES DESCRIPTION: The variable DGMTI is the ien for the Means Test in file #408.31 which has been acted upon. VARIABLES: DGMTINF TYPE: Input VARIABLES DESCRIPTION: The variable DGMTINF indicates whether the process is interactive or running in the background. VARIABLES: DGMTP TYPE: Input VARIABLES DESCRIPTION: The variable DGMTP is the zeroth node of the Means Test specified by DGMTI prior to the action which took place on the test. VARIABLES: DGMTA TYPE: Input VARIABLES DESCRIPTION: The variable DGMTA is the zeroth node of the Means Test specified by DGMTI after action was taken on the test. SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 959 IA #: 959 DATE CREATED: AUG 22, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTSCU NAME: DBIA959 ID: DGMTSCU GENERAL DESCRIPTION: The IVM package adds new Means Tests into the PIMS Means Test module. In order to calculate the correct category for these tests, a call to PAR^DGMTSCU is made to retrieve the Means Test threshold figures for the correct year. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11699410 COMPONENT/ENTRY POINT: PAR COMPONENT DESCRIPTION: This call is used to retrieve the Means Test threshold figures used to calculate the Means Test category. VARIABLES: DGLY TYPE: Input VARIABLES DESCRIPTION: The variable DGLY is the year prior to the Means Test. VARIABLES: DGMTPAR TYPE: Output VARIABLES DESCRIPTION: The output variable DGMTPAR contains the zeroth node of MEANS TEST DATA (#250) multiple in the MAS PARAMETERS (#43) file for the appropriate Means Test year. VARIABLES: DGMTPAR(PREV) TYPE: Output VARIABLES DESCRIPTION: The output variable DGMTPAR("PREV") is defined if the appropriate MEANS TEST DATA multiple is not defined. SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 960 IA #: 960 DATE CREATED: AUG 22, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTSCU2 NAME: DBIA960 ID: DGMTSCU2 GENERAL DESCRIPTION: The IVM package adds Means Tests to the PIMS Means Test module. This call is used to calculate the Means Test category once a veteran's Means Test, income, and income relations information is filed. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11699410 COMPONENT/ENTRY POINT: SET COMPONENT DESCRIPTION: This call is used to compute the Means Test category for a Means Test. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The variable DFN points to the patient in file #2. VARIABLES: DGMTDT TYPE: Input VARIABLES DESCRIPTION: The variable DGMTDT is the Date of Test of the Means Test. VARIABLES: DGMTYPT TYPE: Input VARIABLES DESCRIPTION: The variable DGMTYPT is the type (Means Test) of income test. VARIABLES: DGMTI TYPE: Input VARIABLES DESCRIPTION: The variable DGMTI is the ien of the Means Test in file #408.31. VARIABLES: DGMTPAR TYPE: Input VARIABLES DESCRIPTION: The variable DGMTPAR contains the appropriate Means Test thresholds. VARIABLES: DGVIRI TYPE: Input VARIABLES DESCRIPTION: The variable DGVIRI contains the ien for the income relation in file #408.22. VARIABLES: DGVINI TYPE: Input VARIABLES DESCRIPTION: The variable DGVINI contains the ien for the individual annual income record in file #408.21. VARIABLES: DGCAT TYPE: Output VARIABLES DESCRIPTION: The output variable DGCAT contains the computed Means Test category for the Means Test. SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 961 IA #: 961 DATE CREATED: AUG 22, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTU1 NAME: DBIA961 ID: DGMTU1 GENERAL DESCRIPTION: The IVM package needs to extract Social Security numbers for a veteran's spouse. The function call $$DEM^DGMTU1 is used to retrieve the zeroth node of the PATIENT (#2) or INCOME PERSON (#408.13) for the spouse. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11699410 COMPONENT/ENTRY POINT: $$DEM(DGPRI) COMPONENT DESCRIPTION: This call is made to retrieve the appropriate zeroth node for the patient relation. The ssn is then extracted from that node. VARIABLES: DGPRI TYPE: Input VARIABLES DESCRIPTION: DGPRI points to the Income relation in file #408.12. VARIABLES: OUT TYPE: Output VARIABLES DESCRIPTION: The output from this function is the zeroth node of the patient relation from either the PATIENT (#2) or INCOME PERSON (#408.13) files. SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 963 IA #: 963 DATE CREATED: AUG 22, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTU2 NAME: DBIA963 ID: DGMTU2 GENERAL DESCRIPTION: The IVM package files new Means Tests into the PIMS Means Test module. As such, income and income relations records must be filed in files #408.21 and #408.22, respectively. Two function calls to routine DGMTU2 are made to add stub entries to these files. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$ADDIN(DFN,DGPRI,DGLY) COMPONENT DESCRIPTION: This function call is used to add entries to the INDIVIDUAL ANNUAL INCOME (#408.21) file. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN points to the patient in file #2. VARIABLES: DGPRI TYPE: Input VARIABLES DESCRIPTION: DGPRI points to the patient relation in file #408.12. VARIABLES: DGLY TYPE: Input VARIABLES DESCRIPTION: DGLY is the year prior to the year of the Means Test. VARIABLES: OUT TYPE: Output VARIABLES DESCRIPTION: The ien for the new record in file #408.21 is output from this function. COMPONENT/ENTRY POINT: $$ADDIR(DFN,DGINI) COMPONENT DESCRIPTION: This call is made to add entries to the INCOME RELATION (#408.22) file. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN points to the patient in file #2. VARIABLES: DGINI TYPE: Input VARIABLES DESCRIPTION: DGINI points to the annual income record in file #408.21. SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 964 IA #: 964 FILE NUMBER: 44 GLOBAL ROOT: SC( DATE CREATED: OCT 26, 2004 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA964 ID: SC( GLOBAL REFERENCE: SC(D0,0) FIELD NUMBER: 2502 FIELD NAME: NON-COUNT CLINIC? LOCATION: 0;17 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The field NON-COUNT CLINIC? is read directly from the zeroth node for a specific clinic. GLOBAL DESCRIPTION: This direct global reference is made to determine if an encounter in a specific clinic may be billed the Means Test copayment. GENERAL DESCRIPTION: The IVM package requests direct access to the field NON-COUNT CLINIC? (#2502) in the HOSPITAL LOCATION (#44) file. The field is used to determine whether an outpatient encounter in a specific clinic is potentially billable for Means Test billing. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11703182 SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 965 IA #: 965 DATE CREATED: AUG 22, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTU3 NAME: DBIA965 ID: DGMTU3 GENERAL DESCRIPTION: The IVM packages files new Means Tests in the PIMS Means Test module. Part of that process is to find income records for specific patient relations. The call to DGMTU3 is used to find the veteran's own income record. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11699410 COMPONENT/ENTRY POINT: $$IAI(DGPRI,DGLY) COMPONENT DESCRIPTION: This call is used to locate the ien for the veteran's income record in file #408.21 which is used to determine his Means Test category. VARIABLES: DGPRI TYPE: Input VARIABLES DESCRIPTION: DGPRI is the pointer to the patient relation in file #408.12. VARIABLES: DGLY TYPE: Input VARIABLES DESCRIPTION: DGLY is the year prior to the veteran's Means Test date. VARIABLES: OUT TYPE: Output VARIABLES DESCRIPTION: The output from this function call is the pointer to the relation's income record in file #408.21. SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 966 IA #: 966 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: AUG 22, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA966 ID: DGPM( GLOBAL REFERENCE: DGPM('ATID3',DFN, FIELD NUMBER: .01 FIELD NAME: DATE/TIME ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The command +$O(^DGPM("ATID3",DFN,"")) is used to find the veteran's most recent date of discharge. GLOBAL DESCRIPTION: The "ATID3" cross-reference is used to find the veteran's most recent discharge date. GENERAL DESCRIPTION: The IVM package needs to determine the last date that a veteran was treated at a specific facility. The "ATID3" cross-reference in the PATIENT MOVEMENT (#405) file is used to determine the patient's last discharge date. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11704137 SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 967 IA #: 967 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: AUG 22, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA967 ID: DPT( GLOBAL REFERENCE: DPT(D0,0) FIELD NUMBER: .02 FIELD NAME: SEX LOCATION: 0;2 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is updated with information received from the IVM Center. FIELD NUMBER: .03 FIELD NAME: DATE OF BIRTH LOCATION: 0;3 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is updated with information received from the IVM Center. GLOBAL DESCRIPTION: The IVM Center may find updated demographics information for the veteran while verifying his Means Test. This information may be uploaded directly into DHCP with user confirmation. GLOBAL REFERENCE: DPT(D0,.11) FIELD NUMBER: .111 FIELD NAME: STREET ADDRESS [LINE 1] LOCATION: .11;1 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is updated with information received from the IVM Center. FIELD NUMBER: .112 FIELD NAME: STREET ADDRESS [LINE 2] LOCATION: .11;2 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is updated with information received from the IVM Center. FIELD NUMBER: .114 FIELD NAME: CITY LOCATION: .11;4 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is updated with information received from the IVM Center. FIELD NUMBER: .115 FIELD NAME: STATE LOCATION: .11;5 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is updated with information received from the IVM Center. FIELD NUMBER: .1112 FIELD NAME: ZIP+4 LOCATION: .11;12 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is updated with information received from the IVM Center. FIELD NUMBER: .117 FIELD NAME: COUNTY LOCATION: .11;7 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is updated with information received from the IVM Center. GLOBAL DESCRIPTION: The IVM Center may find updated demographics information for the veteran while verifying his Means Test. This information may be uploaded directly into DHCP with user confirmation. GLOBAL REFERENCE: DPT(D0,.13) FIELD NUMBER: .131 FIELD NAME: PHONE NUMBER [RESIDENCE] LOCATION: .13;1 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is updated with information received from the IVM Center. GLOBAL DESCRIPTION: The IVM Center may find updated demographics information for the veteran while verifying his Means Test. This information may be uploaded directly into DHCP with user confirmation. GLOBAL REFERENCE: DPT(D0,.35) FIELD NUMBER: .351 FIELD NAME: DATE OF DEATH LOCATION: .35;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This field is updated with information received from the IVM Center. GLOBAL DESCRIPTION: The IVM Center may find updated demographics information for the veteran while verifying his Means Test. This information may be uploaded directly into DHCP with user confirmation. GENERAL DESCRIPTION: The IVM package requests permission to directly access and file various fields in the PATIENT (#2) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11704137 SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 968 IA #: 968 FILE NUMBER: 408.31 GLOBAL ROOT: DGMT(408.31, DATE CREATED: AUG 22, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA968 ID: DGMT(408.31, GLOBAL REFERENCE: DGMT(408.31,D0,0) FIELD NUMBER: .01 FIELD NAME: DATE OF TEST LOCATION: 0;1 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is part of the IVM verified Means Test. FIELD NUMBER: .19 FIELD NAME: TYPE OF TEST LOCATION: 0;19 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is part of the IVM verified Means Test. FIELD NUMBER: .02 FIELD NAME: PATIENT LOCATION: 0;2 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is part of the IVM verified Means Test. FIELD NUMBER: .03 FIELD NAME: STATUS LOCATION: 0;3 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This field is calculated as part of the IVM verified Means Test. FIELD NUMBER: .04 FIELD NAME: INCOME LOCATION: 0;4 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is calculated as part of the IVM verified Means Test. FIELD NUMBER: .05 FIELD NAME: NET WORTH LOCATION: 0;5 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is calculated as part of the IVM verified Means Test. FIELD NUMBER: .06 FIELD NAME: COMPLETED BY LOCATION: 0;6 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is part of the IVM verified Means Test. FIELD NUMBER: .07 FIELD NAME: DATE/TIME COMPLETED LOCATION: 0;7 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is calculated as part of the IVM verified Means Test. FIELD NUMBER: .11 FIELD NAME: AGREE TO PAT DEDUCTIBLE LOCATION: 0;11 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is part of the IVM verified Means Test. FIELD NUMBER: .12 FIELD NAME: THRESHOLD A LOCATION: 0;12 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is part of the IVM verified Means Test. FIELD NUMBER: .13 FIELD NAME: THRESHOLD B LOCATION: 0;13 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is part of the IVM verified Means Test. FIELD NUMBER: .14 FIELD NAME: DECLINES TO GIVE INCOME INFO LOCATION: 0;14 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is part of the IVM verified Means Test. FIELD NUMBER: .15 FIELD NAME: DEDUCTIBLE EXPENSES LOCATION: 0;15 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is calculated as part of the IVM verified Means Test. FIELD NUMBER: .16 FIELD NAME: PREVIOUS YEARS THRESHOLD LOCATION: 0;16 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is calculated as part of the IVM verified Means Test. FIELD NUMBER: .18 FIELD NAME: TOTAL DEPENDENTS LOCATION: 0;18 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is calculated as part of the IVM verified Means Test. FIELD NUMBER: .2 FIELD NAME: HARDSHIP? LOCATION: 0;20 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This field is part of the IVM verified Means Test. FIELD NUMBER: .23 FIELD NAME: SOURCE OF INCOME TEST LOCATION: 0;23 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This field is part of the IVM verified Means Test. FIELD NUMBER: .24 FIELD NAME: DATE VETERAN SIGNED TEST LOCATION: 0;24 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is part of the IVM verified Means Test. FIELD NUMBER: .25 FIELD NAME: DATE IVM VERIFIED MT COMPLETED LOCATION: 0;25 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is part of the IVM verified Means Test. FIELD NUMBER: .26 FIELD NAME: REFUSED TO SIGN LOCATION: 0;26 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is part of the IVM verified Means Test. GLOBAL DESCRIPTION: All of these fields are updated in file #408.31 while adding a new Means Test. GLOBAL REFERENCE: DGMT(408.31,D0,'PRIM') FIELD NUMBER: 2 FIELD NAME: PRIMARY INCOME TEST FOR YEAR? LOCATION: PRIM;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This field is part of the IVM verified Means Test. GLOBAL DESCRIPTION: This field is updated in file #408.31 when adding a new Means Test. GLOBAL REFERENCE: DGMT(408.31,D0,'C',N,0) FIELD NUMBER: 50 FIELD NAME: COMMENT LOCATION: C;0 ACCESS: Read w/Fileman FIELD DESCRIPTION: The word-processing comments for a Means Test are extracted from DHCP and transmitted to the IVM Center. GLOBAL DESCRIPTION: The Means Test comments need to be extracted for transmission to the IVM Center. GENERAL DESCRIPTION: The IVM package files new Means Tests in the PIMS Means Test module. IVM requests permission to add new entries into the ANNUAL MEANS TEST (#408.31) file, and to update several fields in that file. Additionally, permission is requested to delete entries from that file (if the IVM Center mistakenly sends a Means Test to a facility). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11704137 SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 973 IA #: 973 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: SEP 23, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA973 ID: VA(200, GLOBAL REFERENCE: VA(200,D0,'PS' FIELD NUMBER: 53.4 FIELD NAME: INACTIVE DATE LOCATION: PS;4 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Used to screen out inactive providers. Below is a listing of files and fields that will be referencing the inactive provider field in 200, indirectly. Routine DGPMDD references the data. The fields contain an extrensic function for screening, $$SCREEN^DGPMDD(ien,da,date) and a call to HELP^DGPMDD(da,date) for executable help. ===================================================================== File 405 - Patient Movement *Field .08 - PRIMARY CARE PHYSICIAN *Field .19 - ATTENDING PHYSICIAN File 2 - Patient Field .104 - PROVIDER Field .1041 - ATTENDING PHYSICIAN File 41.1 - Scheduled Admission Field 5 - PROVIDER File 45 - PTF (Subfile 45.02, 50) Field 24 - PROVIDER File 45.7 - FACILITY TREATING SPECIALTY (Subfile 45.701, 10) Field .01 - PROVIDERS STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12047878 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 974 IA #: 974 DATE CREATED: AUG 23, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTU NAME: DBIA974 ID: DGMTU GENERAL DESCRIPTION: IVM requests permission to make the function call $$MTS^DGMTU in order to determine the Means Test status, given a pointer to the status in the MEANS TEST STATUS (#408.32) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11699410 COMPONENT/ENTRY POINT: $$MTS(DFN,MTS) COMPONENT DESCRIPTION: This call returns the Means Test Status Name for a given pointer to the Means Test Status (#408.32) file. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN points to the patient in file #2. VARIABLES: MTS TYPE: Input VARIABLES DESCRIPTION: MTS points to the Means Test Status in file #408.32. VARIABLES: OUT TYPE: Output VARIABLES DESCRIPTION: This function returns the Means Test Status Name and the Status Code concatenated by a caret ('^'). SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 975 IA #: 975 FILE NUMBER: 1.5 GLOBAL ROOT: DIW(1.5, DATE CREATED: AUG 29, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA975 ID: DIW(1.5, GENERAL DESCRIPTION: This integration agreement permits LetterMan to install and reference the WORD LIST file #1.5 stored in global ^DIW(1.5,. The WORD LIST file is used by the LetterMan spell checker. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10903891 SUBSCRIBING PACKAGE: LETTERMAN ISC: Washington/Silver Spring NUMBER: 976 IA #: 976 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: AUG 29, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA976 ID: VA(200, GENERAL DESCRIPTION: This integration agreement permits LetterMan to distribute and add/edit data in the fields in the range of 8983 to 8984 in the NEW PERSON FILE #200. The following is a standard data dictionary listing of the fields: 200,8983.11 DISPLAY HELP AT ENTRY TO LM LM;1 SET 'y' FOR YES; 'n' FOR NO; LAST EDITED: JAN 26, 1990 HELP-PROMPT: Enter yes to display the help text before entering the editor. DESCRIPTION: If set to yes, a help text will be displayed before entering the editor. This is used primarily for new users. 200,8983.12 ASK TERMINAL TYPE AT LM ENTRY LM;2 SET 'y' FOR YES; 'n' FOR NO; HELP-PROMPT: Enter yes to ask the terminal type upon entry to the editor. DESCRIPTION: If set to yes, the terminal type will be asked upon entry to the editor. 200,8983.13 DEFAULT TERMINAL TYPE FOR LM LM;3 POINTER TO TERMINAL TYPE FILE ( #3.2) LAST EDITED: JAN 26, 1990 DESCRIPTION: This field stores the default terminal type for a user. 200,8983.14 DISPLAY LM COMMANDS LM;4 SET 'y' FOR YES; 'n' FOR NO; LAST EDITED: JAN 26, 1990 HELP-PROMPT: Enter yes to display the list of commands when entering the command mode. DESCRIPTION: If set to yes, the list of commands will be displayed at the bottom of the screen when entering the command mode. 200,8983.15 BRIGHT CHARS AT EXIT FROM LM LM;5 SET 'y' FOR YES; 'n' FOR NO; LAST EDITED: JAN 26, 1990 HELP-PROMPT: Enter yes to leave the terminal in high intensity after exiting LetterMan. DESCRIPTION: If set to yes, the terminal will be left in high intensity after exiting. 200,8983.16 DATE LAST ACCESSED LM WP LM;6 DATE INPUT TRANSFORM: S %DT="ETR" D ^%DT S X=Y K:Y<1 X LAST EDITED: JAN 28, 1990 DESCRIPTION: The date and time a user last accessed the LetterMan word processor document editor. 200,8983.17 TOTAL MINUTES USING LM WP LM;7 NUMBER INPUT TRANSFORM: K:+X'=X!(X>999999999)!(X<0)!(X?.E1"."1N.N) X LAST EDITED: JAN 28, 1990 HELP-PROMPT: Enter the total minutes spent using the LetterMan Word Processor (Editor), from 0 to 999999999. DESCRIPTION: The total minutes a user has used the LetterMan word processor document editor. 200,8983.18 KEYSTROKES FROM LM WP LM;8 NUMBER INPUT TRANSFORM: K:+X'=X!(X>999999999)!(X<0)!(X?.E1"."1N.N) X LAST EDITED: JAN 28, 1990 HELP-PROMPT: Enter the total number of keystrokes a user has typed from the word processor document editor, from 0 to 999999999. DESCRIPTION: This field stores the total number of keystrokes a user has typed from the word processor document editor. 200,8983.5 SPELLING EXCEPTION DICTIONARY LM1;0 Multiple #200.0089831 DESCRIPTION: This field stores the exception spelling dictionary for the user. 200.0089831,.01 WORD 0;1 FREE TEXT (Multiply asked) INPUT TRANSFORM: K:$L(X)>30!($L(X)<1) X I $D(X),X'?.L,X'["-" K X LAST EDITED: JAN 26, 1990 HELP-PROMPT: Enter the WORD which should be checked by the spelling checker, from 1 to 30 lower case characters including '-'. DESCRIPTION: This field stores words which will be checked when spell checking a document. NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER CROSS-REFERENCE: 200.0089831^B 1)= S ^VA(200,DA(1),"LM1","B",$E(X,1,30),DA)= "" 2)= K ^VA(200,DA(1),"LM1","B",$E(X,1,30),DA) 200.0089831,1 ITS A WORD ? 0;2 SET 'y' FOR YES; LAST EDITED: MAY 4, 1992 CROSS-REFERENCE: 200.0089831^AW^MUMPS 1)= S ^VA(200,DA(1),"LM1","AW",$P(^VA(200,DA( 1),"LM1",DA,0),"^"),DA)="" 2)= K ^VA(200,DA(1),"LM1","AW",$P(^VA(200,DA( 1),"LM1",DA,0),"^"),DA) This cross reference is used to identify the entry in the exception dictionary as a word. 200.0089831,2 ITS NOT A WORD ? 0;3 SET 'y' FOR YES; LAST EDITED: MAY 4, 1992 CROSS-REFERENCE: 200.0089831^AN^MUMPS 1)= S ^VA(200,DA(1),"LM1","AN",$P(^VA(200,DA( 1),"LM1",DA,0),"^"),DA)="" 2)= K ^VA(200,DA(1),"LM1","AN",$P(^VA(200,DA( 1),"LM1",DA,0),"^"),DA) This cross reference is used to identify the entry in the exception dictionary as a non-word. 200,8983.51 DEFINED FORMATS FOR LM LM2;0 Multiple #200.0089832 DESCRIPTION: This field is used to store predefined format lines which a user can select from during editing. 200.0089832,.01 NUMBER 0;1 NUMBER (Multiply asked) INPUT TRANSFORM: K:+X'=X!(X>9999999)!(X<1)!(X?.E1"."1N.N) X LAST EDITED: JAN 26, 1990 HELP-PROMPT: Enter the number of the predefined format line, from 1 to 9999999. DESCRIPTION: This is the reference number to the predefined format line. CROSS-REFERENCE: 200.0089832^B 1)= S ^VA(200,DA(1),"LM2","B",$E(X,1,30),DA)= "" 2)= K ^VA(200,DA(1),"LM2","B",$E(X,1,30),DA) 200.0089832,1 DEFAULT 0;2 SET 'y' FOR YES; 'n' FOR NO; LAST EDITED: JAN 26, 1990 HELP-PROMPT: Enter yes to use this format line when you enter the screen editor. DESCRIPTION: If set to yes, this format line will be used as the default format line when using the screen editor. If a document already has a format line defined, then the document format will be used. CROSS-REFERENCE: 200.0089832^AC 1)= S ^VA(200,DA(1),"LM2","AC",$E(X,1,30),DA) ="" 2)= K ^VA(200,DA(1),"LM2","AC",$E(X,1,30),DA) 200.0089832,2 FORMAT LINE 0;3 FREE TEXT INPUT TRANSFORM: K:$L(X)>79!($L(X)<1) X I $D(X) S %=X,X="WPSEF ORM" X ^%ZOSF("TEST") K X I $T S X=% D CHECK^ WPSEFORM LAST EDITED: MAR 23, 1992 HELP-PROMPT: The format line should contain dots '.' representing spaces or 'T' representing tab or indent markers followed by a '<' indicating the end of the right margin. DESCRIPTION: This field stores the predefined format lines of the user. NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER 200,8983.52 DEFINED PHRASES FOR LM LM3;0 Multiple #200.0089833 DESCRIPTION: This field stores predefined phrases which can be inserted into the document during editing. 200.0089833,.01 KEYWORD 0;1 FREE TEXT (Multiply asked) INPUT TRANSFORM: K:$L(X)>50!($L(X)<1) X LAST EDITED: JAN 26, 1990 HELP-PROMPT: Enter the keyword used to select this phrase, from 1 to 50 characters. DESCRIPTION: The predefined phrase 'keyword' used to select the phrase. CROSS-REFERENCE: 200.0089833^B 1)= S ^VA(200,DA(1),"LM3","B",$E(X,1,30),DA)= "" 2)= K ^VA(200,DA(1),"LM3","B",$E(X,1,30),DA) 200.0089833,1 PHRASE 1;0 WORD-PROCESSING #200.00898331 (NO WRAP) DESCRIPTION: The phrase to be inserted into the document. 200,8983.6 LM LIMIT WP FIELDS TO EDIT LM4;0 Multiple #200.0089834 DESCRIPTION: This field is used by the user to limit which word processing fields should be edited by LetterMan. 200.0089834,.01 LM LIMIT WP FIELDS TO EDIT 0;1 FREE TEXT (Multiply asked) Limited Word-Processing Fields to Edit INPUT TRANSFORM: K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>150!($L (X)<4) X I $D(X) S %=X,X="WPSEFM" X ^%ZOSF("T EST") K X I $T S X=% D SCREEN^WPSEFM LAST EDITED: DEC 12, 1990 HELP-PROMPT: Answer must be 4-150 characters in length. EXECUTABLE HELP: S X="WPSEHELP" X ^%ZOSF("TEST") I $T D FMHELP ^WPSEHELP NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER CROSS-REFERENCE: 200.0089834^B 1)= S ^VA(200,DA(1),"LM4","B",$E(X,1,30),DA)= "" 2)= K ^VA(200,DA(1),"LM4","B",$E(X,1,30),DA) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10903795 SUBSCRIBING PACKAGE: LETTERMAN ISC: Washington/Silver Spring NUMBER: 978 IA #: 978 FILE NUMBER: 3.2 GLOBAL ROOT: %ZIS(2, DATE CREATED: AUG 30, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA978 ID: %ZIS(2, GLOBAL REFERENCE: %ZIS(2,D0,10) FIELD NUMBER: 110 FIELD NAME: OPEN PRINTER PORT LOCATION: 10;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: %ZIS(2,D0,11) FIELD NUMBER: 111 FIELD NAME: CLOSE PRINTER PORT LOCATION: 111;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: %ZIS(2,D0,'BAR0') FIELD NUMBER: 61 FIELD NAME: BAR CODE OFF LOCATION: BAR0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: %ZIS(2,D0,'BAR1') FIELD NUMBER: 60 FIELD NAME: BAR CODE ON LOCATION: BAR1;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This integration agreement allows IFCAP to lookup data in the TERMINAL TYPE File #3.5. The lookups are direct global references (^%ZIS(2,IOST(0),node)). The agreement is established since the routine %ZISS does not return the values for the fields above. In a future version of %ZISS, the fields 60 and 61 could be included since the bar code fields can be turned on/off by writing the value of the field (i.e. W ^%ZIS(2,IOST(0),"BAR1")). The routine %ZISS could also return the field values for opening and closing the printer port providing the field value returned is in its executable form (i.e. X ^%ZIS(2,IOST(0),10)). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11789564 SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring NUMBER: 979 IA #: 979 FILE NUMBER: 3.5 GLOBAL ROOT: %ZIS(2, DATE CREATED: AUG 30, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA979 ID: %ZIS(2, GENERAL DESCRIPTION: This integration agreement allows LetterMan to lookup terminal type attributes from the TERMINAL TYPE File #3.5 using direct global references. One option in LetterMan will automatically set up the terminal type to be used with LetterMan. In the next version of LetterMan, it will migrate to using the %ZISS routine to return the attributes. There are approximately 15 attributes used by LetterMan. Half of the attributes will be converted from executable code to writeable attributes (as returned by %ZISS). STATUS: Active DURATION: Next Version MAIL MESSAGE: 11789666 GOOD ONLY FOR VERSION: 5.1 SUBSCRIBING PACKAGE: LETTERMAN ISC: Washington/Silver Spring NUMBER: 980 IA #: 980 DATE CREATED: AUG 30, 1994 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSODISP NAME: PSODISP ID: PSODISP GENERAL DESCRIPTION: To display help at the prescription selection prompt. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11739760 COMPONENT/ENTRY POINT: HELP SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 981 IA #: 981 DATE CREATED: AUG 30, 1994 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOFUNC NAME: PSOFUNC ID: PSOFUNC GENERAL DESCRIPTION: To determine the status of a prescription STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11739760 COMPONENT/ENTRY POINT: PSOFUNC VARIABLES: J TYPE: Input VARIABLES DESCRIPTION: Internal entry number from ^PSRX( VARIABLES: RX0 TYPE: Input VARIABLES DESCRIPTION: Zero node from ^PSRX( VARIABLES: RX2 TYPE: Input VARIABLES DESCRIPTION: 2 node from ^PSRX( VARIABLES: ST TYPE: Output VARIABLES DESCRIPTION: External form of status SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 982 IA #: 982 DATE CREATED: AUG 30, 1994 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOLSET NAME: PSOLSET ID: PSOLSET GENERAL DESCRIPTION: To kill Outpatient variables. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11739760 COMPONENT/ENTRY POINT: FINAL SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 983 IA #: 983 DATE CREATED: AUG 30, 1994 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOCSRL NAME: PSOCSRL ID: PSOCSRL GENERAL DESCRIPTION: To release prescriptions from a vault. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11739760 COMPONENT/ENTRY POINT: PSOCSRL VARIABLES: RXP TYPE: Input VARIABLES DESCRIPTION: Internal entry number of prescription. VARIABLES: XTYPE TYPE: Input VARIABLES DESCRIPTION: Original = "", Refill = "1^#", Partial = "P^#" VARIABLES: PSRH TYPE: Input VARIABLES DESCRIPTION: DUZ of releasing pharmacist. SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 986 IA #: 986 FILE NUMBER: 52 GLOBAL ROOT: PSRX( DATE CREATED: AUG 30, 1994 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA986 ID: PSRX( GLOBAL REFERENCE: PSRX( FIELD NUMBER: .01 FIELD NAME: RX # LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The "B" x-ref may also be read directly. FIELD NUMBER: 2 FIELD NAME: PATIENT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6 FIELD NAME: DRUG LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7 FIELD NAME: QTY LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 100 FIELD NAME: STATUS LOCATION: STA;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 22 FIELD NAME: FILL DATE LOCATION: 2;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 31 FIELD NAME: RELEASED DATE/TIME LOCATION: 2;13 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 32.1 FIELD NAME: RETURNED TO STOCK LOCATION: 2;15 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSRX(D0,1, FIELD NUMBER: .01 FIELD NAME: REFILL DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: QTY LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 14 FIELD NAME: RETURNED TO STOCK LOCATION: 0;16 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 17 FIELD NAME: RELEASED DATE/TIME LOCATION: 0;18 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSRX(D0,'P', FIELD NUMBER: .01 FIELD NAME: PARTIAL DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: QTY LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5 FIELD NAME: RETURNED TO STOCK LOCATION: 0;16 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 8 FIELD NAME: RELEASED DATE/TIME LOCATION: 0;19 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSRX(D0,4,D1, FIELD NUMBER: 3 FIELD NAME: STATUS LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: RX INDICATOR LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSRX(D0,'A', FIELD NUMBER: .01 FIELD NAME: ACTIVITY LOG LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: REASONS LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: INITIATOR OF ACTIVITY LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSRX(D0,'L', FIELD NUMBER: .01 FIELD NAME: LABEL DATE/TIME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: RX REFERENCE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: WARNING LABEL TYPE LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: For the Controlled Substances/Outpatient interface, read access is required for several fields in the PRESCRIPTION file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11739760 SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 987 IA #: 987 GLOBAL ROOT: DD( DATE CREATED: SEP 26, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA987 ID: DD( GENERAL DESCRIPTION: The Laboratory package Version 5.2 requests agreement from the VA FileMan package to modify the B cross-references in the LABORATORY TEST FILE #60 and the WKLD CODE FILE #64 to be greater than 30 characters. The first 30 characters are quite frequently the same for more than one test or workload code. ^DD(60,.01,1,1,1)=S ^LAB(60,"B",$E(X,1,40),DA)="" ^DD(64,.01,1,1,1)=S ^LAM("B",$E(X,1,60),DA)="" ^DD(64.061,.01,1,1,1)=^LAB(64.061,"B",$E(X,1,50),DA) STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 988 IA #: 988 FILE NUMBER: 440 GLOBAL ROOT: PRC(440, DATE CREATED: SEP 26, 1994 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: LIBRARY USE OF VENDOR FILE ID: PRC(440, GENERAL DESCRIPTION: STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11750166 SUBSCRIBING PACKAGE: LIBRARY ISC: Washington/Silver Spring NUMBER: 990 IA #: 990 FILE NUMBER: 130 GLOBAL ROOT: SRF( DATE CREATED: SEP 30, 1994 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA990-A ID: SRF( GLOBAL REFERENCE: SRF(D0,0) FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Standard VA FileMan EN^DIQ lookup. FIELD NUMBER: .011 FIELD NAME: IN/OUT-PATIENT STATUS LOCATION: 0;12 ACCESS: Read w/Fileman FIELD DESCRIPTION: Standard VA FileMan EN^DIQ lookup. FIELD NUMBER: .02 FIELD NAME: OPERATING ROOM LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: Standard VA FileMan EN^DIQ lookup. FIELD NUMBER: .04 FIELD NAME: SURGERY SPECIALTY LOCATION: 0;4 ACCESS: Read w/Fileman FIELD DESCRIPTION: Standard VA FileMan EN^DIQ lookup. FIELD NUMBER: .09 FIELD NAME: DATE OF OPERATION LOCATION: 0;9 ACCESS: Read w/Fileman FIELD DESCRIPTION: Standard VA FileMan EN^DIQ lookup. FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: Pointed to by field 130 SCHEDULED OPERATION in file 445.3 INTERNAL DISTRIBUTION ORDER. GLOBAL REFERENCE: SRF(D0,.1) FIELD NUMBER: .14 FIELD NAME: SURGEON LOCATION: .1;4 ACCESS: Read w/Fileman FIELD DESCRIPTION: Standard VA FileMan EN^DIQ lookup. GLOBAL REFERENCE: SRF(D0,OP) FIELD NUMBER: 27 FIELD NAME: PRINCIPAL PROCEDURE CODE LOCATION: OP;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: Standard VA FileMan EN^DIQ lookup. GLOBAL REFERENCE: SRF(D0,5,I,0) FIELD NUMBER: .28 FIELD NAME: GENERAL COMMENTS LOCATION: 5;0 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Reads the GENERAL COMMENTS word-processing field. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10986177 SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring NUMBER: 991 IA #: 991 FILE NUMBER: 137.45 GLOBAL ROOT: SRO(137.45, DATE CREATED: SEP 30, 1994 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA990-B ID: SRO(137.45, GLOBAL REFERENCE: SRO(137.45,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: Pointed to by field 130.03 SURGICAL SPECIALTY in file 446.1 INVENTORY DISTRIBUTED PATIENT SUPPLIES. FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Direct global read from the routine PRCPRPC1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10986177 SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring NUMBER: 992 IA #: 992 DATE CREATED: SEP 30, 1994 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SROPS NAME: DBIA990-C ID: SROPS GENERAL DESCRIPTION: Routine: PRCPCSOR: 1. Call the routine ^SROPS to lookup the patient and scheduled operation. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17382559 COMPONENT/ENTRY POINT: SROPS VARIABLES: PRCP("I") TYPE: Used VARIABLES DESCRIPTION: After the release of patch SR*3*44, the variable PRCP("I"), which is an Inventory system variable, must be defined to bypass the future date checking function added to the lookup process by the patch. If this variable is not defined and a surgical case with a future date is selected, the user will be notified that the case selected has a future date and the user must then enter YES to continue. SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring NUMBER: 994 IA #: 994 FILE NUMBER: 45.84 GLOBAL ROOT: DGP(45.84, DATE CREATED: SEP 30, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA993-B ORIGINAL NUMBER: 993 ID: DGP(45.84, GLOBAL REFERENCE: DGP(45.84, FIELD NUMBER: 2 FIELD NAME: CLOSE OUT DATE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to determine the date that a PTF record in file #45 was closed out. FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Read access to the "AC" x-ref also allowed. FIELD NUMBER: 3 FIELD NAME: CLOSE OUT BY LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Used to check and make sure the PTF record has not been closed out. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23720883 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES DBA Comments: JSH/10-23-2006 Deleted Fee Basis as a subscriber as per agreement between Zach Fain and Bob Yorty. Deleted description said: 1>Fee Basis uses the "AFEE" cross-reference in the PTF file to locate 2>a Non-VA PTF record that is created on admission to a Non-VA facility. 3>There are times when the admission is cancelled or entered in error 4>and fee locates the PTF record, assures it is not closed out by checking 5>in file 45.84, and deletes the stub record. 7/16/13-MM: Added Clinical Case Registries as a subscriber to ICR #994. Connie Ray found references to this ICR in existing CCR code. DATE/TIME EDITED: OCT 23, 2006@17:00 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: ZAIN,ZACHARY WITH CONCURRENCE OF: BAUMANN,SCOTT DATE/TIME EDITED: JUL 16, 2013@16:51 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: RAY,CONNIE NUMBER: 996 IA #: 996 FILE NUMBER: 72 GLOBAL ROOT: RA(72, DATE CREATED: AUG 31, 1994 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA118-D ORIGINAL NUMBER: 118 ID: RA(72, GLOBAL REFERENCE: RA(72,D0,0) FIELD NUMBER: .01 FIELD NAME: CURRENT EXAM STATUS LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: RA(72,'B',X,DA) FIELD NUMBER: .01 FIELD NAME: CURRENT EXAM STATUS ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: B cross-reference is used to determine STATUS. GLOBAL REFERENCE: RA(72,'AA', GLOBAL DESCRIPTION: Direct Global Read Access permitted. GENERAL DESCRIPTION: These look fine for the current field version (4.0) of Radiology. There are a few cautions for you when we release Radiology/Nuclear Medicine Version 4.5. These things may have no affect on you whatsoever, but you need to know so you can make your own judgement: a) Currently the exam statuses (file 72) each can be used for any exam regardless of imaging type. In Version 4.5, exam statuses will be specific to imaging type. We are adding the basic statuses (WAITING FOR EXAM, CALLED FOR EXAM, EXAMINED, CANCELLED, COMPLETE) to this file for each of the 8 imaging types. (i.e. there will be an EXAMINED status for General Radiology, an EXAMINED status for Nuclear Med, an EXAMINED status for Ultrasound , etc.. so that each imaging department can set up their exam status parameters differently.) b) Because of item a above, the 'B' cross-reference on file 72 becomes much less meaningful - there will now be 8 instances of each of the basis exam statuses. This may affect the proposed DBIA. Since the sites can add their own site-specific statuses, it's possible to have many instances of any status. So, the 'B' x-ref no longer represents a unique status name. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11757794 GOOD ONLY FOR VERSION: Radiology 4 SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION ISC: Oakland SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY ISC: Oakland SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE ISC: Oakland SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: CLINICAL REMINDERS NUMBER: 997 IA #: 997 FILE NUMBER: 42.4 GLOBAL ROOT: DIC(42.4 DATE CREATED: AUG 31, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA997 ID: DIC(42.4 GLOBAL REFERENCE: DIC(42.4,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11757796 SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY ISC: Oakland SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION ISC: Oakland SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES NUMBER: 998 IA #: 998 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: AUG 31, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA998 ID: DPT( GLOBAL REFERENCE: DPT(D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DPT(D0,'LR') FIELD NUMBER: 63 FIELD NAME: LABORATORY REFERENCE LOCATION: 63;1 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11757796 SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION ISC: Oakland SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT NUMBER: 999 IA #: 999 GLOBAL ROOT: DD( DATE CREATED: SEP 02, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA999 ID: DD( GENERAL DESCRIPTION: Read only access for the ^DD( Global. $O(^DD(FN,"GL",subscript,piece,0)) to get the field #. Read ^DD(FN,FLD,0), Custodial files only, where FN is a file # and FLD is a field #, to obtain the field name, the set of codes, or the input transform. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11857175 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas SUBSCRIBING PACKAGE: ASISTS SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE SUBSCRIBING DETAILS: added Oct 2008 DATE/TIME EDITED: OCT 15, 2008@14:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SHAMUKHAMEDOV,SHAVKAT WITH CONCURRENCE OF: TOMLIN,BRIAN NUMBER: 1003 IA #: 1003 FILE NUMBER: 41.1 GLOBAL ROOT: DGS(41.1, DATE CREATED: SEP 13, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Scheduled Admission DBIA ID: DGS(41.1, GLOBAL REFERENCE: DGS(41.1,"B",DFN,DA) FIELD NUMBER: 2 FIELD NAME: Reservation Date/Time LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: Length of Stay Expected LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: Admitting Diagnosis LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: 5 FIELD NAME: Provider LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 6 FIELD NAME: Surgery LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 8 FIELD NAME: Ward LOCATION: 0;8 ACCESS: Read w/Fileman FIELD NUMBER: 9 FIELD NAME: Treating Specialty LOCATION: 0;9 ACCESS: Read w/Fileman FIELD NUMBER: 10 FIELD NAME: Ward or Treating Specialty LOCATION: 0;10 ACCESS: Read w/Fileman FIELD NUMBER: 13 FIELD NAME: Date/Time Cancelled LOCATION: 0;13 ACCESS: Read w/Fileman FIELD NUMBER: 17 FIELD NAME: Admitted LOCATION: 0;17 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The health summary package needs to set up a DBIA to access Registration data in the Scheduled Admission File. We need to have read only access on the cross reference ^DGS(41.1,"B",Patient DFN,Internal Entry # in File 41.1) to check if any scheduled admissions exist for a given patient and to find the record number in file 41.1. A call will then be issued to EN^DIQ1 after setting DA=Internal entry in file 41.1, DIC=41.1, and DR="2:6;8:10;13;17". We need read only data on the following fields in file 41.1: 2 - Reservation Date/Time 3 - Length of Stay Expected 4 - Admitting Diagnosis 5 - Provider 6 - Surgery 8 - Ward 9 - Treating Specialty 10 - Ward or Treating Specialty 13 - Date/Time Cancelled 17 - Admitted STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11945140 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 1004 IA #: 1004 FILE NUMBER: 9999999.06 GLOBAL ROOT: AUTTLOC DATE CREATED: SEP 24, 1994 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1004 ID: AUTTLOC GENERAL DESCRIPTION: The PCE Patient/IHS Subset Package (PXPT) requests a file DBIA to distribute a partial definition of the Indian Health Services Location File (9999999.06) in the VA. The PXPT Post Installation routine will populate this Location File with dinumed entries from the Institution File (4). The description for this file is very specific about going through the IHS DBA for any changes. The IHS DBA proposed that the VA should use the dinumed Institution entries, and not distribute required IHS fields. The following data dictionary definition represents the subset of the Location File to be distributed by PXPT: STANDARD DATA DICTIONARY #9999999.06 -- LOCATION FILE 09/6/94 PAGE 1 STORED IN ^AUTTLOC( (251 ENTRIES) SITE: SLC UCI: DVA,DEV DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE --------------------------------------------------------------------------- This file contains the IHS Standard Facilities and their Associated codes, CHS Vendors, pointers to their respective service units and areas, a 2-4 character abbreviation, and the highest medical record number assigned by that facility. Changes to this data dictionary should be coordinated thru the IHS DBA. This file reflects entries in the IHS Standard Code Book, section VIII-C Area - Service Unit - Facility. Local additions or modifications should not be made. Monthly updates (if required) are provided by the IHS DBA thru the patch module. DD ACCESS: @ DEL ACCESS: @ AUDIT ACCESS: @ IDENTIFIED BY: POINTED TO BY: DEFAULT INSTITUTION field (#.04) of the VISIT TRACKING PARAMETERS File (#150.9) HEALTH RECORD FAC field (#.01) of the HEALTH RECORD NO. sub-field (#9000001.41) of the PATIENT/IHS File (#9000001) LOC. OF ENCOUNTER field (#.06) of the VISIT File (#9000010) FACILITY field (#.06) of the PROBLEM File (#9000011) NOTE FACILITY field (#.01) of the NOTE FACILITY sub-field (#9000011.11) of the PROBLEM File (#9000011) SITE field (#.01) of the PCC MASTER CONTROL File (#9001000) LOCATION field (#.03) of the TAXONOMY File (#9002226) LOCATION OF ENCOUNTER field (#.18) of the TAXONOMY File (#9002226) CROSS REFERENCED BY: NAME(B) 9999999.06,.01NAME 0;1 POINTER TO INSTITUTION FILE (#4) (Required) INPUT TRANSFORM: S:$D(X) DINUM=X LAST EDITED: APR 2, 1986 DESCRIPTION: This field points to the Institution file (#4) and has the same internal number as that file. Thus, the location has the same name as the Institution file (#4). The location is also referred to as the Facility. NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER CROSS-REFERENCE: 9999999.06^B 1)= S ^AUTTLOC("B",$E(X,1,30),DA)="" 2)= K ^AUTTLOC("B",$E(X,1,30),DA) FILES POINTED TO FIELDS INSTITUTION (#4) NAME (#.01) INPUT TEMPLATE(S): PRINT TEMPLATE(S): SORT TEMPLATE(S): STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING DETAILS: This DBIA allows PXPT to become the custodial package for the 9999999.06 file in the VA. EDITOR: BLOCKER,DAVE NUMBER: 1005 IA #: 1005 FILE NUMBER: 9999999.27 GLOBAL ROOT: AUTNPOV DATE CREATED: SEP 24, 1994 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1005 ID: AUTNPOV GENERAL DESCRIPTION: The PCE Patient/IHS Subset package (PXPT) requests a DBIA to distribute the Indian Health Services Provider Narrative File (9999999.27) in the VA. There have been two new fields added by the VA on the 757 node. These two fields are used for 1)documenting the clinical lexicon which could be used to represent the provider narrative, and 2) determining the context of the narrative when it was entered into the Provider Narrative File. The originating file will be populated by the VA Problem List and PCE. The clinical lexicon field will be populated in the future as provider narratives get mapped to clinical lexicon expressions. STANDARD DATA DICTIONARY #9999999.27 -- PROVIDER NARRATIVE FILE 09/14/94 PAGE 1 STORED IN ^AUTNPOV( (275 ENTRIES) SITE: SLC UCI: DVA,DEV (VERSION 93.2) DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE -------------------------------------------------------------------------- This file contains each unique POV NARRATIVE QUALIFIER. DD ACCESS: @ DEL ACCESS: @ AUDIT ACCESS: @ POINTED TO BY: PROVIDER NARRATIVE field (#.04) of the V POV File (#9000010.07) PROVIDER NARRATIVE CATEGORY field (#80201) of the V POV File (#9000010.07) PROVIDER NARRATIVE field (#.04) of the V PROCEDURE File (#9000010.08) PROVIDER NARRATIVE field (#.06) of the V TREATMENT File (#9000010.15) PROVIDER NARRATIVE CATEGORY field (#80201) of the V TREATMENT File (#9000010.15) PROVIDER NARRATIVE field (#.04) of the V CPT File (#9000010.18) PROVIDER NARRATIVE CATEGORY field (#80201) of the V CPT File (#9000010.18) PROVIDER NARRATIVE field (#.05) of the PROBLEM File (#9000011) PROVIDER NARRATIVE field (#.04) of the PERSONAL HISTORY File (#9000013) PROVIDER NARRATIVE field (#.04) of the FAMILY HISTORY File (#9000014) CROSS REFERENCED BY: NARRATIVE(B), MNEMONIC(B) 9999999.27,.01NARRATIVE 0;1 FREE TEXT (Required) INPUT TRANSFORM: K:$L(X)>80!($L(X)<2)!'(X'?1P.E)!(X'?.ANP) X LAST EDITED: JUL 20, 1987 HELP-PROMPT: ANSWER MUST BE 2-80 CHARACTERS IN LENGTH DESCRIPTION: This is the Narrative that the provider has written out that is his description of what he treated the patient for. Enter a 2 to 80 character description. CROSS-REFERENCE: 9999999.27^B 1)= S ^AUTNPOV("B",$E(X,1,30),DA)="" 2)= K ^AUTNPOV("B",$E(X,1,30),DA) 9999999.27,8801MNEMONIC 88;1 FREE TEXT INPUT TRANSFORM: K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>2!($ LAST EDITED: DEC 16, 1985 HELP-PROMPT: ANSWER MUST BE 1-2 CHARACTERS IN LENGTH DESCRIPTION: This is a mnemonic that stands for this provider narrative. Enter a 1-2 character mnemonic. Enter a 1-2 character mnemonic. CROSS-REFERENCE: 9999999.27^B^MNEMONIC 1)= S ^AUTNPOV("B",$E(X,1,30),DA)=1 2)= K ^AUTNPOV("B",$E(X,1,30),DA) 9999999.27,75701CLINICAL LEXICON 757;1 POINTER TO EXPRESSIONS FILE (#757.01) LAST EDITED: MAY 25, 1994 DESCRIPTION: This is the clinical expression related to the provider narrative. TECHNICAL DESCR: This field will be primarily populated by the Problem List package. 9999999.27,75702ORIGINATING FILE 757;2 FREE TEXT INPUT TRANSFORM: K:$L(X)>15!($L(X)<1) X LAST EDITED: MAY 25, 1994 DESCRIPTION: This field is used in the VA to identify what file pointing to the provider narrative file created the entry in the Provider Narrative File. This may be useful as more packages create pointers to the Provider Narrative File to store the local capture of provider terminology. The Problem List package puts its free text file number in this field when it adds provider narratives to the Provider Narrative File. HELP FRAME: INPUT TEMPLATE(S): PRINT TEMPLATE(S): SORT TEMPLATE(S): STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING DETAILS: This DBIA allows the Patietn/IHS Subset (PXPT) to be the custodial package for distributing the file 9999999.27 in the VA. NUMBER: 1006 IA #: 1006 DATE CREATED: SEP 24, 1994 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: AUTNPOV NAME: DBIA1006 ID: AUTNPOV GENERAL DESCRIPTION: The PCE Patient/IHS Subset package (namespaced PXPT) requests a DBIA with the Indian Health Service to distribute the AUTNPOV routine with the PXPT package. The PXPT package will distribute it as PXPTNPOV and use ZOSF to load and save the routine as AUTNPOV. There have been no coding changes to the AUTNPOV code by the VA. This is the same version that is at Tucson VAMC running as of September 4, 1994. This routine is called by the .01 Narrative field input transform on any lookup of the Provider Narrative File (9999999.27). The Provider Narrative File is distributed with the PXPT package and has a File type DBIA for distribution of the Provider Narrative File in the VA. The Provider Narrative file is used by the VA's Problem List Package and by the PCE package. AUTNPOV ; PROVIDER NARRATIVE TRUE INPUT TRANSFORM ;;92.1;IHS STANDARD DICTIONARIES;;NOV 13, 1991 ; START ; Q:'$D(APCDOVRR) I X="=",$D(APCDTNQP) S X=APCDTNQP Q:X?.E1C.E I $L(X)>30,$D(^AUTNPOV("B",X)) S X="`"_$O(^(X,0)) Q S AUTNPOVX=$E(X,1,30) F AUTNPOVY=0:0 S AUTNPOVY=$O(^AUTNPOV("B",AUTNPOVX, AUTNPOVY)) Q:'AUTNPOVY Q:$P(^AUTNPOV(AUTNPOVY,0),U,1)=X S X=$S(AUTNPOVY:"`"_AUTNPOVY,$E(X)="`":X,$E(X)="""":X,1:"""" _X_"""") K AUTNPOVX,AUTNPOVY Q The following routine (PXPTNPOV) is a PXPT version of AUTNPOV that is being distributed to the field. When the ZOSF("SAVE") is completed, the AUTNPOV routine will appear as displayed above. PXPTNPOV ; SLC/DLT - Provider Narrative True Input Transform for Export ;1/22/94 14:48 ;;1.0V1;PCE PATIENT/IHS SUBSET (PXPT);;Sept 7, 1994 AUTNPOV ; IHS/LB - PROVIDER NARRATIVE TRUE INPUT TRANSFORM ;;92.1;IHS STANDARD DICTIONARIES;;NOV 13, 1991 ; START ; Q:'$D(APCDOVRR) I X="=",$D(APCDTNQP) S X=APCDTNQP Q:X?.E1C.E I $L(X)>30,$D(^AUTNPOV("B",X)) S X="`"_$O(^(X,0)) Q S AUTNPOVX=$E(X,1,30) F AUTNPOVY=0:0 S AUTNPOVY=$O(^AUTNPOV("B",AUTNPOVX, AUTNPOVY)) Q:'AUTNPOVY Q:$P(^AUTNPOV(AUTNPOVY,0),U,1)=X S X=$S(AUTNPOVY:"`"_AUTNPOVY,$E(X)="`":X,$E(X)="""":X,1:"""" _X_"""") K AUTNPOVX,AUTNPOVY Q STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING DETAILS: This DBIA allows the Patient/IHS Subset (PXPT) to distribute the routine AUTNPOV for use in the VA. NUMBER: 1013 IA #: 1013 DATE CREATED: OCT 05, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: %ZOSV NAME: DOLRO LINE TAG IN ROUTINE %ZOSV ID: %ZOSV GENERAL DESCRIPTION: In the FileMan MUMPS OS file, we use code that does routine DOLRO^%ZOSV to save the local symbol table. This entry point is not documented. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12181956 COMPONENT/ENTRY POINT: DOLRO COMPONENT DESCRIPTION: Save local symbol table. SUBSCRIBING PACKAGE: VA FILEMAN ISC: Oakland NUMBER: 1014 IA #: 1014 GLOBAL ROOT: %ZOSF( DATE CREATED: OCT 05, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: SET PIECE OF %ZOSF GLOBAL ID: %ZOSF( GLOBAL REFERENCE: %ZOSF('OS') GENERAL DESCRIPTION: FileMan sets the second piece of ^%ZOSF("OS") equal to the record number selected from the FileMan MUMPS OS file during DINIT. This second piece acts like a pointer to the MUMPS OS file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12181887 SUBSCRIBING PACKAGE: VA FILEMAN ISC: Oakland NUMBER: 1015 IA #: 1015 DATE CREATED: APR 03, 2003 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SDCOU2 NAME: DBIA1015 ID: SDCOU2 GENERAL DESCRIPTION: Integrated Billing requests use of the function $$EXOE^SDCOU2. The purpose of the function is to determine whether the classification questions should be asked for a specific outpatient encounter. IB needs to know whether the classification questions were not asked of patients who have claimed exposures, so that a message may be sent to the Category C Billing mailgroup to alert MCCR personnel to manually review whether that particular encounter was actually related to the veteran's claimed exposures. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12194983 COMPONENT/ENTRY POINT: $$EXOE(X) COMPONENT DESCRIPTION: This entry point is used to determine if an outpatient encounter in file #409.68 is exempt from classification. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: X is a pointer to the outpatient encounter in file #409.68 for which the classification decision is to be made VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Y is the output of the function. The function returns a zero if the encounter is not exempt from asking the classification questions, or a one if the encounter is exempt from classification. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany DBA Comments: RESTORED FROM RETIRED AS PER ANY HARPER DATE ACTIVATED: MAR 15, 2007 DATE/TIME EDITED: MAR 15, 2007@21:00 ACTION: APPROVED AT THE REQUEST OF: HARPER,AMY WITH CONCURRENCE OF: WOLF,ED NUMBER: 1016 IA #: 1016 DATE CREATED: OCT 17, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIR0 NAME: FIELD EDITOR - EN~DIR0() ID: DIR0 GENERAL DESCRIPTION: Kernel needs to use the screen-oriented field editor for the character based GUI emulation module. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12207264 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: This procedure initiates a screen-oriented read. The editing window appears in reverse video. On exit, the field editor writes the final text in high intensity. VARIABLES: ROW TYPE: Input VARIABLES DESCRIPTION: The $Y position of the editing window. The default value is 0. VARIABLES: COL TYPE: Input VARIABLES DESCRIPTION: The $X position of the first column of the editing window. The default is 0. VARIABLES: WIDTH TYPE: Input VARIABLES DESCRIPTION: The width (number of characters) of the editing window. The default value is IOM-COL-1. VARIABLES: HEIGHT TYPE: Input VARIABLES DESCRIPTION: The height (number of lines) of the editing window. The default value is 1. If HEIGHT is greater than 1, the editing window will not scroll horizontally. VARIABLES: DEF TYPE: Input VARIABLES DESCRIPTION: The text to initially display in the editing window. The default value is null. VARIABLES: MAX TYPE: Input VARIABLES DESCRIPTION: The maximum number of characters that can be entered into the editing window. If HEIGHT is 1, the default value is 245 and the editing window can scroll horizontally. If HEIGHT is greater than 1, MAX can be no larger than WIDTH*HEIGHT-1. VARIABLES: IP TYPE: Input VARIABLES DESCRIPTION: The initial location of the cursor (the Insertion Point) within the default answer DEF. The default value is 1. VARIABLES: MAP TYPE: Both VARIABLES DESCRIPTION: This input array can be used to disable or override the default key sequences of the field editor, or to define customized key sequences with associated associated entry points. This array is passed by reference, and its contents are changed by the call. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: Control the way field editor operates. The values and effects are: K Keep screen handling variables. Makes subsequent calls more efficient. P Don't Paint the answer upon exit. T On exit, turn Terminators on and Echo off. W On exit, keep autoWrap mode off, type ahead on, and right margin at 0. r Right justify the answer upon exit. VARIABLES: ANSWER TYPE: Both VARIABLES DESCRIPTION: The text entered by the user. If a time-out occured, ANSWER is equal to the DEF input parameter. VARIABLES: CODE TYPE: Both VARIABLES DESCRIPTION: This variable consists of one or two up arrow (^)-pieces. The first ^-piece of CODE is a mnemonic code that indicates the key(s) the user pressed to terminate the field editor. The second ^-piece of CODE is 1 if the user made any modifications to the default value, even if the net result of series of modifications leaves the value effecitvely unchanged. If no modi- fications were made, the second ^-piece of CODE is 0. (This info corresponds to the MWAPI CHANGED element attribute.) VARIABLES: COMPONENT/ENTRY POINT: UPDATE COMPONENT DESCRIPTION: This procedure can be called from within the entry points defined in the MAP input variable to EN^DIR0. It can be used to change the value of the current answer and the cursor position within the current answer. VARIABLES: NEW_VALUE TYPE: Input VARIABLES DESCRIPTION: The new value of the current answer. If this parameter is not passed in, then the current answer is unchanged. VARIABLES: NEW_IP TYPE: Input VARIABLES DESCRIPTION: The insertion point within NEW_VALUE. If NEW_IP is not passed in, then the insertion point is not changed. If NEW_IP is less than 1, then a value of 1 is assumed. If NEW_IP is greater than the length of NEW_VALUE plus 1, a NEW_IP value of $L(NEW_VALUE)+1 is assumed. SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 1017 IA #: 1017 DATE CREATED: OCT 07, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIFROMSU NAME: CALLS TO FILEMAN FOR KIDS ID: DIFROMSU GENERAL DESCRIPTION: Kernel Installation and Distribution System needs to call the FileMan DIFROMSU Server routine. This call is used during the build and installation of a package. VIEWER: SCHLEHUBER,CAMERON VIEWER: DIMICELI,RON VIEWER: MALMROSE,CARY VIEWER: WINN,TAMI VIEWER: MARSHALL,RICK VIEWER: HOYE,MAUREEN VIEWER: LALIBERTE,DAVID VIEWER: MANAPSAL,DANILA VIEWER: OGI,MICHAEL VIEWER: CREAVEN,DONALD P STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12744309 COMPONENT/ENTRY POINT: FIA VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: File number VARIABLES: INPUT ROOT TYPE: Input VARIABLES DESCRIPTION: Closed array root which contains a list of field numbers to be exported. VARIABLES: TARGET ROOT TYPE: Input VARIABLES DESCRIPTION: Closed array root which will be used to place entries into a FIA structure. VARIABLES: ANSWERS TYPE: Input VARIABLES DESCRIPTION: List of answers, delimited by "^" VARIABLES: DD SCREEN TYPE: Input VARIABLES DESCRIPTION: Screen logic that sets $T VARIABLES: DATA SCREEN TYPE: Input VARIABLES DESCRIPTION: Screen logic that sets $T VARIABLES: VERSION TYPE: Input VARIABLES DESCRIPTION: Version number SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 1019 IA #: 1019 FILE NUMBER: 3.6 GLOBAL ROOT: XMB(3.6, DATE CREATED: OCT 07, 1994 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: BULLETIN FILE ID: XMB(3.6, GLOBAL REFERENCE: XMB(3.6, FIELD NUMBER: ALL ACCESS: Direct Global R/W & w/Fileman GENERAL DESCRIPTION: Kernel Installation and Distributions System needs to update the Bulletin file, 3.6. KIDS needs to extract data from this file during Package transportations. KIDS also needs to update this file during Package installation. STATUS: Active SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 1020 IA #: 1020 FILE NUMBER: 442 GLOBAL ROOT: PRC DATE CREATED: OCT 23, 1998 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PBM ID: PRC GLOBAL REFERENCE: PRC(442,D0,0) FIELD NUMBER: 1 FIELD NAME: FCP LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: .01 FIELD NAME: PURCHASE ORDER NUMBER LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: COST CENTER LOCATION: 0;5 ACCESS: Read w/Fileman GLOBAL REFERENCE: PRC(442,D0,2,D1,0) FIELD NUMBER: 3 FIELD NAME: UNIT OF PURCHASE LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 5 FIELD NAME: ACTUAL UNIT COST LOCATION: 0;9 ACCESS: Read w/Fileman FIELD NUMBER: 3.1 FIELD NAME: PACKAGING MULTIPLE LOCATION: 0;12 ACCESS: Read w/Fileman FIELD NUMBER: 9.5 FIELD NAME: NSN LOCATION: 0;13 ACCESS: Read w/Fileman FIELD NUMBER: 9.3 FIELD NAME: NATIONAL DRUG CODE LOCATION: 0;15 ACCESS: Read w/Fileman FIELD NUMBER: 40 FIELD NAME: ITEM LOCATION: 0 ACCESS: Read w/Fileman FIELD NUMBER: .01 FIELD NAME: LINE ITEM NUMBER LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1.5 FIELD NAME: ITEM MASTER FILE NO. LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 9 FIELD NAME: VENDOR STOCK NUMBER LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 10 FIELD NAME: 2237 REFERENCE # LOCATION: 0;10 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: Quantity LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 3.5 FIELD NAME: BOC LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: 5.5 FIELD NAME: Est. Unit Cost LOCATION: 0;7 ACCESS: Read w/Fileman FIELD NUMBER: 3.2 FIELD NAME: Item Delivery Points LOCATION: 0;8 ACCESS: Read w/Fileman FIELD NUMBER: 3.6 FIELD NAME: Intermediate Product Code LOCATION: 0;11 ACCESS: Read w/Fileman FIELD NUMBER: 9.6 FIELD NAME: Maximum Order Qty LOCATION: 0;14 ACCESS: Read w/Fileman FIELD NUMBER: 9.4 FIELD NAME: SKU LOCATION: 0;16 ACCESS: Read w/Fileman FIELD NUMBER: 9.7 FIELD NAME: Unit Conversion Factor LOCATION: 0;17 ACCESS: Read w/Fileman GLOBAL REFERENCE: PRC(442,D0,2,D1,1,D2,0) FIELD NUMBER: .01 FIELD NAME: DESCRIPTION LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: PRC(442,D0,2,D1,2) FIELD NUMBER: 11 FIELD NAME: QUANTITY PREVIOUSLY RECEIVED LOCATION: 0;8 ACCESS: Read w/Fileman GLOBAL REFERENCE: PRC(442,D0,1) FIELD NUMBER: 5 FIELD NAME: VENDOR LOCATION: 1;1 ACCESS: Read w/Fileman FIELD NUMBER: .1 FIELD NAME: P.O.Date LOCATION: 1;15 ACCESS: Read w/Fileman GLOBAL REFERENCE: PRC(442,D0,7) FIELD NUMBER: .5 FIELD NAME: SUPPLY STATUS LOCATION: 7;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: All the fields are read from the file using Fileman calls, except the P.O. DATE. The P.O. DATE's "AB" cross reference is used for sorting purposes. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28108089 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 1021 IA #: 1021 FILE NUMBER: 445 GLOBAL ROOT: PRCP DATE CREATED: JUN 01, 1998 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: D&PPM ID: PRCP GLOBAL REFERENCE: PRCP(445,D0,1,D1,0) FIELD NUMBER: 50 FIELD NAME: DISPENSING UNIT LOCATION: 0;28 ACCESS: Read w/Fileman FIELD NUMBER: 51 FIELD NAME: DISPENSING UNIT CONV FACTOR LOCATION: 0;29 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27134055 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 1022 IA #: 1022 FILE NUMBER: 420.5 GLOBAL ROOT: PRCD DATE CREATED: OCT 12, 1994 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: D&PPM ID: PRCD GLOBAL REFERENCE: PRCD(420.5,D0,0) FIELD NUMBER: .01 FIELD NAME: UNIT OF PURCHASE LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12673720 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 1023 IA #: 1023 DATE CREATED: OCT 13, 1994 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED ROUTINE: VAQUTL50 NAME: HS Components-PDX Segments ID: VAQUTL50 GENERAL DESCRIPTION: As the Health Summary package adds new components to the HEALTH SUMMARY COMPONENT file (#142.1), it will also add those components to PDX's VAQ - DATA SEGMENT file (#394.71). At this time, Health Summary will only add those components that do not have selection items. Health Summary will use the entry point $$ADDSEG^VAQUTL50() to add it's components to the VAQ - DATA SEGMENT file. Health Summary will also use the entry point $$FIRSTUP^VAQUTL50() to check that the component name is in the uppercase/lowercase naming convention used by PDX. As new components are made available to the PDX users, those components will be added to DBIA297-E (816). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11803215 COMPONENT/ENTRY POINT: $$FIRSTUP(TEXT) COMPONENT DESCRIPTION: INPUT : TEXT - Text string to convert OUTPUT : Text - Same text string with beginning of every word in uppercase and all other characters in lowercase COMPONENT/ENTRY POINT: $$ADDSEG(HSPTR,MAXTIME,MAXOCCUR) COMPONENT DESCRIPTION: INPUT : HSPTR - Pointer to HEALTH SUMMARY COMPONENT file (#142.1) MAXTIME - Max time limit allowed for auto processing MAXOCCUR - Max occurrence limit allowed for auto processing OUTPUT : X - Pointer to VAQ - DATA SEGMENT file (#394.71) that was created -1^ErrorText - Entry not created NOTES : If time and/or occurrence limits do not apply to the component, MAXTIME and/or MAXOCCUR are not required. : If time and/or occurrence limits apply to the component, default values will be taken from the VAQ - PARAMETER file (#394.81). If parameter file does not contain these values, a default of 1 year and 10 occurrences will be used. : If a maximum limit is not valid, the default limit will be used. SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 1024 IA #: 1024 FILE NUMBER: 40.7 GLOBAL ROOT: DIC(40.7, DATE CREATED: OCT 17, 1994 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Health Summary to File 40.7 ID: DIC(40.7, GLOBAL REFERENCE: DIC(40.7,DO,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: This file contains all Clinic Stops and their associated AMIS Stop Code. GENERAL DESCRIPTION: Health Summary accesses file ^DIC(40.7, to display the Name of the Clinic Stop in one of its components. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12295818 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: In the Health Summary component, Clinic Past Visits (CVP), the Clinic Stop is displayed. SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL NUMBER: 1027 IA #: 1027 DATE CREATED: NOV 02, 1994 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA1027 GENERAL DESCRIPTION: Health Summary will distribute the routine, VAQUTL50, under the routine GMTSPDXA. If the routine, VAQUTL50, is not on the system where the components are being loaded, Health Summary will load it's routine, GMTSPDXA and rename it to VAQUTL50. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11803215 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 1030 IA #: 1030 DATE CREATED: NOV 09, 1994 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOBBC NAME: DBIA1030-A ORIGINAL NUMBER: 1030 ID: PSOBBC GENERAL DESCRIPTION: These entry points can be used to batch process prescriptions received via telecommunications. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18024801 COMPONENT/ENTRY POINT: ASK VARIABLES: PSOINST TYPE: Input VARIABLES DESCRIPTION: This is the site number for the site running the Outpatient Pharmacy package. VARIABLES: PSOBBC("QFLG") TYPE: Both VARIABLES DESCRIPTION: This flag is set equal to 0 as input and equal to 1 as output if an up-arrow is entered or timeout occurs at the Suspense, Inpatient, or Early Refill prompts. VARIABLES: PSOBBC("DFLG") TYPE: Both VARIABLES DESCRIPTION: This flag is set equal to 0 as input and equal to 1 as output if an up-arrow, null, or erroneous data is entered or if timeout occurs at the Fill Date, Mail/Window, or Clerk prompts. VARIABLES: PSOBBC("FROM") TYPE: Input VARIABLES DESCRIPTION: This must be set equal to REFILL. Otherwise the telephone refills will not be processed. COMPONENT/ENTRY POINT: PROCESSX VARIABLES: PSOBBC("QFLG") TYPE: Input VARIABLES DESCRIPTION: This flag, if set equal to 1, will result in this entry point being called to queue labels to print and clean up variables. COMPONENT/ENTRY POINT: PT VARIABLES: PSODFN TYPE: Output VARIABLES DESCRIPTION: This is the pointer to the Patient file for the patient. VARIABLES: PSOBBC("DFLG") TYPE: Both VARIABLES DESCRIPTION: This flag is set equal to 0 as input and equal to 1 as output if the patient is either an Inpatient, Nursing Home Patient, or Deceased. COMPONENT/ENTRY POINT: REFILL VARIABLES: PSOBBC("DONE") TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number of the prescription. VARIABLES: PSOBBC("DFLG") TYPE: Both VARIABLES DESCRIPTION: This flag is set equal to 0 as input and to 1 as output if the refill is not successful. COMPONENT/ENTRY POINT: PTC COMPONENT DESCRIPTION: This entry point does some checks on the patient to see if a prescription can be refilled for this patient. VARIABLES: PSODFN TYPE: Input VARIABLES DESCRIPTION: This is the pointer to the Patient File for the patient. This value remains unchanged. VARIABLES: PSOBBC(DFLG) TYPE: Output VARIABLES DESCRIPTION: Upon return from PTC^PSOBBC, the variable PSOBBC("DFLG") will be equal to 1 if the prescription cannot be filled for any of the following 3 reasons. 1)The patient has died. 2)The patient is an inpatient, and inpatient fills are currently not allowed through this process. 3)The patient is in a Contract Nursing Home, and Contract Nursing Home fills are currently not allowed through this process. SUBSCRIBING PACKAGE: VENDOR - AUDIOFAX, INC. SUBSCRIBING PACKAGE: VENDOR - TECHPRO SYSTEMS INC NUMBER: 1031 IA #: 1031 DATE CREATED: OCT 20, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGSEC NAME: DBIA1031 ID: DGSEC GENERAL DESCRIPTION: The PDX application is granted permission to use the function call $$LOADXMY^DGSEC() in order to place the mail group contained in the SENSITIVE REC ACCESSED GROUP field (#509) of the MAS PARAMETER file (#43) into the array XMY. Input: None Output: 0 = Successfully created XMY("G.MailGroup")="" where MailGroup is text value of mail group pointed to by field #509 of file #43 -1^ErrorText = Error STATUS: Active COMPONENT/ENTRY POINT: $$LOADXMY SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Albany NUMBER: 1032 IA #: 1032 DATE CREATED: OCT 21, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DPTLK NAME: DBIA1032 ID: DPTLK GENERAL DESCRIPTION: The PXPT - PCE Patient/IHS subset package requests persmission to include the routine DPTLK as the LOOK-UP PROGRAM for the Patient/IHS file that is being distributed in the VA for use by PCE. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City NUMBER: 1033 IA #: 1033 FILE NUMBER: 9000010 GLOBAL ROOT: AUPNVSIT( DATE CREATED: OCT 18, 1994 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1033 ID: AUPNVSIT( GENERAL DESCRIPTION: Requesting permission to export the Visit File with the release of Visit Tracking V2.0. File Global Number ----- ------ -------- VISIT AUPNVSIT( 9000010 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12338237 SUBSCRIBING PACKAGE: VISIT TRACKING ISC: Dallas NUMBER: 1034 IA #: 1034 FILE NUMBER: 3.9 GLOBAL ROOT: XMB(3.9, DATE CREATED: OCT 18, 1994 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: FILEGRAMS use of MESSAGE file ID: XMB(3.9, GLOBAL REFERENCE: XMB(3.9,D0,0) GLOBAL DESCRIPTION: In ^DIFGO we display the subject online from the 0 node of message file GLOBAL REFERENCE: XMB(3.9,D0,2,D) GLOBAL DESCRIPTION: In ^DIFGO we $O through the text lines in the message at one place to display the text, and in another place to process the Filegram contents. GENERAL DESCRIPTION: VA FileMan looks directly at the MESSAGE file in processing FILEGRAMS. FM is requesting the DBIA for FM Version 21. We will include the migration of the Filegram processor to use the SERVER protocol to our V22 to-do-list; it will then be prioritized along w/ the n number of things already planned for V22. STATUS: Active DURATION: Next Version MAIL MESSAGE: 12340275 GOOD ONLY FOR VERSION: 21 SUBSCRIBING PACKAGE: VA FILEMAN ISC: Oakland NUMBER: 1036 IA #: 1036 FILE NUMBER: 58.8 GLOBAL ROOT: PSD(58.8 DATE CREATED: NOV 17, 1994 CUSTODIAL PACKAGE: DRUG ACCOUNTABILITY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1036 ID: PSD(58.8 GLOBAL REFERENCE: PSD(58.8,'AOP', FIELD NUMBER: 20 FIELD NAME: OUTPATIENT SITE LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSD(58.8,D0,1,D1) FIELD NUMBER: 10 FIELD NAME: DRUG ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Instead of collecting dispensing by looping through the "AL", "AJ", "AM", and "AN" x-refs in the outpatient ^PSRX( global, the dispensing data will be stored on a daily basis in ^XTMP("PSA",. If the Drug Acct. background job is not scheduled, the Outpatient routine will not update ^XTMP("PSA",. If it is scheduled and a Drug Acct. Location for that Outpatient Division is tracking the drug being released or returned to stock, a cumulative total will be updated in ^XTMP("PSA",DIVISION,DRUG,DT). The Drug Acct. background job is intended to be run nightly and will loop thru ^XTMP("PSA", updating Drug Acct. files and then killing off that node in ^XTMP("PSA",. When the job completes, ^XTMP("PSA",0) is updated. This file agreement supports Outpatient direct global reads to ^PSD(58.8, and direct writes to ^XTMP("PSA", in routines PSODISP* and PSORESK*. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12661897 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 1037 IA #: 1037 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: OCT 24, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1037 ID: DPT( GLOBAL REFERENCE: DPT(D0,0) FIELD NUMBER: .082 FIELD NAME: PATIENT MERGED TO LOCATION: 0;19 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: GENERAL DESCRIPTION: The PCE Patient/IHS Subset (PXPT) package request permission to directly access the zeroth node of the ^DPT global for the PATIENT MERGED TO field. This field is checked in screening logic on the PATIENT/IHS file. This field is used by IHS in their PATIENT MERGE application. By documenting this dependency on the PATIENT MERGE TO field by IHS, this agreement serves to show a current dependency based on Joint Sharing of the Patient File (2) and the Patient/IHS file (9000001). The Patient/IHS file is distributed in the VA by the PCE Patient/IHS Subset (PXPT) package. When the VA determines how it will use the PATIENT MERGE TO field, a modification to this agreement may be needed. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany NUMBER: 1038 IA #: 1038 FILE NUMBER: 59.4 GLOBAL ROOT: PS(59.4, DATE CREATED: OCT 27, 1994 CUSTODIAL PACKAGE: CONTROLLED SUBSTANCES CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1038-A ORIGINAL NUMBER: 1038 ID: PS(59.4, GLOBAL REFERENCE: PS(59.4,D0,0) FIELD NUMBER: 31 FIELD NAME: IS SITE SELECTABLE FOR CS? LOCATION: 0;31 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Should this site name be shown for use by the Controlled Substances module of the Pharmacy software? If you answer "YES", the software will display or allow you to pick this site name for Controlled Substances. If you answer "NO", the software will screen out the site name so that CS users will not see or be able to select the site name while in the CS package. GENERAL DESCRIPTION: Controlled Substances Version 2.0 exports field #31 from INPATIENT SITE file #59.4. Inpatient Medications will remain custodian of the file and will provide clean up of fields * for deletion in Version 5.0. At that time, Controlled Substances will become custodian of this File 59.4. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12096728 SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 1039 IA #: 1039 FILE NUMBER: 4 GLOBAL ROOT: DIC(4, DATE CREATED: OCT 24, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1039 ID: DIC(4, GLOBAL REFERENCE: DIC(4,D0) GENERAL DESCRIPTION: The PCE Patient/IHS Subset (PXPT) package requests permission to directly access the Institution file. This direct access is needed to setup the IHS Location file (9999999.06), which is DINUMed to the Institution File. The Location file is distributed by the PXPT package to support the Visit file and Problem List files which are jointly shared files between the VA and IHS. The direct access is referencing the internal entry number, without actually looking at any fields in the Institution file. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany NUMBER: 1040 IA #: 1040 DATE CREATED: OCT 24, 1994 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMAH NAME: LIST INDEX OF MESSAGE RESPONSES ID: XMAH GENERAL DESCRIPTION: This API may be called in a roll and scroll mode to list the responses of a message. STATUS: Active MAIL MESSAGE: 12340275 COMPONENT/ENTRY POINT: ENT8 COMPONENT DESCRIPTION: Display an index of the responses to a message. The index is either in forward or reverse order, depending on personal preference. The index includes the response number, the date of the response, the sender of the response, and the number of lines in the response. (The index is exactly what one would see in MailMan upon responding with "??" to the prompt: "Backup to which response?") Usage: S XMZ=Message IEN D ENT8^XMAH Example: S XMZ=100328 D ENT8^XMAH There are 3 responses. Response 0 is the original message. Response.....From...........Lines 3) 13 May 99 USER,TWO 6 2) 27 Apr 99 USER,ONE 3 1) 21 Apr 99 USER,TWO 3 0) 07 Apr 99 USER,ONE 1 VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the MESSAGE file (#3.9) of the message for which the response index should be displayed. NUMBER: 1043 IA #: 1043 FILE NUMBER: 59.4 GLOBAL ROOT: PS(59.4, DATE CREATED: OCT 27, 1994 CUSTODIAL PACKAGE: CONTROLLED SUBSTANCES CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1038-B ORIGINAL NUMBER: 1038 ID: PS(59.4, GLOBAL REFERENCE: PS(59.4,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 31 FIELD NAME: IS SITE SELECTABLE FOR CS? LOCATION: 0;31 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Controlled Substances Version 2.0 utilizes INPATIENT SITE file #59.4 to distinguish which sites are flagged for CS use. Inpatient Medications will remain custodian of the file and will provide clean up of fields * for deletion in Version 5.0. At that time, Controlled Substances will become custodian of this File 59.4. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12096728 SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 1044 IA #: 1044 DATE CREATED: OCT 27, 1994 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: AUPNVSIT NAME: DBIA1044 ID: AUPNVSIT GENERAL DESCRIPTION: Visit Tracking V2.0 request permission to export the AUPNVSIT routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11069756 SUBSCRIBING PACKAGE: VISIT TRACKING ISC: Dallas NUMBER: 1045 IA #: 1045 FILE NUMBER: 355.1 GLOBAL ROOT: IBE(355.1 DATE CREATED: OCT 28, 1994 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1045 ID: IBE(355.1 GLOBAL REFERENCE: IBE(355.1,D0,0) => 1st piece FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: GLOBAL DESCRIPTION: Standard types of plans that an insurance company may provide. GENERAL DESCRIPTION: IVM Center software utilizes the Type of Plan File (#355.1) to correctly categorize insurance policies identified through the IVM verification process. The type of plan (derived from file 355.1) is transmitted from the IVM Center database via HL7 IN1 (Insurance) Segment to DHCP facilities for insurance policies identified for veterans. The Type of Plan file is pointed to by an IVM specific file (IVM Verified Insurance - #300.122) -- local entries are not added (file 355.1 is utilized for reference purposes only). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12460101 SUBSCRIBING PACKAGE: INCOME VERIFICATION NAT'L DB NUMBER: 1046 IA #: 1046 DATE CREATED: OCT 28, 1994 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBARXEU1 NAME: DBIA1046 ID: IBARXEU1 GENERAL DESCRIPTION: This function returns the value of various VA pension rates. These values are date sensitive and vary depending upon the number of dependents that a veteran has. These pension values are compared with the veteran's income to determine the veteran's eligibility for the medication copayment. This function is used primarily as an internal utility for Integrated Billing during the process of determining a veteran's medication copayment exemption status, but is also accessible to a limited number of applications for the purpose of accessing and displaying these values as they would apply to a specific veteran. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33243000 COMPONENT/ENTRY POINT: $$THRES(DATE,TYPE,DEPEND) COMPONENT DESCRIPTION: This function is used to retrieve a specific type of VA pension value based upon an effective date and the number of dependents that the veteran can claim. VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: This variable contains the date, in internal FileMan format, on which the requested rate must be effective. VARIABLES: TYPE TYPE: Input VARIABLES DESCRIPTION: This variable describes the type of pension for which a value is requested. The value of this variable must equal one of the two following codes: 1 = Basic Pension 2 = Pension plus Aid & Attendance VARIABLES: DEPEND TYPE: Input VARIABLES DESCRIPTION: This variable contains the number of dependents that a veteran can claim. VARIABLES: OUT TYPE: Output VARIABLES DESCRIPTION: The output of this function is of the form 1^2^3, where: 1 = Pension Rate. This is the pension rate of the required type on the requested date, taking into account the number of dependents that the veteran has. This value will be null if a rate cannot be determined. 2 = Effective Date. This is the date on which the pension rate returned above initally became effective. 3 = Prior Year Date. This value is optionally returned. If the Effective Date of the pension rate is over one year in the past, this date is returned as the Prior Year Date to indicate that the pension rate has been effective for over a year and may no longer be the most current rate. SUBSCRIBING PACKAGE: INCOME VERIFICATION NAT'L DB SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL SUBSCRIBING DETAILS: Checking the last Means test or RX Copay Test is within the last 365 days and if so displaying the income on the Bene Travel screen. It is also used as one of the factors in whether or not the patients Bene Travel copay is waived. DBA Comments: 2/8/13-MM: Added Beneficiary Travel as a subscriber for patch DGBT*1*20. DATE/TIME EDITED: FEB 08, 2013@09:19 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: DELLINGER,BARRY WITH CONCURRENCE OF: HARPER,AMY NUMBER: 1049 IA #: 1049 FILE NUMBER: 19.1 GLOBAL ROOT: DIC(19.1 DATE CREATED: NOV 04, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PNs use of Security Key file (19.1) ID: DIC(19.1 GENERAL DESCRIPTION: Progress Notes is adding field #.05 SECURITY KEY to the GENERIC PROGRESS NOTE TITLE file (121.2). This field will point to the SECURITY KEY file (19.1) This is being done to implement functionality requested in E3R 4858 and will be exported in patch GMRP*2.5*29. Many services use the Progress Notes package. Sites will now have the option to restrict entering of new Progress Notes to users that hold the key associated with a particular title. This is accomplished using DIC("S") when creating a new progress note. If a TITLE does not have a security key associated with it, no restriction will apply. This will be particularly useful for sites wanting to control access to the CWAD titles; Crisis Note, Clinical Warning, and Advance Directive. Any existing security key may be used to lock any title. It is entirely at the sites' discretion. This will not in any way impact the display or printing of any notes. The SECURITY KEY field (#.05) entry in GENERIC PROGRESS NOTE TITLE file (121.2) may be edited at any time. This can be accomplished by using the 'GMRPN TITLE MGMT MENU' option. The next version of Progress Notes will utilize the TIU (Text Integration Utility) which will inlude the ASU (Authorization/Subcription Utility). The use of the SECURITY FIELD will no longer be necessary at this time. STATUS: Active DURATION: Next Version MAIL MESSAGE: 12538110 GOOD ONLY FOR VERSION: 2.5 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 1050 IA #: 1050 FILE NUMBER: 42.4 GLOBAL ROOT: DIC(42.4, DATE CREATED: JUL 14, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA909-B ORIGINAL NUMBER: 909 ID: DIC(42.4, CREATOR: KOPP,TERRY M GLOBAL REFERENCE: DIC(42.4,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Obtain name or Specialty FIELD NUMBER: 3 FIELD NAME: SERVICE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Obtain location's service designation. FIELD NUMBER: 5 FIELD NAME: BILLING RATE BEDSECTION LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Obtain location's billing section designation FIELD NUMBER: 6 FIELD NAME: CDR ACCOUNT LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Obtain location's CRD ACCOUNT GLOBAL REFERENCE: DIC(42.4,D1,'E',D0,0) FIELD NUMBER: .02 FIELD NAME: ACTIVE? LOCATION: 0;.02 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DIC(42.4,D1,'E','ADATE', FIELD NUMBER: 10 FIELD NAME: EFFECTIVE DATE LOCATION: E;0 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The laboratory LMIP reports require that workload data be collected based on Facility Treating Specialty #45.7 and Specialty #42.4. We determine this information by looking at the ordering location. We are asking permission to read the these files to obtain .01 field and the field #6 CDR ACCOUNT field for certain reports. The logic uses the ^SC(X,42) to determine if the location is a ward. If it is the n use the Facility Treating specialty pointers to navigate to the data. See DBIA909-A & DBIA909-C. The laboratory package also needs to access the ACTIVE status of the entries in the SPECIALTY file (#42.4). This will be done using direct access via the "ADATE" cross reference of the EFFECTIVE DATE multiple field and extracting the data from the 0-node of the EFFECTIVE DATE multiple. The call will be to ACTV^LRJSDX with the ien of the entry in file 42.4 and optionally an 'as of' date passed into it. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 52734841 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham DATE ACTIVATED: SEP 09, 2010 DATE/TIME EDITED: SEP 09, 2010@10:40 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: KOPP,TERRY DATE/TIME EDITED: SEP 09, 2010@11:55 ACTION: APPROVED AT THE REQUEST OF: KOPP,TERRY WITH CONCURRENCE OF: YORTY,ROBERT NUMBER: 1051 IA #: 1051 FILE NUMBER: 42 GLOBAL ROOT: DIC(42, DATE CREATED: JUL 14, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA909-C ORIGINAL NUMBER: 909 ID: DIC(42, GLOBAL REFERENCE: DIC(42,D0,0) GLOBAL DESCRIPTION: Using the X-reference to determine if the ordering location is in the Ward Location File #42. GENERAL DESCRIPTION: The laboratory LMIP reports require that workload data be collected based on Facility Treating Specialty #45.7 and Specialty #42.4. We determine this information by looking at the ordering location. We are asking permission to read the these files to obtain .01 field and the field #6 CDR ACCOUNT field for certain reports. The logic uses the ^SC(X,42) to determine if the location is a ward. If it is the n use the Facility Treating specialty pointers to navigate to the data. See DBIA909-A & DBIA909-B. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11246997 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 1052 IA #: 1052 DATE CREATED: NOV 07, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIFROMS NAME: DBIA1052-A ORIGINAL NUMBER: 1052 ID: DIFROMS GENERAL DESCRIPTION: Kernel Installation and Distribution System needs to call the FileMan DIFROM Server routines and Compiler routines. These calls are used to update the Data Dictionaries, Templates, Forms, and Functions at a site during the installation of a package. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: DDOUT VARIABLES: TARGET ROOT TYPE: Input VARIABLES DESCRIPTION: Closed array reference where the data will be stored. COMPONENT/ENTRY POINT: DDIN VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: File number VARIABLES: SOURCE ROOT TYPE: Input VARIABLES DESCRIPTION: Closed array reference where the data will be stored. COMPONENT/ENTRY POINT: DATAOUT VARIABLES: TARGET ROOT TYPE: Input VARIABLES DESCRIPTION: Closed array reference where the data will be stored. COMPONENT/ENTRY POINT: DATAIN VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: File number VARIABLES: SOURCE ROOT TYPE: Input VARIABLES DESCRIPTION: Closed array reference where the data will be stored. SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 1053 IA #: 1053 DATE CREATED: NOV 07, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIFROMSO NAME: DBIA1052-B ORIGINAL NUMBER: 1052 ID: DIFROMSO GENERAL DESCRIPTION: Kernel Installation and Distribution System needs to call the FileMan DIFROM Server routines and Compiler routines. These calls are used to update the Data Dictionaries, Templates, Forms, and Functions at a site during the installation of a package. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EDEOUT VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: File number VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal entry number to export VARIABLES: PKGNAME TYPE: Input VARIABLES DESCRIPTION: Package name SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 1054 IA #: 1054 DATE CREATED: NOV 07, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIFROMSI NAME: DBIA1052-C ORIGINAL NUMBER: 1052 ID: DIFROMSI GENERAL DESCRIPTION: Kernel Installation and Distribution System needs to call the FileMan DIFROM Server routines and Compiler routines. These calls are used to update the Data Dictionaries, Templates, Forms, and Functions at a site during the installation of a package. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: FPRE VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: File number VARIABLES: PKGNAME TYPE: Input VARIABLES DESCRIPTION: Package name COMPONENT/ENTRY POINT: EPRE VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: File number VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Interal entry number on target system VARIABLES: PKGNAME TYPE: Input VARIABLES DESCRIPTION: Package name VARIABLES: OLDIEN TYPE: Input VARIABLES DESCRIPTION: Internal entry number on source system COMPONENT/ENTRY POINT: EPOST VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: File number VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal entry number on target system VARIABLES: PKGNAME TYPE: Input VARIABLES DESCRIPTION: Package name SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 1055 IA #: 1055 DATE CREATED: NOV 07, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIEZ NAME: DBIA1052-D ORIGINAL NUMBER: 1052 ID: DIEZ GENERAL DESCRIPTION: Kernel Installation and Distribution System needs to call the FileMan DIFROM Server routines and Compiler routines. These calls are used to update the Data Dictionaries, Templates, Forms, and Functions at a site during the installation of a package. The DIEZ routine is used to recompile input templates in non-interactive mode. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN2 VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal entry number on target system VARIABLES: RTN TYPE: Input VARIABLES DESCRIPTION: Routine name SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 1056 IA #: 1056 DATE CREATED: NOV 07, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIKZ NAME: DBIA1052-E ORIGINAL NUMBER: 1052 ID: DIKZ GENERAL DESCRIPTION: Kernel Installation and Distribution System needs to call the FileMan DIFROM Server routines and Compiler routines. These calls are used to update the Data Dictionaries, Templates, Forms, and Functions at a site during the installation of a package. The DIKZ routine is used to recompile a file's cross-references in non-interactive mode. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN2 VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal entry number on target system VARIABLES: RTN TYPE: Input VARIABLES DESCRIPTION: Routine name SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 1057 IA #: 1057 DATE CREATED: NOV 07, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIPZ NAME: DBIA1052-F ORIGINAL NUMBER: 1052 ID: DIPZ GENERAL DESCRIPTION: Kernel Installation and Distribution System needs to call the FileMan DIFROM Server routines and Compiler routines. These calls are used to update the Data Dictionaries, Templates, Forms, and Functions at a site during the installation of a package. The DIPZ routine is used to recompile print templates in non-interactive mode. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN2 VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal entry number on target system VARIABLES: RTN TYPE: Input VARIABLES DESCRIPTION: Routine name SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 1058 IA #: 1058 DATE CREATED: NOV 07, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DDSUTL NAME: DBIA1052-G ORIGINAL NUMBER: 1052 ID: DDSUTL GENERAL DESCRIPTION: Kernel Installation and Distribution System needs to call two undocumented ScreenMan entry points from the 7.5 node of .01 fields of multiples in the Build file. These entry points are used to inform ScreenMan of subrecords that have been added or deleted during the execution of the 7.5 node. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13547592 COMPONENT/ENTRY POINT: MLOAD VARIABLES: SOURCE ROOT TYPE: Input VARIABLES DESCRIPTION: Closed root of array that contains the record numbers of subrecords that were added. COMPONENT/ENTRY POINT: MDEL VARIABLES: SOURCE ROOT TYPE: Input VARIABLES DESCRIPTION: Closed root of array that contains the record numbers of subrecords that were deleted. SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 1059 IA #: 1059 FILE NUMBER: 1 GLOBAL ROOT: DIC( DATE CREATED: NOV 08, 1994 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: FILE SECURITY CODE ACCESS ID: DIC( GENERAL DESCRIPTION: This integration agreement will allow the MAS package to release a patch to allow sites to review and update file security codes without having to install inits of all files. Due to problems reported in several recent NOIS mesages, we've had cause to review and update our recommended levels of access. We feel this is the best way to get the sites up-to-date. An informal message and a draft copy of the routines has already been submitted to FileMan development for review and concurrence. Our instructions will be that this is a one time only run. No options will be created for this patch. The patch is DG*5.3*49 and is currently under development. We are requesting the ability to view and edit the following nodes in the DIC global: ^DIC(filenum,0,"WR") file write access ^DIC(filenum,0,"DD") file DD access ^DIC(filenum,0,"RD") file read access ^DIC(filenum,0,"DEL") file delete access ^DIC(filenum,0,"LAYGO") file LAYGO access VIEWER: SCHLEHUBER,CAMERON VIEWER: MALMROSE,CARY VIEWER: WRAY,CECELIA A VIEWER: MANAPSAL,DANILA VIEWER: WHELAN,ROBERT E STATUS: Active DURATION: Next Version EXPIRATION DATE: JUN 01, 1995 MAIL MESSAGE: 12262216 GOOD ONLY FOR VERSION: 5.3 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 1061 IA #: 1061 DATE CREATED: NOV 10, 1994 CUSTODIAL PACKAGE: Missing Patient Register CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MPRCHK NAME: PATIENT LOOK-UP CALL TO MPR ID: MPRCHK GENERAL DESCRIPTION: At the request of the MPR (Missing Patient Register) developer, we have added a call to MPRCHK from the security routine Q+2^DGSEC. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN(Y) VARIABLES: Y TYPE: Input VARIABLES DESCRIPTION: Passed as IEN of PATIENT file. SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 1062 IA #: 1062 DATE CREATED: JAN 12, 1995 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: 1062 GENERAL DESCRIPTION: Kernel Toolkit needs this agreement with Fileman to be able to use the variable D0 in DD definitions. Here are some examples of the use of variable D0. 15,99991 LOOKUP1 ; COMPUTED MUMPS CODE: S X="`"_+^VA(15,D0,0) ALGORITHM: S X="`"_+^VA(15,D0,0) DESCRIPTION: This field is used to navigate to the file pointed to by RECORD1. TECHNICAL DESCR: This field is used to navigate to the file pointed to by RECORD1. 15,99992 LOOKUP2 ; COMPUTED MUMPS CODE: S X="`"_+$P(^VA(15,D0,0),U,2) ALGORITHM: S X="`"_+$P(^VA(15,D0,0),U,2) DESCRIPTION: This field is used to navigate to the file pointed to by RECORD2. TECHNICAL DESCR: This field is used to navigate to the file pointed to by RECORD2. 15,99993 LOOKUP3 ; COMPUTED MUMPS CODE: S X="`"_D0 ALGORITHM: S X="`"_D0 LAST EDITED: AUG 08, 1989 DESCRIPTION: This computed field provides navigational capability to any file that points to this file and has a DINUM relationship. TECHNICAL DESCR: This computed field provides navigational capability to any file that points to this file and has a DINUM relationship. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13368155 COMPONENT/ENTRY POINT: D0 COMPONENT DESCRIPTION: This variable is the internal entry number of the current record. VARIABLES: D0 TYPE: Used SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 1064 IA #: 1064 FILE NUMBER: 19.2 GLOBAL ROOT: DIC(19.2 DATE CREATED: NOV 16, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1063-B ORIGINAL NUMBER: 1063 ID: DIC(19.2 GLOBAL REFERENCE: DIC(19.2,D0,0) FIELD NUMBER: 2 FIELD NAME: QUEUED TO RUN AT WHAT TIME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Drug Acct. background job, PSA IV ALL LOCATIONS is scheduled to run before updating ^XTMP("PSA". STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12260762 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham NUMBER: 1067 IA #: 1067 FILE NUMBER: 552.5 GLOBAL ROOT: PSX DATE CREATED: NOV 17, 1994 CUSTODIAL PACKAGE: CMOP CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Pharmacy Benefits Management ID: PSX GLOBAL REFERENCE: PSX(552.5,D0,0) FIELD NUMBER: .01 FIELD NAME: FACILITY LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSX(552.5,D0,1,D1,1,D2,1,D3,0) FIELD NUMBER: .01 FIELD NAME: DRUG ID# LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: TOTAL ORIGINAL FILLS LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: TOTAL REFILLS LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: TOTAL COST LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: TOTAL QUANTITY LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Pharmacy Benefits Management package will extract statistical data on a monthly basis from "HOST" CMOP facilities' file STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30056829 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham EDITOR: BLOCKER,DAVE NUMBER: 1069 IA #: 1069 FILE NUMBER: 405 GLOBAL ROOT: DGPM DATE CREATED: DEC 05, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DS needs WARD AT DISCHARGE ID: DGPM GENERAL DESCRIPTION: Discharge Summary is using the computed field WARD AT DISCHARGE from the PATIENT MOVEMENT FILE in lieu of the location returned in VAIP(17,4) from ^VADPT. DS was having a problem with the value that is returned from VADPT being accurate when the pt was ASIH. The use of this field is being implemented in GMRD*1*2 in rtns GMRDLIBA and GMRDLIBF. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12873551 SUBSCRIBING PACKAGE: DISCHARGE SUMMARY ISC: Salt Lake City NUMBER: 1070 IA #: 1070 DATE CREATED: MAR 30, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTSCU3 NAME: DBIA1070 ID: DGMTSCU3 GENERAL DESCRIPTION: The IVM package files new Means Tests into the PIMS Means Test module. This routine contains utilities for Means Test processing. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14558289 COMPONENT/ENTRY POINT: MT(DGINR,DGMTI) COMPONENT DESCRIPTION: This call is used to update the ANNUAL MEANS TEST field in 408.22 with the Means Test IEN. VARIABLES: DGINR TYPE: Input VARIABLES DESCRIPTION: DGINR is the INCOME RELATION IEN. VARIABLES: DGMTI TYPE: Input VARIABLES DESCRIPTION: DGMTI is the ANNUAL MEANS TEST IEN. SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 1076 IA #: 1076 DATE CREATED: DEC 09, 1994 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAUQWK NAME: VAUQWK ID: VAUQWK CREATOR: INSLEY,MARCIA GENERAL DESCRIPTION: Quick Lookup for Patient Data. STATUS: Active SUBSCRIBING PACKAGE: SCHEDULING EDITOR: BARNSON,TREVA S DATE ACTIVATED: DEC 10, 1994 NUMBER: 1078 IA #: 1078 FILE NUMBER: 121 GLOBAL ROOT: GMR DATE CREATED: DEC 09, 1994 CUSTODIAL PACKAGE: PROGRESS NOTES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1078 ID: GMR GLOBAL REFERENCE: GMR(121, FIELD NUMBER: 30 FIELD NAME: DXLS LOCATION: GMR(121,D0,30) ACCESS: Pointed to FIELD DESCRIPTION: Diagnosis identified for length of stay Used in the Final Discharge Note Summary. GENERAL DESCRIPTION: Mental Health V. 5.01 requests to change Generic Progress Notes file (#121) field DXLS (#30) variable pointer value to point to the new DSM file (#627.7), instead of the DSM-III-R file (#627.5). STATUS: Active DURATION: Next Version MAIL MESSAGE: 12936414 GOOD ONLY FOR VERSION: 5.01 SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas SUBSCRIBING DETAILS: This agreement is needed just for the installation of Mental Health V. 5.01. NUMBER: 1080 IA #: 1080 FILE NUMBER: 55 GLOBAL ROOT: PS( DATE CREATED: DEC 13, 1994 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1079-B ORIGINAL NUMBER: 1079 ID: PS( GLOBAL REFERENCE: PS(55,PATDFN,'P','A',SRCHDT) GLOBAL DESCRIPTION: Used to order through the "A" xref to find RX's GLOBAL REFERENCE: PS(55,PATDFN,1 FIELD NUMBER: 1 FIELD NAME: NARRATIVE ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14262095 SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE ISC: Albany NUMBER: 1087 IA #: 1087 FILE NUMBER: 200 GLOBAL ROOT: VA( DATE CREATED: DEC 13, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1087 ORIGINAL NUMBER: 1087 ID: VA( GLOBAL REFERENCE: VA(200,DUZ,'XQA' GLOBAL DESCRIPTION: ALERT CONTENT/DATA GLOBAL REFERENCE: VA(200,'AXQA' GLOBAL DESCRIPTION: ALERT CROSS REFERENCE GLOBAL REFERENCE: VA(200,'AXQAN' GLOBAL DESCRIPTION: ALERT CROSS REFERENCE GENERAL DESCRIPTION: Agreement for the Notifications component of OE/RR 2.5 to directly access the global ^VA(200. This includes Read/Delete access to the global. VIEWER: MALMROSE,CARY VIEWER: ANDRUS,RUSTY VIEWER: IVEY,JOEL VIEWER: DEFA,TANA VIEWER: MELDRUM,KEVIN STATUS: Active DURATION: Next Version MAIL MESSAGE: 12794026 GOOD ONLY FOR VERSION: 2.5 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 1088 IA #: 1088 DATE CREATED: APR 04, 1995 CUSTODIAL PACKAGE: CMOP CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSXREF NAME: DBIA1088 ID: PSXREF GENERAL DESCRIPTION: When running CMOP and NDF software, NDF has a hook into CMOP in the Rematch/Match Single Drug option. If a drug has been marked to transmit to CMOP through the CMOP package and an individual wants to rematch it, the software will display a message telling the user that it is matched and marked for CMOP. If the user chooses to rematch, the software will kill off the match, unmark it to transmit CMOP. The entry point is REMTCH^PSNHELP. This entry point sets the variable +Y equal to the variable DA. It then calls the CMOP routine PSXREF. This routine sets the proper information into a CMOP activity log multiple in file 50 (subfile 50.0214). In addition, when the software marks or unmarks a drug, it sets field 213 "CMOP DISPENSE" in 50 to a "1" for mark and a "0" for unmark. This field also belongs to CMOP. File 50 is a shared pharmacy file. Each module owns different fields and nodes in this file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12995254 COMPONENT/ENTRY POINT: PSXREF VARIABLES: DA TYPE: Input SUBSCRIBING PACKAGE: NATIONAL DRUG FILE ISC: Birmingham NUMBER: 1089 IA #: 1089 DATE CREATED: JAN 09, 1995 CUSTODIAL PACKAGE: GENERIC CODE SHEET CUSTODIAL ISC: Washington USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GECSCALL NAME: Supported Option File Routines ID: GECSCALL GENERAL DESCRIPTION: This integration agreement contains the entry points supported by the Generic Code Sheet package. For more information on using the supported references, please refer to the Generic Code Sheet Technical Manual. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 10581952 COMPONENT/ENTRY POINT: CREATE COMPONENT DESCRIPTION: Create a Code Sheet Use the OPTION file #19 ENTRY ACTION to call this option using the label 'CREATE' in the 'GECSCALL' routine as follows: S GECSSYS="batch name" D CREATE^GECSCALL VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: Set the GECSSYS variable to the name of the batch type from the GENERIC CODE SHEET BATCH TYPE file #2101.1. COMPONENT/ENTRY POINT: KEY COMPONENT DESCRIPTION: Keypunch a code sheet Use the OPTION file #19 ENTRY ACTION to call this option using the label 'KEY' in the 'GECSCALL' routine as follows: S GECSSYS="batch name" D KEY^GECSCALL VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: Set the GECSSYS variable to the name of the batch type from the GENERIC CODE SHEET BATCH TYPE file #2101.1. COMPONENT/ENTRY POINT: EDITCOD COMPONENT DESCRIPTION: Code Sheet Edit Use the OPTION file #19 ENTRY ACTION to call this option using the label 'EDITCOD' in the 'GECSCALL' routine as follows: S GECSSYS="batch name" D EDITCOD^GECSCALL VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: Set the GECSSYS variable to the name of the batch type from the GENERIC CODE SHEET BATCH TYPE file #2101.1. COMPONENT/ENTRY POINT: BATCH COMPONENT DESCRIPTION: Batch Code Sheets Use the OPTION file #19 ENTRY ACTION to call this option using the label 'BATCH' in the 'GECSCALL' routine as follows: S GECSSYS="batch name" D BATCH^GECSCALL VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: Set the GECSSYS variable to the name of the batch type from the GENERIC CODE SHEET BATCH TYPE file #2101.1. COMPONENT/ENTRY POINT: EDITBAT COMPONENT DESCRIPTION: Batch Edit Use the OPTION file #19 ENTRY ACTION to call this option using the label 'EDITBAT' in the 'GECSCALL' routine as follows: S GECSSYS="batch name" D EDITBAT^GECSCALL VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: Set the GECSSYS variable to the name of the batch type from the GENERIC CODE SHEET BATCH TYPE file #2101.1. COMPONENT/ENTRY POINT: DELCODE COMPONENT DESCRIPTION: Delete Code Sheet Use the OPTION file #19 ENTRY ACTION to call this option using the label 'DELCODE' in the 'GECSCALL' routine as follows: S GECSSYS="batch name" D DELCODE^GECSCALL VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: Set the GECSSYS variable to the name of the batch type from the GENERIC CODE SHEET BATCH TYPE file #2101.1. COMPONENT/ENTRY POINT: RETRAN COMPONENT DESCRIPTION: Mark Batch for Retransmission Use the OPTION file #19 ENTRY ACTION to call this option using the label 'RETRAN' in the 'GECSCALL' routine as follows: S GECSSYS="batch name" D RETRAN^GECSCALL VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: Set the GECSSYS variable to the name of the batch type from the GENERIC CODE SHEET BATCH TYPE file #2101.1. COMPONENT/ENTRY POINT: REBAT COMPONENT DESCRIPTION: Mark code Sheet for Rebatching Use the OPTION file #19 ENTRY ACTION to call this option using the label 'REBAT' in the 'GECSCALL' routine as follows: S GECSSYS="batch name" D REBAT^GECSCALL VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: Set the GECSSYS variable to the name of the batch type from the GENERIC CODE SHEET BATCH TYPE file #2101.1. COMPONENT/ENTRY POINT: REVCODE COMPONENT DESCRIPTION: Review Code Sheet Use the OPTION file #19 ENTRY ACTION to call this option using the label 'REVCODE' in the 'GECSCALL' routine as follows: S GECSSYS="batch name" D REVCODE^GECSCALL VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: Set the GECSSYS variable to the name of the batch type from the GENERIC CODE SHEET BATCH TYPE file #2101.1. COMPONENT/ENTRY POINT: TRANS COMPONENT DESCRIPTION: Transmit Code Sheets Use the OPTION file #19 ENTRY ACTION to call this option using the label 'TRANS' in the 'GECSCALL' routine as follows: S GECSSYS="batch name" D TRANS^GECSCALL VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: Set the GECSSYS variable to the name of the batch type from the GENERIC CODE SHEET BATCH TYPE file #2101.1. COMPONENT/ENTRY POINT: RBATWA COMPONENT DESCRIPTION: Batches Waiting to be Transmitted. Use the OPTION file #19 ENTRY ACTION to call this option using the label 'RBATWA' in the 'GECSCALL' routine as follows: S GECSSYS="batch name" D RBATWA^GECSCALL VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: Set the GECSSYS variable to the name of the batch type from the GENERIC CODE SHEET BATCH TYPE file #2101.1. COMPONENT/ENTRY POINT: RCODEBA COMPONENT DESCRIPTION: Code Sheets Ready for Batching Use the OPTION file #19 ENTRY ACTION to call this option using the label 'RCODEBA' in the 'GECSCALL' routine as follows: S GECSSYS="batch name" D RCODEBA^GECSCALL VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: Set the GECSSYS variable to the name of the batch type from the GENERIC CODE SHEET BATCH TYPE file #2101.1. COMPONENT/ENTRY POINT: RSTATUS COMPONENT DESCRIPTION: Status of all Batches Use the OPTION file #19 ENTRY ACTION to call this option using the label 'RSTATUS' in the 'GECSCALL' routine as follows: S GECSSYS="batch name" D RSTATUS^GECSCALL VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: Set the GECSSYS variable to the name of the batch type from the GENERIC CODE SHEET BATCH TYPE file #2101.1. COMPONENT/ENTRY POINT: PURGE COMPONENT DESCRIPTION: Purge Transmission Records/Code Sheets Use the OPTION file #19 ENTRY ACTION to call this option using the label 'PURGE' in the 'GECSCALL' routine as follows: S GECSSYS="batch name" D PURGE^GECSCALL VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: Set the GECSSYS variable to the name of the batch type from the GENERIC CODE SHEET BATCH TYPE file #2101.1. COMPONENT/ENTRY POINT: STACRETR COMPONENT DESCRIPTION: Retransmit Stack File Document Use the OPTION file #19 ENTRY ACTION to call this option using the label 'STACRETR' in the 'GECSCALL' routine as follows: S GECSSYS="batch name" D STACRETR^GECSCALL For Version 2.0, the only "batch name" which uses the stack file, and therefore this option is FINANCIAL MANAGEMENT. VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: Set the GECSSYS variable to the name of the batch type from the GENERIC CODE SHEET BATCH TYPE file #2101.1. COMPONENT/ENTRY POINT: STACSTAT COMPONENT DESCRIPTION: Stack Status Report Use the OPTION file #19 ENTRY ACTION to call this option using the label 'STACSTAT' in the 'GECSCALL' routine as follows: S GECSSYS="batch name" D STACSTAT^GECSCALL For Version 2.0, the only "batch name" which uses the stack file, and therefore this option is FINANCIAL MANAGEMENT. VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: Set the GECSSYS variable to the name of the batch type from the GENERIC CODE SHEET BATCH TYPE file #2101.1. COMPONENT/ENTRY POINT: COMMENT COMPONENT DESCRIPTION: User Comments Use the OPTION file #19 ENTRY ACTION to call this option using the label 'COMMENT' in the 'GECSCALL' routine as follows: S GECSSYS="batch name" D COMMENT^GECSCALL For Version 2.0, the only "batch name" which uses the stack file, and therefore this option is FINANCIAL MANAGEMENT. VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: Set the GECSSYS variable to the name of the batch type from the GENERIC CODE SHEET BATCH TYPE file #2101.1. NUMBER: 1090 IA #: 1090 DATE CREATED: DEC 14, 1994 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA1090 GENERAL DESCRIPTION: The Medicine developers and the Consult/Request Tracking developers have agreed to remove the GMRCACT NEW PATIENT protocol (child) as an item from the GMRCACTM MEDICINE PKG MENU protocol (parent) in the Consult/ Request Tracking package. The functionality provided in the GMRCACT NEW PATIENT protocol as an item in the GMRCACTM MED PKG MENU is not appropriate within the defined context of the Medicine package and removing this item will ensure that users are not prompted twice for selecting a patient. The routine MCFIXOEP, has been developed and will be included in the pre-installation process for Medicine V2.2 which will remove the protocol item. The Consult/Request Tracking developers will remove the GMRCACT NEW PATIENT protocol item from future versions of Consults. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12508939 SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Washington/Silver Spring NUMBER: 1091 IA #: 1091 DATE CREATED: JAN 05, 1995 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA316-C GENERAL DESCRIPTION: Multi Term Lookup (a component of TOOLKIT) requests the ability to read the "GL" node of ^DIC in order to retrieve a global root. This reference can be found in the routines XTLKEFOP, XTLKKWL, XTLKMGR, XTLKPRT and in the MUMPS X-REF of file 8984.3: CROSS-REFERENCE: 8984.3^AC^MUMPS 1)= I $D(^XT(8984.3,DA,0)),$P(^(0),U,2)'="" S J L=$P(^(0),U,2),JL=$P(^DIC(JL,0,"GL"),U,2),^XT(8 984.3,"AC",JL,$E(X,1,30),DA)="" K JL 2)= I $D(^XT(8984.3,DA,0)),$P(^(0),U,2)'="" S J L=$P(^(0),U,2),JL=$P(^DIC(JL,0,"GL"),U,2) K ^XT (8984.3,"AC",JL,$E(X,1,30),DA),JL Associates the synonym with the global root of the lookup file. ***** Amendment 1/23/95 ***** The above request should be modified to include both Multi-Term Lookup and the Duplicate Resolution modules of Toolkit. The 'GL' node is referenced for the same purpose in file 15.1, field .01, "AGL" x-reference. STATUS: Active DURATION: Next Version MAIL MESSAGE: 13298890 GOOD ONLY FOR VERSION: 7.3 SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 1092 IA #: 1092 DATE CREATED: DEC 20, 1994 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ZISPL NAME: Use of Spooler by Health Summary ID: ZISPL GENERAL DESCRIPTION: The API for PDX to request Health Summary data functions by Spooling Health Summary output into a SPOOL DOCUMENT and transfering the resulting data from ^XMBS(3.519, into an array (usually ^TMP) named by the calling application. This was necessary, given the current design of Health Summary, and the absence of HFS space on the 486 systems. To be portable, the most practical means of generating ASCII output to a MUMPS global was to use the Spooler. To that end, Health Summary requests permission to make direct reference to the SPOOL DOCUMENT (^XMB(3.51,) and SPOOL DATA (^XMBS(3.519,) files to evaluate the status of the Spool Document, and to transfer the resulting text to the target array respectively. We also call the entry points DSD^ZISPL and DSDOC^ZISPL to delete the SPOOL DATA and SPOOL DOCUMENT records once the transfer is successfully completed until otherwise specified. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 8757732 COMPONENT/ENTRY POINT: DSDOC COMPONENT DESCRIPTION: Deletes Spool Document file entry following transfer of data, to minimize consumption of disk space. COMPONENT/ENTRY POINT: DSD COMPONENT DESCRIPTION: Deletes Spool Data file entry following transfer of data, to minimize consumption of data. SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE NUMBER: 1093 IA #: 1093 DATE CREATED: DEC 22, 1994 CUSTODIAL PACKAGE: GENERIC CODE SHEET CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GECSXMAP NAME: DBIA1093-A ORIGINAL NUMBER: 1093 ID: GECSXMAP GENERAL DESCRIPTION: This is a request for an integration agreement between GECS and PIMS. With the changes made in GECS V2.0, the calls made from PIMS no longer were available. The call to GETMAP^GECSXMAP( ) will return variable GECSMAP( ) containing the fields in the GENERIC CODE SHEET file (#2100) that are associated with the code sheet selected. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13147102 COMPONENT/ENTRY POINT: GETMAP COMPONENT DESCRIPTION: Returns GECSMAP containing the fields used in the associated code sheet, among other things. VARIABLES: GECSMAP TYPE: Used VARIABLES DESCRIPTION: Contains the fields used in the associated code sheet, among other things. SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 1094 IA #: 1094 FILE NUMBER: 2100 GLOBAL ROOT: GECS DATE CREATED: DEC 22, 1994 CUSTODIAL PACKAGE: GENERIC CODE SHEET CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1093-B ORIGINAL NUMBER: 1093 ID: GECS GLOBAL REFERENCE: GECS(2100 FIELD NUMBER: 7 FIELD NAME: TRANSACTION/TYPE SEGMENT LOCATION: PIECE 8,0 NODE ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Type of code sheet FIELD NUMBER: 51 FIELD NAME: KEYPUNCH CODE SHEET LOCATION: "KEY", 0 node ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: signals keypunch code sheet FIELD NUMBER: 9.1 FIELD NAME: AMIS MONTH/YEAR LOCATION: PIECE 9, 0 NODE ACCESS: Read w/Fileman FIELD DESCRIPTION: AMIS month/year for code sheet GLOBAL DESCRIPTION: Generic Code Sheet File. This file is used to store the fields and data which make up the actual codesheet. GLOBAL REFERENCE: GECS(2101.2 FIELD NUMBER: #.5 FIELD NAME: EDIT TEMPLATE LOCATION: PIECE 3,0 NODE ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: CONTAINS EDIT TEMPLATE, NEEDED FOR CALL TO GECS ROUTINE. FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: PIECE 1, 0 NODE ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: "B" Cross reference of the name field. FIELD NUMBER: .5 ACCESS: Read w/Fileman GLOBAL DESCRIPTION: GENERIC CODE SHEET TRANSACTION TYPE/SEGMENT FILE. This file stores the different types of code sheets used for each type of batch (in file 2101.1). GLOBAL REFERENCE: DD(2100 GLOBAL DESCRIPTION: Data dictionary of 2100 to access field names for display. GENERAL DESCRIPTION: This is a request for an integration agreement between GECS and PIMS. PIMS will be making references to files in GECS and a print template. This integration agreement will formalize references that have been included in PIMS in the past, and modified to incorporate the changes in GECS V2.0. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13147102 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 1095 IA #: 1095 DATE CREATED: DEC 29, 1994 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA1095 GENERAL DESCRIPTION: Controlled Substances Version 2.0 utilizes three security keys exported by the Inpatient Medications software. The keys are used, within Inpatient Meds, to identify the user of the package. The same use is requested by Controlled Substances. The PSJ RPHARM key identifies a pharmacist, the PSJ RNURSE key identifies a nurse, and the PSJ PHARM TECH key identifies a pharmacy technician. These same identifications are used in the Controlled Substances package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12825199 SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 1096 IA #: 1096 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: JAN 03, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PATIENT MOVEMENT file cross reference ID: DGPM( GLOBAL REFERENCE: DGPM( GLOBAL DESCRIPTION: The "ATID1" xref.of the Patient Movement file. This is to order through admissions in inverse date order. GENERAL DESCRIPTION: Patient Movement file (#405) - The "ATID1" xref.of the Patient Movement file. This is to order through admissions in inverse date order. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13261617 SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: DIETETICS SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) SUBSCRIBING DETAILS: VPS 1*15, After Visit Summary (AVS) integration has a need to read the ATID1 cross reference of the Patient Movement field #405 to return the admission for an identified patient to AVS. VPS 1*15 AVS integration is planned for release in March 2015. DBA Comments: 10/12/12-MM: Added Dietetics as a subscriber for FB*5.5*30. During the development of this patch, the developer discovered existing references to the ATID1 cross reference in routine FHASN71. Requested Dietetics be added as a subscriber to document this reference. 3/5/15-DT: Added VPS KIOSK (VA POINT OF SERVICE (KIOSKS) as subscriber. VPS 1*15, After Visit Summary (AVS) integration has a need to read the ATID1 cross reference of the Patient Movement field #405 to return the admission for an identified patient to AVS. VPS 1*15 AVS integration is planned for release in March 2015. Since Registration concurrence unavailable - documented concurrence person as: Registration,documentonly DATE/TIME EDITED: OCT 12, 2012@10:18 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: UNDERHILL,GARDNER WITH CONCURRENCE OF: KOPECKY,STEVE DATE/TIME EDITED: MAR 05, 2015@11:57 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: Registration,DocumentOnly NUMBER: 1097 IA #: 1097 FILE NUMBER: 405.1 GLOBAL ROOT: DG(405.1 DATE CREATED: JAN 03, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Lookup on Facility Movement file ID: DG(405.1 GLOBAL REFERENCE: DG(405.1,0) FIELD NUMBER: .02 FIELD NAME: TRANSACTION TYPE LOCATION: 2 ACCESS: Read w/Fileman FIELD DESCRIPTION: FIELD NUMBER: .03 FIELD NAME: MOVEMENT TYPE LOCATION: 3 ACCESS: Read w/Fileman FIELD DESCRIPTION: Use of the "AM" cross reference on this field. GLOBAL DESCRIPTION: GENERAL DESCRIPTION: - A lookup on the FACILITY MOVEMENT TYPE file (#405.1) for discharge types with a screen that utilizes the "AM" Xref of the FACILITY MOVEMENT TYPE file (#405.1) and the fourth piece, the 'ACTIVE' field, on the zero node. The 'AM' cross reference will be $O through to search for active facility movement types. - Global read access to the FACILITY MOVEMENT TYPE file (#405.1) the second piece of the zero node the TRANSACTION TYPE field to identify discharge types. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 1098 IA #: 1098 FILE NUMBER: 405.2 GLOBAL ROOT: DG(405.2 DATE CREATED: JAN 03, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GENERAL LOOKUP ID: DG(405.2 GENERAL DESCRIPTION: The AMIE software will perform a FM lookup on the MAS MOVEMENT file (#405.2) in order to create and display a list of movement types. No pointer values will be stored as part of the AMIE database. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 1099 IA #: 1099 FILE NUMBER: 405.3 GLOBAL ROOT: DG(405.3 DATE CREATED: JAN 03, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: LOOKUP on MAS MOVEMENT TRANSACTION TYPE file ID: DG(405.3 GENERAL DESCRIPTION: The AMIE software will perform a FM lookup on the MAS MOVEMENT TRANSACTION TYPE file (#405.3) in oder to check for a specific transaction type and gather its internal file number. This value will be used for comparison during the processing of records. This value will not be stored as part of the AMIE database. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 1100 IA #: 1100 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: JAN 03, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DISPOSITION NODE ID: DPT( GLOBAL REFERENCE: DPT(2,DFN,DIS FIELD NUMBER: .01 FIELD NAME: LOG IN DATE/TIME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: GENERAL DESCRIPTION: Global read access to the "DIS" node of the PATIENT file, to look at the STATUS field. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 1106 IA #: 1106 DATE CREATED: JAN 09, 1995 CUSTODIAL PACKAGE: QUALITY ASSURANCE INTEGRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: QAQAHOC0 NAME: EEO/PAID - QAQ ADHOC REPORT ID: QAQAHOC0 GENERAL DESCRIPTION: Equal Employment Opportunity Complaint Tracking version 2.0 (EEO) will be referencing the routine ^QAQAHOC0 from within the routine ^EEOEAHOC. The neccessary QAQ* variables will be set for this call after establishing the existance of the routine ^QAQAHOC0. This reference will provide the EEO user with flexible report generation capabilities. PAID version 4.0 will be referencing the routine ^QAQAHOC0 from within routines PRSDAH1, PRSDAH2, PRSDAH3 and PRSDAH4. The neccessary QAQ* variables will be set for this call after establishing the existance of the routine ^QAQAHOC0. This reference will provide the PAID user with flexible report generation capabilities. VIEWER: ZZROTTA,JOHN STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 16950626 COMPONENT/ENTRY POINT: QAQAHOC0 COMPONENT DESCRIPTION: Ad Hoc Report main driver routine. VARIABLES: QA TYPE: Input VARIABLES DESCRIPTION: Incremental variable. VARIABLES: QAQDIC TYPE: Input VARIABLES DESCRIPTION: File number of the file to print from. VARIABLES: QAQFOUND TYPE: Input VARIABLES DESCRIPTION: Variable set to determine if any data was found for the print. VARIABLES: QAQMRTN TYPE: Input VARIABLES DESCRIPTION: Entry point to setup the QAQMENU array (format TAG^ROUTINE). VARIABLES: QAQORTN TYPE: Input VARIABLES DESCRIPTION: Entry point to set up other VA FileMan EN1^DIP variables, i.e. DCOPIES, DHD , DHIT, DIOBEG, DIOEND, DIS(), IOP. VARIABLES: QAQMHDR TYPE: Input VARIABLES DESCRIPTION: Text to be used as a header at the top of sort/print menu screens. Maximum of 45 characters. VARIABLES: QAQMENU TYPE: Input VARIABLES DESCRIPTION: Array containing sort, menu text, field, and sort from/to range information. VARIABLES: VARIABLES: QAQMMAX TYPE: Input VARIABLES DESCRIPTION: Variable for determining maximum number of choices appearing on AD HOC menus only neccessary for older versions of QA Integration Module. SUBSCRIBING PACKAGE: EEO COMPLAINT TRACKING ISC: Hines SUBSCRIBING PACKAGE: PAID ISC: Hines NUMBER: 1107 IA #: 1107 DATE CREATED: JAN 10, 1995 CUSTODIAL PACKAGE: GENERIC CODE SHEET CUSTODIAL ISC: Washington USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GECSENTR NAME: GECSENTR reference ID: GECSENTR GENERAL DESCRIPTION: This integration agreement contains the GECSENTR reference supported by the Generic Code Sheet package. For more information on using the supported reference, please refer to the Generic Code Sheet Technical Manual. STATUS: Active MAIL MESSAGE: 11948526 COMPONENT/ENTRY POINT: GECSENTR COMPONENT DESCRIPTION: The routine GECSENTR can be called to automatically build a code sheet by stuffing the data into the GENERIC CODE SHEET File (#2100). It will take the data in the GECS("STRING",i) array and map it to the input template, thus building the code sheet. VARIABLES: GECS(STRING,i) TYPE: Input VARIABLES DESCRIPTION: This variable stores the data to be mapped into the input template. The data is delimited by the '^' (up-arrow). The GECSENTR routine will $Order through the GECS("STRING",i) array starting with i=. Therfore, when building this array, the value of 'i' must start with 0 and count up. This variable is required. VARIABLES: GECS(TTF) TYPE: Input VARIABLES DESCRIPTION: This variable must be set to the GENERIC CODE SHEET TRANSACTION TYPE/SEGMENT File (#2101.2) entry (.01 field). The GECSENTR routine will lookup on the 'B' cross-reference in file 2101.2 using the GECS("TTF") variable. This variable is required. VARIABLES: GECS(SITENOASK) TYPE: Input VARIABLES DESCRIPTION: This variable GECS("SITENOASK") can be set to the station number which is generating the code sheet. This variable is optional. If it is not passed and there is more than one entry in the GENERIC CODE SHEET SITE File (#2101.7), the user will be prompted to select the station. VARIABLES: GECSSYS TYPE: Input VARIABLES DESCRIPTION: This variable must be set to the GENERIC CODE SHEET BATCH TYPE File (#2101.1) entry (.01 field). The GECSENTR routine will lookup on the "B" cross-reference in file 2101.1 using the GECSSYS variable. This variable is required. VARIABLES: GECSAMIS TYPE: Input VARIABLES DESCRIPTION: This variable can be set to the amis month year in the internal format YYYMM00. For example, December 1994 would be passed as 2941200. This variable is optional. VARIABLES: GECSAUTO TYPE: Input VARIABLES DESCRIPTION: This variable can be set to "BATCH" or "SAVE". If this variable is set to "BATCH", the GECSENTR routine will automatically mark the code sheet for batching without asking the user. If this variable is set to "SAVE", the GECSENTR routine will automatically save the code sheet for editing at a later time by the user. This variable is optional. If this variable is not passed or is set to a value different from "BATCH" and "SAVE", the user will be prompted to select the status of the code sheet. NUMBER: 1108 IA #: 1108 DATE CREATED: JAN 11, 1995 CUSTODIAL PACKAGE: GENERIC CODE SHEET CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GECSUFMS NAME: FMS code sheets ID: GECSUFMS GENERAL DESCRIPTION: This integration agreement contains the routine used by IFCAP/AR and ENGINEERING to build and transmit the Financial Management System (FMS) code sheets. For more information regarding the use of this routine, please refer to the Generic Code Sheet Technical Manual. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11084765 COMPONENT/ENTRY POINT: CONTROL COMPONENT DESCRIPTION: This entry point is provided for IFCAP to build the FMS control segments CTL, BAT, DOC, and 1 where is the transaction class segment. The entry point will format the segments and add the segments to the GENERIC CODE SHEET STACK File (#2100.1). The entry point is called as follows: DO CONTROL^GECSUFMS(1,2,3,4,5,6,7,8) where the variables 1, 2, 3, 4, 5, 6, 7, 8 must be passed by the calling program. VARIABLES: 1 TYPE: Input VARIABLES DESCRIPTION: The system creating the FMS code sheet: A for accounts receivable; I for IFCAP; E for Engineering; C for manual create a code sheet. This variable is required and must be passed as the first parameter. VARIABLES: 2 TYPE: Input VARIABLES DESCRIPTION: The 3 digit station number. This variable is required and must be passed as the second parameter. VARIABLES: 3 TYPE: Input VARIABLES DESCRIPTION: The source document number creating the code sheet prefixed with the station number. This variable is required and must be passed as the third parameter. VARIABLES: 4 TYPE: Input VARIABLES DESCRIPTION: The transaction code, 2 alpha characters. This variable is required and must be passed as the fourth parameter. VARIABLES: 5 TYPE: Input VARIABLES DESCRIPTION: The security code, from 1 to 4 characters. This variable is required and must be passed as the fifth parameter. VARIABLES: 6 TYPE: Input VARIABLES DESCRIPTION: A flag to indicate if its a modification document. Pass a 1 for a modification document, 0 otherwise. This variable is required and must be passed as the sixth parameter. VARIABLES: 7 TYPE: Input VARIABLES DESCRIPTION: A flag to indicate if the FMS code sheet has already updated the IFCAP fund control point balance. Pass a Y if the transaction has updated the IFCAP fund control point balance. This variable is required and must be passed as the seventh parameter. VARIABLES: 8 TYPE: Input VARIABLES DESCRIPTION: The description of the calling program which created the code sheet. The description will be displayed to the user when printing the Stack Status Report. This variable is required and must be passed as the eighth parameter. VARIABLES: GECSFMS(CTL) TYPE: Output VARIABLES DESCRIPTION: The variable GECSFMS("CTL") will be returned as the control segment. VARIABLES: GECSFMS(BAT) TYPE: Output VARIABLES DESCRIPTION: The variable GECSFMS("BAT") will be returned as the modification segment. VARIABLES: GECSFMS(DOC) TYPE: Output VARIABLES DESCRIPTION: The variable GECSFMS("DOC") is returned as the document and 1 segment. VARIABLES: GECSFMS(DA) TYPE: Output VARIABLES DESCRIPTION: The variable GECSFMS("DA") is returned as the internal entry number of the GENERIC CODE SHEET STACK File (#2100.1) entry which was added. SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring NUMBER: 1111 IA #: 1111 GLOBAL ROOT: DD( DATE CREATED: JAN 10, 1995 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: 1111 ID: DD( GLOBAL REFERENCE: DD(15,.01,'V','B') GLOBAL DESCRIPTION: This node is used in the input transform and in the screen of the DUPLICATE RESOLUTION FILE 15.1. It's used in a variable pointer type field to restrict the user to only those files which have been set up for the merge. GLOBAL REFERENCE: DD(FILE,FIELD) GLOBAL DESCRIPTION: These global references are used in displaying the fields that can be compared and assigned a matching value. The 0 node of the field is referenced in order to screen out 'computed' and 'multi-valued' fields from this display and comparison. One use of these references can be seen in the executable help of field .05, FIELD TO BE CHECKED. GLOBAL REFERENCE: DD(FILE,FIELD,0) GLOBAL DESCRIPTION: These global references are used in displaying the fields that can be compared and assigned a matching value. The 0 node of the field is referenced in order to screen out 'computed' and 'multi-valued' fields from this display and comparison. One use of these references can be seen in the executable help of field .05, FIELD TO BE CHECKED. GENERAL DESCRIPTION: Kernel Toolkit files have a number of fields whose screens, input transforms, and executable helps contain code that directly references ^DD. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13368155 SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 1112 IA #: 1112 FILE NUMBER: 391 GLOBAL ROOT: DG( DATE CREATED: JAN 26, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PATIENT TYPE ID: DG( CREATOR: HARVEY,JULIE S GLOBAL REFERENCE: DG(391,,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the name field in this file. GLOBAL DESCRIPTION: GENERAL DESCRIPTION: Read access to the following global and cross reference is being requested. The file in question is Type of Patient (391) the zero node first piece, as well as the "B" cross reference. The AMIE package needs this information when transferring 2507 requests. Internal entry numbers are not used during the transfer, only external values. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM SUBSCRIBING DETAILS: ADDED 12/11/2008 DBA Comments: 11/5/14-MM: VPS requested to be added as a subscriber to ICR #1112. They withdrew this request when it was determined they could use ELIG~VADPT to get the patient type. DATE/TIME EDITED: DEC 11, 2008@20:23 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BAUMANN,SCOTT WITH CONCURRENCE OF: PRIETULA,LAURA NUMBER: 1113 IA #: 1113 FILE NUMBER: 9.4 GLOBAL ROOT: DIC( DATE CREATED: JAN 10, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: 1113 ID: DIC( GLOBAL REFERENCE: DIC(9.4,D0,20,D1,0) FIELD NUMBER: 3 FIELD NAME: NAME OF MERGE ROUTINE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DIC(9.4,D0,20,D1,1) GLOBAL REFERENCE: DIC(9.4,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Kernel Toolkit needs this agreement with Kernel to reference ^DIC(9.4 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13368155 SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 1114 IA #: 1114 DATE CREATED: JAN 11, 1995 CUSTODIAL PACKAGE: GENERIC CODE SHEET CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GECSUFM1 NAME: FMS code sheets ID: GECSUFM1 GENERAL DESCRIPTION: This integration agreement contains the routine used by IFCAP/AR and Engineering to build and transmit the Financial Management System (FMS) code sheets. For more information regarding the use of this routine, please refer to the Generic Code Sheet Technical Manual. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11084765 COMPONENT/ENTRY POINT: REBUILD COMPONENT DESCRIPTION: This entry point is provided for IFCAP to rebuild the FMS control segments CTL, BAT, DOC, and 1 where is the transaction class segment. The entry point will format the segments, remove the existing code sheet, and add the rebuilt segments to the GENERIC CODE SHEET STACK File (#2100.1). The entry point is called as follows: DO REBUILD^GECSUFM1(1,2,3,4,5) where the variables 1, 2, 3, 4, 5 must be passed by the calling program. VARIABLES: 1 TYPE: Input VARIABLES DESCRIPTION: The internal entry number of the GENERIC CODE SHEET STACK File (#2100.1) entry to be rebuilt. This variable is required and must be passed as the first parameter. VARIABLES: 2 TYPE: Input VARIABLES DESCRIPTION: The system creating the FMS code sheet; A for accounts receivable; I for IFCAP; E for Engineering; C for manual create a code sheet. This variable is required and must be passed as the second parameter. VARIABLES: 3 TYPE: Input VARIABLES DESCRIPTION: The security code, from 1 to 4 characters. This variable is required and must be passed as the third parameter. VARIABLES: 4 TYPE: Input VARIABLES DESCRIPTION: A flag to indicate if the FMS code sheet has already updated the IFCAP fund control point balance. Pass a Y if the transaction has updated the IFCAP fund control point balance. This variable is required and must be passed as the fourth parameter. VARIABLES: 5 TYPE: Input VARIABLES DESCRIPTION: The description of the calling program which created the code sheet. The description will be displayed to the user when printing the Stack Status Report. This variable is required and must be passed as the fifth parameter. VARIABLES: GECSFMS(CTL) TYPE: Output VARIABLES DESCRIPTION: The variable GECSFMS("CTL") will be returned as the rebuilt control segment. VARIABLES: GECSFMS(BAT) TYPE: Output VARIABLES DESCRIPTION: The variable GECSFMS("BAT") will be returned as the rebuilt modification segment. VARIABLES: GECSFMS(DOC) TYPE: Output VARIABLES DESCRIPTION: The variable GECSFMS("DOC") will be returned as the rebuild document and 1 segment. SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: AR (ACCOUNTS RECEIVABLE) ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 1115 IA #: 1115 DATE CREATED: JAN 11, 1995 CUSTODIAL PACKAGE: GENERIC CODE SHEET CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GECSSTAA NAME: FMS code sheets ID: GECSSTAA GENERAL DESCRIPTION: This integration agreement contains the routine used by IFCAP/AR and Engineering to build and transmit the Financial Management System (FMS) code sheets. For more information regarding the use of this routine, please refer to the Generic Code Sheet Technical Manual. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11084765 COMPONENT/ENTRY POINT: SETCS COMPONENT DESCRIPTION: This entry point is provided for IFCAP to store the FMS segments in the GENERIC CODE SHEET STACK File (#2100.1). The entry point is called as follows: DO SETCS^GECSSTAA(1,2) where the variables 1, 2 must be passed by the calling program. VARIABLES: 1 TYPE: Input VARIABLES DESCRIPTION: The internal entry number of the GENERIC CODE SHEET STACK File (#2100.1) entry. This variable is required and must be passed as the first parameter. VARIABLES: 2 TYPE: Input VARIABLES DESCRIPTION: The data to be added to the code sheet. This variable is required and must be passed as the second parameter. COMPONENT/ENTRY POINT: SETSTAT COMPONENT DESCRIPTION: This entry point is provided for IFCAP to set the status of the FMS code sheets in the GENERIC CODE SHEET STACK File (#2100.1). The entry point is called as follows: DO SETSTAT^GECSSTAA(1,2) where the variables 1, 2 must be passed by the calling program. VARIABLES: 1 TYPE: Input VARIABLES DESCRIPTION: The internal entry number of the GENERIC CODE SHEET STACK File (#2100.1) entry. This variable is required and must be passed as the first parameter. VARIABLES: 2 TYPE: Input VARIABLES DESCRIPTION: The status of the entry. Select Q for queued for transmission; M for marked for transmission. If marked for transmission, transmission will be immediate. This variable is required and must be passed as the second parameter. COMPONENT/ENTRY POINT: SELECT COMPONENT DESCRIPTION: This entry point is provided for IFCAP to select a GENERIC CODE SHEET STACK File (#2100.1) entry. The entry point is called as follows: SET Y=$$SELECT^GECSSTAA(1,2,3,4,5) where the variables 1, 2, 3, 4, 5 must be passed by the calling program. VARIABLES: 1 TYPE: Input VARIABLES DESCRIPTION: Optional screen on transaction types. Pass the selectable transaction types using the ^ delimiter, or null to select all transaction types. This variable is required and must be passed as the first parameter. VARIABLES: 2 TYPE: Input VARIABLES DESCRIPTION: Optional screen on the station number. Pass the selectable station number, or null to select all station numbers. This variable is required and must be passed as the second parameter. VARIABLES: 3 TYPE: Input VARIABLES DESCRIPTION: Optional screen on the status. Pass the selectable status using the ^ delimiter, or null to select all code sheets. This variable is required and must be passed as the third parameter. VARIABLES: 4 TYPE: Input VARIABLES DESCRIPTION: Optional screen which is M code executed when looking up the GENERIC CODE SHEET STACK File (#2100.1) entry. This variable is required and must be passed as the fourth parameter. VARIABLES: 5 TYPE: Input VARIABLES DESCRIPTION: Optional prompt displayed to the user. This variable is required and must be passed as the fifth parameter. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: The call will return the internal entry number of the selected GENERIC CODE SHEET STACK File (#2100.1) entry followed by an ^ followed by the .01 stack name. If no selection is made, a zero will be returned. SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring NUMBER: 1116 IA #: 1116 DATE CREATED: JAN 11, 1995 CUSTODIAL PACKAGE: GENERIC CODE SHEET CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GECSSDCT NAME: FMS code sheets ID: GECSSDCT GENERAL DESCRIPTION: This integration agreement contains the routine used by IFCAP/AR to build and transmit the Financial Management System (FMS) code sheets. For more information regarding the use of this routine, please refer to the Generic Code Sheet Technical Manual. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11084765 COMPONENT/ENTRY POINT: SETCODE COMPONENT DESCRIPTION: This entry point is provided for IFCAP to set the GENERIC CODE SHEET STACK File (#2100.1) M code which will be executed when the code sheet is accepted or rejected by FMS in Austin. The entry point is called as follows: DO SETCODE^GECSSDCT(1,2) where the variables 1, 2 must be passed by the calling program. VARIABLES: 1 TYPE: Input VARIABLES DESCRIPTION: The internal entry number of the GENERIC CODE SHEET STACK File (#2100.1) entry. This variable is required and must be passed as the first parameter. VARIABLES: 2 TYPE: Input VARIABLES DESCRIPTION: The M code label^routine which will be executed when processing the accept/reject server message. It should be in the form 'DO LABEL^ROUTINE'. When LABEL^ROUTINE is called, it will use parameter passing and pass the following variables: 1 The FMS document number which is the .01 entry in the GENERIC CODE SHEET STACK File (#2100.1); 2 A flag to indicate if the code sheet was accepted or rejected. Pass A for accepted, or R for rejected. Also, if the code sheet is rejected, the reject message will be stored in TMP($J,"GECSSDCT",linenumber,0). COMPONENT/ENTRY POINT: SETPARAM COMPONENT DESCRIPTION: This entry point is provided for IFCAP to set the parameters in the GENERIC CODE SHEET STACK File (#2100.1) which will be used when rebuilding the FMS code sheets. The entry point is called as follows: DO SETPARAM^GECSSDCT(1,2) where the variables 1, 2 must be passed by the calling program. VARIABLES: 1 TYPE: Input VARIABLES DESCRIPTION: The internal entry number of the GENERIC CODE SHEET STACK File (#2100.1) entry. This variable is required and must be passed as the first parameter. VARIABLES: 2 TYPE: Input VARIABLES DESCRIPTION: The parameters used when rebuilding the code sheet. This is free text from 1 to 200 characters. This variable is required and must be passed as the second parameter. COMPONENT/ENTRY POINT: PROCESS COMPONENT DESCRIPTION: This entry point is provided for IFCAP to process the document confirmation transaction (DCT) from the server. The entry point will update the GENERIC CODE SHEET STACK File (#2100.1) entry as accepted or rejected. If there is M code set by the entry point SETCODE^GECSSDCT, the M code will be executed after setting the GENERIC CODE SHEET STACK File (#2100.1) entry status. The entry point is called as follows: DO PROCESS^GECSSDCT(1,2) where the variables 1, 2 must be passed by the calling program. VARIABLES: 1 TYPE: Input VARIABLES DESCRIPTION: The stack entry name .01 field. This variable is required and must be passed as the first parameter. VARIABLES: 2 TYPE: Input VARIABLES DESCRIPTION: Pass A for accepted or R for rejected. This variable is required and must be passed as the second parameter. VARIABLES: TMP TYPE: Input VARIABLES DESCRIPTION: Pass the accept or reject mail message in the global ^TMP($J,"GECSSDCT",linenumber,0). The mail message will be sent to the users responsible for submitting the code sheet. This global is optional. SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 1117 IA #: 1117 DATE CREATED: JAN 11, 1995 CUSTODIAL PACKAGE: GENERIC CODE SHEET CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GECSSGET NAME: FMS code sheets ID: GECSSGET GENERAL DESCRIPTION: This integration agreement contains the routine used by IFCAP/AR and Engineering to build and transmit the Financial Management System (FMS) code sheets. For more information regarding the use of this routine, please refer to the Generic Code Sheet Technical Manual. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 11084765 COMPONENT/ENTRY POINT: DATA COMPONENT DESCRIPTION: This entry point is provided for IFCAP to retrieve data from the GENERIC CODE SHEET STACK File (#2100.1). The entry point is called as follows: DO DATA^GECSSGET(1,2) where the variables 1, 2 must be passed by the calling program. VARIABLES: 1 TYPE: Input VARIABLES DESCRIPTION: The stack entry name .01 field. This variable is required and must be passed as the first parameter. VARIABLES: 2 TYPE: Input VARIABLES DESCRIPTION: A flag to return the actual code sheet. Pass a 1 for the actual code sheet, otherwise 0. This variable is required and must be passed as the second parameter. VARIABLES: GECSDATA TYPE: Output VARIABLES DESCRIPTION: A standard VA FileMan DIQ array with external data only. COMPONENT/ENTRY POINT: STATUS COMPONENT DESCRIPTION: This entry point is provided for IFCAP to return the status of a code sheet from the GENERIC CODE SHEET STACK File (#2100.1). The entry point is called as follows: SET Y=$$STATUS^GECSSGET(1) where the variable 1 must be passed by the calling program. VARIABLES: 1 TYPE: Input VARIABLES DESCRIPTION: The stack entry name .01 field. This variable is required and must be passed as the first parameter. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: This variable is returned as the status of the code sheet. SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring NUMBER: 1118 IA #: 1118 FILE NUMBER: 45.89 GLOBAL ROOT: DIC(45.89, DATE CREATED: JAN 11, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ICD Codes update in PTF ID: DIC(45.89, GENERAL DESCRIPTION: This is to enable the annual DRG Grouper ICD release to include updates to the PTF Expanded Code file (#45.89). New entries are added, updating fields .01, CATEGORY; and .02, DIAGNOSIS/PROCEDURE CODE. Several codes are inactivated, adding entries to their .03, INACTIVE DATE field. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DRG GROUPER ISC: Albany NUMBER: 1120 IA #: 1120 DATE CREATED: JAN 18, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRVUTL NAME: GMRVUTL ID: GMRVUTL GENERAL DESCRIPTION: User can extract the latest record for a desired vital type from the Vital/Measurement database for a particular patient by calling EN6^GMRVUTL. Input Variables: DFN = The internal entry number in the Patient file (#2) for the patient data that is to be retrieved. GMRVSTR = The abbreviation of the vital/measurement desired from the Vital Type file (#120.51). For example: S GMRVSTR="T",DFN=5 D EN6^GMRVUTL "T" is the abbreviation of temperature. GMRVSTR will be killed. Output Variable: X is set to the entire zeroth node for the entry in question in the Vital/Measurement file (#120.5), for example, ^GMR(120.5,IEN,0), where IEN is the subscript in the file that contains the data. The following shows the format of value containd in X. X=2920728.06^5^2^2920728.13482^42^2098^6^101.1 STATUS: Active MAIL MESSAGE: 10868960 COMPONENT/ENTRY POINT: EN6 COMPONENT DESCRIPTION: User can extract the latest record for a desired vital type from the Vital/ Measurement database for a particular patient. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The internal entry number in the Patient file (#2). VARIABLES: GMRVSTR TYPE: Input VARIABLES DESCRIPTION: The abbreviation of the vital/measurement desired from the Vital Type file (#120.51). VARIABLES: X TYPE: Output VARIABLES DESCRIPTION: The entire zeroth node for the entry in question in the Vital/Measurement file (#120.5). NUMBER: 1123 IA #: 1123 DATE CREATED: JAN 31, 1995 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRARAD NAME: Contrast Media Allergy ID: GMRARAD GENERAL DESCRIPTION: The Allergy package is providing extrinsic functions to support adding and entering in error Radiological contrast media allergy data for Radiology/Nuclear Medicine patients. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13546276 COMPONENT/ENTRY POINT: RADD COMPONENT DESCRIPTION: Adds contrast media allergy to Allergy package $$RADD^GMRARAD(DFN,OH,YN,VER) VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal record number of Patient file #2 VARIABLES: OH TYPE: Input VARIABLES DESCRIPTION: "o" if reaction was 'observed' "h" if reaction was 'historical' "p" if user should be asked if reaction was observed or historical VARIABLES: YN TYPE: Input VARIABLES DESCRIPTION: "Y" means contrast reaction "N" means no contrast reaction "U" means contrast reaction unknown "" means contrast reaction deleted VARIABLES: VER TYPE: Input VARIABLES DESCRIPTION: (optional) "1" means data will be autoverified "0" means data will not be verified '$D means use Allergy package autoverification checks VARIABLES: X TYPE: Output VARIABLES DESCRIPTION: Internal record number of the newly added contrast allergy record, or -1 if no record was added. COMPONENT/ENTRY POINT: RACHK COMPONENT DESCRIPTION: Lets user enter contrast media in error $$RACHK^GMRARAD(DFN,YN) This function will ask user the 'Are you sure ...' question if the Allergy package finds that there is an existing contrast media allergy record for the patient. If the patient answers 'Yes', the Allergy package will enter the record in error. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal record number of Patient file #2 VARIABLES: YN TYPE: Input VARIABLES DESCRIPTION: "N" if Rad/Nuc Med user enters 'NO' at the contrast media prompt. SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 1124 IA #: 1124 FILE NUMBER: 9.4 GLOBAL ROOT: DIC(9.4 DATE CREATED: FEB 01, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: References to Package File (9.4) ID: DIC(9.4 GLOBAL REFERENCE: DIC(9.4,DA,0) FIELD NUMBER: 1 FIELD NAME: PREFIX LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DIC(9.4,DA,4) FIELD NUMBER: 6 FIELD NAME: *FILE LOCATION: 4;0 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: ^XTSUMBLD, %INDEX, and the XINDEX routines need to look at the Package file to find out what files are part of the package. For example, >>>>>XTSUMBLD+14 (FIELD: PREFIX) S X=$P(^DIC(9.4,+$P(Y(0),U,2),0),U,2) D NAME(X) G EXIT:'$D(XTRNAME) >>>>>XINDX10+11 (FIELD: FILE) F J=0:0 S J=$O(^DIC(9.4,DA,4,J)) Q:J'>0 I $D(^(J,0)) SINDFN=+^(0),INDRN="|dd" _INDFN,(INDF,INDL)=0 D INSERT >>>>>XINDX11+22 (FIELD: PREFIX) NAMSP S INDXN=$P(^DIC(9.4,DA,0),"^",2),C9=0,INDXN(C9)="," F A=0:0 S A=$O(^DIC(9. 4,DA,"EX",A)) Q:A'>0 I $D(^(A,0))#2 S C9=C9+1,INDXN(C9)=$P(^(0),"^") >>>>>ZINDX10+4 (FIELD: FILE) F J=0:0 S J=$O(^DIC(9.4,DA,4,J)) Q:J'>0 I $D(^(J,0)) S INDFN=+^(0),INDRN=" |dd" _INDFN,(INDF,INDL)=0 D INSERT >>>>>ZINDX11+5 (FIELD: PREFIX) NAMSP S INDXN=$P(^DIC(9.4,DA,0),"^",2),C9=0,INDXN(C9)="," F A=0:0 S A=$O(^DIC(9. 4,DA,"EX",A)) Q:A'>0 I $D(^(A,0))#2 S C9=C9+1,INDXN(C9)=$P(^(0),"^") STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13612183 SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 1125 IA #: 1125 FILE NUMBER: 9.6 GLOBAL ROOT: XPD(9.6 DATE CREATED: FEB 01, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Index and BUILD file ID: XPD(9.6 GLOBAL REFERENCE: XPD(9.6,D0,4 FIELD NUMBER: 4 FIELD NAME: FILE ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: XPD(9.6,D0,'KRN', FIELD NUMBER: 6 FIELD NAME: BUILD COMPONENTS ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Index reads the file list, option list, Function list, routine list to get the components of a build. The references are in XINDX10, XINDX11, XINDX51. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13612281 SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 1126 IA #: 1126 GLOBAL ROOT: DD( DATE CREATED: FEB 01, 1995 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Index and the DD global. ID: DD( GLOBAL REFERENCE: DD( GLOBAL DESCRIPTION: The VA Cross-Referencer utility in Toolkit needs to reference several ^DD nodes in order to cross-reference a package. Several of the referenced DD nodes contain M code. They are inspected to find items such as global/variables names and label /external references. Some of the referenced nodes are the "LAYGO", "DEL" nodes. A specific example of a DD reference follows: >>>>>%INDX10+25 S INDEL="" F G=0:0 S INDEL=$O(^DD(INDFN,INDF,"LAYGO",INDEL)) Q:INDEL="" I $D(^(INDEL,0))#2 S INDC=INDF_"LAYGO"_INDEL_" ; LAYGO CHECK CODE",INDX=^(0) D ADD The DD references are found in routines %INDX10, %INDX11, %INDX53. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13612325 SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 1128 IA #: 1128 DATE CREATED: FEB 03, 1995 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: Killing global DOPT GENERAL DESCRIPTION: This integration agreement allows the LetterMan pre-init to remove the old version namespace entries in the global ^DOPT. The globals killed are: ^DOPT("WPSE") ^DOPT("WPSE1") ^DOPT("WPSE2") ^DOPT("WPSE3") ^DOPT("WPSE4") STATUS: Active DURATION: Next Version MAIL MESSAGE: 13275309 SUBSCRIBING PACKAGE: LETTERMAN ISC: Washington/Silver Spring NUMBER: 1129 IA #: 1129 GLOBAL ROOT: ZZSLOT( DATE CREATED: FEB 06, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1129-A ORIGINAL NUMBER: 1129 ID: ZZSLOT( GLOBAL REFERENCE: ZZSLOT(nodename,'ACTIVE') GLOBAL DESCRIPTION: # active slots on this node. GENERAL DESCRIPTION: Reference to ^ZZSLOT. Toolkit requests read access to this node to maintain the number of active slots in it's performance database. .S XUCMSLOT=+$G(^ZZSLOT(XUCMND,"ACTIVE")) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13669472 SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 1130 IA #: 1130 DATE CREATED: FEB 06, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: %ZOSV2 NAME: DBIA1129-B ORIGINAL NUMBER: 1129 ID: %ZOSV2 GENERAL DESCRIPTION: References to ^%ZOSV* STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: DB COMPONENT DESCRIPTION: Collect data on current database size VARIABLES: XUCM() TYPE: Output COMPONENT/ENTRY POINT: RTHSTOP COMPONENT DESCRIPTION: Stops the current RTHIST session, prepares data for filing by moving to the %ZRTL global, purges ^RTH global in MGR, begins a new RTHIST session. COMPONENT/ENTRY POINT: $$TRNLNM COMPONENT DESCRIPTION: Translates a VMS logical name. COMPONENT/ENTRY POINT: $$TI COMPONENT DESCRIPTION: Returns MSM cpu tic interval. COMPONENT/ENTRY POINT: $$OS COMPONENT DESCRIPTION: Return current operating system and version level. COMPONENT/ENTRY POINT: $$PRV COMPONENT DESCRIPTION: Return current user priv's on VMS systems. SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 1131 IA #: 1131 GLOBAL ROOT: XMB('NETNAME') DATE CREATED: FEB 09, 1995 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: XMB('NETNAME') ID: XMB('NETNAME') GENERAL DESCRIPTION: ^XMB("NETNAME") contains the human-readable form of the name of the local domain. It is a copy of the .01 field of the record in the DOMAIN file 4.2 pointed to by the .01 field of the only record in the MAILMAN SITE PARAMETERS file 4.3. You may reference this global in any routine. STATUS: Active MAIL MESSAGE: 13715033 NUMBER: 1132 IA #: 1132 DATE CREATED: FEB 21, 1995 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMUT7 NAME: TEST FORWARDING ADDRESS ID: XMUT7 GENERAL DESCRIPTION: This API sends a test message from the Postmaster to the forwarding address of a user. If the MAILMAN SITE PARAMETER field 7.01, FWD TEST MESSAGE TO POSTMASTER, is not set, the Postmaster is a recipient. The message will either be successful or a message will be returned to the Postmaster from the remote system identified in the forwarding address explaining that the message could not be delivered. This entry point is not normally used by application programmers. Usage: D ^XMUT7(Y), where Y is the DUZ of the user whose forwarding address is to be tested. STATUS: Active NUMBER: 1135 IA #: 1135 DATE CREATED: FEB 17, 1995 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRAMCU0 NAME: GMRAMCU0 ID: GMRAMCU0 GENERAL DESCRIPTION: The Patient Wristband software calls IDBAND^GMRAMCU0(DFN,DATE,USR) to update the ID BAND MARKED field in file 120.8 (PATIENT ALLERGIES). VIEWER: SCHLEHUBER,CAMERON VIEWER: MILFAJT,ROBERT VIEWER: WRAY,CECELIA A STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: IDBAND COMPONENT DESCRIPTION: IDBAND(DFN,DATE,USR) ; This program will mark all the ID Band fields for ; all reactions for a patient VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN for a patient in file 2 (Required) VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: Date of marking in File Manager format (optional- if undefined or null current date/time will be used) VARIABLES: USR TYPE: Input VARIABLES DESCRIPTION: User Marking the ID band (optional- if undefined null will be used indicating data automatically entered). SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 1136 IA #: 1136 DATE CREATED: FEB 21, 1995 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMCU1 NAME: ENCODE/DECODE CARETS AND CTRL CHARS ID: XMCU1 GENERAL DESCRIPTION: This API contains the following functions: $$ENCODEUP^XMCU1(STRING) - convert all "^" to "~U~" $$DECODEUP^XMCU1(STRING) - convert all "~U~" to "^" $$STRAN^XMCU1(STRING) - convert all control characters to printables $$RTRAN^XMCU1(STRING) - undo the conversion by $$STRAN^XMCU1 STATUS: Active COMPONENT/ENTRY POINT: $$ENCODEUP COMPONENT DESCRIPTION: Takes a string, converts any "^" to "~U~", and returns the result. This function is identical to $$ENCODEUP^XMXUTIL (DBIA 2734). This function is used when putting strings, which may contain "^", into fields in globals. Fields in globals are delimited by "^", so any "^" in a string would, in effect, create an unintended field. So, before we put such strings into fields, we convert any "^". MailMan uses this to convert any subjects with "^" before putting them in the .01 field in the MESSAGE file, 3.9. Usage: S X=$$ENCODEUP^XMCU1(string) VARIABLES: STRING TYPE: Input VARIABLES DESCRIPTION: Any string, usually with one or more "^" in it. COMPONENT/ENTRY POINT: $$DECODEUP COMPONENT DESCRIPTION: Takes a string, converts any "~U~" to "^", and returns the result. This function is identical to $$DECODEUP^XMXUTIL (DBIA 2734). Usage: S X=$$DECODEUP^XMCU1(STRING) VARIABLES: STRING TYPE: Input VARIABLES DESCRIPTION: A string with embedded "~U~". COMPONENT/ENTRY POINT: $$STRAN COMPONENT DESCRIPTION: Takes a string, converts any control characters (and "~") to printable characters, and returns the result. The conversion may be undone by $$RTRAN^XMCU1. Usage: S X=$$STRAN^XMCU1(STRING) Note: "~" is replaced by "~>" $C(I) by $C(I+64) for I=0 to 31, for example $C(0) by "~@" $C(1) by "~A" $C(7) by "~G" (i.e. BELL) $C(13) by "~M" (i.e. CR = Carriage Return) $C(26) by "~Z" $C(31) by "~_" etc. VARIABLES: STRING TYPE: Input VARIABLES DESCRIPTION: A string with control characters in it. COMPONENT/ENTRY POINT: $$RTRAN COMPONENT DESCRIPTION: Takes a string which had been converted by $$STRAN^XMCU1, undoes the conversion, and returns the result. VARIABLES: STRING TYPE: Input VARIABLES DESCRIPTION: A string whose control characters have been converted by $$STRAN^XMCU1. NUMBER: 1137 IA #: 1137 DATE CREATED: SEP 19, 1995 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBOUTL NAME: DBIA1137 ID: IBOUTL GENERAL DESCRIPTION: IBQ Package requests use of the routines to derive date ranges. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17534172 COMPONENT/ENTRY POINT: DATE COMPONENT DESCRIPTION: Derive date ranges. VARIABLES: IBBDT TYPE: Output VARIABLES DESCRIPTION: IBBDT is returned as the beginning date. VARIABLES: IBEDT TYPE: Output VARIABLES DESCRIPTION: IBEDT is returned as the ending date. SUBSCRIBING PACKAGE: UTILIZATION MANAGEMENT ROLLUP ISC: Albany NUMBER: 1138 IA #: 1138 DATE CREATED: FEB 17, 1995 CUSTODIAL PACKAGE: AUTOMATED MED INFO EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DVBCHS0 NAME: DBIA1138 ID: DVBCHS0 CREATOR: FAIRBROTHER,EILEEN GENERAL DESCRIPTION: The health summary package needs to be able to retrieve Compensation and Pension data for a health summary C & P component. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13778959 COMPONENT/ENTRY POINT: HSCP COMPONENT DESCRIPTION: The Health Summary application needs permission to use the entry point HSCP^DVBCHS0(PATPTR,INVBEGDT,INVENDDT,OUTCODE,ARRAY) in order to extract compensation and pension (C & P) information from the 2507 EXAM (#396.4) and 2507 REQUEST (#396.3) files. Entry Point ----------- HSCP^DVBCHS0(PATPTR,INVBEGDT,INVENDDT,OUTCODE,ARRAY) Input ----- PATPTR - Pointer to PATIENT file (#2) INVBEGDT - Beginning date in inverse FileMan format - Defaults to one year before today INVENDDT - Ending date in inverse FileMan format - Defaults to today OUTCODE - Flag indicating which optional nodes to return 0 = Do not return any optional nodes 1 = Node 1 should also be returned 2 = Node 2 should also be returned 3 = Nodes 1 & 2 should also be returned (default) ARRAY - Where to store output (full global reference) - Defaults to ^TMP("DVBC",$J) Ouptput ------- ARRAY(InvExDt,Type,0) = Code ^ DATE OF EXAM [.06] ^ EXAM TYPE [.03] ^ EXAMINING PHYSICIAN [.07] ^ PRIORITY OF EXAM [396.3;9] ARRAY(InvExDt,Type,1) = ROUTING LOCATION [396.3;24] <-- ^ OWNER DOMAIN [396.3;28] ^ TRANSFERRED OUT TO [62] ARRAY(InvExDt,Type,2) = REQUEST STATUS [396.3;17] <-- ^ APPROVED BY [396.3;25] ^ APPROVAL DATE/TIME [396.3;26] ARRAY(InvExDt,Type,"RES",0) = Number of lines in EXAM RESULTS ARRAY(InvExDt,Type,"RES",X) = Line X of EXAM RESULTS [70] Subscripts: InvExDt - Inverse FileMan date of DATE OF EXAM [.06] Type - Poiner value of EXAM TYPE [.03] Code used as follows: 1 = Exam was performed locally 2 = Exam was performed by another facility 3 = Exam was performed locally for another facility Dates will be in FileMan format, while all other information will be in external format With the exception of dates, N/A (not applicable) and UNKNOWN will be used when appropriate Optional nodes are marked by an arrow (<--) Notes ----- - Output array will be initialized (KILLed) - Information for an exam is only returned when: 1. The exam status is COMPLETED 2. The status of the request containing the exam is a) RELEASED TO RO, NOT PRINTED b) COMPLETED, PRINTED BY RO c) COMPLETED, TRANSFERRED OUT - The Priority of Exam codes and text that may be returned are: 'T' FOR TERMINAL 'P' FOR POW 'OS' FOR ORIGINAL SC 'ON' FOR ORIGINAL NSC 'I' FOR INCREASE 'R' FOR REVIEW 'OTR' FOR OTHER 'E' FOR INSUFFICIENT EXAM 'AO' FOR AGENT ORANGE 'BDD' FOR BEN DELIV AT DISCHG 'IDES' FOR DISABILITY EVAL SYS 'QS' FOR QUICK START VARIABLES: PATPTR TYPE: Input VARIABLES DESCRIPTION: Pointer to PATIENT file (#2) VARIABLES: INVBEGDT TYPE: Input VARIABLES DESCRIPTION: Beginning date in inverse FileMan Format Defaults to one year before today. VARIABLES: INVENDDT TYPE: Input VARIABLES DESCRIPTION: Ending date in inverse FileMan format. Defaults to today VARIABLES: OUTCODE TYPE: Input VARIABLES DESCRIPTION: Flag indicating which optional nodes to return. 0 = Do not return any optional nodes 1 = Node 1 should also be returned 2 = Node 2 should also be returned 3 = Node 1 and 2 should also be returned (default) VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: Where to store output (full global reference). Defaults to ^TMP("DVBC",$J) VARIABLES: ARRAY(InvExDt,Type,0) TYPE: Output VARIABLES DESCRIPTION: Node contain the following data: Code ^ DATE OF EXAM [.06] ^ EXAM TYPE [.03] ^ EXAMINING PHYSICIAN [.07] ^ PRIORITY OF EXAM [396.3;9] VARIABLES: ARRAY(InvExDt,Type,1) TYPE: Output VARIABLES DESCRIPTION: Node contains the following data: ROUTING LOCATION [396.3;24] ^ OWNER DOMAIN [396.3;28] ^ TRANSFERRED OUT TO [62] VARIABLES: ARRAY(InvExDt,Type,2) TYPE: Output VARIABLES DESCRIPTION: Node contains the following data: REQUEST STATUS [396.3;17] ^ APPROVED BY [396.3;25] ^ APPROVAL DATE/TIME [396.3;26] VARIABLES: ARRAY(InExDt,Typ,"RES",0) TYPE: Output VARIABLES DESCRIPTION: Node contains the following data: Number of lines in EXAM RESULTS VARIABLES: ARRAY(InExDt,Typ,"RES",X) TYPE: Output VARIABLES DESCRIPTION: Node contain the following data: Line X of the EXAM RESULTS [70]. VARIABLES: SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City DBA Comments: 10/12/2010 - modify Priority of Exam field by Fairbrother. 4/2/13-MM: Opened ICR for edits. Donna Sandusky modified the Priority of Exam codes. DCS (DES Claimed Cond by Svcmbr) and DFD (DES Fit-For-Duty) will be removed and replaced by IDES (Disability Eval System). ICR has been activated for DVBA*2.7*184 scheduled for release in May 2013. DATE ACTIVATED: OCT 13, 2010 DATE/TIME EDITED: OCT 12, 2010@11:59 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: FAIRBROTHER,EILEEN WITH CONCURRENCE OF: BRATHWAITE,MICHAEL DATE/TIME EDITED: OCT 13, 2010@13:35 ACTION: APPROVED AT THE REQUEST OF: FAIRBROTHER,EILEEN WITH CONCURRENCE OF: BRATHWAITE,MICHAEL DATE/TIME EDITED: APR 02, 2013@09:56 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: SANDUSKY,DONNA WITH CONCURRENCE OF: THOMPSON,TONY DATE/TIME EDITED: APR 02, 2013@12:04 ACTION: APPROVED AT THE REQUEST OF: SANDUSKY,DONNA WITH CONCURRENCE OF: THOMPSON,TONY NUMBER: 1139 IA #: 1139 FILE NUMBER: 3.5 GLOBAL ROOT: %ZIS(1 DATE CREATED: OCT 12, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Add HFS device for OE/RR ID: %ZIS(1 GLOBAL REFERENCE: %ZIS(1, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1 FIELD NAME: $I LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: 2 FIELD NAME: TYPE LOCATION: TYPE;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: 35 FIELD NAME: RESOURCE SLOTS LOCATION: 1;10 ACCESS: Both R/W w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34787251 GOOD ONLY FOR VERSION: 3.0 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: This is a one-time request to allow the OE/RR packag to add a HFS device to the DEVICE file. The entry will be named OR WORKSTATION. It will have a subtype of P-OTHER. This device is used by the listmanager and GUI portions of CPRS (OE/RR version 3.0) to generate DHCP reports into a list format. The following is the code used to create this device: ZIS ; -- Add OR WORKSTATION and resource devices N DA,DIC,DIE,DLAYGO,X,Y S DIC(0)="LQMZ",(DIC,DLAYGO)=3.5,X="OR WORKSTATION" D ^DIC I Y,$P(Y,"^",3) D ; if newly added . S DA=+Y,DIE=DIC . S DR=".02///^S X=""OR Workstation HFS Device"";1///^S X=""ORDEV.DAT""" . S DR=DR_";1.95////0;2///^S X=""HFS"";4////0;5////0;5.1////0;5.2////0" . S DR=DR_";3///^S X=""`""_"_$$SUBTYPE^ORCPOST() . D ^DIE Q ; SUBTYPE() ; get subtype for P-OTHER N DIC,X S DIC(0)="QMXZ",DIC="^%ZIS(2,",X="P-OTHER" D ^DIC Q +Y SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: CLINICAL REMINDERS NUMBER: 1142 IA #: 1142 DATE CREATED: FEB 20, 1995 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMGAPI0 NAME: MESSAGE SUBJECT API ID: XMGAPI0 GENERAL DESCRIPTION: This API contains the following functions: $$SUBCHK^XMGAPI0 - validate a proposed message subject $$SUBGET^XMGAPI0 - retrieve the subject of a message STATUS: Active MAIL MESSAGE: 14000372 COMPONENT/ENTRY POINT: $$SUBGET COMPONENT DESCRIPTION: Given the message number, returns the subject of a message. Any ~U~ are automatically converted to up-arrow (^). If the message does not exist, returns null. Compare to ZSUBJ^XMXUTIL2 and SUBJ^XMXUTIL2 (DBIA 2736). Usage: S A=$$SUBGET^XMGAPI0(XMZ) Example: W $$SUBGET^XMGAPI0(51537) zzzzzz message subject zzzzz VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the MESSAGE file (3.9), of the message whose subject you wish to get. COMPONENT/ENTRY POINT: $$SUBCHK COMPONENT DESCRIPTION: Checks a prospective message subject to see if it passes validity checks/input transform. If valid, it returns the subject. If not valid, it returns an error string explaining why it's not valid. Leading and trailing blanks are automatically removed. Up-arrows (^) are automatically converted to "~U~". Function can be set to be interactive (to display results of the check to the screen) or non-interactive. In interactive mode, control characters are removed, too. Compare to VSUBJ^XMXAPI (DBIA 2728). Usage: S A=$$SUBCHK^XMGAPI0(XMSUB,XMFLG) Parameters: XMSUB - string to be validated as a message subject XMFLG - interactive, and display results to the user, too? (0=no; 1=yes) Returns: If OK: ^ valid string If error: error number ^ string Possible results, in actual order: Subject is too long Non-interact: 3-Entered subject too long ^$E(,1,65) Interactive: "Entered subject too long "1^$E(,1,250) At this point, leading and trailing blanks are removed, and up-arrows (^) are converted to ~U~. Subject contains control characters Non-interact: 5-Subject cannot contain control characters.^ Interactive: "Control characters removed ( is Subject accepted)." (Control characters are removed and checking continues.) Subject is null Non-interact: Interactive: Subject is "?" Non-interact: 4-Enter a Message Subject, between 3 & 65 characters long or '^' to exit.^ Interactive: "Enter a Message Subject, between 3 & 65 characters long or '^' to exit." 1^ Subject is too short Non-interact: 1-SUBJECT must be at least 3 characters long.^ Interactive: "SUBJECT must be at least 3 characters long." 1^ Subject is reserved format Non-interact: 2-Subject names of this format (1""R""1.N) are RESERVED ^ Interactive: "Subject names of this format (1""R""1.N) are RESERVED" 1^ Subject is OK Non-interact: ^ Interactive: ^ VARIABLES: XMSUB TYPE: Input VARIABLES DESCRIPTION: Proposed message subject. VARIABLES: XMFLG TYPE: Input VARIABLES DESCRIPTION: Should results of the check be written to the screen, too? Possible values are: 0 - no 1 - yes NUMBER: 1143 IA #: 1143 DATE CREATED: FEB 20, 1995 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMRENT NAME: MESSAGE HEADER API ID: XMRENT GENERAL DESCRIPTION: This API contains the following function: $$NET^XMRENT - Get message header information STATUS: Active MAIL MESSAGE: 14000218 COMPONENT/ENTRY POINT: $$NET COMPONENT DESCRIPTION: This extrinsic function is used for getting message information. Given a message number, it returns an "^"-delimited string containing message header information. If there is no such message, it returns the null string. Compare to $$HDR^XMGAPI2 (DBIA 1144), and INMSG^XMXUTIL2 and other ^XMXUTIL2 APIs (DBIA 2736). Usage: S X=$$NET^XMRENT(XMZ) Returns: If the message is NOT defined, the null string. If the message is defined, a string with the following pieces, separated by "^": Piece Contents 1 Origination date. If remote, as sent. If local, in format MAY 25, 1999@08:16:00 2 Scramble hint, if any; otherwise null 3 From (external) 4 Message ID at originating site (XMZ@site, if local) 5 Message sender, usually surrogate (external); otherwise null 6 Subject 7 Message ID of original message, if this is a reply (XMZ@site, if local); otherwise null 8 Message type (piece 7 of message's zero node) Examples: W $$NET^XMRENT(51537) date@time^HINT^From^10576@MAILSYS^SurrogateDUZ^Subject^4321@site^Type 1 2 3 4 5 6 7 8 VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the MESSAGE file (3.9). NUMBER: 1144 IA #: 1144 DATE CREATED: FEB 20, 1995 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMGAPI2 NAME: MESSAGE INFO API ID: XMGAPI2 GENERAL DESCRIPTION: This API contains the following function: $$HDR^XMGAPI2 - retrieve information about a message. STATUS: Active COMPONENT/ENTRY POINT: $$HDR COMPONENT DESCRIPTION: This function retrieves message header information, as well as other information about a message. How much information is returned depends on the value of FLAG, one of the parameters. If successful, it sets up (in ARRAY, which must be passed by reference) an array of information about a message, and returns zero (0). If unsuccessful, returns one of the following: "1-Undefined message number" "1-No message number" "1-No such message" "2-User is not a sender of recipient." "4-Invalid user" Compare to $$NET^XMRENT (DBIA 1143), and INMSG^XMXUTIL2 and all other APIs in ^XMXUTIL2 (DBIA 2736). Usage: S X=$$HDR^XMGAPI2(XMZ,.ARRAY,FLAG) Examples: --------------------------------------------------------------- Example of specifying an non-existent message: S X=$$HDR^XMGAPI2(999,.VAR,"") I +X>0 W !,X "1-No such message" Note that VAR is UNCHANGED from state prior to call if function value is greater than zero. -------------------------------------------------------------- USING A FLAG OF ZERO Example of a Message from a Local User: S DATA=$$HDR^XMGAPI2(123456,.VAR,0) Data will be returned as 0, if 123456 is a valid message. Array will be returned as: VAR("BROADCAST") = 0 VAR("BSKT") = "IN" VAR("BSKT IEN") = 1 VAR("DATE") = "SEPTEMBER 10, 1993@09:00:00" VAR("DATE FM") = 2930910.9 VAR("LINES") = 22 VAR("NEW") = 1 VAR("PXMZ") = "" VAR("SENDER") = "USER,JOE" VAR("SENDER DUZ")= 77 VAR("SUBJ") = "HELLO!" VAR("SURROG") = "" VAR("TYPE") = "P" VAR("XMZ") = 123456 Example of Message from a Remote User: S DATA=$$HDR^XMGAPI2(123457,.VAR,0) Data and the array information for message 123457 will be returned as above for message 123456. The remote user will be returned as a string. VAR("SENDER") = "JEAN247@domainname.FR" VAR("SENDER DUZ")= "" Example of a Response from a Local User: DATA=$$HDR^XMGAPI2(123458,.VAR,0) Data and the array information for message 123458 will be returned as above for message 123456. The value of the pointer to the message will be returned as below: VAR("PXMZ") = 123456 VAR("SUBJ") = "Re: HELLO!" VAR("XMZ") = 123458 Example of a Response from a Remote User: S DATA=$$HDR^XMGAPI2(123459,.VAR,0) Data and the array information for message 123459 will be returned as above for message 123458. The remote user will be returned as a string. VAR("PXMZ") = 123456 VAR("SENDER") = "JEAN247@domainname.FR" VAR("SENDER DUZ")= "" VAR("SUBJ") = "Re: HELLO!" VAR("XMZ") = 123459 ---------------------------------------------------------------------- USING A FLAG OF 1 Example of Message from a Local User: S DATA=$$HDR^XMGAPI2(123456,.VAR,1) Data and the array information for message 123456 will be returned as above. In addition, the following will be returned in the VAR array: VAR("RRED") = 2 Responses Read VAR("RRCV") = 3 Responses Received VAR("BLOBCNT") = 0 Non-textual body parts attached. -------------------------------------------------------------------- USING A FLAG OF 91 Example of a Message from a Local User: S DATA=$$HDR^XMGAPI2(123456,.VAR,91) Data and the array information for message 123456 will be returned as above. In addition, the following will be returned in the VAR array. Each node is a response number and each value is a pointer to File #3.9. VAR("RSP",1)=123458 VAR("RSP",2)=123459 VAR("RSP",3)=123501 -------------------------------------------------------------------------- USING A FLAG OF 92 Example of a Message from a Local User: S DATA=$$HDR^XMGAPI2(123456,.VAR,92) Data and the array information for message 123456 will be returned as with Flag 1. In addition, the following will be returned the VAR array. (Each node is an image counter and each value is a pointer to the Object file (#2005), A Binary Large OBject - BLOB). VAR("BLOB",1)=100 VAR("BLOB",2)=3345 VAR("BLOB",3)=14445 -------------------------------------------------------------------------- USING A FLAG OF 93 Example of a Message from a Local User: S DATA=$$HDR^XMGAPI2(123456,.VAR,93) Data and the array information for message 123456 will be returned as with Flag 91. In addition, the array of image counter and values will be returned as above. VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: User's DUZ. The IEN of the user in the NEW PERSON file (200). VARIABLES: XMDUZ TYPE: Used VARIABLES DESCRIPTION: The user's DUZ. Default is DUZ. This is the user, in relation to whom, some of the message information will be obtained. VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: IEN of the message in the MESSAGE file (3.9) about which information is to be obtained. VARIABLES: FLAG TYPE: Used VARIABLES DESCRIPTION: Determines what information is obtained about the message. Possible values are: 0 - return basic information (default) 1 - return basic information + response and BLOB count information 91 - return flag 1 information + response IDs 92 - return flag 1 information + BLOB IDs 93 - return all of the above VARIABLES: ARRAY TYPE: Output VARIABLES DESCRIPTION: Array of information. If FLAG=0 or undefined: ("BROADCAST") = 1 if the message was broadcast; 0 otherwise ("BSKT") basket name (XMDUZ); null if not in basket ("BSKT IEN") basket IEN (XMDUZ); null if not in basket ("DATE") message date/time, in format MAY 25, 1999@08:16:00, if local, or as sent, if remote. ("DATE FM") message date/time (FileMan format); date only, if remote. ("LINES") number of lines in the original message ("NEW") = 1 if the message is new; 0 otherwise ("PXMZ") message number of original message; null if not a response ("SENDER") sender (from) (external format) ("SENDER DUZ") sender (from) DUZ; null if remote or fictitious ("SUBJ") subject (external format) ("SURROG") surrogate sender (external format) ("TYPE") message type (piece 7 of the message's zero node) ("XMZ") message IEN in message file If FLAG=1, returns value array as with flag 0, and additional value array as follows: ("RRED") responses read (XMDUZ); null if not applicable ("RRCV") responses received; null if not applicable ("BLOBCNT") (specific to Imaging pkg) number of non-textual body parts attached If FLAG=91, and if the message has responses, returns value array as with flag 1, and an array of response nodes and values as follows: ("RSP",i) (pointer to 3.9 file) array of responses, where i is the response number If FLAG=92, and if the message has BLOBs, returns value array as with flag 1, and an array of non-textual body parts as follows: ("BLOB",i) (specific to Imaging pkg) (pointer to 2005 file) array of BLOBS If FLAG=93, returns all of the above. NUMBER: 1145 IA #: 1145 DATE CREATED: FEB 20, 1995 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMA2R NAME: REPLY TO / ANSWER A MESSAGE API ID: XMA2R GENERAL DESCRIPTION: The APIs (functions) in this DBIA send non-interactive replies and answers. $$ENT^XMA2R - Send a reply to a message. Add a response to the response chain of original message. $$ENTA^XMA2R - Send an answer to a message. Create a new message (rather than adding a response to the response chain of original message). STATUS: Active MAIL MESSAGE: 15644239 COMPONENT/ENTRY POINT: $$ENT COMPONENT DESCRIPTION: Send a reply to a message. Add a response to the response chain of original message, so that all local recipients of the message get the reply. If the message is from a remote site, you can indicate (with XMNET), whether the reply should be send to the author of the message, too. This function is non-interactive. Compare to REPLYMSG^XMXAPI (DBIA 2729). Usage: S variable=$$ENT^XMA2R(XMZ,XMSUBJ,.XMTEXT,XMSTRIP,XMDUZ,XMNET) If successful, function returns: Message IEN in file 3.9 of the reply. If failure, function returns: The letter "E", followed by a number, followed by an error message. e.g. "E3 Subject too long or short !" Examples: W $$ENT^XMA2R(51537,"test of XMA2R",.T,"",DUZ) E2 No message text ! S T(1)="test line 1" S X=$$ENT^XMA2R(51537,"test of XMA2R",.T,"",DUZ) W X 51541 VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the MESSAGE FILE (#3.9) of the message being replied to. VARIABLES: XMSUBJ TYPE: Input VARIABLES DESCRIPTION: Subject of the reply. Must be 3-65 characters. VARIABLES: XMTEXT TYPE: Input VARIABLES DESCRIPTION: Text of the reply. Must be an array, passed by reference, and in a format acceptable as input to FileMan word-processing fields. VARIABLES: XMSTRIP TYPE: Input VARIABLES DESCRIPTION: (optional) String containing characters to be stripped from the text of the reply (XMTEXT). Default is none. VARIABLES: XMDUZ TYPE: Used VARIABLES DESCRIPTION: (optional) The DUZ of the user sending the answer. May also be free text. Default is DUZ. VARIABLES: XMNET TYPE: Used VARIABLES DESCRIPTION: (optional) If the sender of the original message is at a remote site, should the reply be sent to the sender, too? Possible values: 0=no (default) 1=yes This parameter is ignored if the message is from a local user. COMPONENT/ENTRY POINT: $$ENTA COMPONENT DESCRIPTION: Send an answer to a message. Create a new message containing the response and send it only to the author of the original message. This function is non-interactive. Compare to ANSRMSG^XMXAPI (DBIA 2729). Usage: S variable=$$ENTA^XMA2R(XMZ,XMSUBJ,.XMTEXT,XMSTRIP,XMDUZ) If successful, function returns: Message IEN in file 3.9 of the answer. If failure, function returns: The letter "E", followed by a number, followed by an error message. e.g. "E1 No subject !" VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the MESSAGE FILE (#3.9) of the message being answered. VARIABLES: XMSUBJ TYPE: Input VARIABLES DESCRIPTION: Subject of the answer. Must be 3-65 characters. VARIABLES: XMTEXT TYPE: Input VARIABLES DESCRIPTION: Text of the answer. Must be an array, passed by reference, and in a format acceptable as input to FileMan word-processing fields. VARIABLES: XMSTRIP TYPE: Used VARIABLES DESCRIPTION: (optional) String containing characters to be stripped from the text of the answer (XMTEXT). Default is none. VARIABLES: XMDUZ TYPE: Used VARIABLES DESCRIPTION: (optional) The DUZ of the user sending the answer. It may also be free text. Default is DUZ. NUMBER: 1146 IA #: 1146 DATE CREATED: FEB 20, 1995 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMBGRP NAME: MAIL GROUP API ID: XMBGRP GENERAL DESCRIPTION: This mail group API contains the following entry points: $$DM^XMBGRP Delete local members from a mail group. $$MG^XMBGRP Create a new mail group or add local members to an existing mail group. STATUS: Active COMPONENT/ENTRY POINT: $$MG COMPONENT DESCRIPTION: Create a mail group or add local members to an existing mail group. If the mail group does not exist, it will be created. Local members may be added. There is no way to add other kinds of members. XMTYPE, XMORG, XMSELF, and XMDESC are accepted. If the mail group exists, local members must be added to it. No other changes can be made. XMTYPE, XMORG, XMSELF, and XMDESC are ignored. There is no MailMan API to change any other mail group fields. Usage: S X=$$MG^XMBGRP(XMGROUP,XMTYPE,XMORG,XMSELF,.XMY,.XMDESC,XMQUIET) This function returns the mail group IEN if successful; 0 if not. Parameters: XMGROUP mail group IEN or name XMTYPE mail group type (public or private) XMORG organizer DUZ XMSELF self enrollment allowed? .XMY array of local members .XMDESC array of text for the mail group description XMQUIET silent flag VARIABLES: XMGROUP TYPE: Input VARIABLES DESCRIPTION: Full Mail group name, exactly as it should appear in the .01 field of the MAIL GROUP file (3.8). Must be 3-30 characters. VARIABLES: XMTYPE TYPE: Used VARIABLES DESCRIPTION: (optional) Type of mail group. Used only for creating a mail group, otherwise it's ignored. Possible values are: 0 - public (default) 1 - private VARIABLES: XMORG TYPE: Used VARIABLES DESCRIPTION: (optional) DUZ of group organizer. Used only for creating a mail group, otherwise it's ignored. Default is DUZ of the user performing the API. If XMORG is less than 1, it is set to .5. VARIABLES: XMSELF TYPE: Used VARIABLES DESCRIPTION: (optional) Allow self enrollment? (0=no; 1=yes) Used only for creating a mail group, otherwise it's ignored. Default is 1 (yes). VARIABLES: XMY TYPE: Used VARIABLES DESCRIPTION: (optional for mail group creation; mandatory otherwise) Array of local members to add to the mail group. XMY(user duz)="" Note that only user DUZs are accepted. User names are not. Remote addresses, or anything else, are not. XMY is killed upon successful completion of this API. VARIABLES: XMDESC TYPE: Used VARIABLES DESCRIPTION: (optional) Array of text to put in the description field of the mail group. Used only for creating a mail group, otherwise it's ignored. The text array must be in a format acceptable to FileMan word-processing APIs. VARIABLES: XMQUIET TYPE: Used VARIABLES DESCRIPTION: (optional) Silent Flag. What should happen if there are any errors, or if (during mail group creation only) local members were successfully added to the mail group? 0 - Display it to the user. 1 - Sent it in a message to the Postmaster and the user (DUZ) performing the API. (Default) COMPONENT/ENTRY POINT: $$DM COMPONENT DESCRIPTION: Delete local members from a mail group. There is no MailMan API to delete other kinds of members. Usage: S X=$$DM^XMBGRP(XMGROUP,.XMY,XMQUIET) This function returns 1 if successful; 0 if not. Parameters: XMGROUP mail group IEN or full name .XMY array of local members to be deleted XMQUIET silent flag (1=Silent, 0=Interactive) VARIABLES: XMGROUP TYPE: Input VARIABLES DESCRIPTION: Mail group IEN in the MAIL GROUP file (3.8), or the full mail group name, exactly as it appears in the .01 field. VARIABLES: XMY TYPE: Input VARIABLES DESCRIPTION: Array of local members to delete from the mail group. XMY(user duz)="" Note that only user DUZs are accepted. User names are not. VARIABLES: XMQUIET TYPE: Used VARIABLES DESCRIPTION: (optional) Silent Flag. Possible values: 0 - Any errors are displayed to the user. 1 - Any errors are sent in a message to the Postmaster and the user (DUZ) performing the API. (Default) NUMBER: 1147 IA #: 1147 DATE CREATED: FEB 20, 1995 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMAD2 NAME: LOOKUP / CREATE BASKET ID: XMAD2 GENERAL DESCRIPTION: This function looks up a mail basket name and returns its IEN. If the basket doesn't exist, the basket will be created and the IEN of the newly created basket will be returned. STATUS: Active MAIL MESSAGE: 14000225 COMPONENT/ENTRY POINT: $$BSKT COMPONENT DESCRIPTION: This function looks up a mail basket name and returns its IEN. Given a basket name and a user's DUZ, lookup the basket. If it doesn't exist, create it and return its IEN. If it does exist, return its IEN. If there's an error, return an error message. CRE8BSKT^XMXAPIB (DBIA 2723) can also be used to create a basket. Usage: S variable=$$BSKT^XMAD2(XMKN,XMDUZ) Where: XMKN=Basket-name XMDUZ=DUZ (user IEN) Examples: W $$BSKT^XMAD2("ZZZZZ",9999) 999 (The IEN is returned when there are no errors.) W $$BSKT^XMAD2(1,1) or W $$BSKT^XMAD2("A",1) An error message to the effect that Basket names contain 2 to 30 chars. W $$BSKT^XMAD2("zzzzzz",99999999) An error message to the effect that No such MailMan user as 99999999 is known. S B=$$BSKT^XMAD2(X,Y) I B<1 W !!,"MailMan found the following error: ",B MailMan found the following error: An error message to the effect that a certain error occurred. VARIABLES: XMKN TYPE: Input VARIABLES DESCRIPTION: The name of the basket to be looked up or created. It must be the exact name. It must be 2-30 characters. VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The DUZ of the user whose basket is being looked up or created. NUMBER: 1148 IA #: 1148 DATE CREATED: FEB 20, 1995 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMCTLK NAME: MAILMAN: Interactive control of a port ID: XMCTLK GENERAL DESCRIPTION: Device and Line Checking GO^XMCTLK This routine allows one to interactively use a device and displays keyboard entry and data coming down the line. Usage: D GO^XMCTLK Note: DHCP programming environment is assumed (initialized through the execution of D ^XUP or sign-on through ^XUS). All I/O from the keyboard and device chosen are echoed on screen. It is good for testing devices, Network outgoing points, etc. What is displayed on the screen may be captured into a mail message. Type an "A" to communicate with TalkMan. STATUS: Active NUMBER: 1150 IA #: 1150 DATE CREATED: FEB 20, 1995 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMA03 NAME: RESEQUENCE MESSAGES API ID: XMA03 GENERAL DESCRIPTION: This API resequences the messages in your basket. STATUS: Active COMPONENT/ENTRY POINT: $$REN COMPONENT DESCRIPTION: This function performs an integrity check on the user's basket and then resequences the messages in the basket. Only the user or a surrogate may use this API. If successful, returns the string: "Resequenced from 1 to n", where n is the number of messages in the basket. If unsuccessful, returns the null string. Compare to RSEQBSKT^XMXAPIB (DBIA 2723). Usage: S X=$$REN^XMA03(XMDUZ,XMK) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: DUZ of the user whose basket is to be resequenced. VARIABLES: XMK TYPE: Input VARIABLES DESCRIPTION: IEN of the basket to be resequenced in the user's mailbox. NUMBER: 1151 IA #: 1151 DATE CREATED: FEB 20, 1995 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMS1 NAME: MAILMAN: Server API ID: XMS1 GENERAL DESCRIPTION: ^XMS1 contains the following application programmer functions: $$STATUS^XMS1(MSGIEN,RDUZ) which extracts the status from network messages only. $$SRVTIME(MSGIEN,RDUZ,Status) which sets status of recipients in a message. Appendix 1 -- Message Server Protocol Overview A server is an option which is invoked when a mail message that has been addressed to it has been delivered. As an option, many of the parameters associated with the servers are embedded in the definition of the option. Therefore, in order to understand servers completely, you should refer to the server documentation in Kernel 7.0 manuals. Options are listed in the Menu Management documentation. Servers may or may not receive data. The received data usually comes in the form of the text of the message being delivered to it, but the data may also be pointed to by the message, and exist in the system either because it was there in the beginning, or because it arrived independently. Servers may be addressed from a remote site. A server on ALTOONA.VA.GOV may receive a message addressed to it from WASHINGTON.VA.GOV. In fact, this is very common. There are security features as parameters of the option that has been designated as a server because of the fact. Please be aware of these security parameters. Messages addressed to servers will not be scheduled if security is not passed. Filegrams work through use of a server. Data is loaded into a mail message, addressed and when delivered, processed by the filegram server into the receiving database. Servers are always invoked through tasks that are set up when the message is delivered into the system locally or over the network. One of the options is to "Run Immediately". Then the task is scheduled to run "NOW". However, tasks may not need to be scheduled at all because the system manager has stated so in the entry for the server in the Option file or because of a problem. See the Menu Management documentation in the MailMan Technical Manual and Systems Management Guide for more information concerning this. Server Statuses Server recipients are recorded in the recipient chain of a message and appear similarly to other users. MailMan enters statuses on its own as stages in the server process are reached. First, the message is marked as "Awaiting Server". This indicates that the message has been received and the option is a valid one. At this point, a task has been created to actually invoke MenuMan to schedule or perform the service (option) required. The last status which MailMan sets is "Served", which means that MenuMan has been called successfully and MenuMan has either performed the task in the case of a server that runs immediately, or that some other action has been done. At this point, a task could be scheduled to invoke the server or simply a message could be sent to indicate that the task exists and needs to be scheduled, or some other action that was required was performed. MenuMan has its own statuses which will be used. $$SRVTIME^XMS1 This extrinsic function sets status of recipients in a message. Usage: S X=$$SRVTIME^XMS1(A,B,C) Where: A = XMZ (message number) B = A string representing the recipient name C = Status is free-text (String less than nine (9) characters in length) If successful, X = 0 ...or If unsuccessful, X will be a number followed by a human readable error Addressing a Server To address a server, precede the recipient name with "S." (e.g., S.XMECHO). This example sends a message to the Mail Man Echo Tester server. "S." must be followed by an option name from the Option file in the Target Domain. If not, a "Recipient not Found" error will occur. A "Recipient Ambiguous" error will occur, if there is more than one option whose name partially matches the name addressed. The District Registry server for admitting a new patient could be addressed as follows: S.DGDISTADMIT@SANFRANCISCO.VA.GOV The message is destined for the DGDISTADMIT option at San Francisco. Replies to this message would be from this same name. Writing a Server Program The server communicates with mail messages in specific ways. Code is used to interface the server to the message system. The code below returns the original message to the sender: ECHO ; K XMY S XMSUB=$E("Server echo of'"_XMBSUB_"`",1,65) S XMY(XMFROM)="",XMTXT="^XMB(3.9,"_XMZ_",2," D ^XMD Q In this example, the variable XMFROM contains the sender address and is supplied to the server when invoked. Other variables also exist upon invocation of the server. The XMF.1 example server program is supplied with MailMan. XMF1 uses some of the other variables supplied to the server. Execute variable XMREC to read a line of the message. XMER and XMRG are returned. XMER This variable returns the execution status of XMREC. XMER<0, if there is no more message text to read. The value of XMER will be zero (0), if XMRG is being returned as non-null. XMRG, in that case, will have as its value the text of the next line of the message. XMRG The value of XMRG will be the next line of message text. XMRG will always be defined, though it will be null when XMER<0. XMPOS This variable contains the current position of the text returned in the variable XMGR. It is initialized if it is undefined, but should be killed by the server when it is finished "Reading" the message. Here's another example of code, this time from XMF1: S XMA=0 A ; X XMREC ; Receive a line I $D(XMER) G Q;XMER<0 ; Check for end of message S XMA=XMA+1 ; Increment local line count S XMTEXT(XMA)=XMRG ; Set local array G A ; Go back for another line Double Serving Messages On occasion, the transmission/receive process is interrupted by a system back-up. It appears to result in the same message being served twice. The Audit Log for the Options file shows two messages with the same message number and subject, but with different Date/Times and Job Numbers. To avoid this, application servers should be written such that they check for and avoid processing of the same message being delivered to any particular server. MailMan transparently checks this and does not deliver twice to mail boxes. However, devices and servers do not have mail boxes to check against. Servers can have some understanding of special mail baskets in the Postmaster's mail box and can be written to check for duplicate deliveries (See reference XMAIC entry points in the Callable Routines section of the Technical Manual and System Manager's Guide). STATUS: Active COMPONENT/ENTRY POINT: STATUS COMPONENT DESCRIPTION: $$STATUS^XMS1 This extrinsic function extracts the status from network messages only. Usage: S X=$$STATUS^XMS1(A,B) Where: A = Message Number B = Recipient (pointer to File #200 or free-text Network Address) If successful, X=String ...or If unsuccessful X="" Examples: W $$STATUS^XMS1(51555,"NOSS,VER@VER.GOLD.VA.GOV") Awaiting transmission. COMPONENT/ENTRY POINT: $$SRVTIME COMPONENT DESCRIPTION: $$SRVTIME^XMS1 This extrinsic function sets status of recipients in a message. Usage: S X=$$SRVTIME^XMS1(A,B,C) Where: A = XMZ (message number) B = A string representing the recipient name C = Status is free-text (String less than nine (9) characters in length) If successful, X = 0 ...or If unsuccessful, X will be a number followed by a human readable error NUMBER: 1152 IA #: 1152 DATE CREATED: FEB 23, 1995 CUSTODIAL PACKAGE: MINIMAL PATIENT DATASET CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAMPAPI0 NAME: VAM ID: VAMPAPI0 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13966784 COMPONENT/ENTRY POINT: MPD COMPONENT DESCRIPTION: MPD^VAMPAPI0(IN,OUT,SCHM,CRIT,BUFFER,WAIT,STARTAT) VARIABLES: IN TYPE: Input VARIABLES DESCRIPTION: Full Global Reference to a global containing an array of SSNs VARIABLES: OUT TYPE: Input VARIABLES DESCRIPTION: Full Global Reference for location of where information will be returned to VARIABLES: SCHM TYPE: Input VARIABLES DESCRIPTION: Search scheme to use- Supported schemes: MPD**00001 - Return full information MPD**00002 - Return site information (for use with PPP) MPD**00003 - Return CD-ROM information VARIABLES: CRIT TYPE: Input VARIABLES DESCRIPTION: Input criteria - Full global reference to an array containing a list of sites to exclude. Global has the form: ^GLOBAL("500")="" ^GLOBAL("520")="" ^^^ ^^^-- | | |-Global |- Site number. Name So CRIT would look like: ^["TRN","KER"]GLOBAL VARIABLES: WAIT TYPE: Input VARIABLES DESCRIPTION: How long to wait for the server to acknowledge the request (else fail saying the server is busy) VARIABLES: STARTAT TYPE: Input VARIABLES DESCRIPTION: SSN to start searching at. The server will begin searching at that SSN in the input array. VARIABLES: BUFFER TYPE: Input VARIABLES DESCRIPTION: Sets the size of the output buffer. It is up to the client application to take SSNs out of the output array and clear it once the data has been read. SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE ISC: Albany NUMBER: 1153 IA #: 1153 FILE NUMBER: 9.4 GLOBAL ROOT: DIC(9.4) DATE CREATED: FEB 24, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PACKAGE FILE REFERENCES CLEANUP ID: DIC(9.4) GENERAL DESCRIPTION: Loop through the "C" cross-reference on the PACKAGE file and delete any extra entries with the subscribing package namespace. Where necessary, the name of a package may be changed to make it unique. STATUS: Active DURATION: Next Version SUBSCRIBING PACKAGE: DRG GROUPER ISC: Albany SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham NUMBER: 1154 IA #: 1154 FILE NUMBER: 45.7 GLOBAL ROOT: DIC(45.7, DATE CREATED: MAR 02, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Supported TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DIC(45.7, ID: DIC(45.7, GLOBAL REFERENCE: DIC(45.7,D0,0) FIELD NUMBER: 1 FIELD NAME: SPECIALTY LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: Pointer to Specialty File. GENERAL DESCRIPTION: The integration agreement allows reading (with FileMan only) the SPECIALTY field (#1) of the FACILITY TREATING SPECIALTY file (#45.7). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14062201 NUMBER: 1155 IA #: 1155 FILE NUMBER: 100.9 GLOBAL ROOT: ORD(100.9 DATE CREATED: MAR 08, 1995 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1155 ID: ORD(100.9 GLOBAL REFERENCE: ORD(100.9,0) GLOBAL DESCRIPTION: The Progress Notes package makes this reference. GLOBAL REFERENCE: ORD(100.9,DA,0) FIELD NUMBER: .02 FIELD NAME: PACKAGE ID LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: The Lab package makes this reference. GENERAL DESCRIPTION: This DBIA allows references to the OE/RR Notifications (#100.9) file. VIEWER: SCHLEHUBER,PAM VIEWER: PRICE,DEBORAH VIEWER: DEFA,TANA VIEWER: EBERT,AL VIEWER: BUECHLER,MELANIE K VIEWER: MERRILL,DAVID P STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30260337 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING DETAILS: A check on this file is made from the PN package: $D(^ORD(100.9,0)) SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING DETAILS: A direct reference is made to this file to get data needed to delete old lab notifications. NUMBER: 1156 IA #: 1156 DATE CREATED: MAR 08, 1995 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSCW NAME: DBIA1156 ID: GMTSCW GENERAL DESCRIPTION: Progress Notes rtn ^GMRPNCW is checking $L($T(CS^GMTSCW)) to ascertain if the 'Advance Directive' component exported with GMTS*2.5*15 has been installed before proceeding with the enhanced CWAD display. VIEWER: SCHLEHUBER,PAM VIEWER: PRICE,DEBORAH VIEWER: CARLSON-GOTTS,NANCY VIEWER: DEFA,TANA VIEWER: EBERT,AL VIEWER: RUSSELL,JOEL VIEWER: WINTERTON,STEVEN VIEWER: MERRILL,DAVID P STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14173030 COMPONENT/ENTRY POINT: CD COMPONENT DESCRIPTION: PNs ^GMRPNCW gets for its' existence. SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 1157 IA #: 1157 DATE CREATED: MAR 08, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XPDMENU NAME: XPDMENU ID: XPDMENU GENERAL DESCRIPTION: Extrinsic functions that can be used to manage the Menu field in the Options file. The ADD and DELETE functions are used to add and delete menu items for a given option. STATUS: Active MAIL MESSAGE: 33562572 COMPONENT/ENTRY POINT: ADD COMPONENT DESCRIPTION: ADD(MENU,OPT,SYN,ORD) is used to add an option to the Menu of another option. Return 1 if the function succeeded, 0 if it failed. VARIABLES: MENU TYPE: Input VARIABLES DESCRIPTION: MENU is the name of the Option you want to add a menu item to. VARIABLES: OPT TYPE: Input VARIABLES DESCRIPTION: OPT is the name of the option you want to add to the menu item of MENU. VARIABLES: SYN TYPE: Input VARIABLES DESCRIPTION: SYN is the value you want added to the SYNONYM field under the MENU field for OPT. VARIABLES: ORD TYPE: Input VARIABLES DESCRIPTION: ORD is the value you want added to the DISPLAY ORDER field under the MENU field for OPT. COMPONENT/ENTRY POINT: DELETE COMPONENT DESCRIPTION: DELETE(MENU,OPT) is used to delete an option from the Menu field of another option. Return 1 if the function succeeded, 0 if it failed. VARIABLES: MENU TYPE: Input VARIABLES DESCRIPTION: MENU is the name of the Option you want to delete a menu item from. VARIABLES: OPT TYPE: Input VARIABLES DESCRIPTION: OPT is the name of the option you want to delete from the menu item of MENU. COMPONENT/ENTRY POINT: RENAME COMPONENT DESCRIPTION: RENAME(OLD,NEW) is used to rename an option. VARIABLES: OLD TYPE: Input VARIABLES DESCRIPTION: OLD is the current name of the option. VARIABLES: NEW TYPE: Input VARIABLES DESCRIPTION: NEW is the name the option is being renamed to. COMPONENT/ENTRY POINT: LKOPT COMPONENT DESCRIPTION: LKOPT(X) is used to lookup options IEN using the "B" cross reference. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: X is the name of the option. The Option File IEN is returned. COMPONENT/ENTRY POINT: OUT COMPONENT DESCRIPTION: OUT(OPT,TXT) is used to place an option Out of Order. VARIABLES: OPT TYPE: Input VARIABLES DESCRIPTION: OPT is the name of the Option you want to place Out-of-Order. VARIABLES: TXT TYPE: Input VARIABLES DESCRIPTION: TXT is the text that will be placed in the Out-of-Order field. NUMBER: 1159 IA #: 1159 DATE CREATED: MAR 30, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTAUD NAME: DBIA1159 ID: DGMTAUD GENERAL DESCRIPTION: The IVM package files new Means Tests into PIMS Means Test module. This routine contains utilities for audit changes to Means Tests. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14558289 COMPONENT/ENTRY POINT: SET COMPONENT DESCRIPTION: This call is used to update the MEANS TEST CHANGES file with demographic differences between the IVM and VAMC dependents. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN points to the patient in file #2. VARIABLES: DGMTI TYPE: Input VARIABLES DESCRIPTION: DGMTI points to Means Test in file #408.31. VARIABLES: DGMTYPT TYPE: Input VARIABLES DESCRIPTION: DGMTYPT is 1 (Means Test). VARIABLES: DGMTACT TYPE: Input VARIABLES DESCRIPTION: DGMTACT is a code indicating type of demographic data. VARIABLES: DGMTSOLD TYPE: Input VARIABLES DESCRIPTION: DGMTSOLD is the old value (VAMC). VARIABLES: DGMTSNEW TYPE: Input VARIABLES DESCRIPTION: DGMTSNEW is the new value (IVM). VARIABLES: DGDEPI TYPE: Input VARIABLES DESCRIPTION: DGDEPI is the pointer to the dependent in file #408.13. VARIABLES: DGMTP TYPE: Input VARIABLES DESCRIPTION: DGMTP is the ANNUAL MEANS TEST 0th node prior to Means Test upload. VARIABLES: 'DGMTA' TYPE: Input VARIABLES DESCRIPTION: DGMTA is the ANNUAL MEANS TEST 0th node after Means Test upload. SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 1160 IA #: 1160 FILE NUMBER: 1 GLOBAL ROOT: DD(164.07,0,'NM' DATE CREATED: MAR 14, 1995 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ONCOLOGY FILE NAME CLEAN-UP ID: DD(164.07,0,'NM' GLOBAL REFERENCE: DD(164.07,0,'NM','ICDO-1ENCODING') GLOBAL REFERENCE: DD(164.07,0,'NM','ICDO-1ENDCODING') GENERAL DESCRIPTION: Clean-up of old file names. STATUS: Active DURATION: Next Version MAIL MESSAGE: 14083098 GOOD ONLY FOR VERSION: 2.11 SUBSCRIBING PACKAGE: ONCOLOGY ISC: Washington/Silver Spring NUMBER: 1162 IA #: 1162 FILE NUMBER: 43.4 GLOBAL ROOT: DIC(43.4, DATE CREATED: MAR 14, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1161-B ORIGINAL NUMBER: 1161 ID: DIC(43.4, GLOBAL REFERENCE: DIC(43.4,AEDR,CODE, FIELD NUMBER: .01 FIELD NAME: NUMBER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Admitting regulation number FIELD NUMBER: 1 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The name of the VA admitting regulation GLOBAL DESCRIPTION: The file contains the recognized VA admitting regulations under which a patient may be admitted to a VA facility GENERAL DESCRIPTION: Convert speciality code to its text equivalent STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14264660 SUBSCRIBING PACKAGE: MINIMAL PATIENT DATASET ISC: Albany SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM SUBSCRIBING DETAILS: ADDED 12/11/2008 DATE/TIME EDITED: DEC 11, 2008@20:54 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BAUMANN,SCOTT WITH CONCURRENCE OF: PRIETULA,LINDA DATE/TIME EDITED: DEC 11, 2008@20:55 ACTION: USAGE CHOICE CHANGED AT THE REQUEST OF: BAUMANN,SCOTT WITH CONCURRENCE OF: PRIETULA,LINDA NUMBER: 1163 IA #: 1163 FILE NUMBER: 40.7 GLOBAL ROOT: DIC(40.7, DATE CREATED: MAR 14, 1995 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1161-C ORIGINAL NUMBER: 1161 ID: DIC(40.7, GLOBAL REFERENCE: DIC(40.7,C,CODE FIELD NUMBER: 1 FIELD NAME: AMIS REPORTING STOP CODE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the number related to the stop code that is used when generating the OPC file. FIELD NUMBER: .01 FIELD NAME: name LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Contains the name of the clinic stop code. GLOBAL DESCRIPTION: This file contains all Clinic Stops and their associated AMIS stop codes. GENERAL DESCRIPTION: Convert Speciality code to its text equivalent STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14264660 SUBSCRIBING PACKAGE: MINIMAL PATIENT DATASET ISC: Albany NUMBER: 1164 IA #: 1164 FILE NUMBER: 42.4 GLOBAL ROOT: DIC(42.4, DATE CREATED: MAR 14, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1161-D ORIGINAL NUMBER: 1161 ID: DIC(42.4, GLOBAL REFERENCE: DIC(42.4,CODE, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The field contains the name of the specialities allowable for selection through PTF. GLOBAL DESCRIPTION: The file contains recognized PTF treating specialties. GENERAL DESCRIPTION: Convert speciality code to text equivalent STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14264660 SUBSCRIBING PACKAGE: MINIMAL PATIENT DATASET ISC: Albany NUMBER: 1166 IA #: 1166 FILE NUMBER: 394.61 GLOBAL ROOT: VAT(394.61 DATE CREATED: MAR 16, 1995 CUSTODIAL PACKAGE: PATIENT DATA EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1166 ID: VAT(394.61 GLOBAL REFERENCE: VAT(394.61,TRANPTR, FIELD NUMBER: .01 FIELD NAME: Transaction Number LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: VAT(394.61,TRANPTR,SEG,B, FIELD NUMBER: 80 FIELD NAME: Data Segment LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: VAT(394.61,TRANPTR,ATHR1, FIELD NUMBER: 50 FIELD NAME: Date/Time of Reply LOCATION: ATHR1;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 51 FIELD NAME: Authorizer LOCATION: ATHR1;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: VAT(394.61,TRANPTR,ATHR2, FIELD NUMBER: 60 FIELD NAME: Authorizing Site LOCATION: ATHR2;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 61 FIELD NAME: Authorizing Address LOCATION: ATHR2;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: VAT(394.61,TRANPTR,QRY, FIELD NUMBER: 11 FIELD NAME: Patients SSN LOCATION: QRY;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Used to verify and extract PDX transaction information STATUS: Active MAIL MESSAGE: 14263120 SUBSCRIBING PACKAGE: PHARMACY PRESCRIPTION PRACTICE ISC: Albany NUMBER: 1167 IA #: 1167 DATE CREATED: APR 14, 1995 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED ROUTINE: YSINI02Q NAME: DBIA1167 ID: YSINI02Q GENERAL DESCRIPTION: When sites run Mental Health V. 5.01 inits and they have the DSM3 ^DIC(627, file that has the 2nd and 3rd pieces flipped the install gracefully aborts and tells the user that the DSM3 file is missing conversion node(s)!! The DSM conversion cannot continue and the correct versions of this file should have been installed during the Mental Health V. 5.01 initialization process. Permission from the FILEMAN community to do the following: 1. Hard KILL the node ^DIC(627,310.1) at END+1^YSD4PRE. 2. Reverse the values of the 2nd and third pieces on line Q+36^YSINI035. All routine changes will be sent out in patch YS*5.01*6. STATUS: Active DURATION: Next Version MAIL MESSAGE: 14313534 GOOD ONLY FOR VERSION: 5.01 SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas NUMBER: 1168 IA #: 1168 FILE NUMBER: 0 GLOBAL ROOT: DD( DATE CREATED: MAR 21, 1995 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: FILE 124.2 B CROSS-REFERENCE CHANGE ID: DD( GLOBAL REFERENCE: DD(124.6,.01,1,1,1) GLOBAL DESCRIPTION: The modification here is to change: ^DD(124.6,.01,1,1,1)=S ^GMRD(124.6,"B",$E(X,1,30),DA)="" to: ^DD(124.6,.01,1,1,1)=S ^GMRD(124.6,"B",$E(X,1,60),DA)="" GLOBAL REFERENCE: DD(124.6,.01,1,1,2) GLOBAL DESCRIPTION: The modification here is to change: ^DD(124.6,.01,1,1,2)=K ^GMRD(124.6,"B",$E(X,1,30),DA) to: ^DD(124.6,.01,1,1,2)=K ^GMRD(124.6,"B",$E(X,1,60),DA) GENERAL DESCRIPTION: Since the .01 field of the TG Term (124.6) file is 2-60 characters in length, and there is no need to add a second regular cross-reference, the Text Generator would request an exemption to modify the "B" cross- reference so that it uses 60 characters instead of 30. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14370481 SUBSCRIBING PACKAGE: GEN. MED. REC. - GENERATOR ISC: Hines NUMBER: 1169 IA #: 1169 FILE NUMBER: 771.5 GLOBAL ROOT: HL(771.5, DATE CREATED: MAR 21, 1995 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1169-A ORIGINAL NUMBER: 1169 ID: HL(771.5, GLOBAL REFERENCE: NONE FIELD NUMBER: .01 FIELD NAME: VERSION NUMBER LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Add version 2.2 if it doesn't exit GLOBAL DESCRIPTION: A list of HL7 versions supported by the DHCP site GENERAL DESCRIPTION: Check for existance of version 2.2 in 771.5. If missing add via Fileman STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: MINIMAL PATIENT DATASET ISC: Albany SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 1170 IA #: 1170 FILE NUMBER: 771.2 GLOBAL ROOT: HL(771.2, DATE CREATED: JUL 29, 1997 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1169-B ORIGINAL NUMBER: 1169 ID: HL(771.2, GLOBAL REFERENCE: NONE FIELD NUMBER: .01 FIELD NAME: ABBREVIATED NAME LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: The three character HL7 message type abbreviation GLOBAL DESCRIPTION: A list of HL7 messages supported by the DHCP site GENERAL DESCRIPTION: Checks and adds "ADR" message type if it does not exist in HL7 MESSAGE TYPE file (#771.2). This DBIA is being revised for version 1.6 of HL7. Applications wishing to export interfaces may have the need to update specific HL7 reference files with entries relevant to the current HL7 standard or VA-specific 'Z' segments. Applications may read/update the following files using KIDS or documented VA Fileman calls following written notification and approval of an appropriate official in Technical Integration. 771.2 HL7 MESSAGE TYPE 771.1 HL7 FIELD 771.3 HL7 SEGMENT 771.5 HL7 VERSION 779.001 HL7 EVENT TYPE CODE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24593960 SUBSCRIBING PACKAGE: MINIMAL PATIENT DATASET ISC: Albany SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham EDITOR: CLEMENS,JOHN NUMBER: 1171 IA #: 1171 FILE NUMBER: 74 GLOBAL ROOT: RARPT DATE CREATED: MAR 21, 1995 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1171 ID: RARPT GLOBAL REFERENCE: RARPT(D0,2005, FIELD NUMBER: .01 FIELD NAME: IMAGE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains a pointer to File 2005 (IMAGE). GLOBAL REFERENCE: RARPT( FIELD NUMBER: 45 FIELD NAME: NO PURGE INDICATOR LOCATION: NOPURGE;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is set when the corresponding field of the associated exam is set to 'NO PURGE'. FIELD NUMBER: 2 FIELD NAME: PATIENT NAME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: CASE NUMBER LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: RARPT(D0,2005,'B', GLOBAL DESCRIPTION: Direct global read on the "B" x-ref. GENERAL DESCRIPTION: The Radiology Package will reserve field 2005 of file #74 to be used as a multiple for pointers to file #2005. This field will first be supported in Radiology/Nuclear Medicine Version 4.5. Imaging will write pointers to field 2005 of file #74. In addition, Imaging reads the 'NO PURGE' node to determine if images should be purged. If this node is set the Image Purge routine will not delete images associated to the case study (radiology case number). Direct global read is required due to the massive amount of image transactions acquired at sites. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32404765 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring NUMBER: 1172 IA #: 1172 FILE NUMBER: 70 GLOBAL ROOT: RADPT DATE CREATED: MAY 05, 1995 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1172 ID: RADPT CREATOR: BARRIOS,LUCILLE GLOBAL REFERENCE: RADPT('AE',CASENUMBER,DA(2),DA(1),DA GLOBAL DESCRIPTION: Cross reference set by the EXAM STATUS field (#3) of the EXAMINATION sub-file (#70.03). Used to look-up exams that are active/incomplete. GLOBAL REFERENCE: RADPT('ADC',CASENUMBER,DA(2),DA(1),DA) GLOBAL DESCRIPTION: This is the date (MMDDYY) - CASE # cross reference set by the CASE NUMBER field of the EXAMINATION sub-file (#70.03) GLOBAL REFERENCE: RADPT('AS',EXAM STATUS,DA(2),DA(1),DA GLOBAL DESCRIPTION: Used to produce a list of active/incomplete exams. GLOBAL REFERENCE: RADPT(DA(1),'DT',DA,0 FIELD NUMBER: 3 FIELD NAME: HOSPITAL DIVISION LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Pointer to the RAD/NUC MED DIVISION file (79). FIELD NUMBER: 4 FIELD NAME: IMAGING LOCATION LOCATION: 0;4 ACCESS: Read w/Fileman FIELD DESCRIPTION: Pointer to 'IMAGING LOCATIONS' file (#79.1), the location where the exam was performed. GLOBAL REFERENCE: RADPT(DA(2),'DT',DA(1),'P',DA,0 FIELD NUMBER: 2 FIELD NAME: PROCEDURE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is a pointer to file 71, RAD/NUC MED PROCEDURES. FIELD NUMBER: 3 FIELD NAME: EXAM STATUS LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is a pointer to file 72, EXAMINATION STATUS. FIELD NUMBER: 11 FIELD NAME: IMAGING ORDER LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is a pointer to file 75.1, RAD/NUC MED ORDERS. FIELD NUMBER: 12 FIELD NAME: PRIMARY INTERPRETING RESIDENT LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is a pointer to file 200, NEW PERSON. FIELD NUMBER: 15 FIELD NAME: PRIMARY INTERPRETING STAFF LOCATION: 0;15 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is a pointer to file 200, NEW PERSON. FIELD NUMBER: 16 FIELD NAME: COMPLICATION LOCATION: 0;16 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is a pointer to file 78.1, COMPLICATION TYPES. FIELD NUMBER: 16.5 FIELD NAME: COMPLICATION TEXT LOCATION: COMP ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to give a brief explanation (4-100 characters) to describe the exam complication. FIELD NUMBER: 17 FIELD NAME: REPORT TEXT LOCATION: 0;17 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is a pointer to file 74, RADIOLOGY REPORT. FIELD NUMBER: 22 FIELD NAME: REQUESTING LOCATION LOCATION: 0;22 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is a pointer to file 44, HOSPITAL LOCATION. FIELD NUMBER: .01 FIELD NAME: CASE NUMBER LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: The case number assigned to the exam study. FIELD NUMBER: 21 FIELD NAME: REQUESTED DATE LOCATION: 0;21 ACCESS: Read w/Fileman FIELD DESCRIPTION: The date the exam was requested. FIELD NUMBER: 31 FIELD NAME: SITE ACCESSION NUMBER LOCATION: 0;31 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field consists of the site number, date/time and sequential case number separated by dashes. This field is generated by the VistA Radiology/Nuclear Medicine application. FIELD NUMBER: 500 FIELD NAME: NUCLEAR MED DATA LOCATION: 0;28 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: If any radiopharmaceuticals were administered to the patient during this exam, they may be recorded here. Radiopharmaceutical data may be automatically entered, if it exists on the procedure file. It is also editable during case edit options and may be configured for editing during status tracking. GLOBAL REFERENCE: RADPT(DA(3),'DT',DA(2),'P',DA(1),'M',DA,0 FIELD NUMBER: 125 FIELD NAME: PROCEDURE MODIFIERS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Imaging modifier, pointer to file 71.2 (PROCEDURE MODIFIERS). GLOBAL DESCRIPTION: Stores the imaging modifiers that are associated with the exam. GLOBAL REFERENCE: RADPT('AO' GLOBAL DESCRIPTION: Global is a cross reference on IMAGING ORDER field (70.03,#11). Used to link the Radiology/Nuclear Medicine Request Order file (#75.1) to the exam. GLOBAL REFERENCE: RADPT(DA(3),'DT',DA(2),'P',DA(1),'RX' FIELD NUMBER: .01 FIELD NAME: MED ADMINISTERED LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: If any medications were administered to the patient during this exam, they may be recorded here. If medications are associated with a procedure during system set-up, the system will enter them automatically when the procedure is registered. GLOBAL DESCRIPTION: If any medications were administered to the patient during this exam, they may be recorded here. If medications are associated with a procedure during system set-up, the system will enter them automatically when the procedure is registered. GENERAL DESCRIPTION: Radiology gives Imaging permission to read file #70 (^RADPT) on the fields specified within this request. Permission to read cross reference ^RADPT('AO' is also granted. VIEWER: SCHLEHUBER,CAMERON STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30361197 KEYWORDS: MAGDRCPB KEYWORDS: outside orders KEYWORDS: RA-MAG meds & radiopharms SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: VistA Imaging DICOM component request reading the Radiology patient file to meet the following requirements: The reading of the Radiology Patient file is required to look-up an accession number for acquiring the corresponding patient and possible Radiology report pointer. (Imaging pointers are stored in the Radiology Report file (#74).) The look up of the accession number is performed on either the "AE" or "ADC" cross-reference depending on what is sent (short or long accession number) from the entity (commercial PACS system, commercial gateway, or modality). After a valid entry is found, the matching process of the patient's name and social security is performed. If entries from the sending application match the Vista (main) hospital database, an image will be captured, the Image file is updated and the image pointer is stored in the corresponding Radiology report file. If entries from the sending application fail the matching process, then the entries are not processed but recorded in an Imaging file and will require user interaction to manually match the failed images with a corresponding Radiology exam order. All of these processes require reading the Radiology Patient file. Vista Imaging component VistARad request reading the Radiology patient file to meet the following requirements: VistARad software provides the Radiologist a paperless workstation functionality including Radiology exam worklists and on-line Radiology requisition and enables them to update the status and interpretation for the exam all on-line. DBA Comments: 7/25/13-MM: John and Greg requested ICR #1172 be opened for edits in April 2013 to add Nuclear Med Data (#500) and Med Administered (#.01 in RADPT(DA(3),'DT',DA(2),'P',DA(1),'RX' multiple) fields. The ICR Team found the ICR had been opened for edits on 1/19/10. Requested Imaging and Radiology review current ICR to verify current ICR meets Imaging's requirements. ICR was updated with new fields and reactivated on 7/25/13 for MAG*3.0*133. 7/25/13-MM: Added Editing History multiple entry for content change removing Peter Kuzmak as an editor. DATE ACTIVATED: JUL 25, 2013 DATE/TIME EDITED: NOV 30, 2009@09:59 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: BARRIOS,LUCILLE DATE/TIME EDITED: JAN 19, 2010@10:08 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CEBELINSKI,GREG DATE/TIME EDITED: JUL 25, 2013@14:33 ACTION: APPROVED AT THE REQUEST OF: CHRISTENSEN,JOHN WITH CONCURRENCE OF: CEBELINSKI,GREG DATE/TIME EDITED: JUL 25, 2013@14:51 ACTION: CONTENT CORRECTED NUMBER: 1174 IA #: 1174 FILE NUMBER: 71 GLOBAL ROOT: RAMIS(71 DATE CREATED: MAY 05, 1995 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1174 ID: RAMIS(71 GLOBAL REFERENCE: RAMIS(71,DA,'MDL' FIELD NUMBER: 731 FIELD NAME: MODALITY LOCATION: MDL,0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Points to the RAD MODALITY DEFINED TERMS file (73.1). GLOBAL REFERENCE: RAMIS(71,DA,0 FIELD NUMBER: .01 FIELD NAME: PROCEDURE NAME ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: NAME OF THE RAD/NUC MED PROCEDURE FIELD NUMBER: 9 FIELD NAME: CPT CODE LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Pointer to the CPT file (#81). GENERAL DESCRIPTION: Radiology gives permission to Imaging to read file #71 (^RAMIS). VIEWER: SCHLEHUBER,CAMERON STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30349761 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging needs access to read the Modality subfile (71.0731) to build a modality worklist. In addition, during the automatic image acquisition on the DICOM gateway, the direct read of the CPT name and procedure is needed to store the information in the Image file. EDITOR: BARRIOS,LUCILLE NUMBER: 1175 IA #: 1175 FILE NUMBER: 72 GLOBAL ROOT: RA(72, DATE CREATED: AUG 12, 2003 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1175 ID: RA(72, GLOBAL REFERENCE: RA(72, FIELD NUMBER: .01 FIELD NAME: EXAM STATUS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Exam status FIELD NUMBER: 3 FIELD NAME: ORDER LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The order of status progression for the exam entry. FIELD NUMBER: 7 FIELD NAME: TYPE OF IMAGING LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The Imaging type for the exam status entry. FIELD NUMBER: 9 FIELD NAME: VISTARAD CATEGORY LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: RA(72,'AVC',VISTARAD CATEGORY,DA GLOBAL DESCRIPTION: Direct global read access to the x-ref. GENERAL DESCRIPTION: Radiology gives permission to Imaging to read file #72 (^RA). STATUS: Active MAIL MESSAGE: 36873012 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging needs to read the status field on a specified accession number. EDITOR: BARRIOS,LUCILLE NUMBER: 1177 IA #: 1177 DATE CREATED: MAY 05, 1995 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RARTR NAME: DBIA1177 ID: RARTR GENERAL DESCRIPTION: Radiology gives permission to Imaging to call ^RARTR to display a radiology report. This will be called with RARPT set to the internal entry number for the report to be displayed. VIEWER: DAYHOFF,RUTH VIEWER: HEUER,CINDY STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15320710 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring NUMBER: 1178 IA #: 1178 DATE CREATED: MAY 05, 1995 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RARIC NAME: DBIA1178 ID: RARIC CREATOR: BARRIOS,LUCILLE GENERAL DESCRIPTION: Radiology gives permission to Imaging to call CREATE^RARIC to write data to the ^RARPT global. This will be called after RA variables are set as done by RAPTLU (for example, RADTE, RACN, RADFN, RADTI, RACNI, etc). A report created through this call by the Imaging Package is a skeletal report that is there solely for the purpose of providing a place to store the Imaging pointer in Field 2005. This is necessary because images are very often captured prior to the report transcription. VIEWER: DAYHOFF,RUTH VIEWER: HEUER,CINDY STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15320813 KEYWORDS: MAGDIR9A KEYWORDS: MAGGTRA COMPONENT/ENTRY POINT: CREATE VARIABLES: RADTE TYPE: Input VARIABLES DESCRIPTION: Date/Time of Radiology Exam (external format) VARIABLES: RADFN TYPE: Input VARIABLES DESCRIPTION: Patient's DFN VARIABLES: RADTI TYPE: Input VARIABLES DESCRIPTION: Radiology Case Date/Time (internal format, reverse chronological) VARIABLES: RACN TYPE: Input VARIABLES DESCRIPTION: Case Number, external format VARIABLES: RACNI TYPE: Input VARIABLES DESCRIPTION: Radiology Case Number, internal pointer to ^RADPT VARIABLES: RARPT TYPE: Both VARIABLES DESCRIPTION: Upon return of the call to CREATE^RARIC this is the internal number of the report record. If the report is not created this variable is null. SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring DATE ACTIVATED: AUG 05, 2009 DATE/TIME EDITED: AUG 04, 2009@11:14 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: BARRIOS,LUCILLE DATE/TIME EDITED: AUG 05, 2009@10:18 ACTION: APPROVED AT THE REQUEST OF: BARRIOS,LUCILLE WITH CONCURRENCE OF: CEBELINSKI,GREG NUMBER: 1179 IA #: 1179 DATE CREATED: MAY 05, 1995 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RARIC NAME: DBIA1179 ID: RARIC CREATOR: BARRIOS,LUCILLE GENERAL DESCRIPTION: Radiology gives permission to Imaging to call PTR^RARIC to write data to the ^RARPT global. This is called with RARPT set to the internal entry number of the radiology report file and MAGGP set to the internal entry number for the image/object in File 2005. MAGGP will be set into file 74 as the pointer to the image/object. VIEWER: DAYHOFF,RUTH VIEWER: HEUER,CINDY STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15320847 KEYWORDS: MAGDIR9A KEYWORDS: MAGGTRA COMPONENT/ENTRY POINT: PTR VARIABLES: RARPT TYPE: Input VARIABLES DESCRIPTION: Internal entry number of radiology report file to receive IMAGE pointer VARIABLES: MAGGP TYPE: Input VARIABLES DESCRIPTION: Internal entry number in File 2005 to be pointed to by report in File 74 VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: The internal entry of the image number in the Radiology sub file: ^RARPT(RARPT,2005, SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring DATE ACTIVATED: AUG 05, 2009 DATE/TIME EDITED: AUG 04, 2009@11:15 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: BARRIOS,LUCILLE DATE/TIME EDITED: AUG 05, 2009@10:18 ACTION: APPROVED AT THE REQUEST OF: BARRIOS,LUCILLE WITH CONCURRENCE OF: CEBELINSKI,GREG NUMBER: 1180 IA #: 1180 DATE CREATED: MAY 05, 1995 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RAUTL1 NAME: DBIA1180 ID: RAUTL1 GENERAL DESCRIPTION: Radiology gives Imaging permission to call UP1^RAUTL1 when updating the Interpreting Radiologist (Primary Interpreting Resident, or Primary Interpreting Staff) from the Imaging VistARad Workstation software. VIEWER: HEUER,CINDY VIEWER: CEBELINSKI,GREGORY VIEWER: KIRIN,GARRETT STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34019400 COMPONENT/ENTRY POINT: UP1 COMPONENT DESCRIPTION: Exam status updating and accompanying updates to status log, oe/rr VARIABLES: RADFN TYPE: Input VARIABLES DESCRIPTION: Patient's internal entry number (DFN) VARIABLES: RADTI TYPE: Input VARIABLES DESCRIPTION: Internal reverse exam date/time VARIABLES: RACNI TYPE: Input VARIABLES DESCRIPTION: Internal case number ien VARIABLES: RAONLINE TYPE: Input VARIABLES DESCRIPTION: Variable used for a silent call VARIABLES: ZTQUEUED TYPE: Input VARIABLES DESCRIPTION: Variable used for a silent call VARIABLES: RAMDV TYPE: Input VARIABLES DESCRIPTION: Individual division's parameters used during various stages of exam and report processing and inquiring. SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: When using an Imaging VistaRAD workstation the progression of the exam status changes. A new status of INTERPRETED is required to be added by the site to the EXAMINATION STATUS file. This allows the radiologist to move the exam status from EXAMINED to INTERPRETED and will record the Interpreting Radiologist (Primary Interpreting Resident, or Primary Interpreting Staff). Once the interpreter's name is recorded the VistaRad software will execute UP1^RAUTL1 to allow the case to move to the next assigned examination status defined in the EXAMINATION STATUS file for the Imaging location. The request is to allow Imaging VistaRad to execute UP1^RAUTL1. NUMBER: 1181 IA #: 1181 DATE CREATED: MAR 23, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DGPM MOVEMENT EVENT ID: DBIA1181 GENERAL DESCRIPTION: This is the event invoked by the registration, discharge, or transfer of a patient. Actions from any application area that are dependent on this event may be added to this event upon approval of the DBIC. The variable DGQUIET -MUST- be checked before doing writes to the screen. E.g., W:'$G(DGQUIET) !!,"Updating appointment status..." Please note: If a package has an installation which affects one of the protocols on DGPM MOVEMENT EVENTS, we strongly urge you to disable the following options during installation: Admit a Patient DG ADMIT PATIENT Transfer a Patient DG TRANSFER PATIENT Treating Specialty Transfer DG TREATING TRANSFER Check-in Lodger DGPM CHECK-IN Lodger Check-out DGPM CHECK-OUT Discharge a Patient DG DISCHARGE PATIENT Disposition and Application DG DISPOSITION APPLICATION Extended Bed Control DG BED CONTROL EXTENDED Load/Edit PTF Data DG PTF SCREEN Quick Load/Edit PTF Data DG PTF QUICK LOAD Enter/Edit an IRT DGJ IRT ENTER/EDIT STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34903941 KEYWORDS: DGPM SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham SUBSCRIBING DETAILS: The subscribing protocol is: PSD PAT ADT SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING DETAILS: The subscribing protocol is: SD APPT STATUS SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: The subscribing protocols are: ORU AUTOLIST ORU PATIENT MOVMT OCX ORDER CHECK PATIENT MOVE ORU REVIEW DELAYED ORDERS OR GUA EVENT PROCESSOR NOTASK SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING DETAILS: The subscribing protocol is: IB CATEGORY C BILLING SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas SUBSCRIBING DETAILS: The subscribing protocol is: YS PATIENT MOVEMENT SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING DETAILS: The subscribing protocol is: FHWMAS SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING ISC: Hines SUBSCRIBING DETAILS: The subscribing protocol is: GMRADGPM MARK CHART SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines SUBSCRIBING DETAILS: The subscribing protocol is: GMRVOR DGPM SUBSCRIBING PACKAGE: HINQ ISC: Albany SUBSCRIBING DETAILS: The subscribing protocol is: DVB ADMISSION HINQ SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING DETAILS: The subscribing protocol is: PSJ OR PAT ADT SUBSCRIBING PACKAGE: VISIT TRACKING ISC: Albany SUBSCRIBING DETAILS: The subscribing protocol is: VSIT PATIENT STATUS SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION SUBSCRIBING DETAILS: The subscribing protocol is: SCD MOVEMENT EVENTS SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING DETAILS: The subscribing protocol is: RG ADT INPATIENT ENCOUNTER DRIVER SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING SUBSCRIBING DETAILS: The subscribing protocol is: DGJ INCOMPLETE EVENTS SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING DETAILS: The subscribing protocol is: ROR EVENT PTF SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM SUBSCRIBING DETAILS: The subscribing protocol is: EAS UE INP EVENT SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING DETAILS: The subscribing protocol is: LR70 MOVEMENT EVENT SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: VPR protocol is VPR DG UPDATES. The VPR protocol listeners will store the patient's DFN in an ^XTMP array; another process within HMP watches this global for patients to update and will re-pull a snapshot of the patient's demographics. DBA Comments: 10/20/14-MM: Added VPR as a subscriber for VPR*1*3. The VPR protocol listeners will simply store the patient's DFN in an ^XTMP array; another process within HMP watches this global for patients to update and will re-pull a snapshot of the patient's demographics. Melanie was notified the ICR team does not currently have Registration knowledgeable resources to review the request and the VPR team is responsible for the technical correctness and use of the event point. They are also responsible for assuring the event point is used for its intended purpose and the protocol they add does not have a negative impact on any of the protocols executed after VPR. She provided the above justification for use of the event point and said she had worked with the event point with CPRS. DATE/TIME EDITED: OCT 20, 2014@14:24 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BEUCHLER,MELANIE WITH CONCURRENCE OF: ICR,TEAM NUMBER: 1183 IA #: 1183 DATE CREATED: MAR 28, 1995 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMPLHS NAME: Health Summary extract routine for Problem List ID: GMPLHS VIEWER: PRICE,DEBORAH VIEWER: RUSSELL,JOEL VIEWER: BUECHLER,MELANIE K STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 35707951 COMPONENT/ENTRY POINT: GETLIST(DFN,STATUS) VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient's internal file number VARIABLES: STATUS TYPE: Input VARIABLES DESCRIPTION: A == Active problems I == Inactive problems ALL == All problems VARIABLES: TMP('GMPLHS',$J, TYPE: Output VARIABLES DESCRIPTION: Problem List will output the following data from the Problem (# 9000011) file in the following global entries: ^TMP("GMPLHS",$J,STATUS,0)= # problems extracted ^ # problems that exist ^TMP("GMPLHS",$J,CNT,0)= Internal Diagnosis (.01) ^ Internal Date Last Modified (.03) ^ External Facility Name (.06) ^ Internal Date Entered (.08) ^ Internal Status (.12) ^ Date of Onset (.13) ^ Responsible Provider (1.05) ^ External Service Name (1.06) ^ Service Abbreviation ^ Internal Date Resolved (1.07) ^ External Clinic Name (1.08) ^ Date Recorded (1.09) ^ ^ External Lexicon Problem Text (1.01) ^ Exposure String (AO/IR/EC/HNC/MST) ^TMP("GMPLHS",$J,CNT,"N")= External Provider Narrative (.06) ^TMP("GMPLHS",$J,CNT,"L")= Internal Lexicon Problem Text (1.01) ^ External Lexicon Problem Text (1.01) ^TMP("GMPLHS",$J,CNT,"C",Note Facility,Note Number,0)= Note Narrative (9000011.1111,.03) ^ Internal Date Note Added (9000011.1111,.05) ^ External Author Name (9000011.1111,.06) Problems will be ordered by CNT in the same order that Problem List displays them based on Problem List parameters. Only Active comments will be included. SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 1184 IA #: 1184 DATE CREATED: MAR 29, 1995 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSLTR NAME: GMTSLTR ID: GMTSLTR GENERAL DESCRIPTION: Progress Notes uses the Health Summary package to print large letters between locations when batch prting PNs. I $L($T(^GMTSLTR)) S GMTSLTR=$P(^SC(GMRPCO,0),U,2) D ^GMTSLTR STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 12282832 COMPONENT/ENTRY POINT: GMTSLTR SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 1185 IA #: 1185 FILE NUMBER: 19 GLOBAL ROOT: DIC(19 DATE CREATED: MAR 30, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED ROUTINE: DGYMODS NAME: DELETE OPTION QUEUING INFORMATION ID: DGYMODS GENERAL DESCRIPTION: We have been tasked with turning off the ODS software. As part of that, we would like to unschedule the nightly background job. The following code will be used in a one time clean-up routine: S DGVER=$$VERSION^XPDUTL("XU") S DIC="^DIC(19,",DIC(0)="QMZ",X="A1B2 BACKGROUND JOB" D ^DIC S (DGIEN,DA)=+Y I DA'>0 G ENQ ; background job not in option file I DGVER<8 S DR="200///@;201///@;202///@;203///@",DIE=DIC D ^DIE I DGVER'<8 S DIK="^DIC(19.2," F DA=0:0 S DA=$O(^DIC(19.2,"B",DGIEN,DA)) Q:'DA D ^DIK STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 1995 MAIL MESSAGE: 14532792 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 1186 IA #: 1186 FILE NUMBER: 19.2 GLOBAL ROOT: DIC(19.2 DATE CREATED: MAR 30, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OPTION SCHEDULING FILE ACCESS ID: DIC(19.2 GENERAL DESCRIPTION: If a site is running KERNEL 8 or higher, we'd like to delete all entries in the SCHEDULED OPTIONS file for the ODS BACKGROUND JOB. Code is as follows: S DGVER=$$VERSION^XPDUTL("XU") S DIC="^DIC(19,",DIC(0)="QMZ",X="A1B2 BACKGROUND JOB" D ^DIC S (DGIEN,DA)=+Y I DA'>0 G ENQ ; background job not in option file I DGVER<8 S DR="200///@;201///@;202///@;203///@",DIE=DIC D ^DIE I DGVER'<8 S DIK="^DIC(19.2," F DA=0:0 S DA=$O(^DIC(19.2,"B",DGIEN,DA)) Q:'DA D ^DIK STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 1995 MAIL MESSAGE: 14532792 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 1187 IA #: 1187 FILE NUMBER: 408.34 GLOBAL ROOT: DG(408.34, DATE CREATED: MAR 30, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1187 ID: DG(408.34, GLOBAL REFERENCE: DG(408.34,D0,0 FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Check is done to see if source of Means Test is IVM or VAMC. GENERAL DESCRIPTION: The IVM package files new Means Tests in the PIMS Means Test module. IVM requests permission to read from the SOURCE OF INCOME TEST file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14558250 SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 1188 IA #: 1188 FILE NUMBER: 408.41 GLOBAL ROOT: DGMT(408.41, DATE CREATED: MAR 30, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1188 ID: DGMT(408.41, GLOBAL REFERENCE: DGMT(408.41,'D', FIELD NUMBER: .03 FIELD NAME: MEANS TEST LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This cross-reference is used to find all records in this file associated with a specific Means Test. GLOBAL DESCRIPTION: When all records for the specific Means Test are found, then a check of the income person field can be done. GLOBAL REFERENCE: DGMT(408.41,D0,0, FIELD NUMBER: .1 FIELD NAME: INCOME PERSON LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field will hold the pointer value of the dependent when a name, DOB, SSN or sex change is audited. GLOBAL DESCRIPTION: When an IVM Means Test is deleted, any demographic entries in this file must be restored to 408.12 & 408.13. GENERAL DESCRIPTION: The IVM package files new Means Tests in the PIMS Means Test module. IVM requests permission to read from the Means Test CHANGES file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14558250 SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 1189 IA #: 1189 DATE CREATED: APR 03, 1995 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1189-A ORIGINAL NUMBER: 1189 GENERAL DESCRIPTION: The purpose of this agreement is to provide access to the Medicine package (custodian) by the Imaging package (subscriber) for the purpose of creating a new Medicine package entry (stub:Pt ID, Date/time) as a holder of an Imaging pointer or set of Imaging pointers. The Imaging pointers are set in the field 2005, as descendants of the 0 subscript of node 2005 in each of the following files: Echo(691), Cardiac Cath(691.1), EKG(691.5), Hematology(694), Endoscopy(699), Generalized Procedure(699.5), and Rheumatology(701). In addition, the MEDICAL PATIENT field (location 0;2) is also permitted for Direct Global Read. The Imaging routines which perform this function are as follows: MAGMCPT* and MAGUFILR STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 9587311 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring EDITOR: FRANK,STUART NUMBER: 1190 IA #: 1190 DATE CREATED: APR 03, 1995 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1189-B ORIGINAL NUMBER: 1189 GENERAL DESCRIPTION: The purpose of this agreement is to provide access to the Medicine package (custodian) by the Imaging package (subscriber) for the purpose of editing (including deletion of) Medicine package Image entries. The Imaging pointers are set in the field 2005, as descendants of the 0 subscript of node 2005 on each of the following files: Echo(691), Cardiac Cath(691.1), EKG(691.5), Hematology(694), Endoscopy(699), Generalized Procedure(699.5), and Rheumatology(701). The Imaging routines which perform this function are as follows: MAGMCPT*, MAGUDEL* and MAGUFILR. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 9587311 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring EDITOR: FRANK,STUART EDITOR: ATKINSON,DEVEN NUMBER: 1193 IA #: 1193 DATE CREATED: APR 06, 1995 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MCMAGDSP NAME: DBIA1193 ID: MCMAGDSP GENERAL DESCRIPTION: This privately supported entry point allows the display the full Medicine report associated with the Imaging Workstation Display. The routine MCMAGDSP has an entry point of REPRT which, when passed the IEN and the Medicine package file number, will display the full report to the Workstation (only). This routine (MCMAGDSP) will be bundled in a patch to Medicine 2.2. It contains display functionality for the following types of Medicine procedures: Electrocardiograms (ECG), Echocardiography (ECHO), Cardiac Catheterization, Hematology (Bone Marrow biopsies and aspirates), Pulmonary Endoscopies, Gastrointestinal Endoscopies, Medicine Consults, Generic Procedures, and Rheumatology. This is the current extent of Medicine procedures that have Imaging pointer fields. This reporting functionality uses the Procedure/Subspecialty file in tandem with the result files to determine the type of procedure. This is necessary as many of the results files share a common structure to house data of different procedure types (as in different CPTs). The MCMAGDSP routine uses the same compiled print templates that Medicine uses and there are also calls to utilities of the common Medicine print driver. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 9587311 COMPONENT/ENTRY POINT: REPRT VARIABLES: MC_IEN TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number of the Medicine procedure being displayed. This variable is passed by value in the first position of the parameter list. VARIABLES: MC_FILE TYPE: Input VARIABLES DESCRIPTION: This variable is the Medicine package Fileman file number which contains the procedure data to be displayed. This variable is passed by value in the second position of the parameter list. SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring EDITOR: ATKINSON,DEVEN NUMBER: 1196 IA #: 1196 DATE CREATED: APR 13, 1995 CUSTODIAL PACKAGE: IMAGING CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MAGSRIC NAME: IMAGING/SURGERY MAGSRIC ID: MAGSRIC GENERAL DESCRIPTION: The Surgery Package is given permission to call IM^MAGSRIC to provide image capture capability to users of the operations options STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14709079 COMPONENT/ENTRY POINT: IM COMPONENT DESCRIPTION: This entry point interacts with user allowing selection of capture mode, capture of image and descriptive text, and storage of image and text data. VARIABLES: SRTN TYPE: Input VARIABLES DESCRIPTION: Internal id number for this patient's procedure SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 1197 IA #: 1197 DATE CREATED: APR 17, 1995 CUSTODIAL PACKAGE: GENERIC CODE SHEET CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCSUTCP NAME: IFCAP FUND CONTROL POINT INFORMATION ID: PRCSUTCP GENERAL DESCRIPTION: This integration agreement allows Generic Code Sheets (version 2.0) to call IFCAP routines from within distributed input templates. The calls will return fund control points and information pertaining to the fund control point which is used to build the FMS code sheets. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13708495 COMPONENT/ENTRY POINT: $$CP COMPONENT DESCRIPTION: This extrinsic function will return the internal entry number of a selected control point. VARIABLES: STATION TYPE: Input VARIABLES DESCRIPTION: The 3 digit station number passed as parameter 1. VARIABLES: PROMPT TYPE: Input VARIABLES DESCRIPTION: The prompt which should be displayed to the user passed as parameter 2. VARIABLES: LEVEL TYPE: Input VARIABLES DESCRIPTION: The level of access. Pass 0 for none; 1 for official; 2 for clerk; or 3 for requestor as the 3rd parameter. VARIABLES: SCREEN TYPE: Input VARIABLES DESCRIPTION: Any additional VA FileMan screen should be passed as the 4th parameter. VARIABLES: DEFAULT TYPE: Input VARIABLES DESCRIPTION: Default is the optional VA FileMan default response displayed to the user. Default is the name of the control point displayed (not the internal entry number). It should be passed as the 5th paramater. SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring NUMBER: 1198 IA #: 1198 DATE CREATED: APR 17, 1995 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCSUT NAME: IFCAP FUND CONTROL POINT INFORMATION ID: PRCSUT GENERAL DESCRIPTION: This integration agreement allows Generic Code Sheets (version 2.0) to call IFCAP routines from within distributed input templates. The calls will return fund control points and information pertaining to the fund control point which is used to build the FMS code sheets. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13708495 COMPONENT/ENTRY POINT: FY COMPONENT DESCRIPTION: This entry point allows the selection of the fiscal year. VARIABLES: PRC(FY) TYPE: Output VARIABLES DESCRIPTION: The variable PRC("FY") is returned as the selected fiscal year. COMPONENT/ENTRY POINT: $$BBFY COMPONENT DESCRIPTION: This extrinsic function returns the beginning budget fiscal year for a control point. VARIABLES: A TYPE: Input VARIABLES DESCRIPTION: The 3 digit station number passed as parameter 1. VARIABLES: B TYPE: Input VARIABLES DESCRIPTION: The fiscal year passed as parameter 2. VARIABLES: C TYPE: Input VARIABLES DESCRIPTION: The control point passed as parameter number 3. VARIABLES: PRCA TYPE: Input VARIABLES DESCRIPTION: Pass 1 for no user interaction as parameter 4. SUBSCRIBING PACKAGE: GENERIC CODE SHEET ISC: Washington/Silver Spring NUMBER: 1199 IA #: 1199 DATE CREATED: APR 17, 1995 CUSTODIAL PACKAGE: GENERIC CODE SHEET CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRC0C NAME: IFCAP FUND CONTROL POINT INFORMATION ID: PRC0C GENERAL DESCRIPTION: This integration agreement allows Generic Code Sheets (version 2.0) to call IFCAP routines from within distributed input templates. The calls will return fund control points and information pertaining to the fund control point which is used to build the FMS code sheets. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 13708495 COMPONENT/ENTRY POINT: $$ACC COMPONENT DESCRIPTION: This extrinsic function returns a fund control points fund table in the form: a/o code ^ program ^ fcp/prj code ^ object class ^ fund code ^ bfy beginning ^ bfy ending ^ fund trans allowed ^ file 420.14 record id ^ job ^ fill in years appropriation ^ gross/net VARIABLES: A TYPE: Input VARIABLES DESCRIPTION: The 3 digit station number passed as parameter 1. VARIABLES: B TYPE: Input VARIABLES DESCRIPTION: Pass 'fund control point ^ year ^ beginning fiscal year' as parameter 2. COMPONENT/ENTRY POINT: $$SEC1 COMPONENT DESCRIPTION: This extrinsic function returns the FMS sec1 code. VARIABLES: A TYPE: Input VARIABLES DESCRIPTION: The 3 digit station number passed as parameter 1. SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring NUMBER: 1201 IA #: 1201 DATE CREATED: APR 20, 1995 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMGAPI4 NAME: KERNEL transport MM routine ID: XMGAPI4 GENERAL DESCRIPTION: Kernel needs to transport MailMan routine XMGAPI4 to sites untill MailMan 7.2 is installed. KIDS will check and only install the routine if it doesn't already exist. STATUS: Active DURATION: Next Version MAIL MESSAGE: 15001530 GOOD ONLY FOR VERSION: 8 COMPONENT/ENTRY POINT: NU COMPONENT DESCRIPTION: Return if the user has new mail in an array. Useage: N XUXM S %=$$NU^XMGAPI4(1,1,"XUXM") SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 1202 IA #: 1202 DATE CREATED: APR 21, 1995 CUSTODIAL PACKAGE: IMAGING CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MAGSRIC NAME: MAGING/SURGERY CLEANUP ID: MAGSRIC GENERAL DESCRIPTION: 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. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14709116 COMPONENT/ENTRY POINT: CLEAN COMPONENT DESCRIPTION: Entry point kills MAG namespaced local variables used during image capture. SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 1203 IA #: 1203 DATE CREATED: APR 21, 1995 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SROPRPT NAME: SURGERY/IMAGING REPORT DISPLAY ID: SROPRPT GENERAL DESCRIPTION: The Imaging Package is given permission to call SROPRPT to display surgery operation reports. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: SROPRPT VARIABLES: SRTN TYPE: Input VARIABLES DESCRIPTION: The variable SRTN (which identifies the surgical case) may be defined before making the call. If the variable SRTN is not defined when the call is made, the user will be prompted to select a patient and operation. SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE NUMBER: 1204 IA #: 1204 FILE NUMBER: 130 GLOBAL ROOT: SRF( DATE CREATED: APR 21, 1995 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: SURGERY/IMAGING FIELD 2005 ID: SRF( GLOBAL REFERENCE: SRF(D0,2005, FIELD NUMBER: .01 FIELD NAME: IMAGE LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman GLOBAL DESCRIPTION: Surgery Operation Report file. GLOBAL REFERENCE: SRF( FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Surgery Package will reserve field 2005 of File 130 for an IMAGE multiple pointing to File 2005. (The Surgery Package will be adding this field to its package as soon as feasible.) Imaging Package is given permission to set and delete pointers from Field 2005 of File 130. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14709209 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring NUMBER: 1205 IA #: 1205 DATE CREATED: APR 21, 1995 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORBUTL NAME: KERNEL 8 transport of ORBUTL ID: ORBUTL GENERAL DESCRIPTION: Kernel 8.0 needs to transport the routine ORBUTL. This routine was modified in order to work with Kernel 8.0. The changes are not compatible with Kernel 7.1. This is a one time release. STATUS: Active DURATION: Next Version GOOD ONLY FOR VERSION: 8.0 SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 1206 IA #: 1206 GLOBAL ROOT: DD( DATE CREATED: APR 28, 1995 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1206 ID: DD( GENERAL DESCRIPTION: During the installation of IFCAP v. 5.0 (namespace PRC) and IFCAP's Generic Inventory Package v. 5.0 (namespace PRCP), direct MUMPS kills of erroneous ^DD nodes need to be done in the Pre-Init After User Commit and the Post-Init routines. The specific nodes are listed below: 1. IFCAP (namespace PRC): a. Field descriptions (node 21) for files and sub-files in the range from 410 to 443.99. The kills are done in the DESCRIP^PRC5INS1 module, which is called from PRC5A, the Pre-Init After User Commit routine. The clean up is necessary as the new description may have fewer lines than the previous description, and, with double question mark help, the left-over lines may appear. b. Erroneous Computed Field nodes for fields currently defined as Free-Text: ^DD(420.01,2,9.01), ^DD(420.01,2,9.1), ^DD(420.01,2,9.2) ^DD(420.01,3,9.01), ^DD(420.01,3,9.1), ^DD(420.01,3,9.2) The kills are done in routine PRC5A, the Pre-Init After User Commit routine. c. Erroneous "IX" node: ^DD(442.8,0,"IX","AE",442.8,.01) The kill is done in routine PRC5A. d. Erroneous "NM" node: ^DD(420.11,0,"NM","SUBACCOUNT") The kill is done in routine PRC5A. 2. Generic Inventory Package of IFCAP (namespace PRCP): a. Field descriptions (node 21) from files and sub-files in the range from 445 to 447. The kills are done in the DESCRIP^PRC5INS1 module, which is called from PRCP5PRE, the Pre-Init After User Commit routine. b. Erroneous "ID" node: ^DD(445.121,0,"ID","WRITE") The kill is done in routine PRCP5POS, the Post-Init routine. c. Erroneous "NM" node: ^DD(445.121,0,"NM","MEMBER OF SET/PACK") The kill is done in routine PRCP5POS. STATUS: Active DURATION: Next Version MAIL MESSAGE: 15015184 GOOD ONLY FOR VERSION: 5.0 SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring NUMBER: 1207 IA #: 1207 DATE CREATED: MAY 04, 1995 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Washington USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MCARDSS NAME: DBIA1207 ID: MCARDSS GENERAL DESCRIPTION: 1) Decision Support System (DSS) interface Functional description: This process provides a reporting mechanism to the DSS package. The subscriber passes a Starting date and ending date to the MCARDSS routine and the TMP global will store the result records in an arbitrary order. The results include the following required fields: Date and Time the record is released, Provider signing or signed for, CPT code, Patient identification Software components: Routines -- ^MCARDSS, ^MCBLD, ^MCPTF File(s) -- Procedure Term File: ^MCAR(694.8 Menu Options: None Technical overview: The DSS application makes a parameterized call to ^MCARDSS(Start_date,End_date) with dates in regular Fileman date/time format. Only results which have a valid signature, CPT code, date signed, and valid patient ID will be returned in the ^TMP($J,count) scratch global. The result is stored as follows: Provider ID(DUZ)^Patient ID(DFN)^Date/time signed(FM DATE/TIME)^CPT code for example -- ^TMP(1231231,3)=194^2323^295101010.1232^93005 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15295151 COMPONENT/ENTRY POINT: START COMPONENT DESCRIPTION: The DSS application makes a parameterized call to ^MCARDSS(Start_date,End_date) with dates in regular Fileman date/time format. SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1208 IA #: 1208 DATE CREATED: MAY 05, 1995 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RAPSET1 NAME: DBIA1208 ID: RAPSET1 GENERAL DESCRIPTION: Radiology gives permission to Imaging to call SET^RAPSET1. The purpose of this call is to set up some variables needed to do exam look-ups, etc. VIEWER: DAYHOFF,RUTH VIEWER: HEUER,CINDY STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15320878 COMPONENT/ENTRY POINT: SET SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring NUMBER: 1209 IA #: 1209 DATE CREATED: MAY 05, 1995 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RACNLU NAME: DBIA1209 ID: RACNLU GENERAL DESCRIPTION: Radiology gives permission to Imaging to call ^RACNLU look up a patient by radiology case number. SET^RAPSET1 must be called first to set variables. This is an interactive routine, so other input is provided by the user. STATUS: Active MAIL MESSAGE: 15320885 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring NUMBER: 1210 IA #: 1210 DATE CREATED: APR 10, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTP NAME: PRINT 1010F WITH ENCOUNTER FORMS ID: DGMTP GENERAL DESCRIPTION: Allow AICS to print 1010F's for patients who require a means test or thier means test will expire within a specified number of days. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23679661 COMPONENT/ENTRY POINT: START COMPONENT DESCRIPTION: Allows printing of a 1010F VARIABLES: DGMTI TYPE: Used VARIABLES DESCRIPTION: the internal entry number of the means test/copay test, returned from $$LST^DGMTU. VARIABLES: DGMTYPT TYPE: Used VARIABLES DESCRIPTION: The type of test, 1 for Means Test, 2 for Copay test. VARIABLES: DGMTDT TYPE: Used VARIABLES DESCRIPTION: Date of Means Test, returned from $$LST^DGMTU VARIABLES: DGOPT TYPE: Used VARIABLES DESCRIPTION: Pretends called from registration so device not closed when print of 1010 is finished. SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring NUMBER: 1220 IA #: 1220 FILE NUMBER: 50.6 GLOBAL ROOT: PSNDF( DATE CREATED: MAY 09, 1995 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1220-A ORIGINAL NUMBER: 1220 ID: PSNDF( GLOBAL REFERENCE: PSNDF(D0,5,1,2) FIELD NUMBER: 5 FIELD NAME: VA PRINT NAME LOCATION: 2;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6 FIELD NAME: VA PRODUCT IDENTIFIER LOCATION: 2;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7 FIELD NAME: TRANSMIT TO CMOP LOCATION: 2;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 8 FIELD NAME: VA DISPENSE UNIT LOCATION: 2;4 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Consolidated Mail Outpatient Pharmacy package will extract informational data on a daily basis. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15997281 SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 1223 IA #: 1223 FILE NUMBER: 54 GLOBAL ROOT: DIC(54, DATE CREATED: MAY 09, 1995 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1220-D ORIGINAL NUMBER: 1220 ID: DIC(54, GLOBAL REFERENCE: DD(54,.01,0) GENERAL DESCRIPTION: The Consolidated Mail Outpatient Pharmacy package modified the input transform for the .01 to prevent the editing of the first 21 entries after the CMOP installation. This will provide consistency in the drug warnings transmitted with drugs to be dispensed by the CMOP. STATUS: Active MAIL MESSAGE: 31276691 SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 1230 IA #: 1230 DATE CREATED: MAY 17, 1995 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMA0 NAME: PRINT A MESSAGE API ID: XMA0 GENERAL DESCRIPTION: The entry points in this API print messages: - PR2^XMA0 print a message with a header - HDR^XMA0 print a message without a header - ENTPRT^XMA0 interactive print a message STATUS: Active MAIL MESSAGE: 29724674 COMPONENT/ENTRY POINT: ENTPRT COMPONENT DESCRIPTION: This interactive API lets the user print a message with a header. The message to print is pre-defined, but the user may choose the device to which to print, and which responses to print. VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: The IEN of the user in the NEW PERSON file. VARIABLES: XMDUZ TYPE: Used VARIABLES DESCRIPTION: (optional) The DUZ of the user. Default is DUZ. VARIABLES: XMK TYPE: Input VARIABLES DESCRIPTION: The IEN of the basket in the user's mailbox in which the message to be printed is located. VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the Message file of the message to be printed. COMPONENT/ENTRY POINT: HDR COMPONENT DESCRIPTION: Headerless print a message. Compare to PRTMSG^XMXAPI (DBIA 2729). Usage: IO has been defined with a KERNEL device call. S XMK=basket IEN S XMZ=message IEN D HDR^XMA0 ; prints the message in its entirety - or - S $P(XMTYPE,";",6)=3 D HDR^XMA0 ; prints the message from response 3 to the end. VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: The IEN of the user in the NEW PERSON file. VARIABLES: XMDUZ TYPE: Used VARIABLES DESCRIPTION: (optional) The DUZ of the user. Default is DUZ. VARIABLES: XMK TYPE: Input VARIABLES DESCRIPTION: The IEN of the basket in the user's mailbox in which the message to be printed is located. VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the Message file of the message to be printed. VARIABLES: IO TYPE: Input VARIABLES DESCRIPTION: The device to which the message is to be printed. VARIABLES: XMTYPE TYPE: Used VARIABLES DESCRIPTION: (optional) Lets you determine from which response to start printing. If XMTYPE="^", then abort. If ";"-piece 6 is null or zero, or if '$D(XMTYPE), the message is printed in its entirety. If ";"-piece 6 is a number, the message will be printed from that response to the end. The other ";"-pieces are ignored. COMPONENT/ENTRY POINT: PR2 COMPONENT DESCRIPTION: Print a message with a header. Compare to PRTMSG^XMXAPI (DBIA 2729). Usage: IO has been defined with a KERNEL device call. S XMK=basket IEN S XMZ=message IEN D PR2^XMA0 ; prints the message in its entirety - or - S $P(XMTYPE,";",6)=3 D PR2^XMA0 ; prints the message from response 3 to the end. VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: The IEN of the user in the NEW PERSON file. VARIABLES: XMDUZ TYPE: Used VARIABLES DESCRIPTION: (optional) The DUZ of the user. Default is DUZ. VARIABLES: XMK TYPE: Input VARIABLES DESCRIPTION: The IEN of the basket in the user's mailbox in which the message to be printed is located. VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the Message file of the message to be printed. VARIABLES: IO TYPE: Input VARIABLES DESCRIPTION: The device to which the message is to be printed. VARIABLES: XMTYPE TYPE: Used VARIABLES DESCRIPTION: (optional) Lets you determine from which response to start printing. If XMTYPE="^", then abort. If ";"-piece 6 is null or zero, or if '$D(XMTYPE), the message is printed in its entirety. If ";"-piece 6 is a number, the message will be printed from that response to the end. The other ";"-pieces are ignored. EDITOR: BEUSCHEL,GARY NUMBER: 1231 IA #: 1231 FILE NUMBER: 52.6 GLOBAL ROOT: PS(52.6 DATE CREATED: OCT 14, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1231 ID: PS(52.6 GENERAL DESCRIPTION: This file was previously in Inpatient Meds versions up to 5.0. Now it has moved to Pharmacy Data Management 1.0. It is used extensively throughout our routines. With this move, we are requesting read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25249372 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: NATIONAL DRUG FILE ISC: Birmingham NUMBER: 1232 IA #: 1232 DATE CREATED: JUN 23, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMAH1 NAME: INTERACTIVE REPLY TO A MESSAGE API ID: XMAH1 GENERAL DESCRIPTION: This API lets the user interactively reply to a message in his mailbox. There are two ways to invoke it: D ^XMAH1 or D ENTA^XMAH1. STATUS: Active COMPONENT/ENTRY POINT: ENTA COMPONENT DESCRIPTION: Interactive reply to a message in your mailbox. Inclusion of previous responses is not possible. All rules of replying to a message apply: If the user is a surrogate, read or send permission is required. If the message is in the WASTE basket, it will be moved to another basket. If the message is 'information only', you can't reply. Usage: S XMDUZ=user's DUZ, XMK=basket IEN, XMZ=message IEN D ENTA^XMAH1 or D ^XMAH1 VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: DUZ of the user who is replying to the message. VARIABLES: XMK TYPE: Input VARIABLES DESCRIPTION: IEN of the basket in the user's mailbox where the message is located. VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the Message file of the message to which the user is replying. VARIABLES: XMDF TYPE: Used VARIABLES DESCRIPTION: (optional) If $D(XMDF), then normal restrictions on message addressing are ignored: - Ignore 'domain closed' - Ignore 'keys required for domain' - Ignore 'message length restrictions to remote addressees' NUMBER: 1233 IA #: 1233 DATE CREATED: MAY 24, 1995 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMA11A NAME: INTERACTIVE ANSWER OR SEND A MESSAGE API ID: XMA11A GENERAL DESCRIPTION: This API lets the user answer a message or send a message. When you send an answer to a message, the original message is copied into the answer, the user edits the answer, the user's network signature is appended to the end of the answer, and the whole thing is automatically addressed to the sender of the original message. STATUS: Active MAIL MESSAGE: 15740938 COMPONENT/ENTRY POINT: WRITE COMPONENT DESCRIPTION: Interactive answer a message or send a message. Usage: To answer a message: S XMDUZ=User's DUZ S X="A" S XMZ=IEN of message being answered D WRITE^XMA11A To send a message: S XMDUZ=User's DUZ D WRITE^XMA11A VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: DUZ of the user who is answering or sending a message. VARIABLES: X TYPE: Used VARIABLES DESCRIPTION: If $E(X)="A", then the user will answer a message. Otherwise, the user will send a message. VARIABLES: XMZ TYPE: Used VARIABLES DESCRIPTION: Message IEN in the Message file of the message being answered. Required if the user is answering a message. Not required (and ignored) if the user is sending a message. NUMBER: 1234 IA #: 1234 FILE NUMBER: 3.1 GLOBAL ROOT: DIC(3.1 DATE CREATED: MAY 25, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1234 ID: DIC(3.1 GLOBAL REFERENCE: DIC(3.1 FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Name field. GLOBAL DESCRIPTION: Title File. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15661980 SUBSCRIBING PACKAGE: REMOTE ORDER/ENTRY SYSTEM ISC: Salt Lake City SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING SUBSCRIBING DETAILS: ADDED 10/14/2008 SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT SUBSCRIBING PACKAGE: MENTAL HEALTH DATE/TIME EDITED: OCT 14, 2008@09:03 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: GERARD,MARTHA WITH CONCURRENCE OF: IVEY,JOEL DATE/TIME EDITED: SEP 28, 2008@13:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: FORT,WALLY DATE/TIME EDITED: JAN 19, 2011@12:18 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: TRAXLER,FRANK WITH CONCURRENCE OF: BEUSCHLE,GARY NUMBER: 1235 IA #: 1235 FILE NUMBER: 662 GLOBAL ROOT: RMPR(662, DATE CREATED: MAY 26, 1995 CUSTODIAL PACKAGE: PROSTHETICS CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1235 ID: RMPR(662, GLOBAL REFERENCE: RMPR(662,i,0) FIELD NUMBER: .01 FIELD NAME: ARABIC DISABILITY NAME ACCESS: Read w/Fileman FIELD DESCRIPTION: The .01 field contains the name of the prosthetic disability selected. GLOBAL DESCRIPTION: PROS DISABILITY CODE GENERAL DESCRIPTION: ROES V2.0 references the Pros Disability Code File to print and display a patient's rated disabilities. Access is read only for the ARABIC DISABILITY NAME (.01) field and the "B" cross-reference of the .01 field. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15662016 SUBSCRIBING PACKAGE: REMOTE ORDER/ENTRY SYSTEM ISC: Salt Lake City NUMBER: 1236 IA #: 1236 DATE CREATED: JUN 16, 1995 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MCORMN NAME: DBIA1236 ID: MCORMN GENERAL DESCRIPTION: To support Medicine 2.2 with 4 new components the $$HL7^MCORMN(MESSNUM) entry point needs to be called. This interface will allow Health Summary to get patient data for a breif summary, a brief summary for only abnormal values, a full summary and a full captioned summary. It will also support the existing one line medicine summary. This interface is setup in an HL7 compliant manner. HS will need to have the Pateint DFN, Beginning Date, Ending Date, # of occurrences, and Type of Date (Full or Brief) set into a message via the ^XMD call. The $$HL7^MCORMN(MESSNUM) call will retrieve the available data based on the above specifications and using the message number returned from the ^XMD call. Data that will be returned via the message is DATE/TIME, PROCEDURE, SUMMARY, PROCEDURE SUMMARY, and the PROCEDURE REPORT. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 16052759 COMPONENT/ENTRY POINT: $$HL7(MESSNUM) COMPONENT DESCRIPTION: This is an extrinsic function that returns the message number holding the returned information. VARIABLES: MESSNUMB TYPE: Input VARIABLES DESCRIPTION: Done with parameter passing. VARIABLES: SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 1237 IA #: 1237 GLOBAL ROOT: DD( DATE CREATED: MAY 31, 1995 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1237 ID: DD( GENERAL DESCRIPTION: The pre-init routines for ROES V2.0 change several file names, clean up leftover DD nodes, and an obsolete cross-reference. These changes were suggested by the verifier to maintain consistency throughout the system. |NOWRAP| 1. The screen on the 'BATTERY TYPE FURNISHED' field is deleted with a Kill command. GLOBAL REFERENCE: ^DD(791810.0101,.02,12) ^DD(791810.0101,.02,12.1) 2. The old name of field 791810.0101 is cleaned up in ORDER^RMPFPOST. FileMan creates a duplicate NM node when a subfile name changes. GLOBAL REFERENCE: ^DD(791810.0101,0,"NM","TRANSACTION") 3. The 'AD' cross-reference on the .01 field of file number 791810 is killed with a direct kill in EXIT^RMPFPRE routines. The following is a capture of the code: EXIT F X=0:0 S X=$O(^DD(791810,.01,1,X)) Q:'X D .K:$G(^DD(791810,.01,1,X,0))="791810^AD^MUMPS" ^DD(791810,.01,1,X) K ^DD(791810,0,"IX","AD",791810,.01) GLOBAL REFERENCE: ^DD(791810,.01,X,0) ^DD(791810,0,"IX","AD",791810,.01) 4. The file names of files 791810, 791810.1, 791810.2, 791812 are changed using DIE like the following: S DIE=1,DA=701810,DR=".01////STATION ORDER" D ^DIE STATUS: Active DURATION: Next Version MAIL MESSAGE: 15767529 GOOD ONLY FOR VERSION: 2.0 SUBSCRIBING PACKAGE: REMOTE ORDER/ENTRY SYSTEM ISC: Salt Lake City NUMBER: 1238 IA #: 1238 DATE CREATED: MAY 25, 1995 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRHS01 NAME: DBIA1238 ID: PXRHS01 GENERAL DESCRIPTION: The Health Summary Package desires to set up an integration agreement with the PCE Package to call the entry point VISIT^PXRHS01 to retrieve Visit, ICD-9, CPT, and Provider data. Input data will be done via parameter passing and output data will be placed in the ^TMP global in the specified format that is described in this agreement. Entry point: VISIT(DFN,ENDDT,BEGDT,OCCLIM,CATCODE,EXTRCODE,TIMEORD) INPUT : DFN - Pointer to PATIENT file (#2) ENDDT - Ending date/time in internal FileMan format - Defaults to today's date at 11:59 pm BEGDT - Beginning date/time in internal FileMan format - Defaults to one year prior to today's date OCCLIM - Maximum number of visits returned CATCODE - Pattern Match which controls visit data that is returned (Can include multiple codes) A = AMBULATORY H = HOSPITALIZATION I = IN HOSPITAL C = CHART REVIEW T = TELECOMMUNICATIONS N = NOT FOUND S = DAY SURGERY O = OBSERVATION E = EVENT (HISTORICAL) R = NURSING HOME D = DAILY HOSPITALIZATION DATA X = ANCILLARY PACKAGE DAILY DATA EXTRCODE - Pattern Match indicating which optional data is returned (Can be multiple) P = return PROVIDER data C = return CPT (procedure) data D = return ICD-9 (diagnosis) data TIMEORD - Order visits on same day are indexed Default is inverse cronological order 1 = Time order in regular cronological order OUTPUT : Data from VISIT (9000010) file except for hosp. loc. abbr. ^TMP("PXHSV",$J,InvExDt,COUNT,0) = VISIT/ADMIT DATE&TIME [I;.01] ^ TYPE [E;.03] ^ LOC. OF ENCOUNTER [E;.06] ^ SERVICE CATEGORY [E;.07] ^ CHECK OUT DATE&TIME [I;.18] ^ HOSPITAL LOCATION [E;.22] ^ HOSP. LOC. ABBREVIATION [E;44;1] ^ OUTSIDE LOCATION [E;2101] ^ CLINIC [E;.08] ^ WALK IN/APPT [E;.16] ^ LEVEL OF SERVICE [E;.17] ^ ELIGIBILITY [E;.21] Data from V CPT (9000010.18) file ^TMP("PXHSV",$J,InvExDt,COUNT,"C",X) = CPT [I;.01] ^ PROVIDER NARRATIVE [E;.04] ^TMP("PXHSV",$J,InvExDt,COUNT,"C",X, MODIFIER [E;1/.01]) = "" Data from V POV (9000010.07) file ^TMP("PXHSV",$J,InvExDt,COUNT,"D",X) = POV [I;.01] ^ MODIFIER [E;.06] ^ CAUSE OF DX [E;.07] ^ PLACE OF ACCIDENT [E;.11] ^ PRIMARY/SECONDARY [E;.12] ^TMP("PXHSV",$J,InvExDt,COUNT,"D",X,"N") = PROVIDER NARRATIVE [E;.04] Data from V PROVIDER (9000010.06) file ^TMP("PXHSV",$J,InvExDt,COUNT,"P",X) = PROVIDER [E;.01] ^ PRIMARY/SECONDARY [E;.04] Data from V HOSPITALIZATION (9000010.02) file (If Service Category is for hospitalization) ^TMP("PXHSV",$J,InvExDt,COUNT,"H",X) = DATE OF DISCHARGE [I;.01] ^ ADMITTING DX [E;.12] [] = [I(nternal)/E(xternal); Optional file #; Record #] Subscripts: InvExDt - Inverse FileMan date of DATE OF visit [.01] Count - # of entry VIEWER: TROST,DEBBIE VIEWER: EATON,DENIS STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15664334 COMPONENT/ENTRY POINT: VISIT SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION SUBSCRIBING DETAILS: ADDED JSHARVEY/ 20070122 as per Swesky's request. DBA Comments: JSHARVEY/ 20070122 SCID ADDED DATE/TIME EDITED: JAN 23, 2007@22:14 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SWESKY,JEFF WITH CONCURRENCE OF: FAIN,ZACH NUMBER: 1239 IA #: 1239 DATE CREATED: MAY 26, 1995 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRHS03 NAME: DBIA1239 ID: PXRHS03 GENERAL DESCRIPTION: The Health Summary Package desires to set up an integration agreement with the PCE Package to call the entry point IMMUN^PXRHS03 to retrieve immunization data. Input data will be done via parameter passing and output data will be placed in the ^TMP global in the specified format that is described in this agreement. Entry point: IMMUN(DFN,HSSD) INPUT : DFN - Pointer to PATIENT file (#2) HSSD - Immunization data from before the Health Summary Start Date will also be retrieved when this parameter is set to 1. OUTPUT : Data from V Immunization (9000010.11) file ^TMP("PXI",$J,IMM,InvDt,IFN,0) = IMMUNIZATION [E; .01] ^ IMMUNIZATION SHORT NAME [E;9999999.14,.02] ^ EVENT DATE/TIME or VISIT/ADMIT DATE&TIME [I;1201 or .03] ^ SERIES CODE [I;.04] ^ SERIES [E;.04] ^ REACTION [E;.06] ^ CONTRAINDICATED [I;.07] ^ ORDERING PROVIDER [E;1202] ^ CLINIC [3;1203] ^ ENCOUNTER PROVIDER [E;1204] ^TMP("PXI",$J,IMM,InvDt,IFN,1) = ^ HOSPITAL LOCATION [E;1205] ^ HOSP. LOC. ABBREVIATION [E;44;1] ^ LOC OF ENCOUNTER [E;9000010;.06] ^ OUTSIDE LOC [E;9000010;2101] ^TMP("PXI",$J,IMM,InvDt,IFN,"R",CNT) = REMARKS [E;1101] ^TMP("PXI",$J,IMM,InvDt,IFN,"S") = DATA SOURCE [E;80102] [] = [I(nternal)/E(xternal); Optional file #; Record #] Subscripts: IMM - Immunization name InvDt - Inverse FileMan date of DATE OF event or visit IFN - Internal Record # STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30881813 COMPONENT/ENTRY POINT: IMMUN SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK DATE/TIME EDITED: SEP 16, 2010@10:51 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE NUMBER: 1240 IA #: 1240 DATE CREATED: MAY 26, 1995 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRHS04 NAME: DBIA1240 ID: PXRHS04 GENERAL DESCRIPTION: The Health Summary Package desires to set up an integration agreement with the PCE Package to call the entry point SKIN^PXRHS04 to retrieve skin test data. Input data will be done via parameter passing and output data will be placed in the ^TMP global in the specified format that is described in this agreement. Entry point: SKIN(DFN) INPUT : DFN - Pointer to PATIENT file (#2) OUTPUT : Data from V SKIN TEST (9000010.12) file ^TMP("PXS,$J,SKIN,InvDt,IFN,0) = SKIN TEST [E;.01] ^ EVENT DATE/TIME or VISIT/ADMIT DATE&TIME [I;1201 or .03] ^ RESULTS CODE [I;.04] ^ RESULTS [E;.04] ^ READING [E;.05] ^ DATE READ [I;.06] ^ ORDERING PROVIDER [E;1202] ^ CLINIC [3;1203] ^ ENCOUNTER PROVIDER [E;1204] ^TMP("PXS",$J,SKIN,InvDt,IFN,1) = ^ HOSPITAL LOCATION [E;1205] ^ HOSP. LOC. ABBREVIATION [ E;44;1] ^ LOC OF ENCOUNTER [E;9000010;.06] ^ OUTSIDE LOC [E;9000010;2101] ^TMP("PXS",$J,SKIN,InvDt,IFN,"S") = DATA SOURCE [E;80102] [] = [I(nternal)/E(xternal); Optional file #; Record #] Subscripts: SKIN - Skin Test name InvDt - Inverse FileMan date of DATE OF event or visit IFN - Internal Record # ****** STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15675649 COMPONENT/ENTRY POINT: SKIN SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES NUMBER: 1241 IA #: 1241 DATE CREATED: MAY 26, 1995 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRHS05 NAME: DBIA1241 ID: PXRHS05 GENERAL DESCRIPTION: The Health Summary Package desires to set up an integration agreement with the PCE Package to call the entry point EXAM^PXRHS05 to retrieve Exam data.Input data will be done via parameter passing and output data will be placed in the ^TMP global in the specified format that is described in this agreement. Entry point: EXAM(DFN,ENDDT,BEGDT,OCCLIM) INPUT : DFN - Pointer to PATIENT file (#2) ENDDT - Ending date/time in internal FileMan format - Defaults to today's date at 11:59 pm BEGDT - Beginning date/time in internal FileMan format - Defaults to one year prior to today's date OCCLIM - Maximum # of each type of exam returned OUTPUT : Data from V EXAM (9000010.13) file ^TMP("PXE,$J,EXAM,InvDt,IFN,0) = EXAM [E;.01] ^ EVENT DATE/TIME or VISIT/ADMIT DATE&TIME [I;1201 or .03] ^ RESULTS CODE [I;.04] ^ RESULTS [E;.04] ^ ORDERING PROVIDER [E;1202] ^ CLINIC [3;1203] ^ ENCOUNTER PROVIDER [E;1204] ^ ^TMP("PXE",$J,EXAM,InvDt,IFN,1) = HOSPITAL LOCATION [E;1205] ^ HOSP. LOC. ABBREVIATION [E;44;1] ^ LOC OF ENCOUNTER [E;9000010;.06] ^ OUTSIDE LOC [E;9000010;2101] ^TMP("PXE",$J,EXAM,InvDt,IFN,"S") = DATA SOURCE [E;80102] [] = [I(nternal)/E(xternal); Optional file #; Record #] Subscripts: EXAM - EXAM name InvDt - Inverse FileMan date of DATE OF event or visit IFN - Internal Record # STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15675674 COMPONENT/ENTRY POINT: EXAM SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 1242 IA #: 1242 DATE CREATED: MAY 26, 1995 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRHS06 NAME: DBIA1242 ID: PXRHS06 GENERAL DESCRIPTION: The Health Summary Package desires to set up an integration agreement with the PCE Package to call the entry point TREAT^PXRHS06 to retrieve Treatment data. Input data will be done via parameter passing and output data will be placed in the ^TMP global in the specified format that is described in this agreement. Entry point: TREAT(DFN,ENDDT,BEGDT,OCCLIM,CATCODE) INPUT : DFN - Pointer to PATIENT file (#2) ENDDT - Ending date/time in internal FileMan format - Defaults to today's date at 11:59 pm BEGDT - Beginning date/time in internal FileMan format - Defaults to one year prior to today's date OCCLIM - Maximum number of days for which data is returned (If multiple visits on a given day, all data for these visit will be returned) or an "R" for only the most recent occurrence of each topic Note: If event date is used, it may appear that too many occurrences are retrieved but it is based on visit date not event date. returned (Can include multiple codes) CATCODE - Pattern Match which controls visit data that is A = AMBULATORY H = HOSPITALIZATION I = IN HOSPITAL C = CHART REVIEW T = TELECOMMUNICATIONS N = NOT FOUND S = DAY SURGERY O = OBSERVATION E = EVENT (HISTORICAL) R = NURSING HOME D = DAILY HOSPITALIZATION DATA X = ANCILLARY PACKAGE DAILY DATA OUTPUT : Data from V TREATMENT (9000010.15) file ^TMP("PXT,$J,InvDt,TREAT,IFN,0) = TREATMENT [E;.01] ^ EVENT DATE/TIME or VISIT/ADMIT DATE&TIME [I;1201 or .03] ^ HOW MANY [I;.04] ^ ORDERING PROVIDER [E;1202] ^ CLINIC [3;1203] ^ ENCOUNTER PROVIDER [E;1204] ^TMP("PXT",$J,InvDt,TREAT,IFN,1) = HOSPITAL LOCATION [E;1205] ^ HOSP. LOC. ABBREVIATION [E;44;1] ^ LOC OF ENCOUNTER [E;9000010;.06] ^ OUTSIDE LOC [E;9000010;2101] ^TMP("PXT",$J,InvDt,TREAT,IFN,"S") = DATA SOURCE [E;80102] ^TMP("PXT",$J,InvDt,TREAT,IFN,"P") = PROVIDER NARRATIVE [E;.06] ^TMP("PXT",$J,InvDt,TREAT,IFN,"PNC") = PROVIDER NARR. CATEGORY [E;80201] [] = [I(nternal)/E(xternal); Optional file # ; Record #] Subscripts: InvDt - Inverse FileMan date of DATE OF event or visit minus time TREAT - TREATMENT PROVIDED IFN - Internal Record # STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15675684 COMPONENT/ENTRY POINT: TREAT SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 1243 IA #: 1243 DATE CREATED: MAY 26, 1995 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRHS07 NAME: DBIA1243 ID: PXRHS07 GENERAL DESCRIPTION: The Health Summary Package desires to set up an integration agreement with the PCE Package to call the entry point HF^PXRHS07 to retrieve Health Factor data. Input data will be done via parameter passing and output data will be placed in the ^TMP global in the specified format that is described in this agreement. Entry point: HF(DFN,ENDDT,BEGDT,OCCLIM,ITEMS) INPUT : DFN - Pointer to PATIENT file (#2) ENDDT - Ending date/time in internal FileMan format - Defaults to today's date at 11:59 pm BEGDT - Beginning date/time in internal FileMan format - Defaults to one year prior to today's date OCCLIM - Maximum number of days for which data is returned for each Health Factors item. If multiple visits on a given day, all data for these visit will be returned. Note: If event date is used, it may appear that too many occurrences are retrieved but it is it is based on visit date not event date. ITEMS - Optional array containing a selected list of HF Categories. If not used will get all catergories of health factors. OUTPUT : Data from V HEALTH FACTORS (9000010.23) file ^TMP("PXF,$J,HFC,HF,InvDt,IFN,0) = Health Factor [E;.01] ^ EVENT DATE/TIME or VISIT/ADMIT DATE&TIME [I;1201 or .03] ^ SHORT NAME [E;9999999.64;.04] ^ LEVEL/SEVERITY [E;.04] ^ ORDERING PROVIDER [E;1202] ^ CLINIC [3;1203] ^ ENCOUNTER PROVIDER [E;1204] ^TMP("PXF",$J,HFC,HF,InvDt,IFN,1) = HOSPITAL LOCATION [E;1205] ^ HOSP. LOC. ABBREVIATION [E;44;1] ^ LOC OF ENCOUNTER [E;9000010;.06] ^ OUTSIDE LOC [E;9000010;2101] ^TMP("PXF",$J,HFC,HF,InvDt,IFN,"S") = DATA SOURCE [E;80102] [] = [I(nternal)/E(xternal); Optional file #; Record #] Subscripts: HFC - Health Factor Category name HF - Health Factor name InvDt - Inverse FileMan date of DATE OF event or visit IFN - Internal Record # STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15675693 COMPONENT/ENTRY POINT: HF SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 1244 IA #: 1244 DATE CREATED: MAY 26, 1995 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRHS09 NAME: DBIA1244 ID: PXRHS09 GENERAL DESCRIPTION: The Health Summary Package desires to set up an integration agreement with the PCE Package to call the entry point MEAS^PXRHS09 to retrieve Measurement data. Input data will be done via parameter passing and output data will be placed in the ^TMP global in the specified format that is described in this agreement. Entry point: MEAS(DFN,ENDDT,BEGDT,OCCLIM) INPUT : DFN - Pointer to PATIENT file (#2) ENDDT - Ending date/time in internal FileMan format - Defaults to today's date at 11:59 pm BEGDT - Beginning date/time in internal FileMan format - Defaults to one year prior to today's date OCCLIM - Maximum number of days for which data is returned (If multiple visits on a given day, all data for these visit will be returned) Note: If event date is used, it may appear that too many occurrences are retrieved but it is based on visit date not event date. OUTPUT : Data from V MEASUREMENT (9000010.01) file ^TMP("PXM",$J,TYPE,InvDt,IFN,0) = TYPE [E;.01] ^ MEASUREMENT TYPE DESCRIPTION [E;9999999;.02] ^ EVENT DATE/TIME or VISIT/ADMIT DATE&TIME [I;1201 or .03] ^ VALUE [E;.04] ^ ORDERING PROVIDER [E;1202] ^ CLINIC [3;1203] ^ ENCOUNTER PROVIDER [E;1204] ^TMP("PXM",$J,TYPE,InvDt,IFN,1) = HOSPITAL LOCATION [E;1205] ^ HOSP. LOC. ABBREVIATION [E;44;1] ^ LOC OF ENCOUNTER [E;9000010;.06] ^ OUTSIDE LOC [E;9000010;2101] ^TMP("PXM",$J,TYPE,InvDt,IFN,"S") = DATA SOURCE [E;80102] [] = [I(nternal)/E(xternal); Optional file #; Record #] Subscripts: TYPE - Measurement Type InvDt - Inverse FileMan date of DATE OF event or visit IFN - Internal Record # STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15675699 COMPONENT/ENTRY POINT: MEAS SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 1245 IA #: 1245 FILE NUMBER: 6914 GLOBAL ROOT: DD(6914 DATE CREATED: JUL 20, 1995 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ENGINEERING XREF CLEAN UP ID: DD(6914 GENERAL DESCRIPTION: Engineering exported a series of cross references in the Equipment Inv (#6914) file to support the upload of equipment data to the ISMS system. These mumps cross references were never activated because the ISMS system was not brought on line. These cross references are now obsolete and should be removed from the Equipment Inv file. The following cross references will be deleted with patch EN*7*25 using code in a PRE-INIT AFTER USER COMMIT routine. CROSS-REFERENCE FIELD # FIELD NAME --------------- ------- ---------------------- AI1 1 MANUFACTURER AI2 2 PARENT SYSTEM AI27 4 MODEL AI3 5 SERIAL # AI0 7 TYPE OF ENTRY AI5 10 VENDOR POINTER AI6 11 PURCHASE ORDER # AI7 12 ACQUISITION VALUE AI8 12.5 LEASE COST AI9 13 ACQUISITION DATE AI10 13.5 ACQUISITION SOURCE AI11 15 LIFE EXPECTANCY AI12 16 REPLACEMENT DATE AI13 18 CATEGORY STOCK NUMBER AI26 19 CMR AI14 20 USE STATUS AI15 20.1 OWNERSHIP AI16 20.5 TURN-IN DATE AI17 22 DISPOSITION DATE AI18 23 PHYSICAL INVENTORY DATE AI19 31 DISPOSITION METHOD AI20 32 DISPOSITION VALUE AI21 33 CONTROLLED ITEM? AI22 34 CAPITALIZED? AI23 36 COST CENTER AI24 38 GENERAL LEDGER ACCOUNT AI25 39 YALD CODE AI28 51 REPLACING (ENTRY NUMBER) Code similar to the following will be used in the pre-init to delete the cross references from the data dictionary. ENXGIPR ;WIRMFO/SAB-PRE INIT ;7/21/95 ;;7.0;ENGINEERING;**25**;Aug 17, 1993 N ENFX Q:'$D(DIFROM) W !,"Performing Pre-Init...",! XREF ; delete any obsolete ISMS cross references W !,"Deleting obsolete xrefs from Equipment Inv (#6914) file..." F ENFX="1^AI1","2^AI2","4^AI27","5^AI3","7^AI0","10^AI5", "11^AI6","12^AI 7","12.5^AI8","13^AI9","13.5^AI10" D DELXREF ($P(ENFX,U),$P(ENFX,U,2)) F ENFX="15^AI11","16^AI12","18^AI13","19^AI26","20^AI14" ,"20.1^AI15","20.5^AI16","22^AI17" D DELXREF($P(ENFX,U),$P(ENFX,U,2)) F ENFX="23^AI18","31^AI19","32^AI20","33^AI21","34^AI22", "36^AI23","38^AI24","39^AI25","51^AI28" D DELXREF($P(ENFX,U),$P(ENFX,U,2)) XREFEND ; end of delete obsolete ISMS cross references EXIT ; W !,"Completed Pre-Init",! Q DELXREF(ENF,ENX) ; for field number ENF delete xref ENX N ENI Q:'$D(^DD(6914,0,"IX",ENX,6914,ENF)) ; already deleted S ENI=0 F S ENI=$O(^DD(6914,ENF,1,ENI)) Q:'ENI D .K:$G(^DD(6914,ENF,1,ENI,0))=("6914^"_ENX_"^MUMPS") ^DD(6914,ENF,1,ENI) K ^DD(6914,0,"IX",ENX,6914,ENF) K:'$O(^DD(6914,ENF,1,0)) ^DD(6914,"IX",ENF) ; no xrefs left on field W !," ",ENX," xref deleted from field ",ENF Q The following DD nodes may be deleted ^DD(6914,field number,1,ien for xref) ^DD(6914,0,"IX",xref,6914,field number) INTEGRATION REFERENCES LIST MAR 18,2015 11:24 PAGE 4 -------------------------------------------------------------------------------- ^DD(6914,"IX",field number) This will only be done if there are no cross references left on the field. (i.e. '$O(^DD(6914,field number,1,0)) is true). STATUS: Active DURATION: Next Version MAIL MESSAGE: 16488291 GOOD ONLY FOR VERSION: 7.0 SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring NUMBER: 1246 IA #: 1246 DATE CREATED: JUL 20, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGPMDDCF NAME: DGPMDDCF CALLS ID: DGPMDDCF GENERAL DESCRIPTION: This agreement allows other packages to call the following tags in the routine DGPMDDCF: WIN, RIN, BOS, AUTH, and OPER. These calls return info on whether wards and beds are in service and the number of beds in service, authorized, and operating for a given ward. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: WIN COMPONENT DESCRIPTION: Requires D0 to be passed as the IEN of the WARD LOCATION (file #42) which you'd like to know is active or not. DGPMOS can be passed as a date to compute whether the ward is in service (it assumes DT if not defined). Returns a 1 if ward is inactive as of date or 0 if it's active. -1 returned if D0 not defined or date not valid. VARIABLES: D0 TYPE: Input VARIABLES DESCRIPTION: IEN of WARD LOCATION file. VARIABLES: DGPMOS TYPE: Input VARIABLES DESCRIPTION: Date to determine if ward is out of service as of. VARIABLES: X TYPE: Output VARIABLES DESCRIPTION: 1 if ward out of service, 0 if in service, or -1 if input variables not defined properly. COMPONENT/ENTRY POINT: RIN COMPONENT DESCRIPTION: Requires D0 to be passed as the IEN of the ROOM-BED (file #405.4) which you'd like to know is active or not. DGPMOS can be passed as a date to compute whether the bed is in service (it assumes DT if not defined). Returns a 1 if bed is inactive as of date or 0 if it's active. -1 returned if D0 not defined or date not valid. VARIABLES: D0 TYPE: Input VARIABLES DESCRIPTION: IEN of ROOM-BED file VARIABLES: DGPMOS TYPE: Input VARIABLES DESCRIPTION: Date for which you'd like to know if room-bed is in service. Optional: assumes DT if left undefined. VARIABLES: X TYPE: Output VARIABLES DESCRIPTION: Returned as 1 if bed is out of service, 0 if it's in service, or -1 if the input variables are not defined properly. COMPONENT/ENTRY POINT: BOS COMPONENT DESCRIPTION: Computes number of beds out of service for a given ward. D0 defines the WARD LOCATION IEN and DGPMOS can be passed as the date on which to make the computation (assumes DT if undefined). VARIABLES: D0 TYPE: Input VARIABLES DESCRIPTION: IEN of WARD LOCATION file VARIABLES: DGPMOS TYPE: Input VARIABLES DESCRIPTION: Date for which to return calculation. Assumes DT if undefined. VARIABLES: X TYPE: Output VARIABLES DESCRIPTION: Number of beds out of service on ward as of date in question. COMPONENT/ENTRY POINT: AUTH COMPONENT DESCRIPTION: Returns number of authorized beds for WARD LOCATION defined by D0 as of date defined in DGPMOS (assumes DT if not defined). VARIABLES: D0 TYPE: Input VARIABLES DESCRIPTION: IEN of WARD LOCATION file VARIABLES: DGPMOS TYPE: Input VARIABLES DESCRIPTION: Optional variable defining date for which to return calculation. Assumes DT if left undefined. VARIABLES: X TYPE: Output VARIABLES DESCRIPTION: Number of authorized beds for ward requested as of date selected. COMPONENT/ENTRY POINT: OPER COMPONENT DESCRIPTION: Computes the number of operating beds for a WARD LOCATION defined in the variable D0 on a date defined by DGPMOS (assumes DT if left undefined). VARIABLES: D0 TYPE: Input VARIABLES DESCRIPTION: IEN of WARD LOCATION file VARIABLES: DGPMOS TYPE: Input VARIABLES DESCRIPTION: Optional variable to define date for which you'd like number of operating beds returned. Assumes DT if left undefined. VARIABLES: X TYPE: Output VARIABLES DESCRIPTION: Number of operating beds for ward requested on date input. NUMBER: 1247 IA #: 1247 DATE CREATED: MAY 26, 1995 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRHS12 NAME: DBIA1247 ID: PXRHS12 GENERAL DESCRIPTION: The Health Summary Package desires to set up an integration agreement with the PCE Package to call the entry point VISIT^PXRHS12 to retrieve Hospitalization Visit, ICD-9, CPT, and Provider data. Input data will be done via parameter passing and output data will be placed in the ^TMP global in the specified format that is described in this agreement. Entry point: VISIT(DFN,ENDDT,BEGDT,OCCLIM) INPUT : DFN - Pointer to PATIENT file (#2) ENDDT - Ending date/time in internal FileMan format - Defaults to today's date at 11:59 pm BEGDT - Beginning date/time in internal FileMan format - Defaults to one year prior to today's date OCCLIM - Maximum number of visits returned OUTPUT : Data from VISIT (9000010) file except for hosp. loc. abbr. ^TMP("PXHSV",$J,InvExDt,COUNT,0) = VISIT/ADMIT DATE&TIME [I;.01] ^ TYPE [E;.03] ^ LOC. OF ENCOUNTER [E;.06] ^ SERVICE CATEGORY [E;.07] ^ CHECK OUT DATE&TIME [I;.18] ^ HOSPITAL LOCATION [E;.22] ^ HOSP. LOC. ABBREVIATION [E;44;1] ^ OUTSIDE LOCATION [E;2101] ^ CLINIC [E;.08] ^ WALK IN/APPT [E;.16] ^ LEVEL OF SERVICE [E;.17] ^ ELIGIBILITY [E;.21] Data from V CPT (9000010.18) file ^TMP("PXHSV",$J,InvExDt,COUNT,"C",X) = CPT [I;.01] ^ PROVIDER NARRATIVE [E;.04] ^TMP("PXHSV",$J,InvExDt,COUNT,"C",X,MODIFIER [E;1/.01]) = "" Data from V POV (9000010.07) file ^TMP("PXHSV",$J,InvExDt,COUNT,"D",X) = POV [I;.01] ^ MODIFIER [E;.06] ^ CAUSE OF DX [E;.07] ^ PLACE OF ACCIDENT [E;.11] ^ PRIMARY/SECONDARY [E;.12] ^TMP("PXHSV",$J,InvExDt,COUNT,"D",X,"N") = PROVIDER NARRATIVE [E;.04] Data from V PROVIDER (9000010.06) file ^TMP("PXHSV",$J,InvExDt,COUNT,"P",X) = PROVIDER [E;.01] ^ PRIMARY/SECONDARY [E;.04] Data from V HOSPITALIZATION (9000010.02) file (If Service Category is for hospitalization) ^TMP("PXHSV",$J,InvExDt,COUNT,"H",X) = DATE OF DISCHARGE [I;.01] ^ ADMITTING DX [E;.12] [] = [I(nternal)/E(xternal); Optional file #; Record #] Subscripts: InvExDt - Inverse FileMan date of DATE OF visit [.01] Count - # of entry STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15675715 COMPONENT/ENTRY POINT: VISIT SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 1248 IA #: 1248 DATE CREATED: MAY 26, 1995 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRHS20 NAME: DBIA1248 ID: PXRHS20 GENERAL DESCRIPTION: The Health Summary Package desires to set up an integration agreement with the PCE Package to call the entry point MEAS^PXRHS20 to retrieve Measurement data. Input data will be done via parameter passing and output data will be placed in the ^TMP global in the specified format that is described in this agreement. Entry point: MEAS(DFN,PATDOB,SEX,ENDDT,BEGDT,OCCLIM,MSRPANEL) INPUT: DFN - Pointer to PATIENT file (#2) PATDOB - Patient's Date of Birth in MM/DD/YY Format SEX - Patient's Sex ("M" for Male and "F" for Female) OCCLIM - Maximum number of days for which data is returned (If multiple visits on a given day, all data for these visit will be returned) Note: If event date is used, it may appear that too many occurrences are retrieved but it is based on visit date not event date. MSRPANEL - Pointer to Health Summary Meas Panel (9001017) file OUTPUT: Data from V MEASUREMENT (9000010.01) file ^TMP("PXM",$J,InvDt,ORDER,IFN) = VALUE [E;.04] ^ Optional error note for BMI and RW values If a transform exists in file 9001017 for this panel item, it will be applied to VALUE. Data from HEALTH SUMMARY MEAS PANEL (9001017) file ^TMP("PXF",$J,PNAME,ORDER)= PANEL COMPONENT [E;9001017.01;1] ^ FIELD WIDTH [E;9001017.01;2] ^ LABEL [E;9001017.01;3] ^ NOTE TO DISPLAY [E;9001017.01;5] [] = [I(nternal)/E(xternal); Optional file #; Record #] Subscripts: InvDt - Inverse FileMan date of DATE OF event or visitr visit TYPE - Measurement Type IFN - Internal Record # ORDER - Order in Panel PNAME - Measurement Panel Name STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15675724 COMPONENT/ENTRY POINT: MEAS SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 1249 IA #: 1249 FILE NUMBER: 10 GLOBAL ROOT: DIC(10, DATE CREATED: MAY 30, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DIC(10, ID: DIC(10, GLOBAL REFERENCE: DIC(10,D0,0) FIELD NUMBER: 2 FIELD NAME: ABBREVIATION LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field contains the abbreviation for this race entry. GENERAL DESCRIPTION: The integration agreement allows reading (with FileMan only) the ABBREVIATION field (#2) of the RACE file (#10). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15733678 SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 1251 IA #: 1251 FILE NUMBER: 150.9 GLOBAL ROOT: DIC(150.9, DATE CREATED: AUG 03, 1995 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA 1251 ID: DIC(150.9, GLOBAL REFERENCE: DIC(150.9,1,4) FIELD NUMBER: 402 FIELD NAME: SITE PART OF VISIT ID LOCATION: 4;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is check by the PCE debugging utility to see if it has been set. GENERAL DESCRIPTION: PCE debugging utility calls Fileman to display the entry number 1 to the user so that they can review it. VIEWER: TROST,DEBBIE VIEWER: DEFA,TANA VIEWER: SEEGER,ANTHONY VIEWER: EATON,DENIS VIEWER: SMITH,VAUGHN STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24794181 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany NUMBER: 1252 IA #: 1252 DATE CREATED: JUN 20, 1995 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SDUTL3 NAME: PRIMARY CARE INPUT AND OUTPUT API CALLS ID: SDUTL3 GENERAL DESCRIPTION: SDUTL3 contains 2 input APIs and 3 output APIs which allow enter of/return of the CURRENT PC PRACTITIONER and CURRENT PC TEAM. The three output APIs will continue to be supported. The two input APIs will be supported as long as the two fields exist in the patient file. The approximate time for deletion of these fields is March 1 2000. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29758012 COMPONENT/ENTRY POINT: $$OUTPTPR(DFN[,SCDATE][,SCPCROLE]) COMPONENT DESCRIPTION: Function: $$OUTPTPR^SDUTL3(DFN) Input: DFN - This is a required parameter that is the internal entry number of the PATIENT file. Output: CURRENT PC PRACTITIONER in Internal^External format Internal- If there is a successful lookup for the CURRENT PC PRACTITIONER, this is a pointer to the NEW PERSON file (#200). If it is not successful, a 0 is returned. External- If there is a successful lookup, this is the practitioner's name, as entered in the NAME field (#.01) of file #200. If there is not a successful lookup, this is null. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal entry of the PATIENT file (#2) VARIABLES: SCDATE TYPE: Input VARIABLES DESCRIPTION: Relevant Date (Default=DT) VARIABLES: SCPCROLE TYPE: Input VARIABLES DESCRIPTION: Type of PC Role (Default =1 (PC Practitioner),2=Attending) COMPONENT/ENTRY POINT: $$OUTPTTM(DFN[,SCDATE][,ASSTYPE]) COMPONENT DESCRIPTION: Output API for CURRENT PC TEAM field: ===================================== Function: $$OUTPTTM^SDUTL3(DFN) Input: DFN - This is a required parameter that is the internal entry number of the PATIENT file. Output: CURRENT PC TEAM in Internal^External format Internal- If there is a successful lookup for the CURRENT PC TEAM, this is a pointer to the TEAM file (#404.51), which is distributed with this patch. If the lookup is not successful, a 0 is returned. External- If there is a successful lookup, this is the team's name, as entered in the NAME field (#.01) of file #404.51. If there is not a successful lookup, this is null. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal entry of the PATIENT file (#2) VARIABLES: ASSTYPE TYPE: Input VARIABLES DESCRIPTION: Assignment Type (Default=1: PC Team) VARIABLES: SCDATE TYPE: Input VARIABLES DESCRIPTION: Date of interest (Default=DT) COMPONENT/ENTRY POINT: INPTPR(DFN,PRACT) COMPONENT DESCRIPTION: Subroutine: INPTPR^SDUTL3(DFN,PRACT) Input: DFN - This is a required parameter that is the internal entry number of the PATIENT file. PRACT- This is a required parameter that is a pointer to file #200 associated with the patient's primary care practitioner. Output: SDOKS- This is 1 if the data is stored successfully, 0 otherwise. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal entry of the PATIENT file (#2) VARIABLES: PRACT TYPE: Input VARIABLES DESCRIPTION: Internal entry number of the NEW PERSON file (#200) denoting the practitioner assigned to the patient. VARIABLES: SDOKS TYPE: Output VARIABLES DESCRIPTION: 1 if addition was successful or 0 if it was not. COMPONENT/ENTRY POINT: INPTTM(DFN,TEAM) COMPONENT DESCRIPTION: Subroutine: INPTTM^SDUTL3(DFN,TEAM) Input: DFN - This is a required parameter that is the internal entry number of the PATIENT file. TEAM - This is a required parameter that is a pointer to the TEAM file, which associate with this patient's primary care team. Output: SDOKS- This is 1 if the data is stored successfully, 0 otherwise. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal entry of the PATIENT file (#2) VARIABLES: TEAM TYPE: Input VARIABLES DESCRIPTION: Then internal entry number of the TEAM file associated with the patient. VARIABLES: SDOKS TYPE: Output VARIABLES DESCRIPTION: 1 if addition was successful or 0 if it was not. COMPONENT/ENTRY POINT: $$OUTPTAP(DFN[,SCDATE]) COMPONENT DESCRIPTION: Function: $$OUTPTAP^SDUTL3(DFN) Input: DFN - This is a required parameter that is the internal entry number of the PATIENT file. Output: CURRENT PC ASSOCIATE PROVIDER in Internal^External format. Internal - If there is a successfule lookup for the CURRENT PC ASSOCIATE PROVIDER, this is a pointer to the PERSON file (#200). If it is not successful, a 0 is returned. External - If there is a successfule lookup, this is the provider's name as entered in the field (#.01) of file #200. If there is not a successfule lookup, this is null. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal entry of the PATIENT file (#2) VARIABLES: SCDATE TYPE: Input VARIABLES DESCRIPTION: Relevant Date (Default=DT) NUMBER: 1253 IA #: 1253 FILE NUMBER: 9000011 GLOBAL ROOT: AUPNPROB( DATE CREATED: MAY 30, 1995 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1253 ID: AUPNPROB( GLOBAL REFERENCE: AUPNPROB('AC',DFN,REC # GLOBAL REFERENCE: AUPNPROB(REC #,0) FIELD NUMBER: .01 FIELD NAME: DIAGNOSIS ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .08 FIELD NAME: date entered ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Health Summary Package desires to set up an integration agreement with the Problem List Package to access the Problem (#900011) file. Health Summary needs to check if the Problem List file contains a specific ICD9 code (diagnosis) for a given patient. The "AC" cross reference is checked to get problem entries for a patient. DFN is the internal patient record number. The Diagnosis pointer (1st piece of the 0 node) and Date Entered (8th piece of the 0 node) are retrieved for each record found. This is done in the following manner: S GMTSHRFE="" F S GMTSHRFE=$O(^AUPNPROB("AC",DFN,GMTSHRFE)) Q:'GMTSHRFE S Y=$P(^AUPNPROB(GMTSHRFE,0),U),GMTSHRID=$P(^(0),U,8), GMTSHRIC=$P(^ICD9(Y,0),U)_" " STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15745708 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 1254 IA #: 1254 FILE NUMBER: 9000001 GLOBAL ROOT: AUPNPAT( DATE CREATED: MAY 30, 1995 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRHS13 NAME: DBIA1254 ID: PXRHS13 GLOBAL REFERENCE: AUPNPAT(DFN,12,REC #, FIELD NUMBER: 1201 FIELD NAME: LOCATION OF HOME ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Health Summary Package desires to set up an integration agreement with the PCE Package to access the ^PXRHS13 routine to get a patient's location of home. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15759896 COMPONENT/ENTRY POINT: LOC COMPONENT DESCRIPTION: This entry point returns a Patient's Location of Home from the Patient/IHS (#9000001) file. This routine will return the data in the ^TMP global in the following format: ^TMP("PXLOC",$J,LINE NUMBER) = LOCATION OF HOME (#1201) WORD PROCESSING FIELD. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient's internal record number. SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 1255 IA #: 1255 DATE CREATED: AUG 08, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTSCU2 NAME: DBIA1255 ID: DGMTSCU2 GENERAL DESCRIPTION: The IVM package files new Means Tests into the PIMS Means Test module. This routine contains utilities for Means Test processing. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 16813142 COMPONENT/ENTRY POINT: STA COMPONENT DESCRIPTION: This call is used to determine Means Test status and type of care. VARIABLES: DGCAT TYPE: Input VARIABLES DESCRIPTION: The variable DGCAT is the Means Test category code. VARIABLES: DGMTYPT TYPE: Input VARIABLES DESCRIPTION: The variable DGMTYPT is 1 for type of test (Means Test). VARIABLES: DGMTS TYPE: Output VARIABLES DESCRIPTION: The variable DGMTS points to the Means Test status in the MEANS TEST STATUS file (#408.32). VARIABLES: DGTYC TYPE: Output VARIABLES DESCRIPTION: The variable DGTYC is the code for the type of care the Means Test status is associated with. SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 1256 IA #: 1256 FILE NUMBER: 811.9 GLOBAL ROOT: PXD(811.9 DATE CREATED: AUG 03, 1995 CUSTODIAL PACKAGE: CLINICAL REMINDERS CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1256 ID: PXD(811.9 GLOBAL REFERENCE: PXD(811.9,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to GENERAL DESCRIPTION: This IA is for packages needing to point to the Reminder Definition (#811.9) file. The Selection Item (.01) field in the Structure Multiple (field 1) of the Health Summary Type (#142) file points to the file #811.9. The Selection File (.01) field in the Selection File Multiple (Field 7) of the Health Summary Component (#142.1) file points to the file #811.9. Health Summary also requires the ability to add the application group "GMTS" ^DIC(811.9) when the Reminder Definition file exists. This is done with a VA Fileman call in the Health Summary Preinit Routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17801999 KEYWORDS: CLINICAL REMINDERS KEYWORDS: HEALTH SUMMARY KEYWORDS: ORDER ENTRY KEYWORDS: AICS KEYWORDS: LAB SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 1257 IA #: 1257 DATE CREATED: AUG 08, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTCOU1 NAME: DBIA1257 ID: DGMTCOU1 GENERAL DESCRIPTION: This routine contains utilities for Means Tests/Copay processing. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 16813142 COMPONENT/ENTRY POINT: $$LST(DFN,DGDT,DGMTYPT1) COMPONENT DESCRIPTION: This call is used to determine last Means Test or Copay for a patient. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The variable DFN points to the patient in the PATIENT file (#2). VARIABLES: DGDT TYPE: Input VARIABLES DESCRIPTION: The variable DGDT is the date/time used for determining the last test for the patient. VARIABLES: DGMTYPT1 TYPE: Input VARIABLES DESCRIPTION: The variable DGMTYPT1 is for type of test (Means Test or Copay). 1-Means Test, 2-Copay, 3-Either Means Test or Copay (Default) VARIABLES: OUT TYPE: Output VARIABLES DESCRIPTION: The output from this function is the last Means Test or Copay for the patient. SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany SUBSCRIBING DETAILS: The IVM package files new Means Tests into the PIMS Means Test module. The variable DGMTYPT1 is 3 for type of test (Means Test or Copay). SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL SUBSCRIBING DETAILS: Beneficiary Travel use $$LST^DGMTCOU1 to return the last Means Test or RX Copay IEN in a single pass by passing the variable DGMTYPT1 = 3. The information returned is then used to determine what is displayed on the Bene Travel information screen 1 for Income, Source of Income and MT Status. It is also used as one of the requirements to determine if an auto waiver is granted for the Bene Travel deductible. The Bene Travel application reads Means Test/Copay data. It does NOT update the Means Test and/or RX-Copay test. DBA Comments: 2/8/13-MM: ICR opened for editing. The original ICR appears to focus on IVM use of the API. The following changes were made to accommodate a second subscriber: * Moved some of the original General Description text ('The IVM package files new Means Tests into the PIMS Means Test module.') to the Subscribing Details section for IVM. * Moved the original variable description for the DGMTYP1 input variable to Subscribing Details section for IVM. * Modified original variable description for the DGMTYP1 input variable and added the values for this parameter. It now reads: 'The variable DGMTYPT1 is for type of test (Means Test or Copay). 1-Means Test, 2-Copay, 3-Either Means Test or Copay (Default)'. 2/15/13-MM: Added Beneficiary Travel as a subscriber for DGBT*1*20 scheduled for completion in February 2013. The Technical Analysis/ICR team reviewed this request. At this time, it is difficult to find knowledgeable Registration/Means Test resources. Bene Travel is a current subscriber to ICR #642 which also returns Means Test/Copay data. Bene Travel indicated for DGBT*1*20 they decided to use DGMTCOU1 as it will check Means Test and RX Copay test in one call. DGMTU (ICR #642) would require two calls to accomplish the same thing. DATE ACTIVATED: FEB 15, 2013 DATE/TIME EDITED: FEB 08, 2013@11:27 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: DELLINGER,BARRY WITH CONCURRENCE OF: MARKS,MARY DATE/TIME EDITED: FEB 08, 2013@11:49 ACTION: CONTENT CORRECTED AT THE REQUEST OF: MARKS,MARY WITH CONCURRENCE OF: MARKS,MARY DATE/TIME EDITED: FEB 15, 2013@09:08 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: DELLINGER,BARRY WITH CONCURRENCE OF: MARKS,MARY DATE/TIME EDITED: FEB 15, 2013@09:09 ACTION: APPROVED AT THE REQUEST OF: DELLINGER,BARRY WITH CONCURRENCE OF: MARKS,MARY NUMBER: 1259 IA #: 1259 FILE NUMBER: 9001017 GLOBAL ROOT: APCHSMPN( DATE CREATED: MAY 30, 1995 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1259 ID: APCHSMPN( GLOBAL REFERENCE: APCHSMPN(REC #,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to GENERAL DESCRIPTION: The Health Summary Package desires to set up an integration agreement with the PCE Package to point to the Health Summary MEAS Panel (#9001017) file. The Selection Item (.01) field in the Structure Multiple (field 1) of the Health Summary Type (#142) file points to this file. The Selection File (.01) field in the Selection File multiple (field 7) of the Health Summary Component (#142.1) file points to this file. Health Summary also requries the ability to add the application group "GMTS" to ^DIC(9001017) when the Health Summary MEAS Panel file exists. This is done with a fileman call. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17801999 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 1261 IA #: 1261 FILE NUMBER: 9000011 GLOBAL ROOT: AUPNPROB( DATE CREATED: AUG 09, 1995 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1261 ID: AUPNPROB( GLOBAL REFERENCE: AUPNPROB(IEN,0) FIELD NUMBER: .02 FIELD NAME: PATIENT NAME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the patient for whom this problem has been observed and recorded. GLOBAL DESCRIPTION: This file contains patient specific problems entered by the various providers of service GENERAL DESCRIPTION: The Patient Care Encounter Package would like to do a direct global read on a Problem List node. VIEWER: PRICE,DEBORAH VIEWER: TROST,DEBBIE VIEWER: GREEN,JOANN VIEWER: DEFA,TANA VIEWER: SEEGER,ANTHONY VIEWER: BUECHLER,MELANIE K VIEWER: EATON,DENIS VIEWER: SMITH,VAUGHN STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 16814465 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City NUMBER: 1265 IA #: 1265 FILE NUMBER: 41.1 GLOBAL ROOT: DGS(41.1 DATE CREATED: OCT 20, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR conversion needs sched admissions ID: DGS(41.1 GLOBAL REFERENCE: DGS(41.1,C GLOBAL DESCRIPTION: Uses C cross-reference to get future scheduled admissions. GLOBAL REFERENCE: DGS(41.1,DA,0) FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Retrieves PATIENT file pointer for use to determine OE/RR record to convert. GENERAL DESCRIPTION: The OE/RR version 3 conversion would like permission to loop through the "C" index of the scheduled admission file. It will then access the 0 node to get the PATIENT pointer. STATUS: Active DURATION: Next Version MAIL MESSAGE: 25302543 GOOD ONLY FOR VERSION: 3.0 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 1268 IA #: 1268 FILE NUMBER: 9999999.64 GLOBAL ROOT: AUTTHF( DATE CREATED: MAY 31, 1995 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1268 ID: AUTTHF( GLOBAL REFERENCE: AUTTHF(REC #,0) FIELD NUMBER: .01 FIELD NAME: FACTOR ACCESS: Pointed to GENERAL DESCRIPTION: The Health Summary Package desires to set up an integration agreement with the PCE Package to point to the Health Factors (#9999999.64) file. The Selection Item (.01) field in the Structure Multiple (field 1) of the Health Summary Type (#142) file points to the Health Factors file. The Selection File (.01) field in the Selection File multiple (field 7) of the Health Summary Component (#142.1) file points to the Health Factors file. Health Summary also requires the ability to add the application group "GMTS" ^DIC(9999999.64) when the Health Factors files exists. This is done with a Fileman Call. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17801999 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 1273 IA #: 1273 FILE NUMBER: 9000010 GLOBAL ROOT: AUPNVSIT( DATE CREATED: AUG 03, 1995 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRHS14 NAME: DBIA1273 ID: PXRHS14 GLOBAL REFERENCE: AUPNVSIT(0) GLOBAL REFERENCE: AUPNVSIT('AA',DFN,VISIT,REC #) GLOBAL REFERENCE: AUPNVSIT(REC #,0) FIELD NUMBER: .01 FIELD NAME: VISIT/ADMIT DATE&TIME ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .08 FIELD NAME: CLINIC ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Health Summary Package desires to set up an integration agreement with the PCE Package to access the described API to the Visit (#900010) file. VISIT^PXRHS14(DFN,FROM,RECNO,OCCLIM,CATCODE,PSTAT) INPUT: DFN - Pointer to PATIENT file (#2). FROM - Index entry from which to begin the list. Passed by reference. RECNO - Record number. Passed by reference. OCCLIM - Maximum number of visits to return. CATCODE - Pattern Match which controls visit data that is returned (Can include multiple codes). A = AMBULATORY H = HOSPITALIZATION I = IN HOSPITAL C = CHART REVIEW T = TELECOMMUNICATIONS N = NOT FOUGERY O = OBSERVATION E = EVENT (HISTORICAL) R = NURSING HOME D = DAILY HOSPITALIZATION DATA X = ANCILLARY PACKAGE DAILY DATA PSTAT - Patient Status. 1 = Inpatient 0 or NULL = Outpatient OUTPUT: Data fro0) file except for hosp. loc. abbr. ^TMP("PXV",$J,InvExDt,RecNo,0) = VISIT/ADMIT DATE&TIME [I;.01] ^ LOC. OF ENCOUNTER [E;.06] ^ SERVICE CATEGORY [E;.07] ^ CLINIC [E;.08] ^ WALK IN/APPT [E;.16] ^ EVALUATION AND MANAGEMENT CODE [E;.17] ^ HOSPITAL LOCATION [E;.22] [] = [I(nternal)/E(xternal); Field #] Subscripts: InvExDt - Inverted Visit Date from "AA" x-ref RecNo - Record Number NOTE: Calling routine is required to delete ^TMP("PXV",$J). It can be deleted between multiple calls to this entry point or after the calling routine makes the last call depending on how the data needs to be accumulated. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15760036 COMPONENT/ENTRY POINT: VISIT(DFN,FROM,RECNO,OCCLIM,CATCODE,PSTAT) SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 1277 IA #: 1277 DATE CREATED: JUN 01, 1995 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RCAMINS NAME: DBIA1277 ID: RCAMINS GENERAL DESCRIPTION: These routine calls are used by Integrated Billing to determine (1) How a user may be allowed to delete an Insurance Company from the INSURANCE COMPANY (#36) file, and (2) To cause the Accounts Receivable module to re-point the debtor (which corresponds to the Insurance Company being deleted) of all applicable AR records to a new debtor. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15780056 COMPONENT/ENTRY POINT: DEL(INS) COMPONENT DESCRIPTION: This call is used to determine whether an insurance company may be outright deleted in Integrated Billing, or whether a second insurance company must be specified in order to merge all billing/receivables information from the company to be deleted into the second company. VARIABLES: INS TYPE: Input VARIABLES DESCRIPTION: This is a pointer to an insurance company in file #36. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: This extrinsic function returns the following values: 0 - Either a valid pointer to file #36 was not passed into the function, or the company is not established as a debtor in Accounts Receivable. 1 - The company is established as a debtor in AR, but there are no receivables where the debtor is the primary payor. 2 - The company is established as a debtor in AR and there are receivables where the debtor is the primary payor. COMPONENT/ENTRY POINT: EN(INS,INS1,INS2,ERROR) COMPONENT DESCRIPTION: This call is used to re-point the debtor for all applicable Accounts Receivable records from the insurance company to be deleted to a second insurance company. VARIABLES: INS TYPE: Input VARIABLES DESCRIPTION: This is a pointer to the insurance company in file #36 which is to be deleted. VARIABLES: INS1 TYPE: Input VARIABLES DESCRIPTION: This is a pointer to the insurance company in file #36 into which all applicable AR records will be merged. VARIABLES: ERROR TYPE: Both VARIABLES DESCRIPTION: This variable is passed into this routine by reference. If the input passed into this entry point is not valid, this variable will contain an error message. Otherwise, the variable is set to null. VARIABLES: INS2 TYPE: Input VARIABLES DESCRIPTION: This variable is a flag which is set to 1 when a second insurance carrier into which the AR data should be merged is NOT specified. The flag indicates that AR should only conduct a search for the insurance carrier being deleted in IB in all the receivables stored in the ACCOUNTS RECEIVABLE (#430) file. Any pointers to this company in the SECONDARY INSURANCE CARRIER (#19) or TERTIARY INSURANCE CARRIER (#19.1) fields of this file should be deleted. COMPONENT/ENTRY POINT: INS2(ROOT,COUNT) COMPONENT DESCRIPTION: This entry point is called by Integrated Billing during a clean-up job which is queued after the user deletes an insurance company. An array containing one or more deleted companies is passed to AR, and a search is conducted through file #430 for all secondary and tertiary insurance carriers which must either be merged or deleted. VARIABLES: ROOT TYPE: Input VARIABLES DESCRIPTION: A global array is passed as input to this entry point. The variable ROOT is a string which is the root of that global array. The array elements themselves are then referenced through indirection. VARIABLES: COUNT TYPE: Both VARIABLES DESCRIPTION: COUNT is passed by reference to this entry point. It is updated each time a secondary or tertiary carrier is updated in file #430. The updated value is passed back to IB and reported to the user. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 1278 IA #: 1278 DATE CREATED: JUN 01, 1995 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBCNSCD1 NAME: DBIA1278 ID: IBCNSCD1 GENERAL DESCRIPTION: The ACCOUNTS RECEIVABLE package will call the entry point BILL in the routine IBCNSCD1 to allow the IB package to merge or delete the Primary Insurance Carrier on corresponding bills in IB. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15783069 COMPONENT/ENTRY POINT: BILL COMPONENT DESCRIPTION: The call will parameter pass as follows: BILL^IBCNSCD1(parameter1,parameter2,parameter3) where parameter1 = the .01 field value in file #399 parameter2 = the internal pointer value in file #36 of the original Primary Carrier on the bill parameter3 = the internal pointer value in file #36 of the Insurance company which will replace the original Primary Insurance Carrier on the bill This may a null value indicating a deletion. VARIABLES: BILL TYPE: Input VARIABLES DESCRIPTION: .01 value in file #399 VARIABLES: INS TYPE: Input VARIABLES DESCRIPTION: internal entry number in file #36 VARIABLES: INS1 TYPE: Input VARIABLES DESCRIPTION: internal entry number in file #36 SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 1279 IA #: 1279 DATE CREATED: JUN 05, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA1279 GENERAL DESCRIPTION: Integrated Billing plans to release the enhancement patch IB*2*28 within 4-6 weeks. We need to update the zeroth node of an entry in the ITEM (#10) multiple in one of our menu protocol (file #101) entries. The easiest way we have found to effect that change is to delete the item from the menu protocol, and have the onits re-add the item, with the new zero node in the multiple, back into the menu protocol. We are formally requesting permission to delete the item which points to the protocol IBCNS QUIT from the menu protocol IBCNSC INSURANCE CO in the post-init of patch IB*2*28. The item would immediately be re-added by invoking the onit right after the deletion. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 15847646 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 1281 IA #: 1281 DATE CREATED: JUN 06, 1995 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOSD1 NAME: DBIA183 - A ID: PSOSD1 GENERAL DESCRIPTION: STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28066833 COMPONENT/ENTRY POINT: DFN COMPONENT DESCRIPTION: This entry point returns a Outpatient Pharmacy Action Profile. VARIABLES: PSONOPG TYPE: Input VARIABLES DESCRIPTION: Variable to indicated that the Action Profiles shouldn't close the device. = "" or 1, indicates that the Action Profiles shouldn't close the device. = 2, indicates that the Action Profiles shouldn't close the device & not to throw a page at the beginning. VARIABLES: PSOPAR TYPE: Input VARIABLES DESCRIPTION: Indicates if Bar codes should be printed with Action Profies. VARIABLES: PSOINST TYPE: Input VARIABLES DESCRIPTION: Variable that contains site name information. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal entry number for the Patient File [Required] VARIABLES: PSDAYS TYPE: Input VARIABLES DESCRIPTION: The number of days which will cut canceled and expired Rx's from the profile. If this variable is not defined, a default of 45 will be used. VARIABLES: PSTYPE TYPE: Input VARIABLES DESCRIPTION: 1 for Action Profile, 0, null, or undefined for Informational SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany NUMBER: 1282 IA #: 1282 FILE NUMBER: 19 GLOBAL ROOT: DIC(19, DATE CREATED: JUN 26, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OPTION FILE ENTRY/EXIT FIELDS ID: DIC(19, GLOBAL REFERENCE: DIC(19,DA,20) FIELD NUMBER: 20 FIELD NAME: ENTRY ACTION LOCATION: 20;E1,245 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: The ENTRY ACTION will be changed to call a supported Generic Code Sheet reference. An example of the change for the option FH GECS CODE EDIT: Before: S GECSSYS="DIETETICS" D EDIT^GECSE1 After : S GECSSYS="DIETETICS" D EDIT^GECSCALL where EDIT^GECSCALL is the supported Generic Code Sheet entry point. GLOBAL REFERENCE: DIC(19,DA,15) FIELD NUMBER: 15 FIELD NAME: EXIT ACTION LOCATION: 15;E1,245 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: The EXIT ACTION will be changed to kill the variable GECSSYS which is set in the ENTRY ACTION of the menu option. GENERAL DESCRIPTION: This integration agreement allows the Generic Code Sheet package version 2.0 to update the OPTION file's (#19) ENTRY and EXIT ACTION fields (#20 and #15) in the routine GECXPOST. The routine GECXPOST is distributed with patch GEC*2*2. The routine GECXPOST will change the ENTRY ACTION field from calling an unsupported Generic Code Sheet entry point to a supported entry point (as defined in integration agreement #1089). It will also change the EXIT ACTION field from null to 'K GECSSYS' where GECSSYS is a supported Generic Code Sheet variable. The options defined as ' GECS*' will have the ENTRY and EXIT ACTION changed. is defined as the namespace as follows: ABSV BLD CHAP DENT DG ESP FB FH GMRC LBRC LR MC NURS PLAY PRCC PRSP PRSP PS RA RMPR SR SOWK VOLU YS STATUS: Active DURATION: Next Version MAIL MESSAGE: 16022876 GOOD ONLY FOR VERSION: 2 SUBSCRIBING PACKAGE: GENERIC CODE SHEET ISC: Washington/Silver Spring NUMBER: 1283 IA #: 1283 DATE CREATED: JUN 28, 1995 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XML NAME: MAILMAN - Access 'as if' a server ID: XML GENERAL DESCRIPTION: Invoking GET^XML with XMCHAN="SERVER" (or any other appropriate channel) sets up the variables available to servers (that channel) invoked during normal delivery. Note that before XMREC is executed, XMZ must be defined; XMER and XMRG are defined by executing XMREC. XMPOS can be changed by the user if appropriate. ========================================================================== Execute variable XMREC to read a line of the message. XMER and XMRG are returned. XMER This variable returns the execution status of XMREC. XMER<0, if there is no more message text to read. The value of XMER will be zero (0), if XMRG is being returned. XMRG, in that case, will have as its value the text of the next line of the message. (Note: which may be null, i.e. a blank line; you cannot test it for being done!) XMRG The value of XMRG will be the next line of message text. XMRG will always be defined, though it will be null when XMER<0. XMPOS This variable contains the current position of the text returned in the variable XMGR. It is initialized if it is undefined and should be killed by the server when it is finished "Reading" the message. Prototype Message Body Reader S XMCHAN="SERVER" GET^XML N A,TEXT ; N MIRROR S A=0 A ; X XMREC ; Receive a line I $D(XMER) G Q:XMER<0 ; Check for end of message S A=A+1 ; Increment local line count S TEXT(A)=XMRG ; Set local array ; S MIRROR(XMPOS)=XMRG ; MIRROR will have the same subscripts ; as the original message G A ; Go back for another line VARIABLES: XMZ Input The internal number of the message to be processed. XMPOS Input The number of the last line read (or null). XMPOS Output The number of the "next" line in the message; if no further lines, XMPOS="" XMER Output 0 unless no lines greater than XMPOS, then -1 XMRG Output line XMPOS of message XMZ STATUS: Active MAIL MESSAGE: 12510326 COMPONENT/ENTRY POINT: GET COMPONENT DESCRIPTION: Invoking GET^XML with XMCHAN="SERVER" sets up the variables available to servers invoked during normal delivery. In particular XMREC is defined and can be used the manner documented fully in DBIA 1151 (and partially above). NUMBER: 1284 IA #: 1284 DATE CREATED: JUL 05, 1995 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMA NAME: INTERACTIVE READ/MANAGE MESSAGES OPTION ID: XMA GENERAL DESCRIPTION: This API lets the user read and manage the messages in his mailbox. STATUS: Active COMPONENT/ENTRY POINT: REC COMPONENT DESCRIPTION: This entry lets the user read and manage the messages in his mailbox. It is the same as the XMREAD option under the XMUSER menu. Compare this to READ^XMXAPIU (DBIA 2774). It may be placed in a menu option as follows: Entry action: S XMMENU(0)= Routine: REC^XMA Exit action: K XMMENU D CHECKOUT^XM VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: User's IEN in the NEW PERSON file. NUMBER: 1296 IA #: 1296 DATE CREATED: AUG 15, 1995 CUSTODIAL PACKAGE: AUTOMATED INFO COLLECTION SYS CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBDF18A NAME: DBIA 1296 GETLST~IBDF18A ID: IBDF18A CREATOR: SHAMUKHAMEDOV,SHAVKAT GENERAL DESCRIPTION: The PCE team requests an agreement to call the following API. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 16842094 COMPONENT/ENTRY POINT: GETLST COMPONENT DESCRIPTION: GETLST^IBDF18A(CLINIC,INTRFACE,ARY,FILTER,COUNT,MODIFIER,ENCDATE) --returns any specified selection list for a clinic --input CLINIC= Pointer to hospital location file for a clinic. INTRFACE= name of selection list in package interface file. Note: the ICD-10 patch IBD*3.0*63 introduces the new additional value "DG SELECT ICD DIAGNOSIS CODES" that can be passed as a parameter, which is introduced to return either ICD-9 or ICD-10 codes depends on the encounter date passed in ENCDATE parameter. This new parameter value works exactly the same as the existing "DG SELECT ICD-9 DIAGNOSIS CODES" item from the package interface file to provide backward compatibility. ARY= name of array to return list in FILTER= predefined filters (optional,defalut=1) 1= must be selection list 2= only visit cpts on list COUNT= number of items already in the ARY MODIFIER= if modifiers are to be passed, 1=yes send modifiers ENCDATE = encounter date --output The format of the returned array is as follows @ARY@(0)=count of array element (0 if nothing found) @ARY@(1)=^group header @ARY@(2) = P1 := cpt or icd code / ien of other items P2 := user defined text P6 := user defined expanded text to send to PCE P7 := second code or item defined for line item P8 := third code or item defined for line item P9 := associated clinical lexicon term @ARY@(2,"MODIFIER",0)=count of CPT Modifiers for entry @ARY@(2,"MODIFIER",1)=2 character CPT Modifier value @ARY@(2,"MODIFIER",2)=2 character CPT Modifier value @ARY@(2,"MODIFIER",k+1)=2 character CPT Modifier value @ARY@(k)=^next group header @ARY@(k+1)=problem ien or cpt or icd code^user defined text Narrative to Send to PCE (instead of printed text) field (2.01) in file 357.3, added as piece 6 of @ARY@(n). If additional codes for an item (diagnosis) are added to item, they are added as pieces 7 and/or 8 of @ARY@(n). If a type of visit code is requested and none found, will automatically look first for blocks named type of visit and second for filtered codes using regular cpt blocks. If a diagnosis block it requested and none found will automatically look for Clinic Common Problem List and then convert it to look like a diagnosis list. SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES DBA Comments: This ICR was deactivated on 4/6/12 by Debbie Trost. The ICR is being changed to support the ICD-10 Class 1 Remediation project. Shavkat Shamukhamedov originally made the request to edit. Thom Holloway indicated the suggested changes to the ICR would not impact PCE. Steve Schmitz has indicated the same for CPRS. Margy McClenahan represents TIU and agrees with the change. Andrey Andriyevskiy indicated Clinical Procedures impact will be included int the ICD-10 Remediation project. Approved on 4/12/12 by Debbie Trost. DATE ACTIVATED: APR 12, 2012 DATE/TIME EDITED: APR 06, 2012@13:17 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: SHAMUKHAMEDOV,SHAVKAT WITH CONCURRENCE OF: SCHMITZ,STEVEN DATE/TIME EDITED: APR 12, 2012@11:21 ACTION: APPROVED AT THE REQUEST OF: SHAMUKHAMEDOV,SHAVKAT WITH CONCURRENCE OF: SCHMITZ,STEVEN NUMBER: 1297 IA #: 1297 FILE NUMBER: 42.5 GLOBAL ROOT: DGWAIT( DATE CREATED: OCT 20, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR conversion needs wait list file ID: DGWAIT( GLOBAL REFERENCE: DGWAIT(C,DFN,DIV,DA GLOBAL DESCRIPTION: Uses C index to loop through WAIT LIST file by patient, division, and IEN GLOBAL REFERENCE: DGWAIT(DIV,P,IEN,ADM) FIELD NUMBER: 13 FIELD NAME: DATE ADMITTED LOCATION: ADM;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Uses DATE ADMITTED field to determine if the patient has already been admitted (patient no longer waiting for admission) GENERAL DESCRIPTION: The OE/RR version 3.0 orders conversion would like permission to loop through the WAIT LIST file to get current/pending waiting list entries. We use this to determine records to convert early in the process. STATUS: Active DURATION: Next Version MAIL MESSAGE: 25302543 GOOD ONLY FOR VERSION: 3.0 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 1298 IA #: 1298 DATE CREATED: AUG 16, 1995 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: PXK VISIT DATA EVENT GENERAL DESCRIPTION: The Scheduling Developers are requesting permission to hook the the protocol named SDAM PCE EVENT to the ITEM multiple of the protocol named PXK VISIT DATA EVENT. This protocol event point was developed to publish data collected by PCE during an encounter via manual data entry or scanned encounter forms. The data represents elements that are stored in the Visit file (9000010) and other PCE V-Files. The data is stored in a ^TMP global array with subscripts denoting the category of published data. An AFTER and BEFORE subscript are included to distinguish changes made to data elements during the encounter session. The data published in the ^TMP global represents data from one encounter. The structure of the ^TMP global that is published is: ^TMP("PXKCO",$J,VISIT,"V FILE STRING",V FILE RECORD,DD SUBSCRIPT, "AFTER/BEFORE")=DATA In cases where there is a CPT modifier, the following structure will be used, this will capture multiple entries for the sub-file. ^TMP("PXKCO",$J,VISIT,"V FILE STRING",V FILE RECORD,DD SUBSCRIPT, "AFTER/BEFORE",DATA)="" Temporary global file root: ^TMP Subscript Piece: 1 Description: String notation representing Package Contents: "PXKCO" Subscript Piece: 2 Description: Job Number Contents: $J Subscript Piece: 3 Description: Internal Entry Number of the Visit (IEN) Contents: Number Subscript Piece: 4 Description: String representing the Visit or V file data category. The "SOR" string refers to the PCE Data Source file (839.7) which is not a V-File. Contents: "CPT" = V CPT (procedure) 9000010.18 "HF" = V Health Factors 9000010.23 "IMM" = V Immunization 9000010.11 "PED" = V Patient Ed 9000010.16 "POV" = V POV (diagnosis) 9000010.07 "PRV" = V Provider 9000010.06 "SK" = V Skin Test 9000010.12 "SOR" = PCE Data Source 839.7 "TRT" = V Treatment 9000010.15 "VST" = Visit file 9000010 "XAM" = V Exam 9000010.13 "CSTP" = Visit file 9000010 This subscript contains child visits used to store additional Stop Codes. Subscript Piece: 5 Description: Internal entry number of the entry in the file represented in subscript #4 Contents: Number Subscript Piece: 6 Description: Subscript or DD node on which the data is stored. Every DD node is published whether or not there is any data for that node. The exception to this is when an entry is deleted from the file, only the 0 node is posted. "ELAP" is the exception. There is no DD subscript in the Visit file that corresponds to this string. "ELAP" represents the patient's eligibility and appointment type for the encounter and has the following structure: ^TMP("PXKCO",$J,VISIT,"VST",VISIT,"ELAP","BEFORE") or ^TMP("PXKCO",$J,VISIT,"VST",VISIT,"ELAP","AFTER") Contents: 0 800 811 or "ELAP" Subscript Piece: 7 Description: String designating whether or not the data is an "AFTER" or "BEFORE" reflection of the data. * If all the "BEFORE"s are blank, then the data represents a new entry. * If a node was edited, the "BEFORE" is the value before it was edited, and the "AFTER" is the value after is was edited. * If the file entry was deleted, only the 0 node is returned; the "AFTER" is blank, and the "BEFORE" is the 0 node as it appeared before it was deleted. Contents: "AFTER" "BEFORE" DATA: The DATA that exists to the right of the global node is a reflection of data as it appears in the global node of the IEN of the file (noted in subscript #5) and the NODE of that IEN (described in subscript #6). Refer to the Data Dictionary for the Visit and V-Files for the format of the data. The data stored on the "ELAP" node is the only exception to this. "ELAP" does not represent a Data Dictionary node and does not have a corresponding DD definition. The data stored on this node has the following structure: ELIG PTR^ELIG TEXT^APPT PTR^APPT TEXT STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 16919410 COMPONENT/ENTRY POINT: PXK VISIT DATA EVENT SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM SUBSCRIBING DETAILS: The subscribing protocol is: - EAS UE PCE EVENT NUMBER: 1299 IA #: 1299 FILE NUMBER: 50 GLOBAL ROOT: PSDRUG( DATE CREATED: MAY 15, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1299 ID: PSDRUG( GLOBAL REFERENCE: PSDRUG(D0,660) FIELD NUMBER: 16 FIELD NAME: PRICE PER DISPENSE UNIT LOCATION: 660;6 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. A direct reference to the Drug file is requested for the Price Per Dispense Unit field so the VA Cost of a drug can be calculated and billed. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 23990432 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 1300 IA #: 1300 DATE CREATED: JUL 19, 2004 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SDCO21 NAME: DBIA1300-A SDCO21 ORIGINAL NUMBER: 1300 ID: SDCO21 GENERAL DESCRIPTION: The Patient Care Encounter Developers would like to request private permission to call the following entry points in routine SDCO21 with the purpose of obtaining outpatient classification requirements. IA #1301 is also associated with this request. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19221909 COMPONENT/ENTRY POINT: CLOE COMPONENT DESCRIPTION: CLOE^SDCO21(SDOE,SDCLOEY) INPUT -- SDOE Outpatient Encounter file IEN. OUTPUT -- SDCLOEY Classification Array Set for Outpatient Encounter Subscripted by Class Type file IEN.Null or 409.42 IEN^ INTERNAL VALUE^1=n/A^=unedt COMPONENT/ENTRY POINT: CL COMPONENT DESCRIPTION: CL~SDCO21(DFN,SDDT,SDOE,SDCLY) INPUT -- DFN Patient IEN SDDT Date/Time SDOE Outpatient Encounter file IEN [optional] OUTPUT -- SDCLY Classification array subscripted by class. Type file (#409.41) IEN. COMPONENT/ENTRY POINT: $$SEQ() COMPONENT DESCRIPTION: Classification Type Sequence by IEN VARIABLES: X TYPE: Output VARIABLES DESCRIPTION: String containing Classification Type Sequence by IEN, "3,7,1,2,4,8,5,6" corresponding to SC,CV,AO,IR,EC,SHAD,MST,HNC. SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City NUMBER: 1301 IA #: 1301 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: AUG 17, 1995 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1300-B PATIENT ORIGINAL NUMBER: 1300 ID: DPT( GLOBAL REFERENCE: DPT(D0,S,D1,0) FIELD NUMBER: .001 FIELD NAME: APPOINTMENT DATE/TIME ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Appointment DATE/TIME FIELD NUMBER: .01 FIELD NAME: CLINIC LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Pointer to the clinic from the Hospital Location file FIELD NUMBER: 21 FIELD NAME: OUTPATIENT ENCOUNTER LOCATION: 0;20 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Pointer to the Outpatient Encounter file (# 409.68) FIELD NUMBER: 3 FIELD NAME: STATUS LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: current status of the patient's appointment FIELD NUMBER: 9 FIELD NAME: PURPOSE OF VISIT LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: reason this patient has this clinic appointment GENERAL DESCRIPTION: Patient Care Encounter would like to request to directly read the following fields in the PATIENT file (# 2). Our goal is to reach the pointer value of the OUTPATIENT ENCOUNTER file (# 409.68) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24820033 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 1302 IA #: 1302 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: OCT 20, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR conversion needs discharges ID: DGPM( GLOBAL REFERENCE: DGPM('AMV3',discharge date,dfn GLOBAL DESCRIPTION: loops through AMV3 x-refs to get discharges by date and by patient. Uses the patient pointer to call OE/RR conversion. GENERAL DESCRIPTION: OE/RR version 3.0 orders conversion would like permission to loop through discharges within 30 days of the OE/RR version 3.0 installation date. This is done to ensure that orders for recently discharged patients are converted early in the process. STATUS: Active DURATION: Next Version MAIL MESSAGE: 25302543 GOOD ONLY FOR VERSION: 3.0 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 1306 IA #: 1306 FILE NUMBER: 9000010.06 GLOBAL ROOT: AUPNVPRV( DATE CREATED: AUG 21, 1995 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: V PROVIDER FILE ORIGINAL NUMBER: 1306 ID: AUPNVPRV( GENERAL DESCRIPTION: The Patient Care Encounter Package requests permission to READ,WRITE,EDIT and DELETE data to and from this file DIRECTLY and with VA FILEMAN. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17001318 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City NUMBER: 1307 IA #: 1307 FILE NUMBER: 9000010.07 GLOBAL ROOT: AUPNVPOV( DATE CREATED: AUG 21, 1995 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: V POV FILE ORIGINAL NUMBER: 1306 ID: AUPNVPOV( GENERAL DESCRIPTION: The Patient Care Encounter Package requests permission to READ,WRITE,EDIT and DELETE data to and from this file DIRECTLY and with VA FILEMAN. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17001330 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City NUMBER: 1308 IA #: 1308 FILE NUMBER: 9000010.11 GLOBAL ROOT: AUPNVIMM( DATE CREATED: AUG 21, 1995 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: V IMMUNIZATION FILE ORIGINAL NUMBER: 1306 ID: AUPNVIMM( GENERAL DESCRIPTION: The Patient Care Encounter Package requests permission to READ,WRITE,EDIT and DELETE data to and from this file DIRECTLY and with VA FILEMAN. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17001354 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City NUMBER: 1309 IA #: 1309 FILE NUMBER: 9000010.12 GLOBAL ROOT: AUPNVSK( DATE CREATED: AUG 21, 1995 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: V SKIN TEST ORIGINAL NUMBER: 1306 ID: AUPNVSK( GENERAL DESCRIPTION: The Patient Care Encounter Package requests permission to READ,WRITE,EDIT and DELETE data to and from this file DIRECTLY and with VA FILEMAN. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17001405 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City NUMBER: 1310 IA #: 1310 FILE NUMBER: 9000010.13 GLOBAL ROOT: AUPNVXAM( DATE CREATED: AUG 21, 1995 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: V EXAM ORIGINAL NUMBER: 1306 ID: AUPNVXAM( GENERAL DESCRIPTION: The Patient Care Encounter Package requests permission to READ,WRITE,EDIT and DELETE data to and from this file DIRECTLY and with VA FILEMAN. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17001415 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City NUMBER: 1311 IA #: 1311 FILE NUMBER: 9000010.15 GLOBAL ROOT: AUPNVTRT( DATE CREATED: AUG 21, 1995 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: V TREATMENT ORIGINAL NUMBER: 1306 ID: AUPNVTRT( GENERAL DESCRIPTION: The Patient Care Encounter Package requests permission to READ,WRITE,EDIT and DELETE data to and from this file DIRECTLY and with VA FILEMAN. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17001434 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City NUMBER: 1312 IA #: 1312 FILE NUMBER: 9000010.16 GLOBAL ROOT: AUPNVPED DATE CREATED: AUG 21, 1995 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: V PATIENT EDUCATION ORIGINAL NUMBER: 1306 ID: AUPNVPED GENERAL DESCRIPTION: The Patient Care Encounter Package requests permission to READ,WRITE,EDIT and DELETE data to and from this file DIRECTLY and with VA FILEMAN. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17001471 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City NUMBER: 1313 IA #: 1313 FILE NUMBER: 9000010.18 GLOBAL ROOT: AUPNVCPT( DATE CREATED: AUG 21, 1995 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: V CPT ORIGINAL NUMBER: 1306 ID: AUPNVCPT( GENERAL DESCRIPTION: The Patient Care Encounter Package requests permission to READ,WRITE,EDIT and DELETE data to and from this file DIRECTLY and with VA FILEMAN. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17001494 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City NUMBER: 1314 IA #: 1314 FILE NUMBER: 9000010.23 GLOBAL ROOT: AUPNVHF DATE CREATED: AUG 21, 1995 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: V HEALTH FACTORS ORIGINAL NUMBER: 1306 ID: AUPNVHF GENERAL DESCRIPTION: The Patient Care Encounter Package requests permission to READ,WRITE,EDIT and DELETE data to and from this file DIRECTLY and with VA FILEMAN. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17001518 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City NUMBER: 1315 IA #: 1315 DATE CREATED: AUG 21, 1995 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: IHS FILES GENERAL DESCRIPTION: The Patient Care Encounter Package requests a DBIA to distribute the following Indian Health Service files in the VA. ---Visit Related Files-- V PROVIDER 9000010.06 AUPNVPRV( V POV 9000010.07 AUPNVPOV( V IMMUNIZATION 9000010.11 AUPNVIMM( V SKIN TEST 9000010.12 AUPNVSK( V EXAM 9000010.13 AUPNVXAM( V TREATMENT 9000010.15 AUPNVTRT( V PATIENT EDUCATION 9000010.16 AUPNVPED( V CPT 9000010.18 AUPNVCPT( V HEALTH FACTORS 9000010.23 AUPNVHF( ---Supporting files EDUCATION TOPIC 9999999.09 AUTTEDT( IMMUNIZATION 9999999.14 AUTTIMM( EXAM 9999999.15 AUTTXAM( TREATMENT 9999999.17 AUTTTRT( SKIN TEST 9999999.28 AUTTSK( HEALTH FACTORS 9999999.64 AUTTHF( STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17001538 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany NUMBER: 1320 IA #: 1320 DATE CREATED: JAN 08, 2004 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: SDAM APPOINTMENT EVENTS GLOBAL REFERENCE: TMP('SDEVT',$J, GLOBAL DESCRIPTION: ^TMP("SDEVT",$J,SDHDL,SDPROC,"SDOE",SDOE,0,"AFTER") = Zero node of encounter after change SDHDL = Handle (can get more than one at a time) SDPROC = Originating process 1 = Appointment 2 = Add/Edit 3 = Disposition 4 = Credit Stop (ignore these) SDOE = Pointer to encounter GENERAL DESCRIPTION: This is the event that is invoked when an action is taken upon an appointment, such as check in. ^TMP("SDEVT",$J,SDHDL,SDPROC,"SDOE",SDOE,0,"AFTER") = Zero node of encounter after change SDHDL = Handle (can get more than one at a time) SDPROC = Originating process 1 = Appointment 2 = Add/Edit 3 = Disposition 4 = Credit Stop (ignore these) SDOE = Pointer to encounter STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 16919375 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City SUBSCRIBING DETAILS: The subscribing protocol is: PXK SDAM TO V-FILES SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING DETAILS: The subscribing protocol is: IBACM OP LINK SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: The subscribing protocol is: ORU PATIENT MOVMT SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING DETAILS: The subscribing protocols are: - DG MEANS TEST REQUIRED - VAFED EDR OUTPATIENT CAPTURE - DGEN PATIENT ENROLLMENT - DGEN ENROLLED VETERANS REPORT SUBSCRIBING PACKAGE: PROSTHETICS ISC: Salt Lake City SUBSCRIBING DETAILS: The subscribing protocol is: RMPR SCH EVENT SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING DETAILS: The subscribing protocol is: RG ADT OUTPATIENT ENCOUNTER DRIVER SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM SUBSCRIBING DETAILS: The subscribing protocol is: - EAS UE SCHED EVENT SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: The subscribing Protocol is: SDAM APPOINTMENT EVENTS Added 10/23/2006 at the request of Zach Fain/Scheduling and Peter Kuzmak/Imaging. SUBSCRIBING PACKAGE: SURGERY SUBSCRIBING DETAILS: 7/10/12-Surgery protocol is SRQ APPOINTMENT EVENT SUBSCRIBER distributed in SR*3.0*180. SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: VPR*1*3 patch will be adding the capability to keep the VPR data cache up-to-date, so this ICR is for subscribing to SDAM APPOINTMENT EVENTS protocol events with listener VPR APPT EVENTS. SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING DETAILS: Added BCE 10/9/14. The Bar Code Enhancement - Transfusion Verification project, new package MJCF*1.0.KID (no patch) will hang MJCF OUTPATIENT EVENT MONITOR on the SDAM APPPOINTMENT EVENTS protocol in order to receive information as to when a patient is admitted (checked-in) to a clinic. This is necessary to insure that people receiving blood transfusions are an admitted patient for the Positive Patient identification project. DBA Comments: JSH/10-23-2006 Modified to add Imaging as a subscriber as per Outlook email between Fain and Kuzmak. MM/7-10-12: Surgery added as subscriber. Surgery protocol is SRQ APPOINTMENT EVENT SUBSCRIBER and will be distributed in SR*3.0*180 scheduled for field testing in September 2012. Filter logic in the SQWM software will determine if the clinic associated with the appointment event is a surgical clinic from the Primary Stop Code of the clinic. If the clinic is a SQWM clinic the VistA SQWM software will create and transmit an HL7 Schedule Information Unsolicited (SIU) message to the SQWM Information Gateway where it is directed to the associated SQWM Install Group. Message types generated will be SIU-S12, SIU-S14, and SIU-S15 based on the scheduling event. Request reviewed by Angela Saunders, Connie Ray, Bob Yorty and Darryl Reese. DT/10-9-14: VPR added as subscriber. VPR*1*3 patch will be adding the capability to keep the VPR data cache up-to-date, so this ICR is for subscribing to SDAM APPOINTMENT EVENTS protocol events with listener VPR APPT EVENTS. Note: Mary sent a message to Melanie addressing the lack of a custodian package reviewer and making sure Melanie knew the technical correctness is Melanie's responsibility. She concurred. DT/10-9-14 continued: BCE added as subscriber. MJCF*1.0.KID (no patch- new package) will be distributed for Bar Code Enhancement - Transfusion Verification project. Vaughn was sent the message about no Custodian Reviewers available and making sure Vaughn knew the technical correctness is Vaughn's responsibility. He concurred. DATE/TIME EDITED: OCT 23, 2006@10:40 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: KUSZMAK,PETER WITH CONCURRENCE OF: SHOVESTUL,MARYANN DATE/TIME EDITED: JUL 10, 2012@09:42 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: TOMLIN,BRIAN WITH CONCURRENCE OF: SAUNDERS,ANGELA DATE/TIME EDITED: OCT 09, 2014@11:49 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: ICR,TEAM DATE/TIME EDITED: OCT 09, 2014@12:10 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SMITH,VAUGHN WITH CONCURRENCE OF: ICR,TEAM NUMBER: 1324 IA #: 1324 FILE NUMBER: 2005 GLOBAL ROOT: MAG(2005 DATE CREATED: AUG 25, 1995 CUSTODIAL PACKAGE: IMAGING CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1324-A ORIGINAL NUMBER: 1324 ID: MAG(2005 GLOBAL REFERENCE: MAG(2005,0) GLOBAL DESCRIPTION: The Radiology/Nuclear Medicine package performs the following test to determine if the Image File #2005 is populated: I $O(^MAG(2005,0)) GENERAL DESCRIPTION: 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. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17103916 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 1325 IA #: 1325 FILE NUMBER: 2005 GLOBAL ROOT: MAG(2006.1 DATE CREATED: AUG 25, 1995 CUSTODIAL PACKAGE: IMAGING CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1324-B ID: MAG(2006.1 GLOBAL REFERENCE: MAG(2006.1,AXSCN) GLOBAL DESCRIPTION: The global node ^MAG(2006.1,"AXSCN") is present if images are scanned before reports are entered. GENERAL DESCRIPTION: 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. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17103916 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 1326 IA #: 1326 DATE CREATED: AUG 25, 1995 CUSTODIAL PACKAGE: IMAGING CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MAGSET3 NAME: DBIA1324-C ID: MAGSET3 GENERAL DESCRIPTION: This DBIA documents a line label reference within the Radiology/Nuclear Medicine package to a routine in the Imaging package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17103916 COMPONENT/ENTRY POINT: MED COMPONENT DESCRIPTION: This routine is called to set the mode on the workstation screen used to display abstracts and images during case and report look-up within the Radiology package. COMPONENT/ENTRY POINT: ERASE COMPONENT DESCRIPTION: This routine call erases the imaging workstation screen in preparation for displaying an abstract or report during case or report lookup through the Radiology/Nuclear Medicine Package. SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 1327 IA #: 1327 DATE CREATED: SEP 19, 1995 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBTRV NAME: DBIA1327 ID: IBTRV GENERAL DESCRIPTION: The IBQ Package requests use of the function $$VNDT^IBTRV to extract Review date. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17534172 COMPONENT/ENTRY POINT: $$VNDT COMPONENT DESCRIPTION: Called to retrieve inpatient information. VARIABLES: IBTRV TYPE: Input VARIABLES DESCRIPTION: Is the IEN for the entry in the HOSPITAL REVIEW File (#356.1) for which the data is to be extracted. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Y is the date of Review from the HOSPITAL REVIEW File (#356.1). SUBSCRIBING PACKAGE: UTILIZATION MANAGEMENT ROLLUP ISC: Albany NUMBER: 1328 IA #: 1328 DATE CREATED: AUG 25, 1995 CUSTODIAL PACKAGE: IMAGING CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MAGRIC NAME: DBIA1324-E ID: MAGRIC GENERAL DESCRIPTION: This DBIA documents a Radiology/Nuclear Medicine package reference to a line label within the Imaging package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17103916 COMPONENT/ENTRY POINT: DISPA COMPONENT DESCRIPTION: This routine is called from the Radiology/Nuclear Med package during case nubmer look-up and report look-up to display the associated abstract or image(s) for the exam. VARIABLES: RARPT TYPE: Input VARIABLES DESCRIPTION: Report IEN in File #73, Rad/Nuc Med Reports. COMPONENT/ENTRY POINT: DISPF COMPONENT DESCRIPTION: This entry is called during Radiology/Nuclear Medicine report printing to display thge image(s) associated with the report. VARIABLES: RARPT TYPE: Input VARIABLES DESCRIPTION: IEN of the Rad/Nuc Med Reports file #74. SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 1329 IA #: 1329 DATE CREATED: SEP 19, 1995 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA1329 GENERAL DESCRIPTION: The IBQ package requests permission to perform the following actions during the initialization of IBQ 1.0. 1. Export the following fields/files: a. Claims Tracking File (#356) - add new field (#1.09) ACUTE CARE DISCHARGE DATE and add new cross-reference 'ADIS'. b. Hospital Review File (#356.1) - add trigger to existing field (#1.17) ACUTE CARE DISCHARGE DATE to update field (#1.09) ACUTE CARE DISCHARGE DATE of File (#356). 2. Post init call ENALL^DIK to index existing entries of field (#1.17) ACUTE CARE DISCHARGE DATE of File (#356.1). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17536647 SUBSCRIBING PACKAGE: UTILIZATION MANAGEMENT ROLLUP ISC: Albany NUMBER: 1332 IA #: 1332 FILE NUMBER: 200 GLOBAL ROOT: VA(200 DATE CREATED: AUG 31, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Rad/Nuc Med flds in File 200 ID: VA(200 GLOBAL REFERENCE: All 70-series fields FIELD NUMBER: 70 FIELD NAME: STAFF REVIEW REQUIRED LOCATION: RA;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Used to determine whether an interpreting physician can verify reports along, or if staff review is required. FIELD NUMBER: 71 FIELD NAME: ALLOW VERIFYING OF OTHERS LOCATION: RA;2 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Used to determine if an interpreting physician has the privilege of verifying reports written by another interpreting physician. FIELD NUMBER: 72 FIELD NAME: CLASSIFICATION LOCATION: RAC;0 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Used to determine if the user is a valid Rad/Nuc Med tech, interpreting physician, interpreting resident, or clerk. FIELD NUMBER: 73 FIELD NAME: RADIOLOGY INACTIVE DATE LOCATION: RA;3 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Used to determine if a Rad/Nuc Med user has been inactivated. This is necessary to shut out various users from being selected as techs, residents, or staff during case and report entry. FIELD NUMBER: 74 FIELD NAME: RAD/NUC MED LOCATION ACCESS LOCATION: RAL;0 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This is a multiple field used to determine which imaging locations within the facility may be accessed by the user. This is used to screen data so that the user only sees the data relevant to the imaging areas in which s/he works. This field is new with version 4.5. GLOBAL DESCRIPTION: These fields reside in the New Person File #200. The Radiology/Nuclear Medicine reads and writes these fields using FileMan callable routines. There are direct global reads of the cross-references on these fields. There are also some direct global reads of the fields themselves. GENERAL DESCRIPTION: This DBIA documents the fields in File 200 that are created by the Radiology/Nuclear Medicine package developers, and are used specifically by the Radiology/Nuclear Medicine package. These fields are to be distributed in a patch by the Kernel developers. The patch will be prepared by the Radiology/Nuclear Medicine developers and will contain an environment check to make sure Version 4.5 of Radiology/Nuclear Medicine is installed before installing these fields on file 200. These fields will also be distributed along with Radiology/Nuclear Medicine 4.5. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 1333 IA #: 1333 DATE CREATED: SEP 07, 1995 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA1333 GENERAL DESCRIPTION: Dietetics V5.0 will include Allergy Tracking Systems option Enter/Edit Patient Reaction Data on Diet Order Management menu. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17287010 COMPONENT/ENTRY POINT: OPTION GMRA PATIENT A/AR EDIT COMPONENT DESCRIPTION: Enter/Edit Patient Reaction Data menu option. SUBSCRIBING PACKAGE: DIETETICS ISC: Hines NUMBER: 1336 IA #: 1336 DATE CREATED: SEP 12, 1995 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSORX NAME: DBIA1030-C ID: PSORX GENERAL DESCRIPTION: This entry point is used to build an Outpatient prescription profile for a patient. This profile is in the form of an array, names PSOSD. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18024934 COMPONENT/ENTRY POINT: PROFILE VARIABLES: PSODFN TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number of the patient. This variable will be unchanged in this component. VARIABLES: PSOSD TYPE: Output VARIABLES DESCRIPTION: This is an array which contains the patients current prescriptions. The variable PSOSD is equal to the number of prescriptions in the list, or it will be equal to null or undefined if there are no prescriptions in the list. The pieces in the array are described after the following example. PSOSD=3 PSOSD("ACTIVE","AMITRIPTYLINE HCL 10MG TAB")=2001317^0^^^CN601^11^132A2^30 PSOSD("ACTIVE","CYTARABINE 100MG INJ")=2001313^0^^^AN300^11^402A1^30 PSOSD("SUSPENDED","EPINEPHRINE 1:1000 INJ VIAL")=2001318^5^^Z^AU100^11^361A1^30 Piece 1) Internal prescription number from the Prescription File (#52) Piece 2) The status of the prescripion from the Status field of the Prescription File (#52) Piece 3) Free text set of characters used for different classifications of the drug (not applicable to the functions of this agreement) Piece 4) Free text set of characters used to identify site parameters and drug characteristics. Piece 5) The VA Classification of the drug Piece 6) The number of refills remaining for the prescription Piece 7) National Drug File information for the drug, in the form of: National Drug File entry_"A"_VA Product Name entry (This piece will be null if the drug is not matched to an entry in the National Drug File) Piece 8) The days supply of the prescription SUBSCRIBING PACKAGE: VENDOR - AUDIOFAX, INC. SUBSCRIBING PACKAGE: VENDOR - TECHPRO SYSTEMS INC NUMBER: 1337 IA #: 1337 FILE NUMBER: 42.4 GLOBAL ROOT: DIC(42.4, DATE CREATED: SEP 12, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1337 ID: DIC(42.4, GLOBAL REFERENCE: DIC(42.4,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The NAME field contents are displayed during radiology exam registration under the caption 'Bedsection:' FIELD NUMBER: 6 FIELD NAME: CDR ACCOUNT LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The contents of the CDR ACCOUNT field are displayed on the Radiology Cost Distribution Report. FIELD NUMBER: 3 FIELD NAME: SERVICE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the name of the service that this specialty is related to. GLOBAL DESCRIPTION: This file contains recognized PTF treating specialties. GENERAL DESCRIPTION: This DBIA documents Radiology/Nuclear Medicine package references to the Specialty file #42.4. Rad/Nuc Med contains a field that points to file 42.4, and there are global reads on the zeroeth node. Direct read of the 'B' Cross Reference is also permitted. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25455770 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: QUASAR ISC: Birmingham SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany SUBSCRIBING DETAILS: DSS EXTRACTS reads only the NAME field (#.01) and the SERVICE field (#3) using FileMan (EN^DIQ1). EDITOR: PAJERSKI,JAN NUMBER: 1338 IA #: 1338 DATE CREATED: SEP 12, 1995 CUSTODIAL PACKAGE: IMAGING CUSTODIAL ISC: Washington USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA1338 GENERAL DESCRIPTION: 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. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 1339 IA #: 1339 FILE NUMBER: 772 GLOBAL ROOT: HL(772, DATE CREATED: SEP 13, 1995 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1339 ID: HL(772, GLOBAL REFERENCE: HL(772,B,date_time) FIELD NUMBER: .01 FIELD NAME: DATE/TIME ENTERED ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Radiology/Nuclear Medicine is checking for the existence of a given date/time in the "B" cross-reference of this file. This cross-reference is on the .01 field. Only the "B" cross-ref is accessed. GENERAL DESCRIPTION: This DBIA documents a Radiology/Nuclear Medicine package reference to the HL7 package file #772. This is only applicable when Health Level Seven Version 1.5 is the version currently installed at a site. STATUS: Active DURATION: Next Version MAIL MESSAGE: 17383258 GOOD ONLY FOR VERSION: 1.5 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 1340 IA #: 1340 FILE NUMBER: 19.1 GLOBAL ROOT: DIC(19.1, DATE CREATED: SEP 14, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1340 ID: DIC(19.1, GLOBAL REFERENCE: DIC(19.1,ifn,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: The .01 NAME field contains the security key name. GENERAL DESCRIPTION: The Security Key file (#19.1) Name field (.01) can be pointed to. Standard utilities should be used for look-up. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17388660 NUMBER: 1341 IA #: 1341 DATE CREATED: SEP 19, 1995 CUSTODIAL PACKAGE: ENGINEERING CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ENWONEW2 NAME: DBIA1341-A ORIGINAL NUMBER: 1341 ID: ENWONEW2 GENERAL DESCRIPTION: Version 1.0 of the Non-Expendable Equipment/Turn-In Request Module will call the Engineering Work Order Module in order to create a work order for equipment that must be disconnected before final turn-in can occur. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20126797 COMPONENT/ENTRY POINT: TRNIN VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: Person requesting the work order. VARIABLES: WODATA TYPE: Input VARIABLES DESCRIPTION: The equipment ID and location of the requested item to be turned in. data (2 pieces delimited by '^') piece 1 = equipment ID piece 2 = (optional) location of the item to be turned in VARIABLES: PRCNSRV TYPE: Input VARIABLES DESCRIPTION: The service that entered the turn-in request. (optional pointer value from Service file) VARIABLES: ENDA TYPE: Output VARIABLES DESCRIPTION: The internal number of the work order. VARIABLES: ENWO TYPE: Output VARIABLES DESCRIPTION: Work Order number. SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1342 IA #: 1342 FILE NUMBER: 6914 GLOBAL ROOT: ENG(6914 DATE CREATED: SEP 19, 1995 CUSTODIAL PACKAGE: ENGINEERING CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1341-B ORIGINAL NUMBER: 1341 ID: ENG(6914 GLOBAL REFERENCE: ENG(6914,D0,0) FIELD NUMBER: .01 FIELD NAME: ENTRY NUMBER LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: This is an entry in the Equipment Inventory file that is being requested either to be turned in or replaced. FIELD NUMBER: 3 FIELD NAME: MFGR. EQUIPMENT NAME LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is a brief narrative description of item in file. GLOBAL REFERENCE: ENG(6914,D0,1) FIELD NUMBER: 1 FIELD NAME: MANUFACTURER LOCATION: 1;4 ACCESS: Read w/Fileman FIELD DESCRIPTION: Firm who manufactured item, not necessary from whom it was purchased. FIELD NUMBER: 4 FIELD NAME: MODEL LOCATION: 1;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: Model number normally assigned by manufacturer. FIELD NUMBER: 5 FIELD NAME: SERIAL # LOCATION: 1;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: Serial number assigned by manufacturer. GLOBAL REFERENCE: ENG(6914,D0,2) FIELD NUMBER: 12 FIELD NAME: TOTAL ASSET VALUE LOCATION: 2;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: Cost of the item at the time of purchase. FIELD NUMBER: 18 FIELD NAME: CATEGORY STOCK NUMBER LOCATION: 2;8 ACCESS: Read w/Fileman FIELD DESCRIPTION: The designated category stock number of a item. FIELD NUMBER: 19 FIELD NAME: CMR LOCATION: 2;9 ACCESS: Read w/Fileman FIELD DESCRIPTION: The Consolidated Memorandum of Receipt for this item's accountability. GLOBAL REFERENCE: ENG(6914,D0,3) FIELD NUMBER: 20 FIELD NAME: USE STATUS LOCATION: 3;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Tells user is item is currently in active use. FIELD NUMBER: 20.1 FIELD NAME: ACQUISITION METHOD LOCATION: 3;4 ACCESS: Read w/Fileman FIELD DESCRIPTION: Establishes whether the facility owns the item. FIELD NUMBER: 20.5 FIELD NAME: TURN-IN DATE LOCATION: 3;3 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Date on which item is turned over to A&MM for disposition. It should then be removed from the using service CMR. FIELD NUMBER: 22 FIELD NAME: DISPOSITION DATE LOCATION: 3;11 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Date on which item is physically disposed of by Materiel Management. Should be removed from asset account. FIELD NUMBER: 24 FIELD NAME: LOCATION LOCATION: 3;5 ACCESS: Read w/Fileman FIELD DESCRIPTION: Physical location of this item at the facility. FIELD NUMBER: 31 FIELD NAME: DISPOSITION METHOD LOCATION: 3;12 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Means by which Materiel Management disposed of item that has been 'turned in'. FIELD NUMBER: 32 FIELD NAME: DISPOSITION VALUE LOCATION: 3;13 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Monetary value of item turned in. GLOBAL REFERENCE: ENG(6914,D0,6,D1,0) FIELD NUMBER: 4 FIELD NAME: LABOR $ LOCATION: 0;5 ACCESS: Read w/Fileman FIELD DESCRIPTION: Amount of labor money spent on repairs of item. FIELD NUMBER: 5 FIELD NAME: MATERIAL $ LOCATION: 0;6 ACCESS: Read w/Fileman FIELD DESCRIPTION: Amount of material money spent on repairs of item. FIELD NUMBER: 6 FIELD NAME: VENDOR $ LOCATION: 0;7 ACCESS: Read w/Fileman FIELD DESCRIPTION: Amount of vendor money spent on repairs of item. GLOBAL REFERENCE: ENG(6914,D0,8) FIELD NUMBER: 38 FIELD NAME: STANDARD GENERAL LEDGER LOCATION: 8;6 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: The General Ledger Account appropriate to the non-expendable item. May be affected when item is 'turned in'. GLOBAL REFERENCE: ENG(6914,D0,9) FIELD NUMBER: 60 FIELD NAME: STATION NUMBER LOCATION: 9;5 ACCESS: Read w/Fileman FIELD DESCRIPTION: Station number of the facility that owns the item. GENERAL DESCRIPTION: The Non-expendable Equipment/Turn-In Request Module requests permission to point to file 6914. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20126809 SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1343 IA #: 1343 FILE NUMBER: 6914.1 GLOBAL ROOT: ENG(6914.1 DATE CREATED: SEP 19, 1995 CUSTODIAL PACKAGE: ENGINEERING CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1341-C ORIGINAL NUMBER: 1341 ID: ENG(6914.1 GLOBAL REFERENCE: ENG(6914.1,D0,0) FIELD NUMBER: .5 FIELD NAME: SERVICE LOCATION: 0;5 ACCESS: Read w/Fileman FIELD DESCRIPTION: Service to which the CMR is assigned FIELD NUMBER: 1 FIELD NAME: RESPONSIBLE OFFICIAL LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field is the CMR who is currently responsible for the equipment to be turned in. FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: CMR name FIELD NUMBER: 5 FIELD NAME: STATION NUMBER LOCATION: 0;7 ACCESS: Read w/Fileman FIELD DESCRIPTION: Station number of facility that owns the asset in the CMR. FIELD NUMBER: 2 FIELD NAME: PHONE (RESP OFFICIAL) LOCATION: 0;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: Phone number of the responsible official. GLOBAL REFERENCE: ENG(6914.1,D0,20) FIELD NUMBER: 20 FIELD NAME: ALTERNATE RESPONSIBLE OFFICIAL LOCATION: 20;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Person authorized to act as a surrogate for the CMR Responsible Official. GENERAL DESCRIPTION: The Non-expendable Equipment/Turn-in Request Module requests permission to point the CMR file, 6914.1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20126819 SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1344 IA #: 1344 FILE NUMBER: 6920 GLOBAL ROOT: ENG(6920 DATE CREATED: MAR 21, 1996 CUSTODIAL PACKAGE: ENGINEERING CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1341-D ORIGINAL NUMBER: 1341 ID: ENG(6920 GLOBAL REFERENCE: ENG(6920,D0,0) FIELD NUMBER: .01 FIELD NAME: WORK ORDER # LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: The work order number for the Engineering department for items that are being turned in. GLOBAL DESCRIPTION: Equipment/Turn-In Request packages checks for each WORK ORDER # generated for a item to be turned in, if the status is COMPLETED. GLOBAL REFERENCE: ENG(6920,D0,5) FIELD NUMBER: 36 FIELD NAME: DATE COMPLETE (or closed) LOCATION: 5;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: Date that work order was completed. GENERAL DESCRIPTION: This reference is to the WORK ORDER # file in Engineering for items which must have a work order created in order to remove or disconnect the item by the Engineering department. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20126831 SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1345 IA #: 1345 FILE NUMBER: 6910 GLOBAL ROOT: DIC(6910 DATE CREATED: SEP 21, 1995 CUSTODIAL PACKAGE: ENGINEERING CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1341-E ORIGINAL NUMBER: 1341 ID: DIC(6910 GLOBAL REFERENCE: DIC(6910,D0,20) FIELD NUMBER: 20 FIELD NAME: EQUIPMENT TURN-IN SECTION LOCATION: 20;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the appropriate work order section for equipment turn-ins when a work order should be generated. GLOBAL REFERENCE: DIC(6910,D0,0) FIELD NUMBER: 1 FIELD NAME: STATION NUMBER LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: Facility identifier GENERAL DESCRIPTION: The ENG INIT PARAMETERS file is checked for the entry of the EQUIPMENT TURN-IN SECTION field. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20126838 SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1346 IA #: 1346 DATE CREATED: MAR 21, 1996 CUSTODIAL PACKAGE: ENGINEERING CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ENFAUTL NAME: DBIA1341-F ORIGINAL NUMBER: 1341 ID: ENFAUTL GENERAL DESCRIPTION: FMS requires FA code sheets on capitalized equipment and FD code sheets when dispositioned. Turn-In items must be sure that the appropriate FA and FD code sheets have been done before finalizing the turn-in. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20126846 COMPONENT/ENTRY POINT: $$CHKFA COMPONENT DESCRIPTION: Checks to see if item has been capitalized or not. VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: The internal number of the equipment item from 6914. VARIABLES: (returns) TYPE: Output VARIABLES DESCRIPTION: Returns output data from function (4 pieces delimited by '^'): Piece 1 = flag (0 or 1) which indicates if equipment item if currently established in Fixed Assets 1 = if currently established 0 = if not currently established. Piece 2 = the date/time of last FA Doc. for item Piece 3 = the date/time of last FD Doc. for item Piece 4 = the IEN of last FA Doc. for item SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1348 IA #: 1348 FILE NUMBER: 6925 GLOBAL ROOT: ENG('PROJ', DATE CREATED: APR 04, 1996 CUSTODIAL PACKAGE: ENGINEERING CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1341-H ORIGINAL NUMBER: 1341 ID: ENG('PROJ', GLOBAL REFERENCE: ENG('PROJ',D0,0) FIELD NUMBER: .01 FIELD NAME: PROJECT NUMBER LOCATION: 6925 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Displays list of possible project numbers when user enters '?'. FIELD NUMBER: 2 FIELD NAME: PROJECT TITLE LOCATION: 6925 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Displays with list of possible project numbers when user enters '?'. GLOBAL DESCRIPTION: Is for display only, special help. GLOBAL REFERENCE: ENG('PROJ',D0,33) FIELD NUMBER: 245 FIELD NAME: CHIEF ENGINEER NAME LOCATION: 6925 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: If user enters a project number which currently exists in the fiel 6925, then the Chief Engineer Name will be directly read but then Write w/FileMan into file 413. GLOBAL DESCRIPTION: Display only but can pull Chief Engineer over into 413 from 6925. GENERAL DESCRIPTION: The Equipment/Turn-In module asks permission to display projects, their description and to pull the Chief Engineer Name if exists for inclusion in Equipment Request if necessary. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20126858 SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1349 IA #: 1349 FILE NUMBER: 6928 GLOBAL ROOT: ENG('SP', DATE CREATED: APR 04, 1996 CUSTODIAL PACKAGE: ENGINEERING CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1341-I ORIGINAL NUMBER: 1341 ID: ENG('SP', GLOBAL REFERENCE: ENG('SP',D0,0) FIELD NUMBER: .01 FIELD NAME: ROOM NUMBER LOCATION: 6928 ACCESS: Pointed to FIELD DESCRIPTION: Points to the location file if user enters location that currently exists, otherwise will place free text location entered in another field. Also, program PRCNUTL1 contains a 'special help' list if user enters a '?' which is a direct global read. GLOBAL DESCRIPTION: This field is to ensure that sufficient space and location exists for purchase of additional equipment. GENERAL DESCRIPTION: Equipment/Turn-In module asks permission to access the Location file (#6928) to identify where new equipment may be located and where equipment will need to be picked up from when being turned in. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20126874 SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1351 IA #: 1351 FILE NUMBER: 356.1 GLOBAL ROOT: IBT(356.1 DATE CREATED: SEP 21, 1995 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1351 ID: IBT(356.1 GLOBAL REFERENCE: IBT(356.1,'C',IBTRN, FIELD NUMBER: .03 FIELD NAME: DAY OF REVIEW LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used for the Day of Review in the IBQ package. FIELD NUMBER: .04 FIELD NAME: SEVERITY OF ILLNESS LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used for Severity of Illness in the IBQ package. FIELD NUMBER: .05 FIELD NAME: INTENSITY OF SERVICE LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used for Intensity of Service in the IBQ package. FIELD NUMBER: .06 FIELD NAME: CRITERIA MET IN 24 HOURS? LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used for Acute Admission(Y/N)? in the IBQ package. FIELD NUMBER: .07 FIELD NAME: SPECIALTY FOR REVIEWS LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field will be used to retrieve a pointer to the FACILITY TREATING SPECIALTY (#45.7) file, which will in turn be used to determine the Service from the SPECIALTY (#42.4) file. FIELD NUMBER: .08 FIELD NAME: SPECIALIZED UNIT SI LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used for Severity of Illness in the IBQ package. FIELD NUMBER: .09 FIELD NAME: SPECIALIZED UNIT IS LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used for Intensity of Service in the IBQ package. FIELD NUMBER: .1 FIELD NAME: PROVIDER INTERVIEWED? LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used for Provider Interviewed(Y/N) in the IBQ package. FIELD NUMBER: .11 FIELD NAME: ADMISSION DECISION INFLUENCED LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used for Admission Influenced(Y/N) in the IBQ package. FIELD NUMBER: .12 FIELD NAME: D/C SCREEN MET LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used for D/C From Continued Stay in the IBQ package. FIELD NUMBER: .19 FIELD NAME: ACTIVE LOCATION: 0;19 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to check the validity of a review. FIELD NUMBER: .21 FIELD NAME: REVIEW STATUS LOCATION: 0;21 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to check the validity of a review. FIELD NUMBER: 356.112,.01 FIELD NAME: REASONS FOR NON-ACUTE ADMISSION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This multiple field of reason codes is used for Reasons for Non-Acute Admission in the IBQ package. FIELD NUMBER: 356.113,.01 FIELD NAME: REASONS FOR NON-ACUTE DAYS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This multiple field of reason codes is used for Reasons from Continued Stay in the IBQ package. GLOBAL DESCRIPTION: The 'C' x-ref is used to retrieve information on the days of review, given it's parent Claims Tracking number. GENERAL DESCRIPTION: The IBQ package needs to retrieve Hospital Review information out of the HOSPITAL REVIEW File (#356.1) for use in the rollup to the National Database. The 'C' x-ref is used for the gathering of review information, given the Claims Tracking entry number from the Claims Tracking File (#356). Refer to IA-1350 for the Claims Tracking IEN that is retrieved from the 'ADIS' x-ref. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17584198 SUBSCRIBING PACKAGE: UTILIZATION MANAGEMENT ROLLUP ISC: Albany NUMBER: 1353 IA #: 1353 FILE NUMBER: .402 GLOBAL ROOT: DIE( DATE CREATED: SEP 21, 1995 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1353 ID: DIE( GENERAL DESCRIPTION: This DBIA documents a Radiology/Nuclear Medicine package look-up on FileMan's Edit template file. The look-up is done within an IRM option so that IRM can select one, many, or all Radiology/ Nuclear Med compiled templates for re-compiling. The look-up must be done through a Radiology program which calls DIC in order to provide the "one-many-all" look-up functionality. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17385063 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 1354 IA #: 1354 FILE NUMBER: 356.9 GLOBAL ROOT: IBT(356.9 DATE CREATED: SEP 21, 1995 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1354 ID: IBT(356.9 GLOBAL REFERENCE: IBT(356.9,'ADG',DGPM, FIELD NUMBER: .01 FIELD NAME: DIAGNOSIS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field will return the diagnosis reference which will return the Diagnosis Code from the ICD 9 File for use in the IBQ Package. GLOBAL DESCRIPTION: The 'ADG' x-ref is used to return the patients diagnosis. GENERAL DESCRIPTION: The IBQ package needs to retrieve diagnosis data related to the patient's admission. The 'ADG' x-ref in the INPATIENT DIAGNOSIS File (#356.9) is used to return the patient's diagnosis, given the PATIENT MOVEMENT number. The PATINT MOVEMENT number retrieved in IA-1350 from ADMISSION in the Claims Tracking File (#356). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17584198 SUBSCRIBING PACKAGE: UTILIZATION MANAGEMENT ROLLUP ISC: Albany NUMBER: 1355 IA #: 1355 FILE NUMBER: .4 GLOBAL ROOT: DIPT( DATE CREATED: SEP 21, 1995 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1355 ID: DIPT( GENERAL DESCRIPTION: This DBIA documents a Radiology/Nuclear Medicine package look-up on FileMan's Print template file. The look-up is done within an IRM option so that IRM can select one, many, or all Radiology/Nuclear Med compiled tempaltes for re-compiling. the look-up must be done through a Radiology program which calls DIC in order to provide the "one-many-all" look-up functionality. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17385063 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 1358 IA #: 1358 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: SEP 21, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1358 ID: DGPM( GLOBAL REFERENCE: DGPM(DGPM,0) FIELD NUMBER: .01 FIELD NAME: MOVEMENT DATE/TIME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to retrieve the Admission Date/Time for use as the Acute Care Admission Date in the IBQ package. GENERAL DESCRIPTION: The IBQ package requests permission to directly access the MOVEMENT DATE/TIME field in the PATIENT MOVEMENT File (#405) for use in the IBQ package. Reference to the PATIENT MOVEMENT File is by the ADMISSION filed in the CLAIMS TRACKING File (#356). Refer to IA-1350 for use of the ADMISSION field in the IBQ package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17584198 SUBSCRIBING PACKAGE: UTILIZATION MANAGEMENT ROLLUP ISC: Albany NUMBER: 1359 IA #: 1359 FILE NUMBER: 45.7 GLOBAL ROOT: DIC(45.7 DATE CREATED: SEP 21, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1359 ID: DIC(45.7 GLOBAL REFERENCE: DIC(45.7,IEN,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used for the Treating Specialty in the IBQ package. GENERAL DESCRIPTION: The IBQ package requests permission to directly access the FACILITY TREATING SPECILTY File (#45.7) in order to retrieve the NAME Field. The SPECIALTY FOR REVIEW Field from the HOSPITAL REVIEW File (#356.1) will be used as the IEN to the FACILITY TREATING SPECIALTY File. Refer to IA-1351 for use of the SPECIALTY FOR REVIEW field in the IBQ package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17584198 SUBSCRIBING PACKAGE: UTILIZATION MANAGEMENT ROLLUP ISC: Albany SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING NUMBER: 1360 IA #: 1360 FILE NUMBER: 42.4 GLOBAL ROOT: DIC(42.4 DATE CREATED: SEP 21, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1360 ID: DIC(42.4 GLOBAL REFERENCE: DIC(42.4,IEN,0) FIELD NUMBER: .03 FIELD NAME: SERVICE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used as for the Service field in the IBQ package. GENERAL DESCRIPTION: The IBQ package requests permission to directly access the SPECILTY File (#42.4) to retrieve the SERVICE field (#.03). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17584198 SUBSCRIBING PACKAGE: UTILIZATION MANAGEMENT ROLLUP ISC: Albany NUMBER: 1361 IA #: 1361 DATE CREATED: SEP 22, 1995 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORMFN NAME: DBIA1361-A ORIGINAL NUMBER: 1361 ID: ORMFN GENERAL DESCRIPTION: This DBIA documents a Radiology/Nuclear Medicine call to an OE/RR routine for the purpose of first-time population of the OE/RR v.3 orderable items file. This DBIA shall take effect with Version 3 of OE/RR. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17603351 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: This entry point is called if the Radiology/Nuclear Medicine package is installed at a site after OE/RR v.3 is installed. The input parameter tells the routine where to look for the HL7 messages containing all data necessary to order Radiology/Nuclear Medicine procedures. VARIABLES: MSG TYPE: Input VARIABLES DESCRIPTION: Message array or global root. SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 1362 IA #: 1362 DATE CREATED: SEP 22, 1995 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORB3 NAME: DBIA1361-B ORIGINAL NUMBER: 1361 ID: ORB3 GENERAL DESCRIPTION: This DBIA documents a call to EN^ORB3 which handles processing of notifications via CPRS. This call is made by packages which must generate CPRS alerts through their own package code. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28751173 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: This routine is called to process a notification regarding an order. The routine determines who is supposed to receive the notification in addition to recipients defined in input parameters. VARIABLES: ORN TYPE: Input VARIABLES DESCRIPTION: Notification ID (ifn from OE/RR Notifications file #100.9) VARIABLES: ORBDFN TYPE: Input VARIABLES DESCRIPTION: Patient DFN from Patient file #2 VARIABLES: ORNUM TYPE: Input VARIABLES DESCRIPTION: Order ifn from Order file #100. VARIABLES: ORBADUZ TYPE: Input VARIABLES DESCRIPTION: Array of notification recipients requested by the calling package. VARIABLES: ORBPMSG TYPE: Input VARIABLES DESCRIPTION: Message text VARIABLES: ORBPDATA TYPE: Input VARIABLES DESCRIPTION: This is an identifier of the package entry which the notification is based on. For radiology: Rad/Nuc Med exam/case ifn's (format: exam_ifn;case_ifn) For consults: the IEN of the consult in file 123 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING DETAILS: This DBIA documents a Radiology/Nuclear Medicine call to OE/RR v.3 notification processing routine that handles notifications that must be generated for Radiology/Nuclear Medicine outside of HL7 messages processed through protocols. This DBIA will take effect when OE/RR v.3 is released. SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: WOMEN'S HEALTH SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING DETAILS: added 7/22/09 SUBSCRIBING PACKAGE: CLINICAL REMINDERS DBA Comments: Debbie Trost added Clinical Reminders package as a new subscriber. PXRM*2*24 will use this ICR to create an OR notification, to be released in late summer. DATE/TIME EDITED: JUL 22, 2009@15:07 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: PULEO,ANTHONY WITH CONCURRENCE OF: CHUNG,TERESA DATE/TIME EDITED: APR 18, 2012@12:23 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: REDINGTON,PATRICK WITH CONCURRENCE OF: CHUNG,TERESA NUMBER: 1363 IA #: 1363 DATE CREATED: SEP 22, 1995 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORBSTAT NAME: KERNEL 8 transport of ORBSTAT ID: ORBSTAT GENERAL DESCRIPTION: Kernel 8.0 needs to transport the routine ORBSTAT. This routine was modified in order to work with Kernel 8.0. The changes are not compatible with Kernel 7.1. This is a one time release. STATUS: Active DURATION: Next Version MAIL MESSAGE: 15016405 GOOD ONLY FOR VERSION: 8.0 SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 1364 IA #: 1364 DATE CREATED: SEP 22, 1995 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORF2 NAME: KERNEL 8 transport of ORF2 ID: ORF2 GENERAL DESCRIPTION: Kernel 8.0 needs to transport the routine ORF2. This routine was modified in order to work with Kernel 8.0. The changes are not compatible with Kernel 7.1. This is a one time release. STATUS: Active DURATION: Next Version MAIL MESSAGE: 15016405 GOOD ONLY FOR VERSION: 8.0 SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 1365 IA #: 1365 DATE CREATED: SEP 25, 1995 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMPLENFM NAME: DBIA1365 ID: GMPLENFM STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34250615 COMPONENT/ENTRY POINT: ACTIVE COMPONENT DESCRIPTION: Permission to call ACTIVE^GMPLENFM for the purpose of obtaining a list of the patient's active problems. INPUTS: DFN = ien of patient in File #2 OUTPUTS: Returns the data in the ^TMP global as follows: ^TMP("IB",$J,"INTERFACES",DFN,"GMP PATIENT ACTIVE PROBLEMS",#) = Piece 1: Text of problem 2: ICD code of problem 3: Date of Onset in 00/00/00 format 4: "SC" or "NSC" or "", if problem is [not] related to a SC Cond. 5: "Y" or "N" or "", if problem is [not] related to a SC Condition (Pieces 4 and 5 give the same data, just in different formats.) 6: "A" or "I" or "P" or "H" or "M" or "", if problem is related to exposure to Agent Orange, Ionization, Persian Gulf, Head and/or Neck Cancer, Military Sexual Trauma or null respectively 7: Full text of the special exposure indicated in piece 6, if any where each # is a different problem, 1 - n with n being the total number of active problems; the 0-node is also set to the total (n). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: ien of patient in File #2 COMPONENT/ENTRY POINT: SELECT COMPONENT DESCRIPTION: Permission to call SELECT^GMPLENFM for the purpose of allowing users access to the EXPRESSIONS file to create lists of Clinic Common Problems. SELECT^GMPLENFM is used for the lookup rather than a simple ^DIC call in order to setup the Problem List context for searching the Lexicon. INPUTS: Requires no input values. OUTPUTS:Returns the entry in the Lexicon Utility selected to add to a form as a commonly selected problem in the ^TMP global as follows: ^TMP("IB",$J,"INTERFACES","GMP SELECT CLINIC COMMON PROBLEMS") = Piece 1: IEN of problem in the Lexicon Utility Expressions file (#757.01) 2: Text of problem 3: ICD Code of problem, if known COMPONENT/ENTRY POINT: DSELECT COMPONENT DESCRIPTION: Permission to call DSELECT^GMPLENFM for the purpose of obtaining a list of the patient's active problems. INPUTS: Requires DFN = ien of patient in File #2 OUTPUTS: Returns the data in the ^TMP global as follows: ^TMP("IB",$J,"INTERFACES","GMP SELECT PATIENT ACTIVE PROBLEMS",#) = Piece 1: ien of problem 2: Text of problem 3: ICD code of problem 4: Date of Onset in 00/00/00 format 5: "SC" or "NSC" or "", if problem is [not] related to a SC Cond. 6: "Y" or "N" or "", if problem is [not] related to a SC Condition (Pieces 4 and 5 give the same data, just in different formats.) 7: "A" or "I" or "P" or "H" or "M" or "", if problem is related to exposure to Agent Orange, Ionization, Persian Gulf Head and/or Neck Cancer, Military Sexual Trauma or null respectively 8: Full text of the special exposure indicated in piece 6, if any where each # is a different problem, 1 - n with n being the total number of active problems; the 0-node is also set to the total (n). VARIABLES: DFN TYPE: Output VARIABLES DESCRIPTION: ien of patient in File #2 SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 1366 IA #: 1366 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: SEP 26, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1366 ID: VA(200, GLOBAL REFERENCE: VA(200,'A',AC,0) FIELD NUMBER: A xref to DUZ ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The A xref is used to obtain the user's DUZ from the Access Code. GLOBAL REFERENCE: VA(200,DUZ,.1) FIELD NUMBER: .1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: The existence of the node is checked to ensure that the access code exist. GLOBAL REFERENCE: VA(200,DUZ,20) FIELD NUMBER: 20.2 FIELD NAME: SIGNATURE BLOCK PRINTED NAME LOCATION: 20;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 20.4 FIELD NAME: ELECTRONIC SIGNATURE CODE LOCATION: 20;4 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: The second and forth piece are used to validate the signature code. GENERAL DESCRIPTION: Version 1.6 of the HL7 package includes support for sending security codes (access and signature) in an HL7 message. As a result the HL7 package needs to directly access the new person file to validate the security codes. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 14622817 SUBSCRIBING PACKAGE: HEALTH LEVEL SEVEN ISC: Albany NUMBER: 1367 IA #: 1367 DATE CREATED: SEP 26, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XPDKEY NAME: XPDKEY ID: XPDKEY CREATOR: FORT,WALLY GENERAL DESCRIPTION: Extrinsic functions that can be used to control the Security Key File. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: $$RENAME COMPONENT DESCRIPTION: Usage: S value=$$RENAME^XPDKEY(oldname,newname) Use this entry point to rename a security key. All necessary indexing is performed to maintain the ^XUSEC global. The return value is 1 for OK, or 0 for failure. VARIABLES: oldname TYPE: Input VARIABLES DESCRIPTION: Name of security key to be renamed. VARIABLES: newname TYPE: Input VARIABLES DESCRIPTION: New name for security key. VARIABLES: value TYPE: Output VARIABLES DESCRIPTION: return 1 if operation successful, 0 if operation failed. COMPONENT/ENTRY POINT: $$LKUP COMPONENT DESCRIPTION: Usage: S value=$$LKUP^XPDKEY(key_value) This extrinsic function will lookup a Security Key by name or by IEN value. If called with a number it returns the name of the KEY. If called with a name it returns the IEN number of the KEY. COMPONENT/ENTRY POINT: DEL COMPONENT DESCRIPTION: Usage: D DEL^XPDKEY(key_name) This call will delete a Security Key from the Security Key File. All necessary indexing is performed to maintain the ^XUSEC global. The KEY is removed from all holders in the NEW PERSON file. VARIABLES: key_name TYPE: Input VARIABLES DESCRIPTION: The name of the Security Key to delete. DBA Comments: Was listed as withdrawn from as far back as Sep 2006. Activated as per Wally Fort. DATE ACTIVATED: MAR 12, 2008 DATE/TIME EDITED: MAR 12, 2008@14:36 ACTION: APPROVED AT THE REQUEST OF: FORT,WALLY NUMBER: 1369 IA #: 1369 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: OCT 02, 1995 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Get Clinic Appointments ID: DPT( GLOBAL REFERENCE: DPT(D0,'DE', GLOBAL DESCRIPTION: Get Clinic appointments GENERAL DESCRIPTION: ^DPT(DFN,"DE" for current clinics STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17388791 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE NUMBER: 1370 IA #: 1370 DATE CREATED: OCT 03, 1995 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DDBRZIS/DDBDMSG GENERAL DESCRIPTION: Progress Notes will check $G(DDBRZIS). If so, the variable DDBDMSG will be set equal to "Progress Notes". This will enable "Progress Notes" to display as the title if the BROWSER device has been selected. VIEWER: PRICE,DEBORAH VIEWER: MANAPSAL,DANILA VIEWER: RUSSELL,JOEL STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32135595 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: MAILMAN ISC: Oakland SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 1371 IA #: 1371 FILE NUMBER: 2101.2 GLOBAL ROOT: GECS DATE CREATED: OCT 04, 1995 CUSTODIAL PACKAGE: GENERIC CODE SHEET CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1371 ID: GECS GLOBAL REFERENCE: GECS(2101.2 FIELD NUMBER: 1 FIELD NAME: ACTIVE CODE SHEET LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field indicates if the code sheet is active or not. GLOBAL DESCRIPTION: This file stores the different typs of code sheets used for each type of batch (in file 2101.1). GENERAL DESCRIPTION: This is a request for an integration agreement between GECS and PIMS. PIMS will be making reference to file ^GECS(2101.2, GENERIC CODE SHEET TRANSACTION TYPE/SEGMENT file, the zero node, 5th piece, to look at the ACTIVE CODE SHEET (#1) field. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17773043 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 1372 IA #: 1372 FILE NUMBER: 45 GLOBAL ROOT: DGPT( DATE CREATED: OCT 06, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PTF file access ID: DGPT( GLOBAL REFERENCE: DGPT(D0,70) FIELD NUMBER: 70 FIELD NAME: DISCHARGE DATE LOCATION: 70;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 71 FIELD NAME: DISCHARGE SPECIALTY LOCATION: 70;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 72 FIELD NAME: TYPE OF DISPOSITION LOCATION: 70;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 73 FIELD NAME: OUTPATIENT TREATMENT LOCATION: 70;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 75 FIELD NAME: PLACE OF DISPOSITION LOCATION: 70;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79 FIELD NAME: DXLS LOCATION: 70;10 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 80 FIELD NAME: PRINCIPAL DIAGNOSIS LOCATION: 70;11 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.16 FIELD NAME: ICD 2 LOCATION: 70;16 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.17 FIELD NAME: ICD 3 LOCATION: 70;17 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.18 FIELD NAME: ICD 4 LOCATION: 70;18 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.19 FIELD NAME: ICD 5 LOCATION: 70;19 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.201 FIELD NAME: ICD 6 LOCATION: 70;20 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.21 FIELD NAME: ICD 7 LOCATION: 70;21 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.22 FIELD NAME: ICD 8 LOCATION: 70;22 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 70.23 FIELD NAME: ICD 9 LOCATION: 70;23 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 70.24 FIELD NAME: ICD 10 LOCATION: 70;24 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DGPT(D0,P,0) FIELD NUMBER: 60 LOCATION: P;0 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DGPT(D0,P,D1,0) FIELD NUMBER: .01 FIELD NAME: PROCEDURE DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: PROCEDURE CODE 1 LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5 FIELD NAME: PROCEDURE CODE 2 LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6 FIELD NAME: PROCEDURE CODE 3 LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7 FIELD NAME: PROCEDURE CODE 4 LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 8 FIELD NAME: PROCEDURE CODE 5 LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DGPT(D0,S,0) FIELD NUMBER: 40 LOCATION: S;0 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DGPT(D0,S,D1,0) FIELD NUMBER: .01 FIELD NAME: SURGERY/PROCEDURE DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 8 FIELD NAME: OPERATION CODE 1 LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 9 FIELD NAME: OPERATION CODE 2 LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 10 FIELD NAME: OPERATION CODE 3 LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 11 FIELD NAME: OPERATION CODE 4 LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 12 FIELD NAME: OPERATION CODE 5 LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DGPT('B',DFN,PTF) GLOBAL DESCRIPTION: DIRECT GLOBAL READ GENERAL DESCRIPTION: The health summary packages needs the ability to access PTF data to display in several of the health summary components. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: LAB SERVICE ISC: Birmingham SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 1373 IA #: 1373 FILE NUMBER: 101 GLOBAL ROOT: ORD(101 DATE CREATED: OCT 12, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1373 ID: ORD(101 GLOBAL REFERENCE: ORD(101, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 1 FIELD NAME: ITEM TEXT LOCATION: 0;2 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 3.5 FIELD NAME: DESCRIPTION LOCATION: 1;0 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 4 FIELD NAME: TYPE LOCATION: 0;4 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 10 FIELD NAME: ITEM LOCATION: 10;0 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 12 FIELD NAME: PACKAGE LOCATION: 0;12 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 15 FIELD NAME: EXIT ACTION LOCATION: 15;E1,245 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 20 FIELD NAME: ENTRY ACTION LOCATION: 20;E1,245 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 770.1 FIELD NAME: SENDING APPLICATION LOCATION: 770;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 770.2 FIELD NAME: RECEIVING APPLICATION LOCATION: 770;2 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 770.3 FIELD NAME: TRANSACTION MESSAGE TYPE LOCATION: 770;3 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 770.4 FIELD NAME: EVENT TYPE LOCATION: 770;4 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 770.5 FIELD NAME: MESSAGE STRUCTURE LOCATION: 770;5 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 770.6 FIELD NAME: PROCESSING ID LOCATION: 770;6 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 770.7 FIELD NAME: LOGICAL LINK LOCATION: 770;7 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 770.8 FIELD NAME: ACCEPT ACK CODE LOCATION: 770;8 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 770.9 FIELD NAME: APPLICATION ACK TYPE LOCATION: 770;9 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 770.95 FIELD NAME: VERSION ID LOCATION: 770;10 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 771 FIELD NAME: PROCESSING ROUTINE LOCATION: 771;E1,245 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 772 FIELD NAME: RESPONSE PROCESSING ROUTINE LOCATION: 772;E1,245 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 773.1 FIELD NAME: SENDING FACILITY REQUIRED? LOCATION: 773;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 773.2 FIELD NAME: RECEIVING FACILITY REQUIRED? LOCATION: 773;2 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 773.3 FIELD NAME: SECURITY REQUIRED? LOCATION: 773;3 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 773.4 FIELD NAME: DATE/TIME OF MESSAGE REQUIRED? LOCATION: 773;4 ACCESS: Direct Global R/W & w/Fileman GLOBAL REFERENCE: ORD(101,'AHL2',CLIENT,DA) GLOBAL DESCRIPTION: This cross reference is needed to provide a list of Client (Subscriber) protocols. GLOBAL REFERENCE: ORD(101,'AHL1',SERVER,MESSAGE TYPE,EVENT TYPE,DA) GLOBAL DESCRIPTION: This cross reference is used to look up the protocol related to an incoming message at the time the incoming message is received. This cross reference is composed of values from the Server Application, Message Type and Event Type fields. This cross reference works in conjuction with the 'AHL1A' cross reference on the Message Type Received field (770.3) and the 'AHL1B' cross reference on the Event Type field (770.4). GLOBAL REFERENCE: ORD(101,'B', GLOBAL DESCRIPTION: Global read access. GLOBAL REFERENCE: ORD(101,D0,775, FIELD NUMBER: .01 FIELD NAME: SUBSCRIBERS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: $O access across ^ORD(101,D0,775,D1) GENERAL DESCRIPTION: Version 1.6 of the HL7 package uses the Protocol file (#101) to store event related information concerning HL7 messages being exchanged by applications. As a result, it was necessary to add values to the Type field (#4) and to add a number of messaging specific fields and cross references to the file. The following Input Template was added to the Protocol file (#101): 'HL MESSAGING PROTOCOL EDIT' This template allow for editing of the fields described in this Integration Agreement. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17673607 SUBSCRIBING PACKAGE: HEALTH LEVEL SEVEN ISC: Albany SUBSCRIBING PACKAGE: VDEF SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING DETAILS: Only using SUBSCRIBERS field 775 SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM SUBSCRIBING DETAILS: Enrollment maintains a list of HEC protocols within the RPC routines and only modifies protocols in the list. The protocols Enrollment has permission The File #101 namespaces involved are: EAS ESR* New Vista to ESR protocols VAMC* Existing Vista to HEC protocols By inclusion as a named subscriber in this ICR, Enrollment has permission to modify the above protocols. SUBSCRIBING PACKAGE: MYHEALTHEVET SUBSCRIBING DETAILS: added 12/21/2007 SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING DETAILS: ADDED 9/13/2007 SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING DETAILS: ADDED 8/3/2007 DATE/TIME EDITED: JAN 23, 2007@23:02 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HARTLEY,PETER WITH CONCURRENCE OF: FORT,WALLY DATE/TIME EDITED: DEC 27, 2007@21:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MONGER,GARY WITH CONCURRENCE OF: GARCIA,JOSE DATE/TIME EDITED: SEP 13, 2007@21:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MCCORMACK,JOHN WITH CONCURRENCE OF: ORMSBY,SKIP DATE/TIME EDITED: AUG 03, 2007@21:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: JUERGENSMEYER,BRIAN WITH CONCURRENCE OF: ORMSBY,SKIP NUMBER: 1376 IA #: 1376 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: NEW PERSON ID: VA(200, GLOBAL REFERENCE: VA(200,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Write w/Fileman FIELD DESCRIPTION: Also LAYGO with FileMan and pointed to from Nurs Staff (210) file. This LAYGO access can be turned off by a site parameter in the Nursing software. Nursing also points to this file from the Employee Name (.01) field of the Nurs Staff (210) file. This pointer uses a DINUM relationship. GLOBAL REFERENCE: VA(200,D0,1) FIELD NUMBER: 4 FIELD NAME: SEX LOCATION: 1;2 ACCESS: Write w/Fileman FIELD NUMBER: 5 FIELD NAME: DOB LOCATION: 1;3 ACCESS: Write w/Fileman FIELD NUMBER: 9 FIELD NAME: SSN LOCATION: 1;9 ACCESS: Write w/Fileman GLOBAL REFERENCE: VA(200,D0,.11) FIELD NUMBER: .111 FIELD NAME: STREET ADDRESS 1 LOCATION: .11;1 ACCESS: Write w/Fileman FIELD NUMBER: .112 FIELD NAME: STREET ADDRESS 2 LOCATION: .11;2 ACCESS: Write w/Fileman FIELD NUMBER: .113 FIELD NAME: STREET ADDRESS 3 LOCATION: .11;3 ACCESS: Write w/Fileman FIELD NUMBER: .114 FIELD NAME: CITY LOCATION: .11;4 ACCESS: Write w/Fileman FIELD NUMBER: .115 FIELD NAME: STATE LOCATION: .11;5 ACCESS: Write w/Fileman FIELD NUMBER: .116 FIELD NAME: ZIP CODE LOCATION: .11;6 ACCESS: Write w/Fileman GENERAL DESCRIPTION: Nursing can access the New Person file as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17791454 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1377 IA #: 1377 FILE NUMBER: 42 GLOBAL ROOT: DIC(42, DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: WARD LOCATION ID: DIC(42, CREATOR: BERNHEIM,ARMAND GLOBAL REFERENCE: DIC(42,D0, FIELD NUMBER: .03 FIELD NAME: SERVICE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .015 FIELD NAME: DIVISION LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Direct global access on the "B" cross-reference of the Ward Location (42) file is supported by this DBIA. GENERAL DESCRIPTION: Controlled access to the Ward Location (42) file fields/cross-references as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18113473 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING DETAILS: added 5/14/09 SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING DETAILS: ADDED 5/3/2011 DBA Comments: 20090710 - ADDED DIVISION AS READABLE DATA ELEMENT DATE ACTIVATED: JUL 10, 2009 DATE/TIME EDITED: MAY 14, 2009@12:28 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: REDINGTON,PATRICK WITH CONCURRENCE OF: MULLER,RICHARD DATE/TIME EDITED: JUL 10, 2009@12:59 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: SILVERMAN,ROBERT WITH CONCURRENCE OF: ELLIS,DONNA DATE/TIME EDITED: JUL 10, 2009@13:00 ACTION: APPROVED AT THE REQUEST OF: SILVERMAN,ROBERT WITH CONCURRENCE OF: ELLIS,DONNA DATE/TIME EDITED: MAY 03, 2011@11:21 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SMULLEN,GEOFFREY WITH CONCURRENCE OF: KOPECKY,STEVE NUMBER: 1378 IA #: 1378 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DGPM ID: DGPM( GLOBAL REFERENCE: DGPM(D0,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: TRANSACTION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: PATIENT LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: WARD LOCATION LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .14 FIELD NAME: ADMISSION/CHECK-IN MOVEMENT LOCATION: 0;14 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DGPM('AMV3', GLOBAL DESCRIPTION: Direct global read to the "AMV3" cross-reference. GLOBAL REFERENCE: DGPM('APMV', GLOBAL DESCRIPTION: Direct global read to the "APMV" cross-reference. GLOBAL REFERENCE: DGPM('ATID1', GLOBAL DESCRIPTION: Direct global read to the "ATID1" cross-reference. GLOBAL REFERENCE: DGPM('ATID2', GLOBAL DESCRIPTION: Direct global read to the "ATID2" cross-reference. GLOBAL REFERENCE: DGPM('ATID3', GLOBAL DESCRIPTION: Direct global read to the "ATID3" cross-reference. GLOBAL REFERENCE: DGPM('CN', GLOBAL DESCRIPTION: Direct global read to the "CN" cross-reference. GENERAL DESCRIPTION: Nursing directly references the ^DGPM global. We would like permissionto reference the following fields/cross-references using direct global reads: .01 DATE/TIME .02 TRANSACTION .03 PATIENT .06 WARD LOCATION .14 ADMISSION/CHECK-IN MOVEMENT "AMV3" cross-reference "APMV" cross-reference "ATID1" cross-reference "ATID2" cross-reference "ATID3" cross-reference "CN" cross reference STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18110263 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines SUBSCRIBING PACKAGE: ONCOLOGY SUBSCRIBING DETAILS: Onc added 1/30/2009 SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING DETAILS: added 12/16/09 SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING DETAILS: LR ADDED 3/21/11 DATE/TIME EDITED: JAN 30, 2009@09:30 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: RIKARD,KEN WITH CONCURRENCE OF: MULLER,RICHARD DATE/TIME EDITED: DEC 16, 2009@19:22 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: REDINGTON,PATRICK WITH CONCURRENCE OF: PULEO,ANTHONY DATE/TIME EDITED: MAR 21, 2011@09:04 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SMULLEN,GEOFFREY WITH CONCURRENCE OF: KOPECKY,STEVE NUMBER: 1380 IA #: 1380 FILE NUMBER: 405.4 GLOBAL ROOT: DG(405.4, DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ROOM-BED ID: DG(405.4, GLOBAL REFERENCE: DG(405.4,0) GLOBAL DESCRIPTION: Direct global reference of this node to check for existence of Room-Bed (405.4) file. GLOBAL REFERENCE: DG(405.4,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DG(405.4,'W', GLOBAL DESCRIPTION: Direct global read on the "W" cross-reference. GENERAL DESCRIPTION: Nursing, Vitals/Measurements and Intake/Output have permission to access the following elements in the Room-Bed (405.4) file. ^DG(405.4,0) to test for existence of file. "W" cross-reference Direct global read of the NAME (.01) field. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18147718 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines SUBSCRIBING PACKAGE: INTAKE/OUTPUT ISC: Hines SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION SUBSCRIBING PACKAGE: DIETETICS SUBSCRIBING DETAILS: added 6/29/09 SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING PACKAGE: AUTOMATED LAB INSTRUMENTS DBA Comments: 12/31/14-MM: On 12/24/14, Phil Burkhalter stated in an email that MBAA PATIENT ADMISSIONS RPC is not included in this release of SCV or VAR2. Scheduling Calendar View will not need to subscribe to ICRs 419, 565, 2965, 1380. We can withdraw these requests. DATE/TIME EDITED: JAN 23, 2007@23:15 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SWESKY,JEFF WITH CONCURRENCE OF: HARRIS,DONNA DATE/TIME EDITED: JUN 29, 2009@15:03 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: UNDERHILL,GARDNER WITH CONCURRENCE OF: MULLER,RICHARD DATE/TIME EDITED: FEB 18, 2011@08:53 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SMULLEN,GEOFF WITH CONCURRENCE OF: KOPECKY,STEVE NUMBER: 1381 IA #: 1381 FILE NUMBER: 120.5 GLOBAL ROOT: GMR(120.5, DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMRV VITAL MEASUREMENT ID: GMR(120.5, GLOBAL REFERENCE: GMR(120.5,D0,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME VITALS TAKEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: VITAL TYPE LOCATION: O;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .05 FIELD NAME: HOSPITAL LOCATION LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: ENTERED BY LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.2 FIELD NAME: RATE LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: GMR(120.5,D0,2) FIELD NUMBER: 2 FIELD NAME: ENTERED IN ERROR LOCATION: 2;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: GMR(120.5,'AA', GLOBAL DESCRIPTION: Direct global read on the "AA" cross-reference. GLOBAL REFERENCE: GMR(120.5,5, FIELD NUMBER: .01 FIELD NAME: QUALIFIER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This DBIA authorizes access to the following fields in the GMRV Vital Measurement (120.5) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30390141 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING DETAILS: Nursing references fields .01, 2.1 and 2. It also uses the 'AA' x-ref. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: OE/RR references fields #.01, 2.1, 2, .03, .05, and .06. In addition, it utilizes the 'AA' x-ref. SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION NUMBER: 1382 IA #: 1382 FILE NUMBER: 120.51 GLOBAL ROOT: GMRD(120.51, DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMRV VITAL TYPE ID: GMRD(120.51, GLOBAL REFERENCE: GMRD(120.51,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: GMRD(120.51,'C', GLOBAL DESCRIPTION: Direct global read on the "C" cross-reference. GENERAL DESCRIPTION: Nursing has permission to access the GMRV Vital Type (120.51) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18115771 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER SUBSCRIBING DETAILS: added 10/10/08 DATE/TIME EDITED: OCT 10, 2008@12:58 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HSI,TUAN WITH CONCURRENCE OF: TRAXLER,FRANK NUMBER: 1385 IA #: 1385 FILE NUMBER: 23 GLOBAL ROOT: DIC(23, DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: BRANCH OF SERVICE ID: DIC(23, GLOBAL REFERENCE: DIC(23,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Nursing also has permission to point to this file from the Military Status multiple in the Nurs Staff (210) file. GENERAL DESCRIPTION: Nursing has permission to access the Branch of Service (23) file as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 17791643 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE NUMBER: 1386 IA #: 1386 FILE NUMBER: 124.1 GLOBAL ROOT: GMRD(124.1, DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - GENERATOR CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMRG PARAMETERS ID: GMRD(124.1, GLOBAL REFERENCE: GMRD(124.1,D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: PACKAGE PARAMETERS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: HIGHLIGHTING OFF LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: GMRD(124.1,D0,1,D1,'P') FIELD NUMBER: 1 FIELD NAME: PRINT ROUTINE LOCATION: P;E1,245 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: GMRD(124.1,D0,1,'B', GLOBAL DESCRIPTION: Direct global read to "B" cross-reference on Package Parameters sub-file. GENERAL DESCRIPTION: Nursing has permission to access the GMRG Parameters (124.1) file fields described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18115276 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1387 IA #: 1387 FILE NUMBER: 124.2 GLOBAL ROOT: GMRD(124.2, DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - GENERATOR CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: AGGREGATE TERM ID: GMRD(124.2, GLOBAL REFERENCE: GMRD(124.2,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Write w/Fileman FIELD DESCRIPTION: Also direct global read is supported. FIELD NUMBER: .02 FIELD NAME: TYPE OF TERM LOCATION: 0;2 ACCESS: Write w/Fileman FIELD NUMBER: .03 FIELD NAME: PACKAGE LOCATION: 0;3 ACCESS: Write w/Fileman FIELD NUMBER: .04 FIELD NAME: CLASSIFICATION LOCATION: 0;4 ACCESS: Write w/Fileman FIELD DESCRIPTION: Direct global read is supported as well. FIELD NUMBER: .05 FIELD NAME: NODE IDENTIFICATION LOCATION: 0;5 ACCESS: Write w/Fileman GLOBAL REFERENCE: GMRD(124.2,D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: CHILD LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: CHILD TEXT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: GMRD(124.2,D0,1,'AC', GLOBAL DESCRIPTION: Direct global read on the "AC" cross-reference of the Children sub-file. GLOBAL REFERENCE: GMRD(124.2,D0,1,'B', GLOBAL DESCRIPTION: Direct global read on the "B" cross-reference of the Children sub-file. GLOBAL REFERENCE: GMRD(124.2,'AA', GLOBAL DESCRIPTION: Direct global read on the "AA" cross-reference of the Aggregate Term (124.2) file. GLOBAL REFERENCE: GMRD(124.2,'AKID', GLOBAL DESCRIPTION: Direct global reference on the "AKID" cross-reference of the Aggregate Term (124.2) file. GENERAL DESCRIPTION: Nursing has permission to access the Aggregate Term (124.2) file fields described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18115276 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1388 IA #: 1388 FILE NUMBER: 124.25 GLOBAL ROOT: GMRD(124.25, DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - GENERATOR CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TERM CLASSIFICATION ID: GMRD(124.25, GLOBAL REFERENCE: GMRD(124.25,'AA', GLOBAL DESCRIPTION: Direct global reference on the "AA" cross-reference of the Term Classification file. GLOBAL REFERENCE: GMRD(124.25,'B', GLOBAL DESCRIPTION: Direct global reference on the "B" cross-reference of the Term Classification file. GLOBAL REFERENCE: GMRD(124.25,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Check for the existence of the zero node and do a direct global read of the first piece. GENERAL DESCRIPTION: Nursing has permission to access the Term Classification (124.25) file fields described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18115276 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1389 IA #: 1389 FILE NUMBER: 124.3 GLOBAL ROOT: GMR(124.3, DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - GENERATOR CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMR TEXT ID: GMR(124.3, GLOBAL REFERENCE: GMR(124.3,D0, FIELD NUMBER: .01 FIELD NAME: TEXT BLOCK LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: DATE CREATED LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: AUTHOR LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5 FIELD NAME: ENTERED IN ERROR LOCATION: 5;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5.1 FIELD NAME: DATE ENTERED IN ERROR LOCATION: 5;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5.2 FIELD NAME: USER ENTERING IN ERROR LOCATION: 5;3 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Nursing can point to this file from the Nurs Care Plan (216.8) file. Nursing can access the ^GMR(124.3,D0,0) node to lock/unlock a record in the GMR Text (124.3) file. Nursing can access the "AA" cross-reference on the GMR Text file using direct global reads. GLOBAL REFERENCE: GMR(124.3,D0,1,D1, FIELD NUMBER: .01 FIELD NAME: SELECTION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: APPENDED/INTERNAL TEXT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: ADDITIONAL TEXT LOCATION: ADD;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Also direct global reads are supported for the "ALIST" and "B" cross-references of the Selection sub-file are supported. GLOBAL REFERENCE: GMR(124.3,D0,1,D1,2,D2, FIELD NUMBER: .01 FIELD NAME: AUDIT TRAIL DATE/TIME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: MODIFICATION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: USER WHO MODIFIED LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Also a direct global read to the "AA" cross-reference of the Audit Trail sub-file is supported. GENERAL DESCRIPTION: Nursing has permission to access the GMR Text (124.3) file fields described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18115276 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1390 IA #: 1390 FILE NUMBER: 126 GLOBAL ROOT: GMR(126, DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMRY PATIENT I/O FILE ID: GMR(126, GLOBAL REFERENCE: GMR(126,D0, GLOBAL DESCRIPTION: Direct global read on "B" cross-reference of GMRY Patient I/O File is supported. LAYGO is allowed to this file using a ^DIC lookup. GLOBAL REFERENCE: GMR(126,D0,'IVM',D1, GLOBAL DESCRIPTION: Direct global reference on the "B" cross-reference of the IV Maintenance sub-file is supported. GLOBAL REFERENCE: GMR(126,D0,'IVM',D1,1,D2, FIELD NUMBER: .01 FIELD NAME: MAINTENANCE DATE/TIME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: SITE DESCRIPTION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: TUBING CHANGED LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: DRESSING CHANGED LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: ENTERED BY LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5 FIELD NAME: SITE DC'ED LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Direct global reads of the "B" and "C" cross-references of the Maintenance sub-file are also supported. GLOBAL REFERENCE: GMR(126,0) GLOBAL DESCRIPTION: Direct global read to test for existence of the file is supported and permission to set it if it does not exist. GLOBAL REFERENCE: GMR(126,D0,'IV',D1,3) FIELD NUMBER: 17 FIELD NAME: PORT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Direct global read to check for its existence and to get the first piece. GLOBAL DESCRIPTION: Direct global read to check for its existence and to get the first piece. GENERAL DESCRIPTION: Nursing has permission to access the GMRY Patient I/O File (126) file fields described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18115703 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1391 IA #: 1391 FILE NUMBER: 126.95 GLOBAL ROOT: GMRD(126.95, DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMRY NUR SHIFT/OTHER ID: GMRD(126.95, GLOBAL REFERENCE: GMRD(126.95,D0, FIELD NUMBER: 1 FIELD NAME: NIGHT LOCATION: 1;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: DAY LOCATION: 1;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: EVENING LOCATION: 1;3 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Nursing and Vitals/Measurements have permission to access the GMRY NUR Shift/Other file fields described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18147486 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines NUMBER: 1392 IA #: 1392 FILE NUMBER: 126.56 GLOBAL ROOT: GMRD(126.56, DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMRY INPUT TYPE ID: GMRD(126.56, GLOBAL REFERENCE: GMRD(126.56,D0, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Direct global read of the "C" cross-reference of the GMRY Input Type file is also supported. GENERAL DESCRIPTION: Vitals/Measurments has permission to access the GMRY Input Type file as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18147486 SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines NUMBER: 1393 IA #: 1393 FILE NUMBER: 126.58 GLOBAL ROOT: GMRD(126.58, DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMRY OUTPUT TYPE ID: GMRD(126.58, GLOBAL REFERENCE: GMRD(126.58,D0, FIELD NUMBER: .01 FIELD NAME: OUTPUT TYPE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Direct global read of the "C" cross-reference of the GMRY Output Type file is also supported. GENERAL DESCRIPTION: Vitals/Measurements has permission to access the GMRY Output Type (126.58) file as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18147486 SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines NUMBER: 1394 IA #: 1394 DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - GENERATOR CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRGED0 NAME: GMRGED0 ID: GMRGED0 GENERAL DESCRIPTION: Nursing has permission to access the GMRGED0 routines as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135646 COMPONENT/ENTRY POINT: EN3 COMPONENT DESCRIPTION: This entry point allows the user to edit a Nursing Care Plan for a specified patient. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient file IEN. VARIABLES: GMRGPDA TYPE: Input VARIABLES DESCRIPTION: Entry in GMR Text (124.3) file of data to be edited. VARIABLES: GMRGRT TYPE: Input VARIABLES DESCRIPTION: A two piece variable in format A^B, where A is the Aggregate Term (124.2) file IEN for prime document to be edited, i.e., Nursing Care Plan, and B is the text representation of the prime document. VARIABLES: GMRGOUT TYPE: Output VARIABLES DESCRIPTION: A flag indicating whether the user abnormally exited the input process, i.e., time-out or ^-out. 0 indicates normal processing, 1 indicates abnormal exit. COMPONENT/ENTRY POINT: Q3 COMPONENT DESCRIPTION: This entry cleans up variables used by the enter/edit patient data process of the Text Generator. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1395 IA #: 1395 DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRYED1 NAME: GMRYED1 ID: GMRYED1 GENERAL DESCRIPTION: Nursing has permission to access the entry points described in this DBIA for the GMRYED1 routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135671 COMPONENT/ENTRY POINT: INPUT COMPONENT DESCRIPTION: Allows user to enter/edit patient intake. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN. VARIABLES: GNUROP TYPE: Input VARIABLES DESCRIPTION: Type of Input/Output/IV. VARIABLES: GMRHLOC TYPE: Input VARIABLES DESCRIPTION: Hospital Location file pointer. VARIABLES: GMROUT TYPE: Both VARIABLES DESCRIPTION: Switch that is set to 0 and returned if abnormal user exit. COMPONENT/ENTRY POINT: OUTPUT COMPONENT DESCRIPTION: Allows user to enter/edit patient Output. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN. VARIABLES: GNUROP TYPE: Input VARIABLES DESCRIPTION: Type of data Input/Output/IV. VARIABLES: GMRHLOC TYPE: Input VARIABLES DESCRIPTION: Hospital Location (44) pointer. VARIABLES: GMROUT TYPE: Both VARIABLES DESCRIPTION: Switch to determine if user abnormally exits. Passed in with value of 0. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1396 IA #: 1396 DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRYRP0 NAME: GMRYRP0 ID: GMRYRP0 GENERAL DESCRIPTION: Nursing has permission to access the following entry points in the GMRYRP0 routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135671 COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: This entry point prints an I/O Summary by Patient (by Shift & Day(s)). VARIABLES: GMRNUR TYPE: Input VARIABLES DESCRIPTION: This variable is set to one to indicate that this routine was called from an external package. COMPONENT/ENTRY POINT: EN4 COMPONENT DESCRIPTION: This entry point prints an I/O Summary (Midnight to Present). VARIABLES: GMRNUR TYPE: Input VARIABLES DESCRIPTION: This variable is set to one to indicate that this routine was called from an external package. COMPONENT/ENTRY POINT: EN5 COMPONENT DESCRIPTION: This entry point prints an I/O Summary (48 hours). VARIABLES: GMRNUR TYPE: Input VARIABLES DESCRIPTION: This variable is set to one to indicate that this routine was called from an external package. COMPONENT/ENTRY POINT: EN2 COMPONENT DESCRIPTION: This entry point prints the Patient I/O Summary Report for the previous day. VARIABLES: GMRNUR TYPE: Input VARIABLES DESCRIPTION: This variable is set to one to indicate that this routine was called from an external package. COMPONENT/ENTRY POINT: Q COMPONENT DESCRIPTION: This entry point cleans up variables used by GMRYRP0 calls. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1397 IA #: 1397 DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRYED3 NAME: GMRYED3 ID: GMRYED3 GENERAL DESCRIPTION: Nursing can access the following entry points described in this DBIA for the GMRYED3 routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135671 COMPONENT/ENTRY POINT: LIST COMPONENT DESCRIPTION: This entry point allows user to start/add/DC IV and maintenance. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN. VARIABLES: GNUROP TYPE: Input VARIABLES DESCRIPTION: Type of Input/Output/IV. VARIABLES: GMRHLOC TYPE: Input VARIABLES DESCRIPTION: Hospital Location file (44) pointer. VARIABLES: GMROUT TYPE: Both VARIABLES DESCRIPTION: This variable indicates whether the user abnormally exited the input process. It is passed in with a value of 0. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1401 IA #: 1401 FILE NUMBER: 452.7 GLOBAL ROOT: PRSE(452.7, DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: EDUCATION TRACKING CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PRSE PARAMETERS ID: PRSE(452.7, GLOBAL REFERENCE: PRSE(452.7,D0, FIELD NUMBER: 1 FIELD NAME: PRSE OFFLINE/ON-LINE LOCATION: OFF;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Nursing has permission to access the PRSE Parameters (452.7) file fields as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18140483 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1403 IA #: 1403 FILE NUMBER: 454 GLOBAL ROOT: PRSP(454, DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: PAID CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PAID CODE FILES ID: PRSP(454, GLOBAL REFERENCE: PRSP(454,D0,'ORG',D1, FIELD NUMBER: .01 FIELD NAME: CODE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: DESCRIPTION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Also included here are direct global reads of the "B" and "C" cross-references of the Cost Center/Organization sub-file. GENERAL DESCRIPTION: Nursing has permission to access the PAID Code Files file fields as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18140516 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1404 IA #: 1404 FILE NUMBER: 454.1 GLOBAL ROOT: PRSP(454.1, DATE CREATED: NOV 07, 1995 CUSTODIAL PACKAGE: PAID CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PAID COST CENTER/ORGANIZATION ID: PRSP(454.1, GENERAL DESCRIPTION: Nursing has permission to access the "B" cross-reference of the PAID Cost Center/Organization (454.1) file using direct global reads. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18140516 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1407 IA #: 1407 DATE CREATED: NOV 08, 1995 CUSTODIAL PACKAGE: DIETETICS CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: FHWHEA NAME: FHWHEA ID: FHWHEA GENERAL DESCRIPTION: Nursing has permission to call the ^FHWHEA routine as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18134698 COMPONENT/ENTRY POINT: FHWHEA COMPONENT DESCRIPTION: This entry point returns information about Dietetics orders for a particular patient. VARIABLES: GMTS1 TYPE: Input VARIABLES DESCRIPTION: 9999999-(End_Date_for_Order_Search) VARIABLES: GMTS2 TYPE: Input VARIABLES DESCRIPTION: 9999999-(Start_Date_for_Order_Search) VARIABLES: GMTSNDM TYPE: Input VARIABLES DESCRIPTION: Number of diets orders to be returned. Nursing sets this variable to 1. VARIABLES: UTILITY($J, TYPE: Output VARIABLES DESCRIPTION: Only two nodes from the ^UTILITY($J are used by Nursing and are documented here. ^UTILITY($J,"DI",9999999-(Order_Start_Date),0)=ST^EN^DIET^COM^TYPE where ST=Order Start Date (FM format) EN=Order End Date (FM format) DIET=Patient's diet (free text) COM=Comments about diet (free text) TYPE=Type of Service for diet (Tray, Cafeteria, Dining Room) ^UTILITY($J,"TF",9999999-(D/T_of_Tubefeeding),0)=TF^CD^PR^ST^QT^CC^KC^COM where TF=Date/time of tubefeeding (FM format) CD=Cancel date/time of tubefeeding (FM format) PR=Product used in tubefeeding (free text) ST=Strength of product used (1/4, 1/2, 3/4, FULL) QT=Quantity of product used (free text) CC=Total CC's of tubefeeding (numeric) KC=Total KCal's of tubefeeding (numeric) COM=Comments about tubefeeding (free text) SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 1409 IA #: 1409 FILE NUMBER: 211.4 GLOBAL ROOT: NURSF(211.4, DATE CREATED: NOV 08, 1995 CUSTODIAL PACKAGE: NURSING SERVICE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: NURS LOCATION ID: NURSF(211.4, GLOBAL REFERENCE: NURSF(211.4, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: PATIENT CARE FLAG LOCATION: 1;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.5 FIELD NAME: INACTIVE FLAG LOCATION: I;1 ACCESS: Read w/Fileman GLOBAL DESCRIPTION: Direct global read of ^NURSF(211.4) is supported to check if the file exists. Direct global read of the "D" cross-reference of the NURS Location (211.4) file is supported. GLOBAL REFERENCE: NURSF(211.4,D0,3, FIELD NUMBER: .01 FIELD NAME: MAS WARD LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Direct global read of ^NURSF(211.4,D0,3,D1) to $Order through the multiple is supported. GENERAL DESCRIPTION: Intake/Output can access the Nurs Location (211.4) file entry as described in this DBIA. Direct read of the 'B' Cross Reference in the NURS LOCATION file (#211.4) is also permitted. Direct global read of the "C" cross-reference of the NURS LOCATION file (#211.4) is also permitted. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30358668 SUBSCRIBING PACKAGE: GEN. MED. REC. - I/O ISC: Hines SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany SUBSCRIBING PACKAGE: BAR CODE MED ADMIN NUMBER: 1410 IA #: 1410 FILE NUMBER: 211.8 GLOBAL ROOT: NURSF(211.8, DATE CREATED: NOV 08, 1995 CUSTODIAL PACKAGE: NURSING SERVICE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: NURS POSITION CONTROL ID: NURSF(211.8, GLOBAL REFERENCE: NURSF(211.8,D0, FIELD NUMBER: .02 FIELD NAME: SERVICE CATEGORY LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Also direct global read access of the "D" cross-reference of file 211.8 is supported. GENERAL DESCRIPTION: Intake/Output has permission to access the NURS Position Control (211.8) file as indicated in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18147986 SUBSCRIBING PACKAGE: GEN. MED. REC. - I/O ISC: Hines NUMBER: 1411 IA #: 1411 FILE NUMBER: 214 GLOBAL ROOT: NURSF(214, DATE CREATED: NOV 08, 1995 CUSTODIAL PACKAGE: NURSING SERVICE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: NURS PATIENT ID: NURSF(214, GLOBAL REFERENCE: NURSF(214,D0, FIELD NUMBER: 2 FIELD NAME: NURS LOCATION LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Direct global read of the "AF" and "E" cross-references of the NURS Patient (214) file is supported. Direct global read of the ^NURSF(214,D0,0) node is also supported. GENERAL DESCRIPTION: Intake/Output can access the NURS Patient (214) file as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18147986 SUBSCRIBING PACKAGE: GEN. MED. REC. - I/O ISC: Hines NUMBER: 1412 IA #: 1412 FILE NUMBER: 0 GLOBAL ROOT: DD( DATE CREATED: MAR 05, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DD GLOBAL ID: DD( GLOBAL REFERENCE: DD(124.2,0,'DIK') GLOBAL DESCRIPTION: Nursing and Text Generator have permission to kill this node to uncompile cross-references on the Aggregate Term (124.2) file. GLOBAL REFERENCE: DD(file,field, FIELD NUMBER: .01 FIELD NAME: LABEL LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Nursing can direct global read the name of a field, and direct global read to loop through the ^DD global to get all of the fields for a particular Nursing file. file is in the range of the Nursing file number space assigned by the DBA, and field is a valid field number in file. FIELD NUMBER: .3 FIELD NAME: POINTER LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Nursing can access this field to decode a set of codes to its external format. file is in the range of the Nursing file number space assigned by the DBA, and field is a valid field number in file. FIELD NUMBER: .5 FIELD NAME: INPUT TRANSFORM LOCATION: 0;5,99 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Nursing can execute the input transform directly for its files/fields. file is in the range of the Nursing file number space assigned by the DBA, and field is a valid field number in file. FIELD NUMBER: 3 FIELD NAME: 'HELP'-PROMPT LOCATION: 3;E1,245 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Nursing can read the 'Help'-Prompt field for its files/fields. file is in the range of the Nursing file number space assigned by the DBA, and field is a valid field number in file. FIELD NUMBER: 4 FIELD NAME: XECUTABLE 'HELP' LOCATION: 4;E1,245 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Nursing can read the Xecutable 'Help' for its files/fields. file is in the range of the Nursing file number space assigned by the DBA, and field is a valid field number in file. FIELD NUMBER: 8 FIELD NAME: READ ACCESS (OPTIONAL) LOCATION: 8;E1,245 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: The Text Generator and Vitals/Measurements can write the Read Access (Optional) for its files/fields. file is in the appropriate package numberspace as assigned by the DBA, and field is a valid field number for file. FIELD NUMBER: 9 FIELD NAME: WRITE ACCESS (OPTIONAL) LOCATION: 9;E1,245 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: The Text Generator and Vitals/Measurements can write the Write Access (Optional) for its files/fields. file is in the appropriate numberspace as assigned by the DBA, and field is a valid field number of file. FIELD NUMBER: 21 FIELD NAME: DESCRIPTION LOCATION: 21;0 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Nursing is allowed direct global read access to the Descriptions for fields to print them out. Also included here are the direct global read references to the ^DD(file,field,21, subtree that would be necessary to read this WP field. file is a valid number in the Nursing numbers space as assigned by the DBA, and field is a valid field number for file. GLOBAL REFERENCE: DD(file,field,1,xref_ien, FIELD NUMBER: 1 FIELD NAME: SET STATEMENT LOCATION: 1;E1,245 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Nursing and the Text Generator are allowed to directly read the Cross-reference Set Statements for their package so they can be executed. file is a valid number in the appropriate number space as assigned by the DBA, field is a valid field number of file, and xref_ien is the cross-reference ien being used. FIELD NUMBER: 2 FIELD NAME: KILL STATEMENT LOCATION: 2;E1,245 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Nursing and the Text Generator are allowed to directly read the Cross-reference Kill Statements for their package so they can be executed. file is a valid number in the appropriate number space as assigned by the DBA, field is a valid field number of file, and xref_ien is the cross-reference ien being used. GLOBAL DESCRIPTION: Nursing and the Text Generator are allowed direct global read access to ^DD(file,field,1,xref_ien) in order to loop through the cross-reference multiple for their files, where file is in the package numberspace assigned by the DBA, field is a valid field in file, and xref_ien is the ien of the cross-reference for field in file. GLOBAL REFERENCE: DD(file,'SB', GLOBAL DESCRIPTION: Nursing can direct global read the ^DD(file,"SB") cross-reference to determine the sub-files for a particular file/sub-file. file is a valid number in the Nursing numberspace as assigned by the DBA. GLOBAL REFERENCE: DD(124.21,0,'DIK') GLOBAL DESCRIPTION: Vitals, Nursing & Text Generator have permission to kill off this node. GLOBAL REFERENCE: DD(124.2,0,'DIKOLD') GLOBAL DESCRIPTION: Vitals, Nursing & Text Generator have permission to kill off this node. GLOBAL REFERENCE: DD(2,0,'IX','ANURS',2,.1) GLOBAL DESCRIPTION: Nursing has permission to direct global kill/write this node when setting up the "ANURS" cross-reference in the Patient file. MAS has already approved this, see MailMessage #18109934. GLOBAL REFERENCE: DD(2,.1,1, GLOBAL DESCRIPTION: Nursing can direct global write the following nodes: ^DD(2,.1,1,xref_ien,0)="2^ANURS^MUMPS", ^DD(2,.1,1,xref_ien,1)="S %X=X,X=""NURSCPL"" X ^%ZOSF(""TEST"") S X=%X D:$T EN1^NURSCPL", ^DD(2,.1,1,xref_ien,2)="S %X=X,X=""NURSCPL"" X ^%ZOSF(""TEST"") S X=%X D:$T EN2^NURSCPL". xref_ien is the next available cross-reference ien for field .1. A direct global read is allowed on ^DD(2,.1,1,xref_ien) to loop through the xrefs of field .1. Nursing can direct global kill the ANURS cross-reference via a direct global kill of the ^DD(2,.1,1,xref_ien) node. xref_ien is ien of the ANURS xref (where $P(^DD(2,.1,xref_ien,0),"^",2)="ANURS"). MAS has already approved this use of their file, ref. msg #18109934. GENERAL DESCRIPTION: The Nursing, Vitals/Measurements, and Text Generator packages have been granted permission to access the DD global as defined in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23688778 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING PACKAGE: GEN. MED. REC. - GENERATOR ISC: Hines SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 1413 IA #: 1413 FILE NUMBER: 11 GLOBAL ROOT: DIC(11, DATE CREATED: NOV 08, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: MARITAL STATUS ID: DIC(11, GLOBAL REFERENCE: DIC(11,D0, FIELD NUMBER: 2 FIELD NAME: MARITAL STATUS CODE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Nursing has permission to access the Marital Status (11) file as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18115018 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE SUBSCRIBING PACKAGE: CLINICAL REMINDERS NUMBER: 1414 IA #: 1414 FILE NUMBER: 13 GLOBAL ROOT: DIC(13, DATE CREATED: NOV 08, 1995 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: RELIGION ID: DIC(13, CREATOR: KOPP,TERRY M GLOBAL REFERENCE: DIC(13,D0, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: CODE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Nursing has permission to access the Religion (13) file as described in this DBIA. LAB SERVICE will use the NAME (#.01) and CODE (#3) fields in sort and print templates. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 52753965 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING PACKAGE: LAB SERVICE DATE ACTIVATED: SEP 01, 2010 DATE/TIME EDITED: SEP 01, 2010@07:01 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: KOPP,TERRY DATE/TIME EDITED: SEP 01, 2010@09:42 ACTION: APPROVED AT THE REQUEST OF: KOPP,TERRY NUMBER: 1415 IA #: 1415 DATE CREATED: NOV 08, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRYFLW0 NAME: GMRYFLW0 ID: GMRYFLW0 GENERAL DESCRIPTION: Nursing has permission to access the following entry point in the GMRYFLW0 routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135671 COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: This entry point allows user to print the Intravenous Infusion Flow Sheet for a selected time range. VARIABLES: GMRNUR TYPE: Input VARIABLES DESCRIPTION: This variable is passed in with a value of 1 to indicate that the report is requested by the Nursing service. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1417 IA #: 1417 FILE NUMBER: 40.9 GLOBAL ROOT: DIC(40.9, DATE CREATED: JUN 24, 2004 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: LOCATION TYPE ID: DIC(40.9, GLOBAL REFERENCE: DIC(40.9,0) FIELD NUMBER: 1 FIELD NAME: DESIGNATION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Also allowed is direct global read access to the "C" cross-reference of the Designation field on the Location Type file. GENERAL DESCRIPTION: Nursing can access the Location Type (40.9) file as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18113204 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1418 IA #: 1418 DATE CREATED: NOV 13, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - GENERATOR CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRGED1 NAME: GMRGED1 ID: GMRGED1 GENERAL DESCRIPTION: Nursing can reference the GMRGED1 routine as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135646 COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: This entry point allows the user to edit only part of the prime document for a patient, and not the whole document. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient's IEN. VARIABLES: GMRGPDA TYPE: Input VARIABLES DESCRIPTION: Entry in GMR Text file for document where part will be edited. VARIABLES: GMRGRT TYPE: Input VARIABLES DESCRIPTION: Two piece variable indicating prime document for this GMR Text (124.3) file entry. The first piece is the Aggregate Term file pointer of the prime document, the second piece is the text representation of the prime document. VARIABLES: GMRGTERM TYPE: Input VARIABLES DESCRIPTION: Term in which user will start editing patient data. This is starting point of the edit. The data for this variable is two-piece, where the first piece is the Aggregate Term file pointer of the term, and the second piece is the text representation of the term. VARIABLES: GMRGVNAM TYPE: Input VARIABLES DESCRIPTION: Free text patient name. VARIABLES: GMRGVSSN TYPE: Input VARIABLES DESCRIPTION: Patient SSN. VARIABLES: GMRGVDOB TYPE: Input VARIABLES DESCRIPTION: Paitent DOB. VARIABLES: GMRGVAGE TYPE: Input VARIABLES DESCRIPTION: Patient age. VARIABLES: GMRGVAMV TYPE: Input VARIABLES DESCRIPTION: IEN in Patient Movement file for current patient admission information, or null if patient not current inpatient. VARIABLES: GMRGVPRV TYPE: Input VARIABLES DESCRIPTION: Patient provider for current patient admission information, or null if patient not current inpatient. VARIABLES: GMRGVWRD TYPE: Input VARIABLES DESCRIPTION: Inpatient ward for current patient admission information, or null if patient not current inpatient. VARIABLES: GMRGVRBD TYPE: Input VARIABLES DESCRIPTION: Patient room/bed for current patient admission information, or null if patient not current inpatient. VARIABLES: GMRGVADT TYPE: Input VARIABLES DESCRIPTION: Admission date/time for current patient admission information, or null if patient not current inpatient. VARIABLES: GMRGVDX TYPE: Input VARIABLES DESCRIPTION: Patient admitting diagnosis for current patient admission information, or null if patient not current inpatient. VARIABLES: GMRGTOP(0) TYPE: Input VARIABLES DESCRIPTION: This is the current prime document for the level that has been jumped to. For this usage it is just +GMRGRT. VARIABLES: GMRGTOP TYPE: Input VARIABLES DESCRIPTION: GMRGTOP represents how many levels the user has jumped to. In this case Nursing just passes in 1. VARIABLES: GMRGLVL TYPE: Input VARIABLES DESCRIPTION: Current jump level being edited. In this case the value 1 is passed in. VARIABLES: GMRGLVL( TYPE: Input VARIABLES DESCRIPTION: GMRGLVL(GMRGLVL)=Tree level for this jump-level. GMRGLVL(GMRGLVL,GMRGTLVL)=Stack level for this tree level for this jump-level. The GMRGLVL array can be used to address the ^TMP($J,"GMRGLVL", global. This application is passing in GMRGLVL(1)=1, and GMRGLVL(1,1)=1. VARIABLES: GMRGTLVL TYPE: Input VARIABLES DESCRIPTION: Current tree level being processed. This application will pass in the value of 1. VARIABLES: GMRGSLVL TYPE: Input VARIABLES DESCRIPTION: The current stack level being processed. This application passes in 1. VARIABLES: TMP($J,'GMRGLVL', TYPE: Input VARIABLES DESCRIPTION: This global maps the selections and how they were picked. Using GMRGLVL, GMRGTLVL, GMRGSLVL, and GMRGLVL( the order of items selected by the user, or what the user typed at each prompt can be determined. ^TMP($J,"GMRGLVL",GMRGLVL,GMRGTLVL,GMRGSLVL)=A^B^C, where A is the Aggregate Term file entry of term processed, B is action to be performed (add, delete, edit internal text, etc.), and C is a flag whether to redisplay the frame (0) or not (1). ^TMP($J,"GMRGLVL",GMRGLVL,GMRGTLVL,GMRGSLVL)=D^E^F, where D is the free text of the aggregate term being edited, E is the IEN in the Selection multiple of the GMR Text file that represents this term, and F is the appended/internal text currently entered for this term. VARIABLES: GMRGPRC TYPE: Input VARIABLES DESCRIPTION: This variable in represents what the user typed in. This variable has 3 pieces, A^B^C, where A is the IEN of the Aggregate Term the user selected, B is the action the user wants to take (add, delete, edit internal text, etc.), and C is whether the user indicated to redisplay the screen for this term or not. VARIABLES: GMRGPRC(0) TYPE: Input VARIABLES DESCRIPTION: This variable contains three pieces, A^B^C, which contain data about the selection the user made. A is the free text of the Aggregate Term selected, B is the entry number of this term in the Selection multiple of the GMR Text file, and C is the appended/internal text stored for this selection. VARIABLES: GMRGTERM(0) TYPE: Input VARIABLES DESCRIPTION: Zeroth node of the Aggregate Term file for the Aggregate Term used as a starting point. VARIABLES: GMRGSCRP TYPE: Input VARIABLES DESCRIPTION: Current script being executed. This is passed in with a value of 0. VARIABLES: GMRGSITE TYPE: Input VARIABLES DESCRIPTION: The IEN in Package Parameters multiple of GMRG Parameters (124.1) file for the type of prime document being edited. In this case it would be the IEN for the NURSC entry. VARIABLES: GMRGSITE(0) TYPE: Input VARIABLES DESCRIPTION: The zeroth node of the GMRGSITE entry in the Package Parameters multiple of the GMRG Parameters file. VARIABLES: GMRGSITE('P') TYPE: Input VARIABLES DESCRIPTION: The "P"-node for the GMRGSITE entry in the Package Parameters multiple of the GMRG Parameters file. VARIABLES: GMRGSTAT TYPE: Input VARIABLES DESCRIPTION: Information about the last audit trail entry for the Aggregate Term being edited. This is a three piece variable set by STAT^GMRGRUT0 utility. VARIABLES: GMRGIO('RVOF') TYPE: Input VARIABLES DESCRIPTION: Reverse video off executable code for the current terminal used, if it exists. VARIABLES: GMRGIO('RVON') TYPE: Input VARIABLES DESCRIPTION: Reverse video on executable code for the current terminal used, if it exists. VARIABLES: GMRGIO('S') TYPE: Input VARIABLES DESCRIPTION: This is a flag indicating whether the current terminal supports reverse video on/off (1), or not (0). VARIABLES: GMRGLIN('-') TYPE: Input VARIABLES DESCRIPTION: A string of "-"'s with lenght IOM. VARIABLES: GMRGLIN('*') TYPE: Input VARIABLES DESCRIPTION: A string of "*"'s with lenght IOM. VARIABLES: GMRGUP TYPE: Both VARIABLES DESCRIPTION: This variable indicates whether the user hit to bypass last level (1), or not (0). It is passed in with value of 0. VARIABLES: GMRGNORD TYPE: Both VARIABLES DESCRIPTION: This variable indicates whether the user wishes to view this screen upon reentry (0), or not (1). It is passed in as 0. VARIABLES: GMRGOUT TYPE: Both VARIABLES DESCRIPTION: This variable indicates whether the user abnormally exited input (1), or not (0). The variable is passed in with value of 0. VARIABLES: GMRGSEL( TYPE: Output VARIABLES DESCRIPTION: This entry also returns the current list of selections for the frame passed in by GMRGTERM. GMRGSEL(A)=B, where A is the selection number from the screen, and B is a three piece variable where the first piece is the Aggregate Term file IEN for the term represented by this selection, the second piece is the printable text of that Aggregate Term, and the third piece is a flag indicating whether the selection is currently active (1), or not (0). SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1419 IA #: 1419 DATE CREATED: NOV 13, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - GENERATOR CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRGED2 NAME: GMRGED2 ID: GMRGED2 GENERAL DESCRIPTION: Nursing can access the GMRGED2 routine as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135646 COMPONENT/ENTRY POINT: QP COMPONENT DESCRIPTION: This entry point will finish processing for a selection edited. VARIABLES: GMRGTERM TYPE: Input VARIABLES DESCRIPTION: This variable represents the Aggregate Term of the frame being processed and has format A^B^C, where A is the Aggregate Term file IEN, B is the free text representation of this Aggregate Term, and C is the Selection mulitple IEN in the GMR Text file for this entry. VARIABLES: GMRGPDA TYPE: Input VARIABLES DESCRIPTION: This is the GMR Text file entry for this frame. VARIABLES: GMRGSEL( TYPE: Input VARIABLES DESCRIPTION: This is the current list of selections for the frame represented by GMRGTERM. GMRGSEL(A)=B, where A is the selection number from the screen, and B is a three piece variable where the first piece is the Aggregate Term file IEN for the term represented by this selection, the second piece is the printable text of that Aggregate Term, and the third piece is a flag indicating whether the selection is currently active (1), or not (0). VARIABLES: GMRGTERM(0) TYPE: Input VARIABLES DESCRIPTION: The zeroth node of the Aggregate Term represeted in GMRGTERM. VARIABLES: GMRGOUT TYPE: Input VARIABLES DESCRIPTION: Represents whether user abnormally exited processing of this frame (1), or not (0). SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1420 IA #: 1420 DATE CREATED: NOV 13, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - GENERATOR CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRGEDB NAME: GMRGEDB ID: GMRGEDB GENERAL DESCRIPTION: Nursing can access the GMRGEDB routine as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135646 COMPONENT/ENTRY POINT: ADSEL COMPONENT DESCRIPTION: This entry point will add a Selection multiple entry in the GMR Text file for an aggregate term if it does not exist already and then updates the Selection multiple to activate the selection. VARIABLES: GMRGPDA TYPE: Input VARIABLES DESCRIPTION: GMR Text (124.3) file entry. VARIABLES: GMRGPRC TYPE: Input VARIABLES DESCRIPTION: This is a three piece variable representing the Aggregate Term file entry. The first piece is the Aggreage Term file IEN, the second piece is the action the user wishes to perform on this aggregate term, and the final piece indicates whether the user wishes to redisplay this frame after processing it. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1421 IA #: 1421 DATE CREATED: NOV 13, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - GENERATOR CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRGPNBL NAME: GMRGPNBL ID: GMRGPNBL GENERAL DESCRIPTION: Nursing can access the GMRGPNBL routine as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135646 COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: This entry point will return the printable text for an aggregate term and a particular GMR Text entry. VARIABLES: GMRGPDT TYPE: Input VARIABLES DESCRIPTION: Date/time that view of data should be taken from. VARIABLES: GMRGPDA TYPE: Input VARIABLES DESCRIPTION: GMR Text file IEN. VARIABLES: GMRGPAR TYPE: Input VARIABLES DESCRIPTION: Aggregate Term file IEN from where to begin data display. VARIABLES: GMRGPAR(0) TYPE: Input VARIABLES DESCRIPTION: A four piece variable A^B^C^D, where A indicates whether to show active plan data only (1), or to show both active/inactive data (0), B is the number of spaces to leave from right margin, C is the number of spaces to leave from left margin, and D is the subscript to be used by the package making the call in the return array. VARIABLES: TMP($J,'GMRGNAR', TYPE: Output VARIABLES DESCRIPTION: The ^TMP($J,"GMRGNAR", array is returned in the following format: ^TMP($J,"GMRGNAR",A,B,0)=^N, and ^TMP($J,"GMRGNAR",A,B,C)=D, where N is the number of lines of printable text, A is the package subscript passed in the GMRGPAR(0) parameter, B is the Aggregate Term IEN passed in the GMRGPAR parameter, C is a number between 1 and N, and D is a printable line of text. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1422 IA #: 1422 DATE CREATED: NOV 13, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - GENERATOR CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRGRUT0 NAME: GMRGRUT0 ID: GMRGRUT0 GENERAL DESCRIPTION: Nursing can use the GMRGRUT0 routine as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135646 COMPONENT/ENTRY POINT: STAT COMPONENT DESCRIPTION: Get the last audit trail entry for this Selection in the GMR Text file. VARIABLES: GMRGST TYPE: Input VARIABLES DESCRIPTION: IEN of Selection multiple of GMR Text file. VARIABLES: GMRGST(1) TYPE: Input VARIABLES DESCRIPTION: GMR Text file IEN. VARIABLES: GMRGSTAT TYPE: Output VARIABLES DESCRIPTION: This is a three piece variable, A^B^C, where A is the IEN of the Audit Trail entry in the Audit Trail sub-file of the Selection sub-file of the GMR Text file, B is the date/time of the audit trail entry, and C is the modification done in this audit trail entry. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1423 IA #: 1423 DATE CREATED: NOV 13, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - GENERATOR CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRGRUT1 NAME: GMRGRUT1 ID: GMRGRUT1 GENERAL DESCRIPTION: Nursing has permission to use the GMRGRUT1 routine as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135646 COMPONENT/ENTRY POINT: FITLINE COMPONENT DESCRIPTION: This entry point takes text and a length of a line and returns the part of the text that will print in the line, broken at the last word, and the rest of the text not printed. VARIABLES: GMRGPLN TYPE: Input VARIABLES DESCRIPTION: Text to be printed. VARIABLES: GMRGLEN TYPE: Input VARIABLES DESCRIPTION: Length of line to fit text into. VARIABLES: GMRGPLN(0) TYPE: Output VARIABLES DESCRIPTION: The line of text that fits into the specified length. VARIABLES: GMRGPLN(1) TYPE: Output VARIABLES DESCRIPTION: The remainder of the text that did not fit on the line. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1424 IA #: 1424 DATE CREATED: NOV 13, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - GENERATOR CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRGRUT2 NAME: GMRGRUT2 ID: GMRGRUT2 GENERAL DESCRIPTION: Nursing can access the GMRGRUT2 routine as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135646 COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: This entry point will take an aggregate term and return/print the printable version of it. VARIABLES: GMRGXPRT TYPE: Both VARIABLES DESCRIPTION: Aggregate Term file IEN of term to be printed is passed in. If the GMRGXPRT(1) variable indicates to return text in GMRGXPRT, then GMRGXPRT will contain the printable text. VARIABLES: GMRGXPRT(0) TYPE: Input VARIABLES DESCRIPTION: Appended/Internal text to be printed with this aggregate term. VARIABLES: GMRGXPRT(1) TYPE: Input VARIABLES DESCRIPTION: Parameters customizing the print. This is a six piece variable, A^B^C^D^E^F, where A is the number of spaces to indent from left margin, B is the length of the line, C indicates whether to include the brackets for internal text (1) or not (0), D indicates whether to highlight this term (1) or not (0), E indicates whether to print the result (0), or return result in GMRGXPRT variable (1), and F indicates whether to hide text in <> bracktes (1) or not (0). SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1425 IA #: 1425 DATE CREATED: NOV 13, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - GENERATOR CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRGRUT3 NAME: GMRGRUT3 ID: GMRGRUT3 GENERAL DESCRIPTION: Nursing can access the GMRGRUT3 routine as indicated in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135646 COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: This entry point will select an entry from the GMR Text file. VARIABLES: GMRGRT TYPE: Input VARIABLES DESCRIPTION: This variable represents the prime document to be screened for. This is a two-piece variable, A^B, where A is the Aggregate Term file IEN for the prime document, and B is the free text representation of the prime document. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient file IEN. VARIABLES: GMRGXPRT TYPE: Input VARIABLES DESCRIPTION: Parameters to customize lookup. This variable has three pieces, A^B^C, where A indicates whether to look at all (1) or only active (0) data, B indicates whether an entry can be added (1) or not (0), and C indicates whether an entry can be entered in error (1) or not (0). VARIABLES: GMRGPDA TYPE: Output VARIABLES DESCRIPTION: GMR Text file IEN. VARIABLES: GMRGOUT TYPE: Output VARIABLES DESCRIPTION: Flag indicating whether user abnormally exited lookup (1) or not (0). SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1426 IA #: 1426 DATE CREATED: NOV 13, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - GENERATOR CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRGTGIF NAME: GMRGTGIF ID: GMRGTGIF GENERAL DESCRIPTION: Nursing can access the GMRGTGIF routine as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135646 COMPONENT/ENTRY POINT: EN4 COMPONENT DESCRIPTION: This entry point allows the user to enter/edit data in the Aggregate Term file. VARIABLES: GMRGRT TYPE: Input VARIABLES DESCRIPTION: This variable represents the prime document to be screened for. This is a two-piece variable, A^B, where A is the Aggregate Term file IEN for the prime document, and B is the free text representation of the prime document. VARIABLES: GMRGPK TYPE: Input VARIABLES DESCRIPTION: Package reference to indicate which prime document is to be edited. NURSC represents Nursing Care Plan. VARIABLES: GMRGOUT TYPE: Output VARIABLES DESCRIPTION: Flag indicating whether user abnormally exited lookup (1) or not (0). SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1430 IA #: 1430 DATE CREATED: NOV 20, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRYRP1 NAME: GMRYRP1 ID: GMRYRP1 GENERAL DESCRIPTION: Nursing has permission to access the NEXT entry point for the GMRYRP1 routine. Vitals/Measurements is allowed to use the entry STARTD for the GMRYRP1 routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18147230 COMPONENT/ENTRY POINT: NEXT COMPONENT DESCRIPTION: This entry point is called to initialize variables required for the SETSIFT^GMRYRP2 call. VARIABLES: GMRFIN TYPE: Input VARIABLES DESCRIPTION: Date/time the current nursing shift ends. VARIABLES: GLASTDT TYPE: Output VARIABLES DESCRIPTION: Date the day before the date stored in GMRFIN. VARIABLES: GDTSTRT TYPE: Output VARIABLES DESCRIPTION: Date the nursing shift starts. VARIABLES: GNXTDT TYPE: Output VARIABLES DESCRIPTION: Date the day after the date stored in GDTSTRT. VARIABLES: GMRNIT TYPE: Output VARIABLES DESCRIPTION: Time the nursing night shift starts. VARIABLES: GDTFIN TYPE: Output VARIABLES DESCRIPTION: Date the nursing shift ends. COMPONENT/ENTRY POINT: STARTD COMPONENT DESCRIPTION: This entry is called to set up the start date/time and end date/time of information extract according to the nursing shift starting hours defined in the GMRY NUR Shift/Other file (126.95). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN. VARIABLES: GMRSTRT TYPE: Both VARIABLES DESCRIPTION: Input: Start date of information extract. Output: Start date_night shift start hour. VARIABLES: GMRFIN TYPE: Both VARIABLES DESCRIPTION: Input: End date of information extract. Output: End date_evening shift end hour. VARIABLES: GMROUT TYPE: Both VARIABLES DESCRIPTION: Passed in with a value of 0. Returned a value of 1 if exited abnormally. VARIABLES: GRPT TYPE: Input VARIABLES DESCRIPTION: Set to 5 to indicate that the data are requested the V/M Graphic Reports. VARIABLES: GMRNIT TYPE: Input VARIABLES DESCRIPTION: Nursing night shift start hour defined in the GMRY NUR Shift/Other file (126.95). VARIABLES: GMRDAY TYPE: Input VARIABLES DESCRIPTION: Nursing day shift start hour defined in the GMRY NUR Shift/Other file (126.95). VARIABLES: GMREVE TYPE: Input VARIABLES DESCRIPTION: Nursing evening shift start hour defined in the GMRY NUR Shift/Other file (126.95). SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines NUMBER: 1431 IA #: 1431 DATE CREATED: NOV 20, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRVDS0 NAME: GMRVDS0 ID: GMRVDS0 GENERAL DESCRIPTION: Nursing can access the GMRVDS0 routine as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135715 COMPONENT/ENTRY POINT: EN2 COMPONENT DESCRIPTION: This entry point allows user to print latest vital signs for a patient if the patient IEN is unknown. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1432 IA #: 1432 DATE CREATED: NOV 20, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRYUT0 NAME: GMRYUT0 ID: GMRYUT0 GENERAL DESCRIPTION: Vitals/Measurements can access the GMTRYUT0 routine as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18147230 COMPONENT/ENTRY POINT: PT COMPONENT DESCRIPTION: This entry is used to call 1^VADPT to set up VAIN and VADM local variables. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN. VARIABLES: GMRAGE TYPE: Output VARIABLES DESCRIPTION: Age of patient. VARIABLES: GMRBED TYPE: Output VARIABLES DESCRIPTION: Room-bed for patient. VARIABLES: GMRSEX TYPE: Output VARIABLES DESCRIPTION: Patient sex. VARIABLES: GMRVADM TYPE: Output VARIABLES DESCRIPTION: Patient admission date. VARIABLES: GMRWARD TYPE: Output VARIABLES DESCRIPTION: Pointer to Ward Location (42) file denoting patient's location. VARIABLES: GMRWARD(1) TYPE: Output VARIABLES DESCRIPTION: Free text of patient's location. SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines NUMBER: 1433 IA #: 1433 DATE CREATED: NOV 20, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRYUT2 NAME: GMRYUT2 ID: GMRYUT2 GENERAL DESCRIPTION: Nursing can access the following entry point in the GMRYUT2 routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135671 COMPONENT/ENTRY POINT: SELSITE COMPONENT DESCRIPTION: This entry point is called to extract all current intravenous infusion sites and the sites discontinued within the last 24 hours for the selected patient. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN. VARIABLES: GMRX TYPE: Output VARIABLES DESCRIPTION: Local global containing the intravenous infusion site information. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1434 IA #: 1434 DATE CREATED: NOV 20, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRYUT9 NAME: GMRYUT9 ID: GMRYUT9 GENERAL DESCRIPTION: Vitals/Measurements can access the GMRYUT9 routine as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18147230 COMPONENT/ENTRY POINT: PATIENT COMPONENT DESCRIPTION: This entry point extracts information from Nurs Patient (214) file. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN. VARIABLES: GMRNUR TYPE: Input VARIABLES DESCRIPTION: This is set to 1 to indicate return data from Nurs Patient file. VARIABLES: SSN TYPE: Output VARIABLES DESCRIPTION: Patient SSN. VARIABLES: GMRAGE TYPE: Output VARIABLES DESCRIPTION: Patient's age. VARIABLES: GMRSEX TYPE: Output VARIABLES DESCRIPTION: Patient's sex. VARIABLES: GMRBED TYPE: Output VARIABLES DESCRIPTION: Patient's room-bed. VARIABLES: GMRVADM TYPE: Output VARIABLES DESCRIPTION: Patient admission date/time. VARIABLES: GMRWARD TYPE: Output VARIABLES DESCRIPTION: Pointer to Ward Location (42) file denoting patient's location. VARIABLES: GMRWARD(1) TYPE: Output VARIABLES DESCRIPTION: Free text version of patient location. SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines NUMBER: 1435 IA #: 1435 DATE CREATED: NOV 20, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRYRP2 NAME: GMRYRP2 ID: GMRYRP2 GENERAL DESCRIPTION: Nursing and Vitals/Measurements can access the following entry points in the GMRYRP2 routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18147230 COMPONENT/ENTRY POINT: SAVE COMPONENT DESCRIPTION: This entry call extracts the intake and output information and stores the data in ^TMP($J,"GMRY") for a selected patient. VARIABLES: DA(1) TYPE: Input VARIABLES DESCRIPTION: Pointer to the GMRY Patient I/O file (126). VARIABLES: II TYPE: Input VARIABLES DESCRIPTION: Passed in with a value of "IN" or "OUT" subscript of the GMRY Patient I/O file (126). VARIABLES: GMRSTRT TYPE: Input VARIABLES DESCRIPTION: Date/time the current nursing shift starts. VARIABLES: GMRFIN TYPE: Input VARIABLES DESCRIPTION: Date/time the current nursing shift ends. VARIABLES: TMP TYPE: Output VARIABLES DESCRIPTION: ^TMP($J,"GMRY") global contains intake and output information for a selected patient. COMPONENT/ENTRY POINT: SAVEIV COMPONENT DESCRIPTION: This entry call extracts patient intravenous infusion information and stores the data in ^TMP($J,"GMRY") global. VARIABLES: DA(1) TYPE: Input VARIABLES DESCRIPTION: Pointer to the Patient I/O file (126). VARIABLES: GMRSTRT TYPE: Input VARIABLES DESCRIPTION: Date/time the current nursing shift starts. VARIABLES: GMRFIN TYPE: Input VARIABLES DESCRIPTION: Date/time the current nursing shift ends. VARIABLES: TMP TYPE: Output VARIABLES DESCRIPTION: ^TMP($J,"GMRY") global contains the patient intravenous infusion information. COMPONENT/ENTRY POINT: SETSIFT COMPONENT DESCRIPTION: This entry is called to assign the nursing shift (night, day or evening) according to the date/time the I/O data was entered. VARIABLES: GMRINDT TYPE: Input VARIABLES DESCRIPTION: Date/time the I/O data was entered. VARIABLES: GDTSTRT TYPE: Input VARIABLES DESCRIPTION: Date the nursing shift starts. VARIABLES: GDTFIN TYPE: Input VARIABLES DESCRIPTION: Date the nursing shift ends. VARIABLES: GLASTDT TYPE: Input VARIABLES DESCRIPTION: Date the day before the current nursing shift ends. VARIABLES: GSHIFT TYPE: Output VARIABLES DESCRIPTION: Value = "SH-1" night shift, = "SH-2" day shift, = "SH-3" evening shift. COMPONENT/ENTRY POINT: GMRYRP2 COMPONENT DESCRIPTION: This routine is called by the Vitals/Measurements to extract patient intake and output information entered within a selected date range. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN. VARIABLES: GMRSTRT TYPE: Input VARIABLES DESCRIPTION: Start date for the information extract. VARIABLES: GMRFIN TYPE: Input VARIABLES DESCRIPTION: End date for the information extract. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines NUMBER: 1436 IA #: 1436 DATE CREATED: NOV 20, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRYRP3 NAME: GMRYRP3 ID: GMRYRP3 GENERAL DESCRIPTION: Nursing and Vitals/Measurements can access the following entry point in the routine GMRYRP3. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18147230 COMPONENT/ENTRY POINT: REPORT1 COMPONENT DESCRIPTION: The Nursing End of Shift Report calls this entry point to aggregate the data obtained from the execution of SAVE^GMRYRP2 and ^GMRYRP2. The V/M Graphic Reports call this entry point to aggregate data obtained from the execution of STARTD^GMRYRP1, PT^GMRYUT0 and ^GMRYRP2. VARIABLES: GRPT TYPE: Input VARIABLES DESCRIPTION: Type of intake/output report. Set GRPT = 10 for the Nursing End of Shift Report. Set GRPT = 5 for the V/M Graphic Reports. VARIABLES: GQ TYPE: Input VARIABLES DESCRIPTION: Passed in with a value of 0, required by the GMRYRP3 routine. VARIABLES: GQT TYPE: Input VARIABLES DESCRIPTION: Passed in with a value of 0, required by the GMRYRP3 routine. VARIABLES: GMROUT TYPE: Both VARIABLES DESCRIPTION: This variable indicates whether the user abnormally exited the process. It is passed in with a value of 0. VARIABLES: TMP TYPE: Both VARIABLES DESCRIPTION: ^TMP($J,"GMRY") contains the intake, output and intravenous infusion data for a patient. If the data is requested by the Vitals/Measurements, ^TMP($J,"GMR") is also used to store the aggregated information. VARIABLES: GTOTLI TYPE: Output VARIABLES DESCRIPTION: Intake grand total. VARIABLES: GTOTLO TYPE: Output VARIABLES DESCRIPTION: Output grand total. VARIABLES: GN(1) TYPE: Output VARIABLES DESCRIPTION: Number of intake types listed in the GMRY Input Type file (126.56). VARIABLES: GN(2) TYPE: Output VARIABLES DESCRIPTION: Number of output types listed in the GMRY Output Type file (126.58). VARIABLES: GIN TYPE: Output VARIABLES DESCRIPTION: Intake nursing shift total. VARIABLES: GOUT TYPE: Output VARIABLES DESCRIPTION: Output nursing shift total. VARIABLES: GTOTIN TYPE: Output VARIABLES DESCRIPTION: Intake day total. VARIABLES: GTOTOUT TYPE: Output VARIABLES DESCRIPTION: Output day total. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines NUMBER: 1437 IA #: 1437 DATE CREATED: NOV 21, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRYSE0 NAME: GMRYSE0 ID: GMRYSE0 GENERAL DESCRIPTION: Nursing can access the following entry point in the GMRYSE0 routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135671 COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: This entry point allows user to print the Patient Intake/Output 24 Hours Itemized Shift Report for a time range. VARIABLES: GMRNUR TYPE: Input VARIABLES DESCRIPTION: This variable is passed in with a value of 1 to indicate that the report is requested by the Nursing Service. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1438 IA #: 1438 DATE CREATED: NOV 21, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRYSE3 NAME: GMRYSE3 ID: GMRYSE3 GENERAL DESCRIPTION: Nursing can access the following entry point in the GMRYSE3 routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135671 COMPONENT/ENTRY POINT: FITLINE COMPONENT DESCRIPTION: This utility breaks a line of text into lines. The length of the new line is defined by user. VARIABLES: GMRLEN TYPE: Input VARIABLES DESCRIPTION: Number of characters for a line of text. VARIABLES: GTXT(0) TYPE: Output VARIABLES DESCRIPTION: The first n-words of the input text in the GTXT(1) that will fit in length GMRLEN. VARIABLES: GTXT(1) TYPE: Both VARIABLES DESCRIPTION: The rest of the text. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1439 IA #: 1439 DATE CREATED: NOV 21, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRVDS1 NAME: GMRVDS1 ID: GMRVDS1 GENERAL DESCRIPTION: Nursing can access the following entry point in the GMRVDS1 routine as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135715 COMPONENT/ENTRY POINT: EN3 COMPONENT DESCRIPTION: This entry point allows user to print the latest vital signs by a Nursing location. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN. VARIABLES: TMP TYPE: Input VARIABLES DESCRIPTION: ^TMP($J,patient room-bed,patient name,DFN) global contains the patients for the report. VARIABLES: GMRVWLO TYPE: Input VARIABLES DESCRIPTION: Free text version of Nursing ward location. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1440 IA #: 1440 DATE CREATED: NOV 22, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRVED0 NAME: GMRVED0 ID: GMRVED0 GENERAL DESCRIPTION: Nursing can access the following entry points described in this DBIA for the GMRVED0 routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135715 COMPONENT/ENTRY POINT: EN3 COMPONENT DESCRIPTION: This entry point allows user to enter vitals/measurements for a patient. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN. VARIABLES: GMROUT TYPE: Both VARIABLES DESCRIPTION: This variable indicates whether the user abnormally exited the input process. It is passed in with a value of 0. VARIABLES: GNUROP TYPE: Input VARIABLES DESCRIPTION: This variable is passed in with a value of 1 to indicates that the edit process is requested by the Nursing Service. VARIABLES: GMRVIDT TYPE: Input VARIABLES DESCRIPTION: The date/time the vitals/measurements were taken. VARIABLES: GMRVHLOC TYPE: Input VARIABLES DESCRIPTION: Hospital Location file (44) pointer. VARIABLES: GMRENTY TYPE: Input VARIABLES DESCRIPTION: The type of vitals/measurements to edit. VARIABLES: GMRSTR TYPE: Input VARIABLES DESCRIPTION: The string of which vitals/measurements to edit, for example, "T;P;R;BP;WT;". COMPONENT/ENTRY POINT: Q COMPONENT DESCRIPTION: This entry point is called to clean up the variables used by the GMRVED0. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1441 IA #: 1441 DATE CREATED: NOV 22, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRVEE0 NAME: GMRVEE0 ID: GMRVEE0 GENERAL DESCRIPTION: Nursing can access the following entry point described in this DBIA for the GMRVEE0 routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135715 COMPONENT/ENTRY POINT: EN2 COMPONENT DESCRIPTION: This entry point allows user to edit a vital/measurement entered in error. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1442 IA #: 1442 DATE CREATED: NOV 22, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRVER0 NAME: GMRVER0 ID: GMRVER0 GENERAL DESCRIPTION: Nursing can access the following entry point described in this DBIA for the GMRVER0 routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135715 COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: This entry point allows user to print vitals/measurements entered in error for a patient. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1443 IA #: 1443 DATE CREATED: NOV 22, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRVSAS0 NAME: GMRVSAS0 ID: GMRVSAS0 GENERAL DESCRIPTION: Nursing can access the following entry point described in this DBIA for the GMRVSAS0 routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135715 COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: This entry point is called for checking the abnormal vital/measurement. VARIABLES: GMRVX TYPE: Input VARIABLES DESCRIPTION: This variable is passed in with a value of "T", "P", "R", "B" or "BP" as vital type code. VARIABLES: GMRVX(0) TYPE: Input VARIABLES DESCRIPTION: This variable contains vital data for the screening. VARIABLES: GMRVX(1) TYPE: Output VARIABLES DESCRIPTION: If the output value equals 0 - vital data within normal range. If the output value equals 1 - abnormal value defined in the GMRV Vitals Parameters file (125.57). SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING PACKAGE: BAR CODE MED ADMIN NUMBER: 1444 IA #: 1444 DATE CREATED: NOV 22, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRVSC0 NAME: GMRVSC0 ID: GMRVSC0 GENERAL DESCRIPTION: Nursing can access the following entry points described in this DBIA for the GMRVSC0 routine. 12/17/2003: Modified this IA to add the EN3 entry point. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 37627129 COMPONENT/ENTRY POINT: DATE COMPONENT DESCRIPTION: This entry point allows user to define start date/time and end date/time for a date range. VARIABLES: GMROUT TYPE: Both VARIABLES DESCRIPTION: This variable indicates whether the user abnormally exited the call. It is passed in with a value of 0. VARIABLES: GMRVSDT TYPE: Output VARIABLES DESCRIPTION: Start date/time of the date range. VARIABLES: GMRVFDT TYPE: Output VARIABLES DESCRIPTION: End date/time of the date range. COMPONENT/ENTRY POINT: EN5 COMPONENT DESCRIPTION: This entry point allows user to print cumulative vitals/measurements for a patient over a given date range. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN. VARIABLES: GMRX TYPE: Input VARIABLES DESCRIPTION: Patient admission date/time. VARIABLES: GMROUT TYPE: Both VARIABLES DESCRIPTION: This variable indicates whether the user abnormally exited the report process. It is passed in with a value of 0. VARIABLES: GMRVSDT TYPE: Input VARIABLES DESCRIPTION: Start date/time of the date range. VARIABLES: GMRVFDT TYPE: Input VARIABLES DESCRIPTION: End date/time of the date range. VARIABLES: GMRPG TYPE: Input VARIABLES DESCRIPTION: This report page count is initialized with a value of 0. COMPONENT/ENTRY POINT: EN3 COMPONENT DESCRIPTION: This entry point displays the patient cumulative report to the current output device. D EN3^GMRVSC0(DFN,GMRVSDT,GMRVFDT) VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient internal entry number (FILE 2). (Required) VARIABLES: GMRVSDT TYPE: Input VARIABLES DESCRIPTION: Start date/time of the date range in FileMan internal format. (Required) VARIABLES: GMRVFDT TYPE: Input VARIABLES DESCRIPTION: End date/time of the date range in FileMan internal format. (Required) SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING PACKAGE: BAR CODE MED ADMIN ISC: Birmingham NUMBER: 1445 IA #: 1445 DATE CREATED: NOV 22, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRVSR0 NAME: GMRVSR0 ID: GMRVSR0 GENERAL DESCRIPTION: Nursing can access the following entry points described in this DBIA for the GMRVSR0 routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135715 COMPONENT/ENTRY POINT: EN5 COMPONENT DESCRIPTION: User can use this entry point to print V/M Graphic Reports, Vital Signs Record, B/P Plotting Chart or Weight Chart. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN. VARIABLES: GFLAG TYPE: Input VARIABLES DESCRIPTION: This variable is passed in with a value of 0 to indicate that the report is requested by the Nursing Service. VARIABLES: GMRDATE TYPE: Input VARIABLES DESCRIPTION: This variable is passed in with a value of "start date/time^end date/time^type of graph". VARIABLES: GMRVWLO TYPE: Input VARIABLES DESCRIPTION: Nursing location free text. COMPONENT/ENTRY POINT: Q2 COMPONENT DESCRIPTION: This entry point is called to clean up the variables used for the graphic reports. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1446 IA #: 1446 DATE CREATED: NOV 28, 2006 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRVUT0 NAME: GMRVUT0 ID: GMRVUT0 CREATOR: TRAXLER,FRANK GENERAL DESCRIPTION: This routine will return vital/measurement for a patient over a given date/time range. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: User can use this entry to gather patient vital/measurement data. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN. VARIABLES: GMRVSTR TYPE: Input VARIABLES DESCRIPTION: Types of vitals/measurements desired. Use the abbreviations found in the GMRV Vital Type file (120.51). For multiple vitals, use the ; as a delimiter, for example, "T;P;R;BP;". VARIABLES: GMRVSTR(0) TYPE: Input VARIABLES DESCRIPTION: This variable specifies which vital/measurement data will be returned. The variable has four pieces, A^B^C^D, where: A=Start date/time (FM format) of vital/measurment data to be returned. B=End date/time (FM format) of vital/measurement data to be returned. C=Number of occurences (numeric) of vital/measurement data to be returned. D=Parameter to govern sort order of return array. The value of this piece can either be 0 or 1. If it is 0, the return data will be sorted by type, then by date/time entered. If it is 1, the return data will be sorted by date/time entered, then by type. See output variable ^UTILITY for more information. VARIABLES: UTILITY TYPE: Output VARIABLES DESCRIPTION: The output array is ^UTILITY($J,"GMRVD"). The subscripts of this array are governed by the 4th piece of the input variable GMRVSTR(0). If $P(GMRVSTR(0),"^",4) is true, the return array will be ^UTILITY($J,"GMRVD",RDT,TYP,IEN)=DATA If $P(GMRVSTR(0),"^",4) is false, the return array will be: ^UTILITY($J,"GMRVD",TYP,RDT,IEN)=DATA In the above, the following abbreviations translate as follows: RDT = Reverse date/time vital/measurement was taken in format 9999999-(Date/time taken). TYP = Abbreviation of vital/measurement type from GMRVSTR variable. IEN = Entry in GMRV Vital/Measurement (120.5) file of this data. DATA = Data about this vital/measurement with the following format, VDT^DFN^ITYP^EDT^LOC^USER^ISITE^RATE^IQUAL^SITE^QUAL^ABN^UNIT^ BMI^LO2^PO2^AQUAL where: VDT = Date/time vital/measurement taken (FM format) DFN = IEN for patient in Patient file. ITYP = IEN for vital type in GMRV Vital Type file. EDT = Date/time vital/measurement entered (FM format) LOC = IEN for patient location in Hospital Location file. USER = User who entered data; IEN in New Person file. ISITE = IEN for site in GMRV Vital Site file. RATE = Rate for this vital/measurement (alphanumeric). IQUAL = IEN for quality in GMRV Vital Quality file. SITE = Site of vital/measurement (free text). QUAL = Quality of vital/measurement (free text). ABN = Flag indicating whether vital/measurement is abnormal. * indicates abnormal, null indicates normal. UNIT = Units of measurement for rate when appropriate, e.g. Centigrade for temperature, Kg for weight and centimeter for height. BMI = Body Mass Index (numeric);value calculated from height; (Applies only to the vital type WT (Weight)) LO2 = Liters/Minute of supplemental O2 (numeric). (Applies only to the vital type PO2 (Pulse Oximetry)). PO2 = % of supplemental O2 (numeric). (Applies only to the vital type PO2 (Pulse Oximetry)). AQUAL = All qualifiers (free text); Each qualifier is separated by a ;. VARIABLES: GMRVSTR('L') TYPE: Input VARIABLES DESCRIPTION: This is an optional variable. It will be set to an ^ delimited list of Hospital Location Types, see Type (2) field of Hospital Location (44) file for a list of types. The first piece and last piece of the list must be null, i.e., ^C^M^. SUBSCRIBING PACKAGE: NURSING SERVICE SUBSCRIBING PACKAGE: HEALTH SUMMARY SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: MYHEALTHEVET SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: SURGERY SUBSCRIBING DETAILS: added 12/15/08 SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: JSH 20061128/Approved as per Frank Traxler. 5/25/12-VPR added as a subscriber for VPR*1.0. 3/2/15-MC: Added VPS as a subscriber at the request of Linda Berry and approval of Frank Traxler for VPS*1*15,After Visit Summary (AVS). DATE/TIME EDITED: NOV 13, 2006@16:19 ACTION: APPROVED AT THE REQUEST OF: HENDERSON,MIKE WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: DEC 15, 2008@10:08 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MONOSKY,ALAN WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: APR 12, 2007@13:18 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: TRAXLER,FRANK DATE/TIME EDITED: SEP 16, 2010@10:57 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE DATE/TIME EDITED: MAY 25, 2012@09:57 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: MAY 25, 2012@09:58 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BERRY,LINDA WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: MAR 02, 2015@14:04 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BERRY,LINDA WITH CONCURRENCE OF: TRAXLER,FRANK NUMBER: 1447 IA #: 1447 DATE CREATED: NOV 22, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRVUT2 NAME: GMRVUT2 ID: GMRVUT2 GENERAL DESCRIPTION: Nursing can access the following entry point described in this DBIA for the GMRVUT2 routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135715 COMPONENT/ENTRY POINT: SETU2 COMPONENT DESCRIPTION: This entry is used to extract the last weight measurement for a patient. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN. VARIABLES: GMRVSTR TYPE: Input VARIABLES DESCRIPTION: GMRVSTR(0) is passed in with a value of "^^1^1". GMRVSTR("T") is passed in with the abbreviation "WT" found in the GMRV Vital Type file (120.51). GMRVSTR("IEN") is passed in with a GMRV Vital Measurement file (120.5) pointer. GMRVSTR("R") is passed in with the date/time the weight was measured. VARIABLES: UTILITY TYPE: Output VARIABLES DESCRIPTION: The output array ^UTILITY($J,"GMRD") contains the desired patient weight. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1448 IA #: 1448 DATE CREATED: NOV 22, 1995 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRVVS0 NAME: GMRVVS0 ID: GMRVVS0 GENERAL DESCRIPTION: Nursing can access the following entry points described in this DBIA for the GMRVVS0 routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18135715 COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: This entry point is used to print the Expanded SF 511 Report (Itemized I/O). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN. VARIABLES: GFLAG TYPE: Input VARIABLES DESCRIPTION: This variable is passed in with a value of 0 to indicate that the report is requested by the Nursing Service. VARIABLES: GMROUT TYPE: Both VARIABLES DESCRIPTION: This variable indicates whether the user abnormally exited the report process. It is passed in with a value of 0. VARIABLES: GMRNUR TYPE: Input VARIABLES DESCRIPTION: This variable is set to a value of 0 to indicate that the proces is requested by the Nursing Service. VARIABLES: GMRSTRT TYPE: Input VARIABLES DESCRIPTION: Start date/time for the report. VARIABLES: GMRFIN TYPE: Input VARIABLES DESCRIPTION: End date/time for the report. COMPONENT/ENTRY POINT: DATE COMPONENT DESCRIPTION: User can use this entry to set up start date/time and end date/time for the report desired. VARIABLES: GMROUT TYPE: Both VARIABLES DESCRIPTION: This variable indicates whether the user abnormally exited the process. It is passed in with a value of 0. VARIABLES: GMRSTRT TYPE: Output VARIABLES DESCRIPTION: Start date/time user entered. VARIABLES: GMRFIN TYPE: Output VARIABLES DESCRIPTION: End date/time user entered. COMPONENT/ENTRY POINT: Q2 COMPONENT DESCRIPTION: This entry point is called to clean up the variables used by the GMRVVS0 routine. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1449 IA #: 1449 DATE CREATED: DEC 07, 1995 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: CHANGE PACKAGE FILE ENTRY GENERAL DESCRIPTION: The Allergy Tracking System package is changing its name to Adverse Reaction Tracking when the next version (4.0) is released. The Expert Panel feels this is a more accurate name for what the package does. When Version 4.0 is installed, the environmental check routine will do a look-up (using a DBS call) on the 'C' cross-reference of the PACKAGE file (#9.4) to find the appropriate entry and change the .01 field value to 'ADVERSE REACTION TRACKING'. The package's namespace is GMRA. Also, the PACKAGE file entry contains the old name and version number as data in the SHORT DESCRIPTION (#2) and DESCRIPTION (#3) fields. Leaving that data in the File 9.4 entry would confuse IRM support personnel. We request permission to edit these two fields, via FileMan, in the environment check routine at the time of installation. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18944240 GOOD ONLY FOR VERSION: 4 SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING ISC: Hines NUMBER: 1450 IA #: 1450 FILE NUMBER: 0 GLOBAL ROOT: DD( DATE CREATED: DEC 13, 1995 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DELETE X-REF ON .01 FIELD OF FILE 120.8 ID: DD( GLOBAL REFERENCE: DD(120.8,.01,1,D0 GLOBAL DESCRIPTION: Direct global read/kill to loop through the cross-reference multiple of the .01 field of File 120.8 to find and kill the ANKA01 cross-reference. D0 is the cross-reference internal entry number. GLOBAL REFERENCE: DD(120.8,.01,1,D0,0) GLOBAL DESCRIPTION: Direct global read of the second piece of the zero node to determine the cross-reference name. D0 is the internal entry number of the cross-reference. GLOBAL REFERENCE: DD(120.8,0,'IX','ANKA01',120.8,.01) GLOBAL DESCRIPTION: Direct kill of this node. GENERAL DESCRIPTION: With the release of Adverse Reaction Tracking v4.0, we would like to directly kill the "ANKA01" cross-reference on the .01 field of File 120.8. In our installation process, we will do the following: STATUS: Active DURATION: Next Version MAIL MESSAGE: 18489203 GOOD ONLY FOR VERSION: 4.0 SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING ISC: Hines NUMBER: 1451 IA #: 1451 DATE CREATED: JAN 03, 1996 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RCJIBFN1 NAME: DBIA1451 ID: RCJIBFN1 GENERAL DESCRIPTION: The following calls are made to routine RCJIBFN1 and are used to display bill transaction information. Each call returns data on a specific entry in the AR TRANSACTION FILE (#433). All data is returned in internal/unformated form unless otherwise stated. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18846024 COMPONENT/ENTRY POINT: $$N0(X) COMPONENT DESCRIPTION: Returns a string of information about the transaction requested: $p1: Transaction Number $p2: Date Calm Done $p3: Processed By (pointer to file #200) $p4: Text message indicating if transaction is 'INCOMPLETE' Returns null if no transaction found. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Internal File Number of a transaction in file #433. COMPONENT/ENTRY POINT: $$N1(X) COMPONENT DESCRIPTION: Returns a string of information about the transaction requested: $p1: Transaction Date $p2: Transaction Type (pointer to file #430.3) $p3: Receipt # $p4: Adjustment Number $p5: Transaction Amount $p6: Termination Reason (external form) $p7: Date Entered Returns null if no transaction found. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Internal File Number of a transaction in file #433. COMPONENT/ENTRY POINT: $$N2(X) COMPONENT DESCRIPTION: Returns a string of information about the transaction requested: $p1: IRS Loc. Cost $p2: Credit Rep Cost $p3: DMV Loc. Cost $p4: Consumer Rep. Agency Cost $p5: Marshal Fee $p6: Court Cost $p7: Interest Cost $p8: Administrative Cost Returns null if no transaction found. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Internal File Number of a transaction in file #433. COMPONENT/ENTRY POINT: $$N3(X) COMPONENT DESCRIPTION: Returns a string of information about the transaction requested: $p1: Principal Collected $p2: Interest Collected $p3: Admin. Collected $p4: Marshal Fee Collected $p5: Court Cost Collected $p6: Total collected for this transaction Returns null if no transaction found. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Internal File Number of a transaction in file #433. COMPONENT/ENTRY POINT: N4(X) VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Internal File Number of a transaction in file #433. VARIABLES: STRG TYPE: Output VARIABLES DESCRIPTION: Defined with a null value only if no data or transaction was found. VARIABLES: STRG(I) TYPE: Output VARIABLES DESCRIPTION: Array containing an entry for each fiscal year associated with the bill, where (I) is a simple 1:1 counter. $p1: Fiscal Year $p2: Principal Amount $p3: Pat Reference # $p4: Transaction Amount Defined on exit only if data was found. COMPONENT/ENTRY POINT: $$N5(X) COMPONENT DESCRIPTION: Returns a string of information about the transaction requested: $p1: Brief Comment $p2: Follow-up Date Returns null if no transaction found. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Internal File Number of a transaction in file #433. COMPONENT/ENTRY POINT: N7(X) VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Internal File Number of a transaction in file #433. VARIABLES: COM(I) TYPE: Output VARIABLES DESCRIPTION: Array containing the transaction Comments, where (I) is a simple 1:1 counter. Defined on exit only if data was found. COMPONENT/ENTRY POINT: $$N8(X) COMPONENT DESCRIPTION: Returns a string of information about the transaction requested: $p1: Principle Balance $p2: Interest Balance $p3: Admin Balance $p4: Marshal Fee $p5: Court Cost $p6: Total account balance after transaction is applied $p7: Transaction Comments Returns null if no transaction found. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Internal File Number of a transaction in file #433. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 1452 IA #: 1452 DATE CREATED: JAN 04, 1996 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RCJIBFN2 NAME: DBIA1452 ID: RCJIBFN2 GENERAL DESCRIPTION: The following calls are made to routine RCJIBFN2. The AR specific information returned for a bill/claim is displayed in Third Party Joint Inquiry. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26240276 COMPONENT/ENTRY POINT: $$TRAN(X) COMPONENT DESCRIPTION: Returns the AR Transaction Type Name. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Pointer to a transaction type in the ACCOUNTS RECEIVABLE TRANS.TYPE file (#430.3). COMPONENT/ENTRY POINT: $$STNO(X) COMPONENT DESCRIPTION: Returns a string of information about the transaction type requested: $p1: Name $p2: Abbreviation $p3: Status Number VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Pointer to a transaction type in the ACCOUNTS RECEIVABLE TRANS.TYPE file (#430.3). COMPONENT/ENTRY POINT: $$STAT(X) COMPONENT DESCRIPTION: Returns Current Status of the bill in AR. This is a pointer to a transaction type in the ACCOUNTS RECEIVABLE TRANS.TYPE file (#430.3). VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Pointer to a bill in the ACCOUNTS RECEIVABLE file (#430). COMPONENT/ENTRY POINT: TRN(X) COMPONENT DESCRIPTION: Returns a string of information on each transaction asscociated with the bill passed in. The output is passed in ^TMP("RCJIB",$J,Y), hwere Y is a pointer to the transaction in the AR TRANSACTION file (#433). $p1: Transaction Number $p2: Transaction Date $p3: Transaction Type (pointer to file #430.3) $p4: Transaction Amount $p5: Amount Due for bill after transaction is applied $p6: Transaction Comments VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Pointer to a bill in the ACCOUNTS RECEIVABLE file (#430). COMPONENT/ENTRY POINT: $$BILL(X) COMPONENT DESCRIPTION: Returns a string of information about the bill requested: $p1: Original Amount of bill $p2: Current Status (pointer to file #430.3) $p3: Current Balance $p4: Total Collected $p5: % Collected Returns null if no data or bill found. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Pointer to a bill in the ACCOUNTS RECEIVABLE file (#430). COMPONENT/ENTRY POINT: BCOM(X) VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Pointer to a bill in the ACCOUNTS RECEIVABLE file (#430). VARIABLES: COM TYPE: Output VARIABLES DESCRIPTION: String containing the following if data was found: $p1: Approved By (Fiscal) (pointer to file #200) $p2: AR Date Signed String will be null if no data found. VARIABLES: COM(I) TYPE: Output VARIABLES DESCRIPTION: Array containing the bill's Comments, where (I) is a simple 1:1 counter. Will only be defined if bill has comments. COMPONENT/ENTRY POINT: DIQ(X1,X2,.X3) COMPONENT DESCRIPTION: This call is needed to return internal and external field values from the Accounts Receivable File 430. The format of the fields will be the output of Fileman's EN^DIQ1 call. VARIABLES: X1 TYPE: Input VARIABLES DESCRIPTION: Internal entry number of File 399 and DINUMED File 430. VARIABLES: X2 TYPE: Input VARIABLES DESCRIPTION: String of File 430 field numbers in the DR format used by Fileman's EN^DIQ1 call. VARIABLES: X3 TYPE: Input VARIABLES DESCRIPTION: Array name to be used to return the internal and external value of the fields sent in X2. VARIABLES: X3 TYPE: Output VARIABLES DESCRIPTION: The array name in X3 will contain the value of the fields sent in X2 as returned by EN^DIQ1. i.e. if X3="ARRAY" ARRAY(430,IEN,Field#,"I")=internal value ARRAY(430,IEN,Field#,"E")=external value SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 1453 IA #: 1453 DATE CREATED: JAN 04, 1996 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RCJIBFN3 NAME: DBIA1453 ID: RCJIBFN3 GENERAL DESCRIPTION: This call is used by the Third Party Joint Inquiry to allow the person viewing a bill to add a comment transaction to the AR bill record. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18846024 COMPONENT/ENTRY POINT: ADJUST(X) COMPONENT DESCRIPTION: Allows addition of a comment transaction to an AR account. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Pointer to a bill in the ACCOUNTS RECEIVABLE file (#430). SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 1457 IA #: 1457 DATE CREATED: JAN 12, 1996 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA1457 GENERAL DESCRIPTION: Third Party Joint Inquiry Menu [IBJ THIRD PARTY JOINT INQUIRY] will be added to the Agent Cashier [PRCAY MASTER] and Clerk's AR Menu [PRCA CLERK MENU]. This will be done by running the PRYQINIT init routine in patch PRCA*4.5*15. STATUS: Active MAIL MESSAGE: 19152106 COMPONENT/ENTRY POINT: N/A VARIABLES: N/A SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 1458 IA #: 1458 FILE NUMBER: 126.76 GLOBAL ROOT: GMRD(126.76, DATE CREATED: JAN 17, 1996 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMRY IV DC'ED REASON ID: GMRD(126.76, GLOBAL REFERENCE: GMRD(126.76,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Nursing is allowed to LAYGO entries into the file using FileMan. GENERAL DESCRIPTION: Nursing has permission to access the following field in the GMRY IV DC'ed Reason (126.76) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18918135 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1459 IA #: 1459 FILE NUMBER: 126.6 GLOBAL ROOT: GMRD(126.6, DATE CREATED: JAN 17, 1996 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMRY OUTPUT SUBTYPE ID: GMRD(126.6, GLOBAL REFERENCE: GMRD(126.6,D0,0) FIELD NUMBER: .01 FIELD NAME: OUTPUT SUBTYPE LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Also Nursing is allowed to LAYGO entries into the file using FileMan. FIELD NUMBER: 1 FIELD NAME: OUTPUT TYPE LOCATION: 0;2 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: Nursing has permission to access the following fields in the GMRY Output Subtype (126.6) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18918204 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1460 IA #: 1460 FILE NUMBER: 126.8 GLOBAL ROOT: GMRD(126.8, DATE CREATED: JAN 17, 1996 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMRY INTAKE ITEMS ID: GMRD(126.8, GLOBAL REFERENCE: GMRD(126.8,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Also Nursing is allowed to LAYGO entries into the file using FileMan. FIELD NUMBER: 1 FIELD NAME: VOLUME LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: 2 FIELD NAME: INPUT TYPE LOCATION: 1;0 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Also Nursing is allowed to LAYGO into multiple using FileMan. GLOBAL REFERENCE: GMRD(126.8,D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: INPUT TYPE LOCATION: 0;1 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: Nursing has permission to access the following fields in the GMRY Intake Items (126.8) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18918229 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1461 IA #: 1461 FILE NUMBER: 126.7 GLOBAL ROOT: GMRD(126.7, DATE CREATED: JAN 17, 1996 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMRY IV SITE ID: GMRD(126.7, GLOBAL REFERENCE: GMRD(126.7,D0,0) FIELD NUMBER: .01 FIELD NAME: IV SITE LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Also Nursing is allowed to LAYGO entries into the file using FileMan. GENERAL DESCRIPTION: Nursing has permission to access the following field in the GMRY IV Site (126.7) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18918239 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1462 IA #: 1462 FILE NUMBER: 126.9 GLOBAL ROOT: GMRD(126.9, DATE CREATED: JAN 18, 1996 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMRY NUR IV SOLUTION ID: GMRD(126.9, GLOBAL REFERENCE: GMRD(126.9,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Also Nursing is allowed to LAYGO entries into the file using FileMan. FIELD NUMBER: 1 FIELD NAME: TYPE LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: 2 FIELD NAME: VOLUME LOCATION: 0;3 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: Nursing has permission to access the following fields in the GMRY NUR IV Solution (126.9) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18918262 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1463 IA #: 1463 FILE NUMBER: 126.56 GLOBAL ROOT: GMRD(126.56, DATE CREATED: JAN 18, 1996 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMRY INPUT TYPE ID: GMRD(126.56, GLOBAL REFERENCE: GMRD(126.56,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Also Nursing is allowed to LAYGO entries into the file using FileMan. FIELD NUMBER: 1 FIELD NAME: ORDER LOCATION: 0;2 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: Nursing has permission to access the following fields in the GMRY Input Type (126.56) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18918284 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1464 IA #: 1464 FILE NUMBER: 126.72 GLOBAL ROOT: GMRD(126.72, DATE CREATED: JAN 18, 1996 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMRY IV SITE DESCRIPTION ID: GMRD(126.72, GLOBAL REFERENCE: GMRD(126.72,D0,0) FIELD NUMBER: .01 FIELD NAME: DESCRIPTION LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Also Nursing is allowed to LAYGO entries into the file using FileMan. GENERAL DESCRIPTION: Nursing has permission to access the following field in the GMRY IV Site Description (126.72) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18918303 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1465 IA #: 1465 FILE NUMBER: 126.74 GLOBAL ROOT: GMRD(126.74, DATE CREATED: JAN 18, 1996 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMRY IV CATHETER ID: GMRD(126.74, GLOBAL REFERENCE: GMRD(126.74,D0,0) FIELD NUMBER: .01 FIELD NAME: IV CATHETER TYPE/SIZE LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Also Nursing is allowed to LAYGO entries into the file using FileMan. GENERAL DESCRIPTION: Nursing has permission to access the following field in the GMRY IV Catheter (126.74) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18918331 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1466 IA #: 1466 FILE NUMBER: 126.58 GLOBAL ROOT: GMRD(126.58, DATE CREATED: JAN 18, 1996 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMRY OUTPUT TYPE ID: GMRD(126.58, GLOBAL REFERENCE: GMRD(126.58,D0,0) FIELD NUMBER: .01 FIELD NAME: OUTPUT TYPE LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Also Nursing is allowed to LAYGO entries into the file using FileMan. FIELD NUMBER: 1 FIELD NAME: ORDER LOCATION: 0;2 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: Nursing has permission to access the following fields in the GMRY Output Type (126.58) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18918340 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1467 IA #: 1467 DATE CREATED: JAN 19, 1996 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: GMRA ENTERED IN ERROR PROTOCOL CREATOR: BUECHLER,MELANIE K GENERAL DESCRIPTION: This extended action protocol is created with v4.0 and is invoked whenever an allergy/adverse reaction for a patient is marked as 'entered-in-error'. Action protocols from other applications may be added to this event upon approval of the DBIC. Listed below are the variables that will be defined for that reaction. Variables: GMRAPA = The Internal Entry Number of the reaction in File 120.8 (PATIENT ALLERGIES) GMRAPA(0) = The zero node of the entry in File 120.8. Below is a description of the data for that node. $P Field name Field type ----------------------------------------------------------- 1 PATIENT Pointer to File 2 (PATIENT) 2 REACTANT Free Text of Reaction 3 GMR ALLERGY Variable Pointer * 4 ORIGINATION DATE/TIME Date/Time (FM format) 5 ORIGINATOR Pointer to File 200 (NEW PERSON) 6 OBSERVED/HISTORICAL Set of Codes (o=Observed,h=Historical) 12 ORIGINATOR SIGN OFF Set of Codes (1=Signed,(Zero or Null)=Unsigned) 14 MECHANISM Set of Codes (U=Unknown, P=Pharmacologic,A=Allergy) 16 VERIFIED Set of Codes (1=Verified,(0 or Null)=Not Verified) 17 VERIFICATION DATE/TIME Date/Time (FM format) 18 VERIFIER Pointer to File 200 20 ALLERGY TYPE Free Text/Set of Codes 1 to 3 characters long (Where "D" = Drug, "F" = Food, "O" = Other) *The GMR ALLERGY field is a variable pointer which points to one of five possible files. They are: File Name File Reference --------- -------------- GMR ALLERGIES GMR(120.8, (e.g., 212;GMR(120.8,) NATIONAL DRUG PSNDF( DRUG PSDRUG( DRUG INGREDIENTS PS(50.416, VA DRUG CLASS PS(50.605, STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19235122 SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: SURGERY SUBSCRIBING DETAILS: The Surgery Quality & Workflow Manager (SQWM) module of the VistA Surgery package is requesting that the Surgery package become listed as a subscriber to ICR 1467 and the ICR changed to an Active status, for the purpose of adding a Surgery action protocol to the GMRA ENTERED IN ERROR extended action Protocol. Patch SR*3.0*180 is the primary SQWM patch being released under the VistA Surgery package. The Surgery software invoked by this Protocol will generate an HL7 message used to update the COTS SQWM system with current patient Adverse Reactions for the purpose of maintaining consistency with VistA for patient allergies verified through CPRS. SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: Added RPC as a listener: VPR GMRA EVENTS DBA Comments: 05-22-14 DT:Added Surgery as subscriber for SQWM module, SR*3.0*180, and activated ICR. 9/24/14-MC: Deactivated for editing and added Melanie Buechler as the editor for VPR*1*3 9/30/14-MC: Activated ICR as requested by Melanie Buechler and approved by Jason Hawsey. 10/27/14 DT: The following RPC was added as a listener: VPR GMRA EVENTS in the subscribers detail. DATE ACTIVATED: SEP 30, 2014 DATE/TIME EDITED: MAY 22, 2014@17:33 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: HAWSEY,JASON DATE/TIME EDITED: SEP 30, 2014@12:55 ACTION: APPROVED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: HAWSEY,JASON NUMBER: 1469 IA #: 1469 DATE CREATED: JAN 19, 1996 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: GMRA SIGN-OFF ON DATA PROTOCOL CREATOR: BUECHLER,MELANIE K GENERAL DESCRIPTION: This extended action protocol is created with v4.0 and is invoked whenever an allergy/adverse reaction tracking incident is signed-off on a patient. Action protocols from other applications may be added to this event upon approval of the DBIC. Listed below are the variables that will be defined for that reaction. Variables: GMRAPA = The Internal Entry Number of the reaction in File 120.8 (PATIENT ALLERGIES) GMRAPA(0) = The zero node of the entry in File 120.8. Below is a description of the data for that node. $P Field name Field type ----------------------------------------------------------- 1 PATIENT Pointer to File 2 (PATIENT) 2 REACTANT Free Text of Reaction 3 GMR ALLERGY Variable Pointer * 4 ORIGINATION DATE/TIME Date/Time 5 ORIGINATOR Pointer to File 200 (NEW PERSON) 6 OBSERVED/HISTORICAL Set of Codes (o=Observed,h=Historical) 12 ORIGINATOR SIGN OFF Set of Codes (1=Signed,(Zero or Null)= Unsigned) 14 MECHANISM Set of Codes (U=Unknown, P=Pharmacologic,A=Allergy) 16 VERIFIED Set of Codes (1=Verified,(0 or Null)=Not Verified) 17 VERIFICATION DATE/TIME Date/Time 18 VERIFIER Pointer to File 200 20 ALLERGY TYPE Free Text/Set of Codes 1 to 3 characters long (Where "D" = Drug, "F" = Food, "O" = Other) *The GMR ALLERGY field is a variable pointer which points to one of five possible files. They are: File Name File Reference --------- -------------- GMR ALLERGIES GMR(120.8, (e.g., 212;GMR(120.8,) NATIONAL DRUG PSNDF( DRUG PSDRUG( DRUG INGREDIENTS PS(50.416, VA DRUG CLASS PS(50.605, STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19235122 SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: SURGERY SUBSCRIBING DETAILS: The Surgery Quality & Workflow Manager (SQWM) module of the VistA Surgery package is requesting that the Surgery package become listed as a subscriber to ICR 1467 and the ICR changed to an Active status, for the purpose of adding a Surgery action protocol to the GMRA SIGN-OFF ON DATA PROTOCOL extended action Protocol. Patch SR*3.0*180 is the primary SQWM patch being released under the VistA Surgery package. The Surgery software invoked by this Protocol will generate an HL7 message used to update the COTS SQWM system with current patient Adverse Reactions for the purpose of maintaining consistency with VistA for patient allergies verified through CPRS. SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: Added RPC as a listener: VPR GMRA EVENTS DBA Comments: 05-22-14 DT:Added Surgery as subscriber for SQWM module, SR*3.0*180, and activated ICR. 9/24/14-MC: ICR deactivated for edits and added Melanie Buechler as an editor for VPR*1*3 9/30/14-MC: Activated ICR at the request of Melanie Buechler and approved by Jason Hawsey. 10/27/14 DT: The following RPC was added as a listener: VPR GMRA EVENTS in the subscribers detail. DATE ACTIVATED: SEP 30, 2014 DATE/TIME EDITED: MAY 22, 2014@17:37 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: HAWSEY,JASON DATE/TIME EDITED: SEP 30, 2014@12:58 ACTION: APPROVED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: HAWSEY,JASON NUMBER: 1472 IA #: 1472 DATE CREATED: JAN 23, 1996 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUTMOPT NAME: XUTMOPT Option scheduling interface ID: XUTMOPT GENERAL DESCRIPTION: This routine holds several supported calls for access to the option scheduling file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32528077 COMPONENT/ENTRY POINT: EDIT COMPONENT DESCRIPTION: This entry point allows users to edit an option's scheduling in the OPTION SCHEDULING file (#19.2). Usage D EDIT^XUTMOPT(option_name) VARIABLES: option_name TYPE: Input VARIABLES DESCRIPTION: The name of the option from the option file that the user is to be allowed to edit. COMPONENT/ENTRY POINT: DISP COMPONENT DESCRIPTION: This entry point is used to display the schedule for an option. Usage D DISP^XUTMOPT(option_name) VARIABLES: option_name TYPE: Input VARIABLES DESCRIPTION: The name of the option from the option file that the taskman schedule is to be displayed. COMPONENT/ENTRY POINT: RESCH COMPONENT DESCRIPTION: This entry point allows an application to set-up the schedule for an option. Usage D RESCH^XUTMOPT(option_name,when_to_run,device_to_use, re-schedule_freq,flags,error_array) VARIABLES: option_name TYPE: Input VARIABLES DESCRIPTION: Name of the option to be rescheduled. VARIABLES: when_to_run TYPE: Input VARIABLES DESCRIPTION: (optional) The new scheduled time for the option to run. VARIABLES: device_to_use TYPE: Input VARIABLES DESCRIPTION: (optional) The device to use for the rescheduled option. VARIABLES: re-schedule_freq TYPE: Input VARIABLES DESCRIPTION: (optional) The frequency to run the rescheduled option. VARIABLES: flags TYPE: Input VARIABLES DESCRIPTION: (optional) If the flag is set to an 'L' LAYGO a new entry if needed. VARIABLES: error_array TYPE: Both VARIABLES DESCRIPTION: (optional) Pass by reference. Will be set to -1 if the option was not found. COMPONENT/ENTRY POINT: OPTSTAT COMPONENT DESCRIPTION: This entry point allows an application to find out when a option is scheduled and get other data. VARIABLES: optionname TYPE: Input VARIABLES DESCRIPTION: This is the name of the OPTION (.01 field of file 19) to return data on. VARIABLES: ROOT TYPE: Both VARIABLES DESCRIPTION: This variable is passed by reference and returns an array of data about the OPTION in question. Example: D OPTSTAT^XUTMOPT("OPTION NAME",.ROOT) Returns an array of data in ROOT (pass by ref) in the form. ROOT=count ROOT(1)=task number^scheduled time^reschedule freq^special queueing flag This is an array because the same task can be scheduled more that once. NUMBER: 1473 IA #: 1473 DATE CREATED: FEB 09, 1996 CUSTODIAL PACKAGE: AUTOMATED MED INFO EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DVBCTRN NAME: DBIA1473 ID: DVBCTRN GENERAL DESCRIPTION: Quality: Audiology and Speech Pathology Audit and Review (QUASAR), will make calls to AMIE routines EN1^DVBCTRN and EN2^DVBCTRN. This is done to acquire the soft link information, verify the availability of the soft link's request, and to download information to AMIE for the purpose of transmitting audiology C&P exam data. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19159444 COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: EN1^DVBCTRN receives parameters: #1 - Patient's DFN #2 - Name of exam needing softlink #3 - Softlink returns: Either new softlink or validity of existing softlink COMPONENT/ENTRY POINT: EN2 COMPONENT DESCRIPTION: EN2^DVBCTRN receives parameters: #1 - Global or Local root of information to be loaded into AMIE #2 - Package name calling AMIE #3 - Softlink information #4 - Pointer to New Person file (indicating examining physician) #5 - Date the examination was performed (in FM format) returns: Indication of success/failure of download SUBSCRIBING PACKAGE: QUASAR ISC: Birmingham NUMBER: 1475 IA #: 1475 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: FEB 09, 1996 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Global Read of S node in File 2 ID: DPT( GLOBAL REFERENCE: DPT(D0,'S',D1,0) FIELD NUMBER: 3 FIELD NAME: STATUS LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DPT(D0,'S',0) FIELD NUMBER: 1900 FIELD NAME: APPOINTMENT ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Adverse Reaction Tracking package requests permission to do a direct global read of the "S" nodes in the Patient file in order to get the STATUS field (#3) value for an APPOINTMENT (#1900) entry. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18467028 SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING ISC: Hines NUMBER: 1476 IA #: 1476 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: FEB 09, 1996 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1476 ID: DPT( GLOBAL REFERENCE: DPT(D0,.36) FIELD NUMBER: .361 FIELD NAME: PRIMARY ELIGIBILITY CODE LOCATION: .36;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DPT(D0,.372,D1,0) FIELD NUMBER: .01 FIELD NAME: RATED DISABILITIES (VA) LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: DISABILITY % LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: SERVICE CONNECTED LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Quality: Audiology and Speech Pathology Audit and Review (QUASAR) will reference the following fields from the PATIENT file. From node .372 of the PATIENT file (#2), fields .01, RATED DISABILITIES (VA), 2 DISABILITY %, and 3 SERVICE CONNECTED. From node .36 of the PATIENT file (#2), field .361 PRIMARY ELIGIBILITY CODE. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19159541 SUBSCRIBING PACKAGE: QUASAR ISC: Birmingham SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING DETAILS: On the Listman Patient Information screen in Outpatient Pharmacy, the Rated Disabilities along with Disability % and Service Connected indicator are displayed. This information is retrieved by looping through the .372 node (Rated Disabilities subfile #2.04) of the PATIENT File (#2). We then set a variable to the zero node, and get the data for fields #01, #2, and #3 from the variable for display. SUBSCRIBING PACKAGE: SCHEDULING NUMBER: 1479 IA #: 1479 DATE CREATED: MAR 01, 1996 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: Delete PACKAGE file entry GENERAL DESCRIPTION: The Allergy package is changing its name to ADVERSE REACTION TRACKING with version 4. The package's namespace is GMRA. Some sites have two entries in their PACKAGE file that have GMRA as the namespace. They are ALLERGY TRACKING SYSTEM and GEN. MED. REC. - ALLERGIES. The former is version 2.2 and the latter is version 3. Both are previous versions of the ADVERSE REACTION TRACKING package. The GEN. MED. REC. - ALLERGIES entry will be changed to ADVERSE REACTION TRACKING in the PACKAGE file (DBIA #1449). This DBIA allows the version 4 environment check routine to delete any other PACKAGE file entries that have the GMRA namespace. When the unwanted entry has a lower internal entry number in the PACKAGE file it confuses the $$VERSION^XPDUTL utility which looks at the namespace cross-reference. For example: W $$VERSION^XPDUTL("GMRA") can return the value 2.2 when it should return 4. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19456916 SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING ISC: Hines NUMBER: 1481 IA #: 1481 FILE NUMBER: 42 GLOBAL ROOT: DIC(42, DATE CREATED: FEB 09, 1996 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Check Out-Of-Service nodes on File 42 ID: DIC(42, GLOBAL REFERENCE: DIC(42,D0,'OOS',D1,0) FIELD NUMBER: .06 FIELD NAME: IS ENTIRE WARD OUT OF SERVICE? LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: RETURN TO SERVICE DATE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DIC(42,D0,'OOS','AINV',D1,D2) GLOBAL DESCRIPTION: This global reference is for the AINV cross reference which is set by the OUT-OF-SERVICE DATE(S) field. In this global reference: D0 = ward location internal entry number (ien) D1 = inverse value of the date being checked D2 = the ien of the OUT-OF-SERVICE DATE(S) multiple GENERAL DESCRIPTION: The Adverse Reaction Tracking package requests permission to do a direct global read of the "OOS" nodes (OUT-OF-SERVICE DATE) in the WARD LOCATION file (#42) in order to determine if a ward is out-of-service during a particular date/time range. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 18469548 SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING ISC: Hines NUMBER: 1483 IA #: 1483 FILE NUMBER: 420.8 GLOBAL ROOT: PRCD(420.8 DATE CREATED: FEB 26, 1996 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1483 ID: PRCD(420.8 GLOBAL REFERENCE: PRCD(420.8,D0,0) FIELD NUMBER: .01 FIELD NAME: CODE LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: This is the code identifying the procurement source for goods. GENERAL DESCRIPTION: Engineering Package is given permission to point to File #420.8 SOURCE CODE. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19087307 SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring NUMBER: 1484 IA #: 1484 FILE NUMBER: 420.1 GLOBAL ROOT: PRCD(420.1 DATE CREATED: FEB 26, 1996 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1484 ID: PRCD(420.1 GLOBAL REFERENCE: PRCD(420.1,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: This is the 6 digit cost center number, a space, and the cost center name. GENERAL DESCRIPTION: The Engineering Package is given permission to point to File 420.1. (COST CENTER). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19087307 SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring NUMBER: 1485 IA #: 1485 FILE NUMBER: 441.2 GLOBAL ROOT: PRC(441.2 DATE CREATED: FEB 26, 1996 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1485 ID: PRC(441.2 GLOBAL REFERENCE: PRC(441.2,D0,0) FIELD NUMBER: .01 FIELD NAME: NUMBER LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: Four digit Federal Supply Classification number. GENERAL DESCRIPTION: The Engineering Package is given permission to point to File 441.2. (FEDERAL SUPPLY CLASSIFICATION) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19087307 SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring NUMBER: 1489 IA #: 1489 FILE NUMBER: 100.21 GLOBAL ROOT: OR(100.21, DATE CREATED: FEB 14, 1996 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Look at File 100.21 ID: OR(100.21, GLOBAL REFERENCE: OR(100.21,D0,1,D1) GLOBAL DESCRIPTION: Direct global read access to determine the existence of a team member entry. GLOBAL REFERENCE: OR(100.21,D0,0) GLOBAL DESCRIPTION: Direct global read access to determine the existence of a team entry. GLOBAL REFERENCE: OR(100.21,'AB',D0,D1) GLOBAL DESCRIPTION: Direct global read access of the AB cross reference to find the teams associated with a patient. GENERAL DESCRIPTION: The Adverse Reaction Tracking (ART) package requests permission to do direct global reads in the OE/RR TEAM FILE (#100.21) through version 2.5 of CPRS (OE/RR). The ART package sends bulletins to the team members associated with a patient. STATUS: Active DURATION: Next Version MAIL MESSAGE: 18468089 GOOD ONLY FOR VERSION: 2.5 SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING ISC: Hines SUBSCRIBING PACKAGE: CARE MANAGEMENT NUMBER: 1490 IA #: 1490 FILE NUMBER: 748.2 GLOBAL ROOT: QA(748.2, DATE CREATED: FEB 22, 1996 CUSTODIAL PACKAGE: SURVEY GENERATOR CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DEMOGRAPHIC REFERENCE FILE ID: QA(748.2, GLOBAL REFERENCE: QA(748.2,D0,0) FIELD NUMBER: .01 FIELD NAME: FILE NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Nursing has permission to Read this field with FileMan. Also, in a pre-init routine, Nursing has permission to LAYGO an entry into this file to set up the NURS Location (211.4) file entry. GENERAL DESCRIPTION: Nursing has permission to access the following field in the Demographic Reference File (748.2). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20172869 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1491 IA #: 1491 FILE NUMBER: 748 GLOBAL ROOT: QA(748, DATE CREATED: FEB 16, 1996 CUSTODIAL PACKAGE: SURVEY GENERATOR CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: SURVEY ID: QA(748, GLOBAL REFERENCE: QA(748,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: QA(748,D0,1,D1,0) FIELD NUMBER: 2 FIELD NAME: FILE LOCATION: 0;3 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Nursing has permission to access the following fields in the Survey (748) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19282914 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1492 IA #: 1492 FILE NUMBER: 748.25 GLOBAL ROOT: QA(748.25, DATE CREATED: FEB 16, 1996 CUSTODIAL PACKAGE: SURVEY GENERATOR CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: SURVEY QUESTIONS ID: QA(748.25, GLOBAL REFERENCE: QA(748.25,D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: QUESTION LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .015 FIELD NAME: QUESTION NUMBER LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: .025 FIELD NAME: MULTIPLE CHOICE TYPE LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: .027 FIELD NAME: NUMBER OF GRADIENTS (LIKERT) LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: LEFT LIKERT LABEL LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: RIGHT LIKERT LABEL LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: LIKERT NUMBERIC DISPLAY TYPE LOCATION: 0;7 ACCESS: Read w/Fileman FIELD NUMBER: .05 FIELD NAME: QUESTION TEXT LOCATION: 2;0 ACCESS: Read w/Fileman GLOBAL REFERENCE: QA(748.25,D0,1,D1,3,D2,0) FIELD NUMBER: .01 FIELD NAME: ANSWER LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Nursing has permission to access the following fields in the Survey Questions (748.25) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19282937 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1493 IA #: 1493 FILE NUMBER: 748.3 GLOBAL ROOT: QA(748.3, DATE CREATED: FEB 16, 1996 CUSTODIAL PACKAGE: SURVEY GENERATOR CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: SURVEY RESPONSE DATA ID: QA(748.3, GLOBAL REFERENCE: QA(748.3,D0,0) FIELD NUMBER: 3 FIELD NAME: SURVEY COMPLETION STATUS LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: .01 FIELD NAME: SURVEY LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: QA(748.3,D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: QUESTION NUMBER LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: ANSWER LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: RESPONSE LOCATION: 1;0 ACCESS: Read w/Fileman GLOBAL DESCRIPTION: Read with Fileman. GLOBAL REFERENCE: QA(748.3,D0,2,D1,0) FIELD NUMBER: 1 FIELD NAME: RESPONSE DATA LOCATION: 0;2 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Nursing has permission to access the following fields in the Survey Response Data (748.3) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19282951 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1494 IA #: 1494 FILE NUMBER: 43 GLOBAL ROOT: DG(43, DATE CREATED: FEB 21, 1996 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: SENSITIVE PATIENT BULLETIN NAME ID: DG(43, GLOBAL REFERENCE: DG(43,D0,NOT) FIELD NUMBER: 509 FIELD NAME: SENSITIVE REC ACCESSED GROUP LOCATION: NOT;6 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: NETWORK HEALTH EXCHANGE (NHE) is requesting permission to access the following element in the MAS PARAMETERS file (^DG(43,). A direct global read will collect the pointer value for the mail group specified to receive sensitive patient accessed bulletins at the site and then look up the mail group name in ^XMB(3.8) in order to trigger a bulletin at the target site when patient data is requested from another NHE site for a Sensitive patient. STATUS: Active DURATION: Next Version MAIL MESSAGE: 19337026 GOOD ONLY FOR VERSION: 5.1 SUBSCRIBING PACKAGE: NETWORK HEALTH EXCHANGE ISC: Oakland SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring NUMBER: 1495 IA #: 1495 FILE NUMBER: 869.2 GLOBAL ROOT: HLCS(869.2, DATE CREATED: FEB 22, 1996 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1495-A ORIGINAL NUMBER: 1495 ID: HLCS(869.2, GLOBAL REFERENCE: HLCS(869.2,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Write w/Fileman FIELD NUMBER: .02 FIELD NAME: LLP TYPE LOCATION: 0;2 ACCESS: Write w/Fileman GLOBAL REFERENCE: HLCS(869.2,D0,200) FIELD NUMBER: 200.01 FIELD NAME: HLLP DEVICE LOCATION: 200;1 ACCESS: Write w/Fileman FIELD NUMBER: 200.08 FIELD NAME: PROTOCOL ID VERSION LOCATION: 200;8 ACCESS: Write w/Fileman GLOBAL REFERENCE: HLCS(869.2,D0,300) FIELD NUMBER: 300.01 FIELD NAME: X3.28 DEVICE LOCATION: 300;1 ACCESS: Write w/Fileman GENERAL DESCRIPTION: Controlled Substances Version 3.0 needs write access to the HL LOWER LEVEL PROTOCOL PARAMETER file to allow a post-init to populate necessary parameters for an interface to narcotic dispensing equipment systems. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19310488 SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 1496 IA #: 1496 FILE NUMBER: 870 GLOBAL ROOT: HLCS(870, DATE CREATED: FEB 22, 1996 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1495-B ORIGINAL NUMBER: 1495 ID: HLCS(870, GLOBAL REFERENCE: HLCS(870, FIELD NUMBER: .01 FIELD NAME: NODE LOCATION: 0;1 ACCESS: Write w/Fileman FIELD NUMBER: 2 FIELD NAME: LLP TYPE LOCATION: 0;3 ACCESS: Write w/Fileman FIELD NUMBER: 14 FIELD NAME: SHUTDOWN LLP ? LOCATION: 0;15 ACCESS: Write w/Fileman GENERAL DESCRIPTION: Write access permitted to the HL LOGICAL LINK file to allow installation to populate necessary fields to support interfaces. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19310501 SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING DETAILS: Only uses Read w/Fileman on the .01 field. SUBSCRIBING PACKAGE: KERNEL SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: INTEGRATED BILLING NUMBER: 1497 IA #: 1497 FILE NUMBER: 420.2 GLOBAL ROOT: PRCD(420.2 DATE CREATED: FEB 26, 1996 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1497 ID: PRCD(420.2 GLOBAL REFERENCE: PRCD(420.2,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: The budget object code, a space, and the budget object code name. GENERAL DESCRIPTION: The Engineering Package is given permission to point to File 420.2. (BUDGET OBJECT CODE). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19087307 SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring NUMBER: 1498 IA #: 1498 FILE NUMBER: 440 GLOBAL ROOT: PRC(440 DATE CREATED: FEB 26, 1996 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1498 ID: PRC(440 GLOBAL REFERENCE: PRC(440,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: The vendor name. GENERAL DESCRIPTION: The Engineering Package is given permission to point to File 440 (Vendor). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19087307 SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring NUMBER: 1499 IA #: 1499 FILE NUMBER: 442 GLOBAL ROOT: PRC(442, DATE CREATED: FEB 26, 1996 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1499 ID: PRC(442, GLOBAL REFERENCE: PRC(442,D0,0) FIELD NUMBER: .01 FIELD NAME: PURCHASE ORDER NUMBER LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the purchase order number. FIELD NUMBER: 1 FIELD NAME: FCP LOCATION: 0;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the valid Fund Control Point. FIELD NUMBER: 2 FIELD NAME: COST CENTER LOCATION: 0;5 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the cost center. GLOBAL REFERENCE: PRC(442,D0,1) FIELD NUMBER: .1 FIELD NAME: P.O. DATE LOCATION: 1;15 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the purchase order date. FIELD NUMBER: 5 FIELD NAME: VENDOR LOCATION: 1;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the name of the vendor. FIELD NUMBER: 5.2 FIELD NAME: REQUESTING SERVICE LOCATION: 1;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the requesting service. FIELD NUMBER: 8 FIELD NAME: SOURCE CODE LOCATION: 1;7 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the source code for this order. GLOBAL REFERENCE: PRC(442,D0,23) FIELD NUMBER: 26 FIELD NAME: BBFY LOCATION: 23;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the beginning budget fiscal year. GLOBAL REFERENCE: PRC(442,D0,2,D1,0) FIELD NUMBER: .01 FIELD NAME: LINE ITEM NUMBER LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the line item number. FIELD NUMBER: 3.5 FIELD NAME: BOC LOCATION: 0;4 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the budget object code ofor the item. GLOBAL DESCRIPTION: Part of Item (#40) multiple. GLOBAL REFERENCE: PRC(442,D0,2,D1,2) FIELD NUMBER: 8 FIELD NAME: FEDERAL SUPPLY CLASSIFICATION LOCATION: 2;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the Federal Supply Classification for the item. GLOBAL DESCRIPTION: Part of Item (#40) multiple. GLOBAL REFERENCE: PRC(442,D0,22,D1,0) FIELD NUMBER: .01 FIELD NAME: SUBACCOUNT LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is a BOC for one or more LINE ITEM NUMBERs within this record. FIELD NUMBER: 1 FIELD NAME: SUBAMOUNT LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the dollar amount reported to FMS for this BOC. GLOBAL DESCRIPTION: part of BOC (#41) multiple. GENERAL DESCRIPTION: The Engineering package is given permission to read data from the following fields in file #442 (PROCUREMENT AND ACCOUNTING TRANSACTIONS) using FileMan utilities and to loop through the global nodes of the ITEM and BOC multiples to obtain the internal entry number of the multiple for use in FileMan calls. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19087307 SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring NUMBER: 1500 IA #: 1500 DATE CREATED: FEB 26, 1996 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRC0C NAME: Returns Accounting Data ID: PRC0C GENERAL DESCRIPTION: The Engineering Package is given permission to call $$ACC^PRC0C. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19087307 COMPONENT/ENTRY POINT: $$ACC(A,B) COMPONENT DESCRIPTION: Returns accounting information for a station and fund control point. VARIABLES: A TYPE: Input VARIABLES DESCRIPTION: Station Number. VARIABLES: B TYPE: Input VARIABLES DESCRIPTION: Data (3 pieces delimited by ^) ^1=fund control point code ^2=(document) fiscal 2-digit year ^3=beginning budget fiscal year (4-digit) VARIABLES: $$ACC TYPE: Output VARIABLES DESCRIPTION: value (12 pieces delimited by ^) ^1=a/o code ^2=program ^3=fcp/prj code ^4=object class ^5=fund code ^6=bfy beginning ^7=bfy end ^8=fund trans allowed ^9=file 420.14 record id ^10=job ^11=fill-in-year(s) appropriation ^12=gross/net SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring NUMBER: 1511 IA #: 1511 DATE CREATED: MAR 08, 1996 CUSTODIAL PACKAGE: LEXICON UTILITY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMPTU NAME: USE OF ICDONE ID: GMPTU GENERAL DESCRIPTION: The Automated Information Collection System has the ability to print lists of terms based on the Clinical Lexicon on Encounter Forms. When the forms are scanned and data is passed the PCE, the ICD9 diagnosis code associated with the term is required to populate the Purpose of Visit. This agreement is to allow AICS to use the call ICDONE^GMPTU (and its successor) ICDONE^LEXU to determine the correct, or best ICD9 Diagnosis code associated with the selected term. Input variable is the pointer to the clinical lexicon entry in file 757.01. Output is the ICD9 code, or null if none is found. This will be coded in such a way as when Clinical Lexicon converts to the LEX namespace that no changes will be required. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19550922 COMPONENT/ENTRY POINT: ICDONE COMPONENT DESCRIPTION: Returns the best ICD9 code to associate with a clinical lexicon entry. VARIABLES: INPUT TYPE: Input VARIABLES DESCRIPTION: The input to this function is the pointer to the Clinical Lexicon file (757.01) as the only parameter. This value is retrieved for other call to the clinical lexicon. VARIABLES: OUTPUT TYPE: Output VARIABLES DESCRIPTION: The function returns the ICD9 Diagnosis most appropriate for the term, or null if none exisits. SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany NUMBER: 1515 IA #: 1515 DATE CREATED: MAR 12, 1996 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Set File Security for ART files GLOBAL REFERENCE: DIC( GENERAL DESCRIPTION: The Adverse Reaction Tracking (ART) package uses the KIDS utility to export the package software. ART exports the file level security codes for its data dictionaries. Currently, KIDS will not change the file level security codes on the target system if they already exist. This DBIA allows ART to check the file level security nodes on the package's data dictionaries and change the target system's file level security to match the ones being exported. They are: ^DIC(120.8,0,"AUDIT") = @ ^DIC(120.8,0,"DD") = @ ^DIC(120.8,0,"DEL") = @ ^DIC(120.8,0,"LAYGO") = @ ^DIC(120.8,0,"WR") = @ ^DIC(120.82,0,"AUDIT") = @ ^DIC(120.82,0,"DD") = @ ^DIC(120.82,0,"DEL") = @ ^DIC(120.83,0,"AUDIT") = @ ^DIC(120.83,0,"DD") = @ ^DIC(120.83,0,"DEL") = @ ^DIC(120.84,0,"AUDIT") = @ ^DIC(120.84,0,"DD") = @ ^DIC(120.84,0,"DEL") = @ ^DIC(120.84,0,"LAYGO") = @ ^DIC(120.84,0,"RD") = @ ^DIC(120.84,0,"WR") = @ ^DIC(120.85,0,"AUDIT") = @ ^DIC(120.85,0,"DD") = @ ^DIC(120.85,0,"DEL") = @ ^DIC(120.85,0,"LAYGO") = @ ^DIC(120.85,0,"WR") = @ ^DIC(120.86,0,"AUDIT") = @ ^DIC(120.86,0,"DD") = @ ^DIC(120.86,0,"DEL") = @ ^DIC(120.86,0,"LAYGO") = @ ^DIC(120.86,0,"RD") = @ ^DIC(120.86,0,"WR") = @ ^DIC(120.87,0,"AUDIT") = @ ^DIC(120.87,0,"DD") = @ ^DIC(120.87,0,"DEL") = @ ^DIC(120.87,0,"LAYGO") = @ ^DIC(120.87,0,"WR") = @ STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19505125 SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING ISC: Hines NUMBER: 1516 IA #: 1516 DATE CREATED: MAR 19, 1996 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSLOAD NAME: Add SCD component ID: GMTSLOAD GENERAL DESCRIPTION: Spinal Cord Dysfunction requests permission to add a new SCD component to the Health Summary Component (#142.1) file which presents SCD information while respecting Time and Occurrence limits. This component will be added by the SCD post-init as record number 74. The post-init also adds this component to the GMTS HS ADHOC OPTION Health Summary Type by calling the subroutine ENPOST^GMTSLOAD, installs the routine SPNHS1 as GMTSSCD (This is the driver/print routine for the component), and will installs SCD into PDX data segment file (refer to DBIA #1023). STATUS: Active DURATION: Next Version MAIL MESSAGE: 19718548 GOOD ONLY FOR VERSION: 2.7 COMPONENT/ENTRY POINT: ENPOST SUBSCRIBING PACKAGE: Spinal Cord Injury ISC: Hines NUMBER: 1517 IA #: 1517 DATE CREATED: MAR 19, 1996 CUSTODIAL PACKAGE: SPINAL CORD DYSFUNCTION CUSTODIAL ISC: Chicago USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SPNHS0 NAME: SCD API ID: SPNHS0 GENERAL DESCRIPTION: Permission to call the routine EN^SPNHS0(SPNDFN,SPNBEG,SPNEND,SPNMAX) to get Spinal Cord Dysfunction data. Parameter passing is being used for Input variables and data will be returned in ^TMP array. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19718551 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: API to allow retrieval of SCD data for a patient for a date range and set number of occurrences. VARIABLES: SPNDFN TYPE: Input VARIABLES DESCRIPTION: Patient file pointer VARIABLES: SPNBEG TYPE: Input VARIABLES DESCRIPTION: Beginning date in internal fileman format VARIABLES: SPNEND TYPE: Input VARIABLES DESCRIPTION: Ending date in internal fileman format VARIABLES: SPNMAX TYPE: Input VARIABLES DESCRIPTION: Maximum number of occurrences (optional) VARIABLES: TMP("SPN",$J) TYPE: Output VARIABLES DESCRIPTION: ^TMP("SPN",$J,154,0)= REGISTRATION STATUS^HIGHEST LEVEL OF INJURY^INFORMATION SOURCE FOR SCD ^COMPLETENESS OF INJURY^EXTENT OF PARALYSIS^PRIMARY CARE PROVIDER^SCI/SCD COORDINATOR ^TMP("SPN",$J,154,INVERSE ONSET DATE)= ONSET DATE (internal FM format)^ETIOLOGY^ONSET OF SCD CAUSED BY TRAUMA ^TMP("SPN",$J,154.1,INVERSE DATE RECORDED, IEN)= DATE RECORDED (internal FM format)^MOTOR SCORE^COGNITIVE SCORE^ TOTAL SCORE ^RECORD TYPE VARIABLES: SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 1519 IA #: 1519 DATE CREATED: MAR 29, 1996 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUTMDEVQ NAME: XUTMDEVQ ID: XUTMDEVQ CREATOR: BEUSCHEL,GARY GENERAL DESCRIPTION: These APIs allow you to run jobs directly or queue them, whether printing to a device or not, and enable varying degrees of user interaction. See the TaskMan: Developer Tools section of the Kernel Developer's Guide for further information. EN^XUTMDEVQ: Use this to allow the user to decide whether to run the job directly or queue it. The user may select the device and the start time. If a task is long-running, and has an output device, it will tie up the output device for the whole time. That's not desirable. We've created a way for you to split the job into two tasks: gather and print. The user may select the device and the start time. $$QQ^XUTMDEVQ(): Double Queue- This API creates the Gather and Print tasks. The gather task is scheduled to run, while the print task is not scheduled. The gather task collects data and stores it, perhaps in ^XTMP. When the gather task is finished, the gather task can schedule the print task. $$REQQ^XUTMDEVQ(): Schedule the Print task that was created by $$QQ^XUTMDEVQ. The print task prints the data that was stored by the gather task. This API should be invoked at the end of the Gather task to print the results. $$DEV^XUTMDEVQ(): Use this to force the user to queue a job. The user may select the device and start time. $$NODEV^XUTMDEVQ(): Use this to force the user to queue a job which doesn't need any device. The user may select the start time. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19873632 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: EN^XUTMDEVQ(ztrtn, ztdesc, ztsave [, %zis] [, retztsk]) Input Parameters: ztrtn - The entry point EN^XUTMDEVQ will DO to start the job. Specify it as "LABEL^ROUTINE" or "^ROUTINE" or "ROUTINE" ztdesc - Task description, up to 200 characters describing the task, with the package name at the front. ztsave - This parameter is passed by reference. Set up this array in the same format as the ZTSAVE input array is set up for a ^%ZTLOAD TaskMan entry point. %zis - (optional) Pass by reference or value. Any parts of the %ZIS variable that is to be used in the ^%ZIS device call. retztsk - (optional) If the job is tasked, and you want to know the task number ZTSK, then set this parameter such that $G(retztsk). Output: ZTSK - (optional output) If $G(retztsk), and the job is tasked, ZTSK will hold the task number upon exit from this API. VARIABLES: ztrtn TYPE: Input VARIABLES: ztdesc TYPE: Input VARIABLES: ztsave TYPE: Input VARIABLES: %zis TYPE: Input VARIABLES: retztsk TYPE: Input VARIABLES: ZTSK TYPE: Output COMPONENT/ENTRY POINT: $$QQ COMPONENT DESCRIPTION: $$QQ^XUTMDEVQ(%rtn1 [, %desc1] [, %var1] [, %voth1] [, %zis] [, iop] [, %wr] %rtn2 [, %desc2] [, %var2] [, %voth2]) Double Queue- This API creates the Gather and Print tasks. The gather task is scheduled to run, while the print task is not scheduled. The gather task collects data and stores it, perhaps in ^XTMP. When the gather task is finished, the gather task must schedule the print task using $$REQQ^XUTMDEVQ. The ^XTMP location used in the gather task can be passed to the print task in a parameter in $$REQQ^XUTMDEVQ. Input Parameters: %rtn1 - (required) 1st task that TaskMan will run, usually a search-and-build-sorted-data type process. May be specified as "LABEL^ROUTINE" or "^ROUTINE" or "ROUTINE". %desc1 - (optional) Description (up to 200 chars) of 1st task. Default is %rtn1, with ~ substituted for ^. %var1 - (optional) ZTSAVE values for 1st task. Single value or passed by reference, this will be used to SET ZTSAVE(). It may be a string of variable names separated by ";". Each ;-piece will be used as a subscript in ZTSAVE. See the ^%ZTLOAD TaskMan API documentation for a description of the ZTSAVE variable. %voth1 - (optional) Other parameters for 1st task. Passed by reference, %voth1(sub)="" or explicit value sub - this is any other ^%ZTLOAD API variable besides ZTRTN, ZTDESC, ZTIO or ZTSAVE. For example, S %VOTH1("ZTDTH")=$H. %zis - (optional) Passed by reference, this is the standard %ZIS variable array for calling the Device Handler ^%ZIS. The 2nd task of the job will be tasked to this device. Exception: - If %D(%ZIS)=0 then the default value is "MQ", and call the Device Handler. - If $D(%ZIS)=1,%ZIS="" then queue the 2nd task also with ZTIO="" (i.e. Do not call the Device Handler.) iop - (optional) The IOP variable as defined in Kernel's Device Handler ^%ZIS. Default value is "Q". If IOP is passed, but does not include "Q", then "Q" is added. %wr - (optional) If %wr>0 then write text to the screen as to whether or not the queueing was successful. %rtn2 - (required) 2nd task that TaskMan will run, usually a print process. May be specified as "LABEL^ROUTINE" or "^ROUTINE" or "ROUTINE". %desc2 - (optional) Description (up to 200 chars) of 2nd task. Default is %rtn1, with ~ substituted for ^. %var2 - (optional) ZTSAVE values for 2nd task. Single value or passed by reference, this will be used to SET ZTSAVE(). It may be a string of variable names separated by ";". Each ;-piece will be used as a subscript in ZTSAVE. If %var2 is not passed, but %var1 is, then %var1 is merged into %var2 by default. %voth2 - (optional) Other parameters for 2nd task. Passed by reference, %voth2(sub)="" or explicit value sub - this is any other ^%ZTLOAD API variable besides ZTRTN, ZTDESC, ZTIO or ZTSAVE. However, if %voth2("ZTDTH")=$H, that setting is ignored, because the 2nd task is not scheduled. Output: If successful, Function returns ztsk1^ztsk2 (ZTSK values of the 1st and 2nd tasks. If unsuccessful, it returns -1. VARIABLES: $$QQ TYPE: Output VARIABLES: %rtn1 TYPE: Input VARIABLES: %desc1 TYPE: Input VARIABLES: %var1 TYPE: Input VARIABLES: %voth1 TYPE: Input VARIABLES: %zis TYPE: Input VARIABLES: iop TYPE: Input VARIABLES: %wr TYPE: Input VARIABLES: %rtn2 TYPE: Input VARIABLES: %desc2 TYPE: Input VARIABLES: %var2 TYPE: Input VARIABLES: %voth2 TYPE: Input COMPONENT/ENTRY POINT: $$REQQ COMPONENT DESCRIPTION: $$REQQ^XUTMDEVQ(xutsk, xudth [,[.]%var]) Schedule the Print task that was created by $$QQ^XUTMDEVQ. The print task prints the data that was stored by the gather task. This API should be invoked at the end of the Gather (1st) task to print the results. Input Parameters: xutsk - (required) This is the task number of the 2nd task which was created by $$QQ^XUTMDEVQ, but not scheduled. The task number is found in the variable XUTMQQ. xudth - (required) This is the date/time to run the task. To start it right away, use $H. [.]%var - (optional) ZTSAVE values for 2nd task. Single value or passed by reference, this will be used to SET ZTSAVE(). It may be a string of variable names separated by ";". Each ;-piece will be used as a subscript in ZTSAVE. See the ^%ZTLOAD TaskMan API documentation for a description of the ZTSAVE variable. Use this parameter to pass the ^XTMP node location under which all the data from the gather task has been saved. Output: Function returns 1 if successful; 0 if not. VARIABLES: xutsk TYPE: Input VARIABLES: xudth TYPE: Input VARIABLES: %var TYPE: Input VARIABLES: $$REQQ TYPE: Output COMPONENT/ENTRY POINT: $$DEV COMPONENT DESCRIPTION: $$DEV^XUTMDEVQ(ztrtn [,ztdesc] [,%var] [,%voth] [,%zis] [,iop] [,%wr]) Use this to force the user to queue a job. The user may select the device and start time. Input Parameters: ztrtn - (required) Routine that TaskMan will run. May be specified as "LABEL^ROUTINE" or "^ROUTINE" or "ROUTINE". ztdesc - (optional) Task description (up to 200 chars). Default is ztrtn, with ~ substituted for ^. %var - (optional) ZTSAVE values for task. Single value or passed by reference, this will be used to SET ZTSAVE(). It may be a string of variable names separated by ";". Each ;-piece will be used as a subscript in ZTSAVE. See the ^%ZTLOAD TaskMan API documentation for a description of the ZTSAVE variable. %voth - (optional) Other parameters for task. Passed by reference, %voth1(sub)="" or explicit value sub - this is any other ^%ZTLOAD API variable besides ZTRTN, ZTDESC, ZTIO or ZTSAVE. For example, S %VOTH1("ZTDTH")=$H. %zis - (optional) Passed by reference, this is the standard %ZIS variable array for calling the Device Handler ^%ZIS. If it doesn't contain "Q", "Q" will be added to it. The default value is "MQ". iop - (optional) The IOP variable as defined in Kernel's Device Handler ^%ZIS. Default value is "Q". %wr - (optional) If %wr>0 then write text to the screen as to whether or not the queueing was successful. Output: Function returns 0 if run ztrtn without queueing; -1 if unsuccessful. VARIABLES: ztrtn TYPE: Input VARIABLES: ztdesc TYPE: Input VARIABLES: %var TYPE: Input VARIABLES: %voth TYPE: Input VARIABLES: %zis TYPE: Input VARIABLES: iop TYPE: Input VARIABLES: %wr TYPE: Input VARIABLES: $$DEV TYPE: Output COMPONENT/ENTRY POINT: $$NODEV COMPONENT DESCRIPTION: $$NODEV^XUTMDEVQ(ztrtn [,ztdesc] [,%var] [,%voth] [,%wr]) Use this function to force the user to queue a job which doesn't need any device. The user may select the start time. Input Parameters: ztrtn - (required) Routine that TaskMan will run. May be specified as "LABEL^ROUTINE" or "^ROUTINE" or "ROUTINE". ztdesc - (optional) Task description (up to 200 chars). Default is ztrtn, with ~ substituted for ^. %var - (optional) ZTSAVE values for task. Single value or passed by reference, this will be used to SET ZTSAVE(). It may be a string of variable names separated by ";". Each ;-piece will be used as a subscript in ZTSAVE. See the ^%ZTLOAD TaskMan API documentation for a description of the ZTSAVE variable. %voth - (optional) Other parameters for task. Passed by reference, %voth1(sub)="" or explicit value sub - this is any other ^%ZTLOAD API variable besides ZTRTN, ZTDESC, ZTIO or ZTSAVE. For example, S %VOTH1("ZTDTH")=$H. %wr - (optional) If %wr>0 then write text to the screen as to whether or not the queueing was successful. Output: Function returns 1 if scheduling is successful; 0 if not. VARIABLES: ztrtn TYPE: Input VARIABLES: ztdesc TYPE: Input VARIABLES: %var TYPE: Input VARIABLES: %voth TYPE: Input VARIABLES: %wr TYPE: Input VARIABLES: $$NODEV TYPE: Output DBA Comments: 6/5/2012-ICR opened for editing when it was learned an entry documented as supported in the Kernel Developer Guide is not included in the ICR. Gary agreed it should be part of the supported ICR. 6/20/12 - Content updated and re-activated. DATE ACTIVATED: JUN 20, 2012 DATE/TIME EDITED: JUN 06, 2012@14:20 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: TJAHJO,BUDY WITH CONCURRENCE OF: BEUSCHEL,GARY DATE/TIME EDITED: JUN 20, 2012@10:10 ACTION: CONTENT CORRECTED AT THE REQUEST OF: BEUSCHEL,GARY WITH CONCURRENCE OF: BEUSCHEL,GARY DATE/TIME EDITED: JUN 20, 2012@10:11 ACTION: APPROVED AT THE REQUEST OF: BEUSCHEL,GARY WITH CONCURRENCE OF: BEUSCHEL,GARY NUMBER: 1520 IA #: 1520 DATE CREATED: APR 04, 1996 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCFSITE NAME: DBIA1520-A ORIGINAL NUMBER: 1520 ID: PRCFSITE GENERAL DESCRIPTION: The NX Module (Equipment/Turn-In) requests permission to use IFCAP program PRCFSITE to set special IFCAP variables used in the package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20320821 COMPONENT/ENTRY POINT: DIVFY COMPONENT DESCRIPTION: Beginning of program PRCFSITE VARIABLES: PRCF('X') TYPE: Input VARIABLES DESCRIPTION: Set to "S" which defines which local values to return. VARIABLES: PRC('FY') TYPE: Output VARIABLES DESCRIPTION: Returns the current fiscal year. VARIABLES: PRC('PARAM') TYPE: Output VARIABLES DESCRIPTION: Returns the zero node of the parameter file. VARIABLES: PRC('PER') TYPE: Output VARIABLES DESCRIPTION: Returns information about the user. VARIABLES: PRC('QTR') TYPE: Output VARIABLES DESCRIPTION: Returns the current fiscal quarter. VARIABLES: PRC('SITE') TYPE: Output VARIABLES DESCRIPTION: Returns the site/station number. SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1521 IA #: 1521 DATE CREATED: APR 04, 1996 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCSEB NAME: DBIA1520-B ORIGINAL NUMBER: 1520 ID: PRCSEB GENERAL DESCRIPTION: The NX module (Equipment/Turn-In) requests permission to reference program PRCSEB when creating 2237s. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20320831 COMPONENT/ENTRY POINT: W61 COMPONENT DESCRIPTION: This portion of creating 2237 checks the fund control point and makes sure enough funds are there before approving the 2237. VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: Person creating the 2237 VARIABLES: PRC('SITE') TYPE: Input VARIABLES DESCRIPTION: The site/station number VARIABLES: PRC('CP') TYPE: Input VARIABLES DESCRIPTION: The control point VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: Internal number of the 2237. SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1522 IA #: 1522 DATE CREATED: APR 04, 1996 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCSUT NAME: DBIA1520-C ORIGINAL NUMBER: 1520 ID: PRCSUT GENERAL DESCRIPTION: This agreement will allow the NX (Equipment/Turn-In) module to call IFCAP routines from within a distributed input template, used to create 2237s. The calls will return fund control points and information pertaining to the fund control point used to create the 2237. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20320838 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: Retrieves site/station number, fiscal year, quarter and control point if not already set. VARIABLES: PRC('CP') TYPE: Output VARIABLES DESCRIPTION: Returns the fund control point COMPONENT/ENTRY POINT: LOCK COMPONENT DESCRIPTION: Locks the global and record being referenced. VARIABLES: DIC TYPE: Input VARIABLES DESCRIPTION: Global reference VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: Record number SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1523 IA #: 1523 DATE CREATED: APR 04, 1996 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCSUT3 NAME: DBIA1520-D ORIGINAL NUMBER: 1520 ID: PRCSUT3 GENERAL DESCRIPTION: This agreement will allow the NX (Equipment/Turn-In) module to call the IFCAP transaction utility program when creating 2237s which will create the record in file 410 and process all checks on creating a 2237. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20320844 COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: This gets the 2237 transaction number. VARIABLES: PRCS('TYPE') TYPE: Input VARIABLES DESCRIPTION: Type of 2237 (non-repetitive, etc.) VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: The transaction number series (Station Number-Fiscal Year-Control Point). Used to get the next sequential number. COMPONENT/ENTRY POINT: EN2 COMPONENT DESCRIPTION: Adds the record to file 410. SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1524 IA #: 1524 FILE NUMBER: 410 GLOBAL ROOT: PRCS(410, DATE CREATED: APR 04, 1996 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1520-E ORIGINAL NUMBER: 1520 ID: PRCS(410, GLOBAL REFERENCE: PRCS(410,D0 FIELD NUMBER: .01 FIELD NAME: TRANSACTION NUMBER LOCATION: 410 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: 2237 Transaction number FIELD NUMBER: 1 FIELD NAME: TRANSACTION TYPE LOCATION: 410 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Transaction type is set to 'O' (obligation) for new 2237s. FIELD NUMBER: 2 FIELD NAME: TEMPORARY TRANSACTION NUMBER LOCATION: 410 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Temporary transaction number is the Equipment Request transaction number placed into 410. FIELD NUMBER: 3 FIELD NAME: FORM TYPE LOCATION: 410 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Form type generally for Equipment Request 2237s should be REPETITIVE AND NON-REP ORDER. FIELD NUMBER: 53 FIELD NAME: ORIGINATOR OF TEMP # REQ. LOCATION: 410 ACCESS: Write w/Fileman FIELD DESCRIPTION: The REQUESTOR of the Equipment Request is placed in this field. FIELD NUMBER: 8 FIELD NAME: CLASSIFICATION OF REQUEST LOCATION: 410 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: If entered in the Equipment Request, it will be placed in this field. FIELD NUMBER: 49 FIELD NAME: SORT GROUP LOCATION: 410 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: If entered in the Equipment Request, it will be placed in this field. FIELD NUMBER: 5 FIELD NAME: DATE OF REQUEST LOCATION: 410 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: It will place 'TODAY' automatically when creating new 2237. FIELD NUMBER: 6.3 FIELD NAME: REQUESTING SERVICE LOCATION: 410 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This will be moved from the Equipment Request and placed in this field. FIELD NUMBER: 7 FIELD NAME: DATE REQUIRED LOCATION: 410 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: It will be moved from the Equipment Request and placed in this field. FIELD NUMBER: 7.5 FIELD NAME: PRIORITY OF REQUEST LOCATION: 410 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Will be set to 'STANDARD' if new 2237. FIELD NUMBER: 9 FIELD NAME: SPECIAL REMARKS ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Allows user to enter any special remarks when creating the 2237. FIELD NUMBER: 15 FIELD NAME: CONTROL POINT LOCATION: 410 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Control point is set after calls to program PRCSUT3. FIELD NUMBER: 28.5 FIELD NAME: BBFY LOCATION: 410 ACCESS: Write w/Fileman FIELD DESCRIPTION: BBFY is set after calls to program PRCSUT3. FIELD NUMBER: 40 FIELD NAME: REQUESTOR LOCATION: 410 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Is set to the CMR Responsible Official from the Equipment Request. FIELD NUMBER: 15.5 FIELD NAME: COST CENTER LOCATION: 410 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Enter the appropriate cost center for the 2237. FIELD NUMBER: 56 FIELD NAME: REQUEST STATUS LOCATION: 410 ACCESS: Write w/Fileman FIELD DESCRIPTION: Set the 2237 status as 'Pending Accountable Officer Signature' if 2237 passes all checks. FIELD NUMBER: 10 FIELD NAME: ITEM LOCATION: 410 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Line item information is moved from Equipment Request into 410 and includes the following sub-fields (since it is multiple): 1 DESCRIPTION 2 QUANTITY 3 UNIT OF PURCHASE 4 BOC 6 STOCK NUMBER FIELD NUMBER: 11 FIELD NAME: VENDOR LOCATION: 410 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Will pull over vendor from Equipment Request if exists. Includes the other vendor fields: 11.1 VENDOR ADDRESS1 11.2 VENDOR ADDRESS2 11.3 VENDOR ADDRESS3 11.4 VENDOR ADDRESS4 11.5 VENDOR CITY 11.6 VENDOR STATE 11.7 VENDOR ZIP CODE 11.8 VENDOR CONTACT 11.9 VENDOR PHONE NO. 13 VENDOR CONTRACT NUMBER GLOBAL DESCRIPTION: Moves data from Equipment Request (file 413) into the 2237 (file 410) if creating a new 2237, otherwise allows user to edit already created 2237 (but only those 2237s created from the Equipment/Turn-In module). GENERAL DESCRIPTION: The NX (Equipment/Turn-In) module requests permission to reference file 410 to create/edit 2237s which are the end product of this module. Includes addition of two templates to file 410, PRCN2237 and PRCN2237E. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20320852 SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1525 IA #: 1525 FILE NUMBER: 440 GLOBAL ROOT: PRC(440, DATE CREATED: APR 04, 1996 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1520-F ORIGINAL NUMBER: 1520 ID: PRC(440, GLOBAL REFERENCE: PRC(440,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: This is the possible vendor that the requested line item could be purchased from. GLOBAL DESCRIPTION: File 413 is the file that contains the non-expendable equipment requests. It is a front-end to the purchasing of equipment. GENERAL DESCRIPTION: This agreement requests permission for the NX (Equipment/Turn-In) module to point, with read access only, to the Vendor file (440). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20320864 SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1527 IA #: 1527 DATE CREATED: APR 05, 1996 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA1527 GENERAL DESCRIPTION: Inpatient Medications would like to include the PSO INTERVENTION MENU andrelated options as a component. This would allow pharmacists to have thesame functionality for interventions in Inpatient Medications that existsin Outpatient Pharmacy. The options included on this menu are: PSO INTERVENTION NEW ENTRY PSO INTERVENTION EDIT PSO INTERVENTION PRINTOUT PSO INTERVENTION DELETE PSO INTERVENTION VIEW STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19899319 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 1528 IA #: 1528 DATE CREATED: APR 05, 1996 CUSTODIAL PACKAGE: SOCIAL WORK USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SOWKHIRM NAME: Homeless Indicator ID: SOWKHIRM GENERAL DESCRIPTION: This integration agreement is in reference to an API to return homeless information on a patient. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19927196 COMPONENT/ENTRY POINT: $$HOMELESS(DFN) COMPONENT DESCRIPTION: This is a function call that will return a value of 1 if the patient is homeless or zero in not. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This is the Internal entry number for the patient in question. SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 1529 IA #: 1529 FILE NUMBER: 211.4 GLOBAL ROOT: NURSF(211.4, DATE CREATED: APR 26, 1996 CUSTODIAL PACKAGE: NURSING SERVICE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1529 ID: NURSF(211.4, GLOBAL REFERENCE: NURSF(211.4,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: NURSF(211.4,D0,3,D1,0) FIELD NUMBER: .01 FIELD NAME: MAS WARD LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: This agreement will allow Controlled Substances Version 3.0 to use VA Fileman read access to the NURS LOCATION FILE (#211.4). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 19645949 SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 1530 IA #: 1530 FILE NUMBER: 161.2 GLOBAL ROOT: FBAAV DATE CREATED: APR 29, 1996 CUSTODIAL PACKAGE: FEE BASIS CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: VENDOR SCREEN CNH ID: FBAAV GLOBAL REFERENCE: $P(FBAAV(0),U,9) FIELD NUMBER: 7 FIELD NAME: PART CODE LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: A DIC("S") screen that will look at the 9th piece of the zero node to see if it equals 5. Indicating a cnh vendor. GLOBAL REFERENCE: $P(FBAAV('ADEL'),U) FIELD NUMBER: 9 FIELD NAME: AUSTIN DELETED LOCATION: ADEL;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: A DIC("S") screen that will look at the 1st piece of the "ADEL" node to see if it not equal to "Y". Indicating not deleted from Austin's master record. GLOBAL REFERENCE: FBAAV GLOBAL DESCRIPTION: A variable pointer from PIMS file PAF (#45.9), field LOCATION (#70) with a DIC("S") screen that will only allow CNH vendors that have not been deleted by Austin. GENERAL DESCRIPTION: PIMS would like to have a variable pointer to the FEE BASIS VENDOR file (#161.2) and a screen (DIC("S")) that will make only contract nursing home vendors a valid choice. Revisions are being made to the RUG-II software that will allow the entry of CNH patient assessments. Looking at the 9th piece of the zero node and the first piece of the "ADEL" node, would allow us to see if the vendor is a CNH and still active in Austin. The 9th piece of the zero node in the PART CODE (field #7). When this field equals 5, the vendor is a contract nursing home. The 1st piece of the "ADEL" node is AUSTIN DELETED. When this field is defined, set to yes, the vendor is no longer active in the eyes of Austin. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20193541 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 1531 IA #: 1531 FILE NUMBER: 727.815 GLOBAL ROOT: ECX(727.815, DATE CREATED: MAY 01, 1996 CUSTODIAL PACKAGE: DSS EXTRACTS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1531 ID: ECX(727.815, GENERAL DESCRIPTION: Event Capture will export the EVENT CAPTURE LOCAL EXTRACT file (#727.815). The global root of this file is ^ECX(727.815,. Event Capture will not populate this file but the procedure data format will change with the release of Version 2.0. The DSS Extracts software routine ^ECXEC populates this file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20201582 SUBSCRIBING PACKAGE: EVENT CAPTURE ISC: Birmingham NUMBER: 1533 IA #: 1533 FILE NUMBER: 725 GLOBAL ROOT: EC(725, DATE CREATED: MAY 07, 1996 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1533 ID: EC(725, GENERAL DESCRIPTION: Event Capture requests to modify the "B" cross reference for the EC NATIONAL PROCEDURE file (#725) to be 63 characters rather than the standard 30 characters. As part of this agreement Event Capture will provide the following: 1. Add a description to the "B" cross reference indicating that it was modified and that ^DIC lookups into this file with DIC(0)["X" will not find exact matches greater than 30 characters in length. 2. Create a post-install routine that kills the "B" index of the file and then calls ENALL^DIK with DIK(1)=".01^B" to rebuild it. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20200518 SUBSCRIBING PACKAGE: EVENT CAPTURE ISC: Birmingham NUMBER: 1534 IA #: 1534 FILE NUMBER: 216.8 GLOBAL ROOT: NURSC(216.8, DATE CREATED: MAY 14, 1996 CUSTODIAL PACKAGE: NURSING SERVICE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: NURS CARE PLAN ID: NURSC(216.8, GLOBAL REFERENCE: NURSC(216.8,D0,0 GLOBAL DESCRIPTION: Text Generator can delete entries in the NURS Care Plan (216.8) file using FileMan ^DIK. GENERAL DESCRIPTION: The Text Generator V3 has permission to delete entries in the NURS Care Plan (216.8) file. STATUS: Active DURATION: Next Version MAIL MESSAGE: 20373727 GOOD ONLY FOR VERSION: 3 SUBSCRIBING PACKAGE: GEN. MED. REC. - GENERATOR ISC: Hines NUMBER: 1535 IA #: 1535 FILE NUMBER: 0 GLOBAL ROOT: DD(142.1,.01,'DEL', DATE CREATED: MAY 17, 1996 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: 'DEL' node modification ID: DD(142.1,.01,'DEL', GENERAL DESCRIPTION: The health summary package needs permission to change the "DEL" node in the DD structure for file 142.1. This will be done with the SET command and will be done with patch 7. Here is the code to reset the "DEL" node: S ^DD(142.1,.01,"DEL",1,0)="I $S(+$G(DUZ(2))'>0:1,DUZ(2)=5000:0,(DA'<100 001)&(DA'>9999999):0,1:1) N GMZ S GMZ=$S(+$G(DUZ(2)):""ONLY Components Created a t your site can be deleted"",1:""DUZ(2) MUST equal your DIVISION"") D EN^DDIOL(GMZ)" S ^DD(142.1,.01,"DEL",2,0)="I '$D(GMCMP) D EN^DDIOL(""You may only delet e COMPONENTS using the GMTS IRM/ADPAC COMP EDIT option."","""",""!!"")" STATUS: Active DURATION: Next Version MAIL MESSAGE: 20317519 GOOD ONLY FOR VERSION: 2.7 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 1540 IA #: 1540 FILE NUMBER: 0 GLOBAL ROOT: DD(440 DATE CREATED: JUN 13, 1996 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Setting ID entries ID: DD(440 GENERAL DESCRIPTION: Since KIDS cannot presently support changing the ID entries for a file without also shipping all fields in the file, IFCAP wants to send a post-INIT to remove the old ID nodes and set a new ID node. This will change the ID display to alow 5 different entries (vendors) to be seen on a 24 line display without any entries scrolling off the top. This change will be used in patch PRC*5*69 only. STATUS: Active DURATION: Next Version EXPIRATION DATE: SEP 1998 MAIL MESSAGE: 20719781 GOOD ONLY FOR VERSION: 5 SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring NUMBER: 1541 IA #: 1541 DATE CREATED: FEB 23, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAPIOE NAME: DBIA1541 ID: PXAPIOE GENERAL DESCRIPTION: This integration agreement permits read access to procedure, diagnosis and provider information associated with a visit using API tags in routine PXAPIOE. Using appropriate API tags, this DBIA also allows the following: 1) Setting of the PERSON CLASS (#.06) field of the V PROVIDER (#9000010.06) file 2) Setting the PRIMARY/SECONDARY (#.12) field in the V POV (#9000010.07) file to 'primary' STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26312842 COMPONENT/ENTRY POINT: GETDX COMPONENT DESCRIPTION: List of diagnoses associated with a visit. COMPONENT/ENTRY POINT: $$CPT COMPONENT DESCRIPTION: Boolean indicating whether at least one procedure is associated with a visit. COMPONENT/ENTRY POINT: GETCPT COMPONENT DESCRIPTION: List of procedures associated with a visit. Returns the "0" nodes of the corresponding VCPT entries. New development should use the CPTARR component instead (see below). COMPONENT/ENTRY POINT: $$PRV COMPONENT DESCRIPTION: Boolean indicating whether at least one provider is associated with a visit. COMPONENT/ENTRY POINT: GETPRV COMPONENT DESCRIPTION: List of providers associated with a visit. The "zero" node of each V PROVIDER entry is returned. COMPONENT/ENTRY POINT: $$DX COMPONENT DESCRIPTION: Boolean indicating whether at least one diagnosis is associated with a visit. COMPONENT/ENTRY POINT: $$VALVST COMPONENT DESCRIPTION: Boolean that validates whether a visit exits for a passed internal entry number. COMPONENT/ENTRY POINT: PDX COMPONENT DESCRIPTION: Flag the diagnosis as 'primary' for a V POV entry. COMPONENT/ENTRY POINT: PLASS COMPONENT DESCRIPTION: Set the provider class for a V PROVIDER entry. COMPONENT/ENTRY POINT: CPTARR COMPONENT DESCRIPTION: List of procedures associated with a visit. For each of the corresponding V CPT entries, a sub-tree is returned that corresponds to the V CPT file's DD structure. SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING DETAILS: This DBIA was initially created for the ACRP Interface Toolkit (AIT) to allow retrieval and modification of specific PCE data. The AIT was initially distributed in patch SD*5.3*131. SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES NUMBER: 1543 IA #: 1543 DATE CREATED: JUN 18, 1996 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DICA NAME: CHECK FOR DI*21*17 ID: DICA GENERAL DESCRIPTION: The Scheduling Developers would like the following one-time integration agreement with the FileMan Developers: For PCMM (SD*5.3*41), as part of the installation environment checker, SCMCENV, we check the second line of the following routine using $TEXT: ^DICA This is the part of VA FileMan's Updater engine. Patch #17 of Version 21.0 was specifically listed as necessary for proper functioning of the RPC Broker (which PCMM depends on). As such, we require that either: o The package version is 22 or higher o The package version is 21 and DICA has patch #17 indicated in its second line. STATUS: Active DURATION: Next Version MAIL MESSAGE: 20539316 GOOD ONLY FOR VERSION: SD*5.3*41 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 1544 IA #: 1544 DATE CREATED: JUN 18, 1996 CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: USRLM NAME: USRLM CALLS ID: USRLM GENERAL DESCRIPTION: The Scheduling Developers would like the following on-going integration agreement with the Authorization/Subscription Developers: Use of the following USRLM calls: $$ISA(USER,CLASS,ERR) - Boolean - Is USER a Member of CLASS? $$SUBCLASS(DA,CLASS) - Evaluate whether a given USER CLASS is a DESCENDENT of another class $$CLNAME(CLASS) - Given a class, return the Display Name $$WHOIS2(MEMBER,CLASS)- Given a Class, return list of CURRENT members Parameters: USER - Pointer to File #200 CLASS - Pointer to File #8930 DA - Pointer to File #8930 ERR - [Optional] Error Variable to contain error message MEMBER is name of array (local or global) in which members are returned in alphabetical order by name - indexed by number i.e. @MEMBER@(1 ...n) @member@(0) = ien of8930^usr class name^count of members @member@(1..n)= 1 2 3 4 5 6 7 8 p200^p8930.3^classname^effectdate^inactdate^username^title^mailcode Note: For pieces 2,4 & 5 - Only one of potentially many is returned These calls are part of the User Class Membership functions that PCMM uses for sites that choose to use the user class functionality. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 35961090 COMPONENT/ENTRY POINT: $$ISA COMPONENT/ENTRY POINT: $$SUBCLASS VARIABLES: DA TYPE: Input VARIABLES: CLASS TYPE: Input COMPONENT/ENTRY POINT: $$CLNAME VARIABLES: CLASS TYPE: Input COMPONENT/ENTRY POINT: $$WHOIS2 VARIABLES: MEMBER TYPE: Output VARIABLES: CLASS TYPE: Input COMPONENT/ENTRY POINT: $$ISA VARIABLES: USER TYPE: Input VARIABLES: CLASS TYPE: Input VARIABLES: ERR TYPE: Output SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: MAILMAN SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES SUBSCRIBING DETAILS: Added 12/20/2007 DBA Comments: 10/25/12-MM: Patient Assessment Documentation package (NUPA) has been added as a subscriber for NUPA*1*1. 7/9/14-MC: PADP did not complete the class 3 to class 1 conversion process, but it is still installed at sites. Sites have the option to utilize the program, however it is no longer nationally supported. There will be no further patching of the package. PADP has been removed as a subscriber to this ICR. DATE/TIME EDITED: DEC 20, 2007@09:19 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MCCLENAHAN,MARGY DATE/TIME EDITED: OCT 25, 2012@09:11 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: DEZORZI,KEVIN WITH CONCURRENCE OF: MCCLENEHAN,MARGY NUMBER: 1546 IA #: 1546 FILE NUMBER: 8930.3 GLOBAL ROOT: USR(8930.3, DATE CREATED: JUN 18, 1996 CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: READ OF USR(8930.3 ID: USR(8930.3, GLOBAL REFERENCE: USR(8930.3 GLOBAL REFERENCE: USR(8930.3,'B',Y GENERAL DESCRIPTION: The Scheduling Developers would like the following on-going integration agreement with the Authorization/Subscription Developers: Read access to the following global: ^USR(8930.3 (The USR CLASS MEMBERSHIP File (#8930.3) We do the following operations: o $DATA check of ^USR(8930.3,"B",Y) as a screen for the PRACTITIONER Field (#.03) of the POSITION ASSIGNMENT HISTORY File (#404.52). o $DATA check of ^USR(8930.3) as part of our post-init routine, SCMCPST, which sets the USE USER CLASS FUNCTIONALITY Field (#801) to 'YES', if this global exists (and other conditions are true). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20539833 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 1549 IA #: 1549 FILE NUMBER: 411 GLOBAL ROOT: PRC(411, DATE CREATED: JUN 19, 1996 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1548-B ORIGINAL NUMBER: 1548 ID: PRC(411, GLOBAL REFERENCE: PRC(411,DA,0) FIELD NUMBER: .01 FIELD NAME: STATION NUMBER LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: The valid station number identifying the primary station as well as substations for integrated systems. GENERAL DESCRIPTION: The Equipment/Turn-In Request package would like access to IFCAP's file ADMIN. ACITIVITY SITE PARAMETER (#411) to identify a station for requests and 2237s. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20896722 SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1550 IA #: 1550 FILE NUMBER: 410.2 GLOBAL ROOT: PRCS(410.2 DATE CREATED: JUN 19, 1996 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1548-C ORIGINAL NUMBER: 1548 ID: PRCS(410.2 GLOBAL REFERENCE: PRCS(410.2,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: Identifies the type of request. GENERAL DESCRIPTION: A CLASSIFICATION OF REQUEST may be assigned to a 2237. The Equipment/Turn-In Request package would like to be able to assign this field early in the request package and transfer it to the 2237. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20896726 SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1551 IA #: 1551 FILE NUMBER: 410.7 GLOBAL ROOT: PRCS(410.7 DATE CREATED: JUN 19, 1996 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1548-D ORIGINAL NUMBER: 1548 ID: PRCS(410.7 GLOBAL REFERENCE: PRCS(410.7,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: Definition in file is that this is the name of the sub-control point. GENERAL DESCRIPTION: The SORT GROUP file (#410.7) is used as a sorting mechanism of requests to categorize their particular cost distribution for 2237s. The Equipment/Turn-In Request package would like to prompt for this information early in the request and then pass it on to the 2237. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20896732 SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1552 IA #: 1552 DATE CREATED: JUN 19, 1996 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCUESIG NAME: DBIA1548-E ORIGINAL NUMBER: 1548 ID: PRCUESIG GENERAL DESCRIPTION: The Equipment/Turn-In Request package would like permission to use PRCUSESIG to check for the electronic signature code. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20896740 COMPONENT/ENTRY POINT: ESIG COMPONENT DESCRIPTION: Asks user for electronic signature code VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: The user who is entering their electronic signature VARIABLES: FAIL TYPE: Output VARIABLES DESCRIPTION: The status returned on whether signature entered correctly or not. SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 1553 IA #: 1553 DATE CREATED: JUN 24, 1996 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA1553 GENERAL DESCRIPTION: This request is to allow Integrated Billing to hard-set an identifier node in the Procedures (#304) sub-file of the Bill/Claims (#399) file. File #399 is a very large file which we would prefer not to distribute just to update the modifier of one of its sub-files. The post-init to patch IB*2*62 will set this identifier. The following code will be executed: S ^DD(399.0304,0,"ID","WRITE")="D DISPID^IBCSC4D" STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20824812 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 1554 IA #: 1554 DATE CREATED: JUN 26, 1996 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAPIIB NAME: DBIA1554 ID: PXAPIIB GENERAL DESCRIPTION: A call is made to POV^PXAPIIB to retrieve all diagnosis (Purpose of Visit) for a visit so they can be added to a claim. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20847955 COMPONENT/ENTRY POINT: POV(VISIT,ARRAY) COMPONENT DESCRIPTION: Returns an array with a string of information on each diagnosis (POV) found for the requested visit. Output is passed in ARRAY(I)=string. VARIABLES: VISIT TYPE: Input VARIABLES DESCRIPTION: Pointer to Visit file (9000010) entry of the visit the diagnosis is being requested for. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: A pass by reference variable name of the array that should contain all diagnosis for the visit on exit. VARIABLES: I TYPE: Output VARIABLES DESCRIPTION: Internal entry number of the diagnosis in the V POV file (9000010.07). VARIABLES: string TYPE: Output VARIABLES DESCRIPTION: The 0 node of the V POV file (9000010.07) entry for the diagnosis. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES NUMBER: 1555 IA #: 1555 FILE NUMBER: 200 GLOBAL ROOT: VA(200 DATE CREATED: JUN 26, 1996 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PCMM Needs DBIA For .01 Field Pointing to File #200 ID: VA(200 GENERAL DESCRIPTION: The SCHEDULING USER PREFERENCE File (#403.35) has a .01 field (SCHEDULING USER) that points to and is DINUMed to the NEW PERSON File (#200). .01 fields are specifically excluded from the normal permission for fields to point to File #200. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20854150 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 1556 IA #: 1556 FILE NUMBER: 1 GLOBAL ROOT: DIC( DATE CREATED: JUL 01, 1996 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: SCHEDULING REPORTS Field Points to File #1 ID: DIC( GENERAL DESCRIPTION: The Scheduling Developers would like the following integration agreement with the FileMan Developers: With PCMM (SD*5.3*41), in the SCHEDULING REPORT File (#404.92), in the FILES multiple (#40), there is a FILE field (#.01) which points to the FILE file. This field contains the name of the file from which selections are made. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20876242 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 1557 IA #: 1557 DATE CREATED: JUL 03, 1996 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: Salt Lake City USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUSESIG1 NAME: E-SIG API'S ID: XUSESIG1 GENERAL DESCRIPTION: This is the list of supported references to the E-SIG facility. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: CHKSUM COMPONENT DESCRIPTION: $$CHKSUM^XUSESIG1($name_value,flag) This would take a root ($name_value) and build a checksum for all data in the root. (Not used now, flag would be used when there is more that one checksum algorithm.) VARIABLES: name_value TYPE: Input VARIABLES DESCRIPTION: This is a global root as would be returned from $NAME. VARIABLES: flag TYPE: Input VARIABLES DESCRIPTION: Not used at this time. COMPONENT/ENTRY POINT: ESBLOCK COMPONENT DESCRIPTION: $$ESBLOCK^XUSESIG1(ien) This extrinsic function would return the set of fields from the new person file that are need as part of the hash for a acceptable E-Sig. If IEN is not passed in then DUZ is used. (E-Sig block, E-Sig title, Degree, Current Date/Time) VARIABLES: ien TYPE: Input VARIABLES DESCRIPTION: Optional. The default is to use the DUZ of the current user. This is the IEN of the new person file entry to return data for. COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: $$EN^XUSESIG1(checksum,esblock) If the ESBLOCK is not passed then the function would get the ESBLOCK. In either case it would encode the ESBLOCK using the checksum as the KEY. Return a encoded string. VARIABLES: checksum TYPE: Input VARIABLES DESCRIPTION: A number that will reveil if the data in the root has been changed. VARIABLES: esblock TYPE: Input VARIABLES DESCRIPTION: Optional. This should be the data returned from the $$ESBLOCK^XUSESIG1 call. COMPONENT/ENTRY POINT: CMP COMPONENT DESCRIPTION: $$CMP^XUSESIG1(checksum,$name_value) The extrinsic function would compare the checksum passed in to the calculated value from the $NAME_VALUE. Return 1 for match, 0 for no match. VARIABLES: checksum TYPE: Input VARIABLES DESCRIPTION: The output from the $$CHKSUM^XUSESIG1 call. VARIABLES: name_value TYPE: Input VARIABLES DESCRIPTION: This is a global root as would be returned from $NAME. COMPONENT/ENTRY POINT: DE COMPONENT DESCRIPTION: $$DE^XUSESIG1(checksum,encoded_string) This extrinsic function would decode the string using the checksum as the key. Return a decoded string. VARIABLES: checksum TYPE: Input VARIABLES DESCRIPTION: The output from the $$CHKSUM^XUSESIG1 call. VARIABLES: encoded_string TYPE: Input VARIABLES DESCRIPTION: The output from the $$EN^XUSESIG1 call. DATE ACTIVATED: MAR 24, 2008 DATE/TIME EDITED: MAR 24, 2008@16:47 ACTION: APPROVED AT THE REQUEST OF: THOMAS,KATIE NUMBER: 1558 IA #: 1558 FILE NUMBER: 509850.6 GLOBAL ROOT: ACK(509850.6, DATE CREATED: JUL 17, 1996 CUSTODIAL PACKAGE: QUASAR CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: A&SP Clinic Visit File ID: ACK(509850.6, GLOBAL REFERENCE: ACK(509850.6,D0,0) FIELD NUMBER: .01 FIELD NAME: DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: PATIENT NAME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2.6 FIELD NAME: CLINIC LOCATION LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: ACK(509850.6,D0,2) FIELD NUMBER: 4 FIELD NAME: CLINIC STOP CODE LOCATION: 2;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .27 FIELD NAME: LEAD ROLE LOCATION: 2;7 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: ACK(509850.6,D0,3,D1,0) FIELD NUMBER: .01 FIELD NAME: PROCEDURE CODE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: VOLUME LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: PROCEDURE CODE sub-file (#509850.61). GLOBAL REFERENCE: ACK(509850.6,D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: DIAGNOSTIC CODE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: ACK(509850.6,D0,3,D1,1,D2,0) FIELD NUMBER: .04 FIELD NAME: CPT MODIFIER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: ACK(509850.6,C,DFN,DO) GENERAL DESCRIPTION: DSS Extracts will reference QUASAR data from the A&SP CLINIC VISIT file (#509850.6). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30358737 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION DBA Comments: JSH 2006-11-05/ Added SCI&D as subscriber as per Sergey Gavrilov/QUASAR and Lucille Harmon/SCI&D. JSH 2006-11-05/ Added "C" reference as a permissable direct global read as per same. JSH 2006-11-05/ Added better IA name. DATE/TIME EDITED: NOV 03, 2006@15:35 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SWESKY,JEFF WITH CONCURRENCE OF: GAVRILOV,SERGEY NUMBER: 1559 IA #: 1559 FILE NUMBER: 509850.8 GLOBAL ROOT: ACK(509850.8, DATE CREATED: JUL 17, 1996 CUSTODIAL PACKAGE: QUASAR CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1559 ID: ACK(509850.8, GLOBAL REFERENCE: ACK(509850.8, FIELD NUMBER: 727.8251 FIELD NAME: AUDIOLOGY DSS UNIT LINK LOCATION: DSS;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 727.8252 FIELD NAME: SPEECH PATHOLOGY DSS UNIT LINK LOCATION: DSS;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .01 FIELD NAME: SITE NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: ACK(509850.8,D0,2,D1,2, FIELD NUMBER: .01 FIELD NAME: PROCEDURE CODE YEAR LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: USE EVENT CAPTURE CODES LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DSS Extracts will reference QUASAR data from the A&SP SITE PARAMETER file (#509850.8). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34407330 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1560 IA #: 1560 FILE NUMBER: 509850.4 GLOBAL ROOT: ACK(509850.4, DATE CREATED: JUL 17, 1996 CUSTODIAL PACKAGE: QUASAR CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1560 ID: ACK(509850.4, GLOBAL REFERENCE: ACK(509850.4,D0,0) FIELD NUMBER: .01 FIELD NAME: CODE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DSS Extracts will reference QUASAR data from the A&SP PROCEDURE CODE file (#509850.4). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21054080 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1561 IA #: 1561 FILE NUMBER: 724 GLOBAL ROOT: ECD( DATE CREATED: JUL 18, 1996 CUSTODIAL PACKAGE: EVENT CAPTURE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DSS UNIT file 724 ID: ECD( GLOBAL REFERENCE: ECD(D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: MEDICAL SPECIALTY LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: COST CENTER LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: UNIT NUMBER LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains a number that is used locally to identify and classify DSS units. GLOBAL DESCRIPTION: This file contains all DSS units defined for use in the Event Capture software. Entries cannot be deleted but may be inactivated using the Event Capture software. The fields representing service, medical specialty and cost center are required for each DSS unit. These fields can be edited using options on the Event Capture Management Menu but cannot be deleted. This file should NOT be modified directly using VA FileMan. The Event Capture Management Menu provides the options necessary to create, edit, and inactivate all DSS units. GENERAL DESCRIPTION: DSS Extracts and QUASAR will reference Event Capture data from the DSS UNIT file (#724). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25458313 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany SUBSCRIBING PACKAGE: QUASAR ISC: Birmingham NUMBER: 1563 IA #: 1563 FILE NUMBER: 3.8 GLOBAL ROOT: XMB(3.8, DATE CREATED: JUL 19, 1996 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1563 ID: XMB(3.8, GLOBAL REFERENCE: XMB(3.8,D0,6,D1,0) FIELD NUMBER: 12 FIELD NAME: MEMBERS - REMOTE LOCATION: 6;0 ACCESS: Write w/Fileman GENERAL DESCRIPTION: As part of the installation process, the Ambulatory Care Reporting Project is granted permission to add 'XXX@Q-ACS.MED.VA.GOV' to the REMOTE MEMBER multiple (#12) of the 'SCDX AMBCARE TO NPCDB' entry in the MAIL GROUP file (#3.8). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20605860 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 1564 IA #: 1564 FILE NUMBER: 3.6 GLOBAL ROOT: XMB(3.6, DATE CREATED: JUL 19, 1996 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1564 ID: XMB(3.6, GLOBAL REFERENCE: XMB(3.6,D0,2,D1,0) FIELD NUMBER: 4 FIELD NAME: MAIL GROUP LOCATION: 2;0 ACCESS: Write w/Fileman GENERAL DESCRIPTION: As part of the installation process, the Ambulatory Care Reporting Project is granted permission to add the mail group contained in the OPC GENERATE MAIL GROUP field (#216) of the MAS PARAMETER file (#43) to the MAIL GROUP multiple (#4) of the 'SCDX AMBCARE TO NPCDB SUMMARY' entry in the BULLETIN file (#3.6). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20605860 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 1565 IA #: 1565 FILE NUMBER: 779.001 GLOBAL ROOT: HL(779.001, DATE CREATED: JUL 19, 1996 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1565 ID: HL(779.001, GLOBAL REFERENCE: HL(779.001,D0,0) FIELD NUMBER: .01 FIELD NAME: CODE LOCATION: 0;1 ACCESS: Write w/Fileman FIELD NUMBER: 2 FIELD NAME: DESCRIPTION LOCATION: 0;2 ACCESS: Write w/Fileman GLOBAL REFERENCE: HL(779.001,D0,1,D1,0) FIELD NUMBER: 100 FIELD NAME: VERSION LOCATION: 1;0 ACCESS: Write w/Fileman GENERAL DESCRIPTION: As part of the installation process, the Ambulatory Care Reporting Project is granted permission to create the following entry in the HL7 EVENT TYPE CODE file (#779.001) CODE (#.01): Z00 DESCRIPTION (#2): Ambulatory Care transmission to/from NPCDB VERSION (#100): 2.2 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20606146 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 1566 IA #: 1566 FILE NUMBER: 869.2 GLOBAL ROOT: HLCS(869.2, DATE CREATED: JUL 19, 1996 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1566 ID: HLCS(869.2, GLOBAL REFERENCE: HLCS(869.2,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Write w/Fileman FIELD NUMBER: .02 FIELD NAME: LLP TYPE LOCATION: 0;2 ACCESS: Write w/Fileman GLOBAL REFERENCE: HLCS(869.2,D0,100) FIELD NUMBER: 100 FIELD NAME: MAIL GROUP LOCATION: 100;1 ACCESS: Write w/Fileman GENERAL DESCRIPTION: As part of the installation process, the Ambulatory Care Reporting Project is granted permission to create the following entry in the HL LOWER LEVEL PROTOCOL PARAMETER file (#869.2) NAME (#.01): AMB-CARE LLP TYPE (#.02): MAILMAN MAIL GROUP (#100): SCDX AMBCARE TO NPCDB STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 20606146 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 1568 IA #: 1568 FILE NUMBER: 1 GLOBAL ROOT: DIC( DATE CREATED: JUL 30, 1996 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Set File Security for Medicine Files ID: DIC( GENERAL DESCRIPTION: The Medicine package uses the KIDS utility to export the package software. Medicine exports file level security codes for its data dictionaries. Currently, KIDS will not change the file level security codes on the target system if they already exist. This DBIA allows Medicine to check the file level security nodes on the package's data dictionaries and change the target system's file level security to match the ones being exported. The nodes changed are: ^DIC(File,0,"DD")="@" and ^DIC(File,0,"AUDIT")="@" Where 'File' has the following values: 690 690.1 690.2 690.5 690.97 690.99 691 691.1 691.5 691.6 691.7 691.8 691.9 692 693 693.2 693.3 693.5 693.6 694 694.1 694.5 694.8 695 695.1 695.3 695.4 695.5 695.6 695.8 695.9 696 696.1 696.2 696.3 696.4 696.5 696.7 696.9 697 697.1 697.2 697.3 697.5 698 698.1 698.2 698.3 698.4 698.6 698.9 699 699.48 699.5 699.55 699.57 699.6 699.7 699.81 699.82 699.83 699.84 699.85 699.86 699.88 700 700.1 700.2 700.5 701 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21130894 SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Hines NUMBER: 1569 IA #: 1569 DATE CREATED: AUG 01, 1996 CUSTODIAL PACKAGE: LIST MANAGER CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VALM NAME: TEXT INTEGRATION UTILITIES ID: VALM GENERAL DESCRIPTION: TIU is using List Manager. For one of our LM displays, we need to display at the beginning of the screen a 60 character name, then 4 or 5 short fields, then a different 60 character name. Sites don't want either 60 character name truncated. Since the screen is only 80 characters wide, we need to set one scroll lock long enough to display a meaningful part of the name and still show our short fields, and then to set a second, very short scroll lock so we can display the whole second 60 character name with enough scroll locked to identify the entry. I have found that if I set VALM("FIXED") and VALMLFT, I can essentially set two different scroll locks, enabling me to display both 60 character names meaningfully. This also enables me to code a PRINT LIST Action which prints columns beyond page width on a separate page rather than wrapping them. Since we are using many columns beyond 80 characters, this is important to our users. For the sake of clarity, this was NOT a simple matter of setting those two variables: I also had to rewrite for TIU the Scroll Right/Left actions and the Print List Action rather than use the actions LM exports. TIU requests a private Integration Agreement with List Manager to read and set the variables VALMLFT and VALM("FIXED"). We understand that if/when LM adds functionality affecting these variables, we would need to rewrite portions of our code. VIEWER: PRICE,DEBORAH VIEWER: RUSSELL,JOEL VIEWER: CRAVEN,MARCIE J VIEWER: HOLMES,ROY A STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21211315 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: EN^VALM is the main entry point for List Manager, called with the name of a List Manager Template. VARIABLES: VALM TYPE: Both VARIABLES DESCRIPTION: This agreement is for the subscripted variable VALM("FIXED"). VALM("FIXED") is the next column to the right AFTER the columns occupied by the Caption field which is scroll locked. It functions as the rightmost column of screen which remains fixed when a user scrolls to the right. VARIABLES: VALMLFT TYPE: Both VARIABLES DESCRIPTION: For a given horizontal scroll setting, VALMLFT is the character position in the List Manager list array string of the character displayed in the leftmost nonfixed column of the screen. NUMBER: 1571 IA #: 1571 FILE NUMBER: 757.01 GLOBAL ROOT: LEX(757.01, DATE CREATED: AUG 07, 1996 CUSTODIAL PACKAGE: LEXICON UTILITY CUSTODIAL ISC: Salt Lake City USAGE: Supported TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: LEXICON UTILITY EXPRESSIONS ID: LEX(757.01, GLOBAL REFERENCE: LEX(757.01,D0,0) FIELD NUMBER: .01 FIELD NAME: Display Text LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This Display Text contained in the Lexicon Utility is the text which will be used in all display/print routines. GENERAL DESCRIPTION: The Lexicon Utility (version 2.0 and greater) will maintain static internal entry numbers (IENs) for the Expression file (#757.01). As a result, this file may be pointed to to retrieve the Display Text (.01) for both current Expressions and deactivated Expressions (Deactivation Flag 757.01;9 1;5 set to 1). This agreement is a follow-on to DBIA 457 (version 1.0) and is re-issued to include the package name, namespace and global root changes occurring in version 2.0. This is not an amendment to 457. Version 1.0 Version 2.0 Package name Clinical Lexicon Utility Lexicon Utility Namespace GMPT LEX Expression File Global Root ^GMP(757.01, ^LEX(757.01, STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21263931 NUMBER: 1573 IA #: 1573 DATE CREATED: AUG 07, 1996 CUSTODIAL PACKAGE: LEXICON UTILITY CUSTODIAL ISC: Salt Lake City USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LEXU NAME: LEXU ID: LEXU GENERAL DESCRIPTION: LEXU is a utility routine for the Lexicon Utility which contains functions useful in retrieving classification code(s) for a term. This agreement is a follow-on to DBIA 10148 (version 1.0) and is re-issued to include the package name, namespace, routine name and global root changes occurring in version 2.0. This is not an amendment to 10148. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 36044879 COMPONENT/ENTRY POINT: $$ICDONE(IEN,DATE) COMPONENT DESCRIPTION: Returns either a single active ICD-9 code linked to the Lexicon expression or Null if no ICD-9 code is found. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal Entry Number in the Expression file ^LEX(757.01). VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: This is a date in Fileman format used to check if a code is active or inactive on a specified date. If not supplied, it will default to TODAY. COMPONENT/ENTRY POINT: $$ICD(IEN,DATE) COMPONENT DESCRIPTION: Returns either a string of active ICD-9 codes linked to an expression (separated by semicolon, i.e., ICD;ICD;ICD) or Null if no ICD-9 codes are found. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal Entry Number in the Expression file ^LEX(757.01). VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: This is a date in Fileman format used to check if a code is active or inactive on a specified date. If not supplied, it will default to TODAY. COMPONENT/ENTRY POINT: $$CPTONE(IEN,DATE) COMPONENT DESCRIPTION: Returns either a single active CPT-4 code linked to the Lexicon expression or Null if no CPT-4 code is found. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal Entry Number in the Expression file ^LEX(757.01). VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: This is a date in Fileman format used to check if a code is active or inactive on a specified date. If not supplied, it will default to TODAY. COMPONENT/ENTRY POINT: $$DSMONE(IEN) COMPONENT DESCRIPTION: Returns either a single DSM-IV code linked to the Lexicon expression or Null if no DSM-IV code is found. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal Entry Number in the Expression file ^LEX(757.01). COMPONENT/ENTRY POINT: $$CPCONE(IEN,DATE) COMPONENT DESCRIPTION: Returns either a single active HCPCS code linked to the Lexicon expression or Null if no HCPCS codes exist. HCPCS stands for Healthcare Financing Administration (HCFA) Common Procedure Coding System. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal Entry Number in the Expressions file ^LEX(757.01). VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: This is a date in Fileman format used to check if a code is active or inactive on a specified date. If not supplied, it will default to TODAY. NUMBER: 1574 IA #: 1574 FILE NUMBER: 43 GLOBAL ROOT: DG(43 DATE CREATED: AUG 07, 1996 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1574 ID: DG(43 GLOBAL REFERENCE: DG(43,D0,0) FIELD NUMBER: 48 FIELD NAME: DEFAULT EF PRINTER LOCATION: 0;48 ACCESS: Read w/Fileman FIELD DESCRIPTION: Printer to be used when printing Encounter Forms from the Registration process. GLOBAL REFERENCE: DG(43,D0,GL) FIELD NUMBER: 11 FIELD NAME: MULTIDIVISION MED CENTER? LOCATION: GL;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: Field indicates whether the Medical Center is multidivisional. GENERAL DESCRIPTION: AICS is requesting direct global access to the following fields within file 43 (MAS Parameters): 48 DEFAULT EF PRINTER 0;48 <-- Read 11 MULTIDIVISION MEDICAL CENTER "GL";2 <-- Read During the Registration process, an Encounter Form may be printed. It is necessary to determine if the site has defined a default EF printer to print the EF on. Access to piece 48 of the 0th node would allow this. Additionally, throughout the AICS package, it is necessary to determine if the facility is Multidivisional. Access to the 2nd piece of the GL node would provide us with this information. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21275073 SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring NUMBER: 1575 IA #: 1575 DATE CREATED: AUG 07, 1996 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SCDXUTL NAME: AMBCARE DATE CALLS ID: SCDXUTL GENERAL DESCRIPTION: The calls in this agreement are to be used in conjunction with the installation and running of the Ambulatory Care Report Project Patch SD*53*44. STATUS: Active COMPONENT/ENTRY POINT: $$DATE() COMPONENT DESCRIPTION: This function call accepts a date and will return whether the new or old Scheduling visit file limitations are to be used. Based upon a date input returns whether this date is older than the date in the corresponding parameter. VARIABLES: date TYPE: Input VARIABLES DESCRIPTION: This is a date that is to be compared to the 10/1 date. If the input date is before the 10/1 date than a zero will be returned. This indicates that the old limitation structure should be used. If the input date is after the 10/1 date than a one will be returned. This indicates that the new limitation structure should be used. COMPONENT/ENTRY POINT: $$FMDATE() COMPONENT DESCRIPTION: This function returns the date at which the new limitation structure is to take place. VARIABLES: DATE TYPE: Output VARIABLES DESCRIPTION: This function call accepts no inputs. It will return the date the new limitation structure is to take place in a FM format. COMPONENT/ENTRY POINT: $$CLOSEFM() COMPONENT DESCRIPTION: This entry point accepts no inputs. It will return what the close out date is in FM format. COMPONENT/ENTRY POINT: $$CLOSED() COMPONENT DESCRIPTION: CLOSED(DATE) This entry point accepts a date in FM format to compare to the close out date. It will return a 1 if the close out period is over or a zero if close out can still occur. VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: This is a date to be compared to the close out date. It is in FM formatt. COMPONENT/ENTRY POINT: $$INPATENC(PTR,PTR2) COMPONENT DESCRIPTION: This function call will determine whether an outpatient encounter is for an inpatient appointment. VARIABLES: PTR TYPE: Input VARIABLES DESCRIPTION: This is a pointer (internal entry number) from one of the following files:- - TRANSMITTED OUTPATIENT ENCOUNTER file (#409.73) - OUTPATIENT ENCOUNTER file (#409.68) - DELETED OUTPATIENT ENCOUNTER file (#409.74) VARIABLES: PTR2 TYPE: Input VARIABLES DESCRIPTION: This value denotes the file being pointed to - 0 - TRANSMITTED OUTPATIENT ENCOUNTER file (Default) 1 - OUTPATIENT ENCOUNTER file 2 - DELETED OUTPATIENT ENCOUNTER file VARIABLES: $$INPATENC TYPE: Output VARIABLES DESCRIPTION: 1 - Encounter is an inpatient appointment. 0 - Encounter is not an inpatient appointment A value of 0 is returned if a valid pointer is not passed or the entry in the TRANSMITTED OUTPATIENT ENCOUNTER file does not point to a valid entry in the OUTPATIENT ENCOUNTER file or DELETED OUTPATIENT ENCOUNTER file. SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 1579 IA #: 1579 DATE CREATED: JUN 30, 2003 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SDCO22 NAME: SCHEDULING CLASSIFICATION ID: SDCO22 GENERAL DESCRIPTION: This IA is for the purpose of calling into routine ^SDCO22 to ask the classification questions such as Service Connected, Agent Orange, Ionizing Radiation and Environmental Contaminants. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21289383 COMPONENT/ENTRY POINT: AO COMPONENT DESCRIPTION: Ask Agent Orange Exposure Classification VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient file IEN VARIABLES: SDOE TYPE: Input VARIABLES DESCRIPTION: Outpatient Encounter file IEN (optional) COMPONENT/ENTRY POINT: EC COMPONENT DESCRIPTION: Ask Environmental Contaminant Exposure Classification VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient file IEN VARIABLES: SDOE TYPE: Input VARIABLES DESCRIPTION: Outpatient Encounter file IEN (optional) COMPONENT/ENTRY POINT: IR COMPONENT DESCRIPTION: Ask Ionizing Radiation Exposure Classification VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient file IEN VARIABLES: SDOE TYPE: Input VARIABLES DESCRIPTION: Outpatient Encounter file IEN (optional) COMPONENT/ENTRY POINT: SC COMPONENT DESCRIPTION: Ask Service Connected Condition Classification VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient file IEN VARIABLES: SDOE TYPE: Input VARIABLES DESCRIPTION: Outpatient Encounter file IEN (optional) COMPONENT/ENTRY POINT: MST COMPONENT DESCRIPTION: Ask Military Sexual Trauma Classification VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient file IEN VARIABLES: SDOE TYPE: Input VARIABLES DESCRIPTION: Outpatient Encounter file IEN (optional) COMPONENT/ENTRY POINT: HNC COMPONENT DESCRIPTION: Ask Head and Neck Classification VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient file IEN VARIABLES: SDOE TYPE: Input VARIABLES DESCRIPTION: Outpatient Encounter file IEN (optional) COMPONENT/ENTRY POINT: CV COMPONENT DESCRIPTION: Ask Combat Veteran Classification VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient file IEN VARIABLES: SDOE TYPE: Input VARIABLES DESCRIPTION: Outpatient Encounter file IEN (optional) VARIABLES: SDDT TYPE: Input VARIABLES DESCRIPTION: Date (optional - SDOE overrides) COMPONENT/ENTRY POINT: SHAD COMPONENT DESCRIPTION: Ask Project 112/SHAD Classification VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient file IEN SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: EVENT CAPTURE ISC: Albany SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING DETAILS: ADDED 3/19/09 DATE/TIME EDITED: MAR 19, 2009@13:31 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: YORTY,ROBERT WITH CONCURRENCE OF: MULLER,RICHARD NUMBER: 1585 IA #: 1585 FILE NUMBER: 409.95 GLOBAL ROOT: SD(409.95, DATE CREATED: AUG 08, 1996 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PRINT MGR CLINIC SETUP ID: SD(409.95, GLOBAL REFERENCE: SD(409.95, GENERAL DESCRIPTION: The purpose of this IA is to retrieve the current print manager clinic setup. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21289383 SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring SUBSCRIBING DETAILS: AICS requires the ability to retrieve the current print manager clinic setup to determine encounter forms defined for a clinic. NUMBER: 1587 IA #: 1587 FILE NUMBER: 81.1 GLOBAL ROOT: DIC(81.1 DATE CREATED: AUG 08, 1996 CUSTODIAL PACKAGE: CPT/HCPCS CODES CUSTODIAL ISC: Albany USAGE: Supported TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: CPT CATEGORY file 81.1 ID: DIC(81.1 CREATOR: ROWE,KIMBALL GLOBAL REFERENCE: DIC(81.1,D0,0) FIELD NUMBER: .01 FIELD NAME: CATEGORY NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This will enable the display of the CPT Category. Both a direct global read and a FileMan read are acceptable. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21264013 DBA Comments: 1/9/15-MC: Kimball Rowe would like to make ICR #1587 the primary ICR for the CPT Category file 81.1. In order to do this he needs to change the ICR from controlled (subscribers Automated Info Collected Sys and VBECS) to supported. Kimball would also like to edit the ICR name from DBIA1587 to CPT CATEGORY file 81.1. Added Kimball as an editor and opened ICR for revision. 1/12/15-MC: Kimball completed requested changes to the ICR name and usage.Activated ICR and removed Kimball as an editor. DATE ACTIVATED: JAN 12, 2015 DATE/TIME EDITED: JAN 09, 2015@11:11 ACTION: APPROVED AT THE REQUEST OF: ROWE,KIMBALL WITH CONCURRENCE OF: ROWE,KIMBALL NUMBER: 1589 IA #: 1589 DATE CREATED: AUG 08, 1996 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRVPCE0 NAME: GMRVPCE0 ID: GMRVPCE0 GENERAL DESCRIPTION: The GMRVPCE0 routine can be used to enter data into the Vitals/Measurements package (using PCE Device Interface Specification), validate measurement data (which uses PCE Device Interface Specification), print help for a particular measurement, or validate a particular measurement. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30390141 COMPONENT/ENTRY POINT: VALIDATE(PXCA) COMPONENT DESCRIPTION: Validate measurement data which is in format described in PCE Device Interface Specification. Returns PXCA("ERROR") if data not valid. VARIABLES: PXCA TYPE: Both VARIABLES DESCRIPTION: PXCA is the the array which contains measurement data to be validated. The array is defined in the PCE Device Interface Specification and must be passed by reference, i.e., .PXCA. The nodes in the array that are used are described below, but their definitions can be found in the PCE Device Interface Specification. PXCA("ENCOUNTER"), PXCA("VITALS") and PXCA("SOURCE") are used by VALIDATE and are input variables. PXCA("ERROR") or PXCA("WARNING") may be returned if data is invalid or duplicate. COMPONENT/ENTRY POINT: STORE(PXCA) COMPONENT DESCRIPTION: This component will validate and store data in the Vitals/Measurements database which is in the format described in the PCE Device Interface Specification. It will return PXCA("ERROR") if there was a problem with the data. VARIABLES: PXCA TYPE: Both VARIABLES DESCRIPTION: PXCA is the the array which contains measurement data to be validated. The array is defined in the PCE Device Interface Specification and must be passed by reference, i.e., .PXCA. The nodes in the array that are used are described below, but their definitions can be found in the PCE Device Interface Specification. PXCA("ENCOUNTER"), PXCA("VITALS") and PXCA("SOURCE") are used by STORE and are input variables. PXCA("ERROR") or PXCA("WARNING") may be returned if data is invalid or duplicate. COMPONENT/ENTRY POINT: HELP(TYPE,HLPARRAY) COMPONENT DESCRIPTION: This procedure will return help for a particular measurement type. VARIABLES: TYPE TYPE: Input VARIABLES DESCRIPTION: Type of measurement. This is a required variable and is the abbreviation for the measurement type found in the PCE Device Interface Specification. VARIABLES: HLPARRAY TYPE: Input VARIABLES DESCRIPTION: This is an optional variable describing location where the help will be found after the procedure call. This is a closed array reference, and if not specified, data will be returned in ^TMP($J,"GMRVHELP"). VARIABLES: TMP($J,'GMRVHELP') TYPE: Output VARIABLES DESCRIPTION: Either this variable or the array defined by HLPARRAY will contain the help for this measurement type. The format is ^TMP($J,"GMRVHELP",X) where X is a number between 1 and the number of lines of help text. COMPONENT/ENTRY POINT: $$RATECHK(TYPE,RATE,UNIT) COMPONENT DESCRIPTION: This function will validate a rate for a particular measurement type. VARIABLES: TYPE TYPE: Input VARIABLES DESCRIPTION: Type of measurement. This is a required variable and is the abbreviation for the measurement type found in the PCE Device Interface Specification. VARIABLES: RATE TYPE: Input VARIABLES DESCRIPTION: The rate to be validated for this measurement type. This variable is required. VARIABLES: UNIT TYPE: Input VARIABLES DESCRIPTION: This is an optional variable which will contain the units of measurement for RATE. VARIABLES: $$RATECHK TYPE: Output VARIABLES DESCRIPTION: The function value will either be 1, rate is valid, or 0 rate is not valid. COMPONENT/ENTRY POINT: $$VMTYPES(TYPE) COMPONENT DESCRIPTION: Returns a 1 if the type of vital is valid and 0 otherwise. VARIABLES: TYPES TYPE: Input VARIABLES DESCRIPTION: Input as the type of vital. VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: Result of extrinsic function ($$VMTYPES(TYPE)) is set to 1 if valid or 0 otherwise. SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING DETAILS: Only are requesting use of RATECHK and HELP entry points. SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City SUBSCRIBING DETAILS: Only are requesting use of STORE and VALIDATE entry points. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING PACKAGE: SURGERY DBA Comments: 5/21/14-MC:Added Surgery as a subscribing package to ICR 1589. Patch SR*3.0*180. Requested by James Harris. Approved by Frank Traxler DATE/TIME EDITED: MAY 21, 2014@14:20 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HARRIS,JAMES WITH CONCURRENCE OF: TRAXLER,FRANK NUMBER: 1590 IA #: 1590 DATE CREATED: AUG 09, 1996 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SCAPMCU2 NAME: PC PRACTITIONER ID: SCAPMCU2 GENERAL DESCRIPTION: This IA is for the purpose of determining the ien and name of the practitioner filling the PC position. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21289383 COMPONENT/ENTRY POINT: $$NMPCPR(DFN[,DATE][,PCROLE]) COMPONENT DESCRIPTION: NMPCPR(DFN,DATE,PCROLE) ;returns ien & name of pract filling pc position VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to patient file VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: Date of interest VARIABLES: PCROLE TYPE: Input VARIABLES DESCRIPTION: Default=1 (PC Practitioner Position) note 2= pc attending SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 1592 IA #: 1592 FILE NUMBER: 9000011 GLOBAL ROOT: AUPNPROB( DATE CREATED: AUG 09, 1996 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PATIENT CARE ENCOUNTER ID: AUPNPROB( GLOBAL REFERENCE: AUPNPROB(D0,0) FIELD NUMBER: .01 FIELD NAME: DIAGNOSIS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.02 FIELD NAME: CONDITION LOCATION: 1;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The purpose of this IA is to allow access to the ^AUPNPROB( global for purposes of gathering information specific to a problem. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21260146 SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring NUMBER: 1593 IA #: 1593 FILE NUMBER: 9999999.27 GLOBAL ROOT: AUTNPOV( DATE CREATED: AUG 09, 1996 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PATIENT CARE ENCOUNTER ID: AUTNPOV( GLOBAL REFERENCE: AUTNPOV(D0,0) FIELD NUMBER: .01 FIELD NAME: NARRATIVE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The purpose of this IA is to allow access to the ^AUTNPOV( global for purposes of gathering information specific to a problem. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21260146 SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT SUBSCRIBING DETAILS: ADDED 10/10/2008 SUBSCRIBING PACKAGE: LEXICON UTILITY SUBSCRIBING DETAILS: added 6/8/2011 DATE/TIME EDITED: OCT 10, 2008@14:54 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: ELLIS,DONNA DATE/TIME EDITED: JUN 08, 2011@11:58 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: ROWE,KIMBALL WITH CONCURRENCE OF: MCCARTHY,CYNTHIA NUMBER: 1594 IA #: 1594 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: AUG 12, 1996 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: APPOINTMENT MULTIPLE ID: DPT( GLOBAL REFERENCE: DPT(D0,'S',D1,0) FIELD NUMBER: .01 FIELD NAME: CLINIC LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: STATUS LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 21 FIELD NAME: OUTPATIENT ENCOUNTER LOCATION: 0;20 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 22 FIELD NAME: ENCOUNTER FORMS PRINTED LOCATION: 0;21 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 23 FIELD NAME: ENCOUNTER FORMS AS ADD-ONS LOCATION: 0;22 ACCESS: Direct Global R/W & w/Fileman GLOBAL DESCRIPTION: Appointment multiple of the Patient file. GENERAL DESCRIPTION: The purpose of this IA is to allow direct reference to the Appointment multiple of the patient file to access a number of fields. This IA will allow reference to the entire ^DPT(D0,'S',D1,0) node. This will prevent multiple global hits to gather data from the fields referenced in this IA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21329390 SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Although Scheduling is allowing AICS to set a variable to the 0th node of this multiple to prevent multiple hits to this node to retrieve the many required fields...AICS will notify Scheduling if it intends to utilize any fields on the 0th node that fall outside of this integration agreement. NUMBER: 1595 IA #: 1595 FILE NUMBER: 1 GLOBAL ROOT: DIC DATE CREATED: AUG 15, 1996 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: FILE SECURITY ID: DIC GLOBAL REFERENCE: DIC(file,0,'DD') GLOBAL DESCRIPTION: Intake/Output can read/write the ^DIC(file,0,"DD") node, where file is a valid file in the Intake/Output package. GLOBAL REFERENCE: DIC(file,0,'DEL') GLOBAL DESCRIPTION: Intake/Output can read/write the ^DIC(file,0,"DEL") node, where file is a valid file in the Intake/Output package. GLOBAL REFERENCE: DIC(file,0,'LAYGO') GLOBAL DESCRIPTION: Intake/Output can read/write the ^DIC(file,0,"LAYGO") node, where file is a valid file in the Intake/Output package. GLOBAL REFERENCE: DIC(file,0,'RD') GLOBAL DESCRIPTION: Intake/Output can read/write the ^DIC(file,0,"RD") node, where file is a valid file in the Intake/Output package. GLOBAL REFERENCE: DIC(file,0,'WR') GLOBAL DESCRIPTION: Intake/Output can read/write the ^DIC(file,0,"WR") node, where file is a valid file in the Intake/Output package. GENERAL DESCRIPTION: Intake/Output V3 is asking for a one-time exemption to be able to read/write to the ^DIC(file,0,access) global where 126 <= file <= 126.95 and access=(DD,RD,WR,LAYGO,DEL). STATUS: Active DURATION: Next Version MAIL MESSAGE: 21373265 GOOD ONLY FOR VERSION: 3.0 SUBSCRIBING PACKAGE: GEN. MED. REC. - I/O ISC: Hines NUMBER: 1597 IA #: 1597 DATE CREATED: AUG 18, 1996 CUSTODIAL PACKAGE: LEXICON UTILITY CUSTODIAL ISC: Salt Lake City USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LEXA NAME: LEXICON EXPRESSION INFORMATION ID: LEXA GENERAL DESCRIPTION: LEXA is used by the Lexicon Utility to perform a silent look-up and return an array of the expression found. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 36044889 COMPONENT/ENTRY POINT: INFO(IEN,DATE) COMPONENT DESCRIPTION: This entry point allows applications to retrieve information about an expression without conducting a search. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal Entry Number in the Expression file #757.01. VARIABLES: LEX TYPE: Output VARIABLES DESCRIPTION: The local array LEX("SEL") contains the major concept, synonyms, lexical variants, associated codes (i.e., ICD, CPT, DSM, etc.), the expression definition (if one exists), the semantic class, the semantic type, and all VA classification sources. See the Lexicon Utility's Technical Manual for a detailed description of this array. VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: This is a date in Fileman format used to check if a code is active or inactive on a specified date. If not supplied, it will default to TODAY. Active codes will be retrieved and displayed. NUMBER: 1599 IA #: 1599 DATE CREATED: AUG 19, 1996 CUSTODIAL PACKAGE: LEXICON UTILITY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LEXDFL NAME: LEXICON USER DEFAULTS - FILTER ID: LEXDFL GENERAL DESCRIPTION: The entry point EN1^LEXDFL will be used to setup user default filter for conducting searches in the Lexicon Utility. This entry point, along with EN1^LEXDCC, EN1^LEXDVO, EN1^LEXDCX and EN1^LEXDDS replaces ^GMPTDUSR used in verion 1.0 of the Clinical Lexicon Utility (see DBIA 339). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21415118 COMPONENT/ENTRY POINT: EN1(LEXAP) COMPONENT DESCRIPTION: This entry point allows a single user to edit their default look-up filter for the Lexicon Utility. VARIABLES: LEXAP TYPE: Input VARIABLES DESCRIPTION: LEXAP is the Internal Entry Number of the Subset Definition file (#757.2) where the application definition is located. SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City NUMBER: 1601 IA #: 1601 DATE CREATED: AUG 19, 1996 CUSTODIAL PACKAGE: LEXICON UTILITY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LEXDCC NAME: LEXICON USER DEFAULTS - DISPLAY ID: LEXDCC GENERAL DESCRIPTION: The entry point EN1^LEXDCC(LEXAP) will be used to setup user default display (classification codes) for conducting searches in the Lexicon Utility. This entry point along with EN1^LEXDFL, EN1^LEXDVO, EN1^LEXDCX and EN1^LEXDDS replaces ^GMPTDUSR used in verion 1.0 of the Clinical Lexicon Utility (see DBIA 339). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21415127 COMPONENT/ENTRY POINT: EN1(LEXAP) COMPONENT DESCRIPTION: This entry point allows a single user to edit their default look-up display for the Lexicon Utility. VARIABLES: LEXAP TYPE: Input VARIABLES DESCRIPTION: LEXAP is the Internal Entry Number of the Subset Definition file (#757.2) where the application definition is located. SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City NUMBER: 1603 IA #: 1603 DATE CREATED: AUG 19, 1996 CUSTODIAL PACKAGE: LEXICON UTILITY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LEXDVO NAME: LEXICON USER DEFAULTS - VOCABULARY ID: LEXDVO GENERAL DESCRIPTION: The entry point EN1^LEXDVO will be used to setup user default vocabulary for conducting searches in the Lexicon Utility. This entry point, along with EN1^LEXDFL, EN1^LEXDCC, EN1^LEXDCX and EN1^LEXDDS replaces ^GMPTDUSR used in version 1.0 of the Clinical Lexicon Utility (see DBIA 339). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21415142 COMPONENT/ENTRY POINT: EN1(LEXAP) COMPONENT DESCRIPTION: This entry point allows a single user to edit their default look-up vocabulary for the Lexicon Utility. VARIABLES: LEXAP TYPE: Input VARIABLES DESCRIPTION: LEXAP is the Internal Entry Number of the Subset Definition file (#757.2) where the application definition is located. SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City NUMBER: 1605 IA #: 1605 DATE CREATED: AUG 19, 1996 CUSTODIAL PACKAGE: LEXICON UTILITY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LEXDCX NAME: LEXICON USER DEFAULTS - SHORTCUTS ID: LEXDCX GENERAL DESCRIPTION: The entry point EN1^LEXDCX will be used to setup user default shortcuts by context for conducting searches in the Lexicon Utility. This entry point along with EN1^LEXDFL, EN1^LEXDCC, EN1^LEXDVO and EN1^LEXDDS replaces ^GMPTDUSR used in version 1.0 of the Clinical Lexicon Utility (see DBIA 339). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21415159 COMPONENT/ENTRY POINT: EN1(LEXAP) COMPONENT DESCRIPTION: This entry point allows a single user to edit their default look-up shortcuts for the Lexicon Utility. VARIABLES: LEXAP TYPE: Input VARIABLES DESCRIPTION: LEXAP is the Internal Entry Number of the Subset Definition file (#757.2) where the application definition is located. SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City NUMBER: 1607 IA #: 1607 DATE CREATED: AUG 19, 1996 CUSTODIAL PACKAGE: LEXICON UTILITY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LEXDDS NAME: LEXICON USER DEFAULTS - LIST ID: LEXDDS GENERAL DESCRIPTION: The entry point EN1^LEXDDS will be used to list user defaults for searching the Lexicon to a device (terminal or printer). This entry point along with EN1^LEXDFL, EN1^LEXDCC, EN1^LEXDVO and EN1^LEXDCX replaces ^GMPTDUSR used in version 1.0 of the Clinical Lexicon Utility (see DBIA 339). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21415178 COMPONENT/ENTRY POINT: EN1(LEXAP) COMPONENT DESCRIPTION: This entry point allows a single user to list their Lexicon Utility defaults to a device (terminal or printer). VARIABLES: LEXAP TYPE: Input VARIABLES DESCRIPTION: LEXAP is the Internal Entry Number of the Subset Defintion file (#757.2) where the application definition is located. SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City NUMBER: 1609 IA #: 1609 DATE CREATED: AUG 19, 1996 CUSTODIAL PACKAGE: LEXICON UTILITY CUSTODIAL ISC: Salt Lake City USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LEXSET NAME: LEXICON SETUP SEARCH PARAMETERS ID: LEXSET GENERAL DESCRIPTION: The Lexicon Utility uses LEXSET to setup search parameters based on applications definitions, subset definitions and user defaults stored in the Subsets Definition file (#757.2). These search parameters are stored in the global array ^TMP("LEXSCH",$J). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 36044886 COMPONENT/ENTRY POINT: CONFIG(LEXNS,LEXSS,DATE) COMPONENT DESCRIPTION: This entry point may be used by other applicaitons to setup parameters for conducting a search of the Lexicon Utility. VARIABLES: LEXNS TYPE: Input VARIABLES DESCRIPTION: LEXNS is an application identifier (formerly namespace) which tells the setup routines which application definition in file 757.2 to use to retrieve application defaults (i.e., global, display, filter, etc.) Acceptable values for LEXNS are found in file 757.2 in the "AN" index: ^LEXT(757.2,"AN",LEXNS) VARIABLES: LEXSS TYPE: Input VARIABLES DESCRIPTION: LEXSS is a subset identifier which tells the setup routines which subset definition in file 757.2 to use to retrieve subset and user defaults (i.e., global, display, filter, etc.). Acceptable values for LEXSS may be found in file 7 57.2 in either the "AA" or the "AB" indexes: ^LEXT(757.2,"AA",LEXSS) ^LEXT(757.2,"AB",LEXSS) VARIABLES: TMP(LEXSCH,$J) TYPE: Output VARIABLES DESCRIPTION: ^TMP("LEXSCH",$J) is a global array used by the Lexicon Utility to control how a search of the Lexicon is to be conducted. It contains the following segments: APP Application (from LEXNS) DIS Display format FIL Filter FLN File Number GBL Global (Fileman DIC) IDX Index used during the search LEN Length of list to display LOC Hospital Location OVR Overwrite User Defaults flag SCT Shortcuts SVC Service UNR Unresolved Narrative flag USR User (DUZ) VDT Version Date Check (for classification codes) VOC Vocabulary A detailed description of this global array may be found in the Lexicon Utility's Technical Manual. VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: This is a date in Fileman format used to check classification code codes to determine if they are active or inactive on the specified date. If not supplied, it will default to TODAY. NUMBER: 1611 IA #: 1611 FILE NUMBER: 9000011 GLOBAL ROOT: AUPNPROB( DATE CREATED: AUG 20, 1996 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PROBLEM FILE UPDATE BY LEXICON ID: AUPNPROB( GLOBAL REFERENCE: AUPNPROB(D0,0) FIELD NUMBER: .01 FIELD NAME: DIAGNOSIS LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Pointer to ICD-9 file #80. GLOBAL REFERENCE: AUPNPROB(D0,1) FIELD NUMBER: 1.01 FIELD NAME: PROBLEM LOCATION: 1;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Pointer to Expressions file #757.01. GENERAL DESCRIPTION: This gives the Lexicon Utility the ability to update the ICD codes and the Lexicon pointer (Problem) in the Problem List application with each new release of the Lexicon. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21341729 SUBSCRIBING PACKAGE: LEXICON UTILITY ISC: Salt Lake City NUMBER: 1612 IA #: 1612 FILE NUMBER: 627.7 GLOBAL ROOT: YSD(627.7, DATE CREATED: AUG 20, 1996 CUSTODIAL PACKAGE: MENTAL HEALTH CUSTODIAL ISC: Dallas USAGE: Supported TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DSM FILE ID: YSD(627.7, GLOBAL REFERENCE: YSD(627.7,D0,0) FIELD NUMBER: .01 FIELD NAME: CODE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: DSM VERSION LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: YSD(627.7,D0,D) FIELD NUMBER: 40 FIELD NAME: DISORDER NAME LOCATION: D;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This will enable access to the DSM Code, DSM version and the Disorder Name. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21371563 NUMBER: 1614 IA #: 1614 DATE CREATED: AUG 20, 1996 CUSTODIAL PACKAGE: LEXICON UTILITY CUSTODIAL ISC: Salt Lake City USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LEXCODE NAME: LEXICON EXPRESSIONS FROM CODES ID: LEXCODE GENERAL DESCRIPTION: The Lexicon Utility uses the LEXCODE routine to extract expressions (terms) in the form of Fileman's output variable "Y" based on a classification code. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 36044887 COMPONENT/ENTRY POINT: EN(LEXSO,DATE) COMPONENT DESCRIPTION: This entry point builds a local array containing expressions linked to an active classification code. VARIABLES: LEXSO TYPE: Input VARIABLES DESCRIPTION: LEXSO is a classification code from one of several sources (i.e., ICD, CPT, DSM). A complete list of these sources can be found in the Lexicon Utility's Technical Manual. VARIABLES: LEXS(SAB,#) TYPE: Output VARIABLES DESCRIPTION: LEXS(SAB,#)=IEN^TERM is a local array containing references to expressions linked to the classification code. SAB refers to the three-character source abbreviation of the classification system (i.e., ICD-9-CM = ICD). A description of this array and a list of the source abbreviations can be found in the Lexicon Utility's Technical Manual. VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: This is a date in Fileman format used to check if a code is active or inactive on a specified date. If not supplied, it will default to TODAY. NUMBER: 1615 IA #: 1615 DATE CREATED: AUG 27, 1996 CUSTODIAL PACKAGE: AUTOMATED INFO COLLECTION SYS CUSTODIAL ISC: Washington USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBDFDEA NAME: ENCOUNTER FORM DATA ENTRY ID: IBDFDEA GENERAL DESCRIPTION: This is a supported reference to process encounter form data. Packages that know patient, visit date/time, and clinic can call this API to use the AICS data entry system to prompt users for encounter data and subsequently store this data using the PCE device interface (this is done automatically using the AICS parameters). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21505189 COMPONENT/ENTRY POINT: EN1(PXCA,IBDF) COMPONENT DESCRIPTION: May be called to use the AICS data entry system to prompt users for encounter data and subsequently store this data using the PCE device interface. VARIABLES: VARIABLES: PXCA TYPE: Both VARIABLES DESCRIPTION: Pass by reference. The results of processing are returned in this array. See PCE device interface manual for description of data nodes. VARIABLES: IBDF TYPE: Input VARIABLES DESCRIPTION: Pass IBDF array to include: REQUIRED: IBDF("APPT") = Appointment date/time IBDF("DFN") = Pointer to Patient file (2) OPTIONAL: IBDF("CLINIC") = Pointer to Hospital Location file (44). If Clinic is not defined and no form printed, data entry will not be allowed. IBDF("NOAPPT") = If the AICS parameters allow for making follow-up appointments, setting this to any non-zero value will suppress the ability to add follow-up appts. IBDF("PROVIDER") = If defined, will be used as primary provider for data entry. Use for provider data entry options. NUMBER: 1616 IA #: 1616 DATE CREATED: AUG 27, 1996 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: PNs TITLE file conv to TIU GENERAL DESCRIPTION: Progress Notes patch GMRP*2.5*44 will be exporting a series of options to facilitate the clean-up of the PNs package in preparation for the conversion to TIU. Once clean-up is complete the final step is to run the conversion of the Progress Notes Title file (#121.2) to the TIU Document Definition file (#8925.1). VIEWER: PRICE,DEBORAH VIEWER: CRAVEN,MARCIE J STATUS: Active DURATION: Next Version MAIL MESSAGE: 21514090 GOOD ONLY FOR VERSION: 1 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 1618 IA #: 1618 DATE CREATED: SEP 13, 1996 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIV NAME: DIV ID: DIV GENERAL DESCRIPTION: Lab is requesting a database agreement to call the DIV routine at line tag VER for the workload data Lab archiving verify option. The option is Verify Files for Archiving. This option allows the user to select either the WKLD DATA (64.1) or LAB MONTHLY WORKLOADS (67.9) file and choose to verify data in either the whole file or entries selected by the Select Entries for Archiving option. Routine name:LRARVER line: ALL D VER^DIV(LRART) where LRART = file # 64.1 or 67.9 line: VWD+1 D VER^DIV(64.11,.LRWIN) where LRWIN is an array of records to verify line: VLMW+1 D VER^DIV(67.911,.LRWIN) where LRWIN is an array of records to verify STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 21684852 COMPONENT/ENTRY POINT: VER SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 1619 IA #: 1619 FILE NUMBER: 357 GLOBAL ROOT: DD(357.02 DATE CREATED: SEP 24, 1996 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Set ID nodes in post-install patch routine ID: DD(357.02 GENERAL DESCRIPTION: KIDS cannot support adding new Identifiers with a partial DD update, AICS wants to send a post-install routine to add a new Identifier and update existing data-file entries for the ENCOUNTER FORM file (357). The following ^DD and ^IBE(357 nodes will be set in a post-install routine: ^DD(357.02,0,"ID",.02)=W " ",@("$P($P($C(59)_$S($D(^DD(357.02,.02,0)): $P(^(0),U,3),1:0)_$E("_DIC_"Y,0),0),$C(59)_$P(^(0),U,2)_"":"",2), $C(59),1)") $P(^DD(357,2,0),"^",2)="357.02I" $P(^IBE(357,D0,2,0),"^",2)="357.02I" STATUS: Active DURATION: Next Version MAIL MESSAGE: 21736049 GOOD ONLY FOR VERSION: 2.1 SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany NUMBER: 1621 IA #: 1621 DATE CREATED: OCT 04, 1996 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: %ZTER NAME: %ZTER (ERROR RECORDING) ID: %ZTER CREATOR: FORT,WALLY GENERAL DESCRIPTION: This IA is to document the supported calls into the %ZTER routine in support of standard error trapping. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29789401 COMPONENT/ENTRY POINT: $$NEWERR COMPONENT DESCRIPTION: This is an extrinsic function to report if the current platform supports the new standard error trapping. It always returns 1. All current VA systems support the new error trapping standard. The SACC has being changed to allow the use of $ESTACK, $ETRAP, $ECODE There are still inconsistency when mixing the old and new error trapping. To set a new trap: N $ESTACK,$ETRAP S $ETRAP="D ERROR^XXX" or N $ESTACK,$ETRAP S $ETRAP="S $EC="""" Q -1" These are still valid. Usage to set new trap: N $ESTACK,$ETRAP S $ETRAP="D ERROR^XXX" Usage to set old style trap: N $ESTACK,$ETRAP S $ETRAP="" S X="ERROR^YYY",@^%ZOSF("TRAP") The vendors differ in how they support the mixing of old and new forms of error trapping. A common way is to look at the current stack frame and, if it finds the old form, it uses that; otherwise it looks for the new style. This gives the old style a local scope of the current stack level. COMPONENT/ENTRY POINT: UNWIND COMPONENT DESCRIPTION: This entry point is used after a package error trap to quit back to the calling routine. Control returns to the level above the one that NEWED $ESTACK. MAIN S X=1 D SUB W X Q SUB N $ESTACK,$ETRAP S $ETRAP="D ERROR" S X=1/0 Q Usage: ERROR D ^%ZTER ;This will record the error info and clear $ECODE S ^XXX="Incomplete record" G UNWIND^%ZTER COMPONENT/ENTRY POINT: %ZTER COMPONENT DESCRIPTION: This routine can be called from the top DO ^%ZTER to record the variables at the current time into the error trap. This will clear $ZE and $ECODE. VARIABLES: %ZT TYPE: Input VARIABLES DESCRIPTION: (optional) The %ZT array can be used to identify a global node whose descendents should be recorded in the error log. When called within the standard Kernel error trap, %ZT is set to record the user's location in the menu system. >S %ZT("^TMP($J)")="" >D ^%ZTER COMPONENT/ENTRY POINT: APPERROR COMPONENT DESCRIPTION: This entry will point allow developers to pass-in the error message that will be displayed in the error trap listing. Usage: D APPERROR^%ZTER("My App Error") VARIABLES: %ZT TYPE: Input VARIABLES DESCRIPTION: The same as calling %ZTER. DATE ACTIVATED: AUG 12, 2009 DATE/TIME EDITED: AUG 12, 2009@10:35 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: FORT,WALLY DATE/TIME EDITED: AUG 12, 2009@12:03 ACTION: APPROVED AT THE REQUEST OF: FORT,WALLY NUMBER: 1622 IA #: 1622 FILE NUMBER: 3.8 GLOBAL ROOT: XMB(3.8, DATE CREATED: OCT 18, 1996 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1622 ID: XMB(3.8, GENERAL DESCRIPTION: Request DBIA to allow MailMan to K ^DD(3.8,0,"ID",5.1) as a post-install routine on a patch. There currently is no other way to remove a field as an identifier. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUL 01, 1997 MAIL MESSAGE: 22063642 SUBSCRIBING PACKAGE: MAILMAN ISC: Oakland NUMBER: 1623 IA #: 1623 DATE CREATED: OCT 22, 1996 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SCDXUAPI NAME: SCDXUAPI - OCCASION OF SERVICE ENTRY ID: SCDXUAPI GENERAL DESCRIPTION: The SCDXUAPI is used to add locations to the HOSPITAL LOCATION file which are deemed occasions of service. This routine has some supported references, but they should only be used after being discussed with the scheduling developers. The subscription to these APIs will be controlled. There are 4 supported calls in this routine. Line tags not specifically mentioned in this DBIA are NOT supported. Detailed documentation on these calls is provided within the routine. The supported calls are: RAD - this tag is specifically written for the radiology package. It allows them to pass in an IEN and convert the entry in file 44 to be an occasion of service location. LOC - main entry point to add occasion of service locations. This may also be used to edit or inactivate a location. SCREEN - provides a screen (S DIC("S")="SCREEN^SCDXUAPI(pkg)" to allow selection of only occasion of service locations which were added by the package passed in. EXEMPT - provides a screen (S DIC("S")="EXEMPT^SCDXUAPI()") which will allow selection of only stop codes which are deemed occasion of service stop codes. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22106730 COMPONENT/ENTRY POINT: $$RAD(IEN,PKG) COMPONENT DESCRIPTION: This call will accept the IEN of a location currently defined. It will check to look for clinic patterns. If none exist, it will update the location fields for an occasion of service location. If there are clinic patterns set up, it will convert the existing entry to non-count and create a new entry with the appropriate fields defined. It will return the IEN of the entry used (either the same as the incoming IEN or the IEN of the new entry which had to be created). Input: IEN of existing entry in the Hospital Location file PKG as either name, namespace, or IEN of package file Output: same IEN or different one if new one had to be created - OR- -1^code^description of error encountered Error codes possible: 1 - Hospital Location IEN is Invalid 2 - Neither institution nor division defined properly for existing entry 3 - Location has an inactivation date 4 - Invalid PKG variable passed in 5 - IEN belongs to another package (PKG file entries don't match) 6 - Invalid stop code passed 7 - Invalid IEN passed to LOC call (package doesn't 'own' IEN) 8 - NAME, INST, and STOP not all defined before LOC call when IEN not set 9 - Unable to add entry to Hospital Location file 10 - Stop code not an occassion of service stop VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of the entry in the Hospital Location file that needs to be converted to an occasion of service location. VARIABLES: PKG TYPE: Input VARIABLES DESCRIPTION: Calling package IEN (pointer to the PACKAGE file). VARIABLES: FUNCTION OUTPUT TYPE: Output VARIABLES DESCRIPTION: Returns one of three things: - If the function was able to alter the location passed in to be an occasion of service location, it will return the same IEN passed in. - If it was unable to use the location passed in, a new one will be created and its IEN will be returned - If the input checks failed for this location, and error message will be returned in the format -1^error code^description. The potential codes and descriptions are: 1 - Hospital Location IEN is Invalid 2 - Neither institution nor division defined properly for existing entry 3 - Location has an inactivation date 4 - Invalid PKG variable passed in 5 - IEN belongs to another package (PKG file entries don't match) 6 - Invalid stop code passed 7 - Invalid IEN passed to LOC call (package doesn't 'own' IEN) 8 - NAME, INST, and STOP not all defined before LOC call when IEN not set 9 - Unable to add entry to Hospital Location file 10 - Stop code not an occassion of service stop COMPONENT/ENTRY POINT: LOC(NAME,INST,STOP,PKG,IEN,INACT) COMPONENT DESCRIPTION: This call will accept the name, division, and stop code (DSS ID) of the clinic location to be add/edited. If the IEN is passed in, the entry with that IEN will be updated. Otherwise, a new entry will be added. If the INACT variable is set to a date, it will INACTIVATE the location (if it exists). Input: NAME of clinic to be created (optional) INST as pointer to the institution file (optional) STOP as number of stop code (not IEN) for occasion of service range of codes (optional) PKG as package file IEN, name, or namespace - required! IEN as IEN of location if you want to update an already existing location (optional. If not defined, NAME, INST, STOP become required) INACT as a date if you want to inactivate the location that has the IEN you defined (optional) Output: IEN of location created/inactivated - OR - -1^error message if problem encountered Possible error messages: 1 - Hospital Location IEN is Invalid 2 - Neither institution nor division defined properly for existing entry 3 - Location has an inactivation date 4 - Invalid PKG variable passed in 5 - IEN belongs to another package (PKG file entries don't match) 6 - Invalid stop code passed 7 - Invalid IEN passed to LOC call (package doesn't 'own' IEN) 8 - NAME, INST, and STOP not all defined before LOC call when IEN not set 9 - Unable to add entry to Hospital Location file 10 - Stop code not an occassion of service stop VARIABLES: NAME TYPE: Input VARIABLES DESCRIPTION: NAME - name of the location to be added. Only required if IEN not passed in. VARIABLES: INST TYPE: Input VARIABLES DESCRIPTION: Pointer to the institution file designating the location of the clinic. Only required if IEN not defined. VARIABLES: stop TYPE: Input VARIABLES DESCRIPTION: External value of the stop code value (example 108). This is only required if IEN is not passed in. VARIABLES: PKG TYPE: Input VARIABLES DESCRIPTION: Required variable indicating the calling package (pointer to the PACKAGE file). VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Optional variable denoting an existing entry in the Hospital Location file. If this exists, the name, institution, stop, and/or inactivation date fields are updated per values passed in. VARIABLES: INACT TYPE: Input VARIABLES DESCRIPTION: Optional: if passed in, it is a date that the location should be inactivated. VARIABLES: FUNCTION OUTPUT TYPE: Output VARIABLES DESCRIPTION: The output will be either: - The IEN of the location created (if IEN is not passed in) - The IEN of the location updated (same as IEN passed in) - An error code if the process could not be completed. The error code will be in the format -1^error code^description where the error codes and descriptions are as follows: 1 - Hospital Location IEN is Invalid 2 - Neither institution nor division defined properly for existing entry 3 - Location has an inactivation date 4 - Invalid PKG variable passed in 5 - IEN belongs to another package (PKG file entries don't match) 6 - Invalid stop code passed 7 - Invalid IEN passed to LOC call (package doesn't 'own' IEN) 8 - NAME, INST, and STOP not all defined before LOC call when IEN not set 9 - Unable to add entry to Hospital Location file 10 - Stop code not an occassion of service stop COMPONENT/ENTRY POINT: $$SCREEN(PKG) COMPONENT DESCRIPTION: Allows a package to select from only the occasion of service locations added by their package. This value should be set to DIC("S") when doing a lookup on the Hospital Location file (S DIC("S")=$$SCREEN^SCDXUAPI(pkg)). VARIABLES: PKG TYPE: Input VARIABLES DESCRIPTION: Pointer to the PACKAGE file indicating the calling package. VARIABLES: FUNCTION OUTPUT TYPE: Output VARIABLES DESCRIPTION: A sting of M code that should be set into the variable DIC("S") when doing a lookup to the Hospital Location file. COMPONENT/ENTRY POINT: $$EXEMPT() COMPONENT DESCRIPTION: Allows a package to select only stop codes which are deemed by Headquarters personnel to be occasion of service stop codes. VARIABLES: FUNCTION OUTPUT TYPE: Output VARIABLES DESCRIPTION: A sting of M code that should be set into the variable DIC("S") when doing a lookup to the Clinic Stop file. SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 1624 IA #: 1624 FILE NUMBER: 2 GLOBAL ROOT: DPT DATE CREATED: OCT 24, 1996 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Cross Reference on Date of Death Field ID: DPT GLOBAL REFERENCE: DPT(D0,.351) => DATE OF DEATH FIELD NUMBER: .351 FIELD NAME: DATE OF DEATH LOCATION: .35;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field is used to indicate a date of death for a patient. GLOBAL DESCRIPTION: ^DD(2,.351,1,52,0) = 2^APSOD^MUMPS ^DD(2,.351,1,52,1) = I $$VERSION^XPDUTL("PSO")>6 D APSOD^PSOCAN3(DA) ^DD(2,.351,1,52,2) = I $$VERSION^XPDUTL("PSO")>6 D APSOD^PSOAUTOC(DA) ^DD(2,.351,1,52,3) = Discontinues Outpatient Medications for v7. ^DD(2,.351,1,52,"%D",0) = ^^2^2^2961024^^^^ ^DD(2,.351,1,52,"%D",1,0) = This xref is used to discontinue all active outpatient medications whenever ^DD(2,.351,1,52,"%D",2,0) = a date of death is entered for the patient. ^DD(2,.351,1,52,"%D",3,0) = This xref is used with v7 of Outpatient Pharmacy (DBIA #1624). ^DD(2,.351,1,52,"%D",4,0) = Kill logic updated with DG*5.3*455. Mail message sent to pharmacy when date ^DD(2,.351,1,52,"%D",5,0) = of death is deleted to holders of PSORPH key. ^DD(2,.351,1,52,"DT") = 2961023 GENERAL DESCRIPTION: A APSOD xref on the Date of Death field in file #2. This Xref will be used to discontinue all active outpatient medication whenever a date of death is entered for a patient. This IA applicable only for Outpatient Pharmacy version 7.0. STATUS: Active DURATION: Next Version MAIL MESSAGE: 22126657 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 1625 IA #: 1625 DATE CREATED: NOV 07, 1996 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUA4A72 NAME: PERSON CLASS API'S ID: XUA4A72 GENERAL DESCRIPTION: Based on a multiple in the NEW PERSON file (#200) which contains entries that reflect the assignement of HCFA taxonomy to providers, these APIs provide data for a given NEW PERSON file entry on HCFA code, profession, specialty, and subspecialty. STATUS: Active MAIL MESSAGE: 25187487 COMPONENT/ENTRY POINT: $$GET(DUZ[,DATE]) COMPONENT DESCRIPTION: Returns the "IEN^Profession^Specialty^Sub-specialty^Effect date^Expired date^VA code" for the person identified by the DUZ in effect on the date passed in, in internal FileMan format, (TODAY if no date passed in). Returns -1 if DUZ doesn't point to a valid user or user has never had a Person Class assigned. Returns -2 if no active Person Class on that date. VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: Internal entry number for the Person being checked in the New Person file. VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: Date in internal FileMan format, to indicate effective date for determination. COMPONENT/ENTRY POINT: $$IEN2CODE(IEN) COMPONENT DESCRIPTION: Returns the VA CODE from the PERSON CLASS file that corresponds to the IEN number passed in. If the IEN passed in does not match a valid entry in file 8932.1, an empty string is returned COMPONENT/ENTRY POINT: $$CODE2TXT(IEN or Vcode) COMPONENT DESCRIPTION: This extrinsic function returns the three parts of the HCFA text from the person class file based on passing in the IEN or the VA's Vcode. VARIABLES: IEN or Vcode TYPE: Input VARIABLES DESCRIPTION: Pass in either the IEN or the VA Vcode for the text that should be returned. VARIABLES: $$CODE2TXT TYPE: Output VARIABLES DESCRIPTION: Text for the code. COMPONENT/ENTRY POINT: $$IEN2DATA(IEN or Vcode) VARIABLES: $$IEN2DATA TYPE: Output VARIABLES DESCRIPTION: Person class data for an IEN VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN to file 200 COMPONENT/ENTRY POINT: $$VCLK(X) VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Vcode VARIABLES: $$VCLK TYPE: Output VARIABLES DESCRIPTION: IEN to file 200 NUMBER: 1629 IA #: 1629 DATE CREATED: NOV 28, 2006 CUSTODIAL PACKAGE: RPC BROKER CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: XWB GET VARIABLE VALUE REMOTE PROCEDURE: XWB GET VARIABLE VALUE GENERAL DESCRIPTION: One can call the XWB GET VARIABLE VALUE RPC (distributed with the RPC Broker) to retrieve the value of any M variable in the server environment. Pass the variable name in Param[0].Value, and the type (reference) in Param[0].PType. Also, the current context of the user must give them permission to execute the XWB GET VARIABLE VALUE RPC (it must be included in the RPC multiple of the "B"-type option registered with the CreateContext function). STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: VISTA WEB ISC: Salt Lake City SUBSCRIBING DETAILS: JSHARVEY 20061128/ ADDED VISTA WEB AS SUBSCRIBER AS PER IVEY. SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM SUBSCRIBING PACKAGE: MEDICAL DOMAN WEB SERVICE SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: JSHARVEY 20061128/MODIFIED SUBSCRIBER LIST 9/7/12-MM: Added VPS as a subscriber for VPS*1*1. Original request from VPS was to add MDWS as a subscriber. In 9/2012,the request was changed from MDWS to VPS. 4/10/14-MM: Added Fee Basis Claim System, MDWS and VIA as subscribers to this ICR. Herlan reviewed the request for FBCS (old request from 2010) and VIA (request from 2013) to be added as subscribers. He concurred with their request and recommended adding MDWS. He provided the following concurrence: I recommend adding VIA, FBCS, and MDWS to the subscription list (known users). I suspect that most GUIs are using this one, including CPRS and BCMA, but we have to start somewhere. In a conversation with Debbie, he also indicated this RPC may be retired at a future date but does not have time to rewrite or redo at this time. DATE/TIME EDITED: NOV 28, 2006@08:54 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: TROHA,ROBERT WITH CONCURRENCE OF: IVEY,JOEL DATE/TIME EDITED: JUN 11, 2009@14:10 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: FORT,WALLY DATE/TIME EDITED: SEP 07, 2012@09:38 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: IVEY,JOEL DATE/TIME EDITED: APR 10, 2014@14:19 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: WESTRA,HERLAN NUMBER: 1630 IA #: 1630 DATE CREATED: JUN 29, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: XUS AV CODE REMOTE PROCEDURE: XUS AV CODE GENERAL DESCRIPTION: Broker Signon RPC'S. This DBIA covers the following RPC's XUS AV CODE XUS VA HELP XUS CVC XUS SIGNON SETUP That are all private to Broker. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: RPC BROKER ISC: Oakland SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 2/12/14 - MM: Added VistA Integration Adaptor (VIA) as a subscriber to ICR #1630. Herlan Westra provided concurrence on this request with the following comments: I don't have a problem with VIA being added to this ICR. FYI to others on the Infrastructure team, VIA is not using the Delphi RPC Broker client code, but is developing their own client code as a planned replacement for MDWS. DATE/TIME EDITED: FEB 12, 2014@11:18 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: WESTRA,HERLAN NUMBER: 1631 IA #: 1631 DATE CREATED: JUN 29, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: XUS INTRO MSG REMOTE PROCEDURE: XUS INTRO MSG GENERAL DESCRIPTION: RPC to return the INTRO TEXT from the KSP file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29789444 SUBSCRIBING PACKAGE: RPC BROKER ISC: Oakland SUBSCRIBING PACKAGE: IMAGING DBA Comments: 1/31/14 MM: New spreadsheet from Stephen Pelchar on 1/9/14 did not include this RPC. VIA request to be added as a subscriber is withdrawn. DATE/TIME EDITED: MAR 02, 2010@14:03 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LITTLES,SHARON WITH CONCURRENCE OF: IVEY,JOEL NUMBER: 1632 IA #: 1632 DATE CREATED: JUN 29, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: XUS SIGNON SETUP REMOTE PROCEDURE: XUS SIGNON SETUP GENERAL DESCRIPTION: This RPC can be used to check if a user has a given security key. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29789448 EDITOR: FORT,WALLY NUMBER: 1633 IA #: 1633 DATE CREATED: JUN 29, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: XUS SEND KEYS REMOTE PROCEDURE: XUS SEND KEYS GENERAL DESCRIPTION: This is a two part RPC for a Broker Signon component. XUS DIVISION GET XUS DIVISION SET The rpc XUS DIVISION GET gets a list of the institutions that this user may signon as belonging to. The rpc XUS DIVISION SET sets the Kernel variable DUZ(2) to the selected Division/institution. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29789450 SUBSCRIBING PACKAGE: RPC BROKER ISC: Oakland EDITOR: FORT,WALLY NUMBER: 1634 IA #: 1634 DATE CREATED: APR 30, 2003 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU NOTES REMOTE PROCEDURE: TIU NOTES STATUS: Active MAIL MESSAGE: 35801438 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 1635 IA #: 1635 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU GET RECORD TEXT REMOTE PROCEDURE: TIU GET RECORD TEXT STATUS: Active MAIL MESSAGE: 31932331 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: 5/10/13-The Mental Health Program Office contracted with Capital Solution Design Corporation to provide the Behavioral Health Lab (BHL) software. BHL is a vendor product that calls this VistA RPC. Capital Solution Design John Boles - 202-642-9280 johnboles@capitalsolutiondesign.com VA BHL Support - 202-670-2847 bhl.support@capitalsolutiondesign.com SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 5/10/13-MM: Mental Health was added as a subscriber for Behavioral Health Lab. A note was added to the Subscribing Details section for Mental Health to document Behavioral Health Lab software is using this RPC. Informational patch YS*5.01*111 documents release of BHL. 3/13/14-MM: Added VIA as a subscriber. VIAB*1*1 and TIU*1*283 are patches associated with this project. TIU*1*283 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: JUN 11, 2009@14:10 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: MAY 10, 2013@16:38 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: MAY 10, 2013@16:41 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: MAR 13, 2014@13:38 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1639 IA #: 1639 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQQAL LIST REMOTE PROCEDURE: ORQQAL LIST STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 3/5/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: MAR 05, 2014@13:47 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1641 IA #: 1641 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQQAL DETAIL REMOTE PROCEDURE: ORQQAL DETAIL STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: BAR CODE EXPANSION NUMBER: 1642 IA #: 1642 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQQPL LIST REMOTE PROCEDURE: ORQQPL LIST STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING DETAILS: JSH/10-23-2006 BCE added in agreement between Tony Thompson and Rich Vertigan. As part of the Bar Code Expansion project, Care Fusion's wCareView software will give providers a read-only view of consolidated patient information in a similar fashion as the CPRS Cover Sheet. DBA Comments: JSH/10-23-2006 Added BCE as subscriber. DATE/TIME EDITED: OCT 23, 2006@08:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: THOMPSON,WILLIAM WITH CONCURRENCE OF: VERTIGAN,RICHARD NUMBER: 1643 IA #: 1643 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQQPL DETAIL REMOTE PROCEDURE: ORQQPL DETAIL STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING DETAILS: JSH/10-23-2006 BCE added in agreement between Tony Thompson and Rich Vertigan. As part of the Bar Code Expansion project, Care Fusion's wCareView software will give providers a read-only view of consolidated patient information in a similar fashion as the CPRS Cover Sheet. DBA Comments: JSH/10-23-2006 BCE added as subscriber. DATE/TIME EDITED: OCT 23, 2006@09:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: THOMPSON,WILLIAM WITH CONCURRENCE OF: VERTIGAN,RICHARD NUMBER: 1647 IA #: 1647 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQQVI VITALS REMOTE PROCEDURE: ORQQVI VITALS STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 4/18/13-MM: Added PADP as a subscriber for NUPA*1*1. CPRS concurred with request indicating the Clinical Reminders Index contains both Vitals and Flowsheets Data (CliO) and is a better source than calling either Vitals or CliO directly. 3/7/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. ICR #5938 was originally entered for VIA's request to access this RPC. ICR #5938 was withdrawn. 7/9/14-MC: PADP did not complete the class 3 to class 1 conversion process, but it is still installed at sites. Sites have the option to utilize the program, however it is no longer nationally supported. There will be no further patching of the package. PADP has been removed as a subscriber to this ICR. DATE/TIME EDITED: APR 18, 2013@16:52 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: DEZORZI,KEVIN WITH CONCURRENCE OF: PETIT,DAN DATE/TIME EDITED: MAR 07, 2014@15:43 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1649 IA #: 1649 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQPT DEFAULT PATIENT LIST REMOTE PROCEDURE: ORQPT DEFAULT PATIENT LIST STATUS: Active MAIL MESSAGE: 34160740 SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: CARE MANAGEMENT NUMBER: 1650 IA #: 1650 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQPT PROVIDERS REMOTE PROCEDURE: ORQPT PROVIDERS STATUS: Active MAIL MESSAGE: 33439595 SUBSCRIBING PACKAGE: MENTAL HEALTH NUMBER: 1651 IA #: 1651 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQPT PROVIDER PATIENTS REMOTE PROCEDURE: ORQPT PROVIDER PATIENTS STATUS: Active MAIL MESSAGE: 33439595 SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 3/5/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: MAR 05, 2014@12:36 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MOULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1652 IA #: 1652 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQPT CLINIC PATIENTS REMOTE PROCEDURE: ORQPT CLINIC PATIENTS STATUS: Active MAIL MESSAGE: 33439595 SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 3/5/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: MAR 05, 2014@12:23 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1653 IA #: 1653 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQPT SPECIALTIES REMOTE PROCEDURE: ORQPT SPECIALTIES STATUS: Active MAIL MESSAGE: 33439595 SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 3/5/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: MAR 05, 2014@12:59 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1654 IA #: 1654 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQPT SPECIALTY PATIENTS REMOTE PROCEDURE: ORQPT SPECIALTY PATIENTS STATUS: Active MAIL MESSAGE: 33439595 SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 3/5/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: MAR 05, 2014@13:04 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1655 IA #: 1655 DATE CREATED: DEC 09, 2004 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQPT TEAMS REMOTE PROCEDURE: ORQPT TEAMS STATUS: Active MAIL MESSAGE: 40043228 SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 3/5/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: MAR 05, 2014@13:26 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1656 IA #: 1656 DATE CREATED: DEC 09, 2004 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQPT TEAM PATIENTS REMOTE PROCEDURE: ORQPT TEAM PATIENTS STATUS: Active MAIL MESSAGE: 40043242 SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 3/5/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: MAR 05, 2014@13:27 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1659 IA #: 1659 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQQPS LIST REMOTE PROCEDURE: ORQQPS LIST STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL NUMBER: 1670 IA #: 1670 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU SUMMARIES REMOTE PROCEDURE: TIU SUMMARIES STATUS: Active MAIL MESSAGE: 31932331 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 1671 IA #: 1671 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQQCN LIST REMOTE PROCEDURE: ORQQCN LIST CREATOR: THOMPSON,WILLIAM ANTHONY GENERAL DESCRIPTION: Parameters: Patien DFN, Start Date, End Date, Service, Status Patient DFN - DFN of patient from VistA system. Start Date - Date to begin searching for consult records. If blank, ALL records for the patient will be returned. End Date - Date to stop searching for consult records. If Start Date is blank, End Date will be ignored. Service - Consult service (File 123.5 entry) to return records for. If Service is blank, records will be returned for All Services. Status - An order status (File 100.01) to search for. May be a single or multiple comma separated statuses. If blank, all statuses will be returned. STATUS: Active KEYWORDS: ORQQCN KEYWORDS: ORQQCN LIST SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: added 4/21/2011 SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 3/5/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE ACTIVATED: APR 21, 2011 DATE/TIME EDITED: JUN 11, 2009@14:15 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: THOMPSON,TONY DATE/TIME EDITED: MAR 18, 2011@09:15 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: THOMPSON,WILLIAM DATE/TIME EDITED: APR 21, 2011@11:20 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: THOMPSON,WILLIAM WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: APR 21, 2011@11:24 ACTION: APPROVED AT THE REQUEST OF: THOMPSON,WILLIAM WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: MAR 05, 2014@16:50 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1672 IA #: 1672 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQQCN DETAIL REMOTE PROCEDURE: ORQQCN DETAIL STATUS: Active SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 3/5/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: MAR 05, 2014@13:48 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1676 IA #: 1676 DATE CREATED: FEB 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQPT WARDS REMOTE PROCEDURE: ORQPT WARDS STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34910759 SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 3/5/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: MAR 05, 2014@13:46 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1681 IA #: 1681 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQPT DEFAULT LIST SOURCE REMOTE PROCEDURE: ORQPT DEFAULT LIST SOURCE STATUS: Active MAIL MESSAGE: 33439595 SUBSCRIBING PACKAGE: MENTAL HEALTH NUMBER: 1684 IA #: 1684 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWPT ID INFO REMOTE PROCEDURE: ORWPT ID INFO STATUS: Active MAIL MESSAGE: 33439595 SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: 5/10/13-The Mental Health Program Office contracted with Capital Solution Design Corporation to provide the Behavioral Health Lab (BHL) software. BHL is a vendor product that calls this VistA RPC. Capital Solution Design John Boles - 202-642-9280 johnboles@capitalsolutiondesign.com VA BHL Support - 202-670-2847 bhl.support@capitalsolutiondesign.com SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING DETAILS: JSH/10-23-2006 BCE added in agreement between Tony Thompson and Rich Vertigan. As part of the Bar Code Expansion project, Care Fusion's wCareView software will give providers a read-only view of consolidated patient information in a similar fashion as the CPRS Cover Sheet. SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: JSH/10-23-2006 BCE added as subscriber. 5/10/13-MM: Mental Health is currently a subscriber to this ICR. Behavioral Health Lab software will also be using this RPC and details regarding its use of the ICR were added to the subscribing details for Mental Health. Informational patch YS*5.01*111 documents release of BHL. 3/6/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. Jamie noted in her review that the data was not owned by CPRS. DATE/TIME EDITED: OCT 23, 2006@08:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: THOMPSON,WILLIAM WITH CONCURRENCE OF: VERTIGAN,RICHARD DATE/TIME EDITED: JUN 11, 2009@14:14 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: THOMPSON,TONY DATE/TIME EDITED: MAY 10, 2013@12:05 ACTION: CONTENT CORRECTED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: CHUNG,TERESA DATE/TIME EDITED: MAY 10, 2013@12:06 ACTION: CONTENT CORRECTED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: MAR 06, 2014@14:13 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1685 IA #: 1685 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWPT LIST ALL REMOTE PROCEDURE: ORWPT LIST ALL STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: 5/10/13-The Mental Health Program Office contracted with Capital Solution Design Corporation to provide the Behavioral Health Lab (BHL) software. BHL is a vendor product that calls this VistA RPC. Capital Solution Design John Boles - 202-642-9280 johnboles@capitalsolutiondesign.com VA BHL Support - 202-670-2847 bhl.support@capitalsolutiondesign.com SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) SUBSCRIBING DETAILS: The ORWPT LIST ALL RPC will be triggered by a request sent by the Vecna Kiosk system. Access to this RPC is needed for VPS*1*1. VPS*1*2 will not be using this RPC. SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 9/12/12-mm: VPS has been added as a subscriber for VPS*1*1. The ORWPT LIST ALL RPC will be triggered by a request sent by the Vecna Kiosk system. Access to this RPC is needed for VPS*1*1. VPS*1*2 will not be using this RPC. 5/10/13-MM: Mental Health is currently a subscriber to this ICR. Behavioral Health Lab software will also be using this RPC and details regarding its use of the ICR were added to the subscribing details for Mental Health. Informational patch YS*5.01*111 documents release of BHL. 3/5/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: SEP 12, 2012@14:42 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: CHUNG,TERESA DATE/TIME EDITED: MAY 10, 2013@12:36 ACTION: CONTENT CORRECTED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: CHUNG,TERESA DATE/TIME EDITED: MAY 10, 2013@12:37 ACTION: CONTENT CORRECTED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: MAR 05, 2014@16:59 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1687 IA #: 1687 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWLR CUMULATIVE REPORT REMOTE PROCEDURE: ORWLR CUMULATIVE REPORT STATUS: Active SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE DBA Comments: 1/30/14 MM: New spreadsheet from Stephen Pelchar on 1/9/14 did not include this RPC. VIA request to be added as a subscriber is withdrawn. NUMBER: 1689 IA #: 1689 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWPT LOOKUP REMOTE PROCEDURE: ORWPT LOOKUP STATUS: Active MAIL MESSAGE: 33439595 SUBSCRIBING PACKAGE: MENTAL HEALTH NUMBER: 1691 IA #: 1691 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQQVS VISITS/APPTS REMOTE PROCEDURE: ORQQVS VISITS/APPTS STATUS: Active SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE NUMBER: 1692 IA #: 1692 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQQPP LIST REMOTE PROCEDURE: ORQQPP LIST STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: BAR CODE EXPANSION NUMBER: 1693 IA #: 1693 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQPT WARDRMBED REMOTE PROCEDURE: ORQPT WARDRMBED STATUS: Active SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 3/6/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. Jamie noted in her review that the data was not owned by CPRS. ICR #1693 was activated and VIA added as a subscriber. DATE ACTIVATED: MAR 06, 2014 DATE/TIME EDITED: MAR 06, 2014@12:31 ACTION: APPROVED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE DATE/TIME EDITED: MAR 06, 2014@12:33 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1694 IA #: 1694 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQQPX IMMUN LIST REMOTE PROCEDURE: ORQQPX IMMUN LIST STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL DBA Comments: 1/30/14 MM: New spreadsheet from Stephen Pelchar on 1/9/14 did not include this RPC. VIA request to be added as a subscriber is withdrawn. NUMBER: 1699 IA #: 1699 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQQLR DETAIL REMOTE PROCEDURE: ORQQLR DETAIL STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL NUMBER: 1702 IA #: 1702 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQQPS DETAIL REMOTE PROCEDURE: ORQQPS DETAIL STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL NUMBER: 1705 IA #: 1705 DATE CREATED: APR 30, 2003 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU NOTES BY VISIT REMOTE PROCEDURE: TIU NOTES BY VISIT STATUS: Active MAIL MESSAGE: 35801452 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 1706 IA #: 1706 DATE CREATED: APR 30, 2003 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU SUMMARIES BY VISIT REMOTE PROCEDURE: TIU SUMMARIES BY VISIT STATUS: Active MAIL MESSAGE: 35801462 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 1713 IA #: 1713 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC LISTER REMOTE PROCEDURE: SC LISTER STATUS: Active NUMBER: 1714 IA #: 1714 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC FILER REMOTE PROCEDURE: SC FILER STATUS: Active NUMBER: 1715 IA #: 1715 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC DELETE ENTRY REMOTE PROCEDURE: SC DELETE ENTRY STATUS: Active NUMBER: 1717 IA #: 1717 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC FILE NUMBER REMOTE PROCEDURE: SC FILE NUMBER STATUS: Active NUMBER: 1718 IA #: 1718 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC GLOBAL NODE REMOTE PROCEDURE: SC GLOBAL NODE STATUS: Active NUMBER: 1719 IA #: 1719 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC GETS ENTRY DATA REMOTE PROCEDURE: SC GETS ENTRY DATA STATUS: Active NUMBER: 1720 IA #: 1720 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC LOCK/UNLOCK NODE REMOTE PROCEDURE: SC LOCK/UNLOCK NODE STATUS: Active NUMBER: 1721 IA #: 1721 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC VALIDATOR REMOTE PROCEDURE: SC VALIDATOR STATUS: Active NUMBER: 1722 IA #: 1722 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC GLOBAL NODE COUNT REMOTE PROCEDURE: SC GLOBAL NODE COUNT STATUS: Active NUMBER: 1723 IA #: 1723 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC PRTP REMOTE PROCEDURE: SC PRTP STATUS: Active NUMBER: 1724 IA #: 1724 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC MAILMAN REMOTE PROCEDURE: SC MAILMAN STATUS: Active NUMBER: 1725 IA #: 1725 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC NEW HISTORY OK REMOTE PROCEDURE: SC NEW HISTORY OK STATUS: Active NUMBER: 1726 IA #: 1726 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC CHANGE HISTORY OK REMOTE PROCEDURE: SC CHANGE HISTORY OK STATUS: Active NUMBER: 1727 IA #: 1727 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC INACTIVATE ENTRY REMOTE PROCEDURE: SC INACTIVATE ENTRY STATUS: Active NUMBER: 1728 IA #: 1728 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC DELETE HISTORY REMOTE PROCEDURE: SC DELETE HISTORY STATUS: Active NUMBER: 1729 IA #: 1729 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC HISTORY STATUS OK REMOTE PROCEDURE: SC HISTORY STATUS OK STATUS: Active NUMBER: 1730 IA #: 1730 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC MEAN TEST REMOTE PROCEDURE: SC MEAN TEST STATUS: Active NUMBER: 1731 IA #: 1731 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC TEAM LIST REMOTE PROCEDURE: SC TEAM LIST STATUS: Active NUMBER: 1732 IA #: 1732 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC PATIENT LOOKUP REMOTE PROCEDURE: SC PATIENT LOOKUP STATUS: Active NUMBER: 1733 IA #: 1733 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC POSITION MEMBERS REMOTE PROCEDURE: SC POSITION MEMBERS STATUS: Active NUMBER: 1734 IA #: 1734 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC FILE SINGLE VALUE REMOTE PROCEDURE: SC FILE SINGLE VALUE INTEGRATION REFERENCES LIST MAR 18, 2015@11:24 PAGE 5 -------------------------------------------------------------------------------- STATUS: Active NUMBER: 1735 IA #: 1735 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SCTM AUTOLINK GETRECORD REMOTE PROCEDURE: SCTM AUTOLINK GETRECORD STATUS: Active NUMBER: 1736 IA #: 1736 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC KEY CHECK REMOTE PROCEDURE: SC KEY CHECK STATUS: Active NUMBER: 1737 IA #: 1737 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SCTM AUTOLINK SETRECORD REMOTE PROCEDURE: SCTM AUTOLINK SETRECORD STATUS: Active NUMBER: 1738 IA #: 1738 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SCTM AUTOLINK GETLINK REMOTE PROCEDURE: SCTM AUTOLINK GETLINK STATUS: Active NUMBER: 1739 IA #: 1739 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SCRP DEFINITION GETRECORD REMOTE PROCEDURE: SCRP DEFINITION GETRECORD STATUS: Active NUMBER: 1740 IA #: 1740 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SCUT GET USER RECORD REMOTE PROCEDURE: SCUT GET USER RECORD STATUS: Active NUMBER: 1741 IA #: 1741 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SCRP QUERY GETRECORD REMOTE PROCEDURE: SCRP QUERY GETRECORD STATUS: Active NUMBER: 1751 IA #: 1751 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: RPC BROKER CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: XWB CREATE CONTEXT REMOTE PROCEDURE: XWB CREATE CONTEXT STATUS: Active SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR SUBSCRIBING PACKAGE: MEDICAL DOMAN WEB SERVICE DBA Comments: 4/8/14-MM: Added MDWS and VIA as subscribers to ICR #1751. VIA patch # is VIAB*1*1. Herlan provided concurrence for the request indicating VIA does not use the RPC Broker Development Kit. VIA is middleware, a potential replacement for MDWS. It will need access to Broker RPCs that are normally internal to the Kernel package, since they are intending to use BSE outside the context of the Delphi RPC Broker. He also indicated MDWS uses the XWB CREATE CONTEXT RPC and will need to be added as a subscriber when the ICR is activated. 4/9/14 - MM: Status changed from Retired to Active based on concurrence from Infrastructure team. DATE ACTIVATED: APR 09, 2014 DATE/TIME EDITED: APR 08, 2014@14:58 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: WESTRA,HERLAN DATE/TIME EDITED: APR 09, 2014@13:08 ACTION: APPROVED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: WESTRA,HERLAN NUMBER: 1752 IA #: 1752 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SCRP SELECTION SOURCE REMOTE PROCEDURE: SCRP SELECTION SOURCE STATUS: Active NUMBER: 1753 IA #: 1753 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SCRP FILE ENTRY GETSELECTION REMOTE PROCEDURE: SCRP FILE ENTRY GETSELECTION STATUS: Active NUMBER: 1754 IA #: 1754 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SCRP QUERY SAVE REMOTE PROCEDURE: SCRP QUERY SAVE STATUS: Active NUMBER: 1755 IA #: 1755 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SCRP QUERY VALIDATE REMOTE PROCEDURE: SCRP QUERY VALIDATE STATUS: Active NUMBER: 1756 IA #: 1756 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SCRP QUERY DELETE REMOTE PROCEDURE: SCRP QUERY DELETE STATUS: Active NUMBER: 1757 IA #: 1757 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SCRP QUERY CHECK NAME REMOTE PROCEDURE: SCRP QUERY CHECK NAME STATUS: Active NUMBER: 1758 IA #: 1758 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SCUT SET USER QUERY DEFAULT REMOTE PROCEDURE: SCUT SET USER QUERY DEFAULT STATUS: Active NUMBER: 1759 IA #: 1759 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SCRP REPORT PRINT REMOTE PROCEDURE: SCRP REPORT PRINT STATUS: Active NUMBER: 1760 IA #: 1760 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC STAFF LOOKUP REMOTE PROCEDURE: SC STAFF LOOKUP STATUS: Active NUMBER: 1761 IA #: 1761 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC USER CLASS STATUS REMOTE PROCEDURE: SC USER CLASS STATUS STATUS: Active NUMBER: 1762 IA #: 1762 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC PRIMARY CARE TEAM REMOTE PROCEDURE: SC PRIMARY CARE TEAM STATUS: Active NUMBER: 1763 IA #: 1763 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC BUILD PAT CLN LIST REMOTE PROCEDURE: SC BUILD PAT CLN LIST STATUS: Active NUMBER: 1764 IA #: 1764 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC GET PAT BUILD REMOTE PROCEDURE: SC GET PAT BUILD STATUS: Active NUMBER: 1765 IA #: 1765 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC ASSIGN PATIENT LIST REMOTE PROCEDURE: SC ASSIGN PATIENT LIST STATUS: Active NUMBER: 1766 IA #: 1766 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC FILE PATIENT LIST REMOTE PROCEDURE: SC FILE PATIENT LIST STATUS: Active NUMBER: 1767 IA #: 1767 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC BUILD PAT TM LIST REMOTE PROCEDURE: SC BUILD PAT TM LIST STATUS: Active NUMBER: 1768 IA #: 1768 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC GET PAT TM LIST REMOTE PROCEDURE: SC GET PAT TM LIST STATUS: Active NUMBER: 1769 IA #: 1769 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC GET PAT BLOCK REMOTE PROCEDURE: SC GET PAT BLOCK STATUS: Active NUMBER: 1770 IA #: 1770 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC BLD PAT LIST REMOTE PROCEDURE: SC BLD PAT LIST STATUS: Active NUMBER: 1771 IA #: 1771 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC FILE PAT TM ASGN REMOTE PROCEDURE: SC FILE PAT TM ASGN STATUS: Active NUMBER: 1772 IA #: 1772 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC BLD PAT CLN LIST REMOTE PROCEDURE: SC BLD PAT CLN LIST STATUS: Active NUMBER: 1773 IA #: 1773 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC FILE PAT POS ASGN REMOTE PROCEDURE: SC FILE PAT POS ASGN STATUS: Active NUMBER: 1774 IA #: 1774 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC BLD PAT SCDE LIST REMOTE PROCEDURE: SC BLD PAT SCDE LIST STATUS: Active NUMBER: 1775 IA #: 1775 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC BLD PAT TM LIST REMOTE PROCEDURE: SC BLD PAT TM LIST STATUS: Active NUMBER: 1776 IA #: 1776 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC BLD PAT POS LIST REMOTE PROCEDURE: SC BLD PAT POS LIST STATUS: Active NUMBER: 1777 IA #: 1777 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC PAT ENROLL CLN REMOTE PROCEDURE: SC PAT ENROLL CLN STATUS: Active NUMBER: 1778 IA #: 1778 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC CHECK FOR PC POS REMOTE PROCEDURE: SC CHECK FOR PC POS STATUS: Active NUMBER: 1779 IA #: 1779 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC FILE ALL PAT TM ASGN REMOTE PROCEDURE: SC FILE ALL PAT TM ASGN STATUS: Active NUMBER: 1780 IA #: 1780 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC BLD PAT APT LIST REMOTE PROCEDURE: SC BLD PAT APT LIST STATUS: Active NUMBER: 1781 IA #: 1781 DATE CREATED: NOV 17, 2006 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC FILE ALL PAT POS ASGN REMOTE PROCEDURE: SC FILE ALL PAT POS ASGN STATUS: Active NUMBER: 1782 IA #: 1782 DATE CREATED: NOV 28, 2006 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU GET PN TITLES REMOTE PROCEDURE: TIU GET PN TITLES STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31932331 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION SUBSCRIBING DETAILS: added 11/28/06/JSHarvey DBA Comments: JSH 20061128/ Added SCID to subscribers as per McClenahan. DATE/TIME EDITED: NOV 22, 2006@19:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SWESKY,JEFF WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 1783 IA #: 1783 DATE CREATED: APR 29, 2003 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU GET DS TITLES REMOTE PROCEDURE: TIU GET DS TITLES STATUS: Active MAIL MESSAGE: 35801251 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 1784 IA #: 1784 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU LOAD BOILERPLATE TEXT REMOTE PROCEDURE: TIU LOAD BOILERPLATE TEXT STATUS: Active MAIL MESSAGE: 31932331 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) SUBSCRIBING DETAILS: Added VPS as subscriber, effective with VPS*1*3 DBA Comments: 10/27/14 DT: Added VPS as subscriber, effective with VPS*1*3, requested by Budy Tjahjo, approved by Margy McClenahan. DATE/TIME EDITED: OCT 27, 2014@13:41 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: TJAHJO,BUDY WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 1790 IA #: 1790 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU SIGN RECORD REMOTE PROCEDURE: TIU SIGN RECORD STATUS: Active MAIL MESSAGE: 31932331 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: JUNE 2009 SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) SUBSCRIBING DETAILS: Effective with VPS*1*3 DBA Comments: 11/19/12-MM: Added Patient Assessment Document Package (PADP) as a subscriber for NUPA*1*1. 3/13/14-MM: Added VIA as a subscriber. VIAB*1*1 and TIU*1*283 are patches associated with this project. TIU*1*283 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. 7/9/14-MC: PADP did not complete the class 3 to class 1 conversion process, but it is still installed at sites. Sites have the option to utilize the program, however it is no longer nationally supported. There will be no further patching of the package. PADP has been removed as a subscriber to this ICR. 11/6/14-DT: VPS Kiosk added as subscriber, effective with VPS*1*3. Original request was to use 3718, which is a duplicate of 3718, which will be updated to withdrawn. DATE/TIME EDITED: JUN 11, 2009@14:09 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: NOV 19, 2012@16:36 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: DEZORZI,KEVIN WITH CONCURRENCE OF: MCCLENEHAN,MARGY DATE/TIME EDITED: MAR 13, 2014@14:44 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE DATE/TIME EDITED: NOV 06, 2014@12:58 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELASS,CAROLYN WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 1791 IA #: 1791 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWU USERINFO REMOTE PROCEDURE: ORWU USERINFO STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING DETAILS: Veteran ID Card Replacement (VIC) uses the RPC to obtain the CPRS timeout parameter. SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING DETAILS: JSH/10-23-2006 BCE added in agreement between Tony Thompson and Rich Vertig an. As part of the Bar Code Expansion project, Care Fusion's wCareView software will give providers a read-only view of consolidated patient information in a similar fashion as the CPRS Cover Sheet. SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: JSH/10-23-2006 BCE added as a subscriber. 3/6/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: OCT 23, 2006@08:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: THOMPSON,WILLIAM WITH CONCURRENCE OF: VERTIGAN,RICHARD DATE/TIME EDITED: JUN 11, 2009@14:14 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: THOMPSON,TONY DATE/TIME EDITED: MAR 06, 2014@10:46 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1796 IA #: 1796 DATE CREATED: APR 30, 2003 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU GET PERSONAL PREFERENCES REMOTE PROCEDURE: TIU GET PERSONAL PREFERENCES STATUS: Active MAIL MESSAGE: 34910759 SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 1797 IA #: 1797 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC BLD NOPC TM LIST REMOTE PROCEDURE: SC BLD NOPC TM LIST STATUS: Active NUMBER: 1798 IA #: 1798 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SC PAT ASGN MAILMAN REMOTE PROCEDURE: SC PAT ASGN MAILMAN STATUS: Active NUMBER: 1799 IA #: 1799 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU UPDATE RECORD REMOTE PROCEDURE: TIU UPDATE RECORD STATUS: Active MAIL MESSAGE: 31932331 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 3/13/14-MM: Added VIA as a subscriber. VIAB*1*1 and TIU*1*283 are patches associated with this project. TIU*1*283 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: JUN 11, 2009@14:08 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: MAR 13, 2014@14:45 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1800 IA #: 1800 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU REQUIRES COSIGNATURE REMOTE PROCEDURE: TIU REQUIRES COSIGNATURE STATUS: Active MAIL MESSAGE: 31932331 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE2009 SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) SUBSCRIBING DETAILS: Effective with VPS*1*3 DBA Comments: 3/13/14-MM: Added VIA as a subscriber. VIAB*1*1 and TIU*1*283 are patches associated with this project. TIU*1*283 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. 11/6/14-DT: Added VPS Kiosk as a subscriber, effective with VPS*1*3. Margy McClenahan granted concurrence 1/7/13. DATE/TIME EDITED: JUN 11, 2009@14:07 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: MAR 13, 2014@14:42 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE DATE/TIME EDITED: NOV 06, 2014@12:06 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELASS,CAROLYN WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 1801 IA #: 1801 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU LOAD RECORD FOR EDIT REMOTE PROCEDURE: TIU LOAD RECORD FOR EDIT STATUS: Active MAIL MESSAGE: 31932331 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE2009 DATE/TIME EDITED: JUN 11, 2009@14:06 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 1802 IA #: 1802 DATE CREATED: APR 30, 2003 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU DETAILED DISPLAY REMOTE PROCEDURE: TIU DETAILED DISPLAY STATUS: Active MAIL MESSAGE: 35801220 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 1805 IA #: 1805 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU CREATE ADDENDUM RECORD REMOTE PROCEDURE: TIU CREATE ADDENDUM RECORD STATUS: Active MAIL MESSAGE: 31932331 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 DBA Comments: 11/19/12-MM: Added Patient Assessment Docum (PADP) as a subscriber for NUPA*1*1. 7/9/14-MC: PADP did not complete the class 3 to class 1 conversion process, but it is still installed at sites. Sites have the option to utilize the program, however it is no longer nationally supported. There will be no further patching of the package. PADP has been removed as a subscriber to this ICR. DATE/TIME EDITED: JUN 11, 2009@12:08 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: NOV 19, 2012@16:43 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: DEZORZI,KEVIN WITH CONCURRENCE OF: MCCLENEHAN,MARGY NUMBER: 1806 IA #: 1806 DATE CREATED: APR 29, 2003 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU CREATE RECORD REMOTE PROCEDURE: TIU CREATE RECORD STATUS: Active MAIL MESSAGE: 35801214 SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: DENTAL RECORD MANAGER SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: 5/10/13-The Mental Health Program Office contracted with Capital Solution Design Corporation to provide the Behavioral Health Lab (BHL) software. BHL is a vendor product that calls this VistA RPC. Capital Solution Design John Boles - 202-642-9280 johnboles@capitalsolutiondesign.com VA BHL Support - 202-670-2847 bhl.support@capitalsolutiondesign.com SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) SUBSCRIBING DETAILS: Effective with VPS*1*3 DBA Comments: 11/19/12-MM: Added Patient Assessment Docum (PADP) as a subscriber for NUPA*1*1. 5/10/13-MM: Mental Health was added as a subscriber for Behavioral Health Lab. A note was added to the Subscribing Details section for Mental Health to document Behavioral Health Lab software is using this RPC. Informational patch YS*5.01*111 documents release of BHL. 3/13/14-MM: Added VIA as a subscriber. VIAB*1*1 and TIU*1*283 are patches associated with this project. TIU*1*283 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. 7/9/14-MC: PADP did not complete the class 3 to class 1 conversion process, but it is still installed at sites. Sites have the option to utilize the program, however it is no longer nationally supported. There will be no further patching of the package. PADP has been removed as a subscriber to this ICR. 11/6/14-DT: Added VPS Kiosk as a subscriber, effective with VPS*1*3. Margy McClenahan approved 3/18/13. Adam Shawn and Budy Tjahjo addressed questions and summarized how VPS will use this RPC: VPS does not need a new national TIU note created for us. We will use the site's local note options and embed in their current processes and currently used note titles. We do need the ability to create TIU notes from the application. The TIU note title would be automated or the user would be offered a choice, primarily depending on the patient characteristics (e.g., inpatient versus outpatient). The staff user can also save without signing and then import the PDO into their own new/unsigned TIU note and modify as they see fit though. DATE/TIME EDITED: JUN 11, 2009@12:07 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: NOV 19, 2012@16:41 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: DEZORZI,KEVIN WITH CONCURRENCE OF: MCCLENEHAN,MARGY DATE/TIME EDITED: MAY 10, 2013@16:21 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: MCLENAHAN,MARGY DATE/TIME EDITED: MAY 10, 2013@16:22 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: MAR 13, 2014@13:36 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE DATE/TIME EDITED: NOV 06, 2014@12:13 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELASS,CAROLYN WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 1811 IA #: 1811 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU DELETE RECORD REMOTE PROCEDURE: TIU DELETE RECORD GENERAL DESCRIPTION: 1) A document in the CONSULTS class/DC can not be written unless it is linked to a Consult request 2) A document outside of the CONSULTS class/DC can not be associated with a consult 3) An addendum can not be linked to a consult request directly STATUS: Active MAIL MESSAGE: 31932331 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM NUMBER: 1812 IA #: 1812 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWPT DEMOG REMOTE PROCEDURE: ORWPT DEMOG STATUS: Active MAIL MESSAGE: 33439595 SUBSCRIBING PACKAGE: MENTAL HEALTH NUMBER: 1813 IA #: 1813 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWPT GETVSIT REMOTE PROCEDURE: ORWPT GETVSIT STATUS: Active MAIL MESSAGE: 33439595 SUBSCRIBING PACKAGE: MENTAL HEALTH NUMBER: 1814 IA #: 1814 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWU VALIDSIG REMOTE PROCEDURE: ORWU VALIDSIG STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 3/7/14 - MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. This request was reviewed by Dan Petit for PADP. He did not provide concurrence. He found upon inspection of the code that it expands into Kernel utilities that are publically available. Jamie agreed with his comments but noted other applications have been given access to the RPC. DATE/TIME EDITED: JUN 11, 2009@14:13 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: THOMPSON,TONY DATE/TIME EDITED: MAR 07, 2014@12:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1815 IA #: 1815 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWPT APPTLST REMOTE PROCEDURE: ORWPT APPTLST STATUS: Active MAIL MESSAGE: 33439595 SUBSCRIBING PACKAGE: MENTAL HEALTH NUMBER: 1816 IA #: 1816 DATE CREATED: MAR 24, 2011 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWU HOSPLOC REMOTE PROCEDURE: ORWU HOSPLOC CREATOR: THOMPSON,WILLIAM ANTHONY GENERAL DESCRIPTION: .Y=returned list, FROM=text to $O from, DIR=$O direction Sample return data: Y(1)="153^AAC-PROS" Y(2)="274^ALB-PRRTP" Y(3)="115^ALCOHOL" Y(4)="64^AUDIOLOGY" Y(6)="11^BCMA" Y(9)="143^BON-HBHC SOCIAL WORK" STATUS: Active KEYWORDS: ORWU KEYWORDS: HOSPLOC SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: 5/10/13-The Mental Health Program Office contracted with Capital Solution Design Corporation to provide the Behavioral Health Lab (BHL) software. BHL is a vendor product that calls this VistA RPC. Capital Solution Design John Boles - 202-642-9280 johnboles@capitalsolutiondesign.com VA BHL Support - 202-670-2847 bhl.support@capitalsolutiondesign.com DBA Comments: 5/10/13-MM: Mental Health is currently a subscriber to this ICR. Behavioral Health Lab software will also be using this RPC and details regarding its use of the ICR were added to the subscribing details for Mental Health. Informational patch YS*5.01*111 documents release of BHL. DATE ACTIVATED: APR 21, 2011 DATE/TIME EDITED: APR 21, 2011@11:23 ACTION: APPROVED AT THE REQUEST OF: THOMPSON,WILLIAM WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: MAY 10, 2013@15:35 ACTION: CONTENT CORRECTED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: CHUNG,TERESA DATE/TIME EDITED: MAY 10, 2013@15:36 ACTION: CONTENT CORRECTED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: TRAXLER,FRANK NUMBER: 1817 IA #: 1817 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWPT ADMITLST REMOTE PROCEDURE: ORWPT ADMITLST STATUS: Active SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 3/5/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: MAR 05, 2014@16:55 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1819 IA #: 1819 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWPT PSCNVT REMOTE PROCEDURE: ORWPT PSCNVT STATUS: Active MAIL MESSAGE: 33439595 SUBSCRIBING PACKAGE: MENTAL HEALTH NUMBER: 1824 IA #: 1824 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWD DT REMOTE PROCEDURE: ORWD DT STATUS: Active MAIL MESSAGE: 34910759 SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE NUMBER: 1834 IA #: 1834 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU PRINT RECORD REMOTE PROCEDURE: TIU PRINT RECORD STATUS: Active MAIL MESSAGE: 31932331 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 1835 IA #: 1835 DATE CREATED: APR 29, 2003 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU GET DOCUMENT PARAMETERS REMOTE PROCEDURE: TIU GET DOCUMENT PARAMETERS STATUS: Active MAIL MESSAGE: 35801228 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 1836 IA #: 1836 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWU NEWPERS REMOTE PROCEDURE: ORWU NEWPERS STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: 5/10/13-The Mental Health Program Office contracted with Capital Solution Design Corporation to provide the Behavioral Health Lab (BHL) software. BHL is a vendor product that calls this VistA RPC. Capital Solution Design John Boles - 202-642-9280 johnboles@capitalsolutiondesign.com VA BHL Support - 202-670-2847 bhl.support@capitalsolutiondesign.com SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING DETAILS: JSH/10-23-2006 BCE added in agreement between Tony Thompson and Rich Vertig an. As part of the Bar Code Expansion project, Care Fusion's wCareView software will give providers a read-only view of consolidated patient information in a similar fashion as the CPRS Cover Sheet. SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM DBA Comments: JSH/10-23-2006 BCE added as subscriber. 5/10/13-MM: Mental Health is currently a subscriber to this ICR. Behavioral Health Lab software will also be using this RPC and details regarding its use of the ICR were added to the subscribing details for Mental Health. Informational patch YS*5.01*111 documents release of BHL. 3/7/14 - MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. In Jamie's review she indicated the data is coming from the New Person (#200) file which is not owned by CPRS. However other packages have been given access to the RPC. 6/3/14-MC: Brandon DeWayne orginally requested that FBCS be added as a subscriber on 6/20/13. Approval received by Tony Thompson. Patch was released on 9/11/13 as an emergency patch (DSIF*3.2*29). Since approval was received anad patch has been released, adding FBCS as a subscribing package to ICR. DATE/TIME EDITED: NOV 23, 2006@08:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SWESKY,JEFF WITH CONCURRENCE OF: VERTIGAN,RICHARD DATE/TIME EDITED: MAY 10, 2013@15:45 ACTION: CONTENT CORRECTED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: CHUNG,TERESA DATE/TIME EDITED: MAY 10, 2013@15:46 ACTION: CONTENT CORRECTED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: MAR 07, 2014@11:57 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: DEWAYNE,BRANDON WITH CONCURRENCE OF: THOMPSON,TONY NUMBER: 1837 IA #: 1837 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWU DEVICE REMOTE PROCEDURE: ORWU DEVICE STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL NUMBER: 1838 IA #: 1838 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWRA IMAGING EXAMS REMOTE PROCEDURE: ORWRA IMAGING EXAMS STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE NUMBER: 1839 IA #: 1839 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWRA REPORT TEXT REMOTE PROCEDURE: ORWRA REPORT TEXT STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL NUMBER: 1840 IA #: 1840 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWRP REPORT LISTS REMOTE PROCEDURE: ORWRP REPORT LISTS STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE DBA Comments: 1/31/14 MM: New spreadsheet from Stephen Pelchar on 1/9/14 did not include this RPC. VIA request to be added as a subscriber is withdrawn. NUMBER: 1841 IA #: 1841 DATE CREATED: DEC 18, 2009 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWRP REPORT TEXT REMOTE PROCEDURE: ORWRP REPORT TEXT CREATOR: PULEO,ANTHONY G GENERAL DESCRIPTION: STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK SUBSCRIBING DETAILS: NHIN will call the entry point RPT^ORWRP directly from a NHIN routine. SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) SUBSCRIBING DETAILS: The ORWRP REPORT TEXT RPC will be triggered by a request sent by the Vecna Kiosk system. SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING DETAILS: MAG*3.0*138 began using this ICR. The subscription will be used in Telepathology project allowing pathologists to view released reports in the Telepathology Worklist GUI application. SUBSCRIBING PACKAGE: VISTA WEB SUBSCRIBING DETAILS: 10/2/13 DT: This is being requested because of patch WEBV*1.0*29. VistAWeb uses the RPC that is covered by the ICR 1841. However, it has been discovered that the ICR was never updated to include that usage. SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 10/2/13 DT: Vista Web (National) added as subscriber for patch WEBV*1.0*29. 9/6/13 DT: Imaging added as a subscriber effective with MAG*3.0*138 8/20/12-mm: VPS Kiosk added as a subscriber. The RPC will be triggered by a request sent by the Vecna Kiosk system. 3/6/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE ACTIVATED: DEC 20, 2009 DATE/TIME EDITED: DEC 18, 2009@16:14 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: PULEO,ANTHONY DATE/TIME EDITED: DEC 18, 2009@16:15 ACTION: DEACTIVATED FOR EDITS DATE/TIME EDITED: SEP 16, 2010@11:14 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE DATE/TIME EDITED: AUG 20, 2012@12:03 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LEYVA,KATHRYN WITH CONCURRENCE OF: HAWSEY,JASON DATE/TIME EDITED: AUG 20, 2012@12:04 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LEYVA,KATHRYN WITH CONCURRENCE OF: MALMROSE,CARY DATE/TIME EDITED: SEP 04, 2013@12:13 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: TOPALOV,NIKOLAY WITH CONCURRENCE OF: TROST,DEBBIE DATE/TIME EDITED: OCT 02, 2013@14:45 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CRUMLEY,JAMIE WITH CONCURRENCE OF: CRUMLEY,JAMIE DATE/TIME EDITED: MAR 06, 2014@10:13 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 1847 IA #: 1847 FILE NUMBER: 21 GLOBAL ROOT: DIC(21, DATE CREATED: NOV 21, 1996 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1847 ID: DIC(21, GLOBAL REFERENCE: DIC(21,D0,0) FIELD NUMBER: .03 FIELD NAME: CODE LOCATION: 0;3 ACCESS: Read w/Fileman GENERAL DESCRIPTION: DSS Extracts will reference the following data from the PERIOD OF SERVICE file (#21). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22394324 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham EDITOR: PAJERSKI,JAN NUMBER: 1848 IA #: 1848 FILE NUMBER: 42 GLOBAL ROOT: DIC(42, DATE CREATED: NOV 26, 1996 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1848 ID: DIC(42, GLOBAL REFERENCE: DIC(42,D0,"OOS", FIELD NUMBER: .01 FIELD NAME: OUT-OF-SERVICE DATE(S) LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: RETURN TO SERVICE DATE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: IS ENTIRE WARD OUT OF SERVICE? LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: DSS examines the OUT-OF-SERVICE DATE multiple (#200). The entire zero node is read into a local variable. The fields above are used. GLOBAL REFERENCE: DIC(42, FIELD NUMBER: 400 FIELD NAME: G&L ORDER LOCATION: ORDER;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field indicates the G&L Order that this Ward will print and subsequently, the Totals on the Bed Status Report, (e.g. Ward with a G&L Order of 1.5 would be placed after a Ward with a G&L Order of 1.49 or earlier and would be before a Ward with a G&L Order of 1.51 or greater). This G&L Order placement has a direct impact on the way the totals calculate on the Bed Status Report. FIELD NUMBER: .015 FIELD NAME: DIVISION LOCATION: 0;15 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: DIC(42,'B', ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: This file contains all the facility ward locations and their related data, i.e., Operating Beds, Bedsection, etc. The wards are created/edited using the WARD DEFINITION option of the ADT module. GLOBAL REFERENCE: DIC(42,D0,1, FIELD NUMBER: .01 FIELD NAME: TOTAL LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is the .01 field on the TOTALS multiple in the Ward Location file. GENERAL DESCRIPTION: In addition to fields which are supported by DBIA 10039, DSS Extracts will reference the following data from the WARD LOCATION file (#42). The DSS Extracts UNIT DOSE EXTRACT DATA file (#728.904) contains a field, WARD, which is a pointer to the WARD LOCATION file (#42). DSS uses the "AINV" cross reference on the OUT-OF-SERVICE DATE(S) field. Global: ^DIC(42,D0,"OOS","AINV",INVERSE_DATE,DA) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25455645 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT NUMBER: 1849 IA #: 1849 FILE NUMBER: 40.8 GLOBAL ROOT: DG(40.8, DATE CREATED: NOV 26, 1996 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1849 ID: DG(40.8, GLOBAL REFERENCE: DG(40.8,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: OUTPATIENT ONLY LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Indicates if a a division has only Outpatient Services. GLOBAL DESCRIPTION: Used by multi-divisional sites to track data by division on the DSS commercial system. The number is used to build feeder locations. GENERAL DESCRIPTION: DSS Extracts will point to the MEDICAL CENTER DIVISION file (#40.8). Most of the DSS extract files include a free text FACILITY field which contains a pointer to this file. Direct read of the 'B' Cross Reference is permitted. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25456568 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany NUMBER: 1850 IA #: 1850 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: NOV 26, 1996 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1850 ID: DPT( GLOBAL REFERENCE: DPT(D0,ENR) FIELD NUMBER: 27.02 FIELD NAME: PREFERRED FACILITY ACCESS: Read w/Fileman GENERAL DESCRIPTION: In addition to fields which are supported by DBIA 10035, DSS Extracts references the following data from the PATIENT file (#2). Most of the DSS Extracts files contain a field, PATIENT NO. - DFN, which is a pointer to the PATIENT file (#2). This agreement now includes only the PREFERRED FACILITY field (#27.02). All other PATIENT file data is obtained by use of supported functionality in ^VADPT. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany SUBSCRIBING PACKAGE: SURGERY SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 DATE/TIME EDITED: JUN 11, 2009@14:11 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: ELLIS,DONNA NUMBER: 1851 IA #: 1851 FILE NUMBER: 78.3 GLOBAL ROOT: RA(78.3, DATE CREATED: DEC 03, 1996 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1851 ID: RA(78.3, GLOBAL REFERENCE: RA(78.3,D0,0) FIELD NUMBER: .01 FIELD NAME: DIAGNOSTIC CODE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The DSS Extracts RADIOLOGY EXTRACT file (#727.814) contains a field, DIAGNOSTIC CODE, which is a pointer to the DIAGNOSTIC CODES file (#78.3). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22505877 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1852 IA #: 1852 FILE NUMBER: 79.2 GLOBAL ROOT: RA(79.2, DATE CREATED: DEC 03, 1996 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1852 ID: RA(79.2, GLOBAL REFERENCE: RA(79.2,D0,0) FIELD NUMBER: .01 FIELD NAME: TYPE OF IMAGING LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field contains the name of this type of imaging. FIELD NUMBER: 3 FIELD NAME: ABBREVIATION LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the abbreviation associated with this type of imaging. This field may also be read via VA FileMan. GLOBAL DESCRIPTION: This file contains, for each imaging type entry, parameters that the module uses during various stages of exam and report processing and inquiring. The parameter switches allow the 'customizing' of the module for each type of imaging. GENERAL DESCRIPTION: DSS Extracts references the following data from the IMAGING TYPE file(#79.2). The DSS Extracts RADIOLOGY EXTRACT file (#727.814) contains a field, IMAGING TYPE, which is a pointer to the IMAGING TYPE file (#79.2). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25457208 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany NUMBER: 1853 IA #: 1853 FILE NUMBER: 131.7 GLOBAL ROOT: SRS( DATE CREATED: DEC 03, 1996 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1853 ID: SRS( GLOBAL REFERENCE: SRS(D0,2) FIELD NUMBER: 9 FIELD NAME: TYPE LOCATION: 2;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DSS Extracts references the following data from the OPERATING ROOM file (#131.7). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22506410 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1854 IA #: 1854 FILE NUMBER: 134 GLOBAL ROOT: SRO(134, DATE CREATED: DEC 03, 1996 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1854 ID: SRO(134, GLOBAL REFERENCE: SRO(134,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The DSS Extracts SURGERY EXTRACT file (#727.811) contains a field, OR TYPE, which is a pointer to the OPERATING ROOM TYPE file (#134). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22506463 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1855 IA #: 1855 FILE NUMBER: 137.45 GLOBAL ROOT: SRO(137.45, DATE CREATED: DEC 03, 1996 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1855 ID: SRO(137.45, GLOBAL REFERENCE: SRO(137.45,D0,0) FIELD NUMBER: 1 FIELD NAME: NATIONAL SURGICAL SPECIALTY LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DSS Extracts references the following data from the LOCAL SURGICAL SPECIALTY file (#137.45). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22506549 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1856 IA #: 1856 FILE NUMBER: 45 GLOBAL ROOT: DGPT( DATE CREATED: DEC 03, 1996 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1856 ID: DGPT( GLOBAL REFERENCE: DGPT(D0,M,D1,0) FIELD NUMBER: 5 FIELD NAME: ICD 1 LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DGPT(D0,M,D1,P) FIELD NUMBER: 20 FIELD NAME: TRANSFER DRG LOCATION: P;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DSS Extracts references the following data from the PTF file (#45). From the 501 multiple (45.02): STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22497675 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1857 IA #: 1857 FILE NUMBER: 45.9 GLOBAL ROOT: DG(45.9, DATE CREATED: DEC 04, 1996 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1857 ID: DG(45.9, GLOBAL REFERENCE: DG(45.9,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: ASSESSMENT DATE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7 FIELD NAME: DATE OF ADMISSION/TRANSFER IN LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: DSS reads the entire zero node into a local variable. The above fields are used. GENERAL DESCRIPTION: DSS Extracts references the following data from the PAF file (#45.9). DSS uses the "AA" cross reference on the ASSESSMENT DATE field. Global: ^DG(45.9,"AA",DATE,D0) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22497939 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1858 IA #: 1858 FILE NUMBER: 72 GLOBAL ROOT: RA(72, DATE CREATED: DEC 04, 1996 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1858 ID: RA(72, GLOBAL REFERENCE: RA(72,D0,0) FIELD NUMBER: 3 FIELD NAME: ORDER LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DSS Extracts references the following data from the EXAMINATION STATUS file (#72). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22505800 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1859 IA #: 1859 FILE NUMBER: 79 GLOBAL ROOT: RA(79, DATE CREATED: DEC 04, 1996 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1859 ID: RA(79, GLOBAL REFERENCE: RA(79,D0,0) FIELD NUMBER: .01 FIELD NAME: DIVISION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DSS Extracts references the following data from the RAD/NUC MED DIVISION file (#79). Direct global read of the 'B' cross reference is also permitted in file #79. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25457287 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany NUMBER: 1860 IA #: 1860 FILE NUMBER: 79.1 GLOBAL ROOT: RA(79.1, DATE CREATED: DEC 04, 1996 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1860 ID: RA(79.1, GLOBAL REFERENCE: RA(79.1,D0,0) FIELD NUMBER: .01 FIELD NAME: LOCATION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The DSS Extracts RADIOLOGY EXTRACT file (#727.814) contains a field, IMAGING LOCATION, which is a pointer to the RADIOLOGY LOCATIONS file (#79.1). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22505980 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 1861 IA #: 1861 FILE NUMBER: 10 GLOBAL ROOT: DIC(10, DATE CREATED: DEC 04, 1996 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1861 ID: DIC(10, GLOBAL REFERENCE: DIC(10,D0,0) FIELD NUMBER: 2 FIELD NAME: ABBREVIATION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the abbreviation for this race entry. GENERAL DESCRIPTION: DSS Extracts references the following data from the RACE file (#10). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22393937 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham SUBSCRIBING DETAILS: DSS EXTRACTS uses a FileMan read (EN^DIQ1) to obtain data from the ABBREVIATION field (#2). NUMBER: 1863 IA #: 1863 FILE NUMBER: 220.5 GLOBAL ROOT: DENT(220.5, DATE CREATED: DEC 04, 1996 CUSTODIAL PACKAGE: DENTAL CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1863 ID: DENT(220.5, GLOBAL REFERENCE: DENT(220.5,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DSS Extracts references the following data from the DENTAL PROVIDER file (#220.5). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22519483 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1864 IA #: 1864 FILE NUMBER: 225 GLOBAL ROOT: DENT(225, DATE CREATED: DEC 04, 1996 CUSTODIAL PACKAGE: DENTAL CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1864 ID: DENT(225, GLOBAL REFERENCE: DENT(225,D0,0) FIELD NUMBER: .01 FIELD NAME: STATION.DIVISION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DSS Extracts references the following data from the DENTAL SITE PARAMETERS file (#225). (Included in these references is a Direct Global Read of the 'B' Cross Reference.) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25450916 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany NUMBER: 1865 IA #: 1865 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: DEC 05, 1996 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1865 ID: DGPM( GLOBAL REFERENCE: DGPM( FIELD NUMBER: .01 FIELD NAME: DATE/TIME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: TRANSACTION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: PATIENT LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: WARD LOCATION LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .09 FIELD NAME: FACILITY TREATING SPECIALTY LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .14 FIELD NAME: ADMISSION/CHECK-IN MOVEMENT LOCATION: 0;14 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .16 FIELD NAME: PTF ENTRY LOCATION: 0;16 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .17 FIELD NAME: DISCHARGE/CHECK-OUT MOVEMENT LOCATION: 0;17 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .18 FIELD NAME: MAS MOVEMENT TYPE LOCATION: 0;18 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .19 FIELD NAME: ATTENDING PHYSICIAN LOCATION: 0;19 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .24 FIELD NAME: RELATED PHYSICAL MOVEMENT LOCATION: 0;24 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: TYPE OF MOVEMENT LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: The zero node is read into a local variable. The fields above are used. The "B" and "C" x-ref may also be read directly. GENERAL DESCRIPTION: DSS Extracts points to and references the following data from the PATIENT MOVEMENT file (#405). Most of the DSS extract files include a MOVEMENT FILE # field which is a pointer to the PATIENT MOVEMENT file (#405). For the extract date range, DSS uses the following cross references: "ATID1" cross reference ^DGPM("ATID1",DFN,INVERSE_DATE,D0 "ATID2" cross reference ^DGPM("ATID2",DFN,INVERSE_DATE,D0 "ATID6" cross reference ^DGPM("ATID6",DFN,INVERSE_DATE,D0 "ATT1" cross reference ^DGPM("ATT1",DATE,D0 "ATT2" cross reference ^DGPM("ATT2",DATE,D0 "ATT3" cross reference ^DGPM("ATT3",DATE,D0 "ATT6" cross reference ^DGPM("ATT6",DATE,D0 "APCA" cross reference ^DGPM("APCA",DFN,CORRES_ADM,DATE,D0 "APMV" cross reference ^DGPM("APMV",DFN,CORRES_ADM,INVERSE_DATE,D0 "ATS" cross reference ^DGPM("ATS",DFN,CORRES_ADM,INVERSE_DATE, TREATING_SPECIALTY,D0 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25456639 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: Virtual Patient Record (VPR), patch VPR*1*2,is using #1865 to get additional patient movement information beyond what VADPT provides; specifically,looking for the movements tied to an admission using the APCA index. DBA Comments: 01-15-14 DT: Added VPR as a subscriber, effective with VPR*1*2 (released fall of 2013) DATE/TIME EDITED: APR 10, 2009@15:50 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MCDEARMON,JAMES WITH CONCURRENCE OF: MULLER,RICHARD DATE/TIME EDITED: SEP 16, 2010@10:55 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE DATE/TIME EDITED: JAN 15, 2014@12:26 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: YORTY,ROBERT NUMBER: 1867 IA #: 1867 FILE NUMBER: 200 GLOBAL ROOT: VA(200 DATE CREATED: DEC 05, 1996 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1867 ID: VA(200 GENERAL DESCRIPTION: This IA adds two fields to file 200 -- COMMERCIAL PHONE (# .135) and SUPPLY EMPLOYEE (# 400). These fields should be sent out any time file 200 is sent out as a full DD. No data should go with these fields. Any data at the sites in those fields should remain. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22530017 SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring NUMBER: 1869 IA #: 1869 FILE NUMBER: 720 GLOBAL ROOT: ECP( DATE CREATED: DEC 05, 1996 CUSTODIAL PACKAGE: EVENT CAPTURE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1869 ID: ECP( GLOBAL REFERENCE: ECP(D0,0) FIELD NUMBER: .01 FIELD NAME: PROCEDURE NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DSS Extracts references the following data from the EVENT CAPTURE PROCEDURE file (#720). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22530845 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1870 IA #: 1870 FILE NUMBER: 720.1 GLOBAL ROOT: EC(720.1, DATE CREATED: DEC 05, 1996 CUSTODIAL PACKAGE: EVENT CAPTURE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1870 ID: EC(720.1, GLOBAL REFERENCE: EC(720.1,D0,0) FIELD NUMBER: 1 FIELD NAME: CONVERSION (V.2.0) DATE/TIME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DSS Extracts references the following data from the EVENT CAPTURE LOG file (#720.1). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22530894 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1872 IA #: 1872 FILE NUMBER: 720.3 GLOBAL ROOT: ECJ( DATE CREATED: DEC 05, 1996 CUSTODIAL PACKAGE: EVENT CAPTURE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1872 ID: ECJ( GLOBAL REFERENCE: ECJ(D0,0) FIELD NUMBER: .01 FIELD NAME: EVENT CODE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DSS Extracts references the following data from the EC EVENT CODE SCREENS file (#720.3). In order to pass the correct version number to the Austin Automation Center, DSS Extracts examines the Event Capture DD as follows: I $D(^DD(720.3)) S ECVER= STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22530940 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1873 IA #: 1873 FILE NUMBER: 721 GLOBAL ROOT: ECH( DATE CREATED: DEC 05, 1996 CUSTODIAL PACKAGE: EVENT CAPTURE CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File NAME: DBIA1873 READ ACCESS TO FILE #721 ID: ECH( CREATOR: MARRI,NAGARAJA GLOBAL REFERENCE: ECH(D0,0) FIELD NUMBER: 1 FIELD NAME: PATIENT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: DATE/TIME OF PROCEDURE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: LOCATION LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5 FIELD NAME: SECTION LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6 FIELD NAME: DSS UNIT LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7 FIELD NAME: CATEGORY LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 8 FIELD NAME: PROCEDURE LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 9 FIELD NAME: VOLUME LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 11 FIELD NAME: ORDERING SECTION LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 27 FIELD NAME: DSS ID LOCATION: 0;20 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 26 FIELD NAME: ASSOCIATED CLINIC LOCATION: 0;19 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: DSS reads the entire zero node into a local variable. The above fields are used. GLOBAL REFERENCE: ECH(D0,P) FIELD NUMBER: 19 FIELD NAME: PCE CPT CODE LOCATION: P;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 20 FIELD NAME: ICD-9 CODE LOCATION: P;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 21 FIELD NAME: AGENT ORANGE LOCATION: P;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 22 FIELD NAME: RADIATION EXPOSURE LOCATION: P;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 23 FIELD NAME: ENVIRONMENTAL CONTAMINANTS LOCATION: P;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 24 FIELD NAME: SERVICE CONNECTED LOCATION: P;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 25 FIELD NAME: SENT TO PCE LOCATION: P;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 35 FIELD NAME: MILITARY SEXUAL TRAUMA LOCATION: P;9 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 39 FIELD NAME: HEAD/NECK CANCER LOCATION: P;10 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 40 FIELD NAME: COMBAT VETERAN LOCATION: P;11 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: DSS reads the entire P node into a local variable. The above fields are used. GLOBAL REFERENCE: ECH(D0,MOD,D1,0) FIELD NUMBER: 36 FIELD NAME: CPT MODIFIER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: GLOBAL REFERENCE: ECH(D0,DX,0) FIELD NUMBER: 38 FIELD NAME: SECONDARY ICD-9 CODE LOCATION: DX;0 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: ECH( FIELD NUMBER: APAT FIELD NAME: "APAT" CROSS-REFERENCE ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DSS Extracts references the following data from the EVENT CAPTURE PATIENT file (#721). DSS checks for the existence of the EVENT CAPTURE PATIENT file (#721) to determine if Event Capture is in use prior to performing the extract (i.e., global ^ECH). DSS uses the "AC1" cross reference on the DATE/TIME OF PROCEDURE field. Global: ^ECH("AC1",LOCATION,DATE,DA) The Re-Engineered SPINAL CORD DYSFUNCTION application needs to acces the EVENT CAPTURE PATIENT file (#721) for reporting purposes. Spinal Cord needs the ability to look at a patient's CPT and ICD code history. MHV uses the "APAT" cross reference on the Procedure IEN, Date/Time of Procedure fields to get the IEN of Workload, ^ECH("APAT",Procedure IEN,Date/Time of Procedure fields,Workload IEN). Read-only access is granted for:- EVENT CAPTURE PATIENT file (# 721) ^ECH(D0,0) 2 DATE/TIME OF PROCEDURE 0;3 ^ECH(D0,"DX",D1,0) .01 SECONDARY ICD-9 CODE 0;1 ^ECH(D0,"P") 19 PCE CPT CODE P;1 20 PRIMARY ICD-9 CODE P;2 ^ECH("APAT") STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 41992776 KEYWORDS: SPINAL CORD KEYWORDS: DSS SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION SUBSCRIBING DETAILS: SUBSCRIBING PACKAGE: MYHEALTHEVET EDITOR: MARRI,NAGARAJA DBA Comments: 10/30/13 DT: Deactivated and added Kumar as editor to add MyHealtheVet comments. JSHARVEY 20061211/ Deactivated and made J. Morrison editor to bring up to date. DATE ACTIVATED: JAN 23, 2007 DATE/TIME EDITED: DEC 11, 2006@11:09 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: MORRISON,JENNIFER WITH CONCURRENCE OF: FAIN,ZACHARY DATE/TIME EDITED: JAN 23, 2007@23:30 ACTION: APPROVED AT THE REQUEST OF: MORRISON,JENNIFER WITH CONCURRENCE OF: FAIN,ZACHARY DATE/TIME EDITED: NOV 14, 2006@17:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MORRISON,JENNIFER WITH CONCURRENCE OF: FAIN,ZACH DATE/TIME EDITED: OCT 30, 2013@11:47 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: MARRI,NAGARAJA NUMBER: 1874 IA #: 1874 FILE NUMBER: 725 GLOBAL ROOT: EC(725, DATE CREATED: DEC 05, 1996 CUSTODIAL PACKAGE: EVENT CAPTURE CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1874 ID: EC(725, CREATOR: MARRI,NAGARAJA GLOBAL REFERENCE: EC(725,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: NATIONAL NUMBER LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: CPT LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The Current Procedural Terminology (CPT) code equivalent for this national or local procedure. The national or local procedure pointer to the CPT file (#81). GLOBAL DESCRIPTION: This file contains a set of nationally defined procedures for use in the Event Capture software. These procedures are necessary for data collection in DSS that are not represented in the CPT file (#81). These procedures were defined by the Decision Support System (DSS) Program Office or its designee. Entries in this file are standard procedures that should not be edited or deleted. Options exist within the Event Capture Management Menu that provide users the tools to add locally recognized procedures to this file. These local entries will be added, by the using the Event Capture software, at internal entry number above 90,000. This file should NOT be modified directly using VA FileMan. GENERAL DESCRIPTION: MHV Secure Messaging - Workload Credit HL7 Interface references NAME, NATIONAL NUMBER fields from the EC NATIONAL PROCEDURE file (#725). DSS Extracts references the following data from the EC NATIONAL PROCEDURE file (#725). The 'E' cross reference will also be referenced with a Direct global read. ^EC(725,"E",National Number, DA). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25451197 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany SUBSCRIBING PACKAGE: MYHEALTHEVET DBA Comments: 10/30/13 DT: Changed 1874 from Private to Controlled and provided Kumar with editor access. 2/25/15-MM: MHV Securing Message project requested to add My HealtheVet as a subscriber to ICR #1874 for MHV*1.0*11. However, MHV is already listed as a subscriber to this ICR. Updates were made to the description to dcoument MHV Secure Messaging's use of HL7 messaging to access this file. After edits were made, deleted Kumar as editor. DATE/TIME EDITED: FEB 25, 2015@15:59 ACTION: CONTENT CORRECTED AT THE REQUEST OF: MARRI,KUMAR NUMBER: 1875 IA #: 1875 FILE NUMBER: 726 GLOBAL ROOT: EC(726, DATE CREATED: DEC 05, 1996 CUSTODIAL PACKAGE: EVENT CAPTURE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1875 ID: EC(726, GLOBAL REFERENCE: EC(726,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DSS Extracts points to and references the following data from the EVENT CAPTURE CATEGORY file (#726). The DSS Extracts EVENT CAPTURE LOCAL EXTRACT file (#727.815) contains a field, CATEGORY, which is a pointer to the EVENT CAPTURE CATEGORY file (#726). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22531001 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1876 IA #: 1876 FILE NUMBER: 59 GLOBAL ROOT: PS(59, DATE CREATED: DEC 06, 1996 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1876 ID: PS(59, GLOBAL REFERENCE: PS(59,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: SITE NUMBER LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to show the site/station number. GLOBAL REFERENCE: PS(59,D0,INI) FIELD NUMBER: 100 FIELD NAME: RELATED INSTITUTION LOCATION: INI;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is a pointer to the Institution file [^DIC(4,]. GENERAL DESCRIPTION: The DSS PRESCRIPTION EXTRACT file (#727.81) contains the DIVISION field (9) which is a pointer to the OUTPATIENT SITE file (#59). Direct global read of the 'B' Cross Reference is permitted into this file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25455370 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT SUBSCRIBING DETAILS: Actually only needs to reference field .01. SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES NUMBER: 1877 IA #: 1877 FILE NUMBER: 213.3 GLOBAL ROOT: NURSF(213.3, DATE CREATED: DEC 10, 1996 CUSTODIAL PACKAGE: NURSING SERVICE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1877 ID: NURSF(213.3, GLOBAL REFERENCE: NURSF(213.3,D0,0) FIELD NUMBER: .01 FIELD NAME: BED SECTION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The DSS Extracts NURSING EXTRACT file (#727.805) contains a field, NURSING BEDSECTION, which is a pointer to the NURS AMIS WARD file (#213.3). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22519284 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1878 IA #: 1878 DATE CREATED: DEC 11, 1996 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOORDER NAME: DBIA1878 ID: PSOORDER GENERAL DESCRIPTION: Open subscription for Outpatient Pharmacy prescription data. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 37842636 COMPONENT/ENTRY POINT: EN(DFN,RX#) COMPONENT DESCRIPTION: Return Outpatient Prescriptions: Open Subscription (Supported). Requires version 7 of Outpatient Pharmacy software installed. Entry Point: EN^PSOORDER(DFN,RX#) Passed: DFN: Internal entry number for patient in Patient file (#2). DFN is optional. A null value must be passed in it's place. RX#: Internal entry number for prescription in Prescription file (#52). Returned: ^TMP("PSOR",$J,RXN,0)=ID^FD^LSFD^ST^RX#^QTY^DS^RF^RFM^DRCT^RXCT^EXDT^RELDT^RTSD T^WPC^PAT^LDT RXN = Internal Rx # ID = Issue date of Rx FD = Fill date of Rx. LSFD = Last fill date of Rx ST = Status of Rx. This variable has the format A;B where: A = code B = external printable form, (e.g., A for ACTIVE, DC for discontinued) If status of prescription equals Hold: ^TMP("PSOR",$J,RXN,"HOLD",0)=HDRS^HDCOM^HDDT HDRS = Hold Reason, HDCOM = Hold Comments, HDDT = Hold Date If status of prescription equals Suspended or has had an entry in the Suspense file (#52.5) ^TMP("PSOR",$J,RXN,"SUS",0)=PRT^CMIND PRT = Printed Status: Printed, or Not Printed CMIND = CMOP Indicator. Data will only appear in this field if sites has the CMOP package installed and in use. Q = Queued for Transmission, X = Transmission Completed, L = Loading for Transmission, P = Printed Locally RX# = External Rx number QTY = Quantity Dispensed DS = Day Supply RF = Number of refills RFM = Number of refills remaining DRCT = Drug Cost of Original Fill RXCT = Cost of Original Fill EXDT = Expiration/Cancel date of Rx RELDT = Release Date/Time RTSDT = Returned to Stock Date WPC = Was Patient Counseled - (Yes/No) PAT = Patient. This variable has the format A;B where A is the internal pointer and B is the external printable form. LDT = This date is the date the original Rx was added to the prescription file (#52). Login Date. ^TMP("PSOR",$J,RXN,1)= PR^CLK^VRP^CLN^RXP^MW^DIV^OERR#^FP^NDC^TPBRX PR = Provider. This variable has the format A;B where A is the internal pointer and B is external printable form. CLK = Entered By (clerk code). This variable has the format A;B where A is the internal pointer and B is external printable form. VRP = Verifying Pharmacist. This variable has the format A;B where A is the internal pointer and B is external printable form. CLN = Clinic. This variable has the format A;B where A is the internal pointer and B is external printable form. Data comes from file #44. RXP = Rx Patient Status. This variable has the format A;B where A is the internal pointer and B is external printable form. M/W = Mail/Window Routing. This variable has the format A;B where A is the code and B is external printable form. DIV = Pointer to Outpatient Site file (#59). OERR# = Order number that points to the CPRS Orders file (#100). FP = Finishing Person. This variable has the format A;B where A is the internal pointer and B is external printable form. NDC = National Drug Code. TPBRX = This variable indicates that the Rx has been created as part of the Transitional Pharmacy Benefit project. CMOP Data: If applicable ^TMP("PSOR",$J,RXN,"CMOP",n,0)=TRANS #^SEQ #^FILL #^CMSTA^CMDCDT^NDC TRANS # = Transaction number. Pointer value to the CMOP Transmission file (#550.2). SEQ # = Sequence number. This number represents the order number sent to the CMOP Host facility. Fill # = Fill #. 0 for original, 1-11 for refills. CMSTA = CMOP Status. This variable has the format A;B where A is the internal pointer and B is external printable form. CMDCDT = CMOP cancel date NDC = National Drug file Code - free text ^TMP("PSOR",$J,RXN,"CMOP",1,1,0)=CMDC REASON CMDC REASON = CMOP cancel reason. note: CMDCDT and CMDC REASON fields are only populated if CMSTA equals 3. Drug Data: ^TMP("PSOR",$J,RXN,"DRUG",0)= DR^VA PRINT NAME^DRUG ID^VA DRUG CLASS DR = Drug in Rx. This variable has the format A;B where A is the internal pointer and B is external printable form. VA Print Name = VA Print name found in NDF DRUG ID = National drug ID found in NDF VA DRUG CLASS = VA DRUG CLASSIFICATION ^TMP("PSOR",$J,RXN,"DRUGOI",0)= ORDERABLE ITEM ORDERABLE ITEM = Pharmacy Orderable Item tied to drug in Rx. This variable has the format A;B where A is the internal pointer and B is external printable form concatenated with dose form, i.e., ASPIRIN TAB. Copay: If applicable ^TMP("PSOR",$J,RXN,"IB",0)=COPAY TRANSACTION TYPE^IB NUMBER) COPAY TRANSACTION TYPE = 1 or 2 IB NUMBER = IB pointer number Refills: ^TMP("PSOR",$J,RXN,"REF",n,0)=RFD^PR^CLK^QTY^DS^DRCT^RXCT^RELDT^RTSDT^M/W^DIV^L DT^NDC RXN = Internal Rx # RFD = Refill Date PR = Provider. This variable has the format A;B where A is the internal pointer and B is external printable form. CLK = Refill entry by. This variable has the format A;B where A is the internal pointer and B is external printable form. QTY = Quantity Dispensed DS = Day Supply DRCT = Drug Cost of Refill RXCT = Cost of Refill RELDT = Release Date/Time RTSDT = Returned to Stock Date M/W = Mail/Window Routing. This variable has the format A;B where A is the code and B is external printable form. DIV = Pointer to Outpatient Site file (#59). LDT = This date indicates the date the refill was requested. This is not the date the refill will be dispensed (Login Date). NDC = National Drug Code Partial Fills: ^TMP("PSOR",$J,RXN,"RPAR",n,0)=PRD^PR^CLK^QTY^DS^DRCT^RXCT^RELDT^RTSDT^M/W^DIV^ LDT^NDC RXN = Internal Rx # PRD = Partial Date PR = Provider. This variable has the format A;B where A is the internal pointer and B is external printable form. CLK = Refill entry by. This variable has the format A;B where A is the internal pointer and B is external printable form. QTY = Quantity Dispensed DS = Day Supply DRCT = Drug Cost of partial RXCT = Cost of partial RELDT = Release Date/Time RTSDT = Returned to Stock Date M/W = Mail/Window Routing. This variable has the format A;B where A is the code and B is external printable form. DIV = Pointer to Outpatient Site file (#59). LDT = This date indicates the date the partial fill was created (Login Date). NDC = National Drug Code Activity Log: ^TMP("PSOR",$J,RXN,"ACT",n,0)=D/T^REA^NEW PERSON^RX #^COMMENTS D/T = Date/Time entry made REA = Reason entry was made New Person = Entry created by RX # = Which fill the activity occurred on (original, refill, partial). Comments = Comments about the Activity that occurred. Medication Instructions: ^TMP("PSOR",$J,RXN,"SIG",n,0)= Condensed Medication Instructions (SIG) ^TMP("PSOR",$J,RXN,"SIG1",n,0)= Expanded Medication Instructions (SIG) Dispensing Instructions: ^TMP("PSOR",$J,RXN,"MI",N,0)=DOSAGE^DOSE^UNITS^NOUN^DURATION^CONJUNCTION^MRT^SC H^VERB DOSAGE = This is the strength of the medication dispensed. This variable can be a numeric value or free-text. DOSE = This numeric value represents the total number of pills to make a total dosage. This value is only returned when the dosage is numeric. UNITS = This data element is the unit of measure the medication is dispense. This variable has the format A;B where A is the internal pointer and B is external printable form. NOUN = This data element indicates the form the medication was dispensed, i.e., tablet. DURATION = This indicates how long this dosage should be taken. CONJUNCTION = This data element is used for complex dosaging instructions. MRT = This data element indicates how the medication is ingested (medication route). This variable has the format A;B where A is the internal pointer and B is external printable form. SCH = This data indicates when the medication is taken (schedule). VERB = This data element indicates what action is taken to ingest the medication. Patient Instructions: ^TMP("PSOR",$J,RXN,"PI",n,0)=EXPANDED PATIENT INSTRUCTIONS The ^TMP("PSOR",$J) is killed each time the entry point is called. It will be the responsibility of each developer to kill the ^TMP("PSOR",$J) global and the DFN and Rx # variables when finished. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This variable is the patient's internal entry number from the Patient file (#2). This variable is optional. If the internal entry number is not sent, then a null value must be passed in it's place. VARIABLES: RX# TYPE: Input VARIABLES DESCRIPTION: This variable is the internal entry number of a prescription. This number either comes from the Pharmacy Patient file (#55), Prescription Profile sub-file which requires a separate DBIA. NUMBER: 1880 IA #: 1880 FILE NUMBER: 52.6 GLOBAL ROOT: PS(52.6, DATE CREATED: DEC 12, 1996 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1880 ID: PS(52.6, GLOBAL REFERENCE: PS(52.6,D0,0) FIELD NUMBER: 1 FIELD NAME: GENERIC DRUG LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DSS Extracts references the following data from the IV ADDITIVES file (#52.6). This reference is used ONLY for the small number of sites who are still running a version of Inpatient Meds prior to version 4.5. For version 4.5 (or greater), this information comes from the IV EXTRACT DATA holding file (#728.113) which is populated by PSIVSTAT. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22498459 SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 1882 IA #: 1882 DATE CREATED: DEC 12, 1996 CUSTODIAL PACKAGE: DSS EXTRACTS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ECXPIV1 NAME: ACCESS TO ECXPIV1 ID: ECXPIV1 GENERAL DESCRIPTION: DSS Extracts needs data from the Inpatient Medications package which cannot be extracted from any file. The IV team has modified routine PSIVSTAT to call, after executing %ZOSF("TEST"), routine ECXPIV1 to move data into a DSS file for future extract by DSS. The requested data is placed in the ECUD variable, which the ECXPIV1 routine uses to store the data in the IV EXTRACT DATA file (#728.113). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34589914 KEYWORDS: EXCPIV1 KEYWORDS: PSIVSTAT COMPONENT/ENTRY POINT: VARIABLES: ECUD TYPE: Output VARIABLES DESCRIPTION: Variable ECUD contains the following pieces of data: 1. Patient for whom drug was dispensed. 2. Order number. 3. The drug dispensed. 4. Date drug dispensed. 5. Transaction type. 6. Additive strength. 7. Additive strength units. 8. Solution volume. 9. Provider who order the drug. 10. Type. 11. Cost of units dispensed. 12. Clinic Location if available for Out Patients. 13. Order Start Date/Time. 14. IV Room associated with this order. 15. Date/time verified by the nurse. If not available, this will be the login date/time of the order. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS NUMBER: 1884 IA #: 1884 FILE NUMBER: 59.5 GLOBAL ROOT: PS(59.5, DATE CREATED: DEC 13, 1996 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1884 ID: PS(59.5, GLOBAL REFERENCE: PS(59.5,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: DIVISION LOCATION: 0;4 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field contains the pointer to the MEDICAL CENTER DIVISION file (#40.8). The division should be the one where the IV Room is located. This field is populated by an option on the DSS menu. It is solely for use by the DSS software and has no impact on Pharmacy at this time. Direct Global Read is also permitted into this field. GLOBAL REFERENCE: PS(59.5,D0,I) FIELD NUMBER: 19 FIELD NAME: INACTIVATION DATE LOCATION: I:1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DSS Extracts references the following data from the IV ROOM file (#59.5). This agreement will be restricted to only Pharmacy packages after 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. An API has been created that can be used in place of any code needing to make use of this agreement. This API was released with patch PSJ*5*163. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with this API, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25451328 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham NUMBER: 1886 IA #: 1886 FILE NUMBER: 631 GLOBAL ROOT: HBHC(631, DATE CREATED: JAN 16, 1997 CUSTODIAL PACKAGE: HOSPITAL BASED HOME CARE CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1886-A ORIGINAL NUMBER: 1886 ID: HBHC(631, GLOBAL REFERENCE: HBHC(631,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 14 FIELD NAME: ADMIT/REJECT ACTION LOCATION: 0;15 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 17 FIELD NAME: ADMISSION DATE LOCATION: 0;18 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 39 FIELD NAME: DISCHARGE DATE LOCATION: 0;40 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: HBHC(631,D0,1) FIELD NUMBER: 67 FIELD NAME: CASE MANAGER LOCATION: 1;13 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The "AC" cross-reference will be used to find HBHC patients discharged within a date range. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22898832 SUBSCRIBING PACKAGE: PATIENT FEEDBACK ISC: Albany NUMBER: 1887 IA #: 1887 FILE NUMBER: 631.4 GLOBAL ROOT: HBHC(631.4, DATE CREATED: JAN 17, 1997 CUSTODIAL PACKAGE: HOSPITAL BASED HOME CARE CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1886-B ORIGINAL NUMBER: 1886 ID: HBHC(631.4, GLOBAL REFERENCE: HBHC(631.4,D0,0) FIELD NUMBER: 1 FIELD NAME: PROVIDER NAME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22898841 SUBSCRIBING PACKAGE: PATIENT FEEDBACK ISC: Albany NUMBER: 1888 IA #: 1888 FILE NUMBER: 45 GLOBAL ROOT: DGPT( DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1888 ID: DGPT( GLOBAL REFERENCE: DGPT(D0,300) FIELD NUMBER: 300.03 FIELD NAME: LEGIONNAIRE'S DISEASE LOCATION: PIECE 3 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DGPT(D0,M,D1,300) FIELD NUMBER: 300.03 FIELD NAME: LEGIONNAIRE'S DISEASE LOCATION: PIECE 3 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Lab Emerging Pathogen Initiative is requesting a integration agreement to reference to two fields in the PTF file (#45) PTF file (#45) ^DGPT(D0,300) = (#300.03) LEGIONNAIRE'S DISEASE ^DGPT(D0,"M",D1,300) = (#300.03) LEGIONNAIRE'S DISEASE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22949308 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 1889 IA #: 1889 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAPI NAME: ADD/EDIT/DELETE PCE DATA SILENTLY ORIGINAL NUMBER: 1889 ID: PXAPI CREATOR: HARVEY,JULIE S GENERAL DESCRIPTION: PURPOSE: Provide a utility for ancillary packages such as Laboratory, Surgery, Medicine, Radiology, Text Integration Utility (TIU) and Computerized Patient Record System (CPRS) to non- interactively (silently) add/edit/delete data, including encounter, provider, diagnosis and procedure information. Dr. Kizer's 10/1/96 mandate which requires a provider, a procedure and a diagnosis to positively document the occurrence of an encounter, and the resulting change to use this data rather than stop codes to document workload and initiate third party billing, necessitated the development of an application programmer interface (API) which would support the mandated requirements. PCE was tasked with developing the API. $$DATA2PCE^PXAPI was developed to enable the adding, editing and deletion of encounter, provider, diagnosis and procedure data. Data will be stored in the Visit and V files and will be posted on the PXK VISIT DATA EVENT for use by subscribing packages such as Scheduling. This document includes: 1. Definitions and Conventions used to describe the API. 2. Description of $$DATA2PCE^PXAPI, its parameter definitions, and the returned values. 3. A table which describes the subscripts used for passing data to PCE. 4. An example array for passing data to PCE. DEFINITIONS AND CONVENTIONS: Listed below are definitions and conventions used to describe this API. 1. Valid data values: [ 1 | 0 | null ] `1' Denotes TRUE or YES `0' Denotes FALSE or NO null Denotes VALUE NOT KNOWN 2. Counter "i" is used as a subscript. It denotes a sequence number, i.e., 1, 2, 3. To denote deletion of a data ITEM, pass the "@" symbol as the data value in the node for the item being deleted. You may not delete required data items. 4. To denote deletion of an ENTRY, pass "1" as the data value in the "DELETE" node of the identified entry. $$DATA2PCE^PXAPI(INPUT_ROOT,PKG,SOURCE,.VISIT,USER,ERRDISP,.ERRARRAY,PPEDIT, .ERRPROB,.ACCOUNT) This is a function which will return a value identifying the status of the call. Data that is processed by PCE will be posted on the PXK VISIT DATA EVENT protocol. Parameter Description: 1. INPUT_ROOT: (required) Where INPUT_ROOT is a unique variable name, either local array or global array, which identifies the defined data elements for the encounter. An example of an INPUT_ROOT is ^TMP("LRPXAPI",$J) or ^TMP("RAPXAPI",$J). The gross structure of the array includes four additional subscripts (ENCOUNTER, PROVIDER, DX/PL, PROCEDURE and STOP) for defining the data passed. A detailed description of this array and its structure are included below in a table format. 2. PKG: (required) Where PKG is a pointer to the Package File (9.4). 3. SOURCE: (required) Where SOURCE is a string of text (3-30 character) identifying the source of the data. The text is the SOURCE NAME field (.01) of the PCE Data Source file (839.7). If the SOURCE currently does not exist in the file, it will be added. Examples of SOURCE are: "LAB DATA" or "RADIOLOGY DATA" or "PXCE DATA ENTRY" or "AICS ENCOUNTER FORM." 4. VISIT: (optional) Where VISIT is a pointer to the Visit file (9000010) which identifies the encounter which this data must be associated with. If the pointer to the Visit file does not match data passed in INPUT_ROOT then this DBIA will return negative value '-3', see the Returned Value description below. If the pointer value to the Visit is saved, it is necessary to also subscribe to IA 1902. 5. USER: (optional) User who is responsible for add/edit/delete action on the encounter. Pointer to the New Person file (200). If USER is not defined, DUZ will be used. 6. ERRDISP: (optional) To display errors during development, this variable may be set to "1". If it is defined the errors will be displayed on screen when the error occurs. If ERRDISP is not defined, errors will be posted on the defined INPUT_ROOT subscripted by "DIERR". BLD^DIALOG is used to manage errors. Review BLD^DIALOG and MSG^DIALOG descriptions included in the FileMan v. 22.0 Programmer Manual on pages 2-33 to 2-38. 7. ERRARRAY: (optional) A dotted variable name. When errors and warnings occur, the array will contain the PXKERROR array elements to the caller. 8. PPEDIT: (optional) Set to 1 if you want to edit the Primary Provider. Only use for the moment that editing is being done. 8. ERRPROB: (optional) A dotted variable name. When errors and warnings occur, they will be passed back in the form of an array with the general description of the problem. 8. ACCOUNT: (optional) A dotted variable name. Where ACCOUNT is the PFSS Account Reference associated with the data being by the calling application. Each PFSS Account represents an internal entry number in the PFSS ACCOUNT file (#375). Returned Value: 1 If no errors occurred and data was processed. -1 An error occurred. Data may or may not have been processed. If ERR_DISPLAY is undefined, errors will be posted on the INPUT_ROOT subscripted by "DIERR". -2 Unable to identify a valid VISIT. No data was processed. -3 API was called incorrectly. No data was processed. It is advisable to verify a Return Value for confirmation if the passed data was processed or not, also if this DBIA is called in background. ENCOUNTER: All data must be associated with an entry in the VISIT file (#9000010). Only one "ENCOUNTER" node may be passed with each call to $$DATA2PCE^PXAPI. The "ENCOUNTER" node documents encounter specific information and must be passed: 1. To create an entry in the VISIT file (9000010). All provider, diagnosis and procedure data is related to an entry in the VISIT file. 2. To enable adding, editing or deleting "ENCOUNTER" node data elements. When encounter data elements are not added, edited or deleted, the VISIT parameter may be passed in lieu of defining an "ENCOUNTER" node. SUBSCRIPT DESCRIPTION: "ENCOUNTER",1,"ENC D/T") Required This is the encounter date/ time for primary encounters or the date for occasions of service. If the encounter is related to an appointment, this is the appointment date/time. If this is an occasion of service created by an ancillary package, this is the date/time of the instance of care. Imprecise dates are allowed for historical encounters. Encounter date/time may be added, but not edited. *Deletions of encounters can occur only when nothing is pointing to the encounter. *"ENC D/T" is not required for existing visits where the visit number is included in the parameter list but if it is passed then it will be checked against the VISIT/ADMIT DATE&TIME field (#.01) in the Visit file of the vistit IEN passed as the VISIT parameter. Only matching values will be accepted and if on match occurs then '-3' will be retured, see the Returned Value above. Format: FileMan Internal Format for date/time "ENCOUNTER",1,"PATIENT") Required This is the patient DFN. This cannot be edited or deleted. *"PATIENT" is not required for existing visits where the visit number is included in the parameter list but if it is passed then it will be checked against the PATIEN NAME field (# .05) in the Visit file of the visit IEN passed as the VISIT parameter. Only matching values will be accepted and if on match occurs then -3 will be returned, see the Returned Value above. Format: Pointer to IHS Patient file (9000001) This file is Dinumed to the Patient file (2) "ENCOUNTER",1,"HOS LOC") Required This is the hospital location where the encounter took place for primary encounters, or this is the ordering location for ancillary encounters. *"HOS LOC" is not required for existing visits where the visit number is included in the parameter list but if it is passed then it will be checked against the HOSPITAL LOCATION filed (#.22) in the Visit file of the visit IEN passed as the VISIT parameter. Only matching values will be accepted and if no match occurs then '-3' will be returned, see the Returned Value above. Format: Pointer to Hospital Location file (44) "ENCOUNTER",1,"OUTSIDE LOCATION") Optional This is an outside location of an encounter, not included in the INSTITUTION file. The OUTSIDE LOCATION should exclude the INSTITUTION: "ENCOUNTER",1,"INSTITUTION") and the INSTITUTION should exclude the OUTSIDE LOCATION. Format: Free text (2-245 characters) "ENCOUNTER",1,"INSTITUTION") Optional This is the Institution where the encounter took place. If it is not defined, the division defined for the Hospital Location is used. If that is not defined, $$SITE^VASITE is used. Format: Pointer to IHS Location file (9999999.06). This file is dinumed to the Institution file (4). "ENCOUNTER",1,"SC") Optional This encounter is related to a service connected condition. Format: [ 1 | 0 | null ] "ENCOUNTER",1,"CV") Optional This encounter is related to Combat Veteran Format: [ 1 | 0 | null ] "ENCOUNTER",1,"AO") Optional This encounter is related to Agent Orange exposure. Format: [ 1 | 0 | null ] "ENCOUNTER",1,"IR") Optional This encounter is related to Ionizing Radiation exposure. Format: [ 1 | 0 | null ] "ENCOUNTER",1,"EC") Optional This encounter is related to Environmental Contaminant exposure. Format: [ 1 | 0 | null ] "ENCOUNTER",1,"SHAD") Optional This encounter is related to Project 112/SHAD Format: [ 1 | 0 | null ] "ENCOUNTER",1,"MST") Optional This encounter is related to Military Sexual Trauma. Format: [ 1 | 0 | null ] "ENCOUNTER",1,"HNC") Optional This encounter is related to Head & Neck Cancer. Format: [ 1 | 0 | null ] "ENCOUNTER",1,"CHECKOUT D/T") Optional This is the date/time when the encounter was checked out. Format: FileMan Internal Format for date/time "ENCOUNTER",1,"ELIGIBILITY") Optional This is the eligibility of the patient for this encounter. Format: Pointer to Eligibility Code file (8) "ENCOUNTER",1,"APPT") Optional This is the appointment type of the encounter. Format: Pointer to Appointment Type file (409.1) "ENCOUNTER",1,"SERVICE CATEGORY") Required This denotes the type of encounter. Format: Set of Codes. A::=Ambulatory Should be used for clinic encounters. "A" s are changed to "I" s by Visit Tracking if patient is an inpatient at the time of the encounter. H::=Hospitalization Should be used for an admission. I::=In Hospital C::=Chart Review T::=Telecommunications N::=Not Found S::=Day Surgery E::=Event (Historical) Documents encounters that occur outside of this facility. Not used for workload credit or 3rd party billing. R::=Nursing Home D::=Daily Hospitalization Data X::=Ancillary Package Daily Data. "X" s are changed to "D" s by Visit Tracking if patient is an inpatient at the time of the encounter. "ENCOUNTER",1,"DSS ID") Optional This is required for ancillary occasions of service such as laboratory and radiology or telephone encounters Format: Pointer to Clinic Stop file (40.7) "ENCOUNTER",1,"ENCOUNTER TYPE") Required This identifies the type of encounter, e.g., primary encounter, ancillary encounter, etc. A "Primary" designation indicates that the encounter is associated with an appointment or is a standalone. Examples of ancillary encounters include Laboratory and Radiology instances of care. Format: Set of Codes. P::=Primary O::=Occasion of Service S::=Stop Code A::=Ancillary Ancillary packages such as Laboratory and Radiology Should pass an "A" C::=Credit Stop If the visit number is included in passed parameters then the passed code will be checked against the ENCOUNTER TYPE field (#15003) in the Visit file of the visit IEN passed as VISIT parameter. Only matching values will be accepted and if no match occurs then '-3' will be returned, see the Returned Value above. "ENCOUNTER",1,"PARENT") Optional This is the parent encounter for which the ENCOUNTER is a supporting encounter. For example, this would be the primary encounter for which this occasion of service supports and should be associated. Format: Pointer to Visit file (9000010). "ENCOUNTER",1,"COMMENT") Optional Comment Format: Free Text (1-245 characters) "ENCOUNTER",1,"DELETE") Optional This is a flag that denotes deletion of the encounter entry. Encounter will not be deleted if other data is pointing to it. Format: [ 1 | null ]| PROVIDER: The "PROVIDER" node may have multiple entries (i) and documents the provider, indicates whether he/she is the primary provider, and indicates whether the provider is the attending provider. Comments may also be passed. To delete the entire "PROVIDER" entry, set the "DELETE" node to 1. SUBSCRIPT DESCRIPTION: "PROVIDER",i,"NAME") Required Provider's IEN. Format: Pointer to NEW PERSON file (200) "PROVIDER",i,"PRIMARY") Optional Indicator that denotes this provider as the "primary" provider. Format: [ 1 | 0 | null ] "PROVIDER",i,"ATTENDING") Optional Indicator that denotes this provider as the attending provider. Format: [ 1 | 0 | null ] "PROVIDER",i,"COMMENT") Optional Comment Format: Free text (1 - 245 characters) "PROVIDER",i,"DELETE") Optional This is a flag that denotes deletion of the Provider entry. Format: [ 1 | null ]| DX/PL: The "DX/PL" node may have multiple entries (i) and documents diagnoses and/or problems. Only active ICD-9-CM codes will be accepted. The "DX/PL" node adds diagnoses to the PCE database as well as adding an active or inactive diagnosis or problem to the Problem List. If a diagnosis or problem already exists on the Problem List, this node may be used to inactivate it. To delete the entire "DX/PL" entry from PCE (not Problem List), set the "DELETE" node to 1. SUBSCRIPT DESCRIPTION: "DX/PL",i,"DIAGNOSIS") Required for PCE Optional for PL Diagnosis code Format: Pointer to ICD9 Diagnosis file (80) "DX/PL",i,"PRIMARY") Optional for PCE N/A for PL Code that specifies that the diagnosis is the "primary" diagnosis for this encounter. Only one "primary" diagnosis is recorded for each encounter. Format: "P"::=Primary "1"::=Primary "S"::=Secondary "0"::=Secondary "DX/PL",i,"ORD/RES") Optional for PCE N/A for PL Code that specifies that the diagnosis is either an "ordering diagnosis or is a "resulting diagnosis or "both for this encounter. Format: "O ::=Ordering "R ::=Resulting "OR ::=Both Ordering and Resulting "DX/PL",i,"LEXICON TERM") Optional for PCE Optional for PL This is a term that is contained in the Clinical Lexicon. Format: Pointer to the Expressions file (757.01) "DX/PL",i,"PL IEN") Optional for PCE *Optional for PL This is the problem IEN that is being acted upon. *This node is required to edit an existing problem on the Problem List. Format: Pointer to Problem List file (9000011) "DX/PL",i,"PL ADD") N/A for PCE *Optional for PL *This is required to Add a diagnosis/problem to the Problem List. "1" indicates that the entry should be added to the Problem List. Format: [ 1 | 0 | null ] "DX/PL",i,"PL ACTIVE") N/A for PCE Optional for PL This documents whether a problem is active or inactive. The Default is Active if not specified. Format: Set of Codes. A::=Active I::=Inactive "DX/PL",i,"PL ONSET DATE") N/A for PCE Optional for PL The date that the problem began. Format: FileMan Internal Format for date. "DX/PL",i,"PL RESOLVED DATE") N/A for PCE Optional for PL The date that the problem was resolved. Format: FileMan Internal Format for date. "DX/PL",i,"PL SC") Required for PCE Optional for PL This problem is related to a service connected condition. Format: [ 1 | 0 | null ] "DX/PL",i,"PL CV") Required for PCE Optional for PL This problem is related to Combat Veteran Format: [ 1 | 0 | null ] "DX/PL",i,"PL AO") Required for PCE Optional for PL This problem is related to Agent Orange exposure. Format: [ 1 | 0 | null ] "DX/PL",i,"PL IR") Required for PCE Optional for PL This problem is related to Ionizing Radiation exposure. Format: [ 1 | 0 | null ] "DX/PL",i,"PL SHAD") Required for PCE Optional for PL This problem is related to Project 112/SHAD Format: [ 1 | 0 | null ] "DX/PL",i,"PL EC") Required for PCE Optional for PL This problem is related to Environmental Contaminant exposure. Format: [ 1 | 0 | null ] "DX/PL",i,"PL MST") Required for PCE Optional for PL This problem is related to Military Sexual Trauma. Format: [ 1 | 0 | null ] "DX/PL",i,"PL HNC") Required for PCE Optional for PL This problem is related to Head and/or Neck Cancer Format: [ 1 | 0 | null ] "DX/PL",i,"NARRATIVE") *Optional for PCE *Optional for PL The provider's description of the diagnosis/problem. *If NARRATIVE is not passed for a diagnosis/problem, the Description from the ICD Diagnosis file (80) will be used as the default. Format: Free text (2-245 characters) "DX/PL",i,"CATEGORY") Optional for PCE N/A for PL A term that denotes a grouping or category for a set of related diagnosis/problem. Format: Free text (2-245 characters) "DX/PL",i,"ENC PROVIDER") Optional for PCE *Optional for PL Provider who documented the diagnosis/problem. *This is required to Add a diagnosis/problem to the Problem List. Format: Pointer to New Person file (200) "DX/PL",i,"EVENT D/T") Optional for PCE N/A for PL Date/Time Diagnosis was documented. Format: FileMan Internal Format for date/time "DX/PL",i,"COMMENT") Optional for PCE *Optional for PL Comment Format: PCE Free Text (1-245 char) PL Free Text (3-60 char) "DX/PL",i,"DELETE") Optional for PCE N/A for PL This is a delete flag used to denote deletion of the diagnosis entry. Format: [ 1 | null ]| PROCEDURE: The "PROCEDURE" node may have multiple entries (i). Only active CPT/HCPCS codes will be accepted. The "PROCEDURE" node documents the procedure(s), the number of times the procedure was performed, the diagnosis the procedure is associated with and the narrative that describes the procedure. It also enables documentation of the provider who performed the procedure, the date/time the procedure was performed and any comments that are associated with the procedure. To delete the entire "PROCEDURE" entry, set the "DELETE" node to 1. SUBSCRIPT DESCRIPTION: "PROCEDURE",i,"PROCEDURE") Required Procedure code Format: Pointer to CPT file (81) "PROCEDURE",i,"MODIFIERS",MODIFIER)="" Optional CPT Modifier(s) Format: external form. Any number of modifiers may be listed. "PROCEDURE",i,"QTY") Required Number of times the procedure was performed. Format: Whole number > 0 "PROCEDURE",i,"DIAGNOSIS") Optional The first diagnosis that is associated with the identified procedure and is the primary diagnosis associated with this procedure. Format: Pointer to ICD Diagnosis file (80) "PROCEDURE",i,"DIAGNOSIS 2") Optional The second diagnosis that is associated with the identified procedure. "PROCEDURE",i,"DIAGNOSIS 3") Optional The third diagnosis that is associated with the identified procedure. "PROCEDURE",i,"DIAGNOSIS 4") Optional The fourth diagnosis that is associated with the identified procedure. "PROCEDURE",i,"DIAGNOSIS 5") Optional The fifth diagnosis that is associated with the identified procedure. "PROCEDURE",i,"DIAGNOSIS 6") Optional The sixth diagnosis that is associated with the identified procedure. "PROCEDURE",i,"DIAGNOSIS 7") Optional The seventh diagnosis that is associated with the identified procedure. "PROCEDURE",i,"DIAGNOSIS 8") Optional The eighth diagnosis that is associated with the identified procedure. Format: Pointer to ICD Diagnosis file (80) "PROCEDURE",i,"NARRATIVE") *Optional The provider's description of the procedure performed. *If NARRATIVE is not passed for a procedure, the Short Name from the CPT file (81) will be used as the default. Format: Free text (2-245 characters) "PROCEDURE",i,"CATEGORY") Optional A term that denotes a grouping or category for a set of related procedures. Format: Free text (2-245 characters) "PROCEDURE",i,"ENC PROVIDER") Optional Provider who performed the procedure. Format: Pointer to New Person file (200) "PROCEDURE",i,"ORD PROVIDER") Optional Provider who ordered the procedure. Format: Pointer to New Person file (200) "PROCEDURE",i,"ORD REFERENCE") Optional Order reference for the ordered procedure. Format: Pointer to the Order file (100) "PROCEDURE",i,"EVENT D/T") Optional Date/Time procedure was done. Format: FileMan Internal Format for date/time "PROCEDURE",i,"DEPARTMENT") Optional A 3-digit code that defines the service area. Missing Department Codes will be assigned a Department Code. The Department Code will be the Stop Code associated (in the HOSPITAL LOCATION file, #44) with the Hospital Location of the patient visit. If no Department Code can be established, a 999 will be passed to the PFSS Cache. Format: Set of Codes. 1::=Poor 2::=Fair 3::=Good 4::=Group--No Assessment 5::=Refused 108::=Laboratory 160::=Pharmacy 419::=Anesthesiology 423::=Prosthetics 180::=Oral Surgery 401::=General Surgery 402::=Cardiac Surgery 403::=Otorhinolaryngology (ENT) 404::=Gynecology 406::=Neurosurgery 407::=Ophthalmology 409::=Orthopedics 410::=Plastic Surgery (inc. H&N) 411::=Podiatry 412::=Proctology 413::=Thoracic Surgery 415::=Peripheral Vascular 457::=Transplantation 105::=General Radiology 109::=Nuclear Medicine 109::=Cardiology Studies (Nuclear Med) 115::=Ultrasound 703::=Mammography 150::=CT Scan 151::=Magnetic Resonance Imaging 152::=Angio-Neuro-Interventional 421::=Vascular Lab "PROCEDURE",i,"COMMENT") Optional Comment Free Text (1-245 characters) "PROCEDURE",i,"DELETE") Optional This is a flag that denotes deletion of the Procedure entry. Format: [ 1 | null ]| PATIENT ED: The "PATIENT ED" node may have multiple entries (i). To delete the entire "PATIENT ED" entry, set the "DELETE" node to 1. SUBSCRIPT DESCRIPTION: "PATIENT ED",i,"TOPIC") Required Education Topic that patient received education. Format: Pointer to Education Topics file (9999999.09) "PATIENT ED",i,"UNDERSTANDING") Optional The patients level of understanding of the education. Format: Set of Codes. 1::=Poor 2::=Fair 3::=Good 4::=Group--No Assessment 5::=Refused "PATIENT ED",i,"ENC PROVIDER") Optional Provider who was the educator. Format: Pointer to New Person file (200) "PATIENT ED",i,"EVENT D/T") Optional Date/Time of Event Format: FileMan Internal Format for date/time "PATIENT ED",i,"COMMENT") Optional Comment Format: Free Text field (1-245 characters) "PATIENT ED",i,"DELETE") Optional This is a flag that denotes deletion of the Provider entry. Format: [ 1 | null ]| "PATIENT ED",i,"DELETE") Optional This is a flag that denotes deletion of the Patient Ed entry. Format: [ 1 | null ]| HEALTH FACTOR: The "HEALTH FACTOR" node may have multiple entries (i). To delete the entire "HEALTH FACTOR" entry, set the "DELETE" node to 1. SUBSCRIPT DESCRIPTION: "HEALTH FACTOR",i,"HEALTH FACTOR") Required Health Factor that contributes to a patient's state of health. Format: Pointer to Health Factors file (9999999.64) "HEALTH FACTOR",i,"LEVEL/SEVERITY") Optional Level/Severity of health factor related to the patient's state of health. Format: Set of Codes. M::=Minimal MO:=Moderate H:=Heavy/Severe "HEALTH FACTOR",i,"ENC PROVIDER") Optional Provider who documented the health factor. Format: Pointer to New Person file (200) "HEALTH FACTOR",i,"EVENT D/T") Optional Date/Time of Event Format: FileMan Internal Format for date/time "HEALTH FACTOR",i,"COMMENT") Optional Comment Format: Free Text field (1-245 characters) "HEALTH FACTOR",i,"DELETE") Optional This is a flag that denotes deletion of the Health Factor entry. Format: [ 1 | null ]| EXAM: The "EXAM" node may have multiple entries (i). To delete the entire "EXAM" entry, set the "DELETE" node to 1. SUBSCRIPT DESCRIPTION: "EXAM",i,"EXAM") Required Exam that was performed. Format: Pointer to Exam file (9999999.15) "EXAM",i,"RESULT") Optional Result of Exam Format: Set of Codes. A::=Abnormal N::=Normal "EXAM",i,"ENC PROVIDER") Optional Provider who performed the exam.. Format: Pointer to New Person file (200) "EXAM",i,"EVENT D/T") Optional Date/Time of Exam Format: FileMan Internal Format for date/time "EXAM",i,"COMMENT") Optional Comment Format: Free Text field (1-245 characters) "EXAM",i,"DELETE") Optional This is a flag that denotes deletion of the Exam entry. Format: [ 1 | null ]| SKIN TEST: The "SKIN TEST" node may have multiple entries (i). To delete the entire "SKIN TEST" entry, set the "DELETE" node to 1. SUBSCRIPT DESCRIPTION: "SKIN TEST",i,"TEST") Required Skin Test that was performed Format: Pointer to Skin Test file (9999999.28) "SKIN TEST",i,"READING") Optional Numeric measurement of the surface area tested (in millimeters). Format: Whole number between 0 and 40 inclusive. "SKIN TEST",i,"RESULT") Optional Results of the Skin Test Format: Set of Codes. P::=Positive D::=Doubtful N::=Negative O::=No Take "SKIN TEST",i,"D/T READ") Optional Date/time skin test was read Format: FileMan Internal Format for date/time "SKIN TEST",i,"DIAGNOSIS") Optional The first diagnosis that is associated with the identified skin test and is the primary diagnosis associated with this skin test. Format: Pointer to ICD Diagnosis file (80) "SKIN TEST",i,"DIAGNOSIS 2") Optional The second diagnosis that is associated with the identified skin test. "SKIN TEST",i,"DIAGNOSIS 3") Optional The third diagnosis that is associated with the identified skin test. "SKIN TEST",i,"DIAGNOSIS 4") Optional The fourth diagnosis that is associated with the identified skin test. "SKIN TEST",i,"DIAGNOSIS 5") Optional The fifth diagnosis that is associated with the identified skin test. "SKIN TEST",i,"DIAGNOSIS 6") Optional The sixth diagnosis that is associated with the identified skin test. "SKIN TEST",i,"DIAGNOSIS 7") Optional The seventh diagnosis that is associated with the identified skin test. "SKIN TEST",i,"DIAGNOSIS 8") Optional The eighth diagnosis that is associated with the identified skin test. Format: Pointer to ICD Diagnosis file (80) "SKIN TEST",i,"ENC PROVIDER") Optional Provider who read the skin test. Format: Pointer to New Person file (200) "SKIN TEST",i,"EVENT D/T") Optional Date/Time test was administered. Format: FileMan Internal Format for date/time "SKIN TEST",i,"COMMENT") Optional Comment Format: Free Text field (1-245 characters) "SKIN TEST",i,"DELETE") Optional This is a flag that denotes deletion of the Skin Test entry. Format: [ 1 | null ]| IMMUNIZATION: The "IMMUNIZATION" node may have multiple entries (i). To delete the entire "IMMUNIZATION" entry, set the "DELETE" node to 1. SUBSCRIPT DESCRIPTION: "IMMUNIZATION",i,"IMMUN") Required Immunization that was performed. Format: Pointer to Immunization file (9999999.14) "IMMUNIZATION",i,"SERIES") Optional Series specifies the sequence of the series for the immunization that was administered. Format: Set of Codes. P::=Partially complete C::=Complete B::=Booster 1::=Series1 thru 8::=Series8 "IMMUNIZATION",i,"REACTION") Optional The observed reaction to the immunization. Format: Set of Codes. 0::=None 1::=Fever 2::=Irritability 3::=Local Reaction or Swelling 4::=Vomiting 5::=Rash or Itching 6::=Lethargy 7::=Convulsions 8::=Arthritis or Arthralgias 9::=Anaphylaxis or Collapse 10::=Respiratory Distress 11::=Other "IMMUNIZATION",i,"CONTRAINDICATED") Optional This field may be used to indicate that this immunization should not be administered again. "1" indicates that the immunization should not be given to the patient in the future. Format: [ 1 | 0 | null ] "IMMUNIZATION",i,"DIAGNOSIS") Optional The first diagnosis that is associated with the identified immunization and is the primary diagnosis associated with this immunization. Format: Pointer to ICD Diagnosis file (80) "IMMUNIZATION",i,"DIAGNOSIS 2") Optional The second diagnosis that is associated with the identified immunization. "IMMUNIZATION",i,"DIAGNOSIS 3") Optional The third diagnosis that is associated with the identified immunization. "IMMUNIZATION",i,"DIAGNOSIS 4") Optional The fourth diagnosis that is associated with the identified immunization. "IMMUNIZATION",i,"DIAGNOSIS 5") Optional The fifth diagnosis that is associated with the identified immunization. "IMMUNIZATION",i,"DIAGNOSIS 6") Optional The sixth diagnosis that is associated with the identified immunization. "IMMUNIZATION",i,"DIAGNOSIS 7") Optional The seventh diagnosis that is associated with the identified immunization. "IMMUNIZATION",i,"DIAGNOSIS 8") Optional The eighth diagnosis that is associated with the identified immunization. Format: Pointer to ICD Diagnosis file (80) "IMMUNIZATION",i,"ENC PROVIDER") Optional Provider who performed the immunization. Format: Pointer to New Person file (200) "IMMUNIZATION",i,"EVENT D/T") Optional Date/Time immunization was administered. Format: FileMan Internal Format for date/time "IMMUNIZATION",i,"COMMENT") Optional Comment Format: Free Text (1-245 characters) "IMMUNIZATION",i,"DELETE") Optional This is a flag that denotes deletion of the Immunization entry. Format: [ 1 | null ]| TREATMENT: The "TREATMENT" node may have multiple entries (i). To delete the entire "TREATMENT" entry, set the "DELETE" node to 1. SUBSCRIPT DESCRIPTION: "TREATMENT",i,"TREATMENT") Required Name of Treatment Format: Pointer to Treatment file (9999999.17) "TREATMENT",i,"QTY") Optional Number of times the treatment was performed. Format: Whole number > 0 "TREATMENT",i,"NARRATIVE") *Optional The provider's description of the treatment performed. *If NARRATIVE is not passed for a treatment, the Treatment Name from the Treatment file (9999999.17) will be used as the default. Format: Free text (2-245 characters) "TREATMENT",i,"CATEGORY") Optional A term that denotes a grouping or category for a set of related treatments. Format: Free text (2-245 characters) "TREATMENT",i,"ENC PROVIDER") Optional Provider who performed the treatment. Format: Pointer to New Person file (200) "TREATMENT",i,"EVENT D/T") Optional Date/Time treatment was done. Format: FileMan Internal Format for date/time "TREATMENT",i,"COMMENT") Optional Comment Format: Free Text (1-245 characters) "TREATMENT",i,"DELETE") Optional This is a flag that denotes deletion of the Treatment entry. Format: [ 1 | null ]| EXAMPLE OF DATA PASSED TO $$DATA2PCE^PXAPI Provided below is an example of data passed to $$DATA2PCE^PXAPI where Laboratory is the ancillary package reporting the data. $$DATA2PCE^PXAPI("LRPXAPI",$J,182,"LAB DATA") This is an example where Laboratory passes two laboratory tests (Glucose and CPK) which were resulted on 4/20/96 at 9:30 a.m. This occasion of service is defined as an Ancillary Package Daily Data (X). ^TMP("LRPXAPI",543173595,"ENCOUNTER",1,"CREDIT STOP") = 59 ^TMP("LRPXAPI",543173595,"ENCOUNTER",1,"ENC D/T") = 2960420.093 ^TMP("LRPXAPI",543173595,"ENCOUNTER",1,"HOS LOC") = 59 ^TMP("LRPXAPI",543173595,"ENCOUNTER",1,"PATIENT") = 1030 ^TMP("LRPXAPI",543173595,"ENCOUNTER",1,"SERVICE CATEGORY") = X ^TMP("LRPXAPI",543173595,"PROCEDURE",1,"ENC PROVIDER") = 58 ^TMP("LRPXAPI",543173595,"PROCEDURE",1,"EVENT D/T") = 2960420.093 ^TMP("LRPXAPI",543173595,"PROCEDURE",1,"PROCEDURE") = 82950 ^TMP("LRPXAPI",543173595,"PROCEDURE",1,"QTY") = 1 ^TMP("LRPXAPI",543173595,"PROCEDURE",2,"ENC PROVIDER") = 58 ^TMP("LRPXAPI",543173595,"PROCEDURE",2,"EVENT D/T") = 2960420.093 ^TMP("LRPXAPI",543173595,"PROCEDURE",2,"PROCEDURE") = 82552 ^TMP("LRPXAPI",543173595,"PROCEDURE",2,"QTY") = 1 ^TMP("LRPXAPI",543173595,"PROVIDER",1,"NAME") = 58 ^TMP("LRPXAPI",543173595,"PROVIDER",1,"PRIMARY") = 1 ^TMP("LRPXAPI",543173595,"PROCEDURE",1,"PROCEDURE") = ^TMP("LRPXAPI",543173595,"PROCEDURE",1,"MODIFIERS",57) = "" ^TMP("LRPXAPI",543173595,"PROCEDURE",1,"QUANTITY") = 1 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29239100 COMPONENT/ENTRY POINT: DATA2PCE SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: EVENT CAPTURE SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: PROSTHETICS SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY SUBSCRIBING PACKAGE: QUASAR SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: JSHARVEY 20061128/Added MH as subscriber as per Fain. SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT SUBSCRIBING DETAILS: ADDED 10/10/2008 SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING DETAILS: ADDED 8/28/09 DATE/TIME EDITED: DEC 01, 2006@17:00 ACTION: CONTENT CORRECTED AT THE REQUEST OF: HARVEY,JULIE DATE/TIME EDITED: DEC 04, 2006@16:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HSU,YUILI WITH CONCURRENCE OF: FAIN,ZACH DATE/TIME EDITED: OCT 10, 2008@14:56 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: ELLIS,DONNA DATE/TIME EDITED: AUG 28, 2009@10:52 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SILVERMAN,ROBERT WITH CONCURRENCE OF: FAIN,ZACHARY NUMBER: 1890 IA #: 1890 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAPI NAME: DBIA1889-B ORIGINAL NUMBER: 1889 ID: PXAPI GENERAL DESCRIPTION: $$DELVFILE^PXAPI(WHICH,VISIT,PKG,SOURCE,ASK,ECHO,USER) This function may be used to delete data from the Visit file (9000010) and V files, including V CPT (9000010.18), V EXAM (9000010.13), V HEALTH FACTORS (9000010.11), V PATIENT ED (9000010.16), V POV (9000010.07), V PROVIDER (9000010.06), V SKIN TEST (9000010.12) and V TREATMENT (9000010.15). Parameter Description: 1. WHICH: (required) An ^ delimited string where two or three characters separated by an ^ designate the V file from which data should be deleted, e.g., "PRV^POV^CPT^HF". "ALL" may be used to delete data from all V files. VISIT is the string which will delete the administrative data and STOP is the string which will delete the additional stop codes. An example of a function call which will delete data typically deleted through Delete Check Out is: $$DELVFILE^PXAPI("ALL",VISIT,,,1,1) Possible individual strings which may be included in WHICH include: ALL To delete all items CPT To delete procedures HF To delete health factors IMM To delete immunizations PEP To delete patient education POV To delete problem of visit (diagnoses) PRV To delete provider SK To delete skin tests STOP To delete additional stop codes. The primary clinic stop will not be deleted. TRT To delete treatments VISIT To delete Service Connected, Classification question data, check out date. XAM To delete examinations 2. VISIT: (required) A number which is a pointer to the VISIT file (9000010). This is the visit for which related data will be deleted. 3. PKG: (optional) The internal entry number of the package in the Package file (9.4) or the namespace for the package. If passed, only items created by this package will be deleted. 4. SOURCE: (optional) A string denoting the source of the data. This is an entry in the Data Source file (839.7). If passed, only items created by this source will be deleted. 5. ASK: (optional) If ASK is passed and it does not equal 0 or "", then PCE will prompt the user to verify that they want to delete the data before proceeding with the deletions. PCE recommends setting ASK to 1 to indicate that the user should be asked to confirm that the data should be deleted. 6. ECHO: (optional) If ECHO is passed and it does not equal 0 or "", then PCE will display to the user what is being deleted. PCE recommends setting ECHO to 1 to indicate that the data deletions should be displayed to the user, e.g. Deleting Procedures.... Deleting Providers.... Deleting Diagnoses.... The message will be displayed only if data has been deleted. 7. USER: (optional) Set USER to the user's DUZ to restrict deletion of data to those entries created by the user. If USER is not passed, is equal to 0 or "", PCE will not apply deletion restriction based on the user. Returned Value: 1 If no errors occurred and deletion processed completely. 0 If errors occurred but deletion processed completely as possible. -1 User indicated that the data should not be deleted, or User up-arrowed out, or errors occurred. In any case, nothing was deleted. -2 If unable to identify a valid VISIT. -3 If API was called incorrectly. -4 If dependent entry count is still greater than zero. STATUS: Active DURATION: Next Version MAIL MESSAGE: 23166314 GOOD ONLY FOR VERSION: 1.0 COMPONENT/ENTRY POINT: DELVFILE SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: EVENT CAPTURE SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: PROSTHETICS SUBSCRIBING PACKAGE: QUASAR SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT SUBSCRIBING DETAILS: ADDED 10/10/2008 DATE/TIME EDITED: OCT 10, 2008@14:56 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: ELLIS,DONNA NUMBER: 1891 IA #: 1891 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAPI NAME: DBIA1889-C ORIGINAL NUMBER: 1889 ID: PXAPI GENERAL DESCRIPTION: $$INTV^PXAPI(WHAT,PKG,SOURCE,.VISIT,.HL,.DFN,APPT,LIMITDT,ALLHLOC) This API should be used by subscribing packages to prompt for Visit and related V-file data. The parameters passed by the subscribing packages determine which prompts will be displayed. If VISIT, HL or DFN are passed by reference (.), a value will be returned for those variables. Parameter Description: 1. WHAT: Required parameter that defines the series of prompts that will be displayed. ADDEDIT When not an appointment. INTV Includes all prompts for the checkout interview: 1. Patient (if not defined) 2. Hospital Location (if not defined) 3. Appointment/Eligibility (Call to Scheduling API if the encounter is not associated with an appointment and is a new encounter.) 4. Check Out Date/Time 5. Service Connected/Classification Questions Service Connected Agent Orange Exposure Ionizing Radiation Exposure Environmental Contaminants Exposure Military Sexual Trauma Head and/or Neck Cancer Combat Vet Project 112/SHAD Exposure 6. Provider (multiple) Provider Primary/Secondary Designation 7. Procedures (multiple) CPT code Modifiers (multiple) Quantity 8. Diagnosis (multiple) ICD9 code Primary/Secondary Designation 9. Stop Code (multiple) Discontinued after 10/1/96 Stop code PRV Includes all prompts for provider information (multiple): 1. Provider 2. Primary/Secondary Designation POV Includes all prompts for diagnosis information (multiple): 1. ICD9 code 2. Primary/Secondary Designation CPT Includes prompts for procedure information and allows association of data with a provider (multiple): 1. Provider 2. Primary/Secondary Provider Designation 3. CPT code 4. CPT Modifiers (multiple) 5. Quantity SCC Includes prompts for service connected conditions and classification questions: 1. Service Connected 2. Combat Vet 3. Agent Orange Exposure 4. Ionizing Radiation Exposure 5. Environmental Contaminants Exposure 6. Project 112/SHAD Exposure 7. Military Sexual Trauma 8. Head and/or Neck Cancer CODT Includes prompt for check-out date/time: 1. Date/time Checked Out ADQ Includes all administrative prompts related to the interview: 1. Patient (if not defined) 3. Appointment/Eligibility (API called if encounter is not associated with an appointment) 4. Check Out Date/Time 5. Service Connected 6. Combat Vet 7. Agent Orange Exposure 8. Ionizing Radiation Exposure 9. Environmental Contaminants Exposure 10. Project 112/SHAD Exposure 11. Military Sexual Trauma 12. Head and/or Neck Cancer STP Includes prompt for a stop code (multiple): 1. Stop Code (only for encounters before 10/1/96) 2. PKG: Required parameter that is the designated namespace for the package as defined in the Package file or is a pointer to the Package file (9.4). 3. SOURCE: Required parameter that is used for auditing purposes and defines the data collection source. This parameter could be the calling routine or a description of the caller, e.g., PIMS CHECKOUT, PXCE DATA ENTRY, PANDAS, TELEFORM. It will be added to the PCE Data Source file (839.7). 4. VISIT: Required parameter except when "INTV" and "ADQ" are called. This parameter defines the encounter and is a pointer to the Visit file (9000010). 5. HL: Optional parameter (passed if known) that defines the hospital location for the encounter and points to the Hospital Location file (44). If the subscribing package knows the hospital location, it should be passed to avoid unnecessary prompting. 6. DFN: Required parameter if there is no known visit (VISIT) and there is an appointment (APPT); otherwise, it is an optional parameter (passed if known) that defines the patient and points to the Patient/IHS file (9000001). If the subscribing package knows the patient, it should be passed to avoid unnecessary prompting. 7. APPT: Optional parameter that points to the Appointment subfile (2.98) of the Patient file (2). This parameter defines the appointment date/time. 8. LIMITDT: Optional parameter that restricts creation of new visits to the date passed or after the date passed. The format of the parameter is internal fileman date. 9. ALLHLOC: Optional parameter if is not passed, 0, or null then only clinics can be entered for hospital locations otherwise any non disposition hospital location can be entered. Returned Variables: If VISIT, HL or DFN are passed by reference (.), a value will be returned for those variables. 1 When the call to the API is successful; no errors were encountered. 0 When user up-arrows out. Minimally, a visit exists. Other processing may have occurred. -1 When user up-arrows out or errors out and nothing has been processed. -2 When no visit was created and no subsequent processing occurred. -3 When the API was incorrectly called. STATUS: Active DURATION: Next Version GOOD ONLY FOR VERSION: 1.0 COMPONENT/ENTRY POINT: INTV SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 1892 IA #: 1892 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAPI NAME: DBIA1889-D ORIGINAL NUMBER: 1889 ID: PXAPI GENERAL DESCRIPTION: $$ENCEDIT^PXAPI(WHAT,PKG,SOURCE,DFN,BEGDT,ENDT,HLOC,SCREEN,APPT,PRMPT) This is an interactive API that may be called to display a list of encounters for selection. It allows adding a new encounter, or selecting an encounter to edit or delete. If the user indicates that an encounter should be added, an entry will be created in the Visit file (9000010), and the user will be prompted based on the WHAT parameter. If an encounter is selected to edit, the user will be prompted based on the WHAT parameter. If an encounter is selected for deletion, all data associated with the encounter will be deleted, and the entry in the Visit file will be assessed for deletion and deleted if possible. Parameter Description: 1. WHAT: (required) This parameter is string text that identifies the set of prompts. INTV Includes all prompts for the checkout interview: 1. Patient (if not defined) 2. Hospital Location (if not defined) Appointment/Eligibility (Call to Scheduling API if the encounter is not associated with an appointment and is a new encounter.) 3. Check Out Date/Time 4. Service Connected/Classification Questions Service Connected Agent Orange Exposure Ionizing Radiation Exposure Environmental Contaminants Exposure Military Sexual Trauma Head and/or Neck Cancer Combat Vet Project 112/SHAD Exposure 5. Provider (multiple) Provider Primary/Secondary Designation 6. Procedures (multiple) CPT code Modifiers (multiple) Quantity 7. Diagnosis (multiple) ICD9 code Primary/Secondary Designation 8. Stop Code (multiple) Discontinued after 10/1/96 Stop code ADQ Includes all administrative prompts related to the interview: 1. Patient (if not defined) 2. Hospital Location (if not defined) 3. Appointment/Eligibility (API called if encounter is not associated with an appointment) 4. Check Out Date/Time 5. Service Connected 6. Combat Vet 7. Agent Orange Exposure 8. Ionizing Radiation Exposure 9. Environmental Contaminants Exposure 10. Project 112/SHAD Exposure 11. Military Sexual Trauma 12. Head and/or Neck Cancer 2. PKG: (required) This parameter is the assigned package Name space as designated in the Package file (9.4) or is a pointer to the Package file (9.4). 3. SOURCE: (required) This parameter is used for auditing purposes and defines the data collection source. This parameter could be the calling routine or a description of the caller, e.g., PIMS CHECKOUT, PXCE DATA ENTRY, PANDAS, TELEFORM. It will be added to the PCE Data Source file (839.7). 4. DFN: (required) This parameter represents the patient and is the internal entry number of the Patient's entry in the Patient/IHS file (9000001) which is dinumed to the Patient file (2). 5. BEGDT: (optional) This is the beginning date, in an INTERNAL FORMAT, of the date range. If no date range is passed, all entries in the Visit file (9000010) for the identified patient will be returned. 6. ENDT: (optional) This is the ending date, in an INTERNAL FORMAT, of the date range. If no date range is passed, all entries in the Visit file (9000010) for the identified patient will be returned. 7. HLOC: (optional) This is the Hospital Location. It is a pointer to the Hospital Location file (44). This restricts display of encounters to those associated with this hospital location. If HLOC is not passed, all encounters for the identified patient, irrespective of the hospital location, will be returned. 8. SCREEN: (optional) This is a screen based on the Primary field (15003) and Service Category field (.07) of the Visit file (9000010). It is a set of codes that represents an encounter type, e.g., primary, occasion of service, stop code. More than one code may be used, e.g., PO. If SCREEN is not passed, all encounters, except those that represent historical encounters, will be included in the list. If the screen includes E, only historical encounters will be displayed. If the screen does not include E, only non-historical encounters will be displayed. A Occasions of service that are passed to PCE by ancillary packages using DATA2PCE^PXAPI. P Primary visits are encounters created for appointments and standalone's either through manual data entry or via DATA2PCE^PXAPI. O Occasions of Service are encounters that are created when data for an ancillary package such as Radiology or Laboratory is manually entered through Scheduling or PCE. Assignment of this code is determined based on a managed set of stop codes provided by ancillary packages. S Stop Codes are child encounters that are created to store additional stop codes for a parent encounter. This will be discontinued after 10/1/96. E Historical Encounters are encounters that document clinical activities. They are not associated with an appointment and are not used for billing or workload purposes. Use "XE" to display all historical encounters. X All encounters, excluding historical encounters. "X" is the default when no SCREEN is defined. 9. APPT: (optional) This parameter determines the contents of the encounter list--whether the encounter include appointments and sandalones, just appointments or just standalones. If APPT is not passed, no appointment/encounter relationship will be assessed. 1 Display only encounters related to an appointment. 0 Don't screen on encounter/appointment relationship. -1 Display only encounters not related to an appointment (standalones). 10. PRMPT:(optional) This determines the prompt used by the API. If PRMPT is not passed or null, only selection of an item from the list will be enabled. A Includes ADD in the prompt. D Includes DELETE in the prompt. Returned Value: >0 Internal entry number of the selected encounter, IEN in the Visit file (9000010). D^Visit IEN User selected an encounter to DELETE. -1 No visit selected, user up-arrowed out, nothing done. -2^Text Error encountered. Text string documents error. -3^Text Deletion Errors. If deletion occurred, it was incomplete. ====================================================================== $$LOPENCED^PXAPI(WHAT,PKG,SOURCE,DFN,BEGDT,ENDT,HLOC,SCREEN,APPT,PRMPT) This is an interactive API that may be called to display a list of encounters for selection. It allows adding a new encounter, or selecting an encounter to edit or delete. If the user indicates that an encounter should be added, an entry will be created in the Visit file (9000010), and the user will be prompted based on the WHAT parameter. If an encounter is selected to edit, the user will be prompted based on the WHAT parameter. If an encounter is selected for deletion, all data associated with the encounter will be deleted, and the entry in the Visit file will be assessed for deletion and deleted if possible. This API should be used to allow continuous looping through encounter edit until the user exits the functionality. This API loops calling ENCEDIT^PXAPI to collect encounter data repeatedly. Parameter Description: 1. WHAT: (required) This parameter is string text that identifies the set of prompts. INTV Includes all prompts for the checkout interview: 1. Patient (if not defined) 2. Hospital Location (if not defined) Appointment/Eligibility (Call to Scheduling API if the encounter is not associated with an appointment and is a new encounter.) 3. Check Out Date/Time 4. Service Connected/Classification Questions Service Connected Agent Orange Exposure Ionizing Radiation Exposure Environmental Contaminants Exposure Military Sexual Trauma Head and/or Neck Cancer Combat Vet Project 112/SHAD Exposure 5. Provider (multiple) Provider Primary/Secondary Designation 6. Procedures (multiple) CPT code Modifiers (multiple) Quantity 7. Diagnosis (multiple) ICD9 code Primary/Secondary Designation 8. Stop Code (multiple) Discontinued after 10/1/96 Stop code ADQ Includes all administrative prompts related to the interview: 1. Patient (if not defined) 2. Hospital Location (if not defined) 3. Appointment/Eligibility (API called if encounter is not associated with an appointment) 4. Check Out Date/Time 5. Service Connected 6. Combat Vet 7. Agent Orange Exposure 8. Ionizing Radiation Exposure 9. Environmental Contaminants Exposure 10. Project 112/SHAD Exposure 11. Military Sexual Trauma 12. Head and/or Neck Cancer 2. PKG: (required) This parameter is the assigned package Namesapce as designated in the Package file (9.4) or is a pointer to the Package file (9.4). 3. SOURCE: (required) This parameter is used for auditing purposes and defines the data collection source. This parameter could be the calling routine or a description of the caller, e.g., PIMS CHECKOUT, PXCE DATA ENTRY, PANDAS, TELEFORM. It will be added to the PCE Data Source file (839.7). 4. DFN: (required) This parameter represents the patient and is the internal entry number of the Patient's entry in the Patient/IHS file (9000001) which is dinumed to the Patient file (2). 5. BEGDT: (optional) This is the beginning date, in an INTERNAL FORMAT, of the date range. If no date range is passed, all entries in the Visit file (9000010) for the identified patient will be returned. 6. ENDT: (optional) This is the ending date, in an INTERNAL FORMAT, of the date range. If no date range is passed, all entries in the Visit file (9000010) for the identified patient will be returned. 7. HLOC: (optional) This is the Hospital Location. It is a pointer to the Hospital Location file (44). This restricts display of encounters to those associated with this hospital location. If HLOC is not passed, all encounters for the identified patient, irrespective of the hospital location, will be returned. 8. SCREEN: (optional) This is a screen based on the Primary field (15003) and Service Category field (.07) of the Visit file (9000010). It is a set of codes that represents an encounter type, e.g., primary, occasion of service, stop code. More than one code may be used, e.g., PO. If SCREEN is not passed, all encounters, except those that represent historical encounters, will be included in the list. If the screen includes E, only historical encounters will be displayed. If the screen does not include E, only non-historical encounters will be displayed. A Occasions of service that are passed to PCE by ancillary packages using DATA2PCE^PXAPI. P Primary visits are encounters created for appointments and standalone's either through manual data entry or via DATA2PCE^PXAPI. O Occasions of Service are encounters that are created when data for an ancillary package such as Radiology or Laboratory is manually entered through Scheduling or PCE. Assignment of this code is determined based on a managed set of stop codes provided by ancillary packages. S Stop Codes are child encounters that are created to store additional stop codes for a parent encounter. This will be discontinued after 10/1/96. E Historical Encounters are encounters that document clinical activities. They are are not associated with an appointment and are not used for billing or workload purposes. Use "XE" to display all historical encounters. X All encounters, excluding historical encounters. "X" is the default when no SCREEN is defined. 9. APPT: (optional) This parameter determines the contents of the encounter list--whether the encounter include appointments and sandalones, just appointments or just standalones. If APPT is not passed, no appointment/encounter relationship will be assessed. 1 Display only encounters related to an appointment. 0 Don't screen on encounter/appointment relationship. -1 Display only encounters not related to an appointment (standalones). 10. PRMPT: (optional) This determines the prompt used by the API. If PRMPT is not passed or null, only selection of an item from the list will be enabled. A Includes ADD in the prompt. D Includes DELETE in the prompt. Returned Value: >0 Internal entry number of the selected encounter, IEN in the Visit file (9000010). D^Visit IEN User selected an encounter to DELETE. -1 No visit selected, user up-arrowed out, nothing done. -2^Text Error encountered. Text string documents error. -3^Text Deletion Errors. If deletion occurred, it was incomplete. STATUS: Active DURATION: Next Version GOOD ONLY FOR VERSION: 1.0 COMPONENT/ENTRY POINT: ENCEDIT COMPONENT/ENTRY POINT: LOPENCED SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 1893 IA #: 1893 DATE CREATED: MAR 08, 2004 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAPI NAME: DBIA1889-E ORIGINAL NUMBER: 1889 ID: PXAPI GENERAL DESCRIPTION: $$VISITLST^PXAPI(DFN,BEGINDT,ENDDT,HLOC,SCREEN,APPT,PRMPT) Use this API to display a list of encounters. This is an interactive API that allows the user to enter "A" to ADD a new encounter or to select an encounter to edit or delete. If no date range is passed, all entries in the Visit file (9000010 ) for the identified patient will be included in the list. If the HLOC is not passed, all entries in the Visit file (9000010) for the identified patient will be included in the list. If SCREEN is not passed, all encounters, except those that represent historical encounters, will be included in the list. If APPT is not passed, no appointment/encounter relationship will be assessed. If PRMPT is not passed or is null, only selection of an item from the list will be enabled. Parameter Description: 1. DFN: (required) This number represents the patient and is the internal entry number of the Patient's entry in the Patient/IHS file (9000001) which is dinumed to the Patient file (2). 2. BEGINDT: (optional) This is the beginning date, in an INTERNAL FORMAT, of the date range. If no date range is passed, all entries in the Visit file (9000010 ) for the identified patient will be included in the list. 3. ENDDT: (optional) This is the ending date, in an INTERNAL FORMAT, of the date range. If no date range is passed, all entries in the Visit file (9000010 ) for the identified patient will be included in the list. 4. HLOC: (optional) This is the Hospital Location. It is a pointer to the Hospital Location file (44). This restricts display of encounters to those associated with this hospital location. If the HLOC is not passed, all entries in the Visit file (9000010) for the identified patient will be included in the list. 5. SCREEN: (optional) This is a screen based on the Primary field (15003) and Service Category field (.07) of the Visit file (9000010). It is a set of codes that represents an encounter type, e.g., primary, occasion of service, stop code. More than one code may be used, e.g., PO. If SCREEN is not passed, all encounters, except those that represent historical encounters, will be included in the list. If the screen includes E, only historical encounters will be displayed. If the screen does not include E, only non-historical encounters will be displayed. A Occasions of service that are passed to PCE by ancillary packages using DATA2PCE^PXAPI. P Primary visits are encounters created for appointments and standalone's either through manual data entry or via DATA2PCE^PXAPI. O Occasions of Service are encounters that are created when data for an ancillary package such as Radiology or Laboratory is manually entered through Scheduling or PCE. Assignment of this code is determined based on a managed set of stop codes provided by ancillary packages. S Stop Codes are child encounters that are created to store additional stop codes for a parent encounter. This will be discontinued after 10/1/96. E Historical Encounters are encounters that document clinical activities. They are not associated with an appointment and are not used for billing or workload purposes. Use "XE" to display all historical encounters. This screen must be used in combination with one of the other codes. X All encounters, excluding historical encounters. "X" is the default when no SCREEN is defined. 6. APPT: (optional) This determines the contents of the encounter list--whether the encounters include appointments and standalones, just appointments or just standalones. If APPT is not passed, no appointment/encounter relationship will be assessed. 1 Display only encounters related to an appointment. 0 Don't screen on encounter/appointment relationship. -1 Display only encounters not related to an appointment (standalones). 7. PRMPT: (optional) This determines the prompt used by the API. If PRMPT is not passed or null, only selection of an item from the list will be enabled. A Includes ADD in the prompt. D Includes DELETE in the prompt. Returned Value: >0 Internal entry number of the selected encounter, IEN in the Visit file (9000010) A User indicated to ADD an encounter. D^IEN User selected an encounter to DELETE. -1 No visit selected -2^Text Error encountered. Text documents error. STATUS: Active DURATION: Next Version MAIL MESSAGE: 38163261 GOOD ONLY FOR VERSION: 1.0 COMPONENT/ENTRY POINT: VISITLST SUBSCRIBING PACKAGE: QUASAR NUMBER: 1894 IA #: 1894 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAPI NAME: DBIA1889-F ORIGINAL NUMBER: 1889 ID: PXAPI GENERAL DESCRIPTION: ENCEVENT^PXKENC(VISITIEN,DONTKILL) This API was developed to extract all encounter data for a single encounter. The data represents elements that are stored in the Visit file (9000010) and other PCE files. Parameter Description: 1. VISITIEN (required) This is a pointer to the Visit file (9000010). 2. DONTKILL (optional) This determines whether or not the ^TMP array will be killed. Enter 0 or "" (null) to kill the array, and 1 to retain the array. Returned: The data is stored in a ^TMP global array with subscripts denoting the category of returned data. The data returned in the ^TMP global represents data from one encounter. The structure of the returned ^TMP global is: ^TMP("PXKENC",$J,VISIT,V FILE STRING,V FILE RECORD,DD SUBSCRIPT) =DATA Where: Global Root Temporary global file root: ^TMP Subscript 1 String notation representing Package: "PXKENC" Subscript 2 Job Number: $J Subscript 3 Internal Entry Number of the Visit (IEN). Subscript 4 String representing the Visit or V file data category: "CPT" = V CPT (procedure) #9000010.18 "HF" = V Health Factors #9000010.23 "IMM" = V Immunization #9000010.11 "PED" = V Patient Ed #9000010.16 "POV" = V POV (diagnosis) #9000010.07 "PRV" = V Provider #9000010.06 "SK" = V Skin Test #9000010.12 "TRT" = V Treatment #9000010.15 "VST" = Visit file #9000010 "XAM" = V Exam #9000010.13 "CSTP" = Visit file #9000010 This subscript contains child visits used to store additional Stop Codes. Subscript 5 Internal entry number of the entry in the file represented in subscript #4 Subscript 6 Subscript or DD node on which the data is stored. Every DD node is published whether or not there is any data for that node. e.g. 0, 12, and 811 Data: The DATA that exists to the right of the global node is a reflection of data as it appears in the global node of the IEN of the file (noted in subscript #5) and the NODE of that IEN (described in subscript #6). Data Capture of Example output: Included below is a capture of the ^TMP("PXKENC" global. ^TMP("PXKENC",549479964,78,"CPT",135,0) = 34510^1030^78^176^^^^^^^^^^^^1 ^TMP("PXKENC",549479964,78,"CPT",135,1,0) = ^^1^1 ^TMP("PXKENC",549479964,78,"CPT",135,1,1,0) = 16 ^TMP("PXKENC",549479964,78,"CPT",135,12) = ^^^108 ^TMP("PXKENC",549479964,78,"CPT",135,802) = ^TMP("PXKENC",549479964,78,"CPT",135,811) = ^TMP("PXKENC",549479964,78,"POV",96,0) = 9054^1030^78^177^^^^^^^^S ^TMP("PXKENC",549479964,78,"POV",96,12) = ^^^108 ^TMP("PXKENC",549479964,78,"POV",96,800) = 0 ^TMP("PXKENC",549479964,78,"POV",96,802) = 168 ^TMP("PXKENC",549479964,78,"POV",96,811) = ^TMP("PXKENC",549479964,78,"POV",104,0) = 2569^1030^78^178^^^^^^^^P ^TMP("PXKENC",549479964,78,"POV",104,12) = ^TMP("PXKENC",549479964,78,"POV",104,800) = ^TMP("PXKENC",549479964,78,"POV",104,802) = ^TMP("PXKENC",549479964,78,"POV",104,811) = this is a comment ^TMP("PXKENC",549479964,78,"PRV",94,0) = 58^1030^78^S^A ^TMP("PXKENC",549479964,78,"PRV",94,12) = ^TMP("PXKENC",549479964,78,"PRV",94,811) = ^TMP("PXKENC",549479964,78,"PRV",114,0) = 108^1030^78^S ^TMP("PXKENC",549479964,78,"PRV",114,12) = ^TMP("PXKENC",549479964,78,"PRV",114,811) = ^TMP("PXKENC",549479964,78,"SK",3,0) = 1^1030^78^D^3^2960328.182336 ^TMP("PXKENC",549479964,78,"SK",3,12) = ^58^^108 ^TMP("PXKENC",549479964,78,"SK",3,811) = ^TMP("PXKENC",549479964,78,"TRT",2,0) = 162^1030^78^3^^175 ^TMP("PXKENC",549479964,78,"TRT",2,12) = ^108^^58 ^TMP("PXKENC",549479964,78,"TRT",2,802) = ^TMP("PXKENC",549479964,78,"TRT",2,811) = ^TMP("PXKENC",549479964,78,"VST",78,0) = 2960321.1^2960326^V^^1030^660 ^A^143^23^^^^2960326^^^^^^^ ^11^39^31^13560 ^TMP("PXKENC",549479964,78,"VST",78,11) = ^TMP("PXKENC",549479964,78,"VST",78,21) = ^TMP("PXKENC",549479964,78,"VST",78,150) = 1^^P ^TMP("PXKENC",549479964,78,"VST",78,800) = 0 ^TMP("PXKENC",549479964,78,"VST",78,811) = ==================================================================== $$GETENC^PXAPI(DFN,ENCDT,HLOC) This API was developed to extract all encounter data for all encounters that match the passed parameters. The data represents elements that are stored in the Visit file (9000010) and other PCE files. Parameter Description: 1. DFN: (required) Pointer to IHS/PATIENT file (9000001) 2. ENCDT: (required) Date/Time of encounter in Fileman format 3. HLOC: (required) Pointer to Hospital Location file (44) Returned Value: -2 If Called incorrectly -1 If no encounter is found >0 Visit file ien(s) separated by ^ The data is stored in a ^TMP global array with subscripts denoting the category of returned data. The data returned in the ^TMP global represents data from one encounter. The structure of the returned ^TMP global is: ^TMP("PXKENC",$J,VISIT,V FILE STRING,V FILE RECORD,DD SUBSCRIPT) =DATA Where: Global Root Temporary global file root: ^TMP Subscript 1 String notation representing Package: "PXKENC" Subscript 2 Job Number: $J Subscript 3 Internal Entry Number of the Visit (IEN). Subscript 4 String representing the Visit or V file data category: "CPT" = V CPT (procedure) #9000010.18 "HF" = V Health Factors #9000010.23 "IMM" = V Immunization #9000010.11 "PED" = V Patient Ed #9000010.16 "POV" = V POV (diagnosis) #9000010.07 "PRV" = V Provider #9000010.06 "SK" = V Skin Test #9000010.12 "TRT" = V Treatment #9000010.15 "VST" = Visit file #9000010 "XAM" = V Exam #9000010.13 "CSTP" = Visit file #9000010 This subscript contains child visits used to store additional Stop Codes. Subscript 5 Internal entry number of the entry in the file represented in subscript #4 Subscript 6 Subscript or DD node on which the data is stored. Every DD node is published whether or not there is any data for that node. e.g. 0, 12, and 811 Data: The DATA that exists to the right of the global node is a reflection of data as it appears in the global node of the IEN of the file (noted in subscript #5) and the NODE of that IEN (described in subscript #6). Data Capture of Example output: Included below is a capture of ^TMP("PXKENC". ^TMP("PXKENC",549479964,78,"CPT",135,0) = 34510^1030^78^176^^^^^^^^^^^^1 ^TMP("PXKENC",549479964,78,"CPT",135,1,0) = ^^1^1 ^TMP("PXKENC",549479964,78,"CPT",135,1,1,0) = 16 ^TMP("PXKENC",549479964,78,"CPT",135,12) = ^^^108 ^TMP("PXKENC",549479964,78,"CPT",135,802) = ^TMP("PXKENC",549479964,78,"CPT",135,811) = ^TMP("PXKENC",549479964,78,"POV",96,0) = 9054^1030^78^177^^^^^^^^S ^TMP("PXKENC",549479964,78,"POV",96,12) = ^^^108 ^TMP("PXKENC",549479964,78,"POV",96,800) = 0 ^TMP("PXKENC",549479964,78,"POV",96,802) = 168 ^TMP("PXKENC",549479964,78,"POV",96,811) = ^TMP("PXKENC",549479964,78,"POV",104,0) = 2569^1030^78^178^^^^^^^^P ^TMP("PXKENC",549479964,78,"POV",104,12) = ^TMP("PXKENC",549479964,78,"POV",104,800) = ^TMP("PXKENC",549479964,78,"POV",104,802) = ^TMP("PXKENC",549479964,78,"POV",104,811) = this is a comment ^TMP("PXKENC",549479964,78,"PRV",94,0) = 58^1030^78^S^A ^TMP("PXKENC",549479964,78,"PRV",94,12) = ^TMP("PXKENC",549479964,78,"PRV",94,811) = ^TMP("PXKENC",549479964,78,"PRV",114,0) = 108^1030^78^S ^TMP("PXKENC",549479964,78,"PRV",114,12) = ^TMP("PXKENC",549479964,78,"PRV",114,811) = ^TMP("PXKENC",549479964,78,"SK",3,0) = 1^1030^78^D^3^2960328.182336 ^TMP("PXKENC",549479964,78,"SK",3,12) = ^58^^108 ^TMP("PXKENC",549479964,78,"SK",3,811) = ^TMP("PXKENC",549479964,78,"TRT",2,0) = 162^1030^78^3^^175 ^TMP("PXKENC",549479964,78,"TRT",2,12) = ^108^^58 ^TMP("PXKENC",549479964,78,"TRT",2,802) = ^TMP("PXKENC",549479964,78,"TRT",2,811) = ^TMP("PXKENC",549479964,78,"VST",78,0) = 2960321.1^2960326^V^^1030^660 ^A^143^23^^^^2960326^^^^^^^ ^11^39^31^13560 ^TMP("PXKENC",549479964,78,"VST",78,11) = ^TMP("PXKENC",549479964,78,"VST",78,21) = ^TMP("PXKENC",549479964,78,"VST",78,150) = 1^^P ^TMP("PXKENC",549479964,78,"VST",78,800) = 0 ^TMP("PXKENC",549479964,78,"VST",78,811) = The ^TMP("PXKENC",$J) global may be killed before and/or after the call. STATUS: Active DURATION: Next Version MAIL MESSAGE: 23166351 GOOD ONLY FOR VERSION: 1.0 COMPONENT/ENTRY POINT: GETENC COMPONENT/ENTRY POINT: ENCEVENT SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY SUBSCRIBING PACKAGE: INTEGRATED BILLING SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: QUASAR SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT SUBSCRIBING DETAILS: ADDED 10/10/2008 SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: Effective with VPR*1*0. SUBSCRIBING PACKAGE: MYHEALTHEVET SUBSCRIBING DETAILS: Added 10/9/14. SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING DETAILS: Added 10/10/14 as subscriber. Effective with new project Bar Code Enhancement - Transfusion Verification, namespace MJCF. The new package build is MJCF*1.0.KID. SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 08/02/13 DT: Added VPR as subscriber, effective with VPR*1*0. This API received concurrence by both Donna Ellis and Robert Yorty. 10/30/13 DT: Added Kumar as editor for MyHealthevet use. 10/10/13 DT: Added MyHealtheVet as subscriber, effective with patch 11 and Added BAR CODE EXPANSION as subscriber, effective with new package MJCF*1.0. Both Kumar and Vaughn understand they are responsible for technical accuracy of using this API. 3/2/15-MC: Added VPS as a subscriber at the request of Carolyn Wheless and approval of Pat Redington for VPS*1*15, scheduled for release in March 2015. DATE ACTIVATED: OCT 10, 2014 DATE/TIME EDITED: OCT 10, 2008@14:57 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: ELLIS,DONNA DATE/TIME EDITED: SEP 16, 2010@10:52 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE DATE/TIME EDITED: AUG 02, 2013@13:26 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: ELLIS,DONNA DATE/TIME EDITED: OCT 30, 2013@11:39 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: MARRI,NAGARAJA DATE/TIME EDITED: OCT 10, 2014@09:07 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MARRI,NAJARAJA WITH CONCURRENCE OF: ICR,TEAM DATE/TIME EDITED: OCT 10, 2014@09:15 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SMITH,VAUGHN WITH CONCURRENCE OF: ICR,TEAM DATE/TIME EDITED: MAR 02, 2015@14:21 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: REDINGTON,PAT NUMBER: 1895 IA #: 1895 DATE CREATED: MAR 02, 2004 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAPI NAME: DBIA1889-G ORIGINAL NUMBER: 1889 ID: PXAPI GENERAL DESCRIPTION: $$VST2APPT^PXAPI(VISIT) This function tells if Visit is related to an appointment. Or if it is a standalone visit (i.e. is not related to an appointment). Parameter: VISIT ien to a Visit file (#9000010) entry Returned value: 1 if the visit is related to an appointment. 0 if the visit is NOT related to an appointment. -1 if the visit is not a valued pointer. ======================================================================= $$APPT2VST^PXAPI(PATIENT,DATETIME,HOSPLOC) The function returns the visit that is related to an appointment. Must be able to resolve the Patient, Date/Time and Clinic to an appointment entry in the Patient file. Parameters: PATIENT DFN of a patient in the Patient file (#2) and the Patient/IHS file (#9000001) DATETIME The date and time of the appointment HOSPLOC The Clinic of the appointment, pointer to Hospital Location file (#44) Returned value: >0 ien of visit that relates to the apppointment 0 if there is no appointment or the appointment does not point to a visit. STATUS: Active DURATION: Next Version MAIL MESSAGE: 38119998 GOOD ONLY FOR VERSION: 1.0 COMPONENT/ENTRY POINT: APPT2VST COMPONENT/ENTRY POINT: VST2APPT SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 3/2/15-MC:Added VPS as a subscriber at the request of Carolyn Wheless and approval of Pat Redington for VPS*1*15,After Visit Summary (AVS).Planned release date in March 2015. DATE/TIME EDITED: SEP 16, 2010@10:53 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE DATE/TIME EDITED: MAR 02, 2015@14:26 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: REDINGTON,PATRICK NUMBER: 1896 IA #: 1896 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAPI NAME: DBIA1889-H ORIGINAL NUMBER: 1889 ID: PXAPI GENERAL DESCRIPTION: $$SOURCE^PXAPI(NAME) This API returns a pointer to the PCE Data Source file (#839.7) for the text name of the Data Source. If the Data Source is not in the file it will be added and the pointer to the new entry returned. Parameter Description: NAME Text name for the source of data to PCE. Returned Value: -1 Error in processing. >0 IEN of the NAME in the PCE Data Source file. STATUS: Active DURATION: Next Version MAIL MESSAGE: 23166323 GOOD ONLY FOR VERSION: 1.0 COMPONENT/ENTRY POINT: SOURCE SUBSCRIBING PACKAGE: VISIT TRACKING ISC: Albany NUMBER: 1897 IA #: 1897 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAPI NAME: DBIA1889-I ORIGINAL NUMBER: 1889 ID: PXAPI GENERAL DESCRIPTION: $$SWITCHD^PXAPI This call may be used to return the switch over date defined in the SD/PCE Switch Over Date field (.02) of the PCE Parameters file (815). This is the date which Scheduling stopped asking for the clinical data and PCE started asking for it instead. Parameter Definition: None Returned Value: Date Internal FileMan format for date. Null If date is undefined. ===================================================================== $$SWITCHCK^PXAPI(DATE) The call may be used to compare a date to the switch over date defined in the SD/PCE Switch Over Date field (.02) of the PCE Parameters file (815). Parameter Definition: DATE Internal FileMan date. Returned Value: 1 If the date passed is greater than or equal to the switch over date. 0 If the date passed is less than the switch over date or the switch over date is undefined. STATUS: Active DURATION: Next Version MAIL MESSAGE: 23166324 GOOD ONLY FOR VERSION: 1.0 COMPONENT/ENTRY POINT: SWITCHD COMPONENT/ENTRY POINT: SWITCHCK SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 1898 IA #: 1898 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAPI NAME: DBIA1889-J ORIGINAL NUMBER: 1889 ID: PXAPI GENERAL DESCRIPTION: $$STOPCODE^PXAPI(STOPCODE,PATIENT,DATE) This function call returns the quantity of a particular Stop Code for a patient on one day. This is used by Scheduling. Parameter Definition: STOPCODE (required) pointer to #40.7 PATIENT (required) pointer to #2 DATE (required) the date in Fileman format (time is ignored if passed) Returned Value: the count of how many of that stop code are stored for that one day ====================================================================== $$CPT^PXAPI(CPT,PATIENT,DATE,HLOC) This is the function call to return the quantity of a particular CPT for a patient on one day and for one hospital location if passed. This is used by Scheduling to make sure that it has the CPT code the same number of times as PCE does. Parameter Description: CPT (required) pointer to #81 PATIENT (required) pointer to #2 DATE (required) the date in Fileman format (time is ignored if passed) HLOC (optional) pointer to Hospital Location file (#44) Returned Value: The count of how many (total quinity) of that cpt code are stored for that one day for that one patient in that one Hospital Location. STATUS: Active DURATION: Next Version MAIL MESSAGE: 23166325 GOOD ONLY FOR VERSION: 1.0 COMPONENT/ENTRY POINT: CPT COMPONENT/ENTRY POINT: STOPCODE SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 1899 IA #: 1899 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXCA NAME: DBIA1889-A ORIGINAL NUMBER: 1889 ID: PXCA GENERAL DESCRIPTION: PCE Device Interface module local array structures exported with PCE. Conventions An Error Suspension file records data that fails the verification process or if there are errors in storing. 1. In listings of valid values [1 | 0 | null] 1 denotes TRUE or YES 0 denotes FALSE or NO null denotes VALUE NOT SUPPLIED BY DATA CAPTURE APPLICATION 2. The PCE Device Interface uses a locally name-spaced array (called LOCAL in this document ) with the following gross structure to receive data from an external device. Developers should use an array in their namespace to represent the LOCAL array. It is possible that data from multiple providers was captured for the encounter. The ENCOUNTER node records information about the "main" provider. It is mandatory that this person be identified in the ENCOUNTER node. Data will NOT be moved to VISTA if such a provider is not identified on the ENCOUNTER node. The remaining nodes in the LOCAL( array [VITALS, DIAGNOSIS, PROCEDURE, PROBLEM... ] are specific to the particular PROVIDER associated with the data on that node. If the provider is unknown, (for example, the identity of the nurse who took the vitals was not captured on a scanned encounter form) the provider subscript may be set to zero except provider is required for PROBLEM. This is a concession to reality, and should not be encouraged. If a provider CAN be identified, they SHOULD be identified. Locally name-spaced array: LOCAL("DIAGNOSIS/PROBLEM",) LOCAL("PROBLEM",) LOCAL("SOURCE") LOCAL("ENCOUNTER") LOCAL("DIAGNOSIS",) LOCAL("PROCEDURE",) LOCAL("PROVIDER",) LOCAL("IMMUNIZATION",) LOCAL("SKIN TEST",) LOCAL("EXAM",) LOCAL("PATIENT ED",) LOCAL("HEALTH FACTORS",) LOCAL("VITALS",) Vitals are not processed by PCE but are passed to the Vitals/Measurement package. LOCAL("LOCAL", This data doesn PCE and will not be processed by PCE, but it may be used to pass local data to a local process (see protocol for local data processing). 3. The Encounter and Source nodes are required; the rest are optional. 4. All entries in the local array are resolved to internal values as defined below. 5. By convention; use a DUZ = .5 (the POSTMASTER) as a default when one cannot be determined. This is only for tasked jobs on some systems. 6. The data in the ENCOUNTER, PROCEDURE, and DIAGNOSIS/ PROBLEM or DIAGNOSIS nodes are the minimal set for capturing workload starting 10/1/96. The data in the rest of the nodes with the associated providers build on the clinically relevant data set and are not used for workload 7. While ENCOUNTER, PROCEDURE, and DIAGNOSIS/PROBLEM or DIAGNOSIS values are required to capture workload and generate a bill, they may not be present in every data set passed through this event point. For example, data on Vitals may be collected by a Nurse and passed through the event point for storage independent of other data associated with the encounter. Because of this, these are NOT required values in this version. 8. If there is a different (ancillary) hospital location for this patient encounter, you have to do a separate encounter. Separate calls for each hospital location are required. Required Input LOCAL( LOCAL( is a local array as defined in the remainder of this document. Developers should use an array in their namespace to represent the LOCAL array; e.g., IBDFPCE. Result returned PXCASTAT 1 = event processing occurred and the data was passed to DHCP. 0 = event processing could not occur. There is data in LOCAL("ERROR" explaining why. LOCAL("ERROR" as described below. Denotes Errors. Data associated with the error was not filed. The node does not exist if errors do not occur. LOCAL("ERROR",,,,)="Free text message^REJECTED VALUE" Where ::= "ENCOUNTER" | "VITALS" | "DIAGNOSIS" | "PROCEDURE" | "PROBLEM" | rest of list| ::= internal entry number of provider. Is 0 (ZERO) for ENCOUNTER and SOURCE ::= sub-entry 'i' for that provider Is 0 (ZERO) for ENCOUNTER, SOURCE and PROVIDER ::= $P( selector in LOCAL(,,) that failed. The value of may be 0 (ZERO) if a problem is found that does not relate to a single specific piece. LOCAL("WARNING" as described below. Denotes problems with the data that did not prevent processing. Processing continued after the warnable condition was detected. The node does not exist if warning, conditions do not occur. Warnings do NOT affect the value of PXCASTAT. LOCAL("WARNING",,,,) ="Free text message^QUESTIONABLE VALUE" Where ::= "ENCOUNTER" | "VITALS" | "DIAGNOSIS" | "PROCEDURE" | "PROBLEM" ::= internal entry number of provider. Is 0 (ZERO) for ENCOUNTER and SOURCE ::= sub-entry 'i' for that provider Is 0 (ZERO) for ENCOUNTER, SOURCE, and PROVIDER ::= $P( selector in LOCAL(,,) in question. The value of may be 0 (ZERO) if a problem is found that does not relate to a single specific piece. Entry Point for processing the data in the foreground FOREGND^PXCA(.LOCAL,.PXCASTAT) All data for the event driver is to be stored in the local array, LOCAL(, in the proper format by the source prior to calling this entry point. This entry point validates and verifies the data and then if there are no validation errors, the data is processed in the foreground. Computation by the source will not continue until all processing is completed by any and all 'down-stream' protocol event points. Entry Point for processing the data in the background on the Host BACKGND^PXCA(.LOCAL,.PXCASTAT) All data for the event driver is to be stored in the local array, LOCAL(, in the proper format by the source prior to calling this entry point. This entry point validates and verifies the data and then if there are no validation errors, the data is processed in the background via TASKMAN. Computation by the source may continue. Entry Point for data validation VALIDATE^PXCA(.LOCAL) The data in the local array, LOCAL(, is validated and verified, but is not processed. Use of this entry point by your application will result in the data being validated twice, since it is validated prior to processing by the FOREGND^PXCAEP and BACKGND^PXCAEP entry points. If a piece of data cannot be validated, an entry is placed in the LOCAL("ERROR" node as described above Protocol for local data processing PXCA DATA EVENT Other developers who wish to use any of the data in the local array, including local additions, can attach a protocol that calls their routines to the item multiple of this protocol. This protocol is activated if there are no errors in the data validation and after PCE has processed the data. For data unique to the encounter SOURCE data LOCAL("SOURCE") = 1^2^3^4^5, where: Piece 1 Data Source Required for PCE Required for SD Format: DATA SOURCES file (#839.7) Piece 2 DUZ Required for PCE Required for Scheduling Piece 3 Form numbers Not stored by PCE Piece 4 Batch ID Not stored by PCE Piece 5 Record ID Not stored by PCE Encounter data LOCAL("ENCOUNTER") = 1^2^3^4^5^6^7^8^9^10^11^12^13^14^15^16^17^18, where: LOCAL("ENCOUNTER",modifier[E;1/.01]) = "" Piece 1 Appointment Date/Time Required for PCE Required for Scheduling Format: Fileman Date/Time Piece 2 Patient DFN Required for PCE Required for Scheduling Format: Pointer to IHS PATIENT file (#9000001) Piece 3 Hospital Location IEN Each hospital location is a separate encounter P,S Format: Pointer to HOSPITAL LOCATION file (#44) Piece 4 Provider IEN This is the person that saw the Patient at the scheduled date and time. Required for PCE Format: Pointer to NEW PERSON file (#200) Piece 5 Visit CPT code IEN Format: Pointer to TYPE OF VISIT (#357.69) Piece 6 SC Condition Format: [1 | 0 | null] Piece 7 AO Condition Format: [1 | 0 | null] Piece 8 IR Condition Format: [1 | 0 | null] Piece 9 EC Condition Format: [1 | 0 | null] Piece 10 MST Condition Format: [1 | 0 | null] Piece 13 Eligibility Code IEN Format: Pointer to ELIGIBILITY CODE file (#8) Piece 14 Check-out date and time Format: Fileman Date/Time Piece 15 Provider indicator (relates to 4) Required for PCE Format: Set of Codes P ::= Primary S ::= Secondary Piece 16 Attending Physician IEN (May or may not be the same as 4) Format: Pointer to NEW PERSON file (#200) Piece 17 HNC Condition Format: [ 1 | 0 | null ] Piece 18 CV Condition Format: [ 1 | 0 | null ] All of the remaining entries in the LOCAL( array are specific to a particular Provider associated with the data on that node. If the provider is unknown, (for example, the identity of the nurse who took the vitals isn t recorded on a scanned encounter form), the provider subscript may be set to zero. Diagnosis and/or Problems, specific to one provider We recommend that you use these nodes instead of the separate Diagnosis and Problem nodes. If no Diagnosis and/or Problems, $D(LOCAL("DIAGNOSIS/PROBLEM")) is true. LOCAL("DIAGNOSIS/PROBLEM",, i) = 1^2^3^4,...17^18 where: Piece 1 Diagnosis Code IEN Required for PCE Required for Scheduling Format: Pointer to ICD9 DIAGNOSIS file (#80) Piece 2 Diagnosis Specification Code Required for PCE N/A for Problem List Format: Set of Codes P ::= Primary S ::= Secondary Piece 3 Clinical Lexicon Term IEN Format: Pointer to EXPRESSIONS file (#757.01) Piece 4 Problem IEN Required by Problem List for existing Format: Pointer to PROBLEM LIST file (#9000011) Piece 5 Add to Problem List N/A for PCE Required by Problem List for new problem Format: [1 | 0 | null] Piece 6 Problem Active? Default is Active if not specified N/A for PCE Format: Set of Codes A ::= Active I ::= Inactive Piece 7 Problem Onset Date N/A for PCE Format: Fileman Date/Time Piece 8 Problem Resolved Date N/A for PCE Format: Fileman Date/Time Piece 9 SC Condition Format: [1 | 0 | null] Piece 10 AO Condition Format: [1 | 0 | null] Piece 11 IR Condition Format: [1 | 0 | null] Piece 12 EC Condition Format: [1 | 0 | null] Piece 13 Provider Narrative Required for PCE Required by Problem List for new problem Format: free text, 2-80 Characters Piece 14 Category Header for Provider Narrative N/A for Problem List Format: free text, 2-80 Characters Piece 15 MST Condition Format: [ 1 | 0 | null ] Piece 16 HNC Condition Format: [ 1 | 0 | null ] Piece 17 CV Condition Format: [ 1 | 0 | null ] Piece 18 Order/Resulting Format: Set of Codes O ::= Ordering R ::= Resulting B ::= Both Ordering and Resulting LOCAL("DIAGNOSIS/PROBLEM",,i,"NOTE") = 1, where: Piece 1 Provider N/A for PCE Format: free text, 3-60 Characters NOTE: If the NOTE node is not needed, it does not have to exist. NOTE: Information is passed to Problem List if there is data for any of the positions 5-8 on the "DIAGNOSIS/PROBLEM" node or if there is "NOTE" node. NOTE: A provider is required to add a new problem to the Problem List. Diagnosis data list, specific to one provider, for Problems being treated at this encounter: If no Diagnoses, then '$D(LOCAL("DIAGNOSIS",))is true. LOCAL("DIAGNOSIS",,i) = 1^2^3^4^...^13^14 where: Piece 1 Diagnosis code IEN Required for PCE Required for Scheduling Format: Pointer to ICD9 DIAGNOSIS File (#80) Piece 2 Diagnosis specification code Will default to "S" if blank Format: Set of Codes. P ::= Primary S ::= Secondary Piece 3 SC Condition Format: [1 | 0 | null] Piece 4 AO Condition Format: [1 | 0 | null] Piece 5 IR Condition Format: [1 | 0 | null] Piece 6 EC Condition Format: [1 | 0 | null] Piece 7 Associated Problem IEN Format: Pointer to PROBLEM LIST file 9000011 Piece 8 Physician's term for Diagnosis Required for PCE Format: free text, 2-80 Characters Piece 9 Physician's term for Category Header May have been used as a grouping for a set of related Diagnosis which the provider selected from Format: free text, 2-80 Characters Piece 10 Lexicon IEN Format: Pointer to EXPRESSIONS File (#757.01) Piece 11 MST Condition Format: [ 1 | 0 | null ] Piece 12 HNC Condition Format: [ 1 | 0 | null ] Piece 13 CV Condition Format: [ 1 | 0 | null ] Piece 14 Order/Resulting Format: Set of Codes O ::= Ordering R ::= Resulting B ::= Both Ordering and Resulting NOTE: PCE recommends using the DIAGNOSIS/PROBLEM node so that the diagnosis can point to the problem that it relates to. Procedures data list, specific to one provider If no Procedures, then '$D(LOCAL("PROCEDURE",)) is true. LOCAL("PROCEDURE",,i) = 1^2^3^4^5^6^7^8^9^10^ 11^12^13^14,(pieces defined below) LOCAL("PROCEDURE",,i,modifier[E;1/.01]) = "" Piece 1 CPT4 Procedure code Required by PCE for V CPT file (Procedures) if this field is blank then will be stored in V TREATMENT file Required for Scheduling Format: Pointer to CPT file (#81) Piece 2 Quantity Performed Required for PCE Required for Scheduling Format: number > 0 Piece 3 Procedure specification code For CPT only. Format: Set of Codes P ::= Primary S ::= Secondary Piece 4 Date/Time Procedure performed Format: Fileman Date/Time Piece 5 Primary Associated Diagnosis IEN For this CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 6 Physician's term for Procedure Required for PCE Format: free text, 2-80 Characters Piece 7 Physician's term for Category Header May have been used as a grouping for a set of related Procedures which the provider selected from Format: free text, 2-80 Characters Piece 8 1st Secondary Associated Diagnosis IEN For this CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 9 2nd Secondary Associated Diagnosis IEN For this CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 10 3rd Secondary Associated Diagnosis IEN For this CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 11 4th Secondary Associated Diagnosis IEN For this CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 12 5th Secondary Associated Diagnosis IEN For this CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 13 6th Secondary Associated Diagnosis IEN For this CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 14 7th Secondary Associated Diagnosis IEN For this CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) NOTE: If a Procedure doesn t have a CPT code, it can be passed without one and will be stored in the V Treatment file but will not be used for workload or billing. Problem data list, specific to one provider If no Problems, then '$D(LOCAL("PROBLEM",)) is true. LOCAL("PROBLEM",,i) = 1^2^3^4^5^...^15 where: Piece 1 Problem Name Required for new Problem List, i.e. if Pos. 10 is null Format: free text Piece 2 Problem Onset Date Format: Fileman Date/Time Piece 3 Problem Active? Default is ACTIVE if not specified Format: [1 | 0 | null] Piece 4 Problem Date Resolved Format: Fileman Date/Time Piece 5 SC Condition Format: [1 | 0 | null] Piece 6 AO Condition Format: [1 | 0 | null] Piece 7 IR Condition Format: [1 | 0 | null] Piece 8 EC Condition Format: [1 | 0 | null] Piece 9 ICD 9 Code value {optional} Format: Pointer to ICD DIAGNOSIS File (#80) Piece 10 Problem IEN Must be null if new problem Required for editing existing Problem Format: Pointer to PROBLEM LIST file 9000011 Piece 11 Physician's term for Problem Null if new problem Format: free text, 60 Characters Max Piece 12 Lexicon IEN Format: Pointer to EXPRESSIONS File (#757.01) Piece 13 MST Condition Format: [ 1 | 0 | null ] Piece 14 HNC Condition Format: [ 1 | 0 | null ] Piece 15 CV Condition Format: [ 1 | 0 | null ] NOTE: The data in this node is passed to Problem List. A Provider is required to add a new problem to the Problem List. When a new problem is added to the Problem List, the problem IEN is not required. If data is passed to edit existing data, the problem IEN must be passed. NOTE: It is better to use the DIAGNOSIS/PROBLEM node so that the diagnosis can point to the problem that it relates to. Provider data list, specific to one provider Use this node to pass of additional providers which do not have data associated with them. If no additional Providers, then '$D(LOCAL("PROVIDER",< PROVIDER IEN>)) is true. LOCAL ("PROVIDER",= 1^2 where: Piece 1 Provider indicator Required for PCE Format: Set of Codes. P: = Primary S: = Secondary Piece 2 Attending Format: [1|0| null] NOTE: If a provider is on the Encounter node and also on this node then the data on this node will be used for Primary/Secondary indicator. Immunization data list, specific to one provider If no immunization entries, then '$D(LOCAL("IMMUNIZATION",)) is true. LOCAL ("IMMUNIZATION",,i)=1^2^3^4^5^6^7^8^9^10^11^12^13^14^15 Piece 1 Immunization Required for PCE Format: Pointer to IMMUNIZATION File (9999999.14) Piece 2 Series Format: Set of Codes. P::=Partially complete C::=Complete B::=Booster 1::=Series1 ... 8::=Series8 Piece 4 Reaction REACTION Field (9000010.11,.06) SET Format: Set of Codes. '0' FOR NONE '1' FOR FEVER; '2' FOR IRRITABILITY; '3' FOR LOCAL REACTION OR SWELLING; '4' FOR VOMITING; '5' FOR RASH OR ITCHING; '6' FOR LETHARGY; '7' FOR CONVULSIONS; '8' FOR ARTHRITIS OR ARTHRALGIAS; '9' FOR ANAPHYLAXIS OR COLLAPSE; '10' FOR RESPIRATORY DISTRESS; '11' FOR OTHER; Piece 5 Contraindicated Format: [1|0|null] Piece 6 Event D/T Format: Fileman Date/Time Piece 7 Remarks Format: Comment Piece 8 Primary Associated Diagnosis IEN For this mapped CPT only. Format: Pointer to ICD DIAGNOSIS File (#80 Piece 9 1st Secondary Associated Diagnosis IEN For this mapped CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 10 2nd Secondary Associated Diagnosis IEN For this mapped CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 11 3rd Secondary Associated Diagnosis IEN For this mapped CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 12 4th Secondary Associated Diagnosis IEN For this mapped CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 13 5th Secondary Associated Diagnosis IEN For this mapped CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 14 6th Secondary Associated Diagnosis IEN For this mapped CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 15 7th Secondary Associated Diagnosis IEN For this mapped CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Skin Test data list, specific to one provider If no skin test entries, then '$D(LOCAL("SKIN TEST",)) is true. LOCAL ("SKIN TEST",,i)=1^2^3^4^5^6^7^8^9^10^11^12^13 Piece 1 SKIN TEST Required for PCE Format: Pointer to SKIN TEST File (9999999.28) Piece 2 READING Format: Whole number between 0 and 40 inclusive Piece 3 RESULT Format: Set of Codes. P::=Positive N::=Negative D::=Doubtful 0::=No Take Piece 4 Date Read Format: Fileman Date/Time Piece 5 Date of Injection Format: Fileman Date/Time Piece 6 Primary Associated Diagnosis IEN For this mapped CPT only. Format: Pointer to ICD DIAGNOSIS File (#80 Piece 7 1st Secondary Associated Diagnosis IEN For this mapped CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 8 2nd Secondary Associated Diagnosis IEN For this mapped CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 9 3rd Secondary Associated Diagnosis IEN For this mapped CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 10 4th Secondary Associated Diagnosis IEN For this mapped CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 11 5th Secondary Associated Diagnosis IEN For this mapped CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 12 6th Secondary Associated Diagnosis IEN For this mapped CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Piece 13 7th Secondary Associated Diagnosis IEN For this mapped CPT only. Format: Pointer to ICD DIAGNOSIS File (#80) Examination data list, specific to one provider If no examination entries, then '$D(LOCAL("EXAM",)) is true. LOCAL ("EXAM",")=1^2 Piece 1 EXAM Required for PCE Format: Pointer to EXAM File (9999999.15) Piece 2 RESULT Format: Set of Codes. A::=Abnormal N::=Normal Patient Education data list, specific to one provider If no Patient Education entries, then '$D(LOCAL("PATIENT ED",)) is true. LOCAL ("PATIENT ED",,i)=1^2 Piece 1 Topic Required for PCE Format: Pointer to EDUCATION TOPICS File (9999999.09) Piece 2 Level of Understanding Format: Set of Codes. 1::=Poor 2::=Fair 3::=Good 4::=Group - No Assessment 5::=Refused Health Factors data list, specific to one provider If no Health Factors entries, then '$D(LOCAL("HEALTH FACTORS",)) is true. LOCAL ("HEALTH FACTORS",,i)=1^2 Piece 1 Health Factor Required for PCE Format: Pointer to HEALTH FACTORS File (9999999.64) Piece 2 Level/Severity Format: Set of Codes. M::=Minimal MO::=Moderate H::=Heavy/Severe Vitals data list, specific to one provider If no Vitals, then '$D(LOCAL("VITALS",)) is true. LOCAL("VITALS",,i) = 1^2^3^4, where: Piece 1 Type Required for PCE Format: Set of Codes. AG::= ABDOMINAL GIRTH AUD::= AUDIOMETREY BP::= BLOOD PRESSURE FH::= FUNDAL HEIGHT FT::= FETAL HEART TONES HC::= HEAD CIRCUMFERENCE HE::= HEARING HT::= HEIGHT PU::= PULSE RS::= RESPIRATIONS TMP::=TEMPERATURE TON::=TONOMETRY VC::= VISION CORRECTED VU::= VISION UNCORRECTED WT::= WEIGHT Piece 2 Value Required for PCE Format: Numeric Piece 3 Units Not stored; used for conversions Format: Set of Codes. C::=Centigrade (degrees) CM::=Centimeter F::= Fahrenheit (degrees) IN::=Inches KG::=Kilograms LB::=Pounds Piece 4 Date/Time Measurement taken Format: Fileman Date/Time If the TYPE is HT: If the UNIT is CM it is converted to IN so that it can be stored. If the UNIT is "" it is assumed to be IN. If the TYPE is WT If the UNIT is KG it is converted to LB so that it can be stored. If the UNIT is "" it is assumed to be LB. If the TYPE is TMP If the UNIT is C it is converted to F so that it can be stored. If the UNIT is "" it is assumed to be F. NOTE: This data is passed to the Vitals/Measurement package for validation and storage. Local data list, specific to one provider If no local entries, then '$D(LOCAL("LOCAL",)) is true. LOCAL("LOCAL",,i) = Site Specific data encoding Pieces All Site Specific data encoding Not stored in PCE Format: Site Specific NOTE: LOCAL("LOCAL" where "LOCAL" is replaced by locally namespaced string. STATUS: Active DURATION: Next Version GOOD ONLY FOR VERSION: 1.0 COMPONENT/ENTRY POINT: FOREGND COMPONENT/ENTRY POINT: BACKGND COMPONENT/ENTRY POINT: VALIDATE SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany EDITOR: BRICKER,DENNIS NUMBER: 1900 IA #: 1900 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VSIT NAME: DBIA1900-A ORIGINAL NUMBER: 1900 ID: VSIT GENERAL DESCRIPTION: Visit Tracking is a utility that can be used by a variety of VISTA modules (usually via PCE), with potential benefits for clinical, administrative, and fiscal applications. Visit Tracking will allow VISTA packages to link an event to a patient visit entry, thereby linking that event to any number of events occurring throughout the hospital during the patient's outpatient and/or inpatient episode. Visit Tracking is not a stand-alone application. Other packages will normally call PCE, which will handle the calls to Visit Tracking. The key to the creation of visits will be to ensure the clinical meaningfulness of visits. The creation of visits is facilitated by the Visit Tracking module. In order to ensure a consistent implementation of visit creation across packages, each package needs to have an agreement with the Visit Administrator to create visits. This section describes the guidelines which should be used for VA developers populating visits in the Visit file. These guidelines are based on a combination of the experience of Albuquerque's joint venture sharing, IHS' PCC pilot test at Tucson VAMC, MCCR data capture pilots, HSR&D workload reporting studies at Hines VAMC, and DMMS/DSS event data capture. The purpose of the VISIT file in the VA: The VISIT file has multiple purposes. The primary role is to record when and where clinical encounters related to a patient have occurred. Visits will be recorded for both Outpatient and Inpatient encounters. Outpatient encounters include scheduled appointments and walk-in unscheduled visits. Inpatient encounters include the admission of a patient to a VAMC and any clinically significant change related to treatment of that patient. For example, a treating specialty change is clinically significant, whereas a bed switch is not. The clinically significant visits created throughout the inpatient stay are related to the inpatient admission visit. If the patient is seen in a clinic while an Inpatient, a separate visit will be created representing the appointment visit?this visit is related to the Admission visit. A clinician's telephone communications with a patient may be represented by a separate visit. The clinical visits can be viewed from two approaches: 1) a team of providers can be associated with a primary clinical visit (this is the traditional view taken by IHS); or 2) a primary clinic visit can represent the primary provider's care, and a separate visit can be created to reflect the secondary provider's care. Additionally, the VISIT file can provide a breakdown of other ancillary services provided during the clinically significant visit. Laboratory or Radiology services are other examples of services provided that could have a separate visit reflecting the service involvement related to a clinic appointment on the same day. Create and/or Match Visit Using Input Criteria ^VSIT INPUT: VSIT VSIT("VDT") may be used instead of VSIT. (time will default to 12 noon if not specified) DFN VSIT("PAT") may be used instead of DFN. [VSIT(0)] [VSIT("")] (used in match logic if VSIT(0)["M") (for SVC, TYP, INS, CLN, ELG, LOC) Note: For multiple field values use [[^...]] i.e., VSIT("SVC")="H^D" (will find both) VSITPKG VSIT("PKG") may be used instead of VSITPKG. OUTPUT: VSIT() N^S[^1] where: N = or -1 if could not get a visit or -2 if calling package is not active in Visit Package Parameters S = 1 = ) array passed in with all the entries defined and the defaulted values added VSIT(,) returns the data that is stored in the Visit file in the same format as VSIT() Variable descriptions: VSIT() Variable Names for VISIT file fields, Where is a general reference to the field mnemonic. file: 9000010, global: ^AUPNVSIT( Key Indicates r indicated a required field m matching/screening logic can/does apply s system generated e strongly encouraged Key Field Variable Description .001 VSIT("IEN") NUMBER (visit internal entry number) rm .01 VSIT("VDT") VISIT/ADMIT DATE&TIME (date) s .02 VSIT("CDT") DATE VISIT CREATED (date) m .03 VSIT("TYP") TYPE (set) rm .05 VSIT("PAT") PATIENT NAME (pointer PATIENT file #9000001) (IHS file DINUMed to PATIENT file #2) m .06 VSIT("INS") LOC. OF ENCOUNTER (pointer LOCATION file #9999999.06) (IHS file DINUMed to INSTITUTION file #4) .07 VSIT("SVC") SERVICE CATEGORY (set) ms .08 VSIT("DSS") DSS ID (pointer to CLINIC STOP file) .09 VSIT("CTR") DEPENDENT ENTRY COUNTER (number) .11 VSIT("DEL") DELETE FLAG (set) .12 VSIT("LNK") PARENT VISIT LINK (pointer VISIT file #9000010) s .13 VSIT("MDT") DATE LAST MODIFIED (date) .18 VSIT("COD") CHECK OUT DATE&TIME (date) .21 VSIT("ELG") ELIGIBILITY (pointer ELIGIBILITY CODE file #8) rm .22 VSIT("LOC") HOSPITAL LOCATION (pointer HOSPITAL LOCATION file #44) .23 VSIT("USR") CREATED BY USER (pointer NEW PERSON file #200) .24 VSIT("OPT") OPTION USED TO CREATE (pointer OPTION file #19) .25 VSIT("PRO") PROTOCOL (pointer PROTOCOL file #101) .26 VSIT("ACT") PFSS ACCOUNT REFERENCE (pointer PFSS ACCOUNT file #375) 2101 VSIT("OUT") OUTSIDE LOCATION (free text) 80001 VSIT("SC") SERVICE CONNECTED (set) 80002 VSIT("AO" AGENT ORANGE EXPOSURE (set) 80003 VSIT("IR") IONIZING RADIATION EXPOSURE (set) 80004 VSIT("EC") PERSIAN GULF EXPOSURE (set) 80005 VSIT("MST") MILITARY SEXUAL TRAUMA (set) 15001 VSIT("VID") VISIT ID (free text) 15002 VSIT("IO") PATIENT STATUS IN/OUT (set) 15003 VSIT("PRI") ENCOUNTER TYPE (set) 81101 VSIT("COM") COMMENTS r 81202 VSIT("PKG") PACKAGE (pointer PACKAGE file #9.4) 81203 VSIT("SOR") DATA SOURCE (pointer PCE DATA SOURCE file #839.7) r VSIT(0) A string of characters that defines how the visit processor will function. F Force adding a new entry. I Interactive mode E Use patient's primary eligibility if not defined on call with VSIT("ELG"). N Allow creation of new visit. D Look back "n" number of days for match, defaults to one (1). D[] i.e., VSIT(0)="D7" e.g., VSIT(0)="D5" (visit date to visit date - 4) use "D0" to require exact match on visit date and time. M Impose criteria on matching/screening of visits. Uses the VSIT() array: Matching elements must equal their corresponding field. mr DFN Internal entry number of the patient file. If not defined the VSIT("PAT") will be used. mr VSIT The date (and time) of the visit. If not defined then VSIT("VDT") will be used. r VSITPKG Package Name Space. If not defined then VSIT("PKG") will be used. VSIT() N^S[^1] where: N = S = 1 = STATUS: Active DURATION: Next Version MAIL MESSAGE: 29239100 GOOD ONLY FOR VERSION: 2.0 COMPONENT/ENTRY POINT: VSIT SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 1901 IA #: 1901 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VSIT NAME: DBIA1900-B ORIGINAL NUMBER: 1900 ID: VSIT GENERAL DESCRIPTION: MODIFIED^VSIT(IEN) Sets the Date Last Modified (.13) field to NOW. This is used by PCE so that the Date Last Modified refers to any modification to the Visit or any V-File. Parameter Description: IEN Pointer to the Visit file (#9000010) Returned Value: none ========================================================================== UPD^VSIT This will update any fields in the Visit file (#9000010) that can be edited. Look up a visit and return all of its information Where VSIT("HNC") has been identified as the reason for the visit, It will also update the NOSE AND THROAT RADIUM HISTORY file (#28.11) to validate the patient has been treated for Head and Neck Cancer, if no previous validation has taken place. Parameter Description: VSIT("IEN") Pointer to the Visit file (#9000010) Any of the following variables that are going to be updated: Field # Variable Description .03 VSIT("TYP") TYPE (set) .06 VSIT("INS") LOC. OF ENCOUNTER (pointer LOCATION file #9999999.06) (IHS file DINUMed to INSTITUTION file #4) .07 VSIT("SVC") SERVICE CATEGORY (set) .08 VSIT("DSS") DSS ID (pointer to CLINIC STOP file) .12 VSIT("LNK") PARENT VISIT LINK (pointer VISIT file #9000010) .13 VSIT("MDT") DATE LAST MODIFIED (date) This will be set to "NOW" by Visit Tracking. .18 VSIT("COD") CHECK OUT DATE&TIME (date) .21 VSIT("ELG") ELIGIBILITY (pointer ELIGIBILITY CODE file #8) .22 VSIT("LOC") HOSPITAL LOCATION (pointer HOSPITAL LOCATION file #44) .23 VSIT("USR") CREATED BY USER (pointer NEW PERSON file #200) .24 VSIT("OPT") OPTION USED TO CREATE (pointer OPTION file #19) .25 VSIT("PRO") PROTOCOL (pointer PROTOCOL file #101) 2101 VSIT("OUT") OUTSIDE LOCATION (free text) 80001 VSIT("SC") SERVICE CONNECTED (set) 80002 VSIT("AO") AGENT ORANGE EXPOSURE (set) 80003 VSIT("IR") IONIZING RADIATION EXPOSURE (set) 80004 VSIT("EC") PERSIAN GULF EXPOSURE (set) 80005 VSIT("MST") MILITARY SEXUAL TRAUMA (set) 80006 VSIT("HNC") HEAD AND NECK CANCER (set) 80007 VSIT("CV") COMBAT VETERAN (set) 80008 VSIT("SHAD") PROJECT 112/SHAD (set) 15001 VSIT("VID") VISIT ID (free text) 15002 VSIT("IO") PATIENT STATUS IN/OUT (set) 15003 VSIT("PRI") ENCOUNTER TYPE (set) 81101 VSIT("COM") COMMENTS 81202 VSIT("PKG") PACKAGE (pointer PACKAGE file #9.4) 81203 VSIT("SOR") DATA SOURCE (pointer PCE DATA Returned Value: none STATUS: Active DURATION: Next Version MAIL MESSAGE: 23353655 GOOD ONLY FOR VERSION: 2.0 COMPONENT/ENTRY POINT: UPD COMPONENT/ENTRY POINT: MODIFIED SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany NUMBER: 1902 IA #: 1902 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VSIT NAME: DBIA1900-C ORIGINAL NUMBER: 1900 ID: VSIT GENERAL DESCRIPTION: Ever field that points to the Visit file (#9000010) needs to have two cross references. One is a regular Fileman cross reference. If the field is in a multiple then this cross reference must be a whole file cross reference. This cross reference is used to make sure that a Visit file entry is not delete as long as there is a user of the entry. The second cross reference calls ADD for the set logic and SUB for the kill logic. This cross reference tells Visit Tracking how many file entries are using (pointing to) a Visit file entry. Below is an example of this cross reference CROSS-REFERENCE: file number^Asomething^MUMPS 1)= D ADD^AUPNVSIT 2)= D SUB^AUPNVSIT This cross-reference adds and subtracts from the dependent entry count in the VISIT file. ADD^VSIT or the more effect version: ADD^AUPNVSIT Increase the dependent entry count for the Visit file entry by one. INPUT X Visit IEN SUB^VSIT or the more effect version: SUB^AUPNVSIT Decrease the dependent entry count for the Visit file entry by one. INPUT X Visit IEN NOTE: These calls are customarily done through a MUMPS cross reference on the field pointing to a Visit file entry. The input parameter X is set by Fileman. STATUS: Active DURATION: Next Version MAIL MESSAGE: 23353668 GOOD ONLY FOR VERSION: 2.0 COMPONENT/ENTRY POINT: ADD COMPONENT/ENTRY POINT: SUB SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: EVENT CAPTURE ISC: Albany SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 1903 IA #: 1903 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VSIT NAME: DBIA1900-D ORIGINAL NUMBER: 1900 ID: VSIT GENERAL DESCRIPTION: $$IEN2VID^VSIT(VISIT) This function returns the Visit ID for the Visit IEN passed in. Parameter: VISIT IEN to a Visit file (#9000010) entry Returned value: Visit ID if value Visit IEN -1 if the Visit IEN is not a valued pointer ======================================================================= $$VID2IEN^VSIT(VID) This function returns the Visit IEN for the Visit ID passed in. Parameter: VID Visit ID Returned value: >0 IEN to a Visit file (#9000010) entry -1 if there is no Visit file (#9000010) entry for the Visit ID STATUS: Active DURATION: Next Version MAIL MESSAGE: 23353679 GOOD ONLY FOR VERSION: 2.0 COMPONENT/ENTRY POINT: IEN2VID COMPONENT/ENTRY POINT: VID2IEN SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 1904 IA #: 1904 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VSIT NAME: DBIA1900-E ORIGINAL NUMBER: 1900 ID: VSIT GENERAL DESCRIPTION: $$PKG2IEN^VSIT(PKG) Returns a pointer to the Package file when you pass in the package name space or name. The pointer to the package is required for some calls to PCE. This function is provided so that the calling packages all do not have to do this lookup themselves. Parameter Description: PKG Package name space or name Returned Value: >0 Pointer to the package in the Package file #9.4 -1 If called without PKG or if could not find the package in the Package file. $$PKGON^VSIT(PKG) Returns the active flag for the package. A package that is active can create Visits. PCE will be creating the Visits for most packages so they will not need to be active. Only PCE will need to be active to create the visit for them. Parameter Description: PKG Package name space or name Returned Value: 1 The package can create visits (active) 0 The package cannot create visits (not active) -1 Called wrong or could not find package in Visit Tracking Parameters file # 150.9 STATUS: Active DURATION: Next Version MAIL MESSAGE: 23353687 GOOD ONLY FOR VERSION: 2.0 COMPONENT/ENTRY POINT: PKG2IEN COMPONENT/ENTRY POINT: PKGON SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING DETAILS: ADDED 8/28/09 DATE/TIME EDITED: AUG 28, 2009@10:53 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SILVERMAN,ROBERT WITH CONCURRENCE OF: FAIN,ZACHARY NUMBER: 1905 IA #: 1905 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VSIT NAME: RETURN SELECTED VISITS FROM VSIT ORIGINAL NUMBER: 1900 ID: VSIT GENERAL DESCRIPTION: SELECTED^VSIT(DFN,SDT,EDT,HOSLOC,ENCTYPE,NENCTYPE,SERVCAT,NSERVCAT,LASTN) Returns selected visits depending on screens passed in. Parameter Description: Only the DFN is required. DFN Pointer to the Patient file (#2) SDT Start Date EDT End Date HOSLOC Pointer to the Hospital Location file (#44) ENCTYPE Encounter types is a string of all the Encounter Types (field #15003) wanted. e.g. "OA" for only Ancillary and Occasion of service NENCTYPE Not Encounter types is a string of all the Encounter Types (field #15003) not wanted. e.g. "T" for do not include Telephone SERVCAT Service Categories is a string of all the Service Categories (field #.07) to include. If non is passed all is assumed. e.g. "H" for just historical. "T" for just Telephone. "AIT" for ambulatory (in and out patient) and Telephone. NSERVCAT Not Service categories is a string of all the Service Categories (field #.07) to not include. LASTN How many to return starting with the End Date an going backwards Returned Array: (may be killed before and after use) ^TMP("VSIT",$J,vsit ien,#) vsit ien Pointer to the Visit file (#9000010) # Is a sequence number i.e. 1,2,3, ... Where the values stored in the array are of the form: Piece 1: Date and Time from the Vsit File Entry Piece 2: If Service Category '= "H" then Hospital Location (pointer to file#44) ";" External Value If Service Category = "H" then Location of Encounter (Pointer to file #9999999.06) ";" External Value Piece 3: Service Category (Value of field .07 set of codes) Piece 4: Service Connected (Value of field 80001 External Value) Piece 5: Patient Status in/out (Value of field 15002 set of codes) Piece 6: Clinic Stop ien (Pointer to file # 40.7 ";" External value) STATUS: Active DURATION: Next Version MAIL MESSAGE: 23353696 GOOD ONLY FOR VERSION: 2.0 COMPONENT/ENTRY POINT: SELECTED SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM SUBSCRIBING PACKAGE: EVENT CAPTURE SUBSCRIBING DETAILS: ECS added 8/12/09 SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: JSH/20090812 - CHANGED NAME FROM DBIA1900-F TO RETURN SELECTED VISITS FROM VSIT 3/16/15-MC: Added VPS as a subscriber at the request of Carolyn Wheless and approved by Anthony Puleo for VPS*1*15, planned for release in April 2015. To implement the ORQQVC VISITS/APPTS functionality, VPS must call SELECTED^VSIT. VPS needs to return a patient's visits as is currently done in ORQQVS/APPTS. DATE/TIME EDITED: AUG 12, 2009@12:34 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: FLEGEL,CHRIS WITH CONCURRENCE OF: MULLER,RICHARD DATE/TIME EDITED: AUG 12, 2009@12:42 ACTION: CONTENT CORRECTED AT THE REQUEST OF: HARVEY,JULIE DATE/TIME EDITED: MAR 16, 2015@09:14 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: PULEO,ANTHONY NUMBER: 1906 IA #: 1906 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VSIT NAME: DBIA1900-G ORIGINAL NUMBER: 1900 ID: VSIT GENERAL DESCRIPTION: $$LOOKUP^VSIT(IEN,FMT,WITHIEN) Look up a visit and return all of its information. Parameter Description: IEN Visit IEN OR the Visit's ID FORMAT Is the format that you want the output in, where: I ::= internal format E ::= external format B ::= both internal and external format B is the default if anything other than "I" or "E" WITHIEN 0 if you do not want the ien of the vsit as the first subscript 1 if you do. 1 is the default. Returned Value: >0 Pointer to the Visit file (#9000010) -1 if IEN was not a valid IEN or Visit ID Returned Array: The array of all the fields in the visit file. If both internal and external format are returned the format is: internal^external VSIT(,) or VSIT() depending on the value of WITHIEN Field # Variable Description .01 VSIT("VDT") VISIT/ADMIT DATE&TIME (date) .02 VSIT("CDT") DATE VISIT CREATED (date) .03 VSIT("TYP") TYPE (set) .05 VSIT("PAT") PATIENT NAME (pointer PATIENT file #9000001) (IHS file DINUMed to PATIENT file #2) .06 VSIT("INS") LOC. OF ENCOUNTER (pointer LOCATION file #9999999.06) (IHS file DINUMed to INSTITUTION file #4) .07 VSIT("SVC") SERVICE CATEGORY (set) .08 VSIT("DSS") DSS ID (pointer to CLINIC STOP file) .09 VSIT("CTR") DEPENDENT ENTRY COUNTER (number) .11 VSIT("DEL") DELETE FLAG (set) .12 VSIT("LNK") PARENT VISIT LINK (pointer VISIT file #9000010) .13 VSIT("MDT") DATE LAST MODIFIED (date) .18 VSIT("COD") CHECK OUT DATE&TIME (date) .21 VSIT("ELG") ELIGIBILITY (pointer ELIGIBILITY CODE file #8) .22 VSIT("LOC") HOSPITAL LOCATION (pointer HOSPITAL LOCATION file #44) .23 VSIT("USR") CREATED BY USER (pointer NEW PERSON file #200) .24 VSIT("OPT") OPTION USED TO CREATE (pointer OPTION file #19) .25 VSIT("PRO") PROTOCOL (pointer PROTOCOL file #101) 2101 VSIT("OUT") OUTSIDE LOCATION (free text) 80001 VSIT("SC") SERVICE CONNECTED (set) 80002 VSIT("AO") AGENT ORANGE EXPOSURE (set) 80003 VSIT("IR") IONIZING RADIATION EXPOSURE (set) 80004 VSIT("EC") PERSIAN GULF EXPOSURE (set) 80005 VSIT("MST") MILITARY SEXUAL TRAUMA (set) 80006 VSIT("HNC") HEAD AND NECK CANCER (set) 80007 VSIT("CV") COMBAT VETERAN (set) 80008 VSIT("SHAD") PROJECT 112/SHAD (set) 15001 VSIT("VID") VISIT ID (free text) 15002 VSIT("IO") PATIENT STATUS IN/OUT (set) 15003 VSIT("PRI") ENCOUNTER TYPE (set) 81101 VSIT("COM") COMMENTS 81202 VSIT("PKG") PACKAGE (pointer PACKAGE file #9.4) 81203 VSIT("SOR") DATA SOURCE (pointer PCE DATA SOURCE file (#839.7) STATUS: Active DURATION: Next Version MAIL MESSAGE: 23353699 GOOD ONLY FOR VERSION: 2.0 COMPONENT/ENTRY POINT: LOOKUP SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI NUMBER: 1907 IA #: 1907 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VSIT NAME: DBIA1900-H ORIGINAL NUMBER: 1900 ID: VSIT GENERAL DESCRIPTION: $$HISTORIC^VSIT(IEN) Returns a flag indicating whether the visit is Historical. Parameter Description: IEN Pointer to the Visit file (#9000010) Returned Value: 1 If it is an Historical visit ("E" in the Service Category field #.07) 0 If it is not an Historical visit -1 If the IEN is bad STATUS: Active DURATION: Next Version MAIL MESSAGE: 23353702 GOOD ONLY FOR VERSION: 2.0 COMPONENT/ENTRY POINT: HISTORIC SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES DBA Comments: 9/13/12-mm: Added Clinical Case Registries as a subscriber for patch ROR*1.5*19. CCR is using $$HISTORIC~VSIT API in CCR code to determine if a given visit is historical or not. DATE/TIME EDITED: SEP 13, 2012@11:55 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: GUPTA,KAPIL WITH CONCURRENCE OF: WOLF,ED DATE/TIME EDITED: SEP 13, 2012@11:56 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: GUPTA,KAPIL WITH CONCURRENCE OF: YORTY,BOB NUMBER: 1908 IA #: 1908 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VSIT NAME: DBIA1900-A ORIGINAL NUMBER: 1900 ID: VSIT GENERAL DESCRIPTION: $$PKG^VSIT(PKG,VALUE) This API adds the package to the Package multiple (field #3) of the Visit Tracking Paramenters (150.9) file. It also set the sets the Active Flag in the multiple. If the package is already in the Package multiple it just set the Active Flag for that package. Parameter Description: PKG Package Name Space VALUE Value on the ON/OFF flag under package multiple 1 for ON and 0 for OFF Returned Value: 1^active Where active is the value stored in the active flag -1 Error in processing STATUS: Active DURATION: Next Version MAIL MESSAGE: 23353714 GOOD ONLY FOR VERSION: 2.0 COMPONENT/ENTRY POINT: PKG SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 1909 IA #: 1909 DATE CREATED: JAN 23, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VSITKIL NAME: DBIA1900-B ORIGINAL NUMBER: 1900 ID: VSITKIL GENERAL DESCRIPTION: KILL^VSITKIL(IEN) Deletes the visit if there is no files pointing to it. Before deleting checks all the backward pointers to see if the visit is being pointed to. Parameter Description: IEN Pointer to the Visit file (#9000010) STATUS: Active DURATION: Next Version MAIL MESSAGE: 23353725 GOOD ONLY FOR VERSION: 2.0 COMPONENT/ENTRY POINT: KILL SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 1910 IA #: 1910 FILE NUMBER: 409.68 GLOBAL ROOT: SCE( DATE CREATED: JAN 24, 1997 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1910 ID: SCE( GLOBAL REFERENCE: SCE(D0,0) FIELD NUMBER: .01 FIELD NAME: DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: PATIENT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: CLINIC STOP CODE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: LOCATION LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .05 FIELD NAME: VISIT FILE ENTRY LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: PARENT ENCOUNTER LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .08 FIELD NAME: ORIGINATING PROCESS TYPE LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: The zero node is read into a local variable. The fields above are used. GENERAL DESCRIPTION: DSS Extracts references the following data from the OUTPATIENT ENCOUNTER file (#409.68). The data is referenced in the Clinic Visit Extract for scheduled appointments, dispositions, stand- alones, and appended visits. (1) In determining the number of scheduled appointments: For each clinic in the HOSPITAL LOCATION file, the APPOINTMENT multiple is examined. For each patient appointment in the date range, the APPOINTMENT multiple in the PATIENT file is examined. We get the OUTPATIENT ENCOUNTER (p20) pointer. Using this IEN, we get the VISIT FILE ENTRY from the OUTPATIENT ENCOUNTER file. This is used to call a PCE API for data. (2) In determining the number of dispositions, stand-alones, etc.: We loop through the "B" cross-reference of the OUTPATIENT ENCOUNTER file for the extract date range and get the encounter IEN. Since all of the data is on the zero node, we set a local variable to the zero node and process it from there. DSS uses the "B" cross reference on the DATE field. ^SCE("B",DATE,D0) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22949980 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas NUMBER: 1911 IA #: 1911 DATE CREATED: JAN 24, 1997 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUPNAPI NAME: DBIA1911 ID: TIUPNAPI GENERAL DESCRIPTION: This API may be called by an application on the VistA server to create a TIU Document with the following constraints and optional properties: Return variable (must pass by reference): TIUIFN (pass by ref) = New note IFN in file 8925, = -1 or variations if error. Required Input parameters: DFN = Patient IFN in file #2 TIUAUTH = Author IFN in file #200 TIURDT = Date/time of note in FM format TIUTITLE = Title IFN in file 8925.1 Required global "input" variable: ^TMP("TIUP",$J) = Array root for text in format compatible with FM Word-processing fields. e.g., ^TMP("TIUP",$J,0)=^^1^1^2961216^ ^TMP("TIUP",$J,1,0)=Testing the TIUPNAPI. Optional Input variables: TIULOC = Patient Location IFN in file #44 TIUES = 1 if TIU should prompt/process E-SIG TIUPRT = 1 if TIU should prompt user to print note TIUESBY = Signer IFN in file #200: Calling App is responsible for Electronic Signature TIUASKVS = BOOLEAN flag indicating whether to ask for visit TIUADEL = BOOLEAN flag for automatic delete instead of leaving UNSIGNED document if TIUESBY>0 and signature fails. See NOTE on TIUADEL, below. NOTE: The following change was made in patch TIU*1*184 in response to a patient safety issue where SIGNED notes were sometimes created without a valid expected cosigner being specified for users requiring cosignature. If the API is called non-interactively for a user requiring cosignature with the intention that the API create a SIGNED document (TIUESBY>0), then the signature will now FAIL. Generally signature failure leaves the document unsigned. However, if TIUADEL=1, signature failure deletes the document. ** Therefore we do not recommend the use of TIUADEL in this particular situation (non-interactive, user requires cosignature, TIUESBY>0). ** STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32739888 COMPONENT/ENTRY POINT: NEW COMPONENT DESCRIPTION: To file a TIU Document from a VistA M-application, call: NEW^TIUPNAPI(TIUIFN,DFN,TIUAUTH,TIURDT,TIUTITLE,TIULOC, TIUES,TIUPRT,TIUESBY,TIUASKVS,TIUADEL) NOTE: per VistA SAC, all input parameters passed by reference in the formal list should be namespaced for the calling application. VARIABLES: TIUIFN TYPE: Output VARIABLES DESCRIPTION: Passed by Reference. If the call to NEW^TIUPNAPI is successful, the internal entry number in file 8925 will be returned. If the call is unsuccessful, the return variable will be set to -1 or a variation. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pass by value. Required. This is the Internal Entry Number of the patient in the PATIENT File (#2). VARIABLES: TIUAUTH TYPE: Input VARIABLES DESCRIPTION: Pass by value. Required. This is the internal entry number of the AUTHOR of the note in the NEW PERSON File (#200). VARIABLES: TIURDT TYPE: Input VARIABLES DESCRIPTION: Pass by value. Required. Reference Date/time of document in internal FM format. VARIABLES: TMP TYPE: Input VARIABLES DESCRIPTION: The temporary global array ^TMP("TIUP",$J) MUST be loaded with the word- processing data to be filed with the note, prior to calling the API, using the following subscripting scheme: ^TMP("TIUP",$J,0)="^^<# lines>^<# lines>^ ^ ^TMP("TIUP",$J,1,0)="" ^TMP("TIUP",$J,2,0)="" ^TMP("TIUP",$J,3,0)="" ^TMP("TIUP",$J,n,0)="" VARIABLES: TIULOC TYPE: Input VARIABLES DESCRIPTION: Pass by value. Optional. This is the Internal Entry Number of the LOCATION in the HOSPITAL LOCATION File (#44). VARIABLES: TIUES TYPE: Input VARIABLES DESCRIPTION: Pass by Value. Optional. BOOLEAN flag. Pass as 1 if you want TIU to prompt for Electronic Signature. VARIABLES: TIUPRT TYPE: Input VARIABLES DESCRIPTION: Pass by Value. Optional. BOOLEAN flag. Pass as 1 if you want TIU to prompt for printing on completion. VARIABLES: TIUESBY TYPE: Input VARIABLES DESCRIPTION: Pass by Value. Optional. Pass IEN of the person whose electronic signature is to be applied to the document. ONLY pass this if the calling application has already prompted for/validated the user's electronic signature. VARIABLES: TIUASKVS TYPE: Input VARIABLES DESCRIPTION: Pass by Value. Optional. BOOLEAN flag. Pass as 1 if you want TIU to prompt for selection of a visit with which the document is to be associated. VARIABLES: TIUADEL TYPE: Input VARIABLES DESCRIPTION: Optional. BOOLEAN flag. Pass as a 1 if TIUESBY>0 and calling application wants to have the newly created document automatically deleted if the electronic signature fails for any reason. If TIUADEL is not set, the document is left UNSIGNED. If TIUESBY>0 and the API is called non-interactively for users who require cosignature, we do NOT recommend the use of TIUADEL. See general description of API. VARIABLES: TIUTITLE SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas SUBSCRIBING DETAILS: The Addiction Severity Index (ASI) module of Mental Health uses this call to file ASI notes. SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: DIETETICS SUBSCRIBING DETAILS: added 12/10/2007 DATE/TIME EDITED: DEC 27, 2007@21:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: UNDERHILL,GARDNER WITH CONCURRENCE OF: BAKKE,ANDREW NUMBER: 1912 IA #: 1912 DATE CREATED: JAN 28, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIFROMSS NAME: DBIA1912 ID: DIFROMSS GENERAL DESCRIPTION: The MAS Developers would like a one-time integration agreement with the FileMan Developers: For patch DG*5.3*111, as part of the installation environment checker, DG53111E, we check the second line of the following routine using $TEXT: DIFROMSS The check is to ensure that the package version is 21 and DIFROMSS has patch #15 indicated in its second line. This environment checker routine is necessary because the prefix, "DI", is not unique to the VA FILEMAN package in the PACKAGE file (#9.4). An earlier package named FILEMAN shares the same Prefix, and as a result, the "Required Build" function in the KIDS Build does not function properly when referencing a FileMan patch. STATUS: Active MAIL MESSAGE: 22959334 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 1914 IA #: 1914 DATE CREATED: JAN 29, 1997 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRVALL0 NAME: GMRVALL0 ID: GMRVALL0 GENERAL DESCRIPTION: Nursing can access the following entry point described in this DBIA for GMRVED0 routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23002007 COMPONENT/ENTRY POINT: LIST COMPONENT DESCRIPTION: This entry point displays the vitals/measurements for the User Configurable Combination option. This option allows users to select types of vitals/measurements to edit. VARIABLES: GNUROP TYPE: Input VARIABLES DESCRIPTION: This variable is passed in with a value of 1 to indicate that the edit process is requested by the Nursing Service. VARIABLES: GMROUT TYPE: Both VARIABLES DESCRIPTION: This variable indicates whether the user abnormally exited the vitals/measurements selection. It is passed in with a value of 0. VARIABLES: GMRENTY TYPE: Output VARIABLES DESCRIPTION: The type of vitals/measurements to edit. VARIABLES: GMRSTR TYPE: Output VARIABLES DESCRIPTION: The string of which vitals/measurements to edit, for example, "T;P;R;BP;". SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1916 IA #: 1916 DATE CREATED: FEB 05, 1997 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SCAPMC NAME: SCAPMC - SUPPORTED PCMM CALLS ID: SCAPMC GENERAL DESCRIPTION: These are supported references in the SCAPMC routine: (1) $$PRTM(SCTEAM,SCDATES,SCUSRA,SCROLEA,SCLIST,SCERR) -- (2) $$PRCL(SC44,SCDATES,SCPOSA,SCUSRA,SCROLEA,SCLIST,SCERR) -- (3) $$PRPT(DFN,SCDATES,SCPOSA,SCUSRA,SCROLEA,SCPURPA,SCLIST,SCERR) -- ; (4) $$PTTM(SCTEAM,SCDATES,SCLIST,SCERR) -- (5) $$TMPT(DFN,SCDATES,SCPURPA,SCLIST,SCERR) -- (6) $$INSTPCTM(DFN,SCEFF) -- (7) $$PTPR(SC200,SCDATES,SCPURPA,SCROLEA,SCLIST,SCERR,SCYESCL)-- STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29464095 COMPONENT/ENTRY POINT: $$PRTM COMPONENT DESCRIPTION: $$PRTM(SCTEAM,SCDATES,SCUSRA,SCROLEA,SCLIST,SCERR) -- Extrinsic function call to return an array of practitioners who are assigned to positions on a team for a time period. Output: @SCLIST() = array of practitioners Format: Subscript: Sequential # from 1 to n Piece Description 1 IEN of NEW PERSON file entry (#200) 2 Name of person 3 IEN of TEAM POSITION file (#404.57) 4 Name of Position 5 IEN OF USR CLASS(#8930) of POSITION (#404.57 6 USR Class Name 7 IEN of STANDARD POSITION (#403.46) 8 Standard Role (Position) Name 9 Activation Date for 404.52 (not 404.59!) 10 Inactivation Date for 404.52 11 IEN of Position Ass History (404.52) 12 IEN of Preceptor Position 13 Name of Preceptor Position SCERR() = Array of DIALOG file messages(errors) . @SCERR(0)= Number of error(s), UNDEFINED if no errors Foramt: Subscript: Sequential # from 1 to n Piece Description 1 IEN of DIALOG file Returned: 1 if ok, 0 if error COMPONENT/ENTRY POINT: $$PRCL COMPONENT DESCRIPTION: $$PRCL(SC44,SCDATES,SCPOSA,SCUSRA,SCROLEA,SCLIST,SCERR) -- Extrinsic function to return a list of practitioners associated to a clinic in PCMM. There is an association if the practitioner is assigned to a position for the time period and that position has the clinic as its ASSOCIATED CLINIC. Note: Multiple positions can have the same clinic. @SCLIST() = array of practitioners Format: Subscript: Sequential # from 1 to n Piece Description 1 IEN of NEW PERSON file entry (#200) 2 Name of person 3 IEN of TEAM POSITION file (#404.57) 4 Name of Position 5 IEN OF USR CLASS(#8930) of POSITION (#404.57) 6 USR Class Name 7 IEN of STANDARD POSITION (#403.46) 8 Standard Role (Position) Name 9 Activation Date for 404.52 (not 404.59!) 10 Inactivation Date for 404.52 11 IEN of Position Ass History (404.52) 12 IEN of Preceptor Position 13 Name of Preceptor Position @sclist@('scpr',sc200,sctp,scact,scn)="" SCERR() = Array of DIALOG file messages(errors) . Foramt: @SCERR@(0) = Number of errors, undefined if none Subscript: Sequential # from 1 to n Piece Description 1 IEN of DIALOG file Returned: 1 if ok, 0 if error COMPONENT/ENTRY POINT: $$PRPT COMPONENT DESCRIPTION: $$PRPT(DFN,SCDATES,SCPOSA,SCUSRA,SCROLEA,SCPURPA,SCLIST,SCERR) -- Extrinsic function to return a list of practitioners assigned to a patient. The practitioner is assigned to a patient if both the patient and the practitioner are assigned to a position for the time period. SCLIST() = array of practitioners Format: Subscript: Sequential # from 1 to n Piece Description 1 IEN of NEW PERSON file entry (#200) 2 Name of person 3 IEN of TEAM POSITION file (#404.57) 4 Name of Position 5 IEN OF USR CLASS(#8930) of POSITION (#404.57) 6 USR Class Name 7 IEN of STANDARD POSITION (#403.46) 8 Standard Role (Position) Name 9 Activation Date for 404.52 (not 404.59!) 10 Inactivation Date for 404.52 11 IEN of Position Ass History (404.52) 12 IEN of Preceptor Position 13 Name of Preceptor Position SCERR() = Array of DIALOG file messages(errors) . @SCERR(0)= Number of error(s), UNDEFINED if no errors Foramt: Subscript: Sequential # from 1 to n Piece Description 1 IEN of DIALOG file Returned: 1 if ok, 0 if error COMPONENT/ENTRY POINT: $$PTTM COMPONENT DESCRIPTION: $$PTTM(SCTEAM,SCDATES,SCLIST,SCERR) -- Extrinsic function to return a list of patients assigned to a team for a time period. @SCLIST() = array of patients Format: Subscript: Sequential # from 1 to n Piece Description 1 IEN of PATIENT file entry 2 Name of patient 3 IEN of Patient Team Assignment 4 Activation Date 5 Inactivation Date 6 Patient Long ID (SSN) SCERR() = Array of DIALOG file messages(errors) . @SCERR@(0)=number of errors, undefined if none Foramt: Subscript: Sequential # from 1 to n Piece Description 1 IEN of DIALOG file Returned: 1 if ok, 0 if error COMPONENT/ENTRY POINT: $$TMPT COMPONENT DESCRIPTION: $$TMPT(DFN,SCDATES,SCPURPA,SCLIST,SCERR) Extrinsic function to return a list of teams assigned to a patient fo time period. Output: @SCLIST() = array of teams (includes SCTM xref) Format: Subscript: Sequential # from 1 to n Piece Description 1 IEN of TEAM file entry 2 Name of team 3 IEN of file #404.42 (Pt Tm Assignment) 4 current effective date 5 current inactivate date (if any) 6 pointer to 403.47 (purpose) 7 Name of Purpose 8 Is this the pt's PC Team? Subscript: "SCTM",SCTM,IEN ="" SCERR() = Array of DIALOG file messages(errors) . @SCERR@(0) = number of errors, undefined if none Format: Subscript: Sequential # from 1 to n Piece Description 1 IEN of DIALOG file Returned: 1 if ok, 0 if error ; COMPONENT/ENTRY POINT: $$INSTPCTM COMPONENT DESCRIPTION: $$INSTPCTM(DFN,SCEFF) -- Extrinsic function to retrun the institution and team for the patient's prinmary care team for a given date. Returned - 0 if not ok (error), otherwise: Piece# Description 1 Pointer to the File #404.51 2 Name of Team 3 Pointer to File #4 4 Name of Institution VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN - - Pointer to File #2, PATIENT File VARIABLES: SC44 TYPE: Input VARIABLES DESCRIPTION: SC44 - Pointer to File #44, Hospital Location File (clinic) VARIABLES: SCTEAM TYPE: Input VARIABLES DESCRIPTION: SCTEAM - Pointer to File #404.51, TEAM File VARIABLES: SCEFF TYPE: Input VARIABLES DESCRIPTION: SCEFF - Effective Date of interest VARIABLES: SCDATES TYPE: Input VARIABLES DESCRIPTION: SCDATES - Name of date array to define time period as follows: @SCDATES@("BEGIN") = begin date to search (inclusive) [default: TODAY] ("END") = end date to search (inclusive) [default: TODAY] ("INCL") = 1: only use pracitioners who were on team for entire date range 0: anytime in date range [default: 1] VARIABLES: SCUSRA TYPE: Input VARIABLES DESCRIPTION: SCUSRA = Name of array of usr classes to use/exclude @SCUSRA@(ptr)="", where ptr is a pointer to File #8930 if $D(@SCUSRA@("EXCLUDE")) -> list to exclude VARIABLES: SCROLEA TYPE: Input VARIABLES DESCRIPTION: SCROLEA = Name of array of roles/standard positions to include/exclude @SCROLEA@(ptr)="" where ptr is a pointer to File #403.46 if $D(@(SCROLEA@("EXCLUDE")) ->list to exclude VARIABLES: SCPURPA TYPE: Input VARIABLES DESCRIPTION: SCPURPA = Name of array of team purposes to include/exclude @SCPURPA@(ptr)="" where ptr is a pointer to File #403.47 if $D(@SCPURPA@("EXCLUDE")) -> list to exclude VARIABLES: SCLIST TYPE: Output VARIABLES DESCRIPTION: SCLIST = Name of output array (local or ^TMP reference) Example using $$PRTM: >S SCTEAM=1 ;1 is ien of 404.51 entry >S RWD("BEGIN")=DT-30 ;Time period starts 30 days ago >S RWD("END")=DT+30 ;and ends 30 days from now >S RWD("INCL")=0 ;list if active any time in period >W $$PRTM^SCAPMC(SCTEAM,"RWD",,,"RWOUT","RWERR") 1 >ZW RWOUT RWOUT(0)=2 RWOUT(1)=1212^INSLEY,MARCIA L.^1^AAA ROB 1^^^2^PHYSICIAN-PRIMARY CARE^2960627^^1 ^^ RWOUT(2)=10866^WHELAN,ROBERT^2^AAA ROB NURSE^^^6^NURSE (RN)^2960627^^2^1^AAA ROB 1 RWOUT("SCPR",1212,1,2960627,1)= RWOUT("SCPR",10866,2,2960627,2)= COMPONENT/ENTRY POINT: $$PTPR COMPONENT DESCRIPTION: VARIABLES: $$PTPR(SC200,SCDATES,SCPURPA,SCROLEA,SCLIST,SCERR,SCYESCL)- Extrinsic function call to return an array of patients for a practitioner within a time period. Output: SCLIST() = array of patients Format: Subscript: Sequential # from 1 to n Piece Description 1 IEN of PATIENT file entry 2 Name of patient 3 IEN of Pt Team Posit Asment if position=source 4 Activation Date 5 Inactivation Date 6 Source 1=Clinic, Null=Position 7 IEN of Clinic if clinic=source SCERR() = Array of DIALOG file messages(errors) . @SCERR@(0) = number of errors, undefined if none Format: Subscript: Sequential # from 1 to n Piece Description 1 IEN of DIALOG file Returned: 1 if ok, 0 if error VARIABLES: SC200 TYPE: Input VARIABLES DESCRIPTION: ien of NEW PERSON file(#200) [required] VARIABLES: SCDATES TYPE: Input VARIABLES DESCRIPTION: SCDATES("BEGIN") = begin date to search (inclusive) [default: TODAY] ("END") = end date to search (inclusive) [default: TODAY] ("INCL") = 1: only use patients who were assigned to team for entire date range 0: anytime in date range [default: 1] VARIABLES: SCPURPA TYPE: Input VARIABLES DESCRIPTION: array of pointers to team purpose file 403.47 ; if none are defined - returns all teams ; if @SCPURPA@('exclude') is defined - exclude listed teams VARIABLES: SCROLEA TYPE: Input VARIABLES DESCRIPTION: array of pointer to 403.46 (per SCPURPA) VARIABLES: SCLIST TYPE: Input VARIABLES DESCRIPTION: array name to store list [ex. ^TMP("SCPT",$J)] VARIABLES: SCERR TYPE: Input VARIABLES DESCRIPTION: array NAME to store error messages. NUMBER: 1929 IA #: 1929 FILE NUMBER: 58.1 GLOBAL ROOT: PSI(58.1, DATE CREATED: FEB 12, 1997 CUSTODIAL PACKAGE: AUTO REPLENISHMENT/WARD STOCK CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1929 ID: PSI(58.1, GLOBAL REFERENCE: PSI(58.1,D0,0) FIELD NUMBER: .01 FIELD NAME: AREA OF USE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSI(58.1,D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: ITEM LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: STOCK LEVEL LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 30 FIELD NAME: INACTIVATION DATE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 10 FIELD NAME: LOCATION LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSI(58.1,D0,1,D1,2,D2,0) FIELD NUMBER: .01 FIELD NAME: TYPE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Controlled Substances routines PSDTRA* need read access to #58.1 to copy data from an AREA OF USE to a NARCOTIC AREA OF USE. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23117103 SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 1930 IA #: 1930 FILE NUMBER: 59.7 GLOBAL ROOT: PS(59.7, DATE CREATED: FEB 13, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1930 ID: PS(59.7, GLOBAL REFERENCE: PS(59.7,D0,49.99) FIELD NUMBER: 49.98 FIELD NAME: DATE OP INSTALLED LOCATION: 49.99;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(59.7,D0,70) FIELD NUMBER: 71 FIELD NAME: DATE V2 CS/DA CONVERSION LOCATION: 70;4 ACCESS: Direct Global R/W & w/Fileman GENERAL DESCRIPTION: Controlled Substances needs to check the DATE OP INSTALLED field before posting outpatient prescriptions and the DATE V2 CS/DA CONVERSION field before doing a conversion in a post-init. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23080192 SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 1931 IA #: 1931 FILE NUMBER: 51.5 GLOBAL ROOT: DIC(51.5, DATE CREATED: FEB 13, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1931 ID: DIC(51.5, GLOBAL REFERENCE: DIC(51.5,D0,0) FIELD NUMBER: .01 FIELD NAME: ABBREVIATION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Various pharmacy packages need read access to this file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23073775 SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham SUBSCRIBING PACKAGE: NATIONAL DRUG FILE ISC: Birmingham SUBSCRIBING PACKAGE: AUTO REPLENISHMENT/WARD STOCK ISC: Birmingham SUBSCRIBING PACKAGE: CMOP ISC: Birmingham SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 1932 IA #: 1932 FILE NUMBER: 393.3 GLOBAL ROOT: VAS(393.3, DATE CREATED: FEB 13, 1997 CUSTODIAL PACKAGE: INCOMPLETE RECORDS TRACKING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1932 ID: VAS(393.3, GENERAL DESCRIPTION: This will allow Text Integration Utilities (TIU) to point to the IRT TYPE OF DEFICIENCY file #393.3. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22888248 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES NUMBER: 1934 IA #: 1934 DATE CREATED: FEB 14, 1997 CUSTODIAL PACKAGE: AUTOMATED MED INFO EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA1934 ORIGINAL NUMBER: 1933 GENERAL DESCRIPTION: Distribute AMIE input template. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23159831 COMPONENT/ENTRY POINT: DVBA C ADD 2507 PAT COMPONENT DESCRIPTION: Input Template: DVBA C ADD 2507 PAT Compiled Routine: DVBAXA File: 2 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 1936 IA #: 1936 DATE CREATED: FEB 14, 1997 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Washington USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA1936 ORIGINAL NUMBER: 1933 GENERAL DESCRIPTION: Distribute IB input template. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23159831 COMPONENT/ENTRY POINT: IB SCREEN1 COMPONENT DESCRIPTION: Input Template: IB SCREEN1 Compiled Routine: IBXSC1 File: 399 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 1937 IA #: 1937 FILE NUMBER: 771 GLOBAL ROOT: HL(771, DATE CREATED: FEB 18, 1997 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1937 - EC HL7 INTERFACE ID: HL(771, GLOBAL REFERENCE: HL(771,D0,0) FIELD NUMBER: 4 FIELD NAME: MAIL GROUP LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Notifications of any problems that occur while generating or processing messages will be sent to the mail group specified in this field. GENERAL DESCRIPTION: The Event Capture HL7 internal interface will reference the following data from the HL7 APPLICATION PARAMETER FILE (#771). In File 771, the Event Capture HL7 internal interface will reference the current mail group from field (#4). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23008655 SUBSCRIBING PACKAGE: EVENT CAPTURE ISC: Birmingham NUMBER: 1938 IA #: 1938 DATE CREATED: FEB 19, 1997 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRVSITE NAME: GMRVSITE ID: GMRVSITE GENERAL DESCRIPTION: The Nursing package can use the DEFAULT and CHAR entry points in the GMRVSITE routine of the Vitals/Measurements package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23193984 COMPONENT/ENTRY POINT: DEFAULT COMPONENT DESCRIPTION: The Change Default Qualifiers for Temp./Pulse [NURCPE-VIT VMQUALITY] option can call this entry point to change default qualifiers for temperature and pulse entries in the GMRV VITAL CATEGORY (#120.53) file. COMPONENT/ENTRY POINT: CHAR COMPONENT DESCRIPTION: The Enter/Edit Vitals Qualifiers [NURCPE-VIT VMSITE] option can call this entry point to configure the GMRV VITAL QUALIFIER (#120.52) file entries. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1939 IA #: 1939 FILE NUMBER: 772 GLOBAL ROOT: HL(772, DATE CREATED: FEB 19, 1997 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1938 - EC HL7 INTERFACE ID: HL(772, GLOBAL REFERENCE: HL(772,D0,'IN',D01,0) FIELD NUMBER: 200 FIELD NAME: MESSAGE TEXT LOCATION: IN;0 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The actual text of the incoming HL7 message(s). GENERAL DESCRIPTION: The Event Capture HL7 internal interface will reference the following data from the HL7 MESSAGE TEXT FILE (#772). In File 772, the Event Capture HL7 internal interface will reference information related to the MSH and MSA segments from the MESSAGE TEXT field (#200). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23008655 SUBSCRIBING PACKAGE: EVENT CAPTURE ISC: Birmingham NUMBER: 1940 IA #: 1940 DATE CREATED: FEB 19, 1997 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRVCAQU NAME: GMRVCAQU ID: GMRVCAQU GENERAL DESCRIPTION: The Nursing package can call EN1^GMRVCAQU in the Vitals/Measurements package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23193997 COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: The Display Vitals Category/Qualifier Table [NURCPE-VIT CAT/QUAL TABLE] option can call this entry point to display a table of categories and qualifiers for various vitals/measurements (e.g., blood pressure). SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1941 IA #: 1941 FILE NUMBER: 1 GLOBAL ROOT: DD( DATE CREATED: FEB 21, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: SETTING DD NODES ID: DD( GLOBAL REFERENCE: DD(357.3,2.02,0) FIELD NUMBER: ALL ACCESS: Direct Global Write & w/Fileman GLOBAL REFERENCE: DD(358.3,2.02,0) FIELD NUMBER: ALL ACCESS: Direct Global Write & w/Fileman GLOBAL REFERENCE: DD(357.951,2.02,0) FIELD NUMBER: ALL ACCESS: Direct Global Write & w/Fileman GENERAL DESCRIPTION: This integration agreement is for a one time use for AICS v3.0 to set the following three DD nodes. These nodes point to the Expressions file (757.01) which has changed global locations in Lexicon Utility v2.0 from ^GMP to ^LEX. Approximately half of VAMC's have installed Lexicon Utility v2.0. The setting of these nodes will set the Data Dictionaries to the correct global location for the version of Lexicon Utility. I $D(^LEX) D .S ^DD(357.3,2.02,0)="CLINICAL LEXICON ENTRY^P757.01'^LEX(757.01,^2;2^Q" .S ^DD(358.3,2.02,0)="CLINICAL LEXICON ENTRY^P757.01'^LEX(757.01,^2;2^Q" .S ^DD(357.951,2.02,0)="CLINICAL LEXICON^P757.01'^LEX(757.01,^2;2^Q" .D MES^XPDUTL(">>> AICS Data Dictionaries updated to use Lexicon Utility version 2.0") E D MES^XPDUTL(">>> AICS Data Dictionaries updated to use Clinical Lexicon Utility version 1.0") STATUS: Active DURATION: Next Version MAIL MESSAGE: 23159100 GOOD ONLY FOR VERSION: AICS V3.0 SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring NUMBER: 1945 IA #: 1945 FILE NUMBER: 404.51 GLOBAL ROOT: SCTM(404.51, DATE CREATED: MAR 03, 1997 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1945 ID: SCTM(404.51, GLOBAL REFERENCE: SCTM(404.51,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: O;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: DSS Extracts references the following data from the TEAM file (#404.51). A DSS option, "Primary Care Team Print", prints an alphabetical list of all primary care teams and the IEN for each team. The intent of the option is to provide help for building primary care teams on the commercial DSS system. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23265098 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1946 IA #: 1946 DATE CREATED: MAR 04, 1997 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LRCAPDSS NAME: DBIA1946 ID: LRCAPDSS GENERAL DESCRIPTION: DSS Extracts uses the Lab Service LRCAPDSS routine. For a date range, the LRCAPDSS routine examines the WKLD DATA file (#64.1) and stores appropriate data into the WKLD LOG FILE file (#64.03) for use by the DSS Laboratory Extract. Variables: LRSDT Input Start Date LREDT Input End Date Prior to running this routine, the calling routine will purge the WKLD LOG FILE file (#64.03). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23312739 COMPONENT/ENTRY POINT: LRCAPDSS SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1947 IA #: 1947 FILE NUMBER: 60 GLOBAL ROOT: LAB(60, DATE CREATED: MAR 04, 1997 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1947 ID: LAB(60, GLOBAL REFERENCE: LAB(60, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 64 FIELD NAME: NATIONAL VA LAB CODE LOCATION: 64;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 64.1 FIELD NAME: RESULT NLT CODE LOCATION: 64;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: DSS Extracts references and points to the following data from the LABORATORY TEST file (#60). DSS accesses the NAME field using a direct global read for the "Print DSS Lab Test Datasheet" option and for generating DSS lab feeder keys. The DSS Extracts LABORATORY EXTRACT file (#727.813) contains a field, TEST, and the DSS LAB TESTS file (#727.2) contains a multiple field, LOCAL LAB TEST NAME, which point to the LABORATORY TEST file (#60). The DSS Lab Results Extract references the NATIONAL VA LAB CODE field. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23312936 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham SUBSCRIBING PACKAGE: VBECS NUMBER: 1948 IA #: 1948 FILE NUMBER: 63 GLOBAL ROOT: LR( DATE CREATED: MAR 04, 1997 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1948 ID: LR( GLOBAL REFERENCE: LR(D0,0) FIELD NUMBER: .01 FIELD NAME: LRDFN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: PARENT FILE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: NAME LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: DSS reads the entire zero node into a local variable. The fields above are used. GENERAL DESCRIPTION: DSS Extracts references the following data from the LAB DATA file (#63). These fields are used in the DSS Lab Extract for the original/old format which does not use LMIP codes. With the FY'98 release of DSS Extracts, this should no longer be needed. Therefore, this IA is to be in effect for no more than 3 years, with a sunset clause of 2000. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: 2000 MAIL MESSAGE: 23313195 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: VBECS NUMBER: 1949 IA #: 1949 FILE NUMBER: 64 GLOBAL ROOT: LAM( DATE CREATED: MAR 04, 1997 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: LAB DSS EXTRACT ID: LAM( CREATOR: SCHLEHUBER,CAMERON GLOBAL REFERENCE: LAM(D0,0) FIELD NUMBER: .01 FIELD NAME: PROCEDURE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: WKLD CODE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LAM(D0,5,D1,1,D2,0 FIELD NUMBER: 3 FIELD NAME: TEST ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LAM(D0,5,D1,1,D2,1 FIELD NUMBER: 4 FIELD NAME: LOINC CODE ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LAM('AI' GLOBAL DESCRIPTION: Access to 'AI' cross reference using LOINC CODE IEN (reference DBIA #5547). GENERAL DESCRIPTION: DSS Extracts references the following data from the WKLD CODE file (#64). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23313278 KEYWORDS: LOINC SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham DATE ACTIVATED: JUN 06, 2011 DATE/TIME EDITED: JUN 06, 2011@11:31 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: YORTY,ROBERY WITH CONCURRENCE OF: CORONA,JOSE DATE/TIME EDITED: JUN 06, 2011@12:31 ACTION: APPROVED AT THE REQUEST OF: ANZALDUA,CAROL WITH CONCURRENCE OF: YORTY,ROBERT NUMBER: 1950 IA #: 1950 FILE NUMBER: 64.03 GLOBAL ROOT: LRO(64.03, DATE CREATED: MAR 04, 1997 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1950 ID: LRO(64.03, GLOBAL REFERENCE: LRO(64.03,D0,0) FIELD NUMBER: .01 FIELD NAME: SEQ NUMBER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: PROVIDER LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: PATIENT NAME LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: DATE COMPLETE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: REPORTING SITE LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5 FIELD NAME: LOCATION TYPE LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6 FIELD NAME: ACCESSION AREA LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7 FIELD NAME: LAB TEST NAME LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 8 FIELD NAME: URGENCY OF TEST LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 9 FIELD NAME: TREATING SPECIALTY LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 10 FIELD NAME: WKLD CODE LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 11 FIELD NAME: LRIDT LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 12 FIELD NAME: DATE COLLECTED LOCATION: 0;13 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 13 FIELD NAME: DATE ORDERED LOCATION: 0;14 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 14 FIELD NAME: HOSPITAL LOCATION LOCATION: 0;15 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 15 FIELD NAME: ACCESSION FILE INDEX LOCATION: 0;16 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 16 FIELD NAME: SPECIMEN LOCATION: 0;17 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 17 FIELD NAME: DATE OF EXTRACT LOCATION: 1;0 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LRO(64.03,D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: DATE OF EXTRACT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: EXTRACT START DATE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: EXTRACT END DATE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: COMPILE COMPLETE DATE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: USER LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: The above fields are used from the DATE OF EXTRACT multiple. GENERAL DESCRIPTION: DSS Extracts references the following data from the WKLD LOG FILE file (#64.03). This LABORATORY file has been converted for exclusive use by DSS software to collect laboratory workload for DSS defined products. In addition to the direct global read references indicated below, DSS has complete direct global read and write access into the entire WKLD LOG FILE file (#64.03). The entire file is KILLed from the system prior to DSS calling a Lab API which populates file 64.03. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25459684 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany NUMBER: 1951 IA #: 1951 FILE NUMBER: 68 GLOBAL ROOT: LRO(68 DATE CREATED: MAR 04, 1997 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: RECONSTRUCT ACCESSION NODE ID: LRO(68 CREATOR: CORONA,JOSE GLOBAL REFERENCE: LRO(68,D0,0) FIELD NUMBER: .01 FIELD NAME: AREA LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The accession area of the Lab. FIELD NUMBER: .09 FIELD NAME: ABBREVIATION LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Abbreviation for the accession area. FIELD NUMBER: .19 FIELD NAME: LAB DIVISION LOCATION: 0;19 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field will be used to determine which lab division a particular accession area belongs. GLOBAL REFERENCE: LRO(68,D0,1,D1,1,D2,0) FIELD NUMBER: 6.5 FIELD NAME: PROVIDER LOCATION: 0;8 ACCESS: Read w/Fileman FIELD DESCRIPTION: The internal number of the provider requesting the test(s) is stored here. GLOBAL REFERENCE: LRO(68,D0,1,D1,1,D2,.4) FIELD NUMBER: 26 FIELD NAME: DIV LOCATION: .4;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: DSS Extracts points to and references the following data from the ACCESSION file (#68). The DSS Extracts LABORATORY EXTRACT file (#727.813) contains a field, ACCESSION AREA, which is a pointer to the ACCESSION file (#68). Direct global read of the 'B' Cross Reference is also permited into the ACCESSION file (#68). Blood Bank Data =============== DSS uses LAB DATA file (#63) and Blood Bank's node ^LR(D0,"BB",D1,0) to extract blood bank records. We then use ACCESSION NUMBER field (#.06) to identify ACCESSION file (#68) corresponding entry. This allows us to identify provider and division associated with patient blood bank record. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25455125 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany DBA Comments: JSHARVEY 20060125/ DEACTIVATED FOR API EDITS JSHARVEY 20060129/ REACTIVATED AFTER REFORMATTING DATE ACTIVATED: JAN 29, 2007 DATE/TIME EDITED: JAN 25, 2007@09:17 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CORONA,JOSE DATE/TIME EDITED: JAN 29, 2007@22:59 ACTION: APPROVED AT THE REQUEST OF: CORONA,JOSE WITH CONCURRENCE OF: MORTON,RANDY NUMBER: 1953 IA #: 1953 DATE CREATED: MAR 04, 1997 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LRCAPDAR NAME: DBIA1953 ID: LRCAPDAR GENERAL DESCRIPTION: DSS Extracts uses the Lab Service LRCAPDAR routine. For a date range, the LRCAPDAR routine examines the LAB DATA file (#63) and stores appropriate data into the LAB DSS LAR EXTRACT file (#64.036) for use by the DSS Laboratory Results Extract. Variables: LRSDT Input Start Date LREDT Input End Date Prior to running this routine, the calling routine will purge the LAB DSS LAR EXTRACT file (#64.036). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23313478 COMPONENT/ENTRY POINT: LRCAPDAR SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1954 IA #: 1954 FILE NUMBER: 64.036 GLOBAL ROOT: LAR(64.036, DATE CREATED: MAR 04, 1997 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1954 ID: LAR(64.036, GLOBAL REFERENCE: LAR(64.036,D0,0) FIELD NUMBER: .01 FIELD NAME: SEQ # LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: POINTED TO FILE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: DFN LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: DATE ORDERED LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: TIME ORDERED LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5 FIELD NAME: DATE RESULTS AVAIL LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6 FIELD NAME: TIME RESULTS AVAIL LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7 FIELD NAME: SPECIMEN LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 8 FIELD NAME: RESULTS LOCATION: 1;0 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 9 FIELD NAME: EXTRACTION DATA LOCATION: 2;0 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LAR(64.036,D0,1,0) FIELD NUMBER: .01 FIELD NAME: DSS TEST NUMBER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: RESULTS LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: HI/LO FLAG LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: NTL CODE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: The above fields are used from the RESULTS multiple. GLOBAL REFERENCE: LAR(64.036,D0,2,0) FIELD NUMBER: .01 FIELD NAME: EXTRACTION DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: EXTRACTION START DATE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: EXTRACTION END DATE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: COMPLETED D/T LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: USER LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: The above fields are used from the EXTRACTION DATA multiple. GENERAL DESCRIPTION: DSS Extracts references the following data from the LAB DSS LAR EXTRACT file (#64.036). This LABORATORY file has been created for exclusive use by DSS software to collect laboratory clinical data for the DSS Lab Results Extract. In addition to the direct global read references indicated below, DSS has complete direct global read and write access into the entire LAB DSS LAR EXTRACT file (#64.036). The entire file is KILLed from the system prior to DSS calling a Lab API which populates file 64.036. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25459200 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany NUMBER: 1955 IA #: 1955 FILE NUMBER: 727.2 GLOBAL ROOT: ECX(727.2 DATE CREATED: MAR 04, 1997 CUSTODIAL PACKAGE: DSS EXTRACTS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1955 ID: ECX(727.2 GLOBAL REFERENCE: ECX(727.2,D0,1,0) FIELD NUMBER: 2 FIELD NAME: SOURCE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: The above field is used from the DSS LAB TEST multiple (727.21). GLOBAL REFERENCE: ECX(727.2,D0,1,D1,LOC,0) FIELD NUMBER: .01 FIELD NAME: LOCAL LAB TEST NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: The above field is used from the LOCAL LAB TEST NAME multiple (727.211). GLOBAL REFERENCE: ECX(727.2,D0,BL,0) FIELD NUMBER: .01 FIELD NAME: BLOOD SPECIMEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: The above field is used from the BLOOD SPECIMEN multiple (727.22). GLOBAL REFERENCE: ECX(727.2,D0,UR,0) FIELD NUMBER: .01 FIELD NAME: URINE SPECIMEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: The above field is used from the URINE SPECIMEN multiple (727.23). GENERAL DESCRIPTION: Lab Service references the following data from the DSS LAB TESTS file (#727.2). This reference is made from the LRCAPDAR routine written by Lab Service to provide lab clinical results data to DSS. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23327716 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 1956 IA #: 1956 FILE NUMBER: 49 GLOBAL ROOT: DIC(49, DATE CREATED: MAR 06, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1956 ID: DIC(49, GLOBAL REFERENCE: DIC(49,D0,730) FIELD NUMBER: 730 FIELD NAME: NATIONAL SERVICE LOCATION: 730;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Supported DBIA #10093 provides FileMan read access to all fields of the SERVICE/SECTION file (#49). The DSS Surgery Extract uses a direct global read on the NATIONAL SERVICE field (730) for the purpose of determining the service to which the attending surgeon is assigned. The technical description follows: ATTENDING'S SERVICE is a pointer to the NATIONAL SERVICE file (#730). Derived from the SERVICE/SECTION field (29) in the NEW PERSON file (#200) for the ATTENDING SURGEON field (13) in the SURGERY EXTRACT file (#727.811) which is a pointer to the SERVICE/SECTION file (#49). The pointer value identifies the NATIONAL SERVICE field (730) in the SERVICE/SECTION file (#49) which points to the NATIONAL SERVICE file (#730). Therefore, DSS Extracts references the following data from the SERVICE/SECTION file (#49). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23327584 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Birmingham NUMBER: 1957 IA #: 1957 FILE NUMBER: 1 GLOBAL ROOT: DIC DATE CREATED: MAR 10, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: File Security Codes ID: DIC GENERAL DESCRIPTION: The Gen. Med. Rec. - I/O (Intake and Output), Gen. Med. Red. - Vitals (Vitals/Measurements), Nursing Service and Text Generator packages have permission to set the security nodes (i.e., "DD", "RD", "DEL", "LAYGO", and "WR") in FILE 1 for those files within the package's number range. For example: S ^DIC(210,0,"DD")="@" Package Number Range ------- ------------ Intake & Output 126-126.95 Vitals/Measurments 120.5-120.57 Nursing Service 210-219.7 Text Generator 124-124.3 With the next release of each package, the installation process will allow the site to change its file security codes to match the codes as they appear in the documentation. The site can answer YES to change their file security codes to match the package documentation or NO to leave them as is. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23383282 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING PACKAGE: GEN. MED. REC. - I/O ISC: Hines SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines SUBSCRIBING PACKAGE: GEN. MED. REC. - GENERATOR ISC: Hines NUMBER: 1958 IA #: 1958 DATE CREATED: MAR 19, 1997 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Salt Lake City USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LR70SUM NAME: DBIA1958 ID: LR70SUM GENERAL DESCRIPTION: This API will get Lab results for a given patient based on various input parameters. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23609572 COMPONENT/ENTRY POINT: EN(Y,DFN,SDATE,EDATE,COUNT,GIOM,SUBHEAD) COMPONENT DESCRIPTION: This is a 'silent' call. No prompts are given. The results are formatted and stored in the global: ^TMP("LRC",$J) "CH" type results are stored in the pre-defined cumulative format. Headers for each format are stored in: ^TMP("LRH",$J,NAME)=line # An index of where tests can be found in a report are found in: ^TMP("LRT",$J,print name)=header^line # of 1st occurrence Test entries without a header means that the test is defined in the report, but there are no results. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Tells the calling routine where the data is stored. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal number of the patient as stored in ^DPT(DFN VARIABLES: SDATE TYPE: Input VARIABLES DESCRIPTION: Start date to search for results (optional) VARIABLES: EDATE TYPE: Input VARIABLES DESCRIPTION: EDATE=End date to search for results (optional) VARIABLES: COUNT TYPE: Input VARIABLES DESCRIPTION: COUNT=Count of results to send (optional) VARIABLES: GIOM TYPE: Input VARIABLES DESCRIPTION: GIOM=Right margin - default 80 (optional) VARIABLES: SUBHEAD TYPE: Input VARIABLES DESCRIPTION: SUBHEAD=Array of subheaders from file 64.5, misc, micro & AP to show results. Null param = get all results COMPONENT/ENTRY POINT: GET64(Y) COMPONENT DESCRIPTION: This entry point will get a list, in Y(name) of all the minor headers from the Lab Reports file. It also includes in the Y array the names of other report headers not included in the Lab Reports file such as S Y("MISCELLANEOUS TESTS")="" S Y("MICROBIOLOGY")="" S Y("BLOOD BANK")="" S Y("CYTOPATHOLOGY")="" S Y("SURGICAL PATHOLOGY")="" S Y("EM")="" This call is intended to be used with EN^LR7OSUM when it is necessary to pre-select a specific area within Lab for retreiving results. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: This is the name of the array that the report headers are returned in. SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 1962 IA #: 1962 FILE NUMBER: 63 GLOBAL ROOT: LR(DO,0 DATE CREATED: MAR 21, 1997 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1962 ID: LR(DO,0 GLOBAL REFERENCE: LR(DO,'AU') FIELD NUMBER: 14.7 FIELD NAME: AUTOPSY RELEASE DATE/TIME LOCATION: AU;15 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Autopy release date/time FIELD NUMBER: 14 FIELD NAME: AUTOPSY ACC # LOCATION: AU;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Autopsy accession number FIELD NUMBER: 13.5 FIELD NAME: RESIDENT PATHOLOGIST LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: RESIDENT PATHOLOGIST FIELD NUMBER: 11 FIELD NAME: AUTOPSY DATE/TIME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: AUTOPSY DATE/TIME GLOBAL DESCRIPTION: Autopsy node. GLOBAL REFERENCE: LR('AAUA', GLOBAL DESCRIPTION: Cross reference for Autopsy by year, accession area abbreviation, accession number, lrdfn. GLOBAL REFERENCE: LR('ASPA', GLOBAL DESCRIPTION: Cross reference for Surical pathology, accession area abbreviation, accession number, lrdfn. GLOBAL REFERENCE: LR('ACYA' GLOBAL DESCRIPTION: Cross reference for Cytology. LR('ACYA',YEAR,ACCESSION AREA ABBREVIATION,ACCESSION NUMBER, LRDFN GLOBAL REFERENCE: LR('AEMA', GLOBAL DESCRIPTION: Cross reference for Electron Microscopy LR('AEMA',YEAR,ACCESSION AREA ABBREVIATION, ACCESSION NUMBER,LRDFN GLOBAL REFERENCE: LR(D0,0) FIELD NUMBER: .02 FIELD NAME: PARENT FILE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Pointer to file of file - Patient file or Referal file. FIELD NUMBER: .03 FIELD NAME: NAME LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Patient name. GLOBAL DESCRIPTION: Root node of file 63 GLOBAL REFERENCE: LR(DO,'SP',D1,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME SPECIMEN TAKEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Date & time speciment taken. FIELD NUMBER: .02 FIELD NAME: PATHOLOGIST LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Pathologist FIELD NUMBER: .06 FIELD NAME: SURGICAL PATH ACC # LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Surgical Pathology accession number. GLOBAL REFERENCE: LR(D0,'SP',D1,.1,D2,0) FIELD NUMBER: .01 FIELD NAME: SPECIMEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Specimen FIELD NUMBER: 2005 FIELD NAME: Image LOCATION: 2005 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Image pointer GLOBAL REFERENCE: LR(DO,'AY',D1,0) FIELD NUMBER: .01 FIELD NAME: AUTOPSY ORGAN/TISSUE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: AUTOPSY ORGAN/TISSUE - Specimen FIELD NUMBER: 2005 FIELD NAME: IMAGE (GROSS) LOCATION: 2005 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: IMAGE POINTER FIELD NUMBER: 2005.1 FIELD NAME: IMAGE (MICROSCOPIC) LOCATION: 2005.1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: IMAGE POINTER GLOBAL DESCRIPTION: AUTOPSY ORGAN/TISSUE subfile. GLOBAL REFERENCE: LR(DO,'CY',D1,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME SPECIMEN TAKEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: DATE/TIME SPECIMEN TAKEN FIELD NUMBER: .02 FIELD NAME: PATHOLOGIST LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: PATHOLOGIST FIELD NUMBER: .06 FIELD NAME: CYTOPATH ACC # LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: CYTOPATH ACCESSION NUMBER. GLOBAL REFERENCE: LR(DO,'CY',D1,.1,D2,0) FIELD NUMBER: .01 FIELD NAME: SPECIMEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: SPECIMEN FIELD NUMBER: 2005 FIELD NAME: IMAGE LOCATION: 2005 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: IMAGE POINER GLOBAL REFERENCE: LR(DO,'EM',D1,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME SPECIMEN TAKEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: DATE/TIME SPECIMEN TAKEN FIELD NUMBER: .02 FIELD NAME: PATHOLOGIST LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: PATHOLOGIST FIELD NUMBER: .06 FIELD NAME: EM ACC # LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: EM ACCESSION NUMBER GLOBAL REFERENCE: LR(DO,'EM',D1,.1,D2,0) FIELD NUMBER: .01 FIELD NAME: SPECIMEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Specimen. FIELD NUMBER: 2005 FIELD NAME: IMAGE LOCATION: 2005 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Image pointer GLOBAL DESCRIPTION: Electron Microscopy sub file. GENERAL DESCRIPTION: This request is for referencing/reading and writing the Image field in the Laboratory Data file 63. Imaging saves Image pointers in the following sub-field of the Lab Data file: For Autopsy Images: Lab Data sub-file: DD(63.2,0) = AUTOPSY ORGAN/TISSUE SUB-FIELD^NL^2005.1^9 sub-fields: DD(63.2,2005,0) = IMAGE (GROSS)^63.28P^^2005;0 DD(63.2,2005.1,0) = IMAGE (MICROSCOPIC)^63.45P^^2005.1;0 For Surgical Pathology Images: Lab Data sub-file: DD(63.08,0) = SURGICAL PATHOLOGY SUB-FIELD^NL^2005^38 Sub-field: DD(63.08,2005,0) = IMAGE^63.82005P^^2005;0 For Cytology Images: Lab Data sub-file: DD(63.09,0) = CYTOPATHOLOGY SUB-FIELD^NL^2005^34 Sub-field: DD(63.09,2005,0) = IMAGE^63.92005P^^2005;0 For Electron Microcopy DD(63.02,0) = EM SUB-FIELD^NL^2005^32 Sub-field: DD(63.02,2005,0) = IMAGE^63.22005P^^2005;0 Reading of this file is required to verify the Lab file's references, saved during image capture, needed for displaying lab reports. Write access is needed during image capture to save the image pointer in the appropriate Lab accession area (SP, CY, etc.). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32354703 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: This request is needed for referencing/reading Lab Data global nodes and writing the Image pointer in the appropriate Image field. To be used for setting Image pointers and for verification of Image pointers (set during image capture) and for report dislay. NUMBER: 1963 IA #: 1963 FILE NUMBER: 68 GLOBAL ROOT: LRO(68 DATE CREATED: MAR 21, 1997 CUSTODIAL PACKAGE: LAB SERVICE USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1963 ID: LRO(68 GLOBAL REFERENCE: LRO(68,DO,0) FIELD NUMBER: .01 FIELD NAME: AREA LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: ACCESSION AREA FIELD NUMBER: .09 FIELD NAME: ABBREVIATION LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: ACCESSION AREA ABBREVIATION FIELD NUMBER: .02 FIELD NAME: LR SUBSCRIPT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The subscript where the data is stored..."SP","CY",etc. GENERAL DESCRIPTION: The purpose of this request is to provide the Imaging package access to read the Laboratory Accession file for image capture. Image capture for Radiology will require the person to provide an Accession area, Accession year and Accession number. These entries are used to verify the existence of the Lab entry and to display a list of specimens for the accession number provided. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23609611 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: VBECS SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD DBA Comments: 5/24/12-VPR added as a subscriber for VPR*1.0 - read (LRO(68) .01 Name). DATE/TIME EDITED: MAY 24, 2012@15:01 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: ANZALDUA,CAROL NUMBER: 1965 IA #: 1965 DATE CREATED: MAR 22, 1997 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRYMNT NAME: GMRYMNT ID: GMRYMNT GENERAL DESCRIPTION: The Nursing Service package has permission to call the GMRYMNT routine in order to display or print its End of Shift report. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23548890 COMPONENT/ENTRY POINT: SELSITE COMPONENT DESCRIPTION: This entry point extracts all current and discontinued IV sites used within the last 24 hours. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The calling routine must have DFN defined. VARIABLES: GMRXY TYPE: Output VARIABLES DESCRIPTION: Contains all current and discontinued IV sites used within the last 24 hours. SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines NUMBER: 1966 IA #: 1966 FILE NUMBER: 4.2 GLOBAL ROOT: DIC(4.2 DATE CREATED: MAR 25, 1997 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1966 ID: DIC(4.2 GLOBAL REFERENCE: DIC(4.2, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23415626 SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Albany SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland SUBSCRIBING DETAILS: Parameter Tools references 4.2 to store system level parameters. SUBSCRIBING PACKAGE: CMOP ISC: Birmingham SUBSCRIBING PACKAGE: HEALTH SUMMARY SUBSCRIBING PACKAGE: HEALTH LEVEL SEVEN SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING DETAILS: Effective with Patch OR*3*401- change to routine ORKMGR to create an error message that could occur when a user uses option [ORK EDITABLE BY USER]. DBA Comments: 02/06/15-DT: VistA Maintenance, David Elwell, provided MailMan concurrence for Order Entry Results Reporting (OE\RR) package), Mark Augustiniak developer, to do a fileman read of the .01 field of file 4.2 [DOMAIN]. DATE/TIME EDITED: FEB 06, 2015@11:16 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: AUGUSTINIAK,MARK WITH CONCURRENCE OF: ELWELL,DAVID NUMBER: 1967 IA #: 1967 FILE NUMBER: 51.5 GLOBAL ROOT: DIC(51.5 DATE CREATED: MAR 27, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1967 ID: DIC(51.5 GLOBAL REFERENCE: DIC(51.5,D0) FIELD NUMBER: .01 FIELD NAME: ABBREVIATION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: EXPANSION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This data is accessed when a drug is marked for CMOP. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23538679 SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 1968 IA #: 1968 DATE CREATED: MAR 27, 1997 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSONEW2 NAME: DBIA1968 ID: PSONEW2 GENERAL DESCRIPTION: In the CMOP routine PSXEDIT, a call is made to EN1^PSONEW2 to complete the editing of a prescription. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23527915 COMPONENT/ENTRY POINT: EN1 VARIABLES: PSORXED TYPE: Output SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 1969 IA #: 1969 DATE CREATED: MAR 27, 1997 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSORXL NAME: DBIA1969 ID: PSORXL GENERAL DESCRIPTION: The CMOP package calls the Outpatient Pharmacy routine, PSORXL in order to print prescription labels at the medical center pharmacy. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23527956 COMPONENT/ENTRY POINT: D1 COMPONENT/ENTRY POINT: QLBL VARIABLES: PPL TYPE: Output SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 1970 IA #: 1970 DATE CREATED: MAR 27, 1997 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOSURST NAME: DBIA1970 ID: PSOSURST GENERAL DESCRIPTION: The CMOP package makes a call to the Outpatient Pharmacy routine, PSOSURST in order to reset and print pharmacy labels. This call is made when the user selects the option to reset and print window labels. There aren't any I/O variables. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23528399 GOOD ONLY FOR VERSION: 6 COMPONENT/ENTRY POINT: START COMPONENT DESCRIPTION: No variables are passed with this call. SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 1971 IA #: 1971 DATE CREATED: MAR 27, 1997 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOSULBL NAME: DBIA1971 ID: PSOSULBL GENERAL DESCRIPTION: The CMOP package makes a call to the Outpatient Pharmacy routine, PSOSULBL. This call is made from the CMOP routine, PSXRSUS when the user selects the option to Print Standard Suspense at the medical center pharmacy. There aren't any I/O variables in this call. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23528099 COMPONENT/ENTRY POINT: ASK COMPONENT DESCRIPTION: No variables are passed with this call. SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 1972 IA #: 1972 DATE CREATED: MAR 27, 1997 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOSUCHG NAME: DBIA1972 ID: PSOSUCHG GENERAL DESCRIPTION: The CMOP package makes a call to the Outpatient Pharmacy routine, PSOSUCHG. This call is made when a user is using the Change Suspense Date option on the Suspense Menu for Outpatient Pharmacy. Any Rx that is entered by the user is screened for CMOP. This screening process is handled by the CMOP routine, PSXCH. Once the screening is finished PSXCH calls PSOSUCHG to complete the processing. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23527991 COMPONENT/ENTRY POINT: RTN COMPONENT/ENTRY POINT: ALL COMPONENT/ENTRY POINT: SPEC VARIABLES: XOK TYPE: Output VARIABLES DESCRIPTION: XOK indicates that the Rx is suspended for CMOP and it is okay to change the suspense date. XOK = 1 -> changing suspense date is okay, XOK = 0, changing of the suspense date is not allowed. SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 1973 IA #: 1973 DATE CREATED: MAR 27, 1997 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOLSET NAME: DBIA1973 ID: PSOLSET GENERAL DESCRIPTION: The CMOP package makes a call to the Outpatient Pharmacy routine, PSOLSET. This call is made to set up the required OP system variables that are necessary for pulling Rx's from suspense during the CMOP transmission process or when CMOP labels are printed at the medical center pharmacy. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23527871 COMPONENT/ENTRY POINT: PSOLSET VARIABLES: PSOPAR TYPE: Output VARIABLES: PSOBAR0 TYPE: Output VARIABLES: PSOBAR1 TYPE: Output VARIABLES: PSOBARS TYPE: Output VARIABLES: PSOCAP TYPE: Output VARIABLES: PSOCLC TYPE: Output VARIABLES: PSOCNT TYPE: Output VARIABLES: PSODIV TYPE: Output VARIABLES: PSXDTCUT TYPE: Output VARIABLES: PSOINST TYPE: Output VARIABLES: PSOION TYPE: Output VARIABLES: PSOIOS TYPE: Output VARIABLES: PSOLAP TYPE: Output VARIABLES: PSONULBL TYPE: Output VARIABLES: PSOPAR7 TYPE: Output VARIABLES: PSOPROP TYPE: Output VARIABLES: PSOPRPAS TYPE: Output VARIABLES: PSOREL TYPE: Output VARIABLES: PSOREO TYPE: Output VARIABLES: PSOSITE TYPE: Output VARIABLES: PSOSITE7 TYPE: Output VARIABLES: PSOSYS TYPE: Output VARIABLES: PSXSYS TYPE: Output SUBSCRIBING PACKAGE: CMOP ISC: Birmingham SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 1974 IA #: 1974 DATE CREATED: MAR 27, 1997 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOCP NAME: DBIA1974 ID: PSOCP GENERAL DESCRIPTION: The CMOP package makes a call to the Outpatient Pharmacy routine, PSOCP. This call is made when the CMOP process is filing the release data that is returned by the CMOP facility. The call is made in order to generate any copay charges for the Rx. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23527784 COMPONENT/ENTRY POINT: CP VARIABLES: PSOCPRX TYPE: Output VARIABLES DESCRIPTION: PSOCPRX contains the record number of the prescription in the Rx file (#52). SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 1978 IA #: 1978 FILE NUMBER: 52.5 GLOBAL ROOT: PS(52.5, DATE CREATED: MAR 28, 1997 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1978 ID: PS(52.5, GENERAL DESCRIPTION: The CMOP package requires direct R/W access to all fields and cross-references in file 52.5. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32928252 SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 1979 IA #: 1979 FILE NUMBER: 54 GLOBAL ROOT: PS(54 DATE CREATED: MAR 28, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1979 ID: PS(54 GLOBAL REFERENCE: PS(54,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Consolidated Mail Outpatient Pharmacy package has modified the input transform for the .01 field in the RX CONSULT file (#54). This modification will prevent the first 20 entries in the file from being edited. This is necessary to provide uniformity in the drug warnings that are transmitted to the CMOP with each prescription. The drug warnings are passed by their record number in the RX CONSULT file from the hospital to the CMOP facility and then on to the vendor system. These numbers must match between all the medical centers using the CMOP software, the CMOP Facility, and the vendor system, or the incorrect drug warning could be printed on the prescription label. The modified input transform is shown below: ^DD("54",".01","0")="NAME^RFX^^0;1^K:$L(X)>25!($L(X)<1)!"(X"?1P.E)!(($G(DA )>0)&($G(DA)<21)) X" STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23524771 SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 1980 IA #: 1980 FILE NUMBER: 51 GLOBAL ROOT: PS(51 DATE CREATED: MAR 28, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1980 ID: PS(51 GLOBAL REFERENCE: PS(51,A,X) GLOBAL DESCRIPTION: This cross reference is used to look up the expanded SIG for a prescription. GENERAL DESCRIPTION: The Consolidated Mail Outpatient Pharmacy package accesses the 'A' cross reference in the MEDICATION INSTRUCTION file (#51). This cross reference used to expand the SIG in order to send this data with the prescription when it is transmitted to the CMOP facility to be filled. The CMOP package only reads the data in this cross reference. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23536019 SUBSCRIBING PACKAGE: CMOP ISC: Birmingham SUBSCRIBING PACKAGE: HEALTH SUMMARY SUBSCRIBING DETAILS: ADDED 6/27/2011 DATE/TIME EDITED: JUN 27, 2011@17:44 ACTION: USAGE CHOICE CHANGED AT THE REQUEST OF: SILVERMAN,ROBERT DATE/TIME EDITED: JUN 27, 2011@17:45 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SILVERMAN,ROBERT NUMBER: 1983 IA #: 1983 FILE NUMBER: 50 GLOBAL ROOT: PSDRUG( DATE CREATED: MAR 28, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1983 ID: PSDRUG( GENERAL DESCRIPTION: The CMOP package requires direct R/W access to all fields and cross-references in file 50. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23535460 SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 1985 IA #: 1985 DATE CREATED: APR 02, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAPIIB NAME: DBIA1985 ID: PXAPIIB GENERAL DESCRIPTION: This IA supports calls into the following linetags within routine PXAPIIB: $$DSPLYED^PXAPIIB <--Education $$DSPLYEX^PXAPIIB <--Examinations $$DSPLYHF^PXAPIIB <--Health Factors $$DSPLYIM^PXAPIIB <--Immunizations $$DSPLYSK^PXAPIIB <--Skin Tests $$POV^PXAPIIB <-Purpose of Visit STATUS: Active DURATION: Next Version MAIL MESSAGE: 21259787 GOOD ONLY FOR VERSION: 1 COMPONENT/ENTRY POINT: DSPLYED COMPONENT DESCRIPTION: Education Factors COMPONENT/ENTRY POINT: DSPLYEX COMPONENT DESCRIPTION: Examinations COMPONENT/ENTRY POINT: DSPLYHF COMPONENT DESCRIPTION: Health Factors COMPONENT/ENTRY POINT: DSPLYIM COMPONENT DESCRIPTION: Immunizations COMPONENT/ENTRY POINT: DSPLYSK COMPONENT DESCRIPTION: Skin Tests COMPONENT/ENTRY POINT: POV COMPONENT DESCRIPTION: Purpose of Visit SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring SUBSCRIBING DETAILS: AICS wishes to call these linetags for the purpose of using the output transforms for outputting entries during formatting and after scanning, before sending data to PCE. NUMBER: 1986 IA #: 1986 FILE NUMBER: 391.71 DATE CREATED: MAY 07, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: EXECUTE DD NODES OF File 391.71 Cross-references ID: EXECUTE DD NODES GENERAL DESCRIPTION: A cross-reference on a field in the Patient file #2 creates an entry in ADT/HL7 PIVOT file #391.71 and/or sets the cross-references in file #391 by executing the ^DD cross-reference nodes. ^DD(2,.01,1,991,0) = 2^AVAFC01^MUMPS ^DD(2,.02,1,991,0) = 2^AVAFC02^MUMPS ^DD(2,.03,1,991,0) = 2^AVAFC03^MUMPS ^DD(2,.05,1,991,0) = 2^AVAFC05^MUMPS ^DD(2,.08,1,991,0) = 2^AVAFC08^MUMPS ^DD(2,.09,1,991,0) = 2^AVAFC09^MUMPS ^DD(2,.111,1,991,0) = 2^AVAFC111^MUMPS ^DD(2,.1112,1,991,0) = 2^AVAFC1112^MUMPS ^DD(2,.112,1,991,0) = 2^AVAFC112^MUMPS ^DD(2,.113,1,991,0) = 2^AVAFC113^MUMPS ^DD(2,.114,1,991,0) = 2^AVAFC114^MUMPS ^DD(2,.115,1,991,0) = 2^AVAFC115^MUMPS ^DD(2,.117,1,991,0) = 2^AVAFC117^MUMPS ^DD(2,.131,1,991,0) = 2^AVAFC131^MUMPS ^DD(2,.132,1,991,0) = 2^AVAFC132^MUMPS ^DD(2,.211,1,991,0) = 2^AVAFC211^MUMPS ^DD(2,.219,1,991,0) = 2^AVAFC219^MUMPS ^DD(2,.2403,1,991,0) = 2^AVAFC2403^MUMPS ^DD(2,.301,1,991,0) = 2^AVAFC301^MUMPS ^DD(2,.302,1,991,0) = 2^AVAFC302^MUMPS ^DD(2,.31115,1,991,0) = 2^AVAFC31115^MUMPS ^DD(2,.323,1,991,0) = 2^AVAFC323^MUMPS ^DD(2,.351,1,991,0) = 2^AVAFC351^MUMPS ^DD(2,391,1,991,0) = 2^AVAFC391^MUMPS ^DD(2,1901,1,991,0) = 2^AVAFC1901^MUMPS Global ^DD(2,1901,1,991 DD(2,1901,1,991 ^DD(2,1901,1,991,0) = 2^AVAFC1901^MUMPS ^DD(2,1901,1,991,1) = D:($T(AVAFC^VAFCDD01)'="") AVAFC^VAFCDD01(DA) ^DD(2,1901,1,991,2) = D:($T(AVAFC^VAFCDD01)'="") AVAFC^VAFCDD01(DA) ^DD(391.71,.06,1,1,0) = 391.71^AC^MUMPS ^DD(391.71,.08,1,1,0) = 391.71^AXMIT2^MUMPS ^DD(391.71,.06,0) = TRANSMITTED^S^1:NEED TO TRANSMIT;^0;6^Q ^DD(391.71,.06,1,0) = ^.1 ^DD(391.71,.06,1,1,0) = 391.71^AC^MUMPS ^DD(391.71,.06,1,1,1) = S:+X ^VAT(391.71,"AC",$E(X,1,30),DA)="" ^DD(391.71,.06,1,1,2) = K ^VAT(391.71,"AC",$E(X,1,30),DA) ^DD(391.71,.08,0) = REQUIRES TRANSMISSION^S^0:NO;1:YES;^0;8^Q ^DD(391.71,.08,.1) = Requires Transmission ^DD(391.71,.08,1,0) = ^.1 ^DD(391.71,.08,1,1,0) = 391.71^AXMIT2^MUMPS ^DD(391.71,.08,1,1,1) = Q:(($G(VAFCA08))!('X)) N A S A=$P(^VAT(391.71,DA,0),"^",4) S:(+A) ^VAT(391.71,"AXMIT",A,DA)="" ^DD(391.71,.08,1,1,2) = N A S A=$P(^VAT(391.71,DA,0),"^",4) K:(+A) ^VAT(391.71,"AXMIT",A,DA) STATUS: Active MAIL MESSAGE: 23859158 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 1987 IA #: 1987 FILE NUMBER: 9999999.09 GLOBAL ROOT: AUTTEDT( DATE CREATED: APR 04, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1987 ID: AUTTEDT( GLOBAL REFERENCE: AUTTEDT(#,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Name of Education Topic FIELD NUMBER: .03 FIELD NAME: Inactive Flag LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Education Topics GENERAL DESCRIPTION: This integration agreement authorizes global reference to the zeroith node of the following file for purposes of retrieving the name and inactive flag: ^AUTTEDT(#,0) piece 1 and piece 3 ... and to the "B" cross-reference STATUS: Active DURATION: Next Version MAIL MESSAGE: 23621192 GOOD ONLY FOR VERSION: 1.0 SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 3/16-15-MC: Added VPS as a subecriber at the request of Carolyn Wheless and approval of Anthony Puleo for VPS*1*15, scheduled for release April 2015 DATE/TIME EDITED: MAR 16, 2015@07:01 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: PULEO,ANTHONY NUMBER: 1988 IA #: 1988 FILE NUMBER: 9999999.15 GLOBAL ROOT: AUTTEXAM( DATE CREATED: APR 04, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1988 ID: AUTTEXAM( GLOBAL REFERENCE: AUTTEXAM(#,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Name of Exam. FIELD NUMBER: .04 FIELD NAME: INACTIVE FLAG LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: This file is a list of Physical Exams that have been defined specifically for use in entering Examinations performed on an Outpatient or Inpatient Encounter. GENERAL DESCRIPTION: This integration agreement authorizes global reference to the zeroith node of the following file for purposes of retrieving the name and inactive flag: ^AUTTEXAM(#,0) piece 1 and piece 4 ... and to the "B" cross-reference STATUS: Active DURATION: Next Version MAIL MESSAGE: 23621192 GOOD ONLY FOR VERSION: 1 SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 3/16/15-MC: Added VPS as subscriber at the request of Carolyn Wheless and approval of Anthony Puleo for VPS*1*15, planned for release in April 2015. VPS is implementing the ORWPCE PCENOTE RPC in the VPS namesspace and will use the global reference to the NAME field and INACTIVE FLAG field in the EXAM file,9999999.15. DATE/TIME EDITED: MAR 16, 2015@06:51 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: PULEO,ANTHONY NUMBER: 1989 IA #: 1989 FILE NUMBER: 9999999.64 GLOBAL ROOT: AUTTHF( DATE CREATED: APR 04, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1989 ID: AUTTHF( GLOBAL REFERENCE: AUTTHF( FIELD NUMBER: .01 FIELD NAME: FACTOR LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Name of Health Factor. FIELD NUMBER: .11 FIELD NAME: INACTIVE FLAG LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .10 FIELD NAME: ENTRY TYPE LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: This file contains a descriptive name of health factors, and their health factor category. GENERAL DESCRIPTION: This integration agreement authorizes global reference to the zeroith node of the following file for purposes of retrieving the name and inactive flag: ^AUTTHF(#,0) piece 1 and piece 11 ... and to the "B" cross-reference STATUS: Active DURATION: Next Version MAIL MESSAGE: 23621192 GOOD ONLY FOR VERSION: 1 SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 1990 IA #: 1990 FILE NUMBER: 9999999.14 GLOBAL ROOT: AUTTIMM( DATE CREATED: APR 04, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1990 ID: AUTTIMM( GLOBAL REFERENCE: AUTTIMM(#,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Name of Immunization. FIELD NUMBER: .07 FIELD NAME: INACTIVE FLAG LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: This file is a list of Immunizations and associated codes developed specifically for use in the IHS. This file contains a full descriptive name for each Immunization, plus a shortened name of Ten Characters which is used on the Health Summary and on reports where space is limited, plus a Two Digit Code for each Immunization. GENERAL DESCRIPTION: This integration agreement authorizes global reference to the zeroith node of the following file for purposes of retrieving the name and inactive flag: ^AUTTIMM(#,0) piece 1 and piece 7 ... and to the "B" cross-reference STATUS: Active DURATION: Next Version MAIL MESSAGE: 23621192 GOOD ONLY FOR VERSION: 1 SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING DETAILS: ADDED 8/28/09 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT SUBSCRIBING DETAILS: ADDED 8/28/09 SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 3/16/15-MC: Added VPS as a subscriber at the request of Carolyn Wheless and approval of Anthony Puleo for VPS*1*15, scheduled for release in April 2015. DATE/TIME EDITED: AUG 28, 2009@10:55 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SILVERMAN,ROBERT WITH CONCURRENCE OF: FAIN,ZACHARY DATE/TIME EDITED: MAR 16, 2015@07:05 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: PULEO,ANTHONY NUMBER: 1991 IA #: 1991 FILE NUMBER: 9999999.28 GLOBAL ROOT: AUTTSK( DATE CREATED: APR 04, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1991 ID: AUTTSK( GLOBAL REFERENCE: AUTTSK(#,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Name of Skin Test FIELD NUMBER: .03 FIELD NAME: INACTIVE FLAG LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: This file contains Skin Tests. It consists of a full descriptive name, a Ten Character Abbreviated Name for the Health Summary and other reports where spaces are limited, plus a Two Digit Code (IHS only). GENERAL DESCRIPTION: This integration agreement authorizes global reference to the zeroith node of the following file for purposes of retrieving the name and inactive flag: ^AUTTSK(#,0) piece 1 and piece 3 ... and to the "B" cross-reference STATUS: Active DURATION: Next Version MAIL MESSAGE: 23621192 GOOD ONLY FOR VERSION: 1 SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 3/16/15-MC: Added VPS as a subscriber at the request of Carolyn Wheless and approval of Anthony Puleo for VPS*1*15, scheduled for release in April 2015. VPS needs to provide a patient's sking test data to be included in a summary of the patient's outpatient clinic visit. To implement the ORWPCE PCE4NOTE functionality, VPS will need to use the global reference to the NAME field and INACTIVE FLAG field. DATE/TIME EDITED: MAR 16, 2015@10:58 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: PULEO,ANTHONY NUMBER: 1992 IA #: 1992 FILE NUMBER: 399 GLOBAL ROOT: DGCR(399 DATE CREATED: APR 04, 1997 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA1992 ID: DGCR(399 GLOBAL REFERENCE: DGCR(399,#,0) FIELD NUMBER: .01 FIELD NAME: BILL NUMBER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DGCR(399,#,S) FIELD NUMBER: 1 FIELD NAME: DATE ENTERED LOCATION: S;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 12 FIELD NAME: DATE FIRST PRINTED LOCATION: S;12 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 17 FIELD NAME: DATE BILL CANCELLED LOCATION: S;17 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DGCR(399,#,OP) FIELD NUMBER: 43 FIELD NAME: OP VISITS DATE(S) LOCATION: OP;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Request to read both the global and the AOPV X-reference on this field. GLOBAL REFERENCE: DGCR(399,#,U1) FIELD NUMBER: 201 FIELD NAME: TOTAL CHARGES LOCATION: U1;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This ingegration agreement allows access to the following global nodes within file 399: ^DGCR(399,"AOPV" use of the AOPV cross-reference for look-up ^DGCR(399,#,0) ^DGCR(399,#,"S") ^DGCR(399,#,"U1") ^DGCR(399,#,"OP",0) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23623009 SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring SUBSCRIBING DETAILS: For use in our Scanned Forms w/ Bill Generated option. SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 1994 IA #: 1994 DATE CREATED: APR 08, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXBUTL NAME: DBIA1994 ID: PXBUTL GENERAL DESCRIPTION: This is a one-time only DBIA with PCE to allow the CPT v.6.0 package update to revise routine PXBUTL to eliminate references to files 409.72, which will no longer be maintained. These references have been replaced by supported calls to supported APIs. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23655348 COMPONENT/ENTRY POINT: CPTOK COMPONENT DESCRIPTION: Returns effective date/status for procedure code. COMPONENT/ENTRY POINT: CPTSCREN COMPONENT DESCRIPTION: Returns status for procedure code. SUBSCRIBING PACKAGE: CPT ISC: Albany NUMBER: 1995 IA #: 1995 DATE CREATED: APR 08, 1997 CUSTODIAL PACKAGE: CPT/HCPCS CODES CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ICPTCOD NAME: CPT Code APIs ORIGINAL NUMBER: 1995 ID: ICPTCOD GENERAL DESCRIPTION: This contains the supported references to routine ICPTCOD for the supported APIs to be released with v.6.0 of CPT. These entry points will retrieve CPT/HCPCS code related data. All entry points will return -1^error description in an error condition. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 35881070 KEYWORDS: 1995 KEYWORDS: 1997 KEYWORDS: 1996 COMPONENT/ENTRY POINT: $$CPT(CODE,CDT,SRC) COMPONENT DESCRIPTION: Extrinsic function that returns basic information for CPT code. WARNING: Use of the INACTIVE FLAG field (#5) can produce unpredictable results if the API is not used. VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: The CPT, HCPCS, or Level III code in either internal or external format. VARIABLES: CDT TYPE: Input VARIABLES DESCRIPTION: The date for which status of the code is being checked. The Default value is TODAY. If CDT < 1/1/1989, use 1/1/1989 If CDT > DT, validate with newest In/Activation Dates If CDT is year only, use first of the year If CDT is year and month only, use first of the month VARIABLES: $$CPT TYPE: Output VARIABLES DESCRIPTION: String, containing the following information in the following "^" pieces: Piece Description ===== =========== 1 internal entry number of code in ^ICPT 2 CPT CODE (.01 field) 3 SHORT NAME (versioned from .01 field #61 multiple) 4 CATEGORY ien (#3 field) 5 SOURCE code (#6 field) ==> C:CPT; H:HCPCS; L:VA LOCAL 6 EFFECTIVE DATE (from .01 field #60 multiple) 7 STATUS 0:inactive; 1:active (from .02 of #60 multiple) 8 INACTIVE DATE (versioned from .01 field #60 multiple) 9 ACTIVE DATE (versioned from .01 field #60 multiple) 10 NOTICE OF TEXTUAL INACCURACY VARIABLES: SRC TYPE: Input VARIABLES DESCRIPTION: Flag to indicate if Level III codes need to be screened out. If SRC=0 or null, Level III codes are not processed as valid input; if SRC>0, Level III codes are accepted. COMPONENT/ENTRY POINT: $$CPTD(CODE,'OUTARR',DFN,CDT) COMPONENT DESCRIPTION: Extrinsic function that returns the full description of a code, from the "D" node (field 50) of the ICPT file. VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: The CPT or HCPCS code in either internal or external format. VARIABLES: $$CPTD TYPE: Output VARIABLES DESCRIPTION: Contains number of lines (number of subscripts) in description (array) VARIABLES: OUTARR TYPE: Both VARIABLES DESCRIPTION: An array name in which to store the returned versioned description. If no name is provided, the default name will be ^TMP("ICPTD",$J,. The calling routine is responsible for killing ^TMP("ICPTD",$J) after the call, if used. On return, the array contains corresponding lines of text of the code's versioned description (field 62) OUTARR(1) = 1st line of description OUTARR(last) = last line of description OUTARR(last+1) = blank line OUTARR(last+2) = NOTICE OF TEXTUAL INACCURACY where last+2 is the value returned by $$CPTD. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Not in use. Added in anticipation of future need. VARIABLES: CDT TYPE: Input VARIABLES DESCRIPTION: Code Date to check, Default = Today (FileMan format) Not in use. Added for future need. If CDT < 1/1/1989, use 1/1/1989 If CDT > DT, use the most recent description If CDT is year only, use first of the year If CDT is year and month only, use first of the month COMPONENT/ENTRY POINT: $$CODM(CODE,'OUTARR',SRC,CDT,DFN) COMPONENT DESCRIPTION: Extrinsic function that returns alphabetic array containing list of all acceptable modifiers for a selected code. VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: The CPT, HCPCS, or Level III code in either internal or external format. VARIABLES: OUTARR TYPE: Both VARIABLES DESCRIPTION: An array name in which to store the list of acceptable modifiers. If no name is provided, the default name will be ^TMP("ICPTM",$J, The calling routine is responsible for killing ^TMP("ICPTM",$J) after the call, if used. Array sorted on Modifier (field .01) and containing the Versioned Name (field #61), and ien of modifier. OUTARR()= versioned name^ien VARIABLES: SRC TYPE: Input VARIABLES DESCRIPTION: Flag to indicate if Level III codes and modifiers need to be screened out. If SRC=0 or null, Level III codes are not valid input and Level III modifiers are not valid output; if SRC>0, Level III codes and modifiers are included. *Note that all Level III modifiers are currently INACTIVE, and will be rejected. VARIABLES: CDT TYPE: Input VARIABLES DESCRIPTION: Date in Fileman format to check modifier status against. If CDT=0 or null, both active and inactive modifiers will be included in the output as acceptable modifiers. If CDT is passed as a date, only modifiers being active as of this date will be included in the output as acceptable modifiers. If CDT < 1/1/1989, use 1/1/1989 If CDT > DT, validate with newest In/Activation Dates If CDT is year only, use first of the year If CDT is year and month only, use first of the month VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Not in use. Included in anticipation of future needs. VARIABLES: $$CODM TYPE: Output VARIABLES DESCRIPTION: Number of modifiers in OUTARR(mod name). or -1^error description in an error condition COMPONENT/ENTRY POINT: $$MOD(MOD,MFT,MDT,SRC) COMPONENT DESCRIPTION: Extrinsic function that returns basic information for MODIFIER WARNING: Use of the INACTIVE FLAG field (#5) can produce unpredictable results if the API is not used. VARIABLES: $$MOD TYPE: Output VARIABLES DESCRIPTION: String containing modifier data in "^" pieces: Piece Description ===== =========== 1 internal entry number 2 MODIFIER (.01 field) 3 NAME (.02 field) 4 CODE (.O3 field) alternate 5-digit code for CPT modifiers 5 SOURCE (.04 field) C:CPT; H:HCPCS; V:VA NATIONAL 6 EFFECTIVE DATE (.01 field of multiple field 60) 7 STATUS (.02 field of multiple field 60) 8 INACTIVE DATE (.01 field of multiple field 60) 9 ACTIVE DATE (.01 field of multiple field 60) 10 NOTICE OF TEXTUAL INACCURACY VARIABLES: MOD TYPE: Input VARIABLES DESCRIPTION: MODIFIER (.01 field or ien: External or ien format) VARIABLES: MFT TYPE: Input VARIABLES DESCRIPTION: MOD format where "I" = internal (ien); "E" = external (.01) Default value is "E". VARIABLES: MDT TYPE: Input VARIABLES DESCRIPTION: Date to check modifier status for. Default value is TODAY. If MDT < 1/1/1989, use 1/1/1989. If MDT > DT, validate with newest In/Activation Dates If MDT is year only, use first of the year If MDT is year and month only, use first of the month VARIABLES: SRC TYPE: Input VARIABLES DESCRIPTION: Flag to indicate if Level III modifiers need to be screened out If SRC=0 or null, Level III modifiers are not valid input; if SRC>0, Level III modifiers are accepted. *Note that all Level III modifiers are currently INACTIVE, and will be rejected. COMPONENT/ENTRY POINT: $$MODP(CODE,MOD,MFT,MDT,SRC) COMPONENT DESCRIPTION: Extrinsic function that returns ien value of modifier if it can be used with code - MODIFIER/CODE pair checker. VARIABLES: $$MODP TYPE: Output VARIABLES DESCRIPTION: If pair not okay, 0. If pair okay, string containing modifier data in "^" pieces: Piece Description ===== =========== 1 internal entry number 2 NAME (.02 field) VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: The CPT, HCPCS, or Level III code in either internal or external format. VARIABLES: MOD TYPE: Input VARIABLES DESCRIPTION: MODIFIER (.01 field or ien: External or ien format) VARIABLES: MFT TYPE: Input VARIABLES DESCRIPTION: MOD format where "I" = internal (ien); "E" = external (.01) Default value is "E". VARIABLES: MDT TYPE: Input VARIABLES DESCRIPTION: Date to check modifier status for. Default value is TODAY. If MDT < 1/1/1989, use 1/1/1989 If MDT > DT, validate with newest In/Activation Dates If MDT is year only, use first of the year If MDT is year and month only, use first of the month VARIABLES: SRC TYPE: Input VARIABLES DESCRIPTION: Flag to indicate if Level III codes and modifiers need to be screened out. If SRC=0 or null, Level III codes and Level III modifiers are not valid input; if SRC>0, Level III codes and modifiers are accepted. *Note that all Level III modifiers are currently INACTIVE, and will be rejected. COMPONENT/ENTRY POINT: $$CODEN(CODE) COMPONENT DESCRIPTION: Extrinsic function that returns the ien of a CPT or HCPCS code VARIABLES: $$CODEN TYPE: Output VARIABLES DESCRIPTION: The Internal Entry Number of the CPT or HCPCS code. VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: CPT/HCPCS Code REQUIRED COMPONENT/ENTRY POINT: $$CODEC(CODE) COMPONENT DESCRIPTION: Extrinsic function that returns the CPT or HCPCS code of an ien. VARIABLES: $$CODEC TYPE: Output VARIABLES DESCRIPTION: The CPT or HCPCS code. VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: The Internal Entry Number of the CPT or HCPCS code. NUMBER: 1996 IA #: 1996 DATE CREATED: APR 08, 1997 CUSTODIAL PACKAGE: CPT/HCPCS CODES CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ICPTMOD NAME: CPT/HCPCS Modifier APIs ORIGINAL NUMBER: 1995 ID: ICPTMOD CREATOR: ROWE,KIMBALL GENERAL DESCRIPTION: This contains the supported references to routine ICPTMOD for the supported APIs. These entry points will retrieve CPT MODIFIER related data. All entry points will return '-1^error description' in an error condition. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 39032941 KEYWORDS: ICPTMOD KEYWORDS: MODD KEYWORDS: 1995 KEYWORDS: 1996 KEYWORDS: 1997 COMPONENT/ENTRY POINT: $$MOD(MOD,MFT,MDT,SRC,DFN) COMPONENT DESCRIPTION: Extrinsic function that returns basic information for MODIFIER. Returns string of data. WARNING: Use of the INACTIVE FLAG field (#5) can produce unpredictable results if the API is not used. VARIABLES: MOD TYPE: Input VARIABLES DESCRIPTION: MODIFIER (.01 field or ien: External or ien format) VARIABLES: MFT TYPE: Input VARIABLES DESCRIPTION: Modifier format where "I"=internal (ien); "E"=external (.01) Default value is "E" VARIABLES: MDT TYPE: Input VARIABLES DESCRIPTION: Date to check modifier status for. If MDT < 1/1/1989, use 1/1/1989 If MDT > DT, validate with newest In/Activation Dates If MDT is year only, use first of the year If MDT is year and month only, use first of the month VARIABLES: $$MOD TYPE: Output VARIABLES DESCRIPTION: A "^" delimited string containing the following pieces: 1 Internal Entry Number (IEN) 2 MODIFIER (.01 field) 3 NAME (Versioned Name from multiple field 61) 4 CODE (.O3 field) alt. 5-digit code for CPT modifiers 5 SOURCE (.04 field) C:CPT; H:HCPCS; V:VA NATIONAL 6 EFFECTIVE DATE (from multiple field 60) 7 STATUS (.02 field of multiple field 60) VARIABLES: SRC TYPE: Input VARIABLES DESCRIPTION: If 0 or Null, check national (level 1, level 2) mods only If SRC>0, include VA modifiers VARIABLES: DFN TYPE: Input COMPONENT/ENTRY POINT: $$MODP(CODE,MOD,MFT,MDT,SRC,DFN) COMPONENT DESCRIPTION: Extrinsic function that returns ien value of modifier if it can be used with code - MODIFIER/CODE pair checker. Returns ien of MOD if acceptable pair, 0 if not. VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: The CPT or HCPCS code in either internal or external format. VARIABLES: MOD TYPE: Input VARIABLES DESCRIPTION: MODIFIER (.01 field or ien: External or ien format) VARIABLES: MFT TYPE: Input VARIABLES DESCRIPTION: Modifier format where "I"=internal (ien); "E"=external (.01) Default value is "E" VARIABLES: MDT TYPE: Input VARIABLES DESCRIPTION: Date to check modifier status for. If MDT < 1/1/1989, use 1/1/1989 If MDT > DT, validate with newest In/Activation Dates If MDT is year only, use first of the year If MDT is year and month only, use first of the month VARIABLES: $$MODP TYPE: Output VARIABLES DESCRIPTION: If pair is acceptable: IEN^Versioned Name (from 61 multiple) If pair is unacceptable: 0 or -1^error message VARIABLES: SRC TYPE: Input VARIABLES DESCRIPTION: If 0 or Null, check national (level 1, level 2) mods only If SRC>0, include VA modifiers COMPONENT/ENTRY POINT: $$MODD(CODE,OUTARR,DFN,CDT) COMPONENT DESCRIPTION: Returns an array of text containing the versioned Modifier description. VARIABLES: $$MODD TYPE: Output VARIABLES DESCRIPTION: Returns the number of lines of text in the versioned description or '-1^error message' if there is no versioned description. VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: This is either a CPT/HCPCS Modifier code (external, field .01) or an Internal Entry Number (IEN) of the CPT Modifier file #81.3. VARIABLES: OUTARR TYPE: Both VARIABLES DESCRIPTION: This is an array name in which to store the returned versioned description of the Modifier - e.g. "ABC" or "ABC("TEST")" or temp array. If no name is provided, the default name will be ^TMP("ICPTD",$J,. The calling routine is responsible for killing ^TMP("ICPTD",$J) after the call, if used. On return, the array contains corresponding lines of text of the Modifier's versioned description (field 62) ARRAY(1) = 1st line of description ARRAY(last) = last line of description ARRAY(last+1) = blank line ARRAY(last+2) = NOTICE OF TEXTUAL INACCURACY where last+2 is the value returned by $$MODD. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Future use. VARIABLES: CDT TYPE: Input VARIABLES DESCRIPTION: Code Set Versioning date - active as of date in Fileman Format, default = today (FM) If CDT < 2890101, use 2890101 If CDT > DT, validate with In/Activation Dates If CDT is year only, use first of the year If CDT is year and month, use first of the month COMPONENT/ENTRY POINT: MODA(CODE,DATE,.ARY) COMPONENT DESCRIPTION: This entry point builds a list of Active and Inactive CPT Modifiers that are used in conjunction with a CPT code. The determination of the status of Active versus Inactive is made based on a date provided (default TODAY). The list is placed in a local array passed by reference. VARIABLES: CODE TYPE: Input VARIABLE SEQUENCE NUMBER: 1 VARIABLES DESCRIPTION: (Required) This is a CPT CODE. VARIABLES: DATE TYPE: Input VARIABLE SEQUENCE NUMBER: 2 VARIABLES DESCRIPTION: (Required) This is the date to use for retrieving the list of CPT Modifiers and determine if the relationship between the CPT code and the CPT Modifier is Active or Inactive. The default value for this date is TODAY. VARIABLES: .ARY TYPE: Input VARIABLE SEQUENCE NUMBER: 3 VARIABLES DESCRIPTION: (Required) Input array passed by reference. VARIABLES: ARY TYPE: Output VARIABLES DESCRIPTION: This is an array of Active and Inactive CPT Modifiers for a CPT code in the following format: ARY(0) = 4 Piece String 1 # of Modifiers found for code CODE (input) 2 # of Modifiers w/Active Ranges 3 # of Modifiers w/Inactive Ranges 4 Code ARY(ST,MOD) = 8 Piece Output String ST Status A=Active I=Inactive MOD Modifier (external format) 8 Piece String 1 IEN of Modifier 2 Versioned Short Text (name) 3 Activation date of Modifier 4 Beginning Range Code 5 Ending Range Code 6 Activation Date of Range 7 Inactivation Date of Range 8 Modifier Identifier DBA Comments: 20080918 - new component MODA(CODE,DATE,.ARY) and its variables were added DATE ACTIVATED: SEP 18, 2008 DATE/TIME EDITED: SEP 18, 2008@17:00 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: ROWE,KIMBALL DATE/TIME EDITED: SEP 18, 2008@19:05 ACTION: APPROVED AT THE REQUEST OF: ROWE,KIMBALL NUMBER: 1997 IA #: 1997 DATE CREATED: APR 08, 1997 CUSTODIAL PACKAGE: CPT/HCPCS CODES CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ICPTAPIU NAME: CPT Utility APIs ORIGINAL NUMBER: 1995 ID: ICPTAPIU CREATOR: ROWE,KIMBALL GENERAL DESCRIPTION: Routine contains supported calls for the CPT package. These include an extrinsic variable, which returns the Distribution Date, an extrinsic function that returns the category name for a category ien, functions to perform Status Checks on codes, to retrieve the Next or Previous code, and to retrieve the History of code activation/inactivation. Both entry points will return -1^error description in an error condition. Another entry point will display the CPT SIGNON COPYRIGHT MESSAGE to the calling device. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 35881077 KEYWORDS: 1995 KEYWORDS: 1997 KEYWORDS: 1996 COMPONENT/ENTRY POINT: CPTDIST COMPONENT DESCRIPTION: Extrinsic Variable - returns distribution date of current release. S X=$$CPTDIST^ICPTAPIU VARIABLES: DATE TYPE: Output VARIABLES DESCRIPTION: DISTRIBUTION DATE (.02 field of file 81.2) COMPONENT/ENTRY POINT: CAT COMPONENT DESCRIPTION: Extrinsic function that returns the CATEGORY NAME, given the internal entry number. S X=$$CAT^ICPTAPIU(CAT) VARIABLES: CAT TYPE: Input VARIABLES DESCRIPTION: Internal entry number of category. VARIABLES: STR TYPE: Output VARIABLES DESCRIPTION: Category name (.01 field) for CAT (file 81.1) -1^error description returned if error condition. COMPONENT/ENTRY POINT: COPY COMPONENT DESCRIPTION: D COPY^ICPTAPIU will display the CPT SIGNON COPYRIGHT MESSAGE to the calling device. VARIABLES: none COMPONENT/ENTRY POINT: $$STATCHK(CODE,CDT) COMPONENT DESCRIPTION: Extrinsic function that returns the Status of a CPT Code or Modifier. VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: CPT Code or Modifier REQUIRED VARIABLES: CDT TYPE: Input VARIABLES DESCRIPTION: Code Date to check, Default = Today (FileMan format) If CDT is year only, use first of the year If CDT is year and month only, use first of the month If CDT < 1/1/1989, use 1/1/1989 If CDT > DT, validate with newest In/Activation Dates VARIABLES: $$STATCHK TYPE: Output VARIABLES DESCRIPTION: String, containing the following information in the following "^" pieces: Piece Description ===== =========== 1 STATUS where 0:inactive; 1:active 2 IEN of code/modifier, -1 on error COMPONENT/ENTRY POINT: $$NEXT(CODE) COMPONENT DESCRIPTION: Extrinsic function that returns the Next CPT Code or Modifier (active or inactive). VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: CPT Code or Modifier REQUIRED VARIABLES: $$NEXT TYPE: Output VARIABLES DESCRIPTION: The Next CPT Code/Modifier, Null if there is none. COMPONENT/ENTRY POINT: $$PREV(CODE) COMPONENT DESCRIPTION: Extrinsic function that returns the Previous CPT Code or Modifier (active or inactive). VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: CPT Code or Modifier REQUIRED VARIABLES: $$PREV TYPE: Output VARIABLES DESCRIPTION: The Previous CPT Code/Modifier, Null if there is none. COMPONENT/ENTRY POINT: $$HIST(CODE,ARY) COMPONENT DESCRIPTION: Extrinsic function that returns the activation history of a CPT Code or Code Modifier. VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: CPT Code or Modifier REQUIRED VARIABLES: .ARY TYPE: Both VARIABLES DESCRIPTION: Array, passed by Reference ARY (which was passed by reference) is returned as follows: ARY(0) = Number of Activation History Entries, -1 if error ARY(date) = STATUS where 0:inactive; 1:active 'date' is in FileMan format ARY("IEN") = Internal Entry Number of CPT code/modifier VARIABLES: $$HIST TYPE: Output VARIABLES DESCRIPTION: Number of Activation History Entries, -1 if error COMPONENT/ENTRY POINT: PERIOD(CODE,ARY) COMPONENT DESCRIPTION: Return Activation/Inactivation Period(s) in ARY ARY(0) = IEN (or, -1 if error) ARY(Act_date) = Inactivation Date^Versioned Short Name Text (field #61) VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: CPT Code or Modifier REQUIRED VARIABLES: ARY TYPE: Output VARIABLES DESCRIPTION: Array, passed by Reference REQUIRED COMPONENT/ENTRY POINT: CR(.ARY) COMPONENT DESCRIPTION: This API is used to place the Copyright Infomration in a Local Array VARIABLES: .ARY TYPE: Input VARIABLE SEQUENCE NUMBER: 1 VARIABLES DESCRIPTION: (Required) Name of Locay Array passed by reference. VARIABLES: ARY TYPE: Output VARIABLE SEQUENCE NUMBER: 2 VARIABLES DESCRIPTION: Local array containing the CPT Copyright information. DBA Comments: 20080918 - new component CR(.ARY) added and its variables DATE ACTIVATED: SEP 18, 2008 DATE/TIME EDITED: SEP 18, 2008@21:04 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: ROWE,KIMBALL DATE/TIME EDITED: SEP 18, 2008@21:20 ACTION: APPROVED AT THE REQUEST OF: ROWE,KIMBALL NUMBER: 1998 IA #: 1998 DATE CREATED: APR 09, 1997 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSODACT NAME: DBIA1998 ID: PSODACT GENERAL DESCRIPTION: This integration agreement allows a call in to routine PSODACT and line tag ENSTUFF for purposes of printing the Drug Use Evaluations (DUE). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23612648 COMPONENT/ENTRY POINT: ENSTUFF COMPONENT DESCRIPTION: Prints an answer sheet for DUE RX's. VARIABLES: PSOINST TYPE: Input VARIABLES: POSPAR TYPE: Input SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring SUBSCRIBING DETAILS: AICS presently prints out action profiles after the Encounter Form, and would like the ability to print the DUE as well. NUMBER: 2005 IA #: 2005 DATE CREATED: APR 15, 1997 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCGPM1 NAME: DBIA2005 ID: PRCGPM1 GENERAL DESCRIPTION: Integrated Funds of Patient routines PRPFPURG and PRPFSCV2 are invoking an IFCAP programming call ADD^PRCGPM1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23929965 COMPONENT/ENTRY POINT: ADD(X,Y,Z) COMPONENT DESCRIPTION: Parameter call to add new entry to purge master file. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Routine entry point (optional) and name to be executed by purgemaster in standard M format - entry point^routine name. VARIABLES: Y TYPE: Input VARIABLES DESCRIPTION: Variable string to be utilized by the routine called in X. Structure of variable is defined by developer of routine being executed. Typically this is a ^ delimited string. VARIABLES: Z TYPE: Both VARIABLES DESCRIPTION: Return variable - 1 if successful, 0 if unsuccessful in adding record to purgemaster. SUBSCRIBING PACKAGE: INTEGRATED PATIENT FUNDS ISC: Washington/Silver Spring EDITOR: GNOFFO,ROSE T NUMBER: 2010 IA #: 2010 FILE NUMBER: 38.5 GLOBAL ROOT: DGIN(38.5, DATE CREATED: APR 15, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2010 ID: DGIN(38.5, GLOBAL REFERENCE: DGIN(38.5,D1,'I',D0 FIELD NUMBER: .01 FIELD NAME: INCONSISTENCY LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The INCONSISTENCY (#.01) field is a pointer to the INCONSISTENT DATA ELEMENTS (#38.6) file. This field is dinummed, so that the values in this multiple are obtained by $Ordering at the sub-file entry level. GLOBAL DESCRIPTION: All inconsistencies for a patient are found in the INCONSISTENCY mulitple which are stored at this level. Pointer values to all inconsistencies in file #38.6 are found by $Ordering at the level of D0. GENERAL DESCRIPTION: This agreement will be used to allow Integrated Billing access to all recorded patient record inconsistencies which are located in the INCONSISTENT DATA (#38.5) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23720883 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 2011 IA #: 2011 FILE NUMBER: 38.6 GLOBAL ROOT: DGIN(38.6, DATE CREATED: APR 15, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2011 ID: DGIN(38.6, GLOBAL REFERENCE: DGIN(38.6,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the Name of the inconsistency. GLOBAL DESCRIPTION: Reference to the inconsistency name is needed to print the patient record inconsistency name on a report. GENERAL DESCRIPTION: This agreement will be used to allow access for Integrated Billing to the table values in the INCONSISTENT DATA ELEMENTS (#38.6) file for all patient record inconsistencies. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23720883 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 2012 IA #: 2012 DATE CREATED: APR 15, 1997 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RAO7PC1 NAME: Rad/Nuc Med non-cancelled exam list by patient ID: RAO7PC1 GENERAL DESCRIPTION: EN2^RAO7PC1 can be used to retrieve a list, by patient, of Radiology/Nuclear Medicine non-cancelled exams within the last seven days. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29228051 COMPONENT/ENTRY POINT: EN2 COMPONENT DESCRIPTION: EN2^RAO7PC1(RADFN) Input: RADFN = Internal entry number (ien) of the patient in the Rad/Nuc Med Patient file #70. (Note: this ien is the same ien used in the Patient file #2. File 70 is DINUMED to file 2. RADFN is also known as the patient ien. Output: ^TMP($J,"RAE7",patient ien,exam id)=procedure name^case number^ report status^imaging location ien^imaging location name^ contrast medium or media used Note regarding contrasts: Single characters in parenthesis indicate contrast involvement: (I)=Iodinated ionic; (N)=Iodinated non-ionic; (L)=Gadolinium; (C)=Oral Cholecystographic; (G)=Gastrografin; (B)=Barium; (M)=unspecified contrast media subscripts ---------- Patient ien: Internal entry number of the patient in both the Rad/Nuc Med Patient file # 70 and the Patient file #2. Exam Id: Reverse exam date/time of the exam concatenated to the ien of the case. Example: 7019698.9093-1 (where the exam date/time is 03/01/1998@9:06am and the case ien is 1. '7019698.9093' is derived from: 9999999.9999-2980301.0906) array value (in ascending piece position) ----------------------------------------- Procedure Name: Name of the procedure in the Rad/Nuc Med Procedure file #71. It is possible for users to change the procedure up until the exam status is 'COMPLETE'. Case Number: Identifying external case number for an exam. Can be a number between 1 and 99999. Report Status: External name of the report status. Possible statuses include: DRAFT, PROBLEM DRAFT, RELEASED/NOT VERIFIED, VERIFIED and NO REPORT. It is possible for the exam to have a report ien, but a 'NO REPORT' status if a stub report record was created to contain a pointer to the Imaging package file of images. Imaging Location (ien): The internal entry number of the Imaging Location in file 79.1 where the exam was performed. This ien is NOT DINUMED to the Hospital Location file #44. Imaging Location Name: Name of the imaging location in the Imaging Locations file #79.1. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2013 IA #: 2013 FILE NUMBER: 101 GLOBAL ROOT: ORD(101,,774) DATE CREATED: APR 16, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2013 ID: ORD(101,,774) GLOBAL REFERENCE: ORD(101,,774 FIELD NUMBER: 774 FIELD NAME: ROUTING LOGIC LOCATION: 774;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: 101,774 ROUTING LOGIC 774;E1,245 MUMPS INPUT TRANSFORM: K:$L(X)>245 X D:$D(X) ^DIM LAST EDITED: SEP 24, 1996 HELP-PROMPT: This is Standard MUMPS code. DESCRIPTION: This field is similar to the GENERATE/PROCESS ROUTINE field for a given CLIENT protocol, but is executed only when a message is in an OUTBOUND state. Normally, HL7 'broadcasts' a message to all subscribers whenever a message is generated. In some cases, a client may need to receive the message only if it matches a particular condition. This field permits the application to set up screening logic to interpret the message and generate a supplemental list of 'recipients' known to be interested in the data when it meets these conditions. The result of this routine should be the creation of the HLL("LINKS") array. WRITE AUTHORITY: @ GENERAL DESCRIPTION: HL7 1.6 needs permission to export new field, ROUTING LOGIC, with Protocol File (101) as part of the CIRN patch HL*1.6*14. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23737559 SUBSCRIBING PACKAGE: HEALTH LEVEL SEVEN ISC: Oakland NUMBER: 2015 IA #: 2015 FILE NUMBER: 50 GLOBAL ROOT: PSDRUG( DATE CREATED: APR 29, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2015 ID: PSDRUG( GLOBAL REFERENCE: PSDRUG(D0,0) FIELD NUMBER: .01 FIELD NAME: GENERIC NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the generic name of the drug. FIELD NUMBER: 20 FIELD NAME: NATIONAL DRUG FILE ENTRY LOCATION: ND;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the pointer to the National Drug file. FIELD NUMBER: 2 FIELD NAME: VA CLASSIFICATION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 16 FIELD NAME: PRICE PER DISPENSE UNIT LOCATION: 660;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 21 FIELD NAME: VA PRODUCT NAME LOCATION: ND;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. The Immunology Case Registry package (ICR) extracts Outpatient Pharmacy data to the National registry for the tracking of disease categories such as HIV and Renal Failure. The ICR SITE PARAMETERS file (#158.9) contains two fields, ENTRY IN DRUG FILE and NDF ENTRY, which is a pointer to the Drug file (#50) and NATIONAL DRUG FILE ENTRY field (#20). In order to consolidate local drug names with the National Drug File name for reporting purposes in the national registry, the Immunology Case Registry package requests a DBIA to point to the following file. Global: ^PSDRUG( Drug File #50 Field : .01 GENERIC NAME 0;1 DIRECT GLOBAL READ 20 NATIONAL DRUG FILE ENTRY ND;1 DIRECT GLOBAL READ STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 23759487 SUBSCRIBING PACKAGE: ICR - IMMUNOLOGY CASE REGISTRY ISC: Hines NUMBER: 2018 IA #: 2018 DATE CREATED: OCT 28, 2003 CUSTODIAL PACKAGE: RPC BROKER CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: Determining RPC Broker context GENERAL DESCRIPTION: This integration agreement is temporary. The Kernel RPC Broker is going to publish a standard method that will replace this agreement. Subscribing packages should be prepared to use that standard method within three months of its availability, or within a time frame negotiated and approved by the Kernel RPC Broker. This agreement allows packages to check for the existence of the variable XWBOS to determine if the current routine execution was called from an RPC Broker context. This is needed to control user interface actions that are dependent on whether they are roll-and-scroll based or GUI based. STATUS: Active MAIL MESSAGE: 37402561 SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Hines SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES NUMBER: 2019 IA #: 2019 DATE CREATED: MAY 13, 1997 CUSTODIAL PACKAGE: DIETETICS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: FHORD7 NAME: DBIA2019 ID: FHORD7 GENERAL DESCRIPTION: Inpatient Medications needs data from the Dietetics System package which can not be extracted from any file. The data returns from CUR^FHORD7 call will be used to display on the Inpatient Medications' MAR. STATUS: Active MAIL MESSAGE: 23939565 COMPONENT/ENTRY POINT: CUR VARIABLES: DFN TYPE: Input VARIABLES: ADM TYPE: Input VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: A string of Abbreviated Labels from file 111. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2021 IA #: 2021 DATE CREATED: MAY 16, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIR2 NAME: FileMan Replace/With Editor Call ID: DIR2 GENERAL DESCRIPTION: This IA permits Capacity Management utilities to call the FileMan Replace/With Editor entry point at RW^DIR2. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23992024 COMPONENT/ENTRY POINT: RW COMPONENT DESCRIPTION: RW^DIR2 is the entry point for the FileMan replace/with editor. The string to be edited is passed in Y. DIRWP mustn't exist unless you want to allow leading "^"s in the text. VARIABLES: Y TYPE: Both VARIABLES DESCRIPTION: The string to be edited is passed and returned in Y. VARIABLES: X TYPE: Output VARIABLES DESCRIPTION: X contains the User's last raw input. VARIABLES: DIRWP TYPE: Input VARIABLES DESCRIPTION: DIRWP allows leading "^"s in the text. SUBSCRIBING PACKAGE: CAPACITY MANAGEMENT ISC: Oakland SUBSCRIBING PACKAGE: VAX CAPACITY MANAGEMENT ISC: Oakland SUBSCRIBING PACKAGE: SIZING AND UTILIZATION MONITOR ISC: Oakland SUBSCRIBING PACKAGE: CAPACITY MANAGEMENT ISC: Oakland NUMBER: 2022 IA #: 2022 FILE NUMBER: .402 GLOBAL ROOT: DIE DATE CREATED: MAY 19, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: RECOMPILATION OF INPUT TEMPLATES ID: DIE GLOBAL REFERENCE: DIE(AF GLOBAL DESCRIPTION: The "AF" cross-reference has the following structure: ^DIE("AF",file,field,template)="" ^DIE("AF",subfile,subfield,template)="" GLOBAL REFERENCE: DIE(D0,ROU FIELD NUMBER: 1815 FIELD NAME: ROUTINE INVOKED LOCATION: ROU;E1,13 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: When installing a patch that includes changes to field definitions in a data dictionary, KIDS does not recompile the compiled input templates. This integration agreement covers recompilation of input templates. Recompilation of input templates may involve the following steps: (1) Traverse the "AF" cross-reference of the ^DIE global (file #.402) to obtain a list of compiled input templates for the affected fields. The structure of this cross-reference is ^DIE("AF",file,field,template)="" Subfields would be treated like fields of their respective subfiles, i.e. ^DIE("AF",subfile,subfield,template)="". (2) For each template that is being recompiled, access ^DIE(template,"ROU") to determine the compiled routine. (3) Invoke EN^DIEZ to recompile that input template. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29466806 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham NUMBER: 2023 IA #: 2023 GLOBAL ROOT: DD( DATE CREATED: MAY 19, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2023 ID: DD( GENERAL DESCRIPTION: PCE Patient Care Encounter and Visit Tracking is requesting permission to look at the following nodes of the Data Dictionary. 1) ^DD(FILE,0,"PT",FILE,FIELD) ;Pointer Nodes 2) ^DD(FILE,FIELD,1,SUB,0) ;Zero node of the Cross-reference Multiple 3) ^DD(FILE,FIELD,1,SUB,1) ;Set logic of the Cross-reference This will allow us to check for any FILE and FIELD that is pointing to the VISIT file #9000010 to make sure that a BROKEN pointer will not be created if an entry in the VISIT file is deleted by way of PCE OR VISIT TRACKING. It will also allow us to write reports to show who is pointing to a particular VISIT at times when it is necessary to Debug the Visit File Data Base. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23753470 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City SUBSCRIBING PACKAGE: VISIT TRACKING ISC: Salt Lake City NUMBER: 2024 IA #: 2024 DATE CREATED: MAY 20, 1997 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCAFN NAME: DBIA2024 ID: PRCAFN GENERAL DESCRIPTION: We are making a call to BN1^PRCAFN to return the AR bill number regardless of the type of bill. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24029900 COMPONENT/ENTRY POINT: $$BN1 COMPONENT DESCRIPTION: This function returns the AR bill number for all types of bills. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Internal file number of the bill entry in file 399. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 2027 IA #: 2027 FILE NUMBER: 9999999.09 GLOBAL ROOT: AUTTEDT( DATE CREATED: MAY 28, 1997 CUSTODIAL PACKAGE: INDIAN HEALTH SERVICE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2027 EDUCATION TOPICS ID: AUTTEDT( GENERAL DESCRIPTION: The PCE Patient Care Encounter Package requests a DBIA to distribute the Indian Health Services EDUCATION TOPICS file (9999999.09) in the VA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24092873 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany NUMBER: 2028 IA #: 2028 FILE NUMBER: 9000010 GLOBAL ROOT: AUPNVSIT( DATE CREATED: MAY 28, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: READ ACCESS ONLY TO PCE VISIT FILE ID: AUPNVSIT( GENERAL DESCRIPTION: Visit Tracking grants PCE Patient Care Encounter Global Read to the Visit file: all fields and all cross references. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24092898 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING DETAILS: To be able to identify an optional secondary visit by checking cross-reference 6/20/14 - PCMMR added. Beginning with SD*5.3*603, PCMMR will assign a patient to a team in a pending status until they have a completed encounter with a team member. Once they have the encounter, they are switched to an active status. PCMMR uses a remote procedure call to identify an encounter in the Outpatient Encounter (#409.68) file based on the checkout date and makes a determination if the status should be updated to active. With the Outpatient Encounter file data, additional data elements can be obtained from the Visit (#9000010) and V Provider (#9000010.06) files. Returned array includes Patient DFN, Encounter Date/Time(#.01 field - 409.68), Provider IEN (#.01 field - 9000010.06), Primary/Secondary (#.04 field - 9000010.06), Stop Code (#.03 field - 409.68), Encounter Type (#15003 field - 9000010), Checkout Completed Date/Time (#.07 field - 409.68), Outpatient Encounter (#409.68) IEN, Outpatient Encounter Parent IEN, Visit (#9000010) IEN, and Visit Parent IEN (#12 field - 9000010). PCMMR will display the last encounter date for the patient. SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT SUBSCRIBING DETAILS: added 10/10/2008 SUBSCRIBING PACKAGE: ONCOLOGY SUBSCRIBING DETAILS: Added 1/8/09 SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: Effective with VPR*1*0. DBA Comments: 08/02/13 DT: Added VPR as subscriber per request by Melanie Buechler - effective with VPR*1*0. 6/20/14-MM: Adding PCMMR details to the Subscribing Details for Scheduling to document how PCMM will be using the Visit and V Provider files for PCMMR functionality distributed in SD*5.3*603. DATE/TIME EDITED: NOV 06, 2006@16:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WOLF,ED WITH CONCURRENCE OF: FAIN,ZACH DATE/TIME EDITED: OCT 10, 2008@14:53 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: ELLIS,DONNA DATE/TIME EDITED: JAN 08, 2009@11:21 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BIELO,GARY WITH CONCURRENCE OF: FAIN,ZACH DATE/TIME EDITED: AUG 02, 2013@13:15 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: YORTY,ROBERT DATE/TIME EDITED: JUN 20, 2014@14:50 ACTION: CONTENT CORRECTED AT THE REQUEST OF: THOMPSON,ANDY WITH CONCURRENCE OF: REDINGTON,PAT NUMBER: 2029 IA #: 2029 DATE CREATED: JUN 02, 1997 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOCPTRI NAME: DBIA2029 ID: PSOCPTRI GENERAL DESCRIPTION: Integrated Billing requests permission to call three entry points in the Outpatient Pharmacy routine PSOCPTRI. This routine contains the interface points between IB and Pharmacy which are needed to support the real-time billing of Tricare prescriptions using a commercial pharmacy billing software package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24128559 COMPONENT/ENTRY POINT: $$CHK(ORIG,REF) COMPONENT DESCRIPTION: This entry point is used to determine if Pharmacy will allow a specific prescription/refill to be billed to the CHAMPUS/Tricare fiscal intermediary. VARIABLES: ORIG TYPE: Input VARIABLES DESCRIPTION: ORIG is a pointer to the specific prescription in file #52 for which authorization to bill the fiscal intermediary is being requested. VARIABLES: REF TYPE: Input VARIABLES DESCRIPTION: REF is a pointer to the refill in file #52.1 for the prescription ORIG. If authorization is requested for the original fill of the prescription, then REF will be 0. VARIABLES: $$CHK TYPE: Output VARIABLES DESCRIPTION: 0 = prescription/refill should not be billed 1 = should not be billed COMPONENT/ENTRY POINT: LABEL(RX,PSOLAP,PSOSITE,DUZ,PSOTRAMT) COMPONENT DESCRIPTION: This entry point is called by Integrated Billing from a background to print the presciption label after authorization to bill the prescription has been electronically received from the Tricare fiscal intermediary. VARIABLES: RX TYPE: Input VARIABLES DESCRIPTION: RX is a pointer to the prescription, in file #52, for the prescription whose label must be printed. VARIABLES: PSOLAP TYPE: Input VARIABLES DESCRIPTION: PSOLAP is the device on which the label should be printed. VARIABLES: PSOSITE TYPE: Input VARIABLES DESCRIPTION: PSOSITE is a pointer to the Pharmacy in file #59 in which the medication was dispensed. VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: DUZ is a pointer to the user in file #200 who originally requested that the prescription label be printed. VARIABLES: PSOTRAMT TYPE: Input VARIABLES DESCRIPTION: PSOTRAMT is the copayment amount to be charged to the patient for the prescription. This amount is printed on the prescription label. COMPONENT/ENTRY POINT: $$TRANS(ORIG,REF,PSOV) COMPONENT DESCRIPTION: This call is used to collect prescription information which is used to build the message which is electronically transmitted to the fiscal intermediary. VARIABLES: ORIG TYPE: Input VARIABLES DESCRIPTION: ORIG is a pointer to the prescription in file #52 for the prescription for which information is being requested. VARIABLES: REF TYPE: Input VARIABLES DESCRIPTION: REF is pointer to the refill in file #52.1 for the prescription for which information is being requested. If information for the original fill is being requested, then REF is set to 0. VARIABLES: PSOV TYPE: Output VARIABLES DESCRIPTION: PSOV is passed by reference to this routine. Prescription information is returned from this routine by populating an array of this referenced variable. The array definition is as follows: PSOV("NDC") - the NDC number of the prescribed drug, from file #50 PSOV("DIV") - the dispensinf Pharmacy from file #59 PSOV("FDT") - the date the prescription was filled, which is the Last Fill (#101) field, or if blank, the Dispensed (#25) field from file #52. PSOV("RX#") - the prescription number from file #52 (field #.01) PSOV("QTY") - the quantity (QTY, field #7) of the prescription from file #52 PSOV("SUP") - the Days Supply (field #8) of the prescription from file #52 PSOV("ISS") - the Issue Date (field #1) of the prescription from file #52 PSOV("#REF") - the number of refills (field #9) authorized for the prescription, from file 52. PSOV("COMP") - Compound Code for the drug of the prescription. If the DEA, SPECIAL HANDLING (#3) field of the drug contains a 0 (zero), a 2 will be returned. If it does not contain a 0 (zero), a 1 will be returned. PSOV("DEA") - This is the DEA# (#53.2) field from the NEW PERSON (#200) file, for the Provider associated with the original fill of the prescription. VARIABLES: $$TRANS TYPE: Output VARIABLES DESCRIPTION: 1 = Adequate information exists for CHAMPUS Rx billing purposes. -1 = Not enough information for CHAMPUS Rx billing pruposes, mainly no prescription data, or an NDC number cannot be determined for the drug associated with the Outpatient prescription. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 2030 IA #: 2030 DATE CREATED: JUN 03, 1997 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBACUS NAME: DBIA2030 ID: IBACUS GENERAL DESCRIPTION: Outpatient Pharmacy requests permission to call two entry points in the Integrated Billing routine IBACUS. This routine contains the interface points between Outpatient Pharmacy and Integrated Billing which are needed to support the real-time billing of Tricare prescriptions using a commercial pharmacy billing software package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24134356 COMPONENT/ENTRY POINT: $$TRI COMPONENT DESCRIPTION: This entry point is used to determine if the site is using a commercial pharmacy billing software package to bill Tricare prescriptions. VARIABLES: OUT TYPE: Output VARIABLES DESCRIPTION: OUT is the value returned by this function. If the site is billing Tricare prescriptions, OUT is returned as 1; otherwise OUT is returned as 0. COMPONENT/ENTRY POINT: $$CHPUS(PSTRP,DT,TRXI,PSTRF,PSOLAP,PSTRD,PSTRDZ) COMPONENT DESCRIPTION: This entry point is used to determine if an Outpatient prescription will be billed as Tricare by the commercial pharmacy billing software package. VARIABLES: PSTRP TYPE: Input VARIABLES DESCRIPTION: PSTRP is the pointer to the PATIENT File (#2), for the patient receiving the prescription. VARIABLES: DT TYPE: Input VARIABLES DESCRIPTION: DT is the current date. VARIABLES: TRXI TYPE: Input VARIABLES DESCRIPTION: TRXI is the pointer to the PRESCRIPTION File (#52). VARIABLES: PSTRF TYPE: Input VARIABLES DESCRIPTION: PSTRF is the fill number for the prescription. It will be 0 for an original prescription, 1 for refill #1, 2 for refill #2, 3 for refill #3, etc. VARIABLES: PSOLAP TYPE: Input VARIABLES DESCRIPTION: PSOLAP is the device which the user is currently signed in under to print Outpatient labels. VARIABLES: PSTRD TYPE: Input VARIABLES DESCRIPTION: PSTRD is the pointer to the OUTPATIENT SITE File (#59), which the user is currently signed in under. VARIABLES: PSTRDZ TYPE: Input VARIABLES DESCRIPTION: PSTRDZ is the pointer to the NEW PERSON File (#200), for the user who is processing the prescription. VARIABLES: OUT TYPE: Output VARIABLES DESCRIPTION: OUT is the value returned by this function. OUT is set to 1 if the prescription is to be billed as Tricare, OUT is 0 if the prescription is not to be billed as Tricare. SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2031 IA #: 2031 DATE CREATED: JUN 04, 1997 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBRFN NAME: DBIA2031 ID: IBRFN CREATOR: GUSTAFSON,ERIC S GENERAL DESCRIPTION: This is needed to get information about the type of charges on the receivables from integrated billing. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 53376652 COMPONENT/ENTRY POINT: $$REC(IBSTR,IBTYP,IBDISP) COMPONENT DESCRIPTION: This function is needed to get the receivable for an authorization number or RX number or an ECME number. VARIABLES: IBSTR TYPE: Input VARIABLES DESCRIPTION: This variable is either the RX number or FI authorization number or the ECME number. VARIABLES: $$REC TYPE: Output VARIABLES DESCRIPTION: The function value will return either IFN in the ACCOUNTS RECEIVABLE (#430) OR -1 if no corresponding bill is found. VARIABLES: IBTYP TYPE: Output VARIABLES DESCRIPTION: Output variable to be passed by reference. This variable will determine how the passed in number in IBSTR was identified by the system. A value of 1 indicates a TRICARE Auth#, 2 indicates an ECME number, 3 indicates an Rx number, while 0 indicates unknown. VARIABLES: IBDISP TYPE: Output VARIABLES DESCRIPTION: Output variable to be passed by reference. This variable will contain the external display version of the passed in number IBSTR. For example to contain the leading zeros on an ECME#. If the passed in value in variable IBSTR was 54321 to perform a claim look-up by the ECME#, then output variable IBDISP will either be 0054321 or 000000054321 depending on if the ECME# is 7 digits or 12 digits in length. COMPONENT/ENTRY POINT: $$AUD(INPUT) COMPONENT DESCRIPTION: This call is needed to determine if a particular receivable needs to be audited or not. VARIABLES: INPUT TYPE: Input VARIABLES DESCRIPTION: This variable is the IFN from the ACCOUNTS RECEIVABLE file (#430). VARIABLES: $$AUD TYPE: Output VARIABLES DESCRIPTION: This variable will return either a 1 for needs to be audited or a 0 if the receivable does not need to be audited. COMPONENT/ENTRY POINT: $$TYP(INPUT) COMPONENT DESCRIPTION: This call will return the type of charge that is being billed. VARIABLES: INPUT TYPE: Input VARIABLES DESCRIPTION: This variable is the IFN from the Accounts Receivable (#430). VARIABLES: $$TYP TYPE: Output VARIABLES DESCRIPTION: This variable will be either one of the following: I - Inpatient bill O - Outpatient bill PH- Pharmacy bill PR- Prosthetics bill -1 if no bill type can be determined SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring DATE ACTIVATED: DEC 13, 2010 DATE/TIME EDITED: DEC 10, 2010@17:32 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: GUSTAFSON,ERIC DATE/TIME EDITED: DEC 13, 2010@11:03 ACTION: APPROVED AT THE REQUEST OF: GUSTAFSON,ERIC NUMBER: 2032 IA #: 2032 FILE NUMBER: 3.9 GLOBAL ROOT: DD(3.91 DATE CREATED: JUN 10, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DELETE C XREF ID: DD(3.91 GENERAL DESCRIPTION: Subj: Request for DBIA [#24183795] 09 Jun 97 11:11 10 Lines From: BEUSCHEL,GARY - MAILMAN DEVELOPER (San Francisco CIOFO) 1 of 1 Response read. in 'IN' basket. Page 1 ------------------------------------------------------------------------------ For MailMan patch XM*7.1*40, Request DBIA to delete "C" xref on field 1 (LAST RESPONSE READ) of RECIPIENT multiple of MESSAGE file. The following code to be included in a pre-init routine: K ^DD(3.91,1,1) K ^DD(3.91,0,"IX","C") K ^DD(3.91,"IX",1) 1) MARSHALL,RICK - COMPUTER SPECIALIST (VA IRMFO San Francisco-Seattle) 10 Jun 97 15:46 1 Line Roll it up and I'll approve it. Forwarding to DBIA folks. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: SEP 01, 1997 MAIL MESSAGE: 24199704 SUBSCRIBING PACKAGE: MAILMAN ISC: Oakland NUMBER: 2033 IA #: 2033 DATE CREATED: JUN 13, 1997 CUSTODIAL PACKAGE: SURGERY USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SROGTSR NAME: DBA2033 ID: SROGTSR GENERAL DESCRIPTION: The purpose of this agreement is to provide access to the Surgery package (custodian) by the Imaging package (subscriber) for obtain a surgical case listing to append images to. Requesting permission to use the Surgery API, GET^SROGTSR, for listing surgical cases. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31069102 COMPONENT/ENTRY POINT: GET COMPONENT DESCRIPTION: Obtains a listing of surgery cases for the patient specified by the calling routine. An array will be passed with the following: array(0)="# of cases found" or "0^There are no cases entered" array(#)="#^display date^description^surgery ien^internal date format ^number of images for the surgical case" VARIABLES: SRDFN TYPE: Input VARIABLES DESCRIPTION: Patient's ien VARIABLES: SRGY TYPE: Output VARIABLES DESCRIPTION: An array of surgery cases: array(0)="# of cases found" or "0^There are no cases entered" array(#)="#^display date^description^surgery ien^internal date format ^number of images for the surgical case."" SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 2034 IA #: 2034 DATE CREATED: JUN 16, 1997 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBCNSU4 NAME: DBIA2034 ID: IBCNSU4 GENERAL DESCRIPTION: This supported reference allows packages to retrieve Sponsor information which is associated with a patient. The sponsors are the people who are responsible for the patient's Tricare or CHAMPVA medical benefits coverage. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24237524 COMPONENT/ENTRY POINT: GET(DFN,.ARRAY) COMPONENT DESCRIPTION: This is the entry point invoked by the calling application to retrieve patient sponsor information. The output is returned in an array which is passed by reference by the calling application. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This is a pointer to the patient in file #2. VARIABLES: ARRAY TYPE: Output VARIABLES DESCRIPTION: This array, passed into the routine by reference by the calling application, has the following structure: ARRAY = #, where # equals the number of relationships which the patient has with different sponsors. For each specific sponsor relationship, the following two array elements are returned: 1. ARRAY(n,"REL") = 1^2^3^4^5, where n => sequential number for each relationship, begining with 1 1 => The Sponsor name 2 => The sponsor "family prefix." This is the DOD scheme for indicating the patient's relationship to the sponsor, where 01 indicates spouse, 02 indicates oldest child, 03 indicates next oldest child, etc. 3 => Sponsor Type (either TRICARE or CHAMPVA) 4 => The effective date of the relationship, in FileMan format 5 => The expiration date of the relationship, in FileMan format 2. ARRAY(n,"SPON") = 1^2^3^4^5^6, where n => sequential number for each relationship, begining with 1 1 => The Sponsor name 2 => Sponsor date of birth, in external (displayable) format 3 => Sponsor social security number, in external (including dashes) format 4 => Sponsor's military status (either ACTIVE DUTY or RETIRED) 5 => Sponsor Branch of Service (expanded value from entry in file #23) 6 => Sponsor's Rank in Service (free-text value entered by user). NUMBER: 2035 IA #: 2035 DATE CREATED: JUN 04, 1997 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBCNSBL2 NAME: DBIA2035 ID: IBCNSBL2 GENERAL DESCRIPTION: This is needed to allow the user to be alerted that there is another payer for a receivable for co-ordination of benefits purposes. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24150299 COMPONENT/ENTRY POINT: BULL(IBIFN,IBORIG,IBPYMT) COMPONENT DESCRIPTION: If a secondary payer exists a bulletin is generated to the IB CAT C mail group. VARIABLES: IBIFN TYPE: Input VARIABLES DESCRIPTION: This is the bill's internal number from ACCOUNTS RECEIVABLE file (#430) VARIABLES: IBORIG TYPE: Input VARIABLES DESCRIPTION: This variable is the original amount of bill. VARIABLES: IBPYMT TYPE: Input VARIABLES DESCRIPTION: This variable is the total paid on bill. COMPONENT/ENTRY POINT: $$EOB(IBIFN,IBORIG,IBPYMT) COMPONENT DESCRIPTION: This function is needed to determine if the receivable has another payer. VARIABLES: IBIFN TYPE: Input VARIABLES DESCRIPTION: IFN from ACCOUNTS RECEIVABLE file (#430). VARIABLES: IBORIG TYPE: Input VARIABLES DESCRIPTION: Original amount of receivable. VARIABLES: IBPYMT TYPE: Input VARIABLES DESCRIPTION: Total paid on receivable. VARIABLES: OUT TYPE: Output VARIABLES DESCRIPTION: 1^free text name of other payer or 0 for no other payer SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 2036 IA #: 2036 FILE NUMBER: 0 GLOBAL ROOT: DD( DATE CREATED: JUN 06, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DD GLOBAL ID: DD( GLOBAL REFERENCE: DD(file,field,0) FIELD NUMBER: .2 FIELD NAME: SPECIFIER LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to determine the data type of the filed. FIELD NUMBER: .3 FIELD NAME: POINTER LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field used to decode a set of codes to its external format and to make sure that a code is a valid code. It is also used to get the pointed to file for pointer fields. GENERAL DESCRIPTION: The Visit Tracking package have been granted permission to access the DD global as defined in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24146207 SUBSCRIBING PACKAGE: VISIT TRACKING ISC: Albany NUMBER: 2037 IA #: 2037 DATE CREATED: APR 21, 2003 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBCNSU41 NAME: DBIA2037 ID: IBCNSU41 GENERAL DESCRIPTION: This DBIA provides an entry point which may be invoked by a calling application to initiate an interactive session which will allow the user to add new sponsors or edit existing sponsors, and to relate a sponsor to a patient. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24237524 COMPONENT/ENTRY POINT: SPON(DFN) COMPONENT DESCRIPTION: This entry point allows the user to add/edit sponsors and relate the sponsor to a patient. In the first sequence of prompts, the user is asked to enter a sponsor. If the sponsor is an existing sponsor, then the user may add/edit sponsor attributes. Otherwise, the user is asked to add the person as a new sponsor, and then to add/edit the attributes. The system then determines if the patient has a relationship with the selected/added sponsor. If so, the sponsor relationship attributes may then be updated. Otherwise, the user is asked to establish a relationship for the patient with the selected sponsor. The sponsor relationship attributes may then be updated. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This is a pointer to the patient in file #2. SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 2038 IA #: 2038 FILE NUMBER: 100 GLOBAL ROOT: OR( DATE CREATED: JUN 17, 1997 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2038 ID: OR( GENERAL DESCRIPTION: This is a one-time request for Consults/Request Tracking Patch GMRC*2.5*13 to correct the pointer field 'CURRENT AGENT/PROVIDER' within the OE/RR Package file, ORDERS #100. This field was incorrectly populated by the Consults/Request package with a Variable Pointer, the Consults patch #13 will replace the incorrect pointer with its Non-Variable equivalent. The correction occurs at the time of the patch install and will only be executed that one time. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24249099 SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 2039 IA #: 2039 DATE CREATED: JUN 24, 1997 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MCUIMAG0 NAME: MEDICINE UPDATE API ID: MCUIMAG0 GENERAL DESCRIPTION: This entry point creates new entries, if needed, in the Medical Patient file (#690) and the Medicine Procedure data files (see file list under MCD0). It also allows the Imaging package to populate the Image multiple in the Medicine Procedure data files. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32284659 COMPONENT/ENTRY POINT: UPDATE(MCDATE,MCPROCD0,MCDFN,.MCMAGPTR,[.]MCD0,OK) VARIABLES: MCDATE TYPE: Input VARIABLES DESCRIPTION: Date/Time of a procedure (VA FileMan internal format) VARIABLES: MCPROCD0 TYPE: Input VARIABLES DESCRIPTION: A pointer to the Procedure/Subspecialty file (#697.2), e.g., ^MCAR(697.2,MCPROCD0,... VARIABLES: MCDFN TYPE: Input VARIABLES DESCRIPTION: A pointer to the Patient file (#2), e.g., ^DPT(MCDFN,... VARIABLES: MCMAGPTR() TYPE: Both VARIABLES DESCRIPTION: An array whose subscripts are pointers to the Image file (#2005). The elements of the array should be set to null. To create a new Medicine Procedure data file stub record without image data, set this paramerter such that $O(MCMAGPTR(0))'>0. (Also see MCD0.) On output: Returned as: MCMAGPTR('File_#2005_Pointer')= MCFILE ^ MCD0 ^ MCD1, e.g., ^MCAR(MCFILE,MCD0,2005,MCD1,0)='File_#2005_Pointer' VARIABLES: MCD0 TYPE: Input VARIABLES DESCRIPTION: A pointer to one of the entries in one of the Medicine Procedure data files, e.g., ^MCAR(691,MCD0,... This parameter may be passed by reference or by value. If passed by reference, it will be returned as Pointer#^File# if there were no problems (i.e., OK>0). If OK'>0, the value of MCD0 should not be relied on. Pass in this parameter as null to create a new stub record in one of the Medicine Procedure data files. (Also see MCMAGPTR.) A list of Medicine Procedure data files follows: 691*, 691.1*, 691.5*, 691.6, 691.7, 691.8, 694*, 694.5 698, 698.1, 698.2, 698.3, 699*, 699.5*, 700, 701* Note, only those marked with a '*' have Image pointer multiples. VARIABLES: OK TYPE: Output VARIABLES DESCRIPTION: Flag: '1^Message' = All is well, '0^Message' = Bad news The list of possible return values is shown below: 0^Medicine Procedure file global location not found MEANING: The Global Location field (#1) in the Procedure / Subspecialty file (#697.2) has a value in it that is less than or equal to zero. 0^Medical Patient field not found in Medicine Procedure file MEANING: A field that points to the Patient file (#2) could not be found in the Medicine Procedure data file (see file list under MCD0). 0^Medicine Procedure file global name not found MEANING: The global root of the Medicine Procedure data file (see file list under MCD0) could not be found. (File file (#1) problem) 0^Medicine Procedure file global subscript location not found MEANING: The node on which the image pointer multiple stores its data cound not be found (Medicine DD problem). 0^Cannot add patient to Medical Patient file MEANING: A new record could not be created in the Medical Patient file (#690). 0^Cannot create stub record in the Medicine Procedure data file MEANING: A new stub record could not be created in one of the Medicine Procedure data files (see file list under MCD0). 0^No image number to file in Medicine Procedure file MEANING: The MCMAGPTR() array was not passed in, does not contain any data, or was passed in incorrectly. 0^Image field not found in the Medicine Procedure file MEANING: A field number of 2005 was not found in the Medicine Procedure data file (see file list under MCD0). 0^Cannot add image to Medicine Procedure file MEANING: A new image sub-record could not be added to the Image multiple (#2005) in the Medicine Procedure data file (see file list under MCD0). 0^Patient mismatch MEANING: The Medicine Procedure data file record pointed to by the MCD0 parameter has a different Patient file (#2) pointer than the Patient file (#2) pointer that was passed in in the MCDFN parameter. 0^Procedure/Subspecialty mismatch MEANING: The Medicine Procedure data file record pointed to by the MCD0 parameter has a different Procedure / Subspecialty file (#697.2) pointer than the Procedure / Subspecialty file (#697.2) pointer that was passed in in the MCPROCD0 parameter. 0^Procedure is invalid MEANING: The value passed in in the MCPROCD0 parameter failed the input transform of the field it was going to be stuffed into. 0^Entry 'GENERIC PROCEDURE' not found MEANING: The 'GENERIC PROCEDURE' entry was not found in the Procedure/Subspecialty file (#697.2). This message is only valid after the installation of patch MC*2.3*8. 0^Entry 'GENERIC SUBSPECIALTY' not found MEANING: The 'GENERIC SUBSPECIALTY' entry was not found in the Procedure/Subspecialty file (#697.2). This message is only valid after the installation of patch MC*2.3*8. 0^Invalid Procedure/Subspecialty MEANING: The pointer to the Procedure/Subspecialty file (697.2) (MCPROCD0) is not flagged as a procedure or a subspecialty in the 'Procedure/Subspecialty' field (697.2,1001). This message is only valid the installation of patch MC*2.3*8. 1^Record match found MEANING: The Medicine Procedure data file record pointed to by the MCD0 parameter has Patient file (#2) and Procedure / Subspecialty (#697.2) pointers that match the values passed in in the MCDFN and MCPROCD0 parameters. Note, this message is used internally within the API and you will most likely never see it since it will be superseded by one of the other messages. 1^New stub record created in Medicine Procedure data file MEANING: New stub record have been created in the Medical Patient file (#690) (if needed) and one of the Medicine Procedure data files (see file list under MCD0). Note, this message will only be returned if $O(MCMAGPTR(0))'>0 and MCD0'>0 and the creation of the new record(s) was successful. 1^The Medicine Procedure file has been updated MEANING: The Image file (#2005) pointers passed in in the MCMAGD0() array have been added to (or have been found to previously exist in) the Image multiple (#2005) of the Medicine Procedure data file (see file list under MCD0). SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring EDITOR: PRICE,RICHARD M NUMBER: 2040 IA #: 2040 DATE CREATED: JUN 24, 1997 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MCUIMAG0 NAME: MEDICINE KILL API ID: MCUIMAG0 GENERAL DESCRIPTION: This entry point removes entries from the Image multiples in the Medicine Procedure data files. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32284682 COMPONENT/ENTRY POINT: KILL VARIABLES: MCFILE TYPE: Input VARIABLES DESCRIPTION: A Medicine Procedure data file number 691*, 691.1*, 691.5*, 691.6, 691.7, 691.8, 694*, 694.5 698, 698.1, 698.2, 698.3, 699*, 699.5*, 700, 701* (Note: only those marked with a '*' have Image pointer multiples) VARIABLES: MCD0 TYPE: Input VARIABLES DESCRIPTION: A pointer to one of the entries in one of the Medicine Procedure data files, e.g., ^MCAR(MCFILE,MCD0,... VARIABLES: MCD1 TYPE: Input VARIABLES DESCRIPTION: A pointer to one of the entries in the in the Image multiple e.g., ^MCAR(MCFILE,MCD0,2005,MCD1,0)='File_#2005_Pointer' VARIABLES: OK TYPE: Output VARIABLES DESCRIPTION: Flag: '1^Message' = All is well, '0^Message' = Bad news The list of possible return values is shown below: 0^Image field not found in the Medicine Procedure file MEANING: A pointer to the Image file (#2005) was not found in the Medicine Procedure data file (see file list under MCD0). 0^Medicine Procedure file global name not found MEANING: The global root of the Medicine Procedure data file (see file list under MCD0) could not be found. (File file (#1) problem) 0^Medicine Procedure file global subscript location not found MEANING: The node on which the image pointer multiple stores its data cound not be found (Medicine DD problem). 1^Image pointer deleted from Medicine Procedure file MEANING: The pointer to the Image file (#2005) has been removed from the Medicine Procedure data file. SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring EDITOR: PRICE,RICHARD M NUMBER: 2041 IA #: 2041 DATE CREATED: JUN 25, 1997 CUSTODIAL PACKAGE: REGISTRATION USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGRPD NAME: DB2041 ID: DGRPD GENERAL DESCRIPTION: Used to display the Patient Profile report via a "silent call". STATUS: Active MAIL MESSAGE: 23498613 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: Prints a patient profile. Passed to this routine is the device and patient's DFN. VARIABLES: IOP TYPE: Input VARIABLES DESCRIPTION: DEVICE NAME VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient's internal entry number in file 2. SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: WOMEN'S HEALTH ISC: Hines SUBSCRIBING PACKAGE: BAR CODE MED ADMIN EDITOR: MOORE,TERRY D DATE/TIME EDITED: AUG 21, 2008@16:06 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: MORRE,TERRY NUMBER: 2043 IA #: 2043 DATE CREATED: JUN 27, 1997 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RAO7PC1 NAME: DBIA2043 ID: RAO7PC1 GENERAL DESCRIPTION: EN1^RAO7PC1 can be used to return a list of a patient's Rad/Nuc Med procedures and related information. Cancelled exams may be included, depending upon the RACINC input parameter. Exam ID output can be used as input to another API to retrieve result reports. (See DBIA #2265) Report ien output can also be used to retrieve a report. (See DBIA #1177) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 35420407 COMPONENT/ENTRY POINT: EN1(RADFN,RABDT,RAEDT,RAEXN,RACINC) VARIABLES: RADFN TYPE: Input VARIABLES DESCRIPTION: Internal entry number (ien) of the patient in the Rad/Nuc Med Patient file #70. (Note: this ien is the same ien used in the Patient file #2. File 70 is DINUMED to file 2. RADFN is also known as the patient ien. VARIABLES: RABDT TYPE: Input VARIABLES DESCRIPTION: Beginning date used to extract exam data for a specific time frame. VARIABLES: RAEDT TYPE: Input VARIABLES DESCRIPTION: Ending date used to extract exam data for a specific time frame. VARIABLES: RAEXN TYPE: Input VARIABLES DESCRIPTION: Maximum number of exams to extract within a time frame. If RAEXN is numeric, then each case within a parent procedure is counted separately. However, if RAEXN has a trailing "P", then all cases within a parent procedure are counted together as 1. VARIABLES: RACINC TYPE: Input VARIABLES DESCRIPTION: Include cancelled exams flag (1 if yes, default is no). This input parameter was added in RA*5.0*26. A later patch, RA*5.0*36, further restricts when cancelled cases would be returned: (1) case's division's ALLOW RPTS ON CANCELLED CASES? is "Y" and (2) case has a report. VARIABLES: TMP($J,'RAE1', TYPE: Output VARIABLES DESCRIPTION: ^TMP($J,"RAE1",patient ien,exam id)= procedure name^case number^report status^ abnormal alert flag^report ien^exam status order #~exam status name^imaging location name^ imaging type abbr~imaging type name^ abnormal results flag^CPT Code^CPRS Order ien^ Images exist flag subscripts ---------- Patient ien: Internal entry number of the patient in both the Rad/Nuc Med Patient file #70 and the Patient file #2. Exam Id: Reverse exam date/time of the exam concatenated to the ien of the case. Example: 7019698.9093-1 (where the exam date/time is 03/01/1998@9:06am and the case ien is 1. '70119689.9093' is derived from: 9999999.9999-2980301.0906) array value (in ascending piece position) ----------------------------------------- Procedure Name: Name of the procedure in the Rad/Nuc Med Procedure file #71. It is possible for users to change the procedure prior to the exam reaching a 'COMPLETE' status. Case Number: Identifying external case number for an exam. Can be a number between 1 and 99999. Report Status: External name of the report status. Possible statuses include: DRAFT, PROBLEM DRAFT, RELEASED/NOT VERIFIED, VERIFIED and NO REPORT. It is possible for the exam to have a report with a 'NO REPORT' status. A 'NO REPORT' status refers to a stub report that was created for the Imaging package file of images, this stub report record has no data entered by Radiology/Nuclear Medicine staff. Abnormal Alert Flag: Set to 'Y' if an abnormal diagnostic code is assigned to this case, blank if no abnormal code. A diagnostic code is considered abnormal if its entry in the Diagnostics Codes file #78.3 contains a 'Y' in the 'Generate Abnormal Alert' field. Report ien: This is the internal entry number of a report in the Rad/Nuc Med Reports file #74. Exam Status Order Number: A number between 0 and 9 where: 0=cancelled, 1=waiting for exam & 9=complete. All other order numbers are site configurable. Exam Status Name: External representation of exam status. Examples: WAITING FOR EXAM, EXAMINED, CANCELLED and COMPLETE. Imaging Location Name: Name of the imaging location in the Imaging Location file #79.1. This file points to the Hospital Location file #44. These files are not DINUMED. Imaging Type Abbreviation: This is a 1-4 character abbreviation of the imaging type of the exam. Examples: ANI, CARD, CT, MAM, MRI, NM, RAD, US and VAS. Imaging Type Name: External representation of the imaging type name. Examples: ANGIO/NEURO/INTERVENTIONAL, CARDIOLOGY STUDIES (NUC MED), CT SCAN, GENERAL RADIOLOGY, MAGNETIC RESONANCE IMAGING, MAMMOGRAPHY, NUCLEAR MEDICINE, ULTRASOUND and VASCULAR LAB. Abnormal Results Flag: Set to 'Y' if our primary diagnostic code has the field, PRINT ON ABNORMAL REPORT set to 'Yes'. If the field is set to any other value than 'Yes', our flag value is blank (null). CPT Code: This is the Current Procedural Terminology (CPT) code assigned to the registered procedure. Detailed and Series procedure types have CPT codes. Broad and Parent procedure types do not have CPT codes. CPRS Order ien: This is a pointer data type that indicates the record number of the order in the Order Entry/Results Reporting (OE/RR) package. This piece will be non-null if the OE/RR package is running and the Radiology/Nuclear Medicine package is available through OE/RR. Images exist flag: Set to 'Y' if images are associated with the report identified by Report ien above. If no images exist this flag will be set to 'N'. This flag was introduced in RA*5.0*26. Patch RA*5.0*10 provides additional ^TMP nodes for optional retrieval: Output: ^TMP($J,"RAE1",patient ien, exam id,"CMOD",n)= CPT modifier^CPT modifier name where n=1,2,3...total number of CPT modifiers for the exam Patch RA*5.0*36 provides additional ^TMP nodes for optional retrieval: Output: ^TMP($J,"RAE1",patient ien, exam id,"CPRS")= member of set^parent procedure name where member of set is the value of MEMBER OF SET in subfile 70.03 If the name of the Parent Procedure cannot be found, then "PARENT PROCEDURE" will be put into the second piece. NUMBER: 2045 IA #: 2045 FILE NUMBER: 409.68 GLOBAL ROOT: SCE( DATE CREATED: JUN 30, 1997 CUSTODIAL PACKAGE: SCHEDULING USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2045 ID: SCE( GLOBAL REFERENCE: SCE('AVSIT', GLOBAL DESCRIPTION: This will enable the user to look up the OUTPATIENT ENCOUNTER associated with a particular visit. GLOBAL REFERENCE: SCE(D0,0) FIELD NUMBER: .12 FIELD NAME: STATUS LOCATION: 0;12 ACCESS: Read w/Fileman FIELD DESCRIPTION: This contains the status of the Outpatient encounter. GENERAL DESCRIPTION: This will permit the direct reads using the "AVSIT" cross reference of the OUTPATIENT ENCOUNTER file (#409.68). This will be used to find an encounter associated with a specific visit from the VISIT file (#9000010), or determine that no entry exists for a visit in the OUTPATIENT ENCOUNTER file. Once the "AVSIT" cross-reference has been used to determine if an entry exists, the entry will be viewed, using VA FileMan, to check the STATUS field (#.12) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24348820 SUBSCRIBING PACKAGE: SURGERY NUMBER: 2048 IA #: 2048 FILE NUMBER: 9000010.18 GLOBAL ROOT: AUPNVCPT( DATE CREATED: JUN 30, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2048 ID: AUPNVCPT( GLOBAL REFERENCE: AUPNVCPT('AD', GLOBAL DESCRIPTION: This will allow the user to find the associated V CPT entries based on the VISIT number. GLOBAL REFERENCE: AUPNVCPT(D0,0) FIELD NUMBER: .01 FIELD NAME: CPT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This contains the pointer to the CPT file (#81) for the associated procedure. GLOBAL REFERENCE: AUPNVCPT(D0,12) FIELD NUMBER: 1204 FIELD NAME: ENCOUNTER PROVIDER LOCATION: 12;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains a pointer to the NEW PERSON file (#200) for the provider associated with this CPT. GENERAL DESCRIPTION: This will allow the user to use the "AD" cross-reference to obtain the ifn of a record using the VISIT number, in order to find the value of the CPT(.01) and ENCOUNTER PROVIDER (1204) fields in the V CPT file (#9000010.18). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24293862 SUBSCRIBING PACKAGE: HOSPITAL BASED HOME CARE NUMBER: 2049 IA #: 2049 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: JUN 30, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: LABORATORY DPT REFERRAL POINTER ID: DPT( GENERAL DESCRIPTION: Laboratory Electronic Date Interchange (LEDI) software is used to accept electronic orders from and send electronic results to other Laboratory Information Systems (LIS). The LEDI specimen accessioning procedure has been redesigned to limit or eliminate the user's clerical patient demographic data entry. This is achieved by adding an enhancement to the existing FileMan patient lookup. All LEDI patients are accessioned into the Referral File (#67). Adding patients to this file requires the entry of Name, DOB, PID and Sex. The clerical step of entering patient's demographic data is done by the accessioning software. If the FileMan lookup on the ^DPT( file is successful, a pointer is to be placed in the Patient ^DPT( file pointing to corresponding Referral entry. This pointer servers as a positive link identifier for future reference. This new pointer serves the same purpose as the existing field in the PATIENT FILE, LABORATORY REFERENCE (#63) except the new field will point to the Referral File (#67). Patient (#2) File ^DD(2,67,0)=LAB REFERRAL REF^P67'X^LRT(67,^LRT(;1^K X NUMBER:67 LABEL: LAB REFERRAL REF SPECIFIER: P67'X POINTER: LRT(67, GLOBAL SUBSCRIPT LOCATION: LRT;1 INPUT TRANSFORM: K X DESCRIPTION: This field contains the pointer reference to the Referral file of the Laboratory Package. This field is set by the laboratory accessioning software and should not be edited. Changing of this pointer will result in misidentification of patients that could have dire medical repercussions. This DBA is requesting the permission for establishment of this field within the Patient File and permission to set and read this field directly. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24291085 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 2050 IA #: 2050 DATE CREATED: JUL 02, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIALOG NAME: Database Server (DBS) API: DIALOG Utilities ID: DIALOG GENERAL DESCRIPTION: DIALOG file utilities. BLD: DIALOG Extractor $$EZBLD: DIALOG Extractor (Single Line) MSG: Output Generator STATUS: Active MAIL MESSAGE: 28390020 COMPONENT/ENTRY POINT: BLD() COMPONENT DESCRIPTION: This entry point performs the following functions: Extracts a dialog from a FileMan DIALOG file entry Substitutes dialog parameters into the text if requested Returns the text in an array Format: BLD^DIALOG(DIALOG#,[.]TEXT_PARAM,[.]OUTPUT_PARAM,OUTPUT_ARRAY,FLAGS) VARIABLES: DIALOG# TYPE: Input VARIABLES DESCRIPTION: (Required) Record number from the DIALOG file for the text to be returned. VARIABLES: [.]TEXT_PARAM TYPE: Input VARIABLES DESCRIPTION: (Optional) Local array containing the dialog parameters to substitute into the resulting text. Set the subscript of each node in this array to a dialog parameter that's in a |window| in the referenced Dialog entry's text. The value of each node should be in external, printable format, and will be substituted in the Dialog text for that dialog parameter. VARIABLES: [.]OUTPUT_PARAM TYPE: Both VARIABLES DESCRIPTION: (Optional) This is useful mainly if you are returning error messages as part of an API for other programmers to use. Use it to pass dialog parameters back to the user of your API, such that they can be accessed individually instead of just being embedded in the error text. VARIABLES: OUTPUT_ARRAY TYPE: Both VARIABLES DESCRIPTION: (Optional) If provided, the text will be output in the local or global array named by this parameter. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flags to control processing. The possible values are: S Suppresses the blank line that is normally inserted between discrete blocks of text that are built by separate calls to this routine. F Formats the local array similar to the default output format of the ^TMP global, so that MSG^DIALOG can be called to either write the array to the current device or to a simple local array. COMPONENT/ENTRY POINT: $$EZBLD() COMPONENT DESCRIPTION: This extrinsic function returns the first line of text from an entry in the DIALOG File. It can be used when the text entry is only one line and when the output does not need to be put into an array. Format $$EZBLD^DIALOG(DIALOG#,[.]TEXT_PARAM) VARIABLES: DIALOG# TYPE: Input VARIABLES DESCRIPTION: (Required) Record number from the DIALOG File for the text to be returned. VARIABLES: [.]TEXT_PARAM TYPE: Input VARIABLES DESCRIPTION: (Optional) Name of local array containing the parameter list for those parameters that are to be incorporated into the resulting text. These parameters should be in external, printable format. If there is only one parameter in the list, it can be passed in a local variable or as a literal. COMPONENT/ENTRY POINT: MSG() COMPONENT DESCRIPTION: This procedure takes text from one of the FileMan dialogue arrays (for errors, help text, or other text) or from a similarly structured local array writes it and/or moves it into a simple local array. Format: MSG^DIALOG(FLAGS,.OUTPUT_ARRAY,TEXT_WIDTH,LEFT_MARGIN,INPUT_ROOT) VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flags to control processing. If none of the text type flags (E, H or M) is entered, the routine behaves as if "E" were entered. If no flags are entered, it behaves as if FLAGS contained "WE". The possible values are: A Local Array specified by the second parameter receives the text. W Writes the text to the current device. S Saves the ^TMP or other designated input array (does not kill the array). E Error array text is processed. H Help array text is processed. M Message array text (other text) is processed. B Blank lines are suppressed between error messages. T Return Total number of lines in the top level node of the local array specified by the second parameter. VARIABLES: VARIABLES: .OUTPUT_ARRAY TYPE: Both VARIABLES DESCRIPTION: (Optional) This parameter contains the name of the local array to which the text is to be written. If FLAGS contains an A, this parameter must be sent. Otherwise, the parameter is ignored. VARIABLES: TEXT_WIDTH TYPE: Input VARIABLES DESCRIPTION: (Optional) Maximum line length for formatting text. VARIABLES: LEFT_MARGIN TYPE: Input VARIABLES DESCRIPTION: (Optional) Left margin for writing text. If sent, the text is lined up in a column starting at this column number. VARIABLES: INPUT_ROOT TYPE: Input VARIABLES DESCRIPTION: (Optional) Closed root of local input array in which text resides. If the text resides in a local array, this parameter must be sent. VARIABLES: ARRAY TYPE: Output VARIABLES DESCRIPTION: Total number of lines (only returned if FLAGS contains "T"). VARIABLES: ARRAY(n) TYPE: Output VARIABLES DESCRIPTION: A line of formatted text (n=sequential integer starting with 1). NUMBER: 2051 IA #: 2051 DATE CREATED: JUL 02, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIC NAME: Database Server API: Lookup Utilities ID: DIC GENERAL DESCRIPTION: Lookup utilities. FIND: Finder $$FIND1: Finder (Single Record) LIST: Lister STATUS: Active MAIL MESSAGE: 28390794 COMPONENT/ENTRY POINT: FIND() COMPONENT DESCRIPTION: This procedure finds records in a file based on an input value. Format FIND^DIC(FILE,IENS,FIELDS,FLAGS,VALUE,NUMBER,INDEXES,SCREEN,IDENTIFIER, TARGET_ROOT,MSG_ROOT) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) This parameter is the number of the file or subfile to search. If it is a subfile, it must be accompanied by the IENS parameter. VARIABLES: IENS TYPE: Input VARIABLES DESCRIPTION: (Optional) The IENS that identifies the subfile if FILE is a subfile number. Defaults to no subfile. VARIABLES: FIELDS TYPE: Input VARIABLES DESCRIPTION: (Optional) The fields to return with each entry found, in addition to the .01 field, internal entry number, and any MUMPS identifiers on the file. Defaults to returning the internal entry number, the .01 field, and all identifiers. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) This parameter lets the caller adjust the Finder's algorithm. The possible values are: A Allow pure numeric input to always be tried as an IEN. M Multiple index lookup allowed. O Only find exact matches if possible. Q Quick lookup. X EXact matches only. VARIABLES: VALUE TYPE: Input VARIABLES DESCRIPTION: (Required) The lookup value. VARIABLES: NUMBER TYPE: Input VARIABLES DESCRIPTION: (Optional) The maximum number of entries to find. VARIABLES: INDEXES TYPE: Input VARIABLES DESCRIPTION: (Optional) The indexes the Finder should search for matches. VARIABLES: SCREEN TYPE: Input VARIABLES DESCRIPTION: (Optional) A screen to apply to each record found. VARIABLES: IDENTIFIER TYPE: Input VARIABLES DESCRIPTION: (Optional) The text to accompany each found entry to help identify it to the end user. VARIABLES: TARGET_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The array that should receive the output list of found entries. If not specified, the default location is descendent from ^TMP("DILIST",$J). When the calling application is finshed with the data the ^TMP("DILIST",$J) array may be killed. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The array that should receive any error messages. COMPONENT/ENTRY POINT: $$FIND1() COMPONENT DESCRIPTION: This extrinsic function finds a single record in a file based on an input value; if more than one match is found, the function returns an error. Format $$FIND1^DIC(FILE,IENS,FLAGS,VALUE,INDEXES,SCREEN,MSG_ROOT) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) This parameter should be the number of the file or subfile to search. If it is a subfile, it must be accompanied by the IENS parameter. VARIABLES: IENS TYPE: Input VARIABLES DESCRIPTION: (Optional) The IENS that identifies the subfile if FILE is a subfile number. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) This parameter lets the caller adjust the Finder's algorithm. The possible values are: A Allow pure numeric input to always be tried as an IEN. M Multiple index lookup allowed. O Only find exact matches if possible. Q Quick lookup. X EXact matches only. VARIABLES: VALUE TYPE: Input VARIABLES DESCRIPTION: (Required) The lookup value. VARIABLES: INDEXES TYPE: Input VARIABLES DESCRIPTION: (Optional) The indexes the Finder should search for a match. VARIABLES: SCREEN TYPE: Input VARIABLES DESCRIPTION: (Optional) A screen to apply to the record found. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The array that should receive any error messages. COMPONENT/ENTRY POINT: LIST() COMPONENT DESCRIPTION: This procedure, expected to be used to populate a GUI Listbox gadget, retrieves a list of records from a file. Format LIST^DIC(FILE,IENS,FIELDS,FLAGS,NUMBER,[.]FROM,PART,INDEX,SCREEN, IDENTIFIER,TARGET_ROOT,MSG_ROOT) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) The file whose entries are to be listed. This should equal the file or subfile number, depending on what the caller wishes to list. VARIABLES: IENS TYPE: Input VARIABLES DESCRIPTION: (Optional) If the FILE parameter equals a file number, don't pass the IENS parameter; it is not needed. If, on the other hand, the FILE parameter equals a subfile number, the Lister needs the IENS parameter to help identify which subfile to list. VARIABLES: FIELDS TYPE: Input VARIABLES DESCRIPTION: (Optional) The fields to return with each entry in the list instead of the field identifiers otherwise returned. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flags to control processing: B Backwards. (Defaults to traversing forward.) I Internal format is returned. VARIABLES: NUMBER TYPE: Input VARIABLES DESCRIPTION: (Optional) The number of entries to return. VARIABLES: [.]FROM TYPE: Both VARIABLES DESCRIPTION: Optional) The index entry from which to begin the list (e.g., a FROM value of "XQ" would list entries following XQ). VARIABLES: PART TYPE: Input VARIABLES DESCRIPTION: (Optional) The partial match restriction. VARIABLES: INDEX TYPE: Input VARIABLES DESCRIPTION: (Optional) The index from which to build the list. Defaults to "B". VARIABLES: SCREEN TYPE: Input VARIABLES DESCRIPTION: (Optional) The screen to apply to each potential entry in the returned list to decide whether or not to include it. This code can rely upon the following: Naked indicator Zero-node of entry's record. D Index being traversed. DIC Number of file being traversed. DIC(0) Flags passed to the Lister (direction). Y Record number of entry under consideration. Y() array For subfiles, descendants give record numbers for all upper levels. Structure resembles DA. Y1 IENS equivalent to Y array. VARIABLES: IDENTIFIER TYPE: Input VARIABLES DESCRIPTION: (Optional) The text to accompany each potential entry in the returned list to help identify it to the end user. VARIABLES: TARGET_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The array that should receive the output list. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The array that should receive any error messages. NUMBER: 2052 IA #: 2052 DATE CREATED: JUL 02, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DID NAME: Database Server API: Data Dictionary Utilities ID: DID GENERAL DESCRIPTION: Data dictionary utilities. FIELD: DD Field Retriever FIELDLST: DD Field List Retriever FILE: DD File Retriever FILELST: DD File List Retriever $$GET1: Attribute Retriever STATUS: Active MAIL MESSAGE: 28395021 COMPONENT/ENTRY POINT: FIELD() COMPONENT DESCRIPTION: This procedure retrieves the values of the specified field-level attributes for the specified field. Format FIELD^DID(FILE,FIELD,FLAGS,ATTRIBUTES,TARGET_ROOT,MSG_ROOT) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) File or subfile number. VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) Field name or number. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flags to control processing. The possible values are: N No entry in the target array is created if the attribute is null. Z Word processing attributes include "0" nodes with text. VARIABLES: ATTRIBUTES TYPE: Input VARIABLES DESCRIPTION: (Required) A list of attribute names separated by semicolons. Full attribute names must be used. Following are the attributes that can be requested: AUDIT AUDIT CONDITION COMPUTE ALGORITHM COMPUTED FIELDS USED DATE FIELD LAST EDITED DECIMAL DEFAULT DELETE ACCESS DESCRIPTION FIELD LENGTH GLOBAL SUBSCRIPT LOCATION HELP-PROMPT INPUT TRANSFORM LABEL MULTIPLE-VALUED OUTPUT TRANSFORM POINTER READ ACCESS SOURCE SPECIFIER TECHNICAL DESCRIPTION TITLE TYPE WRITE ACCESS XECUTABLE HELP VARIABLES: TARGET_ROOT TYPE: Both VARIABLES DESCRIPTION: (Required) The closed root of the array that should receive the attributes. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The name of a closed root reference that is used to pass error messages. If not passed, ^TMP("DIERR",$J) is used. COMPONENT/ENTRY POINT: FIELDLST() COMPONENT DESCRIPTION: This procedure returns a list of field-level attributes that are supported by FileMan. It shows specifically which attributes the Data Dictionary retriever calls can return. Format FIELDLST^DID(TARGET_ROOT) VARIABLES: TARGET_ROOT TYPE: Both VARIABLES DESCRIPTION: (Required) The root of an output array. Output TARGET_ROOT The descendants of the array root are subscripted by the attribute names. "WP" nodes indicate that the attribute consists of a word processing field. COMPONENT/ENTRY POINT: FILE() COMPONENT DESCRIPTION: This procedure retrieves the values of the file-level attributes for the specified file. It does not return subfile attributes. Format FILE^DID(FILE,FLAGS,ATTRIBUTES,TARGET_ROOT,MSG_ROOT) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) File number (but not subfile attributes). VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flags to control processing. The possible values are: N No entry in the target array is created if the attribute is null. Z Word processing attributes include Zero (0) nodes with text. VARIABLES: ATTRIBUTES TYPE: Input VARIABLES DESCRIPTION: (Required) A list of attribute names separated by semicolons. Full attribute names must be used: ARCHIVE FILE AUDIT ACCESS DATE DD ACCESS DEL ACCESS DESCRIPTION DEVELOPER DISTRIBUTION PACKAGE ENTRIES GLOBAL NAME LAYGO ACCESS LOOKUP PROGRAM NAME PACKAGE REVISION DATA REQUIRED IDENTIFIERS RD ACCESS VERSION WR ACCESS VARIABLES: TARGET_ROOT TYPE: Both VARIABLES DESCRIPTION: (Required) The name of a closed array reference. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The name of a closed root array reference that is used to pass error messages. If not passed, messages are returned in ^TMP("DIERR",$J). COMPONENT/ENTRY POINT: FILELST() COMPONENT DESCRIPTION: DD File List Retriever COMPONENT/ENTRY POINT: $$GET1() COMPONENT DESCRIPTION: This extrinsic function retrieves a single attribute from a single file or field. Format $$GET1^DID(FILE,FIELD,FLAGS,ATTRIBUTE,TARGET_ROOT,MSG_ROOT) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) File number. VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: Field number or name. (Required only when field attributes are being requested, otherwise this function assumes a file attribute is being requested). VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flag to control processing: Z Zero nodes on word processing attributes are included in the array subscripts. VARIABLES: ATTRIBUTE TYPE: Input VARIABLES DESCRIPTION: (Required) Data dictionary attribute name. VARIABLES: TARGET-ROOT TYPE: Both VARIABLES DESCRIPTION: Closed array reference where multi-lined attributes will be returned. (Required only when multi-line values are returned, such as word processing attributes like "DESCRIPTION"). VARIABLES: MSG-ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The name of a closed root reference that is used to pass error messages. If not passed, ^TMP("DIERR",$J) is used. NUMBER: 2053 IA #: 2053 DATE CREATED: JUL 02, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIE NAME: Data Base Server API: Editing Utilities ID: DIE GENERAL DESCRIPTION: Editing Utilities CHK: Data Checker FILE: Filer HELP: Helper UPDATE: Updater VAL: Validator WP: Word Processing Filer $$KEYVAL^DIE( ): Key Validator VALS^DIE( ): Fields Validator STATUS: Active MAIL MESSAGE: 30004955 COMPONENT/ENTRY POINT: CHK() COMPONENT DESCRIPTION: This procedure checks user-supplied data against the data dictionary definition of a field. Format CHK^DIE(FILE,FIELD,FLAGS,VALUE,.RESULT,MSG_ROOT) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) File or subfile number. VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) Field number for which data is being validated. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flags to control processing. The possible values are: H Help (single "?") is returned if VALUE is not valid. E External value is returned in RESULT(0). VARIABLES: VALUE TYPE: Input VARIABLES DESCRIPTION: (Required) Value to be validated, as entered by a user. VARIABLES: .RESULT TYPE: Both VARIABLES DESCRIPTION: (Required) Local variable that receives output from the call. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) Root into which error, help, and message arrays are put. If this parameter is not passed, these arrays are put into nodes descendent from ^TMP. COMPONENT/ENTRY POINT: FILE() COMPONENT DESCRIPTION: This procedure: Puts validated data that is in internal FileMan format into the database. OR: Validates data that is in external (user-provided) format, converts it to internal FileMan format, and files valid data into the database. Format FILE^DIE(FLAGS,FDA_ROOT,MSG_ROOT) VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flags to control processing. The possible values are: K LocKing is done by the Filer. (See discussion of Locking below.) S Save FDA. If this flag is not set and there were no errors during the filing process, the FDA is deleted. If this flag is set, the array is never deleted. E External values are processed. If this flag is set, the values in the FDA must be in the format input by the user. The value is validated and filed if it is valid. If the flag is not set, values must be in internal format and must be valid; no validation or transformation is done by the Filer VARIABLES: FDA_ROOT TYPE: Input VARIABLES DESCRIPTION: (Required) The root of the FDA that contains the data to file. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The root of an array (local or global) into which error messages are returned. If this parameter is not included, error messages are returned in the default array-^TMP("DIERR",$J). COMPONENT/ENTRY POINT: HELP() COMPONENT DESCRIPTION: This procedure retrieves user-oriented help for a field from the Data Dictionary and other sources. Format HELP^DIE(FILE,IENS,FIELD,FLAGS,MSG_ROOT) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) File or subfile number. VARIABLES: IENS TYPE: Input VARIABLES DESCRIPTION: (Optional) Standard IENS indicating internal entry numbers. VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) Field number for which help is requested. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Required) Flags used to determine what kind of help is returned by the call. If a lower case letter is shown, use it to suppress that kind of help-useful in conjunction with ? or ??. The possible values are: ? Help equivalent to user entering one "?" at an edit prompt. (Also help returned for an invalid response.) ?? Help equivalent to user entering "??" at an edit prompt. A All available help for the field. F Fields that can be used for lookups. Returned for top-level .01 fields and for pointed-to files for pointer data types. For pointed-to files, the "F" flag is effective only if the "G" flag is also sent. H Help prompt text. X Xecutable help-the MUMPS code contained in Xecutable Help is executed. In order to have the help returned in an array, the executed code must use EN^DDIOL to load the help message. D Description text for the field; this may be multiple lines. P Pointer screen description. C Set of Codes screen description. T Date/Time generic help. This help text is customized based on the allowable and required elements of the particular Date/Time field. S Set of codes possible choices. Any screen that exists on the set of codes field is applied so that only actually selectable choices are presented. U Unscreened set of codes choices. V Variable pointer help that lists the prefixes and messages associated with a particular variable pointer field. B (b) Brief variable pointer help. A INTEGRATION REFERENCES LIST MAR 18,2015 11:24 PAGE 6 -------------------------------------------------------------------------------- single line beginning with "To see the entries ...". M More variable pointer help. Detailed description of how to enter variable pointer data. G (g) getting help from pointed-to file. Help for the .01 field of pointed-to file is returned. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) Closed root into which the output from the call is put. If not supplied, output is returned in ^TMP. VARIABLES: DIHELP TYPE: Output VARIABLES DESCRIPTION: Number of lines of help text returned VARIABLES: TMP("DIHELP",$J,n) TYPE: Output VARIABLES DESCRIPTION: Array containing the lines of help text. The text is found in integer subscripted nodes (n), beginning with 1. A blank node is inserted between each different type of help returned. COMPONENT/ENTRY POINT: UPDATE() COMPONENT DESCRIPTION: This procedure adds new entries in files or subfiles. Format UPDATE^DIE(FLAGS,FDA_ROOT,IEN_ROOT,MSG_ROOT) VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flags to control processing. The possible values are: E External values are processed. If this flag is set, the values in the FDA must be in the format input by the user. The Updater validates all values and converts them to internal format. Invalid values cancel the entire transaction. If the flag is not set, values must be in internal format and must be valid. S The Updater Saves the FDA instead of killing it at the end. VARIABLES: FDA_ROOT TYPE: Input VARIABLES DESCRIPTION: (Required) The name of the root of a FileMan Data Array, which describes the entries to add to the database. VARIABLES: IEN_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The name of the Internal Entry Number Array (or IEN Array). Output: As the Updater assigns record numbers to the records described in the FDA, it sets up nodes in the IEN Array to indicate how it decoded the sequence numbers. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The array that should receive any error messages. If the MSG_ROOT is not passed, errors are returned descendent from ^TMP("DIERR",$J). COMPONENT/ENTRY POINT: VAL() COMPONENT DESCRIPTION: The purpose of the Validator procedure is to take the external form of user input and determine if that value is valid. Format VAL^DIE(FILE,IENS,FIELD,FLAGS,VALUE,.RESULT,FDA_ROOT,MSG_ROOT) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) File or subfile number. VARIABLES: IENS TYPE: Input VARIABLES DESCRIPTION: (Required) Standard IENS indicating internal entry numbers. VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) Field number for which data is being validated. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flags to control processing. The possible values are: E External value is returned in RESULT(0). F FDA node is set for valid data in array identified by FDA_ROOT. H Help (single ?) is returned if VALUE is not valid. R Record identified by IENS is verified to exist and to be editable. Do not include "R" if there are placeholders in the IENS. VARIABLES: VALUE TYPE: Input VARIABLES DESCRIPTION: (Required) Value to be validated as input by a user. VARIABLES: .RESULT TYPE: Both VARIABLES DESCRIPTION: (Required) Local variable which receives output from call. VARIABLES: FDA_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional; required if F flag present) Root of FDA into which internal value is loaded if F flag is present. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) Root into which error, help, and message arrays are put. If this parameter is not passed, these arrays are put into nodes descendent from ^TMP. COMPONENT/ENTRY POINT: WP() COMPONENT DESCRIPTION: This procedure files a single word processing field. Format WP^DIE(FILE,IENS,FIELD,FLAGS,WP_ROOT,MSG_ROOT) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) File or subfile number. VARIABLES: IENS TYPE: Input VARIABLES DESCRIPTION: (Required) Standard IENS indicating internal entry numbers. VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) Field number of the word processing field into which data is being filed. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flags to control processing. The possible values are: A Append new word processing text to the current word processing data. If this flag is not sent, the current contents of the word processing field are completely erased before the new word processing data is filed. K LocK the entry or subentry before changing the word processing data. VARIABLES: WP_ROOT TYPE: Input VARIABLES DESCRIPTION: (Required) The root of the array that contains the word processing data to be filed. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) Root into which errors are put. If this parameter is not passed, these arrays are put into nodes descendent from ^TMP. COMPONENT/ENTRY POINT: $$KEYVAL() COMPONENT DESCRIPTION: The Key Validator extrinsic function verifies that new values contained in the FDA do not produce an invalid key. All keys in which any field in the FDA participates are checked. If the value for a field in a key being checked is not present in the FDA, the value used to verify the key is obtained from the previously filed data. Format $$KEYVAL^DIE(FLAGS,FDA_ROOT,MSG_ROOT) VARIABLES: FLAGS TYPE: Both VARIABLES DESCRIPTION: (Optional) Flags to control processing. The possible values are: Q = Quit when the first problem in the FDA is encountered. VARIABLES: FDA_ROOT TYPE: Both VARIABLES DESCRIPTION: (Required) The root of the FDA that contains the data to be checked. The array can be a local or global one. See the Database Server Introduction for details of the structure of the FDA. The value of fields in the FDA must be the internal value. Do not pass external (e.g., unresolved pointer values, non-FileMan dates) in the FDA. No action is taken on fields in the referenced FDA if those fields do not participate in a Key defined in the KEY file. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The root of an array into which error messages are returned. If this parameter is not included, errors are returned in the default array: ^TMP("DIERR",$J). VARIABLES: 0/1 TYPE: Output VARIABLES DESCRIPTION: The function returns a 1 if key integrity is not violated by any value in the FDA and a 0 if an invalid key was produced by any of the values. COMPONENT/ENTRY POINT: VALS() COMPONENT DESCRIPTION: The Fields Validator procedure validates data for a group of fields and converts valid data to internal VA FileMan format. It is intended for use with a set of fields that comprise a logical record; fields from more than one file can be validated by a single call. By default, the integrity of any keys affected by the new values is checked. The Fields Validator performs the same checks performed by VAL^DIE (see for details). Format VALS^DIE(FLAGS,FDA_EXT_ROOT,FDA_INT_ROOT,MSG_ROOT) VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flags to control processing. The possible values are: K - If the file has a Primary Key, this flag indicates that the Primary Key fields, not the .01 field, are to be used for lookup in the Finding and LAYGO/Finding nodes of the FDA. Without this flag, VALS^DIE assumes that you want to file the fields in the Primary Key, rather than use them for lookup, and performs the uniqueness check. This flag is equivalent to the "K" flag in the Updater (UPDATE^DIE). R - Records identified by IENSs in the FDA_EXT are verified to exist and to be editable. (Same as R flag for VAL^DIE.) U - Don't perform key validation. Without this flag, the data in the FDA is checked to ensure that no duplicate keys are created and that key field values are not deleted. VARIABLES: FDA_EXT_ROOT TYPE: Input VARIABLES DESCRIPTION: (Required) The root of a standard FDA. This array should contain the external values that you want to validate. This is the input array. See the Database Server Introduction for details of the structure of the FDA. VARIABLES: FDA_INT_ROOT TYPE: Both VARIABLES DESCRIPTION: (Required) The root of a standard FDA. This FDA is the output array, and upon return is set equal to the internal values of each validated field. If a field fails validation, its value is set to an up-arrow (^). (NOTE: If a field is valid, the corresponding node in the output array is set to the internal value, not an up-arrow (^), even if that field violates key integrity.) See the Database Server Introduction for details of the structure of the FDA VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The root of an array (local or global) into which error messages are returned. If this parameter is not included, error messages are returned in the default array: ^TMP("DIERR",$J). NUMBER: 2054 IA #: 2054 DATE CREATED: JUL 02, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DILF NAME: Data Base Server API: Misc. Library Functions ID: DILF GENERAL DESCRIPTION: Various libaray functions. CLEAN: Array and Variable Clean-up $$CREF: Root Converter (Open to Closed Format) DA: DA( ) Creator DT: Date Converter FDA: FDA Loader $$IENS: IENS Creator $$OREF: Root Converter (Closed to Open Format) $$VALUE1: FDA Value Retriever (Single) VALUES: FDA Values Retriever STATUS: Active MAIL MESSAGE: 28396452 COMPONENT/ENTRY POINT: CLEAN COMPONENT DESCRIPTION: This procedure kills the standard message arrays and variables that are produced by VA FileMan. VARIABLES: None COMPONENT/ENTRY POINT: $$CREF() COMPONENT DESCRIPTION: This extrinsic function converts the traditional open root format to the closed root format used by subscript indirection. Format $$CREF^DILF(OPEN_ROOT) VARIABLES: OPEN_ROOT TYPE: Input VARIABLES DESCRIPTION: (Required) An open root which is a global root ending in either an open parenthesis or a comma. COMPONENT/ENTRY POINT: DA() COMPONENT DESCRIPTION: This procedure converts an IENS into an array with the structure of a DA() array. Format DA^DILF(IENS,.DA) VARIABLES: IENS TYPE: Input VARIABLES DESCRIPTION: (Required) A string with record and subrecord numbers in IENS format. VARIABLES: .DA TYPE: Both VARIABLES DESCRIPTION: (Required) The name of the array which receives the record numbers. NOTE: This array is cleaned out (killed) before the record numbers are loaded. COMPONENT/ENTRY POINT: DT() COMPONENT DESCRIPTION: This procedure converts a user-supplied value into VA FileMan's internal date format and (optionally) into the standard VA FileMan external, readable date format. Format DT^DILF(FLAGS,IN_DATE,.RESULT,LIMIT,MSG_ROOT) VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Control processing of user input and the type of output returned. Generally, FLAGS is the same as %DT input variable to ^%DT entry point, with the following exceptions: "A" is not allowed and the meaning of "E" is different (see below). The possible values are: E External, readable date returned in zero-node of RESULT. F Future dates are assumed. N Numeric-only input is not allowed. P Past dates are assumed. R Required time input. S Seconds will be returned. T Time input is allowed but not required. X EXact date (with month and day) is required. VARIABLES: IN_DATE TYPE: Input VARIABLES DESCRIPTION: (Required) Date input as entered by the user in any of the formats known to VA FileMan. VARIABLES: .RESULT TYPE: Both VARIABLES DESCRIPTION: (Required) Local array that receives the internal value of the date/time and, if the "E" flag is sent, the readable value of the date. Output Output is returned in the local array passed by reference in the RESULT parameter, shown below: RESULT Date in internal FileMan format. If input is invalid or if help is requested with a "?", -1 is returned. RESULT(0) If requested, date in external, readable format. When appropriate, error messages and help text are returned in the standard manner in ^TMP or in MSG_ROOT (if it is specified). VARIABLES: LIMIT TYPE: Input VARIABLES DESCRIPTION: (Optional) A value equal to a date/time in FileMan internal format or NOW. IN_DATE is accepted only if it is greater than or equal to LIMIT if it is positive, or less than or equal to LIMIT if it is negative. This is equivalent to the %DT(0) variable in the ^%DT call. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) Root into which error, help, and message arrays are put. COMPONENT/ENTRY POINT: FDA() COMPONENT DESCRIPTION: This procedure can be used to load data into the FDA. It accepts either the traditional DA( ) array or the IENS for specifying the entry. No validation of VALUE is done. Format 1. FDA^DILF(FILE,IENS,FIELD,FLAGS,VALUE,FDA_ROOT,MSG_ROOT) 2. FDA^DILF(FILE,.DA,FIELD,FLAGS,VALUE,FDA_ROOT,MSG_ROOT) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) File or subfile number. VARIABLES: .DA TYPE: Input VARIABLES DESCRIPTION: (Required for format 2) DA() array containing entry and subentry numbers. VARIABLES: IENS TYPE: Input VARIABLES DESCRIPTION: (Required for format 1) Standard IENS indicating internal entry numbers. VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) Field number for which data is being loaded into the FDA. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flag to control processing: R Record identified by IENS or .DA is verified to exist. Do not use the "R" FLAG if the IENS or DA() array contain placeholder codes instead of actual record numbers. VARIABLES: VALUE TYPE: Input VARIABLES DESCRIPTION: (Required, can be null) Value to which the FDA node will be set. VARIABLES: FDA_ROOT TYPE: Both VARIABLES DESCRIPTION: (Required) The root of the FDA in which the new node is loaded. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) Root into which error, help, and message arrays are put. If this parameter is not passed, these arrays are put into nodes descendent from ^TMP. COMPONENT/ENTRY POINT: $$IENS() COMPONENT DESCRIPTION: This extrinsic function returns the IENS when passed an array in the traditional DA() structure. Format $$IENS^DILF(.DA) VARIABLES: .DA TYPE: Both VARIABLES DESCRIPTION: Input Parameters .DA (Required) An array with the structure of the traditional VA FileMan DA() array-that is, DA=lowest subfile record number, DA(1)=next highest subfile record number, etc. Output A string of record numbers in the IENS format-that is, "DA,DA(1),...DA(n),". COMPONENT/ENTRY POINT: $$OREF() COMPONENT DESCRIPTION: This extrinsic function converts a closed root to an open root. It converts an ending close parenthesis to a comma. Format $$OREF^DILF(CLOSED_ROOT VARIABLES: CLOSED_ROOT TYPE: Input VARIABLES DESCRIPTION: (Required) A closed root, which is a global root ending in a closed parenthesis. COMPONENT/ENTRY POINT: $$VALUE1() COMPONENT DESCRIPTION: This extrinsic function returns the value associated with a particular file and field in a standard FDA. Only a single value is returned. Format $$VALUE1^DILF(FILE,FIELD,FDA_ROOT) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) File or subfile number. VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) Field number for which data is being requested. VARIABLES: FDA_ROOT TYPE: Input VARIABLES DESCRIPTION: (Required) The root of the FDA from which data is being requested. COMPONENT/ENTRY POINT: VALUES() COMPONENT DESCRIPTION: This procedure returns values from an FDA for a specified field. Format VALUES^DILF(FILE,FIELD,FDA_ROOT,.RESULT) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) File or subfile number. VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) Field number for which data is being requested. VARIABLES: FDA_ROOT TYPE: Input VARIABLES DESCRIPTION: (Required) The root of the FDA from which data is being requested. VARIABLES: .RESULT TYPE: Both VARIABLES DESCRIPTION: (Required) Local array that receives output from the call. The array is killed at the beginning of each call. COMPONENT/ENTRY POINT: LOCK() COMPONENT DESCRIPTION: The purpose is to lock a global reference using VA FileMan's Lock time out value(DILOCKTM). Format: LOCK^DILF(resolved global reference) Input: RESOLVED GLOBAL REFERENCE - (Required)This is the fully resolved global reference. Output: $Truth value - 1 equals lock obtained; 0 equals lock failed Example: >S REF="^MYFILE(123,1,0)" >D LOCK^DILF(REF) >W $T 1 >W DILOCKTM 3 VARIABLES: REF TYPE: Both VARIABLES DESCRIPTION: Input: RESOLVED GLOBAL REFERENCE - (Required) This is the fully resolved global reference. Output: $Truth value - 1 equals lock obtained; 0 equals lock failed. EDITOR: ORMSBY,SKIP DBA Comments: 2006-10-2006/JSH Turned off Active and Approved to allow S. Ormsby to modify the entry. DATE/TIME EDITED: OCT 20, 2006@17:00 ACTION: CONTENT CORRECTED AT THE REQUEST OF: ORMSBY,SKIP WITH CONCURRENCE OF: HARVEY,JULIE NUMBER: 2055 IA #: 2055 DATE CREATED: JUL 02, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DILFD NAME: Data Base Server API: Misc. Data Libaray Functions ID: DILFD GENERAL DESCRIPTION: Data libaray functions. $$EXTERNAL: Converter to External $$FLDNUM: Field Number Retriever PRD: Package Revision Data Initializer RECALL: Recall Record Number $$ROOT: File Root Resolver $$VFIELD: Field Verifier $$VFILE: File Verifier STATUS: Active MAIL MESSAGE: 28397443 COMPONENT/ENTRY POINT: $$EXTERNAL() COMPONENT DESCRIPTION: This extrinsic function converts any internal value to its external format. Format $$EXTERNAL^DILFD(FILE,FIELD,FLAGS,INTERNAL,MSG_ROOT) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) The number of the file or subfile that contains the field that describes the internal value passed in. VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) The number of the field that describes the internal value passed in. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) A single-character code that explains how to handle output transforms found along pointer chains. F First. If the first field in a pointer chain has an output transform, apply the transform to that first field and quit. Ignore any other output transforms found along the pointer chain. With the exception of this function, FileMan regularly handles output transforms this way. L Last. If the last field in a pointer chain has an output transform, apply the transform to that last field and quit. Ignore any other output transforms found along the pointer chain. U Use. Use the first output transform found on the last field in the pointer chain. Following the pointer chain, watch for output transforms. When one is found, remember it, but keep following the pointer chain. When the last field in the chain is reached, apply the remembered transform to that last field. VARIABLES: INTERNAL TYPE: Input VARIABLES DESCRIPTION: (Required) The internal value that is to be converted to its external format. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The array that should receive any error messages. If the MSG_ROOT is not passed, errors are returned descendent from ^TMP("DIERR",$J). COMPONENT/ENTRY POINT: $$FLDNUM() COMPONENT DESCRIPTION: This extrinsic function returns a field number when passed a file number and a field name. Format $$FLDNUM^DILFD(FILE,FIELDNAME) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) The file number of the field's file or subfile. VARIABLES: FIELDNAME TYPE: Input VARIABLES DESCRIPTION: (Required) The full name of the field for which you want the number. COMPONENT/ENTRY POINT: PRD() COMPONENT DESCRIPTION: This procedure sets the PACKAGE REVISION DATA attribute for a file. Format PRD^DILFD(FILE,DATA) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) File or subfile number. VARIABLES: DATA TYPE: Input VARIABLES DESCRIPTION: (Required) Free text information, determined by the developer. COMPONENT/ENTRY POINT: RECALL() COMPONENT DESCRIPTION: This procedure saves a record number for later retrieval using spacebar recall. Format RECALL^DILFD(FILE,IENS,USER) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) The file or subfile number. VARIABLES: IENS TYPE: Input VARIABLES DESCRIPTION: (Required) The IENS that identifies the record selected. VARIABLES: USER TYPE: Input VARIABLES DESCRIPTION: (Required) The user number (i.e., DUZ) of the user who made the selection. COMPONENT/ENTRY POINT: $$ROOT() COMPONENT DESCRIPTION: This extrinsic function resolves the file root when passed file or subfile numbers. Format $$ROOT^DILFD(FILE,IENS,FLAGS,ERROR_FLAG) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) File number or subfile number. VARIABLES: IENS TYPE: Input VARIABLES DESCRIPTION: (Required when passing subfile numbers) Standard IENS indicating internal entry number. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) If set to 1 (true), returns a closed root. The default is to return an open root. VARIABLES: ERROR_FLAG TYPE: Input VARIABLES DESCRIPTION: (Optional) If set to 1 (true), processes an error message if error is encountered. COMPONENT/ENTRY POINT: $$VFIELD() COMPONENT DESCRIPTION: This extrinsic function verifies that a field in a specified file exists. Format $$VFIELD^DILFD(FILE,FIELD) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) The number of the file or subfile in which the field to be checked exists. VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) The number of the field to be checked. COMPONENT/ENTRY POINT: $$VFILE() COMPONENT DESCRIPTION: This extrinsic function verifies that a file exists. Format $$VFILE^DILFD(FILE) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) The number of the file or subfile that you want to check. EDITOR: ORMSBY,SKIP NUMBER: 2056 IA #: 2056 DATE CREATED: JUL 02, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIQ NAME: Data Base Server API: Data Retriever Utilities ID: DIQ GENERAL DESCRIPTION: Data retriever utilities. $$GET1: Single Data Retriever GETS: Multiple Data Retriever STATUS: Active MAIL MESSAGE: 28398720 COMPONENT/ENTRY POINT: $$GET1() COMPONENT DESCRIPTION: This procedure retrieves one or more fields of data from a record or sub-record(s) and places the values in a target array. Format GETS^DIQ(FILE,IENS,FIELD,FLAGS,TARGET_ROOT,MSG_ROOT) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) File or subfile number. VARIABLES: IENS TYPE: Input VARIABLES DESCRIPTION: (Required) Standard IENS indicating internal entry numbers. VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) Can be one of the following: A single field number A list of field numbers, separated by semicolons A range of field numbers, in the form M:N, where M and N are the end points of the inclusive range. All field numbers within this range are retrieved. * for all fields at the top level (no sub-multiple record). ** for all fields including all fields and data in sub-multiple fields. Field number of a multiple followed by an * to indicate all fields and records in the sub-multiple for that field. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flags to control processing. The possible values are: E Returns External values in nodes ending with "E". I Returns Internal values in nodes ending with "I". (Otherwise, external is returned). N Does not return Null values. R Resolves field numbers to field names in target array subscripts. Z Word processing fields include Zero nodes. VARIABLES: TARGET_ROOT TYPE: Both VARIABLES DESCRIPTION: (Required) The name of a closed root reference. Output: The output array is in the FDA format, i.e., TARGET_ROOT(FILE,IENS,FIELD)=DATA. WP fields have data descendent from the field nodes in the output array. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The name of a closed root reference that is used to pass error messages. COMPONENT/ENTRY POINT: GETS() COMPONENT DESCRIPTION: This procedure retrieves one or more fields of data from a record or sub-record(s) and places the values in a target array. Format GETS^DIQ(FILE,IENS,FIELD,FLAGS,TARGET_ROOT,MSG_ROOT) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) File or subfile number. VARIABLES: IENS TYPE: Input VARIABLES DESCRIPTION: (Required) Standard IENS indicating internal entry numbers. VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) Can be one of the following: A single field number A list of field numbers, separated by semicolons A range of field numbers, in the form M:N, where M and N are the end points of the inclusive range. All field numbers within this range are retrieved. * for all fields at the top level (no sub-multiple record). ** for all fields including all fields and data in sub-multiple fields. Field number of a multiple followed by an * to indicate all fields and records in the sub-multiple for that field. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flags to control processing. The possible values are: E Returns External values in nodes ending with "E". I Returns Internal values in nodes ending with "I". (Otherwise, external is returned). N Does not return Null values. R Resolves field numbers to field names in target array subscripts. Z Word processing fields include Zero nodes. VARIABLES: TARGET_ROOT TYPE: Both VARIABLES DESCRIPTION: (Required) The name of a closed root reference. Output: The output array is in the FDA format, i.e., TARGET_ROOT(FILE,IENS,FIELD)=DATA. WP fields have data descendent from the field nodes in the output array. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The name of a closed root reference that is used to pass error messages. EDITOR: ORMSBY,SKIP NUMBER: 2058 IA #: 2058 FILE NUMBER: 9.4 GLOBAL ROOT: DIC(9.4, DATE CREATED: JUL 07, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PACKAGE FILE LOOKUP ID: DIC(9.4, GLOBAL REFERENCE: DIC(9.4,B,PACKAGE NAME,IEN) GLOBAL DESCRIPTION: uses B x-ref to get IEN for given package name GLOBAL REFERENCE: DIC(9.4,C,PREFIX,IEN) GLOBAL DESCRIPTION: Uses C index to get IEN for a given package prefix GLOBAL REFERENCE: DIC(9.4,IEN,0) FIELD NUMBER: 1 FIELD NAME: PREFIX LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: gets PREFIX for existing package FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: With the addition of the new Parameter Tools functionality, Lab has need to retrieve the package file internal entry number and the namespace. Lab would like permission to retrieve the IEN of the package file by referencing the B and C indexes. Additionally, a direct access of the PREFIX field is requested. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30447311 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Salt Lake City SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING DETAILS: Only good for version 4.5 of Outpatient Pharmacy SUBSCRIBING PACKAGE: INTEGRATED BILLING SUBSCRIBING DETAILS: Looking up the IEN for the KERNEL package and lookup is only being done in a post-install routine. Using the IEN as an input to the function PUT^XPAR to define an entry in file 8989.5 (PARAMETERS) for XUSNPI QUALIFIED IDENTIFIER. 1 SUBSCRIBING PACKAGE: EVENT CAPTURE SUBSCRIBING DETAILS: ADDED 2/28/2012 EDITOR: INSLEY,MARCIA DATE/TIME EDITED: JAN 24, 2007@22:34 ACTION: USAGE CHOICE CHANGED AT THE REQUEST OF: WHITE,DARLENE WITH CONCURRENCE OF: FORT,WALLY DATE/TIME EDITED: JAN 24, 2007@22:35 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHITE,DARLENE WITH CONCURRENCE OF: FORT,WALLY DATE/TIME EDITED: FEB 29, 2012@13:48 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: NABER,DAVID WITH CONCURRENCE OF: BEUSCHEL,GARY NUMBER: 2060 IA #: 2060 FILE NUMBER: 100 GLOBAL ROOT: OR(100, DATE CREATED: JUL 09, 1997 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: LAB USE OF OR(100, ID: OR(100, CREATOR: CRUMLEY,JAMIE GLOBAL REFERENCE: OR(100,DA,0) FIELD NUMBER: 4 FIELD NAME: CURRENT AGENT/PROVIDER LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Lab checks for existence of an order ($D(^OR(100,DA,0)) as wel as the value in field #4. GLOBAL REFERENCE: OR(100,DA,3) FIELD NUMBER: 5 FIELD NAME: STATUS LOCATION: 3;3 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: OR(100,DA(1),8,DA,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME ORDERED LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: OR(100,'AN' GLOBAL DESCRIPTION: Reference to the AN cross reference is needed in the OE/RR 2.5 interface to clean-up old lab notifications. This is not used with OE/RR 3.0. GLOBAL REFERENCE: OR(100,DA,4) FIELD NUMBER: 33 FIELD NAME: PACKAGE REFERENCE LOCATION: 4;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: OR(100,DA,6) FIELD NUMBER: 65 FIELD NAME: DC REASON TEXT LOCATION: 6;5 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Lab needs to access the ORDERS file (#100) as part of its interface with the Order Entry/Results Reporting package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30260277 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING DETAILS: DBA Comments: Package Reference (#33) field added to support Lab Re-Engineering installations. DC Reason Text (#65) was added as a result of SQA review. It was discovered Lab was using this field but it had not been added to the ICR. Patches are LR*5.2*393 and LR*5.2*383. 3/29/13-MM: Added comment regarding patch LR*5.2*393: LR*5.2*393 is part of the Laboratory System Re-engineering Project. This patch has been installed at the Huntington VAMC. As of 3/25/13, it is not known if or when the patch will be nationally released. There is also a possibility a different LR patch will release this functionality. DATE ACTIVATED: APR 13, 2012 DATE/TIME EDITED: MAR 07, 2012@16:40 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CRUMLEY,JAMIE DATE/TIME EDITED: APR 13, 2012@16:49 ACTION: APPROVED AT THE REQUEST OF: CRUMLEY,JAMIE WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 2061 IA #: 2061 FILE NUMBER: 3.8 GLOBAL ROOT: XMB(3.8 DATE CREATED: JUL 11, 1997 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2061 ID: XMB(3.8 GLOBAL REFERENCE: XMB(3.8,D1,6, FIELD NUMBER: .01 FIELD NAME: MEMBERS - REMOTE LOCATION: 0;1 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: This is an agreement for FileMan read/write access to subfile 3.812, (#12) MEMBERS - REMOTE. STATUS: Active MAIL MESSAGE: 24380811 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: NATIONAL DRUG FILE ISC: Birmingham SUBSCRIBING PACKAGE: person.idmgmt SUBSCRIBING DETAILS: Person Services has a need to obtain remote member information DBA Comments: JSH 2006-11-3/ Added person service id to subscribers as per Mary Marks/PSID and Tom Kehoe/VMP DATE/TIME EDITED: NOV 03, 2006@13:54 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MARKS,MARY WITH CONCURRENCE OF: KEHOE,THOMAS NUMBER: 2065 IA #: 2065 FILE NUMBER: 409.68 GLOBAL ROOT: SCE( DATE CREATED: JUL 21, 1997 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2065 ID: SCE( GLOBAL REFERENCE: SCE(DA,0) FIELD NUMBER: .03 FIELD NAME: CLINIC STOP CODE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: LOCATION LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .05 FIELD NAME: VISIT FILE ENTRY LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: PARENT ENCOUNTER LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .08 FIELD NAME: ORIGINATING PROCESS TYPE LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: SCE('ADFN' GENERAL DESCRIPTION: This will permit direct reads using the "ADFN" cross reference of the OUTPATIENT ENCOUNTER file (#409.68). This will be used to find an encounter associated with a specific patient for a specific date via ^SCE("ADFN",PATIENT,DATE,D0). Once the "ADFN" cross-reference has been used to determine if an entry exists, the entry will be viewed by a direct global read of the 0-node, and using the following fields: .03 - CLINIC STOP CODE; .04 - LOCATION; .05 - VISIT FILE ENTRY; .06 - PARENT ENCOUNTER; and .08 - ORIGINATING PROCESS TYPE. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 35910754 SUBSCRIBING PACKAGE: HEALTH SUMMARY SUBSCRIBING PACKAGE: WOMEN'S HEALTH ISC: Hines SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK DATE/TIME EDITED: SEP 16, 2010@10:55 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE NUMBER: 2067 IA #: 2067 DATE CREATED: JUL 22, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XPDIP NAME: UPDATE PACKAGE APPLICATION HISTORY ID: XPDIP GENERAL DESCRIPTION: This function can be used during the Pre or Post Install routine to update the PATCH APPLICATION HISTORY of the VERSION multiple in the PACKAGE file. STATUS: Active MAIL MESSAGE: 28287373 COMPONENT/ENTRY POINT: $$PKGPAT(package ien, version, .X) COMPONENT DESCRIPTION: Update the PATCH APPLICATION HISTORY of the VERSION multiple in the PACKAGE file. VARIABLES: package ien TYPE: Input VARIABLES DESCRIPTION: PACKAGE file entry ien. VARIABLES: version TYPE: Input VARIABLES DESCRIPTION: This is the version number, must contain a decimal. i.e. 8.0 VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: ARRAY needs to be passed by reference if you want to update the DESCRIPTION field in the PATCH APPLICATION HISTORY multiple. ARRAY = patch number^date installed^installed by patch number = number SEQ#number, i.e. 51 SEQ #32 date installed = Fileman format, use DT installed by = user ien, use DUZ ARRAY(1) = closed global root of location of Description i.e. ^XTMP($J,""WP"") VARIABLES: $$PKGPAT TYPE: Output VARIABLES DESCRIPTION: version ien^patch ien NUMBER: 2068 IA #: 2068 DATE CREATED: JUL 24, 1997 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE CUSTODIAL ISC: Washington USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: AR PACKAGE FILE UPDATE GENERAL DESCRIPTION: This is a one time agreement to allow the updating of patch information in the AR package file for a consolidated patch release. VIEWER: SCHLEHUBER,CAMERON VIEWER: RHODES,CHRISTINE VIEWER: SURI,ASHWANI STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: SEP 1997 MAIL MESSAGE: 24516455 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Washington/Silver Spring NUMBER: 2069 IA #: 2069 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: JUL 24, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2069 ID: DPT( GLOBAL REFERENCE: DPT(D0,.32) FIELD NUMBER: DPT(D0,.32) FIELD NAME: PERIOD OF SERVICE ACCESS: Read w/Fileman GLOBAL REFERENCE: DPT(D0,.322) FIELD NUMBER: .32201 FIELD NAME: PERSIAN GULF SERVICE? ACCESS: Read w/Fileman GENERAL DESCRIPTION: The patient Representative package would like to reference two fields from the patient file, and stuff the information into the 0 node of file 745.1 (CONSUMER CONTACT file). .323 Period of Service .32201 Persian Gulf Service STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PATIENT REPRESENTATIVE ISC: Washington/Silver Spring NUMBER: 2070 IA #: 2070 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: AUG 04, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2070 ID: DPT( GLOBAL REFERENCE: DPT(D0,'MPI', FIELD NUMBER: 991.01 FIELD NAME: INTEGRATION CONTROL NUMBER LOCATION: MPI;1 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: The FM r/w is to allow the Master Patient Index VistA package to retrieve and update the Integration Control Number field via APIs. FIELD NUMBER: 991.02 FIELD NAME: ICN CHECKSUM LOCATION: MPI;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: 991.03 FIELD NAME: CIRN MASTER OF RECORD LOCATION: MPI;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: 991.04 FIELD NAME: LOCALLY ASSIGNED ICN LOCATION: MPI;4 ACCESS: Both R/W w/Fileman FIELD NUMBER: 991.05 FIELD NAME: SUBSCRIPTION CONTROL NUMBER LOCATION: MPI;5 ACCESS: Both R/W w/Fileman FIELD NUMBER: 991.06 FIELD NAME: CMOR ACTIVITY SCORE LOCATION: MPI;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: 991.07 FIELD NAME: SCORE CALCULATION DATE LOCATION: MPI;7 ACCESS: Both R/W w/Fileman FIELD NUMBER: 991.01 FIELD NAME: INTEGRATION CONTROL NUMBER LOCATION: MPI;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The Direct Read access is to support the seeding process of the last treatment date field in the Treating Facility file in the RG*1*4 patch. The direct read will minimize the number of disk hits and effeciency of disk hits and effeciency of the seeding which affects thousands of entries. GLOBAL REFERENCE: DPT('ACMOR', FIELD NUMBER: 991.03 FIELD NAME: CIRN MASTER OF RECORD LOCATION: x-ref ACCESS: Direct Global R/W & w/Fileman GLOBAL REFERENCE: DPT('ACMORS', FIELD NUMBER: 991.06 FIELD NAME: CMOR ACTIVITY SCORE LOCATION: x-ref ACCESS: Direct Global R/W & w/Fileman GLOBAL REFERENCE: DPT('AICN', FIELD NUMBER: 991.01 FIELD NAME: INTEGRATION CONTROL NUMBER LOCATION: x-ref ACCESS: Direct Global R/W & w/Fileman GLOBAL REFERENCE: DPT('AICNL', FIELD NUMBER: 991.04 FIELD NAME: LOCALLY ASSIGNED ICN LOCATION: x-ref ACCESS: Direct Global R/W & w/Fileman GLOBAL REFERENCE: DPT('AMPIMIS', FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: x-ref ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Temporary cross reference that lets the MPI Missing ICN job know that a patient was added to the Patient file, via another package other than PIMS, and needs to get an ICN. Once the ICN is assigned (local or national) the cross reference is killed. GLOBAL REFERENCE: DPT('AHICN', FIELD NUMBER: 991.01 FIELD NAME: INTEGRATION CONTROL NUMBER LOCATION: x-ref ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Used to create ICN History, ICN lookup capability. GLOBAL REFERENCE: DPT('AR', FIELD NUMBER: 991.01 FIELD NAME: INTEGRATION CONTROL NUMBER LOCATION: x-ref ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Cross Reference is used to delete the 'AMPIMIS' cross reference denoting missing ICN. GLOBAL REFERENCE: DPT(D0,'MPIFHIS',D1, FIELD NUMBER: .01 FIELD NAME: ICN HISTORY LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: ICN History, to track changes in Integration Control Number for each patient. This will be used by M code to perform lookups when ICN can't be found to see if it was used previously. FIELD NUMBER: 1 FIELD NAME: ICN CHECKSUM LOCATION: 0;2 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 2 FIELD NAME: CMOR LOCATION: 0;3 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 3 FIELD NAME: DATE/TIME OF CHANGE LOCATION: 0;4 ACCESS: Direct Global R/W & w/Fileman GLOBAL REFERENCE: DPT('ASCN2', FIELD NUMBER: 991.05 FIELD NAME: SUBSCRIPTION CONTROL NUMBER LOCATION: x-ref ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: This cross-reference is used by CIRN (Clinical Information Resource Network) for various data validation and reporting functions. GLOBAL REFERENCE: DPT(0) GLOBAL DESCRIPTION: CIRN is requesting permission to reference by Direct Read the Header Node of the PATIENT file in order to display the number of patients (piece 4) and the last record number entered (piece 3). **CIRN IS AWARE THAT THIS DATA MAY NOT BE RELIED ON TO BE ACCURATE, AS THOSE PIECES OF THE HEADER NODE ARE NOT ALWAYS CORRECTLY UPDATED.** GLOBAL REFERENCE: DPT(D0,'MPICMOR', FIELD NUMBER: .01 FIELD NAME: CMOR HISTORY LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: CMOR CHANGE DATE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Clinical Information Resource Network (CIRN) and Master Patient Index (MPI) will use the following fields on the MPI and MPIHIS nodes to facilitate the exchange of patient demographic and clinical data. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27725861 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA SUBSCRIBING PACKAGE: HEALTH DATA REPOSITORY SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES SUBSCRIBING DETAILS: TIU access is only permitted for the AICN x-ref. NUMBER: 2071 IA #: 2071 FILE NUMBER: 420.6 GLOBAL ROOT: PRCD(420.6 DATE CREATED: AUG 12, 1997 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: CODE INDEX (FPDS) ID: PRCD(420.6 GLOBAL REFERENCE: PRCD(420.6,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the name of the code index. FIELD NUMBER: 1 FIELD NAME: CODE INDEX LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the code for the index. FIELD NUMBER: 2 FIELD NAME: EFFECTIVE DATE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the year that the Federal Procurement Data Systems (FPDS) index became effective. FIELD NUMBER: 5 FIELD NAME: APPLICABLE BUSINESS TYPES LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains a comma delimited list of applicable business types. The list entered here will determine the choices displayed when editing a vendor's SOCIOECONOMIC GROUPS (FPDS) data. GENERAL DESCRIPTION: This agreement permits FEE BASIS to point to the CODE INDEX (#420.6) file and also to access data in the 0 node to support a screen of choices. The CODE INDEX file contains the list of vendor FPDS socio-econonomic groups. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24714736 SUBSCRIBING PACKAGE: FEE BASIS ISC: Washington/Silver Spring NUMBER: 2074 IA #: 2074 FILE NUMBER: 40.7 GLOBAL ROOT: DIC(40.7, DATE CREATED: AUG 18, 1997 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2074 ID: DIC(40.7, GLOBAL REFERENCE: DIC(40.7,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: The Name of the Clinic Stop Code. FIELD NUMBER: 1 FIELD NAME: AMIS REPORTING STOP CODE LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field contains the number related to the stop code that is used when generating the OPC file. This number is what is transmitted. FIELD NUMBER: 2 FIELD NAME: INACTIVE DATE LOCATION: 0;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field contains a date of when a Clinic Stop code has been inactivated. FIELD NUMBER: 3 FIELD NAME: CONVERT TO STOP CODE LOCATION: 0;4 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field contains a pointer value to the new Clinic Stop codes that have a three number AMIS REPORTING STOP CODE. FIELD NUMBER: 4 FIELD NAME: COST DISTRIBUTION CENTER LOCATION: 0;5 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field contains a number related to the cost distribution center. GLOBAL DESCRIPTION: This file contains all Clinic Stops (DSS IDs) and their associated AMIS Stop Code. GENERAL DESCRIPTION: Read access is requested of all fields on the Zero node of this file. These fields will be used for reporting purposes. These fields are: Fld # Fld Name Node;Pce .01 NAME 0;1 1 AMIS REPORTING STOP CODE 0;2 2 INACTIVE DATE 0;3 3 CONVERT TO STOP CODE 0;4 4 COST DISTRIBUTION CENTER 0;5 Read access is requested of the "C" cross reference on this file. The "C" cross reference will be used to check the existence of a specific 'Amis Reporting Stop Code' as defined in field number 1. It is noted that Event Capture needs to reference entries in the Clinic Stop file (40.7) via Internal Entry Numbers (pointers) to that file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24729730 SUBSCRIBING PACKAGE: EVENT CAPTURE ISC: Albany NUMBER: 2075 IA #: 2075 DATE CREATED: AUG 20, 1997 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XTKERM4 NAME: DBIA2075 ID: XTKERM4 GENERAL DESCRIPTION: This agreement expands agreement 10095 for XTKERMIT. This agreement allows access to the KERMIT HOLDING file (#8980) and the API that adds entries to it, RFILE^XTKERM4. The "AOK" cross-reference of the KERMIT HOLDING file (#8980) may be checked to see if the user has an entry in the KERMIT HOLDING file (#8980). If not, RFILE^XTKERM4 may be called to add an entry to the file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24721542 COMPONENT/ENTRY POINT: RFILE COMPONENT DESCRIPTION: A call to RFILE^XTKERM4 will allow a user to add or select an entry in the KERMIT HOLDING file (#8980). VARIABLES: XTKDIC TYPE: Output VARIABLES DESCRIPTION: This variable returns the global root and is a calling variable used by calls to RECEIVE^XTKERMIT or SEND^XTKERMIT. VARIABLES: XTMODE TYPE: Output VARIABLES DESCRIPTION: This variable is returned, it is used as input to calls to RECEIVE^XTKERMIT or SEND^XTKERMIT. SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham NUMBER: 2076 IA #: 2076 DATE CREATED: AUG 20, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DG10 NAME: DBIA2076-A ORIGINAL NUMBER: 2076 ID: DG10 GENERAL DESCRIPTION: To support patient data review, CIRN needs to include a Hinq inquiry. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24714795 COMPONENT/ENTRY POINT: HINQ COMPONENT DESCRIPTION: Background Hinq inquiry VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham NUMBER: 2077 IA #: 2077 FILE NUMBER: 9999999.17 GLOBAL ROOT: AUTTTRT( DATE CREATED: SEP 24, 1997 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2077 ID: AUTTTRT( GLOBAL REFERENCE: AUTTTRT(#,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: INACTIVE FLAG LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL DESCRIPTION: This file is a table with site defined Treatment names. These are names of treatments that are not covered in the ICD-9-CM Procedures or the CPT Procedures. Examples may include treatments such as Ear Irrigation, or Instructions or Counseling given to a patient for a Medical Problem. GENERAL DESCRIPTION: This integration agreement authorizes global reference to the zeroith node of the following file for purposes of retrieving the name and inactive flag: ^AUTTTRT(#,0) piece 1 and piece 4 ... and to the "B" cross-reference STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25071670 SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2078 IA #: 2078 FILE NUMBER: 8980 GLOBAL ROOT: DIZ(8980 DATE CREATED: AUG 20, 1997 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2078 ID: DIZ(8980 GLOBAL REFERENCE: DIZ(8980,D0,0) FIELD NUMBER: 4 FIELD NAME: CREATOR LOCATION: 0;5 ACCESS: Read w/Fileman FIELD DESCRIPTION: The CREATOR field contains the person who owns this entry. GLOBAL DESCRIPTION: This file provides a holding place for data being transferred by the KERMIT protocol. By default the data can only be accessed by the user that created it. The Kermit Menu (XT-KERMIT options) may be used to send and receive data via this file. The menu also allows the creator of the data to permit access by others. This file is cross-referenced by name, creator, and access allowed to user. GENERAL DESCRIPTION: Integration Agreement to read the "AOK" cross reference and check for the existence of the ^DIZ(8980,"AOK",DUZ) cross-reference. If not, data is added to the KERMIT HOLDING file (#8980) via the RFILE^XTKERM4 entry point. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24721542 SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham NUMBER: 2079 IA #: 2079 FILE NUMBER: 50.6 GLOBAL ROOT: PSNDF DATE CREATED: AUG 22, 1997 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2079 ID: PSNDF GLOBAL REFERENCE: PSNDF(D0,0) FIELD NUMBER: .01 FIELD NAME: VA GENERIC NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSNDF(D0,2,D1,0) FIELD NUMBER: .01 FIELD NAME: DOSAGE FORM LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSNDF(D0,5,D1,0) FIELD NUMBER: .01 FIELD NAME: VA PRODUCT NAMES LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: DOSAGE FORM ENTRY LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSNDF(D0,5,D1,2) FIELD NUMBER: 5 FIELD NAME: VA PRINT NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6 FIELD NAME: VA PRODUCT IDENTIFIER LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7 FIELD NAME: TRANSMIT TO CMOP LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 8 FIELD NAME: VA DISPENSE UNIT LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Pharmacy Data Management requests an intergration agreement to look at National Drug file 50.6. VIEWER: TATUM,WILLIAM STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24799627 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2080 IA #: 2080 DATE CREATED: AUG 22, 1997 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSNOUT NAME: DBIA2080 ID: PSNOUT GENERAL DESCRIPTION: Pharmacy Data Management requests an intergration agreement with National Drug File package to call up line-tag REACT1^PSNOUT. The master Drug Enter/Edit option in PDM needs the ability to match to NDF if the user has the proper key. PDM requires at least NDF 3.15 to be in place in order to install. A ^%ZOSF test will be executed on routine PSNOUT. The line-tag allows the user to match, verify, and merge an entry in DRUG file 50 to NATIONAL DRUG file 50.6. VIEWER: TATUM,WILLIAM STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24804037 COMPONENT/ENTRY POINT: REACT1 COMPONENT DESCRIPTION: Allows user to match, verify, and merge to NDF. VARIABLES: none SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2081 IA #: 2081 DATE CREATED: SEP 30, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2081 GENERAL DESCRIPTION: Pharmacy Data Management requests an intergration agreement with the VA FileMan package. PDM requests to do a one-time hard kill of four triggers which are no longer valid in DRUG file 50. These triggers will be killed in a post install routine in Pharmacy Data Management version 1.0. The fields affected in DRUG file 50 are: Field 12 ORDER UNIT Field 13 PRICE PER ORDER UNIT Field 15 DISPENSE UNITS PER ORDER UNIT Field 16 PRICE PER DISPENSE UNIT In addition: Field 23 PACKAGE SIZE (input transform) Field 24 PACKAGE TYPE (input transform) Field 8 WARNING LABEL (overflow of input transform code) The KILL logic looks as follows: K ^DD(50,12,1,535000),^DD(50,203),^DD(50,13,1,535000),^DD(50,15,1,535000), ^DD(50,16,1,1),^DD(50,"TRB",16) K ^DD(50,0,"IX","AE",50,202),^DD(50,0,"IX","IV",50.03,.01) K ^DD(50,0,"IX","IV1",50,204),^DD(50,0,"IX","IV2",50,201.1),^DD(50,0,"PT",50.03,. 02) K ^DD(50,0,"IX","AV1",50,200),^DD(50,0,"IX","AD",50,201),^DD(50,0,"IX","AF",50,20 1.3),^DD(50,0,"IX","AV2",50,201),K ^DD(50,23,2),^DD(50,23,2.1),^DD(50,24,2),^DD(50,24,2.1),^DD(50,8,9.2) VIEWER: TATUM,WILLIAM STATUS: Active DURATION: Next Version MAIL MESSAGE: 24833495 GOOD ONLY FOR VERSION: 1.0 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2082 IA #: 2082 FILE NUMBER: 357.69 GLOBAL ROOT: IBE(357.69, DATE CREATED: AUG 25, 1997 CUSTODIAL PACKAGE: AUTOMATED INFO COLLECTION SYS CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2082 ID: IBE(357.69, GENERAL DESCRIPTION: This DBIA is to allow PCE to read AICS' file TYPE OF VISIT file (#357.69) for the following files. ^IBE(357.69, .01 CODE [0;1] Read/Fileman .015 SHORT NAME [computed] Read/Fileman .02 RECOMMENDED HEADER [0;2] Read/Fileman .03 RECOMMENDED TEXT [0;3] Read/Fileman .04 INACTIVE FLAG [0;4] Read/Fileman .05 NEW,ESTABLISHED,CONSULT [0;5] Read/Global STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24794291 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany NUMBER: 2083 IA #: 2083 FILE NUMBER: 409.41 GLOBAL ROOT: SD(409.41, DATE CREATED: AUG 26, 1997 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2083 ID: SD(409.41, GLOBAL REFERENCE: SD(409.41, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: PROMPT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: INPUT TYPE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: DEFAULT LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .05 FIELD NAME: REQUIRED LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: DISPLAY NAME LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .07 FIELD NAME: ABBREVIATION LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This DBIA allows PCE to Globally read Scheduling's OUTPATIENT CLASSIFICATION TYPE file (#409.41) for the below fields. This is used in asking the user the patient Service Connected and Classification questions. PCE is now asking these question for Scheduling. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24794021 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE NUMBER: 2084 IA #: 2084 FILE NUMBER: 409.42 GLOBAL ROOT: SDD(409.42, DATE CREATED: AUG 26, 1997 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2084 ID: SDD(409.42, GENERAL DESCRIPTION: PCE request a DBIA with Scheduling to kill entries in the OUTPATIENT CLASSIFICATION file (#409.42). This is done in the process of asking the user for the patient's classification if the classification " is no longer applicable...". This is needed because PCE now ask the classification questions for Scheduling and this was done in the asking of the classification questions. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24794108 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany NUMBER: 2085 IA #: 2085 FILE NUMBER: 43 GLOBAL ROOT: DG(43 DATE CREATED: AUG 26, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2085 ID: DG(43 GLOBAL REFERENCE: DG(43,1,SCLR) FIELD NUMBER: 224 FIELD NAME: ALLOW UP-ARROW OUT OF CLASS LOCATION: SCLR;24 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This is needed because PCE now ask the classification questions for Scheduling. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24794172 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany NUMBER: 2086 IA #: 2086 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: AUG 26, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2086 ID: DPT( GLOBAL REFERENCE: DPT(DFN,0) FIELD NUMBER: .083 FIELD NAME: CHECK FOR DUPLICATE LOCATION: 0;20 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DPT(DFN,DIS,D1,0) FIELD NUMBER: 18 FIELD NAME: OUTPATIENT ENCOUNTER LOCATION: 0;18 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This is so PCE can find the Outpatient Encounter and thus the Visit for a disposition. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24794208 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany NUMBER: 2087 IA #: 2087 FILE NUMBER: 120.5 GLOBAL ROOT: GMR(120.5, DATE CREATED: AUG 26, 1997 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2087 ID: GMR(120.5, GLOBAL REFERENCE: GMR(120.5,D0,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME VITALS TAKEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: VITAL TYPE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.2 FIELD NAME: RATE LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: GMR(120.5,C, GLOBAL DESCRIPTION: This is the "C" cross reference. Direct Global Read. GENERAL DESCRIPTION: This is used in the Caseload Profile report. It is looking for blood pressures above 159/90 (either value high). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24794253 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION NUMBER: 2088 IA #: 2088 FILE NUMBER: 409.68 GLOBAL ROOT: SCE( DATE CREATED: AUG 26, 1997 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2088 ID: SCE( GLOBAL REFERENCE: SCE(D0,0) FIELD NUMBER: .02 FIELD NAME: PATIENT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .05 FIELD NAME: VISIT FILE ENTRY LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: PATENT ENCOUNTER LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .1 FIELD NAME: APPOINTMENT TYPE LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .12 FIELD NAME: STATUS LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: SCE(AVSIT, GLOBAL DESCRIPTION: This is the "AVSIT" cross reference. Direct Global Read. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24794371 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany NUMBER: 2090 IA #: 2090 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: AUG 27, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ACCESS TO PATIENT MOVEMENT DATA ID: DGPM( CREATOR: CORONA,JOSE GLOBAL REFERENCE: DGPM(APTT1,DFN, GLOBAL DESCRIPTION: This is the cross reference on admitting date. GLOBAL REFERENCE: DGPM(APTT3,DFN, GLOBAL DESCRIPTION: This is the cross reference on discharge date. GLOBAL REFERENCE: DGPM(APTT2,DFN GLOBAL REFERENCE: DGPM(APID,DFN,INVERSE DATE_AS,DA GLOBAL REFERENCE: DGPM(D0,0 FIELD NUMBER: .03 FIELD NAME: PATIENT LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: WARD LOCATION LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .07 FIELD NAME: ROOM-BED LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .14 FIELD NAME: ADMISSION/CHECK-IN MOVEMENT LOCATION: 0;14 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .18 FIELD NAME: MAS MOVEMENT TYPE LOCATION: 0;18 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .01 FIELD NAME: DATE/TIME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .17 FIELD NAME: DISCHARGE/CHECK-OUT MOVEMENT LOCATION: 0;17 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: THIS ICR ALLOWS ACCESS TO PATIENT MOVEMENT DATA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24844448 KEYWORDS: DGPM KEYWORDS: PATIENT MOVEMENT SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS SUBSCRIBING DETAILS: ADDED 4/10/09 SUBSCRIBING PACKAGE: DIETETICS SUBSCRIBING DETAILS: ADDED 6/8/09 10/12/12-Added Date/Time (#.01) and Discharge/Check-Out Movement (#.17) fields for Dietetics DBA Comments: 20090410 - changed Private to Controlled to add MSRA 20090608 - ATT2 ENTRY POINT ADDED 20090608 - DGPM(D0,0 ADDED 20090608 - DGPM(APID,DFN,INVERSE DATE_AS, ADDED 10/12/12-MM: Deactivated ICR for edits for Dietetics to add two additional fields to ICR. Date/Time (#.01) and Discharge/Check-out Movement (#.17) fields will be added. During development of FH*5.5*30, developer found existing references to these fields and requested to add them to the existing ICR between Dietetics and Registration. Reactivated on 10/12/12. DATE ACTIVATED: OCT 12, 2012 DATE/TIME EDITED: APR 10, 2009@15:50 ACTION: USAGE CHOICE CHANGED AT THE REQUEST OF: HARVEY,JULIE DATE/TIME EDITED: APR 10, 2009@15:51 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MCDEARMON,JAMES WITH CONCURRENCE OF: MULLER,RICHARD DATE/TIME EDITED: APR 10, 2009@15:54 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CORONA,JOSE DATE/TIME EDITED: JUN 08, 2009@15:58 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: UNDERHILL,GARDNER WITH CONCURRENCE OF: MULLER,RICHARD DATE/TIME EDITED: JUN 08, 2009@15:59 ACTION: CONTENT CORRECTED AT THE REQUEST OF: TIETELBAUM,LEVI WITH CONCURRENCE OF: MULLER,RICHARD DATE/TIME EDITED: JUN 08, 2009@16:00 ACTION: APPROVED AT THE REQUEST OF: MULLER,RICHARD DATE/TIME EDITED: OCT 12, 2012@10:33 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: UNDERHILL,GARDNER WITH CONCURRENCE OF: KOPECKY,STEVE DATE/TIME EDITED: OCT 12, 2012@11:48 ACTION: APPROVED AT THE REQUEST OF: UNDERHILL,GARDNER WITH CONCURRENCE OF: KOPECKY,STEVE NUMBER: 2091 IA #: 2091 FILE NUMBER: 8932.1 GLOBAL ROOT: USC(8932.1, DATE CREATED: AUG 27, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2091 ID: USC(8932.1, GLOBAL REFERENCE: USC(8932.1, FIELD NUMBER: .01 FIELD NAME: OCCUPATION (HCFA) LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: SPECIALTY (HCFA) LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: SUBSPECIALTY (HCFA) LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: STATUS LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: USC(8932.1,B, GLOBAL DESCRIPTION: This is the "B" cross reference. GLOBAL REFERENCE: USC(8932.1,F, GLOBAL DESCRIPTION: This is the "F" cross reference. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT SUBSCRIBING DETAILS: The Pharmacy Benefits Management package extracts provider data monthly to support the VA National Formulary, disease management issues and patient safety initiatives. SUBSCRIBING PACKAGE: SCHEDULING NUMBER: 2092 IA #: 2092 FILE NUMBER: 60 GLOBAL ROOT: LAB(60, DATE CREATED: AUG 27, 1997 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: 2092 ORIGINAL NUMBER: 2092 ID: LAB(60, GLOBAL REFERENCE: LAB(60,D0,0) FIELD NUMBER: 5 FIELD NAME: LOCATION (DATA NAME) LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LAB(60,C, GLOBAL DESCRIPTION: This is the "C" cross reference. Direct Global Read. GENERAL DESCRIPTION: This is used by the PCE Reports. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24821133 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany NUMBER: 2093 IA #: 2093 FILE NUMBER: 63 GLOBAL ROOT: LR( DATE CREATED: AUG 27, 1997 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2092-B ORIGINAL NUMBER: 2092 ID: LR( GLOBAL REFERENCE: LR(D0,CH,D1,0) FIELD NUMBER: .05 FIELD NAME: SPECIMEN TYPE LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LR(D0,CH,D1,test) FIELD NUMBER: test FIELD NAME: test value LOCATION: test;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: high/low FIELD NAME: high/low flag LOCATION: test;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field flags if a result is high or low and an "*" is include for critical values. The "*" is being looked for to find critical results. GLOBAL DESCRIPTION: This is for all of the "CH" nodes that the different test results are stored on. GENERAL DESCRIPTION: This is used by the PCE Reports. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24821133 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2094 IA #: 2094 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: AUG 27, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: 2094 ORIGINAL NUMBER: 2094 ID: VA(200, GLOBAL REFERENCE: VA(200,D0,PS) FIELD NUMBER: 53.4 FIELD NAME: INACTIVE DATE LOCATION: PS;4 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This is used to see if a provider has been inactivated at the time of the patient encounter. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24794136 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany NUMBER: 2095 IA #: 2095 FILE NUMBER: 50 GLOBAL ROOT: PSDRUG( DATE CREATED: SEP 04, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2095 ID: PSDRUG( GLOBAL REFERENCE: PSDRUG(D0,0) FIELD NUMBER: .01 FIELD NAME: GENERIC NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the generic name of the drug. FIELD NUMBER: 51 FIELD NAME: NON-FORMULARY LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is used to designate the drug as non-formulary. GLOBAL DESCRIPTION: This file holds the information related to each drug that can be used to fill a prescription. It is pointed to from several other files and should be handled carefully, usually only by special individuals in the pharmacy service. Entries are not typically deleted, but rather made inactive by entering an inactive date. This file must be built by Pharmacy Service BEFORE going on-line. It is common to use another centers file and edit it to match your center's unique formulary. GLOBAL REFERENCE: PSDRUG(D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: SYNONYM LOCATION: 0;1 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is used as a quick code for look ups or to locate NDCs so the drug's inventory can be incremented when orders are received. FIELD NUMBER: 1 FIELD NAME: INTENDED USE LOCATION: 0;3 ACCESS: Write w/Fileman FIELD DESCRIPTION: If you designate a synonym as a quick code, then it will not appear on the formulary listing for distribution in the hospital. If it is designated as a trade name, then it will appear on the listing. This field does not affect the ability to look-up a drug by quick code or trade name. If the intended use is for Controlled Substances or Drug Accountability, the synonym is used to locate NDCs so the drug's inventory can be incremented when orders are received. FIELD NUMBER: 2 FIELD NAME: NDC CODE LOCATION: 0;2 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field will contain the national drug code. FIELD NUMBER: 400 FIELD NAME: VSN LOCATION: 0;4 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the vendor's stock number for the NDC. FIELD NUMBER: 401 FIELD NAME: ORDER UNIT LOCATION: 0;5 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the NDC's unit of order. FIELD NUMBER: 402 FIELD NAME: PRICE PER ORDER UNIT LOCATION: 0;6 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the price for one unit of order. FIELD NUMBER: 403 FIELD NAME: DISPENSE UNITS PER ORDER UNIT LOCATION: 0;7 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the number of dispense units in one order unit. FIELD NUMBER: 404 FIELD NAME: PRICE PER DISPENSE UNIT LOCATION: 0;8 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the cost of one dispense unit. FIELD NUMBER: 405 FIELD NAME: VENDOR LOCATION: 0;9 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the name of the vendor from which the drug was purchased. GLOBAL DESCRIPTION: This multiple contains the Synonym, NDC Code, Intended Use, VSN, Order Unit, Price per Order Unit, Dispense Units per Order Unit, Price per Dispense Unit, and Vendor fields. It is used for a quick code for look ups or to locate NDCs to increment the drug's inventory when orders are received. GLOBAL REFERENCE: PSDRUG(D0,2) FIELD NUMBER: 63 FIELD NAME: APPLICATION PACKAGES' USE LOCATION: 2;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is free text, but contains the codes of the DHCP packages that consider this drug part of its formulary. This field is set through the routine ^PSGIU, and NOT through VA FileMan. FIELD NUMBER: 31 FIELD NAME: NDC LOCATION: 2;4 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the National Drug Code for this drug. GLOBAL DESCRIPTION: This global node contains the drug restriction, which VISTA applications are using the drug, the primary NDC, and a pointer to the PRIMARY DRUG file (#50.3). GLOBAL REFERENCE: PSDRUG(D0,441,0) FIELD NUMBER: .01 FIELD NAME: ITEM NUMBER LOCATION: 0;1 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field contains any or all items in the ITEM MASTER file that relate to this drug. This relationship will enable automated receiving from the IFCAP Inventory module. GLOBAL DESCRIPTION: With the "AB" cross reference this multiple will be used when PRCP routines pass receiving data to PSA routines. GLOBAL REFERENCE: PSDRUG(D0,660) FIELD NUMBER: 12 FIELD NAME: ORDER UNIT LOCATION: 660;2 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the order unit for this drug. FIELD NUMBER: 13 FIELD NAME: PRICE PER ORDER UNIT LOCATION: 660;3 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the price per order unit for this drug. FIELD NUMBER: 15 FIELD NAME: DISPENSE UNITS PER ORDER UNIT LOCATION: 660;5 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the dispense units per order unit for this drug. FIELD NUMBER: 16 FIELD NAME: PRICE PER DISPENSE UNIT LOCATION: 660;6 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the dispense units per order unit for this drug. NOTE: This field is set with a TRIGGER when the PRICE PER ORDER UNIT is set. FIELD NUMBER: 14.5 FIELD NAME: DISPENSE UNIT LOCATION: 660;8 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the dispense unit for this drug. GLOBAL DESCRIPTION: This global node contains packaging, dispense unit, pricing, reordering levels, and source data. GLOBAL REFERENCE: PSDRUG(D0,660.1) FIELD NUMBER: 50 FIELD NAME: CURRENT INVENTORY LOCATION: 660.1;1 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field contains the current number of the drug in stock. GLOBAL DESCRIPTION: This node contains the total number of dispense units that are in inventory for all sites using this DRUG file. GLOBAL REFERENCE: PSDRUG(D0,'I') FIELD NUMBER: 100 FIELD NAME: INACTIVE DATE LOCATION: I;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the date the drug is inactive. GLOBAL DESCRIPTION: This global node contains the date the drug will be or was made inactive. GLOBAL REFERENCE: PSDRUG(D0,'ND') FIELD NUMBER: 20 FIELD NAME: NATIONAL DRUG FILE ENTRY LOCATION: 'ND';1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the pointer to the National Drug file (^PSNDF). FIELD NUMBER: 22 FIELD NAME: PSNDF VA PRODUCT NAME ENTRY LOCATION: 'ND';3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the index of the VA Product Name in the National Drug file. FIELD NUMBER: 23 FIELD NAME: PACKAGE SIZE LOCATION: 'ND';4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the pointer to the Package Size file. FIELD NUMBER: 24 FIELD NAME: PACKAGE TYPE LOCATION: 'ND';5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the pointer to the Package Type file. GLOBAL DESCRIPTION: This global node contains NATIONAL DRUG FILE (50.6) links and packaging data. GENERAL DESCRIPTION: Drug Accountability/Inventory Interface (DA) v3.0 interfaces with the DRUG (#50) file to assist Pharmacy in maintaining a perpetual inventory. DA contains two methods of maintaining the drug balances. The site can either interface with the Generic Inventory Package (GIP) or with the prime vendor's electronic invoice data. The DRUG file is used to store matches between drugs and either an item in GIP or the NDC in the prime vendor's invoice data. It is also used to identify matched drugs when they are received and dispensed drugs via other VISTA Pharmacy packages. When the fields are read, it is by a direct global read. When the fields are written to, it is by a FileMan DIE call. Read fields: ============ GLOBAL MAP DATA DICTIONARY #50 -- DRUG FILE -------------------------------------------------------------------------- ^PSDRUG(D0,0)= (#.01) GENERIC NAME [1F] ^ ^ ^ ^ ^ (#6) FSN [6F] ^ ^ ^ ==>(#51) NON-FORMULARY [9S] ^ ^ ^PSDRUG(D0,1,0)=^50.1A^^ (#9) SYNONYM ^PSDRUG(D0,1,D1,0)= (#.01) SYNONYM [1F] ^ (#2) NDC CODE [2F] ^ ==>(#1) INTENDED USE [3S] ^ (#400) VSN [4F] ^ (#401) ==>ORDER UNIT [5P] ^ (#402) PRICE PER ORDER UNIT [6N] ^ ==>(#403) DISPENSE UNITS PER ORDER UNIT [7N] ^ (#404) ==>PRICE PER DISPENSE UNIT [8N] ^ (#405) VENDOR [9F] ^ ^PSDRUG(D0,2)= ^ ^ (#63) APPLICATION PACKAGES' USE [3F] ^ (#31) NDC [4F] ^ ^PSDRUG(D0,441,0)=^50.0441P^^ (#441) IFCAP ITEM NUMBER ^PSDRUG(D0,441,D1,0)= (#.01) ITEM NUMBER [1P] ^ ^PSDRUG(D0,660)= ^ (#12) ORDER UNIT [2P] ^ (#13) PRICE PER ORDER UNIT [3N] ==>^ ^ (#15) DISPENSE UNITS PER ORDER UNIT [5N] ^ (#16) ==>PRICE PER DISPENSE UNIT [6N] ^ ^ (#14.5) DISPENSE UNIT ==>[8F] ^ ^PSDRUG(D0,660.1)= (#50) CURRENT INVENTORY [1N] ^ ^PSDRUG(D0,I)= (#100) INACTIVE DATE [1D] ^ ^PSDRUG(D0,ND)= (#20) NATIONAL DRUG FILE ENTRY [1P] ^ (#21) VA PRODUCT ==>NAME ENTRY [2N] ^ (#22) PSNDF VA PRODUCT NAME ENTRY [3N] ^ ==>(#23) PACKAGE SIZE [4P] ^ (#24) PACKAGE TYPE [5P] ^ Cross-references Read: ===================== ITEM NUMBER(AB), VSN(AVSN), SYNONYM(C), VA PRODUCT NAME(VAPN), NDC(NDC) Fields Written to: ================== GLOBAL MAP DATA DICTIONARY #50 -- DRUG FILE -------------------------------------------------------------------------- ^PSDRUG(D0,0)= (#.01) GENERIC NAME [1F] ^ ^PSDRUG(D0,1,0)=^50.1A^^ (#9) SYNONYM ^PSDRUG(D0,1,D1,0)= (#.01) SYNONYM [1F] ^ (#2) NDC CODE [2F] ^ ==>(#1) INTENDED USE [3S] ^ (#400) VSN [4F] ^ (#401) ==>ORDER UNIT [5P] ^ (#402) PRICE PER ORDER UNIT [6N] ^ ==>(#403) DISPENSE UNITS PER ORDER UNIT [7N] ^ (#404) ==>PRICE PER DISPENSE UNIT [8N] ^ (#405) VENDOR [9F] ^ ^PSDRUG(D0,2)= ^ ^ ^ (#31) NDC [4F] ^ ^PSDRUG(D0,441,0)=^50.0441P^^ (#441) IFCAP ITEM NUMBER ^PSDRUG(D0,441,D1,0)= (#.01) ITEM NUMBER [1P] ^ ^PSDRUG(D0,660)=^ (#12) ORDER UNIT [2P] ^ (#13) PRICE PER ORDER UNIT [3N] ==>^ ^ (#15) DISPENSE UNITS PER ORDER UNIT [5N] ^ (#16) ==>PRICE PER DISPENSE UNIT [6N] ^^ (#14.5) DISPENSE UNIT [8F] ^PSDRUG(D0,660.1)= (#50) CURRENT INVENTORY [1N] ^ Three print templates are used to print two reports. PSADRIP and PSADRIH are used to print the DRUG file/ITEM MASTER file Comparison Report from a selected sort range The report contains information on packaging and pricing. PSADRIH is the header on this report. PSADRI is used to print the Inquire/Compare DRUG file/ITEM MASTER file report that compares the packaging and pricing between the DRUG file and the ITEM MASTER file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24911014 SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham NUMBER: 2096 IA #: 2096 FILE NUMBER: 409.63 GLOBAL ROOT: SD(409.63, DATE CREATED: DEC 01, 2005 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: 2096 ORIGINAL NUMBER: 2096 ID: SD(409.63, GLOBAL REFERENCE: SD(409.63,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24847394 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER NUMBER: 2097 IA #: 2097 FILE NUMBER: 1.1 GLOBAL ROOT: DIA( DATE CREATED: AUG 29, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2097 ID: DIA( GLOBAL REFERENCE: DIA(D0,0) FIELD NUMBER: .001 FIELD NAME: NUMBER LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Last entry GLOBAL REFERENCE: DIA(2,'B',DFN,IEN) GLOBAL DESCRIPTION: "B" x-ref for PATIENT file GLOBAL REFERENCE: DIA(D0,IEN,0) FIELD NUMBER: .02 FIELD NAME: DATE/TIME RECORDED LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: CIRN needs to display the last date edited for a patient. CIRN recommends that sites turn on auditing for demographic fields. To get the last date edited, if auditing is turned on, CIRN checks the $P(^DIA(2,0),U,3)+1 for the last entry and then $O(^DIA(2,"B",DFN,LAST ENTRY),-1) to find the most recent edit, $P(^DIA(2,IEN,0),U,2). CIRN requests direct read access to these nodes. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24791067 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: MASTER PATIENT INDEX SUBSCRIBING DETAILS: the MPI is viewing AUDIT data from the MPI VETERAN/CLIENT (#985) file, including the B cross-reference. GLOBAL REFERENCE: ^DIA(985,'B',ICN,IEN) "B" x-ref for MPI VETERAN/CLIENT (#985) file NUMBER: 2098 IA #: 2098 DATE CREATED: SEP 02, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DIQUIET TO SUPPRESS WRITES GENERAL DESCRIPTION: 1. DESCRIPTION OF USE OF DIQUIET IN FILEMAN HISTORY OF DIQUIET: The purpose for creating DIQUIET was mostly that as we were creating the data-base server calls, we sometimes needed to call into Classic FileMan, and we absolutely didn't want FileMan to talk. DIQUIET was a variable that would let us know within those classic calls that we were being called from a DBS call, so we shouldn't talk. Therefore, at the start of almost all the DBS calls, we set DIQUIET=1. DIQUIET was also used as a flag in EN^DDIIOL, which is embedded in Xecutable code in the DD, to assure that text is placed in ^TMP instead of being Written when DBS calls are involved. SETTING DIQUIET WITHIN FILEMAN CODE: DIQUIET is set to 1 at the start of the following published calls: Finder FIND^DIC Finder (Single Record) $$FIND1^DIC Lister LIST^DIC DD Field Retriever FIELD^DID DD Field List Retriever FIELDLST^DID DD File Retriever FILE^DID DD File List Retriever FILELIST^DID Attribute Retriever $$GET1^DID Data Checker CHK^DIE Filer FILE^DIE Helper HELP^DIE Updater UPDATE^DIE Validator VAL^DIE Word-Processing Filer WP^DIE Single Data Retriever $$GET1^DIQ Data Retriever GETS^DIQ In addition, there are a few places that Classic FileMan sets DIQUIET for the same reason. Import Tool (DDMP, DDMPU) because the Import tool is designed to be silent like the DBS calls. DIED and DIEZ1 (classic DIE call to edit data) sets DIQUIET if the user is stuffing data in a SET OF CODES field, because it makes a call to ^DIR and does not want the Reader to talk. DIEZ, DIKZ and DIPZ (template and x-ref compilation) appear to have silent entry points (all labeled EN2) that set DIQUIET. I believe that these were created by Rick, I don't think they're documented. Perhaps KIDS uses them, I need to discuss this with him. DIP (the PRINT routine) sets DIQUIET if it is not already set, and if all the information that DIP normally prompts the user for has been sent (I.E., file and fields to print, sort criteria, device, etc.), or if the print job is queued. That was to avoid some places where FileMan was writing error messages. HONORING DIQUIET TO SUPPRESS WRITES: Mostly we made changes to classic FileMan as we needed to, in places where we were calling it from the new DBS calls and wanted it to be silent. The places are: DDIOL (The loader), where DIQUIET tells the routine to load the text that is passed into an array rather than writing it. That's why we were able to tell people that any writes that they have in their DDs should call ^DDIOL rather than just write. %DT (date validation routine) to keep the date from echoing back. DT^DICRW (routine that sets up required FileMan variables). Was writing a line-feed. DIE3 (enter/edit) Does not write "Searching for a..." when doing a lookup on a file pointed-to by a variable pointer, and does not ask OK when a pointed-to entry is found, even if the DD has been set up that way. DIP The changes to the print are described above, and were not done for the DBS calls, as we don't call the print from within any of them. DIR1 The Reader doesn't write a message when processing sets of codes if DIQUIET is set. This was required by DIE when stuffing a SET OF CODES field, as I described above. 2. REASON RPC BROKER NEEDS TO SET DIQUIET: Setting of DIQUIET variable, which is used within the VA FileMan package to suppress WRITEs from FileMan routines and DDs, to 1. Variable being set by RPC Broker when it is certain that no direct user-interaction is appropriate (client/server environment). The only FileMan code that the Broker does directly that requires DIQUIET to be set is DT^DICRW (a linefeed is suppressed). However, since the Broker performs the code written in RPCs, having DIQUIET set protects the code in the RPCs from inadvertently Writing because of a call to a FileMan routine or the Xecution of a DD node. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24783104 KEYWORDS: DIQUIET SUBSCRIBING PACKAGE: RPC BROKER ISC: Oakland SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING PACKAGE: MAILMAN SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: INTEGRATED BILLING SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING NUMBER: 2099 IA #: 2099 DATE CREATED: SEP 05, 1997 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: PSORPH GENERAL DESCRIPTION: PDM requests permission to check for the PSORPH security key. VIEWER: SCHLEHUBER,CAMERON VIEWER: BROWN,STANLEY A VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24965137 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2100 IA #: 2100 DATE CREATED: SEP 16, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2100 GENERAL DESCRIPTION: PDM requests permission to check for the following security keys: PSJU MGR PSJI MGR PSGWMGR PSJ RPHARM PSJ RNURSE PSJ PHARM TECH VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24965198 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2104 IA #: 2104 DATE CREATED: SEP 05, 1997 CUSTODIAL PACKAGE: DRUG ACCOUNTABILITY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2104 GENERAL DESCRIPTION: PDM requests permission to check for the PSAMGR and PSA ORDERS security keys. VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE VIEWER: BARNETT,JANICE H STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24917545 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2105 IA #: 2105 DATE CREATED: SEP 05, 1997 CUSTODIAL PACKAGE: CONTROLLED SUBSTANCES CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2105 GENERAL DESCRIPTION: PDM requests permission to check for the PSDMGR security key. VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE VIEWER: BARNETT,JANICE H STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24965284 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2106 IA #: 2106 DATE CREATED: SEP 05, 1997 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2106 GENERAL DESCRIPTION: PDM requests permission to check for the PSNMGR security key. VIEWER: SCHLEHUBER,CAMERON VIEWER: ALEXANDER,DAVID VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24965302 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2107 IA #: 2107 DATE CREATED: SEP 05, 1997 CUSTODIAL PACKAGE: CMOP CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: PSXCMOPMGR GENERAL DESCRIPTION: PDM requests permission to check for the PSXCMOPMGR security key. VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: WARREN,BRENDA A VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24965330 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2108 IA #: 2108 DATE CREATED: SEP 05, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2108 GENERAL DESCRIPTION: PDM requests permission to use the PSJ OAOPT input template to Pharmacy System file 59.7. VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33261965 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2109 IA #: 2109 FILE NUMBER: 53.45 GLOBAL ROOT: PS(53.45 DATE CREATED: SEP 16, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2109 ID: PS(53.45 GENERAL DESCRIPTION: PDM requests to look at INPATIENT USER PARAMETERS file 53.45. PDM requests permission to use the [PSJ IUP SUPER EDIT] and [PSJ IUP USER EDIT] input templates for INPATIENT USER PARAMETERS file 53.45. VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24965374 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2110 IA #: 2110 FILE NUMBER: 59.6 GLOBAL ROOT: PS(59.6 DATE CREATED: SEP 16, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2110 ID: PS(59.6 GENERAL DESCRIPTION: PDM requests permission to look at INPATIENT WARD PARAMETERS file 59.6. PDM requests permission to use the [PSJIWPIEDIT] input template for INPATIENT WARD PARAMETERS file 59.6. VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24965387 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2111 IA #: 2111 FILE NUMBER: 57.7 GLOBAL ROOT: PS(57.7 DATE CREATED: SEP 16, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2111 ID: PS(57.7 GENERAL DESCRIPTION: PDM requests permission to look at MEDICATION ADMINISTERING TEAM file 57.7. PDM requests permission to use the [PSJUMATE] input template to MEDICATION ADMINISTERING TEAM file 57.7. VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24965399 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2112 IA #: 2112 FILE NUMBER: 57.5 GLOBAL ROOT: PS(57.5 DATE CREATED: SEP 16, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2112 ID: PS(57.5 GENERAL DESCRIPTION: PDM requests permission to look at WARD GROUP file 57.5. PDM requests permission to use the [PSJU WG] input template for WARD GROUP file 57.5. VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24965413 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2114 IA #: 2114 FILE NUMBER: 51.15 GLOBAL ROOT: PS(51.15 DATE CREATED: SEP 16, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2114 ID: PS(51.15 GENERAL DESCRIPTION: PDM requests permission to look at ADMINISTRATION SHIFT file 51.15. PDM requests permission to use the [PSJ SHIFT EDIT] input template for ADMINISTRATION SHIFT file 51.15. VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24965450 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2115 IA #: 2115 FILE NUMBER: 53.2 GLOBAL ROOT: PS(53.2 DATE CREATED: SEP 16, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2115 ID: PS(53.2 GENERAL DESCRIPTION: PDM requests permission to look at ORDER SET file 53.2. PDM requests permission to use the [PSJUOSE] input template for UNIT DOSE ORDER SET file 53.2. VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24965472 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2116 IA #: 2116 DATE CREATED: SEP 05, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2116 GENERAL DESCRIPTION: PDM requests permission to use [PSJ SCHEDULE EDIT] and [PSJ EXT SCHEDULE EDIT] input templates to ADMINISTRATION SCHEDULE file 51.1. VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33261968 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2118 IA #: 2118 DATE CREATED: SEP 05, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: %ZISTCP NAME: DBIA2118 ID: %ZISTCP GENERAL DESCRIPTION: This routine is part of the Kernel Device handler. It is used for making TCP/IP connection between computers. It only deals with IP address. STATUS: Active MAIL MESSAGE: 24917534 COMPONENT/ENTRY POINT: CALL(IPaddress,Socket [,Timeout]) COMPONENT DESCRIPTION: This entry point is used to make a TCP/IP connection to a remote system. VARIABLES: IPaddress TYPE: Input VARIABLES DESCRIPTION: This first parameter is the IP address of the host system to connect to. It must be in the IP format of 4 numbers separated by dots. i.e. 152.128.1.25 VARIABLES: Socket TYPE: Input VARIABLES DESCRIPTION: This second parameter is the socket to connect to on the remote host. It is a integer from 1-65535. Values below 5000 are for standard internet services like SMTP mail. VARIABLES: Timeout TYPE: Input VARIABLES DESCRIPTION: This optional third parameter is the timeout to apply to the open. VARIABLES: IO TYPE: Output VARIABLES DESCRIPTION: If the connection is made then IO will hold the implemention value that is used to reference the connection. VARIABLES: POP TYPE: Output VARIABLES DESCRIPTION: This variable reports the connection status. A value of 0 means the connection was successful. A positive value means the connection failed. It works the same as a call to %ZIS. COMPONENT/ENTRY POINT: CLOSE COMPONENT DESCRIPTION: This call is used to close the connection opened with the CALL entry point. It works like a call to %ZISC. VARIABLES: IO TYPE: Both VARIABLES DESCRIPTION: This hold the connection to close. It gets reset to the home device for the process. NUMBER: 2119 IA #: 2119 DATE CREATED: SEP 05, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: %ZISUTL NAME: DBIA2119 ID: %ZISUTL GENERAL DESCRIPTION: Access to some device handler tools. STATUS: Active MAIL MESSAGE: 29783275 COMPONENT/ENTRY POINT: OPEN(handle [,valiop] [,.valzis]) COMPONENT DESCRIPTION: One of three functions that support using multiple devices at the same time. OPEN^%ZISUTL returns all the same output variables as the ^%ZIS entry point. OPEN^%ZISUTL serves as a "wrapper" arount the ^%ZIS entry point, providing additional management of IO variables that ^%ZIS does not (principally to support opening multiple devices simultaneously). VARIABLES: handle TYPE: Input VARIABLES DESCRIPTION: A unique free text name to associate with a device you want to open. VARIABLES: valiop TYPE: Input VARIABLES DESCRIPTION: Output device specification, in the same format as the IOP input variable for the %ZIS entry point. The one execption to this is passing a value of null: this is like leaving IOP undefined. With %ZIS, on the other hand, setting IOP to null specifies the home device. To request the home device, pass a value of "HOME" instead. VARIABLES: valzis TYPE: Input VARIABLES DESCRIPTION: (optional) Input specification array, in the same format (and with the same meanings) as the %ZIS input specification array for the ^%ZIS entry point. Must be passed by reference. Please see the documentation of the ^%ZIS function for more information. COMPONENT/ENTRY POINT: CLOSE(handle) COMPONENT DESCRIPTION: Use the CLOSE^%ZISUTL to close a device opened with the OPEN^%ZISUTL function. When you close a device with CLOSE^%ZISUTL, the IO variables are set back to the home device's and the home device is made the current device. VARIABLES: handle TYPE: Input VARIABLES DESCRIPTION: The handle of a device opened with an OPEN^%ZISUTL call. COMPONENT/ENTRY POINT: SAVDEV(handle) COMPONENT DESCRIPTION: Use SAVDEV^%ZISUTL to save the current device IO* variables under the handle name. VARIABLES: handle TYPE: Input VARIABLES DESCRIPTION: A unique free text name to associate with a device you want to use. VARIABLES: IO* TYPE: Both VARIABLES DESCRIPTION: The standard set of IO variables. COMPONENT/ENTRY POINT: RMDEV(handle) COMPONENT DESCRIPTION: This call deletes the data associated with the handle. It doesn't change any of the IO* variables. VARIABLES: handle TYPE: Input VARIABLES DESCRIPTION: A unique free text name to associate with a device you want to delete. COMPONENT/ENTRY POINT: USE(handle) COMPONENT DESCRIPTION: Use the USE^%ZISUTL to restore the variables save with OPEN^%ZISUTL or SAVDEV^%ZISUTL. It then does a USE of the device if it is open. The same a a DO USE^%ZISUTL(handle) U IO. VARIABLES: IO* TYPE: Output VARIABLES DESCRIPTION: Standard IO variables. NUMBER: 2120 IA #: 2120 DATE CREATED: SEP 05, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUSRB NAME: DBIA2120 ID: XUSRB GENERAL DESCRIPTION: IA between Kernel and RPB Broker. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24917540 COMPONENT/ENTRY POINT: $$KCHK(key) COMPONENT DESCRIPTION: This entry point is used to check if a user holds a given KEY. VARIABLES: key TYPE: Input VARIABLES DESCRIPTION: A security key name to be checked. COMPONENT/ENTRY POINT: LOGOUT COMPONENT DESCRIPTION: This entry point is used by BROKER to update Kernel sign-on logs when a user ends a Broker session. SUBSCRIBING PACKAGE: RPC BROKER ISC: Oakland SUBSCRIBING PACKAGE: INTEGRATED BILLING NUMBER: 2121 IA #: 2121 DATE CREATED: SEP 05, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUSRB1 NAME: DBIA2121 ID: XUSRB1 GENERAL DESCRIPTION: This is a custom call developed for the RPC Broker. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24917541 COMPONENT/ENTRY POINT: $$DECRYP(string) COMPONENT DESCRIPTION: This call is used to unscramble strings that are sent between the Broker client and Kernel. VARIABLES: string TYPE: Input VARIABLES DESCRIPTION: A text string. SUBSCRIBING PACKAGE: RPC BROKER ISC: Oakland NUMBER: 2122 IA #: 2122 DATE CREATED: SEP 05, 1997 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOHELP1 NAME: DBIA2122 ID: PSOHELP1 GENERAL DESCRIPTION: PDM requests permission to call PSOHELP1. This routine is called by a compiled cross-reference routine (PSSJXR) ON PHARMACY PATIENT file 55. PSOHELP1 sets two cross-references in file #55 ("A" and "P") involked from VA FileMan. VIEWER: SCHLEHUBER,CAMERON VIEWER: BROWN,STANLEY A VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE VIEWER: RUZBACKI,RON T STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33261995 COMPONENT/ENTRY POINT: SREF VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: DATE VARIABLES: DA TYPE: Both VARIABLES DESCRIPTION: ENTRY NUMBER IN SUB-FILE 55.03 VARIABLES: DA(1) TYPE: Both VARIABLES DESCRIPTION: ENTRY NUMBER COMPONENT/ENTRY POINT: KREF VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: date VARIABLES: DA(1) TYPE: Both VARIABLES DESCRIPTION: entry number VARIABLES: DA TYPE: Both VARIABLES DESCRIPTION: ENTRY NUMBER IN SUB-FILE 55.05 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2124 IA #: 2124 DATE CREATED: SEP 05, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XQCS NAME: DBIA2124 ID: XQCS GENERAL DESCRIPTION: Special call to menu system to check access to options and RPC's. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29789396 COMPONENT/ENTRY POINT: $$CHK(user, option, rpc) COMPONENT DESCRIPTION: This call checks that a given user has access to a option or RPC. VARIABLES: user TYPE: Input VARIABLES DESCRIPTION: DUZ VARIABLES: option TYPE: Input VARIABLES DESCRIPTION: A option name. VARIABLES: rpc TYPE: Input VARIABLES DESCRIPTION: A RPC name. COMPONENT/ENTRY POINT: $$OPTLK(option) COMPONENT DESCRIPTION: This API does a lookup on the OPTION file to find a option IEN that is passed back to the calling routine. VARIABLES: option TYPE: Input VARIABLES DESCRIPTION: This is the Option name to be looked up. SUBSCRIBING PACKAGE: RPC BROKER ISC: Oakland EDITOR: FORT,WALLY NUMBER: 2125 IA #: 2125 FILE NUMBER: 53.45 GLOBAL ROOT: PS(53.45 DATE CREATED: SEP 08, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2125 ID: PS(53.45 GLOBAL REFERENCE: PS(53.45, FIELD NUMBER: .01 FIELD NAME: INPATIENT USER LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: MAY SELECT DISPENSE DRUGS LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .03 FIELD NAME: ALLOW USER TO RENEW ORDERS LOCATION: 0;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: .04 FIELD NAME: ALLOW USER TO HOLD ORDERS LOCATION: 0;4 ACCESS: Both R/W w/Fileman FIELD NUMBER: .05 FIELD NAME: ALLOW USER TO D/C ORDERS LOCATION: 0;5 ACCESS: Both R/W w/Fileman FIELD NUMBER: .06 FIELD NAME: PRINT PROFILE IN ORDER ENTRY LOCATION: 0;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: .07 FIELD NAME: LABEL PRINTER LOCATION: 0;7 ACCESS: Both R/W w/Fileman FIELD NUMBER: .08 FIELD NAME: TYPE OF USER LOCATION: 0;8 ACCESS: Both R/W w/Fileman FIELD NUMBER: .09 FIELD NAME: ALLOW AUTO-VERIFY FOR USER LOCATION: 0;9 ACCESS: Both R/W w/Fileman FIELD NUMBER: .1 FIELD NAME: USE WARD LABEL SETTINGS LOCATION: 0;10 ACCESS: Both R/W w/Fileman FIELD NUMBER: .11 FIELD NAME: INPATIENT PROFILE ORDER SET LOCATION: 0;11 ACCESS: Both R/W w/Fileman FIELD NUMBER: .12 FIELD NAME: ORDER ENTRY PROCESS LOCATION: 0;12 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: PDM requests permission to look at INPATIENT USE PARAMETERS file 53.45. VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33261962 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2127 IA #: 2127 FILE NUMBER: 50.3 GLOBAL ROOT: PS(50.3 DATE CREATED: SEP 08, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2127 ID: PS(50.3 GLOBAL REFERENCE: PS(50.3,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .02 FIELD NAME: DEA, SPECIAL HANDLING LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .03 FIELD NAME: MESSAGE LOCATION: 0;3 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: PS(50.3,D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: APPLICATION LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: NON-FORMULARY LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .03 FIELD NAME: INACTIVE DATE LOCATION: 0;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: .05 FIELD NAME: DAY (nD) or DOSE (nL) LIMIT LOCATION: 0;5 ACCESS: Both R/W w/Fileman FIELD NUMBER: .06 FIELD NAME: MED ROUTE LOCATION: 0;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: .07 FIELD NAME: SCHEDULE TYPE LOCATION: 0;7 ACCESS: Both R/W w/Fileman FIELD NUMBER: .08 FIELD NAME: SCHEDULE LOCATION: 0;8 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: PS(50.3,D0,1,D1,1,D2,0) FIELD NUMBER: .01 FIELD NAME: FORMULARY ALTERNATIVE LOCATION: 0;1 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: PS(50.3,D0,2,0) FIELD NUMBER: 2 FIELD NAME: SYNONYM LOCATION: 0;1 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: PDM requests permission to look at PRIMARY DRUG file 50.3. VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24965643 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2131 IA #: 2131 FILE NUMBER: 59.4 GLOBAL ROOT: PS(59.4 DATE CREATED: SEP 08, 1997 CUSTODIAL PACKAGE: CONTROLLED SUBSTANCES CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2131 ID: PS(59.4 GLOBAL REFERENCE: PS(59.4, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: 4 FIELD NAME: MERGE INV. SHEET AND PICK LIST LOCATION: 0;5 ACCESS: Both R/W w/Fileman FIELD NUMBER: 5 FIELD NAME: PRINT RETURN COLUMNS? LOCATION: 0;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: 4.5 FIELD NAME: AR/WS AMIS FLAG LOCATION: 0;25 ACCESS: Both R/W w/Fileman FIELD NUMBER: 5.5 FIELD NAME: IS SITE SELECTABLE FOR AR/WS? LOCATION: 0;26 ACCESS: Both R/W w/Fileman FIELD NUMBER: 5.6 FIELD NAME: PROMPT FOR BAR CODES? LOCATION: 0;27 ACCESS: Both R/W w/Fileman FIELD NUMBER: 31 FIELD NAME: IS SITE SELECTABLE FOR CS? LOCATION: 0;31 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: PDM requests permission to look at INPATIENT SITE file 59.4. VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33261950 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2132 IA #: 2132 FILE NUMBER: 51.15 GLOBAL ROOT: PS(51.15 DATE CREATED: SEP 08, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2132 ID: PS(51.15 GLOBAL REFERENCE: PS(51.15, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 1 FIELD NAME: ABBREVIATION LOCATION: 0;2 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 2 FIELD NAME: STANDARD START/STOP TIMES LOCATION: 0;3 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 4 FIELD NAME: PACKAGE LOCATION: 0;4 ACCESS: Direct Global R/W & w/Fileman GLOBAL REFERENCE: PS(51.15,D0,1, FIELD NUMBER: .01 FIELD NAME: HOSPITAL LOCATION LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 1 FIELD NAME: START/STOP TIMES LOCATION: 0;2 ACCESS: Direct Global R/W & w/Fileman GENERAL DESCRIPTION: PDM requests permission to look at ADMINISTRATION SHIFT file 51.15. VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24965745 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2133 IA #: 2133 FILE NUMBER: 56 GLOBAL ROOT: PS(56 DATE CREATED: SEP 08, 1997 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2133 ID: PS(56 GLOBAL REFERENCE: PS(56,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 1 FIELD NAME: INGREDIENT 1 LOCATION: 0;2 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 2 FIELD NAME: INGREDIENT 2 LOCATION: 0;3 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 3 FIELD NAME: SEVERITY LOCATION: 0;4 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 6 FIELD NAME: LOCALLY EDITED LOCATION: L;1 ACCESS: Direct Global R/W & w/Fileman GENERAL DESCRIPTION: PDM requests permission to look at DRUG INTERACTION file 56. VIEWER: SCHLEHUBER,CAMERON VIEWER: ALEXANDER,DAVID VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24965769 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2135 IA #: 2135 DATE CREATED: SEP 08, 1997 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCFSITE NAME: DBIA2135 ID: PRCFSITE GENERAL DESCRIPTION: The Prosthetics package requests permission to use IFCAP program PRCFSITE to set special IFCAP variables used in the package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24855249 COMPONENT/ENTRY POINT: DIVFY VARIABLES: PRC('FY') TYPE: Output VARIABLES DESCRIPTION: Return the current fiscal year. VARIABLES: PRC('PARAM') TYPE: Output VARIABLES DESCRIPTION: Returns the zero node of the parameter file. VARIABLES: PRC('PER') TYPE: Output VARIABLES DESCRIPTION: Returns information about the user. VARIABLES: PRC('QTR') TYPE: Output VARIABLES DESCRIPTION: Returns the current fiscal quarter. VARIABLES: PRC('SITE') TYPE: Output VARIABLES DESCRIPTION: Returns the site/station number. VARIABLES: PRCF('X') TYPE: Input VARIABLES DESCRIPTION: Set to "S" which defines which local values to return. SUBSCRIBING PACKAGE: PROSTHETICS ISC: Hines NUMBER: 2136 IA #: 2136 FILE NUMBER: 50.608 GLOBAL ROOT: PS(50.608 DATE CREATED: SEP 09, 1997 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2136 ID: PS(50.608 GLOBAL REFERENCE: PS(50.608,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: PDM requests permission to look at PACKAGE TYPE file 50.608. VIEWER: SCHLEHUBER,CAMERON VIEWER: ALEXANDER,DAVID VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24965822 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2137 IA #: 2137 FILE NUMBER: 50.609 GLOBAL ROOT: PS(50.609 DATE CREATED: SEP 09, 1997 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2137 ID: PS(50.609 GLOBAL REFERENCE: PS(50.609,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: PDM requests permission to look at PACKAGE SIZE file 50.609. VIEWER: SCHLEHUBER,CAMERON VIEWER: ALEXANDER,DAVID VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24965837 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2138 IA #: 2138 FILE NUMBER: 50.605 GLOBAL ROOT: PS(50.605 DATE CREATED: SEP 09, 1997 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2138 ID: PS(50.605 GLOBAL REFERENCE: PS(50.605,D0,0) FIELD NUMBER: .01 FIELD NAME: CODE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: CLASSIFICATION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: PDM requests permission to look at VA DRUG CLASS file 50.605. VIEWER: SCHLEHUBER,CAMERON VIEWER: ALEXANDER,DAVID VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24965853 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2139 IA #: 2139 FILE NUMBER: 57.1 GLOBAL ROOT: PS(57.1 DATE CREATED: NOV 25, 1998 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2139 ID: PS(57.1 GLOBAL REFERENCE: PS(57.1,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: PROTOCOL LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: TYPE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(57.1,D0,3,D1,0) FIELD NUMBER: .01 FIELD NAME: ADDITIVE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: STRENGTH LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(57.1,D0,4,D1,0) FIELD NUMBER: .01 FIELD NAME: SOLUTION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: VOLUME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(57.1,D0,2,D1,0) FIELD NUMBER: 6 FIELD NAME: PROVIDER COMMENTS LOCATION: 2;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(57.1,D0,1) FIELD NUMBER: 3 FIELD NAME: *PRIMARY DRUG LOCATION: 1;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: MED ROUTE LOCATION: 1;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5 FIELD NAME: SCHEDULE LOCATION: 1;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 9 FIELD NAME: DOSAGE ORDERED LOCATION: 1;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 10 FIELD NAME: INFUSION RATE LOCATION: 1;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 11 FIELD NAME: PROVIDER COMMENTS PROMPT LOCATION: 1;6 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: PDM requests permission to look at PHARMACY QUICK ORDER file 57.1. VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28415724 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2140 IA #: 2140 FILE NUMBER: 53.1 GLOBAL ROOT: PS(53.1, DATE CREATED: SEP 09, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2140 ID: PS(53.1, GLOBAL REFERENCE: PS(53.1, FIELD NUMBER: 7 FIELD NAME: SCHEDULE TYPE LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This describes the type of schedule for the dispensing of the medication(s) that make up the order. PRE-OP orders are usually considered to be ON-CALL orders, and orders dispensed as MUTLI-DOSE CONTAINERS are usually considered to be FILL ON REQUEST orders. FIELD NUMBER: 49 FIELD NAME: ORDERS FILE ENTRY LOCATION: 0;21 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the pointer value of the corresponding entry in the Orders file (100) when the order is entered through the OE/RR process. FIELD NUMBER: 9 FIELD NAME: RENEWAL LOCATION: 4;9 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 28 FIELD NAME: STATUS LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Pharmacy Data Management package requests permission to read fields from the NON-VERIFIED ORDERS file (#53.1). VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33070423 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2142 IA #: 2142 FILE NUMBER: 9.7 GLOBAL ROOT: XPD(9.7 DATE CREATED: SEP 10, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: INSTALL File Read ID: XPD(9.7 GLOBAL REFERENCE: XPD(9.7, GLOBAL DESCRIPTION: This is the NAME cross-reference of the INSTALL File (#9.7). GENERAL DESCRIPTION: Because we didn't do a package link for Library Version 2.5 Patch 1, checks for installation of this patch will not work. Would like to use $D(^XPD(9.7,"B","LBR*2.5*1")) in our environment check programs until next version of the Library package comes out. STATUS: Active DURATION: Next Version MAIL MESSAGE: 24954507 GOOD ONLY FOR VERSION: 2.5 SUBSCRIBING PACKAGE: LIBRARY ISC: Washington/Silver Spring NUMBER: 2143 IA #: 2143 FILE NUMBER: 19.2 GLOBAL ROOT: DIC(19.2 DATE CREATED: SEP 10, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Option Schedule Look-up ID: DIC(19.2 GLOBAL REFERENCE: DIC(19.2, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Lookup option with DIC FIELD NUMBER: 2 FIELD NAME: QUEUED TO RUN AT WHAT TIME LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: To show the user when the Library TaskMan option is scheduled to run. FIELD NUMBER: 6 FIELD NAME: RESCHEDULING FREQUENCY LOCATION: 0;6 ACCESS: Read w/Fileman FIELD DESCRIPTION: To show the user how often the Library TaskMan option is scheduled to run. GLOBAL DESCRIPTION: S DIC="^DIC(19.2,",DIC(0)="NZ",X=OPTION D ^DIC Y(0) returns all necessary values for report display. GENERAL DESCRIPTION: Sometimes the Library package TaskMans are not restarted when the system is shut down. This causes a problem with transaction processing back and forth with FORUM. To help the Librarians with observation of this problem, a program has been written that displays the option, the frequency and the next scheduled time. We need to do a DIC lookup into file 19.2 to retrieve this information because using XUTMOPT displays more information than the general user needs to see and also page feeds for each option. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24954691 SUBSCRIBING PACKAGE: LIBRARY ISC: Washington/Silver Spring NUMBER: 2144 IA #: 2144 DATE CREATED: SEP 17, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSGAL5 NAME: DBIA2144 ID: PSGAL5 GENERAL DESCRIPTION: PDM requests permission to use the PSGAL5 Inpatient Medications routine. PHARMACY PATIENT File (#55) belongs to PDM, however, there are subfiles within this file which are compiled cross-references. The PSSJXR routine serves as the driver for these cross-references in file #55. This driver routine calls PSGAL5 routine. VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: TEAGUE,LYN VIEWER: VO,MAI STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33261957 COMPONENT/ENTRY POINT: PSGAL5 VARIABLES: PSGAL TYPE: Input VARIABLES DESCRIPTION: OLD VALUE VARIABLES: PSGALFF TYPE: Input VARIABLES DESCRIPTION: FIELD NUMBER IN SUB-FILE 55.09 VARIABLES: PSGALFN TYPE: Input VARIABLES DESCRIPTION: SUB-FILE NUMBER SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2145 IA #: 2145 DATE CREATED: SEP 17, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSGAMSA NAME: DBIA2145 ID: PSGAMSA GENERAL DESCRIPTION: PDM requests permission to use the PSGAMSA Inpatient Medications routine. A ZOSF test will be done before invoking the routine. PHARMACY PATIENT File (#55) belongs to PDM, however, there are subfiles within this file which are compliled cross-references. The PSSJXR routine serves as the driver for these cross-references in file #55. This driver routine calls PSGAMSA routine. VIEWER: SCHLEHUBER,CAMERON VIEWER: MONTALI,MICHAEL VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE VIEWER: TEAGUE,LYN VIEWER: VO,MAI STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33261919 COMPONENT/ENTRY POINT: EN VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: ENTRY NUMBER VARIABLES: PSGORD TYPE: Input VARIABLES DESCRIPTION: PRE-EXCHANGE UNITS VARIABLES: PSGORD1 TYPE: Input VARIABLES DESCRIPTION: EXTRA UNITS DISPENSED VARIABLES: PSGLOG TYPE: Input VARIABLES DESCRIPTION: RETURNS SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2146 IA #: 2146 DATE CREATED: SEP 17, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSGCT NAME: DBIA2146 ID: PSGCT GENERAL DESCRIPTION: A ZOSF test will be done before invoking the routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31602016 COMPONENT/ENTRY POINT: $$EN(ST,AM) VARIABLES: ST TYPE: Input VARIABLES DESCRIPTION: Start Date/Time in FileMan format. VARIABLES: AM TYPE: Input VARIABLES DESCRIPTION: # minutes to add or subtract. VARIABLES: $$EN TYPE: Output VARIABLES DESCRIPTION: new date. SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham EDITOR: TEAGUE,LYN NUMBER: 2150 IA #: 2150 DATE CREATED: SEP 17, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSGNE3 NAME: DBIA2150 ID: PSGNE3 GENERAL DESCRIPTION: A ZOSF test will be done before invoking the routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31601997 COMPONENT/ENTRY POINT: $$ENSD(schedule,admin time,login time,'') VARIABLES: schedule TYPE: Input VARIABLES: admin time TYPE: Input VARIABLES DESCRIPTION: Administration Times. VARIABLES: login time TYPE: Input VARIABLES DESCRIPTION: Login Date/Time. VARIABLES: $$ENSD TYPE: Output VARIABLES DESCRIPTION: Default Start Date/Time for an Inpatient Medication Order. SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham EDITOR: TEAGUE,LYN NUMBER: 2153 IA #: 2153 DATE CREATED: JUL 07, 2000 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSGSETU NAME: DBIA2153 ID: PSGSETU GENERAL DESCRIPTION: The Pharmacy Data Management V. 1.0 application requests an integration agreement with the Inpatient Medications V. 5.O application to make an external call to ENIVKV^PSGSETU. The external call is executed from the PSSVIDRG routine within the Pharmacy Data Management application. The PSSVIDRG routine will perform an ^%ZOSF test before invoking the routine This external call is used to clean up or kill existing IV variables. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31627261 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham EDITOR: HOLMES,TIM NUMBER: 2154 IA #: 2154 DATE CREATED: SEP 17, 1997 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSIVWL NAME: DBIA2154 ID: PSIVWL GENERAL DESCRIPTION: PDM requests permission to use the PSIVWL Inpatient Medications routine. A ZOSF test will be done before invoking the routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31601967 COMPONENT/ENTRY POINT: ENT VARIABLES: PSIVMIN TYPE: Input VARIABLES DESCRIPTION: PSIVMIN=# of minutes to add or subtract. VARIABLES: PSIVSD TYPE: Input VARIABLES DESCRIPTION: PSIVSD=date to add or subtract from in FileMan format. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Y=result. SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham EDITOR: TEAGUE,LYN NUMBER: 2155 IA #: 2155 DATE CREATED: JUL 07, 2000 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSIV NAME: DBIA2155 ID: PSIV GENERAL DESCRIPTION: Pharmacy Data Management V. 1.0 application requests an integration agreement with the Inpatient Medications V. 5.O application to make an external call to ENQ^PSIV. The external call is executed from the PSSVIDRG routine within the Pharmacy Data Management application. This external call is used to read a user response. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31627260 COMPONENT/ENTRY POINT: ENQ COMPONENT DESCRIPTION: Example: ... an IV ADDITIVE or IV SOLUTION (A/S): ADDITIVE// ^ VARIABLES: X TYPE: Both VARIABLES DESCRIPTION: **Input** X = data string with conditions. X ="... an IV ADDITIVE or IV SOLUTION (A/S): ^ADDITIVE^^ADDITIVE,SOLUTION" **Output** X= Results or User Response SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham EDITOR: HOLMES,TIM NUMBER: 2156 IA #: 2156 DATE CREATED: JUL 07, 2000 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSIVHLP1 NAME: DBIA2156 ID: PSIVHLP1 GENERAL DESCRIPTION: Pharmacy Data Management V. 1.0 application requests an integration agreement with the Inpatient Medications V. 5.O application to make an external call to the PSIVHLP1 routine. The external call is executed from the PSSVIDRG routine within the Pharmacy Data Management application. This external call is used to provide help information related to IV Additives and Solutions. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31627210 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham EDITOR: HOLMES,TIM NUMBER: 2157 IA #: 2157 DATE CREATED: JUL 07, 2000 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSIVXU NAME: DBIA2157 ID: PSIVXU GENERAL DESCRIPTION: The Pharmacy Data Management V. 1.0 application requests an integration agreement with the Inpatient Medications V. 5.O application to make an external call to the PSIVXU routine. The external call is executed from the PSSVIDRG routine within the Pharmacy Data Management application. The PSSVIDRG routine will perform an ^%ZOSF test before invoking the routine. This external call is used to group drug information for reports. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31627262 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham EDITOR: HOLMES,TIM NUMBER: 2159 IA #: 2159 DATE CREATED: SEP 29, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2159 GENERAL DESCRIPTION: PDM requests permission to look at the ^DD global for following files: Global route File # File -------------------------------------------------------------------- ^DD(50 50 DRUG File 50 DRUG MUMPS x-ref (AUDAP) Field .01 GENERIC NAME - ^DD(50,51,0). ^DD("50",".01","1","3","0")="50^AUDAP^MUMPS" ^DD("50",".01","1","3","1")="I '$D(PSGINITF) S ^PSDRUG("AUDAP")=$S($D(^PS(59.7,1 ,20)):$P(^(20),"^"),1:"")" ^DD("50",".01","1","3","1.1")="S X=Y(0) S Y(1)=$S($D(^PSDRUG(D0,0)):^(0),1:"") S X=$P(Y(1),U,1) S XMB(1)=X" ^DD("50",".01","1","3","1.2")="S X=Y(0) S Y(2)=$C(59)_$S($D(^DD(50,51,0)):$P(^(0 ),U,3),1:""),Y(1)=$S($D(^PSDRUG(D0,0)):^(0),1:"") S X=$P($P(Y(2),$C(59)_$P(Y(1), U,9)_":",2),$C(59),1) S XMB(2)=X" ^DD("50",".01","1","3","1.3")="S X=Y(0) S Y(1)=$S($DPSDRUG(D0,0)):^(0),1:"") S X=$S('$D(^PS(50.5,+$P(Y(1),U,2),0)):"",1:$P(^(0),U,1)) S XMB(3)=X" ^DD("50",".01","1","3","1.4")="S X=Y(0) S Y(1)=$S($D(^PSDRUG(D0,0)):^(0),1:"") S X1),U,10) S XMB(4)=X" ^DD("50",".01","1","3","2")="Q" ^DD("50",".01","1","3","2.2")="S X=Y(0) S Y(2)=$C(59)_$S($D(^DD(50,51,0)):$P(^(0 ),U,3),1:""),Y(1)=$S($D(^PSDRUG(D0,0)):^(0),P(Y(2),$C(59)_$P(Y(1), U,9)_":",2),$C(59),1) S XMB(2)=X" ^DD("50",".01","1","3","2.3")="S X=Y(0) S Y(1)=$S($D(^PSDRUG(D0,0)):^(0),1:"") S X=$S('$D(^PS(50.5,+$P(Y(1),U,2),0)):"",(0),U,1)) S XMB(3)=X" ^DD("50",".01","1","3","2.4")="S X=Y(0) S Y(1)=$S($D(^PSDRUG(D0,0)):^(0),1:"") S X=$P(Y(1),U,10) S XMB(4)=X" ^DD("50",".01","1","3","3")="Used by the Unit npatient Medications package s." **************** ^DD(51.1 51.1 ADMINISTRATION SCHEDULE File 52.6 IV ADDITIVES INPUT TRANSFORM Field 5 ADMINISTRATION TIMES - ^DD(51.1,1,0) ^DD("52.6","5","0")="ADMINISTRATION TIMES^FX^^0;6^X $P(^DD(51.1,1,0),"^",5,999) Q" ^DD("52.6","5","3")="Answer must be 2-119 characters in length." ^DD("52.6","5","20","0")="^.3LA^1^1" ^DD("52.6","5","20","1","0")="PSJI" ^DD("52.6","5","21","0")="^^3^3^2910412^^^^" ^DD("52.6","5","21","1","0")=" Enter the admin. times that this drug is given m ost frequently. This" ^DD("52.6","5","21","2","0")="field will be shown as default for the 'ADMIN. TIM ES: ' prompt during" ^DD("52.6","5","21","3","0")="ordry of IVPB's." ^DD("52.6","5","DT")="2910412" **************** ^DD(52.6 52.6 IV ADDITIVES File 52.6 IV ADDITIVES INPUT TRANSFORM Field 13 CONCENTRATION - ^DD(52.6,2,0) ^DD("52.6","13","0")="CONCENTRATION^FX^^0;10^K:X'=+X!(X>99999)!(X<0)!(X?.E1"."3 N .N) X I $D(X) S PSIVX=X,Y=^DD(52.6,2,0),X=$P(^PS(52.6,D0,0),"^",3) D ENC^PSIV D EN^DDIOL(" "_X_"/ML","","?0") S X=PSIVX_" "_X_"/ML" K PSIVX" ^DD("52.6","13","3")="Type a number between 0 and 99999 (no more than 2 decimal digits, and no trailing 0's are allowed)." **************** ^DD(50.4 50.4 DRUG ELECTROLYTES File 52.6 IV ADDITIVES INPUT TRANSFORM Subfile 52.62 Field 1 CONCENTRATION - ^DD(50.4,1,0) ^DD("52.62","1","0")="CONCENTRATION^RFX^^0;2^K:+X'=X!(X>99999)!(X<0)!(X?.E1"."5 N .N) X I $D(X) S PSIVX=X,Y=^DD(50.4,1,0),X=$P(^PS(50.4,+^PS(52.6,DA(1),2,DA,0),0) ,"^",2) D ENC^PSIV S X=PSIVX_" "_X K PSIVX D STRTH^PSSDDUT2" ^DD("52.62","1","3")="Type a number between 0 and 99999." **************** ^DD(59.723 59.7 PHARMACY SYSTEM File 59.7 PHARMACY SYSTEM INPUT TRANSFORM Subfile 59.723 Field .01 TO SERVICE - ^DD(59.723,.01,0) PSYS2 D EN^DDIOL("(""From"" service is "_$S('$D(PS(59.7,D0,23,D1,0)):"UNKNOWN" ,$P(^(0),"^")]"":$P(^PS(";"_$P(^DD(59.723,.01,0),"^",3),";"_$P(^PS(59.7,D0,23,D 1 ,0),"^")_":",2),";"),1:"UNKNOWN")_")") Q **************** ^DD(55.01 55 PHARMACY PATIENT File 52.6 IV ADDITIVES INPUT TRANSFORM Field 4 USUAL IV SCHEDULE - ^DD(55.01,.09,0) ^DD("52.61","4","0")="USUAL IV SCHEDULE^FX^^0;5^X $P(^DD(55.01,.09,0),"^",5,999) " ^DD("52.61","4","3")="Answer must be 1-22 characters in length." ^DD("52.61","4","20","0")="^.3LA^1^1" ^DD("52.61","4","20","1","0")="PSJI" ^DD("52.61","4","21","0")="^^2^2^2910305^^^" ^DD("52.61","4","21","1","0")=" Enter the schedule that should be 'stuffed' int o the schedule field" ^DD("52.61","4","21","2","0")="of the IV order using this quick code." ^DD("52.61","4","DT")="2860223" **************** ^DD(50.4 50.4 DRUG ELECTROLYTES File 52.7 IV SOLUTIONS INPUT TRANSFORM Subfile 52.702 Field 1 CONCENTRATION - ^DD(50.4,1,0) ^DD("52.702","1","0")="CONCENTRATION^RFX^^0;2^K:+X'=X!(X>99999)!(X<0)!(X?.E1"." 5 N.N) X I $D(X) S PSIVX=X,Y=^DD(50.4,1,0),X=$P(^PS(50.4,+^PS(52.7,DA(1),2,DA,0),0 ),"^",2) D ENC^PSIV S X=PSIVX_" "_X K PSIVX D STRTH^PSSDDUT2" ^DD("52.702","1","3")="Type a number between 0 and 99999." VIEWER: SCHLEHUBER,CAMERON VIEWER: MARSHALL,RICK VIEWER: TATUM,WILLIAM STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25024610 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2160 IA #: 2160 GLOBAL ROOT: XUTL('OR',$J DATE CREATED: SEP 30, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2160 ID: XUTL('OR',$J GENERAL DESCRIPTION: Order Entry uses ^XUTL("OR",$J,xxx where xxx is the ancillary or support packages' namespace. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25124112 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 2161 IA #: 2161 DATE CREATED: OCT 29, 1997 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: HLFNC2 NAME: HLFNC2 ORIGINAL NUMBER: 2161 ID: HLFNC2 STATUS: Active MAIL MESSAGE: 36034824 COMPONENT/ENTRY POINT: INIT COMPONENT DESCRIPTION: API call INIT^HLFNC2(EID,.HL,INT), returns an array of values in the variable specified by parameter HL. If no error occurs, the array of values is returned. Otherwise, the single value HL is returned equal to the following : error code^error messages. VARIABLES: EID TYPE: Input VARIABLES DESCRIPTION: (required) Name or IEN of the event driver or subscriber protocol in the Protocol file (#101) for which the initialization variables are to be returned. VARIABLES: HL TYPE: Both VARIABLES DESCRIPTION: (required) Pass by reference. The variable in which the array of values will be returned or an error message. VARIABLES: INT TYPE: Input VARIABLES DESCRIPTION: 1 indicates that only array values for internal DHCP to DHCP message exchange should be initialized. COMPONENT/ENTRY POINT: MSH COMPONENT DESCRIPTION: API call MSH^HLFNC2(.HL,MID,.RESULT,SECURITY), builds an HL7 Message Header (MSH) segment. The MSH segment is returned in variable RESULT. VARIABLES: HL TYPE: Input VARIABLES DESCRIPTION: (required) Pass by reference. The array of values returned by the call to INIT^HLFNC2. VARIABLES: MID TYPE: Input VARIABLES DESCRIPTION: (required) The Message Control ID to be included in the MSH segment. The Batch Control ID for the batch is returned by the call to CREATE^HLTF. The application concatenates a sequential number to the batch ID to create the MID. VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: (required) Pass by reference. The variable that will be returned to the calling application that contains the MSH segment. If the MSH segment is longer than 245 characters there will be a RESULT(1). If the required variables, HL or MID are missing, RESULT will be null. VARIABLES: SECURITY TYPE: Input VARIABLES DESCRIPTION: An optional input parameter which includes the security to be included in field #8 of the MSH segment. COMPONENT/ENTRY POINT: RSPINIT COMPONENT DESCRIPTION: API call RSPINIT^HLFNC2(HL("EIDS"),.MYNSPCHL), returns an array of values in the variable specified by parameter MYNSPCHL. If no error occurs, the array of values is returned. Otherwise, the single value MYNSPCHL is returned equal to the following : error code^error messages. 1. Response message(s) not constructed properly when the HL7 field separator and encoding characters are different between sending system and receiving system. This issue is a result of the Processing Routine utilizing the environmental variables HL("FS") and HL("ECH") for both parsing the inbound HL7 message and constructing the outbound response message. After the Processing Routine has constructed the body of the response message, it calls GENACK^HLMA1 to queue up the response message. In turn, VistA HL7 constructs the message header based on the application associated with the subscriber protocol. Thus, the message header would have a different set of delimiters than the body of the HL7 message. This patch does not immediately correct this problem. However, it does provide a new API that can be used to create environmental variables to assist the Processing Routine in constructing the response message with the proper delimiters. This problem will only disappear when all VistA HL7 applications have migrated to using this new API to assist each in constructing the response message. New API: RSPINIT^HLFNC2 RSPINIT(EIDS,HL);Initialize Variables in HL array for Building a Response Message ; ;This is a subroutine call with parameter passing that returns an ;array of values in the variable specified by the parameter HL. If no ;error occurs, the array of values is returned. Otherwise, the single ;value HL is returned equal to the following: error code^error message ; ;Required Input Parameters ; EIDS = Name or IEN of the subscriber protocol in ; Protocol file for which the initialization variables are ; to be returned ; HL = The variable in which the array of values will be returned ; This parameter must be passed by reference ; Usage: D RSPINIT^HLFNC2(HL("EIDS"),.MYHLARRY) The Processing Routine should call this RSPINIT^HLFNC2 API to create the environmental variables needed to assist in constructing the response message. This API should be used especially when there is a possibility of the field separator and Encoding Characters being different between the sending application and the receiving application. The second parameter to this API should be an application namespaced variable passed by reference. This second parameter should NOT have HL namespace. However, the first parameter should be the name or IEN of the subscriber protocol. VistA HL7 provides this information to the Processing Routine through the variable HL("EIDS"). Therefore, HL("EIDS") should be used as the first parameter passed by value. As before, the Processing Routine should use the environmental variables HL("FS") and HL("ECH") in parsing the inbound HL7 message. However, the Processing Routine should use its own namespaced array as the second parameter of the call to RSPINIT^HLFNC2. For instance, if the second parameter was MYHLARRY, then the Processing Routine should use MYHLARRY("RFS") and MYHLARRY("RECH") as the variables containing the delimiters to assist in constructing the response message. This RSPINIT^HLFNC2 API may be called by the Processing Routine any time after the VistA HL7 has called the Processing Routine to process the inbound message and just before constructing the response message and calling GENACK^HLMA1. Below is an example of what may be returned in the second parameter: Description: ============================ MYHLARRY("RAN")=XWB RECEIVER receiving application name MYHLARRY("RECH")=~|\& response encoding characters MYHLARRY("RETN")=R08 response event type name MYHLARRY("RFS")=^ response field separator MYHLARRY("RMTN")=TBR response message type Before referencing the return array with the individual subscripts (as shown above) for the purpose of building the response message, the processing routine should first check the top level root (i.e.: MYHLARRY) for a possible error. If an error should occur, RSPINIT^HLFNC2 will return the error code and text description in the top level root. The format of this of this top level root when an error occurs will look like the following: MYHLARRY=Error_Code#^Error_Text The following is a list of potential errors returned: o Missing EIDS Input Parameter o Invalid Subscriber Protocol o Susbscriber Applicaton Missing in Protocol File The above list is provided only as an example and the actual error code and error text description are subject to change. Therefore, the processing routine should merely check to see if an error was returned. For example, I $G(MYHLARRY) D ALERT ... Q D BLDRSPNs D GENACK^HLMA1(... Note, the processing routine should check for an error to determine whether it should proceed with building the response message and subsequently call GENACK^HLMA1. If an error was returned by RSPINIT^HLFNC2, the processing routine should not proceed. However, if the processing routine already parsed and processed the inbound message, it should be aware that the sending application may continue to resend the same message repeatedly and as such act accordingly. VARIABLES: EIDS TYPE: Input VARIABLES DESCRIPTION: (required) Name or IEN of the subscriber protocol in the Protocol file (#101) for which the initialization variables are to be returned. This is the first parameter. The receiving application processing the inbound message should use HL("EIDS") as this first parameter to RSPINIT^HLFNC2 API as this variable is created for the application by the HL7 background job. This parameter should be used as a call by value. VARIABLES: HL TYPE: Output VARIABLES DESCRIPTION: (required) Pass by reference. The variable in which the array of values will be returned or an error message. The application should use its own namespaced HL array name. NUMBER: 2163 IA #: 2163 FILE NUMBER: 740 GLOBAL ROOT: QA(740 DATE CREATED: DEC 09, 1997 CUSTODIAL PACKAGE: QUALITY ASSURANCE INTEGRATION CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2163 ID: QA(740 GLOBAL REFERENCE: QA(740, FIELD NUMBER: 751 FIELD NAME: MULTI-DIVISIONAL INCID REP FACILITY LOCATION: QAN ACCESS: Read w/Fileman FIELD DESCRIPTION: Stores whether or not station is an NDBI Integration Site. FIELD NUMBER: 752 FIELD NAME: IR HOSPITAL DIVISION LOCATION: QAN2 ACCESS: Read w/Fileman FIELD DESCRIPTION: Multiple storing the names of the Medical Centers within an Integration Group. GENERAL DESCRIPTION: Requesting permission to add two new fields in QA Site Paramter file (#740) to store whether or not the station is multi-divisional for the Incident Reporting package (namespace QAQ), and if yes, the names of the Medical Centers within the NDBI Integration Group. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25720338 SUBSCRIBING PACKAGE: INCIDENT REPORTING ISC: Washington/Silver Spring NUMBER: 2164 IA #: 2164 DATE CREATED: OCT 30, 1997 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: HLMA NAME: HL7 MESSAGE ADMINISTRATION ORIGINAL NUMBER: 2161 ID: HLMA GENERAL DESCRIPTION: API to generate a HL7 message. STATUS: Active MAIL MESSAGE: 37164777 COMPONENT/ENTRY POINT: GENERATE COMPONENT DESCRIPTION: The GENERATE^HLMA(HLEID,HLARYTYP,HLFORMAT,HLRSLT,HLMTIEN,HLP) entry point to used to generate a HL7 message. It returns a unique message ID if a message is successfully generated. VARIABLES: HLEID TYPE: Input VARIABLES DESCRIPTION: The name or IEN of the event driver protocol in the Protocol File (#101). VARIABLES: HLARYTYP TYPE: Input VARIABLES DESCRIPTION: Array type. One of the following codes: LM = local array containing a single message LB = local array containing a batch of messages GM = global array containing a single message GB = global array containing a batch of messages VARIABLES: HLFORMAT TYPE: Input VARIABLES DESCRIPTION: Format of array, 1 for pre-formatted in HL7 format, otherwise 0 VARIABLES: HLRESLT TYPE: Both VARIABLES DESCRIPTION: The variable that will be returned to the calling application with either a error message or a unique message ID. VARIABLES: HLMTIEN TYPE: Input VARIABLES DESCRIPTION: Optional IEN of entry in Message Text file where the message being generated is to be stored. This parameter is only passed for a batch type message. VARIABLES: HLP TYPE: Input VARIABLES DESCRIPTION: The HLP parameter is passed-by-reference. The HLP subscripts that are processed by GENERATE^HLMA are identical to the DIRECT^HLMA HLP subscripts. These subscripts are listed below. o HLP("PRIORITY") = I for immediate or D for deferred o HLP("SECURITY") = A 1 to 40 character string o HLP("CONTPTR") = Continuation pointer, a 1 to 180 character string o HLP("NAMESPACE") = Free-text value, 4 character limit, stored that is to be stored in the NAMESPACE field (#16) in the HL Message Text file (#772.) o HLP("SUBSCRIBER") = Free-text, multi-piece value, used to control the routing-related fields in the MSH segment. See patch HL*1.6*93 documentation for full details. COMPONENT/ENTRY POINT: DIRECT COMPONENT DESCRIPTION: The DIRECT^HLMA(HLEID,HLARYTYP,HLFORMAT,HLRSLT,HLMTIEN,HLP) entry point is used to generate a HL7 message. It returns a unique message ID if a message was successfully generated. Unlike the GENERATE^HLMA API, the DIRECT^HLMA API opens the connection directly for message delivery. (GENERATE^HLMA delivers messages via queued background job.) Applications that use the DIRECT API must provide the guaranteed delivery if needed. Call INIT^HLFNC2 before making this call, to set up HL7 environment variables needed to build your message and needed by DIRECT^HLMA. The DIRECT^HLMA call has the same input parameters as GENERATE^HLMA. Like GENERATE^HLMA, it expects segments for the message to be already loaded in the HLA("HLS") local array or the^TMP("HLS") global array. For more information on the expected format of HLA("HLS") or^TMP("HLS"), please see the GENERATE^HLMA call. To select the subscriber to transmit to, this call first checks the contents of the HLL("LINKS")array; it will use first record it finds. If that array is empty, it uses the first subscriber protocol it finds in the Subscribers multiple of the event driver protocol. Upon return, DIRECT^HLMA does not invoke the event driver protocol's GENERATE/PROCESS ACK ROUTINE to processes the acknowledgment. When control is returned to the calling routine, the environment is left in the same condition as if you were in the "processing routine environment" when receiving an acknowledgment; the variables HLNEXT,HLNODE, and HLQUIT are defined so that you can process the response. Note that DIRECT^HLMA supports: o All acknowledgment modes (including deferred acknowledgments o Batch message transmission The timeout for the synchronous transmission is determined by the settings of the TCP used. Example: D DIRECT^HLMA("EVENT DRIVER PROTOCOL","GB",1,.MYRESULT) I +$P(MYRESULT,U,2) D ERR Q ; message was not transmitted I HLMTIEN D PROCESS ; response was returned from target system VARIABLES: HLEID TYPE: Input VARIABLES DESCRIPTION: The name or IEN of the event driver protocol in the Protocol File (#101). VARIABLES: HLARYTYP TYPE: Input VARIABLES DESCRIPTION: Array type. One of the following codes: LM = local array containing a single message LB = local array containing a batch of messages GM = global array containing a single message GB = global array containing a batch of messages VARIABLES: HLFORMAT TYPE: Input VARIABLES DESCRIPTION: Format of array, 1 for pre-formatted in HL7 format, otherwise 0 VARIABLES: HLRESLT TYPE: Both VARIABLES DESCRIPTION: The variable that will be returned to the calling application with either a error message or a unique message ID. If the call is successful (message sent), the Result parameter is returned with piece 1 equal to the message ID of the message created. If the call failed (message was not sent), the Result parameter is returned with the following three pieces of data: message ID(0 if none assigned)^error code^error description If the call failed, +$P(RESULT,U,2) returns True. VARIABLES: HLMTIEN TYPE: Input VARIABLES DESCRIPTION: Optional IEN of entry in Message Text file where the message being generated is to be stored. This parameter is only passed for a batch type message. VARIABLES: HLP TYPE: Input VARIABLES DESCRIPTION: The HLP parameter is passed-by-reference. The HLP subscripts that are processed by DIRECT^HLMA are identical to the GENERATE^HLMA HLP subscripts. These subscripts are listed below. o HLP("PRIORITY") = I for immediate or D for deferred o HLP("SECURITY") = A 1 to 40 character string o HLP("CONTPTR") = Continuation pointer, a 1 to 180 character string o HLP("NAMESPACE") = Free-text value, 4 character limit, stored that is to be stored in the NAMESPACE field (#16) in the HL Message Text file (#772.) o HLP("SUBSCRIBER") = Free-text, multi-piece value, used to control the routing-related fields in the MSH segment. See patch HL*1.6*93 documentation for full details. EDITOR: ANDREASSEN,LARRY NUMBER: 2165 IA #: 2165 DATE CREATED: OCT 30, 1997 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: HLMA1 NAME: HL7 MESSAGE ADMINISTRATION ORIGINAL NUMBER: 2161 ID: HLMA1 GENERAL DESCRIPTION: API to generate a HL7 acknowledgement message. STATUS: Active MAIL MESSAGE: 30719832 COMPONENT/ENTRY POINT: GENACK COMPONENT DESCRIPTION: GENACK(HLEID,HLMTIENS,HLEIDS,HLARYTYP,HLFORMAT,HLRESLTA,HLMTIENA,HLP) Entry point to generate a HL7 acknowledgement message. VARIABLES: HLEID TYPE: Input VARIABLES DESCRIPTION: IEN of the event driver protocol from the Protocol File (#101) VARIABLES: HLMTIENS TYPE: Input VARIABLES DESCRIPTION: IEN of entry in Message Text file for subscriber application. VARIABLES: HLEIDS TYPE: Input VARIABLES DESCRIPTION: IEN of subscriber event from the Protocol File (#101) VARIABLES: HLARYTYP TYPE: Input VARIABLES DESCRIPTION: Array type. One of the following codes: LM = local array containing a single message LB = local array containing a batch of messages GM = global array containing a single message. GB = global array containing a batch of messages. VARIABLES: HLFORMAT TYPE: Input VARIABLES DESCRIPTION: Format of array, 1 for pre-formatted in HL7 format, otherwise 0 VARIABLES: HLRESLTA TYPE: Both VARIABLES DESCRIPTION: Variable returned to the calling application either containing an error message or null if no error occurred. VARIABLES: HLMTIENA TYPE: Input VARIABLES DESCRIPTION: Optional variable of the IEN of the entry in Message Text file where the acknowledgement message will be stored. This is only passed for a batch acknowledgement. VARIABLES: HLP TYPE: Input VARIABLES DESCRIPTION: HLP("PRIORITY") = I for immediate or D for deferred HLP("SECURITY") = A 1 to 40 character string EDITOR: DIMICELI,RON EDITOR: ANDREASSEN,LARRY NUMBER: 2166 IA #: 2166 FILE NUMBER: 120.8 GLOBAL ROOT: GMR(120.8, DATE CREATED: MAR 10, 2006 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PATIENT ALLERGIES ORIGINAL NUMBER: 2161 ID: GMR(120.8, GLOBAL REFERENCE: GMR(120.8,'B',DFN, FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the patient to whom a allergy/adverse reaction pertains. By looping through the "B" cross-reference, any multiple allergies/ adverse reactions can be obtained. FIELD NUMBER: .02 FIELD NAME: REACTANT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the agent to which the patient has a reaction. GLOBAL DESCRIPTION: This global contains patient allergy/adverse reaction information. GLOBAL REFERENCE: GMR(120.8,D0,26,'AVER','E') FIELD NUMBER: 26 FIELD NAME: COMMENTS LOCATION: 26 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This global reference checks to see if an allergy/adverse reaction was entered in error. If this is an error entry, it will be ignored. GENERAL DESCRIPTION: The Baxter Sure-Med Pharmacy Interface needs to reference a patient's allergies to transmit via HL7 segment message. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 42621689 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 2167 IA #: 2167 FILE NUMBER: 120.83 GLOBAL ROOT: GMRD(120.83, DATE CREATED: OCT 30, 1997 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ALLERGY SIGN/SYMPTOMS ORIGINAL NUMBER: 2161 ID: GMRD(120.83, GLOBAL REFERENCE: GMRD(120.83,D0,0),U) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: A sign/symptom that can be associated with an allergy. GLOBAL DESCRIPTION: D0 is obtained as the first piece from the first piece of ^GMR(120.8,D0,10,D1,0). GENERAL DESCRIPTION: The Baxter Sure-Med Pharmacy Interface is requesting permission to retrieve the reaction for the HL7 AL1 segment message. It is currently an optional field. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25566732 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham NUMBER: 2171 IA #: 2171 DATE CREATED: OCT 07, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUAF4 NAME: DBIA2171 ID: XUAF4 GENERAL DESCRIPTION: Function API's to access parts of the Institution file. This DBIA documents some entry point for accessing the Institution file that were requested by the CIRN developers or implemented by the IFR project. STATUS: Active MAIL MESSAGE: 35734035 COMPONENT/ENTRY POINT: PARENT COMPONENT DESCRIPTION: PARENT^XUAF4(array,lookup[,type]) for a specified institution who is its VISN or parent. VARIABLES: array TYPE: Both VARIABLES DESCRIPTION: As a input it is the $NAME reference for the Array name you want results back in. As output it holds - array("p",ien)=station name ^ station number Note: with the business rule that institutions can only have one parent per type, if you specific the input variable type - you will get an array that will only have one pien in it. If the type variable is left blank, find all parents for the institution and list then in the array. VARIABLES: lookup TYPE: Input VARIABLES DESCRIPTION: Lookup value - either ien, station number, station name. If IEN it will have the ` in front of it. VARIABLES: type TYPE: Input VARIABLES DESCRIPTION: Type (optional) - type of institution from file 4.05 (in cirn case it is = visn) COMPONENT/ENTRY POINT: SIBLING COMPONENT DESCRIPTION: SIBLING^XUAF4(array,child [,type]) - all institutions in a specified institutions visn. VARIABLES: array TYPE: Both VARIABLES DESCRIPTION: As a input it is the $NAME reference for the Array name you want results back in. As the output array("p",pien,"c",cien)=station name ^ station number Note: with the business rule that institution can only have one parent per type, if you specific the input variable type - you will get an array that will only have one pien in it. If the type variable is left blank, find all parents for the institution and list then in the array. Also, the input site is included in the list VARIABLES: child TYPE: Input VARIABLES DESCRIPTION: Lookup value - either ien, station number, station name. If IEN it will have the ` in front of it. VARIABLES: type TYPE: Input VARIABLES DESCRIPTION: Type (optional) - type of institution from file 4.05 (in cirn case it is = visn) COMPONENT/ENTRY POINT: CHILDREN COMPONENT DESCRIPTION: CHILDREN^XUAF4(array,parent) - for a specified VISN return a list of all institutions that make up the VISN. VARIABLES: array TYPE: Both VARIABLES DESCRIPTION: Array - As a input it is the $NAME reference for the Array name you want results back in. Output Variable array ("c" , ien)=station name ^ station number VARIABLES: parent TYPE: Input VARIABLES DESCRIPTION: Parent - Lookup value either ien, station number, station name. If IEN it will have the ` in front of it. COMPONENT/ENTRY POINT: $$NNT COMPONENT DESCRIPTION: $$NNT^XUAF4(ien) - This will return the "station name ^ station number ^ station type" VARIABLES: ien TYPE: Input VARIABLES DESCRIPTION: ien is the pointer value to file 4. COMPONENT/ENTRY POINT: $$CIRN COMPONENT DESCRIPTION: $$CIRN^XUAF4(inst [,value]) - This function returns the value of the CIRN enabled field from the institution file. VARIABLES: inst TYPE: Input VARIABLES DESCRIPTION: inst - Lookup value either ien, station number, station name. If IEN it will have the ` in front of it. VARIABLES: value TYPE: Input VARIABLES DESCRIPTION: value - (optional) Restricted to use by CIRN. This allows the setting of the field to a new value. COMPONENT/ENTRY POINT: $$LKUP COMPONENT DESCRIPTION: $$LKUP^XUAF4(inst) - This function does a lookup on the Institution file and returns the IEN OR 0. VARIABLES: inst TYPE: Input VARIABLES DESCRIPTION: inst - Lookup value either ien, station number, station name. If IEN it will have the ` in front of it. COMPONENT/ENTRY POINT: $$NS COMPONENT DESCRIPTION: This extrinsic function returns a string with the institution name a "^" and the institution station number. The input is a valid IEN for the institution. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: The internal entry number for the institution that is requested. COMPONENT/ENTRY POINT: $$WHAT COMPONENT DESCRIPTION: This entry point returns the data from one field in the institution file. VARIABLES: ien TYPE: Input VARIABLES DESCRIPTION: ien is the pointer value to file 4. VARIABLES: field TYPE: Input VARIABLES DESCRIPTION: "field" is a single valued field in the file. Controls what data is returned. COMPONENT/ENTRY POINT: $$IEN COMPONENT DESCRIPTION: $$IEN^XUAF4(STA) - This function returns the Internal Entry Number (IEN) of the entry for a given STATION NUMBER (#99) in the INSTITUTION (#4) file. VARIABLES: STA TYPE: Input VARIABLES DESCRIPTION: Station number (required) COMPONENT/ENTRY POINT: $$STA COMPONENT DESCRIPTION: $$STA^XUAF4(IEN) - This function returns the STATION NUMBER (#99) of the INSTITUTION (#4) file entry for a given Internal Entry Number (IEN). This entry point will be available after patch XU*8*126. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal Entry Number (required) COMPONENT/ENTRY POINT: $$TF COMPONENT DESCRIPTION: This function returns the truth-value to the question is this an active treating medical facility? VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal Entry Number (required) VARIABLES: COMPONENT/ENTRY POINT: $$O99 COMPONENT DESCRIPTION: $$O99^XUAF4(IEN) - This function returns the Internal Entry Number of the valid INSTITUTION (#4) file entry with station number that this entry (input IEN) was merged with during the clean up. This function may be used by application developers to re-point their INSTITUTION (#4) file references to a valid entry complete with station number. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: The Internal Entry Number of the INSTITUTION (#4) file entry whose STATION NUMBER (#99) was deleted. VARIABLES: IEN TYPE: Output VARIABLES DESCRIPTION: The Internal Entry Number of the INSTITUTION (#4) file entry with a valid STATION NUMBER (#99) -- the station number deleted from the input IEN during the clean up process with patch XU*8.0*126. COMPONENT/ENTRY POINT: F4 COMPONENT DESCRIPTION: F4^XUFA4(STA,ARRAY,FLAG,DATE) - This API returns the INSTITUTION (#4) file Internal Entry Number and other data, including historical, for a given station number. VARIABLES: STA TYPE: Input VARIABLES DESCRIPTION: Station number (required) VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: The array for return values (required). VARIABLES: FLAG TYPE: Input VARIABLES DESCRIPTION: A = Active entries only (optional) M = Medical treating facilities only VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: Return name on this FM internal date (optional) VARIABLES: ARRAY TYPE: Output VARIABLES DESCRIPTION: ARRAY=IEN or '0^error message' ARRAY("NAME")=name ARRAY("VA NAME")=official VA name ARRAY("STATION NUMBER")=station number ARRAY("TYPE")=facility type name ARRAY("INACTIVE")=inactive FM internal date (0=not inactive) Note: if inactive date not available then 1 ARRAY("REALIGNED TO")='IEN^station number^date' ARRAY("REALIGNED FROM")='IEN^station number^date' ARRAY("MERGE",IEN)=merged records COMPONENT/ENTRY POINT: $$LEGACY COMPONENT DESCRIPTION: This function returns the truth value for a station number. Has this station number been realigned? (Is it a legacy station number.) VARIABLES: STA TYPE: Input VARIABLES DESCRIPTION: Station Number in question. COMPONENT/ENTRY POINT: $$NAME COMPONENT DESCRIPTION: This function returns the OFFICIAL NAME (#100) of an Institution given its Internal Entry Number. If field #100 is null, the #.01 field is returned. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal Entry Number COMPONENT/ENTRY POINT: $$ACTIVE COMPONENT DESCRIPTION: This function returns the truth value for the question -- is this an active facility? (The INACTIVE FACILITY FLAG #101 not set.) VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal Entry Number COMPONENT/ENTRY POINT: $$PADD COMPONENT DESCRIPTION: This function returns the physcial address information for an Institution in an up-arrow delimited string (street addr^city^state^zip) for a given Internal Entry Number. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal Entry Number COMPONENT/ENTRY POINT: $$MADD COMPONENT DESCRIPTION: This function returns the mailing address information for an Institution in an up-arrow delimited string (street addr^city^state^zip) for a given Internal Entry Number. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal Entry Number COMPONENT/ENTRY POINT: $$PRNT COMPONENT DESCRIPTION: This function returns the string "IEN^station_number^name" of the parent facility of a given child facility station number. VARIABLES: STA TYPE: Input VARIABLES DESCRIPTION: STA is station number of the child facility. COMPONENT/ENTRY POINT: LOOKUP COMPONENT DESCRIPTION: This utility prompts a user for a coding system and then prompts for an identifier -- its an IX^DIC call on a new style cross-reference of the ID (#.02) field of the IDENTIFIER (#9999) multiple of the INSTITUTION (#4) file. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: See FileMan IX^DIC documentation. COMPONENT/ENTRY POINT: $$IDX COMPONENT DESCRIPTION: This function returns the Internal Entry Number of an Institution file entry for a given coding sytem / ID pair. VARIABLES: CDSYS TYPE: Input VARIABLES DESCRIPTION: CDSYS is an existing CODING SYSTEM (#.01) in the INDENTIFIER (#9999) multiple of the INSTITUTION (#4) file. D CDSYS^XUAF4(.Y) to see existing coding systems in the file. VARIABLES: ID TYPE: Input VARIABLES DESCRIPTION: ID is the ID (#.02) in the INDENTIFIER (#9999) multiple of the INSTITUTION (#4) that corresponds to the coding system you input as the first parameter. VARIABLES: $$ TYPE: Output VARIABLES DESCRIPTION: Internal Entry Number COMPONENT/ENTRY POINT: CDSYS VARIABLES: Y TYPE: Both VARIABLES DESCRIPTION: Y -- pass by reference returns Y(coding_system) = $D_of_local_system ^ coding_system name COMPONENT/ENTRY POINT: $$ID COMPONENT DESCRIPTION: This function returns the ID of an Institution file entry for a given coding system / IEN. VARIABLES: CDSYS TYPE: Input VARIABLES DESCRIPTION: CDSYS is an existing CODING SYSTEM (#.01) in the INDENTIFIER (#9999) multiple of the INSTITUTION (#4) file. D CDSYS^XUAF4(.Y) to see existing coding systems in the file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal Entry Number VARIABLES: $$ID TYPE: Output VARIABLES DESCRIPTION: The ID (identifier) that is associated with the given coding system / IEN. COMPONENT/ENTRY POINT: $$BNSTA COMPONENT DESCRIPTION: This function returns the billing facility name for a given station number. VARIABLES: STA TYPE: Input VARIABLES DESCRIPTION: Station Number COMPONENT/ENTRY POINT: $$BNIEN COMPONENT DESCRIPTION: This function returns the billing facility name for a given IEN. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal Entry Number NUMBER: 2172 IA #: 2172 DATE CREATED: OCT 08, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XPDID NAME: DBIA2172 ID: XPDID GENERAL DESCRIPTION: The routine XPDID contains calls to support the Kernel Installation and Distribution System. All of the calls can only be used in the context of the KIDS software. INIT This tag initializes the screen and draws the borders for the box and draws the progress bar. It also creates a scrolling region in the box. INPUT: none OUTPUT: XPDIDVT=1 if output device supports graphics, =0 if not TITLE(text) This tag displays the text as a title at the top of the box. INPUT: text OUTPUT: none EXIT(text) This tag restore the screen to normal, cleans up all variables, and displays the text. INPUT: text OUTPUT: none UPDATE(current number of items) This tag updates the progress bar to show the percentage complete of the installation. INPUT: current number of items XPDIDTOT = total number of items For example, if you are converting 100 records and want to update the user every time you have completed 10% of the records you would do the following: Set XPDIDTOT=100 F%=1:1:100 D CONVERT I'(%#10) D UPDATE^XPDID(%) STATUS: Active MAIL MESSAGE: 25250355 COMPONENT/ENTRY POINT: UPDATE(N) COMPONENT DESCRIPTION: Update the progress bar by N, current number of items. VARIABLES: XPDIDTOT TYPE: Input VARIABLES DESCRIPTION: This is the total number of items that is being updated. VARIABLES: N TYPE: Input VARIABLES DESCRIPTION: The current number of items being updated. COMPONENT/ENTRY POINT: TITLE(X) COMPONENT DESCRIPTION: Display the text, X, as a title at the top of the box. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: This is the text you want to display COMPONENT/ENTRY POINT: INIT COMPONENT DESCRIPTION: Initializes the device and draws the borders for the box and draws the progress bar. COMPONENT/ENTRY POINT: EXIT(X) COMPONENT DESCRIPTION: Restores the screen to normal, cleans up all variables, and displays the text in the variable X. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Text to display on screen after removing box and progress bar. NUMBER: 2173 IA #: 2173 FILE NUMBER: 52.7 GLOBAL ROOT: PS(52.7 DATE CREATED: OCT 14, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2173 ID: PS(52.7 GENERAL DESCRIPTION: This file was previously in Inpatient Meds versions up to 5.0. Now it has moved to Pharmacy Data Management 1.0. It is used extensively throughout our routines. With this move, we are requesting read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25249397 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: NATIONAL DRUG FILE ISC: Birmingham NUMBER: 2174 IA #: 2174 FILE NUMBER: 50.606 GLOBAL ROOT: PS(50.606 DATE CREATED: OCT 14, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2174 ID: PS(50.606 GENERAL DESCRIPTION: Inpatient Medications request permission to look at DOSAGE FORM file 50.606. This file was previously in National Drug File. Now it has moved to Pharmacy Data Management 1.0. It is used extensively throughout our routines. With this move, we are requesting read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25249427 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: NATIONAL DRUG FILE ISC: Birmingham SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2175 IA #: 2175 FILE NUMBER: 50.4 GLOBAL ROOT: PS(50.4 DATE CREATED: OCT 14, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2175 ID: PS(50.4 GENERAL DESCRIPTION: Inpatient Medications requests permission to look at DRUG ELECTROLYTES file 50.4. This file was previously in Inpatient Meds versions up to 5.0. Now it has moved to Pharmacy Data Management 1.0. It is used extensively throughout our routines. With this move, we are requesting read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25249453 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2176 IA #: 2176 FILE NUMBER: 51 GLOBAL ROOT: PS(51 DATE CREATED: OCT 14, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2176 ID: PS(51 GENERAL DESCRIPTION: Inpatient Medications request permission to look at MEDICATION INSTRUCTION file 51. This file was previously in Inpatient Meds versions up to 5.0. Now it has moved to Pharmacy Data Management 1.0. It is used extensively throughout our routines. With this move, we are requesting read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25249476 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2177 IA #: 2177 FILE NUMBER: 51.1 GLOBAL ROOT: PS(51.1 DATE CREATED: OCT 14, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2177 ID: PS(51.1 GENERAL DESCRIPTION: Inpatient Medications requests permission to look at ADMINISTRATION SCHEDULE file 51.1. This file was previously in Inpatient Meds versions up to 5.0. Now it has moved to Pharmacy Data Management 1.0. It is used extensively throughout our routines. With this move, we are requesting read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25249495 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2178 IA #: 2178 FILE NUMBER: 51.2 GLOBAL ROOT: PS(51.2 DATE CREATED: OCT 14, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2178 ID: PS(51.2 GENERAL DESCRIPTION: Inpatient Medications request permission to look at MEDICATION ROUTES file 51.2. This file was previously in Inpatient Meds versions up to 5.0. Now it has moved to Pharmacy Data Management 1.0. It is used extensively throughout our routines. With this move, we are requesting read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25249509 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: NATIONAL DRUG FILE ISC: Birmingham NUMBER: 2179 IA #: 2179 FILE NUMBER: 9009032.4 GLOBAL ROOT: APSPQA(32.4 DATE CREATED: OCT 14, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2179 ID: APSPQA(32.4 GLOBAL REFERENCE: APSPQA(32.4,D0,0) FIELD NUMBER: .01 FIELD NAME: INTERVENTION DATE LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: PATIENT LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .04 FIELD NAME: PHARMACIST LOCATION: 0;4 ACCESS: Both R/W w/Fileman FIELD NUMBER: .05 FIELD NAME: DRUG LOCATION: 0;5 ACCESS: Both R/W w/Fileman FIELD NUMBER: .06 FIELD NAME: INTERVENTION LOCATION: 0;7 ACCESS: Both R/W w/Fileman FIELD NUMBER: .08 FIELD NAME: RECOMMENDATION LOCATION: 0;8 ACCESS: Both R/W w/Fileman FIELD NUMBER: .14 FIELD NAME: ORIGINATING PACKAGE LOCATION: 0;14 ACCESS: Both R/W w/Fileman FIELD NUMBER: .15 FIELD NAME: RX # LOCATION: 0;15 ACCESS: Both R/W w/Fileman FIELD NUMBER: .03 FIELD NAME: PROVIDER LOCATION: 0;3 ACCESS: Direct Global R/W & w/Fileman GENERAL DESCRIPTION: Inpatient Medications requests permission to look at APSP INTERVENTION file 9009032.4. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25249522 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2180 IA #: 2180 FILE NUMBER: 50.7 GLOBAL ROOT: PS(50.7 DATE CREATED: OCT 14, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2180 ID: PS(50.7 GENERAL DESCRIPTION: Inpatient Medications request permission to look at PHARMACY ORDERABLE ITEM file 50.7. This is a new file with Pharmacy Data Management v1.0. It is used extensively throughout our routines. We are requesting read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25249535 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: NATIONAL DRUG FILE ISC: Birmingham SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING DETAILS: ADDED 8/28/09 DATE/TIME EDITED: AUG 28, 2009@10:54 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SILVERMAN,ROBERT WITH CONCURRENCE OF: FAIN,ZACHARY NUMBER: 2181 IA #: 2181 FILE NUMBER: 59.7 GLOBAL ROOT: PS(59.7 DATE CREATED: OCT 15, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2181 ID: PS(59.7 GENERAL DESCRIPTION: Inpatient Medications requests permission to look at the following fields in the PHARMACY SYSTEM file 59.7. FIELD NUMBER NAME NODE AND PIECE 59.7,20.01 IV STATS/200 CONVERSION STATUS 20;10 59.7,20.1 VERSION NUMBER LAST INITS RUN 20;1 59.7,20.11 NEW PERSON CONVERSION DATE 20;11 59.7,20.12 PRIMARY DRUG CONVERSION DATE 20;12 59.7,20.13 DATE V4 PRE-PACKET INSTALLED 20;13 59.7,20.14 LAST N-V ORDER CONVERTED TO V4 20;14 59.7,20.15 DATE NON-VERIFIED CONVERTED 20;15 59.7,20.16 ORDERABLE ITEM CONVERSION DATE 20;16 59.7,20.2 DATE INITS LAST RUN 20;2 59.7,20.3 USER TO LAST RUN INITS 20;3 59.7,20.4 SITE FOR BACKGROUND JOB 20;4 59.7,20.401 UD STATS/200 CONVERSION MARKER 20.4;1 59.7,20.402 IV STATS/200 CONVERSION STATUS 20.4;2 59.7,20.403 NEW PERSON CONVERSION DATE 20.4;3 59.7,20.404 LAST N-V ORDER CONVERTED TO V4 20.4;4 59.7,20.405 DATE NON-VERIFIED CONVERTED 20.4;5 59.7,20.406 LAST PAT CONVERTED FOR VER 4 20.4;6 59.7,20.407 LAST PICK LIST TO PD MARKER 20.4;7 59.7,20.408 DATE PICK LISTS CONVERT TO PD 20.4;8 59.7,20.409 ORDER SET CONVERSION MARKER 20.4;9 59.7,20.41 ORDER SET CONVERSION DATE 20.4;10 59.7,20.411 DATE UD STATS FILE CONVERTED 20.4;11 59.7,20.5 DATE ATC DATA CONVERTED 20;5 59.7,20.6 DEFAULT WARD 20;6 59.7,20.8 LAST PATIENT CONVERTED TO V4 20;8 59.7,20.9 UD STATS/200 CONVERSION STATUS 20;9 59.7,21 NON-FORMULARY MESSAGE 21;0 59.7,22 WARD ACTIONS 22;0 59.722,.01 FROM WARD 0;1 59.722,1 TO WARD 1;0 59.7221,.01 TO WARD 0;1 59.722,2 'ON PASS' ACTION 0;2 59.722,3 ACTION ON AUTHORIZED ABSENCE 0;3 59.722,4 ACTION ON UNAUTHORIZED ABSENCE 0;4 59.7,23 D/C ON SERVICE TRANSFER 23;0 59.723,.01 FROM SERVICE 0;1 59.723,1 TO SERVICE 1;0 59.7231,.01 TO SERVICE 0;1 59.7,25 INPATIENT ORDER NUMBER 25;E1,245 59.7,25.1 DATE 5.0 UD VER CONV FINISHED 20.5;1 59.7,25.2 DATE 5.0 CONVERSION COMPLETED 20.5;2 59.7,25.3 DATE 5.0 PICK LIST CONV FINISH 20.5;3 59.7,25.4 DATE 5.0 ORDER SET CONV FINISH 20.5;4 59.7,26 PRINT 6 BLOCKS FOR THE PRN MAR 26;1 59.7,26.2 ATC SORT PARAMETER 26;2 59.7,26.3 PRINT DIET ABBR LABEL ON MAR 26;3 59.7,26.4 MAR SORT 26;4 59.7,26.5 CALC UNITS NEEDED PRN ORDERS 26;5 59.7,26.6 DAYS UNTIL STOP FOR ONE-TIME 26;6 59.7,26.7 ROUND ATC PICK LIST UNITS 26;7 59.7,26.8 EFD SCHEDULE 26;8 59.7,30.1 DATE IV ORDERS CONVERTED 30;1 59.7,30.2 LAST PATIENT CONVERTED (IV) 30;2 59.7,31 DAYS TO RETAIN IV STATISTICS 31;1 59.7,32 IV IDENTIFIER 31;2 59.7,34 EXPIRED IV TIME LIMIT 31;4 59.7,60.02 LAST PAT CONVERTED FOR VER 4 60;2 59.7,61.2 DAYS NEW LABELS LAST 61;2 59.7,63.51 PICK LIST AUTO-PURGE 63.5;1 59.7,63.52 DATE/TIME AUTO-PURGE EDITED 63.5;2 59.7,63.53 USER LAST EDITING AUTO-PURGE 63.5;3 59.7,63.54 DATE PICK LIST LAST FILED AWAY 63.5;4 59.7,64 PARAM FILE CONVERSION STATUS 20.4;12 59.7,65 PICK LIST CONVERSION DATE 20.4;13 59.7,66 V4.5 PICK LIST CONVERT MARKER 20.4;14 59.7,67 V4.5 PICK LIST CONVERT STATUS 20.4;15 59.7,80 PSS VERSION 80;1 59.7,81 ORDERABLE ITEM STATUS TRACKER 80;2 Use of input template PSJ OAOPT is also requested. GLOBAL MAP DATA DICTIONARY #59.7 -- PHARMACY SYSTEM FILE 10/17/97 STORED IN ^PS(59.7, (1 ENTRY) SITE: SALT LAKE ISC UCI: OEX,OER -------------------------------------------------------------------------- This file contains data that pertains to the entire Pharmacy system of a medical center, and not to any one site or division. The number ranges for the nodes and field numbers are as follows: 0 - 9.99 RESERVED 10 - 19.99 National Drug File 20 - 29.99 Inpatient 30 - 39.99 IV's 40 - 49.99 Outpatient 50 - 59.99 Ward Stock/AR 60 - 69.99 Unit Dose 70 - 79.99 Drug Accountability 80 - 89.99 Pharmacy Data Management STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25256666 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2182 IA #: 2182 DATE CREATED: JAN 14, 1998 CUSTODIAL PACKAGE: CLINICAL REMINDERS CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRM NAME: CLINICAL REMINDERS APIs ID: PXRM CREATOR: REDINGTON,PATRICK STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25279962 KEYWORDS: CLINICAL REMINDERS COMPONENT/ENTRY POINT: MAIN(DFN,PXRMITEM,OUTTYPE,DISC) COMPONENT DESCRIPTION: This is the standard entry point for reminder evaluation. The current date and time are used for the evaluation date and time. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient file (#2) VARIABLES: PXRMITEM TYPE: Input VARIABLES DESCRIPTION: Internal entry number of Clinical Reminder definition (file #811.9) VARIABLES: OUTTYPE TYPE: Input VARIABLES DESCRIPTION: This is the type of output to return. The possible values are: 0 - Reminders DUE NOW only (CLINICAL REMINDERS DUE HS component) 1 - All Reminders with Next and Last Information (CLINICAL REMINDERS SUMMARY HS component) 5 - Health Maintenance (CLINICAL REMINDERS MAINTENANCE HS component) 10 - MyHealtheVet summary 11 - MyHealtheVet detailed 12 - MyHealtheVet combined VARIABLES: DISC TYPE: Input VARIABLES DESCRIPTION: (optional) If this variable is true then the disclaimer will be loaded in ^TMP("PXRM",$J,"DISC") VARIABLES: TMP TYPE: Output VARIABLES DESCRIPTION: The results of the reminder evaluation are returned in ^TMP("PXRHM",$J,PXRMITEM,PXRMRNAM) where PXRMRNAM is the PRINT NAME or if it is undefined then it is the NAME. The format is: ^TMP("PXRHM",$J,PXRMITEM,PXRMRNAM)=STATUS^DUE DATE^LAST D0NE DATE and ^TMP("PXRHM",$J,PXRMITEM,PXRMRNAM,"TXT",N)=TEXT where N is a number and TEXT is a text string. The text returned depends on the output type (OUTTYPE) and the results of the reminder evaluation. If DISC is true then the disclaimer will be loaded into ^TMP("PXRM",$J,"DISC"). It contains the disclaimer. The caller should kill both ^TMP("PXRHM",$J) and ^TMP("PXRM",$J) after display of the data is complete. COMPONENT/ENTRY POINT: FIDATA(DFN,PXRMITEM,.FINDINGS) COMPONENT DESCRIPTION: Return the finding evaluation array to the caller in the array FINDINGS. The caller should use the form: D FIDATA^PXRM(DFN,PXRMITEM,.FINDINGS) The elements of the FINDINGS array will correspond to the findings in the reminder definition. For finding N, FINDINGS(N) will be 0 if the finding is false and 1 if it is true. For true findings there will be additional elements. The exact set of additional elements will depend on the type of finding. Some examples are: FINDINGS(N)=1 FINDINGS(N,"DATE")=FileMan date FINDINGS(N,"FINDING")=variable pointer to the finding FINDINGS(N,"SOURCE")=variable pointer to the data source FINDINGS(N,"VALUE")=value of the finding, for example the value of a lab test COMPONENT/ENTRY POINT: $$INACTIVE(PXRMITEM) VARIABLES: $$INACTIVE(PXRMITEM) TYPE: Output VARIABLES DESCRIPTION: Return the INACTIVE FLAG 1 - reminder is inactive 0 - reminder is active COMPONENT/ENTRY POINT: MAINDF(DFN,PXRMITEM,OUTTYPE,EVALDT) COMPONENT DESCRIPTION: This entry point is used for reminder evaluation. The date and time to use for the evaluation is an input parameter. The finding evaluation array is returned in ^TMP("PXRHM",$J,PXRMITEM,PXRMRNAM). See below for details. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient file (#2) VARIABLES: PXRMITEM TYPE: Input VARIABLES DESCRIPTION: Internal entry number of Clinical Reminder definition (file #811.9) VARIABLES: OUTTYPE TYPE: Input VARIABLES DESCRIPTION: This is the type of output to return. The possible values are: 0 - Reminders DUE NOW only (CLINICAL REMINDERS DUE HS component) 1 - All Reminders with Next and Last Information (CLINICAL REMINDERS SUMMARY HS component) 5 - Health Maintenance (CLINICAL REMINDERS MAINTENANCE HS component) 10 - MyHealtheVet summary 11 - MyHealtheVet detailed 12 - MyHealtheVet combined VARIABLES: EVALDT TYPE: Input VARIABLES DESCRIPTION: This is the FileMan date and time to use for the reminder evaluation. VARIABLES: TMP TYPE: Output VARIABLES DESCRIPTION: The results of the reminder evaluation are returned in ^TMP("PXRHM",$J,PXRMITEM,PXRMRNAM) where PXRMRNAM is the PRINT NAME or if it is undefined then it is the NAME. The format is: ^TMP("PXRHM",$J,PXRMITEM,PXRMRNAM)=STATUS^DUE DATE^LAST DONE DATE and ^TMP("PXRHM",$J,PXRMITEM,PXRMRNAM,"TXT",N)=TEXT where N is a number and TEXT is a text string. The text returned depends on the output type (OUTTYPE) and the results of the reminder evaluation. The finding evaluation array (FIEVAL) is returned in: ^TMP("PXRHM",$J,"PXRMITEM,"FIEVAL") A description of the contents of FIEVAL can be found in the Clinical Reminders Managers Manual. The caller should kill both ^TMP("PXRHM",$J) and ^TMP("PXRM",$J) after display of the data is complete. SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: JSH/ Edited Component MAIN & Variable NODISC to turn NODISC into DISC as per P. Redington DLT/ P. Redington needed access to add a new label entry point to this ICR. 06/26/12 DLT - Activated after MAINDF component added. Note INACTIVE was removed because it doesn't exist in the code. 10/1/14-MC: Added VPS as a subscriber at the request of Carolyn Wheless and approved by Pat Redington for patch VPS*1*4. DATE ACTIVATED: JUN 27, 2012 DATE/TIME EDITED: NOV 03, 2006@16:00 ACTION: CONTENT CORRECTED AT THE REQUEST OF: REDINGTON,PATRICK WITH CONCURRENCE OF: HARVEY,JULIE DATE/TIME EDITED: JUN 20, 2012@10:42 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: REDINGTON,PATRICK WITH CONCURRENCE OF: FERRARESE,MARYANN DATE/TIME EDITED: JUN 27, 2012@10:37 ACTION: APPROVED AT THE REQUEST OF: REDINGTON,PATRICK WITH CONCURRENCE OF: FERRARSE,MARYANN NUMBER: 2184 IA #: 2184 DATE CREATED: OCT 15, 1997 CUSTODIAL PACKAGE: DRG GROUPER CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2184 GENERAL DESCRIPTION: Clinical Reminders use the application group PXRS for screening taxonomy selections. The following files need to belong to this application group: File 80 - ICD DIAGNOSIS, File 80.1 - ICD OPERATION/PROCEDURE File 81 - CPT STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25279972 SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 2185 IA #: 2185 DATE CREATED: OCT 16, 1997 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORCONV3 NAME: DBIA2185 ID: ORCONV3 GENERAL DESCRIPTION: Inpatient Medications requests permission to call PSJQOS^ORCONV3. This entry point passes Unit Dose Order Set information to OERR to allow the creation of Quick orders from each Order Set. Inpatient Meds receives no output from this call. The data passed is described below. ^TMP("PSJQOS",$J,"NM")=ORDER SET NAME ^TMP("PSJQOS",$J,#,1)=ORDERABLE ITEM IEN^MED ROUTE IEN^ SCHEDULE ^DOSAGE ORDERED ^TMP("PSJQOS",$J,#,2)=SPECIAL INSTRUCTIONS ^TMP("PSJQOS",$J,#,3)=DISPENSE DRUG IEN^UNITS PER DOSE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25266746 COMPONENT/ENTRY POINT: PSJQOS SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2186 IA #: 2186 DATE CREATED: OCT 16, 1997 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORX1 NAME: DBIA2186 ID: ORX1 GENERAL DESCRIPTION: This routine has a number of supported entry points to support package interfaces with CPRS. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25267674 COMPONENT/ENTRY POINT: $$NA(DEFAULT,REQUIRD,FB,DIRA,DC,LIST) COMPONENT DESCRIPTION: This is a function that will prompt for and return a Nature of Order from the Nature of Order file. VARIABLES: DEFAULT TYPE: Input VARIABLES DESCRIPTION: Free text code or pointer value to the nature of order in file 100.02 VARIABLES: REQUIRD TYPE: Input VARIABLES DESCRIPTION: Set to 1 to require a response from the user. VARIABLES: FB TYPE: Input VARIABLES DESCRIPTION: Used to screen selection by type (frontdoor or backdoor types). VARIABLES: DIRA TYPE: Input VARIABLES DESCRIPTION: Prompt used to set DIR("A") in call to ^DIR VARIABLES: DC TYPE: Input VARIABLES DESCRIPTION: Set to 1 if you only want to include DC types. VARIABLES: LIST TYPE: Input VARIABLES DESCRIPTION: List of nature of order codes allowed (from file 100.02). If this is passed then DC and FB parameters are ignored. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Y represents the value returned by the function. It is in the form: pointer^name^code COMPONENT/ENTRY POINT: NA1(SCREEN) COMPONENT DESCRIPTION: This is a call to get a standard help matrix for Nature of Order. VARIABLES: SCREEN TYPE: Input VARIABLES DESCRIPTION: Used like DIC("S") to screen out entries. COMPONENT/ENTRY POINT: NA2(SCREEN) COMPONENT DESCRIPTION: This is a call to get a standard help matrix for DC Reason. VARIABLES: SCREEN TYPE: Input VARIABLES DESCRIPTION: Used like DIC("S") to screen out entries. COMPONENT/ENTRY POINT: $$DC(DEFAULT,REQ,PKG,DIRA) COMPONENT DESCRIPTION: Function to prompt for and get a DC Reason from the Order Reason (100.03) file. VARIABLES: DEFAULT TYPE: Input VARIABLES DESCRIPTION: Internal # from ORDER REASON (100.03) file to use as default. VARIABLES: REQ TYPE: Input VARIABLES DESCRIPTION: Set to 1 to require a response. VARIABLES: PKG TYPE: Input VARIABLES DESCRIPTION: Pointer to file 9.4 (Package) to screen selection to package specific reasons. VARIABLES: DIRA TYPE: Input VARIABLES DESCRIPTION: Default prompt used to set DIR("A") when calling ^DIR. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Y represents the value returned by this function. It is in the form: pointer^name EDITOR: BAYLIS,RANDALL S NUMBER: 2187 IA #: 2187 DATE CREATED: OCT 16, 1997 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORERR NAME: DBIA2187 ID: ORERR GENERAL DESCRIPTION: This is a supported entry point for use by packages interfacing with CPRS. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25268571 COMPONENT/ENTRY POINT: EN(ORTYP,ORMSG,ORVAR) COMPONENT DESCRIPTION: This call will log an error/problem in the OE/RR Errors (100.4) file. It is used by OE/RR and interfacing packages to identify potential problems. VARIABLES: ORTYP TYPE: Input VARIABLES DESCRIPTION: Text to identify problem. VARIABLES: ORMSG TYPE: Input VARIABLES DESCRIPTION: HL7 message array. VARIABLES: ORVAR TYPE: Input VARIABLES DESCRIPTION: ORVAR is an array with a list of variable names as subscripts that you need saved when ORERR is called. NUMBER: 2188 IA #: 2188 DATE CREATED: OCT 16, 1997 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOHLNEW NAME: DBIA2188 ID: PSOHLNEW GENERAL DESCRIPTION: Inpatient Medications requests permission to call (Outpatient Pharmacy) EN^PSOHLNEW. This entry point allows the order message array from OERR to be passed to Outpatient Pharmacy for processing. All message arrays from OERR come through the Inpatient Meds routine. The PATIENT CLASS field comes in the array from OERR. If the value is "I", it is processed as an Inpatient Order. If the value is "O" this call is made to process the order as an Outpatient order. Variables are described below. Input: EN^PSOHLNEW(.MSG) MSG - The message array from OERR. Output: none STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25272295 COMPONENT/ENTRY POINT: EN SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2189 IA #: 2189 DATE CREATED: OCT 17, 1997 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSODRDU2 NAME: DBIA2189 ID: PSODRDU2 GENERAL DESCRIPTION: Inpatient Medications request permission to call (Outpatient Pharmacy) EN^PSODRDU2. If the inpatient has a drug-drug interaction, drug class, or duplicate drug with an outpatient order with call is made. The call displays the outpatient order's information. The call occurs during the inpatient order entry. Variables are described below. Input: EN^PSODRDU2(DFN,RXNUM) DFN - Patient's internal entry number is ^DPT. RXNUM - P1_P2_;_P3 where P1= Order number P2= Order Type, either "P" for pending or "R" for active RX P3= Pharmacy package code, either "I" or "O" Output: none STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25298289 COMPONENT/ENTRY POINT: EN SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2190 IA #: 2190 DATE CREATED: OCT 21, 1997 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOORDRG NAME: DBIA2190 ID: PSOORDRG GENERAL DESCRIPTION: Inpatient Medications request permission to call (Outpatient Pharmacy) ^PSOORDRG. This call returns drug-drug order checks. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25300324 COMPONENT/ENTRY POINT: EN(PSODFN,DREN) COMPONENT DESCRIPTION: This call returns drug-drug order checks. VARIABLES: PSODFN TYPE: Input VARIABLES DESCRIPTION: Patient's internal entry number in ^DPT. VARIABLES: DREN TYPE: Input VARIABLES DESCRIPTION: Drug internal entry number in ^PSDRUG (#50) VARIABLES: DRUG INTERACTION NODE TYPE: Output VARIABLES DESCRIPTION: ^TMP($J,"DI",n,0) = Interacting Drug IEN^Interacting Drug Name^Interaction Ptr (file #56)^severity (CRITICAL or SIGNIFICANT) ^Ingredient #1 (ptr to file #50.416) ^Ingredient #2 (ptr to file #50.416)^OERR IEN^ORDER #;TYPE^PKG (I or O) VARIABLES: DRUG CLASS NODE TYPE: Output VARIABLES DESCRIPTION: ^TMP($J,"DC",n,0) = VA Drug Class Name^Generic Drug Name (file #50)^Drug File (#50) IEN)^OERR IEN^ORDER # ;TYPE^PKG (I or O) VARIABLES: DUPLICATE DRUG NODE TYPE: Output VARIABLES DESCRIPTION: ^TMP($J,"DD",n,0) = Duplicate drug IEN (file #50)^Duplicate Drug Name)^OERR IEN^ORDER #;TYPE^PKG (I or O) COMPONENT/ENTRY POINT: DRGCHK SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City EDITOR: INSLEY,MARCIA NUMBER: 2191 IA #: 2191 FILE NUMBER: 55 GLOBAL ROOT: PS(55 DATE CREATED: OCT 21, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2191 ID: PS(55 GENERAL DESCRIPTION: This file is used extensively throughout our routines. We request read and write access to the entire file and cross-references via FileMan utilities and direct writes/reads. The fields we use are listed below. The UNIT DOSE multiple and IV multiple represent the majority of the fields in the file. Because they are so numerous, we would like full access to the file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25308425 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: NATIONAL DRUG FILE NUMBER: 2192 IA #: 2192 FILE NUMBER: 50 GLOBAL ROOT: PSDRUG( DATE CREATED: OCT 21, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2192 ID: PSDRUG( GENERAL DESCRIPTION: This file was previously under Outpatient Pharmacy. Now, Pharmacy Data Management 1.0 sends it out. This file is used extensively throughout our routines. We use a majority of the fields in this file. We request read and write access to the entire file, cross-references and templates via FileMan utilities and direct writes/reads. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25310201 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: NATIONAL DRUG FILE NUMBER: 2195 IA #: 2195 FILE NUMBER: 50.6 GLOBAL ROOT: PSNDF(50.6, DATE CREATED: OCT 22, 1997 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2195 ID: PSNDF(50.6, GLOBAL REFERENCE: PSNDF(D0,0) FIELD NUMBER: .01 FIELD NAME: VA GENERIC NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSNDF(D0,2,D1,0) FIELD NUMBER: .01 FIELD NAME: DOSAGE FORM LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: ROUTE OF ADMINISTRATION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: VA DRUG CLASSIFICATION LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSNDF(D0,5,D1,0) FIELD NUMBER: .01 FIELD NAME: VA PRODUCT NAMES LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: DOSAGE FORM ENTRY LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: STRENGTH ENTRY LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: UNITS ENTRY LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 11 FIELD NAME: PPI LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 12 FIELD NAME: USP GENERIC LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSNDF(D0,5,D1,1) FIELD NUMBER: 4 FIELD NAME: INGREDIENT ENTRY#1 LOCATION: 1;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSNDF(D0,5,D1,2) FIELD NUMBER: 5 FIELD NAME: VA PRINT NAME LOCATION: 2,1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6 FIELD NAME: VA PRODUCT IDENTIFIER LOCATION: 2,2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7 FIELD NAME: TRANSMIT TO CMOP LOCATION: 2,3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 8 FIELD NAME: VA DISPENSE UNIT LOCATION: 2,4 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSNDF(D0,5,D1,3) FIELD NUMBER: 9 FIELD NAME: INGREDIENT ENTRY#2 LOCATION: 3;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSNDF(D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: INGREDIENTS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSNDF(D0,2,D1,3,D2,4,D3,0) FIELD NUMBER: .01 FIELD NAME: UNITS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSNDF(D0,2,D1,3,D2,0) FIELD NUMBER: .01 FIELD NAME: STRENGTH LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Inpatient Medications requests access to file 50.6 NATIONAL DRUG. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25317087 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2196 IA #: 2196 FILE NUMBER: 50.416 GLOBAL ROOT: PS(50.416 DATE CREATED: OCT 22, 1997 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2196 ID: PS(50.416 GLOBAL REFERENCE: PS(50.416,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Also Direct Global Read to the 'B' cross-reference. GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSN*4*94. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of June 1, 2006. Inpatient Medications requests access to file 50.416, DRUG INGREDIENTS. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 25317293 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING EDITOR: RUZBACKI,RON T NUMBER: 2197 IA #: 2197 FILE NUMBER: 9.7 GLOBAL ROOT: XPD(9.7, DATE CREATED: OCT 25, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: CPRS needs Install Start Time ID: XPD(9.7, GLOBAL REFERENCE: XPD(9.7,'B' GLOBAL DESCRIPTION: Would like to use the B x-ref to pull the IEN of the INSTALL file entry for the first build in the series. GLOBAL REFERENCE: XPD(9.7,IEN,1) FIELD NUMBER: 11 FIELD NAME: INSTALL START TIME LOCATION: 1;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Uses IEN obtained by B index to get the INSTALL START TIME for the first build in the series. This is used to determine the overall installation start time. GENERAL DESCRIPTION: Currently, the only way to get the start and completion date of an install is to get the IEN of the build and reference the fields directly. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25347177 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING PACKAGE: MASTER PATIENT INDEX SUBSCRIBING DETAILS: ADDED 3/12/09 DATE/TIME EDITED: MAR 12, 2009@09:07 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MANISPAL,DANILA NUMBER: 2198 IA #: 2198 DATE CREATED: NOV 19, 1997 CUSTODIAL PACKAGE: RPC BROKER CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XWBLIB NAME: TEST FOR BROKER CONTEXT ID: XWBLIB GENERAL DESCRIPTION: Use this function in the M code called by an RPC to determine if the current process is being executed by the Broker. STATUS: Active MAIL MESSAGE: 24832423 COMPONENT/ENTRY POINT: $$BROKER() COMPONENT DESCRIPTION: Format $$BROKER^XWBLIB Input (none) Output Return Value 1 if the current process is being executed by the Broker; 0 if not. Example I $$BROKER^XWBLIB D .; broker-specific code NUMBER: 2199 IA #: 2199 FILE NUMBER: 550 GLOBAL ROOT: PSX(550 DATE CREATED: OCT 27, 1997 CUSTODIAL PACKAGE: CMOP CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: CPRS checks for CMOP activation ID: PSX(550 GLOBAL REFERENCE: PSX(550,'C') GENERAL DESCRIPTION: CPRS checks to see whether CMOP is activated or not to determine whether to default meds for mail or window pick-up. The installation of CPRS also makes a check to ensure that CMOP is inactivated prior to installation. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30449301 GOOD ONLY FOR VERSION: OE/RR 3.0 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2200 IA #: 2200 DATE CREATED: OCT 28, 1997 CUSTODIAL PACKAGE: CMOP CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSXOPUTL NAME: DBIA2200 ID: PSXOPUTL GENERAL DESCRIPTION: The Outpatient Pharmacy package makes a call to the CMOP routine, PSXOPUTL to get CMOP data from the pharmacy files. This data is used when displaying the Rx profile to the screen. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25301046 COMPONENT/ENTRY POINT: PSXOPUTL VARIABLES: PSXZ TYPE: Output VARIABLES DESCRIPTION: This variable passes the value in the CMOP Indicator field (#3) of the Rx Suspense file (#52.5). SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2201 IA #: 2201 DATE CREATED: OCT 28, 1997 CUSTODIAL PACKAGE: CMOP CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSXSRP NAME: DBIA2201 ID: PSXSRP GENERAL DESCRIPTION: The Outpatient Pharmacy routine, PSOLBL, calls the CMOP routine, PSXSRP to make the activity log entry in the Prescription file (#52) when labels are reprinted using the Outpatient Pharmacy option Reprint Batches from Suspense [PSO PNDRPT]. This call doesn't pass variables. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25301106 COMPONENT/ENTRY POINT: AREC SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2203 IA #: 2203 DATE CREATED: OCT 28, 1997 CUSTODIAL PACKAGE: CMOP CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSXOPUTL NAME: DBIA2203 ID: PSXOPUTL GENERAL DESCRIPTION: The Outpatient Pharmacy routine, PSOORUT1, calls the CMOP routine, PSXOPUTL, to get CMOP data from the Outpatient Pharmacy and CMOP files. This data is used by the OERR interface. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25301214 COMPONENT/ENTRY POINT: PSXOPUTL VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number of the record in the Rx Suspense file (#52.5). VARIABLES: PSXZ TYPE: Output VARIABLES DESCRIPTION: This stores the value of the CMOP Indicator field (#3) in the Rx Suspense file (#52.5). SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2204 IA #: 2204 DATE CREATED: OCT 28, 1997 CUSTODIAL PACKAGE: CMOP CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSXVIEW NAME: DBIA2204 ID: PSXVIEW GENERAL DESCRIPTION: The Outpatient Pharmacy routine, PSORXPR, calls the CMOP routine, PSXVIEW, to get CMOP data from the Outpatient Pharmacy and CMOP files. This data is displayed when viewing Rx's. The only variable passed in this call is DA. The PSXVIEW routine displays the information on the screen. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25301253 COMPONENT/ENTRY POINT: PSXVIEW VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: DA is the internal entry number of the record in the Rx file (#52). SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2205 IA #: 2205 DATE CREATED: OCT 28, 1997 CUSTODIAL PACKAGE: CMOP CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSXCH NAME: DBIA2205 ID: PSXCH GENERAL DESCRIPTION: The Outpatient Pharmacy routine, PSOSUCHG, calls the CMOP routine, PSXCH to screen Rx's for CMOP when changing the suspense date for Rx's. Suspense dates cannot be changed for CMOP prescriptions if the CMOP suspense status is "TRANSMISSION COMPLETED" or "LOADING FOR TRANSMISSION". STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28972434 COMPONENT/ENTRY POINT: P VARIABLES: SFN TYPE: Input VARIABLES DESCRIPTION: SFN is the internel entry number of the record in the RX SUSPENSE (#52.5) file. COMPONENT/ENTRY POINT: A VARIABLES: SFN TYPE: Input VARIABLES DESCRIPTION: SFN is the internal entry number of the record in the RX SUSPENSE (#52.5) file. VARIABLES: XOK TYPE: Output VARIABLES DESCRIPTION: XOK=0 indicates that the suspense date cannot be changed at this time. XOK'=0 indicates that the suspense date can be changed at this time. SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2206 IA #: 2206 DATE CREATED: OCT 28, 1997 CUSTODIAL PACKAGE: CMOP CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSXCH NAME: DBIA2206 ID: PSXCH GENERAL DESCRIPTION: The Outpatient Pharmacy routine, PSOSUCH1, calls the CMOP routine, PSXCH, to screen Rx's when changing the suspense date. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25301292 COMPONENT/ENTRY POINT: X VARIABLES: SFN TYPE: Input VARIABLES DESCRIPTION: SFN is the internal entry number of the record in the Rx Suspense file (#52.5). SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2207 IA #: 2207 DATE CREATED: OCT 28, 1997 CUSTODIAL PACKAGE: CMOP CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSXRSUS NAME: DBIA2207 ID: PSXRSUS GENERAL DESCRIPTION: The Outpatient Pharmacy routine, PSOSULB1, calls the CMOP routine, PSXRSUS if the site is using the CMOP software. This call displays the CMOP Print from Suspense file options. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25301326 COMPONENT/ENTRY POINT: PSXRSUS VARIABLES: PSXSYS TYPE: Input VARIABLES DESCRIPTION: This is a CMOP system variable. If this variable is defined, the site is a CMOP remote medical center. SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2208 IA #: 2208 DATE CREATED: OCT 28, 1997 CUSTODIAL PACKAGE: CMOP CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSXRPPL1 NAME: DBIA2208 ID: PSXRPPL1 GENERAL DESCRIPTION: The Outpatient Pharmacy routine, PSOSURST, calls the CMOP routine, PSXRPPL1 if the site is using the CMOP software. This call displays the CMOP Reprint Batches from Suspense options. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25301343 COMPONENT/ENTRY POINT: PSXRPPL1 VARIABLES: PSXSYS TYPE: Input VARIABLES DESCRIPTION: This is a CMOP system variable. If this variable is defined, the site is a CMOP remote medical center. SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2209 IA #: 2209 DATE CREATED: OCT 28, 1997 CUSTODIAL PACKAGE: CMOP CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSXEDIT NAME: DBIA2209 ID: PSXEDIT GENERAL DESCRIPTION: The Outpatient Pharmacy routine, PSORXED, calls the CMOP routine, PSXEDIT. This call will screen Rx's for CMOP when editing the Rx. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25372528 COMPONENT/ENTRY POINT: PSXEDIT VARIABLES: PSORXED TYPE: Input VARIABLES DESCRIPTION: This variable stores the zero node of the entry in the Rx file (#52). VARIABLES: PSXFROM TYPE: Input VARIABLES DESCRIPTION: This variable stores the process name that is making the call to the routine. It is used to determine the action to be made on the Rx during processing. SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2211 IA #: 2211 DATE CREATED: OCT 29, 1997 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOORDA NAME: DBIA2211 ID: PSOORDA GENERAL DESCRIPTION: Inpatient Medications requests permission to call (Outpatient Pharmacy) ^PSOORDA. This call builds the ^TMP("PSJAL" and ^TMP("PSJDA" globals that contain the patients Allergy/Adverse Reaction information to display on the ListMan screen. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25391393 COMPONENT/ENTRY POINT: BEG COMPONENT DESCRIPTION: This entry point builds the ^TMP("PSJDA" global containing all of the patients allergy and adverse reaction information. VARIABLES: PSJINPT TYPE: Input VARIABLES DESCRIPTION: This variable is set to 1 to identify that the call is coming from the Inpatient Meds routine. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This is the patient's IEN number in ^DPT. VARIABLES: TMP global entries TYPE: Output VARIABLES DESCRIPTION: The call returns all of a patients allergy and adverse reaction information in the ^TMP("PSJDA",N,0). The variable "N" is the screen line numbers. Inpatient Meds uses this ^TMP global to display the information through ListMan. Example below. ^TMP("PSJDA",539016357,1,0) = Verified ^TMP("PSJDA",539016357,2,0) = Drug: ^TMP("PSJDA",539016357,3,0) = 1 DAVE DRUG ^TMP("PSJDA",539016357,4,0) = Food: ^TMP("PSJDA",539016357,5,0) = 2 STRAWBERRIES ^TMP("PSJDA",539016357,6,0) = Other: ^TMP("PSJDA",539016357,7,0) = ^TMP("PSJDA",539016357,8,0) = Non-Verified ^TMP("PSJDA",539016357,9,0) = Drug: ^TMP("PSJDA",539016357,10,0) = 3 CODEINE ^TMP("PSJDA",539016357,11,0) = 4 PENNTUSS ^TMP("PSJDA",539016357,12,0) = 5 RADIOLOGICAL/CONTRAST MEDIA ^TMP("PSJDA",539016357,13,0) = Other: ^TMP("PSJDA",539016357,14,0) = 6 DUST COMPONENT/ENTRY POINT: DSPLY COMPONENT DESCRIPTION: The call returns all of a patients allergy and adverse reaction information in the ^TMP("PSJAL",N,0). The variable "N" is the screen line numbers. Inpatient Meds uses this ^TMP global to display the information through ListMan. VARIABLES: PSJINPT TYPE: Input VARIABLES DESCRIPTION: This variable is set to 1 to identify that the call is coming from the Inpatient Meds routine. VARIABLES: ORN TYPE: Input VARIABLES DESCRIPTION: This variable is the allergy/adverse reaction number choosen from the allergy/adverse reaction screen. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This is the patient's IEN number in ^DPT. VARIABLES: TMP global TYPE: Output VARIABLES DESCRIPTION: This call returns detailed information about a single allergy/adverse reaction for a patient in ^TMP("PSJAL",N,0). The variable "N" is the screen line numbers. Inpatient Meds uses this ^TMP global to display the information through ListMan. Example below. ^TMP("PSJAL",539016357,1,0) = Causative Agent: STRAWBERRIES ^TMP("PSJAL",539016357,2,0) = Severity: ^TMP("PSJAL",539016357,3,0) = Ingredients: ^TMP("PSJAL",539016357,4,0) = ^TMP("PSJAL",539016357,5,0) = VA Drug Class: ^TMP("PSJAL",539016357,6,0) = Originated: 03/10/95 Originator: ANDERSON,CURTIS ^TMP("PSJAL",539016357,7,0) = Verified: Yes OBS/Hist: OBSERVED ^TMP("PSJAL",539016357,8,0) = ^TMP("PSJAL",539016357,9,0) = Comments: ^TMP("PSJAL",539016357,10,0) = Patient reacts severly to strawberries in any naturally occurring form. ^TMP("PSJAL",539016357,11,0) = ^TMP("PSJAL",539016357,12,0) = Signs/Symptoms: HIVES ^TMP("PSJAL",539016357,13,0) = Mechanism: UNKNOWN SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2212 IA #: 2212 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: OCT 29, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: NEW PERSON editing ID: VA(200, GLOBAL REFERENCE: VA(200,D0,.13) => phone numbers FIELD NUMBER: .132 FIELD NAME: OFFICE PHONE LOCATION: .13;2 ACCESS: Write w/Fileman FIELD NUMBER: .133 FIELD NAME: PHONE #3 LOCATION: .13;3 ACCESS: Write w/Fileman FIELD NUMBER: .134 FIELD NAME: PHONE #4 LOCATION: .13;4 ACCESS: Write w/Fileman FIELD NUMBER: .136 FIELD NAME: FAX NUMBER LOCATION: .13;6 ACCESS: Write w/Fileman FIELD NUMBER: .137 FIELD NAME: VOICE PAGER LOCATION: .13;7 ACCESS: Write w/Fileman FIELD NUMBER: .138 FIELD NAME: DIGITAL PAGER LOCATION: .13;8 ACCESS: Write w/Fileman GLOBAL REFERENCE: VA(200,D0,.11) => address FIELD NUMBER: .111 FIELD NAME: STREET ADDRESS 1 LOCATION: .11;1 ACCESS: Write w/Fileman FIELD NUMBER: .112 FIELD NAME: STREET ADDRESS 2 LOCATION: .11;2 ACCESS: Write w/Fileman FIELD NUMBER: .113 FIELD NAME: STREET ADDRESS 3 LOCATION: .11;3 ACCESS: Write w/Fileman FIELD NUMBER: .114 FIELD NAME: CITY LOCATION: .11;4 ACCESS: Write w/Fileman FIELD NUMBER: .115 FIELD NAME: STATE LOCATION: .11;5 ACCESS: Write w/Fileman FIELD NUMBER: .116 FIELD NAME: ZIP CODE LOCATION: .11;6 ACCESS: Write w/Fileman GLOBAL REFERENCE: VA(200,D0,1) => preferred editor FIELD NUMBER: 31.3 FIELD NAME: PREFERRED EDITOR LOCATION: 1;5 ACCESS: Write w/Fileman GENERAL DESCRIPTION: With patch XM*7.1*50, MailMan will be dropping phone and address fields from its MAILBOX file 3.7 and would like to let users edit, instead, various fields in the NEW PERSON file 200. The fields are: 31.3 preferred editor .111 street address 1 .112 street address 2 .113 street address 3 .114 city .115 state .116 zip .132 office phone .133 phone #3 .134 phone #4 .136 fax # .137 voice pager .138 digital pager I intend to let the user edit the fields using a FileMan call. I intend to retrieve the data by direct global reads. One global access will retrieve the record with the address fields; the other, the record with the phone numbers. I will not be retrieving the data for the preferred editor. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: DEC 31, 2500 MAIL MESSAGE: 25383374 SUBSCRIBING PACKAGE: MAILMAN ISC: Oakland NUMBER: 2213 IA #: 2213 DATE CREATED: OCT 29, 1997 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: XRTL SET TO FORCE RESPONSE TIME MONITORING GENERAL DESCRIPTION: XRTL=1 is a flag that allows response time monitoring. It is typically set during signon based on a flag in the Kernel Site Parameter file. Because resource utilization must be monitored closely in the new client/server environment, the RPC Broker needs to NEW and SET the XTRL variable in its code. This will allow for the monitoring of all RPCs. (The README file that accompanies version 1.1 of the RPC Broker notifies IRM staff that the monitoring is being turned on.) When sufficient data has been collected the SETting of XTRL will be removed by a patch. STATUS: Active DURATION: Next Version MAIL MESSAGE: 24884973 GOOD ONLY FOR VERSION: 1.1 SUBSCRIBING PACKAGE: RPC BROKER ISC: Oakland NUMBER: 2214 IA #: 2214 FILE NUMBER: 120.8 GLOBAL ROOT: GMR(120.8 DATE CREATED: OCT 30, 1997 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2214 ID: GMR(120.8 GLOBAL REFERENCE: GMR(120.8,D0,0) => GMR ALLERGY (0;3) FIELD NUMBER: 1 FIELD NAME: GMR ALLERGY LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is a variable pointer to help relate this allergy to some record in one of the files to which this field points. GLOBAL DESCRIPTION: This is the PATIENT ALLERGY file. GENERAL DESCRIPTION: The Outpatient Pharmacy package request permission to look at the PATIENT ALLERGY file 120.8 for the purpose of its drug-allergy check functionality. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25396344 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2215 IA #: 2215 FILE NUMBER: 350 GLOBAL ROOT: IB( DATE CREATED: OCT 30, 1997 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2215 ID: IB( GLOBAL REFERENCE: IB(D0,0) FIELD NUMBER: .03 FIELD NAME: ACTION TYPE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field points to an entry in the IB ACTION TYPE file. Entries in the IB ACTION TYPE file provide specific information about the type of entry that is being created and provides data necessary to AR to resolve the data from the applicaiton. FIELD NUMBER: .09 FIELD NAME: PARENT CHARGE LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is a pointer to the original IB ACTION entry that this entry refers to. For a NEW entry it will point to itself. For all other entries it will point to the original entry. The most recent entry can be found by reading the ^IB("APDT",parent,0) cross reference. GLOBAL DESCRIPTION: This is the INTEGRATED BILLING ACTION file 350. It is a link between ACCOUNTS RECEIVABLE and an application. Entries in this file are created by applications calling approved application specific routines. GENERAL DESCRIPTION: The Outpatient Pharmacy package request permission to look at the INTEGRATED BILLING ACTION file 350. STATUS: Active MAIL MESSAGE: 25397583 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2216 IA #: 2216 FILE NUMBER: 350.3 GLOBAL ROOT: IBE(350.3 DATE CREATED: OCT 30, 1997 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2216 ID: IBE(350.3 GLOBAL REFERENCE: IBE(350.3,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: The FileMan read is required to allow the user to select an entry from this file, and to find the entry RX DELETED. GLOBAL DESCRIPTION: This reference represents an entry in this file that may be looked up by a user or the application itself. GENERAL DESCRIPTION: The Outpatient Pharmacy package requests access to the Pharmacy Copayment charge cancellation reasons that are stored in the IB CHARGE REMOVE REASONS (#350.3) file. Pharmacy needs to conduct two look-ups on this file. The first look-up allows the user to select a Pharmacy Copayment charge cancellation reason from this file. The second look-up is conducted internally by the application to find the entry RX DELETED from this file, when a prescription is deleted or returned to stock. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25397881 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham EDITOR: MINARDI,CHRISTOPHER P NUMBER: 2219 IA #: 2219 FILE NUMBER: 100 GLOBAL ROOT: OR(100 DATE CREATED: NOV 03, 1997 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2219 ID: OR(100 GLOBAL REFERENCE: OR(100, FIELD NUMBER: .02 FIELD NAME: OBJECT OF ORDER LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the individual object of the order. Depending on the parent file entry, this will be the Patient, Control Point, etc. FIELD NUMBER: 9 FIELD NAME: REPLACED ORDER LOCATION: 3;5 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: This is the file of orders/requisitions made for any package through the ORder Entry option (OR). GENERAL DESCRIPTION: The Outpatient Pharmacy package request permission to look at ORDER file 100. STATUS: Active MAIL MESSAGE: 25419825 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: VBECS SUBSCRIBING DETAILS: ADDED 11/27/2007 DBA Comments: FROM PRIVATE TO CONTROLLED DATE/TIME EDITED: NOV 20, 2007@21:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MORTON,RANDY WITH CONCURRENCE OF: BUECHLER,MELANIE DATE/TIME EDITED: NOV 20, 2007@19:00 ACTION: USAGE CHOICE CHANGED AT THE REQUEST OF: BUECHLER,MELANIE NUMBER: 2220 IA #: 2220 DATE CREATED: APR 01, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SCDXHLDR NAME: DBIA2220 ID: SCDXHLDR GENERAL DESCRIPTION: Integration agreement to use the variables SDSTPAMB, SDIEMM, VALQUIET in the routine SCDXHLDR. SDSTPAMB prevents Scheduling/Amb Care from sending an Event Capture patient procedure to the Austin NPCD for workload credit. However, the patient procedure is still filed in the respective Scheduling/PCE files. SDIEMM is used to prevent the validation checks from executing during the Event Capture conversion completed as part of the install of EC*2*7. VALQUIET is used to prevent the validation dialogue from displaying to the user during Event Capture patient record edit processing. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26786165 COMPONENT/ENTRY POINT: EN VARIABLES: SDSTPAMB TYPE: Input VARIABLES DESCRIPTION: Variable used to prevent Scheduling/Amb Care from sending an Event Capture patient procedure (encounter) to Austin NPCD for workload credit. VARIABLES: SDIEMM TYPE: Input VARIABLES DESCRIPTION: Variable used to prevent the validation checks from executing. VARIABLES: VALQUIET TYPE: Input VARIABLES DESCRIPTION: Variable used to prevent the validation dialogue from displaying. SUBSCRIBING PACKAGE: EVENT CAPTURE ISC: Albany NUMBER: 2221 IA #: 2221 FILE NUMBER: 50.607 GLOBAL ROOT: PS(50.607 DATE CREATED: NOV 03, 1997 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2221 ID: PS(50.607 GLOBAL REFERENCE: PS(50.607,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the drug unit of the measure. GLOBAL DESCRIPTION: This file contains the individual drug units. GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSN*4*94. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of June 1, 2006. The Outpatient Pharmacy package request permission to look at DRUG UNITS file 50.607. We need the individual drug unit of a drug when building our segments for HL7 data transmission. STATUS: Active EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 25424005 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham EDITOR: RUZBACKI,RON T NUMBER: 2223 IA #: 2223 FILE NUMBER: 50.7 GLOBAL ROOT: PS(50.7 DATE CREATED: NOV 03, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2223 ID: PS(50.7 GENERAL DESCRIPTION: The Outpatient Pharmacy package request permission to look at PHARMACY ORDERABLE ITEM file 50.7. This is a new file of Pharmacy Data Management 1.0. It is used extensively throughout our routines. We are requesting read/write access to the entire file and cross-references through direct reads/writes and VA Fileman utilities. STATUS: Active MAIL MESSAGE: 25424243 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2224 IA #: 2224 FILE NUMBER: 51 GLOBAL ROOT: PS(51 DATE CREATED: NOV 03, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2224 ID: PS(51 GLOBAL REFERENCE: PS(51, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the name of the medication instruction. We use the 'A' cross reference to get the expanded SIG for the prescription. We use the 'B' cross reference to get the IEN of the entry in the file. FIELD NUMBER: 1 FIELD NAME: EXPANSION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the full explanation of the medication instruction. FIELD NUMBER: 2 FIELD NAME: MED ROUTE LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is a pointer to the MEDICATION ROUTES file 51.2. FIELD NUMBER: 3 FIELD NAME: SCHEDULE LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the prescription schedule. FIELD NUMBER: 9 FIELD NAME: PLURAL LOCATION: 9;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to indicate if there is a plural name for this medication instruction. FIELD NUMBER: 30 FIELD NAME: INTENDED USE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is a set of codes field used to determine how the instruction is viewed by the user. The entry may be marked for OUTPATIENT ONLY (0), for OUTPATIENT AND INPATIENT (1), or for INPATIENT ONLY (2). FIELD NUMBER: 31 FIELD NAME: FREQUENCY (IN MINUTES) LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the number of minutes between each time that the action should take place. This field will be used to calculate defaults for Quantity and Days Supply in the Outpatient Pharmacy Package. It will also be used to calculate defaults for the fields in the pharmacy dialog in Computerized Patient Record System (CPRS). FIELD NUMBER: 1.1 FIELD NAME: OTHER LANGUAGE EXPANSION LOCATION: 4;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: This file holds the abbreviations which are often used when entering the prescription's SIG. Each record holds an expansion of the abbreviation. GLOBAL REFERENCE: PS(51,'A',D0) GLOBAL DESCRIPTION: This cross reference is used to get the drug's expanded name and plural. GLOBAL REFERENCE: PS(51,'B',D0) GLOBAL DESCRIPTION: This cross reference is used to obtain the expanded SIG. GENERAL DESCRIPTION: The Outpatient Pharmacy package request permission to look at MEDICATION INSTRUCTION file 51. STATUS: Active MAIL MESSAGE: 25425554 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2225 IA #: 2225 FILE NUMBER: 51.1 GLOBAL ROOT: PS(51.1 DATE CREATED: NOV 03, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2225 ID: PS(51.1 GLOBAL REFERENCE: PS(51.1, FIELD NUMBER: 8 FIELD NAME: OUTPATIENT EXPANSION LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the expansion for this Administration Schedule to be used in the Outpatient Pharmacy package. FIELD NUMBER: 2 FIELD NAME: FREQUENCY (IN MINUTES) LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the number of minutes between each time that the action should take place. GLOBAL DESCRIPTION: This file contains a set of standard times over which medications are to be administered. GLOBAL REFERENCE: PS(51.1,'B',D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This cross reference on the .01 field is used to $Order through the file to get the Outpatient Expansion for the prescription. GENERAL DESCRIPTION: The Outpatient Pharmacy package request permission to look at ADMINISTRATION SCHEDULE file 51.1. We use the 'B' cross reference to $Order through the file to get the expansion of the Administration Schedule for the prescription. STATUS: Active MAIL MESSAGE: 25425705 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2226 IA #: 2226 FILE NUMBER: 51.2 GLOBAL ROOT: PS(51.2 DATE CREATED: NOV 03, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2226 ID: PS(51.2 GLOBAL REFERENCE: PS(51.2,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the route of administration for a medication. FIELD NUMBER: 1 FIELD NAME: ABBREVIATION LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is an abbreviation of the medication route. FIELD NUMBER: 3 FIELD NAME: PACKAGE USE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to screen out Med Routes not needed by Outpatient or Inpatient. FIELD NUMBER: 4 FIELD NAME: OUTPATIENT EXPANSION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the Medication Route's expansion used by Outpatient Pharmacy. GLOBAL DESCRIPTION: This file contains the medication routes. GENERAL DESCRIPTION: The Outpatient Pharmacy package request permission to look at MEDICATION ROUTES file 51.2. STATUS: Active MAIL MESSAGE: 25425846 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2227 IA #: 2227 FILE NUMBER: 54 GLOBAL ROOT: PS(54 DATE CREATED: NOV 04, 1997 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2227 ID: PS(54 GLOBAL REFERENCE: PS(54,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains a brief description of any medical warnings associated with the specific drug. FIELD NUMBER: 1 FIELD NAME: TEXT LOCATION: 1;0 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is a multiple field which contains an expansion of any medical warnings associated with the specific drug. GLOBAL DESCRIPTION: This file holds the expansion of the number codes that represent the additional warnings/consultations that may be needed for a particular drug. GLOBAL REFERENCE: PS(54,D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: TEXT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the expanded description of any medical warnings. GENERAL DESCRIPTION: This Outpatient Pharmacy package request permission to look at RX CONSULT file 54. STATUS: Active MAIL MESSAGE: 25432161 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 2228 IA #: 2228 FILE NUMBER: 55 GLOBAL ROOT: PS(55 DATE CREATED: NOV 14, 2005 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2228 ID: PS(55 GENERAL DESCRIPTION: This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. The Outpatient Pharmacy and CMOP packages request full access to PHARMACY PATIENT file 55. This file is used extensively throughout our routines. Therefore, we request read and write access to the entire file and cross references through Fileman utilities and direct reads/writes. STATUS: Active EXPIRATION DATE: DEC 31, 2006 MAIL MESSAGE: 25432342 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: CMOP SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH EDITOR: BLOCKER,DAVE NUMBER: 2229 IA #: 2229 FILE NUMBER: 56 GLOBAL ROOT: PS(56 DATE CREATED: NOV 04, 1997 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2229 ID: PS(56 GLOBAL REFERENCE: PS(56,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the name of the drug interaction. FIELD NUMBER: 1 FIELD NAME: INGREDIENT 1 LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is a pointer to DRUG INGREDIENTS file 50.416. It is used to store the first ingredient of the adverse drug/drug interaction. FIELD NUMBER: 2 FIELD NAME: INGREDIENT 2 LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is a pointer to DRUG INGREDIENTS file 50.416. It is used to store the second ingredient of the adverse drug/drug interaction. It must be different from the first ingredient. FIELD NUMBER: 3 FIELD NAME: SEVERITY LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to indicate the type of reaction from the interaction. It is a set of codes for Critical (1) or Significant (2). FIELD NUMBER: 4 FIELD NAME: NATIONALLY ENTERED LOCATION: 0;5 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This field is used to indicate if this data was sent out by the ISC. FIELD NUMBER: 5 FIELD NAME: TOTAL INDEXES LOCATION: 0;6 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: This field is used to store the total number of interactions for an entry. FIELD NUMBER: 7 FIELD NAME: INACTIVATION DATE LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: This file is used to store drug-drug interactions. GLOBAL REFERENCE: PS(56,'APD',D0,D1,0) GLOBAL DESCRIPTION: This cross reference is used to index the file by adverse drug reactions. GENERAL DESCRIPTION: The Outpatient Pharmacy package request permission to look at DRUG INTERACTION file 56. STATUS: Active MAIL MESSAGE: 25433057 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2230 IA #: 2230 FILE NUMBER: 550 GLOBAL ROOT: PSX(550 DATE CREATED: NOV 04, 1997 CUSTODIAL PACKAGE: CMOP CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2230 ID: PSX(550 GLOBAL REFERENCE: PSX(550,D0,0) FIELD NUMBER: 1 FIELD NAME: STATUS LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is a set of codes field indicating whether the status of thee facility relative to CMOP transmission is ACTIVE (A) or INACTIVE (I). GLOBAL DESCRIPTION: This is a system parameter file for CMOP. GLOBAL REFERENCE: PSX(550,'C',D0) GLOBAL DESCRIPTION: This cross reference on the STATUS field will exist only if there is an active CMOP site that the remote will be transmitting CMOP Rx's to. GENERAL DESCRIPTION: The Outpatient Pharmacy package request permission to look at CMOP SYSTEM file 550. STATUS: Active MAIL MESSAGE: 25435856 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2231 IA #: 2231 FILE NUMBER: 550.2 GLOBAL ROOT: PSX(550.2 DATE CREATED: NOV 04, 1997 CUSTODIAL PACKAGE: CMOP CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2231 ID: PSX(550.2 GLOBAL REFERENCE: PSX(550.2, FIELD NUMBER: 5 FIELD NAME: TRANSMISSION DATE/TIME LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the date and time of the CMOP transmission. FIELD NUMBER: 3 FIELD NAME: CMOP SYSTEM LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: .01 FIELD NAME: TRANSMISSION LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: STATUS LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: DIVISION LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: SENDER LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 6 FIELD NAME: CREATED DATE/TIME LOCATION: 0;7 ACCESS: Read w/Fileman FIELD NUMBER: 7 FIELD NAME: RECEIVED DATE/TIME LOCATION: 1;1 ACCESS: Read w/Fileman FIELD NUMBER: 8 FIELD NAME: RETRANSMISSION # LOCATION: 1;2 ACCESS: Read w/Fileman FIELD NUMBER: 9 FIELD NAME: ORIGINAL TRANSMISSION LOCATION: 1;3 ACCESS: Read w/Fileman FIELD NUMBER: 10 FIELD NAME: CLOSED DATE/TIME LOCATION: 1;4 ACCESS: Read w/Fileman FIELD NUMBER: 13 FIELD NAME: TOTAL ORDERS LOCATION: 1/7 ACCESS: Read w/Fileman FIELD NUMBER: 14 FIELD NAME: TOTAL RXS LOCATION: 1;8 ACCESS: Read w/Fileman GLOBAL DESCRIPTION: This file maintains summary information of all CMOP transmissions. GLOBAL REFERENCE: PSX(550.2,'B',D0,D1) GLOBAL DESCRIPTION: This cross reference on the TRANSMISSION field contains the number of the CMOP transmission. GLOBAL REFERENCE: PSX(550.2,'D',D0,D1) GLOBAL REFERENCE: PSX(550.2,D0,15, FIELD NUMBER: .01 FIELD NAME: PRESCRIPTIONS LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .02 FIELD NAME: FILL LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: .03 FIELD NAME: PATIENT LOCATION: 0;3 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The Outpatient Pharmacy package request permission to look at CMOP TRANSMISSION file 550.2. STATUS: Active MAIL MESSAGE: 41103748 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE NUMBER: 2232 IA #: 2232 DATE CREATED: NOV 05, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUDHSET NAME: Resource Device ID: XUDHSET GENERAL DESCRIPTION: This IA describes some API's to support Resource devices. STATUS: Active MAIL MESSAGE: 25450107 COMPONENT/ENTRY POINT: RES COMPONENT DESCRIPTION: $$RES^XUDHSET(device_name,resource_name,slot_count,description,subtype) device_name For the resource device. resource_name (optional) The resource name if not the same as the device name. slot_count The number of concurrent jobs that can use this device. defaults to 1. description The device description, defaults to 'Resource Device'. subtype The subtype to use, defaults to P-OTHER. returns If an error '-1^text' The 'IEN^device name' like a DIC call. This call is used to setup a Resource device. NUMBER: 2233 IA #: 2233 FILE NUMBER: 43 GLOBAL ROOT: DG(43, DATE CREATED: NOV 06, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2233 ID: DG(43, GLOBAL REFERENCE: DG(43,D0,GL) FIELD NUMBER: 11 FIELD NAME: MULTIDIVISIONAL MED CENTER? LOCATION: GL;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Indicates if the facility is a multi-divisional medical center. GLOBAL DESCRIPTION: This file contains site specific parameters used by ADT Modules. GENERAL DESCRIPTION: DSS Extracts has permission to execute a direct global read to the MULTIDIVISIONAL MED CENTER? field (#43) (GL;2) in the MAS PARAMETERS file (#43). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25460021 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING NUMBER: 2235 IA #: 2235 FILE NUMBER: 4 GLOBAL ROOT: DIC(4, DATE CREATED: NOV 06, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2235 ID: DIC(4, GENERAL DESCRIPTION: DSS Extracts has permission to execute a $Order direct global read of the 'LOC' Cross Reference on the Institution file (#4). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25460117 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany NUMBER: 2236 IA #: 2236 DATE CREATED: APR 01, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SCDXFU04 NAME: DBIA2236 ID: SCDXFU04 GENERAL DESCRIPTION: Integration agreement to use the function $$OKTOXMIT^SCDXFU04 to determine if Event Capture patient procedures are to be sent to the Austin NPCD for workload credit. This integration agreement is used solely by the Event Capture Patient file (#721) clean up patch, EC*2*7. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26786398 COMPONENT/ENTRY POINT: $$OKTOXMIT(ENCDATE,COMPDATE) COMPONENT DESCRIPTION: Determine if an encounter occurring on a specified date should be transmitted to the National Patient Care Database for database and workload credit. SUBSCRIBING PACKAGE: EVENT CAPTURE ISC: Albany NUMBER: 2237 IA #: 2237 FILE NUMBER: 133 GLOBAL ROOT: SRO(133 DATE CREATED: NOV 06, 1997 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2237 ID: SRO(133 GLOBAL REFERENCE: SRO(133,D0,0) FIELD NUMBER: .01 FIELD NAME: SITE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the institution responsible for the Surgery service. If the facility is multi-divisional, there will be more than one entry in this file. GLOBAL DESCRIPTION: The Surgery Site Parameter file contains elements to the Surgery package that may be specific to each individual site. GENERAL DESCRIPTION: DSS Extracts has permission to execute direct global reads of the SITE field (#.01) (0;1) and the 'B' Cross Reference on the SURGERY SITE file (#133). STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI NUMBER: 2238 IA #: 2238 DATE CREATED: NOV 19, 1997 CUSTODIAL PACKAGE: RPC BROKER CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XWBLIB NAME: CHANGE RPC RETURN TYPE ID: XWBLIB GENERAL DESCRIPTION: Use this function in the M code called by an RPC to change the return value type that the RPC will return on the fly. STATUS: Active MAIL MESSAGE: 24832423 COMPONENT/ENTRY POINT: $$RTRNFMT(TYPE,WRAP) COMPONENT DESCRIPTION: Format $$RTRNFMT^XWBLIB(type, wrap) Input type Set this to the RETURN VALUE TYPE to change the RPC's setting to. You can set it to one of the following numeric or free text values: numeric free text 1 SINGLE VALUE 2 ARRAY 3 WORD PROCESSING 4 GLOBAL ARRAY 5 FOR GLOBAL INSTANCE wrap Set to 1 to set the RPC's WORD WRAP ON setting to True; set to 0 to set the RPC's WORD WRAP ON setting to False. Output Return Value 0 if the return value type could not be changed; otherwise, the numeric code representing the return value type that the RPC is changed to. Example I '$$RTRNFMT^XWBLIB("ARRAY",1) D .; branch to code if can't change RPC type VARIABLES: TYPE TYPE: Input VARIABLES DESCRIPTION: Set this to the RETURN VALUE TYPE to change the RPC's setting to. You can set it to one of the following numeric or free text values: numeric free text 1 SINGLE VALUE 2 ARRAY 3 WORD PROCESSING 4 GLOBAL ARRAY 5 FOR GLOBAL INSTANCE VARIABLES: WRAP TYPE: Input VARIABLES DESCRIPTION: Set to 1 to set the RPC's WORD WRAP ON setting to True; set to 0 to set the RPC's WORD WRAP ON setting to False. NUMBER: 2239 IA #: 2239 DATE CREATED: NOV 19, 1997 CUSTODIAL PACKAGE: RPC BROKER CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: XWBAPVER -- RPC VERSION GENERAL DESCRIPTION: XWBAPVER is a documented variable that will contain an RPC version if one was set in the client application (using the RPCVersion property). Otherwise XWBAPVER defaults to 0. STATUS: Active MAIL MESSAGE: 24832423 NUMBER: 2240 IA #: 2240 DATE CREATED: NOV 19, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUSRB1 NAME: ENCRYPTING -- CLIENT/SERVER ID: XUSRB1 GENERAL DESCRIPTION: Kernel and the RPC Broker provide encryption functions that can be used to encrypt messages sent between the client and the server. This function encrypts a string before transport to a Client system, where it will be decrypted. STATUS: Active MAIL MESSAGE: 24832423 COMPONENT/ENTRY POINT: $$ENCRYP(STRING) COMPONENT DESCRIPTION: Function performs encryption on the input string, returning the encrypted string. VARIABLES: STRING TYPE: Input VARIABLES DESCRIPTION: The string that needs to be encrypted. NUMBER: 2241 IA #: 2241 DATE CREATED: NOV 19, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUSRB1 NAME: DECRYPTING -- CLIENT/SERVER ID: XUSRB1 GENERAL DESCRIPTION: Kernel and the RPC Broker provide encryption functions that can be used to encrypt messages sent between the client and the server. This function decrypts a string that was encrypted on a Client system. STATUS: Active MAIL MESSAGE: 24832423 COMPONENT/ENTRY POINT: $$DECRYP(ENCRIPTED_STRING) COMPONENT DESCRIPTION: Function decrypts a string that has been encrypted using the Encrypt Delphi function supplied by Broker, returning the decrypted string. VARIABLES: ENCRYPTED_STRING TYPE: Input NUMBER: 2242 IA #: 2242 DATE CREATED: NOV 20, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGSEC NAME: DBIA2242 ID: DGSEC GENERAL DESCRIPTION: This DBIA will provide temporary entry points to routine DGSEC to enable the listed packages to update the DG SECURITY LOG when a sensitive patient has been accessed. This will be in effect until supported entry points are defined. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 23689903 COMPONENT/ENTRY POINT: BULTIN COMPONENT DESCRIPTION: Generate bulletin that Sensitive Patient has been accessed. VARIABLES: Y TYPE: Input VARIABLES DESCRIPTION: Y = DFN, Pointer to the PATIENT file (#2) VARIABLES: DGOPT TYPE: Input VARIABLES DESCRIPTION: S DGOPT=$S(XQOPT<0:"^UNKNOWN",1:XQOPT) ; equals the calling option VARIABLES: XMCHAN TYPE: Input VARIABLES DESCRIPTION: Set = 1 to suppress dots printed by mailman VARIABLES: DIC(0) TYPE: Input VARIABLES DESCRIPTION: Set = $TR(DIC(0),"E") to suppress output and prompting COMPONENT/ENTRY POINT: SETLOG COMPONENT DESCRIPTION: Create entry in DG SECURITY LOG of sensitive patient access. VARIABLES: Y TYPE: Input VARIABLES DESCRIPTION: Y = DFN, Pointer to the PATIENT file (#2) VARIABLES: DGOPT TYPE: Input VARIABLES DESCRIPTION: S DGOPT=$S(XQOPT<0:"^UNKNOWN",1:XQOPT) ; equals the calling option VARIABLES: DG1 TYPE: Input VARIABLES DESCRIPTION: Set = 1 for inpatient, = 0 for outpatient VARIABLES: DIC(0) TYPE: Input VARIABLES DESCRIPTION: Set = $TR(DIC(0),"E") to suppress output and prompting SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines NUMBER: 2243 IA #: 2243 DATE CREATED: DEC 03, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XPDIJ NAME: Tasking KIDS Installation ID: XPDIJ GENERAL DESCRIPTION: The purpose of this DBIA is to document the use of a KIDS entry point to task off a KIDS Install. This is useful if a large conversion needs to run in background while users are back on the system. For example, the first KIDS build can install a new version of software, then task off a second clean-up/conversion build. This allows users back on the system because the new version install completes and unlocks options and protocols. Meanwhile the clean-up runs in background under KIDS and makes use of KIDS checkpoints, restart upon failure, and message logging that can later be accessed in the Install File Print. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25617638 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: The KIDS entry point EN^XPDIJ can be used with XPDA defined to task off a KIDS install. VARIABLES: XPDA TYPE: Input VARIABLES DESCRIPTION: Internal entry number of the build to be tasked in the Install file #9.7 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2244 IA #: 2244 FILE NUMBER: 740 GLOBAL ROOT: QA( DATE CREATED: DEC 04, 1997 CUSTODIAL PACKAGE: QUALITY ASSURANCE INTEGRATION CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PATIENT REPRESENTATIVE ID: QA( GLOBAL REFERENCE: QA(740,D0,'QAC') FIELD NUMBER: 749 FIELD NAME: MULTI-DIVISIONAL PAT REP FACILITY LOCATION: QAC;3 ACCESS: Read w/Fileman GLOBAL REFERENCE: QA(740,D0,'QAC2', FIELD NUMBER: 750 FIELD NAME: PAT REP HOSPITAL DIVISION LOCATION: QAC2;0 ACCESS: Read w/Fileman FIELD DESCRIPTION: Multiple for division within an NDBI group. GENERAL DESCRIPTION: I am the developer for the Quality Assurrance packages. I had previouly gotten an agreement to use two fields in the QA Site Parameter file (#740) to keep multi-divisional information fot the Patient Representative package. The Integration agreement is #2073. File 740 is part of the Integration Module. Both of these packages are in the Quality Assurrance group, the agreements are to keep a documentation trail. It turns out that the two fields in the agreement (741.1 and 741.11) are on the "OS" nodes, which are still being used by some stations for Occurrance Screening. I have decided to create comparable fields on the "QAC" nodes to provide the same functionality. The new fields are #749 MULTI-DIVISIONAL PAT REP FACILITY #750 PAT REP HOSPITAL DIVISION STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25678575 SUBSCRIBING PACKAGE: PATIENT REPRESENTATIVE ISC: Washington/Silver Spring NUMBER: 2245 IA #: 2245 DATE CREATED: DEC 09, 1997 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBARX1 NAME: DBIA2245 ID: IBARX1 GENERAL DESCRIPTION: Outpatient Pharmacy requests permission to pass an internal entry number from the SERVICE/SECTION File (#49) to Integrated Billing, and have a flag returned that indicates if the service can be used for Copay billing in Outpatient Pharmacy. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25725440 COMPONENT/ENTRY POINT: $$SERV(Y) COMPONENT DESCRIPTION: This entry point is used to determine if the Service/Section pointer associated with the Outpatient Site is valid for Outpatient Copay billing. VARIABLES: Y TYPE: Input VARIABLES DESCRIPTION: Pointer to the SERVICE/SECTION File (#49) associated with the Outpatient Site. VARIABLES: PSOIBST TYPE: Output VARIABLES DESCRIPTION: Indicates if the SERVICE/SECTION is valid for Copay Billing, 1 for yes, 0 for no. SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2246 IA #: 2246 FILE NUMBER: 19 GLOBAL ROOT: DIC(19, DATE CREATED: JAN 07, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2246 ID: DIC(19, GLOBAL REFERENCE: DIC(19,#,0) FIELD NUMBER: 2 FIELD NAME: OUT OF ORDER MESSAGE LOCATION: 0;3 ACCESS: Write w/Fileman FIELD DESCRIPTION: Use ^DIE to edit this field. GENERAL DESCRIPTION: Inpatient Medications requests permission to $O through the OPTION file (#19), "B" cross reference. We also request Write access by VA FileMan to the OUT OF ORDER MESSAGE field (#2). In version 5.0, this code is used to disable options during the pre install routine and enable them in the post install routine. The group of options that deal with Pick Lists are inactivated during the pre install routine. The options cannot be enabled until the end of the Pick List conversion, which is hours after the KIDS install finishes. The last task of the Pick List conversion routine is to enable the Pick List options again. This is needed to keep the users from processing any Pick Lists until the conversion is completely finished. Making the edit to the OUT OF ORDER MESSAGE FIELD seems to be the only way to accomplish this job. STATUS: Active DURATION: Next Version SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY NUMBER: 2247 IA #: 2247 FILE NUMBER: 3.2 GLOBAL ROOT: %ZIS(2 DATE CREATED: DEC 09, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA-2247 ID: %ZIS(2 GLOBAL REFERENCE: %ZIS(2,D0,BAR0) FIELD NUMBER: 61 FIELD NAME: BAR CODE OFF LOCATION: BAR0;E1,245 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The argument of a MUMPS WRITE statement that will turn off bar code printing mode of a device. GLOBAL DESCRIPTION: This file is pointed to by the Subtype field of the Device file. It holds attributes that charaterize a terminal type. GLOBAL REFERENCE: %ZIS(2,D0,BAR1) FIELD NUMBER: 60 FIELD NAME: BAR CODE ON LOCATION: BAR1;E1,245 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The argument of a MUMPS WRITE statement that will turn on bar code printing mode of a device. GENERAL DESCRIPTION: Outpatient Pharmacy package request permission to look at TERMINAL TYPE file 3.2. STATUS: Active MAIL MESSAGE: 27450866 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 2248 IA #: 2248 DATE CREATED: DEC 12, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGACT NAME: DBIA 2248 ID: DGACT CREATOR: SCHLEHUBER,CAMERON GENERAL DESCRIPTION: This agreement gives permission to use registration software to determine Facility Treating Specialty file (#45.7) and Specialty file (#42.4) properties. Line tag ACTIVE^DGACT will determine if a Facility Treating Specialty or Specialty is active on a specific date. Line tag TSDATA^DGACT returns Facility Treating Specialty or Specialty; whether the node exits, active on a specific date, associated properties. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 45565742 COMPONENT/ENTRY POINT: ACTIVE COMPONENT DESCRIPTION: DSS has permission to call ACTIVE^DGACT passing in three arguments. Argument 1: File number 45.7 or 42.4 Argument 2: IEN of the Facility Treating Specialty or Specialty Argument 3: Date to check the active/inactive status of the treating speciality DSS expects ACTIVE^DGACT to return the following result: 1 if the Facility Treating Speciality was active on the given date 0 if the Facility Treating Speciality was inactive on the given date An example of how this tag may be referenced: S ACTVAL=$$ACTIVE^DGACT(45.7,ECXSPIEN,DT) COMPONENT/ENTRY POINT: TSDATA COMPONENT DESCRIPTION: Subscriber has permission to call TSDATA^DGACT passing in three, optionally four arguments. Argument 1: File number 45.7 or 42.4 Argument 2: IEN of Facility Treating Specialty or Specialty Files Argument 3: Array variable used to return entry properties Argument 4: Date to check the active/inactive status of the treating specialty (optional, if no date is passed, the current date will be used) Subscriber expects TSDATA^DGACT to return the following results: 1 if the Treating Specialty exists. -1 if the Treating Specialty does not exist. If the Teating Specialty exists, return array: ARRAY(0) := 1 if Treating Specialty was active on the given date. 0 if Treating Spdcialty was not active on the given date. If Argument 1 = 45.7 ARRAY(1) := Name of Facility Treating Specialty ARRAY(2) := Specialty ptr to 42.4 File^Specialty Name ARRAY(3) := Abbreviaton ARRAY(4) := Service ptr to 49 File^Service name If Argument 1 = 42.4 ARRAY(1) := Name of Specialty ARRAY(2) := Print Name ARRAY(3) := Service (set of codes value)^Service name ARRAY(4) := Ask Psychiatric Question? (set of codes value)^null,yes,or no. ARRAY(5) := Billing Rate Bedsection^ ARRAY(6) := MPCR Account ARRAY(7) := PTF Code (alpha-numeric) An example of how this tag may be referenced: S ACTVAL=$$TSDATA^DGACT(45.7,124,.DATA) S ACTVAL=$$TSDATA^DGACT(45.7,124,.DATA,3071002) S ACTVAL=$$TSDATA^DGACT(42.4,100,.DATA) S ACTVAL=$$TSDATA^DGACT(42.4,100,.DATA,3071002) SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany SUBSCRIBING DETAILS: DSS EXTRACTS use the result of ACTIVE^DGACT will be used to determine if a Facility Treating Specialty should be reported on DSS reports. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING DETAILS: ADDED 5/20/2010 SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING DETAILS: added 4/3/2007 SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) SUBSCRIBING DETAILS: To implement the ORWPT SELECT functionality in the VPS namespace, VPS is subscribing to ICR 2248. This will allow VPS to call TSDATA^DGACT as is currently done by ORWPT SELECT and to obtain active facility treating specialty/specialties. SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: HMP team added the call to TSDATA~DGACT to their demogaphic update. VPR needs the data returned from this call as well as ensuring the selected specialty is still active. DBA Comments: 3/9/15-MM: Added VPS as a subscriber to ICR #2248. VA Point of Service (VPS) Kiosks is implementing the ORWPT SELECT RPC in the VPS namespace. VPS Kiosk's request to subscribe to ICR 4907 covering use of ORWPT SELECT was denied by the OERR team. To implement the ORWPT SELECT functionality in the VPS namespace, VPS is requesting to subscribe to ICR 2248. This will allow VPS to call TSDATA^DGACT as is currently done by ORWPT SELECT and to obtain active facility treating specialties. The VPS ORWPT functionality will be included in VPS*1*15, planned for release in April 2015. ICR team processed without custodial review. 3/9/15-MM: Added VPR as a subscriber to ICR #2248 for VPR*1*3. Melanie indicated Mike Kilmade is part of the HMP team and added the call to TSDATA~DGACT to the demographic update. VPR needs the data returned from this call as well as ensuring the selected specialty is still active. Project team was notified ICR team does not currently have Registration knowledgeable resources to review requests for the Registration application and it is the responsibility of the project team to confirm the API and returned data are used as intended by the custodial application. DATE ACTIVATED: MAY 20, 2010 DATE/TIME EDITED: APR 03, 2007@12:25 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: YORTY,ROBERT DATE/TIME EDITED: MAY 20, 2010@13:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: RUSSELL,JOEL WITH CONCURRENCE OF: MINARDI,CHRIS DATE/TIME EDITED: MAY 20, 2010@13:01 ACTION: APPROVED AT THE REQUEST OF: MINARDI,CHRIS DATE/TIME EDITED: APR 03, 2007@13:10 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: YORTY,ROBERT DATE/TIME EDITED: MAR 09, 2015@09:59 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BERRY,LINDA DATE/TIME EDITED: MAR 09, 2015@11:25 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BEUCHLER,MELANIE NUMBER: 2249 IA #: 2249 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: DEC 09, 1997 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA-2249 ID: DGPM( GLOBAL REFERENCE: DGPM('AMV1' GLOBAL DESCRIPTION: This file holds data for all admissions, transfers, discharges, treating specialty changes, and lodger movements. GLOBAL REFERENCE: DGPM('APTT1' GENERAL DESCRIPTION: Outpatient Pharmacy package request permission to read the 'AMV1' and 'APTT1' cross references of REGISTRATION file 405. STATUS: Active MAIL MESSAGE: 25725246 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2250 IA #: 2250 FILE NUMBER: 49 GLOBAL ROOT: DIC(49, DATE CREATED: DEC 09, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2250 ID: DIC(49, CREATOR: BEUSCHEL,GARY GLOBAL REFERENCE: DIC(49,DA GLOBAL DESCRIPTION: Outpatient needs the Internal numbers of entries in this file to determine the correct entry for generating Pharmacy Copay charges. GLOBAL REFERENCE: DIC(49, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Outpatient needs the Internal numbers of entries in this file to determine the correct entry for generating Pharmacy CoPay charges. GENERAL DESCRIPTION: Outpatient Pharmacy requests permission to access data in the SERVICE/SECTION (#49) file. One use will be to loop through the file to retrieve internal entry numbers to be used for a call to Integrated Billing to find the correct entry necessary to process Co-pay prescriptions in Pharmacy. Another will be to access the names of the file entries in order to provide complete demographic information for an outpatient site through the Pharmacy Reengineering APIs. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 53622926 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham DATE ACTIVATED: JAN 21, 2011 DATE/TIME EDITED: JAN 20, 2011@09:18 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: SILVERMAN,ROBERT DATE/TIME EDITED: JAN 24, 2011@16:09 ACTION: APPROVED AT THE REQUEST OF: SILVERMAN,ROBERT WITH CONCURRENCE OF: BEUSCHEL,GARY NUMBER: 2251 IA #: 2251 FILE NUMBER: 4 GLOBAL ROOT: DIC(4 DATE CREATED: AUG 25, 2003 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA-2251 ID: DIC(4 GLOBAL REFERENCE: DIC(4, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the name of the Institution. FIELD NUMBER: 99 FIELD NAME: STATION NUMBER LOCATION: 99;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5 FIELD NAME: MULTI-DIVISION FACILITY LOCATION: DIV;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: This file contains a listing of VA institutions. GENERAL DESCRIPTION: Outpatient Pharmacy package request permission to look at INSTITUTION file 4 to get the Institution name and/or station number. STATUS: Active SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: EVENT CAPTURE SUBSCRIBING DETAILS: ADDED 2/28/2012 DATE/TIME EDITED: FEB 29, 2012@13:49 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: NABER,DAVID WITH CONCURRENCE OF: BEUSCHEL,GARY NUMBER: 2252 IA #: 2252 FILE NUMBER: 7 GLOBAL ROOT: DIC(7, DATE CREATED: DEC 16, 1997 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2252 ID: DIC(7, GENERAL DESCRIPTION: This request is so that the Laboratory Package to be able to read from the ^DIC(7, global. The purpose of this would be to take the second piece of the zero node, ^DIC(7,D0,0)= (#.01) NAME [1F] ^ (#1) ABBREV. TITLE [2F] ^ to append onto the Pathologist's Name on the various Pathology reports. This should be a temporary request and can be revisited when the Anatomic Pathology reports incorporate electronic signature. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25746740 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 2253 IA #: 2253 FILE NUMBER: 55.06 GLOBAL ROOT: DD(55.06, DATE CREATED: DEC 30, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED ROUTINE: DIC NAME: DBIA2253 ID: DIC GENERAL DESCRIPTION: Inpatient Medications requests permission to call routine ^DIC with the variable DIC defined as "^DD(55.06," and DIC(0)="QEM" or DIC(0)="QE". This will perform a lookup on the field names of a particular file and return the needed variables. This is used in our routines to allow a user to up-arrow jump to another field during the editing of an order. Example: The user is editing an order and enters "^STA". The ^DIC lookup is performed, finds the START DATE field, and returns the field's internal entry number. That number is then used to go to the appropriate code to edit that field. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25867394 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2255 IA #: 2255 FILE NUMBER: 0 GLOBAL ROOT: DD( DATE CREATED: DEC 30, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2255 ID: DD( GLOBAL REFERENCE: DD(file #,field #,12) FIELD NUMBER: 12 FIELD NAME: POINTER SCREEN ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Pointer Screen description for the field. GENERAL DESCRIPTION: Inpatient Medications requests direct read access to pharmacy files node ^DD(file #,field #,12). We are reading from this node to return the POINTER SCREEN description. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25867804 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2256 IA #: 2256 FILE NUMBER: 53.1 GLOBAL ROOT: DD(53.1 DATE CREATED: DEC 31, 1997 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2256 ID: DD(53.1 GENERAL DESCRIPTION: Inpatient Medications requests permission to call routine ^DIC with the variable DIC defined as "^DD(53.1," and DIC(0)="QEM". This will perform a lookup on the field names of a particular file and return the needed variables. This is used in our routines to allow a user to up-arrow jump to another field during the editing of an order. Example: The user is editing an order and enters "^STA". The ^DIC lookup is performed, finds the START DATE field, and returns the field's internal entry number. That number is then used to go to the appropriate code to edit that field. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25874180 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2257 IA #: 2257 DATE CREATED: JAN 06, 1998 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOBUILD NAME: DBIA2257 ID: PSOBUILD GENERAL DESCRIPTION: Inpatient Medications requests permission to call INPAT^PSOBUILD. This entry point is used to display a patient's current Outpatient medications. Input variable: PSODFN Output variable: STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25908805 COMPONENT/ENTRY POINT: INPAT COMPONENT DESCRIPTION: This entry point will display a patient's current Outpatient Medications. VARIABLES: PSODFN TYPE: Input VARIABLES DESCRIPTION: Patient's IEN in ^DPT(. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2258 IA #: 2258 DATE CREATED: JAN 06, 1998 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOVWI NAME: DBIA2258 ID: PSOVWI GENERAL DESCRIPTION: Inpatient Medications requests permission to call ^PSOVWI (Outpatient Pharmacy). This entry point is used to display a Pharmacy intervention in a captioned format. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25909243 COMPONENT/ENTRY POINT: PSOVWI (top of routine) COMPONENT DESCRIPTION: This entry point is used to display a Pharmacy intervention in a captioned format. VARIABLES: PSOVWI TYPE: Input VARIABLES DESCRIPTION: PSOVWI("DIC"). The global root for DIC. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2259 IA #: 2259 DATE CREATED: JAN 06, 1998 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2259 GENERAL DESCRIPTION: Inpatient Medications requests permission to use the following Outpatient Pharmacy templates. These templates are used by Inpatient Medications to Enter, Edit, and Print Pharmacy interventions. Input Template [PSO INTERVENTION EDIT] [PSO INTERVENTION NEW] Print Template [PSO INTERVENTIONS] Sort Template [PSO INTERVENTIONS] These templates are used by the following Inpatient Medication protocols: PSJ LM INTERVENTION EDIT PSJ LM INTERVENTION NEW ENTRY PSJ LM INTERVENTION PRINTOUT PSJ LM INTERVENTION VIEW STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25915717 COMPONENT/ENTRY POINT: PSO INTERVENTIONS COMPONENT DESCRIPTION: This print and sort template is used to print Pharmacy Interventions for a certain date range. COMPONENT/ENTRY POINT: PSO INTERVENTION NEW COMPONENT DESCRIPTION: This input template is used to enter Pharmacy Interventions. COMPONENT/ENTRY POINT: PSO INTERVENTION EDIT COMPONENT DESCRIPTION: This input template is used to edit already existing Pharmacy Interventions. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2260 IA #: 2260 DATE CREATED: JAN 09, 1998 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSORX1 NAME: DBIA1030-D ID: PSORX1 GENERAL DESCRIPTION: This entry point is used to build an Outpatient prescription profile for a patient. The profile is returned in the form of an array, named PSOSD. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25955003 COMPONENT/ENTRY POINT: PROFILE COMPONENT DESCRIPTION: This entry point returns an Outpatient prescription profile in the form of a PSOSD array. VARIABLES: PSODFN TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number of the patient. This variable will be unchanged in this component. VARIABLES: PSOSD TYPE: Output VARIABLES DESCRIPTION: This is the array which contains the current prescriptions for the patient. It also contains current Pending orders that are in the PENDING OUTPATIENT ORDERS File (#52.41) for the patient. The variable PSOSD will be equal to the number of entries in the array. The pieces of the array are described after the following 2 examples. PSOSD("ACTIVE","CEFOPERAZONE 1GM INJ")=2050^5^^Z^AM103^10^820A1^30^ PSOSD("PENDING","METYRAPONE 250GM TAB")=*****^17^Z^Z^DX900^0^1132A1^90^29712 12.121545^1068^128 The first example, for CEFOPERAZONE 1GM INJ, is an active prescription. The pieces are as follows: Piece 1 - Internal number from the PRESCRIPTION File (#52). Piece 2 - Status code from the Status field of the PRESCRIPTION File (#52). Piece 3 - Free text set of characters used for different classifications of the drug (not applicable to the functions of this agreement). Piece 4 - Free text set of characters used to identify site parameters and drug characteristics. Piece 5 - VA classification of the drug. Piece 6 - Refills remaining for the prescription. Piece 7 - National Drug File information, in the form of National Drug File entry_"A"_VA Product Name entry. Piece 8 - Days supply of the prescription. The second example, for METYRAPONE 250MG TAB, is a Pending Outpatient ordered, not yet finished. The pieces are as follows: Piece 1 - Always ***** for a Pending order. Piece 2 - Always 17 for a Pending order. (Indicates Pending order status) Piece 3 - Always Z for a Pending order. Piece 4 - Always Z for a Pending order. Piece 5 - VA classification of the drug. Piece 6 - Number of refills requested by the ordering person. Piece 7 - National Drug File information, in the form of National Drug File entry_"A"_VA Product Name entry. Piece 8 - Quantity requested by the ordering person. Piece 9 - Effective date of the order. Piece 10 - Internal entry number from the PENDING OUTPATIENT ORDERS File (#52.41). Piece 11 - Internal entry number from the DRUG File (#50). SUBSCRIBING PACKAGE: VENDOR - AUDIOFAX, INC. SUBSCRIBING PACKAGE: VENDOR - TECHPRO SYSTEMS INC NUMBER: 2261 IA #: 2261 DATE CREATED: JAN 09, 1998 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSNPPIP NAME: Print Med Instruction Sheet ID: PSNPPIP GENERAL DESCRIPTION: This IA will be used in the Outpatient Pharmacy package to print medication instruction sheets. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 25942859 COMPONENT/ENTRY POINT: PSNPPIP COMPONENT DESCRIPTION: The top level entry point will be used to allow any instruction sheet to be printed for any selected drug. The user will be prompted for a drug name. COMPONENT/ENTRY POINT: ENOP COMPONENT DESCRIPTION: This entry point will be used to pass in an internal number of a drug. The ENOP is an entry point where variables are passed. Variables: Drug IFN - required Trade Name - optional Internal Rx number - optional Patient's IFN - optional VARIABLES: DRUG IEN TYPE: Input VARIABLES DESCRIPTION: Internal entry number of drug from file 50. VARIABLES: Trade Name TYPE: Used VARIABLES DESCRIPTION: This free text variable is printed as part of the header info. on the medication instruction sheet. VARIABLES: PSNPPI("MESSAGE") TYPE: Output VARIABLES DESCRIPTION: This variable is only returned if there's no information available to print on the drug entered/selected. If this variable is returned the message will be diplayed to the user and killed after display. VARIABLES: Rx Number TYPE: Used VARIABLES DESCRIPTION: This variable is used to print the Rx number as part of the header. VARIABLES: PSODFN TYPE: Used VARIABLES DESCRIPTION: This variable is passed as the internal entry for the patient from file #2. SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2263 IA #: 2263 DATE CREATED: JAN 11, 1998 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XPAR NAME: SUPPORTED PARAMETER TOOL ENTRY POINTS ID: XPAR CREATOR: DIMICELI,RON GENERAL DESCRIPTION: Parameter Tools is a generic method of handling parameter definition, assignment, and retrieval. A parameter may be defined for various entities where an entity is the level at which you want to allow the parameter defined (e.g. package level, system level, division level, location level, user level, etc.). A developer may then determine in which order the values assigned to given entities are interpreted. The following are some basic definitions used by Parameter Tools: Entity: ======= An entity is a level at which you can define a parameter. The entities allowed are stored in the Parameter Entity file (#8989.518). The list of allowable entities at the time this utility was released were: Prefix Message Points to File ------- ---------- ------------------------ PKG Package Package (9.4) SYS System Domain (4.2) DIV Division Institution (4) SRV Service Service/Section (49) LOC Location Hospital Location (44) TEA Team Team (404.51) CLS Class Usr Class (8930) USR User New Person (200) BED Room-Bed Room-Bed (405.4) OTL Team (OE/RR) OE/RR List (101.21) (Note: entries will be maintained via ToolKit patches. Entries existing in the file at the time it is referenced are considered supported.) Parameter: ========== A parameter is the actual name which values are stored under. The name of the parameter must be namespaced and it must be unique. Parameters can be defined to store the typical package parameter data (e.g. the default add order screen in OE/RR), but they can also be used to store GUI application screen settings a user has selected (e.g. font or window width). When a parameter is defined, the entities which may set that parameter are also defined. The definition of parameters is stored in the PARAMETER DEFINITION file (#8989.51). Value: ====== A value may be assigned to every parameter for the entities allowed in the parameter definition. Values are stored in the PARAMETERS file (#8989.5). Instance: ========= Most parameters will set instance to 1. Instances are used when more than one value may be assigned to a given entity/parameter combination. An example of this would be lab collection times at a division. A single division may have multiple collection times. Each collection time would be assigned a unique instance. Parameter Template: =================== A parameter template is similar to an input template. It contains a list of parameters that can be entered through an input session (e.g. option). Templates are stored in the Parameter Template file (#8989.52). Entries in this file must also be namespaced. This integration agreement defines the callable entry points in routine XPAR. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 36985706 COMPONENT/ENTRY POINT: EN(Entity,Parameter,Instance,Value,.Error) COMPONENT DESCRIPTION: This entry point will: 1) add the value as a new entry to the Parameters file if the Entity/Parameter/Instance combination does not already exist. 2) change the value assigned to the parameter if the Entity/Parameter/Instance combination already exists. or 3) delete the parameter instance if the value assigned is "@". VARIABLES: Entity TYPE: Input VARIABLES DESCRIPTION: REQUIRED The entity may be set to: 1) the internal variable pointer (nnn;GLO(123,) 2) the external format of the variable pointer using the 3 character prefix (prefix.entryname) or 3) the prefix alone to set the parameter based on current entity selected. This will work for the following entities: "USR" - uses current value of DUZ "DIV" - uses current value of DUZ(2) "SYS" - uses system (domain) "PKG" - uses the package to which the parameter belongs VARIABLES: Parameter TYPE: Input VARIABLES DESCRIPTION: REQUIRED Identifies the name or internal entry number of the parameter as defined in the PARAMETER DEFINITION file (#8989.51). VARIABLES: Instance TYPE: Input VARIABLES DESCRIPTION: OPTIONAL (defaults to 1 if not passed in) May be passed in external or internal format. Internal format requires that the value be preceded by the ` character). VARIABLES: Value TYPE: Input VARIABLES DESCRIPTION: REQUIRED May be passed in external or internal format. If using internal format for a pointer type parameter, the value must be preceded with the ` character.). If the value is being assigned to a word processing parameter, the text may be passed in the subordinate nodes of Value (e.g. Value(1,0)=Text) and the variable Value itself may be defined as a title or description of the text. VARIABLES: Error TYPE: Output VARIABLES DESCRIPTION: OPTIONAL If used, must be passed in by reference. It will return any error condition which may occur. If no error occurs, the value assigned will be 0 (zero). If an error does occur, it will be in the format: "#^errortext". COMPONENT/ENTRY POINT: ADD(Entity,Parameter,Instance,Value,.Error) COMPONENT DESCRIPTION: This entry point can be called to add a new parameter value. For definition of input and output variables, see component EN description. VARIABLES: Entity TYPE: Input VARIABLES: Parameter TYPE: Input VARIABLES: Instance TYPE: Input VARIABLES: Value TYPE: Input VARIABLES: Error TYPE: Output COMPONENT/ENTRY POINT: CHG(Entity,Parameter,Instance,Value,.Error) COMPONENT DESCRIPTION: This entry point can be called to change an existing parameter value. For definition of input and output variables, see component EN description. VARIABLES: Entity TYPE: Input VARIABLES: Parameter TYPE: Input VARIABLES: Instance TYPE: Input VARIABLES: Value TYPE: Input VARIABLES: Error TYPE: Output COMPONENT/ENTRY POINT: DEL(Entity,Parameter,Instance,.Error) COMPONENT DESCRIPTION: This entry point can be called to delete an existing parameter value. For definition of input and output variables, see component EN description. VARIABLES: Entity TYPE: Input VARIABLES: Parameter TYPE: Input VARIABLES: Instance TYPE: Input VARIABLES: Error TYPE: Output COMPONENT/ENTRY POINT: NDEL(Entity,Parameter,.Error) COMPONENT DESCRIPTION: This entry point can be called to delete the value for all instances of a parameter for a given entity. For definition of input and output variables, see component EN description. COMPONENT/ENTRY POINT: REP(Entity,Parameter,CurrentInstance,NewInstance,.Error) COMPONENT DESCRIPTION: This entry point will allow a developer to replace the value of an instance with another value. VARIABLES: Entity TYPE: Input VARIABLES DESCRIPTION: See EN^XPAR component for description. VARIABLES: Parameter TYPE: Input VARIABLES DESCRIPTION: See EN^XPAR component for description. VARIABLES: CurrentInstance TYPE: Input VARIABLES DESCRIPTION: REQUIRED: The instance for which the value is currently defined. VARIABLES: NewInstance TYPE: Input VARIABLES DESCRIPTION: REQUIRED The instance for which you want to assign the value currently assigned to CurrentInstance. VARIABLES: Error TYPE: Output VARIABLES DESCRIPTION: See EN^XPAR component for description. COMPONENT/ENTRY POINT: $$GET(Entity,Parameter,Instance,Format) COMPONENT DESCRIPTION: This call will allow you to retrieve the value of a parameter. The value is returned from this extrinsic function in the format defined by the variable Format (see below). VARIABLES: Entity TYPE: Input VARIABLES DESCRIPTION: Entity is defined as the single entity or group of entities you want to look at in order to retrieve the value. Entities may be passed in internal or external format (e.g. LOC.PULMONARY or LOC.'57 or 57;SC(). The list of entities in this variable may be defined as follows: 1) a single entity to look at (e.g. LOC.PULMONARY). 2) the word "ALL" which will tell the utility to look for values assigned to the parameter using the entity precedence defined in the PARAMETER DEFINITION file. 3) A list of entities you want to search (e.g. "USR^LOC^SYS^PKG"). The list is searched from left to right with the first value found returned. 4) Items 2 or 3 with specific entity values referenced such as: ALL^LOC.PULMONARY - to look at the defined entity precedence, but when looking at location, only look at the PULMONARY location. USR^LOC.PULMONARY^SYS^PKG - to look for values for all current user, PULMONARY location, system, or package). VARIABLES: Parameter TYPE: Input VARIABLES DESCRIPTION: REQUIRED Identifies the name or internal entry number of the parameter as defined in the PARAMETER DEFINITION file (#8989.51). VARIABLES: Instance TYPE: Input VARIABLES DESCRIPTION: OPTIONAL (defaults to 1 if not passed in) May be passed in external or internal format. Internal format requires that the value be preceded by the ` character). VARIABLES: Format TYPE: Input VARIABLES DESCRIPTION: OPTIONAL - defaults to "Q" if not defined Format determines how the value is returned. It can be set to the following: 1) "Q" - returns the value in the quickest manner - internal format 2) "E" - returns external value 3) "I" - returns internal value 4) "B" - returns internal^external value COMPONENT/ENTRY POINT: GETLST(.List,Entity,Parameter,Format,.Error[,gbl]) COMPONENT DESCRIPTION: This entry point is similar to $$GET^XPAR, but this will return ALL instances of a parameter. VARIABLES: List TYPE: Output VARIABLES DESCRIPTION: The array passed as List will be returned with all of the possible values assigned to the parameter. See variable description for Format to see how this data can be returned. If the parameter gbl is set to one, Then this parameter becomes a input and holds the closed root of a global where GETLST should put the output. e.i. $NA(^TMP($J,"XPAR")). VARIABLES: Entity TYPE: Input VARIABLES DESCRIPTION: See description of this variable under $$GET component. VARIABLES: Parameter TYPE: Input VARIABLES DESCRIPTION: See description of this variable under $$GET component. VARIABLES: Error TYPE: Output VARIABLES DESCRIPTION: Returns 0 if no error was encountered or returns an error code in the format #^errortext. VARIABLES: Format TYPE: Input VARIABLES DESCRIPTION: This variable defines how the data is returned from this call. The data will be returned in the array specified by the variable List. Possible values for Format are: 1) "Q" List(#)=internal instance^internal value 2) "I" List(internal instance)=internal value 3) "E" List(#)=external instance^external value 4) "B" List(#,"N")=internal instance^external instance List(#,"V")="internal value^external value 5) "N" List(external instance)=internal value^external value VARIABLES: gbl TYPE: Input VARIABLES DESCRIPTION: If this optional variable is set to 1. Then the parameter List must be set before the call to the closed global root where the return data should be put. e.i. GETLST^XPAR($NA(^TMP($J)),ent,par,fmt,.error,1) COMPONENT/ENTRY POINT: GETWP(.ReturnedText,Entity,Parameter,Instance,.Error) COMPONENT DESCRIPTION: This call returns word processing text in ReturnedText. ReturnedText itself contains the value field, which is free text that may contain a title, description, etc. The word processing text is returned in ReturnedText(#,0). VARIABLES: ReturnedText TYPE: Both VARIABLES DESCRIPTION: This variable is defined as the name of an array in which you want the text returned. .ReturnedText will be set to the title, description, etc. The actual word processing text will be returned in ReturnedText(#,0). Example: ReturnedText="Select Notes Help" ReturnedText(1,0)="To select a progress note from the list, " ReturnedText(2,0)="click on the date/title of the note." VARIABLES: Entity TYPE: Input VARIABLES DESCRIPTION: See description of variable under $$GET call. VARIABLES: Parameter TYPE: Input VARIABLES DESCRIPTION: See description of variable under $$GET call. VARIABLES: Instance TYPE: Input VARIABLES DESCRIPTION: See description of variable under $$GET call. VARIABLES: Error TYPE: Output VARIABLES DESCRIPTION: See description of this variable under the GETLST component. COMPONENT/ENTRY POINT: ENVAL(.List,Parameter,Instance,.Error[,gbl]) COMPONENT DESCRIPTION: This entry point will return all parameter instances. See GETLST and $$GET for a definition of input and output variables to this call. VARIABLES: List TYPE: Output VARIABLES DESCRIPTION: If the parameter gbl is set to one, Then this parameter becomes a input and holds the closed root of a global where GETLST should put the output. e.i. $NA(^TMP($J,"XPAR")). VARIABLES: Parameter TYPE: Input VARIABLES DESCRIPTION: (required) See description of variable under EN^XPAR() call. VARIABLES: Instance TYPE: Input VARIABLES DESCRIPTION: (required) See description of variable under EN^XPAR() call. VARIABLES: Error TYPE: Output VARIABLES DESCRIPTION: (optional) See description of variable under EN^XPAR() call. VARIABLES: gbl TYPE: Input VARIABLES DESCRIPTION: If this optional variable is set to 1. Then the parameter List must be set before the call to the closed global root where the return data should be put. e.i. S LIST=$NA(^TMP($J)) ENVAL^XPAR(LIST,par,inst,.error,1) COMPONENT/ENTRY POINT: PUT(Entity,Parameter,Instance,Value,.Error) COMPONENT DESCRIPTION: This entry point can be called to add or update a parameter instance and bypass the input transforms. VARIABLES: Entity TYPE: Input VARIABLES DESCRIPTION: (required) See description of variable under EN^XPAR() call. VARIABLES: Parameter TYPE: Input VARIABLES DESCRIPTION: (required) See description of variable under EN^XPAR() call. VARIABLES: Instance TYPE: Input VARIABLES DESCRIPTION: (optional) See description of variable under EN^XPAR() call. VARIABLES: Value TYPE: Input VARIABLES DESCRIPTION: (required) See description of variable under EN^XPAR() call. VARIABLES: Error TYPE: Output VARIABLES DESCRIPTION: (optional) See description of variable under EN^XPAR() call. DBA Comments: 11/7/12 DT: Ron DiMiceli, Kernel Developer, requested edit access because one of the parameters is not documented. 11/9/12 DT: Ron DiMiceli completed edits. There is no patch related to the edits. This is a correction. DATE ACTIVATED: NOV 09, 2012 DATE/TIME EDITED: NOV 07, 2012@11:50 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: DIMICELI,RON DATE/TIME EDITED: NOV 09, 2012@12:35 ACTION: APPROVED AT THE REQUEST OF: DIMICELI,RON NUMBER: 2264 IA #: 2264 FILE NUMBER: 3.7 GLOBAL ROOT: XMB(3.7, DATE CREATED: JAN 12, 1998 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2264 ID: XMB(3.7, GLOBAL REFERENCE: XMB(3.7,M,XMZ,XMDUZ,BASKET,NUMBER) GENERAL DESCRIPTION: Clinical Reminders (PCE) would like to use : ^XMB(3.7,"M",XMZ,XMDUZ,BASKET,NUMBER) as part of a DIC lookup screen in an application that lets sites exchange reminder definitions via MailMan messages. The lookup is done on ^XMB(3.9) and the screen is used to filter out messages that have been deleted i.e., they are not in a basket. STATUS: Active MAIL MESSAGE: 25957805 SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 2266 IA #: 2266 DATE CREATED: JAN 20, 1998 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RAO7PC1 NAME: Rad/Nuc Med return report narrative text (order) ID: RAO7PC1 CREATOR: CEBELINSKI,GREGORY GENERAL DESCRIPTION: EN30^RAO7PC1 can be used to return report narrative text associated with a patient's order. *************************************************************************** ***************** REASON FOR STUDY data will NOT be available until AFTER ***************** the release of patch RA*5.0*75 by the RADIOLOGY product. ************************************************************************* STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32100435 GOOD ONLY FOR VERSION: SEE ALERT COMPONENT/ENTRY POINT: EN30(RAOIFN) COMPONENT DESCRIPTION: ** Please note that REASON FOR STUDY data will not be captured until the release of RA*5.0*75 ** EN30^RAO7PC1(RAOIFN) Input: RAOIFN = Internal entry number (IEN) of the order requested. Output: ^TMP($J,"RAE2",patient IEN,case IEN,procedure name)=report status^abnormal flag^CPRS Order IEN subscripts ---------- Patient IEN: IEN of the patient in both the Rad/Nuc Med Patient file #70 and the Patient file #2. Case IEN: IEN of the exam this data is extracted from. Procedure Name: Name of the procedure in the Rad/Nuc Med Procedure file #71. It is possible for users to change the procedure prior to the exam reaching a 'COMPLETE' status. array value (in ascending piece position) ----------------------------------------- Report Status: External name of the report status. Possible statuses include: DRAFT, PROBLEM DRAFT, RELEASED/NOT VERIFIED, VERIFIED and NO REPORT. It is possible for the exam to have a report ien with a 'NO REPORT' status. A 'NO REPORT' status refers to a stub report that was created for the Imaging package file of images, this stub report record has no data entered by Radiology/Nuclear Medicine staff. Abnormal Alert Flag: Will be set to "Y" if the Primary Dx Code or Secondary Dx Code (if any) associated with this exam specifies that an Abnormal Alert be generated. Will be null if present Dx Codes do not specify Abnormal Alert generation. CPRS Order IEN: This is a pointer data type that indicates the record number of the order in the Order Entry/Results Reporting (OE/RR) package. This piece will be non-null if the OE/RR package is running and the Radiology/Nuclear Medicine package is available through OE/RR. Additional output ----------------- Note: The subscripts used in these data arrays are used in the data globals listed below. For subscript definitions, check section called 'subscripts' listed above. ^TMP($J,"RAE2",patient IEN,case IEN,procedure name,"D",n) Array Value ----------- Diagnostic code (n=1, this is the primary Dx returned in a brief text format) ^TMP($J,"RAE2",patient IEN,case IEN,procedure name,"H",n) Array Value ----------- Clinical History (a line of text) ^TMP($J,"RAE2",patient IEN,case IEN,procedure name,"I",n) Array Value ----------- Impression Text (a line of text) ^TMP($J,"RAE2",patient IEN,case IEN,procedure name,"M",n) Array Value ----------- Modifier(s) (external format) ^TMP($J,"RAE2",patient IEN,case IEN,procedure name,"R",n) Array Value ----------- Report Text (a line of text) ^TMP($J,"RAE2",Patient IEN,case IEN,procedure name,"RFS") Array Value ----------- Reason for Study (a line of text) ^TMP($J,"RAE2",Patient IEN,case IEN,procedure name,"CM",n) Array Value ----------- If applicable, the contrast media used during exam. Format: internal value^external value ^TMP($J,"RAE2",patient IEN,case IEN,procedure name,"V") Array Value (in ascending piece position) -------------------------------- Verifier IEN: IEN of the physician verifying the report. Signature Block Name: The name of the user as they wish it to appear with the notation that they signed the document electronically. ^TMP($J,"RAE2",patient IEN,"PRINT_SET") Array Value ----------- Null (exists iff this is a printset) ^TMP($J,"RAE2",patient IEN,"ORD") Array Value ----------- Name of ordered parent procedure for examsets and printsets. ^TMP($J,"RAE2",patient IEN,"ORD",case IEN) Array Value ----------- Name of orderer procedure, this may differ from the procedure registered. This global will be defined when the ordered procedure is not a parent procedure. (Not an examset or printset) ^TMP($J,"RAE2",patient IEN,case IEN,procedure name,"TCOM",1) Array value ----------- most recent technologist comment for this case DBA Comments: JSHARVEY 20061214/ DEACTIVATED FOR EDITING BY GREG CEBELINSKI JSHARVEY 20060130/ RE-ACTIVATION OF THIS AGREEMENT IS PENDING RELEASE OF JSHARVEY 20080220/ REACTIVATED PATCH *75. DATE ACTIVATED: FEB 20, 2008 DEFERRED UNTIL: MAR 28, 2007 DATE/TIME EDITED: JAN 31, 2007@01:17 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CEBELINSKI,GREG DATE/TIME EDITED: MAR 04, 2007@21:43 ACTION: POSTPONED UNTIL PATCH RELEASE DATE/TIME EDITED: FEB 20, 2008@09:00 ACTION: APPROVED AT THE REQUEST OF: CEBELINSKI,GREG NUMBER: 2267 IA #: 2267 DATE CREATED: JAN 20, 1998 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RAO7PC1 NAME: Rad/Nuc Med return imaging location information ID: RAO7PC1 GENERAL DESCRIPTION: EN4^RAO7PC1 can be used to return a list of valid, active imaging locations within a particular imaging type. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26527639 COMPONENT/ENTRY POINT: EN4(RABBRV,RAARY) COMPONENT DESCRIPTION: EN4^RAO7PC1(RABBRV,RAARY) Input: RABBRV = The abbreviation of the imaging type as it appears in the Imaging Type file #79.2. (Examples: ANI, CARD, CT, MAM, MRI, NM, RAD US and VAS) RAARY = This is the local array name in which the subscribing package would like the data returned. Returns a list of valid, active imaging locations associated with a specific imaging type. Output: local_array_name(file #79.1 ien)=ien Imaging Locations file #79.1^Hospital Location Name^ien Rad/Nuc Med Division file #79^ Division Name (from file #4) subscripts ---------- file #79.1 ien: The internal entry number of the record in the Imaging Locations file. array value (in ascending order) -------------------------------- ien Imaging Locations file #79.1: The internal entry number of the record in the Imaging Locations file. Hospital Location Name: The name of the Hospital Location. This is derived from the Imaging Locations file #79.1 entry. The Imaging Locations file #79.1 points to the Hospital Location file #44. ien Rad/Nuc Med Division file #79: The internal entry number of the record in the Rad/Nuc Med Division file. Division Name: The name of the Rad/Nuc Med Division. The Rad/Nuc Med Division file points to the Institution file #4. The division name is taken from the Institution file. The Rad/Nuc Med Division file #79 is DINUMED to the Institution file #4. EDITOR: CEBELINSKI,GREGORY NUMBER: 2268 IA #: 2268 DATE CREATED: JAN 20, 1998 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RAO7PC1 NAME: Rad/Nuc Med exam case numbers linked to an order ID: RAO7PC1 GENERAL DESCRIPTION: CASE^RAO7PC1 is an extrinsic function that can be used to retrieve the exam case numbers associated with an order. It returns the case numbers, the total number of exams linked to the order, and a flag indicating whether these exams are linked to a single report. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31070114 COMPONENT/ENTRY POINT: CASE(RAOIFN,RARRAY) COMPONENT DESCRIPTION: CASE^RAO7PC1(RAOIFN,RARRAY) Input: RAOIFN = Internal entry number of the order requested. RARRAY = This is the local array name in which the subscribing package would like data returned. Returns an array subscripted by case number(s) for non-cancelled exam(s) associated with the order. It also returns a string in which the first piece is the number of exam(s) linked to the order. The second piece indicates whether or not the exam(s) are part of a printset. Output: local_array_name(case number)=total number of exams -or- error code^printset -or- error code text subscripts ---------- Case Number: This is the case number of the non-cancelled exam linked to an order. All registered exams have case numbers. array value (in ascending order) -------------------------------- First Piece: This can be a positive number indicating the number of exam(s) registered for a single order. It also may be an error code. For example, if an order is requested for an exam set, and we register three exams, the first piece would be a three. An error code of '-1' will exist if the order number is invalid. An error code of '-2' will exist if all the exams for this order are cancelled, or if we have not registered exams for the order at the time of the data extract. Second Piece: If the second piece equals the string, 'PRINTSET', the exams are part of a special exam set. The PRINTSET links all the exams of an exam set to a single report. If the first piece is a negative number, then the second piece defines the error code. Examples: 'cases cancelled', 'no case registered to date' or 'invalid order ien' are valid error code descriptors. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City EDITOR: CEBELINSKI,GREGORY NUMBER: 2269 IA #: 2269 FILE NUMBER: 40.8 GLOBAL ROOT: DG(40.8, DATE CREATED: JAN 23, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2269 ID: DG(40.8, GLOBAL REFERENCE: DG(40.8, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: The Inpatient Medications IV ROOM file (#59.5), DIVISION field (#.02) points to ^DD(40.8,.01). The Inpatient Medications field is populated by an option on the DSS Extracts menu. It is solely for use by the DSS software and has no impact on Pharmacy at this time. This field in Inpatient Medications supports DBIA #1849 for the DSS Extracts package. GENERAL DESCRIPTION: Inpatient Medications requests permission to have a field defined in the IV ROOM file (#59.5) that points to the MEDICAL CENTER DIVISION file (#40.8). This field contains the division where the IV Room is located. The Inpatient Medications field is populated by an option on the DSS Extracts menu. It is solely for use by the DSS software and has no impact on Pharmacy at this time. This field in Inpatient Medications supports DBIA #1849 for the DSS Extracts package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26053742 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL SUBSCRIBING DETAILS: Referenced by the DIVISION (#11) field in the BENEFICIARY TRAVEL CLAIM file 392. NUMBER: 2270 IA #: 2270 DATE CREATED: JAN 23, 1998 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: HLSUB NAME: Subscription Management ID: HLSUB GENERAL DESCRIPTION: The following API's support creation, references, and updates to HL7 subscriptions using the SUBSCRIPTION CONTROL FILE (774). In addition, Vista applications may set up a pointer to file 774 if needed. An example of this can be found in the Patient file. See the CIRN documentation for details on how this is used. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26057894 COMPONENT/ENTRY POINT: $$ACT COMPONENT DESCRIPTION: $$ACT^HLSUB Purpose: Request a new Subscription Control Number Example: KRN,KDE>S X=$$ACT^HLSUB KRN,KDE>W X 2 COMPONENT/ENTRY POINT: UPD COMPONENT DESCRIPTION: UPD^HLSUB(HLSCN,HLNN,HLTP,HLAD,HLTD,HLRAP,.HLER) Purpose: Subscription Update-add/edit a subscriber Input: HLSCN=Subscription Control Number (required) HLNN=Logical Link name in file 870 (required) HLTP=Subscription Type (required) 0=descriptive updates only 1=clinical updates 2=other (locally defined) HLAD=Activation date (optional), defaults to 'now' HLTD=Termination date (optional), default is 'open-ended' HLRAP=HL7 receiving application HLER=error message(s) Notes: a. The ACTIVATION DATE and TERMINATION DATE fields can be pre-determined by the subscriber. b. Setting the TERMINATION DATE field is optional. Setting this field is effectively setting an expiration date for the subscriber. Messages will no longer be delivered to this network node as long as the current date is later than the termination date. If the current subscription has a Termination Date set and the subscriber changes their mind, the date can be changed or deleted with a new subscription update message. The current termination date will be deleted when the variable HLTD is set to 'null.' c. The Subscription Control Number and the Destination multiple are UNEDITABLE fields. d. All modifications to existing subscriber records using this call results in an update of the Subscriber History multiple. Example: a. KRN,KDE>D UPD^HLSUB(1,"TEST-LLP",1,"4/29/1997@10:27:57","","CIRN",.HLER) b. INQUIRE TO FILE ENTRIES: DESTINATION: CIRN@TEST LLP RECEIVING APPLICATION: CIRN LOGICAL LINK: TEST LLP TYPE: Patient Clinical and Descriptive CREATION DATE/TIME: APR 29, 1997@10:27:57 ACTIVATION DATE/TIME: APR 29, 1997@10:27:57 MODIFICATION DATE/TIME: APR 29, 1997@10:27:57 LAST CREATION DATE/TIME: APR 29, 1997@10:25:07 LAST ACTIVATION DATE/TIME: APR 29, 1997@10:25:07 LAST SUBSCRIPTION TYPE: Patient Clinical and Descriptive COMPONENT/ENTRY POINT: GET COMPONENT DESCRIPTION: GET^HLSUB(HLSCN,HLTP,HLCL,.HLL) Purpose: Return active subscriber information Input: HLSCN=Subscription control number HLTP=Subscription type (optional) HLCL=HL7 Client Protocol (optional) HLL=Array of current subscribers (passed by reference) Output: HLL("LINKS",n)=CLIENT PROTOCOL^LOGICAL LINK^TYPE^CREATION DATE^ACTIVATION DATE^TERMINATION DATE Notes: a. When HLTP is 'null' all subscribers are returned. b. Multiple calls can be made to GET. For example, to route a message to both Clinical and Descriptive subscribers, the first call would have HLTP set to '0', and in the second call it would be set to '1.' If the HLL array already exists, it will be appended to. c. The HL7 Package requires the HLL array to contain both the HL7 Client Protocol and the Logical Link. In this call, the Client Protocol is optional. If you pass in the Protocol name, it will be returned in the first piece of the array. If you are making this call specifically to dynamically route a message, submit the Client Protocol. If you make this call to retrieve other information about the subscriber, the first piece of the HLL array will be null. Examples: (1) Return all subscriber information for SCN #1 KRN,KDE>K HLL D GET^HLSUB(1,,,.HLL) KRN,KDE>ZW HLL HLL("LINKS",1)=^INDY-TCP^RG SUBSCRIPTION@INDY-TCP^9^^23^1^2970501.184903^2970501.184903 (2) Return all subscribers using multiple calls and selected 'subscriber types' KRN,KDE>K HLL D GET^HLSUB(1,1,"CIRN ROUTER",.HLL) KRN,KDE>ZW HLL HLL("LINKS",1)=CIRN ROUTER^ISC-SF^1^2961031.142702^2950617.13 KRN,KDE>D GET^HLSUB(1,2,"CIRN ROUTER",.HLL) KRN,KDE>ZW HLL HLL("LINKS",1)=CIRN ROUTER^ISC-SF^1^2961031.142702^2950617.13 HLL("LINKS",2)=CIRN ROUTER^KERNEL^2^2961031.11144^2961031.110628 NUMBER: 2271 IA #: 2271 DATE CREATED: JAN 23, 1998 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: HLUTIL3 NAME: DERIVE LOGICAL LINK FROM INSTITUTION ID: HLUTIL3 GENERAL DESCRIPTION: A new API has been created to return an array of Logical links when only an institution entry is known. This can be either a single institution or a VISN. A new field has been added to the HL LOGICAL LINK file (870) pointing to the INSTITUTION FILE. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26058048 COMPONENT/ENTRY POINT: LINK COMPONENT DESCRIPTION: NOTE: THIS API IS DEPENDENT ON KERNEL PATCH XU*8*43 AND PROPER GROUPING OF INSTITUTIONS WITHIN A VISN AND PROPER ASSOCIATION OF A LOGICAL LINK WITH THE CORRESPONDING INSTITUTION. API TO RETURN LOGICAL LINKS WHEN YOU INPUT INSTITUTION OR VISN (NAME OR IEN) 1. LINK^HLUTIL3(HLINST,.HLI) Purpose: Return Logical Link(s) from DHCP Institution Input: HLINST=Institution or VISN name or ien Output: HLI(LINK_IEN)=LINK NAME passed by reference EXAMPLE: DEV,CRN>D LINK^HLUTIL3("VISN 2",.HLZ) DEV,CRN>ZW HLZ HLZ= HLZ(9)=TAMPA, FL EDITOR: CLEMENS,JOHN NUMBER: 2278 IA #: 2278 FILE NUMBER: 441 GLOBAL ROOT: PRC(441 DATE CREATED: FEB 02, 1998 CUSTODIAL PACKAGE: IFCAP USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2278 ID: PRC(441 GLOBAL REFERENCE: PRC(441,D0,0) FIELD NUMBER: .05 FIELD NAME: SHORT DESCRIPTION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PRC(441,'C', GLOBAL DESCRIPTION: $Order() through the "C" cross reference on the SHORT DESCRIPTION (#.05) field. GENERAL DESCRIPTION: The purpose of this agreement is to allow another package to lookup Item Master file (#441) entries by the short description (field #.05) using the "C" cross reference on that field or extract the value of the short description for a item whose Item Master File (IMF) number is known. STATUS: Active DURATION: Till Otherwise Agreed KEYWORDS: ITEM MASTER FILE SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION DBA Comments: JSH 20061114/ Placed Lyford Greene as editor to bring up to date for SCID. JSH 20061204/ ACTIVATED AS PER GREENE AND SWESKY. SD QUESTIONED TO FAIN. DATE/TIME EDITED: DEC 06, 2006@20:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SWESKY,JEFF WITH CONCURRENCE OF: FAIN,ZACH NUMBER: 2283 IA #: 2283 FILE NUMBER: 58.8 GLOBAL ROOT: PSD(58.8 DATE CREATED: FEB 03, 1998 CUSTODIAL PACKAGE: DRUG ACCOUNTABILITY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2283 ID: PSD(58.8 GLOBAL REFERENCE: PSD(58.8,'D',DRUG,WARD) FIELD NUMBER: D Cross ref FIELD NAME: WARD (FOR DRUG) LOCATION: PSD(58.8,'D' ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the "D" cross-reference for field WARD (FOR DRUG) for sub-file 58.800115. This cross-reference is the link between the Controlled Substances package and the Unit Dose package for determining ward stocked drugs. GENERAL DESCRIPTION: Inpatient Medications requests permission to reference by a direct read cross-reference ^PSD(58.8,"D",DRUG,WARD). This is the "D" cross-reference for field WARD (FOR DRUG) for sub-file 58.800115. This cross-reference is the link between the Controlled Substances package and the Inpatient Medications package for determining ward stocked drugs. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26157582 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2284 IA #: 2284 FILE NUMBER: 58.1 GLOBAL ROOT: PSI(58.1 DATE CREATED: FEB 03, 1998 CUSTODIAL PACKAGE: AUTO REPLENISHMENT/WARD STOCK CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2284 ID: PSI(58.1 GLOBAL REFERENCE: PSI(58.1,'D',ITEM,WARD) FIELD NUMBER: D Cross-ref FIELD NAME: WARD (FOR ITEM) LOCATION: PSI(58.1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the "D" cross-reference for field WARD (FOR ITEM) for sub-file 58.26. GLOBAL DESCRIPTION: This cross-reference is used by the Inpatient Medications package to identify items on the Unit Dose pick list that are Ward Stock items. GENERAL DESCRIPTION: Inpatient Medications requests permission to reference by a direct read cross-reference ^PSI(58.1,"D", ITEM, WARD). This is the"D" cross-reference for field WARD (FOR ITEM) for sub-file 58.26. This cross-reference is used by the Inpatient Medications package to identify items on the Unit Dose pick list that are Ward Stock items. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26157594 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2285 IA #: 2285 DATE CREATED: FEB 03, 1998 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORCONV3 NAME: DBIA2285 ID: ORCONV3 GENERAL DESCRIPTION: Dietetics uses the entry point FH^ORCONV3 of Order Entry version 3 (CPRS) and pass the converted PACKAGE REFERENCE to Order Entry for storage. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26137091 COMPONENT/ENTRY POINT: FH COMPONENT DESCRIPTION: FH entry point of routine ORCONV3. VARIABLES: ORIFN TYPE: Input VARIABLES DESCRIPTION: The Internal Entry Number of the order in the Order file #100. VARIABLES: ORPK TYPE: Input VARIABLES DESCRIPTION: The converted PACKAGE REFERENCE string. SUBSCRIBING PACKAGE: DIETETICS ISC: Hines NUMBER: 2286 IA #: 2286 DATE CREATED: FEB 03, 1998 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORCDFH NAME: DBIA2286 ID: ORCDFH STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26137178 COMPONENT/ENTRY POINT: $$CANCEL COMPONENT DESCRIPTION: Returns 0 or 1 for No or Yes on whether a tray service should be cancelled. VARIABLES: ORIFN TYPE: Input VARIABLES DESCRIPTION: The Internal Entry Number of the order in the Order file (#100). COMPONENT/ENTRY POINT: $$RESUME COMPONENT DESCRIPTION: Returns a 0 or 1 for No or Yes on whether a tray service should be resumed. VARIABLES: ORIFN TYPE: Input VARIABLES DESCRIPTION: The Internal Entry Number of the order in the Order file (#100). SUBSCRIBING PACKAGE: DIETETICS ISC: Hines NUMBER: 2287 IA #: 2287 DATE CREATED: FEB 06, 1998 CUSTODIAL PACKAGE: DIETETICS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: FHWOR8 NAME: DBIA2287 ID: FHWOR8 GENERAL DESCRIPTION: Routine FHWOR8 will pass back an array of the Dietetics Order parameter. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 37311929 COMPONENT/ENTRY POINT: EN(DFN,FHPAR) COMPONENT DESCRIPTION: The entry point EN will return the Dietetics Order Parameter. Sample call: FHPAR is null before the call. D EN^FHWOR8(DFN,.FHPAR) The array is passed back to FHPAR. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The Internal Entry Number of the inpatient. VARIABLES: FHPAR TYPE: Both VARIABLES DESCRIPTION: FHPAR is a Call By Reference variable. It is null before the call. After the call, the following array is pass back: FHPAR(1)=EARLY BREAKFAST TIME 1 EARLY BREAKFAST TIME 2 EARLY BREAKFAST TIME 3 LATE BREAKFAST TIME 1 LATE BREAKFAST TIME 2 LATE BREAKFAST TIME 3 EARLY NOON TIME 1 EARLY NOON TIME 2 EARLY NOON TIME 3 LATE NOON TIME 1 LATE NOON TIME 2 LATE NOON TIME 3 EARLY EVENING TIME 1 EARLY EVENING TIME 2 EARLY EVENING TIME 3 LATE EVENING TIME 1 LATE EVENING TIME 2 LATE EVENING TIME 3 FHPAR(2)=LATE BREAKFAST ALARM BEGIN LATE BREAKFAST ALARM END LATE NOON ALARM BEGIN LATE NOON ALARM END LATE EVENING ALARM BEGIN LATE EVENING ALARM END BEGIN BREAKFAST WINDOW BEGIN NOON WINDOW BEGIN EVENING WINDOW PROVIDE BAGGED MEALS? FHPAR(3)=TYPE OF SERVICE Each piece of data is separated by a "^". Sample Array: FHPAR(1)=6:20A^8:00A^^8:50A^9.25A^^11:00A^12:00P^^12:50P^2:00P^3:00P^3:00P^ 4:30P^5:30P^^5:50P^8:50P^9:00P FHPAR(2)=630^830^1000^1505^2030^6:50A^11:25A^4:55P^Y FHPAR(3)=TC COMPONENT/ENTRY POINT: EN1(LOC,FHPAR) COMPONENT DESCRIPTION: The entry point EN1 will return the Dietetics Order Parameter when passed a location. Sample call: FHPAR is null before the call. D EN1^FHWOR8(LOC,.FHPAR) The array is passed back to FHPAR. VARIABLES: FHPAR TYPE: Both VARIABLES DESCRIPTION: FHPAR is a Call By Reference variable. It is null before the call. After the call, the following array is passed back: FHPAR(1)=EARLY BREAKFAST TIME 1 EARLY BREAKFAST TIME 2 EARLY BREAKFAST TIME 3 LATE BREAKFAST TIME 1 LATE BREAKFAST TIME 2 LATE BREAKFAST TIME 3 EARLY NOON TIME 1 EARLY NOON TIME 2 EARLY NOON TIME 3 LATE NOON TIME 1 LATE NOON TIME 2 LATE NOON TIME 3 EARLY EVENING TIME 1 EARLY EVENING TIME 2 EARLY EVENING TIME 3 LATE EVENING TIME 1 LATE EVENING TIME 2 LATE EVENING TIME 3 FHPAR(2)=LATE BREAKFAST ALARM BEGIN LATE BREAKFAST ALARM END LATE NOON ALARM BEGIN LATE NOON ALARM END LATE EVENING ALARM BEGIN LATE EVENING ALARM END BEGIN BREAKFAST WINDOW BEGIN NOON WINDOW BEGIN EVENING WINDOW PROVIDE BAGGED MEALS? FHPAR(3)=TYPE OF SERVICE Each piece of data is separated by a "^". Sample Array: FHPAR(1)=6:20A^8:00A^^8:50A^9.25A^^11:00A^12:00P^^12:50P^2:00P^3:00P^3:00P^ 4:30P^5:30P^^5:50P^8:50P^9:00P FHPAR(2)=630^830^1000^1505^2030^6:50A^11:25A^4:55P^Y FHPAR(3)=TC SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2289 IA #: 2289 DATE CREATED: FEB 06, 1998 CUSTODIAL PACKAGE: DIETETICS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: FHWOR5R NAME: DBIA2289 ID: FHWOR5R GENERAL DESCRIPTION: Extrinsic function call $$QUAN^FHWOR5R will return the total quantity in cc for a tubefeeding product. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26175261 COMPONENT/ENTRY POINT: QUAN COMPONENT DESCRIPTION: This extrinsic function will return the total quantity in cc of a tubefeeding product. Sample call: S X=$$QUAN^FHWOR5R(FHS,FHQ) X would contain the total cc of a tubefeeding product. VARIABLES: FHS TYPE: Input VARIABLES DESCRIPTION: This is a Call By Value variable. The input format consist of the Internal Entry Number of the tubefeeding product concatenated with a "-" and concatenate with the strength of the product. Example, "12-3". VARIABLES: FHQ TYPE: Input VARIABLES DESCRIPTION: This is a Call By Value variable. The input consist of the Health Level 7 message segment of the tubefeeding product quantity, duration, and interval each separate by a "^". Example, 100&C^BID^H6. The input is 100CC, twice a day, for 6 hours. VARIABLES: TC TYPE: Output VARIABLES DESCRIPTION: This variable is the total quantity of the tubefeeding product in cc which will be returned by the function call. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2290 IA #: 2290 DATE CREATED: FEB 06, 1998 CUSTODIAL PACKAGE: DIETETICS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: FHWORR NAME: DBIA2290 ID: FHWORR GENERAL DESCRIPTION: Extrinsic function $$RESUME^FHWORR will return a flag on whether to prompt the user to resume the tray service or not. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26175261 COMPONENT/ENTRY POINT: RESUME COMPONENT DESCRIPTION: This entry point will check whether to prompt to resume tray service. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The Internal Entry Number of the inpatient. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: This is a flag which is returned by the function call. The flag can be a null, 1, or 0. If Y = Null which means No Current Diet Order in file. If Y = 1 means to prompt the user to resume tray service. If Y = 0 means not to prompt the user. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2291 IA #: 2291 DATE CREATED: FEB 06, 1998 CUSTODIAL PACKAGE: DIETETICS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: FHWOR7 NAME: DBIA2291 ID: FHWOR7 GENERAL DESCRIPTION: Routine FHWOR7 will return the information on the Dietetics Profile. DFN have to be defined before using the routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26175261 COMPONENT/ENTRY POINT: FHWOR7 COMPONENT DESCRIPTION: This routine will return Supplemental Feeding, Tubefeeding, and Food Preference of a particular inpatient in the ^TMP global. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The Internal Entry Number of the inpatient. VARIABLES: TMP($J) TYPE: Output VARIABLES DESCRIPTION: Dietetics will return the following arrays: Supplemental Feeding: ^TMP($J,"FHSF",1)=Date/Time (Internal FM form 2970422.103109)_"^"_ 10am feeding Quantity # 1_" "_10am Feeding name # 1_";"_ 10am feeding Quantity # 2_" "_10am Feeding name # 2_";"_ 10am feeding Quantity # 3_" "_10am Feeding name # 3_";"_ 10am feeding Quantity # 4_" "_10am Feeding name # 4_"^"_ 2pm feeding Quantity # 1_" "_2pm Feeding name # 1_";"_ 2pm feeding Quantity # 2_" "_2pm Feeding name # 2_";"_ 2pm feeding Quantity # 3_" "_2pm Feeding name # 3_";"_ 2pm feeding Quantity # 4_" "_2pm Feeding name # 4_"^"_ 8pm feeding Quantity # 1_" "_8pm Feeding name # 1_";"_ 8pm feeding Quantity # 2_" "_8pm Feeding name # 2_";"_ 8pm feeding Quantity # 3_" "_8pm Feeding name # 3_";"_ 8pm feeding Quantity # 4_" "_8pm Feeding name # 4 Tubefeeding: ^TMP($J,"FHTF",1)=Kcal/Day Food Preference: Likes: ^TMP($J,"FHFP","L",n)=Quantity_" "_Food Preference name_"^"_Meal (example BNE) n=Sequential number Dislikes: ^TMP($J,"FHFP","D",n)=Food Preference name_"^"_Meal n=Sequential number SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2292 IA #: 2292 DATE CREATED: FEB 06, 1998 CUSTODIAL PACKAGE: DIETETICS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: FHWOR71 NAME: DBIA2292 ID: FHWOR71 GENERAL DESCRIPTION: P^FHWOR71 is an extrinsic function which returns the printable Dietetics Profile for a particular inpatient. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26175261 COMPONENT/ENTRY POINT: P COMPONENT DESCRIPTION: This extrinsic function returns a flag of either a -1 or 1. If flag is a -1, there is no profile. If flag is a 1, there is a profile and the printable Dietetics Profile is stored in ^TMP($J,"FHPROF",DFN,Sequential number). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The Internal Entry number of the inpatient. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: A flag of either a -1^displayable error text or 1 for sucessful. VARIABLES: TMP($J,FHPROF,DFN,N) TYPE: Output VARIABLES DESCRIPTION: The displayable text of the Dietetics Profile is stored in the global ^TMP($J,"FHPROF",DFN,N)=Lines of text. Where N = sequential number. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2293 IA #: 2293 DATE CREATED: FEB 06, 1998 CUSTODIAL PACKAGE: DIETETICS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: FHWORA NAME: DBIA2293 ID: FHWORA GENERAL DESCRIPTION: Routine FHWORA contains two extrinsic functions which will return the Nutrient Assessment dates for a particular patient and the printable Nutrient Assessment for an Assessment date of that patient. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26175261 COMPONENT/ENTRY POINT: FHWORADT COMPONENT DESCRIPTION: This extrinsic function returns a flag of either a -1 or 1. If flag is a -1, no Assessment found. If flag is a 1, Assessment found and the Assessment dates for a paticular patient is stored in the global ^TMP($J,"FHADT",DFN,Inverse internal date/time). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The Internal Entry Number of the patient. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: A flag of either -1^error text for no assessment dates passed back with reason being error text or 1 for assessments dates for the patient have been found. VARIABLES: TMP($J,FHADT,DFN) TYPE: Output VARIABLES DESCRIPTION: All the Nutrient Assessment dates for a particular patient are stored in the global ^TMP($J,"FHADT",DFN,inverse internal date/time)=external date/time. COMPONENT/ENTRY POINT: FHWORASM COMPONENT DESCRIPTION: This extrinsic function returns a flag of either a -1 or 1. If flag is a -1, no Assessment found. If flag is a 1, the Assessment is found and the printable Nutrient Assessment for an Assessment date of a particular patient is stored in the global ^TMP($J,"FHASM",DFN,Sequential number). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The Internal Entry Number of the patient. VARIABLES: FHADTX TYPE: Input VARIABLES DESCRIPTION: The external format of the Assessment date. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: A flag of -1^error text for no assessment passed back with reason being in the error text or 1 for assessment for the patient have been found. VARIABLES: TMP($J,FHASM,DFN) TYPE: Output VARIABLES DESCRIPTION: The printable Nutrient Assessment is stored in the global ^TMP($J,"FHASM",DFN, Sequence number)="Lines of text". SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2294 IA #: 2294 DATE CREATED: FEB 06, 1998 CUSTODIAL PACKAGE: DIETETICS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: FHORD7 NAME: DBIA2294 ID: FHORD7 GENERAL DESCRIPTION: Entry Point CUR^FHORD7 will return the Current Diet of a particular inpatient. Before executing this entry point, make sure both variables, DFN and ADM, exists. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26175261 COMPONENT/ENTRY POINT: CUR COMPONENT DESCRIPTION: This entry point returns the current Diet for an inpatient. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The Internal Entry Number of the inpatient. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: The free text of the current Diet. VARIABLES: ADM TYPE: Input VARIABLES DESCRIPTION: The admission number. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2295 IA #: 2295 FILE NUMBER: 40.8 GLOBAL ROOT: DG(40.8 DATE CREATED: FEB 07, 1998 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2295 ID: DG(40.8 GLOBAL REFERENCE: DG(40.8,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .07 FIELD NAME: INSTITUTION FILE POINTER LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26059407 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2296 IA #: 2296 FILE NUMBER: 43 GLOBAL ROOT: DG(43 DATE CREATED: FEB 07, 1998 CUSTODIAL PACKAGE: REGISTRATION USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2296 ID: DG(43 GLOBAL REFERENCE: DG(43,D0,GL) FIELD NUMBER: 11 FIELD NAME: MULTIDIVISION MED CENTER? LOCATION: GL;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 12 FIELD NAME: MEDICAL CENTER NAME LOCATION: GL;3 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26059407 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL NUMBER: 2298 IA #: 2298 DATE CREATED: MAR 05, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2298 GLOBAL REFERENCE: DD(779.001,0,'ID' GLOBAL DESCRIPTION: 'identifier' node of DD for file 779.001 and 771.2 GLOBAL REFERENCE: DD(771.2,0,'ID' GLOBAL DESCRIPTION: This is the 'identifier' node on the description field of file 771.2. GENERAL DESCRIPTION: HL7 Patch 14 brings in updates to reference files for version 2.3 of the standard. These files contain identifiers that have changed with the latest version. KIDS does not install the new data correctly unless these identifiers are removed before installing the patch. Permission is requested to execute the following code as pre and post install routines in patch 14. HLP14PRE ;SFIRMFO/JC - HL7 PATCH 14 PRE-INIT ;03/05/98 11:44 ;;1.6;HEALTH LEVEL SEVEN;**14**;Oct 13, 1995 PRE ; K ^DD(779.001,0,"ID") K ^DD(771.2,0,"ID") Q POST ; S ^DD(779.001,0,"ID",2)="W "_""""_" "_""""_",$P(^(0),U,2)" S ^DD(771.2,0,"ID",2)="W "_""""_" "_""""_",$P(^(0),U,2)" STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26413490 SUBSCRIBING PACKAGE: HEALTH LEVEL SEVEN ISC: Oakland NUMBER: 2300 IA #: 2300 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: FEB 07, 1998 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2300 ID: DPT( GLOBAL REFERENCE: DPT(D0,DIS, GLOBAL DESCRIPTION: Fileman captioned output of entire DISPOSITION LOG-IN DATE/TIME subrecord. GLOBAL REFERENCE: DPT(D0,S, GLOBAL DESCRIPTION: Fileman captioned output of entire APPOINTMENT subrecord. GLOBAL REFERENCE: DPT(D0,DIS,D1,2) FIELD NUMBER: 21 FIELD NAME: WORKMEN'S COMP CLAIM FILED LOCATION: 2;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 23 FIELD NAME: NEED RELATED TO AN ACCIDENT LOCATION: 2;4 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DPT(D0,S,D1,0) FIELD NUMBER: 3 FIELD NAME: STATUS LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 9 FIELD NAME: PURPOSE OF VISIT LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26059407 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2309 IA #: 2309 FILE NUMBER: 9000010 GLOBAL ROOT: AUPNVSIT( DATE CREATED: FEB 07, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2309 ID: AUPNVSIT( GLOBAL REFERENCE: AUPNVSIT(AA GLOBAL DESCRIPTION: 'AA' xref. GLOBAL REFERENCE: AUPNVSIT(AD GLOBAL DESCRIPTION: 'AD' xref. GLOBAL REFERENCE: AUPNVSIT(D0, GLOBAL DESCRIPTION: Fileman captioned output of entire VISIT record. GLOBAL REFERENCE: AUPNVSIT(D0,0) FIELD NUMBER: .12 FIELD NAME: PARENT VISIT LINK LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26059411 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES NUMBER: 2310 IA #: 2310 FILE NUMBER: 9000010.18 GLOBAL ROOT: AUPNVCPT( DATE CREATED: FEB 07, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2310 ID: AUPNVCPT( GLOBAL REFERENCE: AUPNVCPT(AD GLOBAL DESCRIPTION: 'AD' xref. GLOBAL REFERENCE: AUPNVCPT(D0, GLOBAL DESCRIPTION: Fileman captioned output of entire V CPT record. GLOBAL REFERENCE: AUPNVCPT(D0,12) FIELD NUMBER: 1204 FIELD NAME: ENCOUNTER PROVIDER LOCATION: 12;4 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26059411 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2311 IA #: 2311 FILE NUMBER: 9000010.13 GLOBAL ROOT: AUPNVXAM DATE CREATED: FEB 07, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2311 ID: AUPNVXAM GLOBAL REFERENCE: AUPNVXAM(AD GLOBAL DESCRIPTION: 'AD' xref. GLOBAL REFERENCE: AUPNVXAM(D0, GLOBAL DESCRIPTION: Fileman captioned output of entire V EXAM record. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26059411 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2312 IA #: 2312 FILE NUMBER: 9000010.23 GLOBAL ROOT: AUPNVHF DATE CREATED: FEB 07, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2312 ID: AUPNVHF GLOBAL REFERENCE: AUPNVHF(AD GLOBAL DESCRIPTION: 'AD' xref. GLOBAL REFERENCE: AUPNVHF(D0, GLOBAL DESCRIPTION: Fileman captioned output of entire V HEALTH FACTORS record. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26059411 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: CLINICAL REMINDERS NUMBER: 2313 IA #: 2313 FILE NUMBER: 9000010.11 GLOBAL ROOT: AUPNVIMM( DATE CREATED: FEB 07, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2313 ID: AUPNVIMM( CREATOR: HARVEY,JULIE S GLOBAL REFERENCE: AUPNVUMM(AD, GLOBAL DESCRIPTION: "AD" xref. GLOBAL REFERENCE: AUPNVIMM(D0, GLOBAL DESCRIPTION: Fileman captioned output of entire V IMMUNIZATION record. GLOBAL REFERENCE: AUPNVIMM(AA, GLOBAL DESCRIPTION: "AA" xref. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26059411 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING DETAILS: BCMA added 12/12/08 /jsh DBA Comments: 20090828/ ADDED "AA" CROSS-REFERENCE DATE ACTIVATED: AUG 28, 2009 DATE/TIME EDITED: DEC 12, 2008@11:15 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: ELLIS,DONNA WITH CONCURRENCE OF: SILVERMAN,ROBERT DATE/TIME EDITED: AUG 28, 2009@11:33 ACTION: CONTENT CORRECTED AT THE REQUEST OF: SILVERMAN,ROBERT WITH CONCURRENCE OF: ELLIS,DONNA NUMBER: 2314 IA #: 2314 FILE NUMBER: 9000010.16 GLOBAL ROOT: AUPNVPED( DATE CREATED: FEB 07, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2314 ID: AUPNVPED( GLOBAL REFERENCE: AUPNVPED(AD GLOBAL DESCRIPTION: 'AD' xref. GLOBAL REFERENCE: AUPNVPED(D0, GLOBAL DESCRIPTION: Fileman captioned output of entire V PATIENT ED record. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26059411 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2315 IA #: 2315 FILE NUMBER: 9000010.07 GLOBAL ROOT: AUPNVPOV( DATE CREATED: FEB 07, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2315 ID: AUPNVPOV( GLOBAL REFERENCE: AUPNVPOV(AD GLOBAL DESCRIPTION: 'AD' xref. GLOBAL REFERENCE: AUPNVPOV(D0, GLOBAL DESCRIPTION: Fileman captioned output of entire V POV record. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26059411 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2316 IA #: 2316 FILE NUMBER: 9000010.06 GLOBAL ROOT: AUPNVPRV( DATE CREATED: FEB 07, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2316 ID: AUPNVPRV( GLOBAL REFERENCE: AUPNVPRV(AD GLOBAL DESCRIPTION: 'AD' xref. GLOBAL REFERENCE: AUPNVPRV(D0, GLOBAL DESCRIPTION: Fileman captioned output of entire V PROVIDER record. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26059411 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING DETAILS: 6/20/14 - PCMMR added. Beginning with SD*5.3*603, PCMMR will assign a patient to a team in a pending status until they have a completed encounter with a team member. Once they have the encounter, they are switched to an active status. PCMMR uses a remote procedure call to identify an encounter in the Outpatient Encounter (#409.68) file based on the checkout date and makes a determination if the status should be updated to active. With the Outpatient Encounter file data, additional data elements can be obtained from the Visit (#9000010) and V Provider (#9000010.06) files. Returned array includes Patient DFN, Encounter Date/Time(#.01 field - 409.68), Provider IEN (#.01 field - 9000010.06), Primary/Secondary (#.04 field - 9000010.06), Stop Code (#.03 field - 409.68), Encounter Type (#15003 field - 9000010), Checkout Completed Date/Time (#.07 field - 409.68), Outpatient Encounter (#409.68) IEN, Outpatient Encounter Parent IEN, Visit (#9000010) IEN, and Visit Parent IEN (#12 field - 9000010). PCMMR will display the last encounter date for the patient. SUBSCRIBING PACKAGE: CLINICAL REMINDERS DBA Comments: 6/20/14-MM: Adding PCMMR details to the Subscribing Details for Scheduling to document how PCMM will be using the Visit and V Provider files for PCMMR functionality distributed in SD*5.3*603. DATE/TIME EDITED: JUN 20, 2014@14:56 ACTION: CONTENT CORRECTED AT THE REQUEST OF: THOMPSON,ANDY WITH CONCURRENCE OF: REDINGTON,PAT NUMBER: 2317 IA #: 2317 FILE NUMBER: 9000010.12 GLOBAL ROOT: AUPNVSK( DATE CREATED: FEB 07, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2317 ID: AUPNVSK( GLOBAL REFERENCE: AUPNVSK(AD GLOBAL DESCRIPTION: 'AD' xref. GLOBAL REFERENCE: AUPNVSK(D0, GLOBAL DESCRIPTION: Fileman captioned output of entire V SKIN TEST record. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26059411 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: CLINICAL REMINDERS NUMBER: 2318 IA #: 2318 FILE NUMBER: 9000010.15 GLOBAL ROOT: AUPNVTRT( DATE CREATED: FEB 07, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2318 ID: AUPNVTRT( GLOBAL REFERENCE: AUPNVTRT(AD GLOBAL DESCRIPTION: 'AD' xref. GLOBAL REFERENCE: AUPNVTRT(D0, GLOBAL DESCRIPTION: Fileman captioned output of entire V TREATMENT record. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26059411 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2319 IA #: 2319 FILE NUMBER: 119.4 GLOBAL ROOT: FH(119.4, DATE CREATED: FEB 09, 1998 CUSTODIAL PACKAGE: DIETETICS CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2319 ID: FH(119.4, GLOBAL REFERENCE: FH(119.4,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: The name of the Isolation/Precaution type. FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: FH(119.4,'B', GLOBAL REFERENCE: FH(119.4,D0,'I') FIELD NUMBER: 99 FIELD NAME: INACTIVE LOCATION: I;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Order Entry Version 3 (CPRS) uses the Isolation/Precaution Type file (#119.4). The Order Dialog file (#101.41) points to file 119.4 and displays the Isolation/Precaution types for ordering. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION NUMBER: 2320 IA #: 2320 DATE CREATED: FEB 09, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: %ZISH NAME: DBIA2320 ID: %ZISH GENERAL DESCRIPTION: The %ZISH calls described in the KERNEL SYSTEM Manual. This is a set of calls to work with Host files of the underlaying system. STATUS: Active MAIL MESSAGE: 37585057 COMPONENT/ENTRY POINT: CLOSE COMPONENT DESCRIPTION: Close host file opened by OPEN^%ZISH. COMPONENT/ENTRY POINT: $$DEL COMPONENT DESCRIPTION: Delete host file. COMPONENT/ENTRY POINT: $$FTG COMPONENT DESCRIPTION: Copy lines from a host file into a global. COMPONENT/ENTRY POINT: $$GATF COMPONENT DESCRIPTION: Append records from a global to a host file. COMPONENT/ENTRY POINT: $$GTF COMPONENT DESCRIPTION: Copy records from a global into a host file. COMPONENT/ENTRY POINT: $$LIST COMPONENT DESCRIPTION: Retrieve a list of files in a directory. COMPONENT/ENTRY POINT: $$MV COMPONENT DESCRIPTION: Rename host file. COMPONENT/ENTRY POINT: OPEN COMPONENT DESCRIPTION: Open host file (bypass device handler). COMPONENT/ENTRY POINT: $$PWD COMPONENT DESCRIPTION: Retrieve name of current directory. COMPONENT/ENTRY POINT: $$STATUS COMPONENT DESCRIPTION: Return end-of-file status. COMPONENT/ENTRY POINT: $$DEFDIR[(df)] COMPONENT DESCRIPTION: This api has two modes. If it is called with a null/missing parameter, it returns the "default directory for HFS files" from the KSP file (8989.3). If it is called with a parameter, it must be the directory for a file. This parameter will be check to see that it is in the correct format for this operating system. VARIABLES: df TYPE: Input VARIABLES DESCRIPTION: This is a directory path to be do a simple format check on. For NT it will change "/" to "\" and see that there is a trailing "\". There is no error response. VARIABLES: $$DEFDIR TYPE: Output NUMBER: 2321 IA #: 2321 FILE NUMBER: 8925.1 GLOBAL ROOT: TIU(8925.1 DATE CREATED: FEB 10, 1998 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2321 ID: TIU(8925.1 GLOBAL REFERENCE: TIU(8925.1,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This includes direct access to the "B" x-ref. FIELD NUMBER: .04 FIELD NAME: TYPE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: AD ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: In order for the AUTHORIZATION/SUBSCRIPTION UTILITY (ASU) to work properly with TIU documents it needs the information contained in the first and fourth pieces of the zero node of the TIU DOCUMENT DEFINITION FILE, # 8925.1. It also needs to use the "AD" cross-reference to traverse the document class hierarchy to determine if authorization is granted at a higher level. Therefore ASU requests permission to do a direct global read of the first and fourth pieces of the zero node of file # 8925.1 and the "AD" node. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26282235 SUBSCRIBING PACKAGE: AUTHORIZATION/SUBSCRIPTION ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING DETAILS: CIRN only references the .01 field. SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING DETAILS: added 11/10/2010 SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: Effective with VPR*1*0. DBA Comments: 08/02/13 DT: Added VPR as subscriber, effective with VPR*1*0. DATE/TIME EDITED: NOV 10, 2010@12:12 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: TROMBETTA,KATHY WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: AUG 02, 2013@13:37 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 2322 IA #: 2322 DATE CREATED: FEB 10, 1998 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIULP NAME: Calls to TIULP ID: TIULP GENERAL DESCRIPTION: This DBIA is a controlled subscription for calls to routine TIULP. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30387939 COMPONENT/ENTRY POINT: $$CANPICK(TIUTYP) COMPONENT DESCRIPTION: This is a Boolean function that returns true if ?? and false otherwise. VARIABLES: TIUTYP TYPE: Input VARIABLES DESCRIPTION: This is the ien of the document. COMPONENT/ENTRY POINT: $$CANDO(IEN,ACTION) COMPONENT DESCRIPTION: Evaluates whether a user can perform an action on a specific TIU document. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of the TIU DOCUMENT file (#8925). VARIABLES: ACTION TYPE: Input VARIABLES DESCRIPTION: Pointer to the USR ACTION file (#8930.8). VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: RESULT=$$CANDO^TIULP(IEN,ACTION) where result is: 1 if user can perform action 0^'why not message' if user can't perform action COMPONENT/ENTRY POINT: $$REQCOSIG(TYPE,IEN,USER) COMPONENT DESCRIPTION: Evaluates whether a user requires a cosignature for a particular document. VARIABLES: TYPE TYPE: Input VARIABLES DESCRIPTION: Pointer to TIU DOCUMENT DEFINITION file (#8925.1). VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Pointer to TIU DOCUMENT file (#8925). VARIABLES: USER TYPE: Input VARIABLES DESCRIPTION: Pointer to NEW PERSON file (#200). VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: RESULT=$$REQCOSIG(TYPE,IEN,USER) where RESULT is 1 if user requires cosignature for the document or 0 otherwise. COMPONENT/ENTRY POINT: $$CANLINK(TYPE) COMPONENT DESCRIPTION: BOOLEAN function which evaluates whether the current user (DUZ) link a document of a particular type to an Interdisciplinary Note. For use in ADD NEW ID NOTE, where the new entry has not yet been entered. not entered yet. Assume most favorable circumstances (i.e., user will complete the note), so if user still can't link, can tell them no, when they first select title for the new entry. Exclude titles that can be selected as Interdisciplinary Parents, since Parent and Child entries function as mutually exclusive, (regardless of business rules). VARIABLES: TYPE TYPE: Input VARIABLES DESCRIPTION: This is the IEN of the document in the TIU DOCUMENT DEFINITION FILE (#8925.1). VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: The function returns a BOOLEAN result (i.e., 1 if the document in question may be linked as an Interdisciplinary Entry, and 0^Explanatory text) if it cannot. COMPONENT/ENTRY POINT: $$CANENTR(TIUTYP) VARIABLES: TIUTYP TYPE: Input VARIABLES DESCRIPTION: Document type IEN. VARIABLES: $$CANENTR TYPE: Output VARIABLES DESCRIPTION: 1 == if user has privileges to enter a document of the type input 0 == otherwise SUBSCRIBING PACKAGE: AUTHORIZATION/SUBSCRIPTION ISC: Salt Lake City SUBSCRIBING DETAILS: In order for the AUTHORIZATION/SUBSCRIPTION UTILITY (ASU) to work properly with TIU documents it needs to screen selection of documents. The function CANPICK^TIULP provides this functionality. ASU would like permission to call CANPICK^TIULP. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: OE/RR calls $$CANDO, $$CANLINK, and $$REQCOSIG. SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: IMAGING NUMBER: 2323 IA #: 2323 DATE CREATED: FEB 10, 1998 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIULC1 NAME: Calls to routine TIULC1 ID: TIULC1 GENERAL DESCRIPTION: This DBIA documents calls to routine TIULC1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30387939 COMPONENT/ENTRY POINT: $$PNAME(DA) COMPONENT DESCRIPTION: Returns the Display Name of a document class. VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: Internal entry number of document. COMPONENT/ENTRY POINT: $$ISADDNDM(IEN) COMPONENT DESCRIPTION: Returns whether a TIU DOCUMENT entry (#8925) is an addendum or not. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT file (#8925). VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: RESULT=$$ISADDNDM(IEN) where RESULT is 1 if the document is an addendum and a 0 otherwise. COMPONENT/ENTRY POINT: $$PTNAME(DFN) COMPONENT DESCRIPTION: Returns patient name. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal entry number of the PATIENT file (#2). VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: RESULT=$$PTNAME^TIULC1(DFN) where RESULT returns the NAME field (.01) of the PATIENT file or "NAME UNKNOWN" if invalid DFN entered. COMPONENT/ENTRY POINT: DOCPRM(TYPE,.PARAMS,IEN) COMPONENT DESCRIPTION: Returns parameters for a document type. VARIABLES: TYPE TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT DEFINITION file (#8925.1). VARIABLES: PARAMS TYPE: Both VARIABLES DESCRIPTION: Array passed in by reference, to return data from the TIU DOCUMENT PARAMETERS file (#8925.95): PARAMS(0)=0-node of file entry PARAMS(5)=#^#^...^# where # is each entry in the Users Requiring Cosignature subfile (#8995.955) VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT file (#8925); optional, used to get document type from parent document, if IEN is an addendum. SUBSCRIBING PACKAGE: AUTHORIZATION/SUBSCRIPTION ISC: Salt Lake City SUBSCRIBING DETAILS: In order for the AUTHORIZATION/SUBSCRIPTION UTILITY (ASU) to work properly with TIU documents it needs the display name for a document class. The function PNAME^TIULC1 returns this information. ASU would like permission to call PNAME^TIULC1. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: OE/RR makes calls to $$ISADDNDM, $$PNAME, and $$PTNAME. SUBSCRIBING PACKAGE: CARE MANAGEMENT ISC: Salt Lake City SUBSCRIBING DETAILS: Care Mgt uses DOCPRM to get document parameters. SUBSCRIBING PACKAGE: IMAGING DBA Comments: 4/2/13-MM: Imaging added as a subscriber for MAG*3.0*129 planned for release in 8/2013. DATE/TIME EDITED: JAN 25, 2007@19:00 ACTION: WITHDREW REQUEST AT THE REQUEST OF: SHOVESTUL,MARYANN WITH CONCURRENCE OF: HARVEY,JULIE DATE/TIME EDITED: APR 02, 2013@12:20 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: KIRIN,GARRETT WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 2325 IA #: 2325 DATE CREATED: FEB 10, 1998 CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: USRLA NAME: DBIA2325 ID: USRLA GENERAL DESCRIPTION: When checking what a user can do with a document, (read, edit, etc.) TIU needs to evaluate the user's authorization. Therefore TIU requests permission to call the function CANDO^USRLA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26282266 COMPONENT/ENTRY POINT: $$CANDO(DOCTYPE,STATUS,EVENT,USER,USRROLE) COMPONENT DESCRIPTION: Return true if a user is authorized to perform the specified action on a document. VARIABLES: DOCTYPE TYPE: Input VARIABLES DESCRIPTION: IEN in file 8925.1 TIU DOCUMENT DEFINITION. VARIABLES: STATUS TYPE: Input VARIABLES DESCRIPTION: Pointer to file 8925.6, TIU STATUS. VARIABLES: EVENT TYPE: Input VARIABLES DESCRIPTION: Pointer to file 8930.8, USR EVENT. VARIABLES: USER TYPE: Input VARIABLES DESCRIPTION: Pointer to file 200, NEW PERSON. VARIABLES: USRROLE TYPE: Input VARIABLES DESCRIPTION: Pointer to file 8930.2, USR ROLE. SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 2326 IA #: 2326 DATE CREATED: FEB 12, 1998 CUSTODIAL PACKAGE: DIETETICS CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: FHWORI NAME: DBIA2326 ID: FHWORI GENERAL DESCRIPTION: Routine ORSETUP in patch OR*2.5*49, CPRS PRE-INSTALL, and in Order Entry Version 3 (CPRS) calls routine FHWORI to populate the Orderable Item file (#101.43). FHWORI sends Order Entry Health Level 7 messages of Tubefeeding products, and Diets for storage in file 101.43. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26175261 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2327 IA #: 2327 DATE CREATED: FEB 17, 1998 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBJTU31 NAME: DBIA2327 ID: IBJTU31 GENERAL DESCRIPTION: This is needed to determine if a bill has multiple Insurance Carriers. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26240980 COMPONENT/ENTRY POINT: $$MINS(X) COMPONENT DESCRIPTION: This call will return 1 if the bill passed in X has multiple insurance carriers, 0 will be returned if bill does not. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: File 399 internal entry number. SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 2328 IA #: 2328 DATE CREATED: FEB 17, 1998 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBJTLA NAME: DBIA2328 ID: IBJTLA GENERAL DESCRIPTION: This call is needed to allow Accounts Receivable to call the Third Party Joint Inquiry List Template (Integated Billing) from an Accounts Receivable List Template option. This is needed to prevent users from having to exit one menu option and access another option. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26240902 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: This call is the main entry point into the Third Party Joint Inquiry List Template option. SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 2329 IA #: 2329 DATE CREATED: FEB 19, 1998 CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: USRLFF NAME: DBIA2329 ID: USRLFF GENERAL DESCRIPTION: USRLFF is a library of file functions for providing read access to various AUTHORIZATION/SUBSCRIPTION data. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26282270 COMPONENT/ENTRY POINT: EVNTPTR COMPONENT DESCRIPTION: Returns a pointer in file 8930.8 to "EVENT." VARIABLES: EVENT TYPE: Input VARIABLES DESCRIPTION: EVENT is the name of the event such as "AMENDMENT" or "SIGNATURE." COMPONENT/ENTRY POINT: EVNTVERB COMPONENT DESCRIPTION: Return the verb in file 8930.8 for the event with ien IEN. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal entry number of an event in file 8930.8. COMPONENT/ENTRY POINT: HASAS COMPONENT DESCRIPTION: Boolean function that returns true if entry IEN in file 8930.1 has Authorizations/Subscriptions. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal entry number of an entry in file 8930.1. COMPONENT/ENTRY POINT: USRCLASS COMPONENT DESCRIPTION: Returns the 0 node of entry IEN in file 8930. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Internal entry number for file 8930. COMPONENT/ENTRY POINT: USRROLE COMPONENT DESCRIPTION: Return the internal entry number from file 8930.2 for the role "ROLE." VARIABLES: ROLE TYPE: Input VARIABLES DESCRIPTION: Examples of "ROLE" are "ATTENDING PHYSICIAN", and "TRANSCRIBER." SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 2331 IA #: 2331 FILE NUMBER: 65 GLOBAL ROOT: LRD(65 DATE CREATED: MAR 02, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2331-A ORIGINAL NUMBER: 2331 ID: LRD(65 GLOBAL REFERENCE: LRD(65 FIELD NUMBER: .01 FIELD NAME: UNIT ID LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: COMPONENT LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: EXPIRATION DATE/TIME LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LRD(65,D0,2, FIELD NUMBER: .01 FIELD NAME: PATIENT XMATCHED/ASSIGNED LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: DATE/TIME UNIT ASSIGNED LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Direct global reads to "AP", "B", and "C" x-refs is also specified. STATUS: Active MAIL MESSAGE: 26345221 SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 2332 IA #: 2332 DATE CREATED: MAR 02, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LRBLB NAME: DBIA2331-B ORIGINAL NUMBER: 2331 ID: LRBLB GENERAL DESCRIPTION: The Surgery package requests permission to call the Blood Bank routine, BAR^LRBLB from the Surgery routine SRBLOOD, to scan the blood product bag, to ensure bar code readability. STATUS: Active MAIL MESSAGE: 26345221 COMPONENT/ENTRY POINT: BAR VARIABLES: LR TYPE: Output VARIABLES: X TYPE: Output SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 2333 IA #: 2333 DATE CREATED: MAR 02, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LRBLBU NAME: DBIA2333 ID: LRBLBU GENERAL DESCRIPTION: The Surgery package requests permission to call the Blood Bank routine, LRBLBU, to scan the Blood Unit ID and return that value in the variable "X" from the blood product bag. The Surgery routine SRBLOOD, will use this value to check for an association with the patient in the operating room and the scanned Blood Unit ID. STATUS: Active MAIL MESSAGE: 26345221 COMPONENT/ENTRY POINT: LRBLBU VARIABLES: X TYPE: Both VARIABLES DESCRIPTION: The variable "X" is returned from scanning the Blood Product ID. VARIABLES: LR TYPE: Input SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 2334 IA #: 2334 DATE CREATED: MAR 04, 1998 CUSTODIAL PACKAGE: LIST MANAGER CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VALM4 NAME: DBIA2334 ID: VALM4 GENERAL DESCRIPTION: Inpatient Medications requests permission to call RESET^VALM4 (List Manager). This entry point allows the use of the ListMan standard protocol VALM TURN ON/OFF MENUS ( Auto-Display(On/Off) )to toggle between a normal and expanded screen length. In each Inpatient Medications Protocol HEADER field, a call is made that declares a short and long screen length and makes the call to RESET^VALM4. Each time the user executes the VALM TURN ON/OFF MENUS protocol, the protocol choices at the bottom of the screen are removed or brought back and the screen length is adjusted accordingly. During the Alpha testing of Inpatient Medications 5.0 and CPRS 1.0 at Tuscaloosa AL and West Palm Beach FL, this ability to expand the ListMan screen viewing area brought extreme positive feedback from the users. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26398631 COMPONENT/ENTRY POINT: RESET COMPONENT DESCRIPTION: This entry point allows the use of the ListMan standard protocol VALM TURN ON/OFF MENUS ( Auto-Display(On/Off) )to toggle between a normal and expanded screen length. In each Inpatient Medications Protocol HEADER field, a call is made that declares a short and long screen length and makes the call to RESET^VALM4. Each time the user executes the VALM TURN ON/OFF MENUS protocol, the protocol choices at the bottom of the screen are removed or brought back and the screen length is adjusted accordingly. In each Inpatient Medications Protocol HEADER field, a call is made to A^PSJ200(a,b) with (a) defined as long screen number of lines and (b) defined as short screen number of lines. A^PSJ200() is coded as: A(LONG,SHORT,SHRINK) ; Resizes list area N PSJBM S PSJBM=$S(VALMMENU:SHORT,+$G(SHRINK):SHORT,1:LONG) I VALM("BM")'=PSJBM S VALMBCK="R" D .S VALM("BM")=PSJBM,VALM("LINES")=(PSJBM-VALM("TM"))+1 .I +$G(VALMCC) D RESET^VALM4 Q VARIABLES: VALM('BM') TYPE: Input VARIABLES DESCRIPTION: Declares a long or short bottom margin variable to be used when displaying the list. VARIABLES: VALM('LINES') TYPE: Input VARIABLES DESCRIPTION: Modifies the number of screen lines for the list to be either regular or expanded. This changes each time the user executes the VALM TURN ON/OFF MENUS protocol. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING DETAILS: See also IA 367. SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES NUMBER: 2335 IA #: 2335 DATE CREATED: MAY 11, 1998 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XPAR NAME: OE/RR CALL TO XPAR FOR BACKWARDS COMPATIBILITY ID: XPAR GENERAL DESCRIPTION: This DBIA is a private agreement between OE/RR and the Parameter Tools portion of Toolkit to allow a call to PUT1^XPAR. This is needed until Radiology converts to using XPAR calls directly. Parameter Tools functionality was originally in the ORXP namespace, but was later moved to the XPAR namespace. STATUS: Active DURATION: Next Version MAIL MESSAGE: 28678942 GOOD ONLY FOR VERSION: 3 of OE/RR COMPONENT/ENTRY POINT: PUT1 COMPONENT DESCRIPTION: Call assumes existence of ENT, PAR, INST, and VAL. It returns output in ERR. For description of these variables, see DBIA 2263 for variables Entity, Parameter, Instance, Value, and Error. VARIABLES: i TYPE: Input VARIABLES: PAR TYPE: Input VARIABLES: INST TYPE: Input VARIABLES: VAL TYPE: Input VARIABLES: ERR TYPE: Output SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2336 IA #: 2336 DATE CREATED: MAY 11, 1998 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XPAREDIT NAME: SUPPORTED CALLS TO XPAREDIT ID: XPAREDIT GENERAL DESCRIPTION: This DBIA contains a list of calls which are supported for use. The calls are part of the Parameter Tools component of Toolkit. Parameter Tools is a generic method of handling parameter definition, assignment, and retrieval. See DBIA 2263 for the main entry points to this module. This DBIA contains calls to XPAREDIT which contain some additional utilities to for editing parameters. STATUS: Active MAIL MESSAGE: 27947783 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: This entry point can be called to prompt the user for a parameter to edit. This is provided more as a tool for developers and not for exported calls as it allows editing of ANY parameter. COMPONENT/ENTRY POINT: TED(Template,ReviewFlags,AllEntities) COMPONENT DESCRIPTION: TED^XPAREDIT(Template,ReviewFlags,AllEntities) allows editing of parameters defined in a template. The parameters in the template are prompted in more of a FileMan style - prompt by prompt. No dashed line dividers are displayed between each parameter. Since the dashed line headers are suppressed, it is important to define the VALUE TERM for each parameter in the template, as this is what is used to prompt for the value. VARIABLES: Template TYPE: Input VARIABLES DESCRIPTION: REQUIRED The IEN or NAME of an entry in the Parameter Template file (#8989.52). VARIABLES: ReviewFlags TYPE: Input VARIABLES DESCRIPTION: OPTIONAL There are 2 flags (A and B) that can be used individually, together, or not at all. An 'A' indicates that the new values for the parameters in the template are displayed AFTER the prompting is done. 'B' indicates that the current values of the parameters will be displayed BEFORE editing. VARIABLES: AllEntities TYPE: Input VARIABLES DESCRIPTION: OPTIONAL This is a variable pointer that should be used as the entity for all parameters in the template. If left blank, prompting for the entity is done as defined in the PARAMETER TEMPLATE file. COMPONENT/ENTRY POINT: TEDH(Template,ReviewFlags,AllEntities) COMPONENT DESCRIPTION: This is similar to the TED^XPAREDIT call, except that the dashed line headers ARE shown between each parameter. For input variable definitions, see TED component/entry point. VARIABLES: Template TYPE: Input VARIABLES: ReviewFlages TYPE: Input VARIABLES: AllEntities TYPE: Input COMPONENT/ENTRY POINT: EDITPAR(Parameter) COMPONENT DESCRIPTION: This entry point can be used to edit a single parameter. VARIABLES: Parameter TYPE: Input VARIABLES DESCRIPTION: Pass as the IEN or the NAME of the entry in the PARAMETER DEFINITION file (#8989.51) which you want to be edited. COMPONENT/ENTRY POINT: GETPAR(.Variable) COMPONENT DESCRIPTION: Allow user to select PARAMETER DEFINITION file entry. VARIABLES: OutputValue TYPE: Output VARIABLES DESCRIPTION: Returns the value Y in standard DIC look-up format. COMPONENT/ENTRY POINT: GETENT(.Entity,Parameter,.OnlyOne?) COMPONENT DESCRIPTION: Interactively prompts for an entity, based on the definition of a parameter. VARIABLES: Entity TYPE: Output VARIABLES DESCRIPTION: REQUIRED Returns the selected entity in variable pointer format. VARIABLES: Parameter TYPE: Input VARIABLES DESCRIPTION: REQUIRED Specifies the parameter for which an entity should be selected. Parameter should contain two pieces: IEN^DisplayNameOfParameter. VARIABLES: OnlyOne? TYPE: Output VARIABLES DESCRIPTION: OPTIONAL Returns "1" if there is only one possible entity for the value. For example, if the parameter can only be set for the system, OnlyOne?=1. If the parameter could be set for any location, OnlyOne?=0. COMPONENT/ENTRY POINT: EDIT(Entity,Parameter) COMPONENT DESCRIPTION: Interactively edits the instance (if multiple instances are allowed) and the value for a parameter associated with a given entity. VARIABLES: Entity TYPE: Input VARIABLES DESCRIPTION: REQUIRED Identifies the specific entity for which a parameter may be edited. Entity must be in variable pointer format. VARIABLES: Parameter TYPE: Input VARIABLES DESCRIPTION: REQUIRED Identifies the parameter that should be edited. Parameter should contain two pieces: IEN^DisplayNameOfParameter. COMPONENT/ENTRY POINT: BLDLST(.List,Parameter) COMPONENT DESCRIPTION: This entry point will return, in the array List, all entities allowed for the input Parameter. VARIABLES: List TYPE: Input VARIABLES DESCRIPTION: Name of array to receive output. VARIABLES: Parameter TYPE: Input VARIABLES DESCRIPTION: IEN of entry in the PARAMETER DEFINITION file. NUMBER: 2338 IA #: 2338 DATE CREATED: MAY 11, 1998 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XDRMERGB NAME: DBIA2338 ID: XDRMERGB GENERAL DESCRIPTION: During special processing related to the Patient Merge, the routine IBAXDR needs to call the entry point SAVEMERG^XDRMERGB. This call is used to save the file image of an entry involved in the merge process when only one of the entries (the entry being merged or the entry being merged into) is present in [FILENUM]. Normally, the merge process would handle when it can identify a FROM or a TO entry which is not present based on the DINUMed values. For [FILENUM], however, the internal entry numbers are determined from the "B"-cross- reference, and missing entries need to be handled separately. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34019124 COMPONENT/ENTRY POINT: SAVEMERG COMPONENT DESCRIPTION: This entry point acts to save an image of the currently existing data for the merge entry and merged into entry in the MERGE IMAGE file (#15.4). VARIABLES: FILENUM TYPE: Input VARIABLES DESCRIPTION: This is the file number for the file which is being merged and for which the images are to be saved. VARIABLES: IENFROM TYPE: Input VARIABLES DESCRIPTION: The internal entry number of the FROM entry (the entry being merged into another entry). VARIABLES: IENTO TYPE: Input VARIABLES DESCRIPTION: The internal entry number of the TO entry (the entry into which the entry is being merged). SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING DETAILS: FILENUM = 391.1 SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE SUBSCRIBING DETAILS: FILENUM = 340 SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING DETAILS: FILENUM = 53.79 EDITOR: DEVILLERS,NANCY NUMBER: 2340 IA #: 2340 DATE CREATED: MAR 05, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIK NAME: DIU(0) ID: DIK GENERAL DESCRIPTION: Specific to preventing DIK from running cross-references which include a test for the value of DIU(0) not being present. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26414569 COMPONENT/ENTRY POINT: DIK COMPONENT DESCRIPTION: The variable DIU(0) will be set to a value of 1 VARIABLES: DIU(0) TYPE: Input VARIABLES DESCRIPTION: SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: SOCIAL WORK ISC: Birmingham SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: IFCAP SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING SUBSCRIBING PACKAGE: AUTOMATED LAB INSTRUMENTS SUBSCRIBING DETAILS: added 3/6/08 EDITOR: WINN,TAMI EDITOR: OGI,MICHAEL DATE/TIME EDITED: MAR 06, 2008@10:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SMULLEN,GEOFF WITH CONCURRENCE OF: ORMSBY,SKIP NUMBER: 2341 IA #: 2341 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: MAR 05, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2341 ID: DPT( GENERAL DESCRIPTION: The Patient Merge application of the Kernel Toolkit requests a private integration agreement to set the variable VAFCA08 during a merge process. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26414741 COMPONENT/ENTRY POINT: PATIENT FILE COMPONENT DESCRIPTION: The major demographic fields are involved. VARIABLES: VAFCA08 TYPE: Used VARIABLES DESCRIPTION: Setting VAFCA08=1 will prevent the REQUIRES TRANSMISSION flag from being set. SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 2342 IA #: 2342 FILE NUMBER: 771 GLOBAL ROOT: HL(771, DATE CREATED: MAY 27, 1998 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2342 ID: HL(771, GLOBAL REFERENCE: HL(771,D0,0) FIELD NUMBER: 2 FIELD NAME: ACTIVE/INACTIVE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Surgery package is granted permission to do a direct global read of the ACTIVE/INACTIVE field (#2) in the HL7 APPLICATION PARAMETER file (#771). Reading this field will allow the Surgery package to determine if the HL7 application associated with the Surgery HL7 interface is active or not. If the HL7 application is not active, the call to the Surgery HL7 interface will quit, thus avoiding needless processing. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27044068 SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 2343 IA #: 2343 DATE CREATED: MAR 10, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUSER NAME: DBIA2343 ID: XUSER CREATOR: MENDOZA,RAUL E GENERAL DESCRIPTION: The routine XUSER has supported entry points to lookup a user and to check if a user is active, and also to return a user's full name. Also a CPRS check for provider. STATUS: Active MAIL MESSAGE: 58389812 COMPONENT/ENTRY POINT: $$LOOKUP COMPONENT DESCRIPTION: Usage S LRDOC=$$LOOKUP^XUSER("") This extrinsic function will do a lookup on the NEW PERSON file screening out uses that are TERMINATED. By default the call will ask if the correct user was selected. ie: Select NEW PERSON NAME: XUUSER,THREE Is XUUSER,THREE the one you want? YES// If the parameter is set to "Q" then this extra question is suppressed. The return is in the same format as a call to DIC. IEN^NAME Adding new entry's isn't allowed. VARIABLES: $$LOOKUP TYPE: Output VARIABLES DESCRIPTION: The return is in the same format as a call to DIC. IEN^NAME COMPONENT/ENTRY POINT: $$ACTIVE COMPONENT DESCRIPTION: Usage S X=$$ACTIVE^XUSER(ien) Parameter: pointer to the NEW PERSON file. It returns the following codes: "" No user record. 0 User can't sign-on. 0^DISUSER User can't sign-on because of DISUSER flag. 0^TERMINATED^2980310 User terminated on date. 1^NEW A new user, could sign-on. 1^ACTIVE^2980310.09 An active user, last sign-on date. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: This is the IEN for the entry to be checked. VARIABLES: $$ACTIVE TYPE: Output VARIABLES DESCRIPTION: "" No user record. 0 User can't sign-on. 0^DISUSER User can't sign-on because of DISUSER flag. 0^TERMINATED^2980310 User terminated on date. 1^NEW A new user, could sign-on. 1^ACTIVE^2980310.09 An active user, last sign-on date. COMPONENT/ENTRY POINT: $$PROVIDER COMPONENT DESCRIPTION: This entry point was added for CPRS. The definition of a provider is any entry in the new person file that doesn't have a termination date. A second parameter could be added to invoke other checks. Usage S X=$$PROVIDER^XUSER(ien) Parameter: pointer to the NEW PERSON file. It returns the following codes: "" No user record. "0^TERMINATED^2980310" User terminated on date. "1" Has a record and no termination date. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: This is the IEN for the entry to be checked. VARIABLES: $$PROVIDER TYPE: Output VARIABLES DESCRIPTION: "" No user record. "0^TERMINATED^2980310" User terminated on date. "1" Has a record and no termination date. COMPONENT/ENTRY POINT: $$DEA COMPONENT DESCRIPTION: The DEA ePCS project requires an API to obtain the value stored in the DEA# field (#53.2) in the NEW PERSON file (#200). This patch provides this new API and also adds a new field, FACILITY DEA NUMBER (#52), to the INSTITUTION file (#4). The specific API information follows: Usage: S X=$$DEA^XUSER(FLAG,IEN) This routine will return a user's DEA number, if it exists in the DEA# field (#53.2) of the NEW PERSON file (#200). If the DEA# field value is null, the value returned depends on the optional FLAG input parameter, see below. *NOTE: Fee Basis,C&A providers only return DEA# or null. VARIABLES: $$DEA TYPE: Output VARIABLES DESCRIPTION: DEA# field (#53.2) value or the value returned based on the (optional) FLAG input parameter, see "Input Parameter" above. *Note: Fee Basis,C&A providers will only return DEA# or null. Example 1: --------- DEA# (#53.2) field is "AB1234567" FACILITY DEA NUMBER field (#52) is "VA7654321" VA# field (#53.3) is "789" If the FLAG input parameter is null or "0", this API would return "AB1234567". If the FLAG input parameter is "1", this API would return "AB1234567". Example 2: --------- DEA# (#53.2) field is null FACILITY DEA NUMBER field (#52) is "VA7654321" VA# field (#53.3) is "789" If the FLAG input parameter is null or "0", this API would return "VA7654321-789". If the FLAG input parameter is "1", this API would return "789" Example 3: --------- DEA# (#53.2) field is null FACILITY DEA NUMBER field (#52) is "VA7654321" VA# field (#53.3) is null If the FLAG input parameter is null or "0", this API would return "". If the FLAG input parameter is "1", this API would return "" In both cases it returns an empty string. Example 4: --------- DEA# (#53.2) field is null FACILITY DEA NUMBER field (#52) is "VA7654321" VA# field (#53.3) is "789" PROVIDER TYPE field (#53.6) is "FEE BASIS" or "C&A" If the FLAG input parameter is null or "0", this API would return "". If the FLAG input parameter is "1", this API would return "" In both cases it returns an empty string. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: This is the New Person file (#200) IEN for the entry to be checked. VARIABLES: FLAG(optional) TYPE: Input VARIABLES DESCRIPTION: This flag controls what is returned when the user does not have a value in the DEA# field (#53.2) of the NEW PERSON file (#200). * FLAG is null or "0" -- This routine will check to see if the user has values in the VA# field (#53.3) of the NEW PERSON file (#200) and the (new) FACILITY DEA NUMBER field (#52) of the INSTITUTION file (#4). If values are found in both of those fields, this routine will return the following: FACILITY DEA NUMBER field (#52)_"-"_VA# field(#53.3) * FLAG is "1" -- This routine will check to see if the user has a value in the VA# field (#53.3) of the NEW PERSON file (#200). If a value is found in that field, this routine will return that field value. Otherwise, this routine returns an empty string. COMPONENT/ENTRY POINT: $$NAME COMPONENT DESCRIPTION: This entry point returns the full name of the specified user in a mixed case displayable format; the user's given name (i.e. First Last) will be returned unless a second parameter of "F" is passed in to get the Family name (i.e. Last,First) Usage: S NAME=$$NAME^XUSER(IEN[,format]) VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: This is the IEN of the user in the New Person file #200. VARIABLES: FORMAT(optional) TYPE: Input VARIABLES DESCRIPTION: This should be either "F" or "G", to indicate if the user's name should be returned formatted by Family or Given name, respectively. For example, "F"-Family (e.g., "Xuuser,Two") "G"(default)-Given (e.g., "Two Xuuser") VARIABLES: $$NAME TYPE: Output VARIABLES DESCRIPTION: The full name of the specified user in a mixed case displayable format; the user's given name (i.e. First Last) will be returned unless a second parameter of "F" is passed in to get the Family name (i.e. Last,First) COMPONENT/ENTRY POINT: $$SDEA COMPONENT DESCRIPTION: The DEA e-Prescribing of Control Substances project requires an API to utilize the following 'Privileges Algorithm' to check for prescribing privileges: -Blank = never answered (Allow all schedules but system to send the followingelectronic message: "DEA credentials have not been populated, call TBD responsible person.") -Any or all fields are answered = provide explicit set of permissions (that have been identified). -If it is answered that Prescriber has No privileges for all schedules = remove DEA number or VA number from file 200. -If Prescriber has been issued a DEA number, you have privileges. -If the Prescriber has been issued a VA number, this is a presumption of privileges. (Note: All of these checks do not apply to documentation of non-VA medication.) This API calls the $$DEA^XUSER() API (documented within this ICR). Usage: S X=$$SDEA^XUSER(FG,IEN,PSDEA) VARIABLES: FG(optional) TYPE: Input VARIABLES DESCRIPTION: This flag is used for $$DEA call refer to description under $$DEA^XUSER component. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: This is the New Person file (#200) IEN for the entry to be checked. VARIABLES: PSDEA TYPE: Input VARIABLES DESCRIPTION: This parameter is DEA schedule. DEA schedule is a 2-6 position field. It comes from the DRUG file (#50) in Pharmacy. This field is used, by this API, to verify the provider is allowed to write orders for specific controlled substances. For example: if the schedule is 2A, this indicates a controlled substance, schedule 2. Chart for all values: 0 MANUFACTURED IN PHARMACY 1 SCHEDULE 1 ITEM 2 SCHEDULE 2 ITEM 3 SCHEDULE 3 ITEM 4 SCHEDULE 4 ITEM 5 SCHEDULE 5 ITEM 6 LEGEND ITEM 9 OVER-THE-COUNTER L DEPRESSANTS AND STIMULANTS A NARCOTICS AND ALCOHOLS P DATED DRUGS I INVESTIGATIONAL DRUGS M BULK COMPOUND ITEMS C CONTROLLED SUBSTANCES - NON NARCOTIC R RESTRICTED ITEMS S SUPPLY ITEMS B ALLOW REFILL (SCH. 3, 4, 5 ONLY) W NOT RENEWABLE F NON REFILLABLE E ELECTRONICALLY BILLABLE N NUTRITIONAL SUPPLEMENT U SENSITIVE DRUG VARIABLES: $$SDEA TYPE: Output VARIABLES DESCRIPTION: Returns: DEA# or Facility DEA_"-"_user VA# similar to the $$DEA call. 1 - DEA# is null from the $$DEA call. 2 - when all schedules equals '0'. 4^expiration date - DEA# expiration date has expired. It will check if DEA# and expiration date are not null. The expiration date is returned in external format. COMPONENT/ENTRY POINT: $$DETOX COMPONENT DESCRIPTION: The DEA e-Prescribing of Control Substances project requires an API to obtain the value storted in the DETOX/MAINTENANCE ID NUMBER field (#53.11) in the New Person file (#200). This routine will return a user's DETOX/MAINTENANCE ID number, if it exists in the field (#53.11) of the NEW PERSON file (#200). The value is null if DETOX/MAINTENANCE ID number is null or the DEA EXPERATION DATE field (#747.44) in the NEW PERSON file (#200) is unpopulated. The third value that is returned is the DEA EXPIRATION DATE (#747.44). This date is returned when the DETOX/MAINTENANCE ID number is valid but the DEA EXPIRATION DATE has expired. Usage: S X=$$DETOX^XUSER(IEN) VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: The IEN of user in NEW PERSON file (#200). VARIABLES: $$DETOX TYPE: Output VARIABLES DESCRIPTION: The return value is one of three values: DETOX/MAINTENANCE ID number - if valid. Null, the DETOX/MAINTENANCE ID number is null or the DEA EXPERATION DATE field (#747.44) in the NEW PERSON file (#200) is unpopulated. DEA EXPIRATION DATE (#747.44), when the DETOX/MAINTENANCE ID number is valid but the DEA EXPIRATION DATE has expired. COMPONENT/ENTRY POINT: $$VDEA COMPONENT DESCRIPTION: The DEA electronic Prescribing of Controlled Substances (ePCS) project requires an API to determine if a user in the NEW PERSON file (#200) is able to sign orders for controlled substances. Usage: S X=$$VDEA^XUSER(.RETURN,IEN) VARIABLES: RETURN TYPE: Input VARIABLES DESCRIPTION: This is a reference to an array where the reasons why the user cannot sign orders for controlled substances and which DEA schedules the user can prescribe will be returned in. For example, RETURN("Is permitted to prescribe all schedules.)="" VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: This is the IEN of the user in the NEW PERSON file (#200). VARIABLES: $$VDEA TYPE: Output VARIABLES DESCRIPTION: Returns 1 if the user is able to sign orders for controlled substances and 0 if the user is not able to sign orders for controlled substances. VARIABLES: RETURN TYPE: Output VARIABLES DESCRIPTION: This array contains the reasons why the user cannot sign orders for controlled substances and which DEA schedules the user can prescribe. For example, RETURN("Is not permitted to prescribe any schedules.")="" DBA Comments: 7/23/14-Reactivate ICR #2343. The ICR was opened for edits on 10/26/11. Raul indicated he added a new API for the DEA ePCS project ($$SDEA, $$DETOX and $$VDEA). Mohamed requested ICR be activated on 6/17/14 for the Safety Updates for Medication/Prescription Management (SUMPM). Patch # is PSO*7*408. Raul made additional updates to $$LOOKUP and $NAME - changed names to XUSER format, $$DEA - reworded description and removed TPD, and $$DETOX - change 53.1 to 53.11. DATE ACTIVATED: JUL 23, 2014 DATE/TIME EDITED: OCT 26, 2011@13:16 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: MENDOZA,RAUL DATE/TIME EDITED: JUL 23, 2014@09:49 ACTION: APPROVED AT THE REQUEST OF: ANWER,MOHAMED WITH CONCURRENCE OF: MENDOZA,RAUL NUMBER: 2345 IA #: 2345 FILE NUMBER: 410 GLOBAL ROOT: PRCS DATE CREATED: JUN 01, 1998 CUSTODIAL PACKAGE: IFCAP USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: D&PPM ID: PRCS GLOBAL REFERENCE: PRCS(410,D0,0) FIELD NUMBER: 4 FIELD NAME: INVENTORY DISTRIBUTION POINT LOCATION: 0;6 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26450016 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 2346 IA #: 2346 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: MAR 24, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2346 ID: DPT( GLOBAL REFERENCE: DPT(D0,.31) FIELD NUMBER: .314 FIELD NAME: CLAIM FOLDER LOCATION LOCATION: .31;4 ACCESS: Read w/Fileman FIELD DESCRIPTION: The original version of the option "Individual Patient Record" references the CLAIM FOLDER LOCATION field (#.312) of the PATIENT File. This was not on the supported reference list. This field, CLAIM FOLDER LOCATION(#.312), has been starred for deletion. In our cleanup of the VIST software, we replaced this with the new field CLAIM FOLDER LOCATION(#.314). We will need a DBIA to allow this type of read. The lines of code read: S DIC="^DPT(",DA=DFN,DR=.314,DIQ="ANRV(" D EN^DIQ1 S ANRV(8)=ANRV(2,DFN,.314) FIELD NUMBER: .313 FIELD NAME: CLAIM NUMBER LOCATION: .31;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: The VARO CLAIMS file (#2043.5) has a print template [ANRV CLAIM REQ INQ] used in the option "Individual Claims Record" that references the CLAIM NUMBER field .313 in the PATIENT File (#2). We request read access on the CLAIM NUMBER field in the PATIENT file via FileMan extended syntax. GLOBAL REFERENCE: DPT(D0,.372,D1,0) FIELD NUMBER: .01 FIELD NAME: RATED DISABILITIES (VA) LOCATION: .372,D1;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The routines used for the option "Individual Patient Record" reference the .372 node (Rated Disabilities sub-file). This is not on the supported reference list and I do not know of a supported API. We need a DBIA to have read access on the .372 node of the PATIENT file. The lines of code look like this: F I=0:0 S I=$O(^DPT(DFN,.372,I)) Q:'I D .S Y=+$G(^DPT(DFN,.372,I,0)),Y(1)=$P(^(0),U,2) FIELD NUMBER: .02 FIELD NAME: PERCENTAGE LOCATION: .372,D1;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The routines used for the option "Individual Patient Record" reference the .372 node (Rated Disabilities sub-file). This is not on the supported reference list and I do not know of a supported API. We need a DBIA to have read access on the .372 node of the PATIENT file. The lines of code look like this: F I=0:0 S I=$O(^DPT(DFN,.372,I)) Q:'I D .S Y=+$G(^DPT(DFN,.372,I,0)),Y(1)=$P(^(0),U,2) GLOBAL REFERENCE: DPT(D0,.36) FIELD NUMBER: .361 FIELD NAME: PRIMARY ELIGIBILITY CODE LOCATION: .36;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: VIST ROSTER File (#2040) .01 Field trigger references the PRIMARY ELIGIBILITY CODE Field (.361) in the PATIENT File. The trigger moves the current information from the PRIMARY ELIGIBILITY CODE field (.361) into the VA ELIGIBILITY CODE field in the VIST ROSTER file when the patient's name is added. We request the ability to access this field via a FileMan trigger cross-reference. GLOBAL REFERENCE: DPT(D0,.32) FIELD NUMBER: .323 FIELD NAME: PERIOD OF SERVICE LOCATION: .32;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: The VIST ROSTER File (#2040) contains a computed field PERIOD OF SERVICE that uses the field PERIOD OF SERVICE .323 in the PATIENT File. We request a DBIA to access the PERIOD OF SERVICE field in the PATIENT File (#2) via FileMan. GLOBAL REFERENCE: DPT(D0,.11) FIELD NUMBER: .117 FIELD NAME: COUNTY LOCATION: .11;7 ACCESS: Read w/Fileman FIELD DESCRIPTION: The VIST ROSTER file (#2040) contains a computed field COUNTY (10) that uses the COUNTY field (.117) and the STATE field (.115) in the PATIENT File (#2). We need to request a DBIA to access the COUNTY field (.117) and the STATE field (.115) in the PATIENT file (#2) via FileMan. The computed field has the following algorithm: NAME:STATE:COUNTY:COUNTY:NAME_VA COUNTY CODE_COUNTY The actual FileMan generated code reads as follows: 2040,10 COUNTY ; COMPUTED MUMPS CODE: X ^DD(2040,10,9.6) S X=X_$P(Y(2040,10,303),U,3) _$P(Y(2040,10,303),U,1) S D0=Y(2040,10,80) S D1=Y(2040,10,281) 9.2 = S I(200)="^DIC(5,",J(200)=5 F D=0:0 S (D,D1)=$N(^DIC(5,D0,1,D)) Q:D'>0 I $D(^(D,0))#2 S X=$P(^(0),U,1) X DICMX Q:'$D(D) S D=D1 9.3 = S Y(2040,10,80)=$S($D(D0):D0,1:""),Y(2040 ,10,1)=$S($D(^ANRV(2040,D0,0)):^(0),1:""), D0=$P (Y(2040,10,1),U,1) S:'$D(^DPT(+D0,0)) D0=-1 S Y (2040,10,180)=$S($D(D0):D0,1:"") 9.4 = X ^DD(2040,10,9.3) S Y(2040,10,101)=$S($D (^DPT(D0,.11)):^(.11),1:""),D0=$P(Y(2040,1 0,101 ),U,5) S:'$D(^DIC(5,+D0,0)) D0=-1 S Y(2040,10,2 80)=$S($D(D0):D0,1:"") 9.5 = X ^DD(2040,10,9.4) S Y(2040,10,281)=$S($D (D1):D1,1:"") X ^DD(2040,10,9.2):D0>0 S X="" K DIC S Y=-1,DIC="^DIC(5,D0,1,",DIC(0)="NMF" D ^DIC:D0>0 S (D,D1)=+Y FIELD NUMBER: .115 FIELD NAME: STATE LOCATION: .11;5 ACCESS: Read w/Fileman FIELD DESCRIPTION: The VIST ROSTER file (#2040) contains a computed field COUNTY (10)that uses the COUNTY field (.117) and the STATE field (.115) in the PATIENT File (#2). We need to request a DBIA to access the COUNTY field (.117) and the STATE field (.115) in the PATIENT file (#2) via FileMan. The computed field has the following algorithm: NAME:STATE:COUNTY:COUNTY:NAME_VA COUNTY CODE_COUNTY The actual FileMan generated code reads as follows: 2040,10 COUNTY ; COMPUTED MUMPS CODE: X ^DD(2040,10,9.6) S X=X_$P(Y(2040,10,303),U,3) _$P(Y(2040,10,303),U,1) S D0=Y(2040,10,80) S D1=Y(2040,10,281) 9.2 = S I(200)="^DIC(5,",J(200)=5 F D=0:0 S (D,D1)=$N(^DIC(5,D0,1,D)) Q:D'>0 I $D(^(D,0))#2 S X=$P(^(0),U,1) X DICMX Q:'$D(D) S D=D1 9.3 = S Y(2040,10,80)=$S($D(D0):D0,1:""),Y(2040 ,10,1)=$S($D(^ANRV(2040,D0,0)):^(0),1:""), D0=$P (Y(2040,10,1),U,1) S:'$D(^DPT(+D0,0)) D0=-1 S Y (2040,10,180)=$S($D(D0):D0,1:"") 9.4 = X ^DD(2040,10,9.3) S Y(2040,10,101)=$S($D (^DPT(D0,.11)):^(.11),1:""),D0=$P(Y(2040,1 0,101),U,5) S:'$D(^DIC(5,+D0,0)) D0=-1 S Y(2040,10,2 80)=$S($D(D0):D0,1:"") 9.5 = X ^DD(2040,10,9.4) S Y(2040,10,281)=$S($D (D1):D1,1:"") X ^DD(2040,10,9.2):D0>0 S X="" K DIC S Y=-1,DIC="^DIC(5,D0,1,",DIC(0)="NMF" D ^DIC:D0>0 S (D,D1)=+Y GENERAL DESCRIPTION: We were tasked to make the class III VIST software a nationally supported product. In doing so, we eliminated many of the unsupported calls to other packages and files. The following is a list of the remaining unsupported calls to the PATIENT file (#2). We will need a DBIA to cover these calls. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26575755 SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM ISC: Birmingham NUMBER: 2347 IA #: 2347 FILE NUMBER: 161 GLOBAL ROOT: FBAAA( DATE CREATED: MAR 24, 1998 CUSTODIAL PACKAGE: FEE BASIS USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2347 ID: FBAAA( GLOBAL REFERENCE: FBAAA(D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: FROM DATE LOCATION: 1;1 ACCESS: Read w/Fileman FIELD NUMBER: .02 FIELD NAME: TO DATE LOCATION: 1;2 ACCESS: Read w/Fileman FIELD NUMBER: .095 FIELD NAME: TREATMENT TYPE CODE LOCATION: 1;13 ACCESS: Read w/Fileman GLOBAL REFERENCE: FBAAA(D0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: We were tasked to make the class III VIST software a nationally supported product. In doing so, we eliminated many of the unsupported calls to other packages and files. The following is a list of the remaining unsupported calls to the FEE BASIS PATIENT file (#161). The VIST software contains a report titled "Fee Basis List". It includes a sort template [ANRV FEE PT] and print template [ANRV FEE PT] with references to NAME (.01), the AUTHORIZATION multiple subfile (#161.01), FROM DATE(.01), TO DATE(.02), and TREATMENT TYPE CODE (.095) fields in the FEE BASIS PATIENT File (#161). We request read access via FileMan extended syntax for the FEE BASIS PATIENT fields NAME, AUTHORIZATION, FROM DATE, TO DATE, and TREATMENT TYPE CODE. Below is a capture of the templates in question and the report it generates. Here is an example of the report output; FEE PATIENT LISTING MAR 19,1998 12:40 PAGE 1 NAME SSN FROM DATE TO DATE TREATMENT TYPE CODE -------------------------------------------------------------------------- JONES,MICK 222-33-4444 FEB 17,1998 APR 18,1998 I.D. CARD STATUS ------------------------------ COUNT 1 This is a copy of the Sort Template; WANT TO EDIT 'ANRV FEE PT' TEMPLATE? NO// y YES NAME: ANRV FEE PT// READ ACCESS: WRITE ACCESS: SORT BY: @INTERNAL(VIST ELIGIBLE (AMIS))'="I";L1 Replace By 'VIST ELIGIBLE ', do you mean VIST ROSTER 'VIST ELIGIBLE (AMIS)'? Yes// (Yes) WITHIN INTERNAL(VIST ELIGIBLE (AMIS))'="I", SORT BY: @NAME// * Previous selection: NAME not null START WITH NAME: FIRST// WITHIN NAME, SORT BY: AUTHORIZATION// NAME:FEE BASIS PATIENT: By 'FEE BASIS PATIENT', do you mean the FEE BASIS PATIENT File, pointing via its 'NAME' Field? Yes// (Yes) FEE BASIS PATIENT FIELD: 1// AUTHORIZATION (multiple) AUTHORIZATION SUB-FIELD: TREATMENT TYPE CODE["CARD"&(TO DATE>T);L1 Replace WITHIN TREATMENT TYPE CODE["CARD"&(TO DATE>T), SORT BY: STORE IN 'SORT' TEMPLATE: This is a copy of the Print template; WANT TO EDIT 'ANRV FEE PT' TEMPLATE? No// Y (Yes) NAME: ANRV FEE PT// READ ACCESS: WRITE ACCESS: FIRST PRINT FIELD: NAME;C1!// THEN PRINT FIELD: NAME:$E(SSN,1,3)_"-"_$E(SSN,4,5)_"-"_$E(SSN,6,9);"SSN" Replace By 'SSN', do you mean PATIENT 'SOCIAL SECURITY NUMBER'? Yes// (Yes) By 'SSN', do you mean PATIENT 'SOCIAL SECURITY NUMBER'? Yes// (Yes) By 'SSN', do you mean PATIENT 'SOCIAL SECURITY NUMBER'? Yes// (Yes) THEN PRINT FIELD: NAME:FEE BASIS PATIENT: Replace By 'FEE BASIS PATIENT', do you mean the FEE BASIS PATIENT File, pointing via its 'NAME' Field? Yes// (Yes) THEN PRINT FEE BASIS PATIENT FIELD: AUTHORIZATION// (multiple) THEN PRINT AUTHORIZATION SUB-FIELD: FROM DATE;C48// THEN PRINT AUTHORIZATION SUB-FIELD: TO DATE// THEN PRINT AUTHORIZATION SUB-FIELD: TREATMENT TYPE CODE// THEN PRINT AUTHORIZATION SUB-FIELD: THEN PRINT FEE BASIS PATIENT FIELD: THEN PRINT FIELD: We will need a DBIA to cover these calls. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26575786 SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM ISC: Birmingham NUMBER: 2348 IA #: 2348 DATE CREATED: MAR 24, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXUTLSCC NAME: SERVICE CONNECTED CONDITIONS ID: PXUTLSCC GENERAL DESCRIPTION: This API returns if the Service Connected and Conditions should/can be asked for a patient at a date/time. It also returns the current answers if any in Scheduling for an encounter for the patient at that date/time. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26487854 COMPONENT/ENTRY POINT: SCCOND COMPONENT DESCRIPTION: Format of call: D SCCOND^PXUTLSCC(DFN,ENCDT,HOSPLOC,VISIT,.RETURN) Input Parameters: DFN pointer to PATIENT file (#2) ENCDT date and time of the encounter HOSPLOC pointer to HOSPITAL LOCATION file (#44) for the enocunter VISIT (optional) pointer to VISIT file (#9000010) for the encounter if know Output Parameters: RETURN this is an array subscriped by "SC","CV","AO","IR","EC", "SHAD","MST", and "HNC" that contains to piece each first piece: 1 if the condition can be answered 0 if it should be null second piece: the answer that Scheduling has if it has one 1 ::= yes, 0 ::= no example: >ZW RETURN RETURN("AO") = "1^1" RETURN("EC") = "0^" RETURN("IR") = "0^" RETURN("SC") = "1^0" RETURN("MST") = "0^" RETURN("HNC") = "0^" Can ask SC and if it is no then can ask AO but do not ask EC or IR. The current answers stored in Scheduling are NO for SC and YES for AO. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: CLINICAL PROCEDURES NUMBER: 2349 IA #: 2349 DATE CREATED: MAR 24, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAPI NAME: ACTIVE PROVIDER ID: PXAPI GENERAL DESCRIPTION: This checks to see if a provider is active on the system and if they have an active Person Class on a given date. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26487854 COMPONENT/ENTRY POINT: ACTIVPRV COMPONENT DESCRIPTION: Format of Call $$ACTIVPRV^PXAPI(PROVIDER,DATETIME) Input parameters: PROVIDER pointer to provider in the NEW PERSON file (#200) DATETIME (optional) the date (and optional time) of to check if not passed the DT is used Returns 1 if provider is good 0 if provider is not active or does not have a Person Class on given date COMPONENT/ENTRY POINT: PRVCLASS COMPONENT DESCRIPTION: Format of call: $$PRVCLASS^PXAPI(PROVIDER,DATETIME) Input parameters: PROVIDER pointer to provider in the NEW PERSON file (#200) DATETIME (optional) the date (and optional time) to check if not passed the DT is used Returns IEN^Occupation^specialty^sub-specialty^Effective date^expiration date ^VA Code if + of the return is >0 provider is active else -1 the provider is not active or bad call else -2 if no current person class SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING DETAILS: ADDED 7/13/07 DATE/TIME EDITED: JUL 13, 2007@09:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SHETLER,BOB WITH CONCURRENCE OF: FAIN,ZACHARY NUMBER: 2350 IA #: 2350 DATE CREATED: MAR 26, 1998 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2350 GENERAL DESCRIPTION: Pharmacy Data Management requests permission to export the Inpatient Medications menu option PSJI IVCATEGORY. VIEWER: SCHLEHUBER,CAMERON VIEWER: MONTALI,MICHAEL VIEWER: TATUM,WILLIAM VIEWER: WASHINGTON,JANET P VIEWER: CHRISTENSEN,KIM VIEWER: BARRON,LUANNE VIEWER: VO,MAI VIEWER: BAYLIS,RANDALL S VIEWER: HOLMES,TIM STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33261916 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2351 IA #: 2351 DATE CREATED: MAR 26, 1998 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBSDU NAME: OUTPATIENT ENCOUNTER SEARCH ID: IBSDU GENERAL DESCRIPTION: IBSDU is a routine I written for IB that provides a generic interface to the ACRP APPLICATION INTERFACE TOOL (AIT) introduced by Scheduling patch SD*5.3*131. The particular function that AICS needs is the 'SCAN' functionality that allows for a search for data in the encounter file without using the now prohibited direct file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26601926 COMPONENT/ENTRY POINT: SCAN COMPONENT DESCRIPTION: This entrypoint uses the ACRP Applications Interface Tools (AIT) to scan through a date or date range and find encounter data for one or more patients. It is parameter driven. VARIABLES: IBINDX TYPE: Input VARIABLES DESCRIPTION: The index name 'property' of the Outpaitent Encounter Query object. This is how the query will be scanned - by patient, patient and date, date or by encounter. This determines the the cross reference to be used to perform the scan. VALID VALUES: PATIENT = individual patient PATIENT/DATE = individual patient and date or date range DATE/TIME = date or date range VISIT = individual encounter VARIABLES: IBVAL TYPE: Input VARIABLES DESCRIPTION: This is an array containing the actual values to use to scan the Outpatient Encounter Query object: IBVAL("DFN") = Patient ien IBVAL("BDT") = Earliest date/time to start scan IBVAL("EDT") = Last date/time to include in the scan IBVAL("VIS") = Encounter ien VARIABLES: IBFILTER TYPE: Input VARIABLES DESCRIPTION: The executable code to be used to filter (screen) entries when scanning using the Outpatient Encounter Query object. Unless the Call Back logic is very complicated and time consuming, it is more efficient to add an 'IF' statement to the Call Back logic than to use the FILTER property. VARIABLES: IBCBK TYPE: Input VARIABLES DESCRIPTION: This is the code that is executed for every outpatient encounter found during the execution of the Outpatient Encounter Query object's SCAN event that passes the 'filter' logic, if any. This directs the object as to what it should do with each valid encounter it finds. VARIABLES: IBCLOSE TYPE: Input VARIABLES DESCRIPTION: This is a flag that stipulates whether the Query object should be closed once the scan is completed. Due to the overhead of setting up the Outpatient Encounter Query object, it should not be opened and closed each time it is called if it is being used to 'loop'. The first 'scan' would open the Query and the last one would indicate to close it. Valid Values: 0 (or null) - DO NOT CLOSE QUERY 1 - CLOSE QUERY ON COMPLETION VARIABLES: IBQUERY TYPE: Both VARIABLES DESCRIPTION: The number coresponding to the Outpatient Encounter Query object that needs to be executed. This parameter is optional for a Query that is being closed and will not be reused. If passed by reference and the object is not requested to close, the value returned can be used for subsequent calls to the object to avoid the overhead associated with the opening of a Query object. VARIABLES: IBDIR TYPE: Input VARIABLES DESCRIPTION: This is a flag [optional] that specifies the direction of the search. VALID VALUES: FORWARD or null - Scan from first to last (default if undefined) BACKWARD - Scan from last to first VARIABLES: IBZXERR TYPE: Input VARIABLES DESCRIPTION: This is the name of the array that will be returned containing any errors found during the SCAN. If this variable is not defined, no errors will be returned. All errors returned are in the same format as the errors returned in the Fileman database server calls. SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE DBA Comments: 2/14/14-MM: Added Accounts Receivable as a subscriber to ICR #2351. During the development of PRCA*4.5*299, it was discovered the call to SCAN~IBSDU in routine RCXVUTIL was not covered by an ICR. The developer requested to add Accounts Receivable as a subscriber to document the existing reference. DATE/TIME EDITED: FEB 14, 2014@11:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WANG,CHI NUMBER: 2353 IA #: 2353 FILE NUMBER: 9000010.11 GLOBAL ROOT: AUPNVIMM( DATE CREATED: APR 03, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2353-A ORIGINAL NUMBER: 2353 ID: AUPNVIMM( GLOBAL REFERENCE: AUPNVIMM( FIELD NUMBER: .04 FIELD NAME: SERIES LOCATION: [0;4] ACCESS: Read w/Fileman FIELD NUMBER: .06 FIELD NAME: REACTION LOCATION: [0;6] ACCESS: Read w/Fileman FIELD NUMBER: .07 FIELD NAME: CONTRAINDICATED LOCATION: [0;7] ACCESS: Read w/Fileman GENERAL DESCRIPTION: This is to allow for the reading of the set of codes with the Fileman call D FIELD^DID(9000010.11,field,"","POINTER","target_root","msg_root"). This is used by a RPC to pass the values for the field to the CPRS GUI. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26534080 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City EDITOR: RUBIN,ALICE NUMBER: 2354 IA #: 2354 FILE NUMBER: 9000010.12 GLOBAL ROOT: AUPNVSK( DATE CREATED: APR 03, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2353-B ORIGINAL NUMBER: 2353 ID: AUPNVSK( GLOBAL REFERENCE: AUPNVSK( FIELD NUMBER: .04 FIELD NAME: RESULTS LOCATION: [0;4] ACCESS: Read w/Fileman GENERAL DESCRIPTION: This is to allow for the reading of the set of codes with the Fileman call D FIELD^DID(9000010.12,field,"","POINTER","target_root","msg_root"). This is used by a RPC to pass the values for the field to the CPRS GUI. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26534080 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City EDITOR: RUBIN,ALICE NUMBER: 2355 IA #: 2355 FILE NUMBER: 9000010.13 GLOBAL ROOT: AUPNVXAM( DATE CREATED: APR 03, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2353-C ORIGINAL NUMBER: 2353 ID: AUPNVXAM( GLOBAL REFERENCE: AUPNVXAM( FIELD NUMBER: .04 FIELD NAME: RESULT LOCATION: [0;4] ACCESS: Read w/Fileman GENERAL DESCRIPTION: This is to allow for the reading of the set of codes with the Fileman call D FIELD^DID(9000010.13,field,"","POINTER","target_root","msg_root"). This is used by a RPC to pass the values for the field to the CPRS GUI. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26534080 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City EDITOR: RUBIN,ALICE NUMBER: 2356 IA #: 2356 FILE NUMBER: 9000010.16 GLOBAL ROOT: AUPNVPED( DATE CREATED: APR 03, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2353-D ORIGINAL NUMBER: 2353 ID: AUPNVPED( GLOBAL REFERENCE: AUPNVPED( FIELD NUMBER: .06 FIELD NAME: LEVEL OF UNDERSTANDING LOCATION: [0;6] ACCESS: Read w/Fileman GENERAL DESCRIPTION: This is to allow for the reading of the set of codes with the Fileman call D FIELD^DID(9000010.16,field,"","POINTER","target_root","msg_root"). This is used by a RPC to pass the values for the field to the CPRS GUI. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26534080 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City EDITOR: RUBIN,ALICE NUMBER: 2357 IA #: 2357 FILE NUMBER: 9000010.23 GLOBAL ROOT: AUPNVHF( DATE CREATED: APR 03, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2353-E ORIGINAL NUMBER: 2353 ID: AUPNVHF( GLOBAL REFERENCE: AUPNVHF( FIELD NUMBER: .04 FIELD NAME: LEVEL/SEVERITY LOCATION: [0;4] ACCESS: Read w/Fileman GENERAL DESCRIPTION: This is to allow for the reading of the set of codes with the Fileman call D FIELD^DID(9000010.23,field,"","POINTER","target_root","msg_root"). This is used by a RPC to pass the values for the field to the CPRS GUI. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26534080 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City EDITOR: RUBIN,ALICE NUMBER: 2358 IA #: 2358 DATE CREATED: APR 03, 1998 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOCAN3 NAME: DISCONTINUE OP MEDS ON DATE OF DEATH ID: PSOCAN3 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 22126657 COMPONENT/ENTRY POINT: APSOD(DA) COMPONENT DESCRIPTION: This is invoked from a Date of Death cross-reference to discontinue all active outpatient medications. It is effective for OP v 7 or higher. VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: The DFN of the Patient. SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 2360 IA #: 2360 FILE NUMBER: 405 GLOBAL ROOT: DGPM DATE CREATED: APR 08, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2360 ID: DGPM GLOBAL REFERENCE: DGPM(DO,0) FIELD NUMBER: .18 FIELD NAME: MAS MOVEMENT TYPE LOCATION: 0;18 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Field is a pointer to the MAS Movement Type file. GLOBAL DESCRIPTION: Global contains the following cross-reference: ^DGPM("ATID3", which lists all PATIENT MOVEMENT TYPES of DISCHARGE. Read access is also requested for this cross-referernce in order for the calculations to be accurate. GLOBAL REFERENCE: DGPM('ATID3', FIELD NUMBER: Cross Reference GENERAL DESCRIPTION: In order to calculate the percentage of deaths within a Medical Center that results in Autopsy, direct global reads of ^DGPM("ATID3", and $P(^DGPM(DO,0),U,18) are requested by the Laboratory Package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26700624 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 2361 IA #: 2361 DATE CREATED: APR 16, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: KILLING NODES IN DD FOR RATED DISABILITIES MULTIPLE GENERAL DESCRIPTION: The Registration Package requests permission to kill 'extra' nodes descendant from ^DD(2.04,0,"NM") in the post-install for patch DG*5.3*147, leaving only ^DD(2.04,0,"NM","RATED DISABILITIES (VA)"). Justification ============= We are currently in testing for patch DG*5.3*147, which is National Enrollment. In part, this software consists of the transmission of patient data to local sites and its upload. We discovered that UPDATE^DIE was failing, resulting in the loss of the patient's rated disabilities. The cause was prior corruption of the DD for the 2.04 multiple (Rated Disabilities (VA)). There are extra nodes at the "NM" cross-reference. Deleting the nodes solved the problem. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26785772 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 2362 IA #: 2362 FILE NUMBER: 19.081 GLOBAL ROOT: XUSEC(19, DATE CREATED: APR 21, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2362-A ORIGINAL NUMBER: 2362 ID: XUSEC(19, GLOBAL REFERENCE: XUSEC(19,D0,0) FIELD NUMBER: .01 FIELD NAME: OPTION LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field indicates the name of the option being audited. POINTER TO OPTION FILE (#19) FIELD NUMBER: 1 FIELD NAME: USER LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field indicates the name of the user who has accessed the option. POINTER TO NEW PERSON FILE (#200) FIELD NUMBER: 2 FIELD NAME: DEVICE LOCATION: 0;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: A free text field, this field indicates the device used while the option was accessed. FIELD NUMBER: 3 FIELD NAME: JOB LOCATION: 0;4 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field records the job number associated with the option access. FIELD NUMBER: 4 FIELD NAME: DATE/TIME OF EXIT FROM OPTION LOCATION: 0;5 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field marks the time when the user exited from the option. FIELD NUMBER: 5 FIELD NAME: CPU LOCATION: 0;6 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field records the CPU location of the option access. GLOBAL REFERENCE: XUSEC(19,D0,1) FIELD NUMBER: 6 FIELD NAME: MESSAGE NUMBER LOCATION: 1;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: For a Server-type option this field will contain the message number in the Message File that activated (or tried to activate) the server option. This message is called the 'server request.' FIELD NUMBER: 7 FIELD NAME: SENDER LOCATION: 1;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: For a Server-type option this field will contain the return address of the person who initiated the server request, that is, the name of the person who sent the message that activated (or tried to activate) the option. GLOBAL REFERENCE: XUSEC(19,D0,2) FIELD NUMBER: 8 FIELD NAME: SUBJECT LOCATION: 2;E1,65 ACCESS: Read w/Fileman FIELD DESCRIPTION: For a Server-type option this field will contain the subject of the MailMan message that activated (or tried to activate) the option. GLOBAL REFERENCE: XUSEC(19,D0,3) FIELD NUMBER: 9 FIELD NAME: ACTION LOCATION: 3;E1,245 ACCESS: Read w/Fileman FIELD DESCRIPTION: For a Server-type option this field will contain the resulting action of a server request. In the event of an error, the error will be trapped by the server software and entered into this field. GENERAL DESCRIPTION: Surgery request read access for all fields within the AUDIT LOG FOR OPTIONS File (#19.081), to produce a sorted audit report using the Surgery sort template, [SR BLOOD PRODUCT VERIFICATION]. The Surgery sort template, [SR BLOOD PRODUCT VERIFICATION] is coded to print the Audit Log for the Surgery option [SR BLOOD PRODUCT VERIFICATION] only. ^XUSEC(19,D0,0)= (#.01) OPTION [1P] ^ (#1) USER [2P] ^ (#2) DEVICE [3F] ^ ==>(#3) JOB [4N] ^ (#4) DATE/TIME OF EXIT FROM OPTION [5D] ^ ==>(#5) CPU [6F] ^ ^XUSEC(19,D0,1)= (#6) MESSAGE NUMBER [1N] ^ (#7) SENDER [2F] ^ ^XUSEC(19,D0,2)= (#8) SUBJECT [E1,65F] ^ ^XUSEC(19,D0,3)= (#9) ACTION [E1,245F] ^ ---------------------------------------------------------------------- Example of Sort Template SR BLOOD PRODUCT VERIFICATION; NAME: SR BLOOD PRODUCT VERIFICATION Replace READ ACCESS: @// WRITE ACCESS: @// SORT BY: ]DATE/TIME// * Previous selection: DATE/TIME from Jan 1,1998 START WITH DATE/TIME: FIRST// WITHIN DATE/TIME, SORT BY: OPTION["SR BLOOD PRODUCT VERIFICATION";L1 Replace WITHIN OPTION["SR BLOOD PRODUCT VERIFICATION", SORT BY: STORE IN 'SORT' TEMPLATE: FIRST PRINT FIELD: STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26817072 SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 2363 IA #: 2363 DATE CREATED: APR 21, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2362-B ORIGINAL NUMBER: 2362 GENERAL DESCRIPTION: The Surgery package requests permission to use the KERNEL print template, [XUOPTLOGP]. It will be called from the Surgery option, [SR BLOOD PRODUCT VERIFY AUDIT], to print the Audit Log for the Surgery option [SR BLOOD PRODUCT VERIFICATION]. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26817072 COMPONENT/ENTRY POINT: [XUOPTLOGP] COMPONENT DESCRIPTION: KERNEL print template [XUOPTLOGP] used to print selected auditted options from the AUDIT LOG FOR OPTIONS File (#19.081). SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 2364 IA #: 2364 FILE NUMBER: 450 GLOBAL ROOT: PRSPC( DATE CREATED: APR 21, 1998 CUSTODIAL PACKAGE: PAID CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ASISTS use of fields in File 450 ID: PRSPC( GLOBAL REFERENCE: PRSPC( FIELD NUMBER: .01 FIELD NAME: EMPLOYEE NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 6 FIELD NAME: STATION NUMBER LOCATION: 0;7 ACCESS: Read w/Fileman FIELD NUMBER: 8 FIELD NAME: SSN LOCATION: 0;9 ACCESS: Read w/Fileman FIELD NUMBER: 10 FIELD NAME: EDUCATION LOCATION: 0;11 ACCESS: Read w/Fileman FIELD NUMBER: 13 FIELD NAME: GRADE LOCATION: 0;14 ACCESS: Read w/Fileman FIELD NUMBER: 16 FIELD NAME: OCCUPATION SERIES & TITLE LOCATION: 0;17 ACCESS: Read w/Fileman FIELD NUMBER: 31 FIELD NAME: SEX LOCATION: 0;32 ACCESS: Read w/Fileman FIELD NUMBER: 32 FIELD NAME: DATE OF BIRTH LOCATION: 0;33 ACCESS: Read w/Fileman FIELD NUMBER: 38 FIELD NAME: STEP LOCATION: 0;39 ACCESS: Read w/Fileman FIELD NUMBER: 458 FIELD NAME: COST CENTER/ORGANIZATION LOCATION: 0;49 ACCESS: Read w/Fileman FIELD NUMBER: 604 FIELD NAME: LEVEL LOCATION: MISC;8 ACCESS: Read w/Fileman FIELD NUMBER: 80 FIELD NAME: SEPARATION IND LOCATION: 1;33 ACCESS: Read w/Fileman FIELD NUMBER: 19 FIELD NAME: PAY BASIS LOCATION: 0;20 ACCESS: Read w/Fileman FIELD NUMBER: 20 FIELD NAME: PAY PLAN LOCATION: 0;21 ACCESS: Read w/Fileman FIELD NUMBER: 26 FIELD NAME: RETIREMENT CODE LOCATION: 0;27 ACCESS: Read w/Fileman FIELD NUMBER: 28 FIELD NAME: SALARY LOCATION: 0;29 ACCESS: Read w/Fileman FIELD NUMBER: 186 FIELD NAME: RESIDENCE STATE LOCATION: ADD;6 ACCESS: Read w/Fileman FIELD NUMBER: 186.1 FIELD NAME: RESIDENCE ADDRESS LINE 1 LOCATION: ADD;7 ACCESS: Read w/Fileman FIELD NUMBER: 186.3 FIELD NAME: RESIDENCE ADDRESS LINE 3 LOCATION: ADD;9 ACCESS: Read w/Fileman FIELD NUMBER: 186.4 FIELD NAME: RESIDENCE ADDRESS ZIP CODE LOCATION: ADD;10 ACCESS: Read w/Fileman FIELD NUMBER: 226 FIELD NAME: FEGLI CODE LOCATION: FEGLI;4 ACCESS: Read w/Fileman FIELD NUMBER: 231 FIELD NAME: HEALTH INSURANCE LOCATION: FEHB;2 ACCESS: Read w/Fileman FIELD NUMBER: 30 FIELD NAME: SERVICE COMPUTATION DATE LOCATION: 0;31 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26854817 SUBSCRIBING PACKAGE: ASISTS ISC: Hines EDITOR: WILLIAMSON,CATHY E NUMBER: 2365 IA #: 2365 DATE CREATED: APR 27, 1998 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XDRMERG NAME: Merge File Entries ID: XDRMERG GENERAL DESCRIPTION: Overview A file in which entries need to be merged may be entered in the DUPLICATE RESOLUTION file (file 15.1). This requires adding the file as one which can be selected as the variable pointer, and search criteria would usually need to be specified to assist in identifying potential duplicate pairs (although an option can be use by which selected pairs can be added directly to the DUPLICATE RECORD file as verified duplicates). Verified duplicate pairs may be approved for merging, and a merge process generated for those approved pairs. A DUPLICATE RECORD file entry will also have handle files which are not associated as normal pointers identified in the PACKAGE file under the 'AFFECTS RECORD MERGE' subfile with special processing routines. ***IF A FILE HAS RELATED FILES WHICH ARE NOT NORMAL POINTERS, THEY SHOULD BE HANDLED ONLY AS ENTRIES IN THE DUPLICATE RECORD FILE AND THE TOOLKIT OPTIONS USED FOR MERGES INVOLVING THE FILE.*** The merge utility of Kernel Toolkit as revised by patch XT*7.3*23 provides an entry point which is available to developers for the merging of one or more pairs of records (a FROM record and a TO record) in a specified file. The merge process me rges the data of the FROM record into that of the TO record and deletes the FROM record, restoring by a hard set only the zero node with the .01 value on it until the merge process is completed (such that any references to that location via pointers will not error out). Any files which contain entries DINUMed with the data pairs are then also merged (and any files which are related to them by DINUM as well). Any pointers which can be identified rapidly by cross-references are modifie d so that references for the FROM entry become references to the TO entry instead. Following this, any files which contain other pointers are searched entry by entry to test for pointers to a FROM entry, and when found are modified to reference the TO entry. This search for pointer values is the most time consuming part of the entire process and may take an extended period depending upon the number of files that must be searched, the number of entries in those files, and how many levels of subfiles pointers may be located at. Since the search through these files will take the same period of time independent of the number of pairs which are being merged, it is suggested that as many pairs as convient be combined in one proc ess. At the end of the conversion of these pointers, the zero node stubs will be removed from the primary file and all related DINUMed files. The merge process is a single job which is tracked with frequent updates on location and status from start to finish. The job can be stopped at any time if necessary using Task Manager utilities (or in the event of a system crash, etc.) and restarted at the point of interruption at a later time. The manner in which data is merged. When a primary file or a DINUMed files entries are merged, any top level (single value) fields which are present in the FROM entry which are not present in the TO entry will be merged into the TO entries data. Any of these fields which contain cross-references will be entered using a VA File Manager utility (FILE^DIE) so that the cross-references will be fired. Other fields (those without cross-references) will be directly set into the data global. If a subfile entry exists in the FROM record which is not present in the TO record (as identified by the .01 value), that entry will be created with a VA File Manager utility (UPDATE^DIE) and the rest of the subfile merged over into the TO record and the cross-references within the subfile and any descendent subfiles run. If a subfile entry exists in the FROM record and an identical .01 value exists in the TO record, the subfile in the FROM record will be searched for any descendent subfiles which are not present in the TO record subfile. If such a subfile is found it will be merged into the subfile in the TO record and any cross-references in the merged subfile run. For fields which are simple pointers to the primary file (or any other file DINUMed to the primary file) the reference to the FROM record will be changed to a reference to the TO record. If the field contains a cross-reference this editing will be performed using a VA File Manager Utility call (FILE^DIE), otherwise it will be set directly into the global node. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26871015 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: The entry point EN^XDRMERG provides for merging of one or more pairs of records in a specified file. This entry point takes two (2) arguments, the file number (a numeric value) and a closed reference to the location where the program will find an array with subscripts indicating the record pairs to be merged (a text value). There can be either two or four subscripts in the data array as described below. the command D EN^XDRMERG(999000014,"MYLOC") would result in record pairs specified as subscripts in the array MYLOC to be merged in a hypotheical file 999000014. The array MYLOC might have been set up prior to this call in the following manner (or any equivalent way) where the subsripts represent the internal entry numbers of the FROM and TO records, respectively. S MYLOC(147,286)="",MYLOC(182,347)="",MYLOC(2047,192)="" S MYLOC(837,492)="",MYLOC(298,299)="" This would result in five record pairs being merged with record 147 (the FROM record) being merged into record 286 (the TO record), record 182 being merged into record 347, etc., to record 298 being merged into 299. Merges using the two subscript format will occur without a specific record of the entries prior to the merge (The internal entry numbers merged would be recorded under the file number in file 15.3) An alternative is a four subscript format for the data array which uses variable pointer formats for the FROM and TO records as the third and fourth subscripts. If the merge is performed with this four subscript array, then a premerge image of the data of both the FROM and TO records in the primary file and all other merged files (those related by DINUM) and information on all single value pointer values modified is stored in the MERGE IMAGE file (file 15.4). For the above example data [assuming that the global root for the hypothetical file 999000014 is ^DIZ(999000014,] the four subscript array might be generated using the following code S MYROOT=";DIZ(99900014," <--- note the leading ^ is ommitted S MYLOC(147,286,147_MYROOT,286_MYROOT)="" S MYLOC(182,347,182_MYROOT,347_MYROOT)="" S MYLOC(2047,192,2047_MYROOT,192_MYROOT)="" S MYLOC(837,492,837_MYROOT,492_MYROOT)="" S MYLOC(298,299,298_MYROOT,299_MYROOT)="" ; D EN^XDRMERG(99900014,"MYLOC") Exclusion of Multiple Pairs For a Record To insure that there are no unanticipated problems due to relationships between a specific record in multiple merges, prior to actually merging any data the various FROM and TO records included in the process are examined, and if one record is involved in more than one merge, all except the first pair of records involving that one are excluded from the merge. If any pairs are excluded for this reason, a mail message is generated to the individual responsible for the merge process as indicated by the DUZ. If the following entries were included in the MYLOC array MYLOC(128,247) MYLOC(128,536) and MYLOC(247,128) Only the first of these entries (based on the numeric sorting of the array) would be permitted to remain in the merge process, while the other two pairs would be omitted). And although it may seem unlikely that someone would indicate that a record should be merged into two different locations, while another location should be merged into one that was merged away, if the pairs are selected automatically and checks aren't included to prohibit such behavior, they will show up. That is why the merge process won't include more than one pair with a specific record in it. Problems Related To Data Entry While Merging The Merge Process has been designed to combine data associated with the two records in the manner described above. On occasion, however, there are problems which cause VA File Manager to reject the data that is being entered. This may happen for a number of reasons. Some that have been observed were: Clinics which had been changed so they no longer were indicated as Clinics (so they wouldn't add to the number that people had to browse through to select a clinic), but were rejected since the input transform checked that they be clinics; Pointer values that no longer had a valid value in the pointed to file (dangling pointers); Fields that have input transforms that prohibit data entry. :-) It is possible to use a validity checker on your data prior to initiating the actual merge process (this is the action taken by merges working from the Potential Duplicate file). The data pairs are processed in a manner similar to the actual merge, so only that data in any of the files which would be merged and for which the data would be entered using VA File Manager utilities for the specific pair are checked to insure they will pass the input transform. Any problems noted are incorporated into a mail message for resolution prior to attempting to merge the pair again, and the pair is removed from the data array that was passed in. Pairs which pass through this checking should not encounter any data problems while being merged. VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: Specifies the FILE NUMBER of the file in which the indcated entries are to be merged. VARIABLES: ARRAYNAM TYPE: Input VARIABLES DESCRIPTION: This variable contains the name of the array as a closed root under which the subscripts indicating the FROM and TO entries will be found. The data may have either two or four subscripts descendent from the array which is passed in. Please see the overall description provided for examples of its usage. COMPONENT/ENTRY POINT: RESTART COMPONENT DESCRIPTION: This entry point is used to restart a merge which has been stopped. The information necessary for restarting may be viewed using the CHKLOCAL entry point in XDRMERG2 (see LOCAL MERGE STATUS). VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: Specifies the FILE NUMBER of the file in which the indcated entries are to be merged. VARIABLES: ARRAYNAM TYPE: Input VARIABLES DESCRIPTION: This variable contains the name of the array as a closed root under which the subscripts indicating the FROM and TO entries will be found. The data may have either two or four subscripts descendent from the array which is passed in. Please see the overall description provided for examples of its usage. VARIABLES: PHASE TYPE: Input VARIABLES DESCRIPTION: This variable indicates the phase of the merge process in which the merge should be restarted. The value is a number in the range of 1 to 3, with no decimal places. Phase 1 is usually quite short and INTEGRATION REFERENCES LIST MAR 18,2015 11:24 PAGE 7 -------------------------------------------------------------------------------- is the merge of the specified entries in the primary file. Phase 2 is the merging of entries in files which are DINUMed to the primary file and changing pointers which can be identified from cross-references. Phase 3 is finding pointer values by searching each entry in a file. This will usually be the longest phase of the merge process. VARIABLES: CURRFILE TYPE: Input VARIABLES DESCRIPTION: This is the current file NUMBER on which the merge process is operating. VARIABLES: CURRIEN TYPE: Input VARIABLES DESCRIPTION: This is the current internal entry number in the file on which the merge process is operating. NUMBER: 2371 IA #: 2371 DATE CREATED: APR 28, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: REATTACH SC TEAM AUTO-ADD PROTOCOL GENERAL DESCRIPTION: CPRS did an OOPS. When we attempted to add our protocol to theSC CLINIC ENTROLL/DISCHARGE EVENT DRIVER protocol, we ended up removing the SC TEAM AUTO-ADD protocol which was already attached. We would like permission to do the reattachment as part of OR*3*19. The patch sends SC TEAM AUTO-ADD as ATTACH AT SITE and SC CLINIC ENROLL/DISCHARGE EVENT DRIVER as USE AS LINK so we're not actually sending out the definitions, just making the connection. STATUS: Active DURATION: Next Version EXPIRATION DATE: APR 23, 1999 MAIL MESSAGE: 26883079 GOOD ONLY FOR VERSION: 3 COMPONENT/ENTRY POINT: SC CLINIC ENROLL/DISCHARGE DRIVER COMPONENT DESCRIPTION: This protocol is being exported as USE AS LINK so we can reassign the SC TEAM AUTO-ADD protocol. COMPONENT/ENTRY POINT: SC TEAM AUTO-ADD COMPONENT DESCRIPTION: This protocol is exported as ATTACH AT SITE to attach it to the SC CLINIC ENROLL/DISCHARGE EVENT DRIVER protocol. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2373 IA #: 2373 FILE NUMBER: 1.2 GLOBAL ROOT: DIST(1.2, DATE CREATED: APR 29, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DIST(1.2 REFERENCE IN OE/RR ID: DIST(1.2, GLOBAL REFERENCE: DIST(1.2,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Used in an extrinsic function to return a 1 if the .01 is set to LINE EDITOR - VA FILEMAN. I 'X!($P($G(^DIST(1.2,+X,0)),U)="LINE EDITOR - VA FILEMAN") S Y=1 GENERAL DESCRIPTION: The Order Entry/Results Reporting module would like permission to reference the ALTERNATE EDITOR file. OE/RR uses the FM reader almost exclusively in the order dialog process. When taking actions such as copy and renew orders, it is necessary to allow comments (a word processing field) to be carried over. OE/RR would like to use the ALTERNATE EDITOR file to determine if the user is using the line editor. If not, it will display the text in the field prior to asking them if they want to edit it. Without this reference, always displaying the text in the field would cause those with the line editor to see it 2x. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26893191 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2374 IA #: 2374 FILE NUMBER: 1 GLOBAL ROOT: DIC(filenumber,0) DATE CREATED: APR 29, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TOOLKIT NEEDS NAME ID: DIC(filenumber,0) GLOBAL REFERENCE: DIC(filenumber,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Parameter Tools component of Toolkit is a generic tool to allow setting parameters at various levels (system, package, etc.). In order to achieve this goal, it is necessary to make a direct global read to DIC to determine file name. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26893191 SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland SUBSCRIBING DETAILS: Toolkit would like permission to retrieve a file name from ^DIC(filenumber,0) via a direct global read. SUBSCRIBING PACKAGE: LAB SERVICE NUMBER: 2375 IA #: 2375 GLOBAL ROOT: DD(8989.5,.01,V DATE CREATED: APR 29, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TOOLKIT NEEDS TO ACCESS VARIABLE PTR DEF ID: DD(8989.5,.01,V GLOBAL REFERENCE: DD(8989.5,.01,V,B GLOBAL DESCRIPTION: File 8989.5 is the Parameters file and its .01 is a variable pointer to multiple files. This reference allows the Parameter Tools component to ensure that only allowable files are being referenced. A function within toolkit returns a 1 if the file exists in the variable pointer definition or 0 otherwise. The following is the code it uses (in XPARDD1): ALLOW(FN) ; Screens allowable entities to variable ptrs in 8989.5,.01 ; ** VPDD ** see which files 8989.5 can point to Q:'FN 0 Q $D(^DD(8989.5,.01,"V","B",FN))>0 GENERAL DESCRIPTION: The Parameter Tools component of Toolkit allows setting of parameters at various levels. This necessitates a file structure with a variable pointer definition to point to the files which are allowed to be used through the Parameter Tools component. To ensure that no other files are pointed to, a check is done on the DD's "V" multiple, "B" cross-reference, to deterine whether an entry is in the variable pointer definitition. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26893191 SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 2376 IA #: 2376 DATE CREATED: APR 30, 1998 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJORUT2 NAME: DBIA2376 ID: PSJORUT2 GENERAL DESCRIPTION: These entry points build drug information for patient's orders entered in the Inpatient Medications package. The data returned is used in order checks in Computerized Patient Record System. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 38327155 COMPONENT/ENTRY POINT: ENCHK COMPONENT DESCRIPTION: This entry point returns drug information for a specific patient's current orders in the Inpatient Medications package. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient internal entry number. VARIABLES: PSJINX TYPE: Input VARIABLES DESCRIPTION: Index number so duplicate drugs will be returned. VARIABLES: PSGOCHK TYPE: Input VARIABLES DESCRIPTION: Set to 1 if check should include dispense drugs in ^PS(53.45. VARIABLES: PSIVOCHK TYPE: Input VARIABLES DESCRIPTION: Set to 1 if check should include entries in DRG array. VARIABLES: TMP($J,'ORDERS',PSJINX) TYPE: Output VARIABLES DESCRIPTION: ^TMP($J,"ORDERS",PSJINX)= VA CLASSIFICATION^NATIONAL DRUG FILE ENTRY_"A"_PSNDF VA PRODUCT NAME ENTRY^DISPENSE DRUG NAME^ORDER NUMBER IN OR(100^INPATIENT MEDS ORDER NUMBER_";I" COMPONENT/ENTRY POINT: DDRUG COMPONENT DESCRIPTION: This entry point returns drug information for a single drug when it is chosen for an order. This is specifically used in IV orders to check against the other additives or solutions entered during a single order entry. VARIABLES: DDRUG TYPE: Input VARIABLES DESCRIPTION: Dispense drug internal entry number. VARIABLES: PSJINX TYPE: Input VARIABLES DESCRIPTION: Index number so duplicate drugs will be returned. VARIABLES: PSJORIEN TYPE: Input VARIABLES DESCRIPTION: Internal entry number for order in ^OR(100. VARIABLES: COD TYPE: Input VARIABLES DESCRIPTION: Order number in Inpatient Meds. number_"P" if order is in ^PS(53.1. number_"U" if order is in ^PS(55. VARIABLES: TMP($J,'ORDERS',PSJINX) TYPE: Output VARIABLES DESCRIPTION: ^TMP($J,"ORDERS",PSJINX)= VA CLASSIFICATION^NATIONAL DRUG FILE ENTRY_"A"_PSNDF VA PRODUCT NAME ENTRY^DISPENSE DRUG NAME^ORDER NUMBER IN OR(100^INPATIENT MEDS ORDER NUMBER_IPOROP IPOROP-Set to ";O" if piece 2 of DDRUG array is "PSO". Set to ";N" if piece 2 of DDRUG array is "PSH". Defaults to an ";I". SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham EDITOR: CRUMLEY,JAMIE NUMBER: 2377 IA #: 2377 DATE CREATED: APR 30, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DIR('V') usage in parameter tools GENERAL DESCRIPTION: The parameter tools component of toolkit would like permission to use DIR("V") to ensure a silent interaction with the reader when doing data validation checks. STATUS: Active DURATION: Next Version MAIL MESSAGE: 26893191 GOOD ONLY FOR VERSION: 7.3 COMPONENT/ENTRY POINT: DIR COMPONENT DESCRIPTION: DIR("V") is an undocumented input variable to ^DIR that causes it to validate X based on the data type and parameters specified in DIR(0). It is like a silent data-type validator. Parameter Tools uses this variable when calling DIR to validate input values. VARIABLES: DIR('V') TYPE: Input VARIABLES DESCRIPTION: DIR("V") is an undocumented input variable to ^DIR that causes it to validate X based on the data type and parameters specified in DIR(0). It is like a silent data-type validator. Parameter Tools uses this variable when calling DIR to validate input values. SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 2380 IA #: 2380 FILE NUMBER: 120.82 GLOBAL ROOT: GMRD(120.82, DATE CREATED: MAY 06, 1998 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMRD(120.82 USAGE IN OE/RR ID: GMRD(120.82, GLOBAL REFERENCE: GMRD(120.82,'B', GLOBAL DESCRIPTION: Allow use of B index to determine if an entry exists in the file and obtain the entry's IEN. GLOBAL REFERENCE: GMRD(120.82, FIELD NUMBER: 1 FIELD NAME: ALLERGY TYPE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: GMRD(120.82,'D', GLOBAL DESCRIPTION: Read access to the D index. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946164 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2381 IA #: 2381 FILE NUMBER: 51.2 GLOBAL ROOT: PS(51.2, DATE CREATED: MAY 06, 1998 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR REFERENCES TO PS(51.2, ID: PS(51.2, GLOBAL REFERENCE: PS(51.2,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: ABBREVIATION LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: PACKAGE USE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: OUTPATIENT EXPANSION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. The Order Entry/Results Reporting package requests permission to access the NAME and ABBREVIATION fields in the MEDICATION ROUTES file (#51.2). STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 26976384 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: OE/RR uses the "B" index to determine if there is an existing entry in the file and, if there is, determine that entry's IEN. NUMBER: 2382 IA #: 2382 DATE CREATED: MAY 07, 1998 CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RGEQ NAME: OUTPATIENT PHARMACY/CIRN ID: RGEQ GENERAL DESCRIPTION: Outpatient Pharmacy provides the CIRN package prescription data at various stages in the prescription life cycle. The data is provided through the use of a single entry point EN^RGEQ("RX",RX IEN) in the CIRN package. The following Outpatient Pharmacy routines call this entry point from the lines indicated: ROUTINE LINE PSOAUTOC CAN+16 PSOBUILD GET+18 PSOCAN3 ADD+1 PSODISP BATCH+11 PSODISPS QTY+16 PSOHLD UHLD+10 UHLD+14 H+8 PSORESK BC1+21 PAR+14 PSORXED1 DIE+6 STATUS: Active DURATION: Next Version MAIL MESSAGE: 26952888 GOOD ONLY FOR VERSION: OP v 6.0 COMPONENT/ENTRY POINT: EN("RX",RX IEN) COMPONENT DESCRIPTION: The call EN^RGEQ("RX",RX) where RX represents the internal entry number of a prescription from the PRESCRIPTION file (#52). VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: The internal entry # from the PRESCRIPTION file (#52). SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 2383 IA #: 2383 DATE CREATED: MAY 07, 1998 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJORRE NAME: SEND INPT MEDS TO CPRS ID: PSJORRE CREATOR: CASTLE,JOHN GENERAL DESCRIPTION: This call, OCL^PSJORRE, returns the Inpatient Medications data that is passed to Computerized Patient Record System and used for display in the CPRS meds screen. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34591096 COMPONENT/ENTRY POINT: OCL COMPONENT DESCRIPTION: Condensed Med list call. OCL^PSJORRE(DFN,BDT,EDT,TFN,MVIEW): Passed: DFN - Patient's Internal Pointer BDT - Date/Time to start search for medications (optional) EDT - Date/Time to terminate search for medications (optional) TFN - Entry number to begin using for each order returned. MVIEW - Sort format for the returned display information (optional) VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient's internal entry number. VARIABLES: BDT TYPE: Input VARIABLES DESCRIPTION: Date/Time to start search for medications. (optional) VARIABLES: EDT TYPE: Input VARIABLES DESCRIPTION: Date/Time to end search for medications. (optional) VARIABLES: TFN TYPE: Input VARIABLES DESCRIPTION: Subscript number to begin using for orders found. Each orders is placed into ^TMP("PS",$J,TFN). The variable TFN is incremented for each order. VARIABLES: TMP('PS',$J,TFN, TYPE: Output VARIABLES DESCRIPTION: ^TMP("PS",$J,TFN,0)=ORDER #_File;I^DRUG^INFUSION RATE^STOP DATE^^TOTAL DOSE^UNITS PER DOSE^PLACER #^STATUS^^^^NOT TO BE GIVEN^PENDING RENEWAL (1 or 0) FILE: U = unit dose order (file #55, subfile 55.06) V = IV order (file #55, subfile 55.01) P = Pending order (file 53.1) ^TMP("PS",$J,TFN,"MDR",0)= # of LINES ^TMP("PS",$J,TFN,"MDR",D1,0)=MED ROUTE ABBR. ^TMP("PS",$J,TFN,"SCH",0)= # of LINES ^TMP("PS",$J,TFN,"SCH",D1,0)=SCHEDULE NAME ^TMP("PS",$J,TFN,"A",0)= # of LINES ^TMP("PS",$J,TFN,"A",D1,0)=ADDITIVE NAME^AMOUNT^BOTTLE ^TMP("PS",$J,TFN,"B",0)= # of LINES ^TMP("PS",$J,TFN,"B",D1,0)=SOLUTION NAME^AMOUNT^PRINT NAME {2} ^TMP("PS",$J,TFN,"P",0)=IEN^.01 of VA 200 ^TMP("PS",$J,TFN,"SIG",0)= # of LINES ^TMP("PS",$J,TFN,"SIG",D1,0)=SIG (outpatient) or INSTRUCTIONS (inpatient) ^TMP("PS",$J,TFN,"ADM",0)= # of LINES ^TMP("PS",$J,TFN,"ADM",D1,0)=ADMINISTRATION TIMES Where: administration time = Free text 2-119 characters ^TMP("PS",$J,TFN,"SIO",0)= # of LINES ^TMP("PS",$J,TFN,"SIO",D1,0)=SPECIAL INSTRUCTIONS/OTHER PRINT INFO (Special instructions = Free text 1-180 characters) ^TMP("PS",$J,TFN,"P",0)=PROVIDER IEN^.01 of VA(200 ^TMP("PS",$J,TFN,"IVLIM",0)=IV LIMIT ^TMP("PS",$J,TFN,"CLINIC",0)=CLINIC NUMBER VARIABLES: MVIEW TYPE: Input VARIABLES DESCRIPTION: Numeric value of 0,1,2,3 or null to denote which sorting option to print the display in CPRS. (optional) 0 or null - This provides the medication list as it was prior to CPRS GUI v27 so that other applications calling this API will not see any changes. 1 - Sorts by Status Group, Stop Date/Expiration Date. Following is the sort order: Pending ------- NON VERIFIED NON-VERIFIED PENDING Active/Hold ----------- ACTIVE ON CALL REFILL REINSTATED RENEWED SUSPENDED HOLD PROVIDER HOLD DONE DRUG INTERACTIONS Expired ------- EXPIRED Discontinued/Deleted -------------------- DATE OF DEATH ENTERED DELETED DISCONTINUED DISCONTINUED (EDIT) DISCONTINUED (RENEWAL) DISCONTINUED BY PROVIDER PURGE 2 - Sorts by Status Group, Status Location, Drug Name Alpha Characters. Following is the sort order: Active ------ ACTIVE REFILL HOLD SUSPENDED PROVIDER HOLD ON CALL Pending ------- NON-VERIFIED DRUG INTERACTIONS INCOMPLETE PENDING Discontinued ------------ DONE EXPIRED DISCONTINUED DELETED DISCONTINUED BY PROVIDER DISCONTINUED (EDIT) REINSTATED RENEWED 3 - Sorts by Drug (Alphabetically), Status Active, Status Recent, Expired (using ORCH context meds stop date). SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham DBA Comments: 20080728/ CHANGED TITLE FROM DEFAULT VALUE/JSHARVEY DATE ACTIVATED: JUL 28, 2008 DATE/TIME EDITED: FEB 05, 2008@13:19 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: Templeton,Shannon DATE/TIME EDITED: JUL 28, 2008@11:43 ACTION: CONTENT CORRECTED AT THE REQUEST OF: HARVEY,JULIE DATE/TIME EDITED: JUL 28, 2008@11:44 ACTION: APPROVED AT THE REQUEST OF: TEMPLETON,SHANNON NUMBER: 2384 IA #: 2384 DATE CREATED: MAY 07, 1998 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJORRE1 NAME: DBIA2384 ID: PSJORRE1 GENERAL DESCRIPTION: This call, OEL^PSJORRE1, returns the Inpatient Medications order data that is passed to Computerized Patient Record System. This array is used for the meds screen detailed order display. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34591095 COMPONENT/ENTRY POINT: OEL COMPONENT DESCRIPTION: Condensed Med list call. OEL^PSJORRE1(DFN,ON): Passed: DFN - Patient's Internal Pointer ON - ORDER #_FILE (from condensed list) FILE: U = unit dose order (file #55, subfile 55.06) V = IV order (file #55, subfile 55.01) P = Pending order (file 53.1) VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient internal entry number. VARIABLES: ON TYPE: Input VARIABLES DESCRIPTION: ON = ORDER #_FILE (from condensed list) FILE: U = unit dose order (file #55, subfile 55.06) V = IV order (file #55, subfile 55.01) P = Pending order (file 53.1) VARIABLES: TMP('PS',$J, TYPE: Output VARIABLES DESCRIPTION: ^TMP("PS",$J,0)=DRUG^INFUSION RATE^STOPDATE^^START DATE^EXTERNAL STATUS^^^TOTAL DOSE^UNIT PER DOSE^PLACER #^^NOT TO BE GIVEN^PENDING RENEWAL (1 or 0) ^TMP("PS",$J,"MDR",0)= # of LINES ^TMP("PS",$J,"MDR",D1,0)=MED ROUTE ABBR. ^TMP("PS",$J,"SCH",0)= # of LINES ^TMP("PS",$J,"SCH",D1,0)=SCHEDULE NAME^SCHEDULE TYPE NAME^SCHEDULE TYPE CODE ^TMP("PS",$J,"SIG",0)= # of LINES ^TMP("PS",$J,"SIG",D1,0)=SIG (outpatient) or INSTRUCTIONS (inpatient) ^TMP("PS",$J,"PC",0)= # of LINES ^TMP("PS",$J,"PC",D1,0)=PROVIDER COMMENTS ^TMP("PS",$J,"A",0)= # of LINES ^TMP("PS",$J,"A",D1,0)=ADDITIVE NAME^AMOUNT^BOTTLE ^TMP("PS",$J,"B",0)= # of LINES ^TMP("PS",$J,"B",D1,0)=SOLUTION NAME^AMOUNT^PRINT NAME {2} ^TMP("PS",$J,"P",0)=IEN^.01 of VA 200 ^TMP("PS",$J,"ADM",0)= # of LINES ^TMP("PS",$J,"ADM",D1,0)=ADMINISTRATION TIMES Where: administration time = Free text 2-119 characters ^TMP("PS",$J,"SIO",0)= # of LINES ^TMP("PS",$J,"SIO",D1,0)=SPECIAL INSTRUCTIONS/OTHER PRINT INFO (Special instructions = Free text 1-180 characters) ^TMP("PS",$J,"DD",0) = # of LINES ^TMP("PS",$J,"DD",D1,0)= DISPENSE DRUG IEN(from the U/D order)^Unit per Dose^CORRESPONDING OUTPATIENT DRUG IEN^ORDERABLE ITEM IEN ^TMP("PS",$J,"P",0)=Provider IEN^.01 of VA 200 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2385 IA #: 2385 DATE CREATED: MAY 07, 1998 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOHLSN1 NAME: DBIA2385 ID: PSOHLSN1 GENERAL DESCRIPTION: The Consolidated Mail Outpatient Pharmacy (CMOP) Package requests an integration agreement with the Outpatient Pharmacy (OP) V. 7.0 package. The agreement covers a single entry point in the OP package at EN^PSOHLSN1(IEN #52, "ZD"). These two parameters are the only ones that are required. Others are optional. Prescription event data is passed through the OP package to the Clinical Information Resources Network (CIRN) package in the form of the Rx internal entry # from file 52. No data is returned to the CMOP package from the CIRN package. This agreement also covers the same entry point in the OP package at EN^PSOHLSN1(IEN #52, "SC"). These two parameters are the only ones that are required. Others are optional. In this case, the prescription event data is passed to the Computerized Patient Record System (CPRS) package to update status information for CMOP prescriptions. No data is returned to the CMOP package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33822804 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: A prescription IEN (file #52) is passed to the OUTPATIENT PHARMACY package, which hands the information to the CIRN software if called as EN^PSOHLSN1(IEN #52, "ZD") or to the CPRS software if called as EN^PSOHLSN1(IEN #52, "SC") VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN file # 52. SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 2386 IA #: 2386 FILE NUMBER: 1 GLOBAL ROOT: DIC( DATE CREATED: MAY 09, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PARAMETER TOOLS POINTS TO FILE 1 ID: DIC( GENERAL DESCRIPTION: The Parameter Tools portion of Toolkit requests approval to point to the file of files (file #1). Parameter Tools uses this pointer to determine allowable files for setting up parameters. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26893191 SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 2387 IA #: 2387 FILE NUMBER: 60 GLOBAL ROOT: LAB(60, DATE CREATED: MAY 09, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: LAB(60 USAGE IN OE/RR ID: LAB(60, GLOBAL REFERENCE: LAB(60, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: SUBSCRIPT LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 320 FIELD NAME: REQUIRED COMMENT LOCATION: 0;19 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 9 FIELD NAME: LAB COLLECTION SAMPLE LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 51 FIELD NAME: PRINT NAME LOCATION: .1;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LAB(60,D0,1, FIELD NUMBER: .01 FIELD NAME: SITE/SPECIMEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 8 FIELD NAME: UNITS LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 95.3 FIELD NAME: LOINC CODE LOCATION: 95.3;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LAB(60,D0,3, FIELD NUMBER: 7 FIELD NAME: REQUIRED COMMENT LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .01 FIELD NAME: COLLECTION SAMPLE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LAB(60,DA,3,"B", GLOBAL DESCRIPTION: Uses B index of COLLECTION SAMPLE multiple to look up entry. GLOBAL REFERENCE: LAB(60,D0,2, FIELD NUMBER: .01 FIELD NAME: LAB TEST LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: GLOBAL REFERENCE: LAB(60,D0,8, FIELD NUMBER: .01 FIELD NAME: INSTITUTION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: ACCESSION AREA LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LAB(60,"B", GLOBAL DESCRIPTION: Global read access permitted GLOBAL REFERENCE: LAB(60,D0,1,'B', GLOBAL DESCRIPTION: Global read access permitted for SITE/SPECIMEN GENERAL DESCRIPTION: Order Entry/Results Reporting requests permission to access the following fields and cross-references in the LABORATORY TEST file (#60). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29154901 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: SUBSCRIBING PACKAGE: VBECS NUMBER: 2388 IA #: 2388 FILE NUMBER: 61 GLOBAL ROOT: LAB(61, DATE CREATED: MAY 09, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: LAB(61 USAGE IN OE/RR ID: LAB(61, CREATOR: CRUMLEY,JAMIE GLOBAL REFERENCE: LAB(61,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: SNOWMED CODE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LAB(61,'B', GLOBAL REFERENCE: LAB(61,'C', GLOBAL REFERENCE: LAB(61,'E', GLOBAL REFERENCE: LAB(61,DA,64.91) FIELD NUMBER: 64.9103 FIELD NAME: INACTIVE DATE LOCATION: 64.91;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field exists only in sites where the Laboratory System Re-engineering Project (LSRP) has been installed. It is the inactive date for this entry. When an entry is inactive, it should be selectable in CPRS for ordering purposes. The Inactive Date field is currently planned for distribution in Lab Re-engineering (patch LR*5.2*393). As of 2/12/13, it is not known if this patch will be nationally released. It is currently installed at the Huntington VAMC. There is also the possibility that a different LR patch will release this functionality. CPRS will reference the Inactive Date field for LSRP after the distribution of OR*3*315 scheduled for national release in February 2013. GENERAL DESCRIPTION: Order Entry/Results Reporting requests permission to access the following fields and cross-references in the TOPOGRAPHY FIELD file (#61). STATUS: Active MAIL MESSAGE: 26946458 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City DBA Comments: 4/20/12 note from Jamie Crumley: LSRP is adding an INACTIVE DATE to file 61 in LR*5.2*393. We have requested that CPRS modify the code they use to display TOPOGRAPHY entries to check this INACTIVE DATE field. CPRS will be making these updates in OR*3*315, but we need to add them to the ICR between Lab and CPRS. 2/20/13-MM: ICR #2388 has been actived for LR*5.3*393 and OR*3*315. OR*3*315 was released in February 2013. The Inactive Date field is currently planned for distribution in Lab Re-engineering (patch LR*5.2*393). As of 2/12/13, it is not known if this patch will be nationally released. It is currently installed at the Huntington VAMC. There is also the possibility that a different LR patch will release this functionality. CPRS will reference the Inactive Date field for LSRP after the distribution of OR*3*315 scheduled for national release in February 2013. DATE ACTIVATED: FEB 20, 2013 DATE/TIME EDITED: APR 23, 2012@12:06 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CRUMLEY,JAMIE WITH CONCURRENCE OF: CRUMLEY,JAMIE DATE/TIME EDITED: FEB 20, 2013@15:33 ACTION: APPROVED AT THE REQUEST OF: CRUMLEY,JAMIE WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 2389 IA #: 2389 FILE NUMBER: 62 GLOBAL ROOT: LAB(62, DATE CREATED: MAY 09, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: LAB(62 USAGE IN OE/RR ID: LAB(62, CREATOR: CRUMLEY,JAMIE GLOBAL REFERENCE: LAB(62,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: DEFAULT SPECIMEN LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: TUBE TOP COLOR LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7 FIELD NAME: CAN LAB COLLECT LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LAB(62,DA,64.91) FIELD NUMBER: 64.9101 FIELD NAME: INACTIVE DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The Inactive Date field is currently planned for distribution in Lab Re-engineering (patch LR*5.2*393). As of 2/12/13, it is not known if this patch will be nationally released. It is currently installed at the Huntington VAMC. There is also the possibility that a different LR patch will release this functionality. CPRS will reference the Inactive Date field for LSRP after the distribution of OR*3*315 scheduled for national release in February 2013. GENERAL DESCRIPTION: Order Entry/Results Reporting requests permission to access the following fields and cross-references in the COLLECTION SAMPLE file (#62). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946458 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 4/20 - Jamie Crumley is working on both the CPRS and Lab changes for the LSRP project. LSRP is requesting access for CPRS to check the new INACTIVE DATE field. ICR reactivated on 4/23/12. Patches are LR*5.2*393 and OR*3*315. It was agreed to add text to the INACTIVE DATE field to better document the issues with this field: The Inactive Date field is currently planned for distribution in Lab Re-engineering (patch LR*5.2*393). As of 2/12/13, it is not known if this patch will be nationally released. It is currently installed at the Huntington VAMC. There is also the possibility that a different LR patch will release this functionality. CPRS will reference the Inactive Date field for LSRP after the distribution of OR*3*315 scheduled for national release in February 2013. 10/1/14-MC: Added VPS as a subscriber at the request of Carolyn Wheless and approved by Carol Anzaldua for patch VPS*1*4. VPS will be required to return a patient's specimem data stored in file #62 to VetLink as part of the RPC access implementation of the VistA Howdy Vomputerized Phlebotomy Login Process. DATE ACTIVATED: APR 23, 2012 DATE/TIME EDITED: APR 20, 2012@11:55 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CRUMLEY,JAMIE WITH CONCURRENCE OF: CRUMLEY,JAMIE DATE/TIME EDITED: APR 23, 2012@11:47 ACTION: APPROVED AT THE REQUEST OF: CRUMLEY,JAMIE WITH CONCURRENCE OF: CRUMLEY,JAMIE DATE/TIME EDITED: FEB 19, 2013@16:17 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: ANZALDUA,CAROL DATE/TIME EDITED: OCT 01, 2014@14:59 ACTION: SUBSCRIBER ADDED NUMBER: 2390 IA #: 2390 FILE NUMBER: 62.05 GLOBAL ROOT: LAB(62.05, DATE CREATED: MAY 09, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: LAB(62.05, USAGE IN OE/RR ID: LAB(62.05, GLOBAL REFERENCE: LAB(62.05,DA,0) FIELD NUMBER: .01 FIELD NAME: URGENCY LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: CAN LAB COLLECT? LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: WORKLOAD ONLY LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: HL7 CODE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LAB(62.05,'B', GLOBAL DESCRIPTION: Use B index of file to look up entry. GENERAL DESCRIPTION: Order Entry/Results Reporting requests permission to access the following fields in the URGENCY file (#62.05). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 37779411 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2391 IA #: 2391 FILE NUMBER: 62.07 GLOBAL ROOT: LAB(62.07, DATE CREATED: MAY 09, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: LAB(62.07, USAGE IN OE/RR ID: LAB(62.07, GLOBAL REFERENCE: LAB(62.07,DA,.1) FIELD NUMBER: 1 FIELD NAME: EXECUTE CODE LOCATION: .1;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Executes value within OE/RR. GENERAL DESCRIPTION: Order Entry/Results Reporting requests permission to access the following field in the EXECUTE CODE file (#62.07). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946458 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2392 IA #: 2392 FILE NUMBER: 51.1 GLOBAL ROOT: PS(51.1, DATE CREATED: MAY 10, 1998 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR ACCESS TO PS(51.1, ID: PS(51.1, GLOBAL REFERENCE: PS(51.1,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: STANDARD ADMINISTRATION TIMES LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: FREQUENCY (IN MINUTES) LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5 FIELD NAME: TYPE OF SCHEDULE LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2.5 FIELD NAME: MAX DAYS FOR ORDERS LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(51.1,'AP'_nmsp, GLOBAL DESCRIPTION: OE/RR uses the AP x-ref to access schedules by package prefix. GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. Order Entry/Results Reporting requests permission to access the following fields and cross-reference in the Administration Schedule file (#51.1). STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 34246795 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2395 IA #: 2395 DATE CREATED: MAY 10, 1998 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCAFRD NAME: CALL TO GMRCAFRD ID: GMRCAFRD GENERAL DESCRIPTION: The Order Entry/Results Reporting packages requests approval to call FR^GMRCAFRD. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 COMPONENT/ENTRY POINT: FR(IEN) COMPONENT DESCRIPTION: Entry point to allow forwarding (rerouting) of a consult request. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of entry in file 123 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City EDITOR: INSLEY,MARCIA NUMBER: 2397 IA #: 2397 DATE CREATED: MAY 10, 1998 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOHLUP NAME: OE/RR CALL TO PSOHLUP ID: PSOHLUP GENERAL DESCRIPTION: Order Entry/Results Reporting calls PSOHLUP during the CPRS orders conversion. STATUS: Active DURATION: Next Version MAIL MESSAGE: 26946658 GOOD ONLY FOR VERSION: 7 COMPONENT/ENTRY POINT: EN1 VARIABLES: DFN TYPE: Input VARIABLES: TALK TYPE: Input VARIABLES DESCRIPTION: We pass in a 1 if we want it to 'talk' and a 0 if not. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2398 IA #: 2398 DATE CREATED: MAY 10, 1998 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSORENW NAME: OE/RR CALL TO PSORENW ID: PSORENW GENERAL DESCRIPTION: The Order Entry/Results Reporting would like approval to call the extrinsic function $$RENEW^PSORENW(ien). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34012828 COMPONENT/ENTRY POINT: $$RENEW(IEN) COMPONENT DESCRIPTION: Extrinsic function to determine whether an order is renewable. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Order number. VARIABLES: $$RENEW TYPE: Output VARIABLES DESCRIPTION: Returns a 1 if the order is renewable. A piece 2 will be included only if the Dispense Drug of the order is now matched to a different Pharmacy Orderable Item. This piece 2 will be the pointer value to the Pharmacy Orderable Item (#50.7) file. Returns a 0^reason if the order is not renewable. The reason (piece 2) is a short descriptive text that explains why the order is not renewable. Returns a -1 if the order cannot be found in Pharmacy. VARIABLES: PSOCPDRG TYPE: Input VARIABLES DESCRIPTION: This variable is the internal entry number of the Dispense Drug of the order. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2399 IA #: 2399 DATE CREATED: MAY 10, 1998 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOREF NAME: OE/RR CALL TO PSOREF FOR REFILL CHECK ID: PSOREF GENERAL DESCRIPTION: Order Entry/Results Reporting requests permission to call REFILL^PSOREF to determine whether an order is refillable. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946658 COMPONENT/ENTRY POINT: REFILL COMPONENT DESCRIPTION: Used to determine if an outpatient pharmacy order can be refilled. VARIABLES: IEN TYPE: Input VARIABLES: FLAG TYPE: Output VARIABLES DESCRIPTION: Returns a 1 if order is refillable, 0 if not, -1 if order could not be found. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2400 IA #: 2400 DATE CREATED: MAY 10, 1998 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOORRL NAME: OE/RR CALLS TO PSOORRL ID: PSOORRL CREATOR: SCHLEHUBER,CAMERON GENERAL DESCRIPTION: Order Entry/Results Reporting requests approval to make the following calls to PSOORRL. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946658 COMPONENT/ENTRY POINT: OCL COMPONENT DESCRIPTION: Called to return a list of meds. OCL^PSOORRL(DFN,STARTDATE,ENDDATE,VIEW) Passed: DFN - Patient's Internal Pointer Startdate - Date/Time to start search for medications (optional) Enddate - Date/Time to terminate search for medications (optional) View - Sort format for the returned display. (optional) Returned: ^TMP("PS",$J,D0,0)=ORDER #_File;PKG^DRUG^INFUSION RATE^STOP DATE^REFILLS REMAINING^TOTAL DOSE^UNITS PER DOSE^PLACER #^STATUS^LAST FILLDATE^DAYS SUPPLY^QUANTITY^NOT TO BE GIVEN^PENDING RENEWAL (1 or 0)^ISSUE DATE(Outpatient) or START DATE(Inpatient)^LAST RELEASE DATE/TIME^LAST FILL DAY SUPPLY File: R;O = prescription (file #52), P;O = pending outpatient order (file #52.41), P;I = pending inpatient order (file #53.1), U;I = unit dose order (file #55, subfile 55.06), V;I = IV order (file #55, subfile 55.01) PKG = I (inpatient) or O (outpatient) ^TMP("PS",$J,D0,"MDR",0)= # of LINES ^TMP("PS",$J,D0,"MDR",D1,0)=MED ROUTE ABBR. ^TMP("PS",$J,D0,"SCH",0)= # of LINES ^TMP("PS",$J,D0,"SCH",D1,0)=SCHEDULE NAME ^TMP("PS",$J,D0,"A",0)= # of LINES ^TMP("PS",$J,D0,"A",D1,0)=ADDITIVE NAME^AMOUNT^BOTTLE ^TMP("PS",$J,D0,"B",0)= # of LINES ^TMP("PS",$J,D0,"B",D1,0)=SOLUTION NAME^AMOUNT ^TMP("PS",$J,D0,"P",0)=IEN^.01 of VA 200 ^TMP("PS",$J,D0,"SIG",0)= # of LINES ^TMP("PS",$J,D0,"SIG",D1,0)=SIG (outpatient) or INSTRUCTIONS (inpatient) ^TMP("PS",$J,"ADM",0)= # of LINES ^TMP("PS",$J,"ADM",D1,0)=ADMINISTRATION TIMES Where: administration time = Free text 2-119 characters ^TMP("PS",$J,"SIO",0)= # of LINES ^TMP("PS",$J,"SIO",D1,0)=SPECIAL INSTRUCTIONS/OTHER PRINT INFO (Special instructions = Free text 1-180 characters) ^TMP("PS",$J,D0,"P",0)=IEN of provider^.01 of VA 200. VARIABLES: DFN TYPE: Input VARIABLES: BEGDATE TYPE: Input VARIABLES DESCRIPTION: Beginning date for search. VARIABLES: ENDDATE TYPE: Input VARIABLES DESCRIPTION: Ending date for search. VARIABLES: TMP('PS',$J, TYPE: Output VARIABLES DESCRIPTION: Global location of returned list of meds. VARIABLES: VIEW TYPE: Input VARIABLES DESCRIPTION: Numeric value of 0,1,2,3 or null to denote which sorting option to print the display in CPRS. (optional) 0 or null - This provides the medication list as it was prior to CPRS GUI v27 so that other applications calling this API will not see any changes. 1 - Sorts the medication list by Prescription Status Group and Stop Date/Expiration Date. Following is the sort order: Pending group: Non-Verified Pending Active group: Active Hold Suspended (Active/Susp) Provider Hold Expired group: Expired Discontinued/Deleted group: Discontinued by Provider Discontinued (Edit) 2 - Sorts the medication list by Prescription Status Group, Status, and Drug Name. Following is the sort order: Active group: Active Hold Pending group: Non-Verified Pending Discontinued group: Discontinued by Provider Discontinued (Edit) 3 - Sorts the medication list by Drug Name, Active/Suspended and Stop Date/Expiration Date. COMPONENT/ENTRY POINT: OEL COMPONENT DESCRIPTION: Returns detailed information on a particular pharmacy order. OEL^PSOORRL(DFN,ORDER) Passed: DFN - Patient's Internal Pointer ORDER - ORDER #_File;PKG (from condensed list) Returned: ^TMP("PS",$J,0)=DRUG^INFUSION RATE^STOPDATE^REFILLS REMAINING^START DATE^EXTERNAL STATUS^DAYS SUPPLY^QUANTITY^TOTAL DOSE^UNIT PER DOSE^PLACER #^LAST FILLDATE^NOT TO BE GIVEN^PENDING RENEWAL (1 or 0) ^TMP("PS",$J,"RXN",0)=EXTERNAL Rx NUMBER^LAST RELEASE DATE^ORIGINAL FILL ROUTING (W or M)^Remarks^FINISHED BY^ORIGINAL FILL DATE^ORIGINAL RELEASE DATE ^TMP("PS",$J,"RXN","RSTC")=ACTIVITY LOG^INITIATOR OF ACTIVITY^COMMENT ^TMP("PS",$J,"MDR",0)= # of LINES ^TMP("PS",$J,"MDR",D1,0)=MED ROUTE ABBR. ^TMP("PS",$J,"SCH",0)= # of LINES ^TMP("PS",$J,"SCH",D1,0)=SCHEDULE NAME ^TMP("PS",$J,"SIG",0)= # of LINES ^TMP("PS",$J,"SIG",D1,0)=SIG (outpatient) or INSTRUCTIONS (inpatient) ^TMP("PS",$J,"PAR",0) = # of LINES ^TMP("PS",$J,"PAR",n,0) = Fill Date^Days Supply^Quantity^Release Date^Routing (W or M)^REMARKS ^TMP("PS",$J,"PC",0)= # of LINES ^TMP("PS",$J,"PC",D1,0)=PROVIDER COMMENTS ^TMP("PS",$J,"A",0)= # of LINES ^TMP("PS",$J,"A",D1,0)=ADDITIVE NAME^AMOUNT^BOTTLE ^TMP("PS",$J,"B",0)= # of LINES ^TMP("PS",$J,"B",D1,0)=SOLUTION NAME^AMOUNT ^TMP("PS",$J,"P",0)=IEN of provider^.01 of VA 200 ^TMP("PS",$J,"ADM",0)= # of LINES ^TMP("PS",$J,"ADM",D1,0)=ADMINISTRATION TIMESWhere: administration time = Free text 2-119 characters ^TMP("PS",$J,"SIO",0)= # of LINES ^TMP("PS",$J,"SIO",D1,0)=SPECIAL INSTRUCTIONS/OTHER PRINT INFO (Special instructions = Free text 1-180 characters) ^TMP("PS",$J,"DD",0) = # of LINES ^TMP("PS",$J,"DD",D1,0)= DISPENSE DRUG IEN(from the U/D order)^Unit per Dose^CORRESPONDING OUTPATIENT DRUG IEN^ORDERABLE ITEM IEN ^TMP("PS",$J,"REF",0) = # of LINES ^TMP("PS",$J,"REF",n,0) = Refill Date^Days Supply^Quantity^Release Date^Routing (W or M)^Remarks ^TMP("PS",$J,"REF",n,"RSTC")=ACTIVITY LOG^INITIATOR OF ACTIVITY^COMMENT VARIABLES: DFN TYPE: Input VARIABLES: RXNUM TYPE: Input VARIABLES DESCRIPTION: Prescription number. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS SUBSCRIBING PACKAGE: VBECS SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING PACKAGE: SURGERY SUBSCRIBING PACKAGE: WOMEN'S HEALTH SUBSCRIBING DETAILS: Women's Health will begin using this ICR in patch WV*1*24, part of the CPRS version 31 release. Women's Health needs to retrieve all of the contraceptive medications prescribed or administered to a patient, as well as the date last filled or last administered. With this information, Women's Health can calculate a patient's risk level of becoming pregnant while taking prescribed contraceptive medications. As some contraceptive medications are administered as clinic meds, Women's Health needs to retrieve both inpatient and outpatient medications. The risk level is calculated as low if the patient's prescription was last filled or a clinic medication was last administered within the last 100 days otherwise, the risk level is set to high. This data is only needed if the patient is identified within the Women's Health package as using a shot or pill, vaginal ring or patch as a contraceptive method. Women's Health is already approved to use ICR #6029 RETURN REMINDER ORDER CHECK ITEMS to identify contraceptive medications. SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 5/25/12-Added VPR as a subscriber for VPR*1.0. 10/29/12-MM: Added Patient Assessment Documentation Package as a subscriber to ICR #2400 for VPS*1*1. 6/16/14-MC: Surgery added as a subscriber as requested by James Harris and approved by Ron Ruzbacki. Patch SR*3.0*180 scheduled for IOC in the Fall of 2014. 7/9/14-MC: PADP did not complete the class 3 to class 1 conversion process, but it is still installed at sites. Sites have the option to utilize the program, however it is no longer nationally supported. There will be no further patching of the package. PADP has been removed as a subscriber to this ICR. 2/20/15-DT: Women's Health added as a subscriber as requested by Robert Ruff and approved by Ron Ruzbacki.Women's Health will begin using this ICR in patch WV*1*24, part of the CPRS version 31 release. 2/23/15-MC: Added VPS as a subscriber to ICR at the request of Anita Hassett and approval of Ron Ruzbacki. VPS*1*15, After Visit Summary will call OCL^PSOORRL through the RPC Broker to retrieve prescription information. Anticipated release date of patch is 3/1/15. DATE ACTIVATED: JUL 28, 2008 DATE/TIME EDITED: OCT 10, 2007@12:12 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: THOMPSON,SETH DATE/TIME EDITED: FEB 05, 2008@15:19 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: TEMPLETON,SHANNON DATE/TIME EDITED: JUL 28, 2008@11:45 ACTION: APPROVED AT THE REQUEST OF: TEMPLETON,SHANNON DATE/TIME EDITED: SEP 16, 2010@11:02 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE DATE/TIME EDITED: MAY 25, 2012@10:55 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: ANWER,MOHAMED DATE/TIME EDITED: OCT 29, 2012@15:56 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: DEZORZI,KEVIN WITH CONCURRENCE OF: BROWN,STANLEY DATE/TIME EDITED: OCT 29, 2012@15:57 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HARRIS,JAMES WITH CONCURRENCE OF: RUZBACKI,RON DATE/TIME EDITED: FEB 23, 2015@09:41 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HASSETT,ANITA WITH CONCURRENCE OF: RUZBACKI,RON NUMBER: 2401 IA #: 2401 DATE CREATED: MAY 10, 1998 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJIPST3 NAME: OE/RR CONVERSION CALL TO PSJIPST3 ID: PSJIPST3 GENERAL DESCRIPTION: The CPRS post-installation makes a call to BADNAMES^PSJIPST3 so that Inpatient Meds can send a list of IV orders where the user name could not be resolved. STATUS: Active DURATION: Next Version MAIL MESSAGE: 26946673 GOOD ONLY FOR VERSION: 5.0 COMPONENT/ENTRY POINT: BADNAMES SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2402 IA #: 2402 DATE CREATED: MAY 10, 1998 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJORUT2 NAME: INPATIENT MED CALLS FOR OE/RR ID: PSJORUT2 GENERAL DESCRIPTION: Order Entry/Results Reporting would like approval to make the following calls to PSJORUT2. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946673 COMPONENT/ENTRY POINT: $$ENNG(PSJDPT,PSJNUM) COMPONENT DESCRIPTION: Call is made to determine whether a med order should be given. VARIABLES: PSJDPT TYPE: Input VARIABLES DESCRIPTION: Patient DFN. VARIABLES: PSJNUM TYPE: Input VARIABLES DESCRIPTION: Order number VARIABLES: $$ENNG TYPE: Output VARIABLES DESCRIPTION: Returns a 1 if order should not be given; 0 otherwise. COMPONENT/ENTRY POINT: ENVOL COMPONENT DESCRIPTION: Returns allowable volumes for a solution. VARIABLES: OI TYPE: Input VARIABLES DESCRIPTION: Pharmacy orderable item VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: Name of array to return results in. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2403 IA #: 2403 DATE CREATED: MAY 10, 1998 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJORUTL NAME: OE/RR CALLS TO PSJORUTL ID: PSJORUTL GENERAL DESCRIPTION: Order Entry/Results Reporting requests approval to make the following calls to PSJORUTL. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946673 COMPONENT/ENTRY POINT: ENDD COMPONENT DESCRIPTION: Returns all local (DRUG file) entries associated with a National Drug file pointer. VARIABLES: PD TYPE: Input VARIABLES DESCRIPTION: Primary Drug VARIABLES: TYPE TYPE: Input VARIABLES DESCRIPTION: O for Outpatient Med U for Unit Dose I for IV Med etc VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: Name of array to be returned. COMPONENT/ENTRY POINT: ENRFA COMPONENT DESCRIPTION: Returns formulary alternatives for a dispense drug. VARIABLES: DRUG TYPE: Input VARIABLES DESCRIPTION: Pointer to DRUG file VARIABLES: TYPE TYPE: Input VARIABLES DESCRIPTION: O for Outpatient Med U for Unit Dose I for IV Med etc VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: Name of array to be returned. COMPONENT/ENTRY POINT: ENDCM COMPONENT DESCRIPTION: Returns price, message, NDF entry, product name, and quantity dispense message. VARIABLES: DRUG TYPE: Input VARIABLES DESCRIPTION: Pointer to DRUG file VARIABLES: RESULTS TYPE: Output VARIABLES DESCRIPTION: Result of extrinsic function = price per dispense drug^message^NDF entry^PSNDF product name^Quantity dispense message COMPONENT/ENTRY POINT: ENDDIV COMPONENT DESCRIPTION: Returns all entries in DRUG file associated with Orderable Item. VARIABLES: OI TYPE: Input VARIABLES DESCRIPTION: Orderable Item pointer VARIABLES: TYPE TYPE: Input VARIABLES DESCRIPTION: Type of drug (A for additive; B for Base) VARIABLES: VOLUME TYPE: Input VARIABLES DESCRIPTION: Volume to uniquely identify orderable item. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: Name of array in which results will be returned. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2404 IA #: 2404 DATE CREATED: MAY 10, 1998 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJORMAR NAME: OE/RR CALL TO PSJORMAR ID: PSJORMAR GENERAL DESCRIPTION: Order Entry/Results Reporting seeks approval to call MAR^PSJORMAR to print MAR label via Print Format. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946673 COMPONENT/ENTRY POINT: MAR COMPONENT DESCRIPTION: Allows printing of MAR label VARIABLES: DFN TYPE: Input VARIABLES: ORDERNO TYPE: Input VARIABLES DESCRIPTION: Order number VARIABLES: FLAG TYPE: Input VARIABLES DESCRIPTION: 1 to print patient data; 0 otherwise VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: Name of array in which results will be returned. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2405 IA #: 2405 DATE CREATED: MAY 10, 1998 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSSHL1 NAME: OE/RR CALLS TO PSSHL1 ID: PSSHL1 GENERAL DESCRIPTION: Order Entry/Results Reporting wishes to document the call to EN1^PSSHL1 which is used to populate pharmacy orderables into the OE/RR ORDERABLE ITEM file. STATUS: Active DURATION: Next Version MAIL MESSAGE: 26976384 GOOD ONLY FOR VERSION: 1 COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: Called to populate Orderable Items file (#101.43) SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2406 IA #: 2406 DATE CREATED: MAY 10, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LR7OV2 NAME: OE/RR CONVERSION CALLS LR7OV2 ID: LR7OV2 GENERAL DESCRIPTION: This is to document OE/RR v3's call to EN^LR7OV2 as part of the CPRS Orders conversion. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946458 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: This entry point will convert lab orders for a particular patient. VARIABLES: ORVP TYPE: Input VARIABLES DESCRIPTION: Variable pointer reference to patient VARIABLES: FLAG TYPE: Input VARIABLES DESCRIPTION: 0 if call should be silent; 1 if it can 'talk' SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City EDITOR: INSLEY,MARCIA NUMBER: 2407 IA #: 2407 FILE NUMBER: 69 GLOBAL ROOT: LRO(69, DATE CREATED: MAY 10, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR REFERENCES TO LRO(69, ID: LRO(69, GLOBAL REFERENCE: LRO(69,D0,1, FIELD NUMBER: .01 FIELD NAME: LRDFN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7 FIELD NAME: PROVIDER LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .11 FIELD NAME: OERR ORDER # LOCATION: 0;11 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 13 FIELD NAME: COLLECTION STATUS LOCATION: 1;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 16 FIELD NAME: WARD COMMENTS LOCATION: WP ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LRO(69,D0,1,'AA', GLOBAL REFERENCE: LRO(69,DA(2),1,DA(1),2,'B', GLOBAL REFERENCE: LRO(69,D0,1,D1,2, FIELD NUMBER: 6 FIELD NAME: OERR ID LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LRO(69,'C', GLOBAL REFERENCE: LRO(69,'D', GENERAL DESCRIPTION: Order Entry/Results Reporting requests approval to make the following refrences to the Lab Order Entry file (#69). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946458 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD DBA Comments: JSHARVEY 20100916 - CHANGED PRIVATE USAGE TO CONTROLLED SUBSCRIPTION DUE T MULTIPLE SUBSCRIBERS. 5/24/12-VPR added as subscriber for VPR*1.0. Left NHIN as subscriber. DATE/TIME EDITED: SEP 16, 2010@10:59 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE DATE/TIME EDITED: SEP 16, 2010@11:01 ACTION: USAGE CHOICE CHANGED AT THE REQUEST OF: BUECHLER,MELANIE DATE/TIME EDITED: MAY 24, 2012@15:38 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: ANZALDUA,CAROL NUMBER: 2409 IA #: 2409 FILE NUMBER: 410 GLOBAL ROOT: PRCS(410, DATE CREATED: MAY 11, 1998 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: 2409 ID: PRCS(410, GLOBAL REFERENCE: PRCS(410,D0, FIELD NUMBER: .01 FIELD NAME: TRANSACTION NUMBER LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active MAIL MESSAGE: 26983200 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 2410 IA #: 2410 DATE CREATED: MAR 12, 2001 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUEDIT NAME: ENTER PROGRESS NOTE ID: TIUEDIT GENERAL DESCRIPTION: This entry point allows a package to invoke the TIU note entry process. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32657337 COMPONENT/ENTRY POINT: MAIN(TIUCLASS,SUCCESS,DFN,TIUTITLE,EVNTFLAG,NOSAVE,TIUNDA ,TIUSNGL,TIUCHNG) COMPONENT DESCRIPTION: This entry point is used to allow a progress note to be entered for a known patient. VARIABLES: TIUCLASS TYPE: Input VARIABLES DESCRIPTION: The IEN of the TIU DOCUMENT DEFINITION file (#8925.1). VARIABLES: SUCCESS TYPE: Input VARIABLES DESCRIPTION: Passed in as a parameter array - .TIUDA VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Poniter to Patient file (#2). VARIABLES: TIUSNGL TYPE: Input VARIABLES DESCRIPTION: Passed in set to 1. VARIABLES: TIUCHNG TYPE: Output VARIABLES DESCRIPTION: Optional. Passed in by reference. Returns array TIUCHNG, whose subscripts describe changes made to an existing document. In particular, user addended or was invited to addend the document, or user edited away the text of an existing document, upon which the document was deleted. Used by TIU Interdisciplinary Notes to determine whether or not to rebuild a List Manager display after user asks to create a new document and ends up addending or editing an existing document instead. SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING DETAILS: This entry point is used by the Outpatient Pharmacy package to enter progress notes after the entry of new prescriptions. Before attempting to make the call to this entry point a check is first made to see if the routine with the entry point reside on the system. The call is made as follows: I $T(MAIN^TIUEDIT)]"" D MAIN^TIUEDIT(3,.TIUDA,PSODFN,"","","","",1) SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: Used to enter text of consult using TIU interface. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS NUMBER: 2411 IA #: 2411 DATE CREATED: MAY 14, 1998 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJUTL1 NAME: DBIA2411 ID: PSJUTL1 GENERAL DESCRIPTION: This entry point is used to backfill/convert a patients Inpatient Medications orders after the installation of Outpatient Pharmacy version 7.0, and Inpatient Medications version 5.0. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27012230 COMPONENT/ENTRY POINT: CONVERT(PSOEDFN,PSOEWRT) COMPONENT DESCRIPTION: This entry point is used to convert/backfill orders to CPRS from the Inpatient Medications package, after installation of Inpatient Medications version 5.0. VARIABLES: PSOEDFN TYPE: Input VARIABLES DESCRIPTION: The internal entry number of the patient to be converted/backfilled. VARIABLES: PSOEWRT TYPE: Input VARIABLES DESCRIPTION: This variable is a 0 or 1. If 0, then it is a tasked job, and nothing is to be written. If 1, then a user has accessed the patient in the foreground, and messages can be written to the screen. SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2412 IA #: 2412 DATE CREATED: MAY 14, 1998 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: OR3CONV NAME: ON-THE-FLY ORDERS CONVERSION ID: OR3CONV GENERAL DESCRIPTION: This DBIA is a controlled subscription for packages needing to envoke the OE/RR version 3 Orders Conversion for a patient. STATUS: Active DURATION: Next Version MAIL MESSAGE: 26946658 GOOD ONLY FOR VERSION: 3 COMPONENT/ENTRY POINT: $$OTF(DFN,ORQUIET) COMPONENT DESCRIPTION: This entry point can be called by packages needing to ensure that the OE/RR Orders Conversion has been completed for a patient. It can be called as a silent or 'talking' call. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The IEN of the PATIENT file denoting the patient being processed. VARIABLES: ORQUIET TYPE: Input VARIABLES DESCRIPTION: Input a 1 to make the call silent or 0 to echo back information to the user as to what is occurring. VARIABLES: Value TYPE: Output VARIABLES DESCRIPTION: Result of extrinsic function will return: -1^error message if problem encountered 0 if patient already converted prior to call 1 if patient was successfully converted as part of call SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2414 IA #: 2414 FILE NUMBER: 100.99 GLOBAL ROOT: ORD(100.99, DATE CREATED: MAY 15, 1998 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Supported TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ORDERS CONVERSION CHECK ID: ORD(100.99, GLOBAL REFERENCE: ORD(100.99,1,'CONV') FIELD NUMBER: 3.01 FIELD NAME: OR3 CONVERSION COMPLETE? LOCATION: CONV;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This will be a 1 if the conversion is complete or a 0 if it is in progress. If CPRS has not been installed or the conversion has not yet started, this node will not exist. FIELD NUMBER: 3.06 FIELD NAME: OR3 BACKGROUND JOB START LOCATION: CONV;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field will contain the start date/time for the CPRS v1 Orders Conversion. FIELD NUMBER: 3.07 FIELD NAME: OR3 BACKGROUND JOB STOP LOCATION: CONV;7 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the completion time of the Orders Conversion. GLOBAL REFERENCE: ORD(100.99,1,'PTCONV',DFN) FIELD NUMBER: .01 FIELD NAME: OR3 PATIENTS TO CONVERT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: DINUMed entry of PATIENT file entries that have not yet been converted GENERAL DESCRIPTION: This DBIA authorizes direct global read of some fields in the ^ORD(100.99,1,"CONV") node. This node contains the fields used by the CPRS v1 Orders Conversion. Calling packages can use this information to determine whether the Orders Conversion is complete. It also authorizes access to ^ORD(100.99,1,"PTCONV") which is a multiple which contains the DFNs of patients left to convert. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27018882 NUMBER: 2415 IA #: 2415 DATE CREATED: MAY 15, 1998 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: PS EVSEND OR GENERAL DESCRIPTION: The PS EVSEND OR protocol is used to pass order messages from Pharmacy packages to other packages. This protocol is exported by the Pharmacy Data Management package, and is invoked by other Pharmacy Packages. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27020739 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING DETAILS: Inpatient Medications order information will be sent to other packages via the PS EVSEND OR protocol in the form of an array. An example of the call is D MSG^XQOR("PS EVSEND OR",.PSJMSG) SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING DETAILS: Outpatient Pharmacy prescription information will be sent to other packages via the PS EVSEND OR protocol in the form of an array. An example of the call is D MSG^XQOR("PS EVSEND OR",.MSG). SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: Listener protocols are OR RECEIVE and OCX ORDER CHECK HL7 RECIEVE. SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: SURGERY SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: Listener protocol VPR XQOR EVENTS added with VPR*1*3. SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT SUBSCRIBING DETAILS: Listener protocol is EDP Monitor. DBA Comments: 6/16/14-MC: Surgery added as a subscriber as requested by James Harris and approved by Ron Ruzbacki. Patch SR*3.0*180 scheduled for IOC in Fall 2014. 9/5/14-MC: Added VPR as a subscriber as requested by Melanie Buechler and approved by Ron Ruzbacki for patch VPR*1*3. 9/5/15-MM: Added Emergency Department as a subscriber with EDP Monitor as the listener protocol. Melanie found the Emergency Department had not been added as a subscriber when the application was released several years ago. Confirmed EDP Monitor was a protocol for this event in PATVEE. DATE/TIME EDITED: SEP 05, 2014@10:26 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: BUECHLER,MELANIE NUMBER: 2417 IA #: 2417 DATE CREATED: MAY 15, 1998 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJEEU NAME: Pharmacy Schedule and Admin Team Utilities ID: PSJEEU GENERAL DESCRIPTION: These entry points provide utilities to access entries in the ADMINISTRATION SCHEDULE file (#51.1). STATUS: Active MAIL MESSAGE: 26946673 COMPONENT/ENTRY POINT: ENSE COMPONENT DESCRIPTION: This allows add/edit/delete access to entries in the ADMINISTRATION SCHEDULE file (#51.1). The following fields are editable through this entry point: NAME (#.01); TYPE OF SCHEDULE (#5); STANDARD ADMINISTRATION TIMES (#1); MAX DAYS FOR ORDERS (#2.5) HOSPITAL LOCATION (#7) NAME (#.01) ADMINISTRATION TIMES (#1) VARIABLES: PSJPP TYPE: Input VARIABLES DESCRIPTION: The prefix of the package that the entry selected is assigned to. COMPONENT/ENTRY POINT: ENSHE COMPONENT DESCRIPTION: This allows add/edit/delete access to entries in the ADMINISTRATION SHIFT file (#51.15). The following fields are editable through this entry point: NAME (#.01); ABBREVIATION (#1); STANDARD START/STOP TIMES (#2) HOSPITAL LOCATION (#3) NAME (#.01) STANDARD START/STOP TIMES (#1) The PACKAGE field (#4) will be assigned whatever value passed in PSJPP. VARIABLES: PSJPP TYPE: Input VARIABLES DESCRIPTION: This must be the prefix of the package that the entry selected is assigned to. COMPONENT/ENTRY POINT: ENSV COMPONENT DESCRIPTION: This validates a schedule and returns information about the selected entry. VARIABLES: PSJW TYPE: Input VARIABLES DESCRIPTION: IEN of the entry in the HOSPITAL LOCATION file (#44). The administration times or shifts for the entry identified will be returned if PSJW is specified and data exists for that location. VARIABLES: PSJNE TYPE: Input VARIABLES DESCRIPTION: If PSJNE exists these will be no dialogue with the user from this call. VARIABLES: PSJPP TYPE: Input VARIABLES DESCRIPTION: This must be the prefix of the package that the entry selected is assigned to. VARIABLES: PSJX TYPE: Both VARIABLES DESCRIPTION: Specifies the name of the schedule to be accessed. If the name specified is ambiguous and PSJNE is undefined the user will be prompted to selected the entry. PSJX will return the name of the entry selected or null if the entry is not found. VARIABLES: PSJAT TYPE: Output VARIABLES DESCRIPTION: Defines the admin times or shift if any are defined for the selected entry. VARIABLES: PSJM TYPE: Output VARIABLES DESCRIPTION: If the entry is found this will define the frequency (in minutes) assigned to the selected schedule. VARIABLES: PSJTS TYPE: Output VARIABLES DESCRIPTION: This will define the type of schedule for the selected entry. VARIABLES: PSJY TYPE: Output VARIABLES DESCRIPTION: Defines the IEN of the selected entry in the ADMINISTRATION SCHEDULE file (#51.1). Null is returned if no entry is found. VARIABLES: PSJAX TYPE: Output VARIABLES DESCRIPTION: This is the maximum days continuous orders last for the specified schedule. Null will be returned if not found. COMPONENT/ENTRY POINT: ENSVI COMPONENT DESCRIPTION: Displays the NAME (#.01), STANDARD ADMINISTRATION TIMES (#1), MAX DAYS FOR ORDERS (#2.5) and SCHEDULE TYPE (#5) of the selected entry in the ADMINISTRATION file (#51.1). The user will be prompted to select the entry. VARIABLES: PSJPP TYPE: Input VARIABLES DESCRIPTION: This must be the prefix of the package that the entry selected is assigned to. COMPONENT/ENTRY POINT: ENATV COMPONENT DESCRIPTION: Validates administration times. VARIABLES: X TYPE: Both VARIABLES DESCRIPTION: This defines the data to be validated. If X defines a valid administration time(s) then it is returned as X. If it is not valid X is killed. COMPONENT/ENTRY POINT: ENSHV VARIABLES: X TYPE: Both VARIABLES DESCRIPTION: This defines the data to be validated. If X defines a valid administration shift then it is returned as X. If it is not valid X is killed. COMPONENT/ENTRY POINT: ENSPU COMPONENT DESCRIPTION: Calculates the number of times an action is to be taken. VARIABLES: PSJSCH TYPE: Input VARIABLES DESCRIPTION: The schedule of the action to be taken. VARIABLES: PSJM TYPE: Input VARIABLES DESCRIPTION: The frequency (in minutes) of the action. VARIABLES: PSJAT TYPE: Input VARIABLES DESCRIPTION: The administration times for the action. VARIABLES: PSJTS TYPE: Input VARIABLES DESCRIPTION: The schedule type of the schedule defined in PSJSCH. VARIABLES: PSJSD TYPE: Input VARIABLES DESCRIPTION: The start date/time of the range during which the action is to be taken. VARIABLES: PSJFD TYPE: Input VARIABLES DESCRIPTION: The stop date/time of the range during which the action is to be taken. VARIABLES: PSJOSD TYPE: Input VARIABLES DESCRIPTION: The start date/time of the action to be taken during the range defined by PSJSD and PSJFD. VARIABLES: PSJOFD TYPE: Input VARIABLES DESCRIPTION: The stop date/time of the action to be taken during the range defined by PSJSD and PSJFD. VARIABLES: PSJC TYPE: Output VARIABLES DESCRIPTION: Defines the number of times an action is to be taken. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2418 IA #: 2418 DATE CREATED: MAY 20, 1998 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSSJORDF NAME: OE/RR CALL TO PSSJORDF ID: PSSJORDF CREATOR: CASTLE,JOHN GENERAL DESCRIPTION: This DBIA allows use of START^PSSJORDF and START1^PSSJORDF as documented in the OE/RR Developer Interface Specification. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33211924 COMPONENT/ENTRY POINT: START(PSJORD,PSJOPAC) COMPONENT DESCRIPTION: The Default med route will be returned from the DEFAULT MED ROUTE field (#.06) of the PHARMACY ORDERABLE ITEM file (#50.7) if it is populated or from the POSSIBLE MED ROUTES multiple (#50.711) of the PHARMACY ORDERABLE ITEM file (#50.7) if it is populated with a single entry and the USE DOSAGE FORM MED ROUTE LIST field (#10) is set to "NO". The med route selection list will be returned with entries from the POSSIBLE MED ROUTES multiple (#50.711) if the USE DOSAGE FORM MED ROUTE LIST field (#10) is set to "NO". Otherwise, the med routes associated with the orderable item's dosage form, MED ROUTE FOR DOSAGE FORM multiple (#50.6061) of the DOSAGE FORM file (#50.606), will be returned. If there are no entries, then all med routes found in the MEDICATION ROUTES file (#51.2) will be returned. VARIABLES: PSJORD TYPE: Input VARIABLES DESCRIPTION: Orderable Item IEN VARIABLES: TMP('PSJMR',$J,IEN) TYPE: Output VARIABLES DESCRIPTION: MED ROUTE^MED ROUTE ABBREVIATION^MED ROUTE IEN^OUTPATIENT EXPANSION^IV FLAG^DEFAULT FLAG D in the DEFAULT FLAG field indicates this is the default MED ROUTE for the specified orderable item. VARIABLES: TMP('PSJNOUN',$J,IEN) TYPE: Output VARIABLES DESCRIPTION: NOUN^VERB^PREPOSITION VARIABLES: TMP('PSJSCH',$J) TYPE: Output VARIABLES DESCRIPTION: DEFAULT SCHEDULE NAME VARIABLES: PSJOPAC TYPE: Input VARIABLES DESCRIPTION: This variable represents the pharmacy package for which the order is being entered in CPRS. "O" will be for an Outpatient order, and "I" will be for an Inpatient order. This will impact the default Schedule that is returned, since some Schedules are allowed for Outpatient orders, but not for Inpatient orders. COMPONENT/ENTRY POINT: START1(PSJORD,PSJQOF) COMPONENT DESCRIPTION: This is the entry point from the CPRS IV Dialog for IV orders. If there is only one orderable item in the IV order request, then the same logic defined under the START component will be used to return the default med route and the med route selection list from the PHARMACY ORDERABLE ITEM file (#50.7). If there is more than one orderable item on the IV order request, the PHARMACY ORDERABLE ITEM file (#50.7) will be checked for each orderable item for the default med route and med route selection list as defined under START component. If there is a default med route common with every orderable item, then that default med route will be returned. Similarly, the list of possible med routes that are common with every orderable item will be returned. VARIABLES: PSJORD TYPE: Both VARIABLES DESCRIPTION: Array of pharmacy orderable items that make up the IV order. The inbound structure is: PSJORD(0)=Number of orderable items in the order PSJORD(n)=Orderable item IEN number The output structure is: PSJORD(n)=IEN^NAME^ABBREVIATION^OUTPATIENT EXPANSION^DEFAULT IEN is the Medication Route IEN from the Medication Route File #51.2. NAME, ABBREVIATION, and OUTPATIENT EXPANSION are all pieces of the data string from ^PS(51.2,IEN,0) If all the orderable items associated with the IV order have the same default med route defined in the Pharmacy Orderable Item File #50.7, then a "D" will be added as the last piece of the data string returned. If there is no default, or if there is more than one orderable item on the order, the DEFAULT piece will be null. VARIABLES: PSJQOF TYPE: Input VARIABLES DESCRIPTION: This denotes whether the IV order is a quick order or not. If the flat is set to 1 then all med routes defined in the med route file that are flagged for use in all packages, and are flagged for use in IVs will be returned. PSJQOF=0 This is not a quick order PSJQOF=1 This is a quick order SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City DBA Comments: Deactivated 20110510 to modify copmonent descriptions deactivated/reactivated 20090713 to add DEFAULT MED ROUTE FOR CPRS (#80.7) edited 20100429 to modify descriptions in START1(PSJORD,PSJQOF) and in in variable PSJORD. DATE ACTIVATED: MAY 10, 2011 DATE/TIME EDITED: FEB 05, 2008@15:18 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: TEMPLETON,SHANNON DATE/TIME EDITED: JUL 28, 2008@11:45 ACTION: APPROVED AT THE REQUEST OF: TEMPLETON,SHANNON DATE/TIME EDITED: JUL 13, 2009@13:31 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CASTLE,JOHN DATE/TIME EDITED: JUL 13, 2009@16:17 ACTION: APPROVED AT THE REQUEST OF: CASTLE,JOHN WITH CONCURRENCE OF: MELDRUM,KEVIN DATE/TIME EDITED: APR 29, 2010@14:52 ACTION: CONTENT CORRECTED AT THE REQUEST OF: HARRIS,JAMES WITH CONCURRENCE OF: PULEO,ANTHONY DATE/TIME EDITED: MAY 10, 2011@10:45 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: ALSAHHAR,SAMI DATE/TIME EDITED: MAY 10, 2011@12:30 ACTION: APPROVED AT THE REQUEST OF: ALSAHHAR,SAMI NUMBER: 2419 IA #: 2419 FILE NUMBER: 71.2 GLOBAL ROOT: RAMIS(71.2, DATE CREATED: MAY 20, 1998 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR REFERENCES TO RAMIS(71.2 ID: RAMIS(71.2, GLOBAL REFERENCE: RAMIS(71.2,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: AMIS CREDIT INDICATOR LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: RAMIS(71.2,'AB' GLOBAL DESCRIPTION: Loops through the 'AB' x-ref which is a whole file x-ref on the TYPE OF IMAGING multiple. GLOBAL REFERENCE: RAMIS(71.2,'B' GLOBAL DESCRIPTION: Used to get IEN of entry by name. GENERAL DESCRIPTION: This DBIA requests direct global read access to the fields and cross-references documented in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27059736 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2420 IA #: 2420 FILE NUMBER: 71 GLOBAL ROOT: RAMIS(71, DATE CREATED: MAY 20, 1998 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR REFERENCE TO RAMIS(71 ID: RAMIS(71, GLOBAL REFERENCE: RAMIS(71,DA,0) FIELD NUMBER: 11 FIELD NAME: RAD/NM PHYS APPROVAL REQUIRED LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This DBIA requests direct global read access to the RAD/NUC MED PROCEDURES file as listed in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27059736 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2421 IA #: 2421 DATE CREATED: MAY 20, 1998 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRAOR1 NAME: GMRADPT DATA SUBSET ID: GMRAOR1 CREATOR: RUFF,ROBERT F GENERAL DESCRIPTION: This integration agreement allows subscribing packages to retrieve a subset of the adverse reaction data returned by integration agreement #10099 GMRADPT. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946164 KEYWORDS: CPRS COVERSHEET API COMPONENT/ENTRY POINT: EN1(DFN,ARRAY) COMPONENT DESCRIPTION: Returns array of adverse reactions for a patient along with signs and symptoms. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The internal entry number (IEN) of the patient in the PATIENT file (#2). VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: Name of the array to return data in. If not defined, data is returned in GMRARXN(). Returned Data Format: ARRAY(X)=Caret-delimited string X - number that starts at one for the first reaction and increments by one for each subsequent reaction Caret-delimited string: Piece Value ================================================== 1 REACTANT field (#.02) in the PATIENT ALLERGIES file (#120.8) NOTE: For reactions of type DRUG, DRUG FOOD, DRUG OTHER, or DRUG FOOD OTHER where the REACTANT field does not exactly match the GMR ALLERGY field (#1) in external format, this piece will contain the GMR ALLERGY field in external format followed by a space followed by the REACTANT field surrounded by brackets. Consider two examples: "ATORVASTATIN [LIPITOR]" and "IODINE". 2 SEVERITY field (#14.5) in the ADVERSE REACTION REPORTING file (#120.85) in external format 3 IEN in the PATIENT ALLERGIES file (#120.8) ARRAY(X,"S",COUNT)=Semi-colon delimited string COUNT - number that starts at one for the first sign or symptom and increments by one for each subsequent sign or symptom. Semi-colon delimited string: Piece Value ================================================== 1 REACTION sub-field (#.01) in the REACTIONS field (#10) in the PATIENT ALLERGIES file (#120.8) in external format 2 DATE ENTERED sub-field (#3) in the REACTIONS field (#10) in the PATIENT ALLERGIES file (#120.8) in internal FileMan format NOTE: This piece is only returned if the GMRAIDT input variable evaluates to true. VARIABLES: GMRA TYPE: Input VARIABLES DESCRIPTION: Optional. Type of reactions to return. Refer to integration agreement #10099 GMRADPT for an explanation of this variable. VARIABLES: GMRAIDT TYPE: Input VARIABLES DESCRIPTION: Optional. If set to a value that evaluates to true, the API will return the date/time on which each sign or symptom that is returned occurred in the second semi-colon piece of ARRAY(X,"S",COUNT). If set to a value that evaluates to false or is undefined, the API will not return the date/time. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: MYHEALTHEVET SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 8/14/13-MC:Deactivated for editing by Robert Ruff 1/9/15-MC: Robert Ruff has confirmed that he has completed his edits and changes will not negatively impact the subscribing applications. 3/11/15-MC: Added VPS as a subscriber at the request of Carolyn Wheless for VPS patch VPS*1*15, planned for release April 2015. Received custodial approval from Bob Ruff. However, Bob emphasized that VPS should note that the API currently in production at sites is not as described in the ICR. Patch GMRA*4*46 (still in development) will update the API to match what is in the currently active ICR. The GMRA patch is scheduled for release later this year (2015). Bob stated that the biggest difference is that the as-is does not allow retrieval of reactions from remote sites via HDR; the to-be will. Also, the to-be adds an additional piece to the ARRAY(X,"S",COUNT) return node; as long as the code explicitely uses the $PIECE to retrieve specific pieces (instead of pulling the entire node) and can function if any of those pieces is blank, everything should be fine. Carolyn has responded that VPS has noted the forthcoming changes in patch GMRA*4*46. VPS confirms that $PIECE is used to retrieve specific pieces from the node and includes edits for blank fields. DATE ACTIVATED: JAN 09, 2015 DATE/TIME EDITED: JAN 09, 2015@08:46 ACTION: APPROVED AT THE REQUEST OF: RUFF,ROBERT DATE/TIME EDITED: MAR 11, 2015@07:28 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: RUFF,ROBERT NUMBER: 2423 IA #: 2423 DATE CREATED: MAY 21, 1998 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSSQOC NAME: Inpatient Medications Quick Order Conversion ID: PSSQOC GENERAL DESCRIPTION: Used by OR*2.5*49 to convert existing Inpatient Medication Quick Orders for use with CPRS v1.0. STATUS: Active MAIL MESSAGE: 26976384 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: This is the main entry point for the Inpatient Medication Quick Order Conversion. COMPONENT/ENTRY POINT: EN(x) COMPONENT DESCRIPTION: Converts the Inpatient Medications Quick Order attached to the protocol identified in X for use with CPRS v1.0. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Identifies protocol that is attached to the quick order that is to be converted. VARIABLES: TMP('PSJQO',$J,1) TYPE: Output COMPONENT/ENTRY POINT: EN(X) SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2424 IA #: 2424 DATE CREATED: MAY 21, 1998 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCA1 NAME: ROUTINE CALLS IN GMRCA1 ID: GMRCA1 GENERAL DESCRIPTION: This DBIA will allow calling various entry points in GMRCA1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32979707 COMPONENT/ENTRY POINT: DC(IEN,ACTION) COMPONENT DESCRIPTION: Call to DC a consult VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of file 123 VARIABLES: ACTION TYPE: Input VARIABLES DESCRIPTION: Input 6 for DC or 19 for Cancel COMPONENT/ENTRY POINT: COMMENT(IEN) COMPONENT DESCRIPTION: Allow comment to be added to existing consult. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of entry in file 123 COMPONENT/ENTRY POINT: RC(IEN) COMPONENT DESCRIPTION: Allow a consult to be received VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of entry in file 123 COMPONENT/ENTRY POINT: PS(IEN) COMPONENT DESCRIPTION: Allow a service copy to be printed for a consult request. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of entry in file 123 COMPONENT/ENTRY POINT: EDTSUB(GMRCO) COMPONENT DESCRIPTION: Allow a provider or update user to edit/resubmit a canceled consult. VARIABLES: GMRCO TYPE: Input VARIABLES DESCRIPTION: IEN of file 123. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City EDITOR: INSLEY,MARCIA EDITOR: ANTRY,MIKE NUMBER: 2425 IA #: 2425 DATE CREATED: MAY 21, 1998 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCACTM NAME: CALL TO GMRCACTM ID: GMRCACTM GENERAL DESCRIPTION: This DBIA will alow Order Entry/Results Reporting to call CPRS^GMRCACTM. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 COMPONENT/ENTRY POINT: CPRS(IENSTRING) COMPONENT DESCRIPTION: Call returns a flag determining whether a user has privileges for a particular consult service. This is used to determine what action menu a user should have to process or review consults. VARIABLES: IENSTRING TYPE: Input VARIABLES DESCRIPTION: A string of IENs of file 123 separated by semi-colons. VARIABLES: ORFLG(IEN) TYPE: Output VARIABLES DESCRIPTION: ORFLG(IEN)=flag (1st piece) where IEN is the consult internal entry number and the flag is a number representing one of the following: 1 = GMRCACTM USER REVIEW SCREEN - tracking/review actions 2 = GMRCACTM SERVICE ACTION menu - service clinician actions 3 = Indicates the user is an administrative update user. CPRS uses this flag to build equivalent menus in the GUI and List Manager. ORFLG(IEN)= (2ND piece) IEN is the Consult (IEN) in file 123. The clinician's DUZ will be used to determine what type of update authority is granted. Piece two will contain the field in file 123.5 (REQUEST SERVICES) that gave the user update authority (ex. Update user WO/Notification, Special Update user, Administrative Update user). ORFLG(IEN)= (3rd piece) Piece will contain the Service in file 123.5 (REQUEST SERVICES) that gave the user update authority (ex. CARDIOLOGY, NEUROLOGY). ORFLG(IEN)= (4th piece) Piece will contain a "1" if the user is allowed to associate medicine results with a consult procedure request. ORFLG(IEN)= (5th piece) Piece will contain a "1" if a user can disassociate a medicine result that was incorrectly associated with a consult procedure request. ORFLG(IEN)= (6th piece) Piece will contain a "1" if the user is the provider or update user for the consult. If the piece contains a "1" the user is allowed to EDIT and RESUBMIT a canceled request. CPRS uses the ORFLG to perform the following: 1. Build equivalent menus (USER REVIEW, SERVICE ACTION) in the GUI and List Manager. 2. Determine user update authority. 3. List the Service that granted the update authority. 4. Determine if a user has authority to associate Medicine results with a Procedure Request. 5. Determine if a user has authority to disassociate a medicine result that was incorrectly associate with a Procedure Request. 6. Determine if a user has authority to EDIT and RESUBMIT a Cancel request. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM EDITOR: INSLEY,MARCIA DBA Comments: 6/3/14-MC: Brandon DeWayne originally requested to add FBCS as a subscriber to this ICR 6/20/13. Approval received from Tony Thompson. Patch was released 9/11/13. Since approval was received and patch has been released, adding FBCS as a subscribing package to the ICR. NUMBER: 2426 IA #: 2426 DATE CREATED: MAY 21, 1998 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCASV NAME: CALLS TO GMRCASV ID: GMRCASV GENERAL DESCRIPTION: This DBIA request permission for Order Entry/Results Reporting to call the following entry points in GMRCASV. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 COMPONENT/ENTRY POINT: SERV1 COMPONENT DESCRIPTION: Gets list of orderable consult services. VARIABLES: GMRCTO TYPE: Input VARIABLES DESCRIPTION: Set to 1 to not include disabled or tracking only services VARIABLES: GMRCDG TYPE: Input VARIABLES DESCRIPTION: IEN of file 123.5 denoting consult service for which to return child entries. For OE/RR, this is 'ALL SERVICES' entry. VARIABLES: TMP('GMRCSLIST',$J, TYPE: Output VARIABLES DESCRIPTION: ^TMP("GMRCSLIST",$J,COUNTER)=IEN^NAME^0^(+ if child exists)^USAGE VARIABLES: TMP('GMRCS',$J, TYPE: Output VARIABLES DESCRIPTION: ^TMP("GMRCS",$J,IEN)=CONSULT SERVICE NAME COMPONENT/ENTRY POINT: ASRV COMPONENT DESCRIPTION: Entry point to select a new consult service VARIABLES: GMRCDG TYPE: Output VARIABLES DESCRIPTION: IEN of consult service selected VARIABLES: GMRCQUT TYPE: Output VARIABLES DESCRIPTION: 1 if user aborts service question VARIABLES: TMP('GMRCSLIST',$J, TYPE: Output VARIABLES DESCRIPTION: ^TMP("GMRCSLIST",$J,COUNTER)=IEN^NAME^0^(+ if child exists)^USAGE VARIABLES: TMP('GMRCS',$J, TYPE: Output VARIABLES DESCRIPTION: ^TMP("GMRCS",$J,IEN)=CONSULT SERVICE NAME SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM EDITOR: INSLEY,MARCIA DBA Comments: 6/3/14-MC: Brandon DeWayne originally requested that FBCS be added to this ICR as a subscriber 6/20/13. Approval was received by Tony Thompson. Last email correspondence with Brandon was July 2013. Patch was discovered to have been released 9/11/13. Since approval was received and patch has been released, adding FBCS as a subscribing package to this ICR. NUMBER: 2427 IA #: 2427 DATE CREATED: MAY 21, 1998 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCTIU NAME: CALLS TO GMRCTIU ID: GMRCTIU CREATOR: THOMPSON,WILLIAM ANTHONY GENERAL DESCRIPTION: This DBIA will document the calls from Order Entry/Results Reporting to GMRCTIU. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 COMPONENT/ENTRY POINT: ENTER(IEN) COMPONENT DESCRIPTION: Allows completion of a consult with a TIU note VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of entry in file 123 COMPONENT/ENTRY POINT: ADDEND(IEN) COMPONENT DESCRIPTION: Allows addendum to be attached to consult VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of entry in file 123. COMPONENT/ENTRY POINT: ANYPENDG(DFN,USER) COMPONENT DESCRIPTION: This API is used to determine if there are any unresolved consults for the patient (DFN) that the user (USER) may complete. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This variable is a pointer to the PATIENT file (#2). VARIABLES: USER TYPE: Input VARIABLES DESCRIPTION: This variable is a pointer to the NEW PERSON (#200) file. VARIABLES: BOOLEAN TYPE: Output VARIABLES DESCRIPTION: This variable is returned as: 1 = there are unresolved consults the user may update 0 = there are no unresolved consults the user may update COMPONENT/ENTRY POINT: GET(IEN,TIEN,STATUS,AUTHOR) COMPONENT DESCRIPTION: Update consult status from TIU results VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IFN from file 123 VARIABLES: TIEN TYPE: Input VARIABLES DESCRIPTION: IFN from TIU VARIABLES: STATUS TYPE: Input VARIABLES DESCRIPTION: TIU status of report VARIABLES: AUTHOR TYPE: Input VARIABLES DESCRIPTION: Author of document as DUZ SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City DATE ACTIVATED: MAY 25, 2010 DATE/TIME EDITED: MAY 25, 2010@13:26 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: THOMPSON,WILLIAM DATE/TIME EDITED: MAY 25, 2010@14:14 ACTION: APPROVED AT THE REQUEST OF: THOMPSON,WILLIAM NUMBER: 2428 IA #: 2428 DATE CREATED: MAY 21, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LR7OR3 NAME: USE OF LR7OR3 CALLS ID: LR7OR3 GENERAL DESCRIPTION: This DBIA formalizes the documentation for calls to LR7OR3 as documented in the OE/RR Interface Specification document. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 37779397 COMPONENT/ENTRY POINT: TEST(TEST,.Y) COMPONENT DESCRIPTION: Call to return ordering parameters for a test. VARIABLES: TEST TYPE: Input VARIABLES DESCRIPTION: IEN of file 60 VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Array of allowable and default attributes for test COMPONENT/ENTRY POINT: SCOM(TEST,SAMP,.Y) COMPONENT DESCRIPTION: Gets ward remarks for specimen and puts in text array. VARIABLES: TEST TYPE: Input VARIABLES DESCRIPTION: IEN of file 60 VARIABLES: SAMP TYPE: Input VARIABLES DESCRIPTION: Collection sample (pointer to file 62) VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Array of text of ward remarks. COMPONENT/ENTRY POINT: $$DEFURG() COMPONENT DESCRIPTION: Returns default urgency for lab. VARIABLES: VALUE TYPE: Output VARIABLES DESCRIPTION: Extrinsic function returns the internal value of the DEFAULT URGENCY field (#301) in the LABORATORY SITE file (#69.9). COMPONENT/ENTRY POINT: GCOM(TEST,.Y) COMPONENT DESCRIPTION: Gets General Ward Instructions for test and puts in text array. VARIABLES: TEST TYPE: Input VARIABLES DESCRIPTION: IEN of file 60 VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Array of text of ward instructions. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2429 IA #: 2429 DATE CREATED: MAY 21, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LR7OV4 NAME: USE OF LR7OV4 CALLS ID: LR7OV4 GENERAL DESCRIPTION: This DBIA formalizes the documentation for calls to LR7OV4 as documented in the OE/RR Interface Specification document. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31727722 COMPONENT/ENTRY POINT: $$ON(DIV) COMPONENT DESCRIPTION: Returns ordering parameters for immediate collection. VARIABLES: DIV TYPE: Input VARIABLES DESCRIPTION: Pointer value from IMMED LAB COLLECT DIV. multiple in LABORATORY SITE file (#69.9). VARIABLES: VALUE TYPE: Output VARIABLES DESCRIPTION: Extrinsic function returns 1 if immediate collect is allowed for division. Otherwise, 0 is returned. COMPONENT/ENTRY POINT: $$DEFTIME(DIV) COMPONENT DESCRIPTION: Returns next valid time form immediate collection. VARIABLES: DIV TYPE: Input VARIABLES DESCRIPTION: Pointer value from IMMED LAB COLLECT DIV. multiple in LABORATORY SITE file (#69.9). VARIABLES: VALUE TYPE: Output VARIABLES DESCRIPTION: Extrinsic function returns: internal date/time^external date/time if valid result found ""^error message if time could not be returned COMPONENT/ENTRY POINT: $$VALID(DIV,TM) COMPONENT DESCRIPTION: Validates immediate collection time. VARIABLES: DIV TYPE: Input VARIABLES DESCRIPTION: Pointer value from IMMED LAB COLLECT DIV. multiple in LABORATORY SITE file (#69.9). VARIABLES: TM TYPE: Input VARIABLES DESCRIPTION: Collection date/time to validate VARIABLES: VALUE TYPE: Output VARIABLES DESCRIPTION: Extrinsic function returns: 1 if time is valid collection time 0^error message if tim not valid COMPONENT/ENTRY POINT: SHOW(DIV,.Y) COMPONENT DESCRIPTION: Returns an array of allowable date/time ranges for immediate collection which is formatted for display. VARIABLES: DIV TYPE: Input VARIABLES DESCRIPTION: Pointer value from IMMED LAB COLLECT DIV. multiple in LABORATORY SITE file (#69.9). VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Array of allowable date/time ranges for immediate collection formatted for display. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: NUMBER: 2430 IA #: 2430 DATE CREATED: MAY 21, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: USE OF XUTL('XQORM', GENERAL DESCRIPTION: Setting data into XUTL("XQORM" allows the protocol unwinder to display the data as if it were a protocol. This has been used for quite some time, but was never formally requested/documented. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26892491 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: Order Entry/Results Reporting uses this functionality to display DIALOG file entries for selection. SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: Health Summary uses this functionality to display Health Summary Components for selection. SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES NUMBER: 2432 IA #: 2432 FILE NUMBER: 44 GLOBAL ROOT: SC( DATE CREATED: JUN 24, 2004 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2432 ID: SC( GLOBAL REFERENCE: SC(D0,0 FIELD NUMBER: 3.5 FIELD NAME: DIVISION LOCATION: 0;15 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field contains the Division assigned to the selected entry in the HOSPITAL LOCATION file (#44) GENERAL DESCRIPTION: Medicine requests a FILEMAN read to the DIVISION field (#3.5) of the HOSPITAL LOCATION file (#44) [$P(^SC(D0,0),"^",15)] to display what division a Ward belongs to. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27066641 SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Hines SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS SUBSCRIBING PACKAGE: INTEGRATED BILLING NUMBER: 2433 IA #: 2433 DATE CREATED: JUN 10, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: XPDGREF GENERAL DESCRIPTION: Developers can put information in the KIDS Transport Global, ^XTMP. The transport global will be available during the Environment Check, Pre-Install, and Post-Install routines. The developer can access the information by using the variable XPDGREF to read or set the transport global. example: to set the transport global S @XPDGREF@("My subscript",1)="Information I need" to read the transport global S X=@XPDGREF@("My subscript",1) Developers can create a routine that will always set information into the transport global whenever a package is transported. The field, PRE-TRANSPORTATION ROUTINE, will be run during the transport process. The variable XPDGREF will be available to set information into the transport global. STATUS: Active MAIL MESSAGE: 27205607 COMPONENT/ENTRY POINT: XPDGREF COMPONENT DESCRIPTION: This variable can be used to set or retrieve information from the KIDS transport global, ^XTMP. It can be used in the following routine: Pre-Transportation Routine, Pre-Install Routine, and Post-Install Routine. Example: to set the transport global S @XPDGREF@("My subscript",1)="Information I need" to read the transport global S X=@XPDGREF@("My subscript",1) VARIABLES: XPDGREF TYPE: Both VARIABLES DESCRIPTION: This variable can be used to set or retrieve information from the KIDS transport global, ^XTMP. It can be used in the following routine: Pre-Transportation Routine, Pre-Install Routine, and Post-Install Routine. Example: to set the transport global S @XPDGREF@("My subscript",1)="Information I need" to read the transport global S X=@XPDGREF@("My subscript",1) NUMBER: 2434 IA #: 2434 DATE CREATED: JUN 16, 1998 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: HLUTIL NAME: DBIA2434 ID: HLUTIL GENERAL DESCRIPTION: Patch HL*1.6*36 introduces 3 new entry points in routine HLUTIL. These entry points support two new features, "Don't Purge" and "Reprocessing" messages, which were originally requested by the CIRN project. Patch HL*1.6*19 added a 4th API and restricted the use of all APIs to TCP/IP connections. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27256002 COMPONENT/ENTRY POINT: $$DONTPURG COMPONENT DESCRIPTION: Sets the new flag field "DON'T PURGE" (#773,10) to prevent a message being purged by the "HL PURGE TRANSMISSIONS" option. input: none return value: 1 means field has been successfully set. -1 means call has failed; nothing has been changed. Call this function from one of the following routines: - RTN routine, in $$REPROC^HLUTIL(IEN,RTN). - routine in "GENERATE/PROCESS ROUTINE"(#101,771). - routine in "GENERATE/PROCESS ACK ROUTINE"(#101,772). When called by these routines, HL7 assumes that the variable HLMTIENS (message IEN of file #773) is already properly defined. This variable should already be defined if in a message processing context. COMPONENT/ENTRY POINT: $$TOPURG COMPONENT DESCRIPTION: Clear the flag field "DON'T PURGE" (#773,10) to allow the message to be purged by the "HL PURGE TRANSMISSIONS" option. input: none return value: 0 means field has been successfully cleared -1 means call has failed; nothing has been changed Call this function from one of the following routines: - RTN routine, in $$REPROC^HLUTIL(IEN,RTN). - routine in "GENERATE/PROCESS ROUTINE"(#101,771). - routine in "GENERATE/PROCESS ACK ROUTINE"(#101,772). When called by these routines, HL7 assumes that the variable HLMTIENS (message IEN of file #773) is already properly defined. This variable should already be defined if in a message processing context. COMPONENT/ENTRY POINT: $$REPROC COMPONENT DESCRIPTION: Call this entry point to reprocess an inbound message in file 773. input value: IEN is the internal entry number of the message in file 773 RNT is the routine to execute to process the message return value: 0 means call has been successfully completed. -1 means call has failed; nothing has been changed. The IEN, which is provided to $$REPROC^HLUTIL(IEN,RTN) should be the message IEN of file #773. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: the internal entry number of the message in file 773 VARIABLES: RTN TYPE: Input VARIABLES DESCRIPTION: routine, to be Xecuted for reprocessing the message. COMPONENT/ENTRY POINT: $$SETPURG COMPONENT DESCRIPTION: This function can set the new flag field "DON'T PURGE" (#773,10) to prevent or allow a message to be purged by the "HL PURGE TRANSMISSIONS" option. input: STATUS set to 0 or 1. 1=prevents message from being purged 0=allows message to be purged return value: 1 means field has been successfully set. -1 means call has failed; nothing has been changed. Call this function from one of the following routines: - RTN routine, in $$REPROC^HLUTIL(IEN,RTN). - routine in "GENERATE/PROCESS ROUTINE"(#101,771). - routine in "GENERATE/PROCESS ACK ROUTINE"(#101,772). When called by these routines, HL7 assumes that the variable HLMTIENS (message IEN of file #773) is already properly defined. This variable should already be defined if in a message processing context. VARIABLES: STATUS TYPE: Input VARIABLES DESCRIPTION: This variable can have a value of 1 or 0. 1 sets the message's purge flag such that the message won't be purged. 0 sets the message's purge flag such that the message will be purged. NUMBER: 2437 IA #: 2437 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: JUN 21, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2437 ID: DGPM( GLOBAL REFERENCE: DGPM('APRD' GLOBAL DESCRIPTION: 'APRD' xref. GLOBAL REFERENCE: DGPM(D0,0) FIELD NUMBER: .06 FIELD NAME: WARD LOCATION LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Zeroeth node GENERAL DESCRIPTION: References to ADT/Registration globals and routines. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281136 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 2438 IA #: 2438 FILE NUMBER: 40.8 GLOBAL ROOT: DG(40.8, DATE CREATED: JUN 22, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2438 ID: DG(40.8, GLOBAL REFERENCE: DG(40.8,DO,0) FIELD NUMBER: 1 FIELD NAME: Facility Number LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field stores the number of the facility that a division is affiliated with. This should be a 3 digit number the site is assigned. It may include a suffix. FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL DESCRIPTION: GENERAL DESCRIPTION: Pharmacy Benefits Management (PBM) software needs to extract the facility number from the Medical Center Division file #40.8. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27301526 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI SUBSCRIBING PACKAGE: POLICE & SECURITY NUMBER: 2440 IA #: 2440 FILE NUMBER: 42 GLOBAL ROOT: DIC(42 DATE CREATED: JUN 22, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2440 ID: DIC(42 GLOBAL REFERENCE: DIC(42, FIELD NUMBER: .015 FIELD NAME: DIVISION LOCATION: 0;11 ACCESS: Read w/Fileman FIELD DESCRIPTION: Division pointer. Division at which this ward is located. GLOBAL DESCRIPTION: GENERAL DESCRIPTION: Pharmacy Benefits Managment (PBM) vs 3.0 (formerly D&PPM) software needs to access the division pointer. This will be used to extract the facility number from the Medical Center Division file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27301547 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING SUBSCRIBING PACKAGE: BAR CODE MED ADMIN NUMBER: 2441 IA #: 2441 FILE NUMBER: 50 GLOBAL ROOT: PSDRUG( DATE CREATED: JUN 29, 1998 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Obtain data from the Drug (50) file. ID: PSDRUG( GLOBAL REFERENCE: PSDRUG(D0,0) FIELD NUMBER: .01 FIELD NAME: Generic Name LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: VA Classification LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSDRUG(D0,'I') FIELD NUMBER: 100 FIELD NAME: Inactive Date LOCATION: I;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the date that the drug was inactivated. GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. Radiology/Nuclear Medicine obtains the following data from Pharmacy Data Management's (PDM) Drug file: field name field number node;piece purpose -------------------------------------------------------------------------- Generic Name .01 0;1 display Generic Name VA Classification 2 0;2 radiopharmaceutical check Inactive Date 100 I;1 check if an active drug VIEWER: SCHLEHUBER,CAMERON VIEWER: TATUM,WILLIAM VIEWER: BERTUZIS,LINA STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 27370794 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines EDITOR: BLOCKER,DAVE NUMBER: 2442 IA #: 2442 FILE NUMBER: 74 GLOBAL ROOT: RARPT( DATE CREATED: JUN 30, 1998 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2442 ID: RARPT( GLOBAL REFERENCE: RARPT(D0,0) FIELD NUMBER: 3 FIELD NAME: EXAM DATE/TIME LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: CIRN needs read access to the ^RARPT global to calculate the Master of Record score. Traversing the ^RARPT("C" x-ref, CIRN uses $P(^RARPT(D0,0),U,3) to calculate the score. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27354136 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: IMAGING NUMBER: 2443 IA #: 2443 FILE NUMBER: 409.68 GLOBAL ROOT: SCE( DATE CREATED: JUN 30, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2443 ID: SCE( GLOBAL REFERENCE: SCE(D0,0) FIELD NUMBER: .01 FIELD NAME: DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: CLINIC STOP CODE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: CIRN traverses the ^SCE("C" x-ref and uses ^SCE(D0,0) to calculate the Master of Record score. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27354173 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION SUBSCRIBING DETAILS: JSHARVEY 20061107/ ADDED SCID TO SUBSCRIBER LIST AS PER FAIN. DBA Comments: JSHARVEY 20061107/MODIFIED SUBSCRIBER LIST DATE/TIME EDITED: NOV 28, 2006@09:33 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SWESKY,JEFF WITH CONCURRENCE OF: FAIN,ZACH NUMBER: 2444 IA #: 2444 FILE NUMBER: 9000010 GLOBAL ROOT: AUPNVSIT( DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2444 ID: AUPNVSIT( GLOBAL REFERENCE: AUPNVSIT(D0,0) FIELD NUMBER: .24 FIELD NAME: OPTION USED TO CREATE LOCATION: 0;24 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Zeroeth node. GENERAL DESCRIPTION: VISIT file access to zeroeth node. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281144 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2445 IA #: 2445 FILE NUMBER: 9000010.13 GLOBAL ROOT: AUPNVXAM( DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2445 ID: AUPNVXAM( GLOBAL REFERENCE: AUPNVXAM(D0,0) FIELD NUMBER: .01 FIELD NAME: EXAM LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Exam name field GLOBAL DESCRIPTION: Zeroeth node. GENERAL DESCRIPTION: V EXAM file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281144 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2446 IA #: 2446 FILE NUMBER: 9000010.23 GLOBAL ROOT: AUPNVHF( DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2446 ID: AUPNVHF( GLOBAL REFERENCE: AUPNVHF(D0,0) FIELD NUMBER: .01 FIELD NAME: HEALTH FACTOR LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Health factor name field. GLOBAL DESCRIPTION: Zeroeth node. GENERAL DESCRIPTION: V HEALTH FACTORS file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281144 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2447 IA #: 2447 FILE NUMBER: 900010.11 GLOBAL ROOT: AUPNVIMM( DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2447 ID: AUPNVIMM( GLOBAL REFERENCE: AUPNVIMM(D0,0) FIELD NUMBER: .01 FIELD NAME: IMMUNIZATION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Immunization name field. GLOBAL DESCRIPTION: Zeroeth node. GENERAL DESCRIPTION: V IMMUNIZATION file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281144 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2448 IA #: 2448 FILE NUMBER: 9000010.16 GLOBAL ROOT: AUPNVPED( DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2448 ID: AUPNVPED( GLOBAL REFERENCE: AUPNVPED(D0,0) FIELD NUMBER: .01 FIELD NAME: TOPIC LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Patient education name field. GLOBAL DESCRIPTION: Zeroeth node. GENERAL DESCRIPTION: V PATIENT ED file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281144 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2449 IA #: 2449 FILE NUMBER: 9000010.12 GLOBAL ROOT: AUPNVSK( DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2449 ID: AUPNVSK( GLOBAL REFERENCE: AUPNVSK(D0,0) FIELD NUMBER: .01 FIELD NAME: SKIN TEST LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Skin test name field. GLOBAL DESCRIPTION: Zeroeth node. GENERAL DESCRIPTION: V SKIN TEST file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281144 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2450 IA #: 2450 FILE NUMBER: 9000010.15 GLOBAL ROOT: AUPNVTRT( DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2450 ID: AUPNVTRT( GLOBAL REFERENCE: AUPNVTRT(D0,0) FIELD NUMBER: .01 FIELD NAME: TREATMENT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: PATIENT NAME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: HOW MANY LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: PROVIDER NARRATIVE LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: Zeroeth node. GLOBAL REFERENCE: AUPNVTRT(AA GLOBAL DESCRIPTION: 'AA' xref. GLOBAL REFERENCE: AUPNVTRT(B GLOBAL DESCRIPTION: 'B' xref. GLOBAL REFERENCE: AUPNVTRT(C GLOBAL DESCRIPTION: 'C' xref. GENERAL DESCRIPTION: V TREATMENT file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 42220153 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 2451 IA #: 2451 FILE NUMBER: 9999999.09 GLOBAL ROOT: AUTTEDT( DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2451 ID: AUTTEDT( GLOBAL REFERENCE: AUTTEDT(D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Education topic name field. GLOBAL DESCRIPTION: Zeroeth node. GENERAL DESCRIPTION: EDUCATION TOPICS file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281144 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2452 IA #: 2452 FILE NUMBER: 9999999.15 GLOBAL ROOT: AUTTEXAM( DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2452 ID: AUTTEXAM( GLOBAL REFERENCE: AUTTEXAM(D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Exam name field. GLOBAL DESCRIPTION: Zeroeth node. GENERAL DESCRIPTION: EXAM file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281144 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2453 IA #: 2453 FILE NUMBER: 9999999.64 GLOBAL ROOT: AUTTHF( DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2453 ID: AUTTHF( GLOBAL REFERENCE: AUTTHF(D0,0) FIELD NUMBER: .01 FIELD NAME: FACTOR LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Health factor name field. GLOBAL DESCRIPTION: Zeroeth node. GENERAL DESCRIPTION: HEALTH FACTORS file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281144 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham NUMBER: 2454 IA #: 2454 FILE NUMBER: 9999999.14 GLOBAL ROOT: AUTTIMM( DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2454 ID: AUTTIMM( GLOBAL REFERENCE: AUTTIMM(D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Immunization name field. GLOBAL DESCRIPTION: Zeroeth node. GENERAL DESCRIPTION: IMMUNIZATION file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281144 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT SUBSCRIBING PACKAGE: CLINICAL REMINDERS NUMBER: 2455 IA #: 2455 FILE NUMBER: 9999999.28 GLOBAL ROOT: AUTTSK( DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2455 ID: AUTTSK( GLOBAL REFERENCE: AUTTSK(D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Skin test name field. GLOBAL DESCRIPTION: Zeroeth node. GENERAL DESCRIPTION: SKIN TEST file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281144 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: CLINICAL REMINDERS NUMBER: 2456 IA #: 2456 FILE NUMBER: 9999999.17 GLOBAL ROOT: AUTTTRT( DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2456 ID: AUTTTRT( GLOBAL REFERENCE: AUTTTRT(D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Treatment name field. GLOBAL DESCRIPTION: Zeroeth node. GENERAL DESCRIPTION: TREATMENT file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281144 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2457 IA #: 2457 FILE NUMBER: 627.8 GLOBAL ROOT: YSD(627.8, DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: MENTAL HEALTH CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2457 ID: YSD(627.8, GLOBAL REFERENCE: YSD(627.8,D0,60) FIELD NUMBER: 65 FIELD NAME: AXIS 5 LOCATION: 60;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Contains GAF score. GLOBAL DESCRIPTION: Data node where GAF score is stored. GLOBAL REFERENCE: YSD(627.8,'AX5', GLOBAL DESCRIPTION: 'AX5' crossreference. GENERAL DESCRIPTION: DIAGNOSTIC RESULTS - MENTAL HEALTH file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281143 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany DBA Comments: Richard Curtis is a VistA Maintenance developer working on SD*5.3*576. In the process of getting the package ready for release, an old ICR was found that should have been set to Active for a previous patch release. The ICR was changed to Active so the new patch would not be held up. No history is available about what the last update was for this ICR. DATE ACTIVATED: JUN 04, 2012 DATE/TIME EDITED: JUN 04, 2012@14:12 ACTION: APPROVED AT THE REQUEST OF: CURTIS,RICHARD WITH CONCURRENCE OF: BEUSCHEL,GARY NUMBER: 2458 IA #: 2458 FILE NUMBER: 357.69 GLOBAL ROOT: IBE(357.69, DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: AUTOMATED INFO COLLECTION SYS CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2458 ID: IBE(357.69, GLOBAL REFERENCE: IBE(357.69,'B', GLOBAL DESCRIPTION: 'B' crossreference. GENERAL DESCRIPTION: TYPE OF VISIT file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281138 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2460 IA #: 2460 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2460 ORIGINAL NUMBER: 2460 ID: DPT( GLOBAL REFERENCE: DPT(D0,.322) FIELD NUMBER: .322013 FIELD NAME: ENVIRONMENTAL CONTAMINANTS? LOCATION: .322;13 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Environmental contaminants exposure indicator. GLOBAL DESCRIPTION: Data node. GENERAL DESCRIPTION: PATIENT file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281136 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2461 IA #: 2461 FILE NUMBER: 408.32 GLOBAL ROOT: DG(408.32, DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2461 ORIGINAL NUMBER: 2460 ID: DG(408.32, GLOBAL REFERENCE: DG(408.32,'C' GLOBAL DESCRIPTION: 'C' cross reference. GENERAL DESCRIPTION: MEANS TEST STATUS file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281136 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2462 IA #: 2462 FILE NUMBER: 27.11 GLOBAL ROOT: DGEN(27.11, DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2462 ORIGINAL NUMBER: 2460 ID: DGEN(27.11, GLOBAL REFERENCE: DGEN(27.11,D0,0) FIELD NUMBER: .01 FIELD NAME: ENROLLMENT DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Enrollment date field. FIELD NUMBER: .03 FIELD NAME: SOURCE OF ENROLLMENT LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Source of enrollment field. FIELD NUMBER: .04 FIELD NAME: ENROLLMENT STATUS LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Enrollment status field. FIELD NUMBER: .06 FIELD NAME: FACILITY RECEIVED LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Facility received field. FIELD NUMBER: .07 FIELD NAME: ENROLLMENT PRIORITY LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Enrollment priority field. FIELD NUMBER: .08 FIELD NAME: EFFECTIVE DATE LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Effective date field. GLOBAL DESCRIPTION: Zeroeth node. GLOBAL REFERENCE: DGEN(27.11,'C', GLOBAL DESCRIPTION: 'C' crossreference. GENERAL DESCRIPTION: PATIENT ENROLLMENT file access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281136 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT SUBSCRIBING PACKAGE: PATIENT REPRESENTATIVE SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 8/3/12-MM: VPS Kiosk added as a subscriber for VPS*1*1. They will be using FileMan ($$GET1^DIQ(27.11,X_",",.04,"E")) to retreive the Enrollment Status field. DATE/TIME EDITED: AUG 03, 2012@14:42 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LAM,ESTELLA WITH CONCURRENCE OF: KOPECKY,STEVE NUMBER: 2463 IA #: 2463 DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTU NAME: DBIA2463 ORIGINAL NUMBER: 2460 ID: DGMTU GENERAL DESCRIPTION: Means Test utility routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281136 COMPONENT/ENTRY POINT: $$LST~DGMTU COMPONENT DESCRIPTION: Last Means Test information. Extrinsic function, the output is: Annual Means Test ien ^ date of test ^ status name ^ status code VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: patient ifn VARIABLES: DGDT TYPE: Input VARIABLES DESCRIPTION: Date/time to use as effective date for last means test status. SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2464 IA #: 2464 DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGPMSTAT NAME: DBIA2464 ORIGINAL NUMBER: 2460 ID: DGPMSTAT GENERAL DESCRIPTION: Inpatient ward location utility. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281136 COMPONENT/ENTRY POINT: ~DGPMSTAT COMPONENT DESCRIPTION: Provides patient ward location for a given date/time. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: patient ifn VARIABLES: DGT TYPE: Input VARIABLES DESCRIPTION: Date to check if patient was an inpatient. VARIABLES: DGA1 TYPE: Output VARIABLES DESCRIPTION: Corresponding admission movement ifn in ^DGPM VARIABLES: DG1 TYPE: Output VARIABLES DESCRIPTION: ward ^ room-bed ^ movement type VARIABLES: DGXFR0 TYPE: Output VARIABLES DESCRIPTION: Zeroeth node of last transfer movement for admission. SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2465 IA #: 2465 DATE CREATED: JUL 01, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGPMUTL NAME: DBIA2465 ORIGINAL NUMBER: 2460 ID: DGPMUTL GENERAL DESCRIPTION: Provides ward location for a given inpatient movement. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27281136 COMPONENT/ENTRY POINT: WARD~DGPMUTL COMPONENT DESCRIPTION: Provides ward location for a given inpatient movement. VARIABLES: D0 TYPE: Input VARIABLES DESCRIPTION: Discharge movement ifn in ^DGPM VARIABLES: X TYPE: Output VARIABLES DESCRIPTION: Ward name for ward at discharge SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2467 IA #: 2467 DATE CREATED: JUL 06, 1998 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORX8 NAME: $$OI, $$VALUE ID: ORX8 CREATOR: BUECHLER,MELANIE K GENERAL DESCRIPTION: This controlled subscription agreement will allow various functions to be called in routine ORX8. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27394204 KEYWORDS: OI KEYWORDS: VALUE COMPONENT/ENTRY POINT: $$OI COMPONENT DESCRIPTION: Returns the orderable item for given ORDER file IEN in the format ien^name^package id. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: The IEN of the ORDER file (#100). VARIABLES: Result TYPE: Output VARIABLES DESCRIPTION: The result of the extrinsic function is returned in the format: Orderable Item IEN^Orderable Item Name^Package ID COMPONENT/ENTRY POINT: $$VALUE COMPONENT DESCRIPTION: Returns a single value from the content of an order. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: The IEN of the ORDER file (#100). VARIABLES: ID TYPE: Input VARIABLES DESCRIPTION: The free text identifier assigned to the prompt in the ID field of the Order Dialog file #101.41 (and stored with the value in the Responses multiple of the Orders file #100). VARIABLES: INST TYPE: Input VARIABLES DESCRIPTION: An integer, the instance of the value to return (default=1). VARIABLES: FORMAT TYPE: Input VARIABLES DESCRIPTION: A flag to indicate the desired form of the value; "E" will return the external form, or null for the default internal format. VARIABLES: Result TYPE: Output VARIABLES DESCRIPTION: The result of this extrinsic function. SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK SUBSCRIBING PACKAGE: HEALTH SUMMARY SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: Effective with VPR*1*0. DBA Comments: 08/02/13 DT: Add VPR as subscriber, effective with VPR*1*0. Melanie Buechler represents OR and VPR. DATE ACTIVATED: DEC 20, 2009 DATE/TIME EDITED: MAY 25, 2010@15:16 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: BUECHLER,MELANIE DATE/TIME EDITED: SEP 16, 2010@11:02 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE DATE/TIME EDITED: JAN 19, 2011@08:48 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SILVERMAN,ROBERT DATE/TIME EDITED: AUG 02, 2013@13:07 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: BUECHLER,MELANIE REMINDER: MAY 25, 2010 NUMBER: 2469 IA #: 2469 FILE NUMBER: 3.5 GLOBAL ROOT: %ZIS(1 DATE CREATED: JUL 07, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: LAB ACCESSING FIELD LAB LABEL PRINTER IN DEVICE FILE ID: %ZIS(1 GLOBAL REFERENCE: %ZIS(1,IOS,101 FIELD NUMBER: 101 FIELD NAME: LAB LABEL PRINTER LOCATION: 101;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field stores a default lab printer for a specific device which overrides the Lab's package-wide default printer LABLABEL. GENERAL DESCRIPTION: Lab requests permission to access the LAB LABEL PRINTER field (#101) in the Kernel DEVICE (#3.5) file. Field is used to determine if user has a Lab label printer associated with the user's home device in the DEVICE (#3.5) file. If an association exists then this device is used as the default prompt for label printer instead of the standard LABLABEL device. Code to access this field is as follows: I $G(IOS) D ; Check if label device assigned to this user's HOME Device . S X=$$GET1^DIQ(3.5,IOS_",",101,"E") . I $L(X) S %ZIS("B")=X STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27395558 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 2474 IA #: 2474 FILE NUMBER: 50 GLOBAL ROOT: PSDRUG( DATE CREATED: JUL 09, 1998 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2474 ID: PSDRUG( GLOBAL REFERENCE: PSDRUG(D0,0) FIELD NUMBER: .01 FIELD NAME: GENERIC NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSDRUG(D0,'ND') FIELD NUMBER: 20 FIELD NAME: NATIONAL DRUG FILE ENTRY LOCATION: ND;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 21 FIELD NAME: VA PRODUCT NAME LOCATION: ND;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 25 FIELD NAME: NATIONAL DRUG CLASS LOCATION: ND;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: VA CLASSIFICATION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 27404469 SUBSCRIBING PACKAGE: DIETETICS ISC: Hines NUMBER: 2476 IA #: 2476 DATE CREATED: JUL 09, 1998 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOCMOP NAME: PSOCMOP ID: PSOCMOP GENERAL DESCRIPTION: This integration agreement between the Consolidated Mail Outpatient Pharmacy (CMOP) package with the Outpatient Pharmacy V 7.0 (OP) package allows CMOP to call the routine PSOCMOP (used exclusively for CMOP purposes) at line tag TEST from routine PSXRESUB. This call allows an Rx fill that has been rejected by a CMOP host facility to be resubmitted to that facility a single time. Two input variables are passed to PSOCMOP: PPL = IEN of Rx in Prescription file (#52) ZD(IEN of Rx in 52) = Current Date/Time One output variable is returned: PPL = If contains a value indicates that Rx was not eligible for CMOP resubmission. If null, then Rx has been placed in suspense for CMOP transmission. CMOP Routine OP Routine Variables in Variables out PSXRESUB TEST^PSOCMOP PPL PPL ZD(IEN 52) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27409906 COMPONENT/ENTRY POINT: TEST VARIABLES: PPL TYPE: Both VARIABLES DESCRIPTION: PPL on input contains the IEN of an Rx in file #52. PPL on output may contain the IEN or may be Null. VARIABLES: ZD(IEN) TYPE: Input VARIABLES DESCRIPTION: ZD(IEN 52) is set to the current Date/Time. COMPONENT/ENTRY POINT: $$CMPRXTYP(DA) VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: The IEN of the Rx in RX SUSPENSE file 52.5 VARIABLES: $$CMPRXTYP TYPE: Output VARIABLES DESCRIPTION: 'C' for Controlled Substance (CS) 'N' for Non-CS SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 2477 IA #: 2477 DATE CREATED: JUL 14, 1998 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOLBL NAME: DBIA2477 ID: PSOLBL STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34911350 COMPONENT/ENTRY POINT: DQ COMPONENT DESCRIPTION: This entry point is called by the CMOP package to pass the internal entry number of the Prescription file (#52) to the Outpatient Pharmacy software to print the prescription label. prescription label information. VARIABLES: PPL TYPE: Input VARIABLES DESCRIPTION: The input variable PPL, which contains the internal entry number from the Prescription file (#52), is passed to PSOLBL. No data is returned to the OP package. COMPONENT/ENTRY POINT: IBCP COMPONENT DESCRIPTION: This entry point is called once for each DFN and it "helps determine" the copay status that will print on the CMOP form. If the patient is income exempt or 100% service connected, it will return a 0 for not billable. ("NO COPAY"). Additional checks for other exemptions are done following the call to determine the copay status if the value returned is a 1 or a 2. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient VistA ID VARIABLES: PSOSITE TYPE: Input VARIABLES DESCRIPTION: Pointer to Pharmacy Site File (#59) VARIABLES: PSOLBLCP TYPE: Output VARIABLES DESCRIPTION: 0 -- NOT BILLABLE 1 -- BILLABLE 2 -- ADDITIONAL DATA NEEDED SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 2479 IA #: 2479 FILE NUMBER: 74 GLOBAL ROOT: RARPT DATE CREATED: JUL 14, 1998 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: RAD/NUC MED REPORTS FILE (#74) ID: RARPT GLOBAL REFERENCE: RARPT(D0,0) FIELD NUMBER: .01 FIELD NAME: DAY-CASE# LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 5 FIELD NAME: REPORT STATUS LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: EXAM DATE/TIME LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 9 FIELD NAME: VERIFYING PHYSICIAN LOCATION: 0;9 ACCESS: Read w/Fileman GLOBAL REFERENCE: RARPT(D0,H) FIELD NUMBER: 400 FIELD NAME: CLINICAL HISTORY LOCATION: H ACCESS: Read w/Fileman FIELD DESCRIPTION: This is a word-processing field. GLOBAL REFERENCE: RARPT(D0,I) FIELD NUMBER: 300 FIELD NAME: IMPRESSION TEXT LOCATION: I ACCESS: Read w/Fileman FIELD DESCRIPTION: This is a word-processing field. GLOBAL REFERENCE: RARPT(D0,R) FIELD NUMBER: 200 FIELD NAME: REPORT TEXT LOCATION: R ACCESS: Read w/Fileman FIELD DESCRIPTION: This is a word-processing field. GLOBAL REFERENCE: RARPT(D0,ERR,D1,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME OF RPT SAVE LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The Women Veterans Health (WVH) package requests permission to read with FileMan an entire RAD/NUC MED REPORTS file (#74) entry and to display certain Radiology/Nuclear Medicine report information concerning mammograms and breast ultrasound exams to the WVH users. The following fields are computed and have no global location: Field # Field Name ------- ---------- 102 PROCEDURE 104 CATEGORY OF EXAM 106 WARD 107 SERVICE 108 PRINCIPAL CLINIC 109 CONTRACT/SHARING SOURCE 112 PRIMARY INTERPRETING RESIDENT 113 PRIMARY DIAGNOSTIC CODE 114 REQUESTING PHYSICIAN 115 PRIMARY INTERPRETING STAFF 116 COMPLICATION STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27757510 SUBSCRIBING PACKAGE: WOMEN'S HEALTH ISC: Hines SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING DETAILS: ADDED 8/11/2010 DBA Comments: JSH 2006-11-05/ Added SCI&D as subscriber as per Jeff Swesky/SCID and Selina Mo/Radiology. DATE/TIME EDITED: NOV 06, 2006@17:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SWESKY,JEFF WITH CONCURRENCE OF: MO,SELINA DATE/TIME EDITED: AUG 11, 2010@14:29 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CEBELINSKI,GREG NUMBER: 2480 IA #: 2480 FILE NUMBER: 70 GLOBAL ROOT: RADPT DATE CREATED: JUL 14, 1998 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: RAD/NM PATIENT FILE (#70) ID: RADPT CREATOR: TRAXLER,FRANK GLOBAL REFERENCE: RADPT( FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: RADPT(D0,DT, FIELD NUMBER: .01 FIELD NAME: EXAM DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: RADPT(D0,DT,D1,P, FIELD NUMBER: .01 FIELD NAME: CASE NUMBER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: PROCEDURE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 8 FIELD NAME: PRINCIPAL CLINIC LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 13 FIELD NAME: PRIMARY DIAGNOSTIC CODE LOCATION: 0;13 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 14 FIELD NAME: REQUESTING PHYSICIAN LOCATION: 0;14 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 26 FIELD NAME: CREDIT METHOD LOCATION: 0;26 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 400 FIELD NAME: CLINICAL HISTORY FOR EXAM LOCATION: H;wp ACCESS: Read w/Fileman FIELD NUMBER: 32 FIELD NAME: PREGNANCY SCREEN LOCATION: 0;32 ACCESS: Read w/Fileman FIELD NUMBER: 11 FIELD NAME: IMAGING ORDER LOCATION: 0;11 ACCESS: Read w/Fileman FIELD NUMBER: 27 FIELD NAME: VISIT LOCATION: 0;27 ACCESS: Read w/Fileman GLOBAL REFERENCE: RADPT(D0,DT,D1,P,D2,M, FIELD NUMBER: .01 FIELD NAME: MODIFIERS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: RADPT('ADC',DATE-CASE,D1,D2,D3) GLOBAL DESCRIPTION: The ADC cross-reference identifies the date and case number of the Radiology exam. It is in the following format: ^RADPT("ADC",DATE-CASE#,DFN,INVERSE DATE/TIME,INTERNAL ENTRY NUMBER) for example: ^RADPT("ADC","121196-73",18,7038788.8783,1) GLOBAL REFERENCE: RADPT(D0,DT,D1,P,D2,PCOMM, FIELD NUMBER: 80 FIELD NAME: PREGNANCY SCREEN COMMENT LOCATION: PCOMM;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The Women Veterans Health (WVH) package requests permission to view the following fields from the RAD/NUC MED PATIENT file (#70): [Modified 5/26/2009 to include Pregnancy Screen,Pregnancy Screen Comment and Imaging Order.] [Modified 08/04/2011 to include read w/FileMan access to the VISIT field (70.03;27). The request was made by AViVA (VPR).] STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27757516 KEYWORDS: VPR KEYWORDS: AViVA KEYWORDS: RA VPR KEYWORDS: RA AViVA KEYWORDS: RA WV KEYWORDS: WV SUBSCRIBING PACKAGE: WOMEN'S HEALTH ISC: Hines SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING PACKAGE: DSS EXTRACTS SUBSCRIBING DETAILS: 4/17/14-DSS added as a subscriber to reference the "ADC" cross reference. DBA Comments: 5/24/12-Activated ICR with VPR as a subscriber and new field in ICR - Visit (#27). 4/17/14-MM: Added DSS Extracts as a subscriber to ICR #2480. They are requesting access to the RADPT("ADC" cross reference for ECX*3.0*149. Greg Cebelinski provided concurrence. DATE ACTIVATED: MAY 24, 2012 DATE/TIME EDITED: MAY 26, 2009@13:17 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: TRAXLER,FRANK DATE/TIME EDITED: MAY 27, 2009@10:11 ACTION: APPROVED AT THE REQUEST OF: TRAXLER,FRANK WITH CONCURRENCE OF: CEBELINSKI,GREG DATE/TIME EDITED: AUG 03, 2011@14:43 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CEBELINSKI,GREG DATE/TIME EDITED: MAY 24, 2012@16:11 ACTION: APPROVED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: CEBELINSKI,GREG DATE/TIME EDITED: APR 17, 2014@09:42 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: NABER,DAVE WITH CONCURRENCE OF: CEBELINSKI,GREG NUMBER: 2481 IA #: 2481 FILE NUMBER: 71 GLOBAL ROOT: RAMIS(71, DATE CREATED: JUL 14, 1998 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: RAD/NUC MED PROCEDURES (#71) ID: RAMIS(71, GLOBAL REFERENCE: RAMIS(71,D0,0) FIELD NUMBER: 9 FIELD NAME: CPT CODE LOCATION: 0;9 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The Women Veterans Health (WVH) package requests permission to view the CPT Code associated with a Radiology/NM procedure to determine if the procedure is a mammogram or breast ultrasound procedure. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27757465 SUBSCRIBING PACKAGE: WOMEN'S HEALTH ISC: Hines NUMBER: 2482 IA #: 2482 FILE NUMBER: 71.2 GLOBAL ROOT: RAMIS(71.2, DATE CREATED: JUL 14, 1998 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PROCEDURE MODIFIERS (#71.2) ID: RAMIS(71.2, GLOBAL REFERENCE: RAMIS(71.2,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The Women Veterans Health (WVH) package requests permission to view the NAME field of the PROCEDURE MODIFIERS file (71.2) to determine which modifiers were used for a Radiology procedure. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27757504 SUBSCRIBING PACKAGE: WOMEN'S HEALTH ISC: Hines NUMBER: 2483 IA #: 2483 FILE NUMBER: 2 GLOBAL ROOT: DPT DATE CREATED: JUL 15, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: FILE 2 IA for WVH ID: DPT GLOBAL REFERENCE: DPT(D0,.13) FIELD NUMBER: .131 FIELD NAME: PHONE NUMBER [RESIDENCE] LOCATION: 13;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: DPT(D0,.11) FIELD NUMBER: .111 FIELD NAME: STREET ADDRESS [LINE 1] LOCATION: .11;1 ACCESS: Read w/Fileman FIELD NUMBER: .114 FIELD NAME: CITY LOCATION: .11;4 ACCESS: Read w/Fileman FIELD NUMBER: .115 FIELD NAME: STATE LOCATION: .11;5 ACCESS: Read w/Fileman FIELD NUMBER: .116 FIELD NAME: ZIP CODE LOCATION: .11;6 ACCESS: Read w/Fileman GLOBAL REFERENCE: DPT(D0,VET) FIELD NUMBER: 1901 FIELD NAME: VETERAN (Y/N)? LOCATION: VET;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The Women Veterans Health package would like to view the following fields in the Patient File (#2): STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27750930 SUBSCRIBING PACKAGE: WOMEN'S HEALTH ISC: Hines NUMBER: 2484 IA #: 2484 FILE NUMBER: 78.3 GLOBAL ROOT: RA(78.3, DATE CREATED: JUL 15, 1998 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DIAGNOSTIC CODES (78.3) ID: RA(78.3, GLOBAL REFERENCE: RA(78.3 FIELD NUMBER: .01 FIELD NAME: DIAGNOSTIC CODE LOCATION: 0;1 ACCESS: Pointed to GENERAL DESCRIPTION: The Women Veterans Health (WVH) package requests permission to point to the DIAGNOSTIC CODES (78.3) file so that the WV RESULTS/DIAGNOSIS file (790.31) file entries can be associated with the Radiology diagnostic codes. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27757494 SUBSCRIBING PACKAGE: WOMEN'S HEALTH ISC: Hines NUMBER: 2485 IA #: 2485 DATE CREATED: JUL 17, 1998 CUSTODIAL PACKAGE: FEE BASIS CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: FBHLZFE NAME: DBIA2485 ID: FBHLZFE GENERAL DESCRIPTION: This API builds the ZFE HL7 segments for a specified veteran. These segments contain FEE Authorization data. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27488317 COMPONENT/ENTRY POINT: EN(DFN,FBSTR,FBCUT) COMPONENT DESCRIPTION: Returns array of ZFE segments containing FEE BASIS Authorization data for a veteran. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: internal entry number of the PATIENT (#2) file VARIABLES: FBSTR TYPE: Input VARIABLES DESCRIPTION: (Optional) Comma delimited sting of requested fields. DEFAULT: "1,2,3,4,5" (returns all fields). VARIABLES: FBCUT TYPE: Input VARIABLES DESCRIPTION: (Optional) Cutoff date (fileman format). Default: "2961001" (Oct 1, 1996). Authorizations with a TO DATE prior to the cutoff will not be considered. VARIABLES: HLFS TYPE: Input VARIABLES DESCRIPTION: HL7 field separator that should be used in the segment. VARIABLES: HLQ TYPE: Input VARIABLES DESCRIPTION: HL7 null field value. VARIABLES: FBZFE(I) TYPE: Output VARIABLES DESCRIPTION: An array of string(s) forming the ZFE segments for the patient's FEE authorizations that meet the criteria. (OR Undefined if no authorizations meet criteria.) Note: Only the latest authorization for each group is returned (where group is FEE PROGRAM + TREATMENT TYPE). SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany SUBSCRIBING DETAILS: The IVM package generates a daily HL7 transmission (ORUZ07) to HEC. This transmission will include ZFE segments that are generated by the FEE BASIS routine. NUMBER: 2486 IA #: 2486 DATE CREATED: JUL 20, 1998 CUSTODIAL PACKAGE: INCOME VERIFICATION MATCH CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IVMPLOG NAME: LOGGING PATIENTS FOR THE NIGHTLY TRANSMISSION ID: IVMPLOG STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27502761 COMPONENT/ENTRY POINT: EVENT(DFN) COMPONENT DESCRIPTION: This tag is used to log a patient into the IVM PATIENT file for inclusion in the nightly IVM Full Data Transmission. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The patient DFN. This is the internal entry number of the patient record in the Patient file. SUBSCRIBING PACKAGE: FEE BASIS ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 2487 IA #: 2487 FILE NUMBER: 3.8 GLOBAL ROOT: XMB(3.8,0 DATE CREATED: JUL 28, 1998 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: CMOP MAILGROUP ACCESS ID: XMB(3.8,0 GENERAL DESCRIPTION: The Consolidated Mail Outpatient Pharmacy (CMOP) package requires access to the "B" cross reference in the Mailgroup (3.8) File. This access will be limited to CMOP V 2.0 software and the routine PSXPOST. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27500276 SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 2488 IA #: 2488 FILE NUMBER: 772 GLOBAL ROOT: HL(772 DATE CREATED: AUG 04, 1998 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: IA2488 ID: HL(772 GLOBAL REFERENCE: HL(772,DA,0) FIELD NUMBER: 20 FIELD NAME: STATUS LOCATION: P;0 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Lab requests a DBIA from HL7 for the following reference: ^HL(772,176674,"P") = 4^2980419.101639^EventProtocol not found^13 Using the code: S LRSTATUS=+$G(^HL(772,LRMID,"P")) I plan to use this during the acknowledgement process of NCH messages from Austin. REFERENCE FORUM MESSAGE: 27535419 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27535419 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 2491 IA #: 2491 FILE NUMBER: 130 GLOBAL ROOT: SRF( DATE CREATED: AUG 10, 1998 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA 16B ID: SRF( GLOBAL REFERENCE: SRF( FIELD NUMBER: .22 FIELD NAME: TIME OPERATION BEGINS LOCATION: .2;2 ACCESS: Read w/Fileman FIELD NUMBER: .23 FIELD NAME: TIME OPERATION ENDS LOCATION: .2;3 ACCESS: Read w/Fileman FIELD NUMBER: .205 FIELD NAME: TIME PAT IN OR LOCATION: .2;10 ACCESS: Read w/Fileman FIELD NUMBER: .31 FIELD NAME: PRINC ANESTHETIST LOCATION: .3;1 ACCESS: Read w/Fileman FIELD NUMBER: 17 FIELD NAME: CANCEL DATE LOCATION: 30;1 ACCESS: Read w/Fileman FIELD NUMBER: 10 FIELD NAME: SCHEDULED START DATE LOCATION: 31;4 ACCESS: Read w/Fileman FIELD NUMBER: 66 FIELD NAME: PRIN DIAGNOSIS CODE LOCATION: 34;2 ACCESS: Read w/Fileman FIELD NUMBER: 118 FIELD NAME: NON-OR PROCEDURE LOCATION: NON;1 ACCESS: Read w/Fileman FIELD NUMBER: 120 FIELD NAME: DATE OF PROCEDURE LOCATION: NON;3 ACCESS: Read w/Fileman FIELD NUMBER: 123 FIELD NAME: PROVIDER LOCATION: NON;6 ACCESS: Read w/Fileman FIELD NUMBER: 134 FIELD NAME: ATTEND PROVIDER LOCATION: NON;7 ACCESS: Read w/Fileman FIELD NUMBER: 125 FIELD NAME: MEDICAL SPECIALTY LOCATION: NON;8 ACCESS: Read w/Fileman FIELD NUMBER: 26 FIELD NAME: PRINCIPLE PROCEDURE LOCATION: OP;1 ACCESS: Read w/Fileman FIELD NUMBER: 36 FIELD NAME: REQUESTED LOCATION: REQ;1 ACCESS: Read w/Fileman FIELD NUMBER: 33 FIELD NAME: PRINCIPAL DIAGNOSIS LOCATION: 33;2 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,12, FIELD NUMBER: .01 FIELD NAME: SURGEON'S DICTATION LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,38, FIELD NUMBER: .01 FIELD NAME: OPERATIVE FINDINGS LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,40, FIELD NUMBER: .01 FIELD NAME: INDICATIONS FOR OPERATIONS LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,'OPMOD', FIELD NUMBER: .01 FIELD NAME: PRIN. PROCEDURE CPT MODIFIER LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: SRF(D0,13,D1,'MOD', FIELD NUMBER: .01 FIELD NAME: OTHER PROCEDURE CPT MODIFIER LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: This amends DBIA #16 to include file reference used for OP and NON-OP Health Summary. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31005651 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 2492 IA #: 2492 FILE NUMBER: 45 GLOBAL ROOT: DGPT( DATE CREATED: AUG 17, 1998 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2492 ID: DGPT( GLOBAL REFERENCE: DGPT( FIELD NUMBER: 2 FIELD NAME: ADMISSION DATE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: CIRN needs read access to ^DGPT to calculate the Master of Record Score Global Reference: ^DGPT('B', The "B" cross-reference is used to find a specific PTF record for a patient. The RGVCCMR2 routine orders through the 'B' cross-reference $O(^DGPT("B",+DFN,NXPTF to order through the ^DGPT(NXPTF,0 for admission dates. It compares the admission dates to current year, and past two years to calculate the CMOR score. ^DGPT(D0,'S',0 Direct Read orders through ^DGPT(NXPTF,"S",0 for the surgury/procedure dates. ^DGPT(D0,0 2 Admission Date 0;2 Direct Global Read CIRN is looking for patient(s) activity over a three-year period. STATUS: Active MAIL MESSAGE: 27725651 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2494 IA #: 2494 FILE NUMBER: 50 GLOBAL ROOT: DD(50,0,ID DATE CREATED: AUG 11, 1998 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Supported TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA-2494 PDM-Delete bad field global ID: DD(50,0,ID GLOBAL REFERENCE: DD(50,0,ID FIELD NUMBER: 534016 LOCATION: DRUG FILE (#50) ACCESS: Direct Global Write & w/Fileman GENERAL DESCRIPTION: To resolve NOIS # EKH-0798-41058, we are inserting a line of code to delete the impartial field data found in File #50. We believe that the ^DD(50,0,"ID",534016) global is a local site-specific field. We do not have a zero node that identifies the field name. We are adding a line of code to routine PSSPCH13 that checks for the zero node. If not there, it will delete the data related to the field number 534016. Example. I '$D(^DD(50,534016)) K ^DD(50,0,"ID",534016). This change is included in patch PSS*1*13. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27656954 EDITOR: BLOCKER,DAVE NUMBER: 2495 IA #: 2495 FILE NUMBER: 7 GLOBAL ROOT: DIC(7, DATE CREATED: AUG 11, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2495 ID: DIC(7, GLOBAL REFERENCE: DIC(7, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: Abbrev. TITLE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Pharmacy Benefits Management needs to extract the name and abbrev from the Provider Class File #7. The provider pointer (#200) will be obtained from various pharmacy files. The new person provider class field #53.5 will be then be used to extract the name and abbrev from the Provider Class File. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27657474 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 2496 IA #: 2496 FILE NUMBER: 4.3 GLOBAL ROOT: XMB(1, DATE CREATED: AUG 11, 1998 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: MAILMAN SITE PARAMETERS ID: XMB(1, CREATOR: BEUSCHEL,GARY GLOBAL REFERENCE: XMB(1,D0,'NETWORK-LIMIT') FIELD NUMBER: 8.3 FIELD NAME: NETWORK - MAX LINES @ SEND TO LOCATION: NETWORK-LIMIT;1 ACCESS: Read w/Fileman FIELD NUMBER: 8.31 FIELD NAME: NETWORK - MAX LINES RECEIVE LOCATION: NETWORK-LIMIT;2 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Pharmacy Benefits Managment is an extract program. It will extract Pharmacy IV, Unit dose, prescription, Controlled substance and ward stock order information along with Procurement and a limited amount of laboratory data. The data will be sent via MailMan message to Pharmacy Benefits Management section at Hines and incorporated into their national database. These messages will be very long and we wanted to make sure that the PBM software 'honored' the sites wishes to limit their message line #. If we do not find a number in the NETWORK -MAX LINES @ SEND TO field, the program will limit the message to 10,000 lines. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27658203 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: Mental Health has permission to read both fields 8.3 and 8.31 with FileMan, to ensure that messages are under the send/receive line limits of particular sites. DBA Comments: 06/26/12 DT - Added Gary Beuschel as editor to add 81.3 and add Mental Health as a subscriber. Approved after Gary made edits and approval by Frank Traxler. DATE ACTIVATED: JUN 26, 2012 DATE/TIME EDITED: JUN 26, 2012@12:08 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: TRAXLER,FRANK WITH CONCURRENCE OF: BEUSHEL,GARY DATE/TIME EDITED: JUN 26, 2012@13:08 ACTION: APPROVED AT THE REQUEST OF: BEUSCHEL,GARY WITH CONCURRENCE OF: TRAXLER,FRANK NUMBER: 2497 IA #: 2497 FILE NUMBER: 55 GLOBAL ROOT: PS(55 DATE CREATED: AUG 12, 1998 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2497 ID: PS(55 GLOBAL REFERENCE: PS(55,'AUDS',X,D0,D1) GLOBAL DESCRIPTION: This cross reference is used to identify active unit dose orders for a specified reporting period and the patients for which the orders are written for. GLOBAL REFERENCE: PS(55,D0,5, FIELD NUMBER: .01 FIELD NAME: Order Number LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .5 FIELD NAME: Patient Name LOCATION: 0;15 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: Provider LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 68 FIELD NAME: Last ward LOCATION: 0;23 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: MED ROUTE LOCATION: 0;3 ACCESS: Read w/Fileman GLOBAL REFERENCE: PS(55,D0,5,D1,2) FIELD NUMBER: 26 FIELD NAME: Schedule LOCATION: 2;1 ACCESS: Read w/Fileman FIELD NUMBER: 10 FIELD NAME: Start date/time LOCATION: 2;2 ACCESS: Read w/Fileman FIELD NUMBER: 34 FIELD NAME: Stop date/time LOCATION: 2;4 ACCESS: Read w/Fileman FIELD NUMBER: 9 FIELD NAME: Original ward LOCATION: 2;10 ACCESS: Read w/Fileman GLOBAL REFERENCE: PS(55,D0,5,D1,1,D2,0) FIELD NUMBER: .01 FIELD NAME: Dispense drug LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .02 FIELD NAME: Units Per Dose LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: .03 FIELD NAME: Inactive Date LOCATION: 0;3 ACCESS: Read w/Fileman GLOBAL DESCRIPTION: Program will $O through the dispense drug multiple to identify all dispense drugs associated with a particular unit dose order. GLOBAL REFERENCE: PS(55,D0,5,D1,11,D2,0) FIELD NUMBER: .01 FIELD NAME: Dispense date/time LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: $O on the "B" x-ref is also covered, plus global reads on the subscripts after "B", FIELD NUMBER: .02 FIELD NAME: DISPENSE DRUG LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: .05 FIELD NAME: How LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: .03 FIELD NAME: AMOUNT LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: .04 FIELD NAME: COST LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: .06 FIELD NAME: USER LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: .07 FIELD NAME: WARD LOCATION: 0;7 ACCESS: Read w/Fileman FIELD NUMBER: .08 FIELD NAME: PROVIDER LOCATION: 0;8 ACCESS: Read w/Fileman GLOBAL DESCRIPTION: $O permitted through the dispense drug multiple. $D may be performed on ^PS(55,D0,5,D1,11,D2) GLOBAL REFERENCE: PS(55,D0,"IV", FIELD NUMBER: .01 FIELD NAME: Order Number LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .02 FIELD NAME: Start Date/time LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: .03 FIELD NAME: Stop date/time LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: .04 FIELD NAME: Type LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: 108 FIELD NAME: Intermittent Syring LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: .06 FIELD NAME: Provider LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: .08 FIELD NAME: Infusion rate LOCATION: 0;8 ACCESS: Read w/Fileman FIELD NUMBER: .09 FIELD NAME: Schedule LOCATION: 0;9 ACCESS: Read w/Fileman FIELD NUMBER: 104 FIELD NAME: Ward LOCATION: 0;22 ACCESS: Read w/Fileman FIELD NUMBER: 106 FIELD NAME: CHEMOTHERAPY TYPE LOCATION: 0;23 ACCESS: Read w/Fileman FIELD NUMBER: 132 FIELD NAME: MED ROUTE LOCATION: .2;3 ACCESS: Read w/Fileman FIELD NUMBER: .22 FIELD NAME: IV ROOM LOCATION: 2;2 ACCESS: Read w/Fileman GLOBAL REFERENCE: PS(55,D0,'IV',D1,AD,D2,0) FIELD NUMBER: .01 FIELD NAME: Additive LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .02 FIELD NAME: Strength LOCATION: 0;2 ACCESS: Read w/Fileman GLOBAL DESCRIPTION: Program will $O through the Additive multiple to identify all additives associated with an IV order. GLOBAL REFERENCE: PS(55,D0,'IV',D1,SOL,D2,0) FIELD NUMBER: .01 FIELD NAME: Solution LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: Volume LOCATION: 0;2 ACCESS: Read w/Fileman GLOBAL DESCRIPTION: The program will $O through the solution multiple to identify all solutions associate with an IV order. GLOBAL REFERENCE: PS(55,D0,'IV',D1,LAB,D2,0) FIELD NUMBER: 1 FIELD NAME: Date LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: Action LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: Labels LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 6 FIELD NAME: Daily Usage LOCATION: 0;7 ACCESS: Read w/Fileman GLOBAL DESCRIPTION: The program will $O through the label tracking multiple to identify dispensing occurrences within a specified time period. GLOBAL REFERENCE: PS(55,'AIVS',X,D0,D1) GLOBAL DESCRIPTION: The program will utilize the "AIVS" cross reference to identify active IV orders for a specific time period and the patients for which the orders are written for. GLOBAL REFERENCE: PS(55,'AUD',X,D0,D1) GLOBAL DESCRIPTION: The "AUD" x-ref is to identify active Unit Dose orders for a specific time period and patients for which the orders are written. GENERAL DESCRIPTION: This agreement will be retired on 12/31/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*101. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. All fields and x-refs in file 55 have global read access by the subscribing packages. This DBIA retirement only applies to non-pharmacy packages. Pharmacy packages are still allowed to utilize this agreement past the expiration date of December 31, 2006. Pharmacy Benefits Management extracts data from the following Pharmacy Patient File #55 fields. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 39376680 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES EDITOR: BLOCKER,DAVE NUMBER: 2498 IA #: 2498 FILE NUMBER: 59.4 GLOBAL ROOT: PS(59.4 DATE CREATED: AUG 12, 1998 CUSTODIAL PACKAGE: CONTROLLED SUBSTANCES CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2498 ID: PS(59.4 GLOBAL REFERENCE: PS(59.4,D0,0) FIELD NUMBER: .01 FIELD NAME: Name LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Pharmacy Benefits Managment will extract the inpatient name from the Inpatient Site file #59.4. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27664280 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 2499 IA #: 2499 FILE NUMBER: 59.5 GLOBAL ROOT: PS(59.5 DATE CREATED: AUG 12, 1998 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2499 ID: PS(59.5 GLOBAL REFERENCE: PS(59.5,D0,0) FIELD NUMBER: .02 FIELD NAME: Division LOCATION: 0;4 ACCESS: Read w/Fileman GLOBAL REFERENCE: PS(59.5,D0,1) FIELD NUMBER: .104 FIELD NAME: LVP'S GOOD FOR HOW MANY DAYS LOCATION: 1;4 ACCESS: Read w/Fileman FIELD NUMBER: .111 FIELD NAME: HYPERAL GOOD FOR HOW MANY DAYS LOCATION: 1;17 ACCESS: Read w/Fileman FIELD NUMBER: .112 FIELD NAME: PB'S GOOD FOR HOW MANY DAYS LOCATION: 1;18 ACCESS: Read w/Fileman GLOBAL REFERENCE: PS(59.5,D0,5) FIELD NUMBER: 17 FIELD NAME: SYRN'S GOOD FOR HOW MANY DAYS LOCATION: 5;1 ACCESS: Read w/Fileman FIELD NUMBER: 18 FIELD NAME: CHEMO'S GOOD FOR HOW MANY DAYS LOCATION: 5;2 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Pharmacy Benefits Management extracts the following fields from the IV Room file #59.5: .02 Division .104 LVP'S GOOD FOR HOW MANY DAYS .111 HYPERAL GOOD FOR HOW MANY DAYS .112 PB'S GOOD FOR HOW MANY DAYS 17 SYRN'S GOOD FOR HOW MANY DAYS 18 CHEMO'S GOOD FOR HOW MANY DAYS STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29439976 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 2500 IA #: 2500 DATE CREATED: AUG 12, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: %ZOSV NAME: DBIA 2500 ID: %ZOSV GENERAL DESCRIPTION: Requesting approval to use DOLRO^%ZOSV. This entry is in every Kernel %ZOSV and only requires the variable X as input as to where the user wants to store a list of the variables in the partition. This functionality is desired and it is located within the Kernel for each platform that Kernel runs on. Its use is requested so that seperate hardcoded routines for each platform do not have to be written to achieve the same functionality. This request is made in behalf of the Pharmacy Benefits Program (PSU) and McKinley Enterprises | WesTech Computer Group (BTW) who is coding PBM under contract with EDS through the VA - EDS Partnership. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27668701 COMPONENT/ENTRY POINT: DOLRO COMPONENT DESCRIPTION: Existing entry point providing a listing of partition variable names in a location that is user specified. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: The global or variable root of where the uses wishes to store the names of the partition variables. SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 2501 IA #: 2501 FILE NUMBER: 40.7 GLOBAL ROOT: DIC(40.7, DATE CREATED: AUG 17, 1998 CUSTODIAL PACKAGE: SCHEDULING USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2501 ID: DIC(40.7, GLOBAL REFERENCE: DIC(40.7,'C',105, GLOBAL DESCRIPTION: ^DIC(40.7,'C',105 Direct Read - IEN of XRAY Stop Code ^DIC(40.7,'C',108, Direct read - IEN of LAB Stop Code The xray and lab stop codes (^DIC(40.7,'C',105 and ^DIC(40.7,'C',108) are not counted to avoid duplication since lab & xray are counted separately. The RGPRPST routine does a Direct Read of ^DIC(40.7 and uses it with the fileman lookup routine ^DIC to set primary care clinics to file 991.8 PRIMARY CARE CLINIC STOPS field (#17) The subfield that points to file 40.7 is PRIMARY CARE CLINIC STOPS field (#.01). GLOBAL REFERENCE: DIC(40.7,'C',108, GLOBAL DESCRIPTION: Same as for DIC(40.7,'C',105, ... GLOBAL REFERENCE: DIC(40.7, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to GENERAL DESCRIPTION: CIRN needs read access to ^DIC(40.7,'C' to calculate the Master of Record Score STATUS: Active MAIL MESSAGE: 27588098 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2502 IA #: 2502 DATE CREATED: AUG 18, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXKMAIN NAME: DBIA2502 ID: PXKMAIN GENERAL DESCRIPTION: An integration agreement is needed with the PCE package for the Scheduling data conversion project. The PCE package's standard filer entrypoints require that all providers added to PCE for a visit have a valid provider class. The problem is that some of the encounters that the Scheduling conversion can convert will consist of old provider data where the provider class for the provider does not exist. As a result, many many providers will not be able to be converted with their visits/encounters because they do not have a valid provider class. Denis Eaton was consulted about this and he concluded the only way to store these old providers in PCE would be to pre-set the global array that PCE uses to file the data to what it would look like after all the edit checks were done, and call the filer directly. Since the affected provider data is old and its corresponding visit will be flagged as historical in PCE, there should not be a data integrity issue with storing a provider without a valid provider class. It also makes the conversion more consistent and complete. This exemption is requested specifically for filing the new provider data and would be a one-time exemption to be used only when new visits are created as a result of the conversion. All other data added to PCE via this project would flow through the normal PCE edits. The agreement would only exist for the life of the conversion. The array definition follows: ^TMP("PXK",$J,"SOR") = Source ien ^TMP("PXK",$J,"VST",1,0,"BEFORE") = the 0-node of the visit file ^TMP("PXK",$J,"VST",1,0,"AFTER") = the same as "BEFORE" ^TMP("PXK",$J,"VST",provider counter,"IEN") = "" ^TMP("PXK",$J,"PRV",provider counter,0,"BEFORE") = "" ^TMP("PXK",$J,"PRV",provider counter,0,"AFTER") = Provider id^DFN^Visit ien^P/S for primary/secondary ^TMP("PXK",$J,"PRV",provider counter,"IEN") = "" ^TMP("PXK",$J,"PRV",provider counter,"BEFORE") = "" ^TMP("PXK",$J,"PRV",provider counter,"AFTER") = ^Package ien^Source ien The entrypoint to call for the post-edit filer is EN1^PXKMAIN STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: DEC 31, 1999 MAIL MESSAGE: 27706886 COMPONENT/ENTRY POINT: EN1 VARIABLES: PXKNOEVT TYPE: Input VARIABLES DESCRIPTION: We need approval to set the variable PXKNOEVT before making the calls to EN1^PXKMAIN and $$DATA2PCE^PXAPI. Setting this variable prevents the PXK VISIT DATA EVENT driver protocol from being executed. Since the data is coming from Scheduling initially and it is old 'historical' information, there is no need to notify Scheduling when the encounter data has been added to the PCE database. Also, by not executing this event driver, conversion processing is faster and less complicated. SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2503 IA #: 2503 DATE CREATED: AUG 18, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LR7OR1 NAME: USE OF LR7OR1 ID: LR7OR1 GENERAL DESCRIPTION: This DBIA formalizes the documentation for calls to LR7OV1 as documented in the OE/RR Interface Specification document. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946458 COMPONENT/ENTRY POINT: RR(DFN,ORDER,BEG,END,SUB,TEST,FLAG,MAX) COMPONENT DESCRIPTION: This call returns lab results in the format: ^TMP("LRRR",$J,DFN,SUB,inverse d/t,sequence #) = Test^result^L/N flag^ units^reference range^result status^^^Nat'l Code^Name^System^Verified b y^^Therapeutic flag^Print Name^Accession^Order# (where Test is a ptr to the Lab Test file #60) VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of PATIENT file (#2) (REQUIRED) VARIABLES: ORDER TYPE: Input VARIABLES DESCRIPTION: Lab order number VARIABLES: BEG TYPE: Input VARIABLES DESCRIPTION: Beginning date for results search (OPTIONAL) VARIABLES: END TYPE: Input VARIABLES DESCRIPTION: Ending date for results search (OPTIONAL) VARIABLES: SUB TYPE: Input VARIABLES DESCRIPTION: Lab subsection of CH,MI,AP or ALL (OPTIONAL - default is ALL) VARIABLES: TEST TYPE: Input VARIABLES DESCRIPTION: Pointer to LABORATORY TEST file (#60) (OPTIONAL - if nothing passed, gets all results) VARIABLES: FLAG TYPE: Input VARIABLES DESCRIPTION: L for LOCAL or N for NATIONAL. Denotes test ID used. (OPTIONAL) VARIABLES: MAX TYPE: Input VARIABLES DESCRIPTION: Maximum number of results to return (OPTIONAL) VARIABLES: TMP('LRRR', TYPE: Output VARIABLES DESCRIPTION: TMP("LRRR",$J,DFN,SUB,inverse date/time,sequence #) set to: = Test^result^L/N flag^units^reference range^result status^^^Nat'l Code^Name^System^Verified by^^Ther flag^Print Name^Accession^Order# Note: Test is a pointer to the LABORATORY TEST file (#60). COMPONENT/ENTRY POINT: $$LRDFN(IFN,FILEROOT) COMPONENT DESCRIPTION: Get LRDFN VARIABLES: IFN TYPE: Input VARIABLES DESCRIPTION: Internal File Number VARIABLES: FILEROOT TYPE: Input VARIABLES DESCRIPTION: Root of file to get LRDFN (optional) "DPT(" is default VARIABLES: $$LRDFN TYPE: Output VARIABLES DESCRIPTION: Internal file number of the entry in the LAB RESULTS file SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: VBECS SUBSCRIBING PACKAGE: MRSA INITIATIVE REPORTS SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 5/24/12-VPR added as subscriber for VPR*1.0. Left NHIN as subscriber. 7/25/13-MM: Added TIU as a subscriber to ICR #2503. Jason Enelow from the VistA Maintenance team requested TIU be added as a subscriber when he discovered a call to RR~LR7OR1 in LAB2+11~TIUWRIIS. Margy McClenehan was notified TIU was added as a subscriber. It was agreed a patch to add the ICR # to the routine as a comment line was not needed. This could be added when/if the routine is modified in the future. This request was processed as a documentation only request to document an existing reference. No further reviews were done. 3/6/15-MC:Added VPS as a subscriber at the request of Anita Hassett and approved by Levi Teitelbaum. VPS,After Visit Summary (AVS) needs to call RR^LR7OR1 through the RPC Broker to pull detailed results of an identified patient's identified lab order. Patch VPS*1*15 planned release is March 2015. DATE/TIME EDITED: APR 10, 2009@15:44 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MCDEARMON,JAMES DATE/TIME EDITED: SEP 16, 2010@10:58 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE DATE/TIME EDITED: MAY 24, 2012@15:39 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: ANZALDUA,CAROL DATE/TIME EDITED: JUL 25, 2013@16:33 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: ENELOW,JASON DATE/TIME EDITED: MAR 06, 2015@06:55 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HASSETT,ANITA WITH CONCURRENCE OF: TEITELBAUM,LEVI NUMBER: 2504 IA #: 2504 FILE NUMBER: 21 GLOBAL ROOT: DIC(21 DATE CREATED: AUG 19, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2504 ID: DIC(21 GLOBAL REFERENCE: DIC(21,D0,0 FIELD NUMBER: 2 FIELD NAME: ABBREVIATION ACCESS: Read w/Fileman GENERAL DESCRIPTION: Lab is requesting a temporary aggreement to read the following: ;NOW GET PERIOD OF SERVICE K VAEL D ELIG^VADPT S:$G(VAEL(2))'="" $P(MSG,HLFS,28)=$P($G(^DIC(21,+VAEL(2),0)),U,3) K VAEL STATUS: Active DURATION: Next Version EXPIRATION DATE: JAN 01, 1999 MAIL MESSAGE: 27575711 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 2505 IA #: 2505 FILE NUMBER: 59.4 GLOBAL ROOT: PS(59.4,D0,0) DATE CREATED: AUG 20, 1998 CUSTODIAL PACKAGE: CONTROLLED SUBSTANCES CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: INPATIENT SITE ID: PS(59.4,D0,0) GLOBAL REFERENCE: PS(59.4,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: In the DRUG ACCOUNTABILITY STATS file (#58.8), there is a field called INPATIENT SITE (#2). This field is a pointer to the NAME field (.01) of the INPATIENT SITE file (#59.4). To obtain the external value of this pointer, a direct global read is used. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27713451 SUBSCRIBING PACKAGE: DRUG ACCOUNTABILITY ISC: Birmingham NUMBER: 2507 IA #: 2507 FILE NUMBER: 771.6 GLOBAL ROOT: HL(771.6 DATE CREATED: AUG 20, 1998 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2507 ID: HL(771.6 GLOBAL REFERENCE: HL(771.6, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Lab requests permission to read file 771.6 as follows: I $G(LRSTATUS) S LRTXT(LRX)="Message: "_LRX_$P(^HL(771.6,+LRSTATUS,0),U) This call will be converted in the next version of the extract. STATUS: Active DURATION: Next Version MAIL MESSAGE: 33511244 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING NUMBER: 2508 IA #: 2508 FILE NUMBER: 4 GLOBAL ROOT: DIC(4, DATE CREATED: AUG 20, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: 2508 ID: DIC(4, GLOBAL REFERENCE: DIC(4,D0,0, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The lab requests a DBIA to perform a direct read on the following: S:$D(^DIC(4,"D",SITE)) ISITE=$O(^DIC(4,"D",SITE,0)) I +ISITE>0,$G(^DIC(4,ISITE,0))'="" S SITE=$P(^DIC(4,SITE,0),U,1) STATUS: Active DURATION: Next Version EXPIRATION DATE: JAN 01, 1999 MAIL MESSAGE: 27575711 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 2509 IA #: 2509 FILE NUMBER: 19 GLOBAL ROOT: DIC(19, DATE CREATED: AUG 24, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2509 ID: DIC(19, GLOBAL REFERENCE: DIC(19,IEN,20) FIELD NUMBER: 20 FIELD NAME: ENTRY ACTION LOCATION: 20;E1,245 ACCESS: Read w/Fileman GLOBAL REFERENCE: DIC(19,IEN,22) FIELD NUMBER: 22 FIELD NAME: XQUIT EXECUTABLE LOCATION: 22;E1,245 ACCESS: Write w/Fileman GENERAL DESCRIPTION: Surgery requests permission to $O through the OPTION file (#19) "B" cross reference to identify options in the SR namespace. Surgery further requests READ access by VA FileMan to the ENTRY ACTION field (#20) and WRITE access to the XQUIT EXECUTABLE field (#22). The purpose of this request is to allow Surgery to issue a patch that will identify the Surgery options that may potentially set the XQUIT variable and to update these options with code to process the XQUIT. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27745213 SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 2510 IA #: 2510 FILE NUMBER: 59 GLOBAL ROOT: PS(59 DATE CREATED: AUG 24, 1998 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2510 ID: PS(59 GLOBAL REFERENCE: PS(59,D0,0) FIELD NUMBER: .01 FIELD NAME: Name LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .06 FIELD NAME: Site Number LOCATION: 0;6 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Pharmacy Benefits Management extracts data from the division fields of the prescription file (#52) and outpatient site field of the drug accountability stats file (#58.8). These fields point to the Outpatient site file #59 from which the outpatient site name and number can be extracted. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27746140 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 2514 IA #: 2514 FILE NUMBER: 50.606 GLOBAL ROOT: PS(50.606, DATE CREATED: AUG 24, 1998 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ACCESS TO DRUG INGREDIENTS FILE (#50.606) ID: PS(50.606, GLOBAL REFERENCE: PS(50.606,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. National Drug File has need to do a direct global read to the zero node of file 50.606. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 28262146 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham NUMBER: 2515 IA #: 2515 FILE NUMBER: 58.1 GLOBAL ROOT: PSI(58.1 DATE CREATED: AUG 24, 1998 CUSTODIAL PACKAGE: AUTO REPLENISHMENT/WARD STOCK CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2515 ID: PSI(58.1 GLOBAL REFERENCE: PSI(58.1,D0,2, FIELD NUMBER: .01 FIELD NAME: WARD/LOCATION (FOR PERCENTAGE) LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: PSI(58.1, FIELD NUMBER: 3 FIELD NAME: INACTIVE DATE LOCATION: I;1 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: INPATIENT SITE LOCATION: SITE;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Pharmacy Benefits Management extracts the following fields from File #58.1, Pharmacy AOU Stock in order to attempt to breakdown the AR/WS statistical data by division. Various portions of the program $O through ^PSI(58.1,D0,0), ^PSI(58.1,D0,2,0 and ^PSI(58.1,"ASITE",in order to use various Area of Uses (AOU) to map an inpatient site to a specific division by using the ward/location (for percentage) field. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27749878 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 2516 IA #: 2516 FILE NUMBER: 8.1 GLOBAL ROOT: DIC(8.1 DATE CREATED: AUG 24, 1998 CUSTODIAL PACKAGE: REGISTRATION USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2516 ID: DIC(8.1 GENERAL DESCRIPTION: ^DIC(8.1,D0,0) .01 NAME 0;1 Direct Global Read 6 INACTIVE 0;7 Direct Global Read One of the CIRN pre-implementation steps is to compare the entries in the ELIGIBILITY CODE file (#8) and the MAS ELIGIBILITY CODE file (#8.1). This is to insure that all the entries in File 8 link to a corresponding entry in File 8.1. The CIRN ELIGIBILITY CODE REVIEW report, routine RGPRELIG, displays these links. STATUS: Active MAIL MESSAGE: 27726476 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING PACKAGE: INTEGRATED BILLING EDITOR: SCOTT,APRIL L NUMBER: 2517 IA #: 2517 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: AUG 24, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: FILE405 ADFN X-REF ID: DGPM( GLOBAL REFERENCE: DGPM('ADFN'_DFN GLOBAL DESCRIPTION: The cross-reference consists of the letters ADFN concatenated to the patient's DFN value followed by the movement date in FileMan format and the internal entry number of the record. For example: ^DGPM("ADFN346",2870225.13,2246) GENERAL DESCRIPTION: The Women Veterans Health (WVH) package requests permission to loop through the ADFN cross-reference to determine if a patient has an entry within a user selected date range. The WVH package does not want to look at the entry itself, but is merely interested in whether the patient has a record. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27751540 SUBSCRIBING PACKAGE: WOMEN'S HEALTH ISC: Hines NUMBER: 2518 IA #: 2518 DATE CREATED: AUG 25, 1998 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSNDINT NAME: OUTPATIENT DRUG INTERACTION ID: PSNDINT GENERAL DESCRIPTION: The Outpatient Pharmacy V 6.0 package (OP) requests the ability to re-route the Drug-Drug interaction function to the National Drug File's (NDF) routine PSNDINT. Upcoming new functionality by NDF will eventually replace the OP Drug-Drug interaction functionality. During the installation period this would allow the users a painless introduction to the new functionality. After a period of time the OP options will be removed. OP ROUTINE/LINETAG ADD+1^PSOHELP Add local drug interactions CRI+1^PSOHELP Change interaction severity Both call PSNDINT at the top. No variables are passed or returned. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27760374 COMPONENT/ENTRY POINT: PSNDINT COMPONENT DESCRIPTION: This is a stand-alone NDF option used to add or change drug interactions. SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 2519 IA #: 2519 FILE NUMBER: 58.8 GLOBAL ROOT: PSD(58.8 DATE CREATED: AUG 30, 1998 CUSTODIAL PACKAGE: DRUG ACCOUNTABILITY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2519 ID: PSD(58.8 GLOBAL REFERENCE: PSD(58.8,D0,0) FIELD NUMBER: .01 FIELD NAME: Pharmacy Location LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: Location type LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: Inpatient site LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: Primary dispensing site LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: 20 FIELD NAME: Outpatient site LOCATION: 0;10 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: INACTIVE DATE LOCATION: I;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: PSD(58.8,D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: Drug LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 7 FIELD NAME: Breakdown Unit LOCATION: 0;8 ACCESS: Read w/Fileman FIELD NUMBER: 8 FIELD NAME: Package Size LOCATION: 0;9 ACCESS: Read w/Fileman GLOBAL REFERENCE: PSD(58.8,D0,3.5,D1,0) FIELD NUMBER: .01 FIELD NAME: IV Room LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: PSD(58.8,D0,3,D1,0) FIELD NUMBER: .01 FIELD NAME: Ward LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: PSD(58.8,"B", GLOBAL DESCRIPTION: "B" x-ref, direct global read access permitted. GENERAL DESCRIPTION: Pharmacy Benefits Management extracts the following fields from the Drug Accountability Stats file #58.8 on a montly basis. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27795092 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 2520 IA #: 2520 FILE NUMBER: 58.81 GLOBAL ROOT: PSD(58.81 DATE CREATED: AUG 30, 1998 CUSTODIAL PACKAGE: DRUG ACCOUNTABILITY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2520 ID: PSD(58.81 GLOBAL REFERENCE: PSD(58.81,D0,0) FIELD NUMBER: .01 FIELD NAME: Transaction Number LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: Type LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: Pharmacy Location LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: Date/time LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: Drug LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 5 FIELD NAME: Quantity LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 8 FIELD NAME: Purchase Order Number LOCATION: 0;9 ACCESS: Read w/Fileman FIELD NUMBER: 12 FIELD NAME: Manufacturer LOCATION: 0;13 ACCESS: Read w/Fileman FIELD NUMBER: 17 FIELD NAME: NAOU LOCATION: 0;18 ACCESS: Read w/Fileman GLOBAL REFERENCE: PSD(58.81,D0,4) FIELD NUMBER: 48 FIELD NAME: Edit Verified Order Date/time LOCATION: 4;1 ACCESS: Read w/Fileman FIELD NUMBER: 50 FIELD NAME: New Quantity LOCATION: 4;3 ACCESS: Read w/Fileman GLOBAL REFERENCE: PSD(58.81,D0,5) FIELD NUMBER: 55 FIELD NAME: Cancelled Verified Order Date/time LOCATION: 5;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: PSD(58.81,D0,8) FIELD NUMBER: 71 FIELD NAME: Prime Vendor Invoice LOCATION: 8;1 ACCESS: Read w/Fileman FIELD NUMBER: 106 FIELD NAME: Prime Vendor Order Number LOCATION: 8;2 ACCESS: Read w/Fileman GLOBAL REFERENCE: PSD(58.81,D0,9) FIELD NUMBER: 73 FIELD NAME: Patient LOCATION: 9;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Pharmacy Benefits Management extracts data from the Drug Accountability Transaction file #58.81 on a monthly basis. The program uses the ^PSD(58.81,"AF" cross reference on the date/time field to identify certain types of controlled substance and procurement transactions. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27795091 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 2521 IA #: 2521 FILE NUMBER: 58.811 GLOBAL ROOT: PSD(58.811 DATE CREATED: AUG 30, 1998 CUSTODIAL PACKAGE: DRUG ACCOUNTABILITY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2521 ID: PSD(58.811 GLOBAL REFERENCE: PSD(58.811,D0,0) FIELD NUMBER: 1 FIELD NAME: Vendor name LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .01 FIELD NAME: ORDER NUMBER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSD(58.811,D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: Invoice Number LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: INVOICE STATUS LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: Pharmacy Location LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 13 FIELD NAME: Master Vault LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: INVOICE DATE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: ORDER DATE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7 FIELD NAME: DELIVERY DATE LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSD(58.811,D0,1,D1,1,D2,0) FIELD NUMBER: 1 FIELD NAME: Drug LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: Quantity Invoiced LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: Order unit LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: Price per Order Unit LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7 FIELD NAME: Date verified LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 13 FIELD NAME: NDC LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 14 FIELD NAME: VSN LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 15 FIELD NAME: UPC LOCATION: 0;13 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .01 FIELD NAME: LINE ITEM NUMBER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5 FIELD NAME: DATE PROCESSED LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6 FIELD NAME: PROCESSOR LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 8 FIELD NAME: VERIFIER LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 12 FIELD NAME: CONTROLLED SUBSTANCE? LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSD(58.811,D0,1,D1,1,D2,1,D3,0) FIELD NUMBER: .01 FIELD NAME: Adjusted field LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5 FIELD NAME: Verifier Adjustment LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: PROCESSOR ADJUSTMENT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: PROCESSOR'S REASON LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: PROCESS DATE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: PROCESSOR LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6 FIELD NAME: VERIFIER'S REASON LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 7 FIELD NAME: VERIFICATION DATE LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 8 FIELD NAME: VERIFIER LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSD(58.811,D0,1,D1,1,D2,2) FIELD NUMBER: 10 FIELD NAME: Dispense Units Per Order Unit LOCATION: 2;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 16 FIELD NAME: Synonym Node LOCATION: 2;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 11 FIELD NAME: REORDER LEVEL LOCATION: 2;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 17 FIELD NAME: STOCK LEVEL LOCATION: 2;4 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSD(58.811,D0,1,D1,1,0) FIELD NUMBER: 5 FIELD NAME: LINE ITEM DATA LOCATION: 1;0 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSD(58.811,D0,1,D1,1,D2,1,0) FIELD NUMBER: 9 FIELD NAME: ADJUSTMENTS LOCATION: 1;0 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSD(58.811,D0,1,0) FIELD NUMBER: 2 FIELD NAME: INVOICE DATA LOCATION: 1;0 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Pharmacy Benefits Management extracts data from the Drug Accountability Order file #58.811 on a monthly basis. The program utilizes the ^PSD(58.811,"ADATE", cross reference to identify prime vendor invoices for a specific time period. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29439890 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 2522 IA #: 2522 FILE NUMBER: 64 GLOBAL ROOT: LAM( DATE CREATED: AUG 30, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2522 ID: LAM( GLOBAL REFERENCE: LAM(D0,7,D1,0) FIELD NUMBER: .01 FIELD NAME: Associated Names LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Pharmacy Benefits Management utilizes the Wkld Code file #64 to identify national laboratory tests with a specific wkld code and then which local laboratory tests are linked. The ^LAM("C" cross reference will be used to identify national laboratory test with a specific wkld code. The ^LAM(D0,7,"B", cross refernce on the associated name field will be used to identify all local laboratory tests linked to specific wkld codes. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27470160 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 2523 IA #: 2523 FILE NUMBER: 60 GLOBAL ROOT: LAB(60 DATE CREATED: AUG 30, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2523 ID: LAB(60 GLOBAL REFERENCE: LAB(60, FIELD NUMBER: .01 FIELD NAME: Name LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 5 FIELD NAME: Location (Data Name) LOCATION: 0;5 ACCESS: Read w/Fileman GLOBAL REFERENCE: LAB(60,D0,1, FIELD NUMBER: .01 FIELD NAME: SITE/SPECIMEN LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 6 FIELD NAME: Units LOCATION: 0;7 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: REFERENCE LOW LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: REFERENCE HIGH LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: CRITICAL LOW LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: CRITICAL HIGH LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 7 FIELD NAME: TYPE OF DELTA CHECK LOCATION: 0;8 ACCESS: Read w/Fileman FIELD NUMBER: 8 FIELD NAME: DELTA VALUE LOCATION: 0;9 ACCESS: Read w/Fileman FIELD NUMBER: 9 FIELD NAME: DEFAULT VALUE LOCATION: 0;10 ACCESS: Read w/Fileman FIELD NUMBER: 9.2 FIELD NAME: THERAPEUTIC LOW LOCATION: 0;11 ACCESS: Read w/Fileman FIELD NUMBER: 9.3 FIELD NAME: THERAPEUTIC HIGH LOCATION: 0;12 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Pharmacy Benefits Management extracts data from the Laboratory test file #60. Only local laboratory tests with a site/specimen that contains 'plasma', 'serum' or 'blood'. The name, units and the location of the test result data can then be extracted. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27470160 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 2524 IA #: 2524 FILE NUMBER: 63 GLOBAL ROOT: LR( DATE CREATED: AUG 30, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2524 ID: LR( GLOBAL REFERENCE: LR(D0,CH,D1,0) FIELD NUMBER: .01 FIELD NAME: Date/time Specimen Taken LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .05 FIELD NAME: Specimen Type LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: .03 FIELD NAME: Date report completed LOCATION: 0;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: GLOBAL DESCRIPTION: GLOBAL REFERENCE: LR(D0,CH,LRIDT,DATANAME) GLOBAL DESCRIPTION: The program extracts all data stored on this node, but only the test results, hi/lo flag and whether or not the test was verified is used. The above fields are found in the first 3 pieces of the DATANAME node. GENERAL DESCRIPTION: Pharmacy Benefits Management extracts test results (^LR(D0,CH,0)=^63.04^^ for certain laboratory tests, the hi/lo flag and the date/time the specimen was taken. The program will go back one year and pull the most recent result for a particular lab test. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27470160 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 2526 IA #: 2526 DATE CREATED: SEP 03, 1998 CUSTODIAL PACKAGE: IFCAP USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCHUTL NAME: PRCHUTL ID: PRCHUTL GENERAL DESCRIPTION: This integration agreement will allow Accounts Receivable to call two functions in this routine. $$VENSEL will return the internal number of a user selected Vendor from the IFCAP Vendor file. $$VEN will return the Vendor ID number when the internal number of a Vendor is sent to this function. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27487423 COMPONENT/ENTRY POINT: $$VENSEL() COMPONENT DESCRIPTION: The call to get a vendor entry is $$VENSEL^PRCHUTL(). This function does 3 things. First, it asks the user for their site. Second, it allows the user to select an IFCAP vendor record. And third, it returns the following: CONDITION RETURNED VALUE ^DIC VALUE LOOKUP FAILED -1 Y=-1 TIMED OUT -2 DTOUT UP-ARROW -3 DUOUT SUCCESSFUL IEN^.01 FIELD Y=N^S SUCCESSFUL & NEW IEN^.01 FIELD^1 Y=N^S^1 VARIABLES: $$VENSEL TYPE: Output VARIABLES DESCRIPTION: The following is returned from the IFCAP Vendor File: CONDITION RETURNED VALUE ^DIC VALUE LOOKUP FAILED -1 Y=-1 TIMED OUT -2 DTOUT UP-ARROW -3 DUOUT SUCCESSFUL IEN^.01 FIELD Y=N^S SUCCESSFUL & NEW IEN^.01 FIELD^1 Y=N^S^1 COMPONENT/ENTRY POINT: $$VEN(A) COMPONENT DESCRIPTION: The call to get the FMS VENDOR CODE + ALTERNATE ADDRESS INDICATOR is $$VEN^PRCHUTL(A). This function does one thing. It requires the internal entry number of the vendor record that the data will be from. It returnes the FMS VENDOR CODE and, if available, the ALTERNATE ADDRESS INDICATOR as 9 or 11 characters. VARIABLES: $$VEN TYPE: Output VARIABLES DESCRIPTION: The call to get the FMS VENDOR CODE + ALTERNATE ADDRESS INDICATOR is $$VEN^PRCHUTL(A). This function does one thing. It requires the internal entry number of the vendor record that the data will be from. It returnes the FMS VENDOR CODE and, if available, the ALTERNATE ADDRESS INDICATOR as 9 or 11 characters. VARIABLES: A TYPE: Input VARIABLES DESCRIPTION: A = internal entry number of the vendor record that the data will be from. SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE NUMBER: 2527 IA #: 2527 FILE NUMBER: 50.612 GLOBAL ROOT: PSNTRAN( DATE CREATED: SEP 01, 1998 CUSTODIAL PACKAGE: NATIONAL DRUG FILE CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2527 ID: PSNTRAN( GLOBAL REFERENCE: PSNTRAN(D0, FIELD NUMBER: 10 FIELD NAME: END LOCATION: END;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 11 FIELD NAME: LAST UNMATCHED DRUG CLASSED LOCATION: END;3 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: The field name entered is correct but is "clipped" in some print-outs. The full field name is: LAST UNMATCHED DRUG CLASSED VIEWER: SCHLEHUBER,CAMERON VIEWER: ALEXANDER,DAVID VIEWER: MONTALI,MICHAEL VIEWER: MIMS,MICHAEL VIEWER: CHRISTENSEN,KIM STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27806122 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 2528 IA #: 2528 FILE NUMBER: 660 GLOBAL ROOT: RMPR(660 DATE CREATED: SEP 03, 1998 CUSTODIAL PACKAGE: PROSTHETICS CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2528 ID: RMPR(660 GLOBAL REFERENCE: RMPR(660,DA) FIELD NUMBER: .02 FIELD NAME: PATIENT NAME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The name is a pointer to the PROSTHETIC PATIENT file which has the same internal entry number as the main patient database. FIELD NUMBER: 2 FIELD NAME: TYPE OF TRANSACTION LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This set of codes will tell what kind of transaction this request is. FIELD NUMBER: 5 FIELD NAME: QTY LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the number of units that was issued or repaired for this transaction. FIELD NUMBER: 8 FIELD NAME: STATION LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The station is the Veterans Affairs site where this transaction is to come to completion. It is the station that is ultimately responsible for the issue and payment for the prosthetic device. This is the station reporting the workload. FIELD NUMBER: 10 FIELD NAME: DELIVERY DATE LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the date that the appliance was delivered and accepted by the patient. FIELD NUMBER: 11 FIELD NAME: FORM REQUESTED ON LOCATION: 0;13 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The FORM REQUESTED ON is based on current VA regulations. FIELD NUMBER: 12 FIELD NAME: SOURCE LOCATION: 0;14 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This set of codes denotes which two possible sources were used for the acquisition of the appliance. The sources are grouped into either VA sources or commercial sources. FIELD NUMBER: 14 FIELD NAME: TOTAL COST LOCATION: 0;16 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the total cost of the transaction. FIELD NUMBER: 6 FIELD NAME: SHIP/DEL LOCATION: 0;17 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the charge associated with shipping. FIELD NUMBER: 4.1 FIELD NAME: HCPCS LOCATION: 0;22 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field should have the HCPCS code for the prosthetics item. FIELD NUMBER: 6.5 FIELD NAME: PICKUP/DEL LOCATION: 0;26 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is a set of codes to identify pickup/delivery charges on VAF 10-2319. FIELD NUMBER: 40 FIELD NAME: REQUESTING STATION LOCATION: LB;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the station requesting services or appliances. FIELD NUMBER: 70 FIELD NAME: RECEIVING STATION LOCATION: LB;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the institution that will receive the VAF 10-2529-3 request for processing. FIELD NUMBER: 46 FIELD NAME: TOTAL LABOR COST LOCATION: LB;7 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The total cost of the labor to perform this job. FIELD NUMBER: 47 FIELD NAME: TOTAL MATERIAL COST LOCATION: LB;8 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The total cost of all the materials to perform the job. FIELD NUMBER: 48 FIELD NAME: TOTAL LAB COST LOCATION: LB;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The Prosthetic Laboratory Total Cost calculated by AMIS. FIELD NUMBER: 81 FIELD NAME: NO ADMIN COUNT LOCATION: AM;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field will be set if the Item will not count on the Administrative AMIS or the Orthotic Laboratory AMIS. FIELD NUMBER: 62 FIELD NAME: PATIENT CATEGORY LOCATION: AM;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the Prosthetic Patient Category used for counting AMIS. FIELD NUMBER: 68 FIELD NAME: AMIS GROUPER LOCATION: AMS;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: A number pulled from the Pros. Site Parameter file, used in AMIS calculations. FIELD NUMBER: 15 FIELD NAME: HISTORICAL DATA LOCATION: 0;15 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: If this field contains an asterisk (*), then this transaction has been counted by the AMIS option, or is considered to be a historical transaction. GLOBAL DESCRIPTION: This Global holds the Prosthetics order information. GENERAL DESCRIPTION: DSS needs to reference the following fields to extract Prosthetics information for the DSS Program. Additionally, DSS Extracts need to $Order through the ^RMPR(660,"CT") cross-reference to pull the Delivery date from the prosthetics entries. the 'C' cross-reference is on the Delivery Date field (#10). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27823973 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany NUMBER: 2529 IA #: 2529 FILE NUMBER: 669.9 GLOBAL ROOT: RMPR(669.9 DATE CREATED: SEP 03, 1998 CUSTODIAL PACKAGE: PROSTHETICS CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2529 ID: RMPR(669.9 GLOBAL REFERENCE: RMPR(669.9 GLOBAL DESCRIPTION: This file holds the list of parameters which controls the operation of the prosthetics package at a site. GENERAL DESCRIPTION: DSS Extracts has permission to $Order through the 'C' Cross-Reference on the Prosthetics Site Parameters file (#669.9). [^RMPR(669.9,"C")] The 'C' Cross-Reference is on the Station field (#1) which points to the Institution file (#4). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27823891 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany NUMBER: 2530 IA #: 2530 DATE CREATED: SEP 15, 1998 CUSTODIAL PACKAGE: INCOME VERIFICATION MATCH CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IVMLINS4 NAME: IB INSURANCE BUFFER ACCEPT/REJECT UPDATES ID: IVMLINS4 CREATOR: HARVEY,JULIE S GENERAL DESCRIPTION: Integrated Billing calls the IVM function $UPDATE^IVMLINS4 when an IB Insurance Buffer file entry that originated in IVM is either accepted or rejected. With patch IVM*2*135, IVMREPTR and IVMSUPPR variables were added to the API. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27895208 COMPONENT/ENTRY POINT: $$UPDATE(DFN,STAT,ID,IVMREPTR,IVMSUPPR) COMPONENT DESCRIPTION: Inform IVM when an insurance policy that originated in the IVM upload is either rejected or accepted into the permanent insurance records. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient associated with the insurance record updated. VARIABLES: STAT TYPE: Input VARIABLES DESCRIPTION: Change in insurance record status: 1 - accepted, 0 - rejected. VARIABLES: ID TYPE: Input VARIABLES DESCRIPTION: Three pieces of data that identify which of the patients IVM insurance records is being updated: Insurance Co Name ^ Street Add [Line1] ^ Group #. VARIABLES: TYPE: Output VARIABLES DESCRIPTION: Function returns: 1 if update successful, 0 otherwise VARIABLES: IVMREPTR TYPE: Input VARIABLES DESCRIPTION: This is the IVM REASONS FOR NOT UPLOADING (#301.91) Internal Entry Number when an Insurance Segment is rejected. This variable will be stored in the REASON NOT UPLOADING INSURANCE (#.08) field of the IVM PATIENT (#301.5) file. This variable should be us ed in conjunction with the IVMSUPPR variable when an insurance entry is rejected and the calling application already has the IVM REASONS FOR NOT UPLOADING. This is an optional variable. VARIABLES: IVMSUPPR TYPE: Input VARIABLES DESCRIPTION: When this is input with a positive value, any writes to the screen are suppressed and the interactive read of the IVM REASON FOR NOT UPLOADING (#301.91) file is not done. This is an option variable. This variable should be used in conjunction with the IVMREPTR variable. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany DBA Comments: IVMREPTR and IVMSUPPR input variables added effective IVM*2.*135. Updated ICR name from old default value. DATE ACTIVATED: APR 13, 2009 DATE/TIME EDITED: APR 13, 2009@10:51 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: WINTERTON,STEVE WITH CONCURRENCE OF: SBERRO,SANDRA DATE/TIME EDITED: APR 13, 2009@11:43 ACTION: APPROVED AT THE REQUEST OF: WINTERTON,STEVE WITH CONCURRENCE OF: SBERRO,SANDRA NUMBER: 2531 IA #: 2531 DATE CREATED: SEP 04, 1998 CUSTODIAL PACKAGE: NATIONAL DRUG FILE USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSNAPIS NAME: Application Programmer Interfaces (APIs) ID: PSNAPIS CREATOR: RUZBACKI,RON T GENERAL DESCRIPTION: Since the National Drug File is being redesigned, these APIs are designed to allow other applications to make a smooth transition to the new file structure. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 53767090 COMPONENT/ENTRY POINT: PSA COMPONENT DESCRIPTION: S X=$$PSA^PSNAPIS(ndc,.array) where ndc is a 12 digit National Drug Code and array is an array defined by the calling application returns array(p50)=Drug name from the DRUG file (#50) and p50 is the internal entry number in that file for every drug which has the same product name as the name of the drug identified by the ndc. Returns X as the number of entries in array. COMPONENT/ENTRY POINT: PSJING COMPONENT DESCRIPTION: S X=$$PSJING^PSNAPIS(p1,p3,.array) where p1 and p3 are the first and third "^" pieces of the "ND" node in the DRUG File (#50) for a selected drug and array is a array defined by the calling application returns array(ien)=ien^ingredient^strength^unit where ien is the internal entry number in the DRUG INGREDIENTS file (#50.416) and ingredient is the name of the ingredient, strength, and unit for each ingredient in the selected drug. Returns X as the number of entries in array. COMPONENT/ENTRY POINT: PSJDF COMPONENT DESCRIPTION: S X=$$PSJDF^PSNAPIS(p1,p3) where p1 and p3 are the first and third pieces of the "ND" node in File #50 for a selected drug returns X=ien^dose where ien is the internal entry number in the DOSAGE FORM file (#50.606) and dose is the name of the dosage form for the selected drug. COMPONENT/ENTRY POINT: PSJST COMPONENT DESCRIPTION: S X=$$PSJST^PSNAPIS(p1,p3) where p1 and p3 are the first and third pieces of the "ND" node in File #50 for the selected drug returns X=1^strength where strength is the strength in the VA PRODUCT file (#50.68). COMPONENT/ENTRY POINT: CLASS COMPONENT DESCRIPTION: S X=$$CLASS^PSNAPIS(class) where class is a five character VA Drug Classification Code (e.g. CN103) returns X=1 if class is a valid code or 0 if it is not. COMPONENT/ENTRY POINT: DRUG COMPONENT DESCRIPTION: S X=$$DRUG^PSNAPIS(drug name) returns X=1 if drug name is either a valid Name entry in the VA GENERIC File (#50.6) or a valid Trade Name entry in the NDC/UPN File (#50.67). Returns X=0 otherwise. COMPONENT/ENTRY POINT: PROD0 COMPONENT DESCRIPTION: S X=$$PROD0^PSNAPIS(p1,p3) where p1 and p3 are the first and third pieces of the "ND" node in File #50 for a selected drug returns product information from the NATIONAL DRUG file (#50.6). X=VA PRODUCT NAME^DOSAGE FORM ENTRY^STRENGTH ENTRY^UNITS ^^^GCNSEQNO^PREVIOUS GCNSEQNO COMPONENT/ENTRY POINT: PROD2 COMPONENT DESCRIPTION: S X=$$PROD2^PSNAPIS(p1,p3) where p1 and p3 are the first and third pieces of the "ND" node in File #50 for a selected drug returns additional product information. X=VA PRINT NAME^VA PRODUCT IDENTIFIER^TRANSMIT TO CMOP^VA DISPENSE UNIT COMPONENT/ENTRY POINT: DCLASS COMPONENT DESCRIPTION: S X=$$DCLASS^PSNAPIS(p1,p3) where p1 and p3 are the first and third pieces of the "ND" node in File #50 returns the VA DRUG CLASSIFICATION for the selected drug (e.g. CYANIDE ANTIDOTES). COMPONENT/ENTRY POINT: DCLCODE COMPONENT DESCRIPTION: S X=$$DCLCODE^PSNAPIS(p1,p3) where p1 and p3 are the first and third pieces of the "ND" node in File #50 for a selected drug returns the 5 character class code for the selected drug (e.g. AD200). COMPONENT/ENTRY POINT: VAGN COMPONENT DESCRIPTION: S X=$$VAGN^PSNAPIS(p1) where p1 is the first piece of the "ND" node in File #50 for a selected drug returns X=VA GENERIC NAME for the selected drug. COMPONENT/ENTRY POINT: DFSU COMPONENT DESCRIPTION: S X=$$DFSU^PSNAPIS(p1,p3) where p1 and p3 are the first and third pieces of the "ND" node in File #50 for a selected drug returns dose, strength, and units X=DFIEN^DOSE^STIEN^STRENGTH^UNIEN^UNITS where DFIEN is the internal entry number of the dosage form, DOSE is the name of the dosage from, STIEN is the internal entry number of the strength, STRENGTH is the strength, UNIEN is the internal entry number of the units and UNITS is the unit. COMPONENT/ENTRY POINT: VAP COMPONENT DESCRIPTION: S X=$$VAP^PSNAPIS(da,.array) where da is an internal entry number in the VA GENERIC file (#50.6) and array is an array defined by the calling application returns array(ien)=ien^VA PRODUCT NAME^dfien^DOSE^clien^ CLASS where ien is the internal entry number of the product, dfien is the internal entry number of the DOSAGE FORM, clien is the internal entry number of the class, and CLASS is the five character class code for all products associated with the selected drug. COMPONENT/ENTRY POINT: PSPT COMPONENT DESCRIPTION: S X=$$PSPT^PSNAPIS(p1,p3,.array) where p1 and p3 are the first and third pieces of the "ND" node in File #50 for a selected drug and array is defined by the calling application returns array(psien^ptien)=psien^psize^ptien^ptype where psien is the internal entry number of the package size, ptien is the internal entry number of the package type, psize is the package size, and ptype is the package type for each package size and type combination for the selected drug. Returns X equals the number of entries in array. COMPONENT/ENTRY POINT: DSS COMPONENT DESCRIPTION: S X=$$DSS^PSNAPIS(p1,p3) where p1 and p3 are the first and third pieces of the "ND" node in File #50 for a selected drug returns x equals the five or seven digit DSS identifier for the selected drug. COMPONENT/ENTRY POINT: CPRS COMPONENT DESCRIPTION: S X=$$CPRS^PSNAPIS(p1,p3) where p1 and p3 are the first and third pieces of the "ND" node in File #50 for a selected drug returns X=DOSAGE FORM^CLASS CODE^STRENGTH^UNITS for the selected drug. COMPONENT/ENTRY POINT: CIRN COMPONENT DESCRIPTION: D CIRN^PSNAPIS(ndc,.array) where ndc is a 12 digit National Drug Code and array is defined by the calling application returns array=ndc array(0)=internal entry number in file 50.6 array(1)=VA GENERIC NAME array(2)=dose form ien^^class ien array(3)=strength array(4)=units ien array(5)=package size ien array(6)=package type pointer array(7)=NDC^MANUFACTURER^TRADE NAME^VA PRODUCT NAME POINTER^ROUTE OF ADMINISTRATION If ndc is not a valid entry array is returned as "000000000000" and the seven elements of array are returned as null. COMPONENT/ENTRY POINT: B COMPONENT DESCRIPTION: S X=$$B^PSNAPIS returns the closed global root of the "B" cross reference on the VA Generic Name. COMPONENT/ENTRY POINT: T COMPONENT DESCRIPTION: S X=$$T^PSNAPIS returns the closed global root of the "T" cross reference on the Trade Name in the NDC/UPN file (#50.67). COMPONENT/ENTRY POINT: OVRIDE COMPONENT DESCRIPTION: S X=$$OVRIDE^PSNAPIS(p1,p3) where p1 and p3 are the first and third pieces of the "ND" node in the DRUG File (#50) for the selected drug. Returns the value of the OVERRIDE DF DOSE CHK EXCLUSION Field (#31) from the VA PRODUCT File (#50.68). This field should always be populated with a '1' for 'YES' or a '0' for 'NO', but if the data is not populated, a null will be returned. COMPONENT/ENTRY POINT: FDAMG COMPONENT DESCRIPTION: S X=$$FDAMG^PSNAPIS(ien) where ien is the internal entry number in the VA PRODUCT file (#50.68), and returns the URL for the medication guide if one exists or null if it does not. COMPONENT/ENTRY POINT: POSDOS COMPONENT DESCRIPTION: S X=$$POSDOS^PSNAPIS(ien) where ien is the internal entry number in the VA PRODUCT file (#50.68). It returns the values from the following three fields for the VA Product, separated by up-arrow (^): CREATE DEFAULT POSSIBLE DOSAGE (#40) POSSIBLE DOSAGES TO CREATE (#41) PACKAGE (#42) Example: "N^O^O" COMPONENT/ENTRY POINT: REDCOP COMPONENT DESCRIPTION: S X=$$REDCOP^PSNAPIS(ien,date) where ien is the internal entry number in the VA PRODUCT file (#50.68) and date is the date to be verified for reduced co-pay. Returns X=1 for reduced co-pay or 0 for regular co-pay. DBA Comments: 20111220 - component REDCOP added by developer 10/24/14-DT: Added William Tatum as editor and deactivated ICR. Bill added 2 new attributes to an array to correct the ICR because these fields have been available for a while from this ICR. Old: COMPONENT: PSJING S X=$$PSJING^PSNAPIS(p1,p3,.array) where p1 and p3 are the first and third "^" pieces of the "ND" node in the DRUG File (#50) for a selected drug and array is a array defined by the calling application returns array(ien)=ien^ingredient where ien is the internal entry number in the DRUG INGREDIENTS file (#50.416) and ingredient is the name of the ingredient for every ingredient in the selected drug. Returns X as the number of entries in array. New: COMPONENT: PSJING S X=$$PSJING^PSNAPIS(p1,p3,.array) where p1 and p3 are the first and third "^" pieces of the "ND" node in the DRUG File (#50) for a selected drug and array is a array defined by the calling application returns array(ien)=ien^ingredient^strength^unit where ien is the internal entry number in the DRUG INGREDIENTS file (#50.416) and ingredient is the name of the ingredient, strength, and unit for each ingredient in the selected drug. Returns X as the number of entries in array. DATE ACTIVATED: OCT 24, 2014 DATE/TIME EDITED: FEB 19, 2009@09:54 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: RUZBACKI,RON DATE/TIME EDITED: FEB 09, 2011@16:24 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: SANTOS,ROBERTO DATE/TIME EDITED: FEB 09, 2011@16:25 ACTION: CONTENT CORRECTED AT THE REQUEST OF: ROCHA,MARCELO DATE/TIME EDITED: FEB 09, 2011@17:02 ACTION: APPROVED AT THE REQUEST OF: ROCHA,MARCELO WITH CONCURRENCE OF: SANTOS,ROBERTO DATE/TIME EDITED: DEC 20, 2011@09:44 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: ANWER,MOHAMED WITH CONCURRENCE OF: ROCHA,MARCELO DATE/TIME EDITED: DEC 20, 2011@10:26 ACTION: APPROVED AT THE REQUEST OF: ANWER,MOHAMED DATE/TIME EDITED: OCT 24, 2014@12:35 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: TATUM,BILL DATE/TIME EDITED: OCT 24, 2014@14:20 ACTION: APPROVED AT THE REQUEST OF: TATUM,BILL WITH CONCURRENCE OF: TATUM,BILL NUMBER: 2532 IA #: 2532 FILE NUMBER: 15 GLOBAL ROOT: VA(15, DATE CREATED: SEP 04, 1998 CUSTODIAL PACKAGE: TOOLKIT USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2532 ID: VA(15, GENERAL DESCRIPTION: In routine RGMTDPCT, CIRN counts duplicate entries for the PATIENT file (#2) in the DUPLICATE RECORD file (#15) by STATUS or MERGE STATUS It then counts the match percentile for the following: For STATUS it matches on (P) potential duplicates, (N) verified, notduplicate, (V) verified duplicate, (X) verified in progress, and (R) required review. For MERGE STATUS the matches are counted on (0) not ready, (1) ready, (2) merged, and (3) in progress. In routine RGMTDPSC, CIRN searches file #15 for duplicate pairs and displays this information by the CIRN Master of Record (CMOR) activity score range. The ranges are in 100'2 with a separate range for pairswhere both members have no score and where both members have zero score or one member has a zero score and the other has no score. The reports will give sites an idea of the active patients (with a CMOR score, incl 0) that are deemed duplicates. File: DUPLICATE RECORD (#15) ^VA(15,D0,0) .01 RECORD1 0;1 Direct Global Read .02 RECORD2 0;2 Direct Global Read .03 STATUS 0;3 Direct Global Read .05 MERGE STATUS 0;5 Direct Global Read STATUS: Active MAIL MESSAGE: 27726547 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2533 IA #: 2533 DATE CREATED: SEP 08, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUSER NAME: DBIA2533 ID: XUSER GENERAL DESCRIPTION: DSS has permission to use the Kernel function DIV4^XUSER according to the following: XUSER New file 200 API for DSS. The call is S X=$$DIV4^XUSER(.ZZ[,duz]) Input: The first parameter is a local variable that is passed by reference. The second is an optional IEN to the New Person file. If not passed it defaults to the current DUZ. Output: Returns a 1 if the user has a Division entry in the New Person file, else returns 0. If it returns a 1 then the first parameter is an array of IEN's for file 4 that have been assigned to the user. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27823643 COMPONENT/ENTRY POINT: DIV4 COMPONENT DESCRIPTION: Receives two parameters, the first is an Array name passed by reference and the second is an optional DUZ. DIV4^XUSER returns 1 to indicate that the array of pointers to the Institution file has been defined and 0 to indicate that the array of pointers to the Institution file has NOT been defined. The array will be defined and left in the applications partition if the user indicated by the value of the DUZ received has divisions defined in the respective New Person file entry. The format is ARRAY([^DIC(4 IEN]). DUZ is an optional parameter. If DUZ is not passed as a parameter, the function will default to the value of DUZ in the application's partition. An example of the function's use is: S X=$$DIV4^XUSER(.ZZ,duz) SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany SUBSCRIBING DETAILS: Request permission for use of this function from the Kernel development team. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI SUBSCRIBING PACKAGE: LAB SERVICE NUMBER: 2534 IA #: 2534 DATE CREATED: SEP 08, 1998 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOCP NAME: DBIA2534 ID: PSOCP GENERAL DESCRIPTION: This agreement provides CPRS two entry points to call that will return flags that indicate whether or not to ask various Copay-related questions concerning the Outpatient order being entered through CPRS. Prior to the effective date of the Veterans Millennium Health Care and Benefits Act, the only question that should be asked in CPRS is the Service Connected question. After the effective date of the Bill, seven additional questions can potentially be asked during the medication order process in CPRS. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33291904 COMPONENT/ENTRY POINT: $$SC(X,Y) COMPONENT DESCRIPTION: This entry point will be used by CPRS to determine whether or not to ask the Service Connected question for an Outpatient order. If this entry point is called after the effective date of the Veterans Millennium Health Care and benefits Act, a "1" will always be returned, because at this point the SCNEW^PSOCP call should be used. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: The internal entry number of the Patient. (required) VARIABLES: Y TYPE: Input VARIABLES DESCRIPTION: The internal entry number of the Dispense Drug. (optional) VARIABLES: $$SC TYPE: Output VARIABLES DESCRIPTION: If returned as 1, then CPRS does not have to ask the Service Connected question. If returned as 0, then the question must be asked. COMPONENT/ENTRY POINT: SCNEW(PSOTG,PSOPT,PSODR,PSORN) COMPONENT DESCRIPTION: This entry point will return an array to CPRS that contains questions that need to be asked during the Outpatient medication order entry process. If this call is made prior to the effective date of the Veterans Millennium Health Care and Benefits Act, nothing will be returned in the array. VARIABLES: PSOTG TYPE: Input VARIABLES DESCRIPTION: This is the target array, passed by reference. (required) VARIABLES: PSOPT TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number of the Patient. (required) VARIABLES: PSODR TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number of the Dispense Drug. (optional) VARIABLES: PSORN TYPE: Input VARIABLES DESCRIPTION: If the order is a Renewal, this is the internal entry number of the prescription that is being renewed from the PRESCRIPTION (#52) file. If defined, and there are questions returned in the array, and the question was asked on the original order, the response to that question will be returned as a default. (optional) VARIABLES: PSOTG() TYPE: Output VARIABLES DESCRIPTION: This is the array returned in the call, subscripted with whatever variable name is passed into the call. Up to six entries can be returned. If no entries are returned, then no questions need to be asked in CPRS for the order. The values that can be returned are: PSOTG("SC") for Service Connected. PSOTG("MST") for Military Sexual Trauma. PSOTG("AO") for Agent Orange. PSOTG("IR") for Ionizing Radiation. PSOTG("EC") for Environmental Contaminant. PSOTG("HNC") for Head or Neck Cancer. PSOTG("CV") for Combat. PSOTG("SHAD") for PROJ 112/SHAD If any of these are returned, then the question needs to be asked in CPRS. If the value is equal to null, then there is no default response. If the value is equal to '0', then the default response should be 'NO'. If the value is equal to '1', then the default response should be 'YES'. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2535 IA #: 2535 DATE CREATED: SEP 08, 1998 CUSTODIAL PACKAGE: MENTAL HEALTH CUSTODIAL ISC: Dallas USAGE: Supported TYPE: Routine ROUTINE: YSGAF NAME: DBIA2535 ID: YSGAF CREATOR: TRAXLER,FRANK GLOBAL REFERENCE: YSD(627.8,D0,60) FIELD NUMBER: 66 FIELD NAME: Patient Type LOCATION: 60;4 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Patient Type indicates that the patient is either an 'I'n-Patient or 'O'ut-Patient. GENERAL DESCRIPTION: GAF API'S The purpose of this patch is the creation of two API's for use with Mental Health system's Global Assessment of Function (GAF) Scores. The API's will be used to (1) return the most recent GAF score and diagnosis date the score was assessed and (2) store a new GAF score and date in the Diagnostics Results file (627.8). These two API's have been added to routine YSGAF. 10/30/13: The recently released Diagnostic and Statistical Manual of Mental Disorders, Fifth Edition, abbreviated as DSM-5, eliminates the use of the Global Assessment of Functioning (GAF) score. Starting with patch YS*5.01*108, new GAF scores for patients will no longer be saved in the Mental Health package. Historical data will continue to be available. The UPD call will set the YSERR variable equal to 1 and write an informational message. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27887655 COMPONENT/ENTRY POINT: RET(YSX) COMPONENT DESCRIPTION: Entry point RET^YSGAF(YSX) returns the most recent GAF score and diagnosis date. The internal entry number is passed into the call as variable YSX. The latest occurrence of the GAF score and GAF date are then passed back in the form of a concatenated string. If there is no GAF score entry then the API will pass back "-1" to indicate this situation. VARIABLES: YSX TYPE: Input VARIABLES DESCRIPTION: Contains the internal entry number. VARIABLES: YSZ TYPE: Output VARIABLES DESCRIPTION: Contains the result. COMPONENT/ENTRY POINT: UPD(YSPN,YSGN,YSGD,YSGC,YSPT) COMPONENT DESCRIPTION: Entry point UPD^YSGAF(YSPN,YSGN,YSGD,YSGC,YSPT) is designed to store patient GAF score information in the DIAGNOSTIC RESULTS - MENTAL HEALTH file (627.8). The information passed into the call includes patient name, GAF score (Axis 5), date/time of diagnosis, name of person giving diagnosis and patient type. VARIABLES: YSPN TYPE: Input VARIABLES DESCRIPTION: Patient name - Pointer to the patient name file (#2). VARIABLES: YSGN TYPE: Input VARIABLES DESCRIPTION: GAF score (Axis 5). VARIABLES: YSGD TYPE: Input VARIABLES DESCRIPTION: Date/Time of diagnosis. VARIABLES: YSGC TYPE: Input VARIABLES DESCRIPTION: Diagnosis by - Pointer to the new person file (#200). VARIABLES: YSPT TYPE: Input VARIABLES DESCRIPTION: Patient type - 'I'npatient or 'O'utpatient VARIABLES: YSERR TYPE: Output VARIABLES DESCRIPTION: The output variable will always be equal to one (i.e., YSERR=1) to indicate a new record was not created. An informational message will also be displayed to the user. EDITOR: TRAXLER,FRANK DBA Comments: 10/30/13 DT: Added Frank as Editor per the following message: In short, we no longer create and store a "Global Assessment of Functioning" (aka GAF) score for a patient in the Mental Health package. There are two ICRs in force that can be used by other VistA packages to pass us a new GAF score. In the case of ICR 2535, the code will now always send back an informational message stating that GAFs are no longer allowed. In case of ICR which never returned any value to sender, we are not doing anything with the data. DATE/TIME EDITED: OCT 30, 2013@11:09 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: TRAXLER,FRANK WITH CONCURRENCE OF: REDINGTON,PATRICK NUMBER: 2536 IA #: 2536 FILE NUMBER: 450 GLOBAL ROOT: PRSPC DATE CREATED: SEP 09, 1998 CUSTODIAL PACKAGE: PAID CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Prosthetics IA With the PAID Employee File (#450) ID: PRSPC GLOBAL REFERENCE: PRSPC(450 FIELD NUMBER: 8 FIELD NAME: SSN LOCATION: 0;9 ACCESS: Read w/Fileman FIELD NUMBER: 19 FIELD NAME: PAY BASIS LOCATION: 0;20 ACCESS: Read w/Fileman FIELD NUMBER: 28 FIELD NAME: SALARY LOCATION: 0;29 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Prosthetics is requesting read access to the following fields in the PAID Employee File (#450): Field (#8) SSN, (#19) Pay Basis, (#28) Salary VIEWER: BAUMANN,SCOTT A VIEWER: DAYON,RUFINO VIEWER: HEIGES,JOHN STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27800556 SUBSCRIBING PACKAGE: PROSTHETICS ISC: Hines NUMBER: 2537 IA #: 2537 DATE CREATED: SEP 15, 1998 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBCNBES NAME: DBIA2537 ID: IBCNBES GENERAL DESCRIPTION: The IVM package requests use of the function $$ADDSTF^IBCNBES to add a new entry to the INSURANCE BUFFER file (#355.33). This data was received at the site from HEC (IVM Center). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27891204 COMPONENT/ENTRY POINT: $$ADDSTF COMPONENT DESCRIPTION: The IVM package uses $$ADDSTF^IBCNBES to add a new entry to the INSURANCE BUFFER file (#355.33). VARIABLES: 3 TYPE: Input VARIABLES DESCRIPTION: The 3 indicates that the source of information is IVM. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient's IEN in the PATIENT file. VARIABLES: IVMIBDAT TYPE: Input VARIABLES DESCRIPTION: Data, to be filed in the IB buffer, in an array subscripted by field number of the data field in the INSURANCE BUFFER file (#355.33) SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany NUMBER: 2538 IA #: 2538 DATE CREATED: SEP 15, 1998 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBCNBME NAME: DBIA2538 ID: IBCNBME GENERAL DESCRIPTION: The Registration package requests use of REG^IBCNBME to add/edit a INSURANCE BUFFER file (#355.33) entry for registration and use of PREG^IBCNBME to add/edit a INSURANCE BUFFER file (#355.33) entry for pre-registration. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27893231 COMPONENT/ENTRY POINT: PREG COMPONENT DESCRIPTION: The Registration package uses PREG^IBCNBME to add/edit a INSURANCE BUFFER file (#355.33) entry for pre-registration. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient's IEN in the PATIENT file. COMPONENT/ENTRY POINT: REG COMPONENT DESCRIPTION: The Registration package uses REG^IBCNBME to add/edit a INSURANCE BUFFER file (#355.33) entry for registration. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient's IEN in the PATIENT file. SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 2539 IA #: 2539 FILE NUMBER: 19 GLOBAL ROOT: DIC(19, DATE CREATED: SEP 21, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DELETE OPTIONS ID: DIC(19, GLOBAL REFERENCE: DIC(19,'B', FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman GENERAL DESCRIPTION: This integration agreement is only for Registration. Permission to loop through the "B" xref on the option file to delete all 'DG172' namespaced options created by the DG*5.3*172 patch. STATUS: Active MAIL MESSAGE: 27861117 SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 2540 IA #: 2540 DATE CREATED: SEP 21, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DDBR2 NAME: BROWSER SWITCHING ID: DDBR2 GENERAL DESCRIPTION: The purpose of this DBIA is to provide a temporary method for switching between 'documents' without the user having to mentally resolve pointers between records in two different files. The needed functionality is currently planned by the VA Fileman developers to released in a patch. When that patch is released, the HL7 developers will modify the Transmission Log code to use the released functionality. See IA# 3594. VIEWER: DIMICELI,RON VIEWER: SHEPPARD,JEAN VIEWER: CLEMENS,JOHN VIEWER: ORMSBY,SKIP VIEWER: HOYE,MAUREEN VIEWER: HOLMES,ROY A STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34573380 COMPONENT/ENTRY POINT: SAVEDDB COMPONENT DESCRIPTION: Used to save variables before 'switching' between documents. COMPONENT/ENTRY POINT: USAVEDDB COMPONENT DESCRIPTION: Used to 'unsave' variables befor switching between documents. COMPONENT/ENTRY POINT: WP COMPONENT DESCRIPTION: Used to display a specific Browser screen without user interaction. (This API is used in conjunction with a call to PSR^DDBRO covered by IA# 3594.) SUBSCRIBING PACKAGE: HEALTH LEVEL SEVEN ISC: Oakland NUMBER: 2541 IA #: 2541 DATE CREATED: SEP 21, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUPARAM NAME: DBIA2541 ID: XUPARAM GENERAL DESCRIPTION: This DBIA documents the supported calls to XUPARAM to get some KERNEL SYSTEM parameters fields. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27934220 COMPONENT/ENTRY POINT: $$KSP COMPONENT DESCRIPTION: This entry point will return several items of site parameter data to the calling routine. Currently supported values: SPOOL LINE returns the max number of lines in one spool document. SPOOL DOC returns the max number of spool documents the user may have. WHERE returns the local domain name. INST returns the IEN of the default institution entry. VARIABLES: $$KSP TYPE: Output VARIABLES DESCRIPTION: Some value from the Kernel system parameter file. VARIABLES: parameter TYPE: Input VARIABLES DESCRIPTION: This is a string to request a value from the Kernel System Parameter file. Currently supported values: "SPOOL LINE" returns the max number of lines in one spool document. "SPOOL DOC" returns the max number of spool documents the user may have. "WHERE" returns the local domain name. "INST" returns the IEN of the default institution entry. NUMBER: 2542 IA #: 2542 DATE CREATED: SEP 21, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUPARAM NAME: DBIA2542 ID: XUPARAM GENERAL DESCRIPTION: These are calls to set or get simple parameters from a file that the site can edit. The file is KERNEL PARAMETERS (#8989.2) STATUS: Active MAIL MESSAGE: 27934219 COMPONENT/ENTRY POINT: $$GET COMPONENT DESCRIPTION: The call is $$GET^XUPARAM([,style]) where 'parameter name' is a namespaced name for the parameter to lookup and return the REPLACEMENT value or DEFAULT. The style parameter controls the return value if both of these are empty. Where 'style' controls how missing parameter entries are retuened, Valid value are: "N" to return call name. "V" to return "". missing returns 0. Kernel uses this to allow sites to select local edit templates. i.e. S DR="["_$$GET^XUPARAM("XUEDIT CHARACTERISTICS","N")_"]" VARIABLES: $$GET TYPE: Output VARIABLES DESCRIPTION: Returns user defined data. VARIABLES: parameter name TYPE: Input VARIABLES DESCRIPTION: This is a user defined namespaced name. VARIABLES: style TYPE: Input VARIABLES DESCRIPTION: This optional input controls what is returned if there isn't a replacement value or a default value. Valid values are "N" to return the call name. "V" to return "" missing returns 0. COMPONENT/ENTRY POINT: SET COMPONENT DESCRIPTION: This entry point allows the setting of the REPLACEMENT value in the file for a given entry. VARIABLES: parameter name TYPE: Input VARIABLES DESCRIPTION: This is a user defined namespaced name. VARIABLES: value TYPE: Input VARIABLES DESCRIPTION: This is the replacement value. COMPONENT/ENTRY POINT: LKUP COMPONENT DESCRIPTION: This entry point allows the creation of a entry. S X=$$LKUP^XUPARAM("XUEDIT PARAM","A") VARIABLES: $$LKUP TYPE: Output VARIABLES DESCRIPTION: Returns -1 if the lookup was unsuccessful. Returns a positive value for success. VARIABLES: parameter name TYPE: Input VARIABLES DESCRIPTION: This is a user defined namespaced name. NUMBER: 2543 IA #: 2543 FILE NUMBER: 1 GLOBAL ROOT: DIC( DATE CREATED: OCT 07, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2543 ID: DIC( GLOBAL REFERENCE: DIC(1, FIELD NUMBER: .01 FIELD NAME: FILE LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27833023 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 2544 IA #: 2544 FILE NUMBER: 301.5 GLOBAL ROOT: IVM(301.5, DATE CREATED: OCT 08, 1998 CUSTODIAL PACKAGE: INCOME VERIFICATION MATCH CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2544 ID: IVM(301.5, GLOBAL REFERENCE: IVM(301.5,D0 GLOBAL DESCRIPTION: When specified conditions are met, the entry will be deleted using a DIK call. GLOBAL REFERENCE: IVM(301.5,'B', GLOBAL DESCRIPTION: This reference is used to find an entry in the IVM PATIENT file. GLOBAL REFERENCE: IVM(301.5,D0,0 FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to find the entry in the PATIENT file that needs to be checked to determine if the entry in 301.5 needs to be deleted. GENERAL DESCRIPTION: When the AMIE package deletes entries from the PATIENT file (#2) it also needs to delete entries from the IVM PATIENT file (#301.5). ^IVM(305.1,"B" is used to determined which entries are to be deleted in the IVM PATIENT file. A cleanup is done to delete current entries in the IVM PATIENT file which point to non-existing or non-veterans in the PATIENT file. These entries are deleted using a DIK call. ^IVM(301.5,D0,0 is used to determine if IVM PATIENT file entries should be deleted. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28069779 SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 2545 IA #: 2545 FILE NUMBER: 120.8 GLOBAL ROOT: GMR(120.8, DATE CREATED: APR 26, 2005 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ALLERGY DATA FOR NDF ID: GMR(120.8, GLOBAL REFERENCE: GMR(120.8,IEN,0) FIELD NUMBER: 1 FIELD NAME: GMR ALLERGY LOCATION: 0;3 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: FIELD NUMBER: 120.8 FIELD NAME: DRUG INGREDIENTS ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: FIELD NUMBER: 2 FIELD NAME: DRUG INGREDIENTS GLOBAL REFERENCE: GMR(120.8,DA(1),2,DA,0) FIELD NUMBER: .01 FIELD NAME: DRUG INGREDIENTS LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman GENERAL DESCRIPTION: The data structure of the National Drug File changes with version 4. Allergy Tracking uses a variable pointer to NDF. These data elements must be converted when NDF version 4 is installed. Pharmacy also needs to be able to directly access the DRUG INGREDIENTS multiple in order to update any non-primary ingredients to their associated primary ingredient. Direct global access to ^GMR(120.8,D0,2 is necessary in order to perform this update. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 44743542 SUBSCRIBING PACKAGE: NATIONAL DRUG FILE SUBSCRIBING DETAILS: EDITOR: MONTALI,MICHAEL DBA Comments: JSHARVEY 20061128/ DEACTIVATED AND SET MONTALI AS EDITOR TO CORRECT GLOBAL REFERENCES. DAVE NABER MADE EDITOR BY MONTALI JSHARVEY 20061204/ RE-APPROVED DATE/TIME EDITED: DEC 04, 2006@11:39 ACTION: CONTENT CORRECTED AT THE REQUEST OF: MONTALI,MIKE WITH CONCURRENCE OF: NABER,DAVID NUMBER: 2546 IA #: 2546 DATE CREATED: SEP 22, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SDOE NAME: ACRP INTERFACE TOOLKIT (AIT) ID: SDOE GENERAL DESCRIPTION: The ACRP Interface Toolkit (AIT) is a set of programmer tools that provides access to outpatient encounter data. The toolkit contains Application Programmer Interfaces (APIs) and Remote Procedure Calls (RPCs) that provide access to procedure, diagnosis, provider, and general data related to an encounter. This AIT provides Class I packages, Class III software, and other local code with one highly structured interface to the encounter data. Note: For detail information on each specific API call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 COMPONENT/ENTRY POINT: GETDX(encounter,dx_list[,errors]) COMPONENT DESCRIPTION: Returns diagnoses for an encounter. VARIABLES: encounter TYPE: Input VARIABLES DESCRIPTION: Encounter IEN VARIABLES: dx_list TYPE: Output VARIABLES DESCRIPTION: List of V POV Entries VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: GETPRV(encounter,provider_list[,errors]) COMPONENT DESCRIPTION: Returns providers for an encounter. VARIABLES: encounter TYPE: Input VARIABLES DESCRIPTION: Encounter IEN VARIABLES: provider_list TYPE: Output VARIABLES DESCRIPTION: List of V PROVIDER Entries VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: GETCPT(encounter,cpt_list[,errors]) COMPONENT DESCRIPTION: Returns procedures for an encounter. VARIABLES: encounte TYPE: Input VARIABLES DESCRIPTION: Encounter IEN VARIABLES: cpt_list TYPE: Output VARIABLES DESCRIPTION: List of V CPT Entries VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: $$PRV(encounter[,errors]) COMPONENT DESCRIPTION: Is at least one provider assigned to an encounter? VARIABLES: $$PRV TYPE: Output VARIABLES DESCRIPTION: 1 - Yes, at least one provider is associated with encounter 0 - No, no providers are associated with encounter VARIABLES: encounter TYPE: Input VARIABLES DESCRIPTION: Encounter IEN VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: $$CPT(encounter[,errors]) COMPONENT DESCRIPTION: Is at least one procedure assigned to an encounter? VARIABLES: $$CPT TYPE: Output VARIABLES DESCRIPTION: 1 - Yes, at least one procedure is associated with encounter 0 - No, no procedures are associated with encounter VARIABLES: encounter TYPE: Input VARIABLES DESCRIPTION: Encounter IEN VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: $$DX(encounter[,errors]) COMPONENT DESCRIPTION: Is at least one diagnosis assigned to an encounter? VARIABLES: $$DX TYPE: Output VARIABLES DESCRIPTION: 1 - Yes, at least one diagnosis is associated with encounter 0 - No, no diagnoses are associated with encounter VARIABLES: encounter TYPE: Input VARIABLES DESCRIPTION: Encounter IEN VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: $$FINDPRV(encounter,provider[,errors]) COMPONENT DESCRIPTION: Is a specific provider assigned to an encounter? VARIABLES: $$FINDPRV TYPE: Output VARIABLES DESCRIPTION: 1 - Yes, specific provider is associated with encounter 0 - No, provider is not associated with encounter VARIABLES: encounter TYPE: Input VARIABLES DESCRIPTION: Encounter IEN VARIABLES: provider TYPE: Output VARIABLES DESCRIPTION: Practitioner ID VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: $$FINDDX(encounter,diagnosis[,errors]) COMPONENT DESCRIPTION: Is a specific diagnosis assigned to an encounter? VARIABLES: $$FINDDX TYPE: Output VARIABLES DESCRIPTION: 1 - Yes, specific diagnosis is associated with encounter 0 - No, diagnoisis is not associated with encounter VARIABLES: encounter TYPE: Input VARIABLES DESCRIPTION: Encounter IEN VARIABLES: diagnosis TYPE: Output VARIABLES DESCRIPTION: Diagnosis IEN VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: $$FINDCPT(encounter,cpt[,errors]) COMPONENT DESCRIPTION: Is a specific procedure assigned to an encounter? VARIABLES: $$FINDCPT TYPE: Output VARIABLES DESCRIPTION: 1 - Yes, specific procedure is associated with encounter 0 - No, procedure is not associated with encounter VARIABLES: encounter TYPE: Input VARIABLES DESCRIPTION: Encounter IEN VARIABLES: cpt TYPE: Output VARIABLES DESCRIPTION: CPT IEN VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: $$EXAE(dfn,begin_date,end_date[,flags][,errors]) COMPONENT DESCRIPTION: Returns the first standalone add/edit encounter for a patient in a date range. VARIABLES: $$EXAE TYPE: Output VARIABLES DESCRIPTION: Outpatient Encounter IEN for first standalone encounter found in date range if no encounter exists VARIABLES: dfn TYPE: Input VARIABLES DESCRIPTION: Patient ID VARIABLES: begin_date TYPE: Input VARIABLES DESCRIPTION: Begin Date/Time VARIABLES: end_date TYPE: Input VARIABLES DESCRIPTION: End Date/Time VARIABLES: flags TYPE: Input VARIABLES DESCRIPTION: Search Flags VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: $$GETPDX(encounter[,errors]) COMPONENT DESCRIPTION: Returns the primary diagnosis for an encounter. VARIABLES: $$GETPDX TYPE: Output VARIABLES DESCRIPTION: ien to ^ICD9 for primary dx 0 no primary dx found for encounter VARIABLES: encounter TYPE: Input VARIABLES DESCRIPTION: Encounter IEN VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: $$EXOE(dfn,begin_date,end_date[,flags][,errors]) COMPONENT DESCRIPTION: Returns the first encounter for a patient in a date range. VARIABLES: $$EXOE TYPE: Output VARIABLES DESCRIPTION: Outpatient Encounter ID for first encounter found in date range if no encounter exists VARIABLES: dfn TYPE: Input VARIABLES DESCRIPTION: Patient ID VARIABLES: begin_date TYPE: Input VARIABLES DESCRIPTION: Begin Date/Time VARIABLES: end_date TYPE: Input VARIABLES DESCRIPTION: End Date/Time VARIABLES: flags TYPE: Input VARIABLES DESCRIPTION: Search Flags VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: $$GETLAST(dfn,begin_date[,flags][,errors]) COMPONENT DESCRIPTION: Returns the last standalone add/edit encounter for a patient from a specified begin date. VARIABLES: $$GETLAST TYPE: Output VARIABLES DESCRIPTION: Outpatient Encounter ID for last standalone encounter found after date if no encounter exists VARIABLES: dfn TYPE: Input VARIABLES DESCRIPTION: Patient ID VARIABLES: begin_date TYPE: Input VARIABLES DESCRIPTION: Begin Date/Time VARIABLES: flags TYPE: Input VARIABLES DESCRIPTION: Search Flags VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: GETGEN(encounter,encounter_data[,errors]) COMPONENT DESCRIPTION: Returns the zeroth and other nodes of an outpatient encounter entry. VARIABLES: encounter TYPE: Input VARIABLES DESCRIPTION: Encounter IEN VARIABLES: encounter_data TYPE: Output VARIABLES DESCRIPTION: Encounter Data VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: PARSE(.encounter_data,format,parsed_data[,errors]) COMPONENT DESCRIPTION: Parses the data returned from the GETGEN supported call. VARIABLES: encounter_data TYPE: Input VARIABLES DESCRIPTION: Encounter Data VARIABLES: format TYPE: Input VARIABLES DESCRIPTION: Encounter Parse Format VARIABLES: parsed_data TYPE: Output VARIABLES DESCRIPTION: Encounter Parsed Data VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: $$GETOE COMPONENT DESCRIPTION: Returns the zeroth node of an Outpatient Encounter record. NUMBER: 2547 IA #: 2547 DATE CREATED: SEP 19, 2001 CUSTODIAL PACKAGE: CLINICAL REMINDERS CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRMMST NAME: DBIA2547 ID: PXRMMST STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33449012 KEYWORDS: CLINICAL REMINDERS KEYWORDS: MST COMPONENT/ENTRY POINT: GSYINFO COMPONENT DESCRIPTION: This extrinsic function returns Clinical Reminders MST synchronization data. It takes one argument called TYPE. If TYPE is passed as "I" then data for the initial synchronization is returned. For any other value of TYPE, including null, data for the most recent daily synchronization is returned. The format of the returned data is date/time^number of updates. Here is an example of how to use this API: S X=$$GSYINFO^PXRMMST("I") for initial synchronization data S X=$$GSYINFO^PXRMMST for most recent daily synchronization data VARIABLES: TYPE TYPE: Input SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING DETAILS: PIMS needs to be able to determine if the Clinical Reminders MST synchronization has taken place. This API provides a method to get the data and time and number of updates made both for the initial synchronization and the most recent daily synchronization. NUMBER: 2548 IA #: 2548 DATE CREATED: SEP 22, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SDQ NAME: ACRP INTERFACE TOOLKIT (AIT) ID: SDQ GENERAL DESCRIPTION: The ACRP Interface Toolkit (AIT) is a set of programmer tools that provides access to outpatient encounter data. The toolkit contains Application Programmer Interfaces (APIs) and Remote Procedure Calls (RPCs) that provide access to procedure, diagnosis, provider, and general data related to an encounter. This AIT provides Class I packages, Class III software, and other local code with one highly structured interface to the encounter data. Note: For detail information on each specific API call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 COMPONENT/ENTRY POINT: OPEN(.query[,errors]) COMPONENT DESCRIPTION: Open a Query Object instance. VARIABLES: query TYPE: Output VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: CLOSE(.query[,errors]) COMPONENT DESCRIPTION: Close a Query Object instance. VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: PAT(query,.dfn,action[,errors]) COMPONENT DESCRIPTION: Set or retrieve Patient property of a Query Object instance. VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: dfn TYPE: Input VARIABLES DESCRIPTION: Patient ID VARIABLES: action TYPE: Input VARIABLES DESCRIPTION: Action VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: DATE(query,.begin_date,.end_date,action[,errors]) COMPONENT DESCRIPTION: Set or retrieve Date Range property of a Query Object instance. VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: begin_date TYPE: Input VARIABLES DESCRIPTION: Begin Date/Time VARIABLES: end-date TYPE: Input VARIABLES DESCRIPTION: End Date/Time VARIABLES: action TYPE: Input VARIABLES DESCRIPTION: Action VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: FILTER(query,.filter,action[.errors]) COMPONENT DESCRIPTION: Set or retrieve Filter property of a Query Object instance. VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: filter TYPE: Both VARIABLES DESCRIPTION: Encounter Query Filter VARIABLES: action TYPE: Input VARIABLES DESCRIPTION: Action VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: current encounter entry number VARIABLES: Y0 TYPE: Output VARIABLES DESCRIPTION: zeroth node of current encounter entry (only supported fields) COMPONENT/ENTRY POINT: VISIT(query,.visit,action[,errors]) COMPONENT DESCRIPTION: Set or retrieve Visit property of a Query Object instance. VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: visit TYPE: Input VARIABLES DESCRIPTION: Visit IEN VARIABLES: action TYPE: Input VARIABLES DESCRIPTION: Action VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: INDEX(query,.index,action[,errors]) COMPONENT DESCRIPTION: Set or retrieve Index property of a Query Object instance. VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: index TYPE: Input VARIABLES DESCRIPTION: Encounter Query Index VARIABLES: action TYPE: Input VARIABLES DESCRIPTION: Action VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: $$EOF(query[,errors]) COMPONENT DESCRIPTION: Is cursor positioned on the last encounter record in the Query Object result set? VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] VARIABLES: $$EOF TYPE: Output VARIABLES DESCRIPTION: 1 - Yes, query cursor is at the last record or no records exist for query 0 - No, query cursor is not at last record COMPONENT/ENTRY POINT: $$BOF(query[,errors]) COMPONENT DESCRIPTION: Is cursor positioned on the first encounter record in the Query Object result set? VARIABLES: $$BOF TYPE: Output VARIABLES DESCRIPTION: 1 - Yes, query cursor is at the first record or no records exist for query 0 - No, query cursor is not at first record VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: ACTIVE(query,.status,action[,errors] COMPONENT DESCRIPTION: Set or retrieve Active property of a Query Object instance. VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: status TYPE: Input VARIABLES DESCRIPTION: Encounter Query Active Status VARIABLES: action TYPE: Input VARIABLES DESCRIPTION: Action VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [otional] COMPONENT/ENTRY POINT: $$COUNT(query[,errors]) COMPONENT DESCRIPTION: Returns the number of encounter records in a Query Object result set. VARIABLES: $$COUNT TYPE: Output VARIABLES DESCRIPTION: count of records in query's result set 0 no records in the query's result set invalid query or query not active VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: FIRST(query[,errors]) COMPONENT DESCRIPTION: Positions the cursor at the first encounter record in the Query Object result set. VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: LAST(query[,errors]) COMPONENT DESCRIPTION: Positions the cursor at the last encounter record in the Query Object result set. VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: NEXT(query[,errors]) COMPONENT DESCRIPTION: Positions the cursor at the next encounter record in the Query Object result set. VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: PRIOR(query[,errors]) COMPONENT DESCRIPTION: Positions the cursor at the previous encounter record in the Query Object result set. VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: REFRESH(query[,errors]) COMPONENT DESCRIPTION: Refresh the Query Object result set. VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: $$GETENTRY(query[,errors]) COMPONENT DESCRIPTION: Returns the internal entry number of the Outpatient Encounter (#409.68) file for the encounter record at the current cursor position of the Query Object result set. VARIABLES: $$GETENTRY TYPE: Output VARIABLES DESCRIPTION: ID for entry if no entries in result set VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optinal] COMPONENT/ENTRY POINT: SCAN(query[,direction][,errors]) COMPONENT DESCRIPTION: Scans encounter records that meet the criteria defined by the properties of the Query Object instance. VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: scan_direction TYPE: Input VARIABLES DESCRIPTION: Direction [optional] VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] COMPONENT/ENTRY POINT: SCANCB(query,.callback,action[,errors]) COMPONENT DESCRIPTION: Set or retrieve Callback property of a Query Object instance. VARIABLES: query TYPE: Input VARIABLES DESCRIPTION: Encounter Query Handle VARIABLES: callback TYPE: Input VARIABLES DESCRIPTION: Scan Callback Logic VARIABLES: action TYPE: Input VARIABLES DESCRIPTION: Action VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] NUMBER: 2552 IA #: 2552 DATE CREATED: SEP 22, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SDQUT NAME: ACRP INTERFACE TOOLKIT (AIT) ID: SDQUT GENERAL DESCRIPTION: The ACRP Interface Toolkit (AIT) is a set of programmer tools that provides access to outpatient encounter data. The toolkit contains Application Programmer Interfaces (APIs) and Remote Procedure Calls (RPCs) that provide access to procedure, diagnosis, provider, and general data related to an encounter. This AIT provides Class I packages, Class III software, and other local code with one highly structured interface to the encounter data. Note: For detail information on each specific API call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 COMPONENT/ENTRY POINT: $$ERRCHK([errors]) COMPONENT DESCRIPTION: Does current error array contain any errors? VARIABLES: $$ERRCHK TYPE: Output VARIABLES DESCRIPTION: 1 - Yes, at least one error is in the error array 0 - No, no errors are in the error array VARIABLES: errors TYPE: Output VARIABLES DESCRIPTION: Error Array [optional] NUMBER: 2553 IA #: 2553 DATE CREATED: SEP 22, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE ASSIGNED A DIAGNOSIS REMOTE PROCEDURE: SDOE ASSIGNED A DIAGNOSIS GENERAL DESCRIPTION: This remote procedure call (RPC) returns a boolean indicator on whether at least one diagnosis has been associated with an encounter. --------------------------------------------------------------------- This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2554 IA #: 2554 DATE CREATED: SEP 22, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE ASSIGNED A PROCEDURE REMOTE PROCEDURE: SDOE ASSIGNED A PROCEDURE GENERAL DESCRIPTION: This remote procedure call (RPC) returns a boolean indicator on whether at least one procedure has been associated with an encounter. --------------------------------------------------------------------- This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2555 IA #: 2555 DATE CREATED: SEP 22, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE ASSIGNED A PROVIDER REMOTE PROCEDURE: SDOE ASSIGNED A PROVIDER GENERAL DESCRIPTION: This remote procedure call (RPC) returns a boolean indicator on whether at least one provider has been associated with an encounter. --------------------------------------------------------------------- This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2556 IA #: 2556 DATE CREATED: SEP 22, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE FIND DIAGNOSIS REMOTE PROCEDURE: SDOE FIND DIAGNOSIS GENERAL DESCRIPTION: This remote procedure call (RPC) returns a boolean indicator on whether a specific diagnosis has been associated with an encounter. --------------------------------------------------------------------- This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2557 IA #: 2557 DATE CREATED: SEP 22, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE FIND FIRST ENCOUNTER REMOTE PROCEDURE: SDOE FIND FIRST ENCOUNTER GENERAL DESCRIPTION: This remote procedure call (RPC) returns the internal entry number of an Outpatient Encounter file (#409.68) entry for the first encounter for a patient in a specified date range. --------------------------------------------------------------------- This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2558 IA #: 2558 DATE CREATED: SEP 22, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE FIND FIRST STANDALONE REMOTE PROCEDURE: SDOE FIND FIRST STANDALONE GENERAL DESCRIPTION: This remote procedure call (RPC) returns the internal entry number of an Outpatient Encounter file (#409.68) entry for the first standalone add/edit encounter for a patient in a specified date range. --------------------------------------------------------------------- This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2559 IA #: 2559 DATE CREATED: SEP 22, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE FIND LAST STANDALONE REMOTE PROCEDURE: SDOE FIND LAST STANDALONE GENERAL DESCRIPTION: This remote procedure call (RPC) returns the internal entry number of an Outpatient Encounter file (#409.68) entry for the last standalone add/edit encounter for a patient in a specified date range. --------------------------------------------------------------------- This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2560 IA #: 2560 DATE CREATED: SEP 22, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE FIND PROCEDURE REMOTE PROCEDURE: SDOE FIND PROCEDURE GENERAL DESCRIPTION: This remote procedure call (RPC) returns a boolean indicator on whether a specific procedure has been associated with an encounter. --------------------------------------------------------------------- This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2561 IA #: 2561 DATE CREATED: SEP 22, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE FIND PROVIDER REMOTE PROCEDURE: SDOE FIND PROVIDER GENERAL DESCRIPTION: This remote procedure call (RPC) returns a boolean indicator on whether a specific provider has been associated with an encounter. --------------------------------------------------------------------- This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2563 IA #: 2563 DATE CREATED: SEP 23, 1998 CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: Linked option to CIRN GENERAL DESCRIPTION: Registration patch DG*5.3*172 is transporting in a KIDS build the CIRN option, CIRN Pre-Implementation Menu (RGPR PRE-IMP MENU), as a link for menu items. STATUS: Active MAIL MESSAGE: 27940634 SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 2564 IA #: 2564 DATE CREATED: SEP 23, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE GET DIAGNOSES REMOTE PROCEDURE: SDOE GET DIAGNOSES GENERAL DESCRIPTION: This remote procedure call (RPC) returns an array of diagnoses for an encounter. ------------------------------------------------------------------ This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2565 IA #: 2565 DATE CREATED: SEP 23, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE GET GENERAL DATA REMOTE PROCEDURE: SDOE GET GENERAL DATA GENERAL DESCRIPTION: This remote procedure call (RPC) returns the zeroth and other nodes of an outpatient encounter. ------------------------------------------------------------------ This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2566 IA #: 2566 DATE CREATED: SEP 23, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE GET PRIMARY DIAGNOSIS REMOTE PROCEDURE: SDOE GET PRIMARY DIAGNOSIS CREATOR: THOMPSON,ANDREW R GENERAL DESCRIPTION: This remote procedure call (RPC) returns the internal entry number of the primary diagnosis code (^ICD9) for an encounter. ------------------------------------------------------------------ This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. These files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 DBA Comments: Deactivated 2566 on 4/5/12 so that Andrew Thompson can make the definition more generic to refer to diagnosis as ICD (instead of ICD9). This change supports the ICD-10 Remediation for Scheduling project. The following is the timeline for testing the changes. Below are the testing dates for ICD-10 Remediation for Scheduling User Functionality Test - 6/22/12-6/28/12 ITE Test (IV&V) - 6/20/12-7/3/12 Initial Operating Capability Test (IOC) - 8/30/12-9/20/12 Activated 2566 on 4/10/12. DATE ACTIVATED: APR 10, 2012 DATE/TIME EDITED: APR 05, 2012@18:25 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: THOMPSON,ANDREW WITH CONCURRENCE OF: GANDHI,KAVITA DATE/TIME EDITED: APR 10, 2012@13:45 ACTION: APPROVED AT THE REQUEST OF: THOMPSON,ANDREW WITH CONCURRENCE OF: GANDHI,KAVITA REMINDER: APR 12, 2012 NUMBER: 2567 IA #: 2567 DATE CREATED: SEP 23, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE GET PROCEDURES REMOTE PROCEDURE: SDOE GET PROCEDURES GENERAL DESCRIPTION: This remote procedure call (RPC) returns a subscripted array of procedures for an encounter. ------------------------------------------------------------------ This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2568 IA #: 2568 DATE CREATED: SEP 23, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE GET PROVIDERS REMOTE PROCEDURE: SDOE GET PROVIDERS GENERAL DESCRIPTION: This remote procedure call (RPC) returns a subscripted array of providers for an encounter. ------------------------------------------------------------------ This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2569 IA #: 2569 DATE CREATED: SEP 23, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE GET ZERO NODE REMOTE PROCEDURE: SDOE GET ZERO NODE GENERAL DESCRIPTION: This remote procedure call (RPC) returns the zeroth node of an outpatient encounter. ------------------------------------------------------------------ This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2570 IA #: 2570 DATE CREATED: SEP 23, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE LIST ENCOUNTERS FOR DATES REMOTE PROCEDURE: SDOE LIST ENCOUNTERS FOR DATES GENERAL DESCRIPTION: This remote procedure call (RPC) returns a list of outpatient encounters for a date range. ------------------------------------------------------------------ This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2571 IA #: 2571 DATE CREATED: SEP 23, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE LIST ENCOUNTERS FOR PAT REMOTE PROCEDURE: SDOE LIST ENCOUNTERS FOR PAT GENERAL DESCRIPTION: This remote procedure call (RPC) returns a list of outpatient encounters for a specified patient and specified date range. ------------------------------------------------------------------ This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2572 IA #: 2572 DATE CREATED: SEP 23, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE LIST ENCOUNTERS FOR VISIT REMOTE PROCEDURE: SDOE LIST ENCOUNTERS FOR VISIT GENERAL DESCRIPTION: This remote procedure call (RPC) returns a list of outpatient encounters for a specified PCE visit. ------------------------------------------------------------------ This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2573 IA #: 2573 DATE CREATED: SEP 23, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: SDOE PARSE GENERAL DATA REMOTE PROCEDURE: SDOE PARSE GENERAL DATA GENERAL DESCRIPTION: This remote procedure call (RPC) will parse the data returned by SDOE GET GENERAL DATA remote procedure call into individual field nodes. ------------------------------------------------------------------ This RPC is part of the ACRP Interface Toolkit (AIT). The AIT is a set of programmer tools that provides access to outpatient encounter data. Note: For detail information on this RPC call, see the following AIT documentation files: sd_53_p131_tooldoc.doc or sd_53_p131_tooldoc.pdf. Theses files are distributed as part of patch SD*5.3*131. Also, the documentation is available on-line at the following URL: http://152.127.1.95/softserv/mip/wr/acrpapi.htm STATUS: Active MAIL MESSAGE: 27948894 NUMBER: 2574 IA #: 2574 DATE CREATED: SEP 23, 1998 CUSTODIAL PACKAGE: NATIONAL DRUG FILE USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSNAPIS NAME: ADDITIONAL APIS FOR NDF ID: PSNAPIS GENERAL DESCRIPTION: This DBIA describes additional Application Programmer Interfaces (APIs) for the National Drug File. APIs described here are in addition to those described in DBIA # 2531. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 39783108 COMPONENT/ENTRY POINT: TTOG COMPONENT DESCRIPTION: S X=$$TTOG^PSNAPIS(TRADE,.LIST) where TRADE is a free text trade name and LIST is an array defined by the calling application returns LIST(IEN)=IEN^GENERIC NAME where IEN is the internal entry number in File #50.6 and GENERIC NAME is the .01 field of that file for every entry which has the given trade name. Also returns X as the number of entries in LIST. COMPONENT/ENTRY POINT: CLIST COMPONENT DESCRIPTION: S X=$$CLIST^PSNAPIS(DA,.LIST) where DA is an internal entry number in File #50.6 and LIST is an array defined by the calling application returns LIST(IEN)=IEN^CLASS where IEN is the internal entry number in File #50.605 and CLASS is the 5 character class code for every class associated with that entry in File #50.6. Also returns X as the number of entries in LIST. COMPONENT/ENTRY POINT: TGTOG COMPONENT DESCRIPTION: S X=$$TGTOG^PSNAPIS(NAME) where NAME is a free text entry returns X=IEN from the VA GENERIC file (#50.6) if NAME is either a valid Name from the VA GENERIC file (#50.6) or if NAME is a valid Trade Name from the NDC/UPN file (#50.67). Returns X=0 otherwise. COMPONENT/ENTRY POINT: TGTOG2 COMPONENT DESCRIPTION: S X=$$TGTOG2^PSNAPIS(NAME,.LIST) returns LIST(IEN)=IEN^GENERIC NAME where IEN is the internal entry number in File #50.6 and GENERIC NAME is the .01 field of that entry for all entries for which NAME is a partial or exact match to either the trade name or the generic name. Also returns X as the number of entries in LIST. COMPONENT/ENTRY POINT: CIRN2 COMPONENT DESCRIPTION: S X=$$CIRN2^PSNAPIS(P1,P3,.LIST) where P1 and P3 are the first and third pieces of the ND node in File #50 and LIST is an array defined by the calling application returns LIST(J)=NDC where J is a simple index and NDC is a twelve character National Drug Code (NDC) for all NDCs associated with the product specified by P1 and P3. Also returns X as the number of entries in LIST. COMPONENT/ENTRY POINT: CLASS2 COMPONENT DESCRIPTION: S X=$$CLASS2^PSNAPIS(IEN) where IEN is an internal entry number in File #50.605 returns X as the first two pieces of the zero node in that entry. COMPONENT/ENTRY POINT: FORMI COMPONENT DESCRIPTION: S X=$$FORMI^PSNAPIS(P1,P3) where P1 and P3 are the first and third pieces of the "ND" node in File #50 for a selected entry returns X=1 if the item is on the National Formulary, X=0 otherwise. COMPONENT/ENTRY POINT: FORMR COMPONENT DESCRIPTION: S X=$$FORMR^PSNAPIS(P1,P3) where P1 and P3 are the first and third pieces of the "ND" node in File #50 for a selected entry returns X=1 if there are restrictions placed on the item, X=0 otherwise. COMPONENT/ENTRY POINT: CMOP COMPONENT DESCRIPTION: S X=$$CMOP^PSNAPIS(CODE) where code is a five character CMOP identifier (e. g. A0105) returns X equal the corresponding product name if CODE is a valid identifier, null otherwise. COMPONENT/ENTRY POINT: FORMRX COMPONENT DESCRIPTION: S X=$$FORMRX^PSNAPIS(DA,K,.LIST) where DA and K are the first and third pieces of the ND node in File #50 for the chosen drug returns X=1 if there are formulary restrictions, 0 if there are not. Also, if there are restrictions, returns LIST as the word-processing field describing these restrictions. COMPONENT/ENTRY POINT: $$DDIEX(VAR1,VAR2) VARIABLES: VAR1 TYPE: Input VARIABLES DESCRIPTION: piece one of the "ND" node of ^PSDRUG file 50 NATIONAL DRUG FILE ENTRY field 20 VARIABLES: VAR2 TYPE: Input VARIABLES DESCRIPTION: piece three of the "ND" node of ^PSDRUG file 50 PSNDF VA PRODUCT NAME ENTRY field 22 VARIABLES: $$DDIEX TYPE: Output VARIABLES DESCRIPTION: 1 indicates that a drug has been exempted from drug-drug interaction order checking. 0 indicates that a drug is not exempted from drug-drug interaction order checking. NUMBER: 2575 IA #: 2575 FILE NUMBER: 100.02 GLOBAL ROOT: ORD(100.02 DATE CREATED: SEP 23, 1998 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: NATURE OF ORDER FILE ACCESS ID: ORD(100.02 CREATOR: MALMROSE,CARY GLOBAL REFERENCE: ORD(100.02,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: CODE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Reference to Nature of Order (100.02) file. This DBIA allows a direct global read of the NAME (.01) and CODE (.02) fields of the NATURE OF ORDER (100.02) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27948382 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas DATE ACTIVATED: JAN 05, 2011 DATE/TIME EDITED: JAN 04, 2011@11:19 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: OSTRANDER,ROBIN WITH CONCURRENCE OF: BUECHLER,MELANIE DATE/TIME EDITED: JAN 05, 2011@09:18 ACTION: APPROVED AT THE REQUEST OF: OSTRANDER,ROBIN WITH CONCURRENCE OF: MALMROSE,CARY NUMBER: 2576 IA #: 2576 FILE NUMBER: 100.03 GLOBAL ROOT: ORD(100.03 DATE CREATED: SEP 23, 1998 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2576 ID: ORD(100.03 GLOBAL REFERENCE: ORD(100.03,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: CODE LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: ORD(100.03,'C',CODE FIELD NUMBER: .06 FIELD NAME: CODE LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Reference to Order Reason (100.03) file. This DBIA allows a direct global read of the NAME (.01) field of the ORDER REASON (100.03) file. Access is also allowed to the "C" cross reference on the file to look for coded entries. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27948437 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 2581 IA #: 2581 FILE NUMBER: 19 GLOBAL ROOT: DIC(19 DATE CREATED: SEP 24, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: SERVER ACTION edit during install ID: DIC(19 GLOBAL REFERENCE: DIC(19 FIELD NUMBER: 221 FIELD NAME: SERVER ACTION LOCATION: 220;2 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: SERVER ACTION (#221) field. GLOBAL DESCRIPTION: OPTION file (#19) GENERAL DESCRIPTION: This integration agreement is for setting the SERVER ACTION field (#221) of the OPTION file (#19) while a patch to the server logic is being installed. The SERVER ACTION field will be reset in a post-init to its original value. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27945057 SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring NUMBER: 2586 IA #: 2586 FILE NUMBER: 123 GLOBAL ROOT: GMR(123, DATE CREATED: SEP 25, 1998 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR references to GMR(123, ID: GMR(123, GLOBAL REFERENCE: GMR(123,DA,0) FIELD NUMBER: .01 FIELD NAME: FILE ENTRY DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: PATIENT NAME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: OE/RR FILE NUMBER LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: TO SERVICE LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: PROCEDURE/REQUEST TYPE LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5 FIELD NAME: URGENCY LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6 FIELD NAME: PLACE OF CONSULTATION LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 11 FIELD NAME: ATTENTION LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 10 FIELD NAME: SENDING PROVIDER LOCATION: 0;14 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 13 FIELD NAME: REQUEST TYPE LOCATION: 0;17 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 14 FIELD NAME: SERVICE RENDERED AS IN OR OUT LOCATION: 0:18 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 16 FIELD NAME: TIU RESULT NARRATIVE LOCATION: 0;20 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: GMR(123,DA,20) FIELD NUMBER: 20 FIELD NAME: REASON FOR REQUEST LOCATION: 20 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Obtains word processing text from REASON FOR REQUEST field. GLOBAL REFERENCE: GMR(123,DA,30) FIELD NUMBER: 30 FIELD NAME: PROVISIONAL DIAGNOSIS LOCATION: 30;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: GMR(123,DA,50) FIELD NUMBER: 50 FIELD NAME: ASSOCIATED RESULTS LOCATION: 50 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Obtains ASSOCIATED RESULTS data and references B index of multiple GLOBAL REFERENCE: GMR(123,DA,50,'B' GLOBAL REFERENCE: GMR(123,DA,51,'B' GENERAL DESCRIPTION: This DBIA serves as documentation of references made from the OE/RR package to the REQUEST/CONSULTATION file (#123). Please note that the OE/RR v3 orders conversion also deletes entries in GMR(123,. VIEWER: SCHLEHUBER,PAM STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: added 5/26/2011 DATE/TIME EDITED: MAY 26, 2011@17:30 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: TRAXLER,FRANK WITH CONCURRENCE OF: THOMPSON,WILLIAM NUMBER: 2588 IA #: 2588 FILE NUMBER: 70 GLOBAL ROOT: RADPT( DATE CREATED: SEP 25, 1998 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OR use of RADPT('AO' x-ref ID: RADPT( GLOBAL REFERENCE: RADPT('AO' GLOBAL DESCRIPTION: The OE/RR v3 Orders Conversion performs a $D check on RADPT('AO', to see if a pointer exists from file 70 to the RAD/NUC MED ORDERS file (#75.1). Care Management also uses a $D check of this index to determine if the Radiology/Nuclear Medicine order whose results have just been viewed and acknowledged has an outstanding notification that may now be deleted; this index links the case number used by the alert to the order number available within Care Management. GENERAL DESCRIPTION: This reference is used by the OE/RR v3 orders conversion and the Care Management application, to link a case number to an order. VIEWER: SCHLEHUBER,PAM STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 36807889 GOOD ONLY FOR VERSION: OE/RR v3 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CARE MANAGEMENT ISC: Salt Lake City NUMBER: 2589 IA #: 2589 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: AUG 31, 2001 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: NEW PERSON editing ID: VA(200, GLOBAL REFERENCE: VA(200, FIELD NUMBER: .135 FIELD NAME: COMMERCIAL PHONE LOCATION: .13;5 ACCESS: Write w/Fileman GENERAL DESCRIPTION: With patch RG*1*21, Master Patient Index/Patient Demographics exports a new option, Add/Edit Point of Contact [RG UPDATE POINT OF CONTACT]. This option allows a facility to update the administrative, IRM and HL7 points of contact name and phone number. This information is sent to the MPI/PD Data Management staff so that they can update the website. The point of contact names reside in the CIRN SITE PARAMETER (#991.8) file and point to the NEW PERSON (#200) file. The option edits the OFFICE PHONE (#.132) field in the NEW PERSON (#200) file, via a FileMan ^DIE call for the identified point of contact. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33335322 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham NUMBER: 2590 IA #: 2590 DATE CREATED: SEP 30, 1998 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SDUTL2 NAME: SD OUTPATIENT GAF SCORE UTILS ID: SDUTL2 GENERAL DESCRIPTION: The purpose of these API's is to facilitate the entry of Global Assessment of Function (GAF) scores to the Mental Health package from outpatient encounters. VHA Directive, 97-059, dated November 25, 1997, "Instituting Global Assessment of Function (GAF) Scores in Axis V Mental Health Patients", provides guidelines for the collection of these GAF scores. These API's will be used to (1) return whether a new GAF score is required for an outpatient and (2) whether the outpatient encounter clinic is a Mental Health clinic for which GAF scores must be collected. These API's have been added to the routine: SDUTL2. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28007493 COMPONENT/ENTRY POINT: NEWGAF(DFN) COMPONENT DESCRIPTION: Entry point NEWGAF^SDUTL2(DFN) returns whether a GAF score is required for a patient, and if one is required, returns the date of the last score, the score, and the IEN of the provider who made the determination. The internal entry number is passed into the call as variable DFN. The determination and latest occurrence of the GAF data are then passed back in the form of a concatenated string in the following format: -1 : New GAF required and no previous data 1 : New GAF required and previous data, the second piece will contain the previous GAF score, the third piece will contain the date of the score, and the fourth piece will contain the IEN of the provider w determined the GAF score. 0 : A new GAF is not required VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Contains the Internal entry number of the patient in the PATIENT File, #2. VARIABLES: SDGAF TYPE: Output VARIABLES DESCRIPTION: Contains the results COMPONENT/ENTRY POINT: MHCLIN(SDCL,SDSC) COMPONENT DESCRIPTION: Entry point MHCLIN^SDUTL2(SDCL,SDSC) returns whether the clinic for the encounter is a mental health clinic or not. The current criterion for this determination is a stop code that starts with a "5", excluding the following codes: 526, 527, 528, 530, 536, 537, 542, 546, 579. Either a pointer to the HOSPITAL LOCATION File, #44, or a pointer to the CLINIC STOP File, #40.7, must be passed into the call. If neither is passed in, the default result will be "0". If the clinic or the clinics stop match the criterion, the call will pass back a "1" to indicate a mental health clinic, otherwise a "0" will be passed back. VARIABLES: SDCL TYPE: Input VARIABLES DESCRIPTION: Contains the internal entry number of the clinic VARIABLES: SDSC TYPE: Input VARIABLES DESCRIPTION: Contains the internal entry number of the CLINIC STOP File, #40.7 VARIABLES: SDMH TYPE: Output VARIABLES DESCRIPTION: Contains the results NUMBER: 2592 IA #: 2592 DATE CREATED: SEP 30, 1998 CUSTODIAL PACKAGE: VA FILEMAN USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TRAVERSE DD FOR FILE CONVERSION GLOBAL REFERENCE: DD(11,0,'PT',DO,D1) GLOBAL REFERENCE: DD(13,0,'PT',DO,D1) GLOBAL REFERENCE: DD(D0,0,'UP') GENERAL DESCRIPTION: The post-install routine in the Registration patch DG*5.3*172 is looping through the "PT" node in both the MARITAL STATUS file (#11) and RELIGION file (#13) to convert the non-standard entries into standard entries. The non-standard entries are deleted after the conversion. However, the conversion cannot convert entries within a subfile, so the patch identifies the subfile within the "PT" node and traverses back through the "UP" nodes looking at the subfile zero nodes to report the subfile NAMES that could not be converted. This information is placed in a mail message which is reported back to the installer of patch DG*5.3*172. STATUS: Active MAIL MESSAGE: 27857102 SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 2596 IA #: 2596 FILE NUMBER: 101 GLOBAL ROOT: ORD(101, DATE CREATED: OCT 27, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Audit File Reference to Protocol File ID: ORD(101, GLOBAL REFERENCE: ORD(101, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: ITEM TEXT LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 771 FIELD NAME: PROCESSING ROUTINE LOCATION: 771;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: CIRN made a request to the FileMan Development Team to add to the Audit File a field that would keep track of what menu Protocol was used to change the data being audited. STATUS: Active MAIL MESSAGE: 28218056 SUBSCRIBING PACKAGE: VA FILEMAN ISC: Oakland SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: MASTER PATIENT INDEX NUMBER: 2597 IA #: 2597 FILE NUMBER: 9000010.12 GLOBAL ROOT: AUPNVSK DATE CREATED: OCT 14, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2597 ID: AUPNVSK GLOBAL REFERENCE: AUPNVSK(D0,0) FIELD NUMBER: .01 FIELD NAME: SKIN TEST LOCATION: 0,1 ACCESS: Read w/Fileman FIELD NUMBER: .02 FIELD NAME: PATIENT NAME LOCATION: 0,2 ACCESS: Read w/Fileman FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0,3 ACCESS: Read w/Fileman FIELD NUMBER: .04 FIELD NAME: RESULTS LOCATION: 0,4 ACCESS: Read w/Fileman FIELD NUMBER: .05 FIELD NAME: READING LOCATION: 0,5 ACCESS: Read w/Fileman FIELD NUMBER: .06 FIELD NAME: DATE READ LOCATION: 0,6 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The CIRN Skin Tests (PCE) data extraction routine (^RGHOSKN - HL7 Message Generation for Skin Tests Results), makes several references to fields in the SKIN TEST V file (#9000010.12), for the purpose of creating the HL7 transmission records. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28100727 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2598 IA #: 2598 FILE NUMBER: 9000010 GLOBAL ROOT: AUPNVSIT DATE CREATED: OCT 14, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2598 ID: AUPNVSIT GLOBAL REFERENCE: AUPNVSIT(D0,0) FIELD NUMBER: .01 FIELD NAME: VISIT/ADMIT DATE&TIME LOCATION: 0,1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: For all CIRN PCE related packages, including: SKIN TESTS, IMMUNIZATIONS, HEALTH FACTORS, TREATMENTS, and MEASUREMENTS, the historical load routine (RGHOVFB - Historical Load of V File Data), makes a reference to the VISIT file (#9000010), for the purpose of setting an entry in the CIRN processing queue. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28100727 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2599 IA #: 2599 FILE NUMBER: 9000010.23 GLOBAL ROOT: AUPNVHF DATE CREATED: OCT 14, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2599 ID: AUPNVHF GLOBAL REFERENCE: AUPNVHF(D0,0) FIELD NUMBER: .01 FIELD NAME: HEALTH FACTOR LOCATION: 0,1 ACCESS: Read w/Fileman FIELD NUMBER: .02 FIELD NAME: PATIENT NAME LOCATION: 0,2 ACCESS: Read w/Fileman FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0,3 ACCESS: Read w/Fileman FIELD NUMBER: .04 FIELD NAME: LEVEL/SEVERITY LOCATION: 0,4 ACCESS: Read w/Fileman GLOBAL REFERENCE: AUPNVHF(D0,12) FIELD NUMBER: 1201 FIELD NAME: EVENT DATE AND TIME LOCATION: 12,1 ACCESS: Read w/Fileman FIELD NUMBER: 1202 FIELD NAME: ORDERING PROVIDER LOCATION: 12,2 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28113279 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2600 IA #: 2600 FILE NUMBER: 9000010.11 GLOBAL ROOT: AUPNVIMM DATE CREATED: OCT 15, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2600 ID: AUPNVIMM GLOBAL REFERENCE: AUPNVIMM(D0,0) FIELD NUMBER: .01 FIELD NAME: IMMUNIZATION LOCATION: 0,1 ACCESS: Read w/Fileman FIELD NUMBER: .02 FIELD NAME: PATIENT NAME LOCATION: 0,2 ACCESS: Read w/Fileman FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0,3 ACCESS: Read w/Fileman FIELD NUMBER: .04 FIELD NAME: SERIES LOCATION: 0,4 ACCESS: Read w/Fileman FIELD NUMBER: 1201 FIELD NAME: EVENT DATE AND TIME LOCATION: 12,1 ACCESS: Read w/Fileman FIELD NUMBER: 1202 FIELD NAME: ORDERING PROVIDER LOCATION: 12,2 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The CIRN Immunizations (PCE) data extraction routine (^RGHOIMM - HL7 Message Generation for Immunization Results), makes several references to fields in the IMMUNIZATION V file (#9000010.11), for the purpose of creating the HL7 transmission records. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28120578 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2602 IA #: 2602 FILE NUMBER: 1.1 GLOBAL ROOT: DIA DATE CREATED: OCT 02, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: READING AUDIT FILE ID: DIA CREATOR: ORMSBY,SKIP GLOBAL REFERENCE: DIA(File number,entry nmber FIELD NUMBER: .02 FIELD NAME: DATE/TIME RECORDED LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: FIELD NUMBER LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .01 FIELD NAME: INTERNAL ENTRY NUMBER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: OLD VALUE LOCATION: ; ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2.1 FIELD NAME: OLD INTERNAL VALUE LOCATION: 2.1;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: NEW VALUE LOCATION: ; ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3.1 FIELD NAME: NEW INTERNAL VALUE LOCATION: 3.1;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .001 FIELD NAME: NUMBER LOCATION: ACCESS: Read w/Fileman FIELD NUMBER: .04 FIELD NAME: USER LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .05 FIELD NAME: RECORD ADDED LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: ENTRY NAME LOCATION: ; ACCESS: Read w/Fileman FIELD NUMBER: 1.1 FIELD NAME: FIELD NAME LOCATION: ; ACCESS: Read w/Fileman FIELD NUMBER: 2.2 FIELD NAME: DATATYPE OF OLD VALUE LOCATION: 2.1;2 ACCESS: Read w/Fileman FIELD NUMBER: 3.2 FIELD NAME: DATATYPE OF NEW VALUE LOCATION: 3.1;2 ACCESS: Read w/Fileman FIELD NUMBER: 4.1 FIELD NAME: MENU OPTION USED LOCATION: 4.1;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4.2 FIELD NAME: PROTOCOL or OPTION USED LOCATION: 4.1;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: 'C' GLOBAL DESCRIPTION: DIRECT READ ACCESS TO THE 'C' CROSS-REFERENCE GENERAL DESCRIPTION: The NDF Management System uses entries in the AUDIT file (#1.1) to track changes made to files involved with NDF and to send these changes to VAMCs using KIDS. To this end, the NDF Management System requests permission to do direct global reads of entries in File #1.1 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 24791067 SUBSCRIBING PACKAGE: NATIONAL DRUG FILE ISC: Birmingham SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: MASTER PATIENT INDEX SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING DETAILS: ADDED 9/27/07 SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING DETAILS: Added Lab as new Subscriber 08/15/13. Lab patch LR*5.2*425 needs to loop through the entries in the Audit file for file 60 (LABORATORY TEST). SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING DETAILS: Effective with OR*3*250 (part of CPRSv30), Order Entry/Results Reporting (OE/RR) is a subscribing package to ICR #2602 READING AUDIT FILE. The DEA has a regulatory requirement that sites audit the logical access control of electronic prescribing of controlled substances (ePCS). The logical access control data is stored in the OE/RR EPCS PARAMETERS file (#100.7) and uses FileMan's audit functionality to audit changes within that file. Unfortunately, there are some sites that prevent clinical applications coordinator staff from accessing FileMan to view and report on this audit data. Therefore, OE/RR has a requirement to create a report that will display the audit data to the user regardless of whether the user has FileMan access or not. DBA Comments: 02/14/14 DT: Added OE/RR as subscriber. 08/15/13 DT: Added Lab Service as subscriber. DATE ACTIVATED: MAR 04, 2007 DATE/TIME EDITED: MAR 04, 2007@22:37 ACTION: CONTENT CORRECTED AT THE REQUEST OF: ALEXANDER,DAVID WITH CONCURRENCE OF: ORMSBY,SKIP DATE/TIME EDITED: SEP 27, 2007@17:33 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: FAIN,ZACH DATE/TIME EDITED: AUG 15, 2013@16:13 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: KOPP,TERRY WITH CONCURRENCE OF: BEUSCHEL,GARY DATE/TIME EDITED: FEB 14, 2014@13:15 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: RUFF,ROBERT WITH CONCURRENCE OF: MENDOZA,RAUL NUMBER: 2604 IA #: 2604 FILE NUMBER: 301.6 GLOBAL ROOT: IVM(301.6 DATE CREATED: OCT 09, 1998 CUSTODIAL PACKAGE: INCOME VERIFICATION MATCH CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2604 ID: IVM(301.6 GLOBAL REFERENCE: IVM(301.6,'B' GLOBAL DESCRIPTION: ^IVM(301.6,"B" is used to determine which IVM TRANSMISSION LOG file entries, if any, should be deleted. GLOBAL REFERENCE: IVM(301.6,D0 GLOBAL DESCRIPTION: When applying conditions are met the entry will be deleted using a DIK call. GENERAL DESCRIPTION: When the AMIE package deletes entries from the PATIENT file (#2) it also needs to delete entries from the IVM PATIENT file (#301.5). A cleanup is done to delete current entries in the IVM PATIENT file which point to non-existing or non-veterans in the PATIENT file. Corresponding entries in the IVM TRANSMISSION LOG file (#301.6) are also deleted. These entries are deleted using a DIK call. ^IVM(301.6,"B" is used to determine which IVM TRANSMISSION LOG file entries, if any, should be deleted. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28069917 SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 2605 IA #: 2605 FILE NUMBER: 9.4 GLOBAL ROOT: DIC(9.4, DATE CREATED: OCT 13, 1998 CUSTODIAL PACKAGE: KERNEL USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2605 ID: DIC(9.4, GENERAL DESCRIPTION: ^DIC(9.4,"C", cross reference - The software facilitating this DBIA, orders through the "C" cross reference which is a cross reference of the PREFIX field (#1) of the PACKAGE file (#9.4). If the PREFIX is "YS", the code then checks the SHORT DESCRIPTION field (#2) of the PACKAGE file (#9.4). If this field does NOT equal "Version 5.01 of Mental Health", the code either (1) deletes the entry from the package file or (2) renames the PREFIX from YS to YS_integer (beginning with 1, incremented by 1, i.e. YS1, YS2, YS3, etc.) depending on the number of Mental Health entries that are not version 5.01. User response to the 'Delete old PACKAGE file entries?' question determines which action will be performed by the code. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28098828 SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas NUMBER: 2606 IA #: 2606 FILE NUMBER: 440 GLOBAL ROOT: PRC(440 DATE CREATED: OCT 14, 1998 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2606 ID: PRC(440 GLOBAL REFERENCE: PRC(440,D0,0) FIELD NUMBER: .01 FIELD NAME: Name LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28107985 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 2607 IA #: 2607 DATE CREATED: OCT 14, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DDBR NAME: Browser API ID: DDBR GENERAL DESCRIPTION: The Browser displays ASCII text on a terminal which supports a scroll region. STATUS: Active MAIL MESSAGE: 28389253 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: This is an interactive procedure that asks the user for: File Word Processing Field Entry and then displays the text. VARIABLES: None COMPONENT/ENTRY POINT: WP() COMPONENT DESCRIPTION: This procedure displays word processing fields, as well as allowing navigation throughout the text, in a FileMan-compatible database using FileMan's Browser facility. Format WP^DDBR(FILE,IENS,FIELD,FLAGS,TITLE,LINE,TABS,TOP,BOTTOM) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) File or subfile number. VARIABLES: IENS TYPE: Input VARIABLES DESCRIPTION: (Required) Standard IENS indicating internal entry number string. VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) Word processing field name or number. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: N No copy of the document is made. The Browser will use the source document. Useful for long static documents. R Restrict switching. VARIABLES: TITLE TYPE: Input VARIABLES DESCRIPTION: (Optional) Text that is centered in header. Document title. VARIABLES: LINE TYPE: Input VARIABLES DESCRIPTION: (Optional) The line in the document that would be at the bottom margin of the opening screen. VARIABLES: TABS TYPE: Input VARIABLES DESCRIPTION: (Optional) Closed array root, passed by value, that is used to scroll horizontally. If not set, the Browser provides default tab stops. VARIABLES: TOP TYPE: Input VARIABLES DESCRIPTION: (Optional) A number representing the location of the title bar of the Browser screen. VARIABLES: BOTTOM TYPE: Input VARIABLES DESCRIPTION: (Optional) A number representing the location of the status bar of the Browser screen. COMPONENT/ENTRY POINT: BROWSE() COMPONENT DESCRIPTION: This procedure enables the user to utilize FileMan's Browser to view and navigate through a document stored in a sequential local or global array. Format BROWSE^DDBR(SOURCE_ARRAY,FLAGS,TITLE,LINE,TABS,TOP,BOTTOM) VARIABLES: SOURCE_ARRAY TYPE: Input VARIABLES DESCRIPTION: (Required) Source array in a closed root format, passed by value which is the location of a sequential local or global array containing text. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flags to control processing are described below: N No copy of the document is made. The Browser will use the source document. Useful for long static documents. R Restrict switching. VARIABLES: TITLE TYPE: Input VARIABLES DESCRIPTION: (Optional) Text centered in screen title. VARIABLES: LINE TYPE: Input VARIABLES DESCRIPTION: (Optional) The line in the document that would be at the bottom margin of the opening screen. VARIABLES: TABS TYPE: Input VARIABLES DESCRIPTION: (Optional) Closed array root, passed by value; used to scroll horizontally. If not set, the Browser provides default tab stops. VARIABLES: TOP TYPE: Input VARIABLES DESCRIPTION: (Optional) A number representing the location of the title bar of the Browser screen. VARIABLES: BOTTOM TYPE: Input VARIABLES DESCRIPTION: (Optional) A number representing the location of the status bar of the Browser screen. COMPONENT/ENTRY POINT: DOCLIST() COMPONENT DESCRIPTION: This procedure call allows passing more than one document to the Browser facility. Format DOCLIST^DDBR(SOURCE_ARRAY,FLAGS,TOP,BOTTOM) VARIABLES: SOURCE_ARRAY TYPE: Input VARIABLES DESCRIPTION: (Required) Source array in a closed root format, passed by value which is subscripted by document titles and set to the source array of the document in a closed root format. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flag to control processing is described below: R Restrict Switching to other documents not in current list. VARIABLES: TOP TYPE: Input VARIABLES DESCRIPTION: (Optional) A number representing the location of the title bar of the Browser screen. VARIABLES: BOTTOM TYPE: Input VARIABLES DESCRIPTION: (Optional) A number representing the location of the status bar of the Browser screen. NUMBER: 2608 IA #: 2608 DATE CREATED: OCT 14, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DDBRT NAME: Browser API ID: DDBRT GENERAL DESCRIPTION: This function call returns a 1 or 0 (true or false) to determine if the CRT being used can support a scroll region and reverse index. STATUS: Active MAIL MESSAGE: 28389278 COMPONENT/ENTRY POINT: $$TEST COMPONENT DESCRIPTION: Function call to determine if a CRT can support scroll region and reverse index. Usage: S X=$$TEST^DDBRT 1 = YES 0 = NO VARIABLES: None NUMBER: 2609 IA #: 2609 DATE CREATED: OCT 14, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DDBRZIS NAME: Browser API ID: DDBRZIS GENERAL DESCRIPTION: Browser device handler functions. STATUS: Active MAIL MESSAGE: 28389329 COMPONENT/ENTRY POINT: CLOSE COMPONENT DESCRIPTION: This procedure executes $$REWIND^%ZISC(), to rewind the file, and copies the text from the host file into a scratch global. VARIABLES: None COMPONENT/ENTRY POINT: OPEN COMPONENT DESCRIPTION: This procedure captures the text used in the Browser's title. VARIABLES: None COMPONENT/ENTRY POINT: POST COMPONENT DESCRIPTION: This procedure initializes the Browser to display the text sent to the device. VARIABLES: None NUMBER: 2610 IA #: 2610 DATE CREATED: OCT 14, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DDSVALF NAME: ScreenMan API: Form Utilities ID: DDSVALF GENERAL DESCRIPTION: $$GET() - This extrinsic function retrieves data from a form-only field or a computed field. PUT() - This procedure stuffs data into a form-only field. STATUS: Active MAIL MESSAGE: 28385733 COMPONENT/ENTRY POINT: $$GET() COMPONENT DESCRIPTION: This extrinsic function retrieves data from a form-only field or a computed field. Format $$GET^DDSVALF(FIELD,BLOCK,PAGE,FLAGS,IENS) VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) The Field Order number, Caption, or Unique Name of the form-only field. VARIABLES: BLOCK TYPE: Input VARIABLES DESCRIPTION: (Required at the page and form levels) The Block Order or Block Name. The default is the current block. VARIABLES: PAGE TYPE: Input VARIABLES DESCRIPTION: (Required at the form level) The Page Number or Page Name. The default is the current page. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Controls whether the internal or external form is returned, as shown below: I Return the Internal form of the data. (Default) E Return the External form of the data. VARIABLES: IENS TYPE: Input VARIABLES DESCRIPTION: (Required at the page and form levels) The standard IENS that identifies the entry or subentry associated with the form-only field. The default is the current entry or subentry. COMPONENT/ENTRY POINT: PUT() COMPONENT DESCRIPTION: This procedure stuffs data into a form-only field. Format PUT^DDSVALF(FIELD,BLOCK,PAGE,VALUE,FLAGS,IENS) VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) The Field Order number, Caption, or Unique Name of the form-only field. VARIABLES: BLOCK TYPE: Input VARIABLES DESCRIPTION: (Required at the page and form levels) The Block Order or Block Name. The default is the current block. VARIABLES: PAGE TYPE: Input VARIABLES DESCRIPTION: (Required at the form level) The Page Number or Page Name. The default is the current page. VARIABLES: VALUE TYPE: Input VARIABLES DESCRIPTION: (Required) The value to stuff into the form-only field. If FLAGS (described below) does not contain an "I", the value must be in the form of a valid, unambiguous user response. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Indicates whether VALUE is in internal or external form, as shown below: I VALUE is in Internal form; it is not validated. E VALUE is in External form (default). VARIABLES: IENS TYPE: Input VARIABLES DESCRIPTION: (Required at the page and form levels) The standard IENS that identifies the entry or subentry associated with the form-only field. The default is the current entry or subentry. NUMBER: 2611 IA #: 2611 FILE NUMBER: 4.4 GLOBAL ROOT: XMB(4.4, DATE CREATED: NOV 20, 1998 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TIME ZONE DIFFERENTIAL ID: XMB(4.4, GLOBAL REFERENCE: XMB(4.4,D0,0) FIELD NUMBER: 2 FIELD NAME: DIFFERENTIAL LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: CIRN would like an agreement to do a direct global read of the DIFFERENTIAL (#2) field in the MAILMAN TIME ZONE file (#4.4). This is used in conjunction with the CIRN REPOSITORY SITE PARAMETER file (#990.8) fields, (#10) STANDARD TIMEZONE and (#11) DST TIMEZONE, to automatically identify the current time and time differential for HL7 messaging. STATUS: Active MAIL MESSAGE: 28266377 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2612 IA #: 2612 FILE NUMBER: 50.3 GLOBAL ROOT: PS(50.3, DATE CREATED: OCT 18, 1998 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2612 ID: PS(50.3, GLOBAL REFERENCE: PS(50.3,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: National Drug File (NDF) request permission to look at the PRIMARY DRUG file (#50.3). Direct Global Read. Field Name Node & Piece .01 NAME 0;1 VIEWER: SCHLEHUBER,CAMERON VIEWER: ALEXANDER,DAVID VIEWER: MONTALI,MICHAEL VIEWER: MIMS,MICHAEL VIEWER: BERTUZIS,LINA VIEWER: CHRISTENSEN,KIM VIEWER: DAVIS,DOUG STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28150460 SUBSCRIBING PACKAGE: NATIONAL DRUG FILE ISC: Birmingham NUMBER: 2613 IA #: 2613 FILE NUMBER: 59.7 GLOBAL ROOT: PS(59.7, DATE CREATED: OCT 18, 1998 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2613 ID: PS(59.7, CREATOR: ROCHA,MARCELO GLOBAL REFERENCE: PS(59.7, FIELD NUMBER: 10 FIELD NAME: NDF VERSION LOCATION: 10;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 11 FIELD NAME: RESTART NUMBER LOCATION: 10;2 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 12 FIELD NAME: CONVERSION REMATCH OPTION DONE LOCATION: 10;3 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 10.1 FIELD NAME: LAST DRUG CONVERTED LOCATION: 10;4 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 10.2 FIELD NAME: V4 CONVERSION COMPLETED LOCATION: 10;5 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 13 FIELD NAME: PIMS PRINTER LOCATION: 10;6 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 14 FIELD NAME: PIMS LANGUAGE LOCATION: 10;7 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 49.99 FIELD NAME: OUTPATIENT VERSION LOCATION: 49.99;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .01 FIELD NAME: SITE NAME LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 15 FIELD NAME: PMIS SECTION DELETE LOCATION: 10;8 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 100 FIELD NAME: FDA MED GUIDE SERVER URL LOCATION: FDA;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: National Drug File (NDF) requests to look at the PHARMACY SYSTEM file (59.7). Direct Global R/W. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 52954135 SUBSCRIBING PACKAGE: NATIONAL DRUG FILE ISC: Birmingham DATE ACTIVATED: OCT 04, 2010 DATE/TIME EDITED: OCT 04, 2010@21:04 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: ROCHA,MARCELO DATE/TIME EDITED: OCT 05, 2010@21:00 ACTION: APPROVED AT THE REQUEST OF: ROCHA,MARCELO NUMBER: 2614 IA #: 2614 DATE CREATED: OCT 18, 1998 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2614 GENERAL DESCRIPTION: National Drug File (NDF) requests permission to export templates to DRUG file (#50). Print Templates --------------- PSNFRMPRT PSNHEAD PSNLDG1 PSNRPT2 PSNRPT4 Sort Templates -------------- PSNFRMSRT STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28150477 SUBSCRIBING PACKAGE: NATIONAL DRUG FILE ISC: Birmingham NUMBER: 2615 IA #: 2615 DATE CREATED: OCT 19, 1998 CUSTODIAL PACKAGE: LIST MANAGER USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VALM0 NAME: TERM OF VALM0 ID: VALM0 GENERAL DESCRIPTION: Inpatient Medications requests an integration agreement with List Manager to call TERM^VALM0. This call is to set the variables that determine terminal characteristics. STATUS: Active DURATION: Next Version MAIL MESSAGE: 27911402 GOOD ONLY FOR VERSION: 5.0 COMPONENT/ENTRY POINT: TERM COMPONENT DESCRIPTION: No variables are passed. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 2616 IA #: 2616 DATE CREATED: OCT 19, 1998 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOCAN NAME: DBIA2616 ID: PSOCAN GENERAL DESCRIPTION: This agreement allows the Controlled Substances package to call the Outpatient Pharmacy package to request that the last refill of a prescription be deleted. This will be for Outpatient Version 7.0 and greater. The Outpatient Pharmacy version check will be done by the Controlled Substances package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28164693 COMPONENT/ENTRY POINT: PSD COMPONENT DESCRIPTION: This entry point will delete the last refill of the prescription and add an Activity Log entry describing this action. VARIABLES: PSDRX TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number from the PRESCRIPTION File (#52). VARIABLES: PSDRFDEL TYPE: Output VARIABLES DESCRIPTION: This variable indicates whether or not the refill was deleted. 1 = Yes (refill deleted) 0 = No (refill not deleted) SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham SUBSCRIBING DETAILS: During the posting/releasing process in Controlled Substances, a check will be done on the status of the prescription. If the status of the prescription is DISCONTINUED, DELETED, DISCONTINUED BY PROVIDER, or DISCONTINUED (EDIT), the prescription will not be posted and released. If the fill is a refill, the call will be made to Outpatient Pharmacy to delete the refill information and add an Activity Log entry detailing why the refill was deleted. NUMBER: 2617 IA #: 2617 FILE NUMBER: 9000010 GLOBAL ROOT: AUPNVSIT DATE CREATED: OCT 19, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2617 ID: AUPNVSIT GLOBAL REFERENCE: AUPNVSIT(D0,0) FIELD NUMBER: .01 FIELD NAME: VISIT/ADMIT DATE&TIME LOCATION: 0,1 ACCESS: Read w/Fileman FIELD NUMBER: .05 FIELD NAME: PATIENT NAME LOCATION: 0,5 ACCESS: Read w/Fileman FIELD NUMBER: .06 FIELD NAME: LOC. OF ENCOUNTER LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: .12 FIELD NAME: PARENT VISIT LINK LOCATION: 0;12 ACCESS: Read w/Fileman FIELD NUMBER: .18 FIELD NAME: CHECK OUT DAT&TIME LOCATION: 0;18 ACCESS: Read w/Fileman FIELD NUMBER: .22 FIELD NAME: HOSPITAL LOCATION LOCATION: 0;22 ACCESS: Read w/Fileman GLOBAL REFERENCE: AUPNVSIT(D0,150) FIELD NUMBER: 15003 FIELD NAME: ENCOUNTER TYPE LOCATION: 150,3 ACCESS: Read w/Fileman FIELD NUMBER: 15001 FIELD NAME: VISIT ID LOCATION: 150;1 ACCESS: Read w/Fileman FIELD NUMBER: 15002 FIELD NAME: PATIENT STATUS IN/OUT LOCATION: 150;2 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The CIRN Visit Tracking data extraction routine (^RGHOPV1 - HL7 Message Generation for In-patient/Out-patient Visit Data) and the historical load routine (^RGHOPV1B - Historical Backload of Visits), make several references to nodes/fields in the VISIT file (#9000010), for the purpose of creating the HL7 transmission records. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28154026 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2619 IA #: 2619 FILE NUMBER: 9000010.15 GLOBAL ROOT: AUPNVTRT DATE CREATED: OCT 21, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2619 ID: AUPNVTRT GLOBAL REFERENCE: AUPNVTRT(D0,0) FIELD NUMBER: .01 FIELD NAME: TREATMENT LOCATION: 0,1 ACCESS: Read w/Fileman FIELD NUMBER: .02 FIELD NAME: PATIENT NAME LOCATION: 0,2 ACCESS: Read w/Fileman FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0,3 ACCESS: Read w/Fileman FIELD NUMBER: .04 FIELD NAME: HOW MANY LOCATION: 0,4 ACCESS: Read w/Fileman FIELD NUMBER: .06 FIELD NAME: PROVIDER NARRATIVE LOCATION: 0,6 ACCESS: Read w/Fileman GLOBAL REFERENCE: AUPNVTRT(D0,12) FIELD NUMBER: 1201 FIELD NAME: EVENT DATE AND TIME LOCATION: 12,1 ACCESS: Read w/Fileman FIELD NUMBER: 1202 FIELD NAME: ORDERING PROVIDER LOCATION: 12,2 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The CIRN Treatments (PCE) data extraction routine (^RGHOVTX - HL7 Transmission of Non CPT Coded Procedures), makes several references to nodes/fields in the V TREATMENT file (#9000010.15), for the purpose of creating the HL7 transmission records. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28174207 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2620 IA #: 2620 FILE NUMBER: 9999999.17 GLOBAL ROOT: AUTTTRT DATE CREATED: OCT 21, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2620 ID: AUTTTRT GLOBAL REFERENCE: AUTTTRT(D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0,1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The CIRN Treatments (PCE) data extraction routine (^RGHOVTX - HL7 Transmission of Non CPT Coded Procedures), makes a reference to a node in the TREATMENT file (#9999999.17), for the purpose of creating the HL7 transmission records. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28174207 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2622 IA #: 2622 DATE CREATED: OCT 20, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XLFUTL NAME: DBIA2622 ID: XLFUTL GENERAL DESCRIPTION: Use of the XLFUTL APIs. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28164360 COMPONENT/ENTRY POINT: $$CCD COMPONENT DESCRIPTION: Compute check digit. See Taylor report Computerworld 1975 Usage: S Y=$$CCD^XLFUTL(X) Input: an integer. Returns the input value with the check digit appended. COMPONENT/ENTRY POINT: $$VCD COMPONENT DESCRIPTION: Verify check digit (last digit). Usage: IF $$VCD^XLFUTL(X) W "OK" Input: an integer with check digit, from $$CCD^XLFUTL Output: 1 if the check digit matches, 0 for non-match. COMPONENT/ENTRY POINT: $$BASE COMPONENT DESCRIPTION: Converts the first parameter from the number base of the second parameter to the number base of the third parameter. Usage: W $$BASE^XLFUTL("1A",16,2) ==> 11010 Input 1: a string representing the number to convert. Input 2: a number from 2 to 16, the base of input 1. Input 3: a number from 2 to 16, the base for the output. The useful values for Input 2 and 2 are 2, 8, 10, 16 but other numbers can be used. e.g. W $$BASE("A",12,3) ==> 101 Because of the use of division, input is limited by the M vendor to the largest integer they handle, 15 digits. COMPONENT/ENTRY POINT: $$DEC(NUMBER,FROMBASE) VARIABLES: NUMBER TYPE: Input VARIABLES DESCRIPTION: Number to be converted to base 10 VARIABLES: FROMBASE TYPE: Input VARIABLES DESCRIPTION: Base to convert NUMBER from VARIABLES: $$DEC TYPE: Output VARIABLES DESCRIPTION: NUMBER converted to Base 10 COMPONENT/ENTRY POINT: $$CNV(NUMBER,TOBASE) VARIABLES: NUMBER TYPE: Input VARIABLES DESCRIPTION: Number to be converted from base 10 to TOBASE VARIABLES: TOBASE TYPE: Input VARIABLES DESCRIPTION: Base to convert NUMBER to VARIABLES: $$CNV TYPE: Output VARIABLES DESCRIPTION: NUMBER converted to TOBASE from base 10 NUMBER: 2623 IA #: 2623 FILE NUMBER: 9999999.27 GLOBAL ROOT: AUTNPOV DATE CREATED: OCT 21, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2623 ID: AUTNPOV GLOBAL REFERENCE: AUTNPOV(D0,0) FIELD NUMBER: .01 FIELD NAME: NARRATIVE LOCATION: 0,1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The CIRN Treatments (PCE) data extraction routine (^RGHOVTX - HL7 Transmission of Non CPT Coded Procedures), makes a reference to a node in the PROVIDER NARRATIVE file (#9999999.27), for the purpose of creating the HL7 transmission records. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28174207 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2624 IA #: 2624 DATE CREATED: OCT 23, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFHUTL NAME: DBIA2624 ID: VAFHUTL GENERAL DESCRIPTION: CIRN would like a DBIA with Registration to use the SEND^VAFHUTL function to identify the status of the PIMS ADT messaging or SEND PIMS HL7 V2.3 MESSAGES field (391.7013) within the MAS PARAMETERS file (#43). STATUS: Active MAIL MESSAGE: 28131730 COMPONENT/ENTRY POINT: $$SEND() COMPONENT DESCRIPTION: this function will test for the on/off parameter to send ADT messages. VARIABLES: $$SEND TYPE: Output VARIABLES DESCRIPTION: ;OUTPUTS 0 will indicate NOT to send ; 1 will indicate TO send ; 0 in second piece will indicate NOT to send HL7 v2.3 ; 1 in second piece will indicate to send HL7 v2.3 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2627 IA #: 2627 FILE NUMBER: 9000010.18 GLOBAL ROOT: AUPNVCPT DATE CREATED: NOV 24, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2627 ID: AUPNVCPT GLOBAL REFERENCE: AUPNVCPT(D0,0) FIELD NUMBER: .01 FIELD NAME: CPT LOCATION: 0,1 ACCESS: Read w/Fileman FIELD NUMBER: .02 FIELD NAME: PATIENT NAME LOCATION: 0,2 ACCESS: Read w/Fileman FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0,3 ACCESS: Read w/Fileman FIELD NUMBER: .04 FIELD NAME: PROVIDER NARRATIVE LOCATION: 0,4 ACCESS: Read w/Fileman GLOBAL REFERENCE: AUPNVCPT(D0,12) FIELD NUMBER: 1201 FIELD NAME: EVENT DATE AND TIME LOCATION: 12,1 ACCESS: Read w/Fileman FIELD NUMBER: 1202 FIELD NAME: ORDERING PROVIDER LOCATION: 12,2 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The CIRN Procedures (PCE) data extraction routine (^RGHOCPT - HL7 Transmission of CPT Coded Procedures), makes several references to the nodes/fields in the V CPT file (#9000010.18), for the purpose of creating the HL7 transmission records. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28245567 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2628 IA #: 2628 FILE NUMBER: 120.8 GLOBAL ROOT: GMR(120.8, DATE CREATED: NOV 06, 1998 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2628 ID: GMR(120.8, GLOBAL REFERENCE: GMR(120.8, FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .02 FIELD NAME: REACTANT LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: GMR ALLERGY LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: ORIGINATION DATE/TIME LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: 5 FIELD NAME: ORIGINATOR LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 6 FIELD NAME: OBSERVED HISTORICAL LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 20 FIELD NAME: VERIFICATION DATE/TIME LOCATION: 0;17 ACCESS: Read w/Fileman FIELD NUMBER: 22 FIELD NAME: ENTERED IN ERROR LOCATION: ER;1 ACCESS: Read w/Fileman FIELD NUMBER: 23 FIELD NAME: DATE TIME ENTERED IN ERROR LOCATION: ER;2 ACCESS: Read w/Fileman FIELD NUMBER: 24 FIELD NAME: USER ENTERING IN ERROR LOCATION: ER;3 ACCESS: Read w/Fileman GLOBAL REFERENCE: GMR(120.8,D0,26,D1,2,D2, FIELD NUMBER: .01 FIELD NAME: COMMENTS LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: CIRN Allergy/Adverse reaction data extraction routine ^RGHOALR/^RGHOALRB make numerous direct global reads of the PATIENT ALLERGY FILE(#120.8). The routines use this information to generate HL7 message for transmission of results and to do historical backloading of data. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28177977 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 2629 IA #: 2629 FILE NUMBER: 51 GLOBAL ROOT: DIC(51, DATE CREATED: NOV 09, 1998 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: EXPANSION FIELD FOR CIRN ID: DIC(51, GLOBAL REFERENCE: DIC(51,D0, FIELD NUMBER: 1 FIELD NAME: EXPANSION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DIC(51,'B', GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. TO GENERATE HL7 PRESCRIPTION MESSAGING. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 28276858 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham EDITOR: BLOCKER,DAVE NUMBER: 2630 IA #: 2630 FILE NUMBER: 70 GLOBAL ROOT: RADPT DATE CREATED: OCT 28, 1998 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2630 ID: RADPT GLOBAL REFERENCE: RADPT(D0,'DT','AP',PROCEDURE) GLOBAL DESCRIPTION: This is used to obtain the list of radiology procedures for the patient. GLOBAL REFERENCE: RADPT('B',DFN) GLOBAL DESCRIPTION: This is used to find the entries in RADPT, i.e. the D0 for the patient. GENERAL DESCRIPTION: PCE Clinical Reminders needs to build a list of radiology procedures received by a patient. In order to do this we would like to use $O on the following cross-references. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28226959 SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 2631 IA #: 2631 GLOBAL ROOT: DD( DATE CREATED: OCT 27, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2631 ID: DD( GLOBAL REFERENCE: DD(D0,O,'UP') GENERAL DESCRIPTION: Knowledge of file and subfile hierarchies is sometimes required. The required information can be obtained from ^DD(D0,0,"UP"). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28059959 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL REMINDERS NUMBER: 2632 IA #: 2632 FILE NUMBER: 70 GLOBAL ROOT: RADPT DATE CREATED: OCT 27, 1998 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2632 ID: RADPT GLOBAL REFERENCE: RADPT(D0,DT,D1,P,D2,0) FIELD NUMBER: 2 FIELD NAME: PROCEDURE LOCATION: 0,2 ACCESS: Read w/Fileman FIELD NUMBER: 14 FIELD NAME: REQUESTING PHYSICIAN LOCATION: 0,14 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The CIRN Radiology/Nuclear Medicine data extraction routine (^RGHORAD - HL7 Message Generation for Radiology/Nuclear Results) and the historical load routine (^RGHORADB - Historical Load of Radiology/Nuclear Medicine Reports), make several references to radiology/nuclear related fields in the RAD/NUC MED PATIENT file (#70), for the purpose of creating the HL7 transmission records. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28219974 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham NUMBER: 2633 IA #: 2633 FILE NUMBER: 71 GLOBAL ROOT: RAMIS(71, DATE CREATED: OCT 27, 1998 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2633 ID: RAMIS(71, GLOBAL REFERENCE: RAMIS(71,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0,1 ACCESS: Read w/Fileman FIELD NUMBER: 9 FIELD NAME: CPT CODE LOCATION: 0,9 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The CIRN Radiology/Nuclear Medicine data extraction routine (^RGHORAD - HL7 Message Generation for Radiology/Nuclear Results) and the historical load routine (^RGHORADB - Historical Load of Radiology/Nuclear Medicine Reports), make several references to radiology/nuclear related fields in the RAD/NUC MED PROCEDURES file (#71), for the purpose of creating the HL7 transmission records. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28219974 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2635 IA #: 2635 FILE NUMBER: 60 GLOBAL ROOT: LAB(60 DATE CREATED: OCT 27, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2635 ID: LAB(60 GLOBAL REFERENCE: LAB(60,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: (The look up on LABORATORY TEST file (#60) uses the DIC("S")="I $L($P(^(0),U,5))&(""BO""[$P(^(0),U,3))") FIELD NUMBER: 5 FIELD NAME: LOCATION (DATA NAME) LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LAB(60,D0,.1) FIELD NUMBER: 51 FIELD NAME: PRINT NAME LOCATION: .1;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 53 FIELD NAME: PRINT CODE LOCATION: .1;3 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: LAB(60,D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: SITE/SPECIMEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .01 FIELD NAME: SITE/SPECIMEN LOCATION: 0;1 ACCESS: Pointed to FIELD NUMBER: 1 FIELD NAME: REFERENCE LOW LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: REFERENCE HIGH LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6 FIELD NAME: UNITS LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 9.2 FIELD NAME: THERAPEUTIC LOW LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 9.3 FIELD NAME: THERAPEUTIC HIGH LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: (When displaying ther/normal values, therapeutic values override normal high/low.) GENERAL DESCRIPTION: Dietetics package displays Lab Test results by using Laboratory Test file #60. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: NOV 09, 1999 MAIL MESSAGE: 28220670 SUBSCRIBING PACKAGE: DIETETICS ISC: Hines NUMBER: 2636 IA #: 2636 FILE NUMBER: 63 GLOBAL ROOT: LR( DATE CREATED: OCT 27, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2636 ID: LR( GLOBAL REFERENCE: LR(D0,'CH',D1,0) FIELD NUMBER: .01 FIELD NAME: DATE/TIME SPECIMEN TAKEN LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2... FIELD NAME: TEST RESULT-FLAG LOCATION: 0;1-2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: DATE REPORT COMPLETED LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .05 FIELD NAME: SPECIMEN TYPE LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Dietetics package displays the Lab Test results by using the Lab Data file #63. STATUS: Active EXPIRATION DATE: NOV 09, 1999 MAIL MESSAGE: 28220732 SUBSCRIBING PACKAGE: DIETETICS ISC: Hines NUMBER: 2638 IA #: 2638 FILE NUMBER: 100.01 GLOBAL ROOT: ORD(100.01, DATE CREATED: OCT 29, 1998 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ORDER STATUS file direct access ID: ORD(100.01, GLOBAL REFERENCE: ORD(100.01,STATUS,0) FIELD NUMBER: .01 FIELD NAME: NAME ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Names that represent an Orders Status. (e.g., DISCONTINUED, COMPLETE) FIELD NUMBER: .02 FIELD NAME: SHORT NAME ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the SHORT NAME for an order status. This is used when the displays need to restrict the order status to 4 characters, or less. FIELD NUMBER: .1 FIELD NAME: ABBREVIATION ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the ABBREVIATION for an order status. (e.g., pr is the abbreviation for PARTIAL RESULTS) GENERAL DESCRIPTION: The Consults package and CPRS are very tightly linked. The Consults package has direct access to the Order Status File, 100.01. Consult routines use the Order status to display the status and create lists of consults for use by the Consults package List Manager, CPRS List Manager Consults tab and the CPRS GUI Consults tab. The Consult package also uses the direct access of the order status to create the Notification text for consult alerts. The Consults package may have read only direct access to the ^ORD(100.01, global for the following information: ^ORD(100.01,D0,0)= (#.01) NAME [1F] ^ (#.02) SHORT NAME [2F] ^ ^ORD(100.01,D0,.1)= (#.1) ABBREVIATION [E1,245F] ^ STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28237498 SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM SUBSCRIBING DETAILS: Fee Basis Claims system is using standard FileMan calls ($$FIND1^DIC) to locate the IEN for the ORDER STATUS (#100.01) file to relate that information into the ^GMR(123 file to pull only Active or Pending consults. DBA Comments: 09/10/12 DT: FBCS was added as subscriber to support the DSIF*3.2*23 (Fee Basis Claims System) and the GMRC*3.0*74 patches. DATE/TIME EDITED: SEP 10, 2012@15:53 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: DEWAYNE,BRANDON WITH CONCURRENCE OF: THOMPSON,TONY NUMBER: 2640 IA #: 2640 DATE CREATED: OCT 29, 1998 CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RGDDHS00 NAME: CIRN HEALTH SUMMARY DATA EXTRACT ID: RGDDHS00 GENERAL DESCRIPTION: This DBIA concerns a call to the CIRN Health Summary extract routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28233836 COMPONENT/ENTRY POINT: EXTRACT COMPONENT DESCRIPTION: D EXTRACT^RGDDHS00(DFN,OPT,BEG,END,[.]CLS,[.]INS,TAX) VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: A pointer to the Patient file (#2). VARIABLES: OPT TYPE: Input VARIABLES DESCRIPTION: A list of option flags used to control the extract process. Defaults to null if not passed in. A - Abnormal results only Cn - Set column width to n (default=10) Dn - Set detail level to n (default=0) Fn - First n results (default=1) I - Show institution information J - First or last for each institution Ln - Last n results (default=1) N - Show normal ranges O - Old results first Rn - Results stored within last n days U - Show units VARIABLES: BEG TYPE: Input VARIABLES DESCRIPTION: The beginning date for extracted data, in internal VA FileMan format. Defaults to the earliest date that the patient has data for if not passed in. VARIABLES: END TYPE: Input VARIABLES DESCRIPTION: The ending date for extracted data, in internal VA FileMan format. Defaults to the latest date that the patient has data for if not passed in. VARIABLES: CLS TYPE: Input VARIABLES DESCRIPTION: A single class name/pointer or array of class names/ pointers to the CIRN Object Dictionary (#990.9). May be passed by reference or by value. If an array is passed by reference, subscripts represent the class name/pointer values. Defaults to all classes if not passed in. VARIABLES: INS TYPE: Input VARIABLES DESCRIPTION: A single pointer or array of pointers to the Institution file (#4). May be passed by reference or by value. If an array is passed by reference, the subscripts represent the pointer values. Defaults to all institutions if not passed in. To include all institutions except a selected list, negate the pointer value, e.g., S INS(-123)="". VARIABLES: TAX TYPE: Input VARIABLES DESCRIPTION: A taxonomy name/pointer to the CIRN Object Taxonomy file (#990.91). Defaults to "CLINICAL SUMMARY" if not passed in. VARIABLES: RETURN VALUE TYPE: Output VARIABLES DESCRIPTION: The output of this call is in the ^TMP("RGHS",$J, global. SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 2641 IA #: 2641 DATE CREATED: NOV 09, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: KIDS VARIABLES GENERAL DESCRIPTION: Variable(s) available pre, during, and post KIDS installation. Variable: XPDPKG = Package file entry ien for build that is currently being processed. STATUS: Active MAIL MESSAGE: 28237935 NUMBER: 2642 IA #: 2642 FILE NUMBER: 0 GLOBAL ROOT: DD( DATE CREATED: NOV 12, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Set Rad/Nuc Med data dictionary 'ID','WRITE' node. ID: DD( GENERAL DESCRIPTION: Radiology/Nuclear Medicine intends to modify the following data dictionary attribute: before: ^DD(71,0,"ID","WRITE") = W ?54,$$PRCCPT^RADD1() after: ^DD(71,0,"ID","WRITE") = D EN^DDIOL($$PRCCPT^RADD1(),"","?54") The intention of this correction is to eliminate the WRITE command from the data dictionary. To execute this action, I must hard set the data dictionary node in a post-init. At present, FileMan does not have a generic tool to export specific file wide data dictionary attributes. I do not wish to carry over the entire data dictionary for the Rad/Nuc Med Procedures file. VIEWER: SCHLEHUBER,CAMERON VIEWER: MO,SELINA VIEWER: WINN,TAMI STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28336619 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 2643 IA #: 2643 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: NOV 03, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED ROUTINE: IBCNSU1 NAME: DBIA2643 ID: IBCNSU1 GLOBAL REFERENCE: DPT(D1,.312,D0) FIELD NUMBER: .3121 FIELD NAME: INSURANCE TYPE ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: This field references the INSURANCE TYPE (#2.312) sub-file in this agreement. GLOBAL REFERENCE: DPT(D0,.31) FIELD NUMBER: .3192 FIELD NAME: COVERED BY HEALTH INSURANCE? LOCATION: .31;11 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: This field references the COVERED BY HEALTH INSURANCE? (#.3192) field in this agreement. GENERAL DESCRIPTION: Since March 1994, the Integrated Billing package has retained full authority for the INSURANCE TYPE (#2.312) sub-file and the field COVERED BY HEALTH INSURANCE? (#.3192), both located in the PATIENT (#2) file. This authority includes development of the data dictionary (DD) for these fields, as well as responsibility for data entry into and data retrieval from these fields. This agreement is a "delegation of custody" of these fields from Registration to Integrated Billing. It provides Integrated Billing all rights and privileges to development and distribution for all DD elements and data in these fields. In addition, all DBIAs required for access to the DD and data for these fields will be between any subscriber and Integrated Billing as the custodian. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28260928 COMPONENT/ENTRY POINT: $$VET VARIABLES: Input Transform TYPE: Output VARIABLES DESCRIPTION: 1 - Set X = to Patient's Name 0 - User may enter/edit field SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany EDITOR: RUBIN,ALICE NUMBER: 2644 IA #: 2644 GLOBAL ROOT: AUPNPROB DATE CREATED: APR 16, 1999 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMPLUTL3 NAME: DBIA2644 ID: GMPLUTL3 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29268789 COMPONENT/ENTRY POINT: CALL0 VARIABLES: GMPLZ TYPE: Input VARIABLES DESCRIPTION: IEN of problem VARIABLES: GMPLICD TYPE: Output VARIABLES DESCRIPTION: DIAGNOSIS VARIABLES: GMPLPNAM TYPE: Output VARIABLES DESCRIPTION: PATIENT NAME VARIABLES: GMPLDLM TYPE: Output VARIABLES DESCRIPTION: DATE LAST MODIFIED VARIABLES: GMPLTXT TYPE: Output VARIABLES DESCRIPTION: PROVIDER NARRATIVE VARIABLES: GMPLODAT TYPE: Output VARIABLES DESCRIPTION: Either DATE OF ONSET or DATE ENTERED VARIABLES: GMPLSTAT TYPE: Output VARIABLES DESCRIPTION: STATUS COMPONENT/ENTRY POINT: CALL1 VARIABLES: GMPLZ TYPE: Input VARIABLES DESCRIPTION: IEN of problem VARIABLES: GMPLLEX TYPE: Output VARIABLES DESCRIPTION: PROBLEM VARIABLES: GMPLCOND TYPE: Output VARIABLES DESCRIPTION: CONDITION VARIABLES: GMPLPRV TYPE: Output VARIABLES DESCRIPTION: Either RECORDING PROVIDER or RESPONSIBLE PROVIDER VARIABLES: GMPLXDAT TYPE: Output VARIABLES DESCRIPTION: DATE RESOLVED VARIABLES: GMPLPRIO TYPE: Output VARIABLES DESCRIPTION: the Priority (A=acute C=chronic) for a Problem List problem COMPONENT/ENTRY POINT: CALL2 COMPONENT DESCRIPTION: Sets variables described in both CALL0 and CALL1, of this DBIA. COMPONENT/ENTRY POINT: MOD COMPONENT DESCRIPTION: This entry point is called a a function and returns the date or date and time of the last time that a patients Problem List was modified. example: W $$MOD^GMPLUTL3(DFN) returns: 2990301 or 2990301.096523 If DFN is not one that has an entry in the problem list then a zero is returned. SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING DETAILS: The CIRN Problem List data extraction routine (^RGHOPL - HL7 Transmission of Problem List Data), and the historical load routine (^RGHOPLB - Historical Load of Problem List), primarily call the GMPLUTL3 API, for the purpose of creating records. SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING DETAILS: Clinical Reminders needs information from a patient's Problem List. This includes the most recent date the patient's Problem List was modified and the following fields: DATE LAST MODIFIED, CONDITION, STATUS, DIAGNOSIS, PROBLEM, and PROVIDER NARRATIVE. SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 2647 IA #: 2647 DATE CREATED: NOV 18, 1998 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSLOAD NAME: ADD CIRN COMPONENTS ID: GMTSLOAD GENERAL DESCRIPTION: CIRN requests permission to add three (3) new components to the Health Summary Component file (#142.1) which will display CIRN information while respecting time and occurrence limits. These components will be exported in a disabled state by a Health Summary patch. The IEN range set aside for CIRN use in the Health Summary Component file (#142.1) will be 400-499. The sub-namespace used by the CIRN HS components will be GMTSRG*. A CIRN post-install routine will add the components to the Ad Hoc Health Summary type by calling the ENPOST^GMTSLOAD entry point. The variable INCLUDE will be set to zero (0) or one (1) by user input before the call to this entry point. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28378097 COMPONENT/ENTRY POINT: ENPOST COMPONENT DESCRIPTION: Rebuild the Ad Hoc Health Summary type. VARIABLES: INCLUDE TYPE: Input VARIABLES DESCRIPTION: INCLUDE=0 Excludes disabled components in the Ad Hoc Health Summary type. INCLUDE=1 Includes disabled components in the Ad Hoc Health Summary type. SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham NUMBER: 2648 IA #: 2648 DATE CREATED: NOV 19, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DDMP NAME: Import Tool API ID: DDMP GENERAL DESCRIPTION: This procedure imports data from ASCII host files into VA FileMan file entries. Format FILE^DDMP([FILE],[[.]FIELDS],[.CONTROL],.SOURCE,[.]FORMAT) STATUS: Active MAIL MESSAGE: 28386657 COMPONENT/ENTRY POINT: FILE() COMPONENT DESCRIPTION: This procedure imports data from ASCII host files into VA FileMan file entries. Each record (line of data) in the host file is stored as a new entry in a specified VA FileMan file. VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Optional) File number into which imported data will be filed. Do not pass this parameter if the import file specifies the destination VA FileMan file and fields. The file must already exist. VARIABLES: [.]FIELDS TYPE: Input VARIABLES DESCRIPTION: (Optional) Array specifying the fields into which imported data will be filed. The array can either: Name an Import Template, or Directly specify the fields for import. Do not pass this parameter if the import file specifies the destination VA FileMan file and fields. If you have the import fields stored in an Import Template, simply set the top-level, unsubscripted node to the name of the template, surrounded by [brackets]. VARIABLES: .CONTROL TYPE: Input VARIABLES DESCRIPTION: (Optional) Pass this array by reference. You can control the behavior of FILE^DDMP by setting the following nodes in the CONTROL array: CONTROL("FLAGS") (Optional) Concatenated string of character flags to control processing of the import. E External values are contained in the import file. F Import File contains identity of destination FileMan file and fields. If F flag is not present, the FILE and FIELDS parameters are required and must contain file and field information. CONTROL("MSGS"): (Optional) Set to the root of an array (local or global) into which error messages should be returned. If a value is not passed, messages are returned in nodes descendant from ^TMP("DIERR",$J). CONTROL("MAXERR"): (Optional) Set to the number of errors encountered at which point to abort the import. Default is not to abort. CONTROL("IOP"): (Optional) Set to the name of the device (as stored in the DEVICE file) on which to print the Import Report. Default is to ask the user for output device. CONTROL("QTIME"): (Optional) Set to the time for queuing the data filing, and subsequent printing of the Import Results report. Default is to ask the user whether or not to queue, and for the queuing time. VARIABLES: .SOURCE TYPE: Input VARIABLES DESCRIPTION: (Required) An array that identifies the import file. Pass this array by reference. SOURCE("FILE") (Required) Set this node to the import file name. SOURCE("PATH") (Optional) Path or directory where the file can be found. If this node is not defined, the default path is used to locate the file. VARIABLES: [.]FORMAT TYPE: Input VARIABLES DESCRIPTION: (Required) Specifies the format of the incoming data. You can either: Pass the name of a FOREIGN FORMAT File entry in the top-level, unsubscripted node of this array, or Set individual nodes in this array to define the import format (pass by reference). If you set individual nodes in the array to define the format, you can set: FORMAT("FDELIM") Set this node to the field delimiter used for the imported data, if a field delimiter is used. FORMAT("FIXED") Set this node to "YES" if the incoming data is in fixed-length format. If not set to "YES", the default format is field-delimited. FORMAT("QUOTED") Set this node to "YES", if you would like VA FileMan to ignore the field delimiter in any quoted strings in the incoming data. NUMBER: 2649 IA #: 2649 DATE CREATED: NOV 19, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DILF NAME: Classic FileMan API: Max. Routine Size ID: DILF GENERAL DESCRIPTION: This argumentless function returns the maximum routine size that should be used when compiling cross references, print templates, or input templates. STATUS: Active MAIL MESSAGE: 28389527 COMPONENT/ENTRY POINT: $$ROUSIZE COMPONENT DESCRIPTION: This argumentless function returns the maximum routine size that should be used when compiling cross references, print templates, or input templates. Format $$ROUSIZE^DILF VARIABLES: None NUMBER: 2650 IA #: 2650 DATE CREATED: NOV 23, 1998 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORCMEDT1 NAME: DBIA2650 ID: ORCMEDT1 GENERAL DESCRIPTION: Pharmacy Data Management calls ADD^ORCMEDT1 to add a single quick order located in the ORDER DIALOG FILE (#101.41) to a menu for use in CPRS 1.0. On installation, CPRS loops through all the Add Orders menus in the Protocol file that are assigned to users as a default; all items on those menus are converted to a new entry in a new format in the Order Dialog file for use with CPRS. Utilities exist in both Pharmacy and CPRS to convert additional protocols that did not get processed [successfully] during installation; the entry point ADD^ORCMEDT1 being called here from the Pharmacy utility will simply loop through the Protocol file and find all menus that the protocol PITEM was attached to and add the corresponding converted dialog DITEM to the same menus in the Order Dialog file. This will help minimize the impact on the sites. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28415127 COMPONENT/ENTRY POINT: ADD COMPONENT DESCRIPTION: Variable PITEM is defined as the quick order IEN in the PROTOCOL FILE (#101). Variable DITEM is defined as the same quick order IEN in the ORDER DIALOG FILE (101.41). Entry point ADD finds the menu location for PITEM that was used in OERR 2.5 and places DITEM under the same menu location for use in CPRS 1.0. VARIABLES: PITEM TYPE: Input VARIABLES DESCRIPTION: IEN of the quick order in the PROTOCOL FILE (#101). VARIABLES: DITEM TYPE: Input VARIABLES DESCRIPTION: IEN of the quick order in the ORDER DIALOG FILE (#101.41). SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2651 IA #: 2651 DATE CREATED: NOV 23, 1998 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORCONV2 NAME: DBIA2651 ID: ORCONV2 GENERAL DESCRIPTION: Routine ORCONV2 is called by Pharmacy Data Management to pass quick order data from the PHARMACY QUICK ORDER FILE (#57.1) to OERR. In preparation for CPRS 1.0, these pharmacy quick orders are converted to entries in the ORDER DIALOG FILE (#101.41). Entry points UD^ORCONV2 and IV^ORCONV2 accomplish this task. STATUS: Active DURATION: Next Version MAIL MESSAGE: 28413615 GOOD ONLY FOR VERSION: 3.0 COMPONENT/ENTRY POINT: UD COMPONENT DESCRIPTION: This entry point is called to process a unit dose pharmacy quick order. The following array is built before the call is made. ^TMP("PSJQO",$J,1)=Quick Order Name^Type^Orderable Item IEN^Med Route IEN^ Schedule^Instructions^Infusion Rate^Provider Comments Prompt ^TMP("PSJQO",$J,"DD")=Dispense Drug IEN ^TMP("PSJQO",$J,"PC",0)=Last Entry^Number of Entries ^TMP("PSJQO",$J,"PC",x,0)=Provider Comments Line x ^TMP("PSJQO",$J,"AD",0)=Last Entry^Number of Entries ^TMP("PSJQO",$J,"AD",x,0)=Orderable Item IEN (for Additive)^Strength^Units ^TMP("PSJQO",$J,"SOL",0)="Last Entry^Number of Entries ^TMP("PSJQO",$J,"SOL",x,0)=Orderable Item IEN (for Solution)^Volume Where QUICK ORDER NAME = Free Text 3-30 characters TYPE = Set of codes 1:IV FLUID, 2:Inpatient Medications PROVIDER COMMENTS PROMPT = Set of Codes 1:Don't prompt,"""":prompt COMPONENT/ENTRY POINT: IV COMPONENT DESCRIPTION: This entry point is called to process an IV fluid pharmacy quick order. The following array is built before the call is made. ^TMP("PSJQO",$J,1)=Quick Order Name^Type^Orderable Item IEN^Med Route IEN^ Schedule^Instructions^Infusion Rate^Provider Comments Prompt ^TMP("PSJQO",$J,"DD")=Dispense Drug IEN ^TMP("PSJQO",$J,"PC",0)=Last Entry^Number of Entries ^TMP("PSJQO",$J,"PC",x,0)=Provider Comments Line ^TMP("PSJQO",$J,"AD",0)=Last Entry^Number of Entries ^TMP("PSJQO",$J,"AD",x,0)=Orderable Item IEN (for Additive)^Strength^Units ^TMP("PSJQO",$J,"SOL",0)="Last Entry^Number of Entries ^TMP("PSJQO",$J,"SOL",x,0)=Orderable Item IEN (for Solution)^Volume Where QUICK ORDER NAME = Free Text 3-30 characters TYPE = Set of codes 1:IV FLUID, 2:Inpatient Medications PROVIDER COMMENTS PROMPT = Set of Codes 1:Don't prompt,"""":prompt SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2652 IA #: 2652 FILE NUMBER: 42.4 GLOBAL ROOT: DIC(42.4, DATE CREATED: NOV 25, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2652 ID: DIC(42.4, GLOBAL REFERENCE: DIC(42.4,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The Surgery package needs to store the specialty associated with certain surgical admissions and requests permission to point to and read by FileMan the NAME field (#.01) of SPECIALTY file (#42.4). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28427245 SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 2653 IA #: 2653 DATE CREATED: NOV 30, 1998 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORYRA NAME: Rad/Nuc Med - CPRS Orderable Item cleanup ID: ORYRA GENERAL DESCRIPTION: The purpose of this database integration agreement (DBIA) is to correct a discrepancy between the Rad/Nuc Med Common Procedure (#71.3) and the Orderable Items (#101.43) file. Rad/Nuc Med will use routine ORYRA to inactivate records in the Orderable Items file, then initiate a whole file update of the Rad /Nuc Med Procedure file. This final action will ensure that the two files are in synch. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28452527 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: No input variables are needed for this call. SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 2654 IA #: 2654 FILE NUMBER: 50 GLOBAL ROOT: PSDRUG( DATE CREATED: NOV 30, 1998 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: CIRN access to PSDRUG file ID: PSDRUG( GLOBAL REFERENCE: PSDRUG(D0,0) FIELD NUMBER: .01 FIELD NAME: GENERIC NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSDRUG(D0,2) FIELD NUMBER: 31 FIELD NAME: NDC LOCATION: 2;4 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PSDRUG(D0,ND) FIELD NUMBER: 23 FIELD NAME: PACKAGE SIZE LOCATION: ND;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 24 FIELD NAME: PACKAGE TYPE LOCATION: ND;5 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. CIRN needs a read access to the PSDRUG (file #50) to generate HL7 prescription messaging STATUS: Active EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 28259512 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2655 IA #: 2655 FILE NUMBER: 2 GLOBAL ROOT: DPT DATE CREATED: DEC 02, 1998 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2655 ID: DPT GENERAL DESCRIPTION: Direct Global access to ^DPT(DFN) For the purpose of locking a patient file while updating demographic information. The following code is used: L +^DPT(DFN):2 STATUS: Active MAIL MESSAGE: 28333051 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA NUMBER: 2656 IA #: 2656 FILE NUMBER: 9.4 GLOBAL ROOT: DIC(9.4, DATE CREATED: DEC 03, 1998 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2656 ID: DIC(9.4, GENERAL DESCRIPTION: I would like to kill the "AMRG" cross reference (x-ref) for the 'Toolkit' entry in the Package File. The entry that created this x-ref was manually killed by XT*7.3*33 Post-Init routine, but the x-ref was inadvertently left. This would be a once time occurance to clean-up the 'Toolkit' entry in the Package File. The "AMRG" cross reference is a whole file x-ref made on the "File Affected" (Field .01) for the "Affects Record Merge Sub-File" (Field 20) in the Package File (#9.4). STATUS: Active MAIL MESSAGE: 28477754 SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland NUMBER: 2657 IA #: 2657 FILE NUMBER: 63 GLOBAL ROOT: LR( DATE CREATED: SEP 15, 1992 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: CLOZAPINE USE OF LABS ID: LR( STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28459972 SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas SUBSCRIBING DETAILS: The Clozapine Roll-Up software in Mental health uses the CH node of file 63 to determine the number of White Blood Count tests performed on a patient. An entry in the Drug file points to the test at the local site that points to the monitoring test. The "DATE/TIME SPECIMEN TAKEN" (field .01), "DATE REPORT COMPLETED" (field .03), and "SPECIMEN TYPE" (field .05) fields of the "CHEM, HEM, TOX, RIA, SER, etc." multiple in file 63 are used to validate the test before it is added to the count. S YSCLWBCT=0 F J=YSCLIED:0 S J=$O(^LR(YSCLLDFN,"CH",J)) Q:'J Q:J>X I $D(^(J,YSCLLDN)),$P(^(0),"^",5)=YSCLSP,$P(^(0),"^",3) ,$P(^(YSCLLDN),"^") S YSCLWBCT=YSCLWBCT+1 EDITOR: SCHLEHUBER,CAMERON NUMBER: 2658 IA #: 2658 GLOBAL ROOT: DD(2260,0,'ID' DATE CREATED: DEC 10, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: REMOVAL OF ID NODE ID: DD(2260,0,'ID' GLOBAL REFERENCE: DD(2260,0,'ID',1) GENERAL DESCRIPTION: Deletion of "ID" node for identifier which is no longer required. STATUS: Active DURATION: Next Version MAIL MESSAGE: 28514637 SUBSCRIBING PACKAGE: ASISTS ISC: Hines NUMBER: 2659 IA #: 2659 FILE NUMBER: 815 GLOBAL ROOT: PX(815 DATE CREATED: DEC 10, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DISPOSITION HOSPITAL LOCATIONS ID: PX(815 GLOBAL REFERENCE: PX(815,1,"DHL",,0) FIELD NUMBER: .01 FIELD NAME: DISPOSITION HOSPITAL LOCATIONS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Clinic HOSPITAL LOCATION file entry that can be asscoiated with disposition VISIT file entries. GENERAL DESCRIPTION: Patch SD*5.3*137 allows the site to convert old Scheduling encounter information to the PCE/Visit Tracking database as 'historical' visits. Registration disposition information is part of this conversion effort. However, in order to create VISIT file entries for dispositions, the disposition must be associated with a valid clinic entry in the HOSPITAL LOCATION file. Furthermore, for old dispositions which are being conversion, this association does not exist. In order to link a disposition to valid disposition clinic, Scheduling needs to match the medical center division of the disposition with tne medical center division of a valid disposition clinc. The valid disposition clinics are stored in the PCE PARAMETERS file in the DISPOSITION HOSPITAL LOCATIONS multiple. Patch SD*5.3*137 needs 'read' access to this multiple in order to accomplish this mapping. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28530815 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 2660 IA #: 2660 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: DEC 10, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: SCHEDULING CONVERSION FIELDS ID: DPT( GLOBAL REFERENCE: DPT(DFN,'S',,0) FIELD NUMBER: 23.1 FIELD NAME: ENCOUNTER CONVERSION STATUS LOCATION: 0;23 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This field indicates whether or not this appointment was converted during the ACRP Database Conversion (SD*5.3*137). The field is set to '1' after the appointment has been converted by the conversion software. GLOBAL REFERENCE: DPT(DFN,'DIS',,0) FIELD NUMBER: 19 FIELD NAME: ENCOUNTER CONVERSION STATUS LOCATION: 0;19 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This field indicates whether or not this disposition was converted during the ACRP Database Conversion (SD*5.3*137). The field is set to '1' after the disposition has been converted by the conversion software. GENERAL DESCRIPTION: These two control fields are used to track whether the appointment or disposition have been converted as part of patch SD*5.3*137. This DBIA will allow Scheduling to distribute these fields in patch DG*5.3*207. DG*5.3*207 will be distributed to the sites with SD*5.3*137 in a KIDS host file. Also, this DBIA will allow the Scheduling conversion software to update these files via VA FileMan calls. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28534877 COMPONENT/ENTRY POINT: PXKNOEVT SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany NUMBER: 2661 IA #: 2661 DATE CREATED: DEC 11, 1998 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DIR Special variable GENERAL DESCRIPTION: The Alert processor makes use of a special input parameter to Fileman DIR. This is done in XQALERT1, it makes a call with DIR(0)="LV^..." to get user input validated. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28537416 SUBSCRIBING PACKAGE: KERNEL ISC: Oakland SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland SUBSCRIBING DETAILS: DIR(0)="SV" to keep DIR from talking during its evaluation of the set of codes. Also set is DIR("V"). NUMBER: 2662 IA #: 2662 DATE CREATED: DEC 11, 1998 CUSTODIAL PACKAGE: NETWORK HEALTH EXCHANGE CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2662 GENERAL DESCRIPTION: AMIE II is an "umbrella" menu for VA Regional Office users on VistA systems. The IA is for the options included on the menu. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28584347 COMPONENT/ENTRY POINT: AFJXNHEX REQUEST COMPONENT DESCRIPTION: Permission to use Option: NHE Network Health Exchange Options ... [AFJXNHEX REQUEST] SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 2663 IA #: 2663 DATE CREATED: DEC 17, 1998 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2663 GENERAL DESCRIPTION: AMIE II is an "umbrella" menu for VA Regional Office users on VistA systems. The IA is for the options included on the menu. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28584355 COMPONENT/ENTRY POINT: DG INPATIENT INQUIRY EXTENDED COMPONENT DESCRIPTION: Permission to use Option: [DG INPATIENT INQUIRY EXTENDED] Detatiled Inpatient Inquiry COMPONENT/ENTRY POINT: DG PATIENT INQUIRY COMPONENT DESCRIPTION: Permission to use Option: [DG PATIENT INQUIRY] Patient Inquiry COMPONENT/ENTRY POINT: DG REGISTRATION VIEW COMPONENT DESCRIPTION: Permission to use Option: [DG REGISTRATION VIEW] View Registration Data SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 2664 IA #: 2664 DATE CREATED: DEC 24, 1998 CUSTODIAL PACKAGE: REGISTRATION USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGPMOBS NAME: OBSERVATION API ID: DGPMOBS GENERAL DESCRIPTION: Routine DGPMOBS provides three entry points (MVT, PT, and SPEC) to determine if a patient's treating specialty for a specified movement or date/time is or was an observation specialty. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31959340 COMPONENT/ENTRY POINT: $$MVT COMPONENT DESCRIPTION: $$MVT^DGPMOBS(IFN) returns the observation status based on the treating specialty associated with a specified PATIENT MOVEMENT (#405) file entry. VARIABLES: IFN TYPE: Input VARIABLES DESCRIPTION: IFN = PATIENT MOVEMENT (#405) file internal entry number. (Required) VARIABLES: OBS TYPE: Output VARIABLES DESCRIPTION: If specialty associated with the specified PATIENT MOVEMENT (#405) entry is an observation treating specialty, function call returns: 1^FACILITY TREATING SPECIALTY (#45.7) file IEN^FACILITY TREATING SPECIALTY (#45.7) file name^SPECIALTY (#42.4) file IEN^SPECIALTY (#42.4) file name If specialty associated with the specified PATIENT MOVEMENT (#405) entry is not an observation treating specialty, function call returns: 0^FACILITY TREATING SPECIALTY (#45.7) file IEN^FACILITY TREATING SPECIALTY (#45.7) file name^SPECIALTY (#42.4) file IEN^SPECIALTY (#42.4) file name If PATIENT MOVEMENT (#405) file internal entry number not defined or invalid, function call returns: -1^Error condition COMPONENT/ENTRY POINT: $$PT COMPONENT DESCRIPTION: $$PT^DGPMOBS(DFN,MVTDT) returns the observation status for a patient based on the treating specialty on a designated date/time. If no date/time is specified, the current date/time is used. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN = PATIENT (#2) file DFN (Required) VARIABLES: MVTDT TYPE: Input VARIABLES DESCRIPTION: MVTDT = File Manager date/time (Optional) If date/time not defined, the current date/time will be used. VARIABLES: OBS TYPE: Output VARIABLES DESCRIPTION: If patient was in an observation treating specialty on the designated date/time, function call returns: 1^FACILITY TREATING SPECIALTY (#45.7) file IEN^FACILITY TREATING SPECIALTY (#45.7) file name^SPECIALTY (#42.4) file IEN^SPECIALTY (#42.4) file name If patient was not in an observation treating specialty on the designated date/time, function call returns: 0^FACILITY TREATING SPECIALTY (#45.7) file IEN^FACILITY TREATING SPECIALTY (#45.7) file name^SPECIALTY (#42.4) file IEN^SPECIALTY (#42.4) file name If PATIENT (#2) file internal entry number not defined or invalid, function call returns: -1^Error condition COMPONENT/ENTRY POINT: $$SPEC COMPONENT DESCRIPTION: $$SPEC^DGPMOBS(SPIFN) determines if a SPECIALTY (#42.4) file entry is an observation treating specialty. VARIABLES: SPIFN TYPE: Input VARIABLES DESCRIPTION: SPIFN = SPECIALTY (#42.4) file internal entry number. (Required) VARIABLES: TX TYPE: Output VARIABLES DESCRIPTION: 1 = Is an observation specialty 0 = Not an observation specialty -1^Error condition NUMBER: 2665 IA #: 2665 DATE CREATED: DEC 17, 1998 CUSTODIAL PACKAGE: FEE BASIS CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2665 GENERAL DESCRIPTION: AMIE II is an "umbrella" menu for VA Regional Office users on VistA systems. The IA is for the options included on the menu. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28584377 COMPONENT/ENTRY POINT: FBCH PRINT 7078 COMPONENT DESCRIPTION: Permission to use Option: [FBCH PRINT 7078] 7078 Print COMPONENT/ENTRY POINT: FBCNH AMIE COMPONENT DESCRIPTION: Permission to use Option: [FBCNH AMIE] Report of Admissions/Discharges for CNH SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 2666 IA #: 2666 DATE CREATED: DEC 17, 1998 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2666 GENERAL DESCRIPTION: AMIE II is an "umbrella" menu for VA Regional Office users on VistA systems. The IA is for the options included on the menu. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28584385 COMPONENT/ENTRY POINT: GMTS HS MENU COMPONENT DESCRIPTION: Permission to use Option: [GMTS HS MENU] Print Health Summary Menu SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 2667 IA #: 2667 DATE CREATED: DEC 17, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2667 GENERAL DESCRIPTION: AMIE II is an "umbrella" menu for VA Regional Office users on VistA systems. The IA is for the options included on the menu. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28584391 COMPONENT/ENTRY POINT: LRAPAUPT COMPONENT DESCRIPTION: Permission to use Option: [LRAPAUPT] Autopsy protocol/supplementary report COMPONENT/ENTRY POINT: LRAPCYSGL COMPONENT DESCRIPTION: Permission to use Option: [LRAPCYSGL] Print cytopathology report for a patient COMPONENT/ENTRY POINT: LRAPEMSGL COMPONENT DESCRIPTION: Permission to use Option: [LRAPEMSGL] Print electron microscopy report for a patient COMPONENT/ENTRY POINT: LRAPSPSGL COMPONENT DESCRIPTION: Permission to use Option: [LRAPSPSGL] Print surgical pathology report for a patient SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 2670 IA #: 2670 DATE CREATED: DEC 17, 1998 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2670 GENERAL DESCRIPTION: AMIE II is an "umbrella" menu for VA Regional Office users on VistA systems. The IA is for the options included on the menu. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28584421 COMPONENT/ENTRY POINT: SROSRPT COMPONENT DESCRIPTION: Permission to use Option: [SROSRPT] Operation Report SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 2671 IA #: 2671 DATE CREATED: DEC 17, 1998 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2671 GENERAL DESCRIPTION: AMIE II is an "umbrella" menu for VA Regional Office users on VistA systems. The IA is for the options included on the menu. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28584425 COMPONENT/ENTRY POINT: TIU MAIN MENU REMOTE USER COMPONENT DESCRIPTION: Permission to use Option: [TIU MAIN MENU REMOTE USER] Text Integration Utilities (Remote User) SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE ISC: Albany NUMBER: 2672 IA #: 2672 FILE NUMBER: 120.82 GLOBAL ROOT: GMRD(120.82, DATE CREATED: DEC 15, 1998 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2672 ID: GMRD(120.82, GLOBAL REFERENCE: GMRD(120.82,D0, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28556390 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham NUMBER: 2673 IA #: 2673 FILE NUMBER: 9000010.06 GLOBAL ROOT: AUPNVPRV DATE CREATED: DEC 16, 1998 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2673 ID: AUPNVPRV GLOBAL REFERENCE: AUPNVPRV('AD' GLOBAL REFERENCE: AUPNVPRV(D0, FIELD NUMBER: .03 FIELD NAME: POINTER TO VISIT FILE LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: .04 FIELD NAME: PRIMARY/SECONDARY LOCATION: 0;4 ACCESS: Read w/Fileman GENERAL DESCRIPTION: CIRN needs read access to ^AUPNVPRV('AD' ^AUPNVPRV(D0, FIELD .03 LOCATION 0;3 ^AUPNVPRV(D0, FIELD .04 LOCATION 0;4 STATUS: Active MAIL MESSAGE: 28458404 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2675 IA #: 2675 FILE NUMBER: 44 GLOBAL ROOT: SC( DATE CREATED: AUG 13, 2003 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: IA2675 ID: SC( GLOBAL REFERENCE: SC(D0, FIELD NUMBER: 3.5 FIELD NAME: DIVISION LOCATION: 0;15 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: to determine the Medical Center Division IEN associated with the Hospital Location when Batch Printing Progress Notes. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28578986 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE NUMBER: 2676 IA #: 2676 DATE CREATED: DEC 22, 1998 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORXD NAME: Disable & Enable Rad/Nuc Med Order Dialog ID: ORXD GENERAL DESCRIPTION: The purpose of this database integration agreement (DBIA) is to allow the subscribing package to disable and enable Order Dialogs in CPRS. This would allow the specific package the ability to shut down their portion of the Order Dialog without impacting the functionality of other packages that interact with CPRS. This request is part of RA*5.0*6, whose goal is to synchronize the Orderable Items (#101.43) file and the Rad/Nuc Med Common Procedure file. This DBIA is dependent on OR*3.0*4, which exports the latest version of routine ORXD. VIEWER: SCHLEHUBER,CAMERON VIEWER: MO,SELINA VIEWER: INSLEY,MARCIA VIEWER: CEBELINSKI,GREGORY VIEWER: BUECHLER,MELANIE K VIEWER: RUTHERFORD,JERALD F STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28611861 COMPONENT/ENTRY POINT: DISABLE COMPONENT DESCRIPTION: This entry point is called to disable Order Dialogs for a particular package. VARIABLES: PKG TYPE: Input VARIABLES DESCRIPTION: PKG (req'd): package in question, the Order Dialogs for this package will be disabled. VARIABLES: MSG TYPE: Input VARIABLES DESCRIPTION: MSG (opt): package specific disable message. (40 chars maximum) If a message in not passed in by the subscribing package, a generic disable message is inserted. COMPONENT/ENTRY POINT: ENABLE COMPONENT DESCRIPTION: This entry point is called to enable Order Dialogs for a particular package. VARIABLES: PKG TYPE: Input VARIABLES DESCRIPTION: PKG (req'd): package, the Order Dialogs for this package will be disabled. SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 2679 IA #: 2679 DATE CREATED: DEC 30, 1998 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RA07MFN NAME: OE/RR calls RAO7MFN to populate radiology orderables ID: RA07MFN GENERAL DESCRIPTION: ENALL^RAO7MFN is called from the post-installation processes of OR*2.5*49 and CPRS (Order Entry/Results Reporting v3.0) to populate radiology orderable items into OE/RR. STATUS: Active DURATION: Next Version MAIL MESSAGE: 27059736 GOOD ONLY FOR VERSION: OE/RR 2.5-3 COMPONENT/ENTRY POINT: ENALL COMPONENT DESCRIPTION: This entry point is called to run through all radiology orderables. It then calls OE/RR to populate those into the ORDERABLE ITEMS file (#101.43). SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2681 IA #: 2681 FILE NUMBER: 69.9 GLOBAL ROOT: LAB(69.9, DATE CREATED: DEC 30, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR limited use of LAB(69.9 ID: LAB(69.9, GLOBAL REFERENCE: LAB(69.6,1,7,division,0) FIELD NUMBER: .06 FIELD NAME: MINIMUM RESPONSE TIME LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Patch OR*2.5*49 releases some setup functionality in advance of CPRS. This DBIA requests the listed access to LAB(69.9,1,7, for the period of time between the release of OR*2.5*49 and time when the last site installs CPRS. CPRS retrieves the information from calls to lab (which don't exist prior to installation of CPRS). STATUS: Active DURATION: Next Version MAIL MESSAGE: 26946458 GOOD ONLY FOR VERSION: OE/RR v2.5 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2683 IA #: 2683 FILE NUMBER: 79.2 GLOBAL ROOT: RA(79.2, DATE CREATED: DEC 30, 1998 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR calls to 2683 ID: RA(79.2, GLOBAL REFERENCE: RA(79.2,'C' GLOBAL DESCRIPTION: Used to look up entries with the same abbreviation. GLOBAL REFERENCE: RA(79.2,DA,0) FIELD NUMBER: .01 FIELD NAME: TYPE OF IMAGING LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: ABBREVIATION LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: OE/RR references RA(79.2 as follows: 1. During order dialog a lookup is performed to select the IMAGING TYPE 2. The C index is used to loop through entries by ABBREVIATION of the IMAGING TYPE 3. The .01 and 3 fields are referenced via direct reads STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 27059736 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2684 IA #: 2684 DATE CREATED: DEC 31, 1998 CUSTODIAL PACKAGE: LIST MANAGER CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: OE/RR needs to save/restore LM video attributes GENERAL DESCRIPTION: List Manager maintains video attributes in ^TMP("VALM VIDEO". Within Order Entry/Results Reporting and Consult/Request Tracking, list manager is used extensively. One of the key features used is to have list manager actions which envoke other list manager displays. An example would be entering CPRS on the patient selection screen, selecting a patient and getting the cover sheet, selecting to change ot the orders tab (another screen), and adding orders (yet another screen). In order to maintain the video attributes of a particular display, it's necessary for OE/RR and Consults to save off the values in ^TMP("VALM VIDEO" prior to changing screens and kill existing values and restore them when returning. Saving/restoring of this data is done with the MERGE command. This DBIA requests authorization to access the ^TMP("VALM VIDEO",$J) data, kill it, and reset it based on previous values. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28677980 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 2685 IA #: 2685 FILE NUMBER: 8989.51 GLOBAL ROOT: XTV(8989.51 DATE CREATED: DEC 31, 1998 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR direct reference to XTV(8989.51 ID: XTV(8989.51 GLOBAL REFERENCE: XTV(8989.51,'B' GLOBAL DESCRIPTION: Used to lookup the IEN of a particular PARAMETER DEFINITION file entry. GENERAL DESCRIPTION: Within OE/RR, it's necessary to determine a parameter definitions IEN. To do this, the 'B' index of the PARAMETER DEFINITION file (#8989.51) is utilized. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28678942 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2686 IA #: 2686 FILE NUMBER: 8989.5 GLOBAL ROOT: XTV(8989.5, DATE CREATED: DEC 31, 1998 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR direct reference to XTV(8989.5 ID: XTV(8989.5, GLOBAL REFERENCE: XTV(8989.5,'AC' GLOBAL DESCRIPTION: Used to determine the parameter values set for a particular parameter definition. GENERAL DESCRIPTION: Within OE/RR, it's necessary to determine if a parameter is in use. To do this, the parameter definition IEN is determined based on the 'B' index of the PARAMETER DEFINITION file (#8989.51) (see DBIA 2685). Using that IEN, the 'AC' x-ref in the PARAMETERS file (#8989.5) is utilized to determine if any parameter entity is set to a given value. If so, deletion of the item is prohibited. In addition, a one time patch post-install routine (ORY27) used this x-ref when populating a new parameter value based on an existing value. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28678942 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: HEALTHEVET DESKTOP NUMBER: 2687 IA #: 2687 DATE CREATED: DEC 31, 1998 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCPOS1 NAME: OE/RR calls GMRCPOS1 to populate consult orderables ID: GMRCPOS1 GENERAL DESCRIPTION: During the OR*2.5*49 and OE/RR v3 (CPRS) post-install processes, EN^GMRCPOS1 is called. This routine loops through those consult services that can be selected and passes them back to OE/RR for population into the Orderable Items file. STATUS: Active DURATION: Next Version MAIL MESSAGE: 31334257 GOOD ONLY FOR VERSION: OE/RR v2.5-3 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: Used to populate consult orderables SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2688 IA #: 2688 DATE CREATED: DEC 31, 1998 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LR7OV1 NAME: OE/RR calls LR7OV1 to populate lab orderables ID: LR7OV1 GENERAL DESCRIPTION: During the OR*2.5*49 post-install process, EN^LR7OV1 is called. This routine takes values from lab files and uses them to populate LR namespaced parameters in Parameter Tools (XPAR*). These parameters are utilized from within CPRS. STATUS: Active DURATION: Next Version MAIL MESSAGE: 26946458 GOOD ONLY FOR VERSION: OE/RR 2.5 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: Populates lab parameters into Parameter Tools parameters for use by CPRS. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2689 IA #: 2689 FILE NUMBER: 8992 GLOBAL ROOT: XTV(8992, DATE CREATED: MAR 05, 2003 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR references to ALERT file ID: XTV(8992, GLOBAL REFERENCE: XTV(8992,D0,'XQA', FIELD NUMBER: .02 FIELD NAME: ALERT ID LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: MESSAGE TEXT LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: DATA FOR ALERT LOCATION: 1;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .01 FIELD NAME: ALERT DATE/TIME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: XTV(8992,'AXQAN' GLOBAL DESCRIPTION: Direct global read of the x-ref GLOBAL REFERENCE: XTV(8992,'AXQA', GENERAL DESCRIPTION: OE/RR utilizes the alerting functionality extensively. While supported calls are often used, there are also direct references to the ALERT file (#8992) as described in this DBIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 35827896 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: PATIENT REPRESENTATIVE EDITOR: IVEY,JOEL EDITOR: WINN,TAMI NUMBER: 2690 IA #: 2690 DATE CREATED: JAN 02, 1999 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORB3FUP1 NAME: Consults calls to ORB3FUP1 ID: ORB3FUP1 GENERAL DESCRIPTION: Consults calls ORB3FUP1 to delete a CPRS-related alert after it has been processed. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28690761 COMPONENT/ENTRY POINT: DEL(.FLAG,XQAID) COMPONENT DESCRIPTION: Used to delete an alert. VARIABLES: FLAG TYPE: Output VARIABLES DESCRIPTION: Passed by reference, this will contain the word TRUE if the deletion is valid or FALSE if not. VARIABLES: XQAID TYPE: Input VARIABLES DESCRIPTION: The ID information for the KERNEL alert. SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City EDITOR: MCDANIEL,DWIGHT EDITOR: INSLEY,MARCIA EDITOR: ANDERSON,CURTIS L EDITOR: RUTHERFORD,JERALD F NUMBER: 2692 IA #: 2692 DATE CREATED: JAN 02, 1999 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORQPTQ1 NAME: ORQPTQ1 calls ID: ORQPTQ1 CREATOR: HAWSEY,JASON GENERAL DESCRIPTION: ORQPTQ1 provides entry points to provide patient lists by providers, etc. This DBIA will include those calls being used by outside packages. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 48929940 COMPONENT/ENTRY POINT: TEAMPROV(.ARRAY,TEAMIEN) COMPONENT DESCRIPTION: Input an OE/RR team IEN and receive back an array of provides linked to the team. VARIABLES: ARRAY TYPE: Output VARIABLES DESCRIPTION: Return array as follows: ARRAY(#) = New Person IEN ^ New Person Name VARIABLES: TEAMIEN TYPE: Input VARIABLES DESCRIPTION: IEN of OE/RR LIST file (#100.21) COMPONENT/ENTRY POINT: TEAMS(.ARRAY) COMPONENT DESCRIPTION: Input name of array and receive back all OE/RR LIST file (#100.21) IENS and names. If no entries in FILE 100.21, then return: ARRAY(1) = "^No teams found." VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: Name of the array to return data in. Return array as follows: ARRAY(#) = FILE 100.21 IEN ^ FILE 100.21 NAME (.01) COMPONENT/ENTRY POINT: TEAMPTS(.ARRAY,TEAM) COMPONENT DESCRIPTION: Input name of array and OE/RR LIST file (#100.21) IEN. Receive back all patient DFNs and names associated with that FILE 100.21 entry. If no entries, then return: ARRAY(1) = "^No patients found." VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: Name of the array to return data in. Return array as follows: ARRAY(#) = DFN ^ FILE 2 NAME (.01) VARIABLES: TEAM TYPE: Input VARIABLES DESCRIPTION: IEN for a FILE 100.21 entry. COMPONENT/ENTRY POINT: TMSPT(ORY,PT) COMPONENT DESCRIPTION: Input a patient DFN in PT to get a list TEAMS linked to a patient in variable ORY. VARIABLES: ORY TYPE: Both VARIABLES DESCRIPTION: The name of the array to return data in. Return array is as follows: ORY(#) = TEAM IEN ^ TEAM NAME ^ TEAM TYPE VARIABLES: PT TYPE: Input VARIABLES DESCRIPTION: IEN for FILE 2 entry. SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: calls TEAMPROV SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING DETAILS: calls TEAMPTS SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines SUBSCRIBING DETAILS: Calls TEAMS and TEAMPTS. SUBSCRIBING PACKAGE: KERNEL SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: MYHEALTHEVET SUBSCRIBING DETAILS: added 9/15/08 DBA Comments: Required TMSPT(ORY,PT) additional entry point to be added to IA. DATE ACTIVATED: SEP 17, 2008 DATE/TIME EDITED: SEP 15, 2008@19:07 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MONGER,GARY WITH CONCURRENCE OF: HAWSEY,JASON DATE/TIME EDITED: SEP 15, 2008@19:09 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: HAWSEY,JASON DATE/TIME EDITED: SEP 17, 2008@11:30 ACTION: APPROVED AT THE REQUEST OF: HAWSEY,JASON NUMBER: 2693 IA #: 2693 DATE CREATED: JAN 02, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIULQ NAME: TIULQ calls ID: TIULQ GENERAL DESCRIPTION: Entry points in this routine provide extract mechanisms for TIU records. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28690496 COMPONENT/ENTRY POINT: EXTRACT(TIUDA,TIUROOT,TIUERR,DR,TIULINE,TIUTEXT,FORMAT,OV RRIDE) COMPONENT DESCRIPTION: Call to retrieve record and addenda VARIABLES: TIUDA TYPE: Input VARIABLES DESCRIPTION: Internal entry number of note in TIU DOCUMENT file (#8925). [REQUIRED] VARIABLES: TIUROOT TYPE: Input VARIABLES DESCRIPTION: Root of the array in which data should be returned. [OPTIONAL] (set to "^TMP(""TIULQ"",$J)" if not defined on entry). VARIABLES: TIUERR TYPE: Output VARIABLES DESCRIPTION: Error message in format 1^message VARIABLES: DR TYPE: Input VARIABLES DESCRIPTION: List of field numbers to return values for. [OPTIONAL] (set to ".01:.1;1201:1701" if not defined on entry) VARIABLES: TIULINE TYPE: Input VARIABLES DESCRIPTION: Offset line number [OPTIONAL] VARIABLES: TIUTEXT TYPE: Input VARIABLES DESCRIPTION: 1 returns report text. [OPTIONAL] VARIABLES: FORMAT TYPE: Input VARIABLES DESCRIPTION: Set as input parameter for format as accepted by EN^DIQ1. [OPTIONAL] (set to "IE" if not defined on entry) VARIABLES: OVRRIDE TYPE: Input VARIABLES DESCRIPTION: Override ability of user to print record text. [OPTIONAL] SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: Effective with VPR*1*0. DBA Comments: 08/02/13 DT: Added VPR as subscriber, effective with VPR*1*0. DATE/TIME EDITED: AUG 02, 2013@13:43 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 2694 IA #: 2694 DATE CREATED: JAN 02, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIURA1 NAME: TIURA1 calls ID: TIURA1 GENERAL DESCRIPTION: This DBIA documents calls allowed to TIURA1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30387939 COMPONENT/ENTRY POINT: ADDEND1 COMPONENT DESCRIPTION: Provides call to interactively add an addenda to an existing TIU document. VARIABLES: TIUDA TYPE: Input VARIABLES DESCRIPTION: The IEN of the TIU DOCUMENT file (#8925) defining the note for which the addenda will be created. COMPONENT/ENTRY POINT: SIGNER COMPONENT DESCRIPTION: Links a selected document to additional signers via user interaction (if user is allowed to assign additional signers). VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT file (#8925). COMPONENT/ENTRY POINT: $$CHARTONE COMPONENT DESCRIPTION: BOOLEAN extrinsic function. Evaluates whether a given document may be printed for the chart. VARIABLES: $$CHARTONE TYPE: Output VARIABLES DESCRIPTION: 1 - document may be printed 0 - document may not be printed VARIABLES: TIUDA TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT file (#8925) SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: Calls ADDEND1 only. NUMBER: 2695 IA #: 2695 FILE NUMBER: 2 GLOBAL ROOT: DD(2,'AUDIT', DATE CREATED: JAN 04, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DD AUDIT ACCESS ID: DD(2,'AUDIT', GLOBAL REFERENCE: DD(2,'AUDIT',D0) GENERAL DESCRIPTION: CIRN PD would like a DBIA for its direct global read of ^DD(2,"AUDIT". This direct global read is used to identify all of the top level PATIENT (#2) file fields that are currently marked for auditing. We realize this will not get subfile fields within the PATIENT (#2) and we are willing to disregard those fields in our report until an API is provided for all audited fields within the PATIENT (#2) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28574656 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2696 IA #: 2696 FILE NUMBER: .4 GLOBAL ROOT: DIPT( DATE CREATED: JAN 06, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: RECOMPILATION OF PRINT TEMPLATES ID: DIPT( CREATOR: BEUSCHEL,GARY GLOBAL REFERENCE: DIPT(AF GLOBAL DESCRIPTION: This cross-reference has the following structure: ^DIPT("AF",file,field,template)="" ^DIPT("AF",subfile,subfield,template)="" GLOBAL REFERENCE: DIPT(D0,ROU) FIELD NUMBER: 1815 FIELD NAME: ROUTINE INVOKED LOCATION: ROU;E1,13 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: When installing a patch that includes changes to field definitions in a data dictionary, KIDS does not recompile the compiled print templates. Recompilation of print templates may involve the following steps: (1) Traverse the "AF" cross-reference of the ^DIPT global (file #.4) to obtain a list of compiled print templates for the affected fields. The structure of this cross-reference is ^DIPT("AF",file,field,template)="" Subfields would be treated like fields of their respective subfiles, i.e. ^DIPT("AF",subfile,subfield,template)="". (2) For each template that is being recompiled, access ^DIPT(template,"ROU") to determine the compiled routine. (3) Invoke EN^DIPZ to recompile that print template. STATUS: Active MAIL MESSAGE: 56767127 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING DBA Comments: Ed Wolf, Vista Maintenance identified an error in IA #2696 From: Wolf, Ed (EDS) Sent: Thursday, March 29, 2012 6:38 AM To: Beuschel, Gary; OIT PD Integration Control Registrations Cc: Michalak, Don; Harvey, Julie S. (OIT-OED/Bay Pines OITFO) Subject: RE: Can we activate IA # 1127 and subscribe to be Scheduling? - Patch SD*5.3*581 I believe in the end of IA# 2696 should be (3) Invoke EN^DIPZ to recompile that print template. instead of (3) Invoke EN^DIPT to recompile that print template. Gary Beuschel agreed and asked for access to edit the IA text. DATE ACTIVATED: APR 03, 2012 DATE/TIME EDITED: APR 02, 2012@10:30 ACTION: CONTENT CORRECTED AT THE REQUEST OF: BEUSCHEL,GARY DATE/TIME EDITED: APR 03, 2012@11:52 ACTION: APPROVED AT THE REQUEST OF: WOLF,ED WITH CONCURRENCE OF: BEUSCHEL,GARY REMINDER: APR 12, 2012 NUMBER: 2697 IA #: 2697 FILE NUMBER: 603.01 GLOBAL ROOT: YSCL(603.01 DATE CREATED: JAN 06, 1999 CUSTODIAL PACKAGE: MENTAL HEALTH CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2697 ID: YSCL(603.01 GLOBAL REFERENCE: 603.01 FIELD NUMBER: .01 FIELD NAME: CLOZAPINE REGISTRATION NUMBER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Clozapine Registration Number. Free Text. Read access to the cross reference: ^YSCL(603.01,"B",$E(X,1,30),DA) FIELD NUMBER: 1 FIELD NAME: CLOZAPINE PATIENT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Clozapine Patient. Pointer to Patient file (#2). Read access to the cross reference: ^YSCL(603.01,"C",$E(X,1,30),DA) FIELD NUMBER: 2 FIELD NAME: DISPENSE FREQUENCY LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This filed identifies those patients that are eligible to get a 14 day supply of Clozapine medication. GLOBAL DESCRIPTION: This is a file of patients authorized to receive Clozapine. This file is maintained by the National Clozapine Coordinating Center (NCCC) in Dallas. GENERAL DESCRIPTION: The Outpatient and Inpatient Medications packages request permission for read access CLOZAPINE PATIENT LIST file (603.01). The packages also request read access to the ^YSCL(603.01,"B",$E(X,1,30),DA) and ^YSCL(603.01,"C",$E(X,1,30),DA) cross references. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28720392 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2698 IA #: 2698 FILE NUMBER: 101.42 GLOBAL ROOT: ORD(101.42, DATE CREATED: JAN 11, 1999 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Direct access to the Urgency File (101.42) ID: ORD(101.42, GLOBAL REFERENCE: ORD(101.42,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: ABBREVIATION ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Consults package uses the ORDER URGENCY file, 101.42 to convert the orders urgency to a protocol value. The Abbreviation field is used to determine which Protocol to use. The abbreviation is what is sent to Consults in an HL7 message. The use of the Protocol file for recording Urgency will be converted to using the ORDER URGENCY file in a future patch. Rather than storing the protocol pointer representing the Urgency, a pointer will be stored to the ORDER URGENCY file. Until the conversion, direct access is needed to the ABBREVIATION field in the ORDER URGENCY file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28757226 SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: IMAGING DBA Comments: 6/16/14-MC: Originally requested by Elsie Casugay 12/12/12. Elsie has since left team. Recent follow-up emails with Peter Kuzmiak revealed that ICR still needed for project. Patch number is MAG*3*110 with an expected release date of 7/31/14. Added Imaging as a subscriber to ICR. NUMBER: 2699 IA #: 2699 FILE NUMBER: 8925 GLOBAL ROOT: TIU(8925, DATE CREATED: JAN 11, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Direct access to TIU(8925, ID: TIU(8925, GLOBAL REFERENCE: TIU(8925,D0,0) GLOBAL DESCRIPTION: Zeroth node of the TIU Document file. GENERAL DESCRIPTION: TIU is used by the Consult package to store the signed notes resolving a Consult or Procedure request. Consults checks for the existing node in ^TIU(8925,D0,0) before calling TIU utilities. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32647140 SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 2700 IA #: 2700 FILE NUMBER: 8925.1 GLOBAL ROOT: TIU(8925.1, DATE CREATED: JAN 11, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Direct access to the TIU CLASS file (8925.1) ID: TIU(8925.1, GLOBAL REFERENCE: TIU(8925.1,'B','CONSULTS',D0 GLOBAL DESCRIPTION: Lookup on "B" cross-reference for "CONSULTS" TIU Document Definition entry. GLOBAL REFERENCE: TIU(8925.1,D0,0) FIELD NUMBER: .04 FIELD NAME: TYPE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Consults package uses the "B" cross-reference of the TIU Document Definition file (8925.1) to find the "CONSULTS" entry. The TYPE field, fourth piece of the zeroth node, of the consults entry is used to check for "CL" or "DC" (Class or Document Class Type). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28690496 SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 2701 IA #: 2701 DATE CREATED: JAN 12, 1999 CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MPIF001 NAME: MPIF001 ID: MPIF001 GENERAL DESCRIPTION: Function APIs to return values on the MPI node in the Patient file. This DBIA documents some entry points for accessing the MPI node in the Patient file for use by the CIRN developers and others that may need this data. STATUS: Active MAIL MESSAGE: 28752601 COMPONENT/ENTRY POINT: $$GETICN COMPONENT DESCRIPTION: $$GETICN^MPIF001(DFN) This function returns the ICN, including checksum for a given DFN or -1^error message. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN - IEN of patient in Patient file (#2) COMPONENT/ENTRY POINT: $$GETDFN COMPONENT DESCRIPTION: $$GETDFN^MPIF001(ICN) This function returns the IEN of the patient in the Patient file for a given ICN or -1^error message. VARIABLES: ICN TYPE: Input VARIABLES DESCRIPTION: ICN - Integration Control Number (ICN) (not including checksum) for a given patient in the Patient file (#2). COMPONENT/ENTRY POINT: $$CMOR2 COMPONENT DESCRIPTION: $$CMOR2^MPIF001(DFN) This function returns the CMOR Site Name for a given DFN or -1^error message. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN - IEN of patient in Patient file (#2). COMPONENT/ENTRY POINT: $$CMORNAME COMPONENT DESCRIPTION: $$CMORNAME^MPIF001(CIEN) This function returns CMOR Site Name for a given Institution IEN or -1^error message. VARIABLES: CIEN TYPE: Input VARIABLES DESCRIPTION: CIEN - IEN for entry in Institution file (#4). COMPONENT/ENTRY POINT: $$GETVCCI COMPONENT DESCRIPTION: $$GETVCCI^MPIF001(DFN) This function returns CMOR Station Number for a given DFN or -1^error message. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN - IEN of patient in Patient file (#2). COMPONENT/ENTRY POINT: $$IFLOCAL COMPONENT DESCRIPTION: $$IFLOCAL^MPIF001(DFN) This function is used to see if a patient has a Local ICN. Returning: 1 = patient has a Local ICN. 0 = patient does not exist, DFN is not defined or no MPI node OR Patient doesn't have a local ICN. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN - IEN of patient in Patient file (#2). COMPONENT/ENTRY POINT: $$IFVCCI COMPONENT DESCRIPTION: $$IFVCCI^MPIF001(DFN) This function returns 1 if your facility is the CMOR for the given patient. Returning: 1 = your site is the CMOR. -1 = your site is NOT the CMOR. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN - IEN of patient in Patient file (#2). COMPONENT/ENTRY POINT: $$HL7CMOR COMPONENT DESCRIPTION: $$HL7CMOR^MPIF001(DFN,SEP) This function returns the CMOR Station Number and Institution Name for a given patient. Returns: Station Number Institution Name or -1^error message. SEP defaults to ^ if not defined. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN = IEN for patient in Patient file (#2). VARIABLES: SEP TYPE: Input VARIABLES DESCRIPTION: SEP = delimeter to separate station number and name. Not required. Defaults to ^ if not provided. COMPONENT/ENTRY POINT: GETICN COMPONENT DESCRIPTION: See $$GETICN NUMBER: 2702 IA #: 2702 DATE CREATED: JAN 12, 1999 CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MPIFAPI NAME: MPIFAPI ID: MPIFAPI GENERAL DESCRIPTION: Functions to return the MPI node, Subscriptioon Control Number from the MPI Node, the name of the HL7 Logical Link for the MPI and to return the next Local Integration Control Number. These APIs are provided for the CIRN developers and others that may need this data. STATUS: Active MAIL MESSAGE: 28752666 COMPONENT/ENTRY POINT: $$MPINODE COMPONENT DESCRIPTION: $$MPINODE^MPIFAPI(DFN) This function returns the MPI node for a given patient in the Patient file (#2). Returning: MPI node OR -1^error message. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN - IEN of patient in Patient file (#2). COMPONENT/ENTRY POINT: $$SUBNUM COMPONENT DESCRIPTION: $$SUBNUM^MPIFAPI(DFN) This function returns the Subscription Control Number from the MPI node for a given patient in the Patient file (#2). Returns: Subscription Control Number OR -1^error message. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN = IEN of patient in the Patient file (#2). COMPONENT/ENTRY POINT: $$EN2 COMPONENT DESCRIPTION: $$EN2^MPIFAPI() This function creates and returns the next Local ICN (Integration Control Number) and ICN Checksum. Returns: ICN V ICN Checksum (no spaces). COMPONENT/ENTRY POINT: $$MPILINK COMPONENT DESCRIPTION: This function returns the name of the MPI logical link from the HL Logical Link file. COMPONENT/ENTRY POINT: GETADFN COMPONENT DESCRIPTION: This API will return the DFN for a given ICN ONLY if the ICN is the active ICN for a patient. VARIABLES: ICN TYPE: Input VARIABLES DESCRIPTION: This is the Integration Control Number that is being used to find a given patient. VARIABLES: DFN TYPE: Output VARIABLES DESCRIPTION: The IEN of the patient in the Patient (#2) file that currently has this ICN as the active ICN (stored in field 991.01). ICN is not found -1^error message is returned. EDITOR: CHESNEY,CHRISTINE M NUMBER: 2703 IA #: 2703 DATE CREATED: JAN 12, 1999 CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MPIF001 NAME: $$CHANGE MPIF001 ID: MPIF001 GENERAL DESCRIPTION: This function updates the CIRN Master of Record (991.03) field in the Patient (#2) file on the MPI node. This is being provided for use by the CIRN developers. STATUS: Active MAIL MESSAGE: 28765585 COMPONENT/ENTRY POINT: $$CHANGE COMPONENT DESCRIPTION: $$CHANGE^MPIF001(DFN,VCCI) This function updates the CIRN MASTER OF RECORD (#991.03) field in the Patient file (#2). Returning: 1 - successfully updated OR -1^error message - problem while updating. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN - IEN of patient in Patient file (#2). VARIABLES: VCCI TYPE: Input VARIABLES DESCRIPTION: VCCI - IEN from the Institution file of the station that is to be the new CMOR. SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 2706 IA #: 2706 DATE CREATED: JAN 13, 1999 CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MPIFAPI NAME: $$UPDATE MPIFAPI ID: MPIFAPI GENERAL DESCRIPTION: This API will allow the calling package to update the MPI node fields (991.01-991.05) in the Patient file (#2). This is being provided for the CIRN developers. STATUS: Active MAIL MESSAGE: 28774832 COMPONENT/ENTRY POINT: $$UPDATE COMPONENT DESCRIPTION: $$UPDATE^MPIFAPI(DFN,ARR) This function update fields on the MPI node passed in ARR(field number) for a patient in the Patient file. Fields 991.01-991.05 only. Returning: -1^error message if unable to update fields OR 0 if successfully updated fields. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN - IEN of patient in the Patient file (#2). VARIABLES: ARR TYPE: Input VARIABLES DESCRIPTION: ARR - array of values for each field to be updated, where the subscript is the field number to be updated. SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: CORBA SERVICES NUMBER: 2707 IA #: 2707 DATE CREATED: JAN 13, 1999 CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MPIFMER NAME: MER MPIFMER ID: MPIFMER GENERAL DESCRIPTION: This routine will trigger the merge/change ICN message to be sent to the MPI and any sites subscribing to this patient via CIRN. This is being provided to the CIRN/DG developers to support the CIRN/MPI effort. STATUS: Active MAIL MESSAGE: 28625553 COMPONENT/ENTRY POINT: MER COMPONENT DESCRIPTION: MER^MPIFMER(PDFN,OLD,ERROR,FLG) this routine is triggered off a change to the Integration Control Number (991.01) field (ICN) in the Patient file (#2) when an old ICN, that is not a local ICN. It will create a Change/Merge ICN message to be sent to the MPI and CIRN subscribers for this patient. VARIABLES: PDFN TYPE: Input VARIABLES DESCRIPTION: DFN - IEN for patient in the Patient file (#2). VARIABLES: OLD TYPE: Input VARIABLES DESCRIPTION: OLD - the ICN value being replaced. VARIABLES: ERROR TYPE: Both VARIABLES DESCRIPTION: ERROR - is passed into the MER call by reference to return any error messages that may occur during the procedure. VARIABLES: FLG TYPE: Input VARIABLES DESCRIPTION: FLG - not required, if not defined is set to null. If the FLG field is not defined and your facility is not the CMOR, the change icn message will not be sent. SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 2708 IA #: 2708 DATE CREATED: JAN 13, 1999 CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MPIFQ1 NAME: DELETE MPIFQ1 ID: MPIFQ1 GENERAL DESCRIPTION: DELETE^MPIFQ1 is used to remove the entry in the Patient file that was just created. It is to be used when the direct connect to the MPI returned a list of patients that are potential matches and asked the user to select one. The user then selects as the match, a patient that is currently in the local Patient file. the Patient file entry that was just created would then be removed. This will only happen if the patient was just entered into the Patient file (#2). This is being supplied to support the MPI/CIRN effort. STATUS: Active MAIL MESSAGE: 28625414 COMPONENT/ENTRY POINT: DELETE COMPONENT DESCRIPTION: DELETE^MPIFQ1(DFN) - This line tag removes the stub Patient file entry that was just created (DFN), when the MPI returned a list of potnetial matches and the user selected a patient that is already in the local Patient file (#2). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN - IEN of patient in Patient file (#2) to be deleted. SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 2709 IA #: 2709 FILE NUMBER: 200 GLOBAL ROOT: VA(200 DATE CREATED: APR 26, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: New Person file ID: VA(200 GLOBAL REFERENCE: VA(200,'A16' GENERAL DESCRIPTION: The Laboratory package is cleaning up a reference to the Person file (#16). We need read access only to the A16 cross reference of the New Person file (#200). This access is only for use with patch LR*5.2*237. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29459007 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 2710 IA #: 2710 DATE CREATED: JAN 13, 1999 CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RGVCCMR2 NAME: CALC RGVCCMR2 ID: RGVCCMR2 GENERAL DESCRIPTION: Function API to calculate the CIRN CMOR Activity Score for an individual patient. This is being provided for the MPI developers to allow for re-calculating the CIRN CMOR Activity Score during the CMOR Batch Comparision job. STATUS: Active MAIL MESSAGE: 28622433 COMPONENT/ENTRY POINT: CALC COMPONENT DESCRIPTION: This entry point calculates the CIRN CMOR activity score for a given patient. The patient's ien from the Patient file is set in the variable RGDFN before making the call to CALC. The fields CMOR ACTIVITY SCORE (991.06) and SCORE CALCULATION DATE (991.07) in the Patient file (#2) are updated by CALC for patient RGDFN. VARIABLES: RGDFN TYPE: Input VARIABLES DESCRIPTION: RGDFN - IEN of the patient in the Patient file (#2). RGDFN is not passed as a formal parameter, but is defined before calling CALC. SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA SUBSCRIBING PACKAGE: TOOLKIT ISC: Oakland SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 2711 IA #: 2711 FILE NUMBER: 58.8 GLOBAL ROOT: PSD(58.8 DATE CREATED: APR 28, 1999 CUSTODIAL PACKAGE: DRUG ACCOUNTABILITY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2711 ID: PSD(58.8 GENERAL DESCRIPTION: This DBIA is to be used as an open agreement between Drug Accountability and Controlled Substances. The terms of this agreement are to allow Controlled Substances access to any field within the DRUG ACCOUNTABILITY STATS file (#58.8). The access method can be either Direct Read/Write access, or by using FileManager to obtain or create data. The reason for this agreement is that prior to the release of Version 3.0 of Drug Accountability, this file was the property of Controlled Substances. STATUS: Active MAIL MESSAGE: 29470880 SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 2712 IA #: 2712 DATE CREATED: JAN 14, 1999 CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: USRLM NAME: DBIA2712 ID: USRLM GENERAL DESCRIPTION: The function ISTERM offers an approved means of identifying whether a user is currently terminated, as supported by DBIA 10060, until such time as Kernel provides a comparable function. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29037826 COMPONENT/ENTRY POINT: $$ISTERM(USER) COMPONENT DESCRIPTION: This function evaluates whether the USER identified by the pointer to file 200 passed as its one required parameter is terminated at the time of the call. VARIABLES: USER TYPE: Input VARIABLES DESCRIPTION: This is the IEN of the user in question in file 200. SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 2713 IA #: 2713 DATE CREATED: JAN 14, 1999 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORB3F1 NAME: Consults calls to ORB3F1 ID: ORB3F1 GENERAL DESCRIPTION: This agreement will allow consults to call the following tag(s) in routine ORB3F1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28690761 COMPONENT/ENTRY POINT: $$XQAKILL(ORN) COMPONENT DESCRIPTION: This extrinsic function will return a 0 if a notification should be deleted for ALL recipients or a 1 if the notification should be deleted just for the current recipient (the one currently processing the alert). VARIABLES: ORN TYPE: Input VARIABLES DESCRIPTION: The IEN of the entry in the OE/RR NOTIFICATIONS denoting the notification being processed. SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CARE MANAGEMENT EDITOR: INSLEY,MARCIA EDITOR: ANDERSON,CURTIS L EDITOR: RUTHERFORD,JERALD F NUMBER: 2714 IA #: 2714 FILE NUMBER: 991.8 GLOBAL ROOT: RGSITE(991.8, DATE CREATED: JAN 19, 1999 CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Input Template to CRIN Site Parameter 991.8 ID: RGSITE(991.8, GENERAL DESCRIPTION: MPIF is requesting to be able to create and utilize an input template to the CIRN Site Parameter file (#991.8) called MPIF SITE PARAMETERS to support in editing the CMOR Request related fields. STATUS: Active MAIL MESSAGE: 28783876 SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA NUMBER: 2716 IA #: 2716 DATE CREATED: JAN 19, 1999 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMSTAPI NAME: DG MST STATUS API'S ID: DGMSTAPI GENERAL DESCRIPTION: The purpose of these API's is to facilitate the entry and retrieval of Military Sexual Trauma status information on veterans. The primary mechanism is within the Registration package, but data will be requested from, and eventually updated from Scheduling and Patient Care Encounters. VAH Directive 98-058 "Sexual Trauma Counseling Care and Services", provides the guidance on this data collection. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28755060 COMPONENT/ENTRY POINT: $$NEWSTAT(DFN,DGSTAT,DGDATE,DGPROV,DGSITE,DGXMIT) COMPONENT DESCRIPTION: Will enter new or edited Military Sexual Trauma (MST) status data for a veteran into the MST HISTORY File (#29.11). This is an historical entry and will be added in addition to any previous entries. A verification check is made on the new or edited MST status entry before allowing any data to be filed to file (#29.11). If the verification check is successful and the DGXMIT variable equals a value of 1, an Enrollment Full Data Transmission (ORF/ORU~Z07) HL7 message will be triggered to the VistA Enrollment module for transmission to the Health Eligibility Center (HEC). The Internal Entry Number (IEN) of the new entry in File (#29.11) is returned if the entry was successful, else an error message is returned in the format: -1^error message. The HEC will transmit the new MST Status data to all sites of record for the patient via an Enrollment/Eligibility (ORF/ORU~Z11) HL7 message. No HL7 Z07 message will be triggered if the MST Status change event is the result of an update received from the HEC via an HL7 Z11 message. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal entry number for patient in the PATIENT File (#2) VARIABLES: DGSTAT TYPE: Input VARIABLES DESCRIPTION: MST Status code, "Y,N,D,U" Y - Yes, Screened reports MST N - No, Screened does not report MST D - Screened, declines to answer U - Unknown, not screened VARIABLES: DGDATE TYPE: Input VARIABLES DESCRIPTION: Date of MST status change [Optional]. Defaults to NOW if parameter is NULL. VARIABLES: DGPROV TYPE: Input VARIABLES DESCRIPTION: Provider making MST status determiniation, pointer to ^VA(200) VARIABLES: $$NEWSTAT TYPE: Output VARIABLES DESCRIPTION: Returns either the IEN of the new file entry, or -1^error message if file update fails. VARIABLES: DGXMIT TYPE: Input VARIABLES DESCRIPTION: HL7 trasmit flag [Optonal]. 0 = don't queue a Z07 message. 1 = queue a Z07 message [Default]. VARIABLES: DGSITE TYPE: Input VARIABLES DESCRIPTION: Site Determining MST Status [Optional]. IEN pointer of the INSTITUTION file (#4) for a Station number. If this parameter is NULL, the current Primary Station number pointer to the INSTITUTION file (#4) will INTEGRATION REFERENCES LIST MAR 18,2015 11:24 PAGE 8 -------------------------------------------------------------------------------- be filed. COMPONENT/ENTRY POINT: $$GETSTAT(DFN,DGDATE) COMPONENT DESCRIPTION: Entry point $$GETSTAT^DGMSTAPI(DFN,DGDATE) will return the current MST status for a patient from the MST HISTORY File (#29.11) AS OF THE DATE passed in as DGDATE. Any MST status entries after the date in DGDATE will be ignored. DGDATE is optional, if it is not passed in, a date of TODAY will be used. To return the most recent MST status for a patient, call GETSTAT^DGMSTAPI(DFN) only. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of patient in the PATIENT File (#2) VARIABLES: DGDATE TYPE: Input VARIABLES DESCRIPTION: Date to check MST status on, [Optional]. If not passed in, default of TODAY is used. VARIABLES: $$GETSTAT TYPE: Output VARIABLES DESCRIPTION: Piece 1 - IEN of entry in MST HISTORY File (#29.11) Piece 2 - Internal value of MST Staus ("Y,N,D,U") Piece 3 - Date of status change Piece 4 - IEN of provider making determination, NEW USER File (#200) Piece 5 - IEN of user who entered status, NEW USER File (#200) Piece 6 - External format of MST Status Piece 7 - IEN pointer of the INSTITUTION file (#4). If no MST history entry is found for the patient, a "0^U" will be returned. If an error occurred while retrieving the MST status, a "-1^^Error msg" will be returned. NUMBER: 2718 IA #: 2718 GLOBAL ROOT: %ZTSCH('WAIT') DATE CREATED: JAN 20, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Check TaskMan State ID: %ZTSCH('WAIT') GENERAL DESCRIPTION: FileMan KIDS Enviromental Check routines: DIENVWRN (Warn the installer, but allow the install to continue) and DIENVSTP (Stop the install) need to check TaskMan's enviroment to see if TaskMan is in a STOPed state or is in the "WAIT" state. There is a supported call to: $$TM^%ZTLOAD which returns whether or not TaskMan is running, but not if TaskMan is in a "WAIT" state. The following code is used in routines DIENVWRN and DIENVSTP to check for these conditions: TMCHK ; Check to see if TaskMan is still running S X=$$TM^%ZTLOAD I X,'$D(^%ZTSCH("WAIT")) D FileMan would like a temporary intergration agreement, with the Kernel, until such time as $$TM^%ZTLOAD can return all three conditions Running, Waiting, and Stopped. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28826436 SUBSCRIBING PACKAGE: VA FILEMAN ISC: Oakland NUMBER: 2719 IA #: 2719 GLOBAL ROOT: %ZIS(14.5,'LOGON', DATE CREATED: JAN 20, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Logons Inhibited ID: %ZIS(14.5,'LOGON', GLOBAL REFERENCE: %ZIS(14.5,'LOGON',) GENERAL DESCRIPTION: FileMan KIDS Enviromental Check routines: DIENVWRN (Warn the installer, but allow the install to continue) and DIENVSTP (Stop the install) need to check if Logons have been Inhibited and the following code is being used: LINH ; Check to see if Logons are Inhibited D GETENV^%ZOSV ; $P(Y,"^",2) = Installing Volume S X=+$G(^%ZIS(14.5,"LOGON",$P(Y,"^",2))) I 'X D Q ; Bail Out of Install FileMan would like a temporary intergration agreement, with the Kernel, until such time a single call can be developed that will return whether or not Logons have been Inhibited. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28826562 SUBSCRIBING PACKAGE: VA FILEMAN ISC: Oakland NUMBER: 2722 IA #: 2722 DATE CREATED: JAN 21, 1999 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXBAPI21 NAME: DBIA2722 ID: PXBAPI21 GENERAL DESCRIPTION: Integration Agreement between PCE and EVENT CAPTURE for use of CLASS^PXBAPI21. After answering "No" to "Service Connected:", the user expects to see the prompt(s) for AO/IR/EC as appropriate for the patient (just as in Scheduling checkout), but these prompts are never seen for SC 50-100% vets. The reason being that Event Capture uses calls to SC^SDCO22, AO^SDCO22, EC^SDCO22, and IR^SDCO22 to determine which of the classification questions should be asked. (That takes place in ASKCLASS^ECUTL1 and GETCLASS^ECUTL1.) AO^SDCO22, EC^SDCO22, and IR^SDCO22 always return zero for an SC 50-100% vet -- therefore Event Capture never prompts for any of these classifications even though the encounter is not related to the patient's service connected disabilities. Looking into the Scheduling checkout functionality, it is CLASS^PXBAPI21 which allows this scenario to be properly handled (starting in INTV^PXAPI) -- it allows the user to answer AO/IR/EC for SC 50-100% vets after specifying that the encounter isn't service connected. Specifically, the call will be constructed as follows: N PBXDATA D NOW^%DTC S DATE=% D CLASS^PXBAPI21("",DFN,DATE,1,"") An example of user prompts for an SC 50-100% patient with exposure to AO, IR, and EC follows: --- Classification --- [Required] Was treatment for SC Condition? NO Was treatment related to Agent Orange Exposure? YES Was treatment related to Ionizing Radiation Exposure? YES Was treatment related to Environmental Contaminant Exposure? YES Data is returned as follows: PXBDATA(1)=0^1 <-- Agent Orange PXBDATA(2)=0^1 <-- Ionizing Radiation PXBDATA(3)=0^0 <-- Service Connected PXBDATA(4)=0^1 <-- Environmental Contaminants where the 2nd piece indicates the user's answer to the classification prompt -- 0=NO, 1=YES STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28784092 COMPONENT/ENTRY POINT: CLASS COMPONENT DESCRIPTION: Subroutine with parameter list -- CLASS^PXBAPI21(PXBOUTEN,PXBPAT,PXBVSTDT,PXBHLOC,PXBVST) Prompts for patient encounter classifications for SC/AO/IR/EC. Results returned in local PXBDATA array. VARIABLES: PXBOUTEN TYPE: Input VARIABLES DESCRIPTION: EVENT CAPTURE will always set variable PXBOUTEN to null. VARIABLES: PXBPAT TYPE: Input VARIABLES DESCRIPTION: EVENT CAPTURE wil always place the internal entry number from the PATIENT file (#2) for the patient of interest into variable PXBPAT. VARIABLES: PXBHLOC TYPE: Input VARIABLES DESCRIPTION: EVENT CAPTURE will always set variable PXBHLOC to the value 1. VARIABLES: PXBVST TYPE: Input VARIABLES DESCRIPTION: EVENT CAPTURE will always set variable PXBVST to null. VARIABLES: PXBVSTDT TYPE: Input VARIABLES DESCRIPTION: EVENT CAPTURE will always place the current date/time in standard FileMan formart into variable PXBVSTDT. SUBSCRIBING PACKAGE: EVENT CAPTURE ISC: Albany NUMBER: 2723 IA #: 2723 DATE CREATED: JAN 25, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMXAPIB NAME: MAILBOX AND BASKET API ID: XMXAPIB GENERAL DESCRIPTION: The APIs in this DBIA perform mailbox and basket actions. If any errors occur, the following variables will be defined: XMERR - The number of errors ^TMP("XMERR",$J,,"TEXT",)= Following is information on some common input parameters: XMDUZ - The user (DUZ or enough of the user's name, alias, initials, or nickname for a positive ID) for whom the API is being called. An FM lookup into the ^VA(200, NEW PERSON file will be performed. XMK - The basket (IEN or enough of its name for a positive ID) for which the API is being called. XMTROOT - (optional) The target root to receive the requested list. This quoted string must be a closed root. The node "XMLIST" will be added underneath it. This is an optional parameter. It defaults to ^TMP("XMLIST",$J). STATUS: Active MAIL MESSAGE: 28881098 COMPONENT/ENTRY POINT: CRE8MBOX COMPONENT DESCRIPTION: Create a mailbox for a user. That is, add the user to file ^XMB(3.7, MAILBOX. The user's IEN in this file is the same as the user's IEN in ^VA(200, NEW PERSON file, that is, the user's DUZ. Usage: D CRE8MBOX^XMXAPIB(XMDUZ,XMDATE) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user for whom a mailbox should be created. User must already exist in ^VA(200,. See General Description for further information. VARIABLES: XMDATE TYPE: Used VARIABLES DESCRIPTION: (optional) Users who are being reinstated after not having worked here for a while may be restricted from seeing messages earlier than a certain date. If the user is a first-time user, then this parameter has no effect and shouldn't be used. Possible values: =0 or null (default) - The user may access any message on the system which was ever addressed to the user. =date - The user may not access any message addressed to the user on the system earlier than this date, unless it is already in the user's mailbox or if someone forwards it to the user. The date must be a FileMan date or any date format which FileMan recognizes. COMPONENT/ENTRY POINT: FLTRMBOX COMPONENT DESCRIPTION: Filter all messages in a user's mailbox. Runs all messages in all baskets in the user's mailbox through any filters which may exist for the mailbox. Only the user or a surrogate may use this API. Usage: D FLTRMBOX^XMXAPIB(XMDUZ,.XMMSG) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: See General Description. VARIABLES: XMMSG TYPE: Output VARIABLES DESCRIPTION: If filtering is completed successfully, contains the message, "Mailbox filtered". COMPONENT/ENTRY POINT: QMBOX COMPONENT DESCRIPTION: Query a mailbox for new messages. Only the user or a surrogate may use this API. Usage: D QMBOX^XMXAPIB(XMDUZ,.XMMSG) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: See General Description. VARIABLES: XMMSG TYPE: Output VARIABLES DESCRIPTION: String giving information on the user's new messages. If user has no new messages, string is 0 (zero). If user has new messages, string contains the following up-arrow delimited pieces of information: Piece 1: number of new messages in the mailbox Piece 2: does the user have priority mail (0=no; 1=yes) Piece 3: number of new messages in the IN basket Piece 4: date/time (FM format) that the last message was received Piece 5: have there been any new messages since the last time this API was called? (0=no; 1=yes) COMPONENT/ENTRY POINT: TERMMBOX COMPONENT DESCRIPTION: Remove all traces of a user from MailMan globals. Only a Postmaster surrogate or XMMGR key holder may use this API. Usage: D TERMMBOX^XMXAPIB(XMDUZ) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user whose mailbox is to be terminated. User must still exist in ^VA(200,. See General Description for further information. COMPONENT/ENTRY POINT: CRE8BSKT COMPONENT DESCRIPTION: Create a basket. Only the user or a surrogate may use this API. If the user is SHARED,MAIL, then the surrogate must be a Postmaster surrogate or XMMGR key holder. Usage: D CRE8BSKT^XMXAPIB(XMDUZ,XMKN,.XMK) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user for whom a basket is to be created. See General Description for more information. VARIABLES: XMKN TYPE: Input VARIABLES DESCRIPTION: The name of the basket to be created. It must be free text, from 2 to 30 characters. VARIABLES: XMK TYPE: Output VARIABLES DESCRIPTION: The IEN of the basket which was created. COMPONENT/ENTRY POINT: DELBSKT COMPONENT DESCRIPTION: Delete a basket. The special baskets (IN and WASTE) may not be deleted. Only empty baskets may be deleted, unless XMFLAGS contains "D". Only the user or a surrogate may use this API. If the user is SHARED,MAIL, then the surrogate must be a Postmaster surrogate or XMMGR key holder. Usage: D DELBSKT^XMXAPIB(XMDUZ,XMK,XMFLAGS) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user for whom a basket is to be deleted. See General Description for more information. VARIABLES: XMK TYPE: Input VARIABLES DESCRIPTION: Basket to be deleted. See General Description for more information. VARIABLES: XMFLAGS TYPE: Used VARIABLES DESCRIPTION: (optional) Used to control processing. May contain any of the following: D - Delete this basket even if there are messages in it. COMPONENT/ENTRY POINT: FLTRBSKT COMPONENT DESCRIPTION: Filter messages in a basket. Runs all messages in a basket through any filters which may exist for the mailbox. Only the user or a surrogate may use this API. If the user is SHARED,MAIL, then the surrogate must be a Postmaster surrogate or XMMGR key holder. Usage: D CRE8MBOX^XMXAPIB(XMDUZ,XMK,.XMMSG) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user whose basket is to be filtered. See General Description for more information. VARIABLES: XMK TYPE: Input VARIABLES DESCRIPTION: The basket to be filtered. See General Description for more information. VARIABLES: XMMSG TYPE: Output VARIABLES DESCRIPTION: If filtering is completed successfully, contains the message, "Basket filtered". COMPONENT/ENTRY POINT: LISTBSKT COMPONENT DESCRIPTION: Get a list of baskets in a mailbox. Gets a list (similar in format to that produced by LIST^DIC) of a user's baskets, optionally restricting the list to only those baskets with new mail, and/or those baskets whose name starts with a certain string. Note: Regardless of the alphabetic order you request, lower-case names sort separately from upper-case names. Therefore, an all upper-case cross reference (under "BSKT") is provided if you do not limit the number of entries returned. Usage: D LISTBSKT^XMXAPIB(XMDUZ,XMFLAGS,XMAMT,.XMSTART,XMPART,XMTROOT) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user for whom a basket list is to be compiled. See General Description for more information. VARIABLES: XMFLAGS TYPE: Used VARIABLES DESCRIPTION: (optional) Used to control processing. May be any combination of the following: B - Backwards alpha order (default is alpha order) N - List only those baskets with new messages. VARIABLES: XMAMT TYPE: Used VARIABLES DESCRIPTION: (optional) How many baskets should be in the list? Possible values: - This many. Upper case xref (under "BSKT") is NOT provided. * - All baskets (default). Upper case xref (under "BSKT") is provided. VARIABLES: XMSTART TYPE: Both VARIABLES DESCRIPTION: (optional) Provides a starting point from which to get the list. It is used to start the lister going. The calling routine does not need to set it. Default is to start with the lowest numbered basket IEN and to start, in each successive call, where the previous call left off. The lister will keep it updated from call to call. Note: This parameter is used if XMAMT is a number, and you intend to call this entry point repeatedly until there are no more baskets. VARIABLES: XMPART TYPE: Used VARIABLES DESCRIPTION: (optional) Get a list only of those baskets whose name starts with this string. VARIABLES: XMTROOT TYPE: Used VARIABLES DESCRIPTION: (optional) The target root to receive the message list. See General Description for more information. COMPONENT/ENTRY POINT: LISTMSGS COMPONENT DESCRIPTION: Get a list a messages in a mailbox or in the Message file. Gets a list (similar in format to that produced by LIST^DIC) of messages in one basket or all baskets, optionally based on certain criteria. Also can get a list of messages in the Message file which were sent to or by the user and are not necessarily still in the user's mailbox. The IENs of the messages (in the message file 3.9) are returned. Only the user or a surrogate may use this API. Also enables 'Super Search' of all messages in the message file, regardless of who sent them. This search should only be used in coordination with the site's ISO, and is intended to be used to gather evidence in cases such as EEO harassment. Only holders of the XM SUPER SEARCH key may use this capability. Usage: D LISTMSGS^XMXAPIB(XMDUZ,XMK,XMFLDS,XMFLAGS,XMAMT,.XMSTART,.XMCRIT,XMTROOT) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user for whom a message list is to be compiled. See General Description for more information. VARIABLES: XMK TYPE: Input VARIABLES DESCRIPTION: The basket to look in. Possible values: IEN or name - look in this basket only * - look in all baskets ! - look in the Message file. VARIABLES: XMFLDS TYPE: Used VARIABLES DESCRIPTION: (optional) A string containing a list, separated by ';', of fields to retrieve. Default is none. Possible values include any combination of the following, separated by ';': (e.g., "SUBJ;DATE") BSKT - basket (default: ^) Optionally followed by ":" and I - for basket IEN only (no 2nd piece) X - adds basket name xref (If XMK="!", and the message is not in the user's mailbox, will be set to "0^* N/A *".) DATE - date sent (default:^
Optionally followed by ":" and I - for internal only (no 2nd piece) F - for FM date as the 2nd piece X - adds FM date xref FROM - message from (default: ^) Optionally followed by ":" and I - for internal only (no 2nd piece) X - adds external from xref LINE - number of lines in the message NEW - is the message new? (0=no; 1=yes; 2=yes, and priority, too) PRI - is the message priority? (0=no; 1=yes) READ - how much of the message has the user read? - has not read the message at all 0 - has read the message, but no responses - has read through this response RESP - how many responses does the message have? 0 - none - this many SEQN - sequence number in basket SUBJ - message subject (always external) Optionally followed by ":" and X - adds message subject xref VARIABLES: XMFLAGS TYPE: Used VARIABLES DESCRIPTION: (optional) Flags control processing. May be any combination of the following: B - backwards order (default is traverse forward) U - Ignore the file screen on file 3.9 so that all messages can be examined. (valid only if XMK="!" and the user possesses the XM SUPER SEARCH key) If XMK="!", the following flags are ignored: C - use basket C-xref (default is message IEN) N - new messages only (C flag ignored) P - new priority messages only (C, N flags ignored) VARIABLES: XMAMT TYPE: Used VARIABLES DESCRIPTION: (optional) How many messages should be returned? Possible values: - this many * - all (default) VARIABLES: XMSTART TYPE: Both VARIABLES DESCRIPTION: (optional) This may be used to start the lister going. The lister will keep it updated from call to call. This variable is usually used when XMAMT is set to a number, and multiple calls to this API may be required. This variable ensures that each successive call resumes where the previous call left off. (If XMK="!", FileMan handles XMSTART, and you should look at FM documentation for an explanation. Messing with XMSTART is not advised if XMK="!", unless you are sure you know what you're doing.) The following variables may updated, depending on how the API is called: XMSTART("XMK") - Start with this basket IEN (valid only if XMK="*"). Continues from there, with each successive call, to the end. (Default is to start with basket .5, the WASTE basket.) XMSTART("XMZ") - Start AFTER this message IEN (valid only if XMFLAGS'["C"). Continues from there, with each successive call, to the end. (Default is to start at the beginning (or end) of the basket.) XMSTART("XMKZ") - Start AFTER this message C-xref (valid only if XMFLAGS["C"). Continues from there, with each successive call, to the end. (Default is to start at the beginning (or end) of the basket.) VARIABLES: XMCRIT TYPE: Used COMPONENT/ENTRY POINT: NAMEBSKT COMPONENT DESCRIPTION: Change the name of a basket. The IN and WASTE baskets may not be renamed. Only the user or a surrogate with 'write' privilege may use this API. If the user is SHARED,MAIL, then the surrogate must be a Postmaster surrogate or XMMGR key holder. Usage: D NAMEBSKT^XMXAPIB(XMDUZ,XMK,XMKN) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user whose basket is to be renamed. See General Description for more information. VARIABLES: XMK TYPE: Input VARIABLES DESCRIPTION: The basket to be renamed. See General Description for more information. VARIABLES: XMKN TYPE: Input VARIABLES DESCRIPTION: The new name of the basket. It is free text, from 2 to 30 characters. COMPONENT/ENTRY POINT: QBSKT COMPONENT DESCRIPTION: Get information about a basket. Only the user of a surrogate may use this API. Usage: D QBSKT^XMXAPIB(XMDUZ,XMK,.XMMSG) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user whose basket is to be queried. See General Description for more information. VARIABLES: XMK TYPE: Input VARIABLES DESCRIPTION: The basket to be queried. See General Description for more information. VARIABLES: XMMSG TYPE: Output VARIABLES DESCRIPTION: String containing the following up-arrow-delimited pieces of information: Piece 1: basket IEN Piece 2: basket name Piece 3: number of messages in the basket Piece 4: number of new messages in the basket COMPONENT/ENTRY POINT: RSEQBSKT COMPONENT DESCRIPTION: Resequence messages in a basket. Before any resequencing is done, a basket integrity check is performed, and any errors detected are corrected. Only the user or a surrogate may use this API. If the user is SHARED,MAIL, then the surrogate must be a Postmaster surrogate or XMMGR key holder. Usage: D RESEQBSKT^XMXAPIB(XMDUZ,XMK,.XMMSG) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user whose basket messages are to be resequenced. See General Description for more information. VARIABLES: XMK TYPE: Input VARIABLES DESCRIPTION: The basket to be resequenced. See General Description for more information. VARIABLES: XMMSG TYPE: Output VARIABLES DESCRIPTION: If resequencing is completed successfully, string contains the message: "Resequenced from 1 to ". NUMBER: 2724 IA #: 2724 DATE CREATED: JAN 26, 1999 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: OR*2.5*49 EXPORTS LAB PARAMETERS GENERAL DESCRIPTION: OR*2.5*49 sends out the following LR namespaced values for the PARAMETER DEFINITION file. These parameters were needed for part of the pre-CPRS setup activities. LR ASK URGENCY LR COLLECT FRIDAY LR COLLECT MONDAY LR COLLECT SATURDAY LR COLLECT SUNDAY LR COLLECT THURSDAY LR COLLECT TUESDAY LR COLLECT WEDNESDAY LR DEFAULT TYPE QUICK LR EXCEPTED LOCATIONS LR IGNORE HOLIDAYS LR MAX DAYS CONTINUOUS LR PHLEBOTOMY COLLECTION This is a one time request. STATUS: Active DURATION: Next Version MAIL MESSAGE: 26946458 GOOD ONLY FOR VERSION: OE/RR 2.5 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2726 IA #: 2726 DATE CREATED: JAN 26, 1999 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMPL1 NAME: OE/RR calls GMPL1 ID: GMPL1 GENERAL DESCRIPTION: This DBIA documents calls to routine GMPL1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28891053 COMPONENT/ENTRY POINT: VERIFY COMPONENT DESCRIPTION: VERIFY accepts a PROBLEM file (#9000011) IEN and records the user verifying the problem and the date/time of verification. Additionally, it maintains audit information and updates the DATE LAST MODIFIED field (#.03). VARIABLES: GMPIFN TYPE: Input VARIABLES DESCRIPTION: IEN of PROBLEM file. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2727 IA #: 2727 FILE NUMBER: 9000011 GLOBAL ROOT: AUPNPROB( DATE CREATED: JAN 26, 1999 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR REFERENCES TO AUPNPROB ID: AUPNPROB( GLOBAL REFERENCE: AUPNPROB(DA,0) FIELD NUMBER: .01 FIELD NAME: DIAGNOSIS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: DATE LAST MODIFIED LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .12 FIELD NAME: STATUS LOCATION: 0;12 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .13 FIELD NAME: DATE OF ONSET LOCATION: 0;13 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: AUPNPROB(DA,1) FIELD NUMBER: 1.01 FIELD NAME: PROBLEM LOCATION: 1;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.02 FIELD NAME: CONDITION LOCATION: 1;2 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 1.03 FIELD NAME: ENTERED BY LOCATION: 1;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.04 FIELD NAME: RECORDING PROVIDER LOCATION: 1;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.05 FIELD NAME: RESPONSIBLE PROVIDER LOCATION: 1;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.06 FIELD NAME: SERVICE LOCATION: 1;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.07 FIELD NAME: DATE RESOLVED LOCATION: 1;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.08 FIELD NAME: CLINIC LOCATION: 1;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.09 FIELD NAME: DATE RECORDED LOCATION: 1;9 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.1 FIELD NAME: SERVICE CONNECTED LOCATION: 1;10 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.11 FIELD NAME: AGENT ORANGE EXPOSURE LOCATION: 1;11 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.12 FIELD NAME: IONIZING RADIATION EXPOSURE LOCATION: 1;12 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.13 FIELD NAME: PERSIAN GULF EXPOSURE LOCATION: 1;13 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.14 FIELD NAME: PRIORITY LOCATION: 1;14 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.15 FIELD NAME: HEAD AND/OR NECK CANCER LOCATION: 1;15 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.16 FIELD NAME: MILITARY SEXUAL TRAUMA LOCATION: 1;16 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: AUPNPROB(DA(2),11,DA(1),11,DA,0) FIELD NUMBER: .04 FIELD NAME: STATUS LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: NOTE NARRATIVE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: AUPNPROB(DA(2),11,DA(1),11,'B' GLOBAL DESCRIPTION: Traverses through B index of NOTE multiple to get NOTE NARRATIVE GLOBAL REFERENCE: AUPNPROB('ACTIVE',DFN,STATUS GLOBAL DESCRIPTION: Traverses through ACTIVE x-ref for patient and status. GLOBAL REFERENCE: AUPNPROB(DA,10) FIELD NUMBER: 11 FIELD NAME: COMMENT LOCATION: 10;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 12 FIELD NAME: LAST EDITED LOCATION: 10;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 13 FIELD NAME: BY WHOM LOCATION: 10;3 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This DBIA documents OE/RR's use of the PROBLEM file (9000011). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34247707 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: OE/RR and, in particular GUI CPRS, need to manually reference the PROBLEM LIST. SUBSCRIBING PACKAGE: DENTAL NUMBER: 2728 IA #: 2728 DATE CREATED: JAN 27, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMVVITAE NAME: USER ENVIRONMENT API ID: XMVVITAE GENERAL DESCRIPTION: Create the MailMan environment in which the user will operate while in MailMan. Set up the user's XMV array, which contains vital user information, user preferences, and, if the user is a surrogate, the user's level of authorization. The information in this array is used throughout MailMan. If any errors occur, the following variables will be defined: XMERR - the number of errors ^TMP("XMERR",$J,,"TEXT",)= STATUS: Active MAIL MESSAGE: 29724674 COMPONENT/ENTRY POINT: INIT COMPONENT DESCRIPTION: Set up the user's MailMan environment in array XMV, which contains vital user information, user preferences, and, if the user is a surrogate, the user's level of authorization. This entry point is meant to be called once, upon entry into MailMan. It should not be used at any other time. Many of the MailMan APIs assume that the information provided by this routine exists. They may abort if it doesn't. Usage: D INIT^XMVVITAE VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: Set by KERNEL when the user logs in to the system, it is a unique user ID, and the IEN for the user in the NEW PERSON file. It is also the IEN for the user in the MAILBOX file. VARIABLES: XMDUZ TYPE: Both VARIABLES DESCRIPTION: (optional) If the user (as identified by DUZ) is acting as a surrogate for another user, XMDUZ should be set by the calling routine to the DUZ of the other user. If XMDUZ is not set by the calling routine, it is assumed that the user is acting for himself, and XMDUZ will be set to DUZ (default) by this routine. VARIABLES: XMDISPI TYPE: Output VARIABLES DESCRIPTION: String containing two up-arrow-delimited pieces of information: Piece 1: Any combination of the following: A - Ask basket, if user sends message to self I - Show institution T - Show title Piece 2: One of the following IN basket message action defaults: I - Ignore the message D - Delete the message NOTE: MailMan does not use this variable, as it duplicates information provided in XMV. VARIABLES: XMDUN TYPE: Output VARIABLES DESCRIPTION: Provides same information as XMV("NAME"). NOTE: MailMan does not use this variable, as it duplicates information provided in XMV. VARIABLES: XMNOSEND TYPE: Output VARIABLES DESCRIPTION: =1, if XMV("NOSEND")=1. Otherwise, not defined. NOTE: MailMan does not use this variable, as it duplicates information provided in XMV. VARIABLES: XMPRIV TYPE: Output VARIABLES DESCRIPTION: If the user is acting as a surrogate, then this string contains two pieces of up-arrow-delimited information, concerning the user's privileges: Piece 1: Does the user have read privilege? y - Yes n - No Piece 2: Does the user have send privilege? y - Yes n - No If the user is acting as a surrogate, then this variable is defined. Otherwise, it isn't. NOTE: MailMan does not use this variable, as it duplicates information provided in XMV. VARIABLES: XMV TYPE: Output VARIABLES DESCRIPTION: An array of values defining the user's MailMan environment, giving information about the user, the user's MailMan preferences, and, if the user's acting as a surrogate, what privileges the user has. The information in this array is used throughout MailMan. The following items will always be set: XMV("ASK BASKET") If user sends a message to himself, should MailMan ask, "which basket?" (0=yes; 1=no) XMV("DUZ NAME") The user's name. (DUZ) XMV("LAST USE") String, in external format, showing when was the last time the user entered MailMan, and if it was a surrogate, which one. If the user never entered MailMan, the string will be "Never". (XMDUZ) XMV("MSG DEF") The default action for a message in the IN basket (I=ignore; D=delete). (DUZ) XMV("NAME") The user's name. (XMDUZ) XMV("NETNAME") The user's network name. (XMDUZ) XMV("NEW MSGS") The number of new messages in the user's mailbox. (XMDUZ) XMV("NOSEND") May the user send messages in this session? (1=no; 0=yes) The user may not send messages in any but the first of multiple concurrent sessions. (XMDUZ) XMV("ORDER") Display the user's messages in which order? (-1=reverse; 1=forward) (DUZ) XMV("PREVU") In the Classic reader, should message previews be displayed? (0=no; 1=yes) (DUZ) XMV("RDR ASK") Ask the user which message reader to use? (N=no; Y=yes) (DUZ) XMV("RDR DEF") User's default message reader (C=classic; D=detailed full screen; S=summary full screen) (DUZ) XMV("SHOW DUZ") Show user's DUZ? (0=no; 1=yes) (site) XMV("SHOW INST") Show user's institution? (0=no; 1=yes) (site) XMV("SHOW TITL") Show user's title? (0=no; 1=yes) (DUZ) XMV("VERSION") What version of MailMan is at this site? "VA MailMan "_version # (site) The following items will be set only if conditions warrant: XMV("BANNER") The user's banner, if one exists; otherwise not defined. (XMDUZ) XMV("ERROR",1) "You do not have a DUZ" if '$D(DUZ). XMV("ERROR",2) "There is no person with DUZ "_XMDUZ_"." if bogus XMDUZ. XMV("ERROR",3) "There is no Access Code for DUZ "_XMDUZ_"." XMV("ERROR",4) "There is no Mailbox for DUZ "_XMDUZ_"." XMV("PRIV") If user is acting as a surrogate, contains the user's privilege(s). Any or all of the following: R - read W - write (send) XMV("SYSERR",i) If Domain incorrectly set up, contains text. (site) XMV("WARNING",1) "Priority Mail" if user has priority mail (XMDUZ) XMV("WARNING",2) "Message in Buffer" (XMDUZ) XMV("WARNING",3) "No Introduction" if user has no intro, but site requires one. (XMDUZ) XMV("WARNING",4) "Multiple Signon" if user is in MailMan in more than one session. (XMDUZ) XMV("WARNING",5) "POSTMASTER has "_I_" baskets." if more than 900 (Only if XMDUZ=.5) COMPONENT/ENTRY POINT: OTHER COMPONENT DESCRIPTION: Set up MailMan user environment when user becomes a surrogate. INIT^XMVVITAE should already have been called. If the XMV variable does not exist, control will be passed to INIT^XMVVITAE, instead. Usage: D OTHER^XMVVITAE VARIABLES: XMV TYPE: Output VARIABLES DESCRIPTION: An array of values giving information about the user for whom the user is acting as a surrogate. Also specifies what surrogate privileges the user has. The information in this array is used throughout MailMan. The following items will always be set, as they pertain to the user for whom the user is acting as a surrogate. Please see entry INIT for a description of the variables. XMV("LAST USE") XMV("NAME") XMV("NETNAME") XMV("NEW MSGS") XMV("NOSEND") XMV("PRIV") The following items will be set only if conditions warrant: XMV("BANNER") XMV("ERROR",1) XMV("ERROR",2) XMV("ERROR",3) XMV("ERROR",4) XMV("WARNING",1) XMV("WARNING",2) XMV("WARNING",3) XMV("WARNING",4) XMV("WARNING",5) VARIABLES: XMDUZ TYPE: Both VARIABLES DESCRIPTION: OTHER^XMVVITAE is specifically designed for becoming a surrogate. Therefore, XMDUZ must be the DUZ of the user to become. It follows that XMDUZ should not equal DUZ. See the variable description for entry INIT for further information. VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: See the variable description for entry INIT. VARIABLES: XMDUN TYPE: Output VARIABLES DESCRIPTION: See the variable description for entry INIT. VARIABLES: XMNOSEND TYPE: Output VARIABLES DESCRIPTION: See the variable description for entry INIT. VARIABLES: XMPRIV TYPE: Output VARIABLES DESCRIPTION: See the variable description for entry INIT. COMPONENT/ENTRY POINT: SELF COMPONENT DESCRIPTION: Return to the user's own MailMan user environment after having finished acting as a surrogate. Usage: D SELF^XMVVITAE VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: See the variable description for entry INIT. VARIABLES: XMDUZ TYPE: Output VARIABLES DESCRIPTION: XMDUZ will be set equal to DUZ, as the first step in returning the user to his own identity. VARIABLES: XMDUN TYPE: Output VARIABLES DESCRIPTION: See the variable description for entry INIT. VARIABLES: XMNOSEND TYPE: Output VARIABLES DESCRIPTION: See the variable description for entry INIT. VARIABLES: XMV TYPE: Output VARIABLES DESCRIPTION: An array of values defining the user and the user's MailMan environment. The information in this array is used throughout MailMan. The following items will always be set. Please see entry INIT for a description of the variables. XMV("NAME") XMV("NETNAME") XMV("NEW MSGS") XMV("NOSEND") The following items will be set only if conditions warrant: XMV("BANNER") XMV("ERROR",1) XMV("ERROR",2) XMV("ERROR",3) XMV("ERROR",4) XMV("WARNING",1) XMV("WARNING",2) XMV("WARNING",3) XMV("WARNING",4) XMV("WARNING",5) NUMBER: 2729 IA #: 2729 DATE CREATED: JAN 27, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMXAPI NAME: MESSAGE ACTION API ID: XMXAPI GENERAL DESCRIPTION: The APIs in this DBIA perform message actions. They are designed to be used individually or incorporated into a MailMan front end. For usage instructions, please refer to the Programmer Manual, available at the Infrastructure web site. When used as part of a MailMan front end, INIT^XMVVITAE should be called to create the MailMan environment in which the user will operate. Please see DBIA 2728 for information on the XMVVITAE APIs. When used individually, from a routine, the XMVVITAE APIs should not be called. After every API call, the calling routine should check for the existence of XMERR. If any errors occur, the following variables will be defined: XMERR - the number of errors ^TMP("XMERR",$J,,"TEXT",)= Parameter definitions: XMDUZ User's DUZ or enough of the name for a positive ID. XMINSTR (optional) Array of special instructions ("ADDR FLAGS") Special addressing instructions, any or all of the following: I Do not Initialize (kill) the ^TMP addressee global, because it already contains addressees for this message, as a result of a previous call to an API. R Do not Restrict message addressing: - Ignore 'domain closed' - Ignore 'keys required for domain' - Ignore 'may not forward to domain' - Ignore 'may not forward priority mail to groups' - Ignore 'message length restrictions to remote addressees' X Do not create the ^TMP addressee global, because addressees are only being checked for validity. ("FLAGS") Message is any or all of the following: P Priority I Information only (may not be replied to) X Closed message (may not be forwarded) C Confidential message (surrogate may not read) S Send to sender (make sender a recipient) R Confirm receipt (return receipt requested) ("FROM") String saying who the message is from (default is user, as identified by XMDUZ parameter). This string is placed in field 1 'from' in the message file. Must not be any real person, except for Postmaster. DUZ is not captured in field 1.1 'sender' of message file, thus making this option well-suited for messages from VISTA packages. ("FWD BY") String saying who forwarded the message (default is user, as identified by XMDUZ parameter). This string is placed in field 8 'forwarded by' in the recipient multiple of the message file. Must not be any real person, except for Postmaster. DUZ is not captured in field 8.01 'forwarded by (xmduz)' in the recipient multiple of message file, thus making this option well-suited for messages forwarded by VISTA packages. ("HDR") Print the messages with a header? (0=no; 1=yes) Default is yes. ("LATER") Date/time (any format understood by FM) on which to send this message. Default is now. ("NET REPLY") Should reply be sent over the network? (0=no; 1=yes) Default is no. Currently valid only if sender of original message is remote. ("NET SUBJ") Subject of reply to be sent over the network. Default is "Re: ". Ignored unless XMINSTR("NET REPLY")=1. ("RCPT BSKT") Basket to deliver to for all recipients. Default is IN basket. Recipients must have specified in their personal preferences that such targeted basket delivery is allowed. Otherwise, this option is ignored. ("RECIPS") Print recipients along with the message? 0 No (default) 1 Print summary recipients 2 Print detailed recipients ("RESPS") Print which responses? * Original message and all responses (default) 0 Original message only range list (e.g. 0-3,5,7-99) - Print this range of responses. Ignored if more than one message is printed. This parameter is not checked. It must be correct. Range list may also be open-ended (e.g. 1,2,5- means print responses 1 and 2 and responses 5 to the end). ("SCR KEY") Scramble key (implies that message should be scrambled). Must be 3-20 characters long. ("SCR HINT") Hint for scramble key (mandatory if message is to be scrambled). Must be 1-40 characters long. ("SELF BSKT") Basket to deliver to if sender is recipient. Default is IN basket. ("SHARE BSKT") Basket to deliver to if SHARED,MAIL is recipient. Default is IN basket. ("SHARE DATE") Date/time (any format understood by FM) to delete this message from SHARED,MAIL if SHARED,MAIL is recipient. ("STRIP") String containing characters to strip from the message text (XMBODY). Must be 1-20 characters long. ("TO PROMPT") During interactive message addressing, contains the suggested initial addressee. Default is the user identified by XMDUZ. ("TYPE") Message type is one of the following special types: D Document S Spooled Document X DIFROM O ODIF B BLOB (reserved for future use) K KIDS ("VAPOR") Date/time (any format understood by FM) on which to delete (vaporize) this message from recipient baskets. Recipients may override this date. Also used to set vaporize date/time for messages already in one's own baskets. ("WHEN") Date/time (any format understood by FM) on which to print messages. Default is now. [.]XMTO Addressee or addressee array (if array, must be passed by reference). May be or contain any of the following: User's DUZ, or enough of user's name for a positive ID eg: 1301 or "lastname,firs" or ARRAY(1301)="" ARRAY("lastname,firs")="" G.group name (enough for positive ID) S.server name (enough for positive ID) D.device name (enough for positive ID) You may prefix each addressee (except devices and servers) by: I: for 'information only' recipient (may not reply) eg: "I:1301" or "I:lastname,firs" C: for 'copy' recipient (not expected to reply) eg: "C:1301" or "C:lastname,firs" L@datetime: for when (in future) to send to this recipient (datetime may be anything accepted by FM) eg: "L@25 DEC@0500:1301" or "L@1 JAN:lastname,firs" or "L@2981225.05:1301" (may combine IL@datetime: or CL@datetime:) To delete recipient, prefix with - eg: -1301 or "-lastname,firs" Append "@" for any addressees at another site: eg: "I:G.group@site.med.va.gov" or "JOE,USER@site.med.va.gov" XMK and XMKZ for APIs which act on one message: XMK (optional, depending on XMKZ) Basket (IEN or name) containing the message. XMKZ Identifies the message. Must be one of the following: Message number (XMZ) in Message global (XMK must not be specified) Message number in the basket (XMK must be specified) XMK and XMKZA for APIs which act on groups of messages: XMK (optional, depending on XMKZA) Basket (IEN or name) containing the messages. XMKZA Identifies messages, using a list or list array, which may end in a comma. Must be one of the following: Message numbers (XMZ) in Message global (XMK must not be specified, AND ranges are not allowed): - List: "1234567" or "1234567,9763213" - List array: ARRAY(1234567)="" ARRAY(9763213)="" Message numbers in the basket (XMK must be specified, ranges are OK): - List: "1" or "1,3,5-7" - List array: ARRAY("1,3")="" ARRAY("5-7")="" STATUS: Active MAIL MESSAGE: 29724674 COMPONENT/ENTRY POINT: ADDRNSND COMPONENT DESCRIPTION: Address a message, add the sender and any special instructions, and send it. The message stub must have already been created, using, for instance, CRE8XMZ^XMXAPI (see elsewhere in this DBIA), and the text must already have been added to the message, using, for instance, TEXT^XMXEDIT (DBIA 2730). Usage: D ADDRNSND^XMXAPI(XMDUZ,XMZ,.XMTO,.XMINSTR) or D ADDRNSND^XMXAPI(XMDUZ,XMZ,XMTO,.XMINSTR) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user who is sending the message. See the General Description for more information. VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the message file. VARIABLES: XMTO TYPE: Input VARIABLES DESCRIPTION: Addressee or array of addressees to whom to send the message. See the General Description for more information. VARIABLES: XMINSTR TYPE: Used VARIABLES DESCRIPTION: (optional) Array of special instructions for the message. Any or all of the following array items may be defined. See the General Description for more information on them. XMINSTR("ADDR FLAGS") Addressing instructions (I and/or R are appropriate, but X is not) XMINSTR("FLAGS") Special handling instructions XMINSTR("FROM") Make this the sender, instead of XMDUZ XMINSTR("LATER") Send later XMINSTR("RCPT BSKT") Delivery basket XMINSTR("SCR HINT") Scramble hint XMINSTR("SCR KEY") Scramble key XMINSTR("SELF BSKT") Sender delivery basket XMINSTR("SHARE BSKT") SHARED,MAIL delivery basket XMINSTR("SHARE DATE") SHARED,MAIL delete date XMINSTR("TYPE") Message type XMINSTR("VAPOR") Message delete date COMPONENT/ENTRY POINT: ANSRMSG COMPONENT DESCRIPTION: Answer a message. VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user who is answering the message. See the General Description for more information. COMPONENT/ENTRY POINT: CRE8XMZ COMPONENT DESCRIPTION: Create a message stub. COMPONENT/ENTRY POINT: DELMSG COMPONENT DESCRIPTION: Delete one or more messages from a user's mailbox. VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user whose messages are to be deleted. See the General Description for more information. COMPONENT/ENTRY POINT: FLTRMSG COMPONENT DESCRIPTION: Filter one or more messages to a user's mailbox. VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user whose messages are to be filtered. See the General Description for more information. COMPONENT/ENTRY POINT: FWDMSG COMPONENT DESCRIPTION: Forward message(s). VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user whose messages are to be forwarded. See the General Description for more information. COMPONENT/ENTRY POINT: LATERMSG COMPONENT DESCRIPTION: Later message(s). VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user whose messages are to be latered. See the General Description for more information. COMPONENT/ENTRY POINT: MOVEMSG COMPONENT DESCRIPTION: Move (save) message(s) to a basket. VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user whose messages are to be moved (saved). COMPONENT/ENTRY POINT: PRTMSG COMPONENT DESCRIPTION: Print message(s). VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user whose messages are to be printed. See the General Description for more information. COMPONENT/ENTRY POINT: PUTSERV COMPONENT DESCRIPTION: Put one message into a server basket. COMPONENT/ENTRY POINT: REPLYMSG COMPONENT DESCRIPTION: Reply to a message. VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user who is replying to a message. See the General Description for more information. COMPONENT/ENTRY POINT: SENDBULL COMPONENT DESCRIPTION: Send a bulletin message. VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user who is sending the bulletin. See the General Description for more information. COMPONENT/ENTRY POINT: SENDMSG COMPONENT DESCRIPTION: Send a message. VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user who is sending the message. See the General Description for more information. COMPONENT/ENTRY POINT: TASKBULL COMPONENT DESCRIPTION: Task the sending of a bulletin for later. VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user who is tasking the bulletin. See the General Description for more information. COMPONENT/ENTRY POINT: TERMMSG COMPONENT DESCRIPTION: Terminate message(s). VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user whose messages are being terminated. See the General Description for more information. COMPONENT/ENTRY POINT: TOWHOM COMPONENT DESCRIPTION: Check one addressee while addressing a message. COMPONENT/ENTRY POINT: VSUBJ COMPONENT DESCRIPTION: Check a subject to make sure it's valid. COMPONENT/ENTRY POINT: ZAPSERV COMPONENT DESCRIPTION: Delete one message from a server basket. COMPONENT/ENTRY POINT: NTOGLMSG COMPONENT DESCRIPTION: Toggle message(s) new or not new. COMPONENT/ENTRY POINT: VAPORMSG COMPONENT DESCRIPTION: Set (schedule) Vaporize date/time for message(s) in one's basket(s) to be automatically deleted. NUMBER: 2730 IA #: 2730 DATE CREATED: JAN 27, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMXEDIT NAME: MESSAGE EDIT API ID: XMXEDIT GENERAL DESCRIPTION: These APIs are intended for use by MailMan front ends. They edit different parts of a message. They may only be used by the message sender, and, with the exception of INFO^XMXEDIT, may only be used before the message has been sent to anyone besides the sender. The APIs do not contain any checks to ensure that it was appropriate to call them. That is the responsibility of the calling routine. For these APIs, it is expected that: INIT^XMVVITAE has been called to set up the user's XMV array, with vital user information, user preferences, and, if the user is a surrogate, determine level of authorization. See DBIA 2728 for information on INIT^XMVVITAE. The calling routine has determined that the user is authorized to see the message. If the message is in the user's mailbox, then that's enough. Otherwise, $$ACCESS^XMXSEC should be used to determine authorization. See DBIA 2731 for information on $$ACCESS^XMXSEC. OPTMSG^XMXSEC2 has been called and has given its permission to edit the message or to toggle information only. (Note: $$EDIT^XMXSEC2 will also let you know whether the user may edit the message.) See DBIA 2733 for information on OPTMSG^XMXSEC2A and $$EDIT^XMXSEC2. OPTEDIT^XMXSEC2 has been called and has given its permission to edit the particular thing we are editing here. See DBIA 2733 for information on OPTEDIT^XMXSEC2. INMSG2^XMXUTIL2 has been called to set XMINSTR. These routines expect that XMINSTR has been correctly set. They will change XMINSTR according to the item being edited. See DBIA 2736 for information on INMSG2^XMXUTIL2. STATUS: Active MAIL MESSAGE: 29724674 COMPONENT/ENTRY POINT: CLOSED COMPONENT DESCRIPTION: Toggle a message's 'closed' flag. The flag is toggled in field 1.95 of the message in the Message file, as well as in the parameter XMINSTR("FLAGS"). See the general description for important information. When a message is closed, it may not be forwarded by anyone, except the person who sent it. Note that messages addressed to SHARED,MAIL may not be closed. If a message is in the process of being addressed to SHARED, MAIL, and this API is called, XMERR and ^TMP("XMERR",$J) will be set. The calling routine should always check for $D(XMERR) after calling this API. Usage: D CLOSED^XMXEDIT(XMZ,.XMINSTR,.XMMSG) VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the MESSAGE file. VARIABLES: XMINSTR TYPE: Both VARIABLES DESCRIPTION: If the message is closed (XMINSTR("FLAGS")["X"), then make the message not closed: - Delete field 1.95 of the message in the Message file. - Remove the "X" from XMINSTR("FLAGS"). If the message is not closed (XMINSTR("FLAGS")'["X"), then make the message closed: - Set field 1.95 of the message in the Message file. - Append an "X" to XMINSTR("FLAGS"). VARIABLES: XMMSG TYPE: Output VARIABLES DESCRIPTION: An appropriate message, suitable for display to the user. Either "'Closed' flag removed" or "Message flagged 'Closed'". COMPONENT/ENTRY POINT: CONFID COMPONENT DESCRIPTION: Toggle a message's 'confidential' flag. The flag is toggled in field 1.96 in the Message file, as well as in the parameter XMINSTR("FLAGS"). See the general description for important information. When a message is confidential, it may not be read by a surrogate. Note that messages addressed to SHARED,MAIL may not be confidential. If a message is in the process of being addressed to SHARED, MAIL, and this API is called, XMERR and ^TMP("XMERR",$J) will be set. The calling routine should always check for $D(XMERR) after calling this API. Usage: D CONFID^XMXEDIT(XMZ,.XMINSTR,.XMMSG) VARIABLES: XMMSG TYPE: Output VARIABLES DESCRIPTION: An appropriate message, suitable for display to the user. Either "'Confidential' flag removed" or "Message flagged 'Confidential'". VARIABLES: XMINSTR TYPE: Both VARIABLES DESCRIPTION: If the message is confidential (XMINSTR("FLAGS")["C"), then make the message not confidential: - Delete field 1.96 of the message in the Message file. - Remove the "C" from XMINSTR("FLAGS"). If the message is not confidential (XMINSTR("FLAGS")'["C"), then make the message confidential: - Set field 1.96 of the message in the Message file. - Append a "C" to XMINSTR("FLAGS"). VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the MESSAGE file. COMPONENT/ENTRY POINT: CONFIRM COMPONENT DESCRIPTION: Toggle a message's 'confirm receipt requested' flag. The flag is toggled in field 1.3 of the message in the Message file, as well as in the parameter XMINSTR("FLAGS"). See the general description for important information. When a message is flagged 'confirm receipt requested', the first time each recipient reads the message, a message will be sent to the sender of the message informing the sender that the recipient has seen the message. Usage: D CONFIRM^XMXEDIT(XMZ,.XMINSTR,.XMMSG) VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the MESSAGE file. VARIABLES: XMINSTR TYPE: Both VARIABLES DESCRIPTION: If the message is 'confirm receipt requested' (XMINSTR("FLAGS")["R"), then make the message not 'confirm receipt requested': - Delete field 1.3 of the message in the Message file. - Remove the "R" from XMINSTR("FLAGS"). If the message is not 'confirm receipt requested' (XMINSTR("FLAGS")'["R"), then make the message 'confirm receipt requested': - Set field 1.3 of the message in the Message file. - Append an "R" to XMINSTR("FLAGS"). VARIABLES: XMMSG TYPE: Output VARIABLES DESCRIPTION: An appropriate message, suitable for display to the user. Either "'Confirm Receipt Requested' flag removed" or "Message flagged 'Confirm Receipt Requested'". COMPONENT/ENTRY POINT: DELIVER COMPONENT DESCRIPTION: Set or delete a message's 'delivery basket' in field 21 of the message in the Message file, as well as in the parameter XMINSTR("RCPT BSKT"). See the general description for important information. When a message specifies a delivery basket, it will be delivered to that basket for each recipient, as long as the recipient has allowed such targeted delivery (by so indicating under User Preferences). If the recipient does not allow such targeted delivery, then the message is delivered as usual. Usage: D DELIVER^XMXEDIT(XMZ,BASKET,.XMINSTR,.XMMSG) VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the MESSAGE file. VARIABLES: BASKET TYPE: Input VARIABLES DESCRIPTION: Full name of the basket to which the message should be delivered. It must be a valid basket name. (Free text, 2-30 characters.) This API does not check to ensure that the basket name is valid. That is the responsibility of the calling routine. If BASKET="@", field 21 of the message in the Message file is deleted, and XMINSTR("RCPT BSKT") is killed. Otherwise, field 21 of the message in the Message file and XMINSTR("RCPT BSKT") are set to BASKET. VARIABLES: XMINSTR TYPE: Output VARIABLES DESCRIPTION: If BASKET="@", field 21 of the message in the Message file is deleted, and XMINSTR("RCPT BSKT") is killed. Otherwise, field 21 of the message in the Message file and XMINSTR("RCPT BSKT") are set to BASKET. VARIABLES: XMMSG TYPE: Output VARIABLES DESCRIPTION: An appropriate message, suitable for display to the user. Either "Delivery basket set" or "Delivery basket removed". COMPONENT/ENTRY POINT: INFO COMPONENT DESCRIPTION: Toggle a message's 'Information only' flag. The flag is toggled in field 1.97 of the message in the Message file, as well as in the parameter XMINSTR("FLAGS"). See the general description for important information. When a message is flagged 'Information only', no one may reply to the message, except for the sender. Note that unlike the other APIs in this DBIA, this API may be used by the sender at any time to toggle the 'Information only' flag, even after the message has been sent to other users. Usage: D INFO^XMXEDIT(XMZ,.XMINSTR,.XMMSG) VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the MESSAGE file. VARIABLES: XMINSTR TYPE: Both VARIABLES DESCRIPTION: If the message is 'information only' (XMINSTR("FLAGS")["I"), then make the message not 'information only': - Delete field 1.97 of the message in the Message file. - Remove the "I" from XMINSTR("FLAGS"). If the message is not 'information only' (XMINSTR("FLAGS")'["I"), then make the message 'information only': - Set field 1.97 of the message in the Message file. - Append an "I" to XMINSTR("FLAGS"). VARIABLES: XMMSG TYPE: Output VARIABLES DESCRIPTION: An appropriate message, suitable for display to the user. Either "'Information only' flag removed" or "Message flagged 'Information only'". COMPONENT/ENTRY POINT: PRIORITY COMPONENT DESCRIPTION: Toggle a message's 'priority' flag. The flag is toggled in field 1.7 of the message in the Message file, as well as in the parameter XMINSTR("FLAGS"). See the general description for important information. When a message is priority, it is delivered normally, but each recipient is alerted to it at logon or when it is delivered, and, when reading new messages, priority messages are displayed first. In a message list, priority messages are marked by an "!". Usage: D PRIORITY^XMXEDIT(XMZ,.XMINSTR,.XMMSG) VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the MESSAGE file. VARIABLES: XMINSTR TYPE: Both VARIABLES DESCRIPTION: If the message is priority (XMINSTR("FLAGS")["P"), then make the message not priority: - Remove the priority indicator from field 1.7 of the message in the Message file. (The parameter XMINSTR("TYPE") is used here.) - Remove the "P" from XMINSTR("FLAGS"). If the message is not priority (XMINSTR("FLAGS")'["P"), then make the message priority: - Add the priority indicator to field 1.7 of the message in the Message file. (The parameter XMINSTR("TYPE") is used here.) - Append a "P" to XMINSTR("FLAGS"). VARIABLES: XMMSG TYPE: Output VARIABLES DESCRIPTION: An appropriate message, suitable for display to the user. Either "'Priority' flag removed" or "Message flagged 'Priority'". COMPONENT/ENTRY POINT: SUBJ COMPONENT DESCRIPTION: Change the message subject. If the subject is null, the subject is set to "* No Subject *". If the subject is "* No Subject *", and the message is sent to a remote site, the subject in the "SUBJECT:" header record will be null. The subject is set in field .01 of the message in the Message file, as well as in the parameter XMIM("SUBJ"). See the general description for important information. Usage: D SUBJ^XMXEDIT(XMZ,XMSUBJ,.XMIM) VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the MESSAGE file. VARIABLES: XMSUBJ TYPE: Input VARIABLES DESCRIPTION: New subject of the message. The subject must be valid. It must be 3-65 characters. It may also be null. It is the responsibility of the calling routine to ensure that the subject is valid. You may use the API VSUBJ^XMXAPI (DBIA 2729) to validate a subject. VARIABLES: XMIM TYPE: Output VARIABLES DESCRIPTION: XMIM("SUBJ") is set to the new message subject. COMPONENT/ENTRY POINT: TEXT COMPONENT DESCRIPTION: Replace the text in field 3 of the message in the Message file. Usage: D TEXT^XMXEDIT(XMZ,XMBODY) VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the MESSAGE file. VARIABLES: XMBODY TYPE: Input VARIABLES DESCRIPTION: The closed root of the array that contains the word processing data to be filed. The array itself must be in a format acceptable to FileMan's WP^DIE API. It is the responsibility of the calling routine to ensure that the root is correctly passed in and that the array itself is correctly formatted. This API does not check it. COMPONENT/ENTRY POINT: VAPOR COMPONENT DESCRIPTION: Set or delete a message's 'vaporize date' in field 1.6 of the message in the Message file, as well as in the parameter XMINSTR("VAPOR"). See the general description for important information. When a message specifies a vaporize date, that date will be set in the Mailbox file for each recipient in field 5 of the message record in the message multiple of the basket to which the message is delivered as the message is delivered to each recipient. This holds true even when the message is forwarded. The vaporize date (from field 5 of the basket message multiple in the Mailbox file) is displayed to the recipient every time the recipient reads the message. Each recipient is free to delete or change the vaporize date (field 5...) of the message in his or her mailbox. Messages with vaporize dates in the user's mailbox are deleted from the user's mailbox when the vaporize date arrives. Usage: D VAPOR^XMXEDIT(XMZ,XMVAPOR,.XMINSTR,.XMMSG) Note that this API does not edit the message vaporize date in a user's basket. Use KVAPOR^XMXUTIL (DBIA 2734) to do that. VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the MESSAGE file. VARIABLES: XMVAPOR TYPE: Input VARIABLES DESCRIPTION: Vaporize date/time. Must be in internal FileMan format. This API does not check to ensure that the date/time is valid. That is the responsibility of the calling routine. If XMVAPOR="@", field 1.6 of the message in the Message file is deleted, and XMINSTR("VAPOR") is killed. Otherwise, field 1.6 of the message in the Message file and XMINSTR("VAPOR") are set to XMVAPOR. VARIABLES: XMINSTR TYPE: Output VARIABLES DESCRIPTION: If XMVAPOR="@", field 1.6 of the message in the Message file is deleted, and XMINSTR("VAPOR") is killed. Otherwise, field 1.6 of the message in the Message file and XMINSTR("VAPOR") are set to XMVAPOR. VARIABLES: XMMSG TYPE: Output VARIABLES DESCRIPTION: An appropriate message, suitable for display to the user. Either "Vaporize Date set" or "Vaporize Date removed". COMPONENT/ENTRY POINT: NETSIG COMPONENT DESCRIPTION: Add the user's network signature to a message. See the general description for important information. This is not a toggle. MailMan has no way of checking to see if the user's network signature has already been added. Everytime this API is called, the network signature is added to the message, so if this API is called 3 times on the same message, the network signature will be added 3 times. Usage: D NETSIG^XMXEDIT(XMDUZ,XMZ,.XMINSTR,.XMMSG) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user whose network signature is to be added to the message. This is, of course, the user who created the message. The DUZ suffices, or enough of the name for a positive ID. VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the MESSAGE file. VARIABLES: XMINSTR TYPE: Used VARIABLES DESCRIPTION: If the message is not scrambled, then this variable is ignored. If the message is scrambled (locked with a key), then XMINSTR("SCR KEY") must contain the scramble key. If the key is not correct or is not supplied, then XMERR AND ^TMP("XMERR",$J) will be set. The calling routine should always check for $D(XMERR) after calling this API. VARIABLES: XMMSG TYPE: Output VARIABLES DESCRIPTION: Upon successful completion of this API, this variable contains an appropriate message, suitable for display to the user. "Network Signature added." COMPONENT/ENTRY POINT: SCRAMBLE COMPONENT DESCRIPTION: Scramble or unscramble a message's text. This API works as a toggle. If the text is scrambled, it will unscramble it. If it's not scrambled, it will scramble it. See the general description for important information. Usage: D SCRAMBLE^XMXEDIT(XMZ,.XMINSTR,.XMMSG) VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Message IEN in the MESSAGE file. VARIABLES: XMINSTR TYPE: Both VARIABLES DESCRIPTION: If the message is scrambled, the XMINSTR("SCR KEY") must contain the correct scramble key, otherwise XMERR and ^TMP("XMERR",$J) will be set. The calling routine should always check for $D(XMERR) after calling this API. XMINSTR("SCR HINT") is ignored as input. XMINSTR("SCR KEY") and XMINSTR("SCR HINT") are both killed upon successful completion of this API, and fields 1.8 and 1.85 of the message are deleted. If the message is not scrambled, XMINSTR("SCR KEY") must contain the key with which the message should be scrambled. It must be 3-20 characters, and case is ignored. XMINSTR("SCR HINT") is shown to the user when s/he receives the message, and is intended to be a hint to the user as to what the key might be. If supplied, it may be no more than 40 characters. The hint is optional. Field 1.8 of the message is set with the hint, and field 1.85 is set with the key. VARIABLES: XMMSG TYPE: Output VARIABLES DESCRIPTION: An appropriate message, suitable for display to the user. Either "Message text Scrambled" or "Message text UnScrambled". NUMBER: 2731 IA #: 2731 DATE CREATED: JAN 27, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMXSEC NAME: SECURITY, PERMISSIONS, & RESTRICTIONS API ID: XMXSEC GENERAL DESCRIPTION: These APIs perform security and permission functions. Please see the Programmer Manual on the Infrastructure web site for further information about the APIs and how to use them. STATUS: Active MAIL MESSAGE: 29724674 COMPONENT/ENTRY POINT: $$ACCESS COMPONENT DESCRIPTION: Returns a value indicating whether the user may access a message or not. COMPONENT/ENTRY POINT: $$ANSWER COMPONENT DESCRIPTION: Returns a value indicating whether the user may answer a message or not. COMPONENT/ENTRY POINT: $$BCAST COMPONENT DESCRIPTION: Returns a value indicating whether a message was broadcast or not. COMPONENT/ENTRY POINT: $$CLOSED COMPONENT DESCRIPTION: Returns a value indicating whether a message is "closed" or not. COMPONENT/ENTRY POINT: $$CONFID COMPONENT DESCRIPTION: Returns a value indicating whether a message is "confidential" or not. COMPONENT/ENTRY POINT: $$CONFIRM COMPONENT DESCRIPTION: Returns a value indicating whether a message is "confirm receipt requested" or not. COMPONENT/ENTRY POINT: $$COPY COMPONENT DESCRIPTION: Returns a value indicating whether the user may copy a message or not. COMPONENT/ENTRY POINT: $$DELETE COMPONENT DESCRIPTION: Returns a value indicating whether the user may delete (or terminate) a message or not. COMPONENT/ENTRY POINT: $$FORWARD COMPONENT DESCRIPTION: Returns a value indicating whether the user may forward a message or not. COMPONENT/ENTRY POINT: $$INFO COMPONENT DESCRIPTION: Returns a value indicating whether a message is "information only" or not. COMPONENT/ENTRY POINT: $$LATER COMPONENT DESCRIPTION: Returns a value indicating whether the user may "later" a message or not. COMPONENT/ENTRY POINT: $$MOVE COMPONENT DESCRIPTION: Returns a value indicating whether the user may save or filter a message or not. COMPONENT/ENTRY POINT: $$ORIGIN8R COMPONENT DESCRIPTION: Returns a value indicating whether the user sent the message or not. COMPONENT/ENTRY POINT: $$POSTPRIV COMPONENT DESCRIPTION: Returns a value indicating whether the user has Postmaster privileges or not, including whether or not the user may perform group message actions in SHARED,MAIL. COMPONENT/ENTRY POINT: $$PRIORITY COMPONENT DESCRIPTION: Returns a value indicating whether a message is "priority" or not. COMPONENT/ENTRY POINT: $$READ COMPONENT DESCRIPTION: Returns a value indicating whether the user may read a message or not. COMPONENT/ENTRY POINT: $$REPLY COMPONENT DESCRIPTION: Returns a value indicating whether the user may reply to a message or not. COMPONENT/ENTRY POINT: $$RPRIV COMPONENT DESCRIPTION: Returns a value indicating whether the surrogate has READ privileges or not. COMPONENT/ENTRY POINT: $$RWPRIV COMPONENT DESCRIPTION: Returns a value indicating whether the surrogate has READ or SEND privileges or not. COMPONENT/ENTRY POINT: $$SEND COMPONENT DESCRIPTION: Returns a value indicating whether the user may send a message or not. COMPONENT/ENTRY POINT: $$SURRACC COMPONENT DESCRIPTION: Returns a value indicating whether the surrogate may access a message or not. COMPONENT/ENTRY POINT: $$SURRCONF COMPONENT DESCRIPTION: Returns a value indicating whether a message is "confidential" or not, and if it is, whether the surrogate may access it. COMPONENT/ENTRY POINT: $$WPRIV COMPONENT DESCRIPTION: Returns a value indicating whether the surrogate has SEND privileges or not. COMPONENT/ENTRY POINT: $$ZCLOSED COMPONENT DESCRIPTION: Returns a value indicating whether a message is "closed" or not. COMPONENT/ENTRY POINT: $$ZCONFID COMPONENT DESCRIPTION: Returns a value indicating whether a message is "confidential" or not. COMPONENT/ENTRY POINT: $$ZCONFIRM COMPONENT DESCRIPTION: Returns a value indicating whether a message is "confirm receipt requested" or not. COMPONENT/ENTRY POINT: $$ZINFO COMPONENT DESCRIPTION: Returns a value indicating whether a message is "information only" or not. COMPONENT/ENTRY POINT: $$ZORIGIN8 COMPONENT DESCRIPTION: Returns a value indicating whether the user sent the message or not. COMPONENT/ENTRY POINT: $$ZPOSTPRV COMPONENT DESCRIPTION: Returns a value indicating whether the user has Postmaster privileges or not, including whether or not the user may perform group message actions in SHARED,MAIL. COMPONENT/ENTRY POINT: $$ZPRI COMPONENT DESCRIPTION: Returns a value indicating whether a message is "priority" or not. NUMBER: 2732 IA #: 2732 DATE CREATED: JAN 27, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMXSEC1 NAME: SECURITY, PERMISSIONS, & RESTRICTIONS API ID: XMXSEC1 GENERAL DESCRIPTION: These APIs perform security and permission functions. Please see the Programmer Manual on the Infrastructure web site for further information about the APIs and how to use them. STATUS: Active MAIL MESSAGE: 29724674 COMPONENT/ENTRY POINT: $$COPYAMT COMPONENT DESCRIPTION: This function may be used when copying a message. It checks the total number of lines and responses to be copied. Returns a value indicating whether or not the amount is within site limitations. COMPONENT/ENTRY POINT: $$COPYLIMS COMPONENT DESCRIPTION: This function may be used when copying a message. Returns the site's copy limits. COMPONENT/ENTRY POINT: $$COPYRECP COMPONENT DESCRIPTION: This function may be used when copying a message. It returns a value indicating whether or not the copy may be sent to all the recipients of the original message. COMPONENT/ENTRY POINT: $$PAKMAN COMPONENT DESCRIPTION: Returns a value indicating whether a message is a PackMan message or not. COMPONENT/ENTRY POINT: CHKLINES COMPONENT DESCRIPTION: Checks whether a message is too long to be sent to a remote site. COMPONENT/ENTRY POINT: CHKMSG COMPONENT DESCRIPTION: Checks whether or not the message is located where the calling routine says it is, and whether or not the user may access it. COMPONENT/ENTRY POINT: GETRESTR COMPONENT DESCRIPTION: Returns assorted restrictions, if any, on sending or forwarding the message. COMPONENT/ENTRY POINT: OPTGRP COMPONENT DESCRIPTION: Determines what the user may do at the basket or message group level. COMPONENT/ENTRY POINT: $$SSPRIV COMPONENT DESCRIPTION: Returns a value (1 or 0) indicating whether the user is authorized to conduct a Super Search or not. If not, also sets XMERR and ^TMP("XMERR",$J). COMPONENT/ENTRY POINT: $$ZSSPRIV COMPONENT DESCRIPTION: Returns a value (1 or 0) indicating whether the user is authorized to conduct a Super Search or not. If not, does NOT set XMERR and ^TMP("XMERR",$J). EDITOR: BEUSCHEL,GARY NUMBER: 2733 IA #: 2733 DATE CREATED: JAN 27, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMXSEC2 NAME: SECURITY, PERMISSIONS, & RESTRICTIONS API ID: XMXSEC2 GENERAL DESCRIPTION: These APIs perform security and permission functions. Please see the Programmer Manual on the Infrastructure web site for further information about the APIs and how to use them. STATUS: Active MAIL MESSAGE: 29724674 COMPONENT/ENTRY POINT: $$EDIT COMPONENT DESCRIPTION: Returns a value indicating whether the user may edit a message or not. COMPONENT/ENTRY POINT: OPTEDIT COMPONENT DESCRIPTION: If OPTMSG^XMXSEC2 (or $$EDIT^XMXSEC2) determines that the user may edit the message, then OPTEDIT determines what, exactly, the user may edit. COMPONENT/ENTRY POINT: $$OPTMSG COMPONENT DESCRIPTION: Determines what the user may do with the message. NUMBER: 2734 IA #: 2734 DATE CREATED: JAN 27, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMXUTIL NAME: MESSAGE & MAILBOX UTILITIES API ID: XMXUTIL GENERAL DESCRIPTION: These APIs are general message and mailbox utilities. Please see the Programmer Manual on the Infrastructure web site for further information about the APIs and how to use them. STATUS: Active MAIL MESSAGE: 29724674 COMPONENT/ENTRY POINT: $$BMSGCT COMPONENT DESCRIPTION: Returns the number of messages in a user's basket. COMPONENT/ENTRY POINT: $$BNMSGCT COMPONENT DESCRIPTION: Returns the number of new messages in a user's basket. COMPONENT/ENTRY POINT: $$BSKTNAME COMPONENT DESCRIPTION: Returns the name of a user's basket. COMPONENT/ENTRY POINT: $$NAME COMPONENT DESCRIPTION: Returns the name of the user (and, optionally, title and institution). COMPONENT/ENTRY POINT: $$NETNAME COMPONENT DESCRIPTION: Returns the network name of the user, including @site name. COMPONENT/ENTRY POINT: $$NEWS COMPONENT DESCRIPTION: Returns information about the new messages in a user's mailbox. COMPONENT/ENTRY POINT: $$TMSGCT COMPONENT DESCRIPTION: Returns the total number of messages in a user's mailbox. COMPONENT/ENTRY POINT: $$TNMSGCT COMPONENT DESCRIPTION: Returns the total number of new messages in a user's mailbox. COMPONENT/ENTRY POINT: $$KVAPOR COMPONENT DESCRIPTION: Sets/Removes a message vaporize date on a message in a user's basket. COMPONENT/ENTRY POINT: LASTACC COMPONENT DESCRIPTION: Records that the user has read the message. COMPONENT/ENTRY POINT: MAKENEW COMPONENT DESCRIPTION: Makes a message new and updates the new message counts. COMPONENT/ENTRY POINT: NONEW COMPONENT DESCRIPTION: Makes a message not new and updates the new message counts. COMPONENT/ENTRY POINT: PAGE COMPONENT DESCRIPTION: Displays to the user: "Enter RETURN to continue or ^ to exit:" and waits until the user presses a key. COMPONENT/ENTRY POINT: WAIT COMPONENT DESCRIPTION: Displays to the user: "Press RETURN to continue:" and waits until the user presses a key. COMPONENT/ENTRY POINT: $$BPMSGCT COMPONENT DESCRIPTION: Returns the number of new priority messages in a user's basket. COMPONENT/ENTRY POINT: $$TPMSGCT COMPONENT DESCRIPTION: Returns the total number of new priority messages in a user's mailbox. NUMBER: 2735 IA #: 2735 DATE CREATED: JAN 27, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMXUTIL1 NAME: DATE & STRING UTILITIES API ID: XMXUTIL1 GENERAL DESCRIPTION: These APIs perform date and string manipulation. Please see the Programmer Manual on the Infrastructure web site for further information about the APIs and how to use them. STATUS: Active MAIL MESSAGE: 29724674 COMPONENT/ENTRY POINT: $$CONVERT COMPONENT DESCRIPTION: Given an Internet date/time string, returns the VA FileMan date/time. COMPONENT/ENTRY POINT: $$CTRL COMPONENT DESCRIPTION: Strip control characters from a string. COMPONENT/ENTRY POINT: $$DECODEUP COMPONENT DESCRIPTION: Change all ~U~ to ^ in a string. COMPONENT/ENTRY POINT: $$ENCODEUP COMPONENT DESCRIPTION: Change all ^ to ~U~ in a string. COMPONENT/ENTRY POINT: $$GMTDIFF COMPONENT DESCRIPTION: Given the time zone, returns the difference (+-hhmm) from GMT. COMPONENT/ENTRY POINT: $$INDT COMPONENT DESCRIPTION: Given the VA FileMan date/time, returns the Internet date/time string. COMPONENT/ENTRY POINT: $$MAXBLANK COMPONENT DESCRIPTION: Reduce all three or more consecutive blanks in a string to two. COMPONENT/ENTRY POINT: $$MELD COMPONENT DESCRIPTION: Combine a string and a number to form a new string of a given length. COMPONENT/ENTRY POINT: $$MMDT COMPONENT DESCRIPTION: Given the VA FileMan date/time, returns MailMan date/time string. COMPONENT/ENTRY POINT: $$SCRUB COMPONENT DESCRIPTION: Strip control characters and leading/trailing blanks from a string. COMPONENT/ENTRY POINT: $$STRIP COMPONENT DESCRIPTION: Strip leading/trailing blanks from a string. COMPONENT/ENTRY POINT: $$TIMEDIFF COMPONENT DESCRIPTION: Given the decimal time difference between time zones, returns +-hhmm. COMPONENT/ENTRY POINT: $$TSTAMP COMPONENT DESCRIPTION: Return a timestamp. COMPONENT/ENTRY POINT: ZONEDIFF COMPONENT DESCRIPTION: Given a time zone (or time difference from GMT), returns the number of hours and minutes difference between that and the local time zone. NUMBER: 2736 IA #: 2736 DATE CREATED: JAN 27, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMXUTIL2 NAME: MESSAGE INFORMATION API ID: XMXUTIL2 GENERAL DESCRIPTION: These APIs return all kinds of information about a message. - Information that can be displayed. - Information that can be used to determine what may (and may not) be done with the message. Please see the Programmer Manual on the Infrastructure web site for further information about the APIs and how to use them. STATUS: Active MAIL MESSAGE: 29724674 COMPONENT/ENTRY POINT: $$BSKT COMPONENT DESCRIPTION: Returns which basket a message is in for a user. COMPONENT/ENTRY POINT: $$DATE COMPONENT DESCRIPTION: Returns the message sent date. COMPONENT/ENTRY POINT: $$FROM COMPONENT DESCRIPTION: Returns the message From information. COMPONENT/ENTRY POINT: $$KSEQN COMPONENT DESCRIPTION: Returns the sequence number fo a message in this user's basket. COMPONENT/ENTRY POINT: $$LINE COMPONENT DESCRIPTION: Returns the number of lines in the text of a message. COMPONENT/ENTRY POINT: $$NEW COMPONENT DESCRIPTION: Returns a value indicating whether or not a message is new for this user in this basket. COMPONENT/ENTRY POINT: $$PRI COMPONENT DESCRIPTION: Returns a value indicating whether the message is priority or not. COMPONENT/ENTRY POINT: $$QRESP COMPONENT DESCRIPTION: Determines whether a message is a response or not, and, optionally, if it is, which response to which message. COMPONENT/ENTRY POINT: $$RESP COMPONENT DESCRIPTION: Returns the number of responses to a message. COMPONENT/ENTRY POINT: $$SUBJ COMPONENT DESCRIPTION: Returns the message subject. COMPONENT/ENTRY POINT: $$ZDATE COMPONENT DESCRIPTION: Returns the message sent date. COMPONENT/ENTRY POINT: $$ZFROM COMPONENT DESCRIPTION: Returns the message From. COMPONENT/ENTRY POINT: $$ZNODE COMPONENT DESCRIPTION: Returns the message zero node. COMPONENT/ENTRY POINT: $$ZPRI COMPONENT DESCRIPTION: Returns a value indicating whether the message is priority or not. COMPONENT/ENTRY POINT: $$ZREAD COMPONENT DESCRIPTION: Returns the number of responses to a message this user has read. COMPONENT/ENTRY POINT: $$ZSUBJ COMPONENT DESCRIPTION: Returns the message subject. COMPONENT/ENTRY POINT: INMSG COMPONENT DESCRIPTION: Sets arrays with message information. COMPONENT/ENTRY POINT: INMSG1 COMPONENT DESCRIPTION: Sets arrays with message information, part 1. COMPONENT/ENTRY POINT: INMSG2 COMPONENT DESCRIPTION: Sets arrays with message information, part 2. COMPONENT/ENTRY POINT: INRESP COMPONENT DESCRIPTION: Sets an array with response information. COMPONENT/ENTRY POINT: INRESPS COMPONENT DESCRIPTION: Sets arrays indicating how many responses a message has, and how many of them the user has read. NUMBER: 2737 IA #: 2737 DATE CREATED: JAN 27, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMXUTIL3 NAME: MESSAGE INFORMATION API ID: XMXUTIL3 GENERAL DESCRIPTION: These APIs provide information about how a message was addressed and who has read it. Please see the Programmer Manual on the Infrastructure web site for further information about the APIs and how to use them. STATUS: Active MAIL MESSAGE: 32653697 COMPONENT/ENTRY POINT: Q COMPONENT DESCRIPTION: Get a list of the addressees of this message. Optionally, find addressees which match a string. COMPONENT/ENTRY POINT: QD COMPONENT DESCRIPTION: Get a list of the recipients of this message. Optionally, find recipients that match a string. COMPONENT/ENTRY POINT: QL COMPONENT DESCRIPTION: Get a list of the "latered" addressees of this message. Optionally, find the "latered" addressees that match a string. COMPONENT/ENTRY POINT: QN COMPONENT DESCRIPTION: Get the network header records from a message that originated at a remote site. COMPONENT/ENTRY POINT: QX COMPONENT DESCRIPTION: Get a list of local recipients who have: - read the message and all responses - not read the message and all responses - terminated the message NUMBER: 2738 IA #: 2738 FILE NUMBER: 120.8 GLOBAL ROOT: GMR(120.8 DATE CREATED: JAN 28, 1999 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR references to GMR(120.8 ID: GMR(120.8 GLOBAL REFERENCE: GMR(120.8,DA,0) FIELD NUMBER: 4 FIELD NAME: ORIGINATION DATE/TIME LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This DBIA documents OE/RR references to the PATIENT ALLERGIES file (#120.8). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946164 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2739 IA #: 2739 FILE NUMBER: 123.5 GLOBAL ROOT: GMR(123.5, DATE CREATED: JAN 28, 1999 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR references to GMR(123.5 ID: GMR(123.5, GLOBAL REFERENCE: GMR(123.5,DA,0) FIELD NUMBER: .01 FIELD NAME: SERVICE NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: SERVICE USAGE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: GMR(123.5,DA,.1) FIELD NUMBER: 1.11 FIELD NAME: PRINT NAME LOCATION: .1;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: GMR(123.5,'APR', GLOBAL DESCRIPTION: Loops through cross-reference by PROCEDURE TYPE. GENERAL DESCRIPTION: This DBIA documents OE/RR references tothe REQUEST SERVICES file (#123.5). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM DBA Comments: 6/3/14-MC: Brandon DeWayne originally requested that FBCS be added as a subscriber to ICR on 6/20/13. Approval received from Tony Thompson. Patch was released on 9/11/13 as an emergency patch. Since approval has been received and patch (DSIF*3.2*29) was released, adding FBCS as a subscribing package to ICR. NUMBER: 2740 IA #: 2740 DATE CREATED: JAN 28, 1999 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCSLM1 NAME: OE/RR calls to GMRCSLM1 ID: GMRCSLM1 GENERAL DESCRIPTION: This DBIA documents calls to GMRCSLM1 as found in the OE/RR v3 interface specification document. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 COMPONENT/ENTRY POINT: OER(DFN,SERVICE,BEG-DT,END-DT,STATUS) COMPONENT DESCRIPTION: Returns a list of consult/procedures. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of the PATIENT file VARIABLES: SERVICE TYPE: Input VARIABLES DESCRIPTION: IEN of the REQUEST SERVICE file VARIABLES: BEG-DT TYPE: Input VARIABLES DESCRIPTION: Beginning date for search VARIABLES: END-DT TYPE: Input VARIABLES DESCRIPTION: End date for search VARIABLES: STATUS TYPE: Input VARIABLES DESCRIPTION: IEN of the ORDER STATUS file VARIABLES: TMP('GMRCR,$J,'C',#,0) TYPE: Output VARIABLES DESCRIPTION: ^TMP("GMRCR",$J,"CS",#,0)=IEN^request date^order status^service^name of procedure or consult # is a sequential number SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING DETAILS: Imaging added 2/15/2011 SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: Effective with VPR*1*0 SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 08/02/13 DT: Added subscriber for VPR*1*0 per request by Melanie Buechler and concurrence by Tony Thompson. 10/2/14-MC: Added VPS as a subscriber as requested by Carolyn Wheless and approved by Tony Thompson for patch VPS*1*4. VPS will return the list of a patient's consult requests within a date range to VetLink. DATE/TIME EDITED: FEB 15, 2011@12:44 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: TOPALOV,NIKOLAY WITH CONCURRENCE OF: THOMPSON,TONY DATE/TIME EDITED: AUG 02, 2013@12:59 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: THOMPSON,TONY NUMBER: 2741 IA #: 2741 DATE CREATED: JAN 28, 1999 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMPLUTL2 NAME: OE/RR calls to GMPLUTL2 ID: GMPLUTL2 CREATOR: CHUNG,TERESA L GENERAL DESCRIPTION: This DBIA documents calls made to routine GMPLUTL2. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34250720 COMPONENT/ENTRY POINT: $$PARAM() COMPONENT DESCRIPTION: Returns the 0 node of the PROBLEM LIST SITE PARAMETERS file (#125.99) COMPONENT/ENTRY POINT: DETAIL(IEN,.GMPL) COMPONENT DESCRIPTION: Returns detailed data for a problem IEN. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of PROBLEM file (#9000011). VARIABLES: GMPL TYPE: Output VARIABLES DESCRIPTION: Array returned as follows (all are in external format except AUDIT data unless otherwise specified): Array: Field Returned GMPL("DIAGNOSIS") DIAGNOSIS (#.01) GMPL("ICDD") ICD DESCRIPTION GMPL("CSYS") CODING SYSTEM (#80202) GMPL("DTINTEREST") DATE OF INTEREST (#80201) GMPL("PATIENT") PATIENT NAME (#.02) GMPL("MODIFIED") LAST MODIFIED (#.03) GMPL("NARRATIVE") NARRATIVE (#.05) GMPL("ENTERED") DATE ENTERED (#.08) ^ ENTERED BY (#1.03) GMPL("STATUS") STATUS (#.12) GMPL("PRIORITY") PRIORITY (#1.14) or null if INACTIVE GMPL("ONSET") DATE OF ONSET (#.13) GMPL("PROVIDER") ENTERED BY (#1.03) GMPL("RECORDED") RECORDED (#1.09) ^ REC PROVIDER (#1.04) GMPL("CONDITION") PATIENT CONDITION (#1.02) GMPL("RESOLVED") DATE RESOLVED (#1.07) GMPL("CLINIC") CLINIC (#1.08) GMPL("SERVICE") SERVICE (#1.06) GMPL("FACILITY") FACILITY ID (#.06) ^ FACILITY NAME GMPL("SC") SERV CONNECTED(#1.1) (UNKNOWN if not 1/0) GMPL("SCTC") SNOMED-CT CONCEPT CODE (#80001) GMPL("SCTD") SNOMED-CT DESIGNATION CODE (#80002) GMPL("SCTT") SNOMED-CT PREFERRED TEXT GMPL("VHATC") VHAT CONCEPT CODE (#80003) GMPL("VHATD") VHAT DESIGNATION CODE (#80004) GMPL("VHATT") VHAT PREFERRED TEXT GMPL("ICD9MLTP") COUNT OF MAPPING TARGETS GMPL("ICD9MLTP",CNT) ICD-9/ICD-10 CODE (#80300.01) ^ ICD-9/ICD-10 DESCRIPTION ^ ICD CODING SYSTEM (#80300.02) GMPL("EXPOSURE") Count of exposures GMPL("EXPOSURE",#) Name of each exposure GMPL("COMMENT") Count of comments GMPL("COMMENT",#) DATE NOTE ADDED ^ AUTHOR ^ [NOTE TEXT] GMPL("COMMENT",#,n) Line of comment text GMPL("AUDIT") Count of changes GMPL("AUDIT",#) FIELD# ^ FIELD NAME ^ DATE MODIFIED ^ WHO MODIFIED ^ OLD VALUE ^ NEW VALUE ^ REASON ^PROVIDER COMPONENT/ENTRY POINT: LIST(.GMPL,DFN,STATUS,COMMENTS?) COMPONENT DESCRIPTION: Returns a list of problems for a patient (DFN) VARIABLES: GMPL TYPE: Output VARIABLES DESCRIPTION: GMPL(0)=number of problems GMPL(#)=IEN^status^description^icd^onset^ last modified^SC^exposure^*^$ GMPL(#,C#) = comment lines * is returned if ACUTE, otherwise null $ is returned if CONDITION is TRANSCRIBED and VERIFY TRANSCRIBED PROBLEMS parameter is set to YES, otherwise null VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of the PATIENT file VARIABLES: STATUS TYPE: Input VARIABLES DESCRIPTION: A for active, I for inactive, other for both statuses VARIABLES: COMMENTS? TYPE: Input VARIABLES DESCRIPTION: 1 to return comments. 0, null, or undefined for no comments. COMPONENT/ENTRY POINT: ADD(DFN,LOCATION,PROVIDER) COMPONENT DESCRIPTION: Interactive list manager action to add a new provider VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of PATIENT file VARIABLES: LOCATION TYPE: Input VARIABLES DESCRIPTION: IEN of HOSPITAL LOCATION file VARIABLES: PROVIDER TYPE: Input VARIABLES DESCRIPTION: IEN of NEW PERSON file COMPONENT/ENTRY POINT: EDIT(DFN,LOCATION,PROVIDER,PROBLEM) COMPONENT DESCRIPTION: Interactive list manager action to edit an existing problem VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of PATIENT file VARIABLES: LOCATION TYPE: Input VARIABLES DESCRIPTION: IEN of HOSPITAL LOCATION file VARIABLES: PROVIDER TYPE: Input VARIABLES DESCRIPTION: IEN of NEW PERSON file VARIABLES: PROBLEM TYPE: Input VARIABLES DESCRIPTION: IEN of PROBLEM file COMPONENT/ENTRY POINT: REMOVE(PROBLEM,PROVIDER,TEXT,.REPLY) COMPONENT DESCRIPTION: Removes a problem VARIABLES: PROBLEM TYPE: Input VARIABLES DESCRIPTION: IEN of PROBLEM file VARIABLES: PROVIDER TYPE: Input VARIABLES DESCRIPTION: IEN of NEW PERSON file VARIABLES: TEXT TYPE: Input VARIABLES DESCRIPTION: Text to store VARIABLES: REPLY TYPE: Output VARIABLES DESCRIPTION: REPLY = -1 if problem, IEN otherwise REPLY(0) = error message if problem, "" otherwise COMPONENT/ENTRY POINT: VAF(DFN,SILENT) COMPONENT DESCRIPTION: Prints a chartable Problem List report, with optional prompt for device if 'SILENT VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of PATIENT file VARIABLES: SILENT TYPE: Input VARIABLES DESCRIPTION: 1 if report to be silently captured to Host File Server, otherwise will prompt for device SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: MYHEALTHEVET SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING PACKAGE: SURGERY SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 6/26/12-mm: VPR added as a subscriber for VPR*1.0. Needed for VistA extracts and approved by Joel Russell. 6/16/14-MC: Surgery added as a subscriber as requested by James Harris and approved by Teresa Chung. Patch is SR*3.0*180 scheduled for IOC in the Fall of 2014 10/21/14-MC: Teresa Chung was reviewing the ICR during a request by VPS, and noticed that the output variable of the DETAIL needs updating. Deactivating ICR for edits and making Teresa the editor in order to make necessary corrections prior to allowing VPS to be added as a subscriber. 11/5/14-MC: Teresa completed updating the output variable of the DETAIL and added VPS as a subscriber. Activating the ICR for VPS*1*4 at the request of Carolyn Wheless and approved by Teresa Chung. DATE ACTIVATED: NOV 05, 2014 DATE/TIME EDITED: SEP 16, 2010@10:56 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE DATE/TIME EDITED: JUN 26, 2012@15:00 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CHUNG,TERESA WITH CONCURRENCE OF: RUZBACKI,RON DATE/TIME EDITED: NOV 05, 2014@12:11 ACTION: APPROVED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: CHUNG,TERESA NUMBER: 2742 IA #: 2742 DATE CREATED: JAN 28, 1999 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMPLX NAME: OE/RR calls to GMPLX ID: GMPLX GENERAL DESCRIPTION: This DBIA documents OE/RR calls to routine GMPLX. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 35925817 COMPONENT/ENTRY POINT: $$PROBTEXT(IEN) COMPONENT DESCRIPTION: Returns external format of PROVIDER NARATIVE field (#.05) in PROBLEM file (#9000011). VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of PROBLEM file. COMPONENT/ENTRY POINT: DTMOD(IEN) COMPONENT DESCRIPTION: Updates DATE LAST MODIFIED field (#.03) to value of system variable DT. Used by CPRS GUI only. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of PROBLEM file COMPONENT/ENTRY POINT: AUDIT(NODE0,NODE1) COMPONENT DESCRIPTION: Store data in AUDIT file (used by CPRS GUI) VARIABLES: NODE0 TYPE: Input VARIABLES DESCRIPTION: 0 node to be placed in PROBLEM LIST AUDIT file (#125.8) VARIABLES: NODE1 TYPE: Input VARIABLES DESCRIPTION: 1 node to be placed in PROBLEM LIST AUDIT file (#125.8) COMPONENT/ENTRY POINT: $$DUPL(DFN,TERM,TEXT) COMPONENT DESCRIPTION: This entry point checks a patient's problem list and returns an IEN if there is already a matching entry on file. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of the PATIENT file VARIABLES: TERM TYPE: Input VARIABLES DESCRIPTION: The value for the PROBLEM field of the PROBLEM file (#9000011). VARIABLES: TEXT TYPE: Input VARIABLES DESCRIPTION: The value of the PROVIDER NARRATIVE (#.05) field of the PROBLEM file (#9000011). COMPONENT/ENTRY POINT: $$CODESTS(PROB,ADATE) COMPONENT DESCRIPTION: This component accepts a pointer to the PROBLEM (#9000011) file and a VA Fileman date as input. The component checks the status of the ICD9 code attached to the problem on the date passed. The component returns a boolean value of 1 (one) if the code is active on the specified date, a 0 (zero) is returned if inactive. VARIABLES: PROB TYPE: Input VARIABLES DESCRIPTION: This variable is a pointer to the PROBLEM (#9000011) file. VARIABLES: ADATE TYPE: Input VARIABLES DESCRIPTION: This variable is a FM date on which to check the status of the ICD9 code associated with the problem. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2743 IA #: 2743 DATE CREATED: JAN 28, 1999 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMPLX1 NAME: OE/RR calls to GMPLX1 ID: GMPLX1 GENERAL DESCRIPTION: This DBIA will document calls made from OE/RR (CPRS GUI only) to routine GMPLX1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34251304 COMPONENT/ENTRY POINT: $$VIEW(DUZ) COMPONENT DESCRIPTION: Returns value for PROBLEM LIST PRIMARY VIEW field (#125) from NEW PERSON file (#200). VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: IEN of NEW PERSON file for user utilizing CPRS GUI. COMPONENT/ENTRY POINT: $$SERVICE(DUZ) COMPONENT DESCRIPTION: Returns users service/section in internal^external format VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: IEN of NEW PERSON file for user utilizing CPRS GUI. COMPONENT/ENTRY POINT: VADPT(DFN) COMPONENT DESCRIPTION: Returns information on SC, Agent Orange, Ioninzing Radiation, Gulf War, Head and/or Neck Cancer and Military Sexual Trauma. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of PATIENT file VARIABLES: GMPSC TYPE: Output VARIABLES DESCRIPTION: Service Connected Indicator: 1 if yes, 0 if no, "" if unknown VARIABLES: GMPAGTOR TYPE: Output VARIABLES DESCRIPTION: Agent Orange Exposure Indicator: 1 if yes, 0 if no, "" if unknown VARIABLES: GMPION TYPE: Output VARIABLES DESCRIPTION: Ionizing Radiation Indicator: 1 if yes, 0 if no, "" if unknown VARIABLES: GMPGULF TYPE: Output VARIABLES DESCRIPTION: Persian Gulf indicator: 1 if yes, 0 if no, "" if unknown VARIABLES: GMPHNC TYPE: Output VARIABLES DESCRIPTION: Head and/or Neck Cancer Indicator: 1 if yes, 0 if no, "" if unknown VARIABLES: GMPMST TYPE: Output VARIABLES DESCRIPTION: Military Sexual Trauma Indicator: 1 if yes, 0 if no, "" if unknown COMPONENT/ENTRY POINT: SCCOND(DFN,.SC) COMPONENT DESCRIPTION: Returns information on SC, Agent Orange, Ioninzing Radiation, Gulf War, Head and/or Neck Cancer and Military Sexual Trauma in an array passed by reference. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of PATIENT file VARIABLES: SC TYPE: Output VARIABLES DESCRIPTION: Local array passed by reference containing a patient's exposure/condition indicators. SC("AO") = Agent Orange Exposure Indicator SC("DFN") = IEN of Patient File SC("HNC") = Head and/or Neck Cancer Indicator SC("IR") = Ionizing Radiation Indicator SC("MST") = Military Sexual Trauma Indicator SC("PG") = Persian Gulf Indicator SC("SC") = Service Connected Indicator 1 if yes, 0 if no, "" if unknown COMPONENT/ENTRY POINT: SCS(PROB,.SC) COMPONENT DESCRIPTION: Returns a combined string of exposure/conditions in 3 formats, delimited abbreviation, delimitied initials and initials. VARIABLES: PROB TYPE: Input VARIABLES DESCRIPTION: IEN of PROBLEM file 9000011 VARIABLES: SC TYPE: Output VARIABLES DESCRIPTION: Array containing combined strings of exposures and/or conditions that relate to the problem identified by input variable PROB. OUTPUT: SC(1) = AO/IR/EC/HNC/MST Delimited abbreviation SC(2) = A/I/E/H/M Delimited Initials SC(3) = AIEHM Initials SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2746 IA #: 2746 FILE NUMBER: 991.8 GLOBAL ROOT: RGSITE(991.8, DATE CREATED: FEB 03, 1999 CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: CIRN SITE PARAMETER 991.8 ID: RGSITE(991.8, GLOBAL REFERENCE: RGSITE(991.8, FIELD NUMBER: .03 FIELD NAME: NEW REQUEST MAILGROUP LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: LOCAL/MISSING DATE LAST RAN LOCATION: 0;4 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .01 FIELD NAME: PARAMETER NUMBER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: CMOR REQUEST CHANGE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 18 FIELD NAME: CMOR LAST PATIENT PROCESSED LOCATION: CMOR;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 19 FIELD NAME: CMOR INIT STARTED DATE/TIME LOCATION: CMOR;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 20 FIELD NAME: CMOR INIT STOPPED DATE/TIME LOCATION: CMOR;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 21 FIELD NAME: CMOR INIT MANUAL STOP LOCATION: CMOR;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 22 FIELD NAME: CMOR DAILY START TIME LOCATION: CMOR;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 23 FIELD NAME: CMOR DAILY STOP TIME LOCATION: CMOR;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 24 FIELD NAME: CMOR INIT STATUS LOCATION: CMOR;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 25 FIELD NAME: CMOR RUN TYPE LOCATION: CMOR;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 26 FIELD NAME: CMOR LAST TASK# LOCATION: CMOR;9 ACCESS: Direct Global Read & w/Fileman STATUS: Active MAIL MESSAGE: 28813797 SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA SUBSCRIBING DETAILS: The Master Patient Index developers requested access to the NEW REQUEST MAILGROUP (#.03) field in the CIRN SITE PARAMETER file (#991.8) via a direct global read. NUMBER: 2747 IA #: 2747 DATE CREATED: JUL 28, 2003 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORCSAVE2 NAME: ORCSAVE2 ID: ORCSAVE2 GENERAL DESCRIPTION: This agreement permits access to data stored in the Orders file (#100) in OE/RR. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 36881626 COMPONENT/ENTRY POINT: VALUE COMPONENT DESCRIPTION: Returns the value of a user's response within the order. VARIABLES: IFN TYPE: Input VARIABLES DESCRIPTION: IEN in the Orders file #100. VARIABLES: ID TYPE: Input VARIABLES DESCRIPTION: A name that identifies the desired value, corresponding to the ID field (#13) of the prompt in the Order Dialog file #101.41 that created the value. VARIABLES: INST TYPE: Input VARIABLES DESCRIPTION: The instance desired; 1 is assumed if not specified [Not Required]. COMPONENT/ENTRY POINT: COMP COMPONENT DESCRIPTION: Marks an order as completed; fields COMPLETED (#66) and COMPLETED BY (#67) will be populated in the Orders file #100, and the status changed to COMPLETE. VARIABLES: IFN TYPE: Input VARIABLES DESCRIPTION: IEN in the Orders file #100. VARIABLES: WHO TYPE: Input VARIABLES DESCRIPTION: IEN in New Person file #200 of user that completed the order; DUZ is assumed if not specified. VARIABLES: WHEN TYPE: Input VARIABLES DESCRIPTION: Date/time when order was completed, in FileMan format; NOW is assumed if not specified. SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING DETAILS: Uses component $$VALUE to retrieve order responses. SUBSCRIBING PACKAGE: CARE MANAGEMENT ISC: Salt Lake City SUBSCRIBING DETAILS: Uses $$VALUE to retrieve order responses, and COMP to complete orders. SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT SUBSCRIBING DETAILS: ADDED 9/25/08 SUBSCRIBING PACKAGE: HEALTH SUMMARY DATE/TIME EDITED: SEP 25, 2008@09:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: BUECHLER,MELANIE DATE/TIME EDITED: JAN 19, 2011@08:49 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SILVERMAN,ROBERT NUMBER: 2748 IA #: 2748 DATE CREATED: FEB 04, 1999 CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MPIFAPI NAME: MPIQ(DFN) in MPIFAPI ID: MPIFAPI GENERAL DESCRIPTION: MPI is providing support for the Registration package to provide real-time queries to the MPI for assignment of an ICN and CMOR. If the MPI is not available, a local ICN will be assigned instead. If the MPI does not already know of this patient, the patient will be added and assigned an ICN. The call to accomplish this task is MPIQ^MPIFAPI(DFN), where DFN is the IEN of the patient in the Patient file. This code is to be inserted after all the required data has been collected on a new patient (new to the Patient file (#2)). If the patient is already known, this code should be inserted after the patient has been selected. Interaction will only occur with the MPI if the patient does not have an ICN assignment. This API is NOT a silent one. It can be made silent by setting the variable MPIFS=1 prior to calling this API. The variable shouldn't be new'd prior to calling MPIQ^MPIFAPI but should be killed after the call has been made. NOTE: The following fields will be updated in the Patient file (#2) when a successful interaction with the MPI has occurred: INTEGRATION CONTROL NUMBER (#991.01), ICN CHECKSUM (#991.02), and CIRN MASTER OF RECORD (#991.03). If the MPI was unavailable, in addition to the fields noted above, the LOCALLY ASSIGNED ICN (#991.04) would be set to yes. STATUS: Active MAIL MESSAGE: 28966235 COMPONENT/ENTRY POINT: MPIFQ COMPONENT DESCRIPTION: MPIQ^MPIFAPI(DFN) is a procedure call that allows a real-time connection with the MPI to request/query for an Integration Control Number (ICN). DFN is passed as the IEN for the patient in the Patient file (#2). the following is the suggested coding for this API: N X S X="MPIFAPI" X ^%ZOSF("TEST") Q:'$T D MPIQ^MPIFAPI(DFN) K MPIFRTN If the call should be silent, MPIFS should be set to 1 prior to calling MPIQ^MPIFAPI and killed afterwards. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN is the IEN of the patient in the Patient file (#2). SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: MYHEALTHEVET SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING DETAILS: RPC - DVBAB MPI ASSIGN ICN from CAPRI GUI -- a silent call to the MPIQ entry point. NUMBER: 2750 IA #: 2750 DATE CREATED: FEB 08, 1999 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSADOR NAME: GMTSADOR ROUTINE ID: GMTSADOR GENERAL DESCRIPTION: The Women's Health package requests permission to call the Health Summary package routine GMTSADOR at the line label of MAIN. This entry point will allow Women's Health package users to create adhoc health summary reports from within the Women's Health package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29000717 COMPONENT/ENTRY POINT: MAIN VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient internal entry number SUBSCRIBING PACKAGE: WOMEN'S HEALTH ISC: Hines NUMBER: 2751 IA #: 2751 FILE NUMBER: 391.91 GLOBAL ROOT: DGCN(391.91 DATE CREATED: MAR 15, 1999 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DGCN(391.91 Treating Facility file ID: DGCN(391.91 GLOBAL REFERENCE: DGCN(391.91,'APAT' GLOBAL DESCRIPTION: Checking for the existance of the ^DGCN(391.91,"APAT",,) so that an addition to the file won't occur if it already exists. GLOBAL REFERENCE: DGCN(391.91, FIELD NUMBER: .02 FIELD NAME: INSTITUTION LOCATION: 0;2 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the Institution that the patient was treated at. FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is a pointer to the patient in question that was seen at this treating facility. GLOBAL DESCRIPTION: Adding an entry to the Treating Facilit file via FILE^DICN call populating .01 and .02 fields. GENERAL DESCRIPTION: The Master Patient Index - VistA package is requesting to add entries to the Treating Facility (#391.91) file via FILE^DICN call and to check the "APAT" cross reference for the existence of the entry. STATUS: Active MAIL MESSAGE: 28504262 SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA NUMBER: 2752 IA #: 2752 DATE CREATED: MAR 15, 1999 CUSTODIAL PACKAGE: VA FILEMAN USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: OUTPATIENT PHARMACY: DD UPDATES GENERAL DESCRIPTION: Outpatient Pharmacy V. 7.0 has permission to kill the following ^DD entries in patch PSO*7*25. This is a one time agreement. ^DD(55,0,"P") ^DD(55,0,"PS") STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29225439 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY NUMBER: 2755 IA #: 2755 DATE CREATED: FEB 17, 1999 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFCMSG5 NAME: $$GETSRVR VAFCMSG5 ID: VAFCMSG5 GENERAL DESCRIPTION: MPIF is requesting to use $$GETSRVR^VAFCMSG5 to get the pointer to the HL7 server protocol for the A28 event type. STATUS: Active MAIL MESSAGE: 28844558 COMPONENT/ENTRY POINT: $$GETSRVR COMPONENT DESCRIPTION: $$GETSRVR^VAFCMSG5(EVNTTYPE) Gets the pointer to HL7 Server Protocol for a given event type. VARIABLES: EVNTTYPE TYPE: Input VARIABLES DESCRIPTION: EVNTTYPE - Event type to build list for (Defaults to A08). Currently supported events: A04, A08, A28. VARIABLES: $$GETSRVR TYPE: Output VARIABLES DESCRIPTION: $$GETSRVR will return the pointer to HL7 Server Protocol (value for HLEID). Note: Zero (0) will be returned if the event does not have an associated HL7 Server Protocol or the HL7 Server Protocol can not be found in the PROTOCOL file (#101). SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA NUMBER: 2756 IA #: 2756 DATE CREATED: FEB 17, 1999 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFCMSG1 NAME: $$BLDMSG VAFCMSG1 ID: VAFCMSG1 GENERAL DESCRIPTION: MPIF is requesting to use $$BLDMSG^VAFCMSG1 to build the HL7 ADT-A28 message for a given patient. STATUS: Active MAIL MESSAGE: 28839748 COMPONENT/ENTRY POINT: $$BLDMSG COMPONENT DESCRIPTION: $$BLDMSG^VAFCMSG1(DFN,EVNTHL7,EVNTDATE,EVNTINFO,XMITARRY,INSRTPNT) This entry point builds HL7 ADT messages for a given patient. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN - Pointer to entry in PATIENT file (#2) for building message. VARIABLES: EVNTHL7 TYPE: Input VARIABLES DESCRIPTION: EVNTHL7 - HL7 ADT event to build message for (Defaults to A08) Currently supported event types: A04, A08, A28. VARIABLES: EVNTDATE TYPE: Input VARIABLES DESCRIPTION: EVNTDATE - Date/time event occurred in FileMan format - Defaults to current date/time (NOW) VARIABLES: EVNTINFO TYPE: Input VARIABLES DESCRIPTION: EVNTINFO - Array containing further event information needed when building HL7 segments/message. Use and subscripting of array is determined by segment and/or message being built. - Defaults to ^TMP("VAFCMSG",$J,"EVNTINFO") Current subscripts include: EVNTINFO("DFN") = Pointer to PATIENT file (#2) EVNTINFO("EVENT") = Event type EVNTINFO("DATE") = Event date/time EVNTINFO("PIVOT") = Pointer to ADT/HL7 PIVOT file (#391.71) EVNTINFO("REASON",X) = Event reason codes EVNTINFO("USER") = User associated with the event VARIABLES: XMITARRAY TYPE: Both VARIABLES DESCRIPTION: As Input: XMITARRY - Array to build message into (full global reference) - Defaults to ^TMP("HLS",$J) As Output: XMITARRY(N) = Line N of message XMITARRY(N,M) = Continuation number M of line N VARIABLES: INSRTPNT TYPE: Input VARIABLES DESCRIPTION: INSRTPNT - Line to begin inserting message text at - Defaults to 1 (can not be zero or less) VARIABLES: $$BLDMSG TYPE: Output VARIABLES DESCRIPTION: LastLine^TotalLine = ADT-Axx message was build Where LastLine = Last line number in message and TotalLine = Number of lines in message (this total includes continuation lines) OR -1^ErrorText = Error generating ADT-Axx message SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA NUMBER: 2757 IA #: 2757 DATE CREATED: FEB 18, 1999 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MCARPS2 NAME: OE/RR calls to MCARPS2 ID: MCARPS2 GENERAL DESCRIPTION: This DBIA authorizes OE/RR v3 calling EN^MCARPS2(DFN) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30947645 COMPONENT/ENTRY POINT: EN(DFN) COMPONENT DESCRIPTION: Returns procedures for a patient. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of PATIENT file VARIABLES: global TYPE: Output VARIABLES DESCRIPTION: Global containing a list of procedures for display in OE/RR. Located at ^TMP("OR",$J,"MCAR", This temporary global is sorted by either inverse date or Procedure Name, based on input parameters. Subscripts S1 and S2 hold the sort values. The sorted version of the TMP global is used for selection of procedures. The second version is used as input to produce the report. $P(^TMP("OR",$J,"MCAR",S1,S2),U,1)=Gross Evaluation ...),U,2)=Pointer to Procedure ...),U,3)=Print Routine (Field #5 from file 697.2) ...),U,4)=Print Line (Field #6 from file 697.2) ...),U,5)=Print Name (Field #7 from file 697.2) ...),U,10)=Summary Title ...),U,11)=Procedure Name ...),U,12)=Print Name_"/"_Procedure Name $P(^TMP("OR",$J,"MCAR","OT",L),U,1)=Print Name ...),U,2)=Pointer to Procedure ...),U,3)=Print Routine ...),U,4)=Print Line ...),U,5)=Print Name ...),U,6)=Date/time of procedure ...),U,7)=Gross Evaluation ...),U,10)=Summary Title ...),U,11)=Inverse date or Procedure (depends on sort) ...),U,12)=Procedure or Inverse date (depends on sort)^ Note: The global ^TMP("MCAR",$J) should be killed before and after the call to EN^MCARPS2. VARIABLES: S5 TYPE: Input VARIABLES DESCRIPTION: S5 may be optionally set to return results from a single file. Values may be: "MCAR(691" for ECHO "MCAR(691.1" for CARDIAC CATHETERIZATION "MCAR(691.5" for ELECTROCARDIOGRAM "MCAR(691.6" for HOLTER "MCAR(691.7" for EXERCISE TOLERANCE "MCAR(691.8" for ELECTROPHYSIOLOGY "MCAR(694" for HEMATOLOGY "MCAR(698" for GENERAL IMPLANT "MCAR(698.1" for V LEAD IMPLANT "MCAR(698.2" for A LEAD IMPLANT "MCAR(698.3" for PACEMAKER SURVEILLANCE "MCAR(699" for ENDOSCOPY/CONSULT "MCAR(700" for PULMONARY FUNCTION TESTS "MCAR(701" for RHEUMATOLOGY SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: NUMBER: 2758 IA #: 2758 DATE CREATED: FEB 22, 1999 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA2758 GENERAL DESCRIPTION: REGISTRATION OPTIONS on CIRN namespaced menus. Patient Data Review [VAFC EXCEPTION HANDLER] option on the MPI/PD Patient Admin User Menu [RG ADMIN USER MENU] Purge Patient Data Reviews [VAFC PDR PURGE] option on the MPI/PD Patient Admin User Menu [RG ADMIN USER MENU] STATUS: Active MAIL MESSAGE: 29063524 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2761 IA #: 2761 DATE CREATED: FEB 26, 1999 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: ATTACH OR PROTOCOLS TO GMRC PROTOCOLS GENERAL DESCRIPTION: CONSULT/REQUEST TRACKING version 3.0 requests the ability to attach three new OR namespaced protocols to GMRC protocols. This is for the purpose of updating CPRS with staus updates to orders from CONSULT/REQUEST TRACKING and updating CPRS with new orderable items from CONSULT/REQUEST TRACKING. The specific protocol linkage: 1) Attach OR RECEIVE and ORDER CHECK HL7 RECIEVE to GMRC EVSEND OR 2) Attach OR ITEM RECEIVE to GMRC ORDERABLE ITEM UPDATE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29118621 SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING NUMBER: 2762 IA #: 2762 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: MAR 01, 1999 CUSTODIAL PACKAGE: VA FILEMAN USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: minus 9 nodes ID: DPT( GLOBAL REFERENCE: DPT(da,-9 GLOBAL DESCRIPTION: The -9 node in the DPT global is being set by the Duplicate Record Merge software after a pair of records is merged. The FROM (record going away) record gets a -9 node entry to prevent the useage of this record. MPI wants to be sure not to get these patients and is checking for the existance of the node. GENERAL DESCRIPTION: MPI needs to check for the -9 node on the Patient file. If the -9 node exists for a given entry, the MPI needs to not use this patient entry. STATUS: Active MAIL MESSAGE: 28504604 SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY NUMBER: 2763 IA #: 2763 GLOBAL ROOT: %ZTSK( DATE CREATED: MAR 01, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Read %ZTSK Global ID: %ZTSK( GENERAL DESCRIPTION: Because Fileman supports both a non-VistA Kernel environment and a VistA Kernel environment, a test is necessary to determine which environment is present. A test that is used to determin if Queueing is Allowed, therefore a VistA Kernel environment, is by checking whether or not the %ZTSK global is present. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29133830 SUBSCRIBING PACKAGE: VA FILEMAN ISC: Oakland NUMBER: 2764 IA #: 2764 DATE CREATED: MAR 02, 1999 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORB3FUP2 NAME: BACKWARD COMPATIBILITY FOR ALERT FOLLOW-UP ID: ORB3FUP2 GENERAL DESCRIPTION: Consult/Request Tracking version 3.0 requests the ability to call RPTCON^ORB3FUP2 from routine GMRCXQ. This will allow existing alerts at the time of Consult/Request Tracking version 3.0 installation to be processed correctly without conversion. This code would branch accordingly to the proper code in the GMRC namespace. This would be called as a result of processing three OE/RR NOTIFICATION types: CONSULT/REQUEST RESOLUTION CONSULT/REQUEST CANCEL/HOLD SERVICE CONSULT/REQUEST STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29140731 SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City EDITOR: RUTHERFORD,JERALD F NUMBER: 2766 IA #: 2766 DATE CREATED: MAR 05, 1999 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LR7OSUM NAME: Formatted Lab Results ID: LR7OSUM GENERAL DESCRIPTION: These calls get formatted Lab Results output into a global array. These formats are based on definitions in the Lab Reports file (64.5) for CH subscripted tests. For AP, Micro and Blood Bank, the format is a hard coded traditional format. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29160164 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: This gets a 'silent', formatted report of lab results. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient ID VARIABLES: SDATE TYPE: Input VARIABLES DESCRIPTION: Start date to search for results (optional). VARIABLES: EDATE TYPE: Input VARIABLES DESCRIPTION: End date to search for results (optional). VARIABLES: COUNT TYPE: Input VARIABLES DESCRIPTION: Number of results to send (optional). VARIABLES: GIOM TYPE: Input VARIABLES DESCRIPTION: Right margin. Default is 80 (optional). VARIABLES: SUBHEAD TYPE: Input VARIABLES DESCRIPTION: Array of subheaders to include in report (optional). These are subheaders from file 64.5 for CH subscripted tests. For other lab areas, they are: SUBHEAD("MICROBIOLOGY") SUBHEAD("BLOOD BANK") SUBHEAD("MISCELLANEOUS TESTS") SUBHEAD("CYTOPATHOLOGY") SUBHEAD("SURGICAL PATHOLOGY") SUBHEAD("EM") SUBHEAD("AUTOPSY") No entry in this parameter gets everything. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: This tells where the formatted output is (^TMP("LRC",$J)). COMPONENT/ENTRY POINT: AP COMPONENT DESCRIPTION: This entry point gets all Anatomic Pathology results in a formatted array. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient ID COMPONENT/ENTRY POINT: GET64 COMPONENT DESCRIPTION: This gets an array of minor headers from the Lab Reports file (64.5). VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Array containing the subheaders from file 64.5. NUMBER: 2767 IA #: 2767 DATE CREATED: MAR 05, 1999 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LRDIST4 NAME: Graph Lab Results ID: LRDIST4 GENERAL DESCRIPTION: These are the entry points used by CPRS to display Lab results graph. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29160164 COMPONENT/ENTRY POINT: L2 COMPONENT DESCRIPTION: Prompts for values needed to graph results. COMPONENT/ENTRY POINT: OERR COMPONENT DESCRIPTION: Sets up patient variables needed. VARIABLES: ORVP TYPE: Input VARIABLES DESCRIPTION: OE/RR's patient ID. DFN;DPT( COMPONENT/ENTRY POINT: CLEAN COMPONENT DESCRIPTION: Cleans up variables used. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2768 IA #: 2768 DATE CREATED: MAR 05, 1999 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LRGEN NAME: Lab Results ID: LRGEN GENERAL DESCRIPTION: This is used by CPRS to get selected Lab Results displayed. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29160164 COMPONENT/ENTRY POINT: SET COMPONENT DESCRIPTION: Set up variables needed prior to calling SET1. COMPONENT/ENTRY POINT: SET1 COMPONENT DESCRIPTION: Prints patient report. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient ID. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2769 IA #: 2769 DATE CREATED: MAR 05, 1999 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LRRP4 NAME: Lab Results Interim Format ID: LRRP4 GENERAL DESCRIPTION: This is used by CPRS to get a display of lab results in interim format. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29160164 COMPONENT/ENTRY POINT: SET COMPONENT DESCRIPTION: Setup variables needed by lab interim routines. COMPONENT/ENTRY POINT: OERR COMPONENT DESCRIPTION: Get display of Lab Results. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient ID. VARIABLES: ~TMP("LR",$J, TYPE: Output VARIABLES DESCRIPTION: May be killed before and after call to OERR. COMPONENT/ENTRY POINT: CLEAN COMPONENT DESCRIPTION: Clean-up variables used to obtain report. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2770 IA #: 2770 DATE CREATED: MAR 05, 1999 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSLRPE NAME: GMTSLRPE ROUTINE ID: GMTSLRPE GENERAL DESCRIPTION: The Women's Health package requests permission to call the GMTSLRPE routine at the XTRCT line label. This routine returns cytology data extracted from the LAB DATA file (#63) of the Laboratory package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29183431 COMPONENT/ENTRY POINT: XTRCT VARIABLES: LRDFN TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number of a LAB DATA (#63) file entry that identifies the patient. It is not the variable DFN, rather it is the value of +^DPT(DFN,"LR"). VARIABLES: GMTS1 TYPE: Input VARIABLES DESCRIPTION: A reverse FileMan date/time (e.g., 7009695.8955) used as the start of a search of the LAB DATA (#63) file. VARIABLES: GMTS2 TYPE: Input VARIABLES DESCRIPTION: A reverse FileMan date/time (e.g., 7019695.8955) used as the end of a search of the LAB DATA (#63) file. VARIABLES: MAX TYPE: Input VARIABLES DESCRIPTION: An integer value which indicates the maximum number of entries to return. For example, if MAX=10 and more than 10 tests were found in the date/time range, then the 10 most recent test entries will be returned. VARIABLES: TMP("LRCY",$J, TYPE: Output VARIABLES DESCRIPTION: The cytology data for all entries found will be returned in the temporary global ^TMP("LRA",$J). The data layout for that global is: S ^TMP("LRCY",$J,sub1,0)=DATE/TIME SPECIMEN TAKEN^CYTOPATH ACC# S ^TMP("LRCY",$J,sub1,1)="Site/Specimen" literal^REPORT RELEASE DATE/TIME S ^TMP("LRCY",$J,sub1,1,sub2)=Site/Specimen text S ^TMP("LRCY",$J,sub1,"AH",sub2)=Brief Clinical History text S ^TMP("LRCY",$J,sub1,"G",sub2)=Gross Description text S ^TMP("LRCY",$J,sub1,"MI",sub2)=Microscopic exam text S ^TMP("LRCY",$J,sub1,"SR",sub2,0)=Supplementary Report text S ^TMP("LRCY",$J,sub1,"SR",sub2,sub3)=Supplementary Report text S ^TMP("LRCY",$J,sub1,"NDX",sub2)=Cytology Diagnosis SUBSCRIBING PACKAGE: WOMEN'S HEALTH ISC: Hines SUBSCRIBING PACKAGE: MYHEALTHEVET SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 2771 IA #: 2771 DATE CREATED: MAR 05, 1999 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSLRAE NAME: GMTSLRAE ROUTINE ID: GMTSLRAE GENERAL DESCRIPTION: The Women's Health package requests permission to call the GMTSLRAE routine at the XTRCT line label. This routine returns surgical pathology data extracted from the LAB DATA file (#63) of the Laboratory package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29183435 COMPONENT/ENTRY POINT: XTRCT VARIABLES: LRDFN TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number of a LAB DATA (#63) file entry that identifies the patient. It is not the variable DFN, rather it is the value of +^DPT(DFN,"LR"). VARIABLES: GMTS1 TYPE: Input VARIABLES DESCRIPTION: A reverse FileMan date/time (e.g., 7009695.8955) used as the start of a search of the LAB DATA (#63) file. VARIABLES: GMTS2 TYPE: Input VARIABLES DESCRIPTION: A reverse FileMan date/time (e.g., 7019695.8955) used as the end of a search of the LAB DATA (#63) file. VARIABLES: MAX TYPE: Input VARIABLES DESCRIPTION: An integer value which indicates the maximum number of entries to return. For example, if MAX=10 and more than 10 tests were found in the date/time range, then the 10 most recent test entries will be returned. VARIABLES: TMP(LRA,$J) TYPE: Output VARIABLES DESCRIPTION: The surgical pathology data for all entries found will be returned in the temporary global ^TMP("LRA",$J). The data layout for that global is: S ^TMP("LRA",$J,sub1,0)=DATE/TIME SPECIMEN TAKEN^SURGICAL PATH ACC# S ^TMP("LRA",$J,sub1,.1)="Site/Specimen" literal^REPORT RELEASE DATE/TIME S ^TMP("LRA",$J,sub1,.1,sub2)=Site/Specimen text S ^TMP("LRA",$J,sub1,.2)="Brief Clinical HX" literal S ^TMP("LRA",$J,sub1,.2,sub2)=Brief Clinical History text S ^TMP("LRA",$J,sub1,1)="Gross Description" literal S ^TMP("LRA",$J,sub1,1,sub2)=Gross Description text S ^TMP("LRA",$J,sub1,1.1)="Microscopic Exam" literal S ^TMP("LRA",$J,sub1,1.1,sub2)=Microscopic Exam text S ^TMP("LRA",$J,sub1,1.2)="Supplementary Report" literal S ^TMP("LRA",$J,sub1,1.2,sub2)=Supplementary Report text S ^TMP("LRA",$J,sub1,1.2,sub2,sub3)=Supplementary Report text S ^TMP("LRA",$J,sub1,1.3)="Frozen Section" literal S ^TMP("LRA",$J,sub1,1.3,sub2)=Frozen Section text S ^TMP("LRA",$J,sub1,1.4)="Surgical Path Dx" literal S ^TMP("LRA",$J,sub1,1.4,sub2)=Surgical Pathology Diagnosis text SUBSCRIBING PACKAGE: WOMEN'S HEALTH ISC: Hines SUBSCRIBING PACKAGE: MYHEALTHEVET SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 2772 IA #: 2772 DATE CREATED: MAR 05, 1999 CUSTODIAL PACKAGE: WOMEN'S HEALTH CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: WVLRLINK NAME: WVLRLINK ROUTINE ID: WVLRLINK GENERAL DESCRIPTION: The Women's Health (WH) package requests that the Lab package will notify the WH package whenever lab test results are released or changed for a cytology or surgical pathology test. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29183878 COMPONENT/ENTRY POINT: CREATE COMPONENT DESCRIPTION: The Lab package will call this entry point when the results for a cytology or surgical pathology test are released. The WH package will store these values in order to track lab tests performed. Also, the WH package will use the values of LRDFN and LRI as input values in private IAs (#2770 and 2771) to the Health Summary (HS) package to display data from HS components for cytology and surgical pathology. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the PATIENT file (#2) VARIABLES: LRDFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the LAB DATA file (#63) VARIABLES: LRI TYPE: Input VARIABLES DESCRIPTION: The reverse date/time subscript of a LAB DATA file (#63) entry for Cytology or Surgical Pathology. VARIABLES: LRA TYPE: Input VARIABLES DESCRIPTION: The zero node of a Cytology or Surgical Pathology entry in the LAB DATA file (#63). Specifically, the WH package is interested in: Piece #1: DATE/TIME SPECIMEN TAKEN #6: CYTOPATH ACC # or SURGICAL PATH ACC # #7: PHYSICIAN #8: PATIENT LOCATION #15: ORIGINAL RELEASE DATE VARIABLES: LRSS TYPE: Input VARIABLES DESCRIPTION: The two letter value that identifies the type of lab test (e.g., CY or SP). COMPONENT/ENTRY POINT: DELETE COMPONENT DESCRIPTION: The Lab package will call this entry point when the lab results for a cytology or surgical pathology test are not to be viewed by other than lab personnel (e.g., the lab test results are being changed). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the PATIENT file (#2) VARIABLES: LRDFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the LAB DATA file (#63) VARIABLES: LRI TYPE: Input VARIABLES DESCRIPTION: The reverse date/time subscript of a LAB DATA file (#63) entry for Cytology or Surgical Pathology. VARIABLES: LRA TYPE: Input VARIABLES DESCRIPTION: The zero node of a Cytology or Surgical Pathology entry in the LAB DATA file (#63). Specifically, the WH package is interested in: Piece #1: DATE/TIME SPECIMEN TAKEN #6: CYTOPATH ACC # or SURGICAL PATH ACC # #7: PHYSICIAN #8: PATIENT LOCATION #15: ORIGINAL RELEASE DATE VARIABLES: LRSS TYPE: Input VARIABLES DESCRIPTION: The two letter value that identifies the type of lab test (e.g., CY or SP). COMPONENT/ENTRY POINT: MOVE COMPONENT DESCRIPTION: The Lab package will call this entry point when the Move anatomic path accession [LRAPMV] option is used by Lab personnel to move a lab accession from one patient to another patient for a cytology or surgical pathology test. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the PATIENT file (#2) VARIABLES: LRDFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the LAB DATA file (#63) VARIABLES: LRI TYPE: Input VARIABLES DESCRIPTION: The reverse date/time subscript of a LAB DATA file (#63) entry for Cytology or Surgical Pathology. VARIABLES: LRA TYPE: Input VARIABLES DESCRIPTION: The zero node of a Cytology or Surgical Pathology entry in the LAB DATA file (#63). Specifically, the WH package is interested in: Piece #1: DATE/TIME SPECIMEN TAKEN #6: CYTOPATH ACC # or SURGICAL PATH ACC # #7: PHYSICIAN #8: PATIENT LOCATION #15: ORIGINAL RELEASE DATE VARIABLES: LRSS TYPE: Input VARIABLES DESCRIPTION: The two letter value that identifies the type of lab test (e.g., CY or SP). SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas EDITOR: TRAXLER,FRANK NUMBER: 2773 IA #: 2773 FILE NUMBER: 774 GLOBAL ROOT: HLS(774 DATE CREATED: MAR 09, 1999 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2773 ID: HLS(774 GLOBAL REFERENCE: HLS(774,D0, FIELD NUMBER: .01 FIELD NAME: NUMBER LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: HLS(774,D0,'TO',D1, FIELD NUMBER: .01 FIELD NAME: DESTINATION LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: LOGICAL LINK LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: TYPE LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 5 FIELD NAME: CREATION DATE/TIME LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 6 FIELD NAME: ACTIVATION DATE/TIME LOCATION: 0;7 ACCESS: Read w/Fileman GENERAL DESCRIPTION: CIRN Option RG SUBSCRIPT STAT INQ uses a Read with FileMan to file ^HLS(774 (SUBSCRIPTION CONTROL) to do a lookup on a patient. This allows users to identify which sites are currently receiving CIRN patient information. It is display only. STATUS: Active MAIL MESSAGE: 28751819 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2774 IA #: 2774 DATE CREATED: MAR 09, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMXAPIU NAME: INTERACTIVE API ID: XMXAPIU GENERAL DESCRIPTION: These APIs are interactive. Please see the Programmer Manual on the Infrastructure web site for further information about the APIs and how to use them. STATUS: Active MAIL MESSAGE: 29724674 COMPONENT/ENTRY POINT: READ COMPONENT DESCRIPTION: Interactive Read/Manage messages in your mailbox. COMPONENT/ENTRY POINT: READNEW COMPONENT DESCRIPTION: Interactive read new messages in your mailbox. COMPONENT/ENTRY POINT: SEND COMPONENT DESCRIPTION: Interactive send a message. COMPONENT/ENTRY POINT: TOWHOM COMPONENT DESCRIPTION: Interactive address a message. COMPONENT/ENTRY POINT: SUBJ COMPONENT DESCRIPTION: Ask the user what the subject of a message should be. It includes all necessary checking to ensure that the subject conforms to the restrictions in the DD. Usage: D SUBJ^XMXAPIU(.XMSUBJ) VARIABLES: XMSUBJ TYPE: Both VARIABLES DESCRIPTION: If XMSUBJ is set by the calling program, then it is displayed as the default response to the prompt. The response of the user is returned in XMSUBJ. NUMBER: 2777 IA #: 2777 FILE NUMBER: 9.4 GLOBAL ROOT: DIC(9.4, DATE CREATED: MAR 19, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: MODIFY ONCOLOGY PACKAGE ENTRIES ID: DIC(9.4, GENERAL DESCRIPTION: The ONCOLOGY package has two PACKAGE file entries. The correct entry contains in incorrect PREFIX value which causes the KIDS "Required Build" feature to function incorrectly. The incorrect entry contains PATCH APPLICATION HISTORY data which belongs in the correct entry. We would like to 1) modify the PREFIX values of both PACKAGE entries, 2) move the PATCH APPLICATION HISTORY data from the incorrect entry to the correct entry and 3) delete the PATCH APPLICATION HISTORY data from the incorrect entry. These modifications will be achieved via standard FileMan calls. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29229163 SUBSCRIBING PACKAGE: ONCOLOGY ISC: Hines NUMBER: 2778 IA #: 2778 DATE CREATED: MAR 19, 1999 CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RGRSDYN1 NAME: CIRN HL7 DYNAMIC ADDRESSING ID: RGRSDYN1 GENERAL DESCRIPTION: This agreement allows the REGISTRATION protocol, VAFC MFU-TFL CLIENT, to contain the following routing logic: N X S X="RGRSDYN1" X ^%ZOSF("TEST") Q:'$T D EN^RGRSDYN1("VAFC MFU-TFL CLIENT",0) This routing logic builds a dynamic link list of subscribering sites for the patient being processed in the inbound HL7 message. STATUS: Active MAIL MESSAGE: 28829529 COMPONENT/ENTRY POINT: EN(CLIENT,CLASS) COMPONENT DESCRIPTION: This entry point builds an HL7 package dynamic link list for a patient. VARIABLES: CLIENT TYPE: Input VARIABLES DESCRIPTION: (Required) HL7 Client protocol, as it appears in the .01 field of the PROTOCOL (#101) file. Ex. "VAFC MFU-TFL CLIENT" VARIABLES: CLASS TYPE: Input VARIABLES DESCRIPTION: (Optional) 0 - Patient Demographic 1 - (default) Patient Demographic and Clinical 2 - other (locally defined) SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING DETAILS: This is only called from the VistA HL7 package byway of the PROTOCOL (#101) File, ROUTING LOGIC (#774) field. EDITOR: LANDRIE,LARRY EDITOR: REED,DANNY EDITOR: LAZABARA,CINDY F EDITOR: SCOTT,APRIL L NUMBER: 2779 IA #: 2779 DATE CREATED: MAR 22, 1999 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFCUTL1 NAME: DBIA2779 ID: VAFCUTL1 GENERAL DESCRIPTION: This function will indentify that a given patient is either a dead patient, test patient, an employee, a non-veteran, or a Psuedo patient. It will return a 1 if it meets the given parameter or a 0 if it does not meet the given parameter. STATUS: Active MAIL MESSAGE: 29184267 COMPONENT/ENTRY POINT: SEND2 COMPONENT DESCRIPTION: Will identify that a given patient is either a dead patient, test patient, an employee, a non-veteran, or a Psuedo patient. VARIABLES: DFN,PARAMS TYPE: Input VARIABLES DESCRIPTION: DFN - IEN of PATIENT (#2) file PARAMS - "D"ead Patient "T"est Patient "E"mployee "V"eteran (Non) "P"suedo VARIABLES: 0 or 1 TYPE: Output VARIABLES DESCRIPTION: The function will return a 1 if the patient is a Dead patient, Test patient, an Employee, a Non-Veteran or psuedo. Otherwise, the function will return a 0. COMPONENT/ENTRY POINT: $$SEND2 COMPONENT DESCRIPTION: This function screens out certain types of patients. VARIABLES: $$SEND2 TYPE: Output VARIABLES DESCRIPTION: if the PARAM variable contains: "D", the function will return a 1 if the patient is a Dead patient. "T", the ...................... 1 ................. a Test patient "E", the ...................... 1 ................. an Employee. "V", the ...................... 1 ................. a Non-Veteran. "P", the ...................... 1 ................. Psuedo otherwise the function returns 0 VARIABLES: PARAMS TYPE: Input VARIABLES DESCRIPTION: "D" - Dead patient. "T" - Test patient "E" - an Employee. "V" - a Non-Veteran. "P" - Psuedo VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN from PATIENT (#2) file SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA EDITOR: CHESNEY,CHRISTINE M EDITOR: LAZABARA,CINDY F NUMBER: 2780 IA #: 2780 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: MAR 23, 1999 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2780 ID: DPT( CREATOR: LEYVA,KATHRYN GLOBAL REFERENCE: DPT(D0,.31) FIELD NUMBER: .3192 FIELD NAME: COVERED BY HEALTH INSURANCE? LOCATION: .31;11 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: DPT(D0,.312,D1,0) FIELD NUMBER: .01 FIELD NAME: INSURANCE TYPE LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1 FIELD NAME: *SUBSCRIBER ID LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: Note: IB*2*497 - replaced by SUBSCRIBER ID field (7.02) FIELD NUMBER: 2 FIELD NAME: GROUP NUMBER LOCATION: 0;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: 3 FIELD NAME: INSURANCE EXPIRATION DATE LOCATION: 0;4 ACCESS: Both R/W w/Fileman FIELD NUMBER: 6 FIELD NAME: WHOSE INSURANCE LOCATION: 0;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: 7 FIELD NAME: RENEWAL DATE LOCATION: 0;7 ACCESS: Both R/W w/Fileman FIELD NUMBER: 8 FIELD NAME: EFFECTIVE DATE OF POLICY LOCATION: 0;8 ACCESS: Both R/W w/Fileman FIELD NUMBER: 16 FIELD NAME: PT. RELATIONSHIP TO INSURED LOCATION: 0;16 ACCESS: Both R/W w/Fileman FIELD NUMBER: 17 FIELD NAME: *NAME OF INSURED LOCATION: 0;17 ACCESS: Read w/Fileman FIELD DESCRIPTION: Note: IB*2*497 - replaced by NAME OF INSURED field (7.01) GLOBAL DESCRIPTION: This agreement also allows PDX to $O through the insurance multiple. GLOBAL REFERENCE: DPT(D0,.312,D1,7) FIELD NUMBER: 7.01 FIELD NAME: NAME OF INSURED LOCATION: 7;1 ACCESS: Read w/Fileman FIELD NUMBER: 7.02 FIELD NAME: SUBSCRIBER ID LOCATION: 7;2 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: Integrated Billing allows PDX to read and write several patient insurance data elements to support the exchange of insurance information between facilities. Update: IB*2*497 increased the length of the SUBSCRIBER ID field and the NAME OF INSURED field to support the EDI New Standards and Operating Rules for VHA providers. This required length increase made it necessary to move the location of these 2 fields to new Data Dictionary nodes in the INSURANCE TYPE sub-file. To support this implementation, all subscribers to this ICR will need to make the necessary changes in their applications to reference the new fields and remove the references to the old fields. When all subscribers have implemented the use of the new fields, the old fields will be deleted with IB*2*518. New fields are noted in the field list detail of this ICR. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29284513 SUBSCRIBING PACKAGE: PATIENT DATA EXCHANGE ISC: Oakland DBA Comments: 11/18/13-MC: DEACATIVATED FOR EDITING BY IB*2*497 PROJECT TEAM 2/21/14-MM: Activated ICR #2780 for IB*2*497. This patch added new fields with longer lengths and marked the original fields for deletion. Currently the old and new fields will contain the same data until IB*2*518 is released and subscribing applications have remediated their applications to work with the new fields. DATE ACTIVATED: FEB 21, 2014 DATE/TIME EDITED: FEB 21, 2014@18:08 ACTION: APPROVED AT THE REQUEST OF: JUTZI,BILL NUMBER: 2781 IA #: 2781 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: MAR 23, 1999 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2781 ID: DPT( GLOBAL REFERENCE: DPT(D0,.31) FIELD NUMBER: .3192 FIELD NAME: COVERED BY HEALTH INSURANCE? LOCATION: .31;11 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This agreement allows certain applications to directly read the field 'Covered by Health Insurance?' for the purpose of display only. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29284519 SUBSCRIBING PACKAGE: SCHEDULING ISC: Albany SUBSCRIBING PACKAGE: CLINICAL MONITORING SYSTEM ISC: Hines NUMBER: 2782 IA #: 2782 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: MAR 23, 1999 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2782 ID: DPT( CREATOR: LEYVA,KATHRYN GLOBAL REFERENCE: DPT(D0,.312,D1,0) FIELD NUMBER: .01 FIELD NAME: INSURANCE TYPE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: *SUBSCRIBER ID LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Note: IB*2*497 - replaced by SUBSCRIBER ID field (7.02) FIELD NUMBER: 2 FIELD NAME: GROUP NUMBER LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: INSURANCE EXPIRATION DATE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: This agreement also allows Mental Health to $O through the insurance multiple. GLOBAL REFERENCE: DPT(D0,.312,D1,7) FIELD NUMBER: 7.02 FIELD NAME: SUBSCRIBER ID LOCATION: 7;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This agreement allows Mental Health to directly read specific patient insurance fields for the purpose of display only. Update: IB*2*497 increased the length of the SUBSCRIBER ID field to support the EDI New Standards and Operating Rules for VHA providers. This required length increase made it necessary to move the location of this field to a new Data Dictionary node in the INSURANCE TYPE sub-file. To support this implementation, all subscribers to this ICR will need to make the necessary changes in their applications to reference the new field and remove the reference to the old field. When all subscribers have implemented the use of the new field, the old field will be deleted with IB*2*518. The new field is noted in the field list detail of this ICR. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29284526 SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas DBA Comments: 11/18/13-MC: DEACTIVATED FOR EDITING BY IB*2*497 PROJECT TEAM 2/21/14-MM: Activated ICR #2782 for IB*2*497. This patch added new fields with longer lengths and marked the original fields for deletion. Currently the old and new fields will contain the same data until IB*2*518 is released and subscribing applications have remediated their applications to work with the new fields. DATE ACTIVATED: FEB 21, 2014 DATE/TIME EDITED: FEB 21, 2014@17:23 ACTION: APPROVED AT THE REQUEST OF: JUTZI,BILL NUMBER: 2784 IA #: 2784 DATE CREATED: MAR 23, 1999 CUSTODIAL PACKAGE: REGISTRATION USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFCPTED NAME: Patient File Edit ID: VAFCPTED CREATOR: SCHLEHUBER,CAMERON GENERAL DESCRIPTION: This private routine agreement allows packages to update certain PATIENT (#2) file fields identified by each subscribing package. STATUS: Active MAIL MESSAGE: 29096430 COMPONENT/ENTRY POINT: EDIT(DFN,ARRAY,STRNGDR) COMPONENT DESCRIPTION: This routine is used to edit an existing patient. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN - IEN in the PATIENT (#2) file VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: Array value which contains fields to be edited. The value should be passed as shown, "ARRAY(2)" and the array should be in the following form: Ex. ARRAY(.111)="123 STREET" or ARRAY(2,.111)="123... VARIABLES: STRNGDR TYPE: Input VARIABLES DESCRIPTION: This is a string of PATIENT (#2) file fields separated by semicolons which match the fields passed in the ARRAY variable. SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING DETAILS: CLINICAL INFO RESOURCE NETWORK (RG*) will only pass the following fields to be edited: NAME (#.01), SEX (#.02), DATE OF BIRTH (#.03), SOCIAL SECURITY NUMBER (#.09), ALIAS (#1), MOTHER'S MAIDEN NAME (#.2403), PSEUDO SSN REASON (#.0906), and SSN VERIFICATION STATUS (#.0907). SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA SUBSCRIBING DETAILS: MASTER PATIENT INDEX VISTA (MPIF*) will only pass the following fields to be edited: NAME (#.01), SEX (#.02), DATE OF BIRTH (#.03), SOCIAL SECURITY NUMBER (#.09), ALIAS (#1), MOTHER'S MAIDEN NAME (#.2403), PSEUDO SSN REASON (#.0906), and SSN VERIFICATION STATUS (#.0907). DATE ACTIVATED: JUL 16, 2007 DATE/TIME EDITED: JUL 16, 2007@08:06 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: DAVIS,PAULETTE DATE/TIME EDITED: JUL 16, 2007@10:21 ACTION: APPROVED AT THE REQUEST OF: DAVIS,PAULETTE WITH CONCURRENCE OF: FAIN,ZACHARY NUMBER: 2786 IA #: 2786 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: MAR 24, 1999 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2786 ID: DPT( GLOBAL REFERENCE: DPT(D1,.312,D0,0) FIELD NUMBER: .01 FIELD NAME: INSURANCE TYPE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: This agreement also allows DSS Extracts to $O through the insurance multiple. GENERAL DESCRIPTION: This agreement allows the DSS EXTRACTS application to directly read specific patient insurance information for extraction by VISN 19. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29284529 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany NUMBER: 2787 IA #: 2787 FILE NUMBER: 2 GLOBAL ROOT: DPT DATE CREATED: MAR 24, 1999 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2787 ID: DPT GENERAL DESCRIPTION: In order to calculate the total number of in-patient deaths in a given time period, the Laboratory package must utilize the DATE OF DEATH cross-reference ^DPT("AEXP1" of the PATIENT file (#2). This is a cross-reference of the DATE OF DEATH field (#.351). This a read-only usage of this file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29309479 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 2788 IA #: 2788 DATE CREATED: MAR 25, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XQALBUTL NAME: XQALBUTL ID: XQALBUTL GENERAL DESCRIPTION: This DBIA lists and defines supported references within the routine XQALBUTL. AHISTORY(XQAID,ROOT) - Returns info on alert XQAID in ROOT in global format $$PENDING(XQAID,XQAUSER) - Indicates whether alert XQAID is pending for user XQAUSER (1=YES, 0=NO). $$PKGPEND(XQAUSER,XQAPKG) - Returns 1 if the user indicated by XQAUSER has any pending alerts in which the first ';'-piece of XQAID contain the package identifier indicated by XQAPKG. ALERTDAT(XQAID,ROOT) - Returns info on alert XQAID in ROOT by field and values (if ROOT is not specified, returned in local variable XQALERTD) USERLIST(XQAID,ROOT) - Returns list of users who received alert XQAID in array under ROOT (if ROOT is not specified, returned in local variable XQAUSRS) USERDATA(XQAID,XQAUSER,ROOT) - Returns info on user XQAUSER for alert XQAID in ROOT by field and values (if ROOT is not specified, returned in local variable XQALUSER). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29629406 KEYWORDS: XQALBUTL KEYWORDS: ALERTS COMPONENT/ENTRY POINT: AHISTORY COMPONENT DESCRIPTION: Returns information from the alert tracking file for alert with XQAID as its alert ID. The data is returned desendent from the closed root passed in ROOT. Usually, XQAID will be known based on alert processing. The following example illustrates the use of this call and the format of the data returned. S XQAID="NO-ID;20;2990212.11294719" D AHISTORY^XQALBUTL(XQAID,"XXXROOT") ZW XXXROOT XXXROOT(0)=NO-ID;20;2990212.11294719^2990212.112947^NO-ID^^20 XXXROOT(1)=TEST MESSAGE (ROUTINE) 20^^^XM XXXROOT(20,0)=^8992.11^20^1 XXXROOT(20,1,0)=20^2990212.112954^2990212.145609^2990212.145621^2990212.145621 XXXROOT(20,"B",20,1)= This is in the basic structure of the nodes taken from the global for this entry, which can be seen from a global map view of file 8992.1 ^XTV(8992.1,D0,0)= (#.01) NAME [1F] ^ (#.02) DATE CREATED [2D] ^ (#.03) PKG ==>ID [3F] ^ (#.04) PATIENT [4P] ^ (#.05) GENERATED BY [5P] ^ ==>(#.06) GENERATED WHILE QUEUED [6S] ^ (#.07) STATUS [7S] ^ ==>(#.08) RETENTION DATE [8D] ^ ^XTV(8992.1,D0,1)= (#1.01) DISPLAY TEXT [1F] ^ (#1.02) OPTION FOR PROCESSING ==>[2F] ^ (#1.03) ROUTINE TAG [3F] ^ (#1.04) ROUTINE FOR ==>PROCESSING [4F] ^ ^XTV(8992.1,D0,2)= (#2) DATA FOR PROCESSING [E1,245F] ^ ^XTV(8992.1,D0,20,0)=^8992.11PA^^ (#20) RECIPIENT ^XTV(8992.1,D0,20,D1,0)= (#.01) RECIPIENT [1P] ^ (#.02) ALERT FIRST DISPLAYED ==>[2D] ^ (#.03) FIRST SELECTED ALERT [3D] ^ (#.04) ==>PROCESSED ALERT [4D] ^ (#.05) DELETED ON [5D] ^ ==>(#.06) AUTO DELETED [6D] ^ (#.07) FORWARDED BY [7P] ==>^ (#.08) DATE/TIME FORWARDED [8D] ^ (#.09) DELETED ==>BY USER [9P] ^ A set of newer entry points are available for returning this information in a more user (developer) friendly form which may be more desirable than this format. ALERTDAT - returns basic information about the alert USERLIST - returns the list of users who have received the alert USERDATA - returns information about one user with respect to the specified alert VARIABLES: XQAID TYPE: Input VARIABLES DESCRIPTION: This is the value XQAID which is the alert identifier. It is passed to the routine or option which is run when the alert is selected. It can also be obtained from a listing of all of the XQAIDs for a specified user and/or patient. VARIABLES: ROOT TYPE: Input VARIABLES DESCRIPTION: This argument is a closed reference to a local or global root. The information associated with the desired entry in the alert tracking file is returned descendent from the specified root. The data returned reflects the global structure of the Alert Tracking file. A more user (developer) friendly call would be ALERTDAT described within this same unit which returns the data in an array with the field numbers and names as the subscripts and the internal and external (if different) values as the value. COMPONENT/ENTRY POINT: PENDING COMPONENT DESCRIPTION: Returns whether the user specified has the alert indicated by the argument XQAID pending. (1=YES, 0=NO). Usage is as $$PENDING^XQALBUTL(XQAUSER,XQAID) S XQAID="NO-ID;20;2990212.11294719" W $$PENDING^XQALBUTL(20,XQAID) 0 <===== Not pending S XQAID="NO-ID;20;2990212.15540723" W $$PENDING^XQALBUTL(20,XQAID) 1 <===== Pending VARIABLES: XQAUSER TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number in file 200 (DUZ value) for the desired user. VARIABLES: XQAID TYPE: Input VARIABLES DESCRIPTION: This is the value XQAID which is the alert identifier. It is passed to the routine or option which is run when the alert is selected. It can also be obtained from a listing of all of the XQAIDs for a specified user and/or patient. COMPONENT/ENTRY POINT: ALERTDAT COMPONENT DESCRIPTION: Returns information from alert tracking file for alert with XQAID in array specified by ROOT. If ROOT is not specified, then the data is returned in an array XQALERTD. If the specified alert is not present, the array root is returned with a NULL value. Usage: D ALERTDAT^XQALBUTL(XQAID,ROOT) S XQAID="NO-ID;20;2990212.11294719" D ALERTDAT^XQALBUTL(XQAID,$NA(^TMP($J,"A"))) D ^%G Global ^TMP($J,"A" TMP($J,"A" ^TMP(539056198,"A",.01) = NO-ID;20;2990212.11294719 ^TMP(539056198,"A",.01,"NAME") = ^TMP(539056198,"A",.02) = 2990212.112947^FEB 12, 1999@11:29:47 ^TMP(539056198,"A",.02,"DATE CREATED") = ^TMP(539056198,"A",.03) = NO-ID ^TMP(539056198,"A",.03,"PKG ID") = ^TMP(539056198,"A",.04) = ^TMP(539056198,"A",.04,"PATIENT") = ^TMP(539056198,"A",.05) = 20^USER,XXX ^TMP(539056198,"A",.05,"GENERATED BY") = ^TMP(539056198,"A",.06) = ^TMP(539056198,"A",.06,"GENERATED WHILE QUEUED") = ^TMP(539056198,"A",.07) = ^TMP(539056198,"A",.07,"STATUS") = ^TMP(539056198,"A",.08) = ^TMP(539056198,"A",.08,"RETENTION DATE") = ^TMP(539056198,"A",1.01) = TEST MESSAGE (ROUTINE) 20 ^TMP(539056198,"A",1.01,"DISPLAY TEXT") = ^TMP(539056198,"A",1.02) = ^TMP(539056198,"A",1.02,"OPTION FOR PROCESSING") = ^TMP(539056198,"A",1.03) = ^TMP(539056198,"A",1.03,"ROUTINE TAG") = ^TMP(539056198,"A",1.04) = XM ^TMP(539056198,"A",1.04,"ROUTINE FOR PROCESSING") = ^TMP(539056198,"A",2) = ^TMP(539056198,"A",2,"DATA FOR PROCESSING") = The data elements at the top level of the Activity Tracking file are returned subscripted by the field numbers. This subscript is sufficient to obtain the data. The values are shown as internal^external if the internal and external forms are different. The next subscript after the field number will provide the field names if they are desired. VARIABLES: XQAID TYPE: Input VARIABLES DESCRIPTION: This is the value XQAID which is the alert identifier. It is passed to the routine or option which is run when the alert is selected. It can also be obtained from a listing of all of the XQAIDs for a specified user and/or patient. VARIABLES: ROOT TYPE: Input VARIABLES DESCRIPTION: This argument is a closed reference to a local or global root. The desired information is returned descendent from the specified root. COMPONENT/ENTRY POINT: USERLIST COMPONENT DESCRIPTION: Returns recipients of alert with ID of XQAID from alert tracking file in the array specified by ROOT. If ROOT is not specified, then the data is returned in the array XQALUSRS. If the specified alert is not present, the array root is returned with a NULL value. Usage: D USERLIST^XQALBUTL(XQAID,ROOT) or Usage: D USERLIST^XQALBUTL(XQAID) (DATA RETURNED IN XQALUSRS) D USERLIST^XQALBUTL(XQAID) ZW XQALUSRS XQALUSRS(1)=20^USER,XXX VARIABLES: XQAID TYPE: Input VARIABLES DESCRIPTION: This is the value XQAID which is the alert identifier. It is passed to the routine or option which is run when the alert is selected. It can also be obtained from a listing of all of the XQAIDs for a specified user and/or patient. VARIABLES: ROOT TYPE: Input VARIABLES DESCRIPTION: This argument is a closed reference to a local or global root. The desired information is returned descendent from the specified root. If this value is not specified, the data will be returned in the local array XQALUSRS. COMPONENT/ENTRY POINT: USERDATA COMPONENT DESCRIPTION: Returns information from alert tracking file related to alert with ID of XQAID for user specified by XQAUSER. Data is returned descendent from the closed root specified by ROOT (or if ROOT is not passed, under the array XQALUSER). If the specified alert is not present, the array root is returned with a NULL value. Usage: D USERDATA^XQALBUTL(XQAID,XQAUSER,ROOT) or Usage: D USERDATA^XQALBUTL(XQAID,XQAUSER) (data returned in local array XQALUSER) D USERDATA^XQALBUTL(XQAID,20,"XXX") ZW XXX XXX(.01)=20^USER,XXX XXX(.01,"RECIPIENT")= XXX(.02)=2990212.112954^FEB 12, 1999@11:29:54 XXX(.02,"ALERT FIRST DISPLAYED")= XXX(.03)=2990212.145609^FEB 12, 1999@14:56:09 XXX(.03,"FIRST SELECTED ALERT")= XXX(.04)=2990212.145621^FEB 12, 1999@14:56:21 XXX(.04,"PROCESSED ALERT")= XXX(.05)=2990212.145621^FEB 12, 1999@14:56:21 XXX(.05,"DELETED ON")= XXX(.06)= XXX(.06,"AUTO DELETED")= XXX(.07)= XXX(.07,"FORWARDED BY")= XXX(.08)= XXX(.08,"DATE/TIME FORWARDED")= XXX(.09)= XXX(.09,"DELETED BY USER")= VARIABLES: XQAID TYPE: Input VARIABLES DESCRIPTION: This is the value XQAID which is the alert identifier. It is passed to the routine or option which is run when the alert is selected. It can also be obtained from a listing of all of the XQAIDs for a specified user and/or patient. VARIABLES: XQAUSER TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number in file 200 (DUZ value) for the desired user. VARIABLES: ROOT TYPE: Input VARIABLES DESCRIPTION: This argument is a closed reference to a local or global root. The desired information is returned descendent from the specified root. If this value is not specified, the data will be returned in the local array XQALUSER COMPONENT/ENTRY POINT: PKGPEND COMPONENT DESCRIPTION: Returns whether the user specified has an alert with XQAID containing the first ';'-piece (PACKAGE identifier) indicated by the argument XQAPKG pending. (1=YES, 0=NO). If a value of 1 is returned, it indicates one or MORE alerts pending containing the specified package identifier. The package identifier used can be a complete package identifier (e.g., XU-TSK) or a more general part (e.g., XU) to find users with any XU package alert. Usage is as $$PKGPEND^XQALBUTL(XQAUSER,XQAPKG) S XQAPKG="XU" W $$PKGPEND^XQALBUTL(20,XQAPKG) 0 <===== Not pending S XQAPKG="XU" W $$PKGPEND^XQALBUTL(20,XQAPKG) 1 <===== Pending (one or more) VARIABLES: XQAUSER TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number in file 200 (DUZ value) for the desired user. VARIABLES: XQAPKG TYPE: Input VARIABLES DESCRIPTION: This variable is the package identifier portion of the alert identifier (XQAID). It is a textual identifier for the package which created the alert and is the first ';'-piece of the XQAID. It can be used in this context to determine whether the user specified by XQAUSER has any alerts pending containing the specified package identifier. The return value of one indicates one or more pending alerts for the user containing the specified package string in the package part of the XQAID. NUMBER: 2789 IA #: 2789 DATE CREATED: MAR 25, 1999 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSSLOCK NAME: DBIA2789 ID: PSSLOCK GENERAL DESCRIPTION: This is the common lock routine for patient locks in Inpatient Medications and Outpatient pharmacy. It also contains the entry points for single order locks between Inpatient/Outpatient and Computerized Patient Record System (CPRS). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29863139 COMPONENT/ENTRY POINT: $$L COMPONENT DESCRIPTION: Pharmacy patient lock entry point. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient internal entry number. VARIABLES: DIS TYPE: Input VARIABLES DESCRIPTION: This variable controls the printing of the unsuccessful lock message. A value of '1' will display the message of who has the patient locked. A value of '0' will cause the message to not be printed. VARIABLES: $T TYPE: Output VARIABLES DESCRIPTION: If the patient was successfully locked, the value of "1" will be returned. If the patient is already locked by another user, the value of "0^User Name^Date/time user locked patient (external form). COMPONENT/ENTRY POINT: UL COMPONENT DESCRIPTION: Pharmacy patient unlock entry point. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient internal entry number. COMPONENT/ENTRY POINT: LS COMPONENT DESCRIPTION: Inpatient Medications single order lock entry point. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient internal entry number. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Inpatient order number. COMPONENT/ENTRY POINT: UNL COMPONENT DESCRIPTION: Inpatient Medications single order Unlock entry point. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient internal entry number. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Inpatient order number. COMPONENT/ENTRY POINT: PSOL COMPONENT DESCRIPTION: Outpatient Pharmacy single order lock entry point. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Outpatient order number. VARIABLES: PSOMSG TYPE: Output VARIABLES DESCRIPTION: Returned as 1 for successful lock, 0 for non-successful lock. COMPONENT/ENTRY POINT: PSOUL COMPONENT DESCRIPTION: Outpatient Pharmacy single order unlock entry point. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Outpatient order number. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: VENDOR - AUDIOFAX, INC. SUBSCRIBING PACKAGE: CMOP ISC: Birmingham SUBSCRIBING PACKAGE: VENDOR - TECHPRO SYSTEMS INC NUMBER: 2790 IA #: 2790 DATE CREATED: MAR 25, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XQALSURO NAME: XQALSURO ID: XQALSURO GENERAL DESCRIPTION: This DBIA describes supported references in the routine XQALSURO which may be used to obtain information on, set, or remove a surrogate for alerts for a user. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29629426 KEYWORDS: XQALSURO KEYWORDS: ALERTS KEYWORDS: SURROGATE COMPONENT/ENTRY POINT: CURRSURO COMPONENT DESCRIPTION: This reference is used to obtain the current surrogate for alerts (if any for the user with DUZ specified by XQAUSER. Usage is $$CURRSURO^XQALSURO(XQAUSER) The value returned is the DUZ of the surrogate or -1 if there is no surrogate specified. VARIABLES: XQAUSER TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number in file 200 (DUZ value) for the user that the surrogate inquiry is for. COMPONENT/ENTRY POINT: SETSURO COMPONENT DESCRIPTION: This entry point is used to establish (or replace) a surrogate for the user specified by XQAUSER. The Surrogate is specified by passing the value of DUZ in the variable XQALSURO. XQALSTRT is an optional date/time for the surrogate to become active. If XQALSTRT is not specified, the surrogate becomes active immediately. XQALEND is an optional date/time when the surrogate would be removed. If XQALEND is not specified, the surrogate will remain active until removed. During a period with an active surrogate, all alerts for the user (XQAUSER) are directed towards the surrogate (XQALSURO). VARIABLES: XQAUSER TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number in file 200 (DUZ value) for the user that the surrogate is to be set for. VARIABLES: XQALSURO TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number in file 200 for the NEW PERSON entry who is to act as surrogate and receive the alerts instead of the user XQAUSER. VARIABLES: XQALSTRT TYPE: Input VARIABLES DESCRIPTION: This is an optional date-time value for when the surrogate activity is to start, if this value is not specified, then the surrogate will become active at the time it is set. VARIABLES: XQALEND TYPE: Input VARIABLES DESCRIPTION: This is an optional date-time value for when the surrogate activity is to stop. When an alert is sent that is after the specified date-time, the surrogate will be removed and alerts will be sent to the user specified instead of the surrogate. If this value is not specified, the surrogate will remain active until the removed or another surrogate specified. COMPONENT/ENTRY POINT: REMVSURO COMPONENT DESCRIPTION: This entry point is used to remove any surrogates for alerts for the specified user. VARIABLES: XQAUSER TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number in file 200 (DUZ value) for the desired user. COMPONENT/ENTRY POINT: ACTVSURO COMPONENT DESCRIPTION: This entry point provides a method to determine who is currently the active recipient for a specified user. This may be the DUZ of the user, or the DUZ of a surrogate designated for the user, or if the user is no longer an active user, a value of -1. Usage is $$ACTVSURO^XQALSURO(XQAUSER) VARIABLES: XQAUSER TYPE: Input VARIABLES DESCRIPTION: This is the DUZ value of the user for whom the currently active alert recipient is desired. EDITOR: IVEY,JOEL NUMBER: 2795 IA #: 2795 FILE NUMBER: 404.51 GLOBAL ROOT: SCTM(404.51 DATE CREATED: APR 23, 1999 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2795 ID: SCTM(404.51 GLOBAL REFERENCE: SCTM(404.51, FIELD NUMBER: .07 FIELD NAME: INSTITUTION ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: SCTM(404.51,"AINST", GLOBAL DESCRIPTION: Cross Reference by Institution GENERAL DESCRIPTION: The Clinical Reminder Package would like to reference the following file directly : TEAM #404.51 - Determine team's institution As corresponding APIs are planned, this IA will be in effect until the appropriate APIs are released. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29446887 KEYWORDS: TEAM INSTITUTION SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 2796 IA #: 2796 DATE CREATED: APR 06, 1999 CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RGHLLOG NAME: RGHLLOG line Tags ID: RGHLLOG GENERAL DESCRIPTION: MPIF is requesting to utilize entry piotns EXC, START and STOP of RGHLLOG to take advantage of the CIRN Exception Handling. STATUS: Active MAIL MESSAGE: 29349070 COMPONENT/ENTRY POINT: EXC COMPONENT DESCRIPTION: EXC^RGHLLOG(RGEXC,RGERR) would be called to log the exception type of RGEXC with a textual message included in RGERR. RGEXC is the .01 of the exception being logged. MPIF will only pass .01s that are in the 200-299 number range. VARIABLES: RGEXC TYPE: Input VARIABLES DESCRIPTION: RGEXC is the .01 NUMBER from the CIRN HL7 EXCEPTION TYPE FILE for the exception you are attempting to log. VARIABLES: RGERR TYPE: Input VARIABLES DESCRIPTION: RGERR is the text message to be included in the Exception message generated. COMPONENT/ENTRY POINT: START COMPONENT DESCRIPTION: START^RGHLLOG(RGMSG,RGDC,RGPARAM) which allow the exceptions to be logged for a particular HL7 message that is being processed. VARIABLES: RGMSG TYPE: Input VARIABLES DESCRIPTION: RGMSG - is the HL7 message number of the message being processed, This can be 0 also. VARIABLES: RGDC TYPE: Input VARIABLES DESCRIPTION: RGDC is used to update the COUNT field in the file. MPI will not be utilizing this field, but instead allow the counting to occur within RGHLLOG functionality. VARIABLES: RGPARAM TYPE: Input VARIABLES DESCRIPTION: RGPARAM - this varibale holds the name of the routine that would be used to reprocess the message. MPI will not be utilizing this functionality. COMPONENT/ENTRY POINT: STOP COMPONENT DESCRIPTION: STOP^RGHLLOG(RGQUIT) to stop exceptions being logged for a HL7 message specified in RGQUIT. VARIABLES: RGQUIT TYPE: Input VARIABLES DESCRIPTION: RGQUIT is the HL7 message number being processed, that was specified when START^RGHLLOG was called. This can be null or 0 also. SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: TOOLKIT EDITOR: CHESNEY,CHRISTINE M NUMBER: 2801 IA #: 2801 DATE CREATED: APR 16, 1999 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCEDIT NAME: Notification/Alert Follow-up Access to GMRCEDIT ID: GMRCEDIT GENERAL DESCRIPTION: Allows subscribing package(s) access into the following routine for Consult/Request Tracking notification/alert follow-up actions: EN^GMRCEDIT STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29404491 KEYWORDS: ALERT KEYWORDS: NOTIFICATION COMPONENT/ENTRY POINT: EN VARIABLES: NXQADATA TYPE: Input VARIABLES DESCRIPTION: NXQADATA is the Consult/Request number. VARIABLES: XQAID TYPE: Input VARIABLES DESCRIPTION: XQAID is the alert identifier in the form: OR,,;; SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2802 IA #: 2802 DATE CREATED: APR 16, 1999 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCALRT NAME: Notification/Alert Follow-up Access to GMRCALRT ID: GMRCALRT GENERAL DESCRIPTION: Allows subscribing package(s) access into the following routine for Consult/Request Tracking notification/alert follow-up actions: EN^GMRCALRT STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29404491 KEYWORDS: ALERT KEYWORDS: NOTIFICATION COMPONENT/ENTRY POINT: EN VARIABLES: NXQADATA TYPE: Input VARIABLES DESCRIPTION: NXQADATA is the Consult/Request number. VARIABLES: XQAID TYPE: Input VARIABLES DESCRIPTION: XQAID is the alert identifier in the form: OR,,;; SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2804 IA #: 2804 FILE NUMBER: 44 GLOBAL ROOT: SC( DATE CREATED: DEC 21, 2004 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2804 ID: SC( GLOBAL REFERENCE: SC(DO,0 FIELD NUMBER: 31 FIELD NAME: CLINIC GROUP LOCATION: 31 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 8 FIELD NAME: STOP CODE NUMBER LOCATION: 7 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Clinical Reminder Package would like to reference the HOSPITAL LOCATION file #44 directly to determine the CLINIC GROUP and STOP CODE NUMBER for a location and all patients with APPOINTMENTS at a clinic on a given date. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29432831 KEYWORDS: CLINIC GROUP KEYWORDS: STOP CODE KEYWORDS: APPOINTMENT SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 2805 IA #: 2805 FILE NUMBER: 59.6 GLOBAL ROOT: PS(59.6, DATE CREATED: APR 28, 1999 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2805 ID: PS(59.6, GLOBAL REFERENCE: PS(59.6,D0,0) FIELD NUMBER: .03 FIELD NAME: DAYS UNTIL STOP DATE/TIME LOCATION: 0;3 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Pharmacy Benefits Management retrieves a data field from FILE: INPATIENT WARD PARAMETERS GLOBAL: ^PS(59.6, FILE #: 59.6 FIELD .03 DAYS UNTIL STOP DATE/TIME STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29440333 KEYWORDS: PBM KEYWORDS: 59.6 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 2806 IA #: 2806 DATE CREATED: APR 21, 1999 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RAO7PC2 NAME: RAD/NUC MED PATIENT PROCEDURE STATUS ID: RAO7PC2 GENERAL DESCRIPTION: CLIN^RAO7PC2 can be used to return information on the most recent date that a list of procedures was completed for a given patient, and if the procedure is currently in progress the appropriate date. Information is also returned if a procedure was cancelled or if there is no record of the procedure for the patient. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29445659 COMPONENT/ENTRY POINT: CLIN COMPONENT DESCRIPTION: CLIN^RAO7PC2(RADFN,.PROCLIST) Input: RADFN = ien of patient in the Rad/Nuc Med Patient File #70 PROCLIST = list of iens of procedures in the Rad/Nuc Med Procedures File #71. This list is delimited by '^'. Output: ^TMP($J,"RADPROC",patient ien,procedure ien,order)= Date/Time^Status^Provider Subscripts ---------- patient ien: same as RADFN input variable procedure ien: an individual ien taken from PROCLIST input variable order: free-text, either "NONE", "CANCELLED", "IN PROGRESS" or "COMPLETE". If the procedure has never been applied to the patient identified by RADFN then an order of NONE will be returned. There will be no other nodes for this procedure. If the procedure has ever been cancelled or completed or is currently in progress then "CANCELLED", "COMPLETED" and "IN PROGRESS" nodes will exist respectively. An order of CANCELLED is returned if EXAM STATUS=0. An order of COMPLETE is returned is EXAM STATUS=9. All other EXAM STATUS values result in an order of "IN PROGRESS". EXAM STATUS is taken from the multiple file #70.03 Array Values ------------ Date/Time: the date and time derived from EXAM DATE on the Registered Exams multiple of the Rad/Nuc Med Patient File #70.02. It is held in FileMan date/time format. e.g. 2990421.1422 Status: derived from the EXAM STATUS on Examinations multiple of the Rad/Nuc Med Patient file #70.03 It is stored as the description taken from STATUS on the Examination Status file #72. Provider: derived from either PRIMARY INTERPRETING RESIDENT or PRIMARY INTERPRETING STAFF on the Examinations multiple of the Rad/Nuc Med Patient file #70.03. PRIMARY INTERPRETING RESIDENT is returned only if no STAFF exists. It is stored as the description taken from NAME on the New Person File #200. Null is returned if the order is "NONE" as there is no information to hold. VARIABLES: RADFN TYPE: Input VARIABLES DESCRIPTION: RADFN = Internal entry number (ien) of the patient in the Rad/Nuc Med Patient file #70. (Note: this is the same ien as used in the Patient file #2. File 70 is DINUMED to file 2. RADFN is also known as the patient ien. VARIABLES: PROCLIST TYPE: Input VARIABLES DESCRIPTION: PROCLIST = List of internal entry numbers (iens) of procedures on the Rad/Nuc Med Procedures file #71. The list is delimited by the '^' character. SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City EDITOR: CEBELINSKI,GREGORY EDITOR: TAYLOR,CAMERON NUMBER: 2807 IA #: 2807 FILE NUMBER: 1 GLOBAL ROOT: DD( DATE CREATED: APR 25, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR sets ID WRITE node ID: DD( GLOBAL REFERENCE: DD(fn,0,'ID','WRITE') GLOBAL DESCRIPTION: Allows hard setting of node for file or subfile. GENERAL DESCRIPTION: This DBIA documents hard setting of the 'ID','WRITE' node for a multiple in the ORDER DIALOG file. We would like to make this a generic request, however, for OE/RR to set 'ID','WRITE' nodes as apporpriate. The only alternative to hard setting this node is to send the entire DD of a file out. Within a patch, sending the whole file can create an unnecessarily large distribution which can cause us to move to an HFS file rather than exporting the build via the National Patch Module. The specific instance that generated this DBIA sends out post-installation code in routine ORY46 as follows: ; -- Reset ID WRITE node for Items S ^DD(101.412,0,"ID","WRITE")="N OR0,ORNM S OR0=^(0) I $P(OR0,U,2) S ORNM=$P($G(^ORD(101.41,+$P(OR0,U,2),0)),U) D:$L(ORNM) EN^DDIOL(ORNM,,""? 10"")" STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29454675 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING NUMBER: 2808 IA #: 2808 FILE NUMBER: 58.81 GLOBAL ROOT: PSD(58.81 DATE CREATED: APR 29, 1999 CUSTODIAL PACKAGE: DRUG ACCOUNTABILITY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2808 ID: PSD(58.81 GENERAL DESCRIPTION: This is an open agreement between Drug Accountability and Controlled Substances. The terms of this agreement are to allow Controlled Substances access to any field in the DRUG ACCOUNTABILITY TRANSACTION file (#58.81). The method of access can be either Direct Read/Write or by using Filemanager. The reason for this agreement is that prior to the release of Drug Accountability 3.0, this file was the property of Controlled Substances. STATUS: Active MAIL MESSAGE: 29475712 SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 2809 IA #: 2809 FILE NUMBER: 58.811 GLOBAL ROOT: PSD(58.811 DATE CREATED: APR 29, 1999 CUSTODIAL PACKAGE: DRUG ACCOUNTABILITY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2809 ID: PSD(58.811 GENERAL DESCRIPTION: This is an open agreement between Drug Accountability and Controlled Substances. The terms of this agreement are to allow Controlled Substances access to any field in the DRUG ACCOUNTABILITY ORDER file (#58.811). The method of acccess can be either Direct Read/Write or by using Filemanager. The reason for this agreement is that prior to the release of Drug Accountability 3.0, this file was the property of Controlled Substances. STATUS: Active MAIL MESSAGE: 29475714 SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 2810 IA #: 2810 FILE NUMBER: 404.57 GLOBAL ROOT: SCTM(404.57 DATE CREATED: APR 29, 1999 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2810-A ORIGINAL NUMBER: 2810 ID: SCTM(404.57 GLOBAL REFERENCE: SCTM(404.57,0 FIELD NUMBER: .09 FIELD NAME: ASSOCIATED CLINIC ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Clinical Reminder Package would like to reference the following file directly : TEAM POSITION #404.57 - Determine associated Clinic for Team Position As corresponding APIs are planned, this IA will be in effect until the appropriate APIs are released. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29446887 KEYWORDS: ASSOCIATED CLINIC SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 2811 IA #: 2811 FILE NUMBER: 404.43 GLOBAL ROOT: SCPT(404.43, DATE CREATED: APR 29, 1999 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2810-B ORIGINAL NUMBER: 2810 ID: SCPT(404.43, GLOBAL REFERENCE: SCPT(404.43,0 FIELD NUMBER: .02 FIELD NAME: TEAM POSITION ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Clinical Reminder Package would like to reference the following files directly : PATIENT TEAM POSITION ASSIGNMENT #404.43 - Determine Team Position As corresponding APIs are planned, this IA will be in effect until the appropriate APIs are released. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29446887 KEYWORDS: TEAM POSITION SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 2812 IA #: 2812 DATE CREATED: APR 30, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUSRVLV NAME: TIU GET DOCUMENT COUNT ID: TIUSRVLV GENERAL DESCRIPTION: This DBIA documents calls to routine TIUSRVLV ^TMP("TIULIST",$J) may be killed before and after use. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29484099 COMPONENT/ENTRY POINT: DOCCNT(TIUY,DFN,VSTR,VSIT) COMPONENT DESCRIPTION: This entry point returns the number of TIU documents for a visit. The Visit may be identified by DFN and visit string or visit. VARIABLES: TIUY TYPE: Output VARIABLES DESCRIPTION: The number of TIU documents, this value is returned to the calling routine. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal number of the patient as stored in ^DPT(DFN VARIABLES: VSTR TYPE: Input VARIABLES DESCRIPTION: A Visit string representing an encounter in the form of "Location";"date/tame";"service category" where "location", "date/time" and "service category" would be replaced with the actual values. VARIABLES: VSIT TYPE: Input VARIABLES DESCRIPTION: Optional value containing the Visit number. COMPONENT/ENTRY POINT: NOTES(.ARRAY,VISIT,STATUS) COMPONENT DESCRIPTION: Returns a list of notes VARIABLES: .ARRAY TYPE: Both VARIABLES DESCRIPTION: Passed by reference as name of array to receive output. Receives list of notes for visit (and optionally only a certain status of notes). Return array is in the following format: Return array is in the following format: ^TMP("TIULIST",$J,9999999-VERIFICATION DATE/TIME,COUNTER)=record data from record is as follows Piece: Data 1 IEN of TIU DOCUMENT file (#8925) 2 Display name of document class 3 Reference date (internal format) 4 Patient Name in format (LAST, FIRST MI) followed by space followed by last 4 5 Signature name of author/dictator 6 Name of Hospital Location associated with note 7 Name of TIU STATUS in lower case 8 'Adm: ' if type of location is a ward or 'Visit: ' otherwise appeneded with EPISODE BEGIN DATE/TIME in format MM/DD/YY 9 If EPISODE END DATE/TIME exists, returns 'Dis: " appended to the date in MM/DD/YY format. VARIABLES: VISIT TYPE: Input VARIABLES DESCRIPTION: Pointer to the VISIT file (#9000010). VARIABLES: STATUS TYPE: Input VARIABLES DESCRIPTION: Optional: Internal value of the TIU STATUS file denoting the status of notes you want returned. If not passed, all notes for visit are returned. COMPONENT/ENTRY POINT: SUMMARY(.ARRAY,VISIT,STATUS) COMPONENT DESCRIPTION: Returns list of summaries VARIABLES: .ARRAY TYPE: Both VARIABLES DESCRIPTION: Passed by reference as name of array to receive output. Receives list of summaries for visit (and optionally only a certain status of summaries). Return array is in the following format: ^TMP("TIULIST",$J,9999999-VERIFICATION DATE/TIME,COUNTER)=record data from record is as follows Piece: Data 1 IEN of TIU DOCUMENT file (#8925) 2 Display name of document class 3 Reference date (internal format) 4 Patient Name in format (LAST, FIRST MI) followed by space followed by last 4 5 Signature name of author/dictator 6 Name of Hospital Location associated with note 7 Name of TIU STATUS in lower case 8 'Adm: ' if type of location is a ward or 'Visit: ' otherwise appeneded with EPISODE BEGIN DATE/TIME in format MM/DD/YY 9 If EPISODE END DATE/TIME exists, returns 'Dis: " appended to the date in MM/DD/YY format. VARIABLES: VISIT TYPE: Input VARIABLES DESCRIPTION: Pointer to the VISIT file (#9000010). VARIABLES: STATUS TYPE: Input VARIABLES DESCRIPTION: Optional: Internal value of the TIU STATUS file denoting the status of summaries you want returned. If not passed, all summaries for visit are returned. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: SCHEDULING DBA Comments: 2/23/15-MC: Added Scheduling as a subscriber to ICR #2812 at the request of Brian Tomlin and approval of Margy McClenahan for patch SD*5.3*628. NUMBER: 2813 IA #: 2813 FILE NUMBER: 8925.1 GLOBAL ROOT: DD(8925.1,0,'ID' DATE CREATED: APR 30, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TIU REMOVE TYPE AS IDENTIFIER FROM DOC DEF FILE (#8925.1) ID: DD(8925.1,0,'ID' GLOBAL REFERENCE: DD(8925.1,0,'ID',.04) FIELD NUMBER: .04 FIELD NAME: TYPE ACCESS: Write w/Fileman GENERAL DESCRIPTION: In initial test versions of TIU the .04 TYPE field of the DOCUMENT DEFINITIONS FILE (#8925.1) was defined as an identifier. This was changed prior to the release of TIU, but initial test sites still have the .04 field defined as an identifier. To remove this relationship, TIU requests permission to directly kill the Data Dictionary node defining this field as an identifier, i.e. K ^DD(8925.1,0,"ID",.04). This kill will be performed during the installation routine of TIU*1.0*38, which could not install properly without removal of the identifier status. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29484378 KEYWORDS: TIU*1*38 KEYWORDS: ID NODE SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 2816 IA #: 2816 FILE NUMBER: 81.3 GLOBAL ROOT: DIC(81.3, DATE CREATED: MAY 05, 1999 CUSTODIAL PACKAGE: CPT/HCPCS CODES USAGE: Supported TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: CPT MODIFIERS FILE ID: DIC(81.3, CREATOR: ROWE,KIMBALL GLOBAL REFERENCE: DIC(81.3,DA FIELD NUMBER: .01 FIELD NAME: MODIFIER LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: May be pointed to by other files. GLOBAL REFERENCE: DIC(81.3,'B', GLOBAL DESCRIPTION: Direct global read of the "B" cross reference. GLOBAL REFERENCE: DIC(81.3,'BA', GLOBAL DESCRIPTION: Direct global read of the "BA" cross reference. GLOBAL REFERENCE: DIC(81.3,'ACT', GLOBAL DESCRIPTION: Direct global read of the "ACT" cross reference. GENERAL DESCRIPTION: This will allow other packages to conduct FileMan lookups and to point to the CPT MODIFIERS file #81.3. Direct read of the "B", "BA" and "ACT" cross-references will be permitted. Direct read of any node in file 81.3 by the Lexicon Environment Check Routines will also be permitted. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 70625627 KEYWORDS: CPT KEYWORDS: MODIFIER DBA Comments: 1/9/15-MC: Kimball Rowe is trying to reduce the number of ICRs being maintained by packages that he supports. He is planning to retire ICR #3026 (current subscribers IB, Automated Info Collection Sys, Imaging) and edit ICR # 2816 to be all inclusive for file 81.3. Added Kimball as an editor for ICR #2816. 1/9/15-MC: Kimball has completed his edits for ICR. Removed Kimball as an editor for the ICR. NUMBER: 2817 IA #: 2817 FILE NUMBER: 40.8 GLOBAL ROOT: DG(40.8, DATE CREATED: MAY 17, 1999 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR looks at 'AD' x-ref in DG(40.8 ID: DG(40.8, GLOBAL REFERENCE: DG(40.8,'AD',DIV) GENERAL DESCRIPTION: OE/RR would like permission to reference the 'AD' x-ref in file 40.8 (MEDICAL CENTER DIVISION). We need this to get the INSTITUTION file pointers associated with a medical center. ALL^VASITE returns the pointers to 40.8 and not file 4. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29570699 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE SUBSCRIBING PACKAGE: SURGERY SUBSCRIBING PACKAGE: VBECS SUBSCRIBING PACKAGE: INTEGRATED BILLING SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING DETAILS: ADDED 9/28/2009 SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING DETAILS: ADDED 5/2/2011 DATE/TIME EDITED: MAY 02, 2011@10:48 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: NAPOLIELLO,GREG WITH CONCURRENCE OF: HARVEY,JULIE NUMBER: 2818 IA #: 2818 FILE NUMBER: 8992.1 GLOBAL ROOT: XTV(8992.1 DATE CREATED: MAY 17, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR References to Alert Tracking File ID: XTV(8992.1 CREATOR: IVEY,JOEL GLOBAL REFERENCE: XTV(8992.1,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: XTV(8992.1,D0,2) FIELD NUMBER: 2 FIELD NAME: DATA FOR PROCESSING LOCATION: 2;E1,245 ACCESS: Read w/Fileman GLOBAL REFERENCE: XTV(8992.1,D0,20) FIELD NUMBER: 20 FIELD NAME: RECIPIENT LOCATION: 20;0 ACCESS: Read w/Fileman GLOBAL REFERENCE: XTV(8992.1,'B', FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: XTV(8992.1,'R', FIELD NUMBER: 20 FIELD NAME: RECIPIENT LOCATION: 20;0 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: OE/RR utilizes the alert tracking file to obtain information from existing alerts to process new alerts. The routine ORB3REG directly accesses the XTV(8992.1 (Alert Tracking) global to obtain information from existing alerts. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29572330 KEYWORDS: ALERT KEYWORDS: NOTIFICATION SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: OE/RR will use this DBIA until the code in ORB3REG can be patched to use apis provided in XU*8.0*114. Once ORB3REG is patched and released, the direct access of XTV(8992.1 will be eliminated and this DBIA will no longer be necessary. DATE ACTIVATED: OCT 22, 2008 DATE/TIME EDITED: OCT 10, 2008@12:32 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: IVEY,JOEL WITH CONCURRENCE OF: DEFA,TANA DATE/TIME EDITED: OCT 22, 2008@02:05 ACTION: APPROVED AT THE REQUEST OF: CHUNG,TERESA WITH CONCURRENCE OF: IVEY,JOEL NUMBER: 2819 IA #: 2819 FILE NUMBER: 45.83 GLOBAL ROOT: DGP(45.83 DATE CREATED: MAY 18, 1999 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2819 ID: DGP(45.83 GLOBAL REFERENCE: DGP(45.83,D0,0) FIELD NUMBER: 1 FIELD NAME: TRANSMISSION DATE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the date the PTF record was transmitted to Austin. GLOBAL DESCRIPTION: This is the main global node for the PTF RELEASE file. GLOBAL REFERENCE: DGP(45.83,D0,'P',D1,0) FIELD NUMBER: 1 FIELD NAME: DATE TRANSMITTED LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the date the PTF record was transmitted to Austin. GLOBAL DESCRIPTION: This is the PTF RECORD sub-file global node for the PTF RELEASE file. GENERAL DESCRIPTION: In one of the routines for the IB Billing Lag Time Report (IBJDB11), the ^DGP(45.83 global for the PTF RELEASE file is being accessed for the PTF Transmission Date. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29577726 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 2820 IA #: 2820 FILE NUMBER: 45.84 GLOBAL ROOT: DGP(45.84 DATE CREATED: MAY 18, 1999 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2820 ID: DGP(45.84 GLOBAL REFERENCE: DGP(45.84,D0,0) FIELD NUMBER: 4 FIELD NAME: RELEASE DATE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the date the PTF record was released for transmission to Austin. GLOBAL DESCRIPTION: This is the main global node for the PTF CLOSE OUT file. GENERAL DESCRIPTION: In the IB Billing Lag Time Report, global ^DGP(45.84 is being accessed for the PTF Transmission Date. In one of the routines for the IB Billing Lag Time Report (IBJDB11), the ^DGP(45.84 global for the PTF CLOSE OUT file is being accessed for the Release Date, which is used as the IEN of the PTF RELEASE entry which has the PTF Transmission Date. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29577739 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 2821 IA #: 2821 FILE NUMBER: .84 DATE CREATED: AUG 09, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DIALOG File GENERAL DESCRIPTION: To qantify supported DIALOG entries in the DIALOG file #.84 STATUS: Active MAIL MESSAGE: 29970595 KEYWORDS: DIALOG COMPONENT/ENTRY POINT: 201 COMPONENT DESCRIPTION: DIALOG NUMBER: 201 TYPE: ERROR INTERNAL PARAMETERS NEEDED: YES PACKAGE: VA FILEMAN DESCRIPTION: The specified input variable is either 1) required but not defined or 2) not valid. TEXT: The input variable |1| is missing or invalid. PARAMETER SUBSCRIPT: 1 PARAMETER DESCRIPTION: Variable name. NUMBER: 2823 IA #: 2823 FILE NUMBER: 8932.1 GLOBAL ROOT: USC(8932.1, DATE CREATED: MAY 19, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2823 ID: USC(8932.1, GLOBAL REFERENCE: USC(8932.1, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: IB is using a pointer to the Person Class file (#8932.1) to define types of providers. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29582773 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 2824 IA #: 2824 FILE NUMBER: 200 GLOBAL ROOT: VA(200 DATE CREATED: MAY 24, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2824 ID: VA(200 GLOBAL REFERENCE: VA(200,DUZ,.13 FIELD NUMBER: .131 FIELD NAME: PHONE (HOME) LOCATION: .13;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .132 FIELD NAME: OFFICE PHONE LOCATION: .13;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .133 FIELD NAME: PHONE #3 LOCATION: .13;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .134 FIELD NAME: PHONE #4 LOCATION: .13;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .135 FIELD NAME: COMMERCIAL PHONE LOCATION: .13;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .136 FIELD NAME: FAX NUMBER LOCATION: .13;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .137 FIELD NAME: VOICE PAGER LOCATION: .13;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .138 FIELD NAME: DIGITAL PAGER LOCATION: .13;8 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Nursing requires direct global read access to the following fields in the New Person (#200) file which contain the telephone data used in the nursing End of Shift Report: .131 PHONE (HOME) .132 OFFICE PHONE .133 PHONE #3 .134 PHONE #4 .135 COMMERCIAL PHONE .136 FAX NUMBER .137 VOICE PAGER .138 DIGITAL PAGER STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29587979 SUBSCRIBING PACKAGE: NURSING SERVICE ISC: Hines SUBSCRIBING DETAILS: NUMBER: 2825 IA #: 2825 DATE CREATED: JUL 19, 2000 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSADH5 NAME: GMTSADH5 ID: GMTSADH5 GENERAL DESCRIPTION: These are the API's used to get information for the Adhoc Health Summary. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31729171 KEYWORDS: adhoc COMPONENT/ENTRY POINT: COMP(Y) COMPONENT DESCRIPTION: Gets Adhoc Health Summary components from file 142.1 VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Y(i)=(1)I;IFN^(2)Component Name [Abb]^(3)Occ Limit^(4)Time Limit^ (5)Header Name^(6)Hosp Loc Disp^(7)ICD Text Disp^(8)Prov Narr Disp (9)CPT Modifier Disp^(10)Summary Order COMPONENT/ENTRY POINT: COMPSUB(Y,GMTSUB) COMPONENT DESCRIPTION: Get subcomponents from a predefined ADHOC component VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Y(i)=ifn of pointed to file entry^name VARIABLES: GMTSUB TYPE: Input VARIABLES DESCRIPTION: Desired Adhoc subcomponent COMPONENT/ENTRY POINT: FILES(Y,GMTSCP) COMPONENT DESCRIPTION: Get Files to select from for a component VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Array of files for selection. VARIABLES: GMTSCP TYPE: Input VARIABLES DESCRIPTION: Internal entry number of component in file 142.1 to retrieve files from. COMPONENT/ENTRY POINT: FILESEL(GMTSRT,GMTSFI,GMTSFM,DIR) COMPONENT DESCRIPTION: Get file entries for selected component. VARIABLES: GMTSRT TYPE: Output VARIABLES DESCRIPTION: Output array: ^TMP("ORDATA",$J, VARIABLES: GMTSFI TYPE: Input VARIABLES DESCRIPTION: File number to select from. VARIABLES: GMTSFM TYPE: Input VARIABLES DESCRIPTION: Last ifn listed in long list box. This is where to start listing from. VARIABLES: DIR TYPE: Input VARIABLES DESCRIPTION: Direction to go in the file. Forward is the default (1). COMPONENT/ENTRY POINT: REPORT(GMTSEG,GMTSEGC,GMTSEGI,GMTSCPS,DFN) COMPONENT DESCRIPTION: Builds Adhoc report VARIABLES: GMTSEG TYPE: Output VARIABLES DESCRIPTION: Output array for report. VARIABLES: GMTSEGC TYPE: Output VARIABLES DESCRIPTION: Set to the last ifn of the GMTSCPS array. VARIABLES: GMTSGI TYPE: Output VARIABLES DESCRIPTION: Array of component names defined in the Adhoc component from file 142. VARIABLES: GMTSCPS TYPE: Input VARIABLES DESCRIPTION: Array of selected components to build the Adhoc report. VARIABLES: DFN TYPE: Input COMPONENT/ENTRY POINT: SUBITEM(Y,GMTSTEST) COMPONENT DESCRIPTION: Get Subitems for a Lab Test panel VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Array of tests included in a lab panel. VARIABLES: GMTSTEST TYPE: Input VARIABLES DESCRIPTION: Internal file number of Laboratory Test from file 60. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: Used for the GUI Adhoc Health Summary. EDITOR: ROWE,KIMBALL NUMBER: 2828 IA #: 2828 DATE CREATED: MAY 25, 1999 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJBCMA NAME: RETURN ACTIVE ORDERS TO BCMA ID: PSJBCMA CREATOR: CRUMLEY,JAMIE GENERAL DESCRIPTION: The entry point EN^PSJBCMA is provided by Inpatient Medications package to return patient active orders to Bar Code Med Admin to be used in administering medications at patient's bedside. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 35681806 KEYWORDS: PSJBCMA COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: OUTPUT DEFINITION ^TMP("PSJ",$J,Index,0) = DFN ^ ON (Order number from Inpatient Medications V. 5.0 package)^ ON_V/U/P ^ PREVIOUS ORDER ^ FOLLOWING ORDER ^ IV TYPE ^ INTERMITTENT SYRINGE ^ CHEMOTHERAPY TYPE ^ ORDERS FILE ENTRY ^TMP("PSJ",$J,Index,1) = MED ROUTE expansion ^ SCHEDULE TYPE CONVERSION ^ SCHEDULE ^ START DATE ^ STOP DATE ^ ADMIN TIMES ^ STATUS ^ NOT TO BE GIVEN FLAG ^ Original SCHEDULE TYPE ^ Auto Cancel/DC flag ^TMP("PSJ",$J,Index,1,0) = PROMPT FOR INJECTION SITE IN BCMA^MED ROUTE name ^ DSPLY ON IVP/IVPB TAB IN BCMA ^TMP("PSJ",$J,Index,2) = DOSAGE ORDERED ^ INFUSION RATE ^ SELF MED ^ HOSPITAL SUPPLIED SELF MED ^TMP("PSJ",$J,Index,3) = ORDERABLE ITEM [P] ^ ORDERABLE ITEM NAME_" "_DOSAGE FORM ^ DOSAGE FORM ^TMP("PSJ",$J,Index,4) = SPECIAL INSTRUCTONS (U/D) or OTHER PRINT INFO (IV) ^TMP("PSJ",$J,Index,5) = NOTIFICATION ^ FLAGGED [S] ^PHARMACY/CPRS ^ FLAG COMMENTS Notificaton will be a 1, if the order should trigger a stat/now notification. It will be 0 if no notification should be done. Piece 3 will contain PHARMACY if the flag was initiated by Pharmacy or CPRS if it was initiated by CPRS. ^TMP("PSJ",$J,Index,700,0) = Number of DISPENSE DRUG return (exists only if order is a Unit Dose order) ^TMP("PSJ",$J,Index,700,Index,0) = DISPENSE DRUG [P] ^ DISPENSE DRUG NAME ^ UNITS PER DOSE [N] ^ INACTIVE DATE ^TMP("PSJ",$J,Index,850,0) = Number of additive(s) return (exists only if IV order) ^TMP("PSJ",$J,Index,850,D0,0) = ADDITIVE [P] ^ ADDITIVE NAME ^ STRENGTH ^ BOTTLE ^^ ORDERABLE ITEM [P] ^ ORDERABLE ITEM NAME_" "_DOSAGE FORM ^ DOSAGE FORM ^TMP("PSJ",$J,Index,950,0) = Number of solution(s) return (exists only if IV order) ^TMP("PSJ",$J,Index,950,D0,0) = SOLUTION [P] ^ SOLUTION NAME ^ VOLUME ^ PRINT NAME {2} [F] ^^ ORDERABLE ITEM [P] ^ ORDERABLE ITEM NAME_" "_DOSAGE FORM ^ DOSAGE FORM Unique ID# is the Bar Code Identification Number for this label. Format: DFN_"V"_Seq, where Seq is a sequential number. ^TMP(PTMP,$J,Index,800,Unique ID#,0) = Number of additives(s) return (exists only if order is an IV order) ^TMP(PTMP,$J,Index,800,Unique ID#,Index) = ADDITIVE[P] ^ ADDITIVE NAME ^ STRENGTH [F] ^ BOTTLE ^TMP(PTMP,$J,Index,900,Unique ID#,0) = Number of solution(s) return (exists only if order is an IV order) ^TMP(PTMP,$J,Index,900,Unique ID#,Index) = SOLUTION[P] ^ SOLUTION NAME ^ VOLUME NOTE: - ^TMP("PSJ",J,1,0) = -1 will be returned if no active orders are found. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient Internal File Number (required). VARIABLES: BDT TYPE: Input VARIABLES DESCRIPTION: Data used to start searching for order stop after this date (optional). If BDT is not included, NOW is used as the time to start searching for active orders. VARIABLES: OTDATE TYPE: Input VARIABLES DESCRIPTION: Include One-Time orders from this date (optional). If OTDATE="" 30 days from today is used. If OTDATE is not included, 30 days from the current date is used. SUBSCRIBING PACKAGE: BAR CODE MED ADMIN DBA Comments: JSHARVEY/20070119 - Deactivated for edit of additional fields as per J. Crumley. JSHARVEY/20060119 - Reactivated DATE/TIME EDITED: JAN 19, 2007@16:00 ACTION: CONTENT CORRECTED AT THE REQUEST OF: CRUMLEY,JAMIE WITH CONCURRENCE OF: HARVEY,JULIE DATE/TIME EDITED: APR 24, 2007@10:00 ACTION: CONTENT CORRECTED AT THE REQUEST OF: CRUMLEY,JAMIE DATE/TIME EDITED: JUL 10, 2007@23:00 ACTION: CONTENT CORRECTED AT THE REQUEST OF: CRUMLEY,JAMIE NUMBER: 2829 IA #: 2829 DATE CREATED: MAY 25, 1999 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJBCMA1 NAME: RETURN DETAIL INFO ON PATIENT'S ORDER FOR BCMA ID: PSJBCMA1 CREATOR: CRUMLEY,JAMIE GENERAL DESCRIPTION: The entry point EN^PSJBCMA1 is provided by Inpatient Medications package to return the detail information on a patient's order for Bar Code Med Admin to use. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 35681808 KEYWORDS: PSJBCMA1 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: OUTPUT DEFINITION ^TMP(PTMP,$J,0) = DFN^ON^ ON_V/U/P ^ PREVIOUS ORDER ^ FOLLOWING ORDER ^ IV TYPE ^ INTERMITTENT SYRINGE ^ CHEMOTHERAPY TYPE ^ ORDERS FILE ENTRY ^TMP(PTMP,$J,1) = PROVIDER [P] ^ PROVIDER NAME ^ MED ROUTE [P] ^ MR abbreviation ^ SELF MED [S] ^ Expand to YES/NO ^ HOSPITAL SUPPLIED SELF MED [S] ^ Expand to YES/NO ^ NOT TO BE GIVEN FLAG [S] ^ STATUS [S] ^ STATUS expansion ^ Auto Cancel/DC flag ^TMP(PTMP,$J,1,0) = PROMPT FOR INJECTION SITE ^ DSPLY ON IVP/IVPB TAB IN BCMA ^TMP(PTMP,$J,2) = ORDERABLE ITEM [1P] ^ ORDERABLE ITEM NAME_" "_DOSAGE FORM ^ DOSAGE ORDERED ^ INFUSION RATE [F] ^ SCHEDULE ^ DOSAGE FORM ^TMP(PTMP,$J,3) = SPECIAL INSTRUCTIONS(U/D)[F] or OTHER PRINT INFO (IV) [F] ^TMP(PTMP,$J,4) = SCHEDULE TYPE Conversion [S]^SCHEDULE TYPE expansion (from Original Schedule Type for U/D and from Schedule Type Conversion for IV orders) ^ LOG-IN DATE[D]^Expand to MM/DD/YYYY HH:MM^START DATE [D]^Expand to MM/DD/YYYY HH:MM^STOP DATE [D]^Expand to MM/DD/YYYY HH:MM^ADMIN TIMES (in four digit format) ^ Original SCHEDULE TYPE ^ FREQUENCY (Unit Dose order) or SCHEDULE INTERVAL (IV order) ^TMP(PTMP,$J,5) = VERIFYING NURSE [P]^ NURSE NAME ^ NURSE INIT^VERIFYING PHARMACIST [P] ^ PHARMACIST NAME ^ PHARMACIST INIT ^TMP(PTMP,$J,6) = REMARKS(IV)[F] ^TMP("PSJ",$J,7) = NOTIFICATION ^ FLAGGED [S] ^ PHARMACY/CPRS ^ FLAG COMMENTS Notification will be a 1 if the order should trigger a stat/now notification. It will be a 0 if no notification should be done. Piece 3 will contain PHARMACY if the flag was initated by Pharmacy or CPRS if it was initated by CPRS. ^TMP(PTMP,$J,700,0) = Number of DISPENSED DRUG return (exists only if order is a Unit Dose order) ^TMP(PTMP,$J,700,Index,0) = DISPENSED DRUG [P] ^ DISPENSED DRUG NAME ^ UNITS PER DOSE [N] ^ INACTIVE DATE [D] ^TMP("PSJ1",$J,850,0) = Number of additives(s) return (exists only if IV order) ^TMP("PSJ1",$J,850,D0,0) = ADDITIVE[P] ^ ADDITIVE NAME ^ STRENGTH [F] ^ BOTTLE ^^ ORDERABLE ITEM [P] ^ ORDERABLE ITEM NAME_" "_DOSAGE FORM ^ DOSAGE FORM ^TMP("PSJ1",$J,950,0) = Number of solution(s) return (exists only if IV order) ^TMP("PSJ1",$J,950,D0,0) = SOLUTION[P] ^ SOLUTION NAME ^ VOLUME [F] ^ PRINT NAME {2} [F] ^^ ORDERABLE ITEM [P] ^ ORDERABLE ITEM NAME_" "_DOSAGE FORM ^ DOSAGE FORM Unique ID# is the Bar Code Identification Number for this label. Format: DFN_"V"_Seq, where Seq is a sequential number. ^TMP(PTMP,$J,800,Unique ID#,0) = Number of additives(s) return (exists only if order is an IV order) ^TMP(PTMP,$J,800,Unique ID#,Index) = ADDITIVE[P] ^ ADDITIVE NAME ^ STRENGTH [F] ^ BOTTLE ^TMP(PTMP,$J,900,Unique ID#,0) = Number of solution(s) return (exists only if order is an IV order) ^TMP(PTMP,$J,900,Unique ID#,Index) = SOLUTION[P] ^ SOLUTION NAME ^ VOLUME [F] ^TMP(PTMP,$J,1000,Unique ID#,0) = Number of label(s) return (exists only if order is an IV order) ^TMP(PTMP,$J,1000,Unique ID#,Index) = LABEL PRINT DATE / TIME ^ BAG # ^ LABEL STATUS (set of codes) NOTE: - ^TMP(PTMP,J,0) = -1 will be returned if no detail data are found. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient Internal File Number (required). VARIABLES: ON_V/U/P TYPE: Input VARIABLES DESCRIPTION: Inpatient Medications Package V. 5.0 Order Number (required). VARIABLES: PSJTMP SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING PACKAGE: DSS EXTRACTS SUBSCRIBING DETAILS: ADDED 11/16/2010 DBA Comments: JSHARVEY/20070119 - Deactivated for edit of additional fields as per J. Crumley JSHARVEY/20070119 - Reactivated j DATE/TIME EDITED: JAN 19, 2007@16:00 ACTION: CONTENT CORRECTED AT THE REQUEST OF: CRUMLEY,JAMIE WITH CONCURRENCE OF: HARVEY,JULIE DATE/TIME EDITED: APR 24, 2007@10:04 ACTION: CONTENT CORRECTED AT THE REQUEST OF: CRUMLEY,JAMIE DATE/TIME EDITED: NOV 16, 2010@12:59 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WILBUR,CHARLIE WITH CONCURRENCE OF: YORTY,ROBERT DATE/TIME EDITED: NOV 16, 2010@13:02 ACTION: USAGE CHOICE CHANGED AT THE REQUEST OF: HARVEY,JULIE NUMBER: 2830 IA #: 2830 DATE CREATED: MAY 25, 1999 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJBCMA2 NAME: DBIA2830 ID: PSJBCMA2 GENERAL DESCRIPTION: The entry point EN^PSJBCMA2 is provided by Inpatient Medications package to return a patient order's activity logs for Bar Code Med Admin to use. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31896772 KEYWORDS: PSJBCMA2 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: INPUT DEFINITION DFN: Patient Internal File Number (required) ON_V/U/P: Inpatient Medications Package V. 5.0 Order Number (required) PSJTMP: Flag to indicate what the first subscript (PTMP) to ^TMP should be (optional). If PSJTMP is not supplied or is 0, ^TMP will be subscripted by PSJ. If PSJTMP is 1, ^TMP will be subscripted by PSJ2. This flag will be removed in the future. It is provided for backward compatibility. OUTPUT DEFINITION ^TMP(PTMP,$J,0) = DFN ^ ON ^ ON_V/U/P ^ Number of activities returned ^TMP(PTMP,$J,INDEX,1) = ACTIVITY DATE ^ USER NAME ^ FIELD CHANGE ^ ACTION (U/D) / TYPE OF ACTIVITY (IV) ^ USER IEN (U/D) ^TMP(PTMP,$J,INDEX,2) = OLD DATA ^TMP(PTMP,$J,INDEX,3) = REASON FOR ACTIVITY (IV) NOTE: ^TMP(PTMP,J,0) = -1 will be returned if patient data are not found. SUBSCRIBING PACKAGE: BAR CODE MED ADMIN NUMBER: 2831 IA #: 2831 DATE CREATED: JUN 01, 1999 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORQPT2 NAME: Calls to ORQPT2 ID: ORQPT2 GENERAL DESCRIPTION: This DBIA is a controlled subscription for calls to routine ORQPT2. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28690761 COMPONENT/ENTRY POINT: $$CWAD(DFN) COMPONENT DESCRIPTION: Returns letters C, W, A, D depending on whether patient has warnings, allergies, etc. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of PATIENT file VARIABLES: STRING TYPE: Output VARIABLES DESCRIPTION: STRING=$$CWAD^ORQPT2(DFN) STRING can be null or up to 4 letters. It will contain a C if the patient has crisis notes, a W if the patient has warnings, A if the patient has allergies, or D if the patient has advance directives. SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: Consult/Request Tracking calls $$CWAD^ORQPT2(DFN). SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 2832 IA #: 2832 DATE CREATED: JUN 01, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUSRV NAME: Calls to TIUSRV ID: TIUSRV GENERAL DESCRIPTION: This DBIA will act as a controlled subscription for calls to TIUSRV. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28690496 COMPONENT/ENTRY POINT: RPC(.ARRAY,IEN) COMPONENT DESCRIPTION: Returns TIU Narrative. VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: Output array contains global location of narrative text. (pass by reference) Default is ^TMP("TIUAUDIT",$J, and may be killed before and after use. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of the TIU DOCUMENT file (#8925) indicating the record for which the narrative text is required. SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: Consult/Request Tracking calls RPC^TIUSRV(.ARRAY,IEN). This call is made to retrieve the TIU narrative for use in the detailed display of the consult for the List Manger interface. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 2833 IA #: 2833 DATE CREATED: JUN 01, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUBR1 NAME: Calls to TIUBR1 ID: TIUBR1 GENERAL DESCRIPTION: This DBIA will act as a controlled subscription for calls to TIUBR1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28690496 COMPONENT/ENTRY POINT: EXSTNOTE(DFN,IEN) COMPONENT DESCRIPTION: Displays existing TIU documents for a patient that belong to CONSULTS class or document class. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of PATIENT file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT file (#8925). SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: Consults calls EXSTNOTE^TIUBR1(DFN,IEN). It is used to display existing TIU documents belonging to the CONSULTS class or document class for an existing patient. Selection of a note allows linking of a consult request with the chosen TIU document. This call assumes that the user is using List Manager (List Manager variables are present). NUMBER: 2834 IA #: 2834 DATE CREATED: JUN 01, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUSRVLO NAME: Calls to TIUSRVLO ID: TIUSRVLO GENERAL DESCRIPTION: This DBIA will act as a controlled subscription for calls to TIUSRVLO. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28690496 COMPONENT/ENTRY POINT: $$RESOLVE(IEN) COMPONENT DESCRIPTION: Returns data that is related to a TIU document. Output string returns (number represents ^ piece position): 1 Display name of TIU Title 2 REFERENCE DATE from TIU DOCUMENT file (internal format) 3 Patient name in format LAST, FIRST MI followed by space followed by last 4 of patient SSN 4 AUTHOR/DICTATOR from TIU DOCUMENT file as IEN;SIGNATURE BLOCK TITLE 5 External format of HOSPITAL LOCATION from TIU DOCUMENT file 6 STATUS from TIU DOCUMENT file (external format in lower case) 7 String_": "_EPISODE BEGIN DATE/TIME where String is "Adm" for ward locations and "Visit" for all other location types. Date/time is in MM/DD/YY format. 8 String_" "_EPISODE END DATE/TIME where string is null if no date/time or "Dis: " if date/time exists. Date/time is in MM/DD/YY format. 9 REQUESTING PACKAGE REFERENCE field from TIU DOCUMENT file (internal format) 10 Number of images associated with TIU DOCUMENT entry 11 SUBJECT (OPTIONAL description) field from TIU DOCUMENT file (note that characters are limited to ensure returned string is not longer than 255 characters). (this piece was added with TIU*1*63) VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of tiu DOCUMENT file VARIABLES: STRING TYPE: Output VARIABLES DESCRIPTION: see component description SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: Consults calls $$RESOLVE^TIUSRVL0(IEN) to retrieve selected information from TIU for a TIU document which is linked to a consult request. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD DBA Comments: 6/26/12-MM: VPR added as a subscriber for VPR*1.0. Approved by Joel Russell and Margy McClenehan. Needed for VistA extracts. DATE/TIME EDITED: JUN 26, 2012@14:48 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: RUSSELL,JOEL DATE/TIME EDITED: JUN 26, 2012@14:55 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: MCCLENEHAN,MARGY NUMBER: 2835 IA #: 2835 FILE NUMBER: 101.43 GLOBAL ROOT: ORD(101.43 DATE CREATED: JUN 01, 1999 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Access to file 101.43 ID: ORD(101.43 GLOBAL REFERENCE: ORD(101.43,D0,0) FIELD NUMBER: 2 FIELD NAME: ID LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This is to document the use of the Orderable Items file (101.43) in CPRS by the Laboratory Interface. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29646257 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE SUBSCRIBING DETAILS: "time to live" --> 1 Sep 2004 NUMBER: 2836 IA #: 2836 FILE NUMBER: 101.43 GLOBAL ROOT: ORD(101.43, DATE CREATED: JUN 01, 1999 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Consults use of S.CSLT and S.PROC x-refs ID: ORD(101.43, GLOBAL REFERENCE: ORD(101.43,'S.CSLT' GLOBAL DESCRIPTION: Gets consult type orderable items GLOBAL REFERENCE: ORD(101.43,'PROC', GLOBAL DESCRIPTION: Gets procedure type orderable items. Loops directly through index and also calls DIC with D="S.PROC". GENERAL DESCRIPTION: This is a private DBIA between Consults and OE/RR to allow use of teh S.CSLT and S.PROC x-refs on the ORDERABLE ITEMS file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28690761 SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 2839 IA #: 2839 DATE CREATED: JUN 03, 1999 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: CPRS USE OF XPAR MENU GENERAL DESCRIPTION: CPRS is requesting the ability to attach the XPAR MENU TOOLS menu to the CPRS Configuration (IRM) menu. This will allow IRM users to get to the tools menu for XPAR when editing using other CPRS-related IRM tools. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28678942 COMPONENT/ENTRY POINT: XPAR MENU TOOLS COMPONENT DESCRIPTION: This menu contains several tools for displaying and editing parameter definitions and values. We are requesting the capability to add this to the CPRS IRM config menu. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2840 IA #: 2840 DATE CREATED: JUN 04, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: Use of TIU ACTION CWAD DISPLAY GENERAL DESCRIPTION: The TIU ACTION CWAD DISPLAY protocol is exported with the TIU package. This controlled subscription DBIA will allow other packages to utilize this protocol. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28690496 COMPONENT/ENTRY POINT: TIU ACTION CWAD DISPLAY COMPONENT DESCRIPTION: This protocol displays the CWAD indicators for a patient. SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: Consults uses the TIU ACTION CWAD DISPLAY protocol on the hidden action when using the Consult Service Tracking menu. It's used to allow a user to check on the types of allergies, directives, warnings, etc. that a patient might have. NUMBER: 2841 IA #: 2841 FILE NUMBER: 50 GLOBAL ROOT: PSDRUG DATE CREATED: SEP 15, 1999 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TIU MEDICATION OBJECTS READ DRUG FILE ID: PSDRUG GLOBAL REFERENCE: PSDRUG FIELD NUMBER: 2 FIELD NAME: VA CLASSIFICATION ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: B FIELD NAME: "B" CROSS REFERENCE ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: ASP FIELD NAME: "ASP" CROSS REFERENCE ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: DEA, SPECIAL HDLG ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. TIU's medication objects now allow for the sorting of medications by drug class, including pending orders for medications that may not yet have a dispense drug. They also allow for the exclusion of supply items from medication lists, if desired. To accomodate this functionality, TIU requests direct global read access to the following pharmacy file: ^PSDRUG( - DRUG FILE (#50): "B" cross reference "ASP" cross reference Node 0, piece 2 - VA CLASSIFICATION FIELD (#2). Node 0, piece 3 - DEA, SPECIAL HDLG FIELD (#3) STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 29677689 KEYWORDS: PSDRUG KEYWORDS: TIU MEDICATION OBJECTS SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 2842 IA #: 2842 DATE CREATED: JUN 09, 1999 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORX8 NAME: DBIA2842 ID: ORX8 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29689335 COMPONENT/ENTRY POINT: LATEST VARIABLES: ORPAT TYPE: Input VARIABLES DESCRIPTION: Pointer to the Patient file #2. VARIABLES: ORIT TYPE: Input VARIABLES DESCRIPTION: Pointer to the Orderable Items file #101.43. VARIABLES: ORY TYPE: Both VARIABLES DESCRIPTION: This is an array passed by reference. On return ORY = total number of orders found or 0 if none are found. If orders are found then ORY(ORSTS)=ORIFN^Ord'd By^Entered^StartDT^StopDT^Loc^sts where ORSTS - the ien in the Order Status file #100.01 ORIFN - the ien of the Orderable Item file #101.43 Ord'd By - Ordered By, pointer to file #200 Entered - the date/time the ordered was entered StartDT - the start date/time StopDT - the stop date/time Loc - the location, a variable pointer to file #44 sts - the status name in lowercase SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING DETAILS: Clinical Reminders needs to obtain information about a patient's orders. NUMBER: 2843 IA #: 2843 FILE NUMBER: 101.43 GLOBAL ROOT: ORD(101.43, DATE CREATED: JUN 09, 1999 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2843 ID: ORD(101.43, CREATOR: PULEO,ANTHONY G GLOBAL REFERENCE: ORD(101,43,D0,.01) => NAME FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;.01 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: ID LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: FIELD NUMBER: .1 FIELD NAME: INACTIVATED LOCATION: .01;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: GENERAL DESCRIPTION: STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29689358 SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING DETAILS: Clinical Reminders needs to display the name, id, and the inactivated fields of an Orderable Item. SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: Added for use with VPR*1*1 DBA Comments: 04/24/13 DT: Added VPR as subscriber. DATE ACTIVATED: MAY 19, 2010 DATE/TIME EDITED: MAY 19, 2010@12:10 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: PULEO,ANTHONY DATE/TIME EDITED: MAY 19, 2010@12:33 ACTION: APPROVED AT THE REQUEST OF: PULEO,ANTHONY DATE/TIME EDITED: APR 24, 2013@13:23 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: BUECHLER,MELANIE NUMBER: 2844 IA #: 2844 FILE NUMBER: 52.41 GLOBAL ROOT: PS(52.41, DATE CREATED: JUN 14, 1999 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA 2844 ID: PS(52.41, GLOBAL REFERENCE: PS(52.41, FIELD NUMBER: .01 FIELD NAME: PLACER NUMBER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: A numeric field that represents the Computerized Patient Record System (CPRS) number of the order. FIELD NUMBER: 2 FIELD NAME: ORDER TYPE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This agreement gives the Pharmacy Data Management package access to the PLACER NUMBER (#.01) field in the PENDING OUTPATIENT ORDERS (#52.41) file. This access will be needed every time an action is taken on a pending Outpatient order, for the purpose of locking the order in Outpatient Pharmacy and in Computerized Patient Record System (CPRS). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29710986 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham SUBSCRIBING DETAILS: Pharmacy Data Management can do a direct global read to get the PLACER NUMBER from the PENDING OUTPATIENT ORDERS (#52.41) file for locking purposes. NUMBER: 2845 IA #: 2845 FILE NUMBER: 52 GLOBAL ROOT: PSRX( DATE CREATED: JUN 14, 1999 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA 2845 ID: PSRX( GLOBAL REFERENCE: PSRX( FIELD NUMBER: 39.3 FIELD NAME: PLACER ORDER # LOCATION: OR1;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: A numeric field that represents the Computerized Patient Record System (CPRS) number of the order. FIELD NUMBER: 26 FIELD NAME: EXPIRATION DATE LOCATION: 2;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 100 FIELD NAME: STATUS LOCATION: STA;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This agreement gives the Pharmacy Data Management package access to the PLACER ORDER # (#39.3) field in the PRESCRIPTION (#52) file. This access will be needed every time an action is taken on a prescription, for the purpose of locking the order in Outpatient Pharmacy and in Computerized Patient Record System (CPRS). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29710988 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham SUBSCRIBING DETAILS: Pharmacy Data Management can do a direct global read to get the PLACER ORDER # from the PRESCRIPTION (#52) file for locking purposes. NUMBER: 2846 IA #: 2846 DATE CREATED: JUN 14, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUPARAM NAME: DBA2846 ID: XUPARAM GENERAL DESCRIPTION: Broker uses $$BAT^XUPARAM in two situations to retrieve the value of the Broker Activity Timeout, which is stored in the Kernel System Parameters file: 1)to set the timeout on READs waiting for client requests. 2) to pass the tiemout value back to the client in order to determine the frequency of polling from client to server. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29787365 COMPONENT/ENTRY POINT: BAT() SUBSCRIBING PACKAGE: RPC BROKER ISC: Oakland NUMBER: 2847 IA #: 2847 DATE CREATED: JUN 16, 1999 CUSTODIAL PACKAGE: VA FILEMAN USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED NAME: ALLOW DIE CALL WITHIN ANOTHER DIE GENERAL DESCRIPTION: This integration agreement is between IFCAP and FileMan. IFCAP is calling templates through a DIE programmer call. In the templates a routine is called. Within that routine a call is made to both DIC and DIE programmer calls to add a new sub-record entry and fill in additional data. This second DIE call is a recursive call. FileMan needs to save a group of variables to prevent the second DIE call from interfering with the first DIE call, the one handling the template. To properly call DIE the following variables need to be NEWed. DIAA,I,J,X,DO,DC,DA,DE,DG,DIE,DR,DIC,D,D0,D1,D2,D3,D4,D5,D6,DI,DH, DIA,DICR,DK,DIK,DL,DLAYGO,DM,DP,DQ,DU,DW,DIEL,DOV,DIOV,DIEC,DB, DV,DIFLD Any place within IFCAP that a recursive call to DIC/DIE needs to be done will be allowed by this agreement. This intregration agreement will stay in effect until FileMan DIC and DIE programmer calls become recursive. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29648482 SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Presently we are using this IA within Purchase Order templates. The template calls PRCHNPO3. Within PRCHNPO3, a call is made to PRCHSP1. In PRCHSP1 is the second DIE call. Here is where the NEWed list of variables is placed. NUMBER: 2848 IA #: 2848 DATE CREATED: JUN 16, 1999 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SCAPMCA NAME: GETALL API CALL ID: SCAPMCA STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29726344 KEYWORDS: GETALL COMPONENT/ENTRY POINT: $$GETALL(DFN[,SCDATE][,SCARR]) COMPONENT DESCRIPTION: Function: $$GETALL^SCAPMCA(DFN) Input: DFN - This is a required parameter that is the internal entry number of the PATIENT file. Output: HIERARCHICAL FORMAT (This format will exist only if there are assignments that exist.) @SCARR@(DFN,"TM",a,b)=team data @SCARR@(DFN,"TM",a,b,"POS",c)=position data @SCARR@(DFN,"TM",a,b,"POS",c,"PROV",d)=provider data @SCARR@(DFN,"TM",a,b,"POS",c,"PPOS",e)=preceptor position data @SCARR@(DFN,"TM",a,b,"POS",c,"PPROV",f)=preceptor provider data where: a = TEAM file (#404.51) ifn b = PATIENT TEAM Assignment file (#404.42) ifn c = PATIENT TEAM POSITION Assignment file (#404.43) ifn d = POSITION Assignment HISTORY file (#404.52) ifn e = TEAM POSITION file (#404.57) ifn f = POSITION Assignment HISTORY file (#404.52) ifn Output: FLAT FORMAT (The zero nodes of this format are always returned. They are equal to zero if no assignments exist.) @SCARR@(DFN,"NPCPOS",0)=non-PC position count @SCARR@(DFN,"NPCPOS",n)=non-PC position data @SCARR@(DFN,"NPCPPOS",0)=non-PC preceptor position count @SCARR@(DFN,"NPCPPOS",n)=non-PC preceptor position data @SCARR@(DFN,"NPCPPR",0)=non-PC preceptor provider count @SCARR@(DFN,"NPCPPR",n)=non-PC preceptor provider data @SCARR@(DFN,"NPCPR",0)=non-PC provider count @SCARR@(DFN,"NPCPR",n)=non-PC provider data @SCARR@(DFN,"NPCTM",0)=non-PC team count @SCARR@(DFN,"NPCTM",n)=non-PC team data @SCARR@(DFN,"PCAP",0)=PC associate provider count @SCARR@(DFN,"PCAP",n)=PC associate provider data @SCARR@(DFN,"PCPOS",0)=PC position count @SCARR@(DFN,"PCPOS",n)=PC position data @SCARR@(DFN,"PCPPOS",0)=PC preceptor position count @SCARR@(DFN,"PCPPOS",n)=PC preceptor position data @SCARR@(DFN,"PCPR",0)=PC provider count @SCARR@(DFN,"PCPR",n)=PC provider data @SCARR@(DFN,"PCTM",0)=PC team count @SCARR@(DFN,"PCTM",n)=PC team data where: n = incrementing number from 1 to 'n'. Output: ARRAY DATA STRINGS (This outlines the various pieces of data that are returned for the Team, Position and Provider.) TEAM Information Data String: Piece Description 1 IEN of TEAM file entry 2 Name of Team 3 IEN of file #404.42 (Patient Team Assignment) 4 Current Effective Date 5 Current Inactive Date (if any) 6 Pointer to #403.47 (purpose) 7 Name of Purpose 8 Is this the Patient's PC Team? POSITION Information Data String: Piece Description 1 IEN of TEAM POSITIONfile (#404.57) 2 Name of Position 3 IEN of Team #404.51 4 IEN of file #404.43 (Patient/Team/Position Assignment) 5 Current Effective Date 6 Current Inactive Date (if any) 7 Pointer to Standard Role (#403.46) 8 Name of Standard Role 9 Pointer to User Class (#8930) 10 Name of User Class 11 Pointer to Patient Team Assignment (#404.42) 12 IEN of Preceptor Position (#404.57) PROVIDER Information Data String: Piece Description 1 IEN of NEW PERSON file entry (#200) 2 Name of Person 3 IEN of Team Position file (#404.57) 4 Name of Position 5 IEN of User Class (#8930) of Position (#404.57) 6 User Class Name 7 IEN of Standard Position (#403.46) 8 Standard Role (Position) Name 9 Activation Date for #404.52 (not 404.59!) 10 Inactivation Date for #404.52 11 IEN of Position Assignment History (#404.52) 12 IEN of Preceptor Position 13 Name of Preceptor Position VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal entry of the PATIENT file (#2). VARIABLES: SCDATE TYPE: Input VARIABLES DESCRIPTION: Array of Dates (Default=DT) SCDATE("BEGIN")=beginning date SCDATE("END")=ending date SCDATE("INCL")= 1: only reference practitioners that were on team for entire date range. 0: anytime in date range (Default = 1) VARIABLES: SCARR TYPE: Output VARIABLES DESCRIPTION: Name of array to return data. (Default is ^TMP("SC",$J) NUMBER: 2849 IA #: 2849 FILE NUMBER: 100 GLOBAL ROOT: OR(100, DATE CREATED: JUN 18, 1999 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Use of ORDERS file (#100) ID: OR(100, GLOBAL REFERENCE: OR(100,DA,0) FIELD NUMBER: 1 FIELD NAME: CURRENT AGENT/PROVIDER LOCATION: 0;4 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 44188513 SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: DSS EXTRACTS DATE/TIME EDITED: SEP 15, 2006@11:04 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CORONA,JOSE WITH CONCURRENCE OF: MALMROSE,CARY NUMBER: 2851 IA #: 2851 FILE NUMBER: 409.63 GLOBAL ROOT: SD(409.63, DATE CREATED: AUG 05, 2004 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TIU use of SD(409.63,'ACO',1,STATUS) ID: SD(409.63, GLOBAL REFERENCE: SD(409.63,'ACO',1,STATUS) FIELD NUMBER: .06 FIELD NAME: CHECK OUT ALLOWED? LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: TIU uses a global read of ^SD(409.63,"ACO",1,STATUS) cross-reference on the 'Check Out Allowed?' field (#.06) of the Appointment Status file (#409.63) to determine if the appointment is allowed for check-out. STATUS := appt status as determined by $$STATUS^SDAM1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29729050 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City DBA Comments: 12/19/14-MM: Received a request from Mobile Apps/Scheduling Calendar View to subscribe to this ICR and to ICR #6057 (new ICR for STATUS~SDAM1 API). On 12/19/14 the project team withdrew the request for access to ICR #2851 and 6057. They will be using SDAMA301 API documented in supported ICR #4433 for the appointment status. NUMBER: 2853 IA #: 2853 DATE CREATED: JUN 24, 1999 CUSTODIAL PACKAGE: INCOME VERIFICATION MATCH CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: FILE USE OVERLAP GENERAL DESCRIPTION: Since IVM has custody of the numberspace from 300 to 304, the following files are delegated to the custody of INCOME VERIFICATION NAT'L DB 300.1 IVM FACILITY 300.11 VETERANS ID VERIFICATION ACCESS 300.111 DEATH TRANSMISSIONS 300.113 AAC TRANSMISSIONS STATISTICS 300.114 IVM AUSTIN TRANSMISSION STATUS 300.12 IVM MASTER CLIENT 300.121 IVM ADJUDICATION 300.122 IVM VERIFIED INSURANCE 300.124 IVM CLOSED CASE CODES 300.13 IVM CLIENT INCOME 300.1311 SITE COMPLETED MT STATISTICS 300.132 ENROLLMENT 300.133 IVM REVIEW RECORDS 300.15 SSA EARNINGS REPORT TYPE 300.16 IRS DOCUMENT TYPE - UNEARNED INCOME 300.17 IVM REFERENCE 300.18 IVM EMPLOYER 300.19 FINANCIAL INSTITUTION 300.2 IVM ELIGIBILITY STATUS 300.21 IVM HL7 SEGMENTS USED 300.22 IRS SUB DOCUMENT TYPE 300.3 IVM EQUIPMENT 300.4 IVM DEVICE TYPE 300.6 IVM LOCATION 300.7 IVM ADDRESS FILE 300.8 IVM ADJUDICATION LETTERS/FORMS 300.899 IVM CASE ASSIGNMENT 300.9 IVM COUNTY CODES 300.999 IVM CASE STATUS 301.1 DCD FINANCIAL/INCOME TEST DATA 301.11 DCD LETTERS 301.12 IVM BILLING TRANSACTIONS 301.13 IVM ELIGIBILITY THRESHOLDS 301.15 PRIORITIZATION REASONS 301.2 DCD CORRESPONDENCE 301.3 DCD CONTACT REPRESENTATIVE/CASE ASSIGNMENT 301.4 DCD DEPENDENTS STATUS: Active MAIL MESSAGE: 29762115 SUBSCRIBING PACKAGE: INCOME VERIFICATION NAT'L DB NUMBER: 2854 IA #: 2854 FILE NUMBER: 59.7 GLOBAL ROOT: PS(59.7, DATE CREATED: JUN 24, 1999 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2854 ID: PS(59.7, GLOBAL REFERENCE: PS(59.7,D0,90) FIELD NUMBER: 90 FIELD NAME: PSU PBM JOB LOCATION: 90;1 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: PS(59.7,D0,90.01,D1,0) FIELD NUMBER: 90.01 FIELD NAME: PBM AR/WS AOU MAPPING FIELD NUMBER: .01 FIELD NAME: AR/WS AOU LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: DIVISION LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .03 FIELD NAME: OUTPATIENT SITE LOCATION: 0;3 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: PS(59.7,D0,90.02,D1,0) FIELD NUMBER: 90.02 FIELD NAME: PBM CS NAOU MAPPING FIELD NUMBER: .01 FIELD NAME: CS NAOU LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: DIVISION LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .03 FIELD NAME: OUTPATIENT SITE LOCATION: 0;3 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: PS(59.7,D0,90.03,D1,0) FIELD NUMBER: 90.03 FIELD NAME: PBM DA PHARM LOC MAPPING FIELD NUMBER: .01 FIELD NAME: DA PHARMACY LOCATION LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: DIVISION LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .03 FIELD NAME: OUTPATIENT SITE LOCATION: 0;3 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: Pharmacy Benefits Managment requests the usage of the PSU PBM JOB field (#90) in the PHARMACY SYSTEM file (#59.7) for monitoring the status of current and previous extracts of the PSU PBM software. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29764681 KEYWORDS: STATUS PSU SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 2856 IA #: 2856 DATE CREATED: JUN 25, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMA32A NAME: DBIA2856 ID: XMA32A GENERAL DESCRIPTION: AR $Orders thru ^XMB(3.9,"B",XMSUBJ,XMZ) to retrieve mail messages. AR references a messages first line in global ^XMB(3.9,XMZ,2,1,0). AR calls D KILL^XMA32A(XMZ,.XMKILL,XMABORT) to delete a message. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29779597 COMPONENT/ENTRY POINT: KILL COMPONENT DESCRIPTION: This entry point purges a message and all of its responses from the Message file 3.9, and also deletes the message from any user mailboxes in the Mailbox fie 3.7. S XMABORT=0,(XMKILL("MSG"),XMKILL("RESP"))=0,XMZ=msgien D KILL^XMA32A(XMZ,.XMKILL,XMABORT) VARIABLES: XMABORT TYPE: Input VARIABLES DESCRIPTION: Preset to ZERO. VARIABLES: XMKILL(MSG) TYPE: Both VARIABLES DESCRIPTION: Preset to ZERO. (MSG is the subscript) Every time KILL^XMA32A is called to delete a message, it is incremented by 1 by this entry point. VARIABLES: XMKILL(RESP) TYPE: Both VARIABLES DESCRIPTION: Preset to ZERO. (RESP is the subscript) Every time KILL^XMA32A is called, it is incremented by the number of responses purged. VARIABLES: XMZ TYPE: Input VARIABLES DESCRIPTION: Preset XMZ to the message number to be deleted. This message and all response to the message XMZ will be deleted. SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Albany EDITOR: MINARDI,CHRISTOPHER P EDITOR: BEUSCHEL,GARY NUMBER: 2857 IA #: 2857 DATE CREATED: JUN 29, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: XUS GET USER INFO REMOTE PROCEDURE: XUS GET USER INFO CREATOR: FORT,WALLY GENERAL DESCRIPTION: This rpc is used by BROKER to maintain a User object in the Delphi environment. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29789451 SUBSCRIBING PACKAGE: RPC BROKER ISC: Oakland DBA Comments: JSHARVEY 20070329/ ADDING IN VALUE OF 'XUS GET USER INFO' AS THE RPC NAME. 1/31/14 MM: New spreadsheet from Stephen Pelchar on 1/9/14 did not include this RPC. VIA request to be added as a subscriber is withdrawn. DATE/TIME EDITED: MAR 29, 2007@13:22 ACTION: CONTENT CORRECTED AT THE REQUEST OF: HARVEY,JULIE NUMBER: 2858 IA #: 2858 FILE NUMBER: 50 GLOBAL ROOT: PSDRUG DATE CREATED: FEB 17, 2000 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2858 ID: PSDRUG GLOBAL REFERENCE: PSDRUG('AND', GLOBAL REFERENCE: PSDRUG('VAC' GLOBAL REFERENCE: PSDRUG('B' GLOBAL DESCRIPTION: The API OCL^PSOORRL returns a drug which can be an entry in the Drug file or the Pharmacy Orderable item file. We would like to use the "B" cross-reference to determine if the returned drug is from the Drug file or the Pharmacy Orderable item file. GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 29729467 SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING DETAILS: Clinical Reminders supports findings based on VA Drug Class and VA GENERIC. These need to be related to a list of entries in the Drug file #50. NUMBER: 2859 IA #: 2859 FILE NUMBER: 440 GLOBAL ROOT: PRC(440 DATE CREATED: JUL 21, 1999 CUSTODIAL PACKAGE: IFCAP USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TAXID FIELDS IN 440 ID: PRC(440 GLOBAL REFERENCE: PRC(440,DA, FIELD NUMBER: 38 FIELD NAME: TAX ID/SSN LOCATION: 3;8 ACCESS: Read w/Fileman FIELD NUMBER: 39 FIELD NAME: SSN/TAX ID INDICATOR LOCATION: 3;9 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Accounts Receivable needs to pull data from fields 38 and 39 in IFCAP file 440. This is necessary to place the Tax ID number on the TOP (Treasury Offset Program) documents. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29902186 SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE SUBSCRIBING DETAILS: A EN1^DIQ reference is used to pull data from fields 38 and 39 in file 440. This is done in RCTOP1. NUMBER: 2860 IA #: 2860 FILE NUMBER: 3.9 GLOBAL ROOT: XMB(3.9 DATE CREATED: JUL 07, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2860-A ORIGINAL NUMBER: 2860 ID: XMB(3.9 GLOBAL REFERENCE: XMB(3.9,D0,0) FIELD NUMBER: 1.4 FIELD NAME: DATE ENTERED LOCATION: 0;3 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The Radiology/Nuclear Medicine package requests permission to lookup the DATE ENTERED value for a message in file 3.9 of the Mailman package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29822180 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING DETAILS: The DATE ENTERED value will be determined from a GET1^DIQ call. EDITOR: CEBELINSKI,GREGORY NUMBER: 2861 IA #: 2861 FILE NUMBER: 3.6 GLOBAL ROOT: XMB(3.6 DATE CREATED: JUL 07, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2860-B ORIGINAL NUMBER: 2860 ID: XMB(3.6 GLOBAL REFERENCE: XMB(3.6,D0,2,0) FIELD NUMBER: 4 FIELD NAME: MAIL GROUP LOCATION: 2;0 ACCESS: Read w/Fileman GLOBAL REFERENCE: XMB(3.6,'B' FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The Radiology/Nuclear Medicine package requests permission to lookup the IEN of a bulletin and the ien of the mail group that's linked to the same bulletin. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29822253 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING DETAILS: The IEN for the bulletin will be determined from a FIND^DIC call, and the IEN for the mail group will be determined from a GETS^DIQ call. EDITOR: CEBELINSKI,GREGORY NUMBER: 2862 IA #: 2862 FILE NUMBER: 3.8 GLOBAL ROOT: XMB(3.8 DATE CREATED: JUL 07, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2860-C ORIGINAL NUMBER: 2860 ID: XMB(3.8 GLOBAL REFERENCE: XMB(3.8,D0,0) FIELD NUMBER: 4 FIELD NAME: TYPE LOCATION: 0;2 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The Radiology/Nuclear Medicine package requests permission to lookup the type of a mailgroup. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29822290 SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING DETAILS: The type of mail group will be determined from a GET1^DIQ call. The Radiology package can recommend that all its mail groups be made public; however, the site can still change the TYPE of a mail group. If the mail group (that will be sent a message re duplicate addenda) is private, the Radiology package must skip the call to ^XMD, in order to avoid an error which adversely affects the HL7 interface. EDITOR: CEBELINSKI,GREGORY EDITOR: TAYLOR,CAMERON NUMBER: 2863 IA #: 2863 DATE CREATED: JUL 12, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIULE NAME: Calls to TIULE ID: TIULE GENERAL DESCRIPTION: This DBIA documents calls to routine TIULE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30387939 KEYWORDS: PREFERENCES KEYWORDS: PERSONAL COMPONENT/ENTRY POINT: $$PERSPRF(USER) COMPONENT DESCRIPTION: This extrinsic function returns a circumflex-delimited string of personal preferences specified by the user indicated in the formal parameter USER. The return string has the following pieces: '^'-piece Preference ========= ========== 1 (#.01) USER NAME [1P] 2 (#.02) DEFAULT LOCATION [2P] 3 (#.03) REVIEW SCREEN SORT FIELD [3S] 4 (#.04) REVIEW SCREEN SORT ORDER [4S] 5 (#.05) DISPLAY MENUS [5S] 6 (#.06) PATIENT SELECTION PREFERENCE [6S] 7 (#.07) ASK 'Save changes?' AFTER EDIT [7S] 8 (#.08) ASK SUBJECT FOR PROGRESS NOTES [8S] 9 (#.09) DEFAULT COSIGNER [9P] 10 (#.1) NUMBER OF NOTES ON REV SCREEN [10N] 11 (#.11) SUPPRESS REVIEW NOTES PROMPT [11S] 12 (#.12) ASK WORKLOAD ON ALL OP VISITS [12S] Descriptions of these fields can be found in the data dictionary of the TIU PERSONAL PREFERENCES FILE (#8926). 8926. VARIABLES: USER TYPE: Input VARIABLES DESCRIPTION: This is the pointer to the NEW PERSON FILE (#200) for the user in question...Ordinarily, it will be the current user (i.e., DUZ), but in the case where a transcriber is entering a document on another user's behalf, it will be the author of the document being entered. COMPONENT/ENTRY POINT: SETPARM COMPONENT DESCRIPTION: Gets parameters for a user's division. VARIABLES: DUZ(2) TYPE: Input VARIABLES DESCRIPTION: The division associated with the user (system wide KERNEL variable). VARIABLES: TIUPRM0 TYPE: Output VARIABLES DESCRIPTION: 0 node of TIU PARAMETERS file (#8925.99). VARIABLES: TIUPRM1 TYPE: Output VARIABLES DESCRIPTION: 1 node of TIU PARAMETERS file (#8925.99). SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING DETAILS: added 3/24/2008 DATE/TIME EDITED: MAR 24, 2008@16:44 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: THOMAS,KATIE NUMBER: 2864 IA #: 2864 DATE CREATED: JUL 12, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUPP3 NAME: DBIA2864 ID: TIUPP3 GENERAL DESCRIPTION: This call evaluates whether the specified patient has any postings (i.e., (C)risis Notes, Clinical (W)arnings, (A)llergies, or Advanced (D)irectives on file, and returns a list of such documents, including the dates and times on which addenda may have been entered for them. Note that the existence of an Advance Directive posting does NOT necessarily indicate that the patient has an Advance Directive. That an Advance Directive exists can only be determined by reading the text of the 'D' postings, which may (or may not) indicate that a Directive exists, STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29903742 KEYWORDS: POSTINGS KEYWORDS: COVERSHEET COMPONENT/ENTRY POINT: ENCOVER(DFN) COMPONENT DESCRIPTION: This procedure receives the parameter DFN (pointer to PATIENT FILE (#2)), and returns the local variable MSG along with the ^TMP("TIUPPCV",$J) array. The MSG variable is returned as follows: Patient has postings on file: MSG=0^Patient Postings on file Patient DOES NOT have postings on file: MSG=-1^No Patient Postings on file while the ^TMP("TIUPPCV",$J) array looks like this: Patient has postings on file: ^TMP("TIUPPCV",$J,n)=IEN^INDICATOR^PRINT NAME^SUBJECT^DATE/TIME^ADDENDUM where IEN = Internal Entry of the posting in the TIU DOCUMENT FILE (#8925) INDICATOR = C for CRISIS NOTE W for CLINICAL WARNING A for ALLERGY/ADR NOTE D for ADVANCED DIRECTIVE PRINT NAME = the PRINT NAME (#.03) field in file 8925 SUBJECT = the optional Free text subject of the note. DATE/TIME = the Date/time of the note ADDENDUM = indicator of last addendum w/date and time. Patient DOES NOT have postings on file: ^TMP("TIUPPCV",$J) is UNDEFINED. ^TMP("TIUPPCV",$J) may be killed before and after use. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This is the pointer to the PATIENT FILE (#2). SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING DETAILS: Clinical Procedures is using this API to indicate that a directive may exist. They are using it with the understanding that users need to review the note title and text before concluding that a directive in fact exists. SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 3/4/15-MC:Added VPS as a subscriber at the request of Carolyn Wheless and approval of Margy McClenahan for VPS*1*15, planned for release April 2015. DATE/TIME EDITED: MAR 04, 2015@07:04 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 2865 IA #: 2865 DATE CREATED: JUL 12, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUSRVLO NAME: DBIA2865 ID: TIUSRVLO GENERAL DESCRIPTION: This entry point (CONTEXT) allows the calling application to fetch lists of TIU Documents that satisfy various criteria (e.g., All signed, unsigned by author, uncosigned notes, signed by author, signed by date range). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29903746 KEYWORDS: NOTES TAB KEYWORDS: SUMMARIES TAB KEYWORDS: QUERY COMPONENT/ENTRY POINT: CONTEXT(.TIUY,CLASS,CONTEXT,DFN,EARLY,LATE,PERSON,OCCLIM, SEQUENCE,...) COMPONENT DESCRIPTION: Call with: TIUY - RETURN ARRAY pass by reference CLASS - Pointer to TIU DOCUMENT DEFINITION #8925.1 CONTEXT - 1=All Signed (by PT), - 2=Unsigned (by PT&(AUTHOR!TANSCRIBER)) - 3=Uncosigned (by PT&EXPECTED COSIGNER - 4=Signed notes (by PT&selected author) - 5=Signed notes (by PT&date range) DFN - Pointer to Patient (#2) [EARLY] - FM date/time to begin search [LATE] - FM date/time to end search [PERSON] - Pointer to file 200 (DUZ if not passed) [OCCLIM] - Occurrence Limit (optional) [SEQUENCE]- "A"=ascending (Regular date/time) - "D"=descending (Reverse date/time) (dflt) [SHOWADD] - BOOLEAN. Include addenda in the return array, when their parent documents are identified by the search [INCUND] - BOOLEAN. Include Undictated and Untranscribed documents along with Unsigned documents, when the CONTEXT is 2. Returns: ^TMP("TIUR",$J,n)='^'-Delimited records as shown below: "^"-Piece Description ========= =========== 1 DOCUMENT IEN 2 PRINT NAME 3 NOTE DATE/TIME 4 PATIENT NAME_" "_LAST4 5 AUTHOR 6 LOCATION 7 STATUS 8 EPISODE BEGIN DATE/TIME 9 EPISODE END DATE/TIME 10 REQUESTING PACKAGE VARIABLE POINTER 11 IMAGE COUNT 12 SUBJECT 13 HAS CHILDREN 14 IEN OF PARENT DOCUMENT VARIABLES: TIUY TYPE: Input VARIABLES DESCRIPTION: Passed by reference. This is the name of the array in which the data are returned. VARIABLES: CLASS TYPE: Input VARIABLES DESCRIPTION: This is the IEN of the Class of TIU documents for which the user is issuing the query (e.g., PROGRESS NOTES, DISCHARGE SUMMARIES, CONSULTS, etc.). VARIABLES: CONTEXT TYPE: Input VARIABLES DESCRIPTION: Integer code indicating the context of the query, as: - 1=All Signed (by PT), - 2=Unsigned (by PT&(AUTHOR!TANSCRIBER)) - 3=Uncosigned (by PT&EXPECTED COSIGNER - 4=Signed notes (by PT&selected author) - 5=Signed notes (by PT&date range) VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the PATIENT FILE (#2) indicating the patient for whom the user is issuing the query. VARIABLES: EARLY TYPE: Input VARIABLES DESCRIPTION: This is the Date (and time) from which to begin searching for documents that satisfy the other search criteria. VARIABLES: LATE TYPE: Input VARIABLES DESCRIPTION: This is the inclusive upper bound Date (and time) for the search. VARIABLES: PERSON TYPE: Input VARIABLES DESCRIPTION: Optional pointer to file 200 for searches by author (DUZ will be assumed if this parameter is not passed). VARIABLES: OCCLIM TYPE: Input VARIABLES DESCRIPTION: Optional occurrence limit for the search (i.e., the number of documents to return). VARIABLES: SEQUENCE TYPE: Input VARIABLES DESCRIPTION: This is the sequence (i.e., "A"=ascending or "D"=decending) in which the data will be sorted in the return array. VARIABLES: SHOWADD TYPE: Input VARIABLES DESCRIPTION: Optional,determines order of returned documents "A" or "D", where "A"=ascending (Regular date/time) "D"=descending (Reverse date/time) (dflt) VARIABLES: INCUND TYPE: Input VARIABLES DESCRIPTION: Optional. Boolean 1 - Include Undictated and Untranscribed documents along with Unsigned documents, when the CONTEXT is 2. 0 - Don't include them SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD DBA Comments: 6/26/12-mm: VPR added as a subscriber for VPR*1.0. Approved by Joel Russell, Margy McClenehan, and Andrew Bakke. Needed for VistA data extracts. DATE/TIME EDITED: SEP 16, 2010@10:56 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE DATE/TIME EDITED: JUN 26, 2012@14:50 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: MCCLENEHAN,MARGY DATE/TIME EDITED: JUN 26, 2012@14:51 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: RUSSELL,JOEL DATE/TIME EDITED: JUN 26, 2012@14:52 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: BAKKE,ANDREW NUMBER: 2866 IA #: 2866 DATE CREATED: JUL 13, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR DELETE ENTRY REMOTE PROCEDURE: DDR DELETE ENTRY GENERAL DESCRIPTION: The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR DELETE ENTRY remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29852884 KEYWORDS: FMDC KEYWORDS: COMPONENTS KEYWORDS: DDR KEYWORDS: RPC KEYWORDS: DELPHI KEYWORDS: DELETE SUBSCRIBING PACKAGE: FILEMAN DELPHI COMPONENTS ISC: Oakland SUBSCRIBING DETAILS: Access to the DDR DELETE ENTRY rpc. NUMBER: 2867 IA #: 2867 DATE CREATED: JUL 13, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR FILER REMOTE PROCEDURE: DDR FILER GENERAL DESCRIPTION: The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR FILER remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29852884 KEYWORDS: FMDC KEYWORDS: COMPONENTS KEYWORDS: DELPHI KEYWORDS: DDR KEYWORDS: FILER KEYWORDS: RPC SUBSCRIBING PACKAGE: FILEMAN DELPHI COMPONENTS ISC: Oakland SUBSCRIBING DETAILS: Access to the DDR FILER rpc. NUMBER: 2868 IA #: 2868 DATE CREATED: JUL 13, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR FIND1 REMOTE PROCEDURE: DDR FIND1 GENERAL DESCRIPTION: The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR FIND1 remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29852884 KEYWORDS: FMDC KEYWORDS: COMPONENTS KEYWORDS: DELPHI KEYWORDS: RPC KEYWORDS: DDR KEYWORDS: FIND1 SUBSCRIBING PACKAGE: FILEMAN DELPHI COMPONENTS ISC: Oakland SUBSCRIBING DETAILS: Access to DDR FIND1 remote procedure call. NUMBER: 2869 IA #: 2869 DATE CREATED: JUL 13, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR FINDER REMOTE PROCEDURE: DDR FINDER GENERAL DESCRIPTION: The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR FINDER remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29852884 KEYWORDS: FMDC KEYWORDS: COMPONENTS KEYWORDS: DELPHI KEYWORDS: DDR KEYWORDS: FINDER KEYWORDS: RPC SUBSCRIBING PACKAGE: FILEMAN DELPHI COMPONENTS ISC: Oakland SUBSCRIBING DETAILS: Access to the DDR FINDER remote procedure call. NUMBER: 2870 IA #: 2870 DATE CREATED: JUL 13, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR GET DD HELP REMOTE PROCEDURE: DDR GET DD HELP GENERAL DESCRIPTION: The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR GET DD HELP remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29852884 KEYWORDS: FMDC KEYWORDS: COMPONENTS KEYWORDS: DELPHI KEYWORDS: DDR KEYWORDS: HELP KEYWORDS: RPC SUBSCRIBING PACKAGE: FILEMAN DELPHI COMPONENTS ISC: Oakland SUBSCRIBING DETAILS: Access to DDR GET DD HELP remote procedure call. NUMBER: 2871 IA #: 2871 DATE CREATED: JUL 13, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR GETS ENTRY DATA REMOTE PROCEDURE: DDR GETS ENTRY DATA GENERAL DESCRIPTION: The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR GETS ENTRY DATA remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29852884 KEYWORDS: FMDC KEYWORDS: COMPONENTS KEYWORDS: DELPHI KEYWORDS: DDR KEYWORDS: GETS KEYWORDS: RPC SUBSCRIBING PACKAGE: FILEMAN DELPHI COMPONENTS ISC: Oakland SUBSCRIBING DETAILS: Access to DDR GETS ENTRY DATA remote procedure call. NUMBER: 2872 IA #: 2872 DATE CREATED: JUL 13, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR LISTER REMOTE PROCEDURE: DDR LISTER GENERAL DESCRIPTION: The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR LISTER remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29852884 KEYWORDS: FMDC KEYWORDS: COMPONENTS KEYWORDS: DELPHI KEYWORDS: DDR KEYWORDS: LISTER KEYWORDS: RPC SUBSCRIBING PACKAGE: FILEMAN DELPHI COMPONENTS ISC: Oakland SUBSCRIBING DETAILS: Access to DDR LISTER remote procedure call. NUMBER: 2873 IA #: 2873 DATE CREATED: JUL 13, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR LOCK/UNLOCK NODE REMOTE PROCEDURE: DDR LOCK/UNLOCK NODE GENERAL DESCRIPTION: The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR LOCK/UNLOCK NODE remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29852884 KEYWORDS: FMDC KEYWORDS: COMPONENTS KEYWORDS: DELPHI KEYWORDS: DDR KEYWORDS: LOCK KEYWORDS: RPC SUBSCRIBING PACKAGE: FILEMAN DELPHI COMPONENTS ISC: Oakland SUBSCRIBING DETAILS: Access to the DDR LOCK/UNLOCK NODE remote procedure call. NUMBER: 2874 IA #: 2874 DATE CREATED: JUL 13, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR VALIDATOR REMOTE PROCEDURE: DDR VALIDATOR GENERAL DESCRIPTION: The Filemanager Delphi Components (FMDC) package requests a private integration agreement with the FileManager package for access to the DDR VALIDATOR remote procedure call. This request is necessary since FMDC is now a separate package with a different namespace and still needs to access the DDR remote procedure calls which are the basis for the functioning of the FMDC components. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29852884 KEYWORDS: FMDC KEYWORDS: COMPONENTS KEYWORDS: DELPHI KEYWORDS: DDR KEYWORDS: VALIDATOR KEYWORDS: RPC KEYWORDS: VALIDATE SUBSCRIBING PACKAGE: FILEMAN DELPHI COMPONENTS ISC: Oakland SUBSCRIBING DETAILS: Access to the DDR VALIDATOR remote procedure call. NUMBER: 2875 IA #: 2875 FILE NUMBER: 601 GLOBAL ROOT: YTT(601 DATE CREATED: JUL 14, 1999 CUSTODIAL PACKAGE: MENTAL HEALTH CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2875 ID: YTT(601 GLOBAL REFERENCE: YTT(601,D0,"S", FIELD NUMBER: .01 FIELD NAME: SCALE NUMBER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .5 FIELD NAME: SCALE NAME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: YTT(601, FIELD NUMBER: .01 FIELD NAME: NAME ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Clinical Reminders would like to be able to read the name of the Mental Instrument to setup the call the LISTONE^YSAPI API and to be able to display the name in the Clinical Maintenance component. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29815988 SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING DETAILS: In order to support Mental Instruments as a findings type Clinical Reminders needs read access to the following globals. NUMBER: 2876 IA #: 2876 DATE CREATED: JUL 21, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUSRVD NAME: DBIA2876 ID: TIUSRVD GENERAL DESCRIPTION: APIs for Document Definition File (#8925.1) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29903766 COMPONENT/ENTRY POINT: BLRPLT COMPONENT DESCRIPTION: The procedure BLRPLT^TIUSRVD may be called with the following parameters, to resolve any TIU OBJECTS embedded in boilerplate text (i.e., pre-defined word-processing forms), regardless of the location of that text in DHCP: D BLRPLT^TIUSRVD(.TIUY,TITLE,DFN,VSTR,ROOT) VARIABLES: TIUY TYPE: Output VARIABLES DESCRIPTION: TIUY is passed by reference, and is returned as the name of the array in which the results are available (i.e., ^TMP("TIUBOIL",$J)). VARIABLES: TITLE TYPE: Input VARIABLES DESCRIPTION: This is the OPTIONAL pointer to the TIU DOCUMENT DEFINITION file (#8925.1) where the boilerplate text is defined for boilerplated TITLES in TIU. Applications which define their boilerplates outside of the TIU DOCUMENT DEFINITION File should pass this as a NULL string. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This is the pointer to the patient in the PATIENT FILE (#2). VARIABLES: VSTR TYPE: Input VARIABLES DESCRIPTION: This is the VISIT STRING, which together with DFN defines the patient's encounter in terms of place and time. It is formatted as follows: ;; VARIABLES: ROOT TYPE: Input VARIABLES DESCRIPTION: This is the closed root reference to the array where the boilerplate to be resolved is to be found. It may be either an M global or local variable name (glvn). Examples might have the format: ROOT="^ORD(101.41,1263,6,4,2)" in the event that an Order Dialog entry #1263 included boilerplate text defined in its TEXT Field, or ROOT="BPTEXT(""DATA"")" in the event that a local array contained the data to be resolved. COMPONENT/ENTRY POINT: CNSLCLAS COMPONENT DESCRIPTION: Gets the IEN for entry CLINICAL PROCEDURES in the TIU Document Definition file (#8925.1) VARIABLES: Y TYPE: Both VARIABLES DESCRIPTION: Returns either the Consults class IEN in the TIU Document file (#8925.1) or 0. COMPONENT/ENTRY POINT: SURGCLAS(Y,CLNAME) COMPONENT DESCRIPTION: Gets the record number of the class identified by the CLNAME parameter in the TIU DOCUMENT DEFINITION file (#8925.1). VARIABLES: Y TYPE: Both VARIABLES DESCRIPTION: Returns either the record number of the class identified by the CLNAME parameter in the TIU DOCUMENT DEFINITION file (#8925.1), or 0. VARIABLES: CLNAME TYPE: Input VARIABLES DESCRIPTION: CLNAME = "SURGICAL REPORTS" or "PROCEDURE REPORTS (NON-O.R.)" COMPONENT/ENTRY POINT: LONGLIST(Y,CLASS,FROM,DIR,IDNOTE) COMPONENT DESCRIPTION: Gets the active titles which the current user is authorized to enter notes under, for a particular class in the TIU DOCUMENT DEFINITION file (#8925.1). VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: This is an array of the 44 titles nearest to the title name or text indicated in FROM, in the direction DIR. Array entries have form Y(n)=DA^TitleName VARIABLES: CLASS TYPE: Input VARIABLES DESCRIPTION: This is a pointer to the CLASS in the Document Definition File (#8925.1) from which the application intends to allow selection of TITLES. VARIABLES: FROM TYPE: Input VARIABLES DESCRIPTION: This is the name of the reference title from which the longlist is scrolling (or the text to $ORDER from). VARIABLES: DIR TYPE: Input VARIABLES DESCRIPTION: This is the direction in which the longlist is scrolling from the reference title, i.e., the $ORDER direction. VARIABLES: IDNOTE TYPE: Input VARIABLES DESCRIPTION: This BOOLEAN Flag should be passed when the call is being made to select a title for an Interdisciplinary Entry. SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING DETAILS: ADDED 8/26/09 DATE/TIME EDITED: AUG 26, 2009@08:37 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: JACKSON,TODD WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 2877 IA #: 2877 DATE CREATED: DEC 06, 1999 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RAO7PC3 NAME: DBIA2877 ID: RAO7PC3 GENERAL DESCRIPTION: Either EN3^RAO7PC3 or EN30^RAO7PC3 can be used to return an entire Radiology/NM report, the same report that is automatically e-mailed to the requesting physician when a report has been verified. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31070186 KEYWORDS: Radiology/NM report COMPONENT/ENTRY POINT: EN3(X) COMPONENT DESCRIPTION: Returns: ^TMP($J,"RAE3",Patient IEN,Case IEN,Procedure Name,n)=line n of report The first line of the report passes the patient name (truncated to 20 chars max), the SSN, and the age of the patient (at the time the software is executed). Example: ^TMP(539390038,"RAE3",21,1,"CHEST 2 VIEWS PA&LAT",1) = OUTPATIENT,SIXTEEN B 000-00-0000 72 yr. old male Subscripts ---------- Patient ien: Internal entry number of the patient in both the Rad/Nuc Med Patient file #70 and the Patient file #2. Case IEN: Internal entry number of the exam that this date is extracted from. Procedure Name: Name of the procedure in the Rad/Nuc Med Procedure file #71. It is possible for users to change the procedure prior to the exam reaching a 'COMPLETE' status. n: sequential number that corresponds to the nth line of the report from Radiology/NM. Additional output ----------------- For subscript definitions, check the section called 'subscripts' listed above. ^TMP($J,"RAE3",Patient IEN,"PRINT_SET") Array Value ----------- Null (exists if and only if this is a printset). ^TMP($J,"RAE3",Patient IEN,"ORD") Array Value ----------- Name of ordered procedure for examsets and printsets. ^TMP($J,"RAE3",Patient IEN,"ORD",Case IEN) Array Value ----------- Name of ordered procedure, this may differ from the procedure registered. This global will be defined when the ordered procedure is not a parent procedure. (Not an examset or printset). VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: X can be either: Patient's DFN^inverse exam date^Case IEN -or- Patient's DFN^inverse exam date^ The first will retrieve a single report for a single exam. The second will retrieve all reports for a set of exams that were ordered on the same order. COMPONENT/ENTRY POINT: EN30(X) COMPONENT DESCRIPTION: Returns: ^TMP($J,"RAE3",Patient IEN,Case IEN,Procedure Name,n)=line n of report Subscripts ---------- Patient ien: Internal entry number of the patient in both the Rad/Nuc Med Patient file #70 and the Patient file #2. Case IEN: Internal entry number of the exam that this date is extracted from. Procedure Name: Name of the procedure in the Rad/Nuc Med Procedure file #71. It is possible for users to change the procedure prior to the exam reaching a 'COMPLETE' status. n: sequential number that corresponds to the nth line of the report from Radiology/NM. Additional output ----------------- For subscript definitions, check the section called 'subscripts' listed above. ^TMP($J,"RAE3",Patient IEN,"PRINT_SET") Array Value ----------- Null (exists if and only if this is a printset). ^TMP($J,"RAE3",Patient IEN,"ORD") Array Value ----------- Name of ordered procedure for examsets and printsets. ^TMP($J,"RAE3",Patient IEN,"ORD",Case IEN) Array Value ----------- Name of ordered procedure, this may differ from the procedure registered. This global will be defined when the ordered procedure is not a parent procedure. (Not an examset or printset). VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: X is the internal entry number (ien) of the record in the RAD/NUC MED REPORTS (#74) file. NUMBER: 2878 IA #: 2878 GLOBAL ROOT: DD(6926.01,.01,1 DATE CREATED: JUL 28, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DELETE TRIGGER X-REF IN FILE 6926.01 FIELD .01 ID: DD(6926.01,.01,1 GENERAL DESCRIPTION: This IA permits patch EN*7*62 to delete the TRIGGER cross-reference (#2) of field #.01 in subfile #6926.01. Code similar to the following will be placed in a pre-install routine of the patch to perform the deletion. N DA,DIK S DIK="^DD(6926.01,.01,1," ;this is the root of "xref multiple" S DA(2)=6926.01,DA(1)=.01,DA=2 ;DA(2) = subfile# ;DA(1) = field# ;DA = xref# D ^DIK ;this deletes the xref definition Patch EN*7*62 will bring in a new #2 cross-reference (regular, whole-file) on the .01 field of #6926.01 during the install. The cross-reference deletion performed during the pre-install will ensure that all the trigger logic is completely removed. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29934856 SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring NUMBER: 2879 IA #: 2879 FILE NUMBER: 51.1 GLOBAL ROOT: PS(51.1, DATE CREATED: JUL 28, 1999 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2879 ID: PS(51.1, GLOBAL REFERENCE: PS(51.1, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Direct global read access to the "B" x-ref is also allowed. FIELD NUMBER: 2 FIELD NAME: FREQUENCY (IN MINUTES) LOCATION: 0;3 ACCESS: Read w/Fileman STATUS: Active MAIL MESSAGE: 32577555 KEYWORDS: BCMA SUBSCRIBING PACKAGE: BAR CODE MED ADMIN NUMBER: 2880 IA #: 2880 FILE NUMBER: 50.7 GLOBAL ROOT: PS(50.7, DATE CREATED: JUL 28, 1999 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2880 ID: PS(50.7, GLOBAL REFERENCE: PS(50.7, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active MAIL MESSAGE: 29934782 KEYWORDS: BCMA SUBSCRIBING PACKAGE: BAR CODE MED ADMIN NUMBER: 2882 IA #: 2882 DATE CREATED: AUG 04, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUSRB NAME: DBIA2882 ID: XUSRB GENERAL DESCRIPTION: XUSRB contains some API's that can be used by other application to check user access. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32039999 COMPONENT/ENTRY POINT: $$CHECKAV COMPONENT DESCRIPTION: This API will check a Access/Verify code pair and return if it is valid. The call is S X=$CHECKVA() The is the users . The return is the users IEN if the codes were OK, or zero otherwise. SUBSCRIBING PACKAGE: BAR CODE MED ADMIN ISC: Birmingham SUBSCRIBING PACKAGE: JAL FEDERAL HEALTH CARE CENTER SUBSCRIBING DETAILS: 20110303 JSHARVEY - JAL ADDED AS SUBSCRIBER DATE/TIME EDITED: MAR 03, 2011@17:24 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: GRIBSCHAW,STEPHEN WITH CONCURRENCE OF: IVEY,JOEL NUMBER: 2883 IA #: 2883 FILE NUMBER: 727.5 GLOBAL ROOT: ECX(727.5, DATE CREATED: AUG 10, 1999 CUSTODIAL PACKAGE: DSS EXTRACTS CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2883 ID: ECX(727.5, GLOBAL REFERENCE: ECX(727.5, GLOBAL DESCRIPTION: Direct read of cross-references only -- ^ECX(727.5,"B", ^ECX(727.5,"AC", ^ECX(727.5,"AX", GENERAL DESCRIPTION: The purpose of DBIA #2883 is to allow the VistA Mental Health package to perform direct global reads on the DSS MH TESTS file (#727.5). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29993396 SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas SUBSCRIBING DETAILS: The Mental Health package will perform direct global reads from the DSS MH TESTS file (#727.5). These direct reads are used only within the routine YSDSS, which has been designed for use as an interface between DSS Extracts and Mental Health. Direct global reads are done on three cross-references in file #727.5: (1) "B" cross-reference - whole file index on the TEST NAME field (#.01). (2) "AC" cross-reference - whole file index on the ACTIVATION DATE sub-field (#.01) of the ACTIVATION DATE multiple field (#1). (3) "AX" cross-reference - whole file index on the INACTIVATION DATE sub-field (#.02) of the ACTIVATION DATE multiple field (#1). NUMBER: 2884 IA #: 2884 DATE CREATED: AUG 10, 1999 CUSTODIAL PACKAGE: MENTAL HEALTH CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: YSDSS NAME: DBIA2884 ID: YSDSS GENERAL DESCRIPTION: The purpose of DBIA #2884 is to allow the VistA DSS Extracts package to call routine YSDSS at tag UPD. The call to UPD^YSDSS will return Mental Health data to be placed in the DSS Mental Health extract. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29993391 COMPONENT/ENTRY POINT: UPD COMPONENT DESCRIPTION: Subroutine UPD in YSDSS must be called with parameters as follows: UPD(YSFILE,YSFRN,YSYRMO,YSEXTN,YSSITE,YSSD,YSEND,YSERR), where YSFILE - MENTAL HEALTH EXTRACT file # (required) YSFRN - last IEN used in the MENTAL HEALTH EXTRACT file (required) YSYRMO - YearMonth of the extract (YYYYMM) (required) YSEXTN - Extract # (required) YSSITE - Facility identifier (required) YSSD - Start date for extract (required) YSEND - End date for extract (required) YSERR - passed by reference; returnes "1", if error; otherwise "0" VARIABLES: YSFILE TYPE: Input VARIABLES DESCRIPTION: This is the file number for the DSS Mental Health extract file. VARIABLES: YSFRN TYPE: Both VARIABLES DESCRIPTION: Input: This is the last internal record number used in the Mental Health extract file before the current extract. Output: This is the last internal record number used for the current Mental Health extract. VARIABLES: YSYRMO TYPE: Input VARIABLES DESCRIPTION: A 6-digit numeric of format YYYYMM. VARIABLES: YSEXTN TYPE: Input VARIABLES DESCRIPTION: The unique extract number for the current Mental Health extract. VARIABLES: YSSITE TYPE: Input VARIABLES DESCRIPTION: May be numeric or alpha-numeric; the Station Number of the facility performing the Mental Health extract. VARIABLES: YSSD TYPE: Input VARIABLES DESCRIPTION: The start date for the data extraction process in standard FileMan internal format. VARIABLES: YSEND TYPE: Input VARIABLES DESCRIPTION: The ending date for the data extracttion process in standard FileMan internal format. VARIABLES: YSERR TYPE: Output VARIABLES DESCRIPTION: Returns "0" if no problems were encountered which would cause the extraction process to abort. Returns "1" if some problem is found which prevents the extraction process from occurring; e.g., missing files. SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany SUBSCRIBING DETAILS: VistA DSS Extracts will call UPD^YSDSS exclusively from routine ECXMTL, which is the DSS Mental Health extract routine. NUMBER: 2885 IA #: 2885 FILE NUMBER: 727.812 GLOBAL ROOT: ECX(727.812, DATE CREATED: AUG 10, 1999 CUSTODIAL PACKAGE: DSS EXTRACTS CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2885 ID: ECX(727.812, GLOBAL REFERENCE: ECX(727.812,DO,0) FIELD NUMBER: .01 FIELD NAME: SEQUENCE NUMBER LOCATION: 1 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: A sequential number for this extract record. It is used to DUNUM the file; i.e., internal entry number is the value of the .01 field. FIELD NUMBER: 1 FIELD NAME: YEAR MONTH LOCATION: 2 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: The year and month for which data is being extracted from the Mental Health files. This is a 6-digit numeric of format YYYYMM. FIELD NUMBER: 2 FIELD NAME: EXTRACT NUMBER LOCATION: 3 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: This is the unique number which identifies this specific extract. FIELD NUMBER: 3 FIELD NAME: FACILITY LOCATION: 4 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: The Station Number for the facility performing the extract. FIELD NUMBER: 4 FIELD NAME: PATIENT NO. - DFN LOCATION: 5 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: The internal entry number in the PATIENT file (#2) for the patient associated with the Mental Health data. FIELD NUMBER: 8 FIELD NAME: DAY LOCATION: 9 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: This is the date associated with the Mental Health data. Data is initially placed here in the usual FileMan internal date format. It is later converted by the DSS Extracts package to an 8-digit numeric of format YYYYMMDD. FIELD NUMBER: 17 FIELD NAME: PROVIDER LOCATION: 18 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: This is the value of the pointer to the NEW PERSON file (#200) for the Provider associated with the Mental Health data. FIELD NUMBER: 20 FIELD NAME: TEST NAME LOCATION: 21 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: This is the name of the Mental Health test for which data is being extracted. This may be "ASI", "GAF", or one of several tests in the MH INSTRUMENT file (#601). FIELD NUMBER: 21 FIELD NAME: TEST IEN LOCATION: 22 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: The internal entry number in the MH INSTRUMENT file (#601) of the test. FIELD NUMBER: 22 FIELD NAME: SCALE NUMBER LOCATION: 23 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: If the Mental Health test is described by a series of scales, the Scale Number is placed here. FIELD NUMBER: 23 FIELD NAME: SCALE NAME LOCATION: 24 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: If the Mental Health test is described by a series of scales, the Scale Name is placed here. FIELD NUMBER: 24 FIELD NAME: TEST SCORE LOCATION: 25 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: The patient's overall numeric score for the Mental Health test. FIELD NUMBER: 25 FIELD NAME: SCALE SCORE LOCATION: 26 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: The patient's subscore on the specific scale, if the test is described in terms of several scales. GLOBAL DESCRIPTION: This is the 0-node of the extract record for the Mental Health extract. There are a total of twenty-eight data elements stored at this location. GLOBAL REFERENCE: ECX(727.812,D0,1) FIELD NUMBER: 32 FIELD NAME: CLASS FOR ASI LOCATION: 5 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: If the test associated with the Mental Health data is ASI, then this field is its classification code: 1 = FULL 2 = LITE 3 = FOLLOW-UP FIELD NUMBER: 33 FIELD NAME: SPECIAL FOR ASI LOCATION: 6 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: If the test associated with the Mental Health data is ASI, then this field is its completion code: 1 = PATIENT TERMINATED 2 = PATIENT REFUSED 3 = UNABLE TO RESPOND N = INTERVIEW COMPLETED GLOBAL DESCRIPTION: This is the 1-node of the extract record for the Mental Health extract. There are a total of six data elements stored at this location. GENERAL DESCRIPTION: The purpose of DBIA #2885 is to allow the VistA Mental Health package to place data directly into the ^ECX(727.812, global. This global is the storage location of the DSS MENTAL HEALTH EXTRACT file (#727.812). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29993395 SUBSCRIBING PACKAGE: MENTAL HEALTH ISC: Dallas SUBSCRIBING DETAILS: VistA Mental Health will place data into the MENTAL HEALTH EXTRACT file (#727.812) using direct global writes. This will occur from within the YSDSS routine, which is the interface between DSS Extracts and the Mental Health packages for the purpose of extracting Mental Health data. Data will be placed in the following locations: (1) ^ECX(727.812,D0,0) - piece 1 - field #.01 (SEQUENCE NUMBER) (2) ^ECX(727.812,D0,0) - piece 2 - field #1 (YEAR MONTH) (3) ^ECX(727.812,D),0) - piece 3 - field #2 (EXTRACT NUMBER) (4) ^ECX(727.812,D0,0) - piece 4 - field #4 (FACILITY) (5) ^ECX(727.812,D0,0) - piece 9 - field #8 (DAY) (6) ^ECX(727.812,D0,0) - piece 18 - field #17 (PROVIDER) (7) ^ECX(727.812,D0,0) - piece 21 - field #20 (TEST NAME) (8) ^ECX(727.812,D0,0) - piece 22 - field #21 (TEST IEN) (9) ^ECX(727.812,D0,0) - piece 23 - field #22 (SCALE NUMBER) (10) ^ECX(727.812,D0,0) - piece 24 - field #23 (SCALE NAME) (11) ^ECX(727.812,D0,0) - piece 25 - field #24 (TEST SCORE) (12) ^ECX(727.812,D0,1) - piece 5 - field #32 (CLASS FOR ASI) (13) ^ECX(727.812,D0,1) - piece 6 - field #33 (SPECIAL FOR ASI) NUMBER: 2887 IA #: 2887 DATE CREATED: SEP 30, 2003 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: HLCS2 NAME: Application Parameter Inquire ID: HLCS2 GENERAL DESCRIPTION: This public API returns the Mail Group and the "active/inactive" flag for an HL7 Application. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 37264429 KEYWORDS: HL7 KEYWORDS: MESSAGING COMPONENT/ENTRY POINT: $$GETAPP(HLAPP) COMPONENT DESCRIPTION: Returns: MAIL GROUP NAME^'a' or 'i' (active or inactive) VARIABLES: HLAPP TYPE: Input VARIABLES DESCRIPTION: APPLICATION NAME OR IEN OF FILE 771 NUMBER: 2888 IA #: 2888 FILE NUMBER: 165.5 GLOBAL ROOT: ONCO(165.5, DATE CREATED: AUG 13, 1999 CUSTODIAL PACKAGE: ONCOLOGY CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2888 ID: ONCO(165.5, GLOBAL REFERENCE: ONCO(165.5,D0,0) FIELD NUMBER: 3 FIELD NAME: DATE DX LOCATION: 0;16 ACCESS: Read w/Fileman FIELD DESCRIPTION: The diagnosis date refers to the first diagnosis of this cancer by any recognized medical practitioner. GLOBAL REFERENCE: ONCO(165.5,D0,2) FIELD NUMBER: 20 FIELD NAME: ICDO-TOPOGRAPHY LOCATION: 2;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: The Topography section of the International Classification of Diseases for Oncology (ICD-O, 1990) is used for coding the Primary Site of all cancers reported to SEER. FIELD NUMBER: 22 FIELD NAME: HISTOLOGY LOCATION: 2;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: Histology is a six-digit code consisting of three parts: A Histologic type (4 digits) B Behavior (1 digit) C Grading or differentiation; or for lymphomas and leukemias designation of T-cell, B-cell, and null cell (1 digit) FIELD NUMBER: 24 FIELD NAME: GRADE/DIFFERENTIATION LOCATION: 2;5 ACCESS: Read w/Fileman FIELD DESCRIPTION: "Grade or Differentiation" of the tumor describes the tumor's resemblance to normal tissue. Well differentiated (grade I) is the most like normal tissue. FIELD NUMBER: 29 FIELD NAME: SIZE OF TUMOR LOCATION: 2;9 ACCESS: Read w/Fileman FIELD DESCRIPTION: SIZE OF TUMOR is the largest dimension, or the diameter of the primary tumor, and is always recorded in millimeters. FIELD NUMBER: 38 FIELD NAME: CLINICAL STAGE GROUP LOCATION: 2;20 ACCESS: Read w/Fileman FIELD DESCRIPTION: CLINICAL STAGE GROUP defines the anatomic extent of disease based on the previously coded T, N, and M elements. FIELD NUMBER: 37.1 FIELD NAME: CLINICAL T LOCATION: 2;25 ACCESS: Read w/Fileman FIELD DESCRIPTION: CLINICAL T evaluates the primary tumor and reflects tumor size and/or extension. FIELD NUMBER: 37.2 FIELD NAME: CLINICAL N LOCATION: 2;26 ACCESS: Read w/Fileman FIELD DESCRIPTION: CLINICAL N identifies the absence or presence of regional lymph node metastases and describes the extent of regional lymph node metastases. FIELD NUMBER: 37.3 FIELD NAME: CLINICAL M LOCATION: 2;27 ACCESS: Read w/Fileman FIELD DESCRIPTION: CLINCIAL M records the presence or absence of distant metastases. GLOBAL REFERENCE: ONCO(165.5,D0,2.1) FIELD NUMBER: 85 FIELD NAME: PATHOLOGIC T LOCATION: 2.1;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: PATHOLOGIC T evaluates the primary tumor and identifies tumor size and/or extension. FIELD NUMBER: 86 FIELD NAME: PATHOLOGIC N LOCATION: 2.1;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: PATHOLOGIC N identifies the absence or presence of regional lymph node metastases and describes the extent of regional lymph node metastases. FIELD NUMBER: 87 FIELD NAME: PATHOLOGIC M LOCATION: 2.1;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: PATHOLOGIC M records the presence or absence of distant metastases. FIELD NUMBER: 88 FIELD NAME: PATHOLOGIC STAGE GROUP LOCATION: 2.1;4 ACCESS: Read w/Fileman FIELD DESCRIPTION: PATHOLOGIC STAGE GROUP defines the anatomic extent of disease based on the T, N, and M elements. GLOBAL REFERENCE: ONCO(165.5,D0,3) FIELD NUMBER: 50 FIELD NAME: SURGERY OF PRIMARY SITE DATE LOCATION: 3;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: SURGERY OF PRIMARY SITE DATE is the date that cancer-directed surgery was performed. FIELD NUMBER: 51 FIELD NAME: RADIATION DATE LOCATION: 3;4 ACCESS: Read w/Fileman FIELD DESCRIPTION: RADIATION DATE is the date the first course of radiation therapy was started. FIELD NUMBER: 51.2 FIELD NAME: RADIATION LOCATION: 3;6 ACCESS: Read w/Fileman FIELD DESCRIPTION: RADIATION is the type of radiation administered to the primary site or any metastatic site. FIELD NUMBER: 53 FIELD NAME: CHEMOTHERAPY DATE LOCATION: 3;11 ACCESS: Read w/Fileman FIELD DESCRIPTION: CHEMOTHERAPY DATE is the date the first course of chemotherapy was started. FIELD NUMBER: 53.2 FIELD NAME: CHEMOTHERAPY LOCATION: 3;13 ACCESS: Read w/Fileman FIELD DESCRIPTION: CHEMOTHERAPY is the type of chemotherapy administered as the first course of treatment. FIELD NUMBER: 54 FIELD NAME: HORMONE THERAPY DATE LOCATION: 3;14 ACCESS: Read w/Fileman FIELD DESCRIPTION: HORMONE THERAPY DATE is the date hormone therapy was started. FIELD NUMBER: 54.2 FIELD NAME: HORMONE THERAPY LOCATION: 3;16 ACCESS: Read w/Fileman FIELD DESCRIPTION: HORMONE THERAPY is the type of hormone therapy the patient received as part of the first course of treatment. FIELD NUMBER: 55 FIELD NAME: IMMUNOTHERAPY DATE LOCATION: 3;17 ACCESS: Read w/Fileman FIELD DESCRIPTION: IMMUNOTHERAPY DATE is the date immunotherapy was started. FIELD NUMBER: 55.2 FIELD NAME: IMMUNOTHERAPY (BRM) LOCATION: 3;19 ACCESS: Read w/Fileman FIELD DESCRIPTION: IMMUNOTHERAPY (BRM) is the type of immunotherapy the patient received as part of the first course of treatment. FIELD NUMBER: 125 FIELD NAME: RADIATION TREATMENT VOLUME LOCATION: 3;21 ACCESS: Read w/Fileman FIELD DESCRIPTION: RADIATION TREATMENT VOLUME is intended primarily to provide a simple expression of the most common radiation volumes treated. FIELD NUMBER: 58.1 FIELD NAME: NON CANCER-DIRECTED SURGERY LOCATION: 3;27 ACCESS: Read w/Fileman FIELD DESCRIPTION: NON CANCER-DIRECTED SURGERY is a surgical procedure performed to diagnose/stage disease (exploratory) or for relief of symptoms (palliative). FIELD NUMBER: 127 FIELD NAME: INTENT OF RADIATION LOCATION: 3;29 ACCESS: Read w/Fileman FIELD DESCRIPTION: INTENT OF RADIATION is the intent of the radiation treatment. This item is useful in assessing the appropriateness of the treatment and correlating the outcome with the original intent of the treatment. FIELD NUMBER: 58.3 FIELD NAME: NON CANCER-DIRECTED SURG DATE LOCATION: 3;31 ACCESS: Read w/Fileman FIELD DESCRIPTION: NON CANCER-DIRECTED SURG DATE is the date that non cancer-directed surgery was performed. FIELD NUMBER: 58.2 FIELD NAME: SURGERY OF PRIMARY SITE LOCATION: 3;38 ACCESS: Read w/Fileman FIELD DESCRIPTION: SURGERY OF PRIMARY SITE modifies, controls, removes, or destroys proliferating cancer tissue. FIELD NUMBER: 128 FIELD NAME: RADIATION COMPLETION STATUS LOCATION: 3;39 ACCESS: Read w/Fileman FIELD DESCRIPTION: RADIATION COMPLETION STATUS indicates whether the patient's radiation therapy was completed as outlined in the initial treatment plan. GLOBAL REFERENCE: ONCO(165.5,D0,7) FIELD NUMBER: 91 FIELD NAME: ABSTRACT STATUS LOCATION: 7;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: ABSTRACT STATUS is the status of the abstract data entry. GLOBAL REFERENCE: ONCO(165.5,D0,'BLA2') FIELD NUMBER: 346 FIELD NAME: PROTOCOL ELIGIBILITY STATUS LOCATION: BLA2;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: PROTOCOL ELIGIBILITY STATUS is the eligibility status of the patient to be entered into a protocol. GLOBAL REFERENCE: ONCO(165.5,D0,'STS2') FIELD NUMBER: 560 FIELD NAME: PROTOCOL PARTICIPATION LOCATION: STS2;31 ACCESS: Read w/Fileman FIELD DESCRIPTION: PROTOCOL PARTICIPATION records whether the patient was enrolled in and treated on a protocol. GLOBAL REFERENCE: ONCO(165.5,D0,'THY1') FIELD NUMBER: 442 FIELD NAME: REGIONAL DOSE:cGy LOCATION: THY1;43 ACCESS: Read w/Fileman FIELD DESCRIPTION: REGIONAL DOSE:cGy is used to code the dominant or most clinically significant dose delivered. GENERAL DESCRIPTION: The Health Summary package has permission to extract and display the following data from the ONCOLOGY PRIMARY (165.5) file: 3 DATE DX 20 ICDO-TOPOGRAPHY 22 HISTOLOGY 24 GRADE/DIFFERENTIATION 29 SIZE OF TUMOR 37.1 CLINICAL T 37.2 CLINICAL N 37.3 CLINICAL M 38 CLINICAL STAGE GROUP 85 PATHOLOGIC T 86 PATHOLOGIC N 87 PATHOLOGIC M 88 PATHOLOGIC STAGE GROUP 58.1 NON CANCER-DIRECTED SURGERY 58.3 NON CANCER-DIRECTED SURG DATE 58.2 SURGERY OF PRIMARY SITE 50 SURGERY OF PRIMARY SITE DATE 51.2 RADIATION 51 RADIATION DATE 442 REGIONAL DOSE:cGy 125 RADIATION TREATMENT VOLUME 127 INTENT OF RADIATION 128 RADIATION COMPLETION STATUS 53.2 CHEMOTHERAPY 53 CHEMOTHERAPY DATE 54.2 HORMONE THERAPY 54 HORMONE THERAPY DATE 55.2 IMMUNOTHERAPY (BRM) 55 IMMUNOTHERAPY DATE 346 PROTOCOL ELIGIBILITY STATUS 560 PROTOCOL PARTICIPATION 91 ABSTRACT STATUS STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30027134 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 2889 IA #: 2889 DATE CREATED: AUG 16, 1999 CUSTODIAL PACKAGE: MENTAL HEALTH CUSTODIAL ISC: Dallas USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: YTAPI NAME: DBIA2889 ID: YTAPI STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30016969 COMPONENT/ENTRY POINT: LISTALL COMPONENT DESCRIPTION: This API returns all psychological test administrations for a specified patient during a specified time period. No scoring is returned. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal Entry number for patient name in the PATIENT file (#2). VARIABLES: BEGIN TYPE: Input VARIABLES DESCRIPTION: Inclusive date in %DT acceptable format (11/11/2011) to begin search [optional]. Example: YS("BEGIN")="10/01/89" VARIABLES: END TYPE: Input VARIABLES DESCRIPTION: Inclusive date in %DT acceptable format (11/11/2011) to end search [optional]. Example: YS("END")="11/11/2011" VARIABLES: YSDATA TYPE: Output VARIABLES DESCRIPTION: Array= internal administration date^external administration date^test code Data is sorted in order of most recent administration to the oldest administration. If no administrations are found Array(2) will not be returned. If patient has no If patient has no PSYCH INSTRUMENT PATIENT file (#601.2) data, Array(1) will return [ERROR] with an explanation. Example: YSDATA(1)=[DATA] YSDATA(2)=2901120^11/20/1990^AOR YSDATA(3)=2900730^07/30/1990^ALCO YSDATA(4)=2900730^07/30/1990^HX2 YSDATA(5)= 2900730^07/30/1990^MROS YSDATA(6)= 2900730^07/30/1990^PSOC YSDATA(7)= 2900730^07/30/1990^TRMT COMPONENT/ENTRY POINT: LISTONE COMPONENT DESCRIPTION: This API returns all psychological test administrations for a specified patient during a specified time period for a specified test. If a scale is also specified, scoring for that scale is returned. User must have adequate privileges to receive this information (i.e. often the YSP KEY). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This is the Patient's name, a pointer value to the Patient file #2. VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: Test code from the MH INSTRUMENT file (#601) or "ASI" e.g. "CAGE", "BDI". VARIABLES: BEGIN TYPE: Input VARIABLES DESCRIPTION: Inclusive date in %DT acceptable format (11/11/2011) to begin search [optional]. VARIABLES: END TYPE: Input VARIABLES DESCRIPTION: Inclusive date in %DT acceptable format (11/11/2011) to end search [optional]. VARIABLES: LIMIT TYPE: Input VARIABLES DESCRIPTION: Constrains to the last N administrations [optional] VARIABLES: SCALE TYPE: Input VARIABLES DESCRIPTION: Scale number from the MH INSTRUMENT file (#601) or 1-7 on ASI [optional] VARIABLES: YSDATA TYPE: Output VARIABLES DESCRIPTION: Array= internal administration date ^ external administration date^test code [^scale name^raw score^transformed score] Data is sorted in order of most recent administration to the oldest administration. If no administrations are found Array(2) will not be returned. If patient has no PSYCH INSTRUMENT PATIENT file (#601.2) data, Array(1) will return [ERROR] with an explanation. EXAMPLE: Input ----- YS("DFN")=83 YS("CODE")=MMPI2 YS("SCALE")=2 Output ------ YSDATA(1)=[DATA] YSDATA(2)=2940509^05/09/1994^MMPI2^F Infrequency^19^95 YSDATA(3)=2920925^09/25/1992^MMPI2^F Infrequency^26^116 YSDATA(4)=2920924^09/24/1992^MMPI2^F Infrequency^25^113 NUMBER: 2891 IA #: 2891 DATE CREATED: AUG 19, 1999 CUSTODIAL PACKAGE: MENTAL HEALTH CUSTODIAL ISC: Dallas USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: YTAPI2 NAME: DBIA2891 ID: YTAPI2 GENERAL DESCRIPTION: This API returns all scoring information for a specified patient given a specified administration date for a specified test or instrument. User must have adequate privileges to receive this information (i.e. often the YSP KEY). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30031659 COMPONENT/ENTRY POINT: SCOREIT VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient internal identifier VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: Test code from MH INSTRUMENT file (#601) or "ASI" (e.g. "CAGE", "BDI") VARIABLES: ADATE TYPE: Input VARIABLES DESCRIPTION: Inclusive administration date in %DT acceptable format (11/11/2011) VARIABLES: YSDATA TYPE: Output VARIABLES DESCRIPTION: Array(2)= Patient Name^Test Code^Test Title^Internal Admin date^External Admin Date ^Ordered by Array(3)=R1^Responses 1-200 undelimited Array(4)=R2^ Responses 201-400 undelimited (even if less than 200) Array(5)=R3^ Responses 401-600 undelimited Array(6)=S1^Scale Name^Raw Score^Transformed Score Array(7)=S2^ Scale Name^Raw Score^Transformed Score And onward as needed Example: Input ----- YS("DFN")=83 YS("CODE")=MMPI2 YS("ADATE")=05/09/1994 Output ------ YSDATA(1)=[DATA] YSDATA(2)=CAPP,ANDY W^MMPI2^--- Minnesota Multiphasic Personality Inventory-2 -- -^2940509^05/09/1994^CAULFIELD,MARY A YSDATA(3)=R1^TTTFTTFTTTFTTFFFFFFTTFFFFFFFTFFFFFFFFFFFFFFFFFFFFFFTFFFFFFFFFFFFFF F FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFTTTTTTFFFFFFFFFFFFFFFFFFFFFFFFFFFFFTTTTFFFTTFFFFF F FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF YSDATA(4)=R2^FFFFFFFFFFFFFFFFFFFFFFFFFTTTTTTTTTTTTTTTTFFFFFFFFFFFFFFFFFFFFFFFFF F FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF F FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFTTT YSDATA(5)=R3^TTTTTTTTTTTTTTTTTTTTTTTFFFFFFFFFFFFFFFFFFFFTTFFFTFTFTFTFTFTFTFTFTF F FTFTFTFTFTFTFTFTFTFTFTFTTFTFTFTFFFFTFFTFTFTFTFTFTFFTFTFTFTFTFFFFFFFFFFFFFFFFFFF F FFFFFFFFFFFFFFFFFFFF YSDATA(6)=S1^L Lie^12^87 YSDATA(7)=S2^F Infrequency^19^95 . . . YSDATA(89)=S84^Ma-S Hypomania, Subtle^10^50 VARIABLES: YS TYPE: Input EDITOR: DEVLIN,MARK J NUMBER: 2893 IA #: 2893 DATE CREATED: AUG 19, 1999 CUSTODIAL PACKAGE: MENTAL HEALTH CUSTODIAL ISC: Dallas USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: YTAPI1 NAME: DBIA2893 ID: YTAPI1 GENERAL DESCRIPTION: This API allows saving of patient responses to a test or interview in the PSYCH INSTRUMENT PATIENT file (#601.2). The patient ien, the test code, and administration date is required along with the responses. All responses are checked for validity. No scoring is returned but successful addition to the PSYCH INSTRUMENT PATIENT file (#601.2) is indicated. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30031661 COMPONENT/ENTRY POINT: SAVEIT VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient internal identifier VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: Test code from MH INSTRUMENT file (#601) or "ASI" (e.g. "CAGE", "BDI") VARIABLES: ADATE TYPE: Input VARIABLES DESCRIPTION: Inclusive administration date in %DT acceptable format (11/11/2011) VARIABLES: STAFF TYPE: Input VARIABLES DESCRIPTION: DUZ of professional ordering the test VARIABLES: R1 TYPE: Input VARIABLES DESCRIPTION: String of patient responses 1-200 VARIABLES: R2 TYPE: Input VARIABLES DESCRIPTION: String of patient responses 201-400 [as needed] VARIABLES: R3 TYPE: Input VARIABLES DESCRIPTION: String of patient responses 401-600 [as needed] VARIABLES: YSDATA TYPE: Output VARIABLES DESCRIPTION: Array(1)=[DATA] indicates successful call Example: Input ----- YS("DFN")=6 YS("ADATE")="T" YS("CODE")="ZUNG" YS("STAFF")=67 YS("R1")="12121212121212121212" Output ------ YSDATA(1)=[DATA] YSDATA(2)=saved NUMBER: 2895 IA #: 2895 DATE CREATED: AUG 19, 1999 CUSTODIAL PACKAGE: MENTAL HEALTH CUSTODIAL ISC: Dallas USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: YTAPI3 NAME: DBIA2895 ID: YTAPI3 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30031663 COMPONENT/ENTRY POINT: SHOWIT COMPONENT DESCRIPTION: This API returns the text, bottom, introduction and possible correct responses for a specified test item in MH INSTRUMENT file (#601). It will work only for tests as opposed to interviews or batteries. The ASI is not supported. VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: Test code from in the MH INSTRUMENT file (#601) (e.g. "CAGE", "BDI") VARIABLES: ITEM TYPE: Input VARIABLES DESCRIPTION: A positive whole number between 1 and the highest item number for the specified test. VARIABLES: YSDATA TYPE: Output VARIABLES DESCRIPTION: Array(1)=[DATA] ;indicates successful call Array(2)=MMPI2 item: 1 ;SECOND LINE IS TEST CODE AND ITEM NUMBER Array(3)=[BEGIN ITEM]; BEGINS EACH ITEM Array(4)=MMPI2^1 ;CODE^ITEM NUMBER Array(5)=[INTRO];HEADER ALWAYS PRESENT OPTIONALY FOLLOWED BY TEXT Array(12)=[TEXT];HEADER ALWAYS PRESENT ALWAYS FOLLOWED BY TEXT Array(14)=[BOTTOM];HEADER ALWAYS PRESENT OPTIONALY FOLLOWED BY TEXT Array(18)=[RESPONSE] ];HEADER ALWAYS PRESENT ALWAYS FOLLOWED BY TEXT Array(21)=[END ITEM]; ENDS EACH ITEM Example: Input ----- YS("CODE")="MMPI2" YS("ITEM")=1 Output ------ YSDATA(1)=[DATA] YSDATA(2)=[BEGIN ITEM] YSDATA(3)=MMPI2^1 YSDATA(4)=[INTRO] YSDATA(5)=Please read each statement carefully and decide whether it is true YSDATA(6)=as applied to you or false as applied to you. YSDATA(7)= YSDATA(8)=If a statement is true or mostly true, as applied to you, answer 'T'. YSDATA(9)=If a statement is false or not usually true, as applied to you, answer YSDATA(10)='F'. YSDATA(11)= YSDATA(12)=Remember to give your own opinion of yourself. YSDATA(13)=[TEXT] YSDATA(14)=I like mechanics magazines. YSDATA(15)=[BOTTOM] YSDATA(16)=T= True YSDATA(17)=F= False YSDATA(18)=Answer= YSDATA(19)=[RESPONSE] YSDATA(20)=TFX YSDATA(21)=[END ITEM] COMPONENT/ENTRY POINT: SHOWALL COMPONENT DESCRIPTION: This API returns the text, bottom, introduction and possible correct responses for all items in a test in the MH INSTRUMENT file (#601). It will work only for tests as opposed to interviews or batteries. The ASI is not supported. VARIABLES: CODE TYPE: Input VARIABLES DESCRIPTION: Test code from the MH INSTRUMENT file (#601). ( e.g. "CAGE", "BDI") VARIABLES: YSDATA TYPE: Output VARIABLES DESCRIPTION: Array(1)=[DATA] ;indicates successful call Array(2)=MMPI2 item: 1 ;SECOND LINE IS TEST CODE AND ITEM NUMBER Array(3)=[BEGIN ITEM]; BEGINS EACH ITEM Array(4)=MMPI2^1 ;CODE^ITEM NUMBER Array(5)=[INTRO];HEADER ALWAYS PRESENT OPTIONALY FOLLOWED BY TEXT Array(12)=[TEXT];HEADER ALWAYS PRESENT ALWAYS FOLLOWED BY TEXT Array(14)=[BOTTOM];HEADER ALWAYS PRESENT OPTIONALY FOLLOWED BY TEXT Array(18)=[RESPONSE] ];HEADER ALWAYS PRESENT ALWAYS FOLLOWED BY TEXT Array(21)=[END ITEM]; ENDS EACH ITEM . . . Array(1003)=[BEGIN ITEM]; BEGINS EACH ITEM Array(1004)=MMPI2^567 ;CODE^ITEM NUMBER Array(1005)=[INTRO];HEADER ALWAYS PRESENT OPTIONALY FOLLOWED BY TEXT Array(1012)=[TEXT];HEADER ALWAYS PRESENT ALWAYS FOLLOWED BY TEXT Array(1014)=[BOTTOM];HEADER ALWAYS PRESENT OPTIONALY FOLLOWED BY TEXT Array(1018)=[RESPONSE] ];HEADER ALWAYS PRESENT ALWAYS FOLLOWED BY TEXT Array(1021)=[END ITEM]; ENDS EACH ITEM Example: Input ----- YS("CODE")="MMPI2" YS("ITEM")=1 Output ------ YSDATA(1)=[DATA] YSDATA(2)=[BEGIN ITEM] YSDATA(3)=MMPI2^1 YSDATA(4)=[INTRO] YSDATA(5)=Please read each statement carefully and decide whether it is true YSDATA(6)=as applied to you or false as applied to you. YSDATA(7)= YSDATA(8)=If a statement is true or mostly true, as applied to you, answer 'T'. YSDATA(9)=If a statement is false or not usually true, as applied to you, answer YSDATA(10)='F'. YSDATA(11)= YSDATA(12)=Remember to give your own opinion of yourself. YSDATA(13)=[TEXT] YSDATA(14)=I like mechanics magazines. YSDATA(15)=[BOTTOM] YSDATA(16)=T= True YSDATA(17)=F= False YSDATA(18)=Answer= YSDATA(19)=[RESPONSE] YSDATA(20)=TFX YSDATA(21)=[END ITEM] . . . YSDATA(6950)=[BEGIN ITEM] YSDATA(6951)=MMPI2^567 YSDATA(6952)=[INTRO] YSDATA(6953)=[TEXT] YSDATA(6954)=Most married couples don't show much affection for each other. YSDATA(6955)=[BOTTOM] YSDATA(6956)=T= True YSDATA(6957)=F= False YSDATA(6958)=Answer= YSDATA(6959)=[RESPONSE] YSDATA(6960)=TFX YSDATA(6961)=[END ITEM] NUMBER: 2896 IA #: 2896 DATE CREATED: JUN 04, 2003 CUSTODIAL PACKAGE: MENTAL HEALTH CUSTODIAL ISC: Dallas USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: YSGAFAPI NAME: DBIA2896 ID: YSGAFAPI GENERAL DESCRIPTION: This API returns the GAF scores for a specified patient. It can be constrained by both date range and occurrence limit. Please note that data for this API comes from the DIAGNOSTIC RESULTS - MENTAL HEALTH file (#627.8). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30031669 COMPONENT/ENTRY POINT: GAFHX VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient internal identifier VARIABLES: BEGIN TYPE: Input VARIABLES DESCRIPTION: Inclusive date in %DT acceptable format (11/11/2011) to begin search [optional] VARIABLES: END TYPE: Input VARIABLES DESCRIPTION: Inclusive date in %DT acceptable format (11/11/2011) to end search [optional] VARIABLES: LIMIT TYPE: Input VARIABLES DESCRIPTION: Constrains to the last N diagnoses [optional] VARIABLES: YSDATA TYPE: Output VARIABLES DESCRIPTION: Array(1)=[DATA] ;indicates successful call Array(1)=GAF Score^Internal Date^External Date^Provider^Comment . . Array(N)=GAF Score^Internal Date^External Date^Provider^Comment Example: Input ----- YS("DFN")=29601 YS("LIMIT")=3 Output ------ YSDATA(1)=[DATA] YSDATA(2)=100^2981209.1105^12/09/1998@11:05^JONES,MARK^ YSDATA(3)=99^2981209.092^12/09/1998@09:20^JONES,MARK^ YSDATA(4)=66^2981124.1406^11/24/1998@14:06^JONES,MARK^ NUMBER: 2897 IA #: 2897 DATE CREATED: AUG 25, 1999 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRCH7D NAME: DBIA2897 ID: PRCH7D GENERAL DESCRIPTION: Routine PRCH7D is used as an interface between Prosthetics Package, Administrative Home Oxygen Module and IFCAP for purchase card transactions. VIEWER: SCHLEHUBER,CAMERON VIEWER: CORKWELL,HELEN N VIEWER: MESSINA,DANIEL VIEWER: GREENE,LYFORD VIEWER: DAYON,RUFINO VIEWER: GRIBSCHAW,STEPHEN J STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29997102 KEYWORDS: HOME OXYGEN KEYWORDS: PURCHASE CARD COMPONENT/ENTRY POINT: ADD COMPONENT DESCRIPTION: Add Administrative Home Oxygen purchase card transaction to File 442, PROCUREMENT & ACCOUNTING TRANSACTIONS. VARIABLES: PRCA TYPE: Both VARIABLES DESCRIPTION: Input variable Station Number and Vendor. Output variable if PRCA is <0, unsuccessful. VARIABLES: COMPONENT/ENTRY POINT: EDITIC COMPONENT DESCRIPTION: Edit existing purchase card transaction. VARIABLES: PRCA TYPE: Input VARIABLES DESCRIPTION: Total monthly amount VARIABLES: PRCB TYPE: Input VARIABLES DESCRIPTION: Internal Entry Number of File 442, PROCUREMENT & ACCOUNTING TRANSACTIONS VARIABLES: PRCC TYPE: Input VARIABLES DESCRIPTION: An array of the Control Point, DFN, and monthly amount. COMPONENT/ENTRY POINT: OBL COMPONENT DESCRIPTION: Obligation of the transaction. VARIABLES: PRCA TYPE: Input VARIABLES DESCRIPTION: Null VARIABLES: X TYPE: Output VARIABLES DESCRIPTION: If X="^" obligation is unsuccessful VARIABLES: PRCB TYPE: Input VARIABLES DESCRIPTION: Internal Entry Number of File 442, PROCUREMENT & ACCOUNTING TRANSACTIONS VARIABLES: PRCC TYPE: Input VARIABLES DESCRIPTION: Total Monthly Amount SUBSCRIBING PACKAGE: PROSTHETICS ISC: Hines SUBSCRIBING DETAILS: Prosthetics Package uses the routine PRCH7D to add, edit and obligate purchase card transactions. NUMBER: 2900 IA #: 2900 FILE NUMBER: 771 GLOBAL ROOT: HL(771, DATE CREATED: AUG 26, 1999 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2900 ID: HL(771, GLOBAL REFERENCE: HL(771, FIELD NUMBER: 3 FIELD NAME: FACILITY NAME LOCATION: 0;3 ACCESS: Write w/Fileman GENERAL DESCRIPTION: A one time update to set the site number in HL7's table for the Application entry in file 771. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30068334 KEYWORDS: HL7 SUBSCRIBING PACKAGE: SCHEDULING NUMBER: 2901 IA #: 2901 DATE CREATED: AUG 31, 1999 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCASF NAME: GMRCASF ID: GMRCASF GENERAL DESCRIPTION: This DBIA will allow calling routine GMRCASF. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30090909 COMPONENT/ENTRY POINT: SF COMPONENT DESCRIPTION: Call to designate a consult as having significant findings. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of entry in file 123 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City EDITOR: BUECHLER,MELANIE K EDITOR: RUTHERFORD,JERALD F NUMBER: 2902 IA #: 2902 DATE CREATED: SEP 01, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIULAPIC NAME: TIU/Health Summary by Visit Date ID: TIULAPIC GENERAL DESCRIPTION: The routine TIULAPIC controls the branching for extracting documents by occurrence, date or type for a given patient. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30074542 KEYWORDS: TIULAPIC KEYWORDS: GMTS KEYWORDS: TIU KEYWORDS: VISIT KEYWORDS: MAIN COMPONENT/ENTRY POINT: VISIT(DFN,TIUDOC,TIME1,TIME2,OCCLIM,TEXT) COMPONENT DESCRIPTION: This entry point is used to extract TIU documents by Visit Date for the Visit Patient Health Summary. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The IEN of the patient file (#2) (required) VARIABLES: TIUDOC TYPE: Input VARIABLES DESCRIPTION: TIU document class, IEN of the TIU DOCUMENT DEFINITION file (#8925.1) (required) VARIABLES: TIME1 TYPE: Input VARIABLES DESCRIPTION: The beginning date for a range of dates to extract TIU documents (optional, default 6666666) VARIABLES: TIME2 TYPE: Input VARIABLES DESCRIPTION: The ending date for a range of dates to extract TIU documents (optional, default 9999999) VARIABLES: OCCLIM TYPE: Input VARIABLES DESCRIPTION: The number of occurrences of teh type of document to extract (optional, default 999) VARIABLES: TEXT TYPE: Input VARIABLES DESCRIPTION: Boolean flag (1/0) to include or not to include document text with the extraction (required) COMPONENT/ENTRY POINT: MAIN(DFN,TIUDOC,TIME1,TIME2,OCCLIM,TEXT) COMPONENT DESCRIPTION: This is entry point is used to extract TIU documents by document Reference Date for the Discharge Summary Component of Health Summary. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The IEN of the Patient file (#2) (required) VARIABLES: TIUDOC TYPE: Input VARIABLES DESCRIPTION: TIU document class, IEN of the TIU DOCUMENT DEFINITION file (#8925.1) (required) VARIABLES: TIME1 TYPE: Input VARIABLES DESCRIPTION: The beginning date for a range of dates to extract TIU documents (optional, default 6666666) VARIABLES: TIME2 TYPE: Input VARIABLES DESCRIPTION: The ending date for a range of dates to extract TIU documents (optional, default 9999999) VARIABLES: OCCLIM TYPE: Input VARIABLES DESCRIPTION: The number of occurrences of the type of document to extract (optional, default 999) VARIABLES: TEXT TYPE: Input VARIABLES DESCRIPTION: Boolean flag (1/0) to include or not to include document text with the extraction (required) SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: MYHEALTHEVET NUMBER: 2903 IA #: 2903 DATE CREATED: SEP 08, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: CHANGING WRITE IDENTIFIERS GENERAL DESCRIPTION: This integration agreement allows the Accounts Receivable package to change the write identifiers on the AR TRANSACTION File #433. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30123385 KEYWORDS: WRITE IDENTIFIERS SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Albany SUBSCRIBING DETAILS: The code is in the routine PRCAI78 which is a post in it for patch PRCA*4.5*78. The code looks like: ; set write identifiers for file 433 (removes old id that references calm) S ^DD(433,0,"ID","WR1")="I +$P(^(0),U,4)<2 D EN^DDIOL("" TRANSACTION STATUS: INCOMPLETE"","""",""?0"")" K ^DD(433,0,"ID","WR2") NUMBER: 2907 IA #: 2907 FILE NUMBER: 53.1 GLOBAL ROOT: PS(53.1, DATE CREATED: SEP 15, 1999 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TIU MEDICATION OBJECTS READ PHARMACY FILE ID: PS(53.1, GLOBAL REFERENCE: PS(53.1, FIELD NUMBER: 108 FIELD NAME: ORDERABLE ITEM ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(53.1,DA,1, FIELD NUMBER: .01 FIELD NAME: DISPENSE DRUG ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: TIU's medication objects now allow for the sorting of medications by drug class, including pending orders for medications that may not yet have a dispense drug. They also allow for the exclusion of supply items from medication lists, if desired. To accomodate this functionality, TIU requests direct global read access to the following pharmacy file: ^PS(53.1, - NON-VERIFIED ORDERS FILE (#53.1) Node .2, piece 1 - ORDERABLE ITEM FIELD (#108) ^PS(53.1,DA,1 - DISPENSE DRUG SUB-FILE (#53.11) Node 0, piece 1 - DISPENSE DRUG FIELD (#.01) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29677689 KEYWORDS: TIU MEDICATION OBJECTS SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 2909 IA #: 2909 FILE NUMBER: 52.6 GLOBAL ROOT: PS(52.6, DATE CREATED: SEP 15, 1999 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TIU MEDICATION OBJECTS READ PHARMACY FILE ID: PS(52.6, GLOBAL REFERENCE: PS(52.6, FIELD NUMBER: 1 FIELD NAME: GENERIC DRUG ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This agreement will be retired on 6/1/2006. Please do not add any additional code that utilizes this Integration Agreement. APIs have been created that can be used in place of any code needing to make use of this agreement. These APIs were released with patch PSS*1*91. Documentation information can be found in the patch description. In addition, any code that currently utilizes this Integration Agreement must be converted to use the new API's. If any part of this Integration Agreement cannot be satisfied with the APIs, please contact the PRE development team mail group at VHA OI SDD PHARM REENG DEV using Microsoft Outlook. TIU's medication objects now allow for the sorting of medications by drug class, including pending orders for medications that may not yet have a dispense drug. They also allow for the exclusion of supply items from medication lists, if desired. To accomodate this functionality, TIU requests direct global read access to the following pharmacy file: ^PS(52.6, - IV ADDITIVES FILE (#52.6) Node 0, piece 2 - GENERIC DRUG FIELD (#1) STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: JUN 01, 2006 MAIL MESSAGE: 29677689 KEYWORDS: TIU MEDICATION OBJECTS SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 2910 IA #: 2910 FILE NUMBER: 1 GLOBAL ROOT: DIC( DATE CREATED: OCT 05, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Delete Read Protection on Files ID: DIC( GLOBAL REFERENCE: DIC(50.6,0,'RD') GLOBAL REFERENCE: DIC(50.64,0,'RD') GLOBAL REFERENCE: DIC(50.67,0,'RD') GLOBAL REFERENCE: DIC(50.68,0,'RD') GENERAL DESCRIPTION: E3R PSN-4-12347 asked that the read protection on files related to National Drug File be removed. To meet this request, NDF requests a one time agreement with VA FileMan to KILL the global nodes ^DIC(50.6,0,"RD"), ^DIC(50.64,0,"RD"), ^DIC(50.67,0,"RD"), and ^DIC(50.68,0,"RD") STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30262350 SUBSCRIBING PACKAGE: NATIONAL DRUG FILE ISC: Birmingham NUMBER: 2911 IA #: 2911 FILE NUMBER: 391.91 GLOBAL ROOT: DGCN(391.91, DATE CREATED: JAN 13, 2000 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TREATING FACILITY LIST (#391.91): relationship with CIRN PD ID: DGCN(391.91, GLOBAL REFERENCE: DGCN(391.91, FIELD NUMBER: .02 FIELD NAME: INSTITUTION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: DATE LAST TREATED LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .07 FIELD NAME: ADT/HL7 EVENT REASON LOCATION: 0;7 ACCESS: Write w/Fileman FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: DGCN(391.91,'APAT') GLOBAL DESCRIPTION: This is a M type cross-reference. It builds the cross-reference from PATIENT (#.01) and INSTITUTION (#.02) field data. The structure is as follows: ^DGCN(391.91,"APAT", PATIENT (#2) file pointer , INSTITUTION (#4) file pointer , internal entry number)="" GLOBAL REFERENCE: DGCN(391.91,'AINST') GLOBAL DESCRIPTION: This is a M type cross-reference. It builds the cross-reference from PATIENT (#.01) and INSTITUTION (#.02) field data. The structure is as follows: ^DGCN(391.91,"AINST", INSTITUTION (#4) file pointer , PATIENT (#2) file pointer , internal entry number)="" GLOBAL REFERENCE: DGCH(391.91,'C', GLOBAL DESCRIPTION: x-ref build from INSTITUTION (#.02) and PATIENT (#.01) fields. GENERAL DESCRIPTION: The CIRN PD package would like to use the TREATING FACILITY (#391.91) file for the following functions: 1) Loop through "B" cross- reference in the TREATING FACILITY (#391.91) file getting the INSTITUTION (#4) file IEN or the (#.02) INSTITUTION [2P] field. 2) Take each IEN and translate into a HL LOGICAL LINK (#870) file entry 3) Using the known SUBSCRIPTION CONTROL IEN, call GET^HLSUB, to get the DESTINATIONS for that IEN. 4) Compare the logical links identified by the entries in the TREATING FACILITY to the links returned by GET^HLSUB. If there is not a one-to-one relationship add an entry to the SUBSCRIPTION CONTROL (#774) file for the missing entry. The missing entry is added using $$ACT^HLSUB and UPD^HLSUB. 5) Utilize the "APAT" cross-reference to determine the internal entry number (ien) of the TREATING FACILITY LIST (TFL) record. If an ien does not exist, we add to the TFL file. 6) Utilize the "AINST" cross-reference to check for patients within a given facility. 7) A direct global read for the DATE LAST TREATED field (#.03 ; node: 0 ; piece: 3) to determine if the data on file is valid. 8) Write access with FileMan for the following fields: DATE LAST TREATED and ADT/HL7 EVENT REASON (field: .07 ; node: 0 ; piece: 7). ADT/HL7 EVENT REASON is a pointer data type pointing to the ADT/HL7 EVENT REASON (#391.72) file. At this time we are only concerned about missing subscriptions and not missing treating facilities. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30191520 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING DETAILS: The CIRN package would like to loop through ^DGCN(391.91,"B",#.01,D0) to get the (#.02)INSTITUTION field. CIRN PD intends to use the "APAT", "AINST" cross-references in some of its applications. The use of these cross-references will determine the internal entry number (ien) of the TREATING FACILITY LIST (TFL) entry. CIRN PD intends to check the DATE LAST TREATED (#.03) field for data. A direct global read is being requested for the DATE LAST TREATED (node: 0 ; piece: 3) field. CIRN PD intends to write data to the TFL file for the following fields: DATE LAST TREATED and ADT/HL7 EVENT REASON (#.07). Write access with FileMan is requested. NUMBER: 2913 IA #: 2913 FILE NUMBER: 396.3 GLOBAL ROOT: DVB(396.3, DATE CREATED: SEP 20, 1999 CUSTODIAL PACKAGE: AUTOMATED MED INFO EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: SUPPORT TIU'S UPLOAD OF C&P EXAMS ID: DVB(396.3, GLOBAL REFERENCE: +DVB(396.3,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is accessed in a read-only manner to determine whether the incoming data was transcribed for the same patient that the corresponding 2507 REQUEST entry refers to. If the patient associated with the incoming data does NOT match the one for whom the REQUEST was entered, a FILING ERROR will be raised. When such a FILING ERROR is corrected the NAME Field is also used to display the NAME and SSN of the patient for each open request (as specified by DIC("W")) in the FIX^TIUPUTA subroutine. GENERAL DESCRIPTION: This DBIA, along with #2914 and #2915, is intended to support the upload of Compensation and Pension Exam Results into AMIE, using TIU's batch upload facility. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29977107 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 2914 IA #: 2914 FILE NUMBER: 396.4 GLOBAL ROOT: DVB(396.4, DATE CREATED: SEP 20, 1999 CUSTODIAL PACKAGE: AUTOMATED MED INFO EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: SUPPORT TIU'S UPLOAD OF C&P EXAMS ID: DVB(396.4, GLOBAL REFERENCE: DVB(396.4,D0,0) FIELD NUMBER: .02 FIELD NAME: 2507 REQUEST LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Given the transcribed record number in file 396.4, this field is read in order to identify the corresponding 2507 Request and thereby determine which patient the request was entered for. FIELD NUMBER: .04 FIELD NAME: STATUS LOCATION: 0;4 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field is set to COMPLETED by the FOLLOWUP^TIUPUTA when the record is successfully filed. FIELD NUMBER: 70 FIELD NAME: EXAM RESULTS LOCATION: RES;0 ACCESS: Direct Global Write & w/Fileman FIELD DESCRIPTION: The plain text for the CP Exam is filed in this word-processing field. GENERAL DESCRIPTION: This DBIA, along with #2913 and #2915, is intended to support the upload of Compensation and Pension Exam Results into AMIE, using TIU's batch upload facility. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29977107 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 2915 IA #: 2915 FILE NUMBER: 396.6 GLOBAL ROOT: DVB(396.6, DATE CREATED: SEP 20, 1999 CUSTODIAL PACKAGE: AUTOMATED MED INFO EXCHANGE CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: SUPPORT TIU'S UPLOAD OF C&P EXAMS ID: DVB(396.6, GLOBAL REFERENCE: DVB(396.6,D0,0) FIELD NUMBER: 6 FIELD NAME: PRINT NAME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is accessed in a read-only manner for the DIC("W") code specified in FIX^TIUPUTA to display the Exam Type for the user who is resolving a FILING ERROR for a case where the look-up method failed to confirm a match between the exam and the patient identified by the incoming transcription. GENERAL DESCRIPTION: This DBIA, along with #2913 and #2914, is intended to support the upload of Compensation and Pension Exam Results into AMIE, using TIU's batch upload facility. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 29977107 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 2916 IA #: 2916 DATE CREATED: SEP 20, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DDMOD NAME: Data Base Server API: DD Modification Utilities ID: DDMOD STATUS: Active MAIL MESSAGE: 30271862 COMPONENT/ENTRY POINT: DELIX COMPONENT DESCRIPTION: This procedure deletes a Traditional Cross-Reference definition from the data dictionary. Optionally, it deletes the data in the index or executes the kill logic for all entries in the file. Compiled input templates that contain the field on which the cross-reference is defined are recompiled. If cross-references on the file are compiled, they are recompiled. Format: DELIX^DDMOD(FILE,FIELD,CROSS_REF,FLAGS,OUTPUT_ROOT,MSG_ROOT) Examples -------- 1. In this example, regular cross-reference #4 (the "C" index), defined on field #12 in file #16200, is deleted. The "K" flag indicates that the entire ^DIZ(16200,"C") index is removed from the file. >D DELIX^DDMOD(16200,12,4,"K","MYOUT") >ZW MYOUT MYOUT("DDAUD")=1 MYOUT("DIEZ",100)=ZZTEST EDIT^16200^ZZIT MYOUT("DIKZ")=ZZCR The MYOUT output array indicates that the deletion was recorded in the DD Audit file (#.6). Field #12 is included in the compiled input template ZZTEST EDIT (#100), which is compiled into the ZZIT namespaced routines. Cross-references on file #16200 are compiled under the ZZCR namespace. 2. In this example, the whole-file regular cross-reference #7 (the "N" index), defined on field #15 within subfile #16200.075, is deleted. The "K" flag indicates that the entire ^DIZ(16200,"N") index should be removed, and the "W" flag indicates that messages should be printed to the current device. >D DELIX(16200.075,15,7,"KW") Removing index ... Deleting cross-reference definition ... Compiling ZZ TEST CR Input Template of File 16200... 'ZZIT1' ROUTINE FILED.. 'ZZIT' ROUTINE FILED.... 'ZZIT2' ROUTINE FILED. Compiling Cross-Reference(s) 16200 of File 16200. ...SORRY, HOLD ON... 'ZZCR1' ROUTINE FILED. 'ZZCR2' ROUTINE FILED. 'ZZCR3' ROUTINE FILED. 'ZZCR4' ROUTINE FILED. 'ZZCR5' ROUTINE FILED. 'ZZCR' ROUTINE FILED. Error Codes Returned -------------------- 202 The specified parameter is missing or invalid. 301 The passed flags are incorrect. 401 The file does not exist. 406 The file has no .01 definition. 407 A word-processing field is not a file. 501 The file does not contain the specified field. VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) File or subfile number. VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) Field number. VARIABLES: CROSS_REF TYPE: Input VARIABLES DESCRIPTION: (Required) Cross-reference number. Traditional cross-references are defined in the data dictionary under: ^DD(file#,field#,1,cross reference number) VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flags to control processing. The possible values are: K For Regular, KWIC, Mnemonic, and Soundex-type cross-references, delete the data in the index. For MUMPS and Trigger-type cross-references, execute the kill logic of the cross-reference for all entries in the file. For Bulletin-type cross-references, the "K" flag is ignored; the kill logic for Bulletin-type cross-references is never executed by this procedure. W Write messages to the current device as the index is deleted and cross-references and input templates are recompiled. VARIABLES: OUTPUT_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) Input: The name of the array that should receive information about input templates and cross-references that may have been recompiled and a flag to indicate that the deletion was audited in the DD Audit file (#.6). This must be a closed root, either local or global. Output: If the field on which the deleted cross-reference was defined is used in any compiled input templates, those input templates are recompiled. Information about the recompiled input templates is stored descendant from OUTPUT_ROOT("DIEZ"): OUTPUT_ROOT("DIEZ",input template #) = input template name ^ file # ^ compiled routine name If cross-references for the file are compiled, they are recompiled, and the compiled routine name is stored in OUTPUT_ROOT("DIKZ"): OUTPUT_ROOT("DIKZ") = compiled routine name If the data dictionary for the file is audited, an entry is made in the DD Audit file (#.6) and OUTPUT_ROOT("DDAUD") is set to 1: OUTPUT_ROOT("DDAUD") = 1 VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The name of the array that should receive any error messages. This must be a closed root, either local or global. If not passed, errors are returned descendent from ^TMP("DIERR",$J). COMPONENT/ENTRY POINT: DELIXN COMPONENT DESCRIPTION: This procedure deletes a New-Style Index definition from the Index file. Optionally, it deletes the data in the index or executes the kill logic for all entries in the file. Compiled input templates that contain one or more of the fields defined in the index are recompiled. If cross-references on the file are compiled, they are recompiled. Format: DELIXN^DDMOD(FILE,INDEX,FLAGS,OUTPUT_ROOT,MSG_ROOT) Examples -------- 1. In this example, the new-style "G" index defined on file #16200 is deleted. The "K" flag indicates that the entire ^DIZ(16200,"G") index should be removed from the file. >D DELIXN^DDMOD(16200,"G","K","MYOUT") >ZW MYOUT MYOUT("DIEZ",94)=ZZ TEST^16200^ZZIT MYOUT("DIEZ",100)=ZZ TEST A^16200^ZZITA MYOUT("DIKZ")=ZZCR The MYOUT output array indicates that a field or fields defined in the deleted index are used in the compiled input templates ZZ TEST (#94) and ZZ TEST 2 (#100). Those two input templates were recompiled. Cross-references on file #16200 were also recompiled under the ZZCR namespace. 2. In this example, the whole-file regular index (the "J" index) is deleted. The fields in the index come from fields in a multiple, subfile #16200.075, but the whole-file index resides at the top-level file #16200. The "K" flag indicates that the entire ^DIZ(16200,"J") index should be removed, and the "W" flag indicates that messages should be printed to the current device. >D DELIXN^DDMOD(16200,"J","KW","MYOUT") Removing index ... Deleting index definition ... Compiling ZZ TEST Input Template of File 16200.... 'ZZIT' ROUTINE FILED.... 'ZZIT1' ROUTINE FILED. Compiling ZZ TEST A Input Template of File 16200.... 'ZZITA' ROUTINE FILED.... 'ZZITA' ROUTINE FILED. Compiling Cross-Reference(s) 16200 of File 16200. ...SORRY, JUST A MOMENT PLEASE... 'ZZCR1' ROUTINE FILED. 'ZZCR2' ROUTINE FILED. 'ZZCR3' ROUTINE FILED. 'ZZCR4' ROUTINE FILED. 'ZZCR5' ROUTINE FILED. 'ZZCR6' ROUTINE FILED. 'ZZCR7' ROUTINE FILED. 'ZZCR8' ROUTINE FILED. 'ZZCR9' ROUTINE FILED. 'ZZCR10' ROUTINE FILED. 'ZZCR' ROUTINE FILED. Error Codes Returned -------------------- 202 The specified parameter is missing or invalid. 301 The passed flags are incorrect. VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) File or subfile number. For whole-file indexes, this is the number of the file at the upper level where the data in the index resides. VARIABLES: INDEX TYPE: Input VARIABLES DESCRIPTION: (Required) Index name. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: (Optional) Flags to control processing. The possible values are: K For Regular indexes, delete the data in the index. For MUMPS indexes, execute the kill logic for all entries in the file. W Write messages to the current device as the index is deleted and cross-references and input templates are recompiled. VARIABLES: OUTPUT_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) Input: The name of the array that should receive information about input templates and cross-references that may have been recompiled. This must be a closed root, either local or global. Output: If a field used in the index is used in any compiled input templates, those input templates are recompiled. Information about the recompiled input templates is stored descendant from OUTPUT_ROOT("DIEZ"): OUTPUT_ROOT("DIEZ",input template #) = input template name ^ file # ^ compiled routine name If cross-references for the file are compiled, they are recompiled, and the compiled routine name is stored in OUTPUT_ROOT("DIKZ"): OUTPUT_ROOT("DIKZ") = compiled routine name VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The name of the array that should receive any error messages. This must be a closed root, either local or global. If not passed, errors are returned descendent from ^TMP("DIERR",$J). COMPONENT/ENTRY POINT: FILESEC COMPONENT DESCRIPTION: Set File Protection Security Codes FORMAT FILESEC^DDMOD(FILE,.SECURITY_CODES,MSG_ROOT) This entry point sets the security access codes for a file, which are stored in the following nodes: ^DIC(filenumber,0,"AUDIT") -- Audit Access ^DIC(filenumber,0,"DD") -- Data Dictionary Access ^DIC(filenumber,0,"DEL") -- Delete Access ^DIC(filenumber,0,"LAYGO") -- LAYGO Access ^DIC(filenumber,0,"RD") -- Read Access ^DIC(filenumber,0,"WR") -- Write Access Error Code: 401 File does not exist or the File Number that was passed was Less Than 2. VARIABLES: FILE TYPE: Both VARIABLES DESCRIPTION: (Required) File number. (Cannot be less than 2.) VARIABLES: .SECURITY_CODES TYPE: Both VARIABLES DESCRIPTION: (Required) Array of new security access codes: SECURITY_CODES("AUDIT") = Audit Access SECURITY_CODES("DD") = Data Dictionary Access SECURITY_CODES("DEL") = Delete Access SECURITY_CODES("LAYGO") = LAYGO Access SECURITY_CODES("RD") = Read Access SECURITY_CODES("WR") = Write Access VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The root of an array into which error messages are returned. If this parameter is not included, errors are returned in the default array: ^TMP("DIERR",$J). COMPONENT/ENTRY POINT: CREIXN COMPONENT DESCRIPTION: This procedure creates a new-style cross-reference definition in the INDEX file (#.11). Optionally, it builds the data in the index (for Regular cross-references) or executes the set logic (for MUMPS cross-references) for all entries in the file. Compiled input templates that contain one or more of the fields defined in the cross-reference are recompiled. If cross-references on the file are compiled, they are recompiled. One use of CREIXN^DDMOD is in the pre-install or post-install routine of a KIDS (Kernel Installation and Distribution System) Build to create a new-style cross-reference at the installing site. If you pass in the cross-reference name in the XREF("NAME") input parameter, before CREIXN^DDMOD creates the new-index it automatically makes a call to DELIXN^DDMOD to delete the cross-reference with the same name, and optionally executes the kill logic for that cross-reference. See ^DIKCBLD for information on a programmer mode utility that can be used to help create a routine that calls CREIXN^DDMOD. Format: ------ CREIXN^DDMOD(.XREF,FLAGS,.RESULT,OUTPUT_ROOT,MSG_ROOT) VARIABLES: .RESULTS TYPE: Both VARIABLES DESCRIPTION: (Optional) Local variable that receives the IEN of the entry that was created in the INDEX file (#.11), if the call is successful, and the Name of the new index. If the cross-reference could not be created, a value of null ("") is returned. RESULT = IEN in Index file ^ cross-reference name or RESULT = "" if cross-reference could not be created VARIABLES: .XREF TYPE: Input VARIABLES DESCRIPTION: (Required) This input array contains information about the new-style cross-reference to be created. The elements in this array are as follows: XREF("FILE") = The number of the file or subfile on which the index physically resides. For whole-file indexes, this should be the file number of the upper level file, not the subfile that contains the fields in the index. For MUMPS cross-references that don't set an index, XREF("FILE") should be the file that contains the fields in the cross-reference. (Required) XREF("TYPE") = "R" or "REGULAR" for regular indexes; or "MU" or "MUMPS" for MUMPS-type cross-references. (Required) XREF("NAME") = The name of the cross-reference. If XREF("NAME") is not passed, CREIXN^DDMOD gets the next available name based on the XREF("FILE") and XREF("USE"). In most cases, however, you should explicitly give your new cross-reference a name. (Required if XREF("USE") is not passed.) XREF("ROOT FILE") = For whole-file indexes, the number of the file or subfile that contains the fields in the cross-reference. This is the subfile number, not the upper level file number where the index physically resides. XREF("ROOT FILE") should only be set for whole-file indexes. (Required for whole-file indexes.) XREF("SHORT DESCR") = Short description of the cross-reference (Required) XREF("DESCR",1) = Line 1 of the cross-reference description. XREF("DESCR",n) = Line n of the cross-reference description. (Optional) XREF("USE") = "LS" or "LOOKUP & SORTING" for indexes used for both lookup and sorting; "S" or "SORTING ONLY" for indexes used for sorting only; or "A" or "ACTION" for MUMPS cross-reference that do not set an index. "LS" ("LOOKUP & SORTING") - The cross-reference sets an index and the index name must start with "B" or a letter that alphabetically follows "B". Calls to Classic FileMan lookup (^DIC) or the Finder (FIND^DIC or $$FIND1^DIC) where the index is not specified will include this index in the search. The index will be available for use by the FileMan Sort and Print (EN1^DIP). "S" ("SORTING ONLY") - The cross-references sets an index, and the index name must start with "A". Calls to Classic FileMan lookup (^DIC) or the Finder (FIND^DIC or $$FIND1^DIC) will not use this index unless it is specified in the input parameters to those calls. The index will be available for use by the FileMan Sort and Print (EN1^DIP). "A" ("ACTION") -This is used for MUMPS cross-references that perform some action(s) other than building an index. The cross-reference name must start with "A". If XREF("USE") is not passed, CREIXN^DDMOD assumes a value based on the cross-reference name and type. If the name starts with "A", XREF("USE") is assumed to be "S" (Sorting Only) for Regular indexes, and "A" (Action) for MUMPS cross-references. If the name doesn't start with an "A", XREF("USE") is assumed to be "LS" (Lookup & Sorting). Note that for clarity, however, it is recommended that you explicitly set XREF("USE"). (Required if XREF("NAME") is not passed.) XREF("EXECUTION") = "F" or "FIELD" for field-level execution; or "R" or "RECORD" for record-level execution. This indicates whether the cross-reference logic should be executed after a field in the cross-reference changes, or only after all fields in a record are updated in an editing session. The logic for most simple (single-field) cross-references should be executed immediately after the field changes, and so should have an Execution of "F". The logic for most compound (multi-field) cross-references should be executed only once after a transaction on the entire record is complete, and so should have an Execution of "R". (Optional) (Defaults to "F" for simple cross-references, and "R" for compound cross-references.) XREF("ACTIVITY") = One or both of the following codes: I = Installing an entry at a site R = Re-cross-referencing this index If Activity contains an "I", FileMan fires the cross-references during a KIDS installation. If Activity contains an "R", FileMan fires the cross-reference during a re-cross-referencing operation. Note that FileMan automatically fires cross-references during an edit, regardless of Activity, although you can control whether a cross-reference is fired by entering set and kill conditions. Also, if you explicitly select a cross-reference in an EN^DIK, EN1^DIK, or ENALL^DIK call, or in the UTILITY FUNCTIONS/RE-INDEX FILE option on the VA FileMan menu, that cross-reference will be fired whether or not its Activity contains an "R". (Optional) (Defaults to "IR") XREF("SET CONDITION") = MUMPS code that sets the variable X. The set logic of the cross-reference is executed only if the set condition, if present, sets X to Boolean true, according the M rules for Boolean interpretation. The MUMPS code can assume the DA array describes the record to be cross-referenced, and that the X(order#) array contains values after the transform for storage is applied, but before the truncation to the maximum length. The variable X also equals X(order#) of the lowest order number. When fields that make up a cross-reference are edited and the kill and set conditions are executed, the X1(order#) array contains the old field values, and the X2(order#) array contains the new field values. If a record is being added, and there is an X1(order#) array element that corresponds to the .01 field, it is set to null. When a record is deleted, all X2(order#) array elements are null. (Optional) XREF("KILL CONDITION") = MUMPS code, that sets the variable X. The kill logic of the cross-reference is executed only if the kill condition, if present, sets X to Boolean true, according the M rules for Boolean interpretation. See XREF("SET CONDITION") above for a description of the DA, X, X1, and X2 arrays that can be used in the MUMPS code. (Optional) For MUMPS cross-references, you can also set the following nodes in the XREF array. (For Regular Indexes, the set and kill logic is determined automatically for you, and so these nodes, if passed in, are ignored.) The code can also make use of the DA, X, X1, and X2 arrays as described in XREF("SET CONDITION") above. XREF("SET") = M code that FileMan should be executed when the values of fields that make up the cross-reference are set or changed. (Optional) (Defaults to "Q") XREF("KILL") = M code that FileMan should be executed when the values of fields that make up the cross-reference are changed or deleted. (Optional) (Defaults to "Q") XREF("WHOLE KILL") = M code that can be executed to remove an entire index for all records in a file. When an entire fire is reindexed, FileMan executes this code rather than looping through all the entries in the file and executing the kill logic once for each entry. (Optional) Each value in the cross-reference is described in the XREF("VAL",order#) portion of the XREF array. The order numbers must be positive integers starting from 1, and determine the order in which FileMan evaluates the cross-reference values to place in the X(order#) array during cross-reference execution. XREF("VAL",order#) = The field number (for field-type xref values); or M code that sets X to the cross-reference value (for computed-type xref values). For computed-type cross-reference values, the X(order#) array is available for those cross-reference values with lower order numbers, and the DA array describes the IEN of the current record. (Required) XREF("VAL",order#,"SUBSCRIPT") = The subscript position number in the index, if this cross-reference value is used as a subscript in the index. The first subscript to the right of the index name is subscript number 1. All subscripts must be consecutive integers starting from 1. (Optional) XREF("VAL",order#,"LENGTH") = The maximum length of the cross-reference value FileMan should use when storing the value as a subscript in the index. (Optional). XREF("VAL",order#,"COLLATION") = "F" for "forwards"; "B" for "backwards". This indicates the direction FileMan's lookup utilities should $ORDER through this subscript when entries are returned or displayed to the user. (Optional) (Defaults to "F".) XREF("VAL",order#,"LOOKUP PROMPT") = Text that becomes the prompt to the user when this index is used for lookup, and a value is requested for this subscript. (Optional) For field-type cross-reference values only, the following nodes can also be set: XREF("VAL",order#,"XFORM FOR STORAGE") = M code that sets the variable X to a new value. X is the only variable guaranteed to be defined and is equal to the internal value of the field. The Transform for Storage can be used to the transform the internal value of the field before it is stored as a subscript in the index. XREF("VAL",order#,"XFORM FOR LOOKUP") = M code that sets the variable X to a new value. X is the only variable guaranteed to be defined and is equal to the lookup value entered by the user. During lookup, if the lookup value is not found in the index, FileMan executes the Transform for Lookup code to transform the lookup value X and tries the lookup again. XREF("VAL",order#,"XFORMFOR DISPLAY") = M code that sets the variableX to a new value. X is the only variable guaranteed to be defined and isset equal to the value of the subscript of in the index. During lookup, ifa match or matches are ma de to the lookup value, the Transform for Display code is executed before displaying the index value to the user. VARIABLES: FLAGS TYPE: Used VARIABLES DESCRIPTION: (Optional) Flags to control processing. The possible values are: k - When CREIXN^DDMOD calls DELIXN^DDMOD to initially delete the old cross-reference with the same name as the one it is creating, don't kill the data in the old index if it is a Regular indexes, and don't execute the old Kill logic if it is a MUMPS cross-references. Whether or not this flag is passed, CREIXN^DDMOD deletes the old cross-reference definition, if it exists, before bringing in the new definition. S - For Regular indexes, set the data in the index. For MUMPS cross-references, execute the Set logic for all entries in the file. W - Write messages to the current device as the index is created and cross-references and input templates are recompiled. VARIABLES: MSG_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The name of the array that should receive any error messages. This must be a closed root, either local or global. If not passed, errors are returned descendent from ^TMP("DIERR",$J). VARIABLES: OUTPUT_ROOT TYPE: Both VARIABLES DESCRIPTION: (Optional) The name of the array that should receive information about input templates and cross-references that may have been recompiled. See Output below. This must be a closed root, either local or global. NUMBER: 2919 IA #: 2919 DATE CREATED: AUG 25, 2006 CUSTODIAL PACKAGE: REGISTRATION USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGENPTA NAME: Patients enrolled/preferred facility ID: DGENPTA GENERAL DESCRIPTION: Looks up a patients enrolled/preferred faility: STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 44032799 COMPONENT/ENTRY POINT: $$PREF(DFN,FACNAME) VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of a record in the PATIENT file. VARIABLES: FACNAME TYPE: Both VARIABLES DESCRIPTION: Optional parameter, pass by refernce - returns institution name. VARIABLES: $$PREF TYPE: Output VARIABLES DESCRIPTION: IEN for the record in the INSTITUTION file that is the patient's preferred facility, NULL if the prefereed facility cannot be determined. EDITOR: FAIN,ZACHARY NUMBER: 2923 IA #: 2923 FILE NUMBER: 450 GLOBAL ROOT: PRSPC( DATE CREATED: OCT 08, 1999 CUSTODIAL PACKAGE: PAID CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ASISTS use of $Order of File 450 ID: PRSPC( GENERAL DESCRIPTION: Use of $Order of through the top level of ^PRSPC(I) is needed in ASISTS. ASISTS needs to get a count of the number of PAID employees at each facility who are not separated. That information will be used in statistical analysis for blood-borne pathogen reporting. After getting the IEN of each PAID employee, the routine will use a FileMan read to determine whether the employee is separated. The routine will be executed on a monthly basis. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30282679 SUBSCRIBING PACKAGE: ASISTS ISC: Washington/Silver Spring NUMBER: 2924 IA #: 2924 FILE NUMBER: 160 GLOBAL ROOT: ONCO(160, DATE CREATED: OCT 12, 1999 CUSTODIAL PACKAGE: ONCOLOGY CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2924 ID: ONCO(160, GLOBAL REFERENCE: ONCO(160,'B', GLOBAL DESCRIPTION: The ONCOLOGY PATIENT (160) file "B" cross-reference is used to look up a patient in the ONCOLOGY PATIENT file. If the look-up is successful, the patient's ONCOLOGY PRIMARY (165.5) data is retrieved. (See DBIA 2888) GENERAL DESCRIPTION: The Health Summary package has permission to do a "Direct Global Read" of the ONCOLOGY PATIENT (160) file's "B" cross-reference. VIEWER: BIELO,GARY STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30300056 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 2925 IA #: 2925 DATE CREATED: OCT 13, 1999 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCSLM2 NAME: GMRCSLM2 ID: GMRCSLM2 GENERAL DESCRIPTION: This DBIA documents calls to GMRCSLM2 as found in the OE/RR v3 interface specification document. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 COMPONENT/ENTRY POINT: DT(IEN) COMPONENT DESCRIPTION: Returns narrative for a consult report VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of request in the REQUEST/CONSULTATION file (#123) VARIABLES: TMP("GMRCR",$J, TYPE: Output VARIABLES DESCRIPTION: ^TMP("GMRCR",$J,"DT",#,0)=line of report text SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: PROSTHETICS ISC: Hines SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: CLINICAL PROCEDURES EDITOR: RUTHERFORD,JERALD F NUMBER: 2926 IA #: 2926 DATE CREATED: OCT 13, 1999 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCGUIA NAME: GMRCGUIA ID: GMRCGUIA GENERAL DESCRIPTION: This DBIA documents calls to GMRCGUIA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 COMPONENT/ENTRY POINT: RT(IEN,ARRAY) COMPONENT DESCRIPTION: Returns narrative for a consult result report VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of request in the REQUEST/CONSULTATION file (#123) VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: Name of the array in which to return the text of the report as ARRAY(#,0)=line of text COMPONENT/ENTRY POINT: $$DC(IEN,PROVIDER,DATETIME,STATUS,.COMMENT) COMPONENT DESCRIPTION: Entry point to discontinue or deny a consult request. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of REQUEST/CONSULTATION file (#123) VARIABLES: PROVIDER TYPE: Input VARIABLES DESCRIPTION: Pointer to NEW PERSON file (#200) denoting provider who discontinued or denied the consult request. VARIABLES: DATETIME TYPE: Input VARIABLES DESCRIPTION: Date/time the actual activity (discontinuation or denial) took place. VARIABLES: STATUS TYPE: Input VARIABLES DESCRIPTION: DY if Cancelled (previously 'deny') DC if Discontinued VARIABLES: .COMMENT TYPE: Input VARIABLES DESCRIPTION: Array of comment containing explanation of denial or discontinuation. VARIABLES: OUTPUT TYPE: Output VARIABLES DESCRIPTION: Extrinsic function returns: ErrorFlag^ErrorMessage ErrorFlag is 0 if no error found or 1 if an errror occured. ErrorMessage is null for no error or descriptive of error if one occurred. COMPONENT/ENTRY POINT: $$FR(IEN,SERVICE,PROVIDER,ATTENTION,URGENCY,.COMMENT,DATE TIME) COMPONENT DESCRIPTION: Call to forward an existing consult to a different service. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of REQUEST/CONSULTATION file (#123) VARIABLES: SERVICE TYPE: Input VARIABLES DESCRIPTION: Pointer to REQUEST SERVICES file (#123.5) indicating service consult request should be forwarded to. VARIABLES: PROVIDER TYPE: Input VARIABLES DESCRIPTION: Pointer to NEW PERSON file (#200) indicating provider responsible for the forwarding action. VARIABLES: ATTENTION TYPE: Input VARIABLES DESCRIPTION: Pointer to NEW PERSON file (#200) indicating the person to whose attention the forwarded consult should be directed. VARIABLES: URGENCY TYPE: Input VARIABLES DESCRIPTION: Value of the URGENCY from the PROTOCOL file (#101) VARIABLES: .COMMENT TYPE: Input VARIABLES DESCRIPTION: Array of comments that explains the reason the request was forwarded. VARIABLES: DATETIME TYPE: Input VARIABLES DESCRIPTION: The date/time the request was forwarded VARIABLES: OUTPUT TYPE: Output VARIABLES DESCRIPTION: Extrinsic function returns: ErrorFlag^ErrorMessage ErrorFlag is 0 if no error found or 1 if an errror occured. ErrorMessage is null for no error or descriptive of error if one occurred. COMPONENT/ENTRY POINT: $$RC(IEN,RECEIVER,DATETIME,.COMMENTS,ENTERER) COMPONENT DESCRIPTION: Call to receive a consult into a service VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of REQUEST/CONSULTATION file (#123) VARIABLES: RECEIVER TYPE: Input VARIABLES DESCRIPTION: Pointer to NEW PERSON file (#200) denoting person who received the consult request. VARIABLES: DATETIME TYPE: Input VARIABLES DESCRIPTION: Actual date/time the consult was received by the service VARIABLES: COMMENTS TYPE: Input VARIABLES DESCRIPTION: Array of comments entered for request VARIABLES: ENTERER TYPE: Input VARIABLES DESCRIPTION: IEN of NEW PERSON file (#200) indicating person who entered consult as being received. VARIABLES: OUTPUT TYPE: Output VARIABLES DESCRIPTION: Extrinsic function returns: ErrorFlag^ErrorMessage ErrorFlag is 0 if no error found or 1 if an errror occured. ErrorMessage is null for no error or descriptive of error if one occurred. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: PROSTHETICS ISC: Hines SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING DETAILS: Permitted to use the RT entry point component only. SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM DBA Comments: 6/3/14-MC: Brandon DeWayne originally requested to add FBCS as a subscriber on 6/20/13. Approval was received from Tony Thompson. Last email correspondence with Brandon was July 2013. Patch was discovered to have been released 9/11/13 as an emergency patch. Since patch has been released and approval was received, adding FBCS to the ICR as a subscribing package. NUMBER: 2927 IA #: 2927 FILE NUMBER: 2005 GLOBAL ROOT: MAG(2005, DATE CREATED: OCT 14, 1999 CUSTODIAL PACKAGE: IMAGING CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: POINTERS TO IMAGE FILE (#2005) ID: MAG(2005, GLOBAL REFERENCE: MAG(2005,D0,0) FIELD NUMBER: IEN FIELD NAME: Internal Entry Number ACCESS: Pointed to FIELD DESCRIPTION: This is the Internal Entry number of the record in the IMAGE FILE. GENERAL DESCRIPTION: 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. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30316932 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING DETAILS: A many-to-many linkage between TIU Documents, stored in file 8925, and Images (stored in file #2005) is maintained by a pointer to the IMAGE FILE from the TIU EXTERNAL LINK FILE (#8925.91). NUMBER: 2928 IA #: 2928 GLOBAL ROOT: DIC( DATE CREATED: OCT 15, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Delete Read Protection on PDM Files ID: DIC( GLOBAL REFERENCE: DIC(51.2,0,'RD') GLOBAL REFERENCE: DIC(50.606,0,'RD') GENERAL DESCRIPTION: E3R PSN-4-12347 asked that the read protection on files related to and shared by National Drug File and Pharmacy Data Management be removed. To meet this request, PDM requests a one time agreement with VA Fileman to KILL the global nodes ^DIC(51.2,0,"RD") and ^DIC(50.606,0,"RD"). This this agreement is simular to and requested in conjunction with DBIA# 2910. VIEWER: SCHLEHUBER,CAMERON VIEWER: ALEXANDER,DAVID VIEWER: MONTALI,MICHAEL VIEWER: CHRISTENSEN,KIM VIEWER: DAVIS,DOUG VIEWER: TEMPLETON,SHANNON STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30262350 SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 2929 IA #: 2929 DATE CREATED: OCT 22, 1999 CUSTODIAL PACKAGE: NDBI CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: A7RHSM NAME: Health Summary/NDBI A7RHSM ID: A7RHSM GENERAL DESCRIPTION: National Database Integration routine A7RHSM contains entry points that extract patient data from the legacy site in an integrated system. VIEWER: ROWE,KIMBALL STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30360141 KEYWORDS: NDBI KEYWORDS: GMTS KEYWORDS: A7RHSM KEYWORDS: NATIONAL KEYWORDS: DATABASE KEYWORDS: INTEGRATION COMPONENT/ENTRY POINT: BT COMPONENT DESCRIPTION: Extract/display of Lab Blood Transfusion data from a legacy site (called by GMTSLRT). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient File VARIABLES: GMTSEG() TYPE: Input VARIABLES DESCRIPTION: Local Array of HS Components VARIABLES: GMTSEGN TYPE: Input VARIABLES DESCRIPTION: Pointer to Local Array of HS Components VARIABLES: GMTS1 TYPE: Input VARIABLES DESCRIPTION: Inverted Begin Date VARIABLES: GMTS2 TYPE: Input VARIABLES DESCRIPTION: Inverted End Date VARIABLES: GMTSNDM TYPE: Input VARIABLES DESCRIPTION: Occurrence Limit COMPONENT/ENTRY POINT: CH COMPONENT DESCRIPTION: Extract/display Lab Chemistry and Hematology data from the legacy site (called by GMTSLRC). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient File VARIABLES: GMTSEG() TYPE: Input VARIABLES DESCRIPTION: Local Array of HS Components VARIABLES: GMTSEGN TYPE: Input VARIABLES DESCRIPTION: Point to Local Array of HS Components VARIABLES: GMTS1 TYPE: Input VARIABLES DESCRIPTION: Inverted Begin Date VARIABLES: GMTS2 TYPE: Input VARIABLES DESCRIPTION: Inverted End Date VARIABLES: GMTSNDM TYPE: Input VARIABLES DESCRIPTION: Occurrence Limit COMPONENT/ENTRY POINT: CVP COMPONENT DESCRIPTION: Extract/display MAS Past Clinic Visits from the legacy site (called by GMTSDA). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient File VARIABLES: GMTSEG() TYPE: Input VARIABLES DESCRIPTION: Local Array of HS Components VARIABLES: GMTSEGN TYPE: Input VARIABLES DESCRIPTION: Pointer to Local Array of HS Components VARIABLES: GMTS1 TYPE: Input VARIABLES DESCRIPTION: Inverted Begin Date VARIABLES: GMTS2 TYPE: Input VARIABLES DESCRIPTION: Inverted End Date VARIABLES: GMTSNDM TYPE: Input VARIABLES DESCRIPTION: Occurrence Limit COMPONENT/ENTRY POINT: CY COMPONENT DESCRIPTION: Extract/display Lab Cytopathology data from the legacy site (called by GMTSLRCP). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patien File VARIABLES: GMTSEG() TYPE: Input VARIABLES DESCRIPTION: Local Array of HS Components VARIABLES: GMTSEGN TYPE: Input VARIABLES DESCRIPTION: Pointer to Local Array of HS Components VARIABLES: GMTS1 TYPE: Input VARIABLES DESCRIPTION: Inverted Begin Date VARIABLES: GMTS2 TYPE: Input VARIABLES DESCRIPTION: Inverted End Date VARIABLES: GMTSNDM TYPE: Input VARIABLES DESCRIPTION: Occurrence Limit COMPONENT/ENTRY POINT: DSP(ADM) COMPONENT DESCRIPTION: Display selected admissions data from the legacy site (called by GMTSDGA and GMTSDGH). VARIABLES: ADM TYPE: Input VARIABLES DESCRIPTION: Inverted Begin Date (same as GMTS1) VARIABLES: GMTSEG() TYPE: Input VARIABLES DESCRIPTION: Local Array of HS Components VARIABLES: GMTSEGN TYPE: Input VARIABLES DESCRIPTION: Pointer to Local Array of HS Components VARIABLES: A7RHS() TYPE: Input VARIABLES DESCRIPTION: Display Array COMPONENT/ENTRY POINT: LST(DFN,.A7RHS) COMPONENT DESCRIPTION: Extract/list admissions data from the legacy site (called by GMTSDGA, GMTSDGH, GMTSLRM, and GMTSLRMB). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient File VARIABLES: GMTSEG() TYPE: Input VARIABLES DESCRIPTION: Local Array of HS Components VARIABLES: GMTSEGN TYPE: Input VARIABLES DESCRIPTION: Pointer to Local Array of HS Components VARIABLES: A7RHS() TYPE: Output VARIABLES DESCRIPTION: Display Array COMPONENT/ENTRY POINT: MIC2(IX) COMPONENT DESCRIPTION: Extract/display Lab Microbiology data from the legacy site (called by GMTSLRM). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient File VARIABLES: IX TYPE: Input VARIABLES DESCRIPTION: Inverted Begin Date (same as GMTS1) VARIABLES: A7RHS() TYPE: Input VARIABLES DESCRIPTION: Display Array COMPONENT/ENTRY POINT: MIC3(IX) COMPONENT DESCRIPTION: Extract/display Lab Microbiology (Brief) data from the legacy site (called by GMTSLRMB). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient File VARIABLES: IX TYPE: Input VARIABLES DESCRIPTION: Inverted Begin Date (same as GMTS1) VARIABLES: A7RHS() TYPE: Input VARIABLES DESCRIPTION: Display Array COMPONENT/ENTRY POINT: $$NAM(TYPE,COMP) COMPONENT DESCRIPTION: Extract/display Component Subscript (Name.Abbr) from the legacy site (called by GMTSLRS, GMTSLRS7 and GMTSLRSC). VARIABLES: TYPE TYPE: Input VARIABLES DESCRIPTION: Pointer to HS Type File 142 VARIABLES: COMP TYPE: Input VARIABLES DESCRIPTION: Pointer to HS Component File 142.1 COMPONENT/ENTRY POINT: OPC COMPONENT DESCRIPTION: Extract/display MAS Surgeries ICD Codes from the legacy site (called by GMTSDGP). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient File VARIABLES: GMTSEG() TYPE: Input VARIABLES DESCRIPTION: Local Array of HS Components VARIABLES: GMTSEGN TYPE: Input VARIABLES DESCRIPTION: Pointer to Local Array of HS Components VARIABLES: GMTS1 TYPE: Input VARIABLES DESCRIPTION: Inverted Begin Date VARIABLES: GMTS2 TYPE: Input VARIABLES DESCRIPTION: Inverted End Date VARIABLES: GMTSNDM TYPE: Input VARIABLES DESCRIPTION: Occurrence Limit COMPONENT/ENTRY POINT: PRC COMPONENT DESCRIPTION: Extract/display MAS Procedure ICD Codes from the legacy site (called by GMTSDGP). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient File VARIABLES: GMTSEG() TYPE: Input VARIABLES DESCRIPTION: Local Array of HS Components VARIABLES: GMTSEGN TYPE: Input VARIABLES DESCRIPTION: Pointer to Local Array of HS Components VARIABLES: GMTS1 TYPE: Input VARIABLES DESCRIPTION: Inverted Begin Date VARIABLES: GMTS2 TYPE: Input VARIABLES DESCRIPTION: Inverted End Date VARIABLES: GMTSNDM TYPE: Input VARIABLES DESCRIPTION: Occurrence Limit COMPONENT/ENTRY POINT: $$PRTNAM(FLD,DFL) COMPONENT DESCRIPTION: Extract/display Laboratory Test Print Name from the legacy site (called by GMTSLRS7 and GMTSLRSC). VARIABLES: FLD TYPE: Input VARIABLES DESCRIPTION: Lab Test Name VARIABLES: DFL TYPE: Input VARIABLES DESCRIPTION: Default Name COMPONENT/ENTRY POINT: SCL COMPONENT DESCRIPTION: Extract/display Lab Cumulative Selected data from the legacy site (called by GMTSLRS7). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient File VARIABLES: GMTSEG() TYPE: Input VARIABLES DESCRIPTION: Local Array of HS Components VARIABLES: GMTSEGN TYPE: Input VARIABLES DESCRIPTION: Pointer to Local Array of HSS Components VARIABLES: GMTS1 TYPE: Input VARIABLES DESCRIPTION: Inverted Begin Date VARIABLES: GMTS2 TYPE: Input VARIABLES DESCRIPTION: Inverted End Date VARIABLES: GMTSNDM TYPE: Input VARIABLES DESCRIPTION: Occurrence Limit COMPONENT/ENTRY POINT: SCLU COMPONENT DESCRIPTION: Extract/display Lab Cumulative Selected data from the legacy site (called by GMTSLRSC). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient File VARIABLES: GMTSEG() TYPE: Input VARIABLES DESCRIPTION: Local Array of HS Components VARIABLES: GMTSEGN TYPE: Input VARIABLES DESCRIPTION: Pointer to Local Array of HS Components VARIABLES: GMTS1 TYPE: Input VARIABLES DESCRIPTION: Inverted Begin Date VARIABLES: GMTS2 TYPE: Input VARIABLES DESCRIPTION: Inverted End Date VARIABLES: GMTSNDM TYPE: Input VARIABLES DESCRIPTION: Occurrence Limit COMPONENT/ENTRY POINT: SLT COMPONENT DESCRIPTION: Extract/display Lab Tests Selected data from the legacy site (called by GMTSLRS). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient File VARIABLES: GMTSEG() TYPE: Input VARIABLES DESCRIPTION: Local Array of HS Components VARIABLES: GMTSEGN TYPE: Input VARIABLES DESCRIPTION: Pointer to Local Array of HS Components VARIABLES: GMTS1 TYPE: Input VARIABLES DESCRIPTION: Inverted Begin Date VARIABLES: GMTS2 TYPE: Input VARIABLES DESCRIPTION: Inverted End Date VARIABLES: GMTSNDM TYPE: Input VARIABLES DESCRIPTION: Occurrence Limit COMPONENT/ENTRY POINT: SP COMPONENT DESCRIPTION: Extract/display Surgical Pathology data from the legacy site (called by GMTSLRA). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient File VARIABLES: GMTSEG() TYPE: Input VARIABLES DESCRIPTION: Local Array of HS Components VARIABLES: GMTSEGN TYPE: Input VARIABLES DESCRIPTION: Pointer to Local Array of HS Components VARIABLES: GMTS1 TYPE: Input VARIABLES DESCRIPTION: Inverted Begin Date VARIABLES: GMTS2 TYPE: Input VARIABLES DESCRIPTION: Inverted End Date VARIABLES: GMTSNDM TYPE: Input VARIABLES DESCRIPTION: Occurrence Limit COMPONENT/ENTRY POINT: SW COMPONENT DESCRIPTION: Extract/display Social Work data from the legacy site (called by GMTSSOWK). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient File SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: The Health Summary package makes calls into the National Database Integration routine A7RHSM. This routine is used to extract patient health data from the legacy site in an integrated system. Calls into NDBI routine A7RHSM from Health Summary are contingent on: 1) the presence of the routine A7RDUP 2) the presence of the global ^A7RCP converted pointers 3) the presence of the called extract/format routine A7RHSM If any one of these three conditions is not met, then Health Summary will not make the call to the legacy site data extraction routine A7RHSM. NUMBER: 2930 IA #: 2930 FILE NUMBER: 509850.5 GLOBAL ROOT: ACK(509850.5, DATE CREATED: OCT 22, 1999 CUSTODIAL PACKAGE: QUASAR CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2930 ID: ACK(509850.5, GLOBAL REFERENCE: ACK(509850.5,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The #.01 field is a pointer to the CPT MODIFIER file (#81.3). GENERAL DESCRIPTION: In order to obtain CPT Modifier data, DSS EXTRACTS must obtain a pointer value from file #509850.5, A&SP MODIFIER. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30359059 SUBSCRIBING PACKAGE: DSS EXTRACTS ISC: Albany NUMBER: 2931 IA #: 2931 DATE CREATED: OCT 22, 1999 CUSTODIAL PACKAGE: NDBI CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: A7RPSOHS NAME: Health Summary/NDBI A7RPSOHS ID: A7RPSOHS GENERAL DESCRIPTION: National Database Integration routine A7RPSOHS contains an entry point that extracts patient data (Rx) from the legacy site in an integrated system. VIEWER: ROWE,KIMBALL STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30360184 KEYWORDS: NATIONAL KEYWORDS: DATABASE KEYWORDS: INTEGRATION KEYWORDS: A7RPSOHS KEYWORDS: GMTS KEYWORDS: NDBI COMPONENT/ENTRY POINT: HS(DFN) COMPONENT DESCRIPTION: Extract/display Out Patient Pharmacy data from the legacy site (called by GMTSPSO). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient File SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: The Health Summary package makes a call into three National Database Integration routine A7RPSOHS. This routine is used to extract patient health data (Rx) from the legacy site in an integrated system. Calls into NDBI routine A7RPSOHS from Health Summary are contingent on: 1) the presence of the routine A7RDUP 2) the presence of the global ^A7RCP converted pointers 3) the presence of the called extract/format routine A7RPSOHS If any one of these three conditions is not met, then Health Summary will not make the call to the legacy site data extraction routine A7RPSOHS. NUMBER: 2932 IA #: 2932 DATE CREATED: OCT 22, 1999 CUSTODIAL PACKAGE: NDBI CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: A7RHSE NAME: Health Summary/NDBI A7RHSE ID: A7RHSE GENERAL DESCRIPTION: National Database Integration routine A7RHSE contains an entry point that extracts patient data from the legacy site in an integrated system. VIEWER: ROWE,KIMBALL STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30360202 KEYWORDS: NATIONAL KEYWORDS: INTEGRATION KEYWORDS: DATABASE KEYWORDS: NDBI KEYWORDS: A7RHSE KEYWORDS: GMTS KEYWORDS: HEALTH KEYWORDS: SUMMARY COMPONENT/ENTRY POINT: LRDFN(DFN) COMPONENT DESCRIPTION: Get the Lab Patient pointer (LRDFN)from the legacy site (called by GMTSLRA, GMTSLRC, GMTSLRCP, GMTSLRM, GMTSLRMB, GMTSLRS, GMTSLRS7, and GMTSLRSC). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient File SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: Health Summary calls into routine A7RHSE for the purpose of retrieving the Laboratory Patient number (LRDFN) at the legacy site on an integrated system to extract laboratory data from the legacy site to be displayed with the primary site in a combined and integrated Health Summary. Calls into NDBI routine A7RHSE from Health Summary are contingent on: 1) the presence of the routine A7RDUP 2) the presence of the global ^A7RCP converted pointers 3) the presence of the called extract/format routine A7RHSE If any one of these three conditions is not met, then Health Summary will not make the call to the legacy site data extraction routine A7RHSE. NUMBER: 2933 IA #: 2933 FILE NUMBER: 73.1 GLOBAL ROOT: RAMIS(73.1 DATE CREATED: OCT 22, 1999 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2933 ID: RAMIS(73.1 GLOBAL REFERENCE: RAMIS(73.1,DA,0 FIELD NUMBER: .01 FIELD NAME: MODALITY ABBREVIATION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Contains the abbreviation of the modality (CT, CR, MRI, etc.). FIELD NUMBER: 1 FIELD NAME: MODALITY NAME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Contains the full name of the modality. GLOBAL DESCRIPTION: Global node contains the name of modality defined term as well as the abbreviation for the modality as defined in the DICOM Standards PS 3.3 - 1998 under section General Series Attribute Descriptions (C.7.3.1.1). GLOBAL REFERENCE: RAMIS(73.1,'B' GLOBAL DESCRIPTION: Cross reference on the modality defined term. GENERAL DESCRIPTION: Imaging requires to read the RAD MODALITY DEFINED TERMS file to build a Modality worklist for a commercial PACS system, commercial gateway or radiology modality. STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Reading of this file is needed to produce a modality worklist from all active Radiology orders. A worklist can be provided by specific modality. Each radiology order request has a RAD/NUC MED PROCEDURE defined and each of these procedures may have one or more modality defined. It is possible for a procedure to be performed on more than one modality (radiology equipment). In addition, we are requesting permission to read the "B" cross reference to match the modality code sent by a query during the testing of the worklist. The query is performed using the modality defined term, i.e., XA, DR, etc. Imaging is requesting direct reads to these global. Our experience in processing large volume of images (example: a CT request can be 500+ images and an image is processes in less than a second) is that using direct reads gives us a better system response time than a FM read. NUMBER: 2934 IA #: 2934 GLOBAL ROOT: A7RHS DATE CREATED: OCT 22, 1999 CUSTODIAL PACKAGE: NDBI CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Health Summary/NDBI Global ID: A7RHS GLOBAL REFERENCE: A7RHS('SP',DFN) GLOBAL DESCRIPTION: Contains the Surgical Pathology data for the legacy site for patient DFN (Pointer to the Patient File). GLOBAL REFERENCE: A7RHS('CH',DFN) GLOBAL DESCRIPTION: Contains the Chemistry and Hematology data for the legacy site for patient DFN (Pointer to the Patient File). GLOBAL REFERENCE: A7RHS('CY',DFN) GLOBAL DESCRIPTION: Contains the Cytopathology data for the legacy site for patient DFN (Pointer to the Patient File). GLOBAL REFERENCE: A7RHS('MIC',DFN) GLOBAL DESCRIPTION: Contains the Microbiology data for the legacy site for patient DFN (Pointer to the Patient File). GLOBAL REFERENCE: A7RHS('BMIC',DFN) GLOBAL DESCRIPTION: Contains the Microbiology (Brief) data for the legacy site for patient DFN (Pointer to the Patient File). GLOBAL REFERENCE: A7RHS('SUB',DFN) GLOBAL DESCRIPTION: Contains the Selected Laboratory data for the legacy site for patient DFN (Pointer to the Patient File). GENERAL DESCRIPTION: The National Database Integration software contains globals that store patient data from the legacy site in an integrated system. VIEWER: ROWE,KIMBALL STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30360521 KEYWORDS: NDBI KEYWORDS: GMTS KEYWORDS: NATIONAL KEYWORDS: DATABASE KEYWORDS: INTEGRATION KEYWORDS: A7RHS KEYWORDS: A7RCP SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: The Health Summary package references a National Database Integration global A7RHS(). Global A7RHS is used to store legacy site patient health care data. References to the NDBI global from Health Summary are contingent on: 1) the presence of the routine A7RDUP 2) the presence of the global ^A7RCP converted pointers 3) the presence of the called extract/format routine A7RHSM If any one of these three conditions is not met, then Health Summary will not reference global ^A7RHS for retrieval of the legacy site's patient data. NUMBER: 2935 IA #: 2935 FILE NUMBER: 51.7 GLOBAL ROOT: PS(51.7, DATE CREATED: FEB 08, 2000 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DRUG TEXT file ID: PS(51.7, GLOBAL REFERENCE: PS(51.7,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: INACTIVATION DATE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(51.7,D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: SYNONYM LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(51.7,D0,2,D1,0) FIELD NUMBER: .01 FIELD NAME: TEXT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: National Drug File (NDF) requests permission to do direct global reads on the Pharmacy Data Management's DRUG TEXT file (#51.7). This file stores rapidly changing drug restrictions, guidelines, and protocols to help assure medications are being used according to formulary specifications. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30284171 SUBSCRIBING PACKAGE: NATIONAL DRUG FILE ISC: Birmingham NUMBER: 2936 IA #: 2936 FILE NUMBER: 404.51 GLOBAL ROOT: SCTM(404.51, DATE CREATED: OCT 26, 1999 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMTS/SCTM Team ID: SCTM(404.51, GLOBAL REFERENCE: SCTM(404.51,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .02 FIELD NAME: TEAM PHONE NUMBER LOCATION: 0;2 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Health Summary extracts references the following data from the TEAM file (#404.51). The Demographic component of Health Summary prints the Team Name and and Team Phone Number of the Primary Care Team. VIEWER: ROWE,KIMBALL STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30375304 KEYWORDS: GMTS KEYWORDS: SCTM SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2937 IA #: 2937 FILE NUMBER: 8925 GLOBAL ROOT: TIU(8925, DATE CREATED: OCT 28, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR references to TIU DOCUMENT file ID: TIU(8925, CREATOR: HAWSEY,JASON GLOBAL REFERENCE: TIU(8925, FIELD NUMBER: .01 FIELD NAME: DOCUMENT TYPE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: PATIENT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .05 FIELD NAME: STATUS LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: PARENT LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .07 FIELD NAME: EPISODE BEGIN DATE/TIME LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .11 FIELD NAME: CREDIT STOP CODE ON COMPLETION LOCATION: 0;11 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .13 FIELD NAME: VISIT TYPE LOCATION: 0;13 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1202 FIELD NAME: AUTHOR/DICTATOR LOCATION: 12;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1204 FIELD NAME: EXPECTED SIGNER LOCATION: 12;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1208 FIELD NAME: EXPECTED COSIGNER LOCATION: 12;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1211 FIELD NAME: VISIT LOCATION LOCATION: 12;11 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1506 FIELD NAME: COSIGNER NEEDED LOCATION: 15;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1201 FIELD NAME: ENTRY DATE/TIME LOCATION: 12;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1301 FIELD NAME: REFERENCE DATE LOCATION: 13;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: TIU(8925,'AAU', GLOBAL REFERENCE: TIU(8925,'ASUP', GLOBAL REFERENCE: TIU(8925,'APT', GLOBAL REFERENCE: TIU(8925,'ACLPT', GENERAL DESCRIPTION: This DBIA documents references from OR* routines to the TIU DOCUMENT file (#8925). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30387939 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CARE MANAGEMENT ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL REMINDERS SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING DETAILS: ADDED 11/10/2010 DATE/TIME EDITED: NOV 10, 2010@12:13 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: TROMBETTA,KATHY WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 2938 IA #: 2938 DATE CREATED: OCT 28, 1999 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCGUIC NAME: OE/RR calls to GMRCGUIC ID: GMRCGUIC GENERAL DESCRIPTION: This DBIA documents calls from OE/RR to routine GMRCGUIC. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 COMPONENT/ENTRY POINT: FILE(IEN,GLOBAL) COMPONENT DESCRIPTION: Files changes made in CPRS GUI into consults files. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: The IEN of the entry in the REQUEST/CONSULTATION file (#123). VARIABLES: GLOBAL TYPE: Input VARIABLES DESCRIPTION: The TMP global location where the subscripted data exists for storage back into file 123 after edit. COMPONENT/ENTRY POINT: SEND(IEN,GLOBAL) COMPONENT DESCRIPTION: Sends data in a subscripted TMP global to calling application for further editing by the application (in this case CPRS GUI). VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: The IEN of the entry in the REQUEST/CONSULTATION file (#123). VARIABLES: GLOBAL TYPE: Input VARIABLES DESCRIPTION: The TMP global location where the subscripted data will be stored. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM EDITOR: RUTHERFORD,JERALD F DBA Comments: 6/3/14-MC: Brandon DeWayne originally requested to add FBCS as a subscriber to ICR 6/20/13. Approval received from Tony Thompson. Last email correspondence with Brandon was July 2013. Patch discovered to have been released 9/11/13 as an emergency patch. Since approval has been received and patch has been released, adding FBCS as a subscribing package to this ICR. NUMBER: 2939 IA #: 2939 FILE NUMBER: 49 GLOBAL ROOT: DIC(49, DATE CREATED: OCT 28, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR direct views of DIC(49 ID: DIC(49, GLOBAL REFERENCE: DIC(49,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.7 FIELD NAME: TYPE OF SERVICE LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DIC(49,'B' GLOBAL DESCRIPTION: Used by CPRS GUI to loop through available entries and ensure that the TYPE OF SERVICE is PATIENT CARE. The entries are then presented to the user in the graphical interface. GENERAL DESCRIPTION: This DBIA documents direct global references made by OE/RR to the SERVICE/SECTION file (#49). These references are mainly used by CPRS GUI to retrieve and display a list of selectable entries from file 49. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26892491 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2941 IA #: 2941 DATE CREATED: OCT 28, 1999 CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MPIFSAQ NAME: DBIA2941 ID: MPIFSAQ GENERAL DESCRIPTION: CIRN PD uses this call to allow users to do a Display Only Query to the MPI through the CIRN Exception Handling option. STATUS: Active MAIL MESSAGE: 30389798 COMPONENT/ENTRY POINT: VTQ VARIABLES: .MPIVAR TYPE: Input VARIABLES DESCRIPTION: The MPIVAR array consists of the following demographic data: MPIVAR("DFN") - DFN - IEN of Patient file (#2) MPIVAR("SSN") - Social Security Number (.09) field of Patient file (#2) MPIVAR("DOB") - Date of Birth (.03) field of Patient file (#2) MPIVAR("NM") - Name (.01) field of Patient file (#2) SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 2942 IA #: 2942 DATE CREATED: OCT 28, 1999 CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MPIFQ0 NAME: DBIA2942 ID: MPIFQ0 GENERAL DESCRIPTION: CIRN PD uses this call to allow users to do a Single Patient Initialization to the MPI from the CIRN Exception Handling option. STATUS: Active MAIL MESSAGE: 30389777 COMPONENT/ENTRY POINT: CIRNEXC COMPONENT DESCRIPTION: This entry point assumes the DFN is known and does not prompt the user for Patient Name. VARIABLES: DFN TYPE: Used VARIABLES DESCRIPTION: IEN of patient in Patient File (#2) SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 2944 IA #: 2944 DATE CREATED: OCT 29, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUSRVR1 NAME: Calls to TIUSRVR1 ID: TIUSRVR1 GENERAL DESCRIPTION: This DBIA documents calls to TIUSRVR1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34774117 COMPONENT/ENTRY POINT: TGET(.GLOBAL,IEN,ACTION) COMPONENT DESCRIPTION: This API returns the textual portion of a TIU document Record. It's also callable via RPC TIU GET RECORD TEXT. VARIABLES: GLOBAL TYPE: Both VARIABLES DESCRIPTION: The global location of the returned data (^TMP("TIUVIEW",$J)) is returned in this variable which is passed by reference. ^TMP("TIUVIEW",$J) may be killed before and after use. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: The IEN of the record from the TIU DOCUMENT file. VARIABLES: ACTION TYPE: Input VARIABLES DESCRIPTION: This optional String type parameter identifies the action (e.g., PRINT, or VIEW) that the user is attempting to execute (DEFAULT: VIEW). SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING SUBSCRIBING PACKAGE: SURGERY SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING DETAILS: added 10/21/2008 SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: ADDED 7/25/07 SUBSCRIBING PACKAGE: NATIONAL HEALTH INFO NETWORK SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD DBA Comments: 6/26/12-mm: VPR added as a subscriber for VPR*1.0. Approved by Margy McClenehan, Andrw Bakke, and Joel Russell. DATE/TIME EDITED: OCT 22, 2008@02:08 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: GREEN,STEVE WITH CONCURRENCE OF: ANZALDUA,CAROL DATE/TIME EDITED: JUL 25, 2007@09:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HSU,YUI WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: SEP 16, 2010@10:57 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE DATE/TIME EDITED: JUN 26, 2012@14:56 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: MCCLENEHAN,MARGY DATE/TIME EDITED: JUN 26, 2012@14:57 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: BAKKE,ANDREW DATE/TIME EDITED: JUN 26, 2012@14:58 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: RUSSELL,JOEL NUMBER: 2945 IA #: 2945 DATE CREATED: OCT 29, 1999 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSIVSP NAME: Use of calls in PSIVSP ID: PSIVSP GENERAL DESCRIPTION: This DBIA documents calls to PSIVSP. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946673 COMPONENT/ENTRY POINT: ORINF COMPONENT DESCRIPTION: This entry point acts as an input transform for infusion rate. VARIABLES: X TYPE: Both VARIABLES DESCRIPTION: X is passed in as the value to be passed through the input transform. If X is returned, it is a valid infusion rate. If X is not returned, the input was rejected. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: OE/RR calls ORINF NUMBER: 2946 IA #: 2946 DATE CREATED: OCT 29, 1999 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSSGSGUI NAME: Calls to PSSGSGUI ID: PSSGSGUI GENERAL DESCRIPTION: This call provides a Schedule validation check for medication orders entered through Computerized Patient Record System (CPRS). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33152565 COMPONENT/ENTRY POINT: EN(X,PSSGUIPK) COMPONENT DESCRIPTION: This call is used by CPRS GUI to validate a Schedule that is entered for a medication order. This call is non-interactive (silent). VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: This variable is passed by reference. It is the Schedule entered for the medication order. VARIABLES: PSSGUIPK TYPE: Input VARIABLES DESCRIPTION: This variable is the pharmacy package for which the order is being entered. "O" will be for Outpatient orders, "I" will be for Inpatient orders. VARIABLES: X TYPE: Output VARIABLES DESCRIPTION: If the Schedule passed the validation checks, the value will be the Schedule, as it was passed in. If the Schedule did not pass the validation checks, this variable will be undefined. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2947 IA #: 2947 DATE CREATED: OCT 29, 1999 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORWLRR NAME: Calls to LR7OGO ID: ORWLRR GENERAL DESCRIPTION: This DBIA documents calls to routine LR7OGO. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946458 COMPONENT/ENTRY POINT: ALLTESTS(.ARRAY,FROM,DIRECTION) COMPONENT DESCRIPTION: Returns 45 test names beginning with the value FROM in either forward or reverse alphabetical order. VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: Passed in as the name of an array and returned with the lab test names. VARIABLES: FROM TYPE: Input VARIABLES DESCRIPTION: Starting point for loop through LABORATORY TEST file by name. VARIABLES: DIRECTION TYPE: Input VARIABLES DESCRIPTION: -1 for reverse order or "" for forward order COMPONENT/ENTRY POINT: ATESTS(.ARRAY,IEN) COMPONENT DESCRIPTION: Returns an array of lab tests included in a panel. VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: Input as name of array and receives array of panels for test specified. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of the LABORATORY TEST file (#60). COMPONENT/ENTRY POINT: ATG(.ARRAY,TESTGROUP,USER) COMPONENT DESCRIPTION: Returns an array of chemistry tests in a group for a particular user. VARIABLES: USER TYPE: Input VARIABLES DESCRIPTION: Pointer to NEW PERSON file (#200). VARIABLES: TESTGROUP TYPE: Input VARIABLES DESCRIPTION: Value of LAB TEST GROUP field from LAB SECTION PRINT file (69.2) COMPONENT/ENTRY POINT: ATOMICS(.ARRAY,FROM,DIR) COMPONENT DESCRIPTION: Returns an array of atomic lab tests (tests without panels). VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: see description for ALLTESTS VARIABLES: FROM TYPE: Input VARIABLES DESCRIPTION: see description in ALLTESTS VARIABLES: DIR TYPE: Input VARIABLES DESCRIPTION: See description in ALLTESTS COMPONENT/ENTRY POINT: CHEMTEST(.ARRAY,FROM,DIR) COMPONENT DESCRIPTION: Returns an array of test names from the CHEM, HEM, TOX, SER, RIA, ETC. areas of lab. VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: See description under ALLTESTS. VARIABLES: FROM TYPE: Input VARIABLES DESCRIPTION: See description under ALLTESTS. VARIABLES: DIR TYPE: Input VARIABLES DESCRIPTION: See description under ALLTESTS. COMPONENT/ENTRY POINT: PARAM(.VALUE) COMPONENT DESCRIPTION: Returns the Laboratory Site parameters found in the LABORATORY SITE (#69.9) file at the global location ^LAB(69.9,1,1). VARIABLES: VALUE TYPE: Output VARIABLES DESCRIPTION: 1 node from LABORATORY SITE file currently defined as: ^LAB(69.9,D0,1)= (#100) DEFAULT BLOOD SPECIMEN [1P] ^ (#101) DEFAULT URINE SPECIMEN [2P] ^ (#102) DEFAULT SERUM SPECIMEN [3P] ^ ==>(#103) DEFAULT PLASMA SPECIMEN [4P] ^ (#104) DEFAULT UNKNOWN SPECIMEN [5P] ^ ^ (#210) DOWNLOAD FULL DATA [7S] ^ ==>(#530) STANDARD LOCATIONS ONLY [8S] ^ (#18) *GRACE PERIOD FOR STATISTICS [9N] ^ (#203) MICRO DEFAULT TEMPLATE ==>[10F] ^ (#204) MICRO OTHER TEMPLATE [11F] ^ COMPONENT/ENTRY POINT: SPEC(.ARRAY,FROM,DIR) COMPONENT DESCRIPTION: Returns an array of lab specimens from the TOPOGRAPHY FIELD (#61) file in the format IEN^NAME. VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: Passed in as the name of the array to receive data. Data returned as ARRAY(COUNTER)=IEN^NAME VARIABLES: FROM TYPE: Input VARIABLES DESCRIPTION: Starting name for search. A maximum of 45 entries are returned at a time. VARIABLES: DIR TYPE: Input VARIABLES DESCRIPTION: See ALLTESTS for description of this variable. COMPONENT/ENTRY POINT: TG(.ARRAY,USER) COMPONENT DESCRIPTION: Returns a list of chemistry test groups associated with a user with the print names (or name if print name is not available) of the lab tests in the panel separated by commas. So, output would look like: ARRAY(COUNT)=TESTGROUP IEN^TESTGROUP) PRINT NAME, PRINT NAME Or actual example: ARRAY(1)=1^1) WBC, RBC, HCT, HB, PLT VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: See description under ALLTESTS VARIABLES: USER TYPE: Input VARIABLES DESCRIPTION: IEN of NEW PERSON file (#200) COMPONENT/ENTRY POINT: USERS(.ARRAY,FROM,DIR) COMPONENT DESCRIPTION: Loops through the NEW PERSON file an returns up to 18 users that have chemistry LAB TEST GROUPS defined. Format ARRAY(COUNT)=IEN^USERNAME Where IEN is the IEN of the USER REQUEST LIST multiple in the LAB SECTION PRINT file (#69.2). VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: See description under ALLTESTS VARIABLES: FROM TYPE: Input VARIABLES DESCRIPTION: Name of NEW PERSON from which to begin search. VARIABLES: DIR TYPE: Input VARIABLES DESCRIPTION: See description under ALLTESTS COMPONENT/ENTRY POINT: UTGA(.Y,TESTS) COMPONENT DESCRIPTION: Places entries in the USER REQUEST LIST multiple of the LAB SECTION PRINT file (#69.2). VARIABLES: Y TYPE: Input VARIABLES DESCRIPTION: Placeholder for RPC usage VARIABLES: TESTS TYPE: Input VARIABLES DESCRIPTION: Array of data to be filed in USER REQUEST LIST multiple COMPONENT/ENTRY POINT: UTGD(.Y,TESTGROUP) COMPONENT DESCRIPTION: Deletes data from the USER REQUEST LIST multiple for a specified TEST GROUP. VARIABLES: Y TYPE: Input VARIABLES DESCRIPTION: Placeholder for RPC usage VARIABLES: TESTGROUP TYPE: Input VARIABLES DESCRIPTION: IEN of LAB TEST GROUP multiple of LAB SECTION PRINT file (#69.2) COMPONENT/ENTRY POINT: UTGR(.Y,TESTS,TESTGROUP) COMPONENT DESCRIPTION: Updates TEST multiple under LAB TEST GROUP multiple in file 69.2. VARIABLES: TESTS TYPE: Input VARIABLES DESCRIPTION: Array of tests to be entered into TESTS subfield of LAB TEST GROUP multiple. VARIABLES: TESTGROUP TYPE: Input VARIABLES DESCRIPTION: IEN of TEST GROUP multiple for which TEST entries will be replaced. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: Routine ORWLRR makes calls to the following linetags in LR7OGO: ALLTESTS ATESTS ATG ATOMICS CHEMTEST PARAM SPEC TG USERS UTGA UTGD UTGR The matching linetags in ORWLRR are called by RPCs for use in CPRS GUI. SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES NUMBER: 2950 IA #: 2950 DATE CREATED: APR 16, 2003 CUSTODIAL PACKAGE: LEXICON UTILITY CUSTODIAL ISC: Dallas USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LEXA NAME: DBIA2950 ID: LEXA GENERAL DESCRIPTION: This entry point is silent and intended to support Graphical User Interface (GUI) development. The lookup returns an array of information on the expressions found. The lookup includes reordering the selection list with the most frequently used at the top, and places any exact match at the top of the list. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 36044876 COMPONENT/ENTRY POINT: LOOK(LEXX,LEXAP,LEXLL,LEXSUB,DATE) VARIABLES: LEXX TYPE: Input VARIABLES DESCRIPTION: Equivalent to Fileman's variable X and contains the text to search for. VARIABLES: LEXAP TYPE: Input VARIABLES DESCRIPTION: This is the aplication identification and may be in the form of a name, namespace, or a pointer (Internal Entry Number - IEN) from an application definition in the Subset Definition file (#757.2). The default value for this parameter, if it is not supplied, is the one (1), pointing to the Lexicon application definition. Included in this application definition are a number of applications defaults which assist in searching the Lexicon. Application defaults included the global root, index, filter, display format, vocabulary, shortcuts, user default flag, overwrite user default flag, and the unresolved narrative flag. These are described in the Special Variable section of the Lexicon Utility V. 2.0 Technical Manual. At this time, there are six (6) application definitions. Name Namspace IEN ---- -------- --- Lexicon LEX 1 Problem List GMPL 4 ICD Diagnosis ICD 12 CPT Procedures CPT 13 Mental Health DSM 14 ICD, CPT, and DSM Terminology VAC 15 To conduct a search of the Lexicon using the application defaults for the Problem List, you may pass this parameter as: Name "PROBLEM LIST" - This form is not case sensitive, and can be found either the "B" or "C" index of file 757.2. Namespace "GMPL" - Namespace - This form is not case sensitive, and can be found in the "AN" index of file 757.2. Pointer 4 - This form is numeric, and is an Internal Entry Number (IEN) of file 757.2. VARIABLES: LEXLL TYPE: Input VARIABLES DESCRIPTION: This is a numeric value which controls the returning list length in the local array LEX("LIST"). The default value for this parameter when not supplied is five (5). VARIABLES: LEXSUB TYPE: Input VARIABLES DESCRIPTION: This parameter represent the vocabulary subset to use during the search. These subsets are defined in the Subset Definition file (#757.2). This parameter may be in one of three forms. To use the "Nursing" subset you may pass the parameter as: Name "NURSING" - This form is not case sensitive and may be found in either the "B" or "C" index of file 757.2. Mnemonic "NUR" - This form is not case sensitive and the mnemonic may be found in either the "AA" or "AB" index of file 757.2. Pointer 2 - This form is numeric, and is an Internal Entry Number (IEN) of file 757.2. VARIABLES: TMP TYPE: Output VARIABLES DESCRIPTION: ^TMP("LEXFND",$J,,) This global array contains all of the entries found during the search. The is a negative number based on the frequency of use for a given term. is the internal entry number in the Lexicon Expression file (757.01). ^TMP("LEXHIT",$J,) This global array contains the entries reviewed by the user. The Lexicon Utility reorders the list based on frequency of use and assigns a sequence number representing where on the list this entry is located. VARIABLES: LEX TYPE: Output VARIABLES DESCRIPTION: LEX("LIST") This local array contains only those entries on the list which are currently being reviewed by the user. The third parameter to the look-up defines the length of this list. VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: This is a date in Fileman format used to check if a code is active or inactive on a specified date. If not supplied, it will default to TODAY. Only active codes can be displayed and returned during a lookup. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City EDITOR: BAYLIS,RANDALL S EDITOR: KEOHAN,PAUL EDITOR: EDKINS,CHRIS EDITOR: FRANKSON,FERDINAND NUMBER: 2951 IA #: 2951 DATE CREATED: NOV 01, 1999 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LR7OSBR NAME: LR7OSBR ID: LR7OSBR GENERAL DESCRIPTION: This DBIA documents calls to LR7OSBR to retrieve the formatted text of a Blood Bank report for a patient. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946458 COMPONENT/ENTRY POINT: EN1(DFN) COMPONENT DESCRIPTION: Returns formatted text of a Blood Bank report. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient file #2 VARIABLES: TMP('LRC' TYPE: Output VARIABLES DESCRIPTION: ^TMP("LRC",$J,#,0)=line of report text SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CARE MANAGEMENT EDITOR: INSLEY,MARCIA EDITOR: BUECHLER,MELANIE K NUMBER: 2952 IA #: 2952 DATE CREATED: NOV 01, 1999 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LR7OSMZ0 NAME: LR7OSMZ0 ID: LR7OSMZ0 GENERAL DESCRIPTION: This DBIA documents calls to LR7OSMZ0 to retrieve the formatted text of a Microbiology report for a patient. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946458 COMPONENT/ENTRY POINT: EN(DFN) COMPONENT DESCRIPTION: Returns formatted text of a Microbiology report. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient file #2 VARIABLES: TMP('LRC' TYPE: Output VARIABLES DESCRIPTION: ^TMP("LRC",$J,#,0)=line of report text SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CARE MANAGEMENT EDITOR: INSLEY,MARCIA EDITOR: BUECHLER,MELANIE K NUMBER: 2953 IA #: 2953 FILE NUMBER: 409.68 GLOBAL ROOT: SCE( DATE CREATED: NOV 02, 1999 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: STATUS OF PATIENT IN THE OUTPATIENT ENCOUNTER FILE ID: SCE( GLOBAL REFERENCE: SCE('ADFN', FIELD NUMBER: .02 FIELD NAME: PATIENT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is named Patient and points to the PATIENT (#2) file. This DBIA is concerned with traversing the 'ADFN' M cross-reference to find an OUTPATIENT ENCOUNTER record with a status of CHECKED OUT. GENERAL DESCRIPTION: This database integration agreement (DBIA) is needed to track a particular status of a patient in the OUTPATIENT ENCOUNTER (#409.68) file. The input variable is the DFN of the patient, so our application needs to roll down the 'ADFN' M cross-reference (Patient field) in file 409.68. Our application intends to read, with FileMan, the STATUS (field .12) of the patient in the OUTPATIENT ENCOUNTER (#409.68) file. We are looking for a private subscription that would allow our application to walk down the 'ADFN' cross-reference and then read, with FileMan, the STATUS field in the OUTPATIENT ENCOUNTER file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30422771 KEYWORDS: ADFN KEYWORDS: OUTPATIENT ENCOUNTER SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 2954 IA #: 2954 DATE CREATED: NOV 04, 1999 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LR7OGG NAME: Calls to LR7OGG ID: LR7OGG GENERAL DESCRIPTION: This DBIA documents calls made to routine LR7OGG STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946458 COMPONENT/ENTRY POINT: GRID(.ROOT,DFN,END,START,SPECTYPE,.TESTS) COMPONENT DESCRIPTION: Returns data for display of labs on grid controls within CPRS lab tab. Data returned: ^TMP("LR7OGX",$J,"INPUT",1)=DFN^END DATE^START DATE^SPECTYPE ,2-n)=lab test number ^TMP("LR7OGX",$J,"OUTPUT",n)=TestSequence^TestNumber^TestName^PrintCode followed by specifics of tests such as comments or indications VARIABLES: .ROOT TYPE: Output VARIABLES DESCRIPTION: Returns root of output data. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of PATIENT file VARIABLES: START TYPE: Input VARIABLES DESCRIPTION: Start date VARIABLES: END TYPE: Input VARIABLES DESCRIPTION: End date VARIABLES: SPECTYPE TYPE: Input VARIABLES DESCRIPTION: Specimen type to be returned VARIABLES: .TESTS TYPE: Input VARIABLES DESCRIPTION: Array of tests to be on grid display VARIABLES: ~TMP("LR7OGX",$J, TYPE: Output VARIABLES DESCRIPTION: Array may be killed prior to GRID call as well as after. VARIABLES: ~TMP("LR7OG",$J, TYPE: Output VARIABLES DESCRIPTION: Array may be killed prior to GRID call as well as after. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2955 IA #: 2955 DATE CREATED: NOV 03, 1999 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LR7OU1 NAME: Calls to LR7OU1 ID: LR7OU1 CREATOR: BUECHLER,MELANIE K GENERAL DESCRIPTION: This DBIA documents calls to routine LR7OU1 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946458 COMPONENT/ENTRY POINT: $$COL(PKGREF,IEN) COMPONENT DESCRIPTION: Returns collection sample with tube type for print fields. VARIABLES: PKGREF TYPE: Input VARIABLES DESCRIPTION: Value as stored in the PACKAGE REFERENCE field in the ORDER file (#100). VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Optional: IEN of ORDER file (#100) VARIABLES: OUTPUT TYPE: Output VARIABLES DESCRIPTION: Extrinsic function returns NAME (#.01)_(space)_TUBE TOP COLOR (#3) fields from COLLECTION SAMPLE file (#62). COMPONENT/ENTRY POINT: $$LU(PKGREF,IEN) COMPONENT DESCRIPTION: Extrinsic function returns urgency for print fields. VARIABLES: PKGREF TYPE: Input VARIABLES DESCRIPTION: Value as stored in the PACKAGE REFERENCE field in the ORDER file (#100). VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Optional: IEN of ORDER file (#100) VARIABLES: OUTPUT TYPE: Output VARIABLES DESCRIPTION: Extrinsic function returns external value of URGENCY file (#62.05). COMPONENT/ENTRY POINT: EXPAND(TEST,ARRAY) COMPONENT DESCRIPTION: Expand a lab panel into its atomic tests VARIABLES: TEST TYPE: Input VARIABLES DESCRIPTION: IEN of panel in LAB TEST file (#60) VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: Array passed by reference, that returns the IEN of LAB TEST file (#60) for each atomic test as a list subscript, i.e. ARRAY(IEN)="" SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD DBA Comments: 5/24/12-VPR added as a subscriber for VPR*1.0. Added EXPAND entry point. DATE ACTIVATED: MAY 24, 2012 DATE/TIME EDITED: AUG 01, 2011@22:38 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: BUECHLER,MELANIE DATE/TIME EDITED: MAY 24, 2012@15:05 ACTION: APPROVED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: ANZALDUA,CAROL NUMBER: 2956 IA #: 2956 DATE CREATED: NOV 03, 1999 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LR7OGC NAME: Calls to LR7OGC ID: LR7OGC GENERAL DESCRIPTION: This DBIA documents calls made to routine LR7OGC. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946458 COMPONENT/ENTRY POINT: CHART(.ARRAY,DFN,END,START,SPECTYPE,TESTNUM) COMPONENT DESCRIPTION: Returns ^TMP("LR7OGX",$J,"OUTPUT",counter) Data varies as top of the array contains DATE/TIME SPECIMEN TAKEN^RESULT Later, external format of the date/time is shown along with comments, interpretations, or other notes. Here are some examples of what might appear: ^TMP("LR7OGX",539019167,"OUTPUT",1) = 44^SERUM^123^60^mg/dL ^TMP("LR7OGX",539019167,"OUTPUT",2) = 2991026.150931^500 ^TMP("LR7OGX",539019167,"OUTPUT",3) = 2990914.07205^105 ^TMP("LR7OGX",539019167,"OUTPUT",4) = 2990914.071727^85 ^TMP("LR7OGX",539019167,"OUTPUT",5) = 2990914.071648^65 ^TMP("LR7OGX",539019167,"OUTPUT",6) = 2990914.071522^45 ^TMP("LR7OGX",539019167,"OUTPUT",7) = 2990907.074908^325 ^TMP("LR7OGX",539019167,"OUTPUT",8) = 2990907.074728^345 ^TMP("LR7OGX",539019167,"OUTPUT",9) = 2990824.154928^302 ^TMP("LR7OGX",539019167,"OUTPUT",10) = 2990824.154643^301 ^TMP("LR7OGX",539019167,"OUTPUT",11) = 2990729.112056^329 ^TMP("LR7OGX",539019167,"OUTPUT",12) = 2990729.110217^325 ^TMP("LR7OGX",539019167,"OUTPUT",13) = 2990729.110003^300 ^TMP("LR7OGX",539019167,"OUTPUT",14) = 2990525.105108^123 ^TMP("LR7OGX",539019167,"OUTPUT",15) = 2990525.10134^234 ^TMP("LR7OGX",539019167,"OUTPUT",16) = 2990525.091542^156 ^TMP("LR7OGX",539019167,"OUTPUT",17) = 2990111.143859^98 ^TMP("LR7OGX",539019167,"OUTPUT",18) = 2990111.143854^443 ^TMP("LR7OGX",539019167,"OUTPUT",19) = 2990111.143851^89 ^TMP("LR7OGX",539019167,"OUTPUT",20) = 2990111.143846^143 ^TMP("LR7OGX",539019167,"OUTPUT",21) = 2990111.143841^153 ^TMP("LR7OGX",539019167,"OUTPUT",22) = 2990111.143837^62 ^TMP("LR7OGX",539019167,"OUTPUT",23) = 2990111.143832^155 ^TMP("LR7OGX",539019167,"OUTPUT",24) = 2990111.143829^15 ^TMP("LR7OGX",539019167,"OUTPUT",25) = 2990111.143824^90 ^TMP("LR7OGX",539019167,"OUTPUT",26) = 2990111.14382^66 ^TMP("LR7OGX",539019167,"OUTPUT",27) = 2990111.143816^166 ^TMP("LR7OGX",539019167,"OUTPUT",28) = 2990111.143809^431 ^TMP("LR7OGX",539019167,"OUTPUT",29) = 2990111.143805^312 ^TMP("LR7OGX",539019167,"OUTPUT",30) = 2990111.1438^98 ^TMP("LR7OGX",539019167,"OUTPUT",31) = 2990111.143756^234 ^TMP("LR7OGX",539019167,"OUTPUT",32) = 2990111.143751^170 ^TMP("LR7OGX",539019167,"OUTPUT",33) = 2990111.143747^55 ^TMP("LR7OGX",539019167,"OUTPUT",34) = 2990111.143742^155 ^TMP("LR7OGX",539019167,"OUTPUT",35) = 2990111.143737^144 ^TMP("LR7OGX",539019167,"OUTPUT",36) = 2990111.143732^980 ^TMP("LR7OGX",539019167,"OUTPUT",37) = 2990111.143725^89 ^TMP("LR7OGX",539019167,"OUTPUT",38) = 2990111.143719^52 ^TMP("LR7OGX",539019167,"OUTPUT",39) = 2990111.143708^87 ^TMP("LR7OGX",539019167,"OUTPUT",40) = 2990111.143701^133 ^TMP("LR7OGX",539019167,"OUTPUT",41) = 2990111.143653^156 ^TMP("LR7OGX",539019167,"OUTPUT",42) = 2990111.143644^99 ^TMP("LR7OGX",539019167,"OUTPUT",43) = 2990111.143628^153 ^TMP("LR7OGX",539019167,"OUTPUT",44) = 2990111.14362^155 ^TMP("LR7OGX",539019167,"OUTPUT",45) = 2990111.143559^133 ^TMP("LR7OGX",539019167,"OUTPUT",46) = ^TMP("LR7OGX",539019167,"OUTPUT",47) = Sep 07, 1999@07:49 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",48) = This specimen was not drawn from above th e IV site. ^TMP("LR7OGX",539019167,"OUTPUT",49) = ^TMP("LR7OGX",539019167,"OUTPUT",50) = Sep 07, 1999@07:47 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",51) = ~For Test: GLUCOSE ^TMP("LR7OGX",539019167,"OUTPUT",52) = ~NO ORDER COMMENT AT THIS TIME ^TMP("LR7OGX",539019167,"OUTPUT",53) = TESTING COMMENTS ON THE GUI LAB TAB ^TMP("LR7OGX",539019167,"OUTPUT",54) = ^TMP("LR7OGX",539019167,"OUTPUT",55) = May 25, 1999@10:52 -- result 'canc' could not be graphed. ^TMP("LR7OGX",539019167,"OUTPUT",56) = ^TMP("LR7OGX",539019167,"OUTPUT",57) = May 25, 1999@10:15 -- result 'canc' could not be graphed. ^TMP("LR7OGX",539019167,"OUTPUT",58) = ^TMP("LR7OGX",539019167,"OUTPUT",59) = May 25, 1999@10:11 -- result 'canc' could not be graphed. ^TMP("LR7OGX",539019167,"OUTPUT",60) = ^TMP("LR7OGX",539019167,"OUTPUT",61) = May 24, 1999@11:37 -- result 'canc' could not be graphed. ^TMP("LR7OGX",539019167,"OUTPUT",62) = ^TMP("LR7OGX",539019167,"OUTPUT",63) = May 24, 1999@11:32 -- result 'canc' could not be graphed. ^TMP("LR7OGX",539019167,"OUTPUT",64) = ^TMP("LR7OGX",539019167,"OUTPUT",65) = May 21, 1999@09:45 -- result 'canc' could not be graphed. ^TMP("LR7OGX",539019167,"OUTPUT",66) = ^TMP("LR7OGX",539019167,"OUTPUT",67) = Jan 11, 1999@14:38 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",68) = 1507 ^TMP("LR7OGX",539019167,"OUTPUT",69) = ^TMP("LR7OGX",539019167,"OUTPUT",70) = Jan 11, 1999@14:38 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",71) = PATETS ^TMP("LR7OGX",539019167,"OUTPUT",72) = ^TMP("LR7OGX",539019167,"OUTPUT",73) = Jan 11, 1999@14:38 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",74) = 134 ^TMP("LR7OGX",539019167,"OUTPUT",75) = ^TMP("LR7OGX",539019167,"OUTPUT",76) = Jan 11, 1999@14:38 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",77) = 09878312 ^TMP("LR7OGX",539019167,"OUTPUT",78) = ^TMP("LR7OGX",539019167,"OUTPUT",79) = Jan 11, 1999@14:38 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",80) = ASDPTW ^TMP("LR7OGX",539019167,"OUTPUT",81) = ^TMP("LR7OGX",539019167,"OUTPUT",82) = Jan 11, 1999@14:38 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",83) = 134 ^TMP("LR7OGX",539019167,"OUTPUT",84) = ^TMP("LR7OGX",539019167,"OUTPUT",85) = Jan 11, 1999@14:38 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",86) = ABOUT HTERE ^TMP("LR7OGX",539019167,"OUTPUT",87) = ^TMP("LR7OGX",539019167,"OUTPUT",88) = Jan 11, 1999@14:38 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",89) = VLOW ^TMP("LR7OGX",539019167,"OUTPUT",90) = ^TMP("LR7OGX",539019167,"OUTPUT",91) = Jan 11, 1999@14:38 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",92) = BET ^TMP("LR7OGX",539019167,"OUTPUT",93) = ^TMP("LR7OGX",539019167,"OUTPUT",94) = Jan 11, 1999@14:38 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",95) = LO ^TMP("LR7OGX",539019167,"OUTPUT",96) = ^TMP("LR7OGX",539019167,"OUTPUT",97) = Jan 11, 1999@14:38 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",98) = PATPE ^TMP("LR7OGX",539019167,"OUTPUT",99) = ^TMP("LR7OGX",539019167,"OUTPUT",100) = Jan 11, 1999@14:38 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",101) = HILT EI TAT ^TMP("LR7OGX",539019167,"OUTPUT",102) = ^TMP("LR7OGX",539019167,"OUTPUT",103) = Jan 11, 1999@14:38 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",104) = ADSFGAHQRET ^TMP("LR7OGX",539019167,"OUTPUT",105) = ^TMP("LR7OGX",539019167,"OUTPUT",106) = Jan 11, 1999@14:38 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",107) = MAUT ^TMP("LR7OGX",539019167,"OUTPUT",108) = ^TMP("LR7OGX",539019167,"OUTPUT",109) = Jan 11, 1999@14:37 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",110) = ASDFREQ ^TMP("LR7OGX",539019167,"OUTPUT",111) = ^TMP("LR7OGX",539019167,"OUTPUT",112) = Jan 11, 1999@14:37 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",113) = APOET ^TMP("LR7OGX",539019167,"OUTPUT",114) = ^TMP("LR7OGX",539019167,"OUTPUT",115) = Jan 11, 1999@14:37 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",116) = ADSF ^TMP("LR7OGX",539019167,"OUTPUT",117) = ^TMP("LR7OGX",539019167,"OUTPUT",118) = Jan 11, 1999@14:37 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",119) = 14 ^TMP("LR7OGX",539019167,"OUTPUT",120) = ^TMP("LR7OGX",539019167,"OUTPUT",121) = Jan 11, 1999@14:37 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",122) = RECA ^TMP("LR7OGX",539019167,"OUTPUT",123) = ^TMP("LR7OGX",539019167,"OUTPUT",124) = Jan 11, 1999@14:37 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",125) = HIGH ^TMP("LR7OGX",539019167,"OUTPUT",126) = ^TMP("LR7OGX",539019167,"OUTPUT",127) = Jan 11, 1999@14:37 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",128) = 3414 ^TMP("LR7OGX",539019167,"OUTPUT",129) = ^TMP("LR7OGX",539019167,"OUTPUT",130) = Jan 11, 1999@14:37 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",131) = 341 ^TMP("LR7OGX",539019167,"OUTPUT",132) = ^TMP("LR7OGX",539019167,"OUTPUT",133) = Jan 11, 1999@14:37 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",134) = POT ^TMP("LR7OGX",539019167,"OUTPUT",135) = ^TMP("LR7OGX",539019167,"OUTPUT",136) = Jan 11, 1999@14:37 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",137) = 6579 ^TMP("LR7OGX",539019167,"OUTPUT",138) = ^TMP("LR7OGX",539019167,"OUTPUT",139) = Jan 11, 1999@14:36 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",140) = 125 ^TMP("LR7OGX",539019167,"OUTPUT",141) = ^TMP("LR7OGX",539019167,"OUTPUT",142) = Jan 11, 1999@14:36 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",143) = 90451 ^TMP("LR7OGX",539019167,"OUTPUT",144) = ^TMP("LR7OGX",539019167,"OUTPUT",145) = Jan 11, 1999@14:36 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",146) = RPAG ^TMP("LR7OGX",539019167,"OUTPUT",147) = ^TMP("LR7OGX",539019167,"OUTPUT",148) = Jan 11, 1999@14:36 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",149) = ASDF ^TMP("LR7OGX",539019167,"OUTPUT",150) = ^TMP("LR7OGX",539019167,"OUTPUT",151) = Jan 11, 1999@14:35 ** Comments: ^TMP("LR7OGX",539019167,"OUTPUT",152) = 134234 ^TMP("LR7OGX",539019167,"OUTPUT",153) = VARIABLES: .ARRAY TYPE: Both VARIABLES DESCRIPTION: Passed by reference to receive output array location. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of PATIENT file (#2) VARIABLES: START TYPE: Input VARIABLES DESCRIPTION: Start date/time for search. VARIABLES: END TYPE: Input VARIABLES DESCRIPTION: End date/time for search. VARIABLES: SPECTYPE TYPE: Input VARIABLES DESCRIPTION: Optional: if a particular speciment type is desired, it is passed in. Otherwise all specimen types are returned. VARIABLES: TESTNUM TYPE: Input VARIABLES DESCRIPTION: IEN of LABORATORY TEST file. VARIABLES: ~TMP("LR7OG",$J, TYPE: Output VARIABLES DESCRIPTION: Array may be killed prior to CHART call as well as after. VARIABLES: ~TMP("LR7OGX",$J, TYPE: Output VARIABLES DESCRIPTION: Array may be killed prior to CHART call as well as after. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2957 IA #: 2957 DATE CREATED: NOV 09, 1999 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCTU NAME: DBIA2957 ID: GMRCTU GENERAL DESCRIPTION: This agreement allows the OE/RR package to call CLNLIST^GMRCTU in order to remove pointers in the CONSULTS package for terminated users. The calling routine is ORLPTU, which is triggered by a Kernel event when a user is terminated. VIEWER: RUTHERFORD,JERALD F STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30440964 KEYWORDS: TERMINATION KEYWORDS: TERMINATED USER KEYWORDS: TERMINATED USERS COMPONENT/ENTRY POINT: CLNLIST COMPONENT DESCRIPTION: The CLNLIST tag utilizes code to remove pointers for terminated users in the file 123.5. The pointers are to file 100.21, the Team List file. VARIABLES: ORLTEAM TYPE: Input VARIABLES DESCRIPTION: Inasmuch as the pointers being removed relate to Team List entries which might exist in file 123.5, the variable ORLTEAM specifies the IEN of the team to be processed. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2958 IA #: 2958 DATE CREATED: NOV 09, 1999 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LR7OGM NAME: Calls to LR7OGM ID: LR7OGM GENERAL DESCRIPTION: This DBIA documents calls to routine LR7OGM. ^TMP("LR7OG",$J) and ^TMP("LR7OGX",$J) may be killed before and after any component call. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946458 COMPONENT/ENTRY POINT: INTERIM(.ROOT,DFN,END,START) COMPONENT DESCRIPTION: Returns data for interim report to be displayed in CPRS GUI. The following shows the output beginning with teh line counter and closing paren. The root is TMP("LR7OGX",$J,"OUTPUT",COUNTER): (NOTE: global root was left off display to have it display appropriately) ---- MICROBIOLOGY ---- Accession: MICRO 99 6 Received: Oct 28, 1999 13:03 Collection sample: SPUTUM Collection date: Oct 28, 1999 13:03 Provider: ANDERSON,CURTIS Test(s) ordered: GRAM STAIN CULTURE & SUSCEPTIBILITY AFB SMEAR ========================================================================== Provider : ANDERSON,CURTIS Specimen: SERUM. CH 1026 1 10/26/1999 15:09 Test name Result units Ref. range GLUCOSE 500 H* mg/dL 60 - 123 PROTEIN,TOTAL 110 H g/dL 6.2 - 7.7 ========================================================================== VARIABLES: ROOT TYPE: Output VARIABLES DESCRIPTION: Global root in which data is returned. This variable will be set to ^TMP("LR7OGX",$J,"OUTPUT") VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal entry number of the PATIENT file VARIABLES: START TYPE: Input VARIABLES DESCRIPTION: Start date range VARIABLES: END TYPE: Input VARIABLES DESCRIPTION: Ending date range COMPONENT/ENTRY POINT: INTERIMG(.ROOT,DFN,END,DIRECTION,FORMAT) COMPONENT DESCRIPTION: Returns interim report for CPRS GUI display. Allows more paratemeters for the direction (forward/reverse) of the date range and the format of the report. Ouptut is in TMP("LR7OGX",$J,"OUTPUT") as described in INTERIM call within this DBIA. VARIABLES: ROOT TYPE: Output VARIABLES DESCRIPTION: Root of output data (set to ^TMP("LR7OGX",$J,"OUTPUT")) VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of the PATIENT file (#2) COMPONENT/ENTRY POINT: END COMPONENT DESCRIPTION: End date for search VARIABLES: DIRECTION TYPE: Input VARIABLES DESCRIPTION: Direction for search (1 goes forward, -1 goes in reverse) VARIABLES: FORMAT TYPE: Input VARIABLES DESCRIPTION: OPTIONAL (default=1) 1 - standard format (as INTERIM returns) 2 - returns micro labs 3 - returns chemistry labs only COMPONENT/ENTRY POINT: INTERIMS(.ROOT,DFN,END,START,.TESTS) COMPONENT DESCRIPTION: Returns interim report for CPRS GUI display. Allows for results from specific tests to be returned. Ouptut is in TMP("LR7OGX",$J,"OUTPUT") as described in INTERIM call within this DBIA. VARIABLES: ROOT TYPE: Output VARIABLES DESCRIPTION: Root of output data (set to ^TMP("LR7OGX",$J,"OUTPUT")) VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of PATIENT file (#2) VARIABLES: START TYPE: Input VARIABLES DESCRIPTION: Start date for search VARIABLES: END TYPE: Input VARIABLES DESCRIPTION: End date for search VARIABLES: TESTS TYPE: Input VARIABLES DESCRIPTION: Array of tests for which results should be returned. Format of input should be TESTS(number)=IEN of file 60 (LABORATORY TEST file) COMPONENT/ENTRY POINT: MICRO(.ROOT,DFN,END,START) COMPONENT DESCRIPTION: Returns micros results in interim report format for CPRS GUI display. Ouptut is in TMP("LR7OGX",$J,"OUTPUT") as described in INTERIM call within this DBIA. VARIABLES: ROOT TYPE: Output VARIABLES DESCRIPTION: Root of output data (set to ^TMP("LR7OGX",$J,"OUTPUT")) VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of PATIENT file (#2) VARIABLES: END TYPE: Input VARIABLES DESCRIPTION: end date for search VARIABLES: START TYPE: Input VARIABLES DESCRIPTION: Start date for search SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: MYHEALTHEVET SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 3/11/15-MC: Added VPS as a subscriber at the request of Carolyn Wheless for patch VPS*1*15. Custodial approval received from Levi Teitelbaum. DATE/TIME EDITED: MAR 11, 2015@07:56 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: TEITELBAUM,LEVI NUMBER: 2959 IA #: 2959 DATE CREATED: NOV 09, 1999 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LR7OGMU NAME: Calls to LR7OGMU ID: LR7OGMU GENERAL DESCRIPTION: This DBIA documents calls to routine LR7OGMU. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946458 COMPONENT/ENTRY POINT: NEWOLD(.VALUE,DFN) COMPONENT DESCRIPTION: Returns most recent and oldest lab tests for a patient (date only) VARIABLES: VALUE TYPE: Output VARIABLES DESCRIPTION: Newest Date^Oldest Date Dates are in internal FM format. Example of output: 2991028.130321^2920428.1044 VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of PATIENT file (#2) SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2960 IA #: 2960 DATE CREATED: NOV 09, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIULX NAME: Calls to TIULX ID: TIULX GENERAL DESCRIPTION: This DBIA documents calls made to routine TIULX STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30387939 COMPONENT/ENTRY POINT: $$HASDS(DFN,VISIT) COMPONENT DESCRIPTION: Returns a string based on whether a discharge summary exists for the given PATIENT and VISIT file pointers. If no summary found, output is 0^0 If summary is found, output is: IEN of TIU DOCUMENT file (#8925)^context 'context; is based on the TIU STATUS file (#8925.6) pointer from the TIU DOCUMENT file. If no valid status is found, a 0 is returned, if the status is UNSIGNED, the context is set to 2, for all other valid discharge summary statuses, the value returned is 1. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of the PATIENT file (#2) VARIABLES: VISIT TYPE: Input VARIABLES DESCRIPTION: IEN of the VISIT file (#9000010). COMPONENT/ENTRY POINT: NEEDSIG(.TIUY,USER,CLASS) COMPONENT DESCRIPTION: This component allows the gathering of a list of TIU documents for which USER is an additional signer VARIABLES: TIUY TYPE: Both VARIABLES DESCRIPTION: This variable is passed by reference and it is returned with a reference to a global array that contains the list of TIU documents for which the user has been identified as an additional signer. VARIABLES: USER TYPE: Input VARIABLES DESCRIPTION: Pointer to the NEW PERSON (#200) file. VARIABLES: CLASS TYPE: Input VARIABLES DESCRIPTION: Pointer to TIU DOCUMENT DEFINITION (#8925.1) file. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CARE MANAGEMENT NUMBER: 2961 IA #: 2961 FILE NUMBER: 142 GLOBAL ROOT: GMT(142, DATE CREATED: NOV 09, 1999 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: OE/RR use of HEALTH SUMMARY TYPE file ID: GMT(142, GLOBAL REFERENCE: GMT(142,'B' GLOBAL DESCRIPTION: 'B' index is used to get list of health summary types for look-up in CPRS GUI. GLOBAL REFERENCE: GMT(142,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: STRUCTURE LOCATION: GMT(142,DA,1,0) ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Checks for entry in this multiple. Prevents selection if there are no components included in the summary type. Uses data on the node to assist with presentation to the CPRS GUI user. The following fields are in the STRUCTURE multiple: .01 SUMMARY ORDER 1 COMPONENT NAME 2 OCCURRENCE LIMIT 3 TIME LIMIT 4 HEADER NAME 5 HOSPITAL LOCATION DISPLAYED 6 ICD TEXT DISPLAYED 8 PROVIDER NARRATIVE DISPLAYED. FIELD NUMBER: 4 FIELD NAME: SELECTION ITEM ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Unable to enter submultiples apporpriately, but CPRS uses the SELECTION ITEM multiple to get multiple of SELECTION ITEMS. GLOBAL REFERENCE: GMT(142,DA,'T') FIELD NUMBER: .02 FIELD NAME: TITLE LOCATION: T;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This DBIA documents CPRS's use of the Health Summary Type file (#142). This file is used to allow displaying of health summaries via the CPRS interface. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30443977 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2962 IA #: 2962 DATE CREATED: NOV 10, 1999 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMPLHIST NAME: Calls to GMPLHIST ID: GMPLHIST GENERAL DESCRIPTION: This DBIA documents calls made to rotuine GMPLHIST. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28891053 COMPONENT/ENTRY POINT: DT COMPONENT DESCRIPTION: Shows auditing trail so detailed displays can show historical ihformation. VARIABLES: AIFN TYPE: Input VARIABLES DESCRIPTION: IEN of PROBLEM LIST AUDIT TRAIL file (#125.8). VARIABLES: LCNT TYPE: Input VARIABLES DESCRIPTION: Line count after which you want audit information to appear. VARIABLES: GMPDT(LCNT,0) TYPE: Output VARIABLES DESCRIPTION: Array of autidt information returned beginning with LCNT+1. INTEGRATION REFERENCES LIST MAR 18,2015 11:24 PAGE 9 -------------------------------------------------------------------------------- GMPDT(LCNT,0)=Audit information SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City EDITOR: ROWE,KIMBALL NUMBER: 2963 IA #: 2963 FILE NUMBER: 3.5 GLOBAL ROOT: %ZIS(1, DATE CREATED: NOV 10, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Direct access to %ZIS(1 ID: %ZIS(1, GLOBAL REFERENCE: %ZIS(1,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5.5 FIELD NAME: QUEUING LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: %ZIS(1,DA,1) FIELD NUMBER: .02 FIELD NAME: LOCATION OF TERMINAL LOCATION: 1;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: %ZIS(1,DA,90) FIELD NUMBER: 6 FIELD NAME: OUT-OF-SERVICE DATE LOCATION: 90;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: %ZIS(1,DA,91) FIELD NUMBER: 9 FIELD NAME: MARGIN WIDTH LOCATION: 91;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 11 FIELD NAME: PAGE LENGTH LOCATION: 91;3 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: %ZIS(1,DA,95) FIELD NUMBER: 15 FIELD NAME: SECURITY LOCATION: 95;E1,99 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: %ZIS(1,DA,'TIME') FIELD NUMBER: 2009 FIELD NAME: PROHIBITED TIMES FOR SIGN-ON LOCATION: TIME;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: %ZIS(1,DA,'TYPE') FIELD NUMBER: 2 FIELD NAME: TYPE LOCATION: TYPE;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This DBIA documents direct access to fields in the DEVICE file (#3.5). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30447311 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: CPRS GUI utilizes device parameters to handle printing from within the GUI environment. NUMBER: 2964 IA #: 2964 FILE NUMBER: 3.2 GLOBAL ROOT: %ZIS(2, DATE CREATED: NOV 10, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Direct access to %ZIS(2 ID: %ZIS(2, GLOBAL REFERENCE: %ZIS(2,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: %ZIS(2,DA,5) FIELD NUMBER: 14 FIELD NAME: REVERSE VIDEO ON LOCATION: 5;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 15 FIELD NAME: REVERSE VIDEO OFF LOCATION: 5;5 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: %ZIS(2,DA,7) FIELD NUMBER: 27 FIELD NAME: HIGH INTENSITY (BOLD) LOCATION: 7;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 28 FIELD NAME: LOW INTENSITY (UNBOLD) LOCATION: 7;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 29 FIELD NAME: NORMAL INTENSITY (RESET) LOCATION: 7;3 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This DBIA documents direct access to the TERMINAL TYPE file (#3.2). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30447311 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2965 IA #: 2965 FILE NUMBER: 405.1 GLOBAL ROOT: DG(405.1, DATE CREATED: NOV 10, 1999 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Direct access to file 405.2 ID: DG(405.1, GLOBAL REFERENCE: DG(405.1,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This DBIA documents references to the FACILITY MOVEMENT TYPE file (#405.1). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30388173 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS DBA Comments: 12/31/14-MM: On 12/24/14, Phil Burkhalter stated in an email that MBAA PATIENT ADMISSIONS RPC is not included in this release of SCV or VAR2. Scheduling Calendar View will not need to subscribe to ICRs 419, 565, 2965, 1380. We can withdraw these requests. NUMBER: 2966 IA #: 2966 FILE NUMBER: 391 GLOBAL ROOT: DG(391, DATE CREATED: NOV 10, 1999 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Use of TYPE OF PATIENT file ID: DG(391, GLOBAL REFERENCE: DG(391,DA,0) FIELD NUMBER: .02 FIELD NAME: IGNORE VETERAN CHECKS? LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This DBIA documents access to the TYPE OF PATIENT file (#391) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30388173 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: This reference is needed to mimic code found in DIS^DGRPDB which displays rated disabilities. The code in DIS^DGRPD is not silent and can't be used by CPRS GUI. CPRS uses only the field IGNORE VETERAN CHECKS? (#.02) NUMBER: 2967 IA #: 2967 FILE NUMBER: 31 GLOBAL ROOT: DIC(31, DATE CREATED: NOV 10, 1999 CUSTODIAL PACKAGE: HINQ CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: References to DISABILITY CONDITION file ID: DIC(31, GLOBAL REFERENCE: DIC(31,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This DBIA documents references to the DISABILITY CONDITION file (#31). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30388173 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: This reference is needed to mimic code found in DIS^DGRPDB which displays rated disabilities. The code in DIS^DGRPD is not silent and can't be used by CPRS GUI. CPRS uses only the field NAME (#.01). SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING SUBSCRIBING DETAILS: ADDED 5/25/10 DATE/TIME EDITED: JUN 02, 2010@14:16 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: THOMPSON,WILLIAM WITH CONCURRENCE OF: MORGAN,BRIAN NUMBER: 2968 IA #: 2968 FILE NUMBER: 34 GLOBAL ROOT: DIC(34, DATE CREATED: NOV 10, 1999 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Direct access to file 34 ID: DIC(34, GLOBAL REFERENCE: DIC(34,DA,0) FIELD NUMBER: .01 FIELD NAME: AGREEMENT NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: TYPE OF AGREEMENT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DIC(34,DA,'I') FIELD NUMBER: 3 FIELD NAME: INACTIVATION DATE LOCATION: I;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This DBIA documents references to the CONTRACT/SHARING AGREEMENTS file (#34). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33935350 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2969 IA #: 2969 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: NOV 10, 1999 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2969 ID: DPT( CREATOR: SCOTT,APRIL L GLOBAL REFERENCE: DPT(D0 FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Write w/Fileman FIELD DESCRIPTION: Patient Name FIELD NUMBER: .03 FIELD NAME: DATE OF BIRTH LOCATION: 0;3 ACCESS: Write w/Fileman FIELD DESCRIPTION: Patient Date of Birth FIELD NUMBER: .09 FIELD NAME: SOCIAL SECURITY NUMBER LOCATION: 0;9 ACCESS: Write w/Fileman FIELD DESCRIPTION: Patient Social Security Number FIELD NUMBER: .351 FIELD NAME: DATE OF DEATH LOCATION: .35;1 ACCESS: Write w/Fileman FIELD DESCRIPTION: Patient Date of Death FIELD NUMBER: .353 FIELD NAME: SOURCE OF NOTIFICATION LOCATION: .35;3 ACCESS: Write w/Fileman FIELD DESCRIPTION: Patient Source of Notification GENERAL DESCRIPTION: To support CIRN Exception Handling, CIRN PD needs to allow user editing of patient name, date of birth, social security number and date of death fields. All appropriate security checking is done. STATUS: Active MAIL MESSAGE: 30448976 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK DATE/TIME EDITED: AUG 30, 2008@08:00 ACTION: CONTENT CORRECTED AT THE REQUEST OF: DAVIS,PAULETTE WITH CONCURRENCE OF: MULLER,RICHARD NUMBER: 2970 IA #: 2970 FILE NUMBER: 125.99 GLOBAL ROOT: GMPL(125.99, DATE CREATED: NOV 10, 1999 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Access to Problem List Parameters ID: GMPL(125.99, GLOBAL REFERENCE: GMPL(125.99,DA,0) FIELD NUMBER: 1 FIELD NAME: VERIFY TRANSCRIBED PROBLEMS LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: PROMPT FOR CHART COPY LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: USE LEXICON LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: DISPLAY ORDER LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This DBIA documents access to the PROBLEM LIST SITE PARAMETER file (#125.99). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28891053 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2971 IA #: 2971 FILE NUMBER: 125 GLOBAL ROOT: GMPL(125, DATE CREATED: JUL 21, 2003 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Access to PROBLEM SELECTION LIST file ID: GMPL(125, GLOBAL REFERENCE: GMPL(125,'C', GENERAL DESCRIPTION: This DBIA documents access made to the PROBLEM SELECTION LIST file (#125). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 35801181 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2972 IA #: 2972 FILE NUMBER: 125.1 GLOBAL ROOT: GMPL(125.1, DATE CREATED: NOV 10, 1999 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: References to file 125.1 ID: GMPL(125.1, GLOBAL REFERENCE: GMPL(125.1,DA,0) FIELD NUMBER: 2 FIELD NAME: CATEGORY LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: SUBHEADER LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: SHOW PROBLEMS LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: GMPL(125.1,'C' GENERAL DESCRIPTION: This DBIA documents references made to the PROBLEM SELECTION LIST CONTENTS file (#125.1). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28891053 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2973 IA #: 2973 FILE NUMBER: 125.12 GLOBAL ROOT: GMPL(125.12, DATE CREATED: NOV 10, 1999 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: References to file 125.12 ID: GMPL(125.12, GLOBAL REFERENCE: GMPL(125.12,DA,0) FIELD NUMBER: 2 FIELD NAME: PROBLEM LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: DISPLAY TEXT LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: CODE LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: GMPL(125.12,'C' GENERAL DESCRIPTION: This DBIA documents references to the PROBLEM SELECTION CATEGORY CONTENTS file (#125.12). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28891053 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2974 IA #: 2974 FILE NUMBER: 125.8 GLOBAL ROOT: GMPL(125.8, DATE CREATED: NOV 10, 1999 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Access to PROBLEM LIST AUDIT file ID: GMPL(125.8, GLOBAL REFERENCE: GMPL(125.8,'B' GLOBAL REFERENCE: GMPL(125.8,'AD' GENERAL DESCRIPTION: This DBIA documents references to the PROBLEM LIST AUDIT file (#125.8). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28891053 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2975 IA #: 2975 FILE NUMBER: 123.1 GLOBAL ROOT: GMR(123.1, DATE CREATED: NOV 10, 1999 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Use of REQUEST ACTION TYPES file ID: GMR(123.1, GLOBAL REFERENCE: GMR(123.1,'AC' FIELD NUMBER: .01 FIELD NAME: ACTION TYPE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: This DBIA documents references to the REQUEST ACTION TYPES file (#123.1). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: SCHEDULING NUMBER: 2976 IA #: 2976 FILE NUMBER: 120.84 GLOBAL ROOT: GMRD(120.84, DATE CREATED: NOV 10, 1999 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Access to Allergy Parameters File ID: GMRD(120.84, GLOBAL REFERENCE: GMRD(120.84,DA(1),1,DA,0) FIELD NUMBER: .01 FIELD NAME: REACTIONS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: CPRS GUI uses the TOP 10 REACTIONS multiple (#120.841) and gets the first 10 entries (mimicking the ART module in the roll and scroll environment). GENERAL DESCRIPTION: This DBIA documents references made to the GMR ALLERGY SITE PARAMETERS file (#120.84). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 26946164 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2977 IA #: 2977 DATE CREATED: NOV 12, 1999 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMPLEDT3 NAME: Calls to GMPLEDT3 ID: GMPLEDT3 GENERAL DESCRIPTION: This DBIA documents calls made to routine GMPLEDT3. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34251612 COMPONENT/ENTRY POINT: GETFLDS(DA) COMPONENT DESCRIPTION: Returns arrays of values stored in PROBLEM file (#9000011). VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: Internal entry number of the PROBLEM file (#9000011). VARIABLES: AUPROV TYPE: Input VARIABLES DESCRIPTION: Pointer to the NEW PERSON file defining the provider for which comments can be returned. VARIABLES: AUPVAMC TYPE: Input VARIABLES DESCRIPTION: Pointer to the LOCATION file (#9999999.06) which is a DINUMed file to the INSTITUTION. This defines the division for which comments should be returned. VARIABLES: GMPFLD TYPE: Output VARIABLES DESCRIPTION: Array, subscripted by field number, containing the internal^external value of data stored for the PROBLEM entry requested. Comments are stored in GMPORIG(10,n) where GMPORIG(10,0) is set to the number of comments and GMPORIG(10,1-n) are the comments returned. Example output: GMPFLD(.01)=9041^413.0 GMPFLD(.03)=2991006^10/6/99 GMPFLD(.05)=305^Angina Decubitus GMPFLD(.08)=2991006^10/6/99 GMPFLD(.12)=A^ACTIVE GMPFLD(.13)= GMPFLD(1.01)= GMPFLD(1.02)=P GMPFLD(1.05)=1364^MERRILL,JEREMY GMPFLD(1.06)=1^MEDICINE GMPFLD(1.07)= GMPFLD(1.08)=16^PULMONARY CLINIC GMPFLD(1.09)= GMPFLD(1.1)= GMPFLD(1.11)= GMPFLD(1.12)= GMPFLD(1.13)= GMPFLD(1.14)= GMPFLD(1.15)= GMPFLD(1.16)= GMPFLD(10,0)=1 GMPFLD(10,1)=1^1^Angina^A^2991006^1364 VARIABLES: GMPORIG TYPE: Output VARIABLES DESCRIPTION: Array returned exactly as the GMPFLD array is returned. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES NUMBER: 2978 IA #: 2978 DATE CREATED: NOV 12, 1999 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMPLSAVE NAME: Calls to GMPLSAVE ID: GMPLSAVE GENERAL DESCRIPTION: This DBIA documents calls made to routine GMPLSAVE. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28891053 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: Saves changes made to PROBLEM file (#9000011) and tracks changes in the PROBLEM LIST AUDIT file (#125.8). VARIABLES: GMPORIG TYPE: Input VARIABLES DESCRIPTION: Array, subscripted by field number, giving values in internal^external format. The array defines how the entry in the PROBLEM file was previous to edit. VARIABLES: GMPFLD TYPE: Input VARIABLES DESCRIPTION: Array, subscripted by field number, giving values in internal^external format. The array defines how the entry in the PROBLEM file was after editing. COMPONENT/ENTRY POINT: NEW COMPONENT DESCRIPTION: Adds a new PROBLEM file (#9000011) entry. VARIABLES: GMPFLD TYPE: Input VARIABLES DESCRIPTION: Array, subscripted by field number, giving values in internal^external format. The array defines how the entry in the PROBLEM file should be stored. VARIABLES: GMPVAMC TYPE: Input VARIABLES DESCRIPTION: Pointer to the LOCATION file (#9999999.06) which is a DINUMed file to the INSTITUTION. This defines the division for which comments should be associated. VARIABLES: GMPDFN TYPE: Input VARIABLES DESCRIPTION: Internal entry number of the PATIENT file (#2). VARIABLES: DA TYPE: Output VARIABLES DESCRIPTION: Internal entry number assigned to the PROBLEM file entry. VARIABLES: GMPSAVED TYPE: Output VARIABLES DESCRIPTION: Set to 1 if the entry was successfully saved. COMPONENT/ENTRY POINT: NEWNOTE COMPONENT DESCRIPTION: Creates a new note for an existing PROBLEM file (#9000011) entry. VARIABLES: GMPIFN TYPE: Input VARIABLES DESCRIPTION: IEN of PROBLEM file VARIABLES: GMPROV TYPE: Input VARIABLES DESCRIPTION: Pointer to NEW PERSON file denoting provider associated with the comment. VARIABLES: GMPVAMC TYPE: Input VARIABLES DESCRIPTION: Pointer to the LOCATION file (#9999999.06) which is a DINUMed file to the INSTITUTION. This defines the division for which comments should be associated.. VARIABLES: GMPFLD TYPE: Input VARIABLES DESCRIPTION: Array GMPFLD(10,"NEW",n) which contains comments to add to the file. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City EDITOR: ROWE,KIMBALL NUMBER: 2979 IA #: 2979 DATE CREATED: NOV 12, 1999 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMPLMGR1 NAME: Calls to GMPLMGR1 ID: GMPLMGR1 GENERAL DESCRIPTION: This DBIA documents calls to GMPLMGR1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28891053 COMPONENT/ENTRY POINT: GETPLIST(.LIST,.TOTAL,.VIEW) COMPONENT DESCRIPTION: Build list of entry numbers from the PROBLEM file meeting requested criteria. VARIABLES: LIST TYPE: Output VARIABLES DESCRIPTION: Output array where LIST(counter)=IEN and LIST("B",IEN)=counter. VARIABLES: TOTAL TYPE: Output VARIABLES DESCRIPTION: Total number of problems returned. VARIABLES: VIEW TYPE: Input VARIABLES DESCRIPTION: VIEW is an array of input parameters determining which PROBLEM file entries are returned: VIEW("ACT") = "A" for active problems only "I" for inactive problems only Anything else for both active and inactive problems VIEW("PROV") = Pointer to the new person file for the provider to be associated with the returned list of PROBLEMs. Null to get all provider's entries. VIEW("VIEW") = X\n\n\n\... where X is C for Clinic or S for Service and n denotes the related file IENs. Less than 2 characters returns all clinic or service entries. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2980 IA #: 2980 DATE CREATED: NOV 12, 1999 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCGUIB NAME: Calls to GMRCGUIB ID: GMRCGUIB GENERAL DESCRIPTION: This DBIA documents calls made to routine GMRCGUIB. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 COMPONENT/ENTRY POINT: CMT(IEN,.COMMENTS,.RECIPIENTS,DATE,WHO) COMPONENT DESCRIPTION: Entry point to add a comment to a consult record. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of the REQUEST/CONSULTATION file (#123) VARIABLES: COMMENTS TYPE: Input VARIABLES DESCRIPTION: Array of commnets in format COMMENTS(1)="xxxx",COMMENTS(2)="xxx", etc. VARIABLES: RECIPIENTS TYPE: Input VARIABLES DESCRIPTION: Array of alert recipients who should be alerted of comment addition. (optional) VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: Date/time of activity in internal FM format. VARIABLES: WHO TYPE: Input VARIABLES DESCRIPTION: IEN of the NEW PERSON who is responsible for the comment (OPTIONAL) COMPONENT/ENTRY POINT: $$SFILE(IEN,TYPE,SIGFIND,PROVIDER,WHO,.COMMENTS,FLAG,WHOG ETS,DATE) COMPONENT DESCRIPTION: This entry point was written for CPRS GUI to process various file update functions including administrative completion and significant findings. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of REQUEST/CONSULTATION file (#123). VARIABLES: TYPE TYPE: Input VARIABLES DESCRIPTION: Pointer to the REQUEST ACTION TYPES file (#123.1) (10=complete, 4=significant findings) VARIABLES: SIGFIND TYPE: Input VARIABLES DESCRIPTION: Y for significant finding N for no significant finding U for unknown significant finding VARIABLES: PROVIDER TYPE: Input VARIABLES DESCRIPTION: IEN of NEW PERSON file (#200) denoting provider responsible for the action. VARIABLES: WHO TYPE: Input VARIABLES DESCRIPTION: Pointer to the NEW PERSON file (#200) denoting person actually performing the action. VARIABLES: COMMENTS TYPE: Input VARIABLES DESCRIPTION: Array of comments describing the action in format COMMENTS(1)="xxxx", COMMENTS(2)="xxx" VARIABLES: FLAG TYPE: Input VARIABLES DESCRIPTION: Flag to signal whether alerts should be sent (Y for yes, N for no). VARIABLES: WHOGETS TYPE: Input VARIABLES DESCRIPTION: Comma-delimited string of NEW PERSON file IENs denoting who should receive an alert. VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: Date/time the activity took place. VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: Result of extrinsic function returned as Error Flag^Error Message Error Flag=1 if error, otherwise 0. Error Message is null if Error Flag is set to 0. COMPONENT/ENTRY POINT: DOCLIST(GMRCAR,GMRCDA) COMPONENT DESCRIPTION: Returns a list of TIU documents linked to the selected consult VARIABLES: GMRCAR TYPE: Both VARIABLES DESCRIPTION: Passed in as the array to return results in. The array will be returned as follows with multiple 50 nodes for every TIU document number: GMRC(0) = zero node of the record. GMRC(50,1) = "ien;TIU(8925," GMRC(50,2) = "ien;TIU(8925," VARIABLES: GMRCDA TYPE: Input VARIABLES DESCRIPTION: IEN of consult to provide array of TIU documents. COMPONENT/ENTRY POINT: SCH(IEN,WHO,DATE,RECIPIENTS,COMMENTS) COMPONENT DESCRIPTION: Entry point to move a consult record to scheduled status VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of the REQUEST/CONSULTATION file (#123) VARIABLES: WHO TYPE: Input VARIABLES DESCRIPTION: IEN of the NEW PERSON who is responsible for the comment (OPTIONAL) VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: Date/time of activity in internal FM format. VARIABLES: RECIPIENTS TYPE: Input VARIABLES DESCRIPTION: Array (passed by reference) of alert recipients who should be alerted of comment addition. (OPTIONAL) VARIABLES: COMMENTS TYPE: Input VARIABLES DESCRIPTION: Array (passed by reference) of comments (OPTIONAL) in format: COMMENTS(1)="xxxx",COMMENTS(2)="xxx", etc. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: PROSTHETICS ISC: Hines SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Hines SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM DBA Comments: 5/31/12 D. Trost added VPR as Subscriber. Original request was made 8/4/2011 by Melanie Buechler to use NHIN as subscriber. On 6/23/2011 Melanie changed the request to make VPR the subscriber, instead of NHIN. Tony Thompson approved VPR subscriber on 6/23/2011. 6/3/14-MC: Brandon DeWayne originally requested to add FBCS as a subscriber 6/20/13. Approval was received from Tony Thompson. Last email correspondence with Brandon was July 2013.Patch has been discovered to have been released on 9/11/13 as an emergency patch. Since patch has been released and approval was already received, adding FBCS to the ICR as a subscribing package. DATE/TIME EDITED: MAY 31, 2012@15:23 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: DEWAYNE,BRANDON WITH CONCURRENCE OF: THOMPSON,TONY NUMBER: 2981 IA #: 2981 DATE CREATED: NOV 12, 1999 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCP5 NAME: Calls to GMRCP5 ID: GMRCP5 GENERAL DESCRIPTION: This DBIA documents calls made to routine GMRCP5. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 COMPONENT/ENTRY POINT: GUI(.ROOT,IEN) COMPONENT DESCRIPTION: Returns SF513 report for display in GUI environment. Root will be set to ^TMP("GMRC",$J,"SF513"). VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of REQUEST/CONSULTATION file (#123) for which report should be returned. COMPONENT/ENTRY POINT: EN(IEN,COPYTYPE,DEVICE,.STATUS) COMPONENT DESCRIPTION: Entry point to send a copy of the SF513 to a printer device. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of REQUEST/CONSULTATION file (#123). VARIABLES: COPYTYPE TYPE: Input VARIABLES DESCRIPTION: C for Chart Copy W for Working Copy null for not applicable VARIABLES: DEVICE TYPE: Input VARIABLES DESCRIPTION: Device to be passed to %ZTLOAD as ZTIO. VARIABLES: STATUS TYPE: Output VARIABLES DESCRIPTION: Returned as: 0^Queued as task # n (if successful) -1^Not Queued (if unsuccessful) SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: PROSTHETICS ISC: Hines SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Hines SUBSCRIBING PACKAGE: SCHEDULING EDITOR: RUTHERFORD,JERALD F NUMBER: 2982 IA #: 2982 DATE CREATED: NOV 12, 1999 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCPR0 NAME: Calls to GMRCPR0 ID: GMRCPR0 GENERAL DESCRIPTION: This DBIA documents calls to routine GMRCPR0 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 COMPONENT/ENTRY POINT: GETSVC(.LIST,PROC) COMPONENT DESCRIPTION: Returns a list of services for a particular procedure type (GMRCR protocol entry). VARIABLES: LIST TYPE: Output VARIABLES DESCRIPTION: LIST=total returned LIST(counter)=internal^external format of REQUEST SERVICES file VARIABLES: PROC TYPE: Input VARIABLES DESCRIPTION: Pointer to the PROTOCOL file (#101) which is based on the PROCEDURE TYPE multiple of the REQUEST SERVICES file (#123.5). SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2983 IA #: 2983 DATE CREATED: NOV 15, 1999 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LR7OSOS1 NAME: LR7OSOS1 ID: LR7OSOS1 GENERAL DESCRIPTION: This routine produces a formatted patient report of Lab order status. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30463267 COMPONENT/ENTRY POINT: EN1(Y,ORVP,START,END,DTRANGE) COMPONENT DESCRIPTION: VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Where the formatted report is stored: ^TMP("ORDATA",$J,... VARIABLES: ORVP TYPE: Input VARIABLES DESCRIPTION: Variable pointer to patient. VARIABLES: START TYPE: Input VARIABLES DESCRIPTION: Starting date/time to get orders. VARIABLES: END TYPE: Input VARIABLES DESCRIPTION: Ending date/time to get orders. VARIABLES: DTRANGE TYPE: Input VARIABLES DESCRIPTION: Can be used as instead of START and END dates. This is a number of days to go back for data. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: NUMBER: 2984 IA #: 2984 DATE CREATED: NOV 15, 1999 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LR7OSBB1 NAME: LR7OSBB1 ID: LR7OSBB1 GENERAL DESCRIPTION: This routine is used to get Blood Bank patient information for disiplay in CPRS. It is a 'silent' version of the routine LRBLPD. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30463267 COMPONENT/ENTRY POINT: SET COMPONENT DESCRIPTION: Sets up environmental variables. COMPONENT/ENTRY POINT: OERR COMPONENT DESCRIPTION: Gets a patient report. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient identifyer COMPONENT/ENTRY POINT: CLEAN COMPONENT DESCRIPTION: Does clean-up SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2985 IA #: 2985 DATE CREATED: NOV 15, 1999 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LR7OSOS NAME: LR7OSOS ID: LR7OSOS GENERAL DESCRIPTION: This routine produces a lab status report for a pre-selected patient. This report is interactive. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30463267 COMPONENT/ENTRY POINT: OERR(X,ALPHA,OMEGA) COMPONENT DESCRIPTION: VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Patient identifier in variable pointer format (dfn;file) VARIABLES: ALPHA TYPE: Input VARIABLES DESCRIPTION: Starting date/time to get report VARIABLES: OMEGA TYPE: Input VARIABLES DESCRIPTION: Ending date/time to get report SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2986 IA #: 2986 DATE CREATED: NOV 15, 1999 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MCARP NAME: OE/RR calls to MCARP ID: MCARP GENERAL DESCRIPTION: This routine is used to get parameters needed to produce a report of Patient Procedures. This DBIA is only to be used for CPRS Reporting and does not include any procedures for editing the Medicine database. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30464253 COMPONENT/ENTRY POINT: MCPPROC COMPONENT DESCRIPTION: Gets parameters necessary to get Summary of Patient Procedures. This call is used in conjunction with other calls to MC routines: EN^MCARPS2 => gets patient related data, sets up ^TMP("OR",$J,"MCAR" MCPPROC^MCARP => gets additional data for report. ***^MC**** => produces report, call depends on data from EN^MCARPS2 VARIABLES: MCPRO TYPE: Input VARIABLES DESCRIPTION: Used in conjunction with the option name to determine which report is produced. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: NUMBER: 2988 IA #: 2988 DATE CREATED: NOV 19, 1999 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFCTFU NAME: IAs for VAFCTFU utilities ID: VAFCTFU GENERAL DESCRIPTION: MPI Vista is requesting a DBIA with Registration to call DELALLTF^VAFCTFU to remove all associated treating facilities for a patient who's ICN has been inactivated. DELALLTF(PAT) ;Entry point to delete all Treating Facilities for a single patient. ;INPUT PAT - The patient's ICN ;OUTPUT 0 (zero) - If no errors ; 1^error description if an error MPI/PD is requesting an IA with Registration to call FILE^VAFCTFU. This subroutine is used to file data into the TREATING FACILITY LIST (TFL - #391.91) file (via the ADT/HL7 PIVOT file) under certain conditions. FILE(PDFN,FSTRG,TICN) ;this module files the individual entry input: PDFN - patient dfn FSTRG- string, three pieces delimited by an '^' 1st piece: treating facility 2nd piece: last treatment date for the patient 3rd piece: Event Reason (ADT/HL7 EVENT REASON #391.72) file TICN - boolean flag, do not update the TFL file (via the PIVOT file) if TICN equals one. MPI/PD needs to expand this DBIA to include a call to DELETE^VAFCTFU. This call is necessary to address the issue of duplicate treating facilities assigned to a patient, therefore the variable being passed is the internal entry number in TREATING FACILITY LIST FILE (#391.91) not the IEN for a site that the other calls are using. DELETE(TFIEN) ;the actual deletion code ; K DIK,DA S DIK="^DGCN(391.91," S DA=TFIEN D ^DIK K DIK,DA Q STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30466266 KEYWORDS: FILE KEYWORDS: DELALLTF KEYWORDS: DELETE COMPONENT/ENTRY POINT: DELALLTF COMPONENT DESCRIPTION: $$DELALLTF(PAT) ;Entry point to delete all Treating Facilities for a single patient. ;INPUT PAT - The patient's ICN ;OUTPUT 0 (zero) - If no errors ; 1^error description if an error VARIABLES: PAT TYPE: Input VARIABLES DESCRIPTION: PAT = ICN for the given patient VARIABLES: RETURNS TYPE: Output VARIABLES DESCRIPTION: This function returns either: 0 (zero) - If no errors 1^error description if an error COMPONENT/ENTRY POINT: FILE COMPONENT DESCRIPTION: This subroutine is used to file data into the TREATING FACILITY LIST (TFL - #391.91) file (via the ADT/HL7 PIVOT file) under certain conditions. VARIABLES: PDFN TYPE: Input VARIABLES DESCRIPTION: The internal entry number of the patient in the PATIENT (#2) file. VARIABLES: FSTRG TYPE: Input VARIABLES DESCRIPTION: This variable is three piece string delimited by an '^' 1st piece: treating facility 2nd piece: last treatment date for the patient 3rd piece: Event Reason (ADT/HL7 EVENT REASON #391.72) file VARIABLES: TICN TYPE: Input VARIABLES DESCRIPTION: This variable acts as a boolean flag. Do not update the TFL file (via the PIVOT file) if TICN equals one. COMPONENT/ENTRY POINT: $$DELETETF(PAT,INST) COMPONENT DESCRIPTION: If the legacy site is on the treating facility list for a patient that it should be deleted. VARIABLES: PAT TYPE: Input VARIABLES DESCRIPTION: ICN of the patient VARIABLES: INST TYPE: Input VARIABLES DESCRIPTION: IEN of the institution to be deleted VARIABLES: $$DELETETF TYPE: Output VARIABLES DESCRIPTION: 0 (zero) - If no errors 1^error description if there was a problem COMPONENT/ENTRY POINT: DELETE(TFIEN) COMPONENT DESCRIPTION: Used to delete specific entries in the TREATING FACILITY LIST FILE (#391.91) when identification of the site is not enough. VARIABLES: TFIEN TYPE: Input VARIABLES DESCRIPTION: Internal entry number of a specific record in the TREATING FACILITY LIST FILE (#391.91). SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA ISC: Oakland SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: CORBA SERVICES NUMBER: 2990 IA #: 2990 DATE CREATED: NOV 23, 1999 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFCTFU1 NAME: Treating Facility List ID: VAFCTFU1 GENERAL DESCRIPTION: As part of the initative to share clinical information among VA facilities, a VA facility will have information about patients that were seen at other locations for health care. This routine will return (given an Integration Control Number or a DFN) a list of facilities the patient was seen for care. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30497048 KEYWORDS: VAFCTFU1 COMPONENT/ENTRY POINT: $$QUERYTF(ICN,.ARRAY,INDX) VARIABLES: ICN TYPE: Input VARIABLES DESCRIPTION: Patient Integration Control Number. VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: This variable is an array variable that the function uses to store the results of the treating facility list. It will be in the structure of x(1), x(2), etc. E.g., X(1)=500^2960101 Where the first peice is the IEN of the institution and the second piece is the current date on record for that institution. VARIABLES: INDX TYPE: Input VARIABLES DESCRIPTION: The cross-reference to $O through. 'APAT' for patient information linked to treating facilities, 'AEVN' for patient info linked with an event reason. INDX will equal one if 'AEVN' is used, else 'APAT' is used. VARIABLES: $$QUERYTF TYPE: Output VARIABLES DESCRIPTION: 0 - If no error 1^error description - If error or no data in the array COMPONENT/ENTRY POINT: TFL(.LIST,DFN) VARIABLES: LIST TYPE: Both VARIABLES DESCRIPTION: LIST(1)=-1^error message Example error messages: parameter missing, no treating facility, missing DFN, missing ICN, etc. The only time LIST(1) will always be defined is if there is an error; the first piece will be a -1. OR an array of treating facilities; they may or may not be VAMCs: LIST(1)=500^ALBANY^3020513.092^3^VAMC LIST(2)=662^SAN FRANCISCO^3020311.14^3^VAMC LIST(3)=200^AUSTIN^^^DPC OR an array of treating facilities; may or may not be sequential: LIST(2)=500^ALBANY^3020513.092^3^VAMC LIST(3)=662^SAN FRANCISCO^3020311.14^3^VAMC VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN - required second input parameter equals the IEN in the PATIENT (#2) file. NUMBER: 2991 IA #: 2991 GLOBAL ROOT: DD( DATE CREATED: NOV 23, 1999 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA2991 ID: DD( GLOBAL REFERENCE: DD(file#,field#,'V',0 GLOBAL REFERENCE: DD(file#,field#,'V',IND,0) GENERAL DESCRIPTION: Variable pointer information is sometimes required. This information can be found in ^DD(file#,field#.,"V"). This DBIA provides for read-only access of the nodes ^DD(file#,field#,"V",. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30497573 KEYWORDS: VARIABLE POINTER KEYWORDS: V NODES SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 2992 IA #: 2992 FILE NUMBER: 8989.51 GLOBAL ROOT: XTV(8989.51, DATE CREATED: NOV 23, 1999 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PARAMETER DEFINITIONS ID: XTV(8989.51, GENERAL DESCRIPTION: Parameter Tools is a generic method of handling parameter definition, assignment, and retrieval. A parameter may be defined for various entities where an entity is the level at which you want to allow the parameter defined (e.g. package level, system level, division level, location level, user level, etc.). A developer may then determine in which order the values assigned to given entities are interpreted. Parameter: ========== A parameter is the actual name which values are stored under. The name of the parameter must be namespaced and it must be unique. Parameters can be defined to store the typical package parameter data (e.g. the default add order screen in OE/RR), but they can also be used to store GUI application screen settings a user has selected (e.g. font or window width). When a parameter is defined, the entities that may set the parameter is also defined. The definition of parameters is stored in the PARAMETER DEFINITION file (#8989.51). KIDS exports them. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30499682 NUMBER: 2993 IA #: 2993 DATE CREATED: NOV 24, 1999 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGRUDD01 NAME: DBIA2993 ID: DGRUDD01 CREATOR: LEYVA,KATHRYN GENERAL DESCRIPTION: RAI/MDS has requested Integrated Billing add cross references to 5 Insurance Type (#2.312) fields to monitor changes to the patient's insurance data. Execution of the cross reference will result in an entry in the ADT/HL7 PIVOT file (#391.71) and mark it as requiring transmission of an HL7 demographic A08 update message to the COTS interface. The local variable DGRUGA08 will be set to 1 if the cross reference is not to be executed as part of a re-indexing. Update: IB*2*497 increased the length of the SUBSCRIBER ID field to support the EDI New Standards and Operating Rules for VHA providers. This required length increase made it necessary to move the location of this field to a new Data Dictionary node in the INSURANCE TYPE sub-file. To support this implementation, all subscribers to this ICR will need to make the necessary changes in their applications. The ADGRU cross- reference cannot be implemented at the new field (2.312, 7.02) until the old field (2.312, 1) has been deleted. Therefore rather than IB*2*497, IB*2*518 will need to implement the ADGRU cross-reference at the new field and delete ADGRU cross-reference at the old field. The old and new field are noted in the field list detail of this ICR. Fields cross-referenced in the Patient File Insurance Type multiple: 2.312, .01 Insurance Type (x-ref #1) 2.312, .18 Group Plan (x-ref #1) 2.312, 1 *Subscriber ID (x-ref #1) Note: IB*2*497 - replaced by SUBSCRIBER ID field (7.02) 2.312, 7.02 Subscriber ID (x-ref to be determined by IB*2*518) 2.312, 3 Insurance Expiration Date (x-ref #1) 2.312, 8 Effective Date of Policy (x-ref #1) The following cross reference is added to all 5 fields: CROSS-REFERENCE: ADGRUxx TYPE: MUMPS SET: D:($T(ADGRU^DGRUDD01)'="") ADGRU^DGRUDD01(DA(1)) KILL: D:($T(ADGRU^DGRUDD01)'="") ADGRU^DGRUDD01(DA(1)) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30502659 COMPONENT/ENTRY POINT: ADGRU(DFN) COMPONENT DESCRIPTION: Call to monitor data field changes required by RAI/MDS. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IFN of patient's record in the Patient file (DFN). SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany DBA Comments: 2/21/14-DT: Approved. Note:IB*2*497 set up the infrastructure to allow subscribing packages to begin coding against. The future IB*2.0*518 will be distributed at the same time as subscribing packages which will use the longer length fields and delete the shorter fields. 11/18/13-MC: DEACTIVATED FOR EDITING BY IB*2*497 PROJECT TEAM. DATE ACTIVATED: FEB 21, 2014 DATE/TIME EDITED: FEB 21, 2014@18:00 ACTION: APPROVED AT THE REQUEST OF: JUTZI,BILL WITH CONCURRENCE OF: PFEIL,CATHERINE NUMBER: 2994 IA #: 2994 DATE CREATED: NOV 26, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUU NAME: Calls to TIUU ID: TIUU GENERAL DESCRIPTION: This DBIA documents calls made to routine TIUU. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30387939 COMPONENT/ENTRY POINT: $$READ(TYPE,PROMPT,DEFAULT,HELP,SCREEN) COMPONENT DESCRIPTION: Generic call to FM Reader. VARIABLES: TYPE TYPE: Input VARIABLES DESCRIPTION: Type of reader call with qualifiers (as you would set DIR(0) for a ^DIR call). VARIABLES: PROMPT TYPE: Input VARIABLES DESCRIPTION: The text of the prompt to be presented to the user. VARIABLES: DEFAULT TYPE: Input VARIABLES DESCRIPTION: (OPTIONAL) Default if one should be presented to the user. VARIABLES: HELP TYPE: Input VARIABLES DESCRIPTION: (OPTIONAL) Help text for prompt. VARIABLES: SCREEN TYPE: Input VARIABLES DESCRIPTION: (OPTIONAL) Screen for DIR call. VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: RESULT=$$READ^TIUU(...) Returns "" for failed look-ups, internal^external value for one character returned values or just external otherwise. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: AUTHORIZATION/SUBSCRIPTION NUMBER: 2995 IA #: 2995 DATE CREATED: NOV 26, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIURS NAME: Calls to TIURS ID: TIURS GENERAL DESCRIPTION: This DBIA documents calls to routine TIURS. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30387939 COMPONENT/ENTRY POINT: $$ASKCSNR(DA,SIGNER) COMPONENT DESCRIPTION: Prompts for a cosigner for the document. VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT file (#8925). VARIABLES: SIGNER TYPE: Input VARIABLES DESCRIPTION: DUZ of person using system. It will look at the person's personal preferences to determine the co-signer to default. COMPONENT/ENTRY POINT: ES(DA,DUZ) COMPONENT DESCRIPTION: Calls to get electronic signature for document. VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT file (#8925). VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: DUZ of person who will enter the electronic signature. COMPONENT/ENTRY POINT: EDSIG(TIUDA,NULL,ASKPRINT) COMPONENT DESCRIPTION: Call from edit action to sign document. VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT file (#8925). VARIABLES: NULL TYPE: Input VARIABLES DESCRIPTION: (OPTIONAL) Pass as null...appears to have no affect on call (variable internally always set to 1). VARIABLES: ASKPRINT TYPE: Input VARIABLES DESCRIPTION: (OPTIONAL) Pass as positive value if user should be prompted to print the note based on parameter settings. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2996 IA #: 2996 DATE CREATED: NOV 26, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIURC NAME: Calls to TIURC ID: TIURC GENERAL DESCRIPTION: This DBIA documents calls to routine TIURC. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30387939 COMPONENT/ENTRY POINT: COPY1 COMPONENT DESCRIPTION: Copies a document. VARIABLES: TIUDA TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT file (#8925). SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2997 IA #: 2997 DATE CREATED: NOV 26, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIURB NAME: Calls to TIURB ID: TIURB GENERAL DESCRIPTION: This DBIA documents calls to routine TIURB STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30387939 COMPONENT/ENTRY POINT: DEL(DA) COMPONENT DESCRIPTION: Allow an entry to be deleted or, to quote Joel, "we don't hand out pencils without erasers". VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT file (#8925) which user wants to delete. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2998 IA #: 2998 DATE CREATED: NOV 26, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIURA NAME: Calls to TIURA ID: TIURA GENERAL DESCRIPTION: This DBIA documents calls to routine TIURA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30387939 COMPONENT/ENTRY POINT: EDIT1 COMPONENT DESCRIPTION: Edit a TIU document. VARIABLES: TIUDA TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT file (#8925) denoting record to edit. COMPONENT/ENTRY POINT: PRNTDOC(METHOD,.ARRAY) COMPONENT DESCRIPTION: Call to print an array of documents of a single document type. VARIABLES: METHOD TYPE: Input VARIABLES DESCRIPTION: PRINT METHOD field from the TIU DOCUMENT DEFINITION file (#8925.1). VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: Array of documents to print in format: ARRAY(METHOD,DFN,COUNTER,TIUDA) where TIUDA is the IEN of the TIU DOCUMENT file (#8925) ^TMP("TIUPR",$J) may be killed before and after use. COMPONENT/ENTRY POINT: BROWS1(LISTTEMP) COMPONENT DESCRIPTION: Browse selected discharge summaries. Note this call expects list manager variables to be in place such as VALMY which is the array of documents to browse. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 2999 IA #: 2999 DATE CREATED: NOV 26, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUPRPN3 NAME: Calls to TIUPRPN3 ID: TIUPRPN3 GENERAL DESCRIPTION: This DBIA documents calls to routine TIUPRPN3. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30387939 COMPONENT/ENTRY POINT: $$FLAG() COMPONENT DESCRIPTION: Asks whether a chart copy or work copy should be printed. VARIABLES: $$FLAG TYPE: Output VARIABLES DESCRIPTION: RESULT=$$FLAG^TIUPRPN3() Returns 1 if CHART copy, 0 if WORK copy, or NULL if '^' SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: ORCNOTE kills ^TMP("TIUPR",$J) to make sure $$FLAG is starting with a clean slate. NUMBER: 3000 IA #: 3000 DATE CREATED: NOV 26, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIULM NAME: Calls to TIULM ID: TIULM GENERAL DESCRIPTION: This DBIA documents calls to TIULM. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30387939 COMPONENT/ENTRY POINT: FIXLST COMPONENT DESCRIPTION: Restores video attributes to List Manager list. VARIABLES: TMP('TIUR',$J,NUMBER) TYPE: Input VARIABLES DESCRIPTION: Array that List Manager uses to display the entries on the list. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3001 IA #: 3001 DATE CREATED: NOV 26, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIULA1 NAME: Calls to TIULA1 ID: TIULA1 GENERAL DESCRIPTION: This DBIA documents calls to routine TIULA1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30387939 COMPONENT/ENTRY POINT: $$ASKSIG() COMPONENT DESCRIPTION: Returns 0 if no valid electronic signature for user. Otherwise returns 1^EsigName^EsigTitle. VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: Expected to exist as system-wide variable DUZ defining the entry of the user in the NEW PERSON file (#200). VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: RESULT=$$ASKSIG^TIULA1() Where result returns: 0 if no valid electronic signature information for user; or 1^EsigName^EsigTitle SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3002 IA #: 3002 DATE CREATED: NOV 26, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUDEV NAME: Calls to TIUDEV ID: TIUDEV GENERAL DESCRIPTION: This DBIA documents calls to routien TIUDEV. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30387939 COMPONENT/ENTRY POINT: $$DEVICE(.IO,DEFAULT,QUEUE,SCREEN,IOP) COMPONENT DESCRIPTION: Prompts for device to print to. VARIABLES: IO TYPE: Output VARIABLES DESCRIPTION: IO of device selected. VARIABLES: DEFAULT TYPE: Input VARIABLES DESCRIPTION: (OPTIONAL) Default device to present to user. VARIABLES: QUEUE TYPE: Input VARIABLES DESCRIPTION: (Optional) Defaults to allow queuing, pass as null to avoid allowing queuing. VARIABLES: SCREEN TYPE: Input VARIABLES DESCRIPTION: (OPTIONAL) Screen for %ZIS if desired. VARIABLES: IOP TYPE: Input VARIABLES DESCRIPTION: (Optional) Define as input documented for call to %ZIS: IOP=device name to force printing to a particular device IOP="Q" to force queuing, but ask user for device IOP="P" to force pritning to the closest printer. VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: RESULT=$$DEVICE(.IO,DEFAULT,QUEUE,SCREEN,IOP) where result is set to ION or the name of the device. COMPONENT/ENTRY POINT: QUE(ZTRTN,ZTIO) COMPONENT DESCRIPTION: Queues output to print to specified device. VARIABLES: ZTRTN TYPE: Input VARIABLES DESCRIPTION: Callable entry point to generate output (as passed to %ZTLOAD). VARIABLES: ZTIO TYPE: Input VARIABLES DESCRIPTION: Device to print output to (as passed to %ZTLOAD). SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3003 IA #: 3003 DATE CREATED: NOV 29, 1999 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIULG NAME: Calls to routine TIULG ID: TIULG GENERAL DESCRIPTION: This DBIA documents calls made to routine TIULG. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30387939 COMPONENT/ENTRY POINT: $$PRNTGRP(IEN) COMPONENT DESCRIPTION: Returns PRINT GROUP (field #6.13) for given TIU DOCUMENT DEFINITION file (#8925.1) entry. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT DEFINITION file (#8925.1). VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: RESULT=$$PRNTGRP^TIULG(IEN) and returns the PRINT GROUP (field #6.13) for given TIU DOCUMENT DEFINITION file (#8925.1) entry. COMPONENT/ENTRY POINT: $$PRNTHDR(IEN) COMPONENT DESCRIPTION: Returns PRINT FORM HEADER (field #6.1) for given TIU DOCUMENT DEFINITION file (#8925.1) entry. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT DEFINITION file (#8925.1). VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: RESULT=$$PRNTHDR^TIULG(IEN) and returns the PRINT FORM HEADER (field #6.1) for given TIU DOCUMENT DEFINITION file (#8925.1) entry. COMPONENT/ENTRY POINT: $$PRNTMTHD(IEN) COMPONENT DESCRIPTION: Returns PRINT METHOD (field #6) for given TIU DOCUMENT DEFINITION file (#8925.1) entry. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT DEFINITION file (#8925.1). VARIABLES: O TYPE: Output VARIABLES DESCRIPTION: RESULT=$$PRNTMTHD^TIULG(IEN) and returns the PRINT METHOD (field #6) for given TIU DOCUMENT DEFINITION file (#8925.1) entry. COMPONENT/ENTRY POINT: $$PRNTNBR(IEN) COMPONENT DESCRIPTION: Returns PRINT FORM NUMBER (field #6.12) for given TIU DOCUMENT DEFINITION file (#8925.1) entry. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT DEFINITION file (#8925.1). VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: RESULT=$$PRNTNBR^TIULG(IEN) and returns the PRINT FORM NUMBER (field #6.12) for given TIU DOCUMENT DEFINITION file (#8925.1) entry. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: SURGERY NUMBER: 3004 IA #: 3004 FILE NUMBER: 100.98 GLOBAL ROOT: ORD(100.98, DATE CREATED: NOV 30, 1999 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: POINT TO DISPLAY GROUP (#100.98) FILE ID: ORD(100.98, GLOBAL REFERENCE: ORD(100.98, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28690761 SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 3005 IA #: 3005 FILE NUMBER: 100.21 GLOBAL ROOT: OR(100.21, DATE CREATED: NOV 30, 1999 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: POINT TO OE/RR LIST (#100.21) FILE ID: OR(100.21, GLOBAL REFERENCE: OR(100.21, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28690761 SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: HEALTH SUMMARY NUMBER: 3006 IA #: 3006 DATE CREATED: NOV 30, 1999 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XMXAPIG NAME: MAIL GROUP API ID: XMXAPIG GENERAL DESCRIPTION: The APIs in this DBIA perform mail group functions and actions. If any errors occur, the following variables will be defined: XMERR - The number of errors ^TMP("XMERR",$J,,"TEXT",)= Following is information on some common input parameters: XMGROUP - Mail group IEN or name (exact, case-sensitive) STATUS: Active MAIL MESSAGE: 32657102 COMPONENT/ENTRY POINT: $$GOTLOCAL COMPONENT DESCRIPTION: Find out whether or not a mail group has any active local members. Function returns 1 if it does; 0 if it doesn't. This can be important information. Just because a mail group may have local members, doesn't mean that any messages will be delivered to them. They must be active (have an access code and a mail box.) If the mail group does not exist or if there are no active local members, the function will return 0, XMERR will be defined, and there will be an appropriate error message in ^TMP("XMERR",$J), as noted above, in the General Description. Usage: I '$$GOTLOCAL^XMXAPIG(XMGROUP[,XMDAYS][,XMMBRS) D error Example: I '$$GOTLOCAL^XMXAPIG("GROUP") D error If the mail group named GROUP has no active local members, do an error routine to notify someone. Otherwise, go ahead and send the message. Optionally, you may specify an additional constraint, that at least one member must have used MailMan in the last few days. Example: I '$$GOTLOCAL^XMXAPIG("GROUP",9) D error If the mail group named GROUP doesn't have at least one active local member who has used MailMan in the last 9 days, do an error routine to notify someone. Otherwise, go ahead and send the message. Optionally, you may specify an additional constraint, that there must be not just 1, but at least XMMBRS active local members. Example: I '$$GOTLOCAL^XMXAPIG("GROUP","",3) D error There must be at least 3 active local members in the group. VARIABLES: XMGROUP TYPE: Input VARIABLES DESCRIPTION: See General Description. VARIABLES: XMDAYS TYPE: Used VARIABLES DESCRIPTION: (optional) Active members of the group must have used MailMan within the past number of days specified by XMDAYS. If XMDAYS is 0 or null or is not supplied, it is ignored. VARIABLES: XMMBRS TYPE: Used VARIABLES DESCRIPTION: Optional requirement that the group must contain at least this many active local members. Default is 1. COMPONENT/ENTRY POINT: ADDMBRS COMPONENT DESCRIPTION: Add members to mail group(s). Local users, devices, server options, mail groups, and remote users may be added to mail groups using this API. (Distribution lists, fax recipients, and fax groups are not handled by this API.) Optionally, find and forward existing mail group messages to the local users. Usage: D ADDMBRS^XMXAPIG(XMDUZ,[.]XMGROUP,[.]XMMBR,.XMINSTR,.XMTSK) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user who is adding the members to the group(s). The user must be authorized to edit the mail groups. Group coordinators or organizers may edit their own groups. The following users may edit public groups or unrestricted private groups: - Clinical Application Coordinators - Anyone possessing the XMMGR key - Anyone possessing the XM GROUP EDIT MASTER key VARIABLES: XMGROUP TYPE: Input VARIABLES DESCRIPTION: The group(s) to be edited. May either be passed by value (for a single group) or by reference (for one or more groups). May be the ien(s) of the group(s) in the MAIL GROUP file 3.8, or their name(s) (full and exact). XMGROUP="GROUP A" - or - XMGROUP("GROUP A")="" XMGROUP("GROUP B")="" VARIABLES: XMMBR TYPE: Input VARIABLES DESCRIPTION: The new member(s). May be passed by value (for one member) or by reference (for one or more members). The same rules apply for specifying XMMBRs as apply when you're addressing a message. VARIABLES: XMINSTR TYPE: Used VARIABLES DESCRIPTION: Optional special instructions to forward past messages to the local members. XMINSTR("FLAGS") - May contain any combination of the following: "F" - Forward messages to users, if the users aren't already on the messages. XMINSTR("FDATE") - Add users to messages originating on or after this date. Must be any exact date recognized by FileMan. Default is from the beginning of time. Used in conjunction with FLAGS. XMINSTR("TDATE") - Add users to messages originating on or before this date. Must be any exact date recognized by FileMan. Default is the present. Used in conjunction with FLAGS. VARIABLES: XMTSK TYPE: Output VARIABLES DESCRIPTION: The number of the task which will find and forward past mail group messages to local users. Returned only if XMINSTR("FLAGS") is passed in. COMPONENT/ENTRY POINT: JOIN COMPONENT DESCRIPTION: A user chooses to join one group, and optionally have past mail group messages forwarded. Usage: D JOIN^XMXAPIG(XMDUZ,XMGROUP,.XMINSTR,.XMTSK) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user who wants to join the group. VARIABLES: XMGROUP TYPE: Input VARIABLES DESCRIPTION: The group the user wants to join. See the General Description for more information. VARIABLES: XMINSTR TYPE: Used VARIABLES DESCRIPTION: Special instructions. See the description of the XMINSTR variable for entry ADDMBRS for more information. Additionally, if XMINSTR("FLAGS")=["F", may specify: XMINSTR("SELF BSKT") - the basket (name or ien) to which to deliver the messages VARIABLES: XMTSK TYPE: Output VARIABLES DESCRIPTION: Task number. See the description of XMTSK for entry ADDMBRS for more information. COMPONENT/ENTRY POINT: DROP COMPONENT DESCRIPTION: User chooses to drop from one mail group. Usage: D DROP^XMXAPIG(XMDUZ,XMGROUP) VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user who wants to drop from the mail group. VARIABLES: XMGROUP TYPE: Input VARIABLES DESCRIPTION: The group from which the user wants to drop. See the General Description for more information. COMPONENT/ENTRY POINT: $$MEMBER COMPONENT DESCRIPTION: Find out whether a user is a member of a mail group. Function returns 1 if yes; 0 if no. If the user isn't a direct member, optionally check to see if the user is a member of any of the group's member groups. Usage: I $$MEMBER^XMXAPIG(XMDUZ,XMGROUP[,XMCHKSUB]) D ... VARIABLES: XMDUZ TYPE: Input VARIABLES DESCRIPTION: The user in question. VARIABLES: XMGROUP TYPE: Input VARIABLES DESCRIPTION: The group to check. See the General Description for more information. VARIABLES: XMCHKSUB TYPE: Used VARIABLES DESCRIPTION: If the user isn't found in the group, should we check the member groups? 1=yes; 0=no. Default is no. NUMBER: 3007 IA #: 3007 FILE NUMBER: 423.6 GLOBAL ROOT: PRCF(423.6, DATE CREATED: DEC 02, 1999 CUSTODIAL PACKAGE: IFCAP CUSTODIAL ISC: Washington USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3007 ID: PRCF(423.6, GLOBAL REFERENCE: PRCF(423.6,B, FIELD NUMBER: .01 FIELD NAME: TRANSACTION ID LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL DESCRIPTION: This is the B cross reference for the .01 field in the file. AR $orders through the B cross reference to locate the transactions that need to be processed. GLOBAL REFERENCE: PRCF(423.6,DA,1, FIELD NUMBER: 1 FIELD NAME: TRANSACTION LOCATION: 1;0 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the actual transactions received from FMS. This is a multiple field. GLOBAL DESCRIPTION: This global stores the transactions received from FMS. AR $orders through these transactions and processes the data. GENERAL DESCRIPTION: This agreement allows AR to reference the IFCAP file ISMS/FMS TRANS #423.6. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30533095 SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring EDITOR: GRIBSCHAW,STEPHEN J EDITOR: LAWSON,DEBBI NUMBER: 3008 IA #: 3008 FILE NUMBER: 8930 GLOBAL ROOT: USR(8930, DATE CREATED: DEC 07, 1999 CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: POINT TO USR CLASS (#8930) FILE ID: USR(8930, GLOBAL REFERENCE: USR(8930, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30519178 SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City NUMBER: 3009 IA #: 3009 DATE CREATED: DEC 08, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XQALFWD NAME: XQALFWD ID: XQALFWD GENERAL DESCRIPTION: This entry point can be used to forward alerts (in most cases, for the current user only). It is a silent (no screen input or output) entry point, and so can be used for windowed applications. Example ; get open alerts for current user K A6AALRT D USER^XQALERT("A6AALRT") ; I +A6AALRT D ; if any current alerts... .; loop through A6AALRT array, parse alert id for each open alert .K A6AALRT1 S A6ASUB="",A6AI=0 .F S A6ASUB=$O(A6AALRT(A6ASUB)) Q:'$L(A6ASUB) D ..S A6AI=A6AI+1,A6AALRT1(A6AI)=$P(A6ASUB,"^",2) .; .;forward open alerts of current user to MAS CLERKS mailgroup .K A6AUSER S A6AUSER="G.MAS CLERKS" .D FORWARD^XQALFWD(.A6AALRT1,A6AUSER,"A","Forwarded Alert") Q STATUS: Active MAIL MESSAGE: 31934677 COMPONENT/ENTRY POINT: FORWARD COMPONENT DESCRIPTION: Usage D FORWARD^XQALFWD([.]alerts,[.]users,type,comment) VARIABLES: [.]alerts TYPE: Input VARIABLES DESCRIPTION: Array of alerts to be forwarded, each identified by its full alert identifier (the value of the ALERT ID field in the ALERT DATE/TIME multiple of the current user's entry in the ALERT file. Current user is identified by the value of the XQADUZ variable). The alert identifiers for a user's current open alerts can be obtained using the USER^XQALERT entry point. If only a single alert is to be forwarded, only the top node must be set (set it to the alert identifier of the alert to forward, and pass by value). If there are multiple alerts to forward, the value of each entry in the array should be one of the desired alert identifier. For example, A6AALRT(1)="NO-ID;92;2941215.100432" A6AALRT(2)="NO-ID;161;2941220.111907" A6AALRT(3)="NO-ID;161;2941220.132401" If using an array, the array must be passed by reference in the parameter list. VARIABLES: [.]users TYPE: Input VARIABLES DESCRIPTION: Users to forward alert to. For forwarding as an alert or as a mail message (when the type parameter is A or M), the variable may specify one or more users, and/or mailgroups. For users, specify by ien (in the NEW PERSON file). You do not need to precede the user's ien with an accent grave. For mail groups, specify in format G.MAILGROUP. If there is only a single user or mailgroup, just set the top node of the array to that value, and pass it by value. If there are multiple values to be passed, pass them as the values of numerically subscripted array nodes (and pass the array by reference). For example, A6AUSER(1)="G.MAS CLERKS" A6AUSER(2)="G.MAS OVERNIGHT" For forwarding to a printer (when the type parameter is P), there should be only a single value specifying the desired entry in the DEVICE file. You can specify the device either by name or by internal entry number (ien). If specifying by ien, precede the ien with an accent grave (e.g., `202). VARIABLES: type TYPE: Input VARIABLES DESCRIPTION: Indicates the method of forwarding desired. The options are the single characters 'A' (to forward as an Alert), 'M' (to forward as a Mail Message), and 'P' (to print a copy of the alert). If the value passed is not either A, M, or P, then no action will be taken. VARIABLES: comment TYPE: Input VARIABLES DESCRIPTION: A character string to use as a comment to accompany the alert when it is forwarded. EDITOR: ORMSBY,SKIP EDITOR: DAVIS,KENNETH L NUMBER: 3010 IA #: 3010 DATE CREATED: DEC 08, 1999 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XQALBUTL NAME: XQALBUTL ID: XQALBUTL STATUS: Active MAIL MESSAGE: 33755309 COMPONENT/ENTRY POINT: RECIPURG COMPONENT DESCRIPTION: Called by option ORB PURG RECIP - purge existing notifs: recipient/DUZ VARIABLES: DUZ TYPE: Input VARIABLES DESCRIPTION: User whose alerts you want to delete COMPONENT/ENTRY POINT: PTPURG COMPONENT DESCRIPTION: called by option ORB PURG PATIENT - purge existing notifs: patient VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN of patient whose alerts you want to delete COMPONENT/ENTRY POINT: NOTIPURG COMPONENT DESCRIPTION: called by option ORB PURG NOTIF - purge existing notifs: notification VARIABLES: NOT TYPE: Input VARIABLES DESCRIPTION: IEN of Notification [#100.9] all instances of which will be deleted NUMBER: 3011 IA #: 3011 DATE CREATED: DEC 08, 1999 CUSTODIAL PACKAGE: RPC BROKER CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: XWB IS RPC AVAILABLE GENERAL DESCRIPTION: This RPC allows an application to determine if a particular RPC is available on a server. INPUT PARAMETER: RPC PARAMETER TYPE: LITERAL SEQUENCE NUMBER: 1 (Required) DESCRIPTION: Name of the RPC to be tested. INPUT PARAMETER: RUN CONTEXT PARAMETER TYPE: LITERAL SEQUENCE NUMBER: 2 (Optional) DESCRIPTION: Specific context in which RPC will run. Possible values are: L = run Locally (on the server the user is logged on to) R = run Remotely (on a server the user is not logged on to) If this parameter is not sent, RPC is checked for both local and remote. The check is done against the value in the INACTIVE field in the Remote Procedure file. See that field's description for more details. INPUT PARAMETER: VERSION NUMBER PARAMETER TYPE: LITERAL SEQUENCE NUMBER: 3 (Optional) DESCRIPTION: Minimum version number of the RPC. This parameter is only used if the RUN CONTEXT parameter = "R". If a numeric value is in this parameter, the value must be less than or equal to the value in the VERSION field of the Remote Procedure file for the RPC is be marked available. Note: if the VERSION field is null, the check will fail for any numeric value in this parameter. RETURN VALUE DESCRIPTION: Boolean. 1 = RPC available. 0 = RPC not available. STATUS: Active MAIL MESSAGE: 30566281 KEYWORDS: RPC KEYWORDS: Remote Procedure NUMBER: 3012 IA #: 3012 DATE CREATED: DEC 08, 1999 CUSTODIAL PACKAGE: RPC BROKER CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: XWB ARE RPCS AVAILABLE GENERAL DESCRIPTION: This RPC allows an application to determine if a list of RPCs are available for use on the server. INPUT PARAMETER: RUN CONTEXT PARAMETER TYPE: LITERAL SEQUENCE NUMBER: 1 (Optional) DESCRIPTION: Specific context in which RPCs will run. Possible values are: L = run Locally (on the server the user is logged on to) R = run Remotely (on a server the user is not logged on to) If this parameter is not sent, RPC is checked for both local and remote. The check is done against the value in the INACTIVE field in the Remote Procedure file. See that field's description for more details. INPUT PARAMETER: RPC PARAMETER TYPE: LIST SEQUENCE NUMBER: 2 (Required) DESCRIPTION: This 0-based array contains list of RPCs to be checked along with (optionally) a minimum acceptable version of the RPC. The format is: RPCName^RPCVersionNumber The RPCVersionNumber is only used if the RUN CONTEXT parameter = "R". If a numeric value is in the second ^-piece and the RUN CONTEXT ="R", the value must be less than or equal to the value in the VERSION field of the Remote Procedure file for the RPC to be marked available. Note: if the VERSION field is null, the check will fail for any numeric value. RETURN VALUE DESCRIPTION: A 0-based array. The index corresponds to the index of the RPC in the RPC Input Parameter. A value of 1 means the corresponding RPC is available; a value of 0 means it is not available. STATUS: Active MAIL MESSAGE: 30566290 KEYWORDS: RPC KEYWORDS: REMOTE PROCEDURE NUMBER: 3013 IA #: 3013 FILE NUMBER: 52.7 GLOBAL ROOT: PS(52.7 DATE CREATED: DEC 21, 1999 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3013 ID: PS(52.7 GENERAL DESCRIPTION: Controlled Substances is given permission to reference the fields identified in this integration agreement. The refernces are made using the VA Fileman API ^DIC. GLOBAL MAP DATA DICTIONARY #52.7 -- IV SOLUTIONS FILE STORED IN ^PS(52.7, (3 ENTRIES) SITE: BIRMINGHAM ISC (#14) ^PS(52.7,D0,0)= (#.01) PRINT NAME [1F] Read w/Fileman ^PS(52.7,D0,0)= (#2) VOLUME [3F] Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30599224 SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 3015 IA #: 3015 DATE CREATED: JAN 12, 2000 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFCPID NAME: PID segment generation (CIRN PD) ID: VAFCPID GENERAL DESCRIPTION: The purpose of this IA is to create a PID segment when a patient is: 1) admitted 2) discharged 3) checked out of a clinic This segment is part of a HL7 message used by CIRN PD to DATE LAST TREATED (#.03) and the ADT/HL7 EVENT REASON (#.07) fields in the TREATING FACILITY LIST (#391.91) file. This is patient/facility specific information. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30723888 COMPONENT/ENTRY POINT: $$EN COMPONENT DESCRIPTION: This entry point is passed three input parameters: 1) internal entry number of the PATIENT file 2) string of fields requested separated by commas 3) sequential number for SET ID (default=1) All three input parameters are used by this IA. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: ien of the patient in the Patient (#2) file VARIABLES: VAFSTR TYPE: Input VARIABLES DESCRIPTION: string of fields of the PID segment requested (separated by commas). VARIABLES: VAFNUM TYPE: Input VARIABLES DESCRIPTION: sequential number for SET ID (default=1) SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING NUMBER: 3017 IA #: 3017 DATE CREATED: JAN 12, 2000 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFHLPD1 NAME: PD1 segment generator ID: VAFHLPD1 GENERAL DESCRIPTION: Supported call for building of HL7 PD1 segment (Patient Additional Demographics). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30725118 KEYWORDS: PD1 COMPONENT/ENTRY POINT: $$EN(DFN,VAFSTR) COMPONENT DESCRIPTION: Main entry point for building of PD1 segment VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to PATIENT file (#2) VARIABLES: VAFSTR TYPE: Input VARIABLES DESCRIPTION: String of fields requested seperated by commas VARIABLES: HL7 variables TYPE: Input VARIABLES DESCRIPTION: Call assumes that all HL7 variables returned from INIT^HLFNC2 are defined VARIABLES: Result of call TYPE: Output VARIABLES DESCRIPTION: String of data forming the PD1 segment NUMBER: 3018 IA #: 3018 DATE CREATED: JAN 12, 2000 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFHLPV1 NAME: PV1 segment generator ID: VAFHLPV1 GENERAL DESCRIPTION: Supported calls for building of HL7 PV1 segment (Patient Visit) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30753825 KEYWORDS: PV1 COMPONENT/ENTRY POINT: $$EN(VAFENC,VAFDENC,VAFSTR,VAFNUM,VAFHLQ,VAFHLFS) COMPONENT DESCRIPTION: Entry point to build PV1 segment for [Deleted] Outpatient Encounter NOTE: Data for the PV1 segment will be retrieved from either the Outpatient Encounter file (#409.68) or Deleted Outpatient Encounter (#409.74) based on the pointer parameter passed in. VARIABLES: VAFENC TYPE: Input VARIABLES DESCRIPTION: Pointer to Outpatient Encounter file (#409.68) VARIABLES: VAFDENC TYPE: Input VARIABLES DESCRIPTION: Pointer to Deleted Outpatient Encounter file (#409.74) VARIABLES: VAFSTR TYPE: Input VARIABLES DESCRIPTION: String of fields requested separated by commas VARIABLES: VAFNUM TYPE: Input VARIABLES DESCRIPTION: Value to use for Set ID (sequence #1). Defaults to 1. VARIABLES: VAFHLQ TYPE: Input VARIABLES DESCRIPTION: Optional HL7 null variable. (Default value is value of HLQ) VARIABLES: VAFHLFS TYPE: Input VARIABLES DESCRIPTION: Optional HL7 field separator. (Default value is value of HLFS) VARIABLES: Result of call TYPE: Output VARIABLES DESCRIPTION: String of data forming the PV1 segment COMPONENT/ENTRY POINT: $$IN(DFN,VAFHDT,VAFSTR,IEN,PIVOT,SETID,.VAFDIAG) COMPONENT DESCRIPTION: Entry point to build PV1 segment for inpatient movement. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient file (#2) VARIABLES: VAFHDT TYPE: Input VARIABLES DESCRIPTION: Date/Time of movement VARIABLES: VAFSTR TYPE: Input VARIABLES DESCRIPTION: String of fields requested seperated by commas VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient Movement file (#405). Optional - used for discharge movements since VADPT doesn't return enough information if only date/time (VAFHDT) is passed. VARIABLES: ALTVISID TYPE: Input VARIABLES DESCRIPTION: Value to use for Alternate Visit ID (sequence 50). Optional. VARIABLES: SETID TYPE: Input VARIABLES DESCRIPTION: Value to use for Set ID (sequence #1). Defaults to 1. VARIABLES: VAFDIAG TYPE: Output VARIABLES DESCRIPTION: Inpatient diagnosis returned in this variable. VARIABLES: Result of call TYPE: Output VARIABLES DESCRIPTION: String of data forming the PV1 segment COMPONENT/ENTRY POINT: $$OUT(DFN,EVT,EVDTS,VPTR,STRP,NUMP) COMPONENT DESCRIPTION: Entry point to build PV1 segment for patient VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to Patient file (#2) VARIABLES: EVT TYPE: Input VARIABLES DESCRIPTION: Pivot number to build segment for. Value comes from the Pivot Number field (#.02) of ADT/HL7 Pivot file (#391.71). If passed, this value will also be used as the Alternate Visit ID (sequence #50). VARIABLES: EVDTS TYPE: Input VARIABLES DESCRIPTION: Event date/time in FileMan format. Only used if input parameter EVT is not passed/valid. VARIABLES: VPTR TYPE: Input VARIABLES DESCRIPTION: Variable pointer (FileMan format) to Patient file (#2), Patient Movement file (#405), or Outpatient Encounter file (#409.68). Only used if input parameter EVT is not passed/valid. VARIABLES: STRP TYPE: Input VARIABLES DESCRIPTION: String of fields requested seperated by commas. If value is "A" or null then all supported fields are returned. VARIABLES: NUMP TYPE: Input VARIABLES DESCRIPTION: Value to use for Set ID (sequence #1). Defaults to 1. SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: LAB SERVICE NUMBER: 3019 IA #: 3019 DATE CREATED: JAN 20, 2000 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DG CHK BS5 XREF Y/N REMOTE PROCEDURE: DG CHK BS5 XREF Y/N ID: 3019 STATUS: Active MAIL MESSAGE: 30756826 NUMBER: 3020 IA #: 3020 CUSTODIAL PACKAGE: REGISTRATION USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DG CHK BS5 XREF ARRAY REMOTE PROCEDURE: DG CHK BS5 XREF ARRAY ID: 3020 STATUS: Active MAIL MESSAGE: 30756826 NUMBER: 3021 IA #: 3021 CUSTODIAL PACKAGE: REGISTRATION USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DG CHK MEANS TEST DIV DISPLAY REMOTE PROCEDURE: DG CHK MEANS TEST DIV DISPLAY ID: 3021 STATUS: Active MAIL MESSAGE: 30756826 NUMBER: 3022 IA #: 3022 CUSTODIAL PACKAGE: REGISTRATION USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DG CHK PAT MEANS TEST REQUIRED REMOTE PROCEDURE: DG CHK PAT MEANS TEST REQUIRED ID: 3022 STATUS: Active MAIL MESSAGE: 30756826 NUMBER: 3023 IA #: 3023 CUSTODIAL PACKAGE: REGISTRATION USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DG CHK PAT/DIV MEANS TEST REMOTE PROCEDURE: DG CHK PAT/DIV MEANS TEST ID: 3023 STATUS: Active MAIL MESSAGE: 30756826 NUMBER: 3027 IA #: 3027 DATE CREATED: JAN 31, 2000 CUSTODIAL PACKAGE: REGISTRATION USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGSEC4 NAME: Security/Sensitive Record access ID: DGSEC4 GENERAL DESCRIPTION: This integration agreement provides 2 entry points in DGSEC4: PTSEC^DGSEC4 determines if patient's record is sensitive or if user is accessing his/her own Patient (#2) file record. NOTICE^DGSEC4 adds or updated the DG Security Log (#38.1) file and optionally generates the Sensitive Record Access mail message. STATUS: Active MAIL MESSAGE: 30810277 COMPONENT/ENTRY POINT: PTSEC COMPONENT DESCRIPTION: This entry point will: - verify user is not accessing his/her own PATIENT (#2) file record if Restrict Patient Record Access parameter in the MAS Parameter (#43) file is yes. - determine if record is sensitive - determine if patient's primary eligibility code is Employee. The following array is returned: RESULT(1)= -1 API failed Required variable not defined 0 No display and no action required Not an employee, not a sensitive record and user is not accessing his/her own Patient (#2) file record. 1 Display warning message Sensitive-inpatient or a DG SENSITIVITY key holder or an Employee and a DG SECURITY OFFICER key holder 2 Display warning message and require OK to continue Sensitive-not an inpatient and not a DG SENSITIVITY key holder or not an employee and not a DG SECURITY OFFICER key holder 3 Access to record denied Accessing own Patient (#2) file record 4 Access to Patient (#2) file records denied User's SSN not defined in New Person (#200) file RESULT(2-10)=error message or warning/Privacy Act message If RESULT(1)=1, an entry is added or updated to the DG SECURITY LOG (#38.1) file. If RESULT(1)=2 and user acknowledges they wish to access the restricted record, the calling application should call NOTICE^DGSEC4 to update DG Security Log (#38.1) file and generate the Sensitive Record Access mail message. VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: The first parameter contains the name of the output array. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN = Patient (#2) file IEN VARIABLES: DGMSG TYPE: Input VARIABLES DESCRIPTION: DGMSG = 1 - if message should be generated when a user's SSN is undefined. 0 - message will not be generated If not defined, defaults to 1. VARIABLES: DGOPT TYPE: Input VARIABLES DESCRIPTION: DGOPT is an optional variable containing the option name ^ menu text. If not defined, OP^XQCHK attempts to identify the option name. UNKNOWN will be entered in the DG Security Log file if option name not passed to call or not identified by OP^XQCHK. COMPONENT/ENTRY POINT: NOTICE COMPONENT DESCRIPTION: This entry point adds or updates an entry to the DG SECURITY LOG (#38.1) file and optionally generate the sensitive record access bulletin depending on the value in the ACTION input parameter. If ACTION parameter is not defined, defaults to update DG Security Log file and generate Sensitive Record Access mail message. VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: RESULT=1 - Added/updated entry and generated sensitive record access msg 0 - unsuccessful VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN is a required parameter containing the Patient (#2) file IEN. VARIABLES: DGOPT TYPE: Input VARIABLES DESCRIPTION: DGOPT is an optional parameter containing the Option Name^Menu Text. If not defined, OP^XQCHK attempts to identify the option name. UNKNOWN will be entered in the DG SECURITY LOG file if option name not passed to call or not identified by OP^XQCHK. VARIABLES: ACTION TYPE: Input VARIABLES DESCRIPTION: ACTION = 1 - Set DG Security Log entry 2 - Generate Sensitive Record Access bulletin 3 - Both This is an optional parameter. If not defined, defaults to 3. DBA Comments: 3/5/15-MM: VPS Kiosk asked to be a subscriber to ICR #767 for access to DG Security Log file. It was decided the APIs in ICR #3027 would provide the functionality they need for VPS*1*15. NUMBER: 3028 IA #: 3028 FILE NUMBER: 8930.3 GLOBAL ROOT: USR(8930.3 DATE CREATED: JAN 31, 2000 CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3028 ID: USR(8930.3 GLOBAL REFERENCE: USR(8930.3 FIELD NUMBER: .01 FIELD NAME: MEMBER ACCESS: Pointed to GLOBAL REFERENCE: USR(8930.3,0) FIELD NUMBER: .01 FIELD NAME: MEMBER ACCESS: Read w/Fileman GENERAL DESCRIPTION: QUASAR A&SP STAFF File, #509850.3, will point to USR CLASS MEMBERSHIP FILE, #8930.3. USR does not normally permit storing User Class memberships. Generally membership is checked on the fly using APIs to determine a permission, or checked and then a result is stored which does not point to the USR file. For example, the TIU document file has field COSIGNATURE NEEDED which stores the result of a lookup in the USR file and in TIU parameters. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30800549 KEYWORDS: QUASAR SUBSCRIBING PACKAGE: QUASAR ISC: Hines SUBSCRIBING DETAILS: Pointer to File #8930.3, USR Class Membership NUMBER: 3029 IA #: 3029 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: FEB 03, 2000 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TRANSFER FACILITY ID: DGPM( GLOBAL REFERENCE: DGPM(D0,0) FIELD NUMBER: .05 FIELD NAME: TRANSFER FACILITY LOCATION: 0;5 ACCESS: Read w/Fileman GENERAL DESCRIPTION: This integration agreement grants permission to the subscribing package to read with FileMan the TRANSFER FACILITY field (#.05) in the PATIENT MOVEMENT file (#405). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30813958 SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham SUBSCRIBING DETAILS: The information in this field will be used by the Continuous Improvement in Cardiac Surgery Program (CICSP). NUMBER: 3031 IA #: 3031 DATE CREATED: APR 29, 2003 CUSTODIAL PACKAGE: RPC BROKER CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: Remote RPCs GENERAL DESCRIPTION: This DBIA describes the Broker RPCs that provide the capability of running any application RPC on a remote system. They were developed to support the CPRS Remote Data Views project. NOTE: This 'Server to Server RPC' functionality is currently limited to sites that have implemented CIRN. CIRN makes it possible for an application to know a patient's current list of treating facilities. Furthermore, CIRN has assumed responsibility for supervising the proper configuration and activation of the VA network nodes that will be used for HL7 message exchange. XWB REMOTE RPC This is the RPC that is called to request that an application RPC be run on a remote system. The data is passed by HL7 to the remote system as is the return value. This RPC will return a HANDLE that can be used to check if the data has been sent back from the remote system. The HANDLE can be used in another RPC to check the status of the RPC. Parameters: (location,rpc name,[rpc version],[1 to 10 params to the RPC)) Return: The return value is always an array. The first node of the array is equal to a string that serves as a HANDLE. This is used to check the status of a RPC request and to retrieve the results of the RPC. In the case of an error condition, the first node of the array is equal to a string with the syntax "-1^error text". XWB REMOTE STATUS CHECK This RPC will return the status of a remote RPC. Parameters: The HANDLE from the XWB REMOTE RPC. Return: The return value is always an array. The first node of the array is equal to one of the following values: "-1^Bad Handle" - An invalid handle has been passed. "0^New" - The request has been sent. "0^Running" - HL7 indicates that the message is being processed. "1^Done" - RPC has completed and the data has returned to the local server. The data is not returned by this RPC. Use the XWB REMOTE GETDATA RPC to retrieve the data. The second node of the array is the status from the HL7 package. XWB REMOTE GETDATA This RPC will return an ARRAY with what ever data has been sent back from the remote site. Parameters: The HANDLE from the XWB REMOTE RPC. It is used to link the call to the data. Return: The return value is the array of data. In the event of an error condition, the first node of the array is equal to a string with the syntax "-1^error text". XWB REMOTE CLEAR This RPC is used to CLEAR the data under the HANDLE in the ^XTMP global. Parameters: The HANDLE from the XWB REMOTE RPC. Return: The return value is always an array. The first node of the array is equal to 1 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30816188 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City EDITOR: MANAPSAL,DANILA NUMBER: 3035 IA #: 3035 DATE CREATED: MAY 29, 2003 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAAVCPT NAME: DBIA3035-A ORIGINAL NUMBER: 3035 ID: PXAAVCPT GENERAL DESCRIPTION: The following is a description of the available APIs for the V CPT (#9000010.18) file. The V CPT (#9000010.18) file is used to store CPT related services performed during a visit. STATUS: Active DURATION: Next Version MAIL MESSAGE: 30948205 GOOD ONLY FOR VERSION: 2 KEYWORDS: PXAA COMPONENT/ENTRY POINT: $$GETIENS(VSITIEN,ARRAY) COMPONENT DESCRIPTION: Use this API to retrieve all Internal Entry Numbers (IEN) from the V CPT (#9000010.18) file associated with the given visit IEN, VSITIEN. VARIABLES: VSITIEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a given patient visit. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) This array variable is populated by the API with the Internal Entry Numbers of records found to be associated in the V CPT (#9000010.18) file with the patient visit IEN. VARIABLES: $$GETIENS TYPE: Output VARIABLES DESCRIPTION: If the value returned is equal to 0, no record was found in the V CPT (#9000010.18) file for the given visit IEN. If the value returned is equal to 1, one or more records were found in the V CPT (#9000010.18). COMPONENT/ENTRY POINT: $$LOADFLDS(IEN,ARRAY) COMPONENT DESCRIPTION: This API loads all the field values for a given record IEN in the V CPT (#9000010.18) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) All the field values of the V CPT (#9000010.18) file for the given record IEN such as; Patient Name, Diagnosis Field, Narrative Field, etc are loaded into this array variable. VARIABLES: $$LOADFLDS TYPE: Output VARIABLES DESCRIPTION: If the value returned is equal to 0, no record was found in the V CPT (#9000010.18) file for the given IEN. Returns 1 if the API has successfully loaded all the field values into the ARRAY variable. COMPONENT/ENTRY POINT: $$CPT(IEN) COMPONENT DESCRIPTION: This API returns field (#.01) - CPT, of the V CPT (#900018.10) file. The CPT code that most closely represents the clinical procedure performed on the patient during the encounter. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$CPT TYPE: Output VARIABLES DESCRIPTION: Returns the CPT code that most closely represents the clinical procedure performed on the patient during the encounter. COMPONENT/ENTRY POINT: $$PATINAME(IEN) COMPONENT DESCRIPTION: This API returns field (#.02) - PATIENT NAME, of the V CPT (#9000010.18) file. A pointer to the Patient Name to whom the procedure was performed. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$PATINAME TYPE: Output VARIABLES DESCRIPTION: A pointer to the PATIENT/IHS (#9000001) file. COMPONENT/ENTRY POINT: $$VISIT(IEN) COMPONENT DESCRIPTION: This API returns field (#.03) - VISIT, of the V CPT (#9000010.18) file. A pointer to the VISIT (#9000010) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$VISIT TYPE: Output VARIABLES DESCRIPTION: A pointer to the Visit (#9000010) file. COMPONENT/ENTRY POINT: $$PROVNARR(IEN) COMPONENT DESCRIPTION: This API returns field (#.04) - PROVIDER NARRATIVE, of the V CPT (#9000010.18) file. A pointer to the Provider Narrative (#9999999.27) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$PROVNARR TYPE: Output VARIABLES DESCRIPTION: A pointer to the Provider Narrative (#9999999.27) file. COMPONENT/ENTRY POINT: $$DIAGNOSI(IEN) COMPONENT DESCRIPTION: This API returns field (#.05) - DIAGNOSIS, of the V CPT (#9000010.18) file. A pointer to the ICD Diagnosis (#80) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$DIAGNOSI TYPE: Output VARIABLES DESCRIPTION: A pointer to the ICD Diagnosis (#80) file. COMPONENT/ENTRY POINT: $$PRINPROC(IEN) COMPONENT DESCRIPTION: This API returns field (#.07) - PRINCIPAL PROCEDURE, of the V CPT (#9000010.18) file. A flag identifying whether this procedure was the principal procedure performed on the patient during the encounter. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$PRINPROC TYPE: Output VARIABLES DESCRIPTION: Returns 'Y' if this procedure has been identified as the principal procedure done to the patient during the encounter. COMPONENT/ENTRY POINT: $$QUANTITY(IEN) COMPONENT DESCRIPTION: This API returns field (#.16) - QUANTITY, of the V CPT (#9000010.18) file. A number between 1 and 99 indicating how many times this procedure was performed. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$QUANTITY TYPE: Output VARIABLES DESCRIPTION: The number of times this procedure was performed for the given visit. COMPONENT/ENTRY POINT: $$CPTMODIF(IEN) COMPONENT DESCRIPTION: This API returns field (#1) - CPT MODIFIER, of the V CPT (#9000010.18) file. A pointer to the CPT Modifier (#81.3) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$CPTMODIF TYPE: Output VARIABLES DESCRIPTION: A pointer to the CPT Modifier (#81.3) file. COMPONENT/ENTRY POINT: $$EVENTDT(IEN) COMPONENT DESCRIPTION: This API returns field (#1201) - EVENT DATE & TIME of the V CPT (#9000010.18) file, the date and time the procedure was performed. Note : This date and time may be different from the visit date and time. For example, for clinic appointment visits, the visit date and time is the date and time of the appointment, not the time the provider performed the clinical event. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$EVENTDT TYPE: Output VARIABLES DESCRIPTION: The Date and Time that the procedure took place. COMPONENT/ENTRY POINT: $$ORDEPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1202) - ORDERING PROVIDER of the V CPT (#9000010.18) file. Indicates identification of the provider who ordered the procedure. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$ORDEPROV TYPE: Output VARIABLES DESCRIPTION: A value identifying the provider who ordered the procedure. COMPONENT/ENTRY POINT: $$ENCOPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1204) - ENCOUNTER PROVIDER, of the V CPT (#9000010.18) file. Indicates the identification of the provider who performed the procedure. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$ENCOPROV TYPE: Output VARIABLES DESCRIPTION: A value identifying the provider who performed the procedure. COMPONENT/ENTRY POINT: $$EDITFLAG(IEN) COMPONENT DESCRIPTION: This API returns field (#80101) - EDITED FLAG, of the V CPT (#9000010.18) file. A value indicating if PCE detects that any original procedure data as being edited. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$EDITFLAG TYPE: Output VARIABLES DESCRIPTION: A value indicating if PCE detects that any original data as being edited. COMPONENT/ENTRY POINT: $$AUDITRAI(IEN) COMPONENT DESCRIPTION: This API returns field (#80102) - AUDIT TRAIL, of the V CPT (#9000010.18) file. This field is populated automatically by the PCE filing logic. The format of the field is as follows: Pointer to PCE data source file_"-"_A for Add or E for Edit_" "_DUZ of the person who entered the data_";". VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$AUDITRAI TYPE: Output VARIABLES DESCRIPTION: A Free Text value in the format; Pointer to PCE data source file_"-"_A for Add or E for Edit_" "_DUZ of the person who entered the data_";" COMPONENT/ENTRY POINT: $$PRONARCA(IEN) COMPONENT DESCRIPTION: This API returns field (#80201) PROVIDER NARRATIVE CATEGORY of the V CPT (#9000010.18) file. A pointer to the Provider Narrative (#9999999.27) file which is the heading or category used to represent the provider narrative on the scanner form. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$PRONARCA TYPE: Output VARIABLES DESCRIPTION: Returns a pointer to the Provider Narrative (#9999999.27) file which indicates the heading or category used to represent the provider narrative on the scanner form. COMPONENT/ENTRY POINT: $$COMMENTS(IEN) COMPONENT DESCRIPTION: This API returns field (#81101) - COMMENTS, of the V CPT (#9000010.18) file. Any comments related to the procedure performed. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$COMMENTS TYPE: Output VARIABLES DESCRIPTION: A Free Text value indicating any comments related to the procedure performed and entered manually. COMPONENT/ENTRY POINT: $$VERIFIED(IEN) COMPONENT DESCRIPTION: This API returns field (#81201) - VERIFIED, of the V CPT (#9000010.18) file. A flag indicating whether the record was Electronically Signed or Verified by the Package. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$VERIFIED TYPE: Output VARIABLES DESCRIPTION: Returns '1' to indicate the record was Electronically Signed. Returns '0' to indicate that the record was Verified by the Package. COMPONENT/ENTRY POINT: $$PACKAGE(IEN) COMPONENT DESCRIPTION: This API returns field (#81202) - PACKAGE, of the V CPT (#9000010.18) file. A pointer to the Package (#9.4) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$PACKAGE TYPE: Output VARIABLES DESCRIPTION: Pointer to the Package (#9.4) file. COMPONENT/ENTRY POINT: $$DATASRC(IEN) COMPONENT DESCRIPTION: This API returns field (#81203) - DATA SOURCE, of the V CPT (#9000010.18) file. A pointer to the PCE Data Source (#839.7) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$DATASRC TYPE: Output VARIABLES DESCRIPTION: Pointer to the PCE Data Source (#839.7) file. COMPONENT/ENTRY POINT: $$DIAGNOS2(IEN) COMPONENT DESCRIPTION: This API returns field (#.09) - DIAGNOSIS 2, of the V CPT (#9000010.18) file. A pointer to the ICD Diagnosis (#80) file. VARIABLES: $$DIAGNOS2 TYPE: Output VARIABLES DESCRIPTION: A pointer to the ICD Diagnosis (#80) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. COMPONENT/ENTRY POINT: $$DIAGNOS3(IEN) COMPONENT DESCRIPTION: This API returns field (#.1) - DIAGNOSIS 3, of the V CPT (#9000010.18) file. A pointer to the ICD Diagnosis (#80) file. VARIABLES: $$DIAGNOS3 TYPE: Output VARIABLES DESCRIPTION: Pointer to the ICD Diagnosis File (#80) VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. COMPONENT/ENTRY POINT: $$DIAGNOS4(IEN) COMPONENT DESCRIPTION: This API returns field (#.11) - DIAGNOSIS 4, of the V CPT (#9000010.18) file. A pointer to the ICD Diagnosis (#80) file. VARIABLES: $$DIAGNOS4 TYPE: Output VARIABLES DESCRIPTION: Pointer to the ICD Diagnosis File (#80) VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. COMPONENT/ENTRY POINT: $$SERVCONN(IEN) COMPONENT DESCRIPTION: This API returns the Service Connected indicator, field (#80001), for this procedure. VARIABLES: $$SERVCONN TYPE: Output VARIABLES DESCRIPTION: If this CPT code is treating a service connected problem VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. COMPONENT/ENTRY POINT: $$AGENORAN(IEN) COMPONENT DESCRIPTION: This API returns the AGENT ORANGE EXPOSURE indicator, field (#80002), for this procedure VARIABLES: $$AGENORAN TYPE: Output VARIABLES DESCRIPTION: If this CPT code is treating an agent orange problem VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. COMPONENT/ENTRY POINT: $$IONIRADI(IEN) COMPONENT DESCRIPTION: This API returns the IONIZING RADIATION EXPOSURE indicator, field (#80003), for this procedure VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$IONIRADI TYPE: Output VARIABLES DESCRIPTION: If this CPT code is treating a problem related to an Ionizing Radiation Exposure COMPONENT/ENTRY POINT: $$ENVICONT(IEN) COMPONENT DESCRIPTION: This API returns the ENVIRONMENTAL CONTAMINANTS indicator, field (#80004), for this procedure VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. VARIABLES: $$ENVICONT TYPE: Output VARIABLES DESCRIPTION: If this CPT code is treating a problem related to Environmental Contaminants COMPONENT/ENTRY POINT: $$MILSXTRA(IEN) COMPONENT DESCRIPTION: This API returns the MILITARY SEXUAL TRAUMA indicator, field (#80005), for this procedure VARIABLES: $$MILSXTRA TYPE: Output VARIABLES DESCRIPTION: If this CPT code is treating a problem related to Military Sexual Trauma VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. COMPONENT/ENTRY POINT: $$CANCERHN(IEN) COMPONENT DESCRIPTION: This API returns the HEAD AND/OR NECK CANCER indicator, field (#80006), for this procedure VARIABLES: $$CANCERHN TYPE: Output VARIABLES DESCRIPTION: If this CPT code is treating a problem related to Head/Neck Cancer VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V CPT (#9000010.18) file. NUMBER: 3036 IA #: 3036 FILE NUMBER: 771 GLOBAL ROOT: HL(771, DATE CREATED: FEB 15, 2000 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: HL7 APPLICATION PARAMETER LOOKUP ID: HL(771, GLOBAL REFERENCE: HL(771,D0,0)=>Name (#.01) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: This IA will allow MPI/PD to lookup an entry in the HL7 APPLICATION PARAMETER (#771) file using DBS FileMan calls. The IA is needed because of the release of two seperate but related patches. DG*5.3*261 exports the ADT/HL7 EVENT REASON (#391.72) file which has a field named HL7 APPLICATION PARAMETER (#.02). This field is a pointer to the HL7 APPLICATION PARAMETER (#771) file. Our data in ADT/HL7 EVENT REASON file is initially exported with the HL7 APPLICATION PARAMETER blank. The HL7 APPLICATION PARAMETER required for this field is being exported in RG*1.0*4. RG*1.0*4 adds the HL7 APPLICATION PARAMETER, and a post-install process adds that data to the ADT/HL7 EVENT REASON file. Our IA will permit our post-install process to lookup the new application with silent FileMan calls and subsequently add that data to the ADT/HL7 EVENT REASON file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30873724 KEYWORDS: HL7 KEYWORDS: APPLICATION SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham NUMBER: 3037 IA #: 3037 FILE NUMBER: 391.72 GLOBAL ROOT: VAT(391.72, DATE CREATED: FEB 15, 2000 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ADT/HL7 EVENT REASON (#391.72) file access ID: VAT(391.72, GLOBAL REFERENCE: VAT(391.72, FIELD NUMBER: .02 FIELD NAME: HL7 APPLICATION PARAMETER LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This field, HL7 APPLICATION PARAMETER, is a pointer to the HL7 APPLICATION PARAMETER (#771) file. FIELD NUMBER: .01 FIELD NAME: EVENT REASON CODE LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: This IA allows the subscribing package to access the ADT/HL7 EVENT REASON (#391.72) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30873809 KEYWORDS: HL7 KEYWORDS: EVENT REASON SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham NUMBER: 3038 IA #: 3038 DATE CREATED: FEB 22, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAAVHF NAME: DBIA3035-B ORIGINAL NUMBER: 3035 ID: PXAAVHF GENERAL DESCRIPTION: The following is a description of the available APIs for the V HEALTH FACTORS (#9000010.23) file. The V HEALTH FACTORS (#9000010.23) file is used for storing patient health factors identified during a visit. STATUS: Active DURATION: Next Version MAIL MESSAGE: 30948205 GOOD ONLY FOR VERSION: 1.0 KEYWORDS: PXAA COMPONENT/ENTRY POINT: $$GETIENS(VSITIEN,ARRAY) COMPONENT DESCRIPTION: Use this API to retrieve all Internal Entry Numbers (IEN) from the V HEALTH FACTORS (#9000010.23) file associated with the given visit IEN, VSITIEN. VARIABLES: VSITIEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a given patient visit. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) This array variable is populated by the API with the Internal Entry Numbers of records found to be associated in the V HEALTH FACTORS (#9000010.23) file with the patient visit IEN, VSITIEN. VARIABLES: $$GETIENS TYPE: Output VARIABLES DESCRIPTION: If the value returned is equal to 0, no record was found in the V HEALTH FACTORS (#9000010.23) file for the given visit IEN. If the value returned is equal to 1, one or more records were found in the V HEALTH FACTORS (#9000010.23) file. COMPONENT/ENTRY POINT: $$LOADFLDS(IEN,ARRAY) COMPONENT DESCRIPTION: This API loads all the field values for a given V HEALTH FACTORS (#9000010.23) record. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V HEALTH FACTORS (#9000010.23) file. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) All the field values of the V HEALTH FACTORS (#9000010.23) file for the given record IEN such as; Patient Name, Health Factor, Event Date and Time, etc are loaded into this array variable. VARIABLES: $$LOADFLDS TYPE: Output VARIABLES DESCRIPTION: If the value returned is equal to 0, no record was found in the V HEALTH FACTORS (#9000010.23) file for the given IEN. Returns 1 if the API has successfully loaded all the field values into the ARRAY variable. COMPONENT/ENTRY POINT: $$HEALFACT(IEN) COMPONENT DESCRIPTION: This API returns field (#.01) - HEALTH FACTOR, of the V HEALTH FACTORS (#9000010.23) file. A pointer to the Health Factor (#9999999.64) file that most closely represents the patient's health factor status during the encounter for a given health factor category. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V HEALTH FACTORS (#9000010.23) file. VARIABLES: $$HEALFACT TYPE: Output VARIABLES DESCRIPTION: A pointer to the Health Factor (#9999999.64) file. COMPONENT/ENTRY POINT: $$PATINAME(IEN) COMPONENT DESCRIPTION: This API returns field (#.02) - PATIENT NAME, of the V HEALTH FACTORS (#9000010.23) file. A pointer to the PATIENT/IHS (#9000001) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V HEALTH FACTORS (#9000010.23) file. VARIABLES: $$PATINAME TYPE: Output VARIABLES DESCRIPTION: A pointer to the PATIENT/IHS (#9000001) file. COMPONENT/ENTRY POINT: $$VISIT(IEN) COMPONENT DESCRIPTION: This API returns field (#.03) - VISIT, of the V HEALTH FACTORS (#9000010.23) file. A pointer to the VISIT (#9000010) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V HEALTH FACTORS (#9000010.23) file. VARIABLES: $$VISIT TYPE: Output VARIABLES DESCRIPTION: A pointer to the Visit (#9000010) file. COMPONENT/ENTRY POINT: $$LEVESEVE(IEN) COMPONENT DESCRIPTION: This API returns field (#.04) - LEVEL/SEVERITY, of the V HEALTH FACTORS (#9000010.23) file. This field indicates the Level/Severity of the patient's Health Factors identified during the visit. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V HEALTH FACTORS (#9000010.23) file. VARIABLES: $$LEVESEVE TYPE: Output VARIABLES DESCRIPTION: 'M' - Minimal level of severity. 'MO' - Moderate level of severity. 'H' - Heavy/Severe level of severity. COMPONENT/ENTRY POINT: $$EVENTDT(IEN) COMPONENT DESCRIPTION: This API returns field (#1201) - EVENT DATE & TIME, of the V HEALTH FACTORS (#9000010.23) fil. The date and time the health factor was recorded by the provider. Note : This date and time may be different from the visit date and time. For example, for clinic appointment visits, the visit date and time is the date and time of the appointment, not the time the provider performed the clinical event. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V HEALTH FACTORS (#9000010.23) file. VARIABLES: $$EVENTDT TYPE: Output VARIABLES DESCRIPTION: The Date and Time that the procedure took place. COMPONENT/ENTRY POINT: $$ORDEPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1202) - ORDERING PROVIDER, of the V HEALTH FACTORS (#9000010.23) file. A pointer to the NEW PERSON (#200) file identifying the provider who ordered this health factor to be recorded. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V HEALTH FACTORS (#9000010.23) file. VARIABLES: $$ORDEPROV TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200) file identifying the provider who ordered this health factor to be recorded. COMPONENT/ENTRY POINT: $$ENCOPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1204) - ENCOUNTER PROVIDER, of the V HEALTH FACTORS (#9000010.23) file. A pointer to the NEW PERSON (#200) file identifying the provider who recorded the health factor. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V HEALTH FACTORS (#9000010.23) file. VARIABLES: $$ENCOPROV TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200) file identifying the provider who recorded the health factor. COMPONENT/ENTRY POINT: $$EDITED(IEN) COMPONENT DESCRIPTION: This API returns field (#80101) - EDITED FLAG, of the V HEALTH FACTORS (#9000010.23) file. A value indicating if PCE detects that any original health factor data is being edited. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V HEALTH FACTORS (#9000010.23) file. VARIABLES: $$EDITED TYPE: Output VARIABLES DESCRIPTION: Returns '1' indicating if PCE detects that any original data is being edited. COMPONENT/ENTRY POINT: $$AUDITRAI(IEN) COMPONENT DESCRIPTION: This API returns field (#80102) - AUDIT TRAIL, of the V HEALTH FACTORS (#9000010.23) file. This field is populated automatically by the PCE filing logic. The format of the field is as follows: Pointer to PCE data source file_"-"_A for Add or E for Edit_" "_DUZ of the person who entered the data_";". VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V HEALTH FACTORS (#9000010.23) file. VARIABLES: $$AUDITRAI TYPE: Output VARIABLES DESCRIPTION: A Free Text value in the format; Pointer to PCE data source file_"-"_A for Add or E for Edit_" "_DUZ of the person who entered the data_";" COMPONENT/ENTRY POINT: $$COMMENTS(IEN) COMPONENT DESCRIPTION: This API returns field (#81101) - COMMENTS, of the V HEALTH FACTORS (#9000010.23) file. Any comments related to the patient's health factors. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V HEALTH FACTORS (#9000010.23) file. VARIABLES: $$COMMENTS TYPE: Output VARIABLES DESCRIPTION: A Free Text value indicating any comments related to the patient's health factors. COMPONENT/ENTRY POINT: $$VERIFIED(IEN) COMPONENT DESCRIPTION: This API returns field (#81201) - VERIFIED, of the V HEALTH FACTORS (#9000010.23) file. A flag indicating whether the record was Electronically Signed or Verified by the Package. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V HEALTH FACTORS (#9000010.23) file. VARIABLES: $$VERIFIED TYPE: Output VARIABLES DESCRIPTION: 1 - Electronically Signed. 2 - Verified by the Package. COMPONENT/ENTRY POINT: $$PACKAGE(IEN) COMPONENT DESCRIPTION: This API returns field (#81202) - PACKAGE, of the V HEALTH FACTORS (#9000010.23) file. A pointer to the Package (#9.4) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V HEALTH FACTORS (#9000010.23) file. VARIABLES: $$PACKAGE TYPE: Output VARIABLES DESCRIPTION: Pointer to the Package (#9.4) file. COMPONENT/ENTRY POINT: $$DATASRC(IEN) COMPONENT DESCRIPTION: This API returns field (#81203) - DATA SOURCE, of the V HEALTH FACTORS (#9000010.23) file. A pointer to the PCE Data Source (#839.7) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V HEALTH FACTORS (#9000010.23) file. VARIABLES: $$DATASRC TYPE: Output VARIABLES DESCRIPTION: Pointer to the PCE Data Source (#839.7) file. NUMBER: 3039 IA #: 3039 DATE CREATED: FEB 15, 2000 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUSRVL NAME: TIU GET STATUS LIST ID: TIUSRVL GENERAL DESCRIPTION: This API returns the list of allowable signature statuses supported by TIU. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30875266 KEYWORDS: SIGNATURE KEYWORDS: STATUS COMPONENT/ENTRY POINT: STATUS COMPONENT DESCRIPTION: This subroutine may be called with an array, passed by reference, in which the list of statuses will be returned in alphabetical order. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: This array is passed by reference from the calling application as the only actual parameter to the subroutine. As such, it must be declared in the namespace () of the calling application (ref. SAC 2.3.1.10.1). The call from CPRS looks Like this: D STATUS^TIUSRVL(.ORY) and returns the ORY array with the following contents: ORY(2)=8^amended ORY(3)=7^completed ORY(4)=14^deleted ORY(6)=9^purged ORY(7)=15^retracted ORY(9)=6^uncosigned ORY(10)=1^undictated ORY(11)=3^unreleased ORY(12)=5^unsigned ORY(13)=2^untranscribed ORY(14)=4^unverified SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3040 IA #: 3040 GLOBAL ROOT: DD( DATE CREATED: FEB 15, 2000 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Direct set DD node ID: DD( GENERAL DESCRIPTION: Agreement allowing the direct setting of the ^DD(file,0,"ACT") node. VIEWER: WINN,TAMI STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30876059 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING DETAILS: A limited integration agreement which allows the setting of the ^DD(file,0,"ACT") node for the PATIENT file (#2) directly from a post-init in a DG patch. Specifically, S ^DD(2,0,"ACT")="I '$G(DICR),$G(DIC(0))'[""I"" D ^DGSEC" This change will allow DIC lookups where DIC(0) contains "I" to avoid both the LOOK-UP PROGRAM and the POST-SELECTION ACTION defined for the file. NUMBER: 3041 IA #: 3041 FILE NUMBER: 20 GLOBAL ROOT: VA(20 DATE CREATED: FEB 16, 2000 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ACCESS TO FILE 20 NAME COMPONENTS ID: VA(20 GLOBAL REFERENCE: VA(20,D0,0) FIELD NUMBER: .01 FIELD NAME: FILE LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: FIELD LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .03 FIELD NAME: IENS LOCATION: 0;3 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: VA(20,D0,1) FIELD NUMBER: 1 FIELD NAME: FAMILY (LAST) NAME LOCATION: 1;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: 2 FIELD NAME: GIVEN (FIRST) NAME LOCATION: 1;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: 3 FIELD NAME: MIDDLE NAME LOCATION: 1;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: 4 FIELD NAME: PREFIX LOCATION: 1;4 ACCESS: Both R/W w/Fileman FIELD NUMBER: 5 FIELD NAME: SUFFIX LOCATION: 1;5 ACCESS: Both R/W w/Fileman FIELD NUMBER: 6 FIELD NAME: DEGREE LOCATION: 1;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: 7 FIELD NAME: SOURCE NAME FORMAT FLAGS LOCATION: 1;7 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: VA(20,D0,11) FIELD NUMBER: 11 FIELD NAME: NOTES ABOUT NAME LOCATION: 11;1 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: All fields can be accessed/edited using FileMan tools. Each entry in the NAME COMPONENTS file (#20) corresponds to a single source name field in another file. The following three fields in the NAME COMPONENTS file contain information about the source name field. These three fields comprise the Primary Key for the NAME COMPONENTS file. .01 File Number of file that contains source name field .02 Field Number of the field that contains the source name field .03 IENS (Internal Entry Number string) of the record that contains the name to which this entry corresponds. The name field in the source file should have cross-references that keep its value in synchronization with the corresponding entry in the NAME COMPONENTS file. For an example of this, see the .01 field of the NEW PERSON file. The following fields are normally available for editing by end-users. Field # Name 1 FAMILY (LAST) NAME 2 GIVEN (FIRST) NAME 3 MIDDLE NAME 4 PREFIX (ex., MR, MS) 5 SUFFIX (ex., JR, III, ESQ) 6 DEGREE (ex., PHD) (The DEGREE and PREFIX field are not part of the source name field (#.01) of the NEW PERSON file.) Kernel APIs that return the name components are available. When any of the following fields in the NAME COMPONENTS file are edited via FileMan tools: Field # Name .01 FILE .02 FIELD .03 IENS 1 FAMILY (LAST) NAME 2 GIVEN (FIRST) NAME 3 MIDDLE NAME 5 SUFFIX 7 SOURCE NAME FORMAT FLAGS the "ANAME" MUMPS cross-reference automatically updates the corresponding source name field in the source file to reflect the changes. To prevent this cross-reference from firing, you can NEW the variable XUNOTRIG and SET it to 1 before editing the any of the above fields. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34587226 KEYWORDS: NAME COMPONENTS KEYWORDS: 20 KEYWORDS: VA(20 KEYWORDS: XUNOTRIG SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany SUBSCRIBING DETAILS: Used with HEC'S MASTER CLIENT file 300.12 SUBSCRIBING PACKAGE: VISTALINK SECURITY SUBSCRIBING PACKAGE: HEALTHEVET DESKTOP NUMBER: 3042 IA #: 3042 DATE CREATED: FEB 16, 2000 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MCAPI NAME: SINGLE PROCEDURE DISPLAY API ID: MCAPI GENERAL DESCRIPTION: This DBIA authorizes CONSULT/REQUEST TRACKING to call ^MCAPI for the purpose of retrieving a single patient procedure and displaying the selected procedure in the Consult/Request Tracking Package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30899523 COMPONENT/ENTRY POINT: EN(RESULT,FLG) COMPONENT DESCRIPTION: Produces a modified display for a single patient procedure that omits the patient's information from the header. This call is used in conjunction with another call to a medicine routine. $$SINGLE^MCAPI => gets patient related data. VARIABLES: RESULT TYPE: Input VARIABLES DESCRIPTION: (required) = "IEN;ROOT" (e.g. "12;MCAR(691.5," IEN is the file number of the desired patient procedure. ROOT is the global root of the medicine file containing the desired Patient procedure. VARIABLES: FLG TYPE: Input VARIABLES DESCRIPTION: (required) =1 if report is to contain a modified header omitting the patient's information. Any other value in the variable FLG will result in the report containing the patient's information in the header. VARIABLES: REPORT TYPE: Output VARIABLES DESCRIPTION: = Modified display of a single patient procedure. The display is defined by the input variables and is to be displayed in the Consult/Request Tracking Package. COMPONENT/ENTRY POINT: $$SINGLE(RESULT) COMPONENT DESCRIPTION: Allows the retrieval of a single patient procedure. (e.g. S VARIABLE=$$SINGLE(RESULT)) VARIABLES: RESULT TYPE: Input VARIABLES DESCRIPTION: (required) = "IEN;ROOT" (e.g. "12;MCAR(691.5," IEN is the file number of the desired patient procedure. ROOT is the global root of the medicine file containing the desired patient procedure. VARIABLES: VARIABLE TYPE: Output VARIABLES DESCRIPTION: Variable containing a single patient procedure for display by Consult/ Request Tracking. This reference is used as input for the modified patient display. $P(VARIABLE,U,1)=Print Name ...),U,2)=Pointer to Procedure ...),U,3)=Print Line ...),U,4)=Print Routine ...),U,5)=Print Name ...),U,6)=Date/Time of procedure ...),U,7)=Gross Evaluation ...),U,10)=Summary Title ...),U,11)=Procedure ...),U,12)=Pointer to Procedure ...),U,13)=Patient DFN SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: NUMBER: 3043 IA #: 3043 DATE CREATED: FEB 22, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAAVIMM NAME: DBIA3035-C ORIGINAL NUMBER: 3035 ID: PXAAVIMM GENERAL DESCRIPTION: The following is a description of the available APIs for the V IMMUNIZATION (#9000010.11) file. The V IMMUNIZATION (#9000010.11) file is used to store immunizations specific to a particular visit for a particular patient. This file contains one record for each immunization. STATUS: Active DURATION: Next Version MAIL MESSAGE: 30948205 GOOD ONLY FOR VERSION: 1.0 KEYWORDS: PXAA COMPONENT/ENTRY POINT: $$GETIENS(VSITIEN,ARRAY) COMPONENT DESCRIPTION: Use this API to retrieve all Internal Entry Numbers (IEN) from the V IMMUNIZATION (#9000010.11) file associated with the given visit IEN, VSITIEN. VARIABLES: VSITIEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a given patient visit. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) This array variable is populated by the API with the Internal Entry Numbers of records found to be associated in the V IMMUNIZATION (#9000010.11) file with the patient visit IEN. VARIABLES: $$GETIENS TYPE: Output VARIABLES DESCRIPTION: Returns '0' if no records were found in the V IMMUNIZATION (#9000010.11) file for the given visit IEN. Returns '1' if one or more records were found in the V IMMUNIZATION (#9000010.11) file for the given visit IEN. COMPONENT/ENTRY POINT: $$LOADFLDS(IEN,ARRAY) COMPONENT DESCRIPTION: This API loads all the field values for a given record IEN in the V IMMUNIZATION (#9000010.11) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. VARIABLES: $$LOADFLDS TYPE: Output VARIABLES DESCRIPTION: Returns '0' if no records were found in the V IMMUNIZATION (#9000010.11) file for the given IEN. Returns '1' if the API has successfully loaded all the field values into the ARRAY variable. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) All the field values of the V IMMUNIZATION (#9000010.11) file for the given record IEN such as; Patient Name, Immunization, Comments, etc are loaded into this array variable. COMPONENT/ENTRY POINT: $$IMMUNIZA(IEN) COMPONENT DESCRIPTION: This API returns field (#.01) - IMMUNIZATION, of the V IMMUNIZATION (#9000010.11) file. A pointer to the IMMUNIZATION (#9999999.14) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. VARIABLES: $$IMMUNIZA TYPE: Output VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. COMPONENT/ENTRY POINT: $$PATINAME(IEN) COMPONENT DESCRIPTION: This API returns field (#.02) - PATIENT NAME, of the V IMMUNIZATION (#9000010.11) file. A pointer to the PATIENT/IHS (#9000001) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. VARIABLES: $$PATINAME TYPE: Output VARIABLES DESCRIPTION: A pointer to the PATIENT/IHS (#9000001) file. COMPONENT/ENTRY POINT: $$VISIT(IEN) COMPONENT DESCRIPTION: This API returns field (#.03) - VISIT, of the V IMMUNIZATION (#9000010.11) file. A pointer to the VISIT (#9000010) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. VARIABLES: $$VISIT TYPE: Output VARIABLES DESCRIPTION: A pointer to the Visit (#9000010) file indicating the date and time when the immunization was given. COMPONENT/ENTRY POINT: $$SERIES(IEN) COMPONENT DESCRIPTION: This API returns field (#.04) - SERIES, of the V IMMUNIZATION (#9000010.11) file. This field specifies which series of immunization types were given to the patient. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. VARIABLES: $$SERIES TYPE: Output VARIABLES DESCRIPTION: P - Partially Complete, C - Complete, B - Booster, 1 - Series 1, 2 - Series 2, 3 - Series 3, 4 Series 4, 5 - Series 5, 6 - Series 6, 7 - Series 7, 8 -Series 8 COMPONENT/ENTRY POINT: $$REACTION(IEN) COMPONENT DESCRIPTION: This API returns field (#.06) - REACTION, of the V IMMUNIZATION (#9000010.11) file. This field represents the patients reaction to the immunization. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. VARIABLES: $$REACTION TYPE: Output VARIABLES DESCRIPTION: 0 - NONE,1 - FEVER, 2 - IRRITABILITY, 3 - LOCAL REACTION OR SWELLING, 4 - VOMITING, 5 - RASH OR ITCHING, 6 - LETHARGY, 7 - CONVULSIONS, 8 - ARTHRITIS or ARTHRALGIAS, 9 - ANAPHYLAXIS or COLLAPSE, 10 - RESPIRATORY DISTRESS, 11 - OTHER COMPONENT/ENTRY POINT: $$CONTRAIN(IEN) COMPONENT DESCRIPTION: This API returns field (#.07) - CONTRAINDICATED, of the V IMMUNIZATION (#9000010.11) file. Indicates whether the immunization was recorded as contraindicated. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. VARIABLES: $$CONTRAIN TYPE: Output VARIABLES DESCRIPTION: Returns '0' to indicate that the immunization was not recorded as contraindicated. Returns '1' to indicate that the immunization was recorded as contraindicated. COMPONENT/ENTRY POINT: $$REMARKS(IEN) COMPONENT DESCRIPTION: This API returns field (#1101) - REMARKS, of the V IMMUNIZATION (#9000010.11) file. Additional comments or remarks related to the immunization given to the patient. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. VARIABLES: $$REMARKS TYPE: Output VARIABLES DESCRIPTION: Additional comments or remarks related to the immunization given to the patient. COMPONENT/ENTRY POINT: $$EVENTDT(IEN) COMPONENT DESCRIPTION: This API returns field (#1201) - EVENT DATE & TIME, of the V IMMUNIZATION (#9000010.11) file. The date and time the immunization was given. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. VARIABLES: $$EVENTDT TYPE: Output VARIABLES DESCRIPTION: The date and time the immunization was given. COMPONENT/ENTRY POINT: $$ORDEPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1202) - ORDERING PROVIDER, of the V IMMUNIZATION (#9000010.11) file. A pointer to the NEW PERSON (#200) file identifying the provider who ordered this immunization. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. VARIABLES: $$ORDEPROV TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200) file identifying the provider who ordered this immunization. COMPONENT/ENTRY POINT: $$ENCOPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1204) - ENCOUNTER PROVIDER, of the V IMMUNIZATION (#9000010.11) file. A pointer to the NEW PERSON (#200) file identifying the provider who administered the immunization. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. VARIABLES: $$ENCOPROV TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200) file identifying the provider who administered the immunization. COMPONENT/ENTRY POINT: $$EDITFLAG(IEN) COMPONENT DESCRIPTION: This API returns field (#80101) - EDITED FLAG, of the V IMMUNIZATION (#9000010.11) file. This field indicates if PCE detects that any original immunization data is being edited. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. VARIABLES: $$EDITFLAG TYPE: Output VARIABLES DESCRIPTION: Returns 1 if PCE detects that any original immunization data is being edited. COMPONENT/ENTRY POINT: $$AUDITRAI(IEN) COMPONENT DESCRIPTION: This API returns field (#80102) - AUDIT TRAIL, of the V IMMUNIZATION (#9000010.11) file. This field is populated automatically by the PCE filing logic. The format of the field is as follows: Pointer to PCE data source file_"-"_A for Add or E for Edit_" "_DUZ of the person who entered the data_";" VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. VARIABLES: $$AUDITRAI TYPE: Output VARIABLES DESCRIPTION: A Free Text value in the format; Pointer to PCE data source file_"-"_A for Add or E for Edit_" "_DUZ of the person who entered the data_";" COMPONENT/ENTRY POINT: $$COMMENTS(IEN) COMPONENT DESCRIPTION: This API returns field (#81101) - COMMENTS, of the V IMMUNIZATION (#9000010.11) file. Any comments related to the procedure performed. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. VARIABLES: $$COMMENTS TYPE: Output VARIABLES DESCRIPTION: A Free Text value indicating any comments related to the immunization. COMPONENT/ENTRY POINT: $$VERIFIED(IEN) COMPONENT DESCRIPTION: This API returns field (#81201) - VERIFIED, of the V IMMUNIZATION (#9000010.11) file. This field indictaes whether the record was Electronically Signed or Verified by the Package. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. VARIABLES: $$VERIFIED TYPE: Output VARIABLES DESCRIPTION: 1 - Electronically Signed, 2 - Verified by the Package. COMPONENT/ENTRY POINT: $$PACKAGE(IEN) COMPONENT DESCRIPTION: This API returns field (#81202) - PACKAGE, of the V IMMUNIZATION (#9000010.11) file. A pointer to the Package (#9.4) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. VARIABLES: $$PACKAGE TYPE: Output VARIABLES DESCRIPTION: Pointer to the Package (#9.4) file. COMPONENT/ENTRY POINT: $$DATASRC(IEN) COMPONENT DESCRIPTION: This API returns field (#81203) - DATA SOURCE, of the V IMMUNIZATION (#9000010.11) file A pointer to the PCE Data Source (#839.7) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V IMMUNIZATION (#9000010.11) file. VARIABLES: $$DATASRC TYPE: Output VARIABLES DESCRIPTION: Pointer to the PCE Data Source (#839.7) file. NUMBER: 3044 IA #: 3044 DATE CREATED: FEB 22, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAAVMSR NAME: DBIA3035-D ORIGINAL NUMBER: 3035 ID: PXAAVMSR GENERAL DESCRIPTION: The following is a description of the available APIs for the V MEASUREMENT (#9000010.01) file. The V MEASUREMENT (#9000010.01) file is used to store measurements such as; weight, height, blood pressure, etc., taken by a health professional during an outpatient encounter. STATUS: Active MAIL MESSAGE: 30948205 KEYWORDS: PXAA COMPONENT/ENTRY POINT: $$GETIENS(VSITIEN,ARRAY) COMPONENT DESCRIPTION: Use this API to retrieve all Internal Entry Numbers (IEN) from the V MEASUREMENT (#9000010.01) file associated with the given visit IEN, VSITIEN. VARIABLES: VSITIEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a given patient visit. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) This array variable is populated by the API with the Internal Entry Numbers of records found to be associated in the V MEASUREMENT (#9000010.01) file with the patient visit IEN. VARIABLES: $$GETIENS TYPE: Output VARIABLES DESCRIPTION: Returns 0 if no record was found in the V MEASUREMENT (#9000010.01) file for the given visit IEN. Returns 1 if one or more records were found in the V MEASUREMENT (#9000010.01) file for the given visit IEN. COMPONENT/ENTRY POINT: $$LOADFLDS(IEN,ARRAY) COMPONENT DESCRIPTION: This API loads all the field values for a given record IEN in the V MEASUREMENT (#9000010.01) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V MEASUREMENT (#9000010.01) file. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) All the field values of the V MEASUREMENT (#9000010.01) file for the given record IEN such as; weight, height, blood pressure, etc VARIABLES: $$LOADFLDS TYPE: Output VARIABLES DESCRIPTION: Returns 0 if no record was found in the V MEASUREMENT (#9000010.01) file for the given IEN. Returns 1 if the API has successfully loaded all the field values into the ARRAY variable. COMPONENT/ENTRY POINT: $$TYPE(IEN) COMPONENT DESCRIPTION: This API returns field (#.01) - TYPE, of the V MEASUREMENT (#9000010.01) file. A pointer to the MEASUREMENT TYPE (#9999999.07) file which indicates the type of measurement taken on the patient. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V MEASUREMENT (#9000010.01) file. VARIABLES: $$TYPE TYPE: Output VARIABLES DESCRIPTION: A pointer to the MEASUREMENT TYPE (#9999999.07) file. COMPONENT/ENTRY POINT: $$PATINAME(IEN) COMPONENT DESCRIPTION: This API returns field (#.02) - PATIENT NAME, of the V MEASUREMENT (#9000010.01) file. A pointer to the PATIENT/IHS (#9000001) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V MEASUREMENT (#9000010.01) file. VARIABLES: $$PATINAME TYPE: Output VARIABLES DESCRIPTION: A pointer to the PATIENT/IHS (#9000001) file. COMPONENT/ENTRY POINT: $$VISIT(IEN) COMPONENT DESCRIPTION: This API returns field (#.03) - VISIT, of the V MEASUREMENT (#9000010.01) file. A pointer to the VISIT (#9000010) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V MEASUREMENT (#9000010.01) file. VARIABLES: $$VISIT TYPE: Output VARIABLES DESCRIPTION: A pointer to the Visit (#9000010) file indicating the date and time the immunization was given. COMPONENT/ENTRY POINT: $$VALUE(IEN) COMPONENT DESCRIPTION: This API returns field (#.04) - VALUE, of the V MEASUREMENT (#9000010.01) file. This field specifies the value of the measurement taken on the patient. VARIABLES: $$VALUE TYPE: Output VARIABLES DESCRIPTION: The value of the measurement taken on the patient. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V MEASUREMENT (#9000010.01) file. COMPONENT/ENTRY POINT: $$EVENTDT(IEN) COMPONENT DESCRIPTION: This API returns field (#1201) - EVTN DATE & TIME, of the V MEASUREMENT (#9000010.01) file. The date and time the measurement was taken by the provider. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V MEASUREMENT (#9000010.01) file. VARIABLES: $$EVENTDT TYPE: Output VARIABLES DESCRIPTION: The date and time the measurement was taken by the provider. COMPONENT/ENTRY POINT: $$ORDEPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1202) - ORDERING PROVIDER, of the V MEASUREMENT (#9000010.01) file. A pointer to the NEW PERSON (#200) file identifying the provider who ordered the measurement. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V MEASUREMENT (#9000010.01) file. VARIABLES: $$ORDEPROV TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200) file identifying the provider who ordered the measurement to be taken. COMPONENT/ENTRY POINT: $$ENCOPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1204) - ENCOUNTER PROVIDER, of the V MEASUREMENT (#9000010.01) file. A pointer to the NEW PERSON (#200) file identifying the provider who took the measurement. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V MEASUREMENT (#9000010.01) file. VARIABLES: $$ENCOPROV TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200) file identifying the provider who took the measurement. COMPONENT/ENTRY POINT: $$EDITFLAG(IEN) COMPONENT DESCRIPTION: This API returns field (#80101) - EDITED FLAG, of the V MEASUREMENT (#9000010.01) file. This field indicates if PCE detects that any original measurement data is being edited. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V MEASUREMENT (#9000010.01) file. VARIABLES: $$EDITFLAG TYPE: Output VARIABLES DESCRIPTION: Returns 1 if PCE detects that any original measurement data is being edited. COMPONENT/ENTRY POINT: $$DATASRC(IEN) COMPONENT DESCRIPTION: This API returns field (#80102) - DATA SOURCE, of the V MEASUREMENT (#9000010.01) file. A pointer to the PCE Data Source (#839.7) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V MEASUREMENT (#9000010.01) file. VARIABLES: $$DATASRC TYPE: Output VARIABLES DESCRIPTION: Pointer to the PCE Data Source (#839.7) file. COMPONENT/ENTRY POINT: $$COMMENTS(IEN) COMPONENT DESCRIPTION: This API returns field (#81101) - COMMENTS, of the V HEALTH FACTORS (#9000010.23) file. Any comments related to the measurements taken during the encounter. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V MEASUREMENT (#9000010.01) file. VARIABLES: $$COMMENTS TYPE: Output VARIABLES DESCRIPTION: A Free Text value indicating any comments related to the Measurements taken during the encounter. NUMBER: 3045 IA #: 3045 DATE CREATED: FEB 22, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAAVPED NAME: DBIA3035-E ORIGINAL NUMBER: 3035 ID: PXAAVPED GENERAL DESCRIPTION: The following is a description of the available APIs for the V PATIENT ED (#9000010.16) file. The V PATIENT ED (#9000010.16) file is used to store stores the patient education given to a patient or his responsible care given. STATUS: Active DURATION: Next Version MAIL MESSAGE: 30948205 GOOD ONLY FOR VERSION: 1.0 KEYWORDS: PXAA COMPONENT/ENTRY POINT: $$GETIENS(VSITIEN,ARRAY) COMPONENT DESCRIPTION: Use this API to retrieve all Internal Entry Numbers (IEN) from the V PATIENT ED (#9000010.16) file associated with the given visit IEN, VSITIEN. VARIABLES: VSITIEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a given patient visit. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) This array variable is populated by the API with the Internal Entry Numbers of records found to be associated in the V PATIENT ED (#9000010.16) file with the patient visit IEN. VARIABLES: $$GETIENS TYPE: Output VARIABLES DESCRIPTION: Returns 0 if no record was found in the V PATIENT ED (#9000010.16) file for the given visit IEN. Returns 1 if one or more records were found in the V PATIENT ED (#9000010.16) file for the given visit IEN. COMPONENT/ENTRY POINT: $$LOADFLDS(IEN,ARRAY) COMPONENT DESCRIPTION: This API loads all the field values for a given record IEN in the V PATIENT ED (#9000010.16) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PATIENT ED (#9000010.16) file. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) Loads all the field values of the V PATIENT ED (#9000010.16) file for the given record IEN such as; Patient Name, Topic, Level of Understanding. VARIABLES: $$LOADFLDS TYPE: Output VARIABLES DESCRIPTION: Returns 0 if no record was found in the V PATIENT ED (#9000010.16) file for the given patient IEN. Returns 1 if the API has successfully loaded all the field values into the ARRAY variable. COMPONENT/ENTRY POINT: $$TOPIC(IEN) COMPONENT DESCRIPTION: This API returns field (#.01) - TOPIC, of the V PATIENT ED (#9000010.16) file. A pointer to the EDUCATION TOPICS (#9999999.09) file indicating the education given to the patient. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PATIENT ED (#9000010.16) file. VARIABLES: $$TOPIC TYPE: Output VARIABLES DESCRIPTION: A pointer to the EDUCATION TOPICS (#9999999.09) file. COMPONENT/ENTRY POINT: $$PATINAME(IEN) COMPONENT DESCRIPTION: This API returns field (#.02) - PATIENT NAME, of the V PATIENT ED (#9000010.16) file. A pointer to the PATIENT/IHS (#9000001) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PATIENT ED (#9000010.16) file. VARIABLES: $$PATINAME TYPE: Output VARIABLES DESCRIPTION: A pointer to the PATIENT/IHS (#9000001) file. COMPONENT/ENTRY POINT: $$VISIT(IEN) COMPONENT DESCRIPTION: This API returns field (#.03) - VISIT, of the V PATIENT ED (#9000010.16) file. A pointer to the VISIT (#9000010) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PATIENT ED (#9000010.16) file. VARIABLES: $$VISIT TYPE: Output VARIABLES DESCRIPTION: A pointer to the Visit (#9000010) file indicating the date and time when the immunization was given. COMPONENT/ENTRY POINT: $$LEVEOFUN(IEN) COMPONENT DESCRIPTION: This API returns field (#.06) - LEVEL OF UNDERSTANDING, of the V PATIENT ED (#9000010.16) file. A number which best rates the patient's level of understanding of the education given. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PATIENT ED (#9000010.16) file. VARIABLES: $$LEVEOFUN TYPE: Output VARIABLES DESCRIPTION: 1 - POOR, 2 - FAIR, 3 - GOOD, 4 - GROUP-NO ASSESSMENT, 5 - REFUSED. COMPONENT/ENTRY POINT: $$EVENTDT(IEN) COMPONENT DESCRIPTION: This API returns field (#1201) - EVENT DATE & TIME, of the V PATIENT ED (#9000010.16) file. The date and time the patient education was given. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PATIENT ED (#9000010.16) file. VARIABLES: $$EVENTDT TYPE: Output VARIABLES DESCRIPTION: The date and time the patient education was given. COMPONENT/ENTRY POINT: $$ORDEPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1202) - ORDERING PROVIDER, of the V PATIENT ED (#9000010.16) file. A pointer to the NEW PERSON (#200) file identifying the provider who ordered the patient education. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PATIENT ED (#9000010.16) file. VARIABLES: $$ORDEPROV TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200) file identifying the provider who ordered the patient education. COMPONENT/ENTRY POINT: $$ENCOPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1204) - ENCOUNTER PROVIDER, of the V PATIENT ED (#9000010.16) file. A pointer to the NEW PERSON (#200) file identifying the provider who gave the patient education. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PATIENT ED (#9000010.16) file. VARIABLES: $$ENCOPROV TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200) file identifying the provider who gave the patient education. COMPONENT/ENTRY POINT: $$EDITFLAG(IEN) COMPONENT DESCRIPTION: This API returns field (#80101) - EDITED FLAG, of the V PATIENT ED (#9000010.16) file. This field indicates if PCE detects that any original exam data is being edited. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PATIENT ED (#9000010.16) file. VARIABLES: $$EDITFLAG TYPE: Output VARIABLES DESCRIPTION: Returns 1 if PCE detects that any original exam data is being edited. COMPONENT/ENTRY POINT: $$AUDITRAI(IEN) COMPONENT DESCRIPTION: This API returns field (#80102) - AUDIT TRAIL, of the V PATIENT ED (#9000010.16) file. This field is populated automatically by the PCE filing logic. The format of the field is as follows: Pointer to PCE data source file_"-"_A for Add or E for Edit _" "_DUZ of the person who entered the data_";" VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PATIENT ED (#9000010.16) file. VARIABLES: $$AUDITRAI TYPE: Output VARIABLES DESCRIPTION: A Free Text value in the format; Pointer to PCE data source file_"-"_A for Add or E for Edit_" "_DUZ of the person who entered the data_";" COMPONENT/ENTRY POINT: $$COMMENTS(IEN) COMPONENT DESCRIPTION: This API returns field (#81101) - COMMENTS, of the V PATIENT ED (#9000010.16) file. Any comments related to the patient's education. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PATIENT ED (#9000010.16) file. VARIABLES: $$COMMENTS TYPE: Output VARIABLES DESCRIPTION: A Free Text value indicating any comments related to the patient's education. COMPONENT/ENTRY POINT: $$VERIFIED(IEN) COMPONENT DESCRIPTION: This API returns field (#81201) - VERIFIED, of the V PATIENT ED (#9000010.16) file. This field flag indicates whether the record was Electronically Signed or Verified by the Package. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PATIENT ED (#9000010.16) file. VARIABLES: $$VERIFIED TYPE: Output VARIABLES DESCRIPTION: 1 - Electronically Signed, 2 - Verified by the Package. COMPONENT/ENTRY POINT: $$PACKAGE(IEN) COMPONENT DESCRIPTION: This API returns field (#81202) - PACKAGE, of the V PATIENT ED (#9000010.16) file. A pointer to the Package (#9.4) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PATIENT ED (#9000010.16) file. VARIABLES: $$PACKAGE TYPE: Output VARIABLES DESCRIPTION: Pointer to the Package (#9.4) file. COMPONENT/ENTRY POINT: $$DATASRC(IEN) COMPONENT DESCRIPTION: This API returns field (#81203) - DATA SOURCE, of the V PATIENT ED (#9000010.16) file. A pointer to the PCE Data Source (#839.7) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PATIENT ED (#9000010.16) file. VARIABLES: $$DATASRC TYPE: Output VARIABLES DESCRIPTION: Pointer to the PCE Data Source (#839.7) file. NUMBER: 3046 IA #: 3046 DATE CREATED: FEB 22, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAAVPOV NAME: DBIA3035-F ORIGINAL NUMBER: 3035 ID: PXAAVPOV GENERAL DESCRIPTION: The following is a description of the available APIs for the V POV (#9000010.07) file. The V POV (#9000010.07) file is used to store clinical data related to the "purpose of visit" or "problem of visit", (POV). STATUS: Active DURATION: Next Version MAIL MESSAGE: 30948205 GOOD ONLY FOR VERSION: 1.0 KEYWORDS: PXAA COMPONENT/ENTRY POINT: $$GETIENS(VSITIEN,ARRAY) COMPONENT DESCRIPTION: Use this API to retrieve all Internal Entry Numbers (IEN) from the V POV (#9000010.07) file associated with the given visit IEN, VSITIEN. VARIABLES: VSITIEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a given patient visit. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) This array variable is populated by the API with the Internal Entry Numbers of records found to be associated in the V POV (#9000010.07) file with the patient visit IEN. VARIABLES: $$GETIENS TYPE: Output VARIABLES DESCRIPTION: Returns 0 if no record was found in the V POV (#9000010.07) file for the given visit IEN. Returns 1 if one or more records were found in the V POV (#9000010.07) file for the given visit IEN. COMPONENT/ENTRY POINT: $$LOADFLDS(IEN,ARRAY) COMPONENT DESCRIPTION: This API loads all the field values for a given record IEN in the V POV (#9000010.07) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) All the field values of the V POV (#9000010.07) file for the given record IEN such as; Patient Name Provider Narrative, Modifier, etc VARIABLES: $$LOADFLDS TYPE: Output VARIABLES DESCRIPTION: Returns 0 if no record was found in the V POV (#9000010.07) file for the given patient IEN. Returns 1 if the API has successfully loaded all the field values into the ARRAY variable. COMPONENT/ENTRY POINT: $$POV(IEN) COMPONENT DESCRIPTION: This API returns field (#.01) - PURPOSE OF VISIT, of the V POV (#9000010.07) file. A pointer to the ICD DIAGNOSIS (#80) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$POV TYPE: Output VARIABLES DESCRIPTION: A pointer to the ICD DIAGNOSIS (#80) file which indicates the ICD Diagnosis code or text for the problem treated at the encounter. COMPONENT/ENTRY POINT: $$PATINAME(IEN) COMPONENT DESCRIPTION: This API returns field (#.02) - PATIENT NAME, of the V POV (#9000010.07) file. A pointer to the PATIENT/IHS (#9000001) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$PATINAME TYPE: Output VARIABLES DESCRIPTION: A pointer to the PATIENT/IHS (#9000001) file. COMPONENT/ENTRY POINT: $$VISIT(IEN) COMPONENT DESCRIPTION: This API returns field (#.03) - VISIT, of the V POV (#9000010.07) file. A pointer to the VISIT (#9000010) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$VISIT TYPE: Output VARIABLES DESCRIPTION: A pointer to the Visit (#9000010) file. COMPONENT/ENTRY POINT: $$PROVNARR(IEN) COMPONENT DESCRIPTION: This API returns field (#.04) - PROVIDER NARRATIVE, of the V POV (#9000010.07) file. A pointer to the PROVIDER NARRATIVE (#9999999.27) file indicating the providers text describing the diagnosis that was treated at the visit. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$PROVNARR TYPE: Output VARIABLES DESCRIPTION: A pointer to the PROVIDER NARRATIVE (#9999999.27) file. COMPONENT/ENTRY POINT: $$MODIFIER(IEN) COMPONENT DESCRIPTION: This API returns field (#.06) - MODIFIER, of the V POV (#9000010.07) file. This field indicates how the provider may modify the diagnosis or problem treated to reflect the status of the diagnosis as of this visit. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$MODIFIER TYPE: Output VARIABLES DESCRIPTION: 'C' - CONSIDER, 'D' - DOUBTFUL, 'F' - FOLLOW UP, 'M' - MAYBE , POSSIBLE, PERHAPS, 'O' - RULE OUT, 'P' - PROBABLE, 'R' - RESOLVED, 'S' - SUSPECT, SUSPICIOUS, 'T' - STATUS POST COMPONENT/ENTRY POINT: $$PRIMSECO(IEN) COMPONENT DESCRIPTION: This API returns field (#.12) - PRIMARY/SECONDARY, of the V POV (#9000010.07) file. This field represents the clinically pertinent ranking of problems treated. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$PRIMSECO TYPE: Output VARIABLES DESCRIPTION: 'P' - PRIMARY, 'S' - SECONDARY COMPONENT/ENTRY POINT: $$DATEOFIN(IEN) COMPONENT DESCRIPTION: This API returns field (#.13) - DATE OF INJURY, of the V POV (#9000010.07) file. The date the injury occurred for the problem being treated. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$DATEOFIN TYPE: Output VARIABLES DESCRIPTION: The date the injury occurred for the problem being treated. COMPONENT/ENTRY POINT: $$CLINTERM(IEN) COMPONENT DESCRIPTION: This API returns field (#.15) - CLINICAL TERM of the V POV (#9000010.07) file. A pointer to the EXPRESSIONS (#757.01) file which indicates the field in the clinical lexicon term which most closely represents the provider narrative of the problem treated. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$CLINTERM TYPE: Output VARIABLES DESCRIPTION: A pointer to the EXPRESSIONS (#757.01) file. COMPONENT/ENTRY POINT: $$PROLISEN(IEN) COMPONENT DESCRIPTION: This API returns field (#.16) - PROBLEM LIST ENTRY, of the V POV (#9000010.07) file. A pointer to the PROBLEM (#9000011) file which identifies the Problem List Entry related to the problem treated at the visit. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$PROLISEN TYPE: Output VARIABLES DESCRIPTION: A pointer to the PROBLEM (#9000011) file. COMPONENT/ENTRY POINT: $$EVENTDT(IEN) COMPONENT DESCRIPTION: This API returns field (#1201) - EVENT DATE AND TIME, of the V POV (#9000010.07) file. The date and time the problem was treated. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$EVENTDT TYPE: Output VARIABLES DESCRIPTION: The date and time the problem was treated. COMPONENT/ENTRY POINT: $$ORDEPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1202) - ORDERING PROVIDER, of the V POV (#9000010.07) file. A pointer to the NEW PERSON (#200) file identifying the provider who ordered the problem to be treated. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$ORDEPROV TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200) file identifying the provider who ordered the problem to be treated. COMPONENT/ENTRY POINT: $$ENCOPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1204) - ENCOUNTER PROVIDER, of the V POV (#9000010.07) file. A pointer to the NEW (#200) file identifying the provider who treated the problem. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$ENCOPROV TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200) file identifying the provider who treated the problem. COMPONENT/ENTRY POINT: $$SERVCONN(IEN) COMPONENT DESCRIPTION: This API returns field (#80001) - SERVICE CONNECTED, of the V POV (#9000010.07) file. This field indicates whether the problem treated was service connected. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$SERVCONN TYPE: Output VARIABLES DESCRIPTION: 1 - YES, 0 - NO COMPONENT/ENTRY POINT: $$AGEORAEX(IEN) COMPONENT DESCRIPTION: This API returns field (#80002) - AGENT ORANGE EXPOSURE, of the V POV (#9000010.07) file. This field indicates if the problem treated is related to Agent Orange exposure. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$AGEORAEX TYPE: Output VARIABLES DESCRIPTION: 1 - YES, 0 - NO COMPONENT/ENTRY POINT: $$IONRADEX(IEN) COMPONENT DESCRIPTION: This API returns field (#80003) - IONIZING RADIATION EXPOSURE, of the V POV (#9000010.07) file. This field indicates if the problem treated is related to Ionizing Radiation exposure. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$IONRADEX TYPE: Output VARIABLES DESCRIPTION: 1 - YES, 0 - NO COMPONENT/ENTRY POINT: $$PERGULEX(IEN) COMPONENT DESCRIPTION: This API returns field (#80003) - PERSIAN GULF EXPOSURE, of the V POV (#9000010.07) file. This field indicates if the problem treated is related to Persian Gulf exposure. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$PERGULEX TYPE: Output VARIABLES DESCRIPTION: 1 - YES, 0 - NO COMPONENT/ENTRY POINT: $$EDITFLAG(IEN) COMPONENT DESCRIPTION: This API returns field (#80101) - EDITED FLAG, of the V POV (#9000010.07) file. This field indicates if PCE detects that any original exam data is being edited. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$EDITFLAG TYPE: Output VARIABLES DESCRIPTION: Returns 1 if PCE detects that any original exam data is being edited. COMPONENT/ENTRY POINT: $$AUDITRAI(IEN) COMPONENT DESCRIPTION: This API returns field (#80102) - AUDIT TRAIL, of the V POV (#9000010.07) file. This field is populated automatically by the PCE filing logic. The format of the field is as follows: Pointer to PCE data source file_"-"_A for Add or E for Edit_" "_DUZ of the person who entered the data_";" VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$AUDITRAI TYPE: Output VARIABLES DESCRIPTION: A Free Text value in the format; Pointer to PCE data source file_"-"_A for Add or E for Edit_" "_DUZ of the person who entered the data_";" COMPONENT/ENTRY POINT: $$PRONARCA(IEN) COMPONENT DESCRIPTION: This API returns field (#80201) - PROVIDER NARRATIVE CATEGORY, of the V POV (#9000010.07) file. A pointer to the PROVIDER NARRATIVE (#9999999.27) file indicating the category narrative related to the problem treated. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$PRONARCA TYPE: Output VARIABLES DESCRIPTION: A pointer to the PROVIDER NARRATIVE (#9999999.27) file. COMPONENT/ENTRY POINT: $$COMMENTS(IEN) COMPONENT DESCRIPTION: This API returns field (#81101) - COMMENTS, of the V POV (#9000010.07) file. Any comments related to the purpose of visit. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$COMMENTS TYPE: Output VARIABLES DESCRIPTION: A Free Text value indicating any comments related to the purpose of visit. COMPONENT/ENTRY POINT: $$VERIFIED(IEN) COMPONENT DESCRIPTION: This API returns field (#81201) - VERIFIED, of the V POV (#9000010.07) file. This field indicates whether the record was Electronically Signed or Verified by the Package. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$VERIFIED TYPE: Output VARIABLES DESCRIPTION: 1 - Electronically Signed, 2 - Verified by the Package. COMPONENT/ENTRY POINT: $$PACKAGE(IEN) COMPONENT DESCRIPTION: This API returns field (#81202) - PACKAGE, of the V POV (#9000010.07) file. A pointer to the Package (#9.4) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$PACKAGE TYPE: Output VARIABLES DESCRIPTION: Pointer to the Package (#9.4) file. COMPONENT/ENTRY POINT: $$DATASRC(IEN) COMPONENT DESCRIPTION: This API returns field (#81203) - DATA SOURCE, of the V POV (#9000010.07) file. A pointer to the PCE Data Source (#839.7) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V POV (#9000010.07) file. VARIABLES: $$DATASRC TYPE: Output VARIABLES DESCRIPTION: Pointer to the PCE Data Source (#839.7) file. NUMBER: 3047 IA #: 3047 DATE CREATED: FEB 22, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAAVPRV NAME: DBIA3035-G ORIGINAL NUMBER: 3035 ID: PXAAVPRV GENERAL DESCRIPTION: The following is a description of the available APIs for the V PROVIDER (#9000010.06) file. This file, along with a Purpose of Visit (POV), is required for each patient encounter at a facility. STATUS: Active DURATION: Next Version MAIL MESSAGE: 30948205 GOOD ONLY FOR VERSION: 1.0 KEYWORDS: PXAA COMPONENT/ENTRY POINT: $$GETIENS(VSITIEN,ARRAY) COMPONENT DESCRIPTION: Use this API to retrieve all Internal Entry Numbers (IEN) from the V PROVIDER (#9000010.06) file associated with the given visit IEN, VSITIEN. VARIABLES: VSITIEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a given patient visit. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) This array variable is populated by the API with the Internal Entry Numbers of records found to be associated in the V PROVIDER (#9000010.06) file with the patient visit IEN. VARIABLES: $$GETIENS TYPE: Output VARIABLES DESCRIPTION: Returns 0 if no record was found in the V PROVIDER (#9000010.06) file for the given visit IEN. Returns 1 if one or more records were found in the V PROVIDER (#9000010.06) file for the given visit IEN. COMPONENT/ENTRY POINT: $$LOADFLDS(IEN,ARRAY) COMPONENT DESCRIPTION: This API loads all the field values for a given record IEN in the V PROVIDER (#9000010.06) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PROVIDER (#9000010.06) file. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) All the field values of the V PROVIDER (#9000010.06) file for the given record IEN such as; Patient Name, Provider Narrative, Modifier, etc VARIABLES: $$LOADFLDS TYPE: Output VARIABLES DESCRIPTION: Returns 0 if no record was found in the V PROVIDER (#9000010.06) file for the given patient IEN. Returns 1 if the API has successfully loaded all the field values into the ARRAY variable. COMPONENT/ENTRY POINT: $$PROVIDER(IEN) COMPONENT DESCRIPTION: This API returns field (#.01) - PROVIDER, of the V PROVIDER (#9000010.06) file. A pointer to the NEW PERSON (#200) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PROVIDER (#9000010.06) file. VARIABLES: $$PROVIDER TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200) file. COMPONENT/ENTRY POINT: $$PATINAME(IEN) COMPONENT DESCRIPTION: This API returns field (#.02) - PATIENT NAME, of the V PROVIDER (#9000010.06) file. A pointer to the PATIENT/IHS (#9000001) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PROVIDER (#9000010.06) file. VARIABLES: $$PATINAME TYPE: Output VARIABLES DESCRIPTION: A pointer to the PATIENT/IHS (#9000001) file. COMPONENT/ENTRY POINT: $$VISIT(IEN) COMPONENT DESCRIPTION: This API returns field (#.03) - VISIT, of the V PROVIDER (#9000010.06) file. A pointer to the VISIT (#9000010) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PROVIDER (#9000010.06) file. VARIABLES: $$VISIT TYPE: Output VARIABLES DESCRIPTION: A pointer to the Visit (#9000010) file indicating the date and time when the immunization was given. COMPONENT/ENTRY POINT: $$PRIMSECO(IEN) COMPONENT DESCRIPTION: This API returns field (#.04) - PRIMARY/SECONDARY, of the V PROVIDER (#9000010.06) file. This field indicates that the provider was the primary or secondary care giver for the encounter. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PROVIDER (#9000010.06) file. VARIABLES: $$PRIMSECO TYPE: Output VARIABLES DESCRIPTION: Returns 'P' - PRIMARY or 'S' - SECONDARY COMPONENT/ENTRY POINT: $$OPERATTE(IEN) COMPONENT DESCRIPTION: This API returns field (#.05) - OPERATING/ATTENDING, of the V PROVIDER (#9000010.06) file. This field indicates whether the provider was Operating or Attending. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PROVIDER (#9000010.06) file. VARIABLES: $$OPERATTE TYPE: Output VARIABLES DESCRIPTION: Returns 'A' - ATTENDING or 'O' - OPERATING. COMPONENT/ENTRY POINT: $$PERSCLAS(IEN) COMPONENT DESCRIPTION: This API returns field (#.06) - PERSON CLASS, of the V PROVIDER (#9000010.06) file. This field indicates class of the provider at the time of the encounter and is a pointer to the PERSON CLASS (#8932.1) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PROVIDER (#9000010.06) file. VARIABLES: $$PERSCLAS TYPE: Output VARIABLES DESCRIPTION: A pointer to the PERSON CLASS (#8932.1) file. COMPONENT/ENTRY POINT: $$EVENTDT(IEN) COMPONENT DESCRIPTION: This API returns field (#1201) - EVENT DATE AND TIME, of the V PROVIDER (#9000010.06) file. The date and time the provider had the encounter with the patient. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PROVIDER (#9000010.06) file. VARIABLES: $$EVENTDT TYPE: Output VARIABLES DESCRIPTION: The date and time the provider had the encounter with the patient. COMPONENT/ENTRY POINT: $$EDITFLAG(IEN) COMPONENT DESCRIPTION: This API returns field (#80101) - EDITED FLAG, of the V PROVIDER (#9000010.06) file. This field indicates if PCE detects that any original provider data is being edited. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PROVIDER (#9000010.06) file. VARIABLES: $$EDITFLAG TYPE: Output VARIABLES DESCRIPTION: Returns 1 if PCE detects that any original provider data is being edited. COMPONENT/ENTRY POINT: $$AUDITRAI(IEN) COMPONENT DESCRIPTION: This API returns field (#80102) - AUDIT TRAIL, of the V PROVIDER (#9000010.06) file. This field is populated automatically by the PCE filing logic. The format of the field is as follows: Pointer to PCE data source file_"-"_A for Add or E for Edit_" " _DUZ of the person who entered the data_";" VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PROVIDER (#9000010.06) file. VARIABLES: $$AUDITRAI TYPE: Output VARIABLES DESCRIPTION: A Free Text value in the format; Pointer to PCE data source file_"-"_A for Add or E for Edit_" "_DUZ of the person who entered the data_";" COMPONENT/ENTRY POINT: $$COMMENTS(IEN) COMPONENT DESCRIPTION: This API returns field (#81101) - COMMENTS, of the V PROVIDER (#9000010.06) file. Any comments related to the patient's provider. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PROVIDER (#9000010.06) file. VARIABLES: $$COMMENTS TYPE: Output VARIABLES DESCRIPTION: A Free Text value indicating any comments related to the patient's provider. COMPONENT/ENTRY POINT: $$VERIFIED(IEN) COMPONENT DESCRIPTION: This API returns field (#81201) - VERIFIED, of the V PROVIDER (#9000010.06) file. This field indicates whether the record was Electronically Signed or Verified by the Package. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PROVIDER (#9000010.06) file. VARIABLES: $$VERIFIED TYPE: Output VARIABLES DESCRIPTION: Returns 1 - Electronically Signed or 2 - Verified by the Package. COMPONENT/ENTRY POINT: $$PACKAGE(IEN) COMPONENT DESCRIPTION: This API returns field (#81202) - PACKAGE, of the V PROVIDER (#9000010.06) file. A pointer to the Package (#9.4) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PROVIDER (#9000010.06) file. VARIABLES: $$PACKAGE TYPE: Output VARIABLES DESCRIPTION: Pointer to the Package (#9.4) file. COMPONENT/ENTRY POINT: $$DATASRC(IEN) COMPONENT DESCRIPTION: This API returns field (#81203) - DATA SOURCE, of the V PROVIDER (#9000010.06) file. A pointer to the PCE Data Source (#839.7) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V PROVIDER (#9000010.06) file. VARIABLES: $$DATASRC TYPE: Output VARIABLES DESCRIPTION: Pointer to the PCE Data Source (#839.7) file. NUMBER: 3048 IA #: 3048 DATE CREATED: FEB 22, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAAVSIT NAME: DBIA3035-H ORIGINAL NUMBER: 3035 ID: PXAAVSIT GENERAL DESCRIPTION: The following is a description of the available APIs for the VISIT (#9000010) file. The VISIT (#9000010) file contains a record of all patient visits at health care facilities or by health care providers, including direct outpatient and clinic visits, as well as inpatient encounters with providers of care. STATUS: Active DURATION: Next Version MAIL MESSAGE: 30948205 GOOD ONLY FOR VERSION: 1.0 KEYWORDS: PXAA COMPONENT/ENTRY POINT: $$LOADFLDS(IEN,ARRAY) COMPONENT DESCRIPTION: This API loads all the field values for a given record IEN in the VISIT (#9000010) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) All the field values of the VISIT (#9000010) file for the given record IEN such as; Patient Name, Provider Narrative, Modifier, etc. VARIABLES: $$LOADFLDS TYPE: Output VARIABLES DESCRIPTION: Returns 0 if no record was found in the VISIT (#9000010) file for the given patient IEN. Returns 1 if the API has successfully loaded all the field values into the ARRAY variable. COMPONENT/ENTRY POINT: $$VISADDAT(IEN) COMPONENT DESCRIPTION: This API returns field (#.01) - VISIT/ADMIT DATE AND TIME, of the VISIT (#9000010) file. The date and time of the visit. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$VISADDAT TYPE: Output VARIABLES DESCRIPTION: The date and time of the visit. COMPONENT/ENTRY POINT: $$DATVISCR(IEN) COMPONENT DESCRIPTION: This API returns field (#.02) - DATE VISIT CREATED, of the VISIT (#9000010) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$DATVISCR TYPE: Output VARIABLES DESCRIPTION: The date and time of the visit was created. COMPONENT/ENTRY POINT: $$TYPE(IEN) COMPONENT DESCRIPTION: This API returns field (#.03) - VISIT TYPE, of the VISIT (#9000010) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$TYPE TYPE: Output VARIABLES DESCRIPTION: Returns; 'I' - HIS, 'C' - CONTRACT, 'T' - TRIBAL, 'O' - OTHER, '6' - 638 PROGRAM, 'V' - VA COMPONENT/ENTRY POINT: $$PATINAME(IEN) COMPONENT DESCRIPTION: This API returns field (#.05) - PATIENT NAME, of the VISIT (#9000010) file. A pointer to the PATIENT/IHS (#9000001) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$PATINAME TYPE: Output VARIABLES DESCRIPTION: A pointer to the PATIENT/IHS (#9000001) file. COMPONENT/ENTRY POINT: $$LOCOFENC(IEN) COMPONENT DESCRIPTION: This API returns field (#.06) - LOCATION OF ENCOUNTER, of the VISIT (#9000010) file. A pointer to the LOCATION (#9999999.06) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$LOCOFENC TYPE: Output VARIABLES DESCRIPTION: A pointer to the LOCATION (#9999999.06) file. COMPONENT/ENTRY POINT: $$SERVCATE(IEN) COMPONENT DESCRIPTION: This API returns field (#.07) - SERVICE CATEGORY, of the VISIT (#9000010) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$SERVCATE TYPE: Output VARIABLES DESCRIPTION: Returns; 'A' - AMBULATORY, 'H' - HOSPITALIZATION, 'I' - IN HOSPITAL, 'C' - CHART REVIEW, 'T' - TELECOMMUNICATIONS, 'N' - NOT FOUND, 'S' - DAY SURGERY, 'O' - OBSERVATION, 'E' - EVENT (HISTORICAL), 'R' - NURSING HOME, 'D' - DAILY HOSPITALIZATION DATA, 'X' - ANCILLARY PACKAGE DAILY DATA COMPONENT/ENTRY POINT: $$DSSID(IEN) COMPONENT DESCRIPTION: This API returns field (#.08) - DSS ID, of the VISIT (#9000010) file. A pointer to the CLINIC STOP (#40.7) file and indicates the organized clinic in which this visit took place. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$DSSID TYPE: Output VARIABLES DESCRIPTION: A pointer to the CLINIC STOP (#40.7) file. COMPONENT/ENTRY POINT: $$DEPENTCO(IEN) COMPONENT DESCRIPTION: This API returns field (#.09) - DEPENDENT ENTRY COUNT, of the VISIT (#9000010) file. A number representing how many "V" file entries are pointing to this visit. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$DEPENTCO TYPE: Output VARIABLES DESCRIPTION: A number representing how many "V" file entries are pointing to this visit. COMPONENT/ENTRY POINT: $$DELEFLAG(IEN) COMPONENT DESCRIPTION: This API returns field (#.11) - DELETE FLAG, of the VISIT (#9000010) file. Flag set to signify that the visit has been deleted. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$DELEFLAG TYPE: Output VARIABLES DESCRIPTION: Returns; '1' - YES or '0' - NO. COMPONENT/ENTRY POINT: $$PARVISLI(IEN) COMPONENT DESCRIPTION: This API returns field (#.12) - PARENT VISIT LINK, of the VISIT (#9000010) file. A pointer to the VISIT (#9000010) file, the PARENT VISIT LINK field points back to the VISIT file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$PARVISLI TYPE: Output VARIABLES DESCRIPTION: A pointer to the VISIT (#9000010) file. COMPONENT/ENTRY POINT: $$DATLASMO(IEN) COMPONENT DESCRIPTION: This API returns field (#.13) - DATE LAST MODIFIED, of the VISIT (#9000010) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$DATLASMO TYPE: Output VARIABLES DESCRIPTION: Date last modified. COMPONENT/ENTRY POINT: $$CHEOUDAT(IEN) COMPONENT DESCRIPTION: This API returns field (#.18) - CHECK OUT DATE AND TIME, of the VISIT (#9000010) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$CHEOUDAT TYPE: Output VARIABLES DESCRIPTION: Check out date and time. COMPONENT/ENTRY POINT: $$ELIGIBIL(IEN) COMPONENT DESCRIPTION: This API returns field (#.21) - ELIGIBILITY, of the VISIT (#9000010) file. A pointer to the ELIGIBILITY CODE (#8) file which defines the patient's eligibility for this visit. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$ELIGIBIL TYPE: Output VARIABLES DESCRIPTION: A pointer to the ELIGIBILITY CODE (#8) file. COMPONENT/ENTRY POINT: $$HOSPLOCA(IEN) COMPONENT DESCRIPTION: This API returns field (#.22) - HOSPITAL LOCATION, of the VISIT (#9000010) file. A pointer to the HOSPITAL LOCATION (#44) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$HOSPLOCA TYPE: Output VARIABLES DESCRIPTION: A pointer to the HOSPITAL LOCATION (#44) file. COMPONENT/ENTRY POINT: $$CREABYUS(IEN) COMPONENT DESCRIPTION: This API returns field (#.23) - CREATED BY USER, of the VISIT (#9000010) file. A pointer to the NEW PERSON (#200) file, indicating the name of the user who created this visit entry. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$CREABYUS TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200) file. COMPONENT/ENTRY POINT: $$OPTUSTOC(IEN) COMPONENT DESCRIPTION: This API returns field (#.24) - OPTION USED TO CREATE, of the VISIT (#9000010) file. A pointer to the OPTION (#19) file, indicating the option which was used to create the visit. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$OPTUSTOC TYPE: Output VARIABLES DESCRIPTION: A pointer to the OPTION (#19) file. COMPONENT/ENTRY POINT: $$PROTOCOL(IEN) COMPONENT DESCRIPTION: This API returns field (#.25) - PROTOCOL, of the VISIT (#9000010) file. A pointer to the PROTOCOL (#101) file, indicating the protocol which was used to create the visit. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$PROTOCOL TYPE: Output VARIABLES DESCRIPTION: A pointer to the PROTOCOL (#101) file. COMPONENT/ENTRY POINT: $$OUTSLOCA(IEN) COMPONENT DESCRIPTION: This API returns field (#2101) - OUTSIDE LOCATION, of the VISIT (#9000010) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$OUTSLOCA TYPE: Output VARIABLES DESCRIPTION: Free text indicating the location of service. COMPONENT/ENTRY POINT: $$VISITID(IEN) COMPONENT DESCRIPTION: This API returns field (#15001) - VISIT ID, of the VISIT (#9000010) file. A unique visit id and is set by Visit Tracking and cannot be changed. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$VISITID TYPE: Output VARIABLES DESCRIPTION: Visit ID. COMPONENT/ENTRY POINT: $$PATSTINO(IEN) COMPONENT DESCRIPTION: This API returns field (#15002) - PATIENT STATUS IN/OUT, of the VISIT (#9000010) file. An indicator of the patient's status at the time of the visit. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$PATSTINO TYPE: Output VARIABLES DESCRIPTION: Returns; '1' - IN or '0' - OUT. COMPONENT/ENTRY POINT: $$ENCOTYPE(IEN) COMPONENT DESCRIPTION: This API returns field (#15003) - ENCOUNTER TYPE, of the VISIT (#9000010) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$ENCOTYPE TYPE: Output VARIABLES DESCRIPTION: Returns; 'P' - PRIMARY, 'O' - OCCASION OF SERVICE, 'S' - STOP CODE, 'A' - ANCILLARY, 'C' - CREDIT STOP COMPONENT/ENTRY POINT: $$SERVCONN(IEN) COMPONENT DESCRIPTION: This API returns field (#80001) - SERVICE CONNECTED, of the VISIT (#9000010) file. This field indicates whether the problem treated was service connected. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$SERVCONN TYPE: Output VARIABLES DESCRIPTION: Returns; 1 - YES or 0 - NO. COMPONENT/ENTRY POINT: $$AGEORAEX(IEN) COMPONENT DESCRIPTION: This API returns field (#80002) - AGENT ORANGE EXPOSURE, of the VISIT (#9000010) file. This field indicates if the problem treated is related to Agent Orange exposure. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$AGEORAEX TYPE: Output VARIABLES DESCRIPTION: Returns; 1 - YES or 0 - NO. COMPONENT/ENTRY POINT: $$IONRADEX(IEN) COMPONENT DESCRIPTION: This API returns field (#80003) - IONIZING RADIATION EXPOSURE, of the VISIT (#9000010) file. This field indicates if the problem treated is related to Ionizing Radiation Exposure. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$IONRADEX TYPE: Output VARIABLES DESCRIPTION: Returns; 1 - YES or 0 - NO. COMPONENT/ENTRY POINT: $$PERGULEX(IEN) COMPONENT DESCRIPTION: This API returns field (#80003) - PERSIAN GULF EXPOSURE, of the VISIT (#9000010) file. This field indicates if the problem treated is related to Persian Gulf Exposure. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$PERGULEX TYPE: Output VARIABLES DESCRIPTION: Returns; 1 - YES or 0 - NO. COMPONENT/ENTRY POINT: $$COMMENTS(IEN) COMPONENT DESCRIPTION: This API returns field (#81101) - COMMENTS, of the VISIT (#9000010) file. Any comments related to the purpose of visit. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$COMMENTS TYPE: Output VARIABLES DESCRIPTION: A Free Text value indicating any comments related to the purpose of visit. COMPONENT/ENTRY POINT: $$DATASRC(IEN) COMPONENT DESCRIPTION: This API returns field (#81203) - DATA SOURCE, of the VISIT (#9000010) file. A pointer to the PCE Data Source (#839.7) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$DATASRC TYPE: Output VARIABLES DESCRIPTION: Pointer to the PCE Data Source (#839.7) file. COMPONENT/ENTRY POINT: $$PACKAGE(IEN) COMPONENT DESCRIPTION: This API returns field (#81202) - PACKAGE, of the VISIT (#9000010) file. A pointer to the Package (#9.4) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$PACKAGE TYPE: Output VARIABLES DESCRIPTION: Pointer to the Package (#9.4) file. COMPONENT/ENTRY POINT: $$MLTYSXTR(IEN) COMPONENT DESCRIPTION: This API returns field (#80005) - MILITARY SEXUAL TRAUMA, of the VISIT (#9000010) file. This field indicates if the problem treated is related to Military Sexual Trauma. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the VISIT (#9000010) file. VARIABLES: $$MLTYSXTR TYPE: Output VARIABLES DESCRIPTION: Returns; 1 - YES or 0 - NO NUMBER: 3049 IA #: 3049 DATE CREATED: FEB 22, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAAVSK NAME: DBIA3035-I ORIGINAL NUMBER: 3035 ID: PXAAVSK GENERAL DESCRIPTION: The following is a description of the available APIs for the V SKIN TEST (#9000010.12) file. The V SKIN TEST (#9000010.12) file stores record details for each type of skin test given to a patient on a given visit. STATUS: Active DURATION: Next Version MAIL MESSAGE: 30948205 GOOD ONLY FOR VERSION: 1.0 KEYWORDS: PXAA COMPONENT/ENTRY POINT: $$GETIENS(VSITIEN,ARRAY) COMPONENT DESCRIPTION: Use this API to retrieve all Internal Entry Numbers (IEN) from the V SKIN TEST (#9000010.12) file associated with the given visit IEN, VSITIEN. VARIABLES: VSITIEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a given patient visit. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) This array variable is populated by the API with the Internal Entry Numbers of records found to be associated in the V SKIN TEST (#9000010.12) file with the patient visit IEN. VARIABLES: $$GETIENS TYPE: Output VARIABLES DESCRIPTION: Returns 0 if no record was found in the V SKIN TEST (#9000010.12) file for the given visit IEN. Returns 1 if one or more records were found in the V SKIN TEST (#9000010.12) file for the given visit IEN. COMPONENT/ENTRY POINT: $$LOADFLDS(IEN,ARRAY) COMPONENT DESCRIPTION: This API loads all the field values for a given record IEN in the V SKIN TEST (#9000010.12) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V SKIN TEST (#9000010.12) file. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) All the field values of the V SKIN TEST (#9000010.12) file for the given record IEN such as; Patient Name, Skin Test, Readings, etc VARIABLES: $$LOADFLDS TYPE: Output VARIABLES DESCRIPTION: Returns 0 if no record was found in the V SKIN TEST (#9000010.12) file for the given patient IEN. Returns 1 if the API has successfully loaded all the field values into the ARRAY variable. COMPONENT/ENTRY POINT: $$SKINTEST(IEN) COMPONENT DESCRIPTION: This API returns field (#.01) - SKIN TEST, of the V SKIN TEST (#9000010.12) file. A pointer to the SKIN TEST (#9999999.28) file which indicates the type of Skin Test that was given to the patient at the encounter. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V SKIN TEST (#9000010.12) file. VARIABLES: $$SKINTEST TYPE: Output VARIABLES DESCRIPTION: A pointer to the SKIN TEST (#9999999.28) file. COMPONENT/ENTRY POINT: $$PATINAME(IEN) COMPONENT DESCRIPTION: This API returns field (#.02) - PATIENT NAME, of the V SKIN TEST (#9000010.12) file. A pointer to the PATIENT/IHS (#9000001) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V SKIN TEST (#9000010.12) file. VARIABLES: $$PATINAME TYPE: Output VARIABLES DESCRIPTION: A pointer to the PATIENT/IHS (#9000001) file. COMPONENT/ENTRY POINT: $$VISIT(IEN) COMPONENT DESCRIPTION: This API returns field (#.03) - VISIT, of the V SKIN TEST (#9000010.12) file. A pointer to the VISIT (#9000010) file, indicating the date and time when the immunization was given. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V SKIN TEST (#9000010.12) file. VARIABLES: $$VISIT TYPE: Output VARIABLES DESCRIPTION: A pointer to the Visit (#9000010) file. COMPONENT/ENTRY POINT: $$RESULTS(IEN) COMPONENT DESCRIPTION: This API returns field (#.04) - RESULTS, of the V SKIN TEST (#9000010.12) file. A numeric value indicating if the test results were positive, negative, doubtful or no take, if known. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V SKIN TEST (#9000010.12) file. VARIABLES: $$RESULTS TYPE: Output VARIABLES DESCRIPTION: Returns; 'P' - POSITIVE, 'N' - NEGATIVE, 'D' - DOUBTFUL, 'O' - NO TAKE COMPONENT/ENTRY POINT: $$READING(IEN) COMPONENT DESCRIPTION: This API returns field (#.05) - READING, of the V SKIN TEST (#9000010.12) file. A value representing the reading of the skin test. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V SKIN TEST (#9000010.12) file. VARIABLES: $$READING TYPE: Output VARIABLES DESCRIPTION: A numeric value representing the reading of the skin test. COMPONENT/ENTRY POINT: $$DATEREAD(IEN) COMPONENT DESCRIPTION: This API returns field (#.06) - DATE READ, of the V SKIN TEST (#9000010.12) file. The Date of the Reading. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V SKIN TEST (#9000010.12) file. VARIABLES: $$DATEREAD TYPE: Output VARIABLES DESCRIPTION: Date of the Reading. COMPONENT/ENTRY POINT: $$EVENTDT(IEN) COMPONENT DESCRIPTION: This API returns field (#1201) - EVENT DATE AND TIME, of the V SKIN TEST (#9000010.12) file. The date and time the skin test was performed. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V SKIN TEST (#9000010.12) file. VARIABLES: $$EVENTDT TYPE: Output VARIABLES DESCRIPTION: The date and time the skin test was performed. COMPONENT/ENTRY POINT: $$ORDEPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1202) - ORDERING PROVIDER, of the V SKIN TEST (#9000010.12) file. A pointer to the NEW PERSON (#200) file identifying the provider who ordered the skin test. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V SKIN TEST (#9000010.12) file. VARIABLES: $$ORDEPROV TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200) file. COMPONENT/ENTRY POINT: $$ENCOPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1204) - ENCOUNTER PROVIDER, of the V SKIN TEST (#9000010.12) file. A pointer to the NEW (#200) file identifying the provider who performed the skin test. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V SKIN TEST (#9000010.12) file. VARIABLES: $$ENCOPROV TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200) file. COMPONENT/ENTRY POINT: $$EDITFLAG(IEN) COMPONENT DESCRIPTION: This API returns field (#80101) - EDITED FLAG, of the V SKIN TEST (#9000010.12) file. This field indicates if PCE detects that any original skin test data is being edited. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V SKIN TEST (#9000010.12) file. VARIABLES: $$EDITFLAG TYPE: Output VARIABLES DESCRIPTION: Returns 1 if PCE detects that any original skin test data is being edited. COMPONENT/ENTRY POINT: $$AUDITRAI(IEN) COMPONENT DESCRIPTION: This API returns field (#80102) - AUDIT TRAIL, of the V SKIN TEST (#9000010.12) file. This field is populated automatically by the PCE filing logic. The format of the field is as follows: Pointer to PCE data source file_"-"_A for Add or E for Edit_" "_DUZ of the person who entered the data_";" VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V SKIN TEST (#9000010.12) file. VARIABLES: $$AUDITRAI TYPE: Output VARIABLES DESCRIPTION: A Free Text value in the format; Pointer to PCE data source file_"-"_A for Add or E for Edit_" "_DUZ of the person who entered the data_";" COMPONENT/ENTRY POINT: $$COMMENTS(IEN) COMPONENT DESCRIPTION: This API returns field (#81101) - COMMENTS, of the V SKIN TEST (#9000010.12) file. Any comments related to the skin test. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V SKIN TEST (#9000010.12) file. VARIABLES: $$COMMENTS TYPE: Output VARIABLES DESCRIPTION: A Free Text value indicating any comments related to the skin test. COMPONENT/ENTRY POINT: $$VERIFIED(IEN) COMPONENT DESCRIPTION: This API returns field (#81201) - VERIFIED, of the V SKIN TEST (#9000010.12) file. This field indicates whether the record was Electronically Signed or Verified by the Package. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V SKIN TEST (#9000010.12) file. VARIABLES: $$VERIFIED TYPE: Output VARIABLES DESCRIPTION: Returns; 1 - Electronically Signed or 2 - Verified by the Package. COMPONENT/ENTRY POINT: $$PACKAGE(IEN) COMPONENT DESCRIPTION: This API returns field (#81202) - PACKAGE, of the V SKIN TEST (#9000010.12) file. A pointer to the Package (#9.4) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V SKIN TEST (#9000010.12) file. VARIABLES: $$PACKAGE TYPE: Output VARIABLES DESCRIPTION: Pointer to the Package (#9.4) file. COMPONENT/ENTRY POINT: $$DATASRC(IEN) COMPONENT DESCRIPTION: This API returns field (#81203) - DATA SOURCE, of the V SKIN TEST (#9000010.12) file. A pointer to the PCE Data Source (#839.7) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V SKIN TEST (#9000010.12) file. VARIABLES: $$DATASRC TYPE: Output VARIABLES DESCRIPTION: Pointer to the PCE Data Source (#839.7) file. NUMBER: 3050 IA #: 3050 DATE CREATED: FEB 22, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAAVTRT NAME: DBIA3035-J ORIGINAL NUMBER: 3035 ID: PXAAVTRT GENERAL DESCRIPTION: The following is a description of the available APIs for the V TREATMENT (#9000010.15) file. The V TREATMENT (#9000010.15) file stores a record for each treatment provided to a patient on a given patient visit. STATUS: Active DURATION: Next Version MAIL MESSAGE: 30948205 GOOD ONLY FOR VERSION: 1.0 KEYWORDS: PXAA COMPONENT/ENTRY POINT: $$GETIENS(VSITIEN,ARRAY) COMPONENT DESCRIPTION: Use this API to retrieve all Internal Entry Numbers (IEN) from the V TREATMENT (#9000010.15) file associated with the given visit IEN, VSITIEN. VARIABLES: VSITIEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a given patient visit. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) This array variable is populated by the API with the Internal Entry Numbers of records found to be associated in the V TREATMENT (#9000010.15) file with the patient visit IEN. VARIABLES: $$GETIENS TYPE: Output VARIABLES DESCRIPTION: Returns 0 if no record was found in the V TREATMENT (#9000010.15) file for the given visit IEN. Returns 1 if one or more records were found in the V TREATMENT (#9000010.15) file for the given visit IEN. COMPONENT/ENTRY POINT: $$LOADFLDS(IEN,ARRAY) COMPONENT DESCRIPTION: This API loads all the field values for a given record IEN in the V TREATMENT (#9000010.15) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V TREATMENT (#9000010.15) file. VARIABLES: $$LOADFLDS TYPE: Output VARIABLES DESCRIPTION: Returns 0 if no record was found in the V TREATMENT (#9000010.15) file for the given patient IEN. Returns 1 if the API has successfully loaded all the field values into the ARRAY variable. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) All the field values of the V TREATMENT (#9000010.15) file for the given record IEN such as; Patient Name, Provider Narrative, Treatment type, etc. COMPONENT/ENTRY POINT: $$TREATMEN(IEN) COMPONENT DESCRIPTION: This API returns field (#.01) - TREATMENT, of the V TREATMENT (#9000010.15) file. A pointer to the TREATMENT (#9999999.17) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V TREATMENT (#9000010.15) file. VARIABLES: $$TREATMEN TYPE: Output VARIABLES DESCRIPTION: A pointer to the TREATMENT (#9999999.17) file. COMPONENT/ENTRY POINT: $$PATINAME(IEN) COMPONENT DESCRIPTION: This API returns field (#.02) - PATIENT NAME, of the V TREATMENT (#9000010.15) file. A pointer to the PATIENT/IHS (#9000001) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V TREATMENT (#9000010.15) file. VARIABLES: $$PATINAME TYPE: Output VARIABLES DESCRIPTION: A pointer to the PATIENT/IHS (#9000001) file. COMPONENT/ENTRY POINT: $$VISIT(IEN) COMPONENT DESCRIPTION: This API returns field (#.03) - VISIT, of the V TREATMENT (#9000010.15) file. A pointer to the VISIT (#9000010) file indicating the date and time for the encounter when the treatment was given. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V TREATMENT (#9000010.15) file. VARIABLES: $$VISIT TYPE: Output VARIABLES DESCRIPTION: A pointer to the Visit (#9000010) file. COMPONENT/ENTRY POINT: $$HOWMANY(IEN) COMPONENT DESCRIPTION: This API returns field (#.04) - HOW MANY, of the V TREATMENT (#9000010.15) file. A numeric value indicating how many times the treatment was provided. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V TREATMENT (#9000010.15) file. VARIABLES: $$HOWMANY TYPE: Output VARIABLES DESCRIPTION: A numeric value indicating how many times the treatment was administered. COMPONENT/ENTRY POINT: $$PROVNARR(IEN) COMPONENT DESCRIPTION: This API returns field (#.06 - PROVIDER NARRATIVE, of the V TREATMENT (#9000010.15) file. A pointer to the PROVIDER NARRATIVE (#9999999.27) file indicating the provider's preferred text used to represent the treatment provided. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V TREATMENT (#9000010.15) file. VARIABLES: $$PROVNARR TYPE: Output VARIABLES DESCRIPTION: A pointer to the PROVIDER NARRATIVE (#9999999.27) file. COMPONENT/ENTRY POINT: $$EVENTDT(IEN) COMPONENT DESCRIPTION: This API returns field (#1201) - EVENT DATE AND TIME, of the V TREATMENT (#9000010.15) file. Date and time the treatment was provided. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V TREATMENT (#9000010.15) file. VARIABLES: $$EVENTDT TYPE: Output VARIABLES DESCRIPTION: The date and time the treatment was provided. COMPONENT/ENTRY POINT: $$ORDEPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1202) - ORDERING PROVIDER, of the V TREATMENT (#9000010.15) file. A pointer to the NEW PERSON (#200) file identifying the provider who ordered the treatment. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V TREATMENT (#9000010.15) file. VARIABLES: $$ORDEPROV TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200) file. COMPONENT/ENTRY POINT: $$ENCOPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1204) - ENCOUNTER PROVIDER, of the V TREATMENT (#9000010.15) file. A pointer to the NEW (#200) file identifying the provider who gave the treatment. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V TREATMENT (#9000010.15) file. VARIABLES: $$ENCOPROV TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200) file identifying the provider who gave the treatment. COMPONENT/ENTRY POINT: $$EDITFLAG(IEN) COMPONENT DESCRIPTION: This API returns field (#80101) - EDITED FLAG, of the V TREATMENT (#9000010.15) file. This field indicates if PCE detects that any original treatment data is being edited. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V TREATMENT (#9000010.15) file. VARIABLES: $$EDITFLAG TYPE: Output VARIABLES DESCRIPTION: Returns 1 if PCE detects that any original treatment data is being edited. COMPONENT/ENTRY POINT: $$AUDITRAI(IEN) COMPONENT DESCRIPTION: This API returns field (#80102) - AUDIT TRAIL, of the V TREATMENT (#9000010.15) file. This field is populated automatically by the PCE filing logic. The format of the field is as follows: Pointer to PCE data source file_"-"_A for Add or E for Edit _" "_DUZ of the person who entered the data_";" VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V TREATMENT (#9000010.15) file. VARIABLES: $$AUDITRAI TYPE: Output VARIABLES DESCRIPTION: A Free Text value in the format; Pointer to PCE data source file_"-"_A for Add or E for Edit_" "_DUZ of the person who entered the data_";" COMPONENT/ENTRY POINT: $$PRONARCA(IEN) COMPONENT DESCRIPTION: This API returns field (#80201) - PROVIDER NARRATIVE CATEGORY, of the V TREATMENT (#9000010.15) file. A pointer to the PROVIDER NARRATIVE (#9999999.27) file indicating the category narrative related to the treatment. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V TREATMENT (#9000010.15) file. VARIABLES: $$PRONARCA TYPE: Output VARIABLES DESCRIPTION: A pointer to the PROVIDER NARRATIVE (#9999999.27) file. COMPONENT/ENTRY POINT: $$COMMENTS(IEN) COMPONENT DESCRIPTION: This API returns field (#81101) - COMMENTS, of the V TREATMENT (#9000010.15) file. Any comments related to the patient's treatment. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V TREATMENT (#9000010.15) file. VARIABLES: $$COMMENTS TYPE: Output VARIABLES DESCRIPTION: A Free Text value indicating any comments related to the patient's treatment. COMPONENT/ENTRY POINT: $$VERIFIED(IEN) COMPONENT DESCRIPTION: This API returns field (#81201) - VERIFIED, of the V TREATMENT (#9000010.15) file. This field indicates whether the record was Electronically Signed or Verified by the Package. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V TREATMENT (#9000010.15) file. VARIABLES: $$VERIFIED TYPE: Output VARIABLES DESCRIPTION: 1 - Electronically Signed, 2 - Verified by the Package. COMPONENT/ENTRY POINT: $$PACKAGE(IEN) COMPONENT DESCRIPTION: This API returns field (#81202) - PACKAGE, of the V TREATMENT (#9000010.15) file. A pointer to the Package (#9.4) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V TREATMENT (#9000010.15) file. VARIABLES: $$PACKAGE TYPE: Output VARIABLES DESCRIPTION: Pointer to the Package (#9.4) file. COMPONENT/ENTRY POINT: $$DATASRC(IEN) COMPONENT DESCRIPTION: This API returns field (#81203) - DATA SOURCE, of the V TREATMENT (#9000010.15) file. A pointer to the PCE Data Source (#839.7) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V TREATMENT (#9000010.15) file. VARIABLES: $$DATASRC TYPE: Output VARIABLES DESCRIPTION: Pointer to the PCE Data Source (#839.7) file. NUMBER: 3051 IA #: 3051 DATE CREATED: FEB 22, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXAAVXAM NAME: DBIA3035-A ORIGINAL NUMBER: 3035 ID: PXAAVXAM GENERAL DESCRIPTION: The following is a description of the available APIs for the V EXAM (#9000010.13) file. The V EXAM (#9000010.13) file stores exam information, one record for each exam for each visit. STATUS: Active DURATION: Next Version MAIL MESSAGE: 30948205 GOOD ONLY FOR VERSION: 1.0 KEYWORDS: PXAA COMPONENT/ENTRY POINT: $$GETIENS(VSITIEN,ARRAY) COMPONENT DESCRIPTION: Use this API to retrieve all Internal Entry Numbers (IEN) from the V EXAM (#9000010.13) file associated with the given visit IEN, VSITIEN. VARIABLES: VSITIEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a given patient visit. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) This array variable is populated by the API with the Internal Entry Numbers of records found to be associated in the V EXAM (#9000010.13) file with the patient visit IEN. VARIABLES: $$GETIENS TYPE: Output VARIABLES DESCRIPTION: Returns 0 if no record was found in the V EXAM (#9000010.13) file for the given visit IEN. Returns 1 if one or more records were found in the V EXAM (#9000010.13) file for the given visit IEN. COMPONENT/ENTRY POINT: $$LOADFLDS(IEN,ARRAY) COMPONENT DESCRIPTION: This API loads all the field values for a given record IEN in the V EXAM (#9000010.13) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V EXAM (#9000010.13) file. VARIABLES: $$LOADFLDS TYPE: Output VARIABLES DESCRIPTION: Returns 0 if no record was found in the V EXAM (#9000010.13) file for the given patient IEN. Returns 1 if the API has successfully loaded all the field values into the ARRAY variable. VARIABLES: ARRAY TYPE: Input VARIABLES DESCRIPTION: (required) All the field values of the V EXAM (#9000010.13) file for the given record IEN such as; Patient Name, Results, Exam type, etc. COMPONENT/ENTRY POINT: $$EXAM(IEN) COMPONENT DESCRIPTION: This API returns field (#.01) - EXAM, of the V EXAM (#9000010.13) file. A pointer to the EXAM (#9999999.15) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V EXAM (#9000010.13) file. VARIABLES: $$EXAM TYPE: Output VARIABLES DESCRIPTION: A pointer to the EXAM (#9999999.15) file. COMPONENT/ENTRY POINT: $$PATINAME(IEN) COMPONENT DESCRIPTION: This API returns field (#.02) - PATIENT NAME, of the V EXAM (#9000010.13) file. A pointer to the PATIENT/IHS (#9000001) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V EXAM (#9000010.13) file. VARIABLES: $$PATINAME TYPE: Output VARIABLES DESCRIPTION: A pointer to the PATIENT/IHS (#9000001) file. COMPONENT/ENTRY POINT: $$VISIT(IEN) COMPONENT DESCRIPTION: This API returns field (#.03) - VISIT, of the V EXAM (#9000010.13) file. A pointer to the VISIT (#9000010) file indicating the date and time for the encounter where the exam took place. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V EXAM (#9000010.13) file. VARIABLES: $$VISIT TYPE: Output VARIABLES DESCRIPTION: A pointer to the Visit (#9000010) file indicating the date and time for the encounter where the exam took place. COMPONENT/ENTRY POINT: $$RESULT(IEN) COMPONENT DESCRIPTION: This API returns field (#.04) - HOW MANY, of the V TREATMENT (#9000010.13) file. A value indicating the result of the exam. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V EXAM (#9000010.13) file. VARIABLES: $$RESULT TYPE: Output VARIABLES DESCRIPTION: Returns; 'A' - ABNORMAL or 'N' - NORMAL COMPONENT/ENTRY POINT: $$EVENTDT(IEN) COMPONENT DESCRIPTION: This API returns field (#1201) - EVENT DATE AND TIME, of the V EXAM (#9000010.13) file. The date and time the exam took place. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V EXAM (#9000010.13) file. VARIABLES: $$EVENTDT TYPE: Output VARIABLES DESCRIPTION: The date and time the exam took place. COMPONENT/ENTRY POINT: $$ORDEPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1202) - ORDERING PROVIDER, of the V EXAM (#9000010.13) file. A pointer to the NEW PERSON (#200) file identifying the provider who ordered the exam. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V EXAM (#9000010.13) file. VARIABLES: $$ORDEPROV TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200) file. COMPONENT/ENTRY POINT: $$ENCOPROV(IEN) COMPONENT DESCRIPTION: This API returns field (#1204) - ENCOUNTER PROVIDER, of the V EXAM (#9000010.13) file. A pointer to the NEW (#200) file identifying the provider who gave the exam. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V EXAM (#9000010.13) file. VARIABLES: $$ENCOPROV TYPE: Output VARIABLES DESCRIPTION: A pointer to the NEW PERSON (#200). COMPONENT/ENTRY POINT: $$EDITFLAG(IEN) COMPONENT DESCRIPTION: This API returns field (#80101) - EDITED FLAG, of the V TREATMENT (#9000010.13) file. This field indicates if PCE detects that any original exam data is being edited. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V EXAM (#9000010.13) file. VARIABLES: $$EDITFLAG TYPE: Output VARIABLES DESCRIPTION: Returns 1 if PCE detects that any original exam data is being edited. COMPONENT/ENTRY POINT: $$AUDITRAI(IEN) COMPONENT DESCRIPTION: This API returns field (#80102) - AUDIT TRAIL, of the V EXAM (#9000010.13) file. This field is populated automatically by the PCE filing logic. The format of the field is as follows: Pointer to PCE data source file_"-"_A for Add or E for Edit_" "_DUZ of the person who entered the data_";" VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V EXAM (#9000010.13) file. VARIABLES: $$AUDITRAI TYPE: Output VARIABLES DESCRIPTION: A Free Text value in the format; Pointer to PCE data source file_"-"_A for Add or E for Edit_" "_DUZ of the person who entered the data_";" COMPONENT/ENTRY POINT: $$COMMENTS(IEN) COMPONENT DESCRIPTION: This API returns field (#81101) - COMMENTS, of the V EXAM (#9000010.13) file. Any comments related to the patient's exam. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V EXAM (#9000010.13) file. VARIABLES: $$COMMENTS TYPE: Output VARIABLES DESCRIPTION: A Free Text value indicating any comments related to the patient's exam. COMPONENT/ENTRY POINT: $$VERIFIED(IEN) COMPONENT DESCRIPTION: This API returns field (#81201) - VERIFIED, of the V EXAM (#9000010.13) file. This field indicates whether the record was Electronically Signed or Verified by the Package. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V EXAM (#9000010.13) file. VARIABLES: $$VERIFIED TYPE: Output VARIABLES DESCRIPTION: 1 - Electronically Signed, 2 - Verified by the Package. COMPONENT/ENTRY POINT: $$PACKAGE(IEN) COMPONENT DESCRIPTION: This API returns field (#81202) - PACKAGE, of the V EXAM (#9000010.13) file. A pointer to the Package (#9.4) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V EXAM (#9000010.13) file. VARIABLES: $$PACKAGE TYPE: Output VARIABLES DESCRIPTION: Pointer to the Package (#9.4) file. COMPONENT/ENTRY POINT: $$DATASRC(IEN) COMPONENT DESCRIPTION: This API returns field (#81203) - DATA SOURCE, of the V EXAM (#9000010.13) file. A pointer to the PCE Data Source (#839.7) file. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (required) This number represents the Internal Entry Number for a record in the V EXAM (#9000010.13) file. VARIABLES: $$DATASRC TYPE: Output VARIABLES DESCRIPTION: Pointer to the PCE Data Source (#839.7) file. NUMBER: 3052 IA #: 3052 DATE CREATED: FEB 24, 2000 CUSTODIAL PACKAGE: NURSING SERVICE CUSTODIAL ISC: Chicago USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: NURSUT5 NAME: Nursing Ward Location API ID: NURSUT5 GENERAL DESCRIPTION: Patch NUR*4*31 introduces a new supported Application Programming Interface(API). This API provides a "Query" and "Look-up" on the NURS LOCATION file (#211.4). This DBIA was developed as a way to provide access to File #211.4 and allow Nursing to retire two existing private DBIAs. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30867000 KEYWORDS: NUR KEYWORDS: API KEYWORDS: WARD LOCATION COMPONENT/ENTRY POINT: WARD(FUNCT,.ARRAY) COMPONENT DESCRIPTION: In the following examples the ARRAY is variable VAR. The first example is a query for all active wards. The second example is a look-up a specific entry in the NURS LOCATION file (#211.4). 1) Coding example of Query call: KILL VAR ; initialize VAR DO WARD^NURSUT5("Q^A",.VAR) ; Call to API User interface: Select NURSING UNIT NAME: ? NOTE: The letters NUR may be in front of the location name. This is not to be corrected under any circumstance. DO YOU WANT THE ENTIRE 26-ENTRY NURSING UNIT LIST? Y (Yes) CHOOSE FROM: 10E SUPPORT ISC 10W SUPPORT ISC 12E SUPPORT ISC 2AS SUPPORT ISC 3AS HINES ISC 3E SUPPORT ISC 4AS PSYCHIATRY SUPPORT ISC 5NP HINES ISC Select NURSING UNIT NAME: 4AS PSYCHIATRY 2) Coding example of Look-up call: KILL VAR ; initialize VAR DO WARD^NURSUT5("L^5",.VAR) ; Call to API In both cases when the API returns the data it will be placed into the variable array specified. If the data value is missing the array element for that value will not be returned. The following is an example of the return array. Example of Return Array: VAR=5 VAR(5,.01)="30^4AS PSYCHIATRY" VAR(5,.02)="499^SUPPORT ISC" VAR(5,.03)="1^NURSING" VAR(5,1)="A^ACTIVE" VAR(5,1.5)="A^ACTIVE" VAR(5,2)=1 VAR(5,2,1,.01)="4^4AS" VAR(5,2,1,1)="1^PSYCHIATRIC" VAR(5,4)=1 VAR(5,4,1.01)="1^PSYCHIATRIC" VAR(5,11)="60" VAR(5,12)="8^PSYCHIATRY" VAR(5,37)="YES" VARIABLES: FUNCT TYPE: Input VARIABLES DESCRIPTION: FUNCT = Piece1_^_Piece2 Piece1 must contain an "L" or "Q" Piece1 "L" means Look-up of specified entry in File 211.4, and Piece2 must contain the IEN for the entry in File 211.4. Piece1 "Q" means do a DIC style query on File 211.4, and Piece2 must contain "I","A" or ""(i.e., null). This will be the screen used on the look-up. The API will do a DIC style look-up for the ward. "I" means look-up only inactive wards. "A" means look-up only active wards. "" means look-up all wards. VARIABLES: .ARRAY TYPE: Both VARIABLES DESCRIPTION: .ARRAY = Recommend the return array should be namespaced. Return Values: ARRAY = -1 means that the Look-up or Query failed. ARRAY = IEN means that the Look-up or Query was successful. ARRAY can be any variable array that the developer chooses. When the API returns the data it will be placed into the variable array specified. If the data value is missing the array element for that value will not be returned. Return Array: ARRAY(IEN,.01) = Pointer to File 44 _"^"_ External value of Hospital Location file(44), Name field(.01) ARRAY(IEN,.02) = Facility pointer to File 4_"^"_ External name of facility ARRAY(IEN,.03) = Pointer to File 212.7 _"^"_ External value of NURS Product Line file(212.7), Name field(.01) ARRAY(IEN,1) = Patient care status internal value_"^"_ External value of Patient care status ARRAY(IEN,1.5) = Ward status Internal value_"^"_ External value of Ward status ARRAY(IEN,2) = Total number of MAS ward pointers X = the IEN of the entry within the MAS ward Multiple. ARRAY(IEN,2,X,.01) = Pointer to File 42 _"^"_ External value of Ward Location file(42), Name field(.01) ARRAY(IEN,2,X,1) = Pointer to File 213.3_"^"_External value of NURS AMIS Ward file(213.3), Bed Section field(.01) ARRAY(IEN,4) = Total number of AMIS ward pointers. Y = the IEN of the entry within the AMIS Bed section Multiple. ARRAY(IEN,4,Y,.01) = Pointer to file 213.3_"^"_External value of NURS AMIS Ward file(213.3), Bed Section field(.01) ARRAY(IEN,11) = Professional Percentage ARRAY(IEN,12) = Pointer to File 211.5_"^"_External value of NURS Clinical Background file(211.5), Description field(.01) ARRAY(IEN,37) = Indicates whether or not active staff is assigned to this ward. NUMBER: 3053 IA #: 3053 DATE CREATED: FEB 29, 2000 CUSTODIAL PACKAGE: PAID CUSTODIAL ISC: Washington USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PRSDUTIL NAME: Obtain Description for PAID Code ID: PRSDUTIL GENERAL DESCRIPTION: This IA allows the ASISTS package to call routine PRSDUTIL to obtain a description of a code from the following tables in the PAID CODE FILES (#454). Use OT^PRSDUTIL for the following tables: Table Subscript ---------- --------- PAY BASIS PB PAY PLAN PP RETIREMENT RET EDUCATION EDU Use OST^PRSDUTIL for the OCCUPATION SERIES/TITLE table. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30936130 COMPONENT/ENTRY POINT: OT COMPONENT DESCRIPTION: Returns the description of a code for several PAID tables. VARIABLES: Y TYPE: Both VARIABLES DESCRIPTION: Y should be set to the value of the code before calling OT. If the code is found in the table then Y will be changed to it's description. VARIABLES: SUB454 TYPE: Input VARIABLES DESCRIPTION: Variable SUB454 must be set to the subscript of the table. For example, set SUB454="PB" to look up a code in the PAY BASIS table. COMPONENT/ENTRY POINT: OST COMPONENT DESCRIPTION: Returns the description for an occupation series & title code. VARIABLES: Y TYPE: Both VARIABLES DESCRIPTION: Y should be set to the value of the code before calling OST. If the code is found in the table then Y will be changed to it's description. SUBSCRIBING PACKAGE: ASISTS ISC: Washington/Silver Spring EDITOR: HOWELL,LYNN NUMBER: 3054 IA #: 3054 FILE NUMBER: 9000001 GLOBAL ROOT: AUPNPAT( DATE CREATED: FEB 29, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3054 ID: AUPNPAT( GENERAL DESCRIPTION: DG namespaced routine deletes PATIENT/IHS entries when the patients that these entries point to in the PATIENT file are being deleted. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30936508 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 3055 IA #: 3055 FILE NUMBER: 811.1 GLOBAL ROOT: PXD(811.1, DATE CREATED: MAR 01, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GET CODE MAPPING ID: PXD(811.1, GLOBAL REFERENCE: PXD(811.1,D0, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30939344 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3056 IA #: 3056 DATE CREATED: MAR 01, 2000 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XLFNSLK NAME: DNS lookup ID: XLFNSLK GENERAL DESCRIPTION: Call a DNS to resolve Domain names. STATUS: Active MAIL MESSAGE: 30943336 KEYWORDS: DNS COMPONENT/ENTRY POINT: $$ADDRESS(domain_name[,type]) COMPONENT DESCRIPTION: $$ADDRESS^XLFNSLK(domain_name[,type]) This call will call a DNS to convert the domain name into IP address's. The IP address of the DNS is in the Kernel System Parameter file, field DNS IP. Example: W $$ADDRESS^XLFNSLK("FORUM.VA.GOV") =>> 152.128.1.25 VARIABLES: domain_name TYPE: Input VARIABLES DESCRIPTION: domain_name is a fully qualified domain name like FORUM.VA.GOV VARIABLES: type TYPE: Input VARIABLES DESCRIPTION: This is input is optional. Type is from the set A: address (the default), CNAME: alias. VARIABLES: $$ADDRESS TYPE: Output VARIABLES DESCRIPTION: Returns a coma-separated list of IP address's that are associated with the domain. COMPONENT/ENTRY POINT: MAIL(RETURN, domain_name) COMPONENT DESCRIPTION: MAIL^XLFNSLK(RETURN, domain_name) This call will call a DNS to get the MX records for a domain name with their IP address. VARIABLES: domain_name TYPE: Input VARIABLES DESCRIPTION: domain_name is a fully qualified domain name like FORUM.VA.GOV VARIABLES: RETURN TYPE: Output VARIABLES DESCRIPTION: Pass by reference a local variable to hold the return array. The data is subscripted by priority. domain_name is a full domain name like FORUM.VA.GOV Example: K ZX D MAIL(.ZX,"ISC-SF.MED.VA.GOV") ZW ZX ZX=2 ZX(30)=a2.isc-sf.med.va.gov.^152.132.1.57 ZX(50)=gateway.forum.va.gov.^152.128.1.2 NUMBER: 3057 IA #: 3057 DATE CREATED: MAR 06, 2000 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUS1A NAME: SET~XUS1A ID: XUS1A GENERAL DESCRIPTION: The is a API for use by code called from the XU USER SIGN-ON protocol to pass text back to the user. STATUS: Active MAIL MESSAGE: 30965142 COMPONENT/ENTRY POINT: SET(T) COMPONENT DESCRIPTION: The line of text passed in will be displayed to the user after all the XU USER SIGN-ON protocol have completed. If the first character is a "!" the text will start on a new line. The "@" as a first character is reserved for future use. VARIABLES: T TYPE: Input VARIABLES DESCRIPTION: Line of text to be displayed. NUMBER: 3058 IA #: 3058 DATE CREATED: MAR 08, 2000 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIULX NAME: TIULX Document Class ID: TIULX GENERAL DESCRIPTION: Text Integration Utilities Cross-reference library functions. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30976017 KEYWORDS: ISA KEYWORDS: TIULX KEYWORDS: HEALTH KEYWORDS: SUMMARY COMPONENT/ENTRY POINT: $$ISA(DA,CLASS) COMPONENT DESCRIPTION: This entry point is used to evaluate whether a given document type is a member of a particular document class. VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: Record number in file 8925.1, represents a document type. VARIABLES: CLASS TYPE: Input VARIABLES DESCRIPTION: Record number in file 8925.1, represents a document class. SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: Used to determine document class (silently) for the GUI Ad Hoc Health Summary. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: Effective with VPR*1*0. DBA Comments: 08/02/13 DT: Added VPR as subscriber, effective with VPR*1*0. DATE/TIME EDITED: JAN 23, 2007@23:56 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SHOVESTUL,MARYANN WITH CONCURRENCE OF: RUSSELL,JOEL DATE/TIME EDITED: AUG 02, 2013@13:45 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 3059 IA #: 3059 FILE NUMBER: 8925.1 GLOBAL ROOT: TIU(8925.1 DATE CREATED: MAR 08, 2000 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TIU(8925.1 Health Summary ID: TIU(8925.1 GLOBAL REFERENCE: TIU(8925.1,DA,0) GLOBAL DESCRIPTION: Used to select document types belonging to the Class of Progress Notes. GLOBAL REFERENCE: TIU(8925.1,'B') GLOBAL DESCRIPTION: B-cross reference used to loop throught document types looking for those types belonging to the document class Progress Notes. GENERAL DESCRIPTION: Access TIU DOCUMENT DEFINITION file #8925.1 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30976365 KEYWORDS: HEALTH KEYWORDS: SUMMARY SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: Access TIU(8925.1 to obtain a list of document types in a class (silent) used in GUI AD Hoc Health Summary. NUMBER: 3060 IA #: 3060 DATE CREATED: MAR 08, 2000 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: Reference to variable DICR GENERAL DESCRIPTION: Reference to undocumented variable, DICR, for the purpose of determining if lookup by patient is originating in a file other than the PATIENT file. VIEWER: WINN,TAMI STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30876059 KEYWORDS: DICR KEYWORDS: DIC SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING DETAILS: Establishing an agreement covering pre-existing references to the variable DICR in the 'post-selection action' of the PATIENT file and the PATIENT file special lookup routine DPTLK. NUMBER: 3062 IA #: 3062 DATE CREATED: MAR 09, 2000 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIULAPIS NAME: TIULAPIS Selected Prog Note ID: TIULAPIS GENERAL DESCRIPTION: The routine TIULAPIS controls the branching for extracting selected Progress Notes by occurrence, date or type for a given patient. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30983379 KEYWORDS: HEALTH KEYWORDS: SUMMARY KEYWORDS: GMTSPNSL COMPONENT/ENTRY POINT: MAIN COMPONENT DESCRIPTION: Extract selected documents from Text Integration Utility. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The IEN of the patient file (#2) (required) VARIABLES: TIUDOC TYPE: Input VARIABLES DESCRIPTION: Array of selected document types to extract, including the IEN of the TIU DOCUMENT DEFINITION file (#8925.1) (required) VARIABLES: STATUS TYPE: Input VARIABLES DESCRIPTION: Document status, i.e., signed, unsigned, not released, etc. VARIABLES: TIME1 TYPE: Input VARIABLES DESCRIPTION: The beginning date for a range of dates to extract TIU documents (optional, default 6666666) VARIABLES: TIME2 TYPE: Input VARIABLES DESCRIPTION: The ending date for a range of dates to extract TIU documents (optional, default 9999999) VARIABLES: OCCLIM TYPE: Input VARIABLES DESCRIPTION: The number of occurrences of teh type of document to extract (optional, default 999) VARIABLES: TEXT TYPE: Input VARIABLES DESCRIPTION: Boolean flag (1/0) to include or not to include document text with the extraction (required) SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: Used for the Health Summary Selected Progress Notes Component. NUMBER: 3063 IA #: 3063 DATE CREATED: MAR 09, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRHS08 NAME: PXRHS08 Patient Education ID: PXRHS08 GENERAL DESCRIPTION: Patient Education data extract. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30983539 KEYWORDS: GMTSPXEP COMPONENT/ENTRY POINT: EDUC(DFN,ENDDT,BEGDT,OCCLIM,CATCODE) COMPONENT DESCRIPTION: Extracts by education topic, the event date and time (or visit/admit date and time), patient's level of understanding, encounter provider, hospital location (or outside location), and data source. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The IEN of the patient file (#2) (required) VARIABLES: ENDDT TYPE: Input VARIABLES DESCRIPTION: Ending date/time in internal FileMan format (optional, default is today's date at 11:59 pm) VARIABLES: BEGDT TYPE: Input VARIABLES DESCRIPTION: Beginning date/time in internal FileMan format (optional, default is one year prior to today's date) VARIABLES: OCCLIM TYPE: Input VARIABLES DESCRIPTION: Maximum number of days for which data is returned (If multiple visits on a given day, all data for these visit will be returned) or an "R" for only the most recent occurrence of each topic. (optional, default is 999) VARIABLES: CATCODE TYPE: Input VARIABLES DESCRIPTION: Pattern Match which controls visit data that is returned (can include multiple codes). (required) A = AMBULATORY H = HOSPITALIZATION I = IN HOSPITAL C = CHART REVIEW T = TELECOMMUNICATIONS N = NOT FOUND S = DAY SURGERY O = OBSERVATION E = EVENT (HISTORICAL) R = NURSING HOME D = DAILY HOSPITALIZATION DATA X = ANCILLARY PACKAGE DAILY DATA VARIABLES: ~TMP("PXPE",$J, TYPE: Output VARIABLES DESCRIPTION: Data from V Patient Education (9000010.16) file ^TMP("PXPE",$J,InvDt,TOPIC,IFN,0) = TOPIC [E;.01] ^ EVENT DATE/TIME or VISIT/ADMIT DATE&TIME [I;1201 or .03] ^ LEVEL OF UNDERSTANDING [E;.06] ^ ORDERING PROVIDER [E;1202] ^ ENCOUNTER PROVIDER [E;1204] ^TMP("PXPE",$J,InvDt,TOPIC,IFN,1) = HOSPITAL LOCATION [E;9000010;.22] ^ HOSP. LOC. ABBREVIATION [E;44;1] ^ LOC OF ENCOUNTER [E;9000010;.06] ^ OUTSIDE LOC [E;9000010;2101] ^TMP("PXPE",$J,InvDt,TOPIC,IFN,"S") = DATA SOURCE [E;80102] [] = [I(nternal)/E(xternal); Optional file #; Record #] Subscripts: InvDt - Inverse FileMan date of DATE OF event or visit TOPIC - Patient Education Topic IFN - Internal Record # ^TMP("PXPE",$J) should be killed by the calling application before EDUC is called and after the array is used. SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: Used to support Patient Education Health Summary Component. NUMBER: 3064 IA #: 3064 DATE CREATED: MAR 14, 2000 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSDOPT0 NAME: CONTROLLED SUBSTANCE API ID: PSDOPT0 GENERAL DESCRIPTION: When a prescription is returned to stock in Outpatient Pharmacy 7.0, the entry is deleted from the prescription file. If the prescription was a controlled substance, the pharmacy location's balance is not updated. This API will check the prescription when it is being returned. If the prescription is for a controlled substance, the user will be asked if they want to update the balances for the associated pharmacy location. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 30997877 COMPONENT/ENTRY POINT: PSDRTS(PSDRX,PSDNUM,PSDSITE,PSDQTY) COMPONENT DESCRIPTION: This entry point is called directly in routine PSDOPT0. The call returns no values to Outpatient Pharmacy. VARIABLES: PSDRX TYPE: Input VARIABLES DESCRIPTION: The name of the prescription VARIABLES: PSDNUM TYPE: Input VARIABLES DESCRIPTION: The refill number VARIABLES: PSDSITE TYPE: Input VARIABLES DESCRIPTION: The pharmacy location the prescription is being returned to. VARIABLES: PSDQTY TYPE: Input VARIABLES DESCRIPTION: The quantity being returned to stock. SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 3065 IA #: 3065 DATE CREATED: MAR 15, 2000 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XLFNAME NAME: Name Standardization APIs ID: XLFNAME GENERAL DESCRIPTION: Supported Name Standardization APIs. STATUS: Active MAIL MESSAGE: 31069582 COMPONENT/ENTRY POINT: STDNAME(.NAME,FLAGS,.AUDIT) COMPONENT DESCRIPTION: Name Standardization Routine ============================ This procedure parses a name and converts it into the following standard format: Family_name,Given_nameMiddle_nameSuffix A name in standard format is entirely in upper-case, and contains no Arabic numerals. The Family_name (last name) portion of a standard name appears to the left of the comma and contains no spaces and no punctuation except hyphens (-). The other parts of a standard name (the portion to the right of the comma) contain no punctuation except for hyphens and spaces. NMI and NMN are not used for the Middle_name. STDNAME^XLFNAME optionally returns in an array the component parts of the name. It also optionally returns information in an array about possible problems encountered during the conversion of the name to standard form and the parsing of the name into its component parts. Details: ------- In forming the standard name, the following changes are made: 1. The name is converted to uppercase. 2. In the Family Name: a. Semicolons (;) and colons (:) are converted to hyphens (-). b. Spaces and all other punctuation except hyphens are removed. 3. In the other name parts (Given Name, Middle Name, and Suffix). a. Semicolon, colons, commas (,), and periods (.) are converted to spaces. b. All punctuation except hyphens and spaces are removed. 4. Hyphens and spaces at the beginning and end of the name are removed. 5. Two or more consecutive hyphens/spaces are replaced with a single hyphen/space. 6. Any suffixes immediate preceding the comma are moved to the end. 7. The suffixes indicating birth positions 1st, 2nd, 3rd, ..., 10th are converted to their Roman numeral equivalents I, II, III, X. 8. DR immediately after the comma (or if there is no comma, at the beginning of the name), is assumed to be a suffix and moved to the end of the name. 9. Any suffixes between two commas immediate after the Family Name are moved to the end of the name. 10. NMI or NMN used as a Middle Name is deleted. In forming the component parts of the name, only the following changes are mode: 1. The name component is converted to uppercase. 2. In the Family Name, semicolons (;) and colons (:) are converted to hyphens (-). 3. In the other name parts (Given Name, Middle Name, and Suffix), semicolons, colons, and commas (,) are converted to spaces. 4. Hyphens and spaces at the beginning and end of the name are removed. 5. Two or more consecutive hyphens/spaces are replaced with a single hyphen/space. 6. A Middle Name of NMI or NMN is changed to null. 7. Spaces after periods are removed. 8. Accent graves (`) and up-arrows (^) are removed. In parsing the name into its component parts, if the name contains a comma or the "F" flag is passed, STDNAME^XLFNAME looks for suffixes immediately to the left of the first comma, and at the very end of the name. The suffixes it recognizes are 1ST through 10TH, JR, SR, DR, MD, ESQ, DDS, RN and Roman numerals I through X. If a name part before any recognizable suffixes is more than one character in length, and contains no vowel or 'Y', it is also assumed to be a suffix. The Name Standardization looks for the DR suffix immediately after the first comma, and for any suffix between two commas immediately after the Family Name. The portion of the name to the left of the comma, less any suffixes, is assumed to be the Family Name. After STDNAME^XLFNAME accounts for all Suffixes, it looks at the portion of the name after the comma. It assumes that the first space-delimited piece is the Given Name. If any other pieces are left, the last one (rightmost) is assumed to be the Middle Name, and anything else is appended to the end of the Given Name. If the name contains no comma, and the "F" flag is not passed, STDNAME^XLFNAME looks for suffixes at the very end of the name. The last space-delimited piece before any suffixes is assumed to be the Family Name. The first space-delimited piece is assumed to be the Given Name. If any other pieces are left, the last one (rightmost) is assumed to be the Middle Name, and anything else is appended to the end of the Given Name. Example: ------- In this example, the variable MYNAME is set to the name to be standardized. The "C" flag indicates that the name components should be returned in the MYNAME array, and the "P" flag indicates that parenthetical text should be removed from the name. STDNAME^XLFNAME sets MYAUD to original name passed in and sets nodes in the MYAUD array to flag changes and possible problems. >S MYNAME="VAN DOREN,JOHN A. B. 2ND (TEST)" >D STDNAME^XLFNAME(.MYNAME,"CP",.MYAUD) >ZW MYNAME MYNAME=VANDOREN,JOHN A B II MYNAME("FAMILY")=VAN DOREN MYNAME("GIVEN")=JOHN A. MYNAME("MIDDLE")=B. MYNAME("SUFFIX")=2ND >ZW MYAUD MYAUD=VAN DOREN,JOHN A. B. 2ND (TEST) MYAUD("MIDDLE")="" MYAUD("PERIOD")="" MYAUD("SPACE")="" MYAUD("STRIP")="" STDNAME^XLFNAME returned the standard form of the name in MYNAME as VANDOREN,JOHN A B II. It interpreted JOHN A. as the given (first) name and B. as the middle name. Since this may not be correct, MYAUD("MIDDLE") is set. Periods were removed and spaces were removed to form the standard name, therefore MYAUD("PERIOD") and MYAUD("SPACE") were set. Finally, since the parenthetical text (TEST) was removed, MYAUD("STRIP") was set. VARIABLES: NAME TYPE: Both VARIABLES DESCRIPTION: (Required) NAME is the name to be converted to standard format. It is assumed that the name is in the general format: Family_name,Given_name(s) Middle_name Suffix(es) If the "F" flag is not used, and the name contains no comma, it is assumed the name is in the general format: Given_name(s) Middle_name Family_name Suffix(es) The standard form of the name is returned in the NAME variable. If the "C" flag is passed in, the components of the name are returned in nodes descendent from NAME. Output: ------ NAME is set to the name that was input converted to standard format. If the FLAGS input parameter contains a "C", the component parts of the name are returned in the NAME array: NAME("FAMILY) = Family (Last) Name NAME("GIVEN") = Given (First) Name(s) NAME("MIDDLE") = Middle Name NAME("SUFFIX") = Suffix(es) VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: Flags to control processing. Possible values are:. C - Return name components in the NAME array. F - If the name passed in the NAME input parameter does not contain a comma, assume it is the Family Name only. For example, if the name input is "ST JAMES", return the name as "STJAMES" instead of "JAMES,ST" G - Don't return AUDIT("GIVEN") even if the Given Name is missing. P - Remove text in parentheses (), brackets [], or braces {} from the name. If such text is actually removed, return AUDIT("STRIP"). VARIABLES: AUDIT TYPE: Both VARIABLES DESCRIPTION: If provided, this is an array that STDNAME^XLFNAME returns if there are any ambiguities or possible problems in stardardizing the name or parsing the name into component parts. Output: ------ AUDIT is set to the original name that was passed in NAME. In addition, if there were any problems in the interpretation of the NAME being standardized, descendents of AUDIT are set: AUDIT("subscript") = "" where "subscript" can be one of the following: AUDIT("FAMILY") The Family Name starts with ST. (The period and space are removed from the Family Name. For example, the name "ST. JOHN" is converted to "STJOHN".) AUDIT("GIVEN") Returned if there is no Given Name and the "G" flag isn't passed in. AUDIT("MIDDLE") Returned if there are three or more names between the first comma and the Suffix(es). (All name parts except the last are assumed to be part of the Given Name. Only the last part is assumed to be the Middle Name.) AUDIT("NM") Returned if NMI or NMN appears to be used as the Middle Name. (NMI and NMN are removed from the standard name, and the Middle Name component is returned as null.) AUDIT("NOTE") Returned if the name appears to contain a note or flag that may not actually be part of the name. For example, the name starts with "C-" or "EEE," or has "FEE" at the end. AUDIT("NUMBER") Returned if a name part (other than a valid numeric Suffix) contains a number. AUDIT("PERIOD") Returned if periods were removed. AUDIT("PUNC") Returned if punctuation was removed. AUDIT("SPACE") Returned if spaces were removed from the Family Name. AUDIT("STRIP") Returned if text in parentheses (), brackets [], or braces {} were removed from the Name. (This is done only if the "P" flag is passed.) AUDIT("SUFFIX") Returned if: - Suffix(es) are found immediately to the left of the 1st comma.7 I, V, or X, and nothing else except valid suffixes, appear immediately after the Given Name. (It is interpreted as the Middle Name.) - The name immediately after the Given Name appears to be a non-numeric suffix (except I, V, and X), and everything after that also appear to be suffixes. (It is assumed there are a Given Name and Suffix(es), but no Middle Name.) - M.D. or M D is found at the end of the name, or before any valid suffixes at the end of the name. (It is assumed that M and D are initials in the Given or Middle Name rather than a Suffix.) - The name part before any recognizable suffixes is more than one character in length and doesn't contain any vowels or Y. It is interpreted as a suffix. - A Suffix is found between commas immediately after the Family Name. COMPONENT/ENTRY POINT: $$CLEANC(COMP,FLAGS) COMPONENT DESCRIPTION: Name Component Standardization Routine ====================================== This extrinsic function takes a single name component and returns that name in standard format. Examples: -------- 1. Standardize family (last) name: $$CLEANC^XLFNAME("O'BRIEN-DE LA ROSA","F) --> OBRIEN-DELAROSA $$CLEANC^XLFNAME("ST. JAMES","F") --> STJAMES 2. Standardize other (non-family) name components: $$CLEANC^XLFNAME("E.C.) --> E C $$CLEANC^XLFNAME("RENEE'") --> RENEE $$CLEANC^XLFNAME("MARY ANN") --> MARY ANN $$CLEANC^XLFNAME("JO-ANNE") --> JO-ANNE VARIABLES: COMP TYPE: Input VARIABLES DESCRIPTION: (Required) The name component to be converted to standard format. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: Flags to control processing. Possible values are: F - If the name component to be converted is the FAMILY (LAST) NAME, pass the "F" flag. With the "F" flag, colons (:), semicolons (;), and commas (,) are converted to hyphens (-). Spaces and all punctuation except hyphens are removed. Leading and trailing spaces and hyphens are removed. Two or more consecutive spaces or hyphens are replaced with a single space or hyphen. Without the "F" flag, the component is converted to upper case. Colons, semicolons, commas, and periods (.) are converted to spaces. All punctuation except for hyphens and spaces are removed. Leading and trailing spaces and hyphens are removed. Two or more consecutive spaces or hyphens are replaced with a single space or hyphen. Birth position indicators 1ST through 10TH are changed to their Roman numeral equivalents. COMPONENT/ENTRY POINT: NAMECOMP(.NAME) COMPONENT DESCRIPTION: Component Parts from Standard Name ================================== This procedure takes a name in standard format and returns in an array the component parts of that name. Example: ------- In this example, the variable MYNAME is set to the standard name, and the NAMECOMP^XLFNAME call is made to return in the MYNAME array the component parts of that name: >S MYNAME="MCDONALD-STJAMES,MARY ANN S MD" >D NAMECOMP^XLFNAME(.MYNAME) >ZW MYNAME MYNAME=MCDONALD-STJAMES,MARY ANN S MD MYNAME("FAMILY")=MCDONALD-STJAMES MYNAME("GIVEN")=MARY ANN MYNAME("MIDDLE")=S MYNAME("SUFFIX")=MD VARIABLES: NAME TYPE: Both VARIABLES DESCRIPTION: (Required) NAME is the name in standard format to be parsed. NAMECOMP^XLFNAME returns the component parts of the name in nodes descendent from NAME. Output: ------ The component parts of the name are returned in the NAME array passed in. NAME("FAMILY) = Family (last) Name NAME("GIVEN") = Given (first) Name NAME("MIDDLE") = Middle Name NAME("SUFFIX") = Suffix(es) COMPONENT/ENTRY POINT: $$NAMEFMT(.NAME,FORMAT,FLAGS) COMPONENT DESCRIPTION: Formatted Name from Name Components =================================== This extrinsic function returns a name converted to a form useful for display. Details: ------- If the L# flag is used, and the resulting name is longer than #, the following pruning algorithm is performed to shorten the name: 1. Drop Degree; 2. Drop Prefix; 3. Truncate Middle Name from the right-most position until only the initial character is left; 4. Drop suffix; 5. Truncate Given Name from the right-most position until only the initial character is left; 6. Truncate Family Name from the right-most position; 7. Truncate the name from the right. Examples: -------- 1. Suppose the MYNAME array contains the following elements: MYNAME("PREFIX") = "MR." MYNAME("GIVEN") = "JOHN" MYNAME("MIDDLE") = "K." MYNAME("FAMILY") = "O'BRIEN" MYNAME("SUFFIX") = "JR" MYNAME("DEGREE") = "PHD" Calls to $$NAMEFMT^XLFNAME will return the name as follows: $$NAMEFMT^XLFNAME(.MYNAME,"F") --> O'BRIEN JOHN K. JR $$NAMEFMT^XLFNAME(.MYNAME,"F","C") --> O'BRIEN,JOHN K. JR $$NAMEFMT^XLFNAME(.MYNAME,"F","CS") --> OBRIEN,JOHN K JR $$NAMEFMT^XLFNAME(.MYNAME,"F","CSD") --> OBRIEN,JOHN K JR PHD $$NAMEFMT^XLFNAME(.MYNAME,"F","CDcXc") --> O'BRIEN,JOHN K., JR, PHD $$NAMEFMT^XLFNAME(.MYNAME,"F","CSL12") --> OBRIEN,JOH K $$NAMEFMT^XLFNAME(.MYNAME,"F","CMD") --> O'Brien,John K. Jr PhD $$NAMEFMT^XLFNAME(.MYNAME,"G") --> JOHN K. O'BRIEN JR $$NAMEFMT^XLFNAME(.MYNAME,"G","D") --> JOHN K. O'BRIEN JR PHD $$NAMEFMT^XLFNAME(.MYNAME,"G","Dc") --> JOHN K. O'BRIEN JR, PHD $$NAMEFMT^XLFNAME(.MYNAME,"G","P") --> MR. JOHN K. O'BRIEN JR $$NAMEFMT^XLFNAME(.MYNAME,"G","Xc") --> JOHN K. O'BRIEN, JR $$NAMEFMT^XLFNAME(.MYNAME,"G","PDcXc") --> MR. JOHN K. O'BRIEN, JR, PHD $$NAMEFMT^XLFNAME(.MYNAME,"G","PDcXcM") --> Mr. John K. O'Brien, Jr, PhD $$NAMEFMT^XLFNAME(.MYNAME,"G","S") --> JOHN K OBRIEN JR $$NAMEFMT^XLFNAME(.MYNAME,"G","SL12") --> JOH K OBRIEN $$NAMEFMT^XLFNAME(.MYNAME,"O") --> O'BRIEN $$NAMEFMT^XLFNAME(.MYNAME,"O","S") --> OBRIEN $$NAMEFMT^XLFNAME(.MYNAME,"O","M") --> O'Brien $$NAMEFMT^XLFNAME(.MYNAME,"O","L3") --> O'B 2. If an entry in the NAME COMPONENTS stores the components of a name stored in the NAME field (#.01) of record number 32 in the NEW PERSON file (#200), and the data in the corresponding record in the NAME COMPONENT file is: FILE = 200 FIELD = .01 IENS = "32," PREFIX = "MR." GIVEN NAME = "JOHN" MIDDLE NAME = "K." FAMILY NAME = "O'BRIEN" SUFFIX = "JR" DEGREE = "PHD" you can set: MYNAME("FILE") = 200 MYNAME("FIELD") = .01 MYNAME("IENS") = "32," and call $$NAMEFMT^XLFNAME as in Example 1, listed previously, to return the name in various formats. VARIABLES: NAME TYPE: Input VARIABLES DESCRIPTION: (Required) An array that contains the component parts of the name: NAME("FAMILY) = Family (Last) Name (required) NAME("GIVEN") = Given (First) Name(s) (optional) NAME("MIDDLE") = Middle Name(s) (optional) NAME("SUFFIX") = Suffix(es) (optional) NAME("PREFIX") = Prefix (optional) NAME("DEGREE") = Degree (optional) Alternatively, this array can contain the file number, IENS, and field number of the field that contains the name. If the name has a corresponding entry in the NAME COMPONENTS file (#20), then the name components are obtained from that entry. Otherwise, the name is obtained directly from the file, record, and field specified, and the name components are obtained by making a call to STDNAME^XLFNAME. NAME("FILE") = Source file number (required) NAME("IENS") = IENS of entry in the source file (required) NAME("FIELD") = Source field number (required) VARIABLES: FORMAT TYPE: Input VARIABLES DESCRIPTION: Controls the general formatting of the output. (Default = G) Possible values are: F - Return Family (Last) Name first G - Return Given (First) Name first O - Return Only the Family (Last) Name VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: Flags to controls processing. Possible values are: C - If the "F" format is used, return a Comma between the Family (Last) and Given (First) Names. Otherwise, the Family (Last) Name and the Given (First) Name are separated by a space. (Ignored if the "F" format is not used.) D - Return the Degree. Dc - Return the Degree preceded by a comma and space. L# - Truncate the returned name to a maximum Length of # characters, where # is an integer between 1 and 256. M - Return the name in Mixed case, with the first letter of each name component capitalized. P - Return the Prefix. S - Standardize the name components before building formatted name. Xc - Precede the SuffiX with a comma and space. COMPONENT/ENTRY POINT: $$BLDNAME(.NAME,MAX) COMPONENT DESCRIPTION: Build Name from Component Parts =============================== This extrinsic function takes the component parts of a name and returns the name, truncated if necessary, in the following format: Family_name,Given_nameMiddle_nameSuffix(es) Details: ------- If the MAX input parameter is used, and the resulting name is longer than MAX, the following pruning algorithm is performed to shorten the name: 1. Truncate Middle Name from the right-most position until only the initial character is left; 2. Drop suffix; 3. Truncate Given Name from the right-most position until only the initial character is left; 4. Truncate Family Name from the right-most position; 5. Truncate the name from the right. Examples: -------- 1. Suppose the MYNAME array contains the following elements: MYNAME("FAMILY") = "O'BRIEN" MYNAME("GIVEN") = "JOHN" MYNAME("MIDDLE") = "K." MYNAME("SUFFIX") = "JR" Calls to $$BLDNAME^XLFNAME will return the name as follows: $$BLDNAME^XLFNAME(.MYNAME) --> OBRIEN,JOHN K JR $$BLDNAME^XLFNAME(.MYNAME,12) --> OBRIEN,JOH K 2. If an entry in the NAME COMPONENTS stores the components of a name stored in the NAME field (#.01) of record number 32 in the NEW PERSON file, and the data in the corresponding record in the NAME COMPONENT file is: FILE = 200 FIELD = .01 IENS = "32," GIVEN NAME = "JOHN" MIDDLE NAME = "K." FAMILY NAME = "O'BRIEN" SUFFIX = "JR" you can set: MYNAME("FILE") = 200 MYNAME("FIELD") = .01 MYNAME("IENS") = "32," and call $$BLDNAME^XLFNAME as in Example 1, listed previously: $$BLDNAME^XLFNAME(.MYNAME) --> OBRIEN,JOHN K JR $$BLDNAME^XLFNAME(.MYNAME,12) --> OBRIEN,JOH K VARIABLES: NAME TYPE: Input VARIABLES DESCRIPTION: (Required) The component parts of the name: NAME("FAMILY") = Family (Last) Name NAME("GIVEN") = Given (First) Name(s) NAME("MIDDLE") = Middle Name(s) NAME("SUFFIX") = Suffix(es) Alternatively, this array can contain the file number, IENS, and field number of the file field that contains the name. If the name has a corresponding entry in the NAME COMPONENTS file, then the name components are obtained from that entry. Otherwise, the name is obtained directly from the file, record, and field specified, and the name components are obtained by making a call to STDNAME^XLFNAME. NAME("FILE") = Source file number (required) NAME("IENS") = IENS of entry in the source file (required) NAME("FIELD") = Source field number (required) VARIABLES: MAX TYPE: Input VARIABLES DESCRIPTION: The maximum length of the Name to be returned. (Default = 256) COMPONENT/ENTRY POINT: $$HLNAME([.]NAME,FLAGS,DELIM) COMPONENT DESCRIPTION: Convert Name to HL7 Formatted Name ================================== This extrinsic function converts a name to HL7 format. Details: ------- If the L# flag is used, and the resulting name is longer than #, the following pruning algorithm is performed to shorten the name: 1. Truncate Middle Name from the right-most position until only the initial character is left; 2. Drop suffix; 3. Truncate Given Name from the right-most position until only the initial character is left; 4. Truncate Family Name from the right-most position; 5. Truncate the name from the right. Examples: -------- 1. Suppose the MYNAME array contains the following elements: MYNAME("PREFIX") = "MR." MYNAME("GIVEN") = "JOHN" MYNAME("MIDDLE") = "K." MYNAME("FAMILY") = "O'BRIEN" MYNAME("SUFFIX") = "JR" MYNAME("DEGREE") = "PHD" Calls to $$HLNAME^XLFNAME will return the name as follows: $$HLNAME^XLFNAME(.MYNAME) --> O'BRIEN^JOHN^K.^JR^MR.^PHD $$HLNAME^XLFNAME(.MYNAME,"","~") --> O'BRIEN~JOHN~K.~JR~MR.~PHD $$HLNAME^XLFNAME(.MYNAME,"S","~") --> OBRIEN~JOHN~K~JR~MR~PHD $$HLNAME^XLFNAME(.MYNAME,"L12S") --> OBRIEN^JOH^K 2. If an entry in the NAME COMPONENTS stores the components of a name stored in the NAME field (#.01) of record number 32 in the NEW PERSON file, and the data in the corresponding record in the NAME COMPONENT file is: FILE = 200 FIELD = .01 IENS = "32," PREFIX = "MR." GIVEN NAME = "JOHN" MIDDLE NAME = "K." FAMILY NAME = "O'BRIEN" SUFFIX = "JR" DEGREE = "PHD" you can set: MYNAME("FILE") = 200 MYNAME("FIELD") = .01 MYNAME("IENS") = "32," and call $$HLNAME^XLFNAME as in Example 1, listed previously, to return the name in various formats. 3. Convert a name passed by value to HL7 format: $$HLNAME^XLFNAME("O'BRIEN,JOHN HOWARD II") --> O'BRIEN^JOHN^HOWARD^II $$HLNAME^XLFNAME("O'BRIEN,JOHN HOWARD II","S") --> OBRIEN^JOHN^HOWARD^II $$HLNAME^XLFNAME("O'BRIEN,JOHN HOWARD II","SL10","~") --> OBRIEN~J~H VARIABLES: NAME TYPE: Input VARIABLES DESCRIPTION: (Required) The component parts of the name to be converted: NAME("FAMILY) = Family (Last) Name (required) NAME("GIVEN") = Given (First) Name(s) (optional) NAME("MIDDLE") = Middle Name(s) (optional) NAME("SUFFIX") = Suffix(es) (optional) NAME("PREFIX") = Prefix (optional) NAME("DEGREE") = Degree (optional) Alternatively, this array can contain the file number, IENS, and field number of the file field that contains the name. If the name has a corresponding entry in the NAME COMPONENTS file (#20), then the name components are obtained from that entry. Otherwise, the name is obtained directly from the file, record, and field specified, and the name components are obtained by making a call to STDNAME^XLFNAME. NAME("FILE") = Source file number (required) NAME("IENS") = IENS of entry in the source file (required) NAME("FIELD") = Source field number (required) Another alternative is to pass in the unsubscripted NAME parameter the name to be converted. $$HLNAME^XLFNAME obtains the components parts of that name by making a call to STDNAME^XLFNAME. This alternative is recommended only for names that do not have associated entries on the NAME COMPONENTS file. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: Flags to controls processing. Possible values are: L# - Truncate the returned name to a maximum Length of # characters, where # is an integer between 1 and 256. S - Return the name components in the HL7 formatted name in Standardized form. VARIABLES: DELIM TYPE: Input VARIABLES DESCRIPTION: The delimiter to use in the HL7 string. (Default = "^") COMPONENT/ENTRY POINT: $$FMNAME(NAME,FLAGS,DELIM) COMPONENT DESCRIPTION: Convert HL7 Formatted Name to Name ================================== This extrinsic function converts an HL7 formatted name to a name in VISTA format. Details: ------- If the L# flag is used, and the resulting name is longer than #, the following pruning algorithm is performed to shorten the name: 1. Truncate Middle Name from the right-most position until only the initial character is left; 2. Drop suffix; 3. Truncate Given Name from the right-most position until only the initial character is left; 4. Truncate Family Name from the right-most position; 5. Truncate the name from the right. Examples: -------- 1. Convert an HL7 formatted name to a VISTA name: $$FMNAME^XLFNAME("O'BRIEN^JOHN^K.^JR^MR.^PHD") --> O'BRIEN,JOHN K. JR $$FMNAME^XLFNAME("O'BRIEN^JOHN^K.^JR^MR.^PHD","S") --> OBRIEN,JOHN K JR $$FMNAME^XLFNAME("O'BRIEN^JOHN^K.^JR^MR.^PHD","M") --> O'Brien,John K. Jr $$FMNAME^XLFNAME("O'BRIEN^JOHN^K.^JR^MR.^PHD","SL12") --> OBRIEN,JOH K 2. Convert an HL7 formatted name where "~" is the delimiter to a standard name: $$FMNAME^XLFNAME("O'BRIEN~JOHN~K.~JR~MR","S","~") --> OBRIEN,JOHN K JR 3. Convert an HL7 formatted name to a standard name, and return the components of that name in the MYNAME array: >S MYNAME="O'BRIEN^JOHN^K.^JR^MR.^PHD" >W $$FMNAME^XLFNAME(.MYNAME,"CS") OBRIEN,JOHN K JR >ZW MYNAME MYNAME=O'BRIEN^JOHN^K.^JR^MR.^PHD MYNAME("FAMILY")=O'BRIEN MYNAME("GIVEN")=JOHN MYNAME("MIDDLE")=K. MYNAME("SUFFIX")=JR VARIABLES: NAME TYPE: Both VARIABLES DESCRIPTION: (Required) NAME is the HL7 name to be converted. If the "C" flag is used, the name components are returned in nodes descendent from NAME. VARIABLES: FLAGS TYPE: Input VARIABLES DESCRIPTION: Flags to controls processing. Possible values are: C - Return name components in the NAME array. (See "Output:" just after this table.) L# - Truncate the returned name to a maximum Length of # characters, where # is an integer between 1 and 256. M - Return the name in Mixed case, with the first letter of each name component capitalized. S - Return the name in Standardized form. VARIABLES: DELIM TYPE: Input VARIABLES DESCRIPTION: The delimiter used in the HL7 formatted name. (Default = "^") NUMBER: 3066 IA #: 3066 DATE CREATED: MAR 15, 2000 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XLFNAME2 NAME: NAME COMPONENTS UPDATE ID: XLFNAME2 GENERAL DESCRIPTION: Controlled Subscription Name Standardization APIs. STATUS: Active MAIL MESSAGE: 34587243 KEYWORDS: NAME COMPONENTS KEYWORDS: XUNOTRIG KEYWORDS: 20 KEYWORDS: VA(20 COMPONENT/ENTRY POINT: UPDCOMP(FILE,[.]RECORD,FIELD,[.]NAME,PTRFIELD,PTRVAL,FMTF LAGS) COMPONENT DESCRIPTION: Update Name Components Entry ============================ This procedure updates an entry in the NAME COMPONENTS file. Optionally, the pointer in the source file that points to the name components entry is also updated. This API is designed to be used in the SET logic of a MUMPS cross-reference on the name field in a source file, to keep the name field and the associated name components in sync. For an example of its use, see the ANAME cross-reference in the NEW PERSON file (#200). The ANAME cross-reference is a MUMPS cross-reference with the .01 NAME field of the NEW PERSON file as its only cross-reference value. If an entry's NAME field is edited, the ANAME cross-reference updates the associated entry in the NAME COMPONENTS file. Note that existing MUMPS cross-references on the NAME COMPONENTS file already exist to update the associated name field on the source file if the components are edited. In the SET and KILL logic, you should check and set the variable XUNOTRIG as follows: I '$G(XUNOTRIG) N XUNOTRIG S XUNOTRIG=1 This prevents the ANAME cross-reference in the NAME COMPONENTS file from circularly updating the source name field. Example: ------- Suppose the .01 field of File #1000 contains a person's name, and the component parts of the name in entry 132 should be updated as follows: Family (last) name: O'BRIEN Given (first) name: JOHN HENRY Middle name: A. Suffix: JR. Field #1.1 is defined as a pointer to the NAME COMPONENTS file (#20) and has a value of 42, the IEN of a record in the NAME COMPONENTS file. To update the NAME COMPONENTS file with this name, you can do the following: >S MYNAME("FAMILY")="O'BRIEN" >S MYNAME("GIVEN")="JOHN HENRY" >S MYNAME("MIDDLE")="A." >S MYNAME("SUFFIX")="JR." >D UPDCOMP^XLFNAME2(1000,132,.01,.MYNAME,1.1,42) If there is an entry in the NAME COMPONENTS file that corresponds to File #1000, Field #.01, IEN #132, that entry is updated with the name components passed in the MYNAME array. Otherwise a new entry is added to the Name Components with this information. If the entry in the Name Components that was updated or added is record #42, no change is made to the value of the pointer field #1.1, since 42 was passed in the 6th parameter. MUMPS cross-references on the NAME COMPONENTS file updates the name in the Field #.01 of File #1000 to "OBRIEN,JOHN HENRY A JR" if it doesn't already contain that name. VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) The number of the file or subfile (the "source file") that contains the name. VARIABLES: RECORD TYPE: Input VARIABLES DESCRIPTION: (Required) The IENS or the internal entry number array (that looks like the DA array) of the record in the source file that contains the name. VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) The number of the field in the source file that contains the name. VARIABLES: NAME TYPE: Input VARIABLES DESCRIPTION: (Required) An array that contains the component parts of the name to store in the NAME COMPONENTS file entry: NAME("FAMILY) = Family Name (required) NAME("GIVEN") = Given Name(s) (optional) NAME("MIDDLE") = Middle Name(s) (optional) NAME("SUFFIX") = Suffix(es) (optional) NAME("PREFIX") = Prefix (optional) NAME("NOTES") = optional free text string Alternatively, a name in standard format can be passed in the NAME input parameter. If the NAME input parameter has no descendents (that is, $D(NAME)=1), UPDCOMP^XLFNAME2 will make a call to NAMECOMP^XLFNAME to build the NAME array for you. VARIABLES: PTRFIELD TYPE: Input VARIABLES DESCRIPTION: The number of the pointer field in the source file that points to the NAME COMPONENTS file. Only if this parameter is passed will the value of this pointer field be updated with the entry number of the record in the NAME COMPONENTS file that was added or edited. VARIABLES: PTRVAL TYPE: Input VARIABLES DESCRIPTION: The current value of the pointer field specified by the PTRFIELD input parameter. This parameter can be used to save processing time. If both PTRFIELD and PTRVAL are passed, the pointer field will be updated only if this value is different from the entry number of the record in the NAME COMPONENTS file that was added or edited. VARIABLES: FMTFLAGS TYPE: Input VARIABLES DESCRIPTION: This contents of this parameter, if passed, is filed into the SOURCE NAME FORMAT FLAGS (#7) field of the NAME COMPONENTS file. See the DESCRIPTION of field for more information. COMPONENT/ENTRY POINT: DELCOMP(FILE,[.]RECORD,FIELD,PTRFIELD) COMPONENT DESCRIPTION: Delete Name Components Entry ============================ This procedure deletes an entry in the NAME COMPONENTS file, and optionally, the value of the pointer in the source file that points to the name components entry. (This call is designed to be used in the KILL logic for the MUMPS cross-reference mentioned in the description of UPDCOMP^XLFNAME2.) Example: ------- Suppose that you have a NAME COMPONENTS file entry that contains the components of a name stored in File #1000, Record #132, Field #.01. Pointer field #1.1 of that File #1000 is a pointer to the NAME COMPONENTS file. To delete the entry in the NAME COMPONENTS file, and the value of the pointer field, you can do the following: >D DELCOMP^XLFNAME(1000,132,.01,1.1) VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: (Required) The number of the file or subfile (the "source file") that contains the name. VARIABLES: RECORD TYPE: Input VARIABLES DESCRIPTION: (Required) The IENS or the internal entry number array (that looks like the DA array) of the record in the source file that contains the name. VARIABLES: FIELD TYPE: Input VARIABLES DESCRIPTION: (Required) The number of the field in the source file that contains the name. VARIABLES: PTRFIELD TYPE: Input VARIABLES DESCRIPTION: The number of the pointer field in the source file that points to the NAME COMPONENTS file. Only if this parameter is passed will the value of this pointer field be deleted. SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH ISC: Albany SUBSCRIBING DETAILS: Used with HEC'S MASTER CLIENT file 300.12 SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 3067 IA #: 3067 FILE NUMBER: 123 GLOBAL ROOT: GMR(123, DATE CREATED: MAR 16, 2000 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DISPLAY CONSULT PROCEDURE ORDER INFO ID: GMR(123, CREATOR: THOMPSON,WILLIAM ANTHONY GLOBAL REFERENCE: GMR(123, FIELD NUMBER: 5 FIELD NAME: URGENCY LOCATION: 0;9 ACCESS: Read w/Fileman FIELD NUMBER: 20 FIELD NAME: REASON FOR REQUEST LOCATION: 20;0 ACCESS: Read w/Fileman FIELD NUMBER: 30.1 FIELD NAME: PROVISIONAL DIAGNOSIS LOCATION: 30.1;1 ACCESS: Read w/Fileman FIELD NUMBER: 8 FIELD NAME: CPRS STATUS LOCATION: 0;12 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: PROCEDURE/REQUEST TYPE LOCATION: 0;8 ACCESS: Read w/Fileman FIELD NUMBER: 13 FIELD NAME: REQUEST TYPE LOCATION: 0;17 ACCESS: Read w/Fileman FIELD NUMBER: .04 FIELD NAME: PATIENT LOCATION LOCATION: 0;4 ACCESS: Read w/Fileman GLOBAL REFERENCE: GMR(123,D0,50, FIELD NUMBER: .01 FIELD NAME: ASSOCIATED RESULTS LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: PURPOSE: Provide Clinical Procedures with a way to display Consult Procedure order information. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31012221 SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Hines DBA Comments: 7/22/2008 - CHANGED DBIA NAME AND ADDED FIELD .04 PATIENT LOCATION TO ICR. DATE ACTIVATED: JUL 22, 2008 DATE/TIME EDITED: JUL 22, 2008@15:57 ACTION: CONTENT CORRECTED AT THE REQUEST OF: ACKERMAN,SHIRLEY NUMBER: 3068 IA #: 3068 DATE CREATED: MAR 22, 2000 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA3068 GENERAL DESCRIPTION: The Primary Care Management Module (PCMM) in Scheduling requests permission to update the 'PCMM' entry in the HL7 APPLICATION PARAMETER (#771) file. The following action will be performed during the post initialization process of patch SD*5.3*210: 1. The Name (#.01) field of this entry will be changed from 'PCMM' to 'PCMM-210'. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31090820 SUBSCRIBING PACKAGE: SCHEDULING NUMBER: 3070 IA #: 3070 DATE CREATED: MAR 22, 2000 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SCAPMC NAME: SCAPMC Clinic List ID: SCAPMC STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31043759 KEYWORDS: CLINIC KEYWORDS: ENROLLMENT KEYWORDS: ORLP KEYWORDS: ORLP2 COMPONENT/ENTRY POINT: PTCL COMPONENT DESCRIPTION: List of patients for a clinic. VARIABLES: SC44 TYPE: Input VARIABLES DESCRIPTION: Pointer to Hospital Location file #44. VARIABLES: SCDATES TYPE: Input VARIABLES DESCRIPTION: Date array (begin, end, incl). VARIABLES: SCLIST TYPE: Both VARIABLES DESCRIPTION: Name of output array. Array of practitioners (users) - pointers to file #200. If not defined, ^TMP("SC TMP LIST",$J, gets used. May be killed before and after calling. VARIABLES: SCERR TYPE: Both VARIABLES DESCRIPTION: Array NAME to store error messages [ex. ^TMP("ORXX",$J]. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: Team Lists use the call to $$PTCL^SCAPMC to retrieve lists of enrolled patients in clinics. NUMBER: 3071 IA #: 3071 DATE CREATED: MAR 22, 2000 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORX8 NAME: ORX8 ID: ORX8 GENERAL DESCRIPTION: This documents the function $$PKGID^ORX8(ORIFN), which returns a package's order number or identifier given the CPRS order number. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31045038 KEYWORDS: $$PKGID COMPONENT/ENTRY POINT: $$PKGID(ORIFN) COMPONENT DESCRIPTION: Returns the package's order number or identifier for an order VARIABLES: ORIFN TYPE: Input VARIABLES DESCRIPTION: The IEN of the ORDER file (#100) VARIABLES: Result TYPE: Output VARIABLES DESCRIPTION: The result of the extrinsic function is a string as defined by the package that identifies the order in the ancillary package files. SUBSCRIBING PACKAGE: PROSTHETICS ISC: Hines SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING DETAILS: CP ADDED 7/9/07 SUBSCRIBING PACKAGE: HEALTH SUMMARY SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: Effective with VPR*1*0. DBA Comments: 8/17/12-MM: Added Health Summary as subscriber to ICR #3071 for GMTS*2.7*94. 8/02/13 DT: Add VPR as subscriber, effective with VPR*1*0. Melanie Buechler represents OR and VPR. DATE/TIME EDITED: JUL 09, 2007@17:16 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: ACKERMAN,SHIRLEY WITH CONCURRENCE OF: BUECHLER,MELANIE DATE/TIME EDITED: AUG 17, 2012@16:03 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SILVERMAN,ROB WITH CONCURRENCE OF: MALMROSE,CARY DATE/TIME EDITED: AUG 17, 2012@16:04 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SILVERMAN,ROB WITH CONCURRENCE OF: BUECHLER,MELANIE DATE/TIME EDITED: AUG 02, 2013@13:10 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: BUECHLER,MELANIE NUMBER: 3072 IA #: 3072 DATE CREATED: MAR 31, 2000 CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MPIF001 NAME: Return new or existing ICN ID: MPIF001 GENERAL DESCRIPTION: This API will return an ICN if one exists or create and return a Local ICN and updating the appropriate fileds if a Local was created. STATUS: Active MAIL MESSAGE: 31086062 COMPONENT/ENTRY POINT: $$ICNLC(DFN) COMPONENT DESCRIPTION: DFN is the IEN from the Patient (#2) file for that patient that the ICN is to be returned on. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN= Patient IEN VARIABLES: $$ICNLC TYPE: Output VARIABLES DESCRIPTION: Returns ICN (local or National including checksum) OR -1^ error message -- couldn't create local or that patient is a test patient with 5 leading 0s for SSN or has been ZZ'd. SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING DETAILS: Registration uses this call to get an ICN local or national to be passed in an HL7 message. SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: person.lookup SUBSCRIBING DETAILS: Person Service Lookup calls ICNLC^MPIF001 to retrieve a patient's national or local ICN or create a local ICN for a patient when a national or local ICN is not found. JSHARVEY 20061128/ADDED PSL AS A NEW SUBSCRIBER AS PER D. REED DBA Comments: JSHARVEY 20061128/DEACTIVATED FOR MARKS TO EDIT DESCRIPTION. JSHARVEY 20061204/RE-ACTIVATED FOR MARKS AS PER REED. DATE/TIME EDITED: DEC 04, 2006@09:09 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MARKS,MARY WITH CONCURRENCE OF: REED,DANNY NUMBER: 3073 IA #: 3073 DATE CREATED: APR 04, 2000 CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RGADT2 NAME: determine the LAST TREATMENT DATE for a patient ID: RGADT2 GENERAL DESCRIPTION: This Integration Agreement (IA) will allow an application to determine the LAST TREATMENT DATE for a single patient. The events that define treatment are: patient admissions, patient discharges and clinic checkouts. This subroutine will trigger Master File Update (MFU) messages that update the DATE LAST TREATED (#.07) field for the TREATING FACILITY LIST (#391.91) file. The CIRN Master of Record (CMOR) and subscribers will have their TREATING FACILITY LIST files updated. VIEWER: DAVIS,PAULETTE VIEWER: WARREN,BRENDA A VIEWER: HERREN,CATHRYN VIEWER: REED,DANNY STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31105045 KEYWORDS: TREATMENT DATE KEYWORDS: SEEDING PROCESS KEYWORDS: DATE LAST TREATED KEYWORDS: RG*1.0*4 COMPONENT/ENTRY POINT: EN1 VARIABLES: RGDFN TYPE: Input VARIABLES DESCRIPTION: The internal entry number (ien) of the patient in the PATIENT (#2) file. Patient ien is also referred to as the patient's dfn. VARIABLES: RGSUP TYPE: Input VARIABLES DESCRIPTION: This is a boolean, if not true then a TREATING FACILTY UPDATES Type of Event is added to the ADT/HL7 PIVOT (#391.71) file. If true, the add is suppressed. SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 3074 IA #: 3074 FILE NUMBER: 75.1 GLOBAL ROOT: RAO(75.1, DATE CREATED: APR 05, 2000 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: RAD/NUC MED ORDERS FILE W/PROC. MODS ID: RAO(75.1, CREATOR: CEBELINSKI,GREGORY GLOBAL REFERENCE: RAO(75.1,D0,0 FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: The name of the patient. FIELD NUMBER: 2 FIELD NAME: PROCEDURE LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field points to the 'RAD/NUC MED PROCEDURES' file (#71) to indicate the imaging procedure associated to the patient. FIELD NUMBER: 5 FIELD NAME: REQUEST STATUS LOCATION: 0;5 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field is a set type field and corresponds to the OE/RR 'ORDER STATUS' file (#100.01). FIELD NUMBER: 6 FIELD NAME: REQUEST URGENCY LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The urgency of the request; '1' for STAT, '2' for URGENT, '9' for ROUTINE. FIELD NUMBER: 12 FIELD NAME: PRE-OP SCHEDULED DATE LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The date/time if a patient has a pre-op scheduled. FIELD NUMBER: 13 FIELD NAME: PREGNANT LOCATION: 0;13 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Pregnancy status of patient. (Yes,No,Unknown) FIELD NUMBER: 16 FIELD NAME: REQUEST ENTERED DATE LOCATION: 0;16 ACCESS: Read w/Fileman FIELD DESCRIPTION: The date and time the request was entered. FIELD NUMBER: 20 FIELD NAME: IMAGING LOCATION LOCATION: 0;20 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: The imaging location for the study. GLOBAL DESCRIPTION: The data for 'RAD/NUC MED ORDERS' file is stored in the ^RAO(75.1,global.. GLOBAL REFERENCE: RAO(75.1,D0,.1 FIELD NUMBER: 1.1 FIELD NAME: REASON FOR STUDY LOCATION: .1;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: The reason for the study is often a short patient history summarizing the condition of the patient and giving background information as to why the study has been initiated. GLOBAL REFERENCE: RAO(75.1,DO,'M',D1,0 FIELD NUMBER: .01 FIELD NAME: PROCEDURE MODIFIERS LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This multiple field is used to provide rad/nuc med procedure modifiers for the exam. GENERAL DESCRIPTION: The following fields are being read from and written to by subscribers to obtain and update patient specific radiology order data. Please look carefully at the fields documented below to determine which can be read from and written to. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31110908 KEYWORDS: MAGDRPCB KEYWORDS: outside orders KEYWORDS: IMAGING KEYWORDS: VPS KEYWORDS: KIOSKS SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Radiology gives Imaging permission to read the PREGNANT field (#13) in the RAD/NUC MED ORDERS file (75.1). Information will be sent in DICOM format messages to commercial PACS, modality worklists for commercial gateways or individual modalities. Radiology also gives Imaging permission to read additional fields to be used during the importing of 'outside' images. SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) SUBSCRIBING DETAILS: The VistA RADIOLOGY/NUCLEAR MEDICINE (RA) application version 5.0 allows the VA POINT OF SERVICE (KIOSKS) application access to the RAD/NUC MED ORDERS (#75.1) file. EDITOR: KUZMAK,PETER DBA Comments: 10/22/14-MC: VPS added as a subscriber to the ICR by custodial reviewer, Greg Cebelinski. ICR status previously was "under revision" for over a year. Greg reviewed ICR, updated name so that it was not specific to Imaging, and updated details when adding VPS as a subscriber. ICR activated for VPS. DATE ACTIVATED: OCT 22, 2014 DATE/TIME EDITED: MAR 04, 2007@22:51 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CEBELINSKI,GREG DATE/TIME EDITED: MAR 05, 2007@08:00 ACTION: APPROVED AT THE REQUEST OF: CEBELINSKI,GREG DATE/TIME EDITED: NOV 30, 2009@10:02 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: BARRIOS,LUCILLE DATE/TIME EDITED: JAN 19, 2010@10:10 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CEBELINSKI,GREG DATE/TIME EDITED: OCT 22, 2014@15:55 ACTION: APPROVED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: CEBELINSKI,GREGORY REMINDER: MAR 08, 2007 NUMBER: 3076 IA #: 3076 DATE CREATED: APR 13, 2000 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: ORQQPX SEARCH ITEMS GENERAL DESCRIPTION: Read access to the XPAR Parameter ORQQPX SEARCH ITEMS. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31148548 SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3078 IA #: 3078 DATE CREATED: APR 11, 2000 CUSTODIAL PACKAGE: CLINICAL REMINDERS CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRMRPCA NAME: DBIA3078 ID: PXRMRPCA GENERAL DESCRIPTION: These are the entry points for the PXRMRPCA routine: 1) ALIST^PXRMRPCA(.ORY,ORPT,.LIST) - Evaluate a list of reminders 2) APPL^PXRMRPCA(.ORY,ORPT,.LIST) - Evaluate reminders for CPRS cover sheet 3) CATEGORY^PXRMRPCA(.ORY,ORPT,ORLOC) - List of categories 4) LIST^PXRMRPCA(.ORY,ORPT,ORLOC) - List of reminders (unevaluated) 5) REMDET^PXRMRPCA(..ORY,ORPT,ORREM) - Clinical Maintenance display 6) WEB^PXRMRPCA(.ORY,ORREM) - Web sites for a reminder Output is returned in ORY array STATUS: Active MAIL MESSAGE: 31143723 KEYWORDS: PXRMRPCA COMPONENT/ENTRY POINT: ALIST COMPONENT DESCRIPTION: ALIST^PXRMRPCA(.ORY,ORPT.LIST) - Evaluate a list of reminders for a patient Allows evaluation of a list of reminders. Returns a list of clinical reminders due/applicable or not applicable to the patient. INPUT: ORPT Patient identifier from the patient file [#2] INPUT: LIST List of reminders in format : LIST(1) = reminder ien1 (from #811.9) LIST(2) = reminder ien2 etc OUTPUT: ORY List of reminders in format: ORY(CNT)=IEN^PRINT NAME^DUE DATE/TIME^LAST OCCURRENCE DATE/TIME^PRIORITY^DUE DUE=0 - Applicable DUE=1 - Due DUE=2 - Not Applicable COMPONENT/ENTRY POINT: APPL COMPONENT DESCRIPTION: APPL^PXRMRPCA(.ORY,ORPT,.LIST) - Evaluate reminders for CPRS cover sheet Returns a list of clinical reminders due/applicable or not applicable to the patient. INPUT: ORPT Patient identifier from the patient file [#2] INPUT: LIST List of reminders in format : LIST(1) = reminder ien1 (from #811.9) LIST(2) = reminder ien2 etc OUTPUT: ORY List of reminders in format: ORY(CNT)=IEN^PRINT NAME^DUE DATE/TIME^LAST OCCURRENCE DATE/TIME^PRIORITY^DUE DUE=0 - Applicable DUE=1 - Due COMPONENT/ENTRY POINT: CATEGORY COMPONENT DESCRIPTION: CATEGORY^PXRMRPCA(.ORY,ORPT,ORLOC) - List of categories Returns list of all CPRS lookup categories and associated reminders INPUT: ORPT Patient Identifier from Patient file [#2] INPUT: ORLOC Patient's HOSPITAL LOCATION [#44]. May be null. OUTPUT: ORY Returns array of categories and reminders based on CPRS lookup categories for this patient service/location. FORMAT OF OUTPUT ORY(1)=identifier^type^name^parent identifier^reminder ien ORY(2)=identifier^type^name^parent identifier^reminder ien type C = category R = reminder COMPONENT/ENTRY POINT: REMDET COMPONENT DESCRIPTION: REMDET^PXRMRPCA(..ORY,ORPT,ORREM) - Clinical Maintenance display Returns the details of a clinical reminder for a patient INPUT: ORPT Patient identifier from Patient file [#2] INPUT: ORREM Clinical reminder (ien) from CLINICAL REMINDER DEFINITION file [#811.9] OUTPUT: ORY Formatted details of the clinical reminder ORY(1)=text ORY(2)=text COMPONENT/ENTRY POINT: WEB COMPONENT DESCRIPTION: WEB^PXRMRPCA(.ORY,ORREM) - Web sites for a reminder Web addresses for selected reminder INPUT: ORREM Clinical reminder (ien) from CLINICAL REMINDER DEFINITION file [#811.9] OUTPUT: ORY Formatted list of web addresses ORY(1)=description^address E.G. ORY(0)=4 ORY(1)=Influenza Directive^http://www.va.gov/publ/direct/194026.htm ORY(2)=Medical Home Pages^http://www.va.gov/bookmark/Medhome.htm ORY(3)=National Guideline Clearinghouse^http://www.guideline.com ORY(4)=VISN01 Web Page^http://vaww.visn1.med.va.gov COMPONENT/ENTRY POINT: LIST COMPONENT DESCRIPTION: LIST^PXRMRPCA(.ORY,ORPT,ORLOC) - List of reminders (unevaluated) Returns list of CPRS reminders for patient/location (no evaluation is done) INPUT: ORPT Patient identifier from the patient file [#2] INPUT: ORLOC Patients location from HOSPITAL LOCATION [#44]. May be null OUTPUT: ORY List of reminder iens [#811.9]. ORY(1)=ien1 ORY(2)=ien2 COMPONENT/ENTRY POINT: $$DLG(IEN) COMPONENT DESCRIPTION: Determine if the Reminder has a Reminder dialog associated with the reminders and the dialog is not disabled. If the reminder has an active dialog assigned to it a value of 1 is return. If the reminder does not have a dialog assign to it or if the dialog is disabled the then a value of 0 is returned. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: the IEN of the Reminder definition from file #811.9 VARIABLES: $$DLG TYPE: Output VARIABLES DESCRIPTION: 0 == if the reminder does no have a dialog assigned or is disabled. 1 == if the reminder has an active dialog assigned. COMPONENT/ENTRY POINT: $$DLGWIPE(IEN) COMPONENT DESCRIPTION: Check to see if the reminder has an associated dialog. If it does then it checks to see if field #112 (Patient Specific) of file 801.41 is set to true, if so the function returns a value of 1. If the reminder does not have an associated dialog or if the field #112 (Patient Specific) is not set to true then the function returns a value of 0. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: the IEN of the Reminder definition from file #811.9 VARIABLES: $$DLGWIPE TYPE: Output VARIABLES DESCRIPTION: 0 == if the reminder does not have an associated dialog or if the field #112 (Patient Specific) of file 801.41 is false. 1 == if the reminder has an associated dialog and if field #112 is set to true. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: Calls to PXRMRPCA NUMBER: 3079 IA #: 3079 DATE CREATED: APR 11, 2000 CUSTODIAL PACKAGE: CLINICAL REMINDERS CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRMRPCB NAME: DBIA3079 ID: PXRMRPCB GENERAL DESCRIPTION: These are the entry points for the PXRMRPCB routine: 1) EDL^PXRMRPCB(.ORY,ORREM) - List education topics for a reminder 2) EDS^PXRMRPCB(.ORY,OREDU) - List sub-topics for an education topic 3) EDU^PXRMRPCB(.ORY,OREDU) - Display an education topic Output is returned in ORY array STATUS: Active MAIL MESSAGE: 31143727 KEYWORDS: PXRMRPCB COMPONENT/ENTRY POINT: EDL COMPONENT DESCRIPTION: EDL^PXRMRPCB(.ORY,ORREM) - List education topics for a reminder INPUT: ORREM Clinical reminder (ien) from CLINICAL REMINDER DEFINITION file [#811.9] OUTPUT: ORY List of education topics for this reminder in format ORY(1)=ien1^name1^print name1 ORY(2)=ien2^name2^print name2 COMPONENT/ENTRY POINT: EDS COMPONENT DESCRIPTION: EDS^PXRMRPCB(.ORY,OREDU) - List sub-topics for an education topic INPUT: OREDU Education topic (ien) from EDUCATION TOPIC file [#9999999.09] OUTPUT: ORY List of education sub-topics in format: ORY(1) = ien1^name1^print name1^sequence number1 ORY(2) = ien2^name2^print name2^sequence number2 COMPONENT/ENTRY POINT: EDU COMPONENT DESCRIPTION: EDU^PXRMRPCB(.ORY,OREDU) - Display an education topic INPUT: OREDU Education topic (ien) from EDUCATION TOPIC file [#9999999.09] OUTPUT: ORY Detailed description of education topic as formatted text ORY(1) = Display text line 1 ORY(2) = Display text line 2 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: Calls to PXRMRPCB NUMBER: 3080 IA #: 3080 DATE CREATED: APR 11, 2000 CUSTODIAL PACKAGE: CLINICAL REMINDERS CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRMRPCC NAME: CPRS REMOTE PROCEDURE CALLS ID: PXRMRPCC CREATOR: RUFF,ROBERT F GENERAL DESCRIPTION: These are the entry points for routine PXRMRPCC: 1) ACTIVE^PXRMRPCC(.ORY,.LIST) - List active dialogs for selected reminders 2) DIALOG^PXRMRPCC(.ORY,ORREM) - Load a reminder dialog 3) HDR^PXRMRPCC(.ORY,ORLOC)- Progress Note Header by location/service/user 4) MH^PXRMRPCC(.ORY,ORTEST) - Load MH test details 5) MHR^PXRMRPCC(.ORY,ORMHR,.ORES) - Get MH test score and result (P/N text) 6) MHS^PXRMRPCC(.ORY,.ORES) - Save MH test results to MH package 7) MST^PXRMRPCC(.ORY,ORPT,ORDATE,ORSTAT,ORPROV,ORFTYP,ORFIEN,ORRES) - Update MST 8) PROMPT^PXRMRPCC(.ORY,ORDLG,ORDCUR,ORFTYP,ORIEN) - Load additional prompts 9) RES^PXRMRPCC(.ORY,ORREM) - Display reminder inquiry 10) WH^PXRMRPCC(.ORY,ORRESULT) - Save WH Exam Results to the WV package 11) PROMPTVL^PXRMRPCC(.ORY,VALUE,DIEN,LITEM,LTYPE,OVALUE) - Calculate prompt value Output is returned in the ORY array STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31143745 KEYWORDS: PXRMRPCC COMPONENT/ENTRY POINT: ACTIVE COMPONENT DESCRIPTION: ACTIVE^PXRMRPCC(.ORY,.LIST) - List active dialogs for selected reminders For a list of reminders [#811.9] returns same list with status to indicate if an active dialog exists for the reminder. INPUT: LIST List of reminders in format : LIST(1) = reminder ien1 (from #811.9) LIST(2) = reminder ien2 OUTPUT: ORY Array of clinical reminders in format ORY(1)=Reminder_U_Status ORY(2)=Reminder_U_Status Where status: 0 - No active dialog 1 - Active dialog COMPONENT/ENTRY POINT: DIALOG COMPONENT DESCRIPTION: DIALOG^PXRMRPCC(.ORY,ORREM) - Load a reminder dialog Dialog for a given reminder INPUT: ORREM Clinical reminder (ien) from CLINICAL REMINDER DEFINITION file [#811.9] OUTPUT: ORY For each dialog item in the reminder dialog for the reminder : Type 1 records - Initial states 1^dialog item ien[#801.41]^dialog ien [#801.412]^^^^ Type 2 records - Question text 2^dialog item ien[#801.41]^dialog ien [#801.412]^text COMPONENT/ENTRY POINT: MH COMPONENT DESCRIPTION: MH^PXRMRPCC(.ORY,ORTEST) - Load MH test details Returns array for given mental health instrument INPUT: ORTEST Name of the mental health instrument OUTPUT: ORY Returns array of mental health instrument questions/answers (variable format) COMPONENT/ENTRY POINT: MHR COMPONENT DESCRIPTION: MHR^PXRMRPCC(.ORY,ORMHR,.ORES) - Get MH test score and result (P/N text) Returns progress note text based on the results of the test. INPUT: ORMHR This is the pointer to the result group for the test [#801.41,.01]. INPUT: ORES Test results in YS array format(R1,R2,DFN,DUZ,ADATE etc). OUTPUT: ORY Returns array of progress note text as multiple type 7 records. COMPONENT/ENTRY POINT: MHS COMPONENT DESCRIPTION: MHS^PXRMRPCC(.ORY,.ORES) - Save MH test results to MH package Stores test result responses from a reminder dialog. INPUT: ORES Test results in YS array format(R1,R2,DFN,DUZ,ADATE etc). OUTPUT: ORY Returns either [DATA]saved ok or -1^[ERROR]description of error COMPONENT/ENTRY POINT: PROMPT COMPONENT DESCRIPTION: PROMPT^PXRMRPCC(.ORY,ORDLG,ORDCUR,ORFTYP,ORIEN) - Load additional prompts Additional prompts for a given dialog element INPUT: ORDLG Reminder dialog element identifier (ien) from REMINDER DIALOG file [#801.41] INPUT: ORCUR Used only for taxonomy dialogs. 0 - Current Diagnosis/Procedure 1 - Historical Diagnosis/Procedure INPUT: ORFTYP For taxonomy dialog the type of finding (POV/CPT) for this dialog line INPUT: ORIEN Reminder dialog identifier (IEN) from REMINDER DIALOG file [#801.41] of the dialog that contains the element identified in parameter ORDLG. OUTPUT: ORY For a selected dialog element type 3 - Resolutions 3^dialog item ien[#801.41]^line id^resolution type code^ien[#various] type 4 - Additional prompts 4^dialog item ien[#801.41]^line id^prompt text type 5 - Listbox items (cpt/pov) 5^dialog item ien[#801.41]^line id^cpt/pov ien^code/desc COMPONENT/ENTRY POINT: RES COMPONENT DESCRIPTION: RES^PXRMRPCC(.ORY,ORREM) - Display reminder inquiry INPUT: ORREM Clinical reminder (ien) from CLINICAL REMINDER DEFINITION file [#811.9] OUTPUT: ORY Detailed description of clinical reminder as formatted text ORY(1) = Display text line 1 ORY(2) = Display text line 2 ORY(3) = etc COMPONENT/ENTRY POINT: MST COMPONENT DESCRIPTION: MST^PXRMRPCC(ORY,ORPT,ORDATE,ORSTAT,ORPROV,ORFTYP,ORFIEN,ORRES) - update MST from reminder dialog. INPUT: ORPT Patient DFN INPUT: ORDATE Date/time of encounter INPUT: ORSTAT MST status code (Y, N or D) - Null if finding is an exam INPUT: ORPROV Primary provider IEN INPUT: ORFTYP Finding type code (from PCE) INPUT: ORFIEN Finding IEN INPUT: ORRES Exam result - Optional. Only required for EXAM type findings OUTPUT: ORY ORY(1) = IEN - successfull update of MST or ORY(1) = -1^ERROR MESSAGE - failure to update and reason COMPONENT/ENTRY POINT: HDR COMPONENT DESCRIPTION: Returned the PXRM Progress Note Header by location/service/user VARIABLES: ORY TYPE: Output VARIABLES DESCRIPTION: Returned the PXRM Progress Note Header to CPRS. VARIABLES: ORLOC TYPE: Input VARIABLES DESCRIPTION: ORLOC is the Hospital Location. COMPONENT/ENTRY POINT: WH COMPONENT DESCRIPTION: This entry point will format the data received from CPRS. Once the data is format this entry point will send the data to the WH package. VARIABLES: ORY TYPE: Output VARIABLES: ORRESULT TYPE: Input VARIABLES DESCRIPTION: ORRESULT is an array containing the unformatted WH Result data from CPRS. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: Calls to PXRMRPCC EDITOR: RUFF,ROBERT F DBA Comments: 7/11/14 DT: Added Robert Ruff as editor to add a new entry point for patch PXRM*2*45, which will be released with CPRS GUI version 31 (estimated release date is June 2015). DATE/TIME EDITED: JUL 11, 2014@11:32 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: RUFF,ROBERT WITH CONCURRENCE OF: RUFF,ROBERT NUMBER: 3081 IA #: 3081 DATE CREATED: APR 12, 2000 CUSTODIAL PACKAGE: CLINICAL REMINDERS CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA3081 GENERAL DESCRIPTION: Read access to the following XPAR Parameter Definitions: PXRM GUI REMINDERS ACTIVE PXRM MENTAL HEALTH ACTIVE STATUS: Active MAIL MESSAGE: 31144726 KEYWORDS: PXRM REMINDERS ACTIVE KEYWORDS: PXRM MENTAL HEALTH ACTIVE KEYWORDS: PXRM PARAMETERS SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: Calls to $$GET^XPAR are allowed NUMBER: 3082 IA #: 3082 DATE CREATED: APR 17, 2000 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: PROTOCOL Distribution GENERAL DESCRIPTION: Clinical Information Resource Network (CIRN) is establishing this integration agreement to include the following Registration PROTOCOLS in CIRN builds, distributed as MERGE MENU ITEMS. The purpose of including these event driver PROTOCOLS is to attach our subscriber PROTOCOLS that are exported in the build. Registration event driver PROTOCOLS CIRN subscriber PROTOCOLS ------------------------------------------------ VAFC ADT-A04 SERVER RG ADT-A04 TRIGGER VAFC ADT-A08 SERVER RG ADT-A08 TRIGGER STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31152766 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham NUMBER: 3083 IA #: 3083 FILE NUMBER: 9999999.64 GLOBAL ROOT: AUTTHF( DATE CREATED: MAY 19, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3083 ID: AUTTHF( GLOBAL REFERENCE: AUTTHF( FIELD NUMBER: .01 FIELD NAME: FACTOR LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .03 FIELD NAME: CATEGORY LOCATION: 0;3 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .04 FIELD NAME: SHORT NAME LOCATION: 0;4 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .05 FIELD NAME: USE ONLY WITH SEX LOCATION: 0;5 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .06 FIELD NAME: LOWER AGE LOCATION: 0;6 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .07 FIELD NAME: UPPER AGE LOCATION: 0;7 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .08 FIELD NAME: DISPLAY ON HEALTH SUMMARY LOCATION: 0;8 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .09 FIELD NAME: SYNONYM LOCATION: 0;9 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .1 FIELD NAME: ENTRY TYPE LOCATION: 0;10 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .11 FIELD NAME: INACTIVE FLAG LOCATION: 0;11 ACCESS: Direct Global R/W & w/Fileman GLOBAL REFERENCE: AUTTHF(D0,11, FIELD NUMBER: .01 FIELD NAME: NOT USED WITH LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman GLOBAL REFERENCE: AUTTHF("B", GLOBAL DESCRIPTION: Direct global read access permitted. GLOBAL REFERENCE: AUTTHF("D", GLOBAL DESCRIPTION: Direct global read access permitted. GENERAL DESCRIPTION: Health Factors are used as a finding in Clinical Reminders. The Clinical Reminder Exchange Utility allows sites to exchange Clinical Reminder definitions and all the associated components. Therefore Clinical Reminders needs to read and write all fields in the file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31336105 KEYWORDS: HEALTH FACTORS KEYWORDS: CLINICAL REMINDERS SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3084 IA #: 3084 FILE NUMBER: 9000010.23 GLOBAL ROOT: AUPNVHF( DATE CREATED: MAY 16, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3084 ID: AUPNVHF( CREATOR: CORONA,JOSE GLOBAL REFERENCE: AUPNVHF('AA', GLOBAL REFERENCE: AUPNVHF(D0,0) FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: LEVEL/SEVERITY LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .01 FIELD NAME: HEALTH FACTOR LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: AUPNVHF('C', GLOBAL REFERENCE: AUPNVHF('AED', GENERAL DESCRIPTION: Health Factors are used as a finding in Clinical Reminders. Therefore Clinical Reminders needs to read the following fields. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31319116 KEYWORDS: CLINICAL REMINDERS KEYWORDS: V HEALTH FACTORS SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM SUBSCRIBING DETAILS: ADDED 6/8/09 DBA Comments: 20090608/ ADDED DATA FIELD .01 Health Factor DATE ACTIVATED: JUN 08, 2009 DATE/TIME EDITED: JUN 08, 2009@17:41 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SWESKY,JEFF WITH CONCURRENCE OF: CORONA,JOSE DATE/TIME EDITED: JUN 08, 2009@17:42 ACTION: USAGE CHOICE CHANGED AT THE REQUEST OF: SWESKY,JEFF WITH CONCURRENCE OF: CORONA,JOSE DATE/TIME EDITED: JUN 08, 2009@17:44 ACTION: CONTENT CORRECTED AT THE REQUEST OF: SWESKY,JEFF WITH CONCURRENCE OF: CORONA,JOSE NUMBER: 3085 IA #: 3085 FILE NUMBER: 9999999.09 GLOBAL ROOT: AUTTEDT( DATE CREATED: MAY 19, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3085 ID: AUTTEDT( GLOBAL REFERENCE: AUTTEDT(D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .04 FIELD NAME: PRINT NAME LOCATION: 0;4 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .03 FIELD NAME: INACTIVE FLAG LOCATION: 0;3 ACCESS: Direct Global R/W & w/Fileman GLOBAL REFERENCE: AUTTEDT(D0,10) FIELD NUMBER: .01 FIELD NAME: SUBTOPIC LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 3 FIELD NAME: SEQUENCE LOCATION: 0;3 ACCESS: Direct Global R/W & w/Fileman GLOBAL REFERENCE: AUTTEDT(D0,11) FIELD NUMBER: .01 FIELD NAME: EDUCATIONAL OUTCOME LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman GLOBAL REFERENCE: AUTTEDT(D0,12) FIELD NUMBER: .01 FIELD NAME: EDUCATIONAL STANDARDS LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman GENERAL DESCRIPTION: Education Topics are used as a finding in Clinical Reminders. The Clinical Reminder Exchange Utility allows sites to exchange Clinical Reminder definitions and all the associated components. Therefore Clinical Reminders needs to read and write all fields in the file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31319120 KEYWORDS: CLINICAL REMINDERS KEYWORDS: EDUCATION TOPICS SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3086 IA #: 3086 FILE NUMBER: 9000010.16 GLOBAL ROOT: AUPNVPED( DATE CREATED: MAY 16, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3086 ID: AUPNVPED( GLOBAL REFERENCE: AUPNVPED('AA', GLOBAL REFERENCE: AUPNVPED(D0,0) FIELD NUMBER: .01 FIELD NAME: TOPIC LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: LEVEL OF UNDERSTANDING LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Education Topics are used as a finding in Clinical Reminders. Therefore Clinical Reminders needs to read the following fields. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31319122 KEYWORDS: CLINICAL REMINDERS KEYWORDS: V PATIENT ED SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3087 IA #: 3087 FILE NUMBER: 9999999.15 GLOBAL ROOT: AUTTEXAM( DATE CREATED: MAY 19, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3087 ID: AUTTEXAM( GLOBAL REFERENCE: AUTTEXAM(D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .03 FIELD NAME: SEX SPECIFIC LOCATION: 0;3 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .04 FIELD NAME: INACTIVE FLAG LOCATION: 0;4 ACCESS: Direct Global R/W & w/Fileman GLOBAL REFERENCE: AUTTEXAM(D0,88) FIELD NUMBER: 1 FIELD NAME: MNEMONIC LOCATION: 88;1 ACCESS: Direct Global R/W & w/Fileman GENERAL DESCRIPTION: Exams are used as a finding in Clinical Reminders. The Clinical Reminder Exchange Utility allows sites to exchange Clinical Reminder definitions and all the associated components. Therefore Clinical Reminders needs to read and write all fields in the file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31319123 KEYWORDS: CLINICAL REMINDERS KEYWORDS: EXAM SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3088 IA #: 3088 FILE NUMBER: 9000010.13 GLOBAL ROOT: AUPNVXAM( DATE CREATED: MAY 16, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3088 ID: AUPNVXAM( GLOBAL REFERENCE: AUPNVXAM('AA', GLOBAL REFERENCE: AUPNVXAM(D0,0) FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: RESULT LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Exams are used as a finding in Clinical Reminders. Therefore Clinical Reminders needs to read the following fields. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31319126 KEYWORDS: CLINICAL REMINDERS KEYWORDS: V EXAM SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3089 IA #: 3089 FILE NUMBER: 9999999.14 GLOBAL ROOT: AUTTIMM( DATE CREATED: JUL 15, 2004 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3089 ID: AUTTIMM( GLOBAL REFERENCE: AUTTIMM(D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .02 FIELD NAME: SHORT NAME LOCATION: 0;2 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .05 FIELD NAME: MAX # IN SERIES LOCATION: 0;5 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .07 FIELD NAME: INACTIVE FLAG LOCATION: 0;7 ACCESS: Direct Global R/W & w/Fileman GLOBAL REFERENCE: AUTTIMM(D0,88) FIELD NUMBER: 1 FIELD NAME: MNEMONIC LOCATION: 88;1 ACCESS: Direct Global R/W & w/Fileman GENERAL DESCRIPTION: Immunizations are used as a finding in Clinical Reminders. The Clinical Reminder Exchange Utility allows sites to exchange Clinical Reminder definitions and all the associated components. Therefore Clinical Reminders needs to read and write all fields in the file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31319128 KEYWORDS: CLINICAL REMINDERS KEYWORDS: IMMUNIZATION SUBSCRIBING PACKAGE: CLINICAL REMINDERS NUMBER: 3090 IA #: 3090 FILE NUMBER: 9000010.11 GLOBAL ROOT: AUPNVIMM( DATE CREATED: MAY 16, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3090 ID: AUPNVIMM( GLOBAL REFERENCE: AUPNVIMM('AA', GLOBAL REFERENCE: AUPNVIMM(D0,0) FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: SERIES LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .06 FIELD NAME: REACTION LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .07 FIELD NAME: CONTRAINDICATED LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Immunizations are used as a finding in Clinical Reminders. Therefore Clinical Reminders needs to read the following fields. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31319131 KEYWORDS: CLINICAL REMINDERS KEYWORDS: V IMMUNIZATION SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3091 IA #: 3091 FILE NUMBER: 9999999.28 GLOBAL ROOT: AUTTSK( DATE CREATED: MAY 19, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3091 ID: AUTTSK( GLOBAL REFERENCE: AUTTSK(D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: .03 FIELD NAME: INACTIVE FLAG LOCATION: 0;3 ACCESS: Direct Global R/W & w/Fileman GLOBAL REFERENCE: AUTTSK(D0,88) FIELD NUMBER: 1 FIELD NAME: MNEMONIC LOCATION: 88;1 ACCESS: Direct Global R/W & w/Fileman GENERAL DESCRIPTION: Skin Tests are used as a finding in Clinical Reminders. The Clinical Reminder Exchange Utility allows sites to exchange Clinical Reminder definitions and all the associated components. Therefore Clinical Reminders needs to read and write all fields in the file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31319134 KEYWORDS: CLINICAL REMINDERS KEYWORDS: SKIN TEST SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3092 IA #: 3092 FILE NUMBER: 9000010.12 GLOBAL ROOT: AUPNVSK( DATE CREATED: MAY 16, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3092 ID: AUPNVSK( GLOBAL REFERENCE: AUPNVSK('AA', GLOBAL REFERENCE: AUPNVSK(D0,0) FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: RESULTS LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .05 FIELD NAME: READING LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Skin Tests are used as a finding in Clinical Reminders. Therefore Clinical Reminders needs to read the following fields. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31319138 KEYWORDS: CLINICAL REMINDERS KEYWORDS: V SKIN TEST SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3093 IA #: 3093 FILE NUMBER: 9000010.18 GLOBAL ROOT: AUPNVCPT( DATE CREATED: MAY 16, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3093 ID: AUPNVCPT( GLOBAL REFERENCE: AUPNVCPT('AA', GLOBAL REFERENCE: AUPNVCPT(D0,0) FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: PROVIDER NARRATIVE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: CPT procedures are used as a finding in Clinical Reminders. Therefore Clinical Reminders needs to read the following fields. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31319143 KEYWORDS: CLINICAL REMINDERS KEYWORDS: V CPT SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3094 IA #: 3094 FILE NUMBER: 9000010.07 GLOBAL ROOT: AUPNVPOV( DATE CREATED: MAY 16, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3094 ID: AUPNVPOV( GLOBAL REFERENCE: AUPNVPOV('AA', GLOBAL REFERENCE: AUPNVPOV(D0,0) FIELD NUMBER: .01 FIELD NAME: POV LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: PROVIDER NARRATIVE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .12 FIELD NAME: PRIMARY/SECONDARY LOCATION: 0;12 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: V POV diagnoses are used as a finding in Clinical Reminders. Therefore Clinical Reminders needs to read the following fields. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31319149 KEYWORDS: CLINICAL REMINDERS KEYWORDS: V POV SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE NUMBER: 3095 IA #: 3095 FILE NUMBER: 9000011 GLOBAL ROOT: AUPNPROB( DATE CREATED: MAY 16, 2000 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3095 ID: AUPNPROB( GLOBAL REFERENCE: AUPNPROB('AC' GLOBAL REFERENCE: AUPNPROB(D0,0) FIELD NUMBER: .05 FIELD NAME: PROVIDER NARRATIVE LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Problem List diagnoses are used as a finding in Clinical Reminders. Therefore Clinical Reminders needs to read the following fields. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31319154 KEYWORDS: CLINICAL REMINDERS KEYWORDS: PROBLEM LIST SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3096 IA #: 3096 FILE NUMBER: 9999999.27 GLOBAL ROOT: AUTNPOV( DATE CREATED: MAY 16, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3096 ID: AUTNPOV( GLOBAL REFERENCE: AUTNPOV(D0,0) FIELD NUMBER: .01 FIELD NAME: NARRATIVE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: A Provider Narrative entry is associated with Problem List, V POV, and V CPT entries. Each of these are used as a finding in Clinical Reminders. The Provider Narrative is displayed in the Clinical Maintenance output for each of this finding types. Therefore Clinical Reminders needs to read the following field. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31319158 KEYWORDS: CLINICAL REMINDERS KEYWORDS: PROVIDER NARRATIVE SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3097 IA #: 3097 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: APR 21, 2000 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3097 ID: DPT( GLOBAL REFERENCE: DPT(D0,'NHC') FIELD NUMBER: 148 FIELD NAME: CNH CURRENT LOCATION: NHC;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to denote when a patient is in a contract nursing home. Answer yes if the patient is in a contract nursing home currently. Otherwise, answer no. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31186301 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY SUBSCRIBING PACKAGE: CMOP NUMBER: 3098 IA #: 3098 DATE CREATED: APR 24, 2000 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: HLUTIL NAME: HL7 APIs ID: HLUTIL GENERAL DESCRIPTION: APIs for HL7 package. These APIs are available after patch HL*1.6*64. STATUS: Active MAIL MESSAGE: 31401646 KEYWORDS: HL7 COMPONENT/ENTRY POINT: $$MSGSTAT(msg id) COMPONENT DESCRIPTION: This function will return the message status for the given message id. input value: X = message id return value: status^status updated^error msg.^error type pointer^queue position or # of retries^# open failed^ack timeout status: 0 = message doesn't exist 1 = waiting in queue 1.5 = opening connection 1.7 = awaiting response, # of retries 2 = awaiting application ack 3 = successfully completed 4 = error 8 = being generated 9 = awaiting processing VARIABLES: msg id TYPE: Input VARIABLES DESCRIPTION: The message identifier that uniquely identifies the message. COMPONENT/ENTRY POINT: $$MSGACT(msg id, action) COMPONENT DESCRIPTION: Take an action on an outgoing HL7 message. Only works on messages going out on a TCP Logical Link. Actions: 1 = cancel, 2 = requeue. Returns: 1 = sucess, 0 = failed VARIABLES: msg id TYPE: Input VARIABLES DESCRIPTION: The message identifier that uniquely identifies the message in file 773, HL7 MESSAGE ADMINISTRATION file. VARIABLES: action TYPE: Input VARIABLES DESCRIPTION: The action to perform on the message. 1 = cancel, 2 = requeue. COMPONENT/ENTRY POINT: $$CHKLL(institution) COMPONENT DESCRIPTION: This function checks the setup of the Logical Link identified by the institution name or number. This will only work with TCP Logical Links. Returns: 1 = Link is setup correctly, 0 = Link is not setup correctly. VARIABLES: institution TYPE: Input VARIABLES DESCRIPTION: This is the institution name or number. NUMBER: 3099 IA #: 3099 DATE CREATED: APR 24, 2000 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: HLCSUTL NAME: HL7 APIs ID: HLCSUTL GENERAL DESCRIPTION: HL7 APIs for the routine HLCSUTL. These are available after patch HL*1.6*64. STATUS: Active MAIL MESSAGE: 31401653 COMPONENT/ENTRY POINT: $$FLD(.HLNODE, field) COMPONENT DESCRIPTION: This function will return the value for the field in a HL7 message segment. input value: HLNODE = HLNODE from the HLNEXT call, passed by reference field = number, field position in segment note: HL("FS") must be defined return value: value for the field in this segment VARIABLES: HLNODE TYPE: Input VARIABLES DESCRIPTION: This variable contains a message segment. It is defined when processing a HL7 message and executing HLNEXT. VARIABLES: field TYPE: Input VARIABLES DESCRIPTION: A number that defines the position in the segment for the value you want. COMPONENT/ENTRY POINT: $$MSG(msg id, return ref) COMPONENT DESCRIPTION: This function puts the complete HL7 message, including header, into the close reference, return ref. This is only for TCP tcp messages. input: msg id = message identifier return ref = closed local or global reference output: return 1 for success and 0 if message doesn't exist The message is returned with blank line between each segment, example: ref(1)=MSH^~|\&VOICERAD^^RADIOLOGY^^20000110145151-0800^^ORU~R01^1231^T^2.2 ref(2)= ref(3)=PID^^^100~10~M11^^JONES~JOHN^^19421111^M^^^^^^^^^^123456789 ref(4)= VARIABLES: msg id TYPE: Input VARIABLES DESCRIPTION: The message identifier that uniquely identifies the message. VARIABLES: return ref TYPE: Input VARIABLES DESCRIPTION: A closed local or global reference to put the HL7 message. NUMBER: 3100 IA #: 3100 FILE NUMBER: 4.2 GLOBAL ROOT: DIC(4.2, DATE CREATED: MAR 22, 2001 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: MPI-AUSTIN.VA.GOV domain set to send ID: DIC(4.2, GLOBAL REFERENCE: DIC(4.2, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: FLAGS LOCATION: 0;2 ACCESS: Read w/Fileman GLOBAL REFERENCE: DIC(4.2,D0,1, FIELD NUMBER: .01 FIELD NAME: TRANSMISSION SCRIPT LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1.4 FIELD NAME: NETWORK LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 1.5 FIELD NAME: OUT OF SERVICE LOCATION: 0;7 ACCESS: Read w/Fileman GENERAL DESCRIPTION: CIRN Patient Demographics has an agreement to do a read with FileMan on the NAME (#.01) and FLAGS (#1) fields in the DOMAIN (#4.2) file, as well as the TRANSMISSION SCRIPT (#4) multiple, the TRANSMISSION SCRIPT (#.01) field, NETWORK ADDRESS (MAILMAN HOST) (#1.4) field and OUT OF SERVICE (#1.5) field. This is used in environment check routine, RGP13ENV, to ensure that the instructions in informational patch XM*DBA*144 have been followed for domain "MPI-AUSTIN.VA.GOV". The environment check routine will not allow patch RG*1.0*13 to be installed in the production environment unless the FLAGS field (#1) has been set to "S", the NETWORK ADDRESS (MAILMAN HOST) (#1.4) field contains the correct address and the OUT OF SERVICE (#1.5) field is null. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: AUG 01, 2001 MAIL MESSAGE: 32710483 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham NUMBER: 3101 IA #: 3101 FILE NUMBER: 2 GLOBAL ROOT: DPT DATE CREATED: MAY 03, 2000 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3101 ID: DPT GLOBAL REFERENCE: DPT(IEN)) GENERAL DESCRIPTION: PCE name-spaced routine references $D(^DPT(IEN)) in order to do a one-time file clean up. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31246815 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES NUMBER: 3102 IA #: 3102 FILE NUMBER: 8925 GLOBAL ROOT: TIU(8925 DATE CREATED: MAY 03, 2000 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3102 ID: TIU(8925 GLOBAL REFERENCE: TIU(8925,'C' GENERAL DESCRIPTION: PCE name-spaced routine references $D(^TIU(8925,"C",IEN)) in order to do a one-time file clean up. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31246815 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Salt Lake City NUMBER: 3103 IA #: 3103 FILE NUMBER: 3.54 GLOBAL ROOT: %ZISL(3.54 DATE CREATED: MAY 04, 2000 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: RESOURCE FILE MANAGEMENT ID: %ZISL(3.54 GENERAL DESCRIPTION: To prevent multiple jobs from running simultaneously through a resource device, the device must be monitored. Also, if a job that is utilizing a resource device fails, the device must be cleared manually. This IA will allow the CMOP package to manage the PSX resource device and prevent potentially harmful results from data merging. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31251919 SUBSCRIBING PACKAGE: CMOP ISC: Birmingham SUBSCRIBING DETAILS: The CMOP transmission process relies on the PSX resource device to ensure that only one CMOP job runs at a time. As long as the sites keep the AVAILABLE SLOTS field set to one there is never a problem. However, despite many efforts at training we continually discover the AVAILABLE SLOTS set to more than one. Because two CMOP jobs running simultaneously has resulted in merged data and involves patient safety, the CMOP package requests the ability to monitor the PSX resource device and, if necessary, reset the available slots field to one. GLOBAL REFERENCE: ^%ZISL(3.54,0 .01 NAME 0;1 Read with Fileman 1 AVAILABLE SLOTS 0;2 Read with Fileman ^%ZISL(3.54,D0,1,0 .01 SLOT IN USE 1;1 R/W with Fileman 3 TASK # 1;4 Read with Fileman NUMBER: 3104 IA #: 3104 FILE NUMBER: 8930.8 GLOBAL ROOT: USR(8930.8 DATE CREATED: MAR 26, 2001 CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Direct Read of USR ACTION FILE (#8930.8) ID: USR(8930.8 GLOBAL REFERENCE: USR(8930.8,'B', GLOBAL REFERENCE: USR(8930.8,DO,0) FIELD NUMBER: .05 FIELD NAME: USER VERB LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .07 FIELD NAME: USER VERB MODIFIER LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: TIU frequently sends "You may not..." messages such as "You may not ATTACH this UNSIGNED TELEPHONE NOTE TO AN ID NOTE." In order to create such messages, TIU reads the B cross-reference of file 8930.8 to get the record number of a given action, and then reads pieces 5 and 7 of the 0 node to get the USER VERB and the USER VERB MODIFIER for the given action, for use in feedback messages such as the one above. VIEWER: ANTRY,MIKE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32681489 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 3105 IA #: 3105 GLOBAL ROOT: %ZTSCH DATE CREATED: MAY 04, 2000 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TASK FILE LOOKUP ID: %ZTSCH GENERAL DESCRIPTION: The CMOP package requests the ability to perform a check against a lock being held on ^%ZTSCH("TASK",ZTSK) to enable a background reset of the resource device PSX. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31252111 SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 3106 IA #: 3106 FILE NUMBER: 49 GLOBAL ROOT: DIC(49 DATE CREATED: MAY 04, 2000 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Problem List direct views of DIC(49 ID: DIC(49 GLOBAL REFERENCE: DIC(49,D0,0) FIELD NUMBER: 1 FIELD NAME: ABBREVIATION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the accepted abbreviation for this service or section. GENERAL DESCRIPTION: This DBIA documents direct global references made by Problem List to the SERVICE/SECTION file (#49). These references are used by Problem List to retrieve the service abbreviation from file 49. This data is then provided to Health Summary for display. VIEWER: ANTRY,MIKE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31258031 KEYWORDS: PROBLEM KEYWORDS: GMPL KEYWORDS: GMTS KEYWORDS: HEALTH KEYWORDS: SUMMARY KEYWORDS: LIST KEYWORDS: GMPLHS SUBSCRIBING PACKAGE: PROBLEM LIST ISC: Salt Lake City NUMBER: 3107 IA #: 3107 DATE CREATED: MAY 08, 2000 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSSUTIL NAME: DBIA3107 ID: PSSUTIL GENERAL DESCRIPTION: National Drug File requests permission to call an entry point in the Pharmacy Data Management package that deletes Possible Dosages and Local Possible Dosages. This call is made when a drug is matched/rematched manually through the National Drug File package to an entry in the VA PRODUCT (#50.68) File. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31274468 COMPONENT/ENTRY POINT: EN1(PSSDIEN,PSSTALK) COMPONENT DESCRIPTION: This entry point is used to delete dosage information in the DRUG (#50) File. VARIABLES: PSSDIEN TYPE: Input VARIABLES DESCRIPTION: This is the pointer to the DRUG (#50) File entry. VARIABLES: PSSTALK TYPE: Input VARIABLES DESCRIPTION: This variable determines whether or not this call is interactive. If this variable is '0', then Possible Dosages and Local Possible Dosages will be deleted. If this variable is '1', the Possible Dosages are deleted, and if Local Possible Dosages exist, the user will be shown these entries, then prompted on whether these entries should be deleted. COMPONENT/ENTRY POINT: EN2(PSSDIEN,PSSTALK) COMPONENT DESCRIPTION: This entry point is used to create dosage information in the DRUG (#50) File from the National Drug File (NDF) match. VARIABLES: PSSTALK TYPE: Input VARIABLES DESCRIPTION: This variable determines whether or not this call is interactive. This variable should always be passed as a '0' for this call. SUBSCRIBING PACKAGE: NATIONAL DRUG FILE ISC: Birmingham SUBSCRIBING DETAILS: When a drug is matched/rematched manually through the National Drug File package, Possible Dosages and Local Possible Dosages may need to be deleted for the DRUG (#50) File entry. NUMBER: 3108 IA #: 3108 DATE CREATED: MAY 10, 2000 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DGMST ENTER NEW MST GENERAL DESCRIPTION: The Women's Health (WH) package requests permission to add the MST Status Add/Edit [DGMST ENTER NEW MST] option onto any WH menu. This option will permit WH users to add/edit Military Sexual Trauma (MST) data directly into the MST module of the Registration package without having to exit the WH package menu structure. Screening veterans for MST is required by the Veterans Millennium Health Care and Benefits Act (PL 106-117). Adding the MST Status Add/Edit [DGMST ENTER NEW MST] option to a WH package menu will aid the WH users to enter the screening data for their patients. The WH package will use a supported KERNEL API ($$ADD^XPDMENU) to add the facility's copy of the option onto the WH menu. The WH pacakge will not export a copy of the DGMST ENTER NEW MST option. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31253927 SUBSCRIBING PACKAGE: WOMEN'S HEALTH ISC: Hines NUMBER: 3109 IA #: 3109 DATE CREATED: MAY 12, 2000 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA3109 GENERAL DESCRIPTION: IB requests permission to check for the DG ELIGIBILITY security key. This check is used to allow the updating of fields Date of Birth, Sex, Marital Status, Veteran(Y/N), and Primary Eligibility while creating a bill. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31304420 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 3110 IA #: 3110 FILE NUMBER: 101.41 GLOBAL ROOT: ORD(101.41, DATE CREATED: MAY 16, 2000 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3110 ID: ORD(101.41, GLOBAL REFERENCE: ORD(101.41,D0,0) => TYPE FIELD NUMBER: 4 FIELD NAME: TYPE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Type of order dialog. GENERAL DESCRIPTION: STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31324921 KEYWORDS: ORDER TYPE SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING DETAILS: Clinical Reminders need to pass the type of an order dialog to CPRS GUI. NUMBER: 3112 IA #: 3112 FILE NUMBER: 120.51 GLOBAL ROOT: GMRD(120.51 DATE CREATED: MAY 17, 2000 CUSTODIAL PACKAGE: GEN. MED. REC. - VITALS CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3112 ID: GMRD(120.51 GLOBAL REFERENCE: GMRD(120.51,D0,0 FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to FIELD NUMBER: 7 FIELD NAME: PCE ABBREVIATION LOCATION: 0;7 ACCESS: Read w/Fileman GENERAL DESCRIPTION: GMRV VITAL TYPE entries are used as findings in Clinical Reminders. Therefore Clinical Reminders needs to point to GMRV VITAL TYPE entries. It also needs the PCE ABBREVIATION for reminder dialogs. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31324542 KEYWORDS: CLINICAL REMINDERS KEYWORDS: GMRV VITAL TYPE SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3113 IA #: 3113 FILE NUMBER: 601.6 GLOBAL ROOT: YTT(601.6, DATE CREATED: MAY 17, 2000 CUSTODIAL PACKAGE: MENTAL HEALTH CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3113 ID: YTT(601.6, GLOBAL REFERENCE: YTT(601.6,D0,0) FIELD NUMBER: 4 FIELD NAME: APPROPRIATE FOR GUI INPUT LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman STATUS: Active MAIL MESSAGE: 31325004 KEYWORDS: APPROPRIATE FOR GUI INPUT SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING DETAILS: The clinical reminders package needs to reference file 601.6 to determine if a mental health instrument/test may be performed as part of a reminder dialog in the CPRS GUI. NUMBER: 3114 IA #: 3114 DATE CREATED: MAY 18, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA3114 GENERAL DESCRIPTION: Clinical Reminders is being split out of PCE. As part of the split the reminder disclaimer is being moved from the PCE parameter file to the Clinical Reminders parameter file. This makes the PCE options to manage the disclaimer obsolete. As a service to PCE the Clinical Reminders installation will clean up the obsolete options. The specific actions are: Re-distributing the following PX prefixed options. 1 PX HS DISCLAIMER EDIT Distributed as Delete Site 2 PX HS/RPT PARAMETER MENU Changed the description text, removing text about the disclaimer. 3 PX HS/RPT PARAMETERS PRINT Changed the description text 4 PX REPORT PARAMETER EDIT Distributed as Attach to Menu Redistributing the print template option PCE HS/RPT PARAMETERS PRINT used by the PX HS/RPT PARAMETER PRINT option. Display of the disclaimers was removed, and added text to refer to the new option to manage the disclaimer. STATUS: Active MAIL MESSAGE: 31329268 KEYWORDS: CLINICAL REMINDERS DISCLAIMER KEYWORDS: PCE SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3115 IA #: 3115 DATE CREATED: MAY 19, 2000 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA3115 GENERAL DESCRIPTION: When a reminder manager is creating a Clinical Reminder definition they may often need access to certain options from other packages. As a convenience for users, Clinical Reminders would like to offer the PXRM OTHER SUPPORTING MENUS option to provide easy access to these useful options. Clinical Reminders would like to include the option GMTS COORDINATOR on this menu. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31329274 KEYWORDS: CLINICAL REMINDERS KEYWORDS: HEALTH SUMMARY COMPONENT/ENTRY POINT: Option: GMTS COORDINATOR SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3116 IA #: 3116 DATE CREATED: MAY 19, 2000 CUSTODIAL PACKAGE: AUTOMATED INFO COLLECTION SYS CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA3116 GENERAL DESCRIPTION: When a reminder manager is creating a Clinical Reminder definition they may often need access to certain options from other packages. As a convenience for users, Clinical Reminders would like to offer the PXRM OTHER SUPPORTING MENUS option to provide easy access to these useful options. Clinical Reminders would like to include the option IBDF PRINT BLNK ENCOUNTER FORM on this menu. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31329279 KEYWORDS: CLINICAL REMINDERS KEYWORDS: ENCOUNTER FORMS COMPONENT/ENTRY POINT: Option: IBDF PRINT BLNK ENCOUNTER FORM SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3117 IA #: 3117 DATE CREATED: MAY 19, 2000 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA3117 GENERAL DESCRIPTION: When a reminder manager is creating a Clinical Reminder definition they may often need access to certain options from other packages. As a convenience for users, Clinical Reminders would like to offer the PXRM OTHER SUPPORTING MENUS option to provide easy access to these useful options. Clinical Reminders would like to include the option ORCM QUICK ORDERS on this menu. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31329283 KEYWORDS: CLINICAL REMINDERS KEYWORDS: ORDER ENTRY COMPONENT/ENTRY POINT: Option: ORCM QUICK ORDERS SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3118 IA #: 3118 DATE CREATED: MAY 19, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA3118 GENERAL DESCRIPTION: When a reminder manager is creating a Clinical Reminder definition they may often need access to certain options from other packages. As a convenience for users, Clinical Reminders would like to offer the PXRM OTHER SUPPORTING MENUS option to provide easy access to these useful options. Clinical Reminders would like to include the options PX PCE COORDINATOR MENU and PXTT TABLE MAINTENANCE on this menu. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31329284 KEYWORDS: CLINICAL REMINDERS KEYWORDS: PCE COMPONENT/ENTRY POINT: Option: PX PCE COORDINATOR MENU COMPONENT/ENTRY POINT: Option: PXTT TABLE MAINTENANCE SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3119 IA #: 3119 DATE CREATED: MAY 18, 2000 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCDRFR NAME: Consult Default Reason for Request ID: GMRCDRFR STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 COMPONENT/ENTRY POINT: GETDEF COMPONENT DESCRIPTION: Retrieves a default reason for request for any consult service entered in the REQUEST SERVICES file 123.5 This is used during order placement in CPRS VARIABLES: GMRCARR TYPE: Output VARIABLES DESCRIPTION: array to return containing default RFR VARIABLES: GMRCSRV TYPE: Input VARIABLES DESCRIPTION: IEN from file 123.5 VARIABLES: GMRCDFN TYPE: Input VARIABLES DESCRIPTION: patient identifier if to return resolved VARIABLES: RESOLV TYPE: Input VARIABLES DESCRIPTION: 1 or 0 ; if RESOLV=1 GMRCARR will be returned resolved COMPONENT/ENTRY POINT: REAF(OI_REF) COMPONENT DESCRIPTION: Determine editing status of default reason for request VARIABLES: OI_REF TYPE: Input VARIABLES DESCRIPTION: reference to file 123.5 (ien;99CON) or file 123.3 (ien;99PRC) VARIABLES: Integer TYPE: Output VARIABLES DESCRIPTION: 0 - unrestricted 1 - ask on edit only 2 - no editing SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM DBA Comments: 6/3/14-MC: Brandon DeWayne originally requested to add FBCS as a subscriber on 6/20/13. Approval received by Tony Thompson. Last email correspondence received from Brandon was July 2013. Patch was released 9/11/13 as an emergency patch. Since approval was already received and patch has been released, adding FBCS as a subscribing package to this ICR. NUMBER: 3120 IA #: 3120 DATE CREATED: MAY 18, 2000 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCDIS NAME: UNLINK RESULTS ID: GMRCDIS STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 COMPONENT/ENTRY POINT: DIS COMPONENT DESCRIPTION: Consult/Request Tracking provides an API to CPRS to allow a previously associated Medicine result to be disassociated from a Consult procedure request. VARIABLES: GMRCO TYPE: Input VARIABLES DESCRIPTION: IEN from REQUEST/CONSULTATION (#123) file COMPONENT/ENTRY POINT: REMOVE(IEN,RSLT,DATE,PERSON) COMPONENT DESCRIPTION: This entry point provides a silent API for removing a previously associated Medcine procedure or Clincial Procedure result from a Consult request. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN from REQUEST/CONSULTATION (#123) file. VARIABLES: RSLT TYPE: Input VARIABLES DESCRIPTION: Variable pointer form of a Medicine or Clinical Procedure result. Example: "19;MCAR(691.5," "19;MDD(702," VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: Fileman date/time the activity took place in the calling application. VARIABLES: PERSON TYPE: Input VARIABLES DESCRIPTION: DUZ of the person responsible for the action. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Hines EDITOR: RUTHERFORD,JERALD F NUMBER: 3121 IA #: 3121 DATE CREATED: MAY 18, 2000 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCUTL1 NAME: Consult Ordering Utilities ID: GMRCUTL1 GENERAL DESCRIPTION: Consult/Request Tracking provides utilities to CPRS for the purpose of retrieving information about certaing consult orderables during the ordering process. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 COMPONENT/ENTRY POINT: PROVDX COMPONENT DESCRIPTION: This extrinsic function is used to retrieve the ordering parameters for the PROVISIONAL DIAGNOSIS when ordering a consult. Output: string A^B A = O (optional), R (required) or S (suppress) B = F (free-text) or L (lexicon) VARIABLES: SERV TYPE: Input VARIABLES DESCRIPTION: IEN from REQUEST SERVICES (#123.5) file COMPONENT/ENTRY POINT: PREREQ COMPONENT DESCRIPTION: This entry point is called to retrieve any information regarding pre-requisites to ordering a consult to a particualr service. This is called during the ordering process in CPRS. VARIABLES: GMRCARR TYPE: Output VARIABLES DESCRIPTION: array to return containing pre-requisite VARIABLES: GMRCSRV TYPE: Input VARIABLES DESCRIPTION: IEN from file 123.5 VARIABLES: GMRCDFN TYPE: Input VARIABLES DESCRIPTION: patient identifier if array is to be returned resolved VARIABLES: UNRESOLV TYPE: Input VARIABLES DESCRIPTION: 1 or 0 ; if UNRESOLV=1 GMRCARR will be returned unresolved COMPONENT/ENTRY POINT: $$ORIFN(GMRCDA) COMPONENT DESCRIPTION: This entry point returns the OE/RR order number from the ORDER (#100) file that corresponds to a particular consult record. VARIABLES: GMRCDA TYPE: Input VARIABLES DESCRIPTION: This variable is the internal entry number from the REQUEST/CONSULTATION (#123) file. VARIABLES: $$ORIFN TYPE: Output VARIABLES DESCRIPTION: This will return the internal entry number of the ORDER associated with a particular consult/procedure record. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM DBA Comments: 6/3/14-MC: Brandon DeWayne originally requested that FBCS be added as as subscriber to ICR on 6/20/13. Approval received from Tony Thompson. Patch was released 9/11/13 as an emergency patch. Since approval has been received and patch was released, adding FBCS as a subscribing package to the ICR. NUMBER: 3122 IA #: 3122 DATE CREATED: MAY 18, 2000 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCGUIU NAME: GUI resulting utilities for consults ID: GMRCGUIU GENERAL DESCRIPTION: Consult/Request Tracking provides utlities for retrieving result information about a particular consult request. These utilities are called by the CPRS GUI during the resulting of Consult procedure requests. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 COMPONENT/ENTRY POINT: GETMED COMPONENT DESCRIPTION: This entry point is called to retrieve a list of available Medicine results that may be associated with a Consult procedure request. VARIABLES: GMRCIFN TYPE: Input VARIABLES DESCRIPTION: IEN from REQUEST/CONSULTATION (#123) file VARIABLES: GMRCRES TYPE: Output VARIABLES DESCRIPTION: Returned as an array as follows: GMRCRES(x) = result_ref^result_name^date^summary example: GMRCRES(1)="19;MCAR(691.5,^EKG^JUN 30,1999@15:52^ABNORMAL" COMPONENT/ENTRY POINT: GETRES COMPONENT DESCRIPTION: This entry point is provided to retrieve a list of all Medicine results currently associated with a given Consult procedure request. VARIABLES: GMRCO TYPE: Input VARIABLES DESCRIPTION: IEN from REQUEST/CONSULTATION (#123) file VARIABLES: GMRCAR TYPE: Output VARIABLES DESCRIPTION: Returned as an array as follows: GMRCAR(x)=result_ref^result_name^date^impression Example: GMRCAR(1)="19;MCAR(691.5,^EKG^JUN 30,1999@15:52^ABNORMAL" COMPONENT/ENTRY POINT: DISPMED COMPONENT DESCRIPTION: This entry point is provided to allow the display of a particular Medicine result that is being associated or disassociated with a Consult procedure request. VARIABLES: GMRCRES TYPE: Input VARIABLES DESCRIPTION: Variable pointer form of a Medicine package result (e.g. "19;MCAR(691.5") VARIABLES: GMRCAR TYPE: Output VARIABLES DESCRIPTION: Array returned containing the text of a Medicine package report. Example: GMRCAR(1)=" PROCEDURE DATE/TIME: 06/30/99 15:52" GMRCAR(2)=" CONFIDENTIAL ECG REPORT" GMRCAR(3...)= SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3123 IA #: 3123 FILE NUMBER: 774 GLOBAL ROOT: HLS(774 DATE CREATED: JUN 08, 2000 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBA3123 ID: HLS(774 GLOBAL REFERENCE: HLS(774 FIELD NUMBER: .01 FIELD NAME: NUMBER LOCATION: 0;1 ACCESS: Write w/Fileman GENERAL DESCRIPTION: Ability to delete subscription record (file 774) with FileMan when deleting the pointer to that record in the MPI node of the Patient file (#2). This is necessary for duplicate record merge. STATUS: Active MAIL MESSAGE: 31448728 SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA NUMBER: 3124 IA #: 3124 DATE CREATED: MAY 23, 2000 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBRFN NAME: DBIA3124 ID: IBRFN GENERAL DESCRIPTION: Routine call to return ^TMP("IBRBT",$J,IBIFN,n and ^TMP("IBRBF",$J,IBIFN,n arrays which contain third party bill information and first party bill information respectively. The purpose of this call is to find associated Third and First Party bills. The call returns arrays containing Third and First Party bills that cover the same episodes of care as the Third Party bill that is passed in as input. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32561688 COMPONENT/ENTRY POINT: RELBILL VARIABLES: IBIFN TYPE: Input VARIABLES DESCRIPTION: The pointer value to the bill entry in file 399 (also 430 same number) that will be used to find associated third party and first party charges based upon the episode of care covered by the bill entry that is passed in IBIFN. VARIABLES: ~TMP TYPE: Output VARIABLES DESCRIPTION: Returns ^TMP("IBRBT",$J,IBIFN)= 1 if patient has any RX coverage null if not ^TMP("IBRBT",$J,IBIFN,associated third party bill ifn)= 1^2^3^4^5^6^7 where Piece Value ----- ----- 1 From date 2 To date 3 1 for cancelled in IB null if not 4 AR bill number 5 Sequence of insurance coverage - p for primary, s for secondary and t for tertiary 6 Payer is medicare supplemental 1 for yes 7 Payer name ^TMP("IBRBF",$J,IBIFN,associated first party charge ifn)= 1^2^3^4^5^6^7 where Piece Value ----- ----- 1 From 2 To 3 Cancelled in IB 1 for yes null for no 4 AR bill number 5 Total charge 6 Action type (short) 7 Days on hold SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Albany NUMBER: 3125 IA #: 3125 FILE NUMBER: 70 GLOBAL ROOT: RADPT( DATE CREATED: MAY 24, 2000 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: RADPT Health Summary ID: RADPT( GLOBAL REFERENCE: RADPT(DO,'DT','AP') GLOBAL DESCRIPTION: This is a cross reference used to Loop through the RAD/NUC MED PATIENT (file 70) looking for selected exams for a patient. This is used in Health Summary Component RADIOLOGY IMPRESSION SELECTED (SRI). GLOBAL REFERENCE: RADPT(DO,'DT',D1) GLOBAL DESCRIPTION: Loop through RAD/NUC MED PATIENT (file 70) REGISTERED EXAMS (sub-file 70.02) looking file entries within a date range. This is used by Health Summary components RADIOLOGY IMPRESSION SELECTED (SRI), RADIOLOGY IMPRESSION (RI) and RADIOLOGY PROFILE (RP). GLOBAL REFERENCE: RADPT(DO,'DT',D1,'P',D2) GLOBAL DESCRIPTION: Loop through RAD/NUC MED PATIENT (file 70) REGISTERED EXAMS (sub-file 70.02), EXAMINATIONS (sub-file 70.03) for radiology exams within a date range. This is used by Health Summary components RADIOLOGY IMPRESSION (RI) and RADIOLOGY PROFILE (RP). GLOBAL REFERENCE: RADPT(DO,'DT',D1,'P',D2, FIELD NUMBER: 2 FIELD NAME: PROCEDURE LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: EXAM STATUS LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 12 FIELD NAME: PRIMARY INTERPRETING RESIDENT LOCATION: 0;12 ACCESS: Read w/Fileman FIELD NUMBER: 13 FIELD NAME: PRIMARY DIAGNOSTIC CODE LOCATION: 0;13 ACCESS: Read w/Fileman FIELD NUMBER: 15 FIELD NAME: PRIMARY INTERPRETING STAFF LOCATION: O;15 ACCESS: Read w/Fileman FIELD NUMBER: 17 FIELD NAME: REPORT TEXT LOCATION: 0;17 ACCESS: Read w/Fileman FIELD NUMBER: 25 FIELD NAME: MEMBER OF SET LOCATION: 0;25 ACCESS: Read w/Fileman FIELD NUMBER: 135 FIELD NAME: CPT MODIFIERS LOCATION: CMOD;0 ACCESS: Read w/Fileman FIELD NUMBER: 175 FIELD NAME: TECHNOLOGIST LOCATION: TC;0 ACCESS: Read w/Fileman FIELD NUMBER: 400 FIELD NAME: CLINICAL HISTORY FOR EXAM LOCATION: WP ACCESS: Read w/Fileman GLOBAL DESCRIPTION: Extract examination data from EXAMINATIONS sub-file 70.03. GLOBAL REFERENCE: RADPT(DO,'DT',D1,'P',D2,'TC', FIELD NUMBER: .01 FIELD NAME: TECHNOLOGIST LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL DESCRIPTION: Extract technologist name from TECHNOLOGIST sub-file 70.12. GLOBAL REFERENCE: RADPT(D0,'DT',D1,'P',D2,'CMOD', FIELD NUMBER: .01 FIELD NAME: CPT MODIFIER LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL DESCRIPTION: Loop through RAD/NUC MED PATIENT (file 70) REGISTERED EXAMS (sub-file 70.02), EXAMINATIONS (sub-file 70.03), CPT MODIFIERS (sub-file 70.3135) for the modifiers to the CPT procedure. This is used by Health Summary components RADIOLOGY IMPRESSION SELECTED (SRI), RADIOLOGY IMPRESSION (RI) and RADIOLOGY PROFILE (RP). GLOBAL REFERENCE: RADPT(D0,'DT',D1,'P',D2,'M', FIELD NUMBER: .01 FIELD NAME: PROCEDURE MODIFIERS LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL DESCRIPTION: Loop through RAD/NUC MED PATIENT (file 70) REGISTERED EXAMS (sub-file 70.02), EXAMINATIONS (sub-file 70.03), PROCEDURE MODIFIERS (sub-file 70.1) for the modifiers to the radiology procedure. This is used by Health Summary components RADIOLOGY IMPRESSION SELECTED (SRI), RADIOLOGY IMPRESSION (RI) and RADIOLOGY PROFILE (RP). GENERAL DESCRIPTION: Access RADPT() to obtain radiology exams for a patient within a date range. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31363245 KEYWORDS: RADPT KEYWORDS: HEALTH KEYWORDS: SUMMARY KEYWORDS: HEALTH SUMMARY KEYWORDS: RI KEYWORDS: SRI SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION DATE/TIME EDITED: JAN 24, 2007@00:02 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SWESKY,JEFF WITH CONCURRENCE OF: MO,SELINA NUMBER: 3127 IA #: 3127 FILE NUMBER: 8989.51 GLOBAL ROOT: XTV(8989.51, DATE CREATED: JUN 01, 2000 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3127 ID: XTV(8989.51, GENERAL DESCRIPTION: Requesting read access/fileman to all fields in the PARAMETER DEFINITION FILE (#8989.51) to retrieve the Clinical Procedures Parameter definitions. Clinical Procedures is a strictly GUI application and includes a Manager executable to setup and maintain site files and system parameters. Additionally a lookup on the parameter definition file by name screening by Entity Type allow for retrieval of all parameters for a specific entity (i.e. Division) and display/update of these values. With the information retrived from file 8989.51 this application dynamically configures input screens for the user and sends data back to the server for the XPAR API's to add/edit/delete parameter values in the XPAR utilities. Access is read-only via GETS^DIQ, GET1^DIQ, FIND^DIC, and FIND1^DIC and is programmed to only allow access to parameters in the subscribing package namespace. STATUS: Active MAIL MESSAGE: 31357060 KEYWORDS: XPAR SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI NUMBER: 3128 IA #: 3128 FILE NUMBER: 8930.2 GLOBAL ROOT: USR(8930.2, DATE CREATED: MAR 26, 2001 CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Direct Read of USR ROLE FILE (#8930.2) ID: USR(8930.2, GLOBAL REFERENCE: USR(8930.2,'B') GENERAL DESCRIPTION: In evaluating whether a user can perform a particular action on a given TIU document, TIU needs the record number in the USER ROLE FILE of each role played by that person with respect to the document. These roles are determined by examining various fields of the document, and then the role record number is read from the B cross-reference of the USER ROLE FILE. VIEWER: ANTRY,MIKE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32681595 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 3129 IA #: 3129 FILE NUMBER: 8930.1 GLOBAL ROOT: USR(8930.1, DATE CREATED: MAR 26, 2001 CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Direct Read of USR AUTHORIZATION/SUBSCRIPTION FILE ID: USR(8930.1, GLOBAL REFERENCE: USR(8930.1,'AR', GLOBAL REFERENCE: USR(8930.1,'AC', GENERAL DESCRIPTION: Document Definition titles for Interdisciplinary Notes may not be used for both ID parent and ID child notes. If there are rules permitting a title to be used for ID parent notes, any existing rules allowing it to be used for ID child notes are ignored. Therefore, ID notes needs to know if rules exist permitting a title to be used as an ID parent. To evaluate this, TIU reads the AR and AC cross-references of the AUTHORIZATION/SUBSCRIPTION FILE (#8930.1). VIEWER: ANTRY,MIKE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32681842 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 3130 IA #: 3130 DATE CREATED: JUN 13, 2000 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBJDF2 NAME: DBIA3130 ID: IBJDF2 GENERAL DESCRIPTION: This function returns the primary division associated with the care on a Third Party bill. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31484349 KEYWORDS: REGIONAL COUNSEL DIVISION COMPONENT/ENTRY POINT: $$DIV VARIABLES: IBX TYPE: Input VARIABLES DESCRIPTION: IBX is a pointer to a claim in file #399 BILL/CLAIMS FILE. VARIABLES: IBY TYPE: Output VARIABLES DESCRIPTION: IBY is a pointer to the MEDICAL CENTER DIVISION file #40.8. SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Albany NUMBER: 3132 IA #: 3132 DATE CREATED: JUN 20, 2000 CUSTODIAL PACKAGE: NDBI USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: A7RDPAGU NAME: DBIA3132 ID: A7RDPAGU GENERAL DESCRIPTION: Call HXDATA^A7RDPAGU from inside an RPC. This routine is already being called by CPRS. It is similar to the call of A7RDPACT by DGSEC whenever a patient is looked up. Both A7RDPAGU and A7RDPACT refer to National Database Integration routines which check whether a patient has historical data on a Legacy system. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32390067 COMPONENT/ENTRY POINT: HXDATA(.LST,DFN) VARIABLES: DFN TYPE: Input VARIABLES: LST TYPE: Output VARIABLES DESCRIPTION: Output array that returns legacy data message. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 3134 IA #: 3134 DATE CREATED: JUN 23, 2000 CUSTODIAL PACKAGE: CLINICAL REMINDERS CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRMXX NAME: DBIA3134 ID: PXRMXX STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31536258 KEYWORDS: CLINICAL REMINDERS COMPONENT/ENTRY POINT: PATS(START,END,OUTPUT) COMPONENT DESCRIPTION: This call returns a list of patients including: Current inpatients Outpatient visits Inpatient admissions VARIABLES: START TYPE: Input VARIABLES DESCRIPTION: Start date for outpatient visit and inpatient admission selection. FileMan Date format. VARIABLES: END TYPE: Input VARIABLES DESCRIPTION: End date for outpatient visit and inpatient admission selection. FileMan Date format. VARIABLES: OUTPUT TYPE: Input VARIABLES DESCRIPTION: A list of patients is assembled in global ^TMP(OUTPUT,$J) sorted by facility and patient ien: ^TMP(OUTPUT,$J,FACILITY,DFN) = "" SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 3135 IA #: 3135 DATE CREATED: JUN 27, 2000 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: OR EVSEND GMRC GENERAL DESCRIPTION: This is the event invoked by CPRS when a new order, or action to an order, is placed to the Consult/Request Tracking package. Actions from any application area that are dependent on this event may be added as Items upon approval. The array XQORMSG(#) will be available for all subscribers to read only, containing the HL7 message with the order to Consults as defined in the 'OE/RR Version 3 Package Interface Specifications' document. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31552621 SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: The subscribing protocol is: GMRC RECEIVE SUBSCRIBING PACKAGE: PROSTHETICS ISC: Hines SUBSCRIBING DETAILS: The subscribing protocols are: RMPR RECEIVE RMPR RECEIVE GMRC SUBSCRIBING PACKAGE: SURGERY SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING DETAILS: CP ADDED 7/9/07 SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT SUBSCRIBING DETAILS: EDIS protocol is EDP OR MONITOR. DBA Comments: 2/22/12 - EDIS project manager requested to add Emergency Department (EDIS) as a subscriber. EDIS software is in produciton but team recently discovered EDIS was not added as as subscriber during development. DATE/TIME EDITED: JUL 09, 2007@17:17 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: ACKERMAN,SHIRLEY WITH CONCURRENCE OF: BUECHLER,MELANIE DATE/TIME EDITED: APR 16, 2012@16:42 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: REED,DAN WITH CONCURRENCE OF: THOMPSON,TONY NUMBER: 3137 IA #: 3137 DATE CREATED: JUN 28, 2000 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORUS NAME: ORUS List Processor ID: ORUS GENERAL DESCRIPTION: ORUS is a utility, which presents a user with a list of entries in a columnar format and allows selection from this list. It is possible to allow multiple items to be selected at one time. Selections made are returned in Y. Since the selections are returned in Y, M code used for screens, display actions, etc., must not change Y. Y(n) may not be sequential, so Y should be processed with $O when returned. Note: In order to allow multiple selections, the characters comma (,), dash (-), equal (=), and apostrophe(') are reserved. Items presented on this list should not contain these characters. Items should also be displayed in uppercase. Upon entry ORUS and ORUS(0) must be defined. All other ORUS variables are optional. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31557387 KEYWORDS: GMTSADH2 KEYWORDS: ORUS COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: Displays a list of items for selection. VARIABLES: ORUS TYPE: Input VARIABLES DESCRIPTION: ORUS GLOBAL REFERENCE 1000 or "^GLO(1000," May be any Fileman compatible file (number or reference from which items will be selected. This may also be any global (^TMP($J,), for example) in a Fileman format. VARIABLES: ORUS(0) TYPE: Input VARIABLES DESCRIPTION: ORUS(0) COL WIDTH & PARAMS "40MN" This is the parameter string which determines how the list is to be displayed and how items are to be selected. Possible values include: Number - sets the display column width and must be at the beginning of the string. "A" - causes the list to be displayed alphabetically. This is not needed if the list is to be presented in entry order of if ORUS("F") is defined. "N" - causes the items displayed to be numbered sequentially. Not needed if mnemonics are used with each item or if no 'short' way of selecting an item is desired. "M" - causes the menu of items to be displayed automatically. Otherwise, the list is displayed only when typing a question mark. "Q" - causes OTHER ITEM (where ITEM is the file or field name) to be prompted for. If OTHER ITEM is selected, OROTHER is defined. "S" - allows the user to select a single item only, rather than sets or ranged of items. VARIABLES: ORUS(L) TYPE: Input VARIABLES DESCRIPTION: ORUS(L) LOOKUP X-REF "^GLO(1000,""B""," This is the cross reference used when looking up selections entered. Normally a standard "B" cross-reference may be used. This cross- reference should include the names of items as they are presented on the list and also any mnemonic identifiers presented. Lookup values in this cross-reference should be in uppercase, as selections made are always converted to uppercase before being looked up. If ORUS(0) contains "N", items may also be selected by number but it is not necessary to include the numbers in the cross-reference. The cross reference should be structured: ^GLO(1000,"B",VALUE,DA). VARIABLES: ORUS(F) TYPE: Input VARIABLES DESCRIPTION: ORUS(F) DISPLAY ORDER "^GLO(1000,""C""," This is the cross reference used if it is desired to present the items in a special order. For instance, lists may often be presented in alphabetical order by using the "B" cross reference here. If this is not defined and ORUS(0) does not contain an "A", the entry order of the file is used. The cross reference should be structured: ^GLO(1000,"C",VALUE,DA). VARIABLES: ORUS(S) TYPE: Input VARIABLES DESCRIPTION: ORUS(S) SCREENING ACTION "I $P(^(0),""^"",2)=1" This is M code, which screens items from being presented on (and selected from) the list. When executing a screen, it may be assumed that ORDA is set to the internal entry number of the entry and the naked is set to the zeroth node of the entry. VARIABLES: ORUS(W) TYPE: Input VARIABLES DESCRIPTION: ORUS(W) DISPLAY ACTION "S X=$P(^(0),""^"",3)" This is M code, which should set X to the text that should be displayed for a particular item. If not defined, the .01 field of the entry is displayed. If it is a pointer, the external value of the pointer is looked up and displayed. When executing a display action, it may be assumed that ORDA is set to the internal entry number of the entry and the naked is set to the zeroth node of the entry. NOTE: What is displayed should be the same as what is looked up in the cross- reference if ORUS("L") is defined. VARIABLES: ORUS(M) TYPE: Input VARIABLES DESCRIPTION: ORUS(M) MNEUMONIC "0;3" This may be used to identify the subscript and piece position of a mnemonic. If defined, the mnemonic(which should be less than 5 characters) is displayed with the item. VARIABLES: ORUS(T) TYPE: Input VARIABLES DESCRIPTION: ORUS(T) HEADER ACTION "W @IOF,?35,""-PATIENT LIST"" This may be used to write a header or title for the list. The header should include a W # so as to reset $Y. VARIABLES: ORUS(ALT) TYPE: Input VARIABLES DESCRIPTION: ORUS(ALT) ALTERNATE LOOKUP On look-up failure, an alternate lookup can be invoked by putting M code in this variable. $T will be checked to determine if the lookup was successful. VARIABLES: ORUS(A) TYPE: Input VARIABLES DESCRIPTION: ORUS(A) PROMPT "Select Items(s): " This allows a selection prompt to be defined. If not defined, the prompt is "Select "_FILENAME_": ". VARIABLES: ORUS(B) TYPE: Input VARIABLES DESCRIPTION: ORUS(B) DEFAULT RESPONSE "OTHER" This allows a default response to be defined. VARIABLES: ORUS(H) TYPE: Input VARIABLES DESCRIPTION: ORUS(H) HELP ACTION "W !,""Equal sign delimits modifiers."",! This is M code to display help other than the help normally given by the ORUS routine. VARIABLES: ORUS(900,n) TYPE: Input VARIABLES DESCRIPTION: ADDITIONAL ITEMS Items other than those in the file may be put on the list of selections. These are usually special items such as "SELECT A NEW LIST". These items may have identifiers but are usually numbered between 900 and 990. They may be passed in the array ORUS(900,n) where n is a number. This number is used as the offset to 900 when displaying the selections. When an item is selected, M code is executed (generally to set or reset a flag). The format of this array is as follows: ORUS(900,n)=display text^mneumonic^executable code VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: This is the return array of values selected. Y number of items selected Y(0) same as Y Y(n) internal entry number^.01 field^display text^value entered SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: Health Summary uses this uitlity to select from multiple items when a unique entry/item can not be found. NUMBER: 3139 IA #: 3139 FILE NUMBER: 702.01 GLOBAL ROOT: MDS(702.01, DATE CREATED: JUN 28, 2000 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3139 ID: MDS(702.01, GLOBAL REFERENCE: MDS(702.01, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to FIELD DESCRIPTION: Name of the procedure. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31574730 SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: Field .04 CLINICAL PROCEDURES of GMRC Procedure file #123.3 can point to CP Definition file 702.01. It uses the screen S DIC("S")="I $F(""OP"",$P(^MDS(702.01,+Y,0),U,2))>1&($P(^(0),U,9))" to list all active procedures and orderable items. File 123 also has a field pointing to file 702.01. NUMBER: 3140 IA #: 3140 DATE CREATED: AUG 10, 2000 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: GMRC EVSEND OR GENERAL DESCRIPTION: The protocol name GMRC EVSEND OR is exported as USE AS LINK FOR MENU ITEMS. This linkage will allow packages to monitor order activity messages. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31868491 SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: PROSTHETICS SUBSCRIBING DETAILS: Protocol RMPR RECEIVE GMRC SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING DETAILS: added 3/19/2008 SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD DBA Comments: 9/5/14-MC:Added VPR as a subscriber to ICR #3140 as requested by Melanie Buechler and approved by Tony Thompson. For patch VPR*1*3. DATE/TIME EDITED: MAR 19, 2008@17:13 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: THOMPSON,WILLIAM NUMBER: 3142 IA #: 3142 DATE CREATED: JUL 13, 2000 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOORAPI NAME: DBIA3142 ID: PSOORAPI GENERAL DESCRIPTION: This agreement allows the Clinical Reminders package to call the Outpatient Pharmacy package for patient and prescription information, based on a specified date range and a specified list of medications. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31661050 COMPONENT/ENTRY POINT: EN(PSOB,PSOE,PSOX,PSODT,PSON) COMPONENT DESCRIPTION: This entry point returns patient and prescription information in a TMP global to the subscribing package, based on the criteria passed into the call. VARIABLES: PSOB TYPE: Input VARIABLES DESCRIPTION: This is the beginning date to search by, in VA FileMan format. VARIABLES: PSOE TYPE: Input VARIABLES DESCRIPTION: This is the ending date for the search, in VA FileMan format. VARIABLES: PSOX TYPE: Input VARIABLES DESCRIPTION: This is the medication array for the search. It can be in two types. PSOX("123;PSDRUG(") where 123 is the internal entry number, and PSDRUG( indicates that the entry number corresponds with an entry in the DRUG file (#50). PSOX("321;PSNDF(50.6,") where 321 is the internal entry number, and PSNDF(50.6, indicates that the entry number corresponds with an entry in the VA GENERIC file (#50.6). VARIABLES: PSODT TYPE: Input VARIABLES DESCRIPTION: This variable determines how the search is to be conducted. "F" for Fill Date, "R" for Release Date. VARIABLES: PSON TYPE: Input VARIABLES DESCRIPTION: This is the first subscript of the TMP global that is returned. VARIABLES: TMP(PSON,$J,DFN,#,0) TYPE: Output VARIABLES DESCRIPTION: This is returned in the format ^TMP(PSON,$J,DFN,#,0). This node contains the medication criteria of the finding. This would be in the format of the PSOX input array. VARIABLES: TMP(PSON,$J,DFN,#,1) TYPE: Output VARIABLES DESCRIPTION: This is returned in the format ^TMP(PSON,$J,DFN,#,1). This node contains 4 pieces. Piece 1 is the Fill Date if the search criteria is by Fill Date. It will be the Fill Date of the released fill, if the search criteria is by Release Date. Piece 2 is the Release Date if the search criteria is by Release Date. It will be Release Date or null, if the search criteria is by Fill Date, so if the fill in this case has not yet been released, a null will be returned. Piece 3 is the name (#01) of the Drug from the DRUG file (#50), regardless of whether the finding was based on the DRUG file (#50) or VA GENERIC file (#50.6) criteria. Piece 4 is the Days Supply of the fill. SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING DETAILS: This entry point is designed to return specific prescription information, based on a set of medication criteria defined by the subscribing package. NUMBER: 3143 IA #: 3143 DATE CREATED: JUL 13, 2000 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJORAPI NAME: DBIA3143 ID: PSJORAPI GENERAL DESCRIPTION: This agreement allows the Clinical Reminders package to call the Inpatient Medications V.5.0 package for patient and order information, based on a specified date range and a specified list of medications. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31664000 KEYWORDS: PSJORAPI COMPONENT/ENTRY POINT: EN(PSJB,PSJE,PSJX,PSJDT,PSJN) COMPONENT DESCRIPTION: This entry point return patient and order information in a TMP global to the subscribing package, based on the criteria passed into the call. VARIABLES: PSJB TYPE: Input VARIABLES DESCRIPTION: This is the beginning date to search by, in VA FileMan format. VARIABLES: PSJE TYPE: Input VARIABLES DESCRIPTION: This is the ending date for the search, in VA FileMan format. VARIABLES: PSJX TYPE: Input VARIABLES DESCRIPTION: This is the medication array for the search. It can be two types. PSJX("123;PSDRUG(") where 123 is the internal entry number, and PSDRUG indicates that the entry number corresponds with an entry in the DRUG file (#50). PSJX("321;PSNDF(50.6,") where 321 is the internal entry number, and PSNDF(50.6, indicates that the entry number corresponds with an entry in the VA GENERIC file (#50.6). VARIABLES: PSJDT TYPE: Input VARIABLES DESCRIPTION: This variable is not used by the Inpatient Medications package. It is included to make it easier for the Clinical Reminders package to make the call in the same format to both the Inpatient Medications and the Outpatient Pharmacy packages. VARIABLES: PSJN TYPE: Input VARIABLES DESCRIPTION: This is the first subscript of the TMP global that is returned. It may be "PSI". The TMP global may be killed before and after use. VARIABLES: TMP(PSJN,$J,DFN,#,0) TYPE: Output VARIABLES DESCRIPTION: This is returned in the format ^TMP(PSJN,$J,DFN,#,0). This node contains the medication criteria finding. This would be in the format of the PSJX input array. VARIABLES: TMP(PSJN,$J,DFN,#,1) TYPE: Output VARIABLES DESCRIPTION: This is returned in the format ^TMP(PSJN,$J,DFN,#,1). This node contains 5 pieces. Piece 1 is the Start Date/Time of the order. Piece 2 is always null. Piece 3 is the name (#.01) of the Drug from the DRUG file (#50), regardless of whether the finding was based on the DRUG file (#50) or VA GENERIC file (#50.6) criteria. Piece 4 is always null. Piece 5 is the Stop Date/Time of the order. Pieces 2 and 4 are left null in order to make the call correspond with the Outpatient Pharmacy call. Piece 2 in the Outpatient Pharmacy call is the Release Date, Inpatient Medications doesn't have any data that corresponds with that data so we leave this piece null. Piece 4 in the Outpatient Pharmacy call is the Days Supply, again Inpatient Medications has no data that corresponds to this so we leave it null. VARIABLES: SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City NUMBER: 3144 IA #: 3144 DATE CREATED: OCT 27, 2000 CUSTODIAL PACKAGE: RPC BROKER CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XWB2HL7 NAME: DIRECT RPC CALL ID: XWB2HL7 GENERAL DESCRIPTION: This call is to make a RPC call on a remote facility. Users of this API should be prepared to modifiy their calls to support support strong authentication when made available by Infrastructure. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33227631 COMPONENT/ENTRY POINT: DIRECT(RET,LOC,RPC,RPCVER,P1,P2,P3,P4,P5,P6,P7,P8,P9,P10) COMPONENT DESCRIPTION: Use of the DIRECT connect whether it is done through DIRECT^XWB2HL7 or with DIRECT^HLMA is susceptible to encountering network errors. This was first noticed with the Institution File Redesign patch and the Integrated Billing patch(RX Copay). Susequently, HL7 issued patches HL*1.6*76 and HL*1.6*77 to address these network errors and return the status of failure back to the calling application. With the DIRECT connect, VistA HL7 only tries to send the message once. If it encounters an network error while attepting to send a message, it does not attempt to resend. When using this API, you should check the returned value of subscript zero of the first parameter. This parameter is passed by reference. For example, if you made a call like D DIRECT^XWB2HL7(.MYRET,... You should check the value of MYRET(0). If there was a problem with sending the message or receiving a response, MYRET(0) will have a value of -1^error message The -1 is both MYRET and MYRET(0), so one can use: I $P(MYRET(0),"^")=-1!(-1=+MYRET) S ERROR=1 Q See code below: DIRECT(RET,LOC,RPC,RPCVER,P1,P2,P3,P4,P5,P6,P7,P8,P9,P10) ;Call a remote RPC N X,I,INX,N,XWBHL7,XWBPAR,XWBPCNT,XWBDVER,XWBESSO,XWBHDL,PMAX N XWBMSG,XWBSEC,RPCIEN ;Protect caller from HL7 N HLMTIEN,HLDOM,HLECH,HLFS,HLINSTN,HLNEXT,HLNODE,HLPARAM,HLQ,HLQUIT D SETUP(1) I $G(RET(1))'="" Q ;(procedurename, query tag, error return, destination, Parameter array) D DIRECT^XWB2HL7A("ZREMOTE RPC",XWBHDL,.XWBMSG,LOC,.XWBPAR) I $P(XWBMSG,U,2) S RET(0)="-1^"_$P(XWBMSG,"^",3) Q I 'HLMTIEN S RET(0)="-1^No Message returned" Q D RETURN,RTNDATA^XWBDRPC(.RET,XWBHDL) Q VARIABLES: RET TYPE: Output VARIABLES DESCRIPTION: This is the return value. VARIABLES: LOC TYPE: Input VARIABLES DESCRIPTION: This is the Institution name or VISN name or ien of where to send the RPC call to. VARIABLES: RPC TYPE: Input VARIABLES DESCRIPTION: This is the name of the RPC to run on the remote system. VARIABLES: RPCVER TYPE: Input VARIABLES DESCRIPTION: version number in Remote Procedure file. (optional) VARIABLES: P1 TYPE: Input VARIABLES DESCRIPTION: 1st RPC paramater on remote system. VARIABLES: P2 TYPE: Input VARIABLES DESCRIPTION: 2nd RPC paramater on remote system. VARIABLES: P3 TYPE: Input VARIABLES DESCRIPTION: 3rd RPC paramater on remote system. VARIABLES: P4 TYPE: Input VARIABLES DESCRIPTION: 4th RPC paramater on remote system. VARIABLES: P5 TYPE: Input VARIABLES DESCRIPTION: 5th RPC paramater on remote system. VARIABLES: P6 TYPE: Input VARIABLES DESCRIPTION: 6th RPC paramater on remote system. VARIABLES: P7 TYPE: Input VARIABLES DESCRIPTION: 7th RPC paramater on remote system. VARIABLES: P8 TYPE: Input VARIABLES DESCRIPTION: 8th RPC paramater on remote system. VARIABLES: P9 TYPE: Input VARIABLES DESCRIPTION: 9th RPC paramater on remote system. VARIABLES: P10 TYPE: Input VARIABLES DESCRIPTION: 10th RPC paramater on remote system. COMPONENT/ENTRY POINT: EN1(RET,LOC,RPC,RPCVER,P1,P2,P3,P4,P5,P6,P7,P8,P9,P10) COMPONENT DESCRIPTION: This entry point is used by CPRS Remote Data Views. It places the HL7 message into the HL7 message queue for deferred transfer. See the DIRECT entry for parameter descriptions. The return from this call is a HANDLE that is used in the follow-up calls. VARIABLES: RET TYPE: Output VARIABLES DESCRIPTION: This variable is passed by reference. If RET(0) is empty, then RET(1) will have some error text. Otherwise RET(0) will have the HANDLE that is used in follow-up calls. COMPONENT/ENTRY POINT: RPCCHK(RET,HDL) COMPONENT DESCRIPTION: This entry point is used after a call to EN1^XWB2HL7 to check the status of the call. When it returns "1^Done" a call can be made to RTNDATA^XWBDRPC to get the data. When it returns "-1^text" there is a problem with the call. VARIABLES: HDL TYPE: Input VARIABLES DESCRIPTION: This is the Handle that was returned from the EN1^XWB2HL7 call. SUBSCRIBING PACKAGE: INTEGRATED BILLING SUBSCRIBING DETAILS: Integrated Billing is to call ONLY IB RPCs to view patient data. SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING DETAILS: For use with the Smart Card. SUBSCRIBING PACKAGE: MASTER PATIENT INDEX SUBSCRIBING DETAILS: MPI is to call ONLY its own RPCs, with the following exceptions allowed: MPIF ACK CHECK MPIF EXP PDAT REMOTE MPIF INACTIVATE MPIF REMOTE SPI MPIF REMOTE ICN UPDATE MPIF CHANGE CMOR RG REM ACTIVITY RG REMOTE HL7 TASK MPIF SSN DUPS SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING SUBSCRIBING DETAILS: Consult/Request Tracking is to call ONLY its own RPCs. SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING DETAILS: CIRN is to call ONLY its own RPCs. SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA SUBSCRIBING DETAILS: Master Patient Index VistA is to call ONLY its own RPCs. SUBSCRIBING PACKAGE: CORBA SERVICES SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL DBA Comments: 1/18/13-MM: Added Beneficiary Travel as a subscriber. Associated patch is DGBT*1.0*20. Bene Travel RPC is DGBT CLAIM DEDUCTIBLE PAID and will be using HL7 to access the RPC. Justification from developer: "They will be using them to access Beneficiary Claim Information at any site the patient has been to in the current month. A single array node is being returned with number of trips, amount of deductible paid, if any etc." DATE/TIME EDITED: JAN 24, 2007@00:08 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HARTLEY,PETER WITH CONCURRENCE OF: FORT,WALLY DATE/TIME EDITED: JAN 24, 2007@00:14 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HARTLEY,PETER WITH CONCURRENCE OF: FORT,WALLY DATE/TIME EDITED: JAN 18, 2013@16:50 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: DELLINGER,BARRY WITH CONCURRENCE OF: WESTRA,HERLAN NUMBER: 3145 IA #: 3145 FILE NUMBER: 42.4 GLOBAL ROOT: DIC(42.4, DATE CREATED: JUL 14, 2000 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Health Summary Admissions Treating Spec ID: DIC(42.4, GLOBAL REFERENCE: DIC(42.4,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the name of the specialties allowable. FIELD NUMBER: 1 FIELD NAME: PRINT NAME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field will contain an abbreviated name of this specialty. This print name will be printed on outputs where the full name of the specialty would not fit. GENERAL DESCRIPTION: Retrieval and display of recognized PTF treating specialties. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31672371 KEYWORDS: GMTSDGA1 KEYWORDS: GMTSDGA2 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: Health Summary needs to retrieve/display the specialty associated with Admissions. To save on screen width, the shorter of either the NAME or PRINT NAME will be displayed. NUMBER: 3146 IA #: 3146 DATE CREATED: SEP 27, 2001 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXUTL1 NAME: TIU use of PXUTL1 ID: PXUTL1 GENERAL DESCRIPTION: TIU calls $$APPOINT^PXUTL1, when the Visit IEN is not available, to check if a Visit is associated with an appointment. STATUS: Active MAIL MESSAGE: 33485467 COMPONENT/ENTRY POINT: $$APPOINT COMPONENT DESCRIPTION: Returns 1 if the patient has an appointment. VARIABLES: PXUTLDFN TYPE: Input VARIABLES DESCRIPTION: Patient file (#2) IEN VARIABLES: PXUTLDT TYPE: Input VARIABLES DESCRIPTION: Visit Date/Time VARIABLES: HLOC TYPE: Input VARIABLES DESCRIPTION: Hospital Location file (#44) IEN VARIABLES: Value TYPE: Output VARIABLES DESCRIPTION: Returns 1 if the patient has an appointment. VARIABLES: SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 3147 IA #: 3147 FILE NUMBER: 45.7 GLOBAL ROOT: DIC(45.7, DATE CREATED: JUL 14, 2000 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Health Summary Facility Treating Specialty ID: DIC(45.7, GLOBAL REFERENCE: DIC(45.7,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Contains the name of the facility treating specialty. Types of treating specialties may vary between facilities. FIELD NUMBER: 1 FIELD NAME: SPECIALTY LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains a pointer to the Specialty file #42.4, containing the specialty name and print name. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31672793 KEYWORDS: GMTSDGA1 KEYWORDS: GMTSDGA2 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: Health Summary needs to access the Facility Treating Specialty to get the treating speciaty and print name used in Admissions components. NUMBER: 3148 IA #: 3148 FILE NUMBER: 811.9 GLOBAL ROOT: PXD(811.9, DATE CREATED: JUL 20, 2000 CUSTODIAL PACKAGE: CLINICAL REMINDERS CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Health Summary Reminders/Maint Items (GUI) ID: PXD(811.9, GLOBAL REFERENCE: PXD(811.9,'B',X,D0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The software loops through the "B" index, on the NAME field (.01), gathering the internal entry numbers of those clinical reminder maintenance items which are active. GLOBAL REFERENCE: PXD(811.9,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the name of a clinical reminder/maintenance item which may be selected for use in the Health Summary components "PCE CLINICAL REMINDERS" and "PCE CLINICAL MAINTENANCE". FIELD NUMBER: 1.6 FIELD NAME: INACTIVE FLAG LOCATION: 0;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: When a reminder is inactive (1) it cannot be selected for inclusion on a Health Summary. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31744024 KEYWORDS: PXD KEYWORDS: GMTSADH5 SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: Health Summary needs to access the "B" index and the INACTIVE FLAG Field 1.6 (0;6) to to retrieve a listing of Active' REMINDER/MAINTENANCE ITEMs (NAMES, field .01) for the Adhoc Health Summary Type (GUI RPC). NUMBER: 3149 IA #: 3149 DATE CREATED: JUL 26, 2000 CUSTODIAL PACKAGE: RPC BROKER CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XWBDRPC NAME: XWBDRPC ID: XWBDRPC GENERAL DESCRIPTION: This routine contains API's for deferred RPC's used by HL7 utilities. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33227634 COMPONENT/ENTRY POINT: RTNDATA(RET,HDL) COMPONENT DESCRIPTION: Returns data retrieved from a remote site. VARIABLES: RET TYPE: Output VARIABLES DESCRIPTION: Return array. VARIABLES: HDL TYPE: Input VARIABLES DESCRIPTION: Handle of data to retrieve. COMPONENT/ENTRY POINT: CLEAR(RET,HDL) COMPONENT DESCRIPTION: This call will clear the data (in XTMP) connected with the handle that is passed in. VARIABLES: RET TYPE: Both VARIABLES DESCRIPTION: This call was setup to be used by RPC Broker this is the return. It will always be set like this: RET(0)=1 VARIABLES: HDL TYPE: Input VARIABLES DESCRIPTION: This is the Handle for the data that you want cleared. COMPONENT/ENTRY POINT: CLEARALL(RET) COMPONENT DESCRIPTION: This call will clear ALL Remote or Deferred data for the current job. VARIABLES: HDL TYPE: Both VARIABLES DESCRIPTION: This call was setup to be used by RPC Broker this is the return. It will always be set like this: RET(0)=1 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: Used by CPRS Remote Data Views. SUBSCRIBING PACKAGE: INTEGRATED BILLING SUBSCRIBING DETAILS: Integrated Billing is to call ONLY IB RPCs to view patient data. SUBSCRIBING PACKAGE: MASTER PATIENT INDEX SUBSCRIBING DETAILS: MPI is to call ONLY its own RPCs, with the following exceptions allowed: MPIF ACK CHECK MPIF EXP PDAT REMOTE MPIF INACTIVATE MPIF REMOTE SPI MPIF REMOTE ICN UPDATE MPIF CHANGE CMOR RG REM ACTIVITY RG REMOTE HL7 TASK MPIF SSN DUPS SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING DETAILS: CIRN is to call ONLY its own RPCs. SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA SUBSCRIBING DETAILS: MPIF is to call ONLY its own RPCs. SUBSCRIBING PACKAGE: CORBA SERVICES SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM SUBSCRIBING PACKAGE: INCOME VERIFICATION MATCH SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL DBA Comments: JSHARVEY 20070124/ added IVM and EAS. 1/18/13-MM: Added Beneficiary Travel as a subscriber. Associated patch is DGBT*1.0*20. Bene Travel RPC is DGBT CLAIM DEDUCTIBLE PAID and will be using HL7 to access the RPC. Justification from developer: "They will be using them to access Beneficiary Claim Information at any site the patient has been to in the current month. A single array node is being returned with number of trips, amount of deductible paid, if any etc." DATE/TIME EDITED: JAN 24, 2007@22:22 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HARTLEY,PETER WITH CONCURRENCE OF: FORT,WALLY DATE/TIME EDITED: JAN 24, 2007@22:23 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HARTLEY,PETER WITH CONCURRENCE OF: FORT,WALLY DATE/TIME EDITED: JAN 18, 2013@16:56 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: DELLINGER,BARRY WITH CONCURRENCE OF: WESTRA,HERLAN NUMBER: 3151 IA #: 3151 FILE NUMBER: 9000010.07 GLOBAL ROOT: AUPNVPOV( DATE CREATED: JUL 28, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ONCOLOGY DISEASE INDEX ID: AUPNVPOV( GLOBAL REFERENCE: AUPNVPOV(D0,0) FIELD NUMBER: .01 FIELD NAME: POV LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .02 FIELD NAME: PATIENT NAME LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0;3 ACCESS: Read w/Fileman GENERAL DESCRIPTION: ONCOLOGY needs to read with FileMan the following V POV (9000010.07) fields for its [Disease Index] option: VIEWER: PATRICK,PAT VIEWER: LEWIS-LITNER,ANN E VIEWER: KNOEPFLE,RICH STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31820470 KEYWORDS: ONCOLOGY KEYWORDS: DISEASE INDEX SUBSCRIBING PACKAGE: ONCOLOGY ISC: Hines NUMBER: 3152 IA #: 3152 DATE CREATED: JUL 31, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXBUTL2 NAME: TIU use of PXBUTL2 ID: PXBUTL2 GENERAL DESCRIPTION: TIU calls PRV^PXBUTL2 to get the default provider. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31828095 COMPONENT/ENTRY POINT: PRV COMPONENT DESCRIPTION: PRV(CLINIC) ;Get default provider and all providers associated with a clinic VARIABLES: CLINIC TYPE: Input VARIABLES DESCRIPTION: ifn of clinic in file 44 VARIABLES: PXBPMT TYPE: Output VARIABLES DESCRIPTION: Array subscripted as follows: Default Provider: PXBPMT("DEF",NAME,+X)="" All Providers associated with a Clinic: PXBPMT("PRV",NAME,+X)="" Subscripts: NAME is the Name field (#.01) in New Person file (#200) +X is the ifn of New Person in New Person file (#200) SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 3154 IA #: 3154 DATE CREATED: AUG 01, 2000 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORQ1 NAME: Health Summary Current Orders ID: ORQ1 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31831960 KEYWORDS: GMTSORC3 KEYWORDS: ORQ1 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: This entry point retrieve a list of current orders and returns results in ^TMP("ORR",$J,ORLIST,i). VARIABLES: PAT TYPE: Input VARIABLES DESCRIPTION: This is a variable pointer to the patient in the format "DFN;DPT(" VARIABLES: GROUP TYPE: Input VARIABLES DESCRIPTION: This is the Display Group (file 100.98), allowing orders to be clustered into groups other than by package. VARIABLES: FLG TYPE: Input VARIABLES DESCRIPTION: Indicates orders to display: 1. All => 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 2. Active/Current => 3,4,5,6, 8,9, 11, 15 Includes CONTEXT HRS 1,2,7,13 & Action Status=13 Orders in ^OR(100,"AC",PAT,TM,IFN,ACTION) 3. Discontinued => 1 12,13 4. Completed/Expired => 2, 7 5. Expiring => 3,4,5,6, 8,9 6. Recent Activity => 1,2,3,4,5,6,7,8,9, 12, 15 Orders in ^OR(100,"AR",PAT,TM,IFN,ACTION) 7. Pending => 5 8. Unverified => 1, 3,4,5,6, 8,9, 15 9. Unverified/Nurse => 1, 3,4,5,6, 8,9, 15 10. Unverified/Clerk => 1, 3,4,5,6, 8,9, 15 11. Unsigned => 1,2,3,4,5,6,7,8,9,10,11, 13,14,15 Orders in ^OR(100,"AS",PAT,TM,IFN) 12. Flagged => 1,2,3,4,5,6,7,8,9, 12,13,14,15 13. Verbal/Phoned => 1,2,3,4,5,6,7,8,9, 13,14,15 Nature of order of verbal or phoned 14. Verb/Phn unsigned => 1,2,3,4,5,6,7,8,9, 13,14,15 Nature of order V or P & unsigned 15. Admission => 10 16. Discharge => 10 17. Transfer => 10 Orders in ^OR(100,"AEVNT",PAT,,IFN) 18. On Hold => 3 19. New Orders => 10,11 Orders in ^TMP("ORNEW",$J,ORIFN) 20. Chart Review => 1, 3,4,5,6, 8,9, 15 21. Chart Copy Summary=> same as All w/screen on Nature of order 22. Lapsed => 14 23. Active status => 6 VARIABLES: EXPAND TYPE: Input VARIABLES DESCRIPTION: Internal entry number of parent order, used to expand child orders. VARIABLES: SDATE TYPE: Input VARIABLES DESCRIPTION: Start date (FM format). VARIABLES: EDATE TYPE: Input VARIABLES DESCRIPTION: End date (FM format). VARIABLES: DETAIL TYPE: Input VARIABLES DESCRIPTION: Level of detail to be returned (optional, default=0) 0 => ^TMP("ORR",$J,ORLIST,i) = order # 1 => ^TMP("ORR",$J,ORLIST,i) = order #^display group^when entered^ start d/t^stop d/t^status^sts abbrv ^TMP("ORR",$J,ORLIST,i,"TX",j) = order text VARIABLES: MULTI TYPE: Input VARIABLES DESCRIPTION: Multiple order flag: 0 = Don't allow multiple occurances of order 1 = Allow multiple occurances VARIABLES: TMP('ORR',$J,ORLIST,i) TYPE: Output VARIABLES DESCRIPTION: Returns data about current orders depending on the value of the input variable DETAIL: DETAIL=0 ^TMP("ORR",$J,ORLIST,i) = order # DETAIL=1 ^TMP("ORR",$J,ORLIST,i) = order #^display group^when entered^ start d/t^stop d/t^status^sts abbrv ^TMP("ORR",$J,ORLIST,i,"TX",j) = order text SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT SUBSCRIBING DETAILS: ADDED 9/25/08 SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: Effective with VPR*1*0. DBA Comments: 08/02/13 DT: Add VPR as subscriber, effective with VPR*1*0. Melanie Buechler represents OR and VPR. DATE/TIME EDITED: SEP 25, 2008@09:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: BUECHLER,MELANIE DATE/TIME EDITED: AUG 02, 2013@13:05 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: BUECHLER,MELANIE NUMBER: 3155 IA #: 3155 DATE CREATED: AUG 01, 2000 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIULAPI NAME: TIU/Health Summary by Visit Date ID: TIULAPI GENERAL DESCRIPTION: The routine TIULAPI controls the branching for extracting documents by occurrence, date or type for a given patient. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31833695 KEYWORDS: GMTSCW KEYWORDS: TIULAPI KEYWORDS: MAIN COMPONENT/ENTRY POINT: MAIN COMPONENT DESCRIPTION: This entry point is used to extract TIU documents by Visit Date for the Clinical Warnings Component (CW). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Pointer to the patient file (#2) (required) VARIABLES: TIUDOC TYPE: Input VARIABLES DESCRIPTION: TIU document class, IEN of the TIU DOCUMENT DEFINITION file (#8925.1) (required) VARIABLES: TIME1 TYPE: Input VARIABLES DESCRIPTION: The beginning date for a range of dates to extract TIU documents (optional, default 6666666) VARIABLES: TIME2 TYPE: Input VARIABLES DESCRIPTION: The ending date for a range of dates to extract TIU documents (optional, default 9999999) VARIABLES: OCCLIM TYPE: Input VARIABLES DESCRIPTION: The number of occurrences of teh type of document to extract (optional, default 999) VARIABLES: TEXT TYPE: Input VARIABLES DESCRIPTION: Boolean flag (1/0) to include or not to include document text with the extraction (required) SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City NUMBER: 3156 IA #: 3156 DATE CREATED: AUG 04, 2000 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XLFCRC NAME: XLFCRC ID: XLFCRC GENERAL DESCRIPTION: This routine has two API's, CRC32 and CRC16. SET CRC=$$CRC32^XLFCRC(string) A check-sum can also be calculated over multiple strings. SET (I,C)=0 FOR SET I=$ORDER(X(I)) QUIT:'I DO . SET C=$$CRC16^XLFCRC(X(I),C) or SET I=0,C=4294967295 FOR SET I=$ORDER(X(I)) QUIT:'I DO . SET C=$$CRC32^XLFCRC(X(I),C) as long as the save method is used all the time. These have been approved for inclusion in a future ANSI M[UMPS] language standard as part of the library. STATUS: Active KEYWORDS: CRC COMPONENT/ENTRY POINT: $$CRC32(string[,seed]) COMPONENT DESCRIPTION: This function computes a Cyclic Redundance Code of the 8-bit character string string, using X^32 + X^26 + X^23 + X^22 + X^16 + X^12 + X^11 + X^10 + X^8 + X^7 + X^5 + X^4 + X^2 + X + 1 as the polynominal. The optional parameter seed may supply an initial value, which allows for running CRC calculations on multiple strings. If the parameter seed is not specified, a default value of 4,294,967,295 (2^32-1) is assumed. The value of seed is limited to 0 <= seed <= 2^32. The function value will be between 0 and 2^32. VARIABLES: string TYPE: Input VARIABLES DESCRIPTION: String to compute the CRC32 on. VARIABLES: seed TYPE: Input VARIABLES DESCRIPTION: Optional seed value, Needed to compute the CRC32 over multiple strings. COMPONENT/ENTRY POINT: $$CRC16(string[,seed]) COMPONENT DESCRIPTION: This function computes a Cyclic Redundance Code of the 8-bit character string string, using X^16 + X^15 + X^2 + 1as the polynominal. The optional parameter seed may supply an initial value, which allows for running CRC calculations on multiple strings. If the parameter seed is not specified, a default value of 0 is assumed. The value of seed is limited to 0 <= seed <= 2^16. The function value will be between 0 and 2^16. VARIABLES: string TYPE: Input VARIABLES DESCRIPTION: String to compute the CRC16 on. VARIABLES: seed TYPE: Input VARIABLES DESCRIPTION: Optional seed value. Needed to compute the CRC16 over multiple strings. DBA Comments: Was in Withdrawn state since creation. As per Wally, IA is wel-formed, necessary, and should be activated. Activated 11/6/07. JSHarvey DATE ACTIVATED: NOV 06, 2007 DATE/TIME EDITED: NOV 06, 2007@11:58 ACTION: APPROVED AT THE REQUEST OF: FORT,WALLY NUMBER: 3157 IA #: 3157 DATE CREATED: AUG 07, 2000 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGPTFAPI NAME: PATIENT TREATMENT FILE DATA ID: DGPTFAPI CREATOR: TROST,DEBBIE GENERAL DESCRIPTION: This call will return data from the Patient Treatment file, initially the type of disposition, place of disposition (name) and the ICD codes, but more data may be returned later. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31855485 COMPONENT/ENTRY POINT: RPC(.RESULTS,PTFNUMBR) VARIABLES: RESULTS TYPE: Output VARIABLES DESCRIPTION: An array with following nodes: (0)=1 or -1 if error (1)=type of disposition^place of disposition^1st ICD code^Coding System (p80.4) (2)=2nd thru 10th ICD codes (3)=Present On Admission for DX and 2nd thru 10th Secondary Diag Codes. VARIABLES: ptfnumbr TYPE: Input VARIABLES DESCRIPTION: the Patient Treatment file IFN (.001 field of file #45) SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES DBA Comments: Deactivated on 04/05/12 by Debbie Trost for edits to support the ICD10 Remediation. Alan Skinner is making the edits and the Remedition Team will address the impact on the Case Registries Subscriber in ICD10 Remediation coding. The tentative release date is 10/1/2012. Activated/approved on 04/05/12. Deactivated on 4/6/12 by Debbie Trost for correction to text to be done by Alan Skinner. Activated/approved on 4/06/12. 4/9/12 - Modified description for DG PATIENT TREATMENT DATA RPC entry in the Remote Procedure (#8994) file to match description changes in ICR. DATE ACTIVATED: APR 05, 2012 DATE/TIME EDITED: APR 05, 2012@16:33 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: SKINNER,ALAN WITH CONCURRENCE OF: SKINNER,ALAN DATE/TIME EDITED: APR 05, 2012@18:08 ACTION: APPROVED AT THE REQUEST OF: SKINNER,ALAN WITH CONCURRENCE OF: SKINNER,ALAN NUMBER: 3158 IA #: 3158 DATE CREATED: AUG 08, 2000 CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MPIFSPC NAME: $$CHECKDG ID: MPIFSPC GENERAL DESCRIPTION: $$CHECKDG^MPIFSPC calculates the checksum for a given 10 digit Integration Control Number (ICN). STATUS: Active MAIL MESSAGE: 31867886 COMPONENT/ENTRY POINT: $$CHECKDG(NUM) VARIABLES: NUM TYPE: Input VARIABLES DESCRIPTION: 10 digit ICN (without check digits) VARIABLES: $$CHECKDG TYPE: Output VARIABLES DESCRIPTION: 6 digit checksum for the ICN SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 3160 IA #: 3160 DATE CREATED: AUG 09, 2000 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCMED NAME: PROCEDURE RESULTING ID: GMRCMED STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31868491 COMPONENT/ENTRY POINT: MEDCOMP COMPONENT DESCRIPTION: This entry point provides a mechanism for CPRS and Clinical Procedures to associate a procedure result with a Consult Procedure request. VARIABLES: GMRCDA TYPE: Input VARIABLES DESCRIPTION: IEN from REQUEST/CONSULTATION (#123) file VARIABLES: GMRCRSLT TYPE: Input VARIABLES DESCRIPTION: Varible pointer form of a procedure result from a Medicine data file or Clinical Procedures. e.g. 19;MCAR(691.5, 21;MDD(702, VARIABLES: GMRCAD TYPE: Input VARIABLES DESCRIPTION: FM date/time of action (optional) VARIABLES: GMRCORNP TYPE: Input VARIABLES DESCRIPTION: DUZ of person taking action VARIABLES: GMRCALRT TYPE: Input VARIABLES DESCRIPTION: Array of users to receive alert in format ARR(DUZ)="" COMPONENT/ENTRY POINT: CPROC COMPONENT DESCRIPTION: This entry point is provided for use by Clinical Procedures to determine if a Procedure ordered in CPRS is linked to a Clinical Procedure. VARIABLES: PROC TYPE: Input VARIABLES DESCRIPTION: IEN from GMRC PROCEDURE (#123.3) file COMPONENT/ENTRY POINT: CPLINK COMPONENT DESCRIPTION: Entry point provided for Clinical Procedures to determine if a particular entry in the CP DEFINITION (#702.01) file is linked to an entry in the GMRC PROCEDURE (#123.3) file. VARIABLES: PROC TYPE: Input VARIABLES DESCRIPTION: IEN from CP DEFINITION (#702.01) file. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Hines NUMBER: 3161 IA #: 3161 FILE NUMBER: 100 GLOBAL ROOT: OR(100, DATE CREATED: AUG 09, 2000 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Point to OR(100) ID: OR(100, GLOBAL REFERENCE: OR(100,D0) FIELD NUMBER: .01 FIELD NAME: ORDER # LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the internal number of the order. GENERAL DESCRIPTION: This agreements documents the clinical packages that have permission to point to the Orders file #100 from within their own package files. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31868662 SUBSCRIBING PACKAGE: DIETETICS ISC: Hines SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING PACKAGE: PROSTHETICS ISC: Hines SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 10/21/14-MC: Requested by Carolyn Wheless and approved by Teresa Chung for VPS*1*4.VPS will need to provide lab order package information for a patient order to VetLink. DATE/TIME EDITED: OCT 21, 2014@16:22 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: CHUNG,TERESA NUMBER: 3162 IA #: 3162 FILE NUMBER: 123 GLOBAL ROOT: GMR(123, DATE CREATED: AUG 09, 2000 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: POINT TO REQUEST/CONSULTATION (#123) FILE ID: GMR(123, GENERAL DESCRIPTION: This Integration Agreement documents the clinical packages that have permission to point to the REQUEST/CONSULTATION (#123) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31868491 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: PROSTHETICS ISC: Hines SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Hines NUMBER: 3164 IA #: 3164 DATE CREATED: AUG 14, 2000 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DG PATIENT TREATMENT DATA REMOTE PROCEDURE: DG PATIENT TREATMENT DATA GENERAL DESCRIPTION: This call will return data from the Patient Treatment file, initially the place of disposition (name) and the ICD9 codes, but more data may be returned later. (This IA# is for the RPC; IA#3157 is for the API) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31884789 NUMBER: 3165 IA #: 3165 FILE NUMBER: 50 GLOBAL ROOT: PSDRUG( DATE CREATED: AUG 14, 2000 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DRUG FILE ACTIVITY LOG ADD/EDIT BY OUTPATIENT PHARMACY ID: PSDRUG( GLOBAL REFERENCE: PSDRUG(D0,4,0) GLOBAL DESCRIPTION: Activity Log multiple global header node. Insert and update the counters of the header node. GLOBAL REFERENCE: PSDRUG(D0,4,D1,0) FIELD NUMBER: .01 FIELD NAME: ACTIVITY LOG LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 1 FIELD NAME: REASON LOCATION: 0;2 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 2 FIELD NAME: INITIATOR OF ACTIVITY LOCATION: 0;3 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 3 FIELD NAME: FIELD EDITED LOCATION: 0;4 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 4 FIELD NAME: VALUE LOCATION: 0;5 ACCESS: Direct Global R/W & w/Fileman GLOBAL REFERENCE: PSDRUG(D0,3) FIELD NUMBER: 213 FIELD NAME: CMOP DISPENSE LOCATION: 3;1 ACCESS: Direct Global R/W & w/Fileman GENERAL DESCRIPTION: CMOP functionality in the Outpatient Pharmacy application has a need to enter comments into the ACTIVITY LOG field (# 214) multiple of the Drug file (# 50). This functionality also reads and sets the CMOP DISPENSE field (# 215) and its index "^PSDRUG("AQ"," within the Drug file (# 50). The node ^PSDRUG(D0,4,D1) is looped through to find the last entry in the Activity Log multiple prior to inserting a new comment. If the header node for the Activity Log field multiple is not present a header node is inserted into the database. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31887295 KEYWORDS: CMOP KEYWORDS: OUTPATIENT KEYWORDS: ACTIVITY LOG SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 3166 IA #: 3166 DATE CREATED: AUG 15, 2000 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSSDIN NAME: CALL FOR PSSDIN - NFI TEXT AVAIL. FOR ORD.ITEM/DISP.DRUG ID: PSSDIN GENERAL DESCRIPTION: Outpatient Pharmacy, Inpatient Medications and Computerized Patient Record System all request permission to call the function provided by the Pharmacy Data Management package - routine name ^PSSDIN. This call builds the temporary global ^TMP("PSSDIN" with the National Formulary Indicator text for both orderable items and dispense drugs that are marked as restricted items. Sending input of either orderable items or dispense drugs is optional and the routine will only return text where it receives either or both variables. The text may be displayed upon request. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33057322 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: This entry point builds the temporary global ^TMP("PSSDIN", with National Formulary Indicator text for both orderable items and dispense drugs that are marked as restricted items. The syntax of this call is D EN^PSSDIN(PSSOI,PSSDD). VARIABLES: PSSOI TYPE: Input VARIABLES DESCRIPTION: Orderable item - This is the Orderable Item internal entry number in the global ^PS(50.7,# (PHARMACY ORDERABLE ITEM file #50.7). VARIABLES: PSSDD TYPE: Input VARIABLES DESCRIPTION: Dispense Drug - This is the Drug internal entry number in the global ^PSDRUG(# (DRUG file #50). VARIABLES: TMP TYPE: Output VARIABLES DESCRIPTION: The call builds all of the NFI text. If entries exist in the global ^PSDRUG(PSSDD,9, (DRUG TEXT ENTRY SUB-FILE #50.037 of DRUG file #50) which points to various drug text entries (dtien), located in the DRUG TEXT file (#51.7) then the global ^TMP("PSSDIN",$J,"DD",PSSDD,dtien,index) is built. If entries exist in the global ^PS(50.7,PSSOI,1 (OI-DRUG TEXT ENTRY SUB-FILE #50.76 of PHARMACY ORDERABLE ITEM file # 50.7) which points to various drug text entries (dtien), located in the DRUG TEXT file (#51.7) then the global ^TMP("PSSDIN",$J,"OI",PSSOI,dtien,index) is built. COMPONENT/ENTRY POINT: PROMPT COMPONENT DESCRIPTION: This entry point checks for the existance of the ^TMP("PSSDIN" global and prompts the user accordingly with the message: Restriction/Guideline(s) exist. Display? O - Orderable Item text available, D - Dispense Drug text available, B - both Orderable Item text and Dispense Drug text are available, N - NO the default not to display any text. If the ^TMP("PSSDIN" global is not found nothing is prompted. If "B" is selected the function will return "Y" as "Y" was used initially not "B". The syntax of this call is S var=$$PROMPT^PSSDIN. SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Birmingham NUMBER: 3167 IA #: 3167 DATE CREATED: AUG 25, 2000 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJORPOE NAME: 3167 ID: PSJORPOE CREATOR: THOMPSON,SETH GENERAL DESCRIPTION: Inpatient Medications is providing 3 entry points to Computerized Patient Record System (CPRS) as a part of the Pharmacy Order Enhancements project. 1) Entry point $$STARTSTP returns to CPRS the setting for the DEFAULT START DATE CALCULATION for the ward the patient is on, Default Start Date/Time based on the parameter, and the number of days or hours the order would last. 2) Entry Point $$RESOLVE returns the parameter passed by CPRS to be resolved and the Date/Time it was resolved to. 3) Entry point $$SCHREQ returns a 1 if a schedule should be required for the order being placed via the Inpatient Medications dialogue through CPRS or a 0 if no schedule is required. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33144825 COMPONENT/ENTRY POINT: $$STARTSTP COMPONENT DESCRIPTION: Entry point $$STARTSTP(PSGP,SCH,OI,PSJPWD,PSGORD,PSJADM,STARTDT) returns to CPRS the setting for the DEFAULT START DATE CALCULATION for the ward the patient is on, Default Start Date/Time based on the parameter, and the number of days or hours the order would last. VARIABLES: PSGP TYPE: Input VARIABLES DESCRIPTION: This is the IEN of the patient from the PATIENT file (#2). It is required. VARIABLES: SCH TYPE: Input VARIABLES DESCRIPTION: This is the schedule for the order being placed. VARIABLES: OI TYPE: Input VARIABLES DESCRIPTION: This is the IEN of the Orderable Item from the PHARMACY ORDERABLE ITEM file (#50.7). VARIABLES: PSJPWD TYPE: Input VARIABLES DESCRIPTION: This is the IEN of the ward location. It is optional. VARIABLES: PSGORD TYPE: Input VARIABLES DESCRIPTION: This is the IEN of the order with the U or V if the order being placed is a renewal of another order. It is optional. VARIABLES: $$STARTSTP TYPE: Output VARIABLES DESCRIPTION: $$STARTSTP=WARD PARAMETER^DEFAULT START DATE/TIME^#_D(NUMBER OF DAYS ORDER LASTS) OR #_H(NUMBER OF HOURS ORDER LASTS) OR 0. VARIABLES: PSJADM TYPE: Input VARIABLES DESCRIPTION: This is the admin times. (Optional) VARIABLES: STARTDT TYPE: Input VARIABLES DESCRIPTION: This is the date upon which calculations are based instead of doing all calculations against NOW. If nothing is passed in, it will default to NOW. (Optional) COMPONENT/ENTRY POINT: $$RESOLVE COMPONENT DESCRIPTION: Entry Point $$RESOLVE(PSGP,SCH,OI,PCH,PSJPWD) returns the parameter passed by CPRS to be resolved and the Date/Time it was resolved to. VARIABLES: PSGP TYPE: Input VARIABLES DESCRIPTION: This is the IEN of the patient from the PATIENT file (#2). It is required. VARIABLES: SCH TYPE: Input VARIABLES DESCRIPTION: This is the schedule for the order being placed. It is required. VARIABLES: OI TYPE: Input VARIABLES DESCRIPTION: This is the IEN of the Orderable Item from the PHARMACY ORDERABLE ITEM file (#50.7). VARIABLES: PCH TYPE: Input VARIABLES DESCRIPTION: This is the provider's choice of time for the order to start. Allowable choices are NOW, NEXT, and CLOSEST. VARIABLES: PSJPWD TYPE: Input VARIABLES DESCRIPTION: This is the IEN of the ward location. It is optional. VARIABLES: $$RESOLVE TYPE: Output VARIABLES DESCRIPTION: $$RESOLVE=PCH_^_Resolved Start Date/Time. COMPONENT/ENTRY POINT: $$SCHREQ COMPONENT DESCRIPTION: Entry point $$SCHREQ(MR,OI,DD) returns a 1 if a schedule should be required for the order being placed via the Inpatient Medications dialogue through CPRS or a 0 if no schedule is required. VARIABLES: MR TYPE: Input VARIABLES DESCRIPTION: Medication Route from MEDICATION ROUTES file (#51.2). Required. VARIABLES: OI TYPE: Input VARIABLES DESCRIPTION: Orderable Item IEN from PHARAMACY ORDERABLE ITEM file (#50.7). Optional. VARIABLES: DD TYPE: Input VARIABLES DESCRIPTION: Dispense Drug IEN from DRUG file (#50). Optional. VARIABLES: $$SCHREQ TYPE: Output VARIABLES DESCRIPTION: $$SCHREQ will equal 1 if a schedule is required or a 0 if no schedule is required. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City DATE ACTIVATED: JUN 08, 2011 DATE/TIME EDITED: JUN 07, 2011@15:59 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: THOMPSON,SETH WITH CONCURRENCE OF: SCOTT,APRIL DATE/TIME EDITED: JUN 08, 2011@12:04 ACTION: APPROVED AT THE REQUEST OF: THOMPSON,SETH WITH CONCURRENCE OF: SCOTT,APRIL NUMBER: 3168 IA #: 3168 DATE CREATED: AUG 16, 2000 CUSTODIAL PACKAGE: TOOLKIT USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XDRDVAL1 NAME: DBIA3168 ID: XDRDVAL1 GENERAL DESCRIPTION: CIRN needs to use the Toolkit routine call RMOVPAIR^XDRDVAL1 to remove pairs from the merge process based on CIRN Exceptions. STATUS: Active MAIL MESSAGE: 31896289 COMPONENT/ENTRY POINT: RMOVPAIR COMPONENT DESCRIPTION: This call is used to remove a pair of duplicate records from the merge process. VARIABLES: FROM TYPE: Input VARIABLES DESCRIPTION: DFN of patient record merging from. VARIABLES: TO TYPE: Input VARIABLES DESCRIPTION: DFN of patient record file (#2) merging into. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: IEN of Duplicate Record file (#15), where record pairs are listed. VARIABLES: array TYPE: Input VARIABLES DESCRIPTION: Array of records to be merged. SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 3169 IA #: 3169 FILE NUMBER: 101.43 GLOBAL ROOT: ORD(101.43, DATE CREATED: AUG 21, 2000 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GLOBAL READ OF FILE 101.43 ID: ORD(101.43, GLOBAL REFERENCE: ORD(101.43,'S.PROC',NAME,DA) GLOBAL DESCRIPTION: This cross-reference holds those records that are of the PROCEDURE type. GLOBAL REFERENCE: ORD(101.43,DA,0) FIELD NUMBER: 2 FIELD NAME: ID LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: This fields holds the IEN and a descriptor for the source file from which the entry was created. FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the name of the ORDERABLE ITEM. GLOBAL REFERENCE: ORD(101.43,DA,.1) FIELD NUMBER: .1 FIELD NAME: INACTIVATED LOCATION: .1;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to indicate that an ORDERABLE ITEM has been inactivated and is no longer in use for ordering in CPRS. GLOBAL REFERENCE: ORD(101.43,DA(1),2,DA,0) FIELD NUMBER: 101.432 FIELD NAME: SYNONYM LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This multiple field contains the list of synonyms for the particular ORDERABLE ITEM. GENERAL DESCRIPTION: Consult/Request Tracking utilizes global reads of the global ^ORD(101.43, to facilitate a data conversion included in patch GMRC*3*15. This conversion only reads those orderable items of the Procedure type by utilizing the "S.PROC" cross-reference. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28690761 SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City EDITOR: BUECHLER,MELANIE K EDITOR: RUTHERFORD,JERALD F NUMBER: 3170 IA #: 3170 DATE CREATED: AUG 21, 2000 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORDD43 NAME: CHANGE ORDERABLE ITEM ID ID: ORDD43 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28690761 COMPONENT/ENTRY POINT: ID(CURRENTID,NEWID) COMPONENT DESCRIPTION: When the source file of ORDERABLE ITEMS for an interfacing package changes, the ID field of file 101.43 must be changed to reference an entry within the new file. VARIABLES: CURRENTID TYPE: Input VARIABLES DESCRIPTION: The current ID of an orderable item. VARIABLES: NEWID TYPE: Input VARIABLES DESCRIPTION: The ID to which the ORDERABLE ITEM should be changed. SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: During the post-install of GMRC*3*15, the source file for PROCEDURE type orderable items is converted from the PROTOCOL (#101) file to the GMRC PROCEDURE (#123.3) file. Upon conversion of an entry the ID field of the corresponding ORDERABLE ITEM is changed to reference file 123.3. NUMBER: 3171 IA #: 3171 DATE CREATED: AUG 21, 2000 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORWRP NAME: PRINT REPORT TO GLOBAL ARRAY ID: ORWRP GENERAL DESCRIPTION: The START^ORWRP call allows the opening of the OR WORKSTATION device and printing of a report to that device, thereby returning the text of the report in a global array descendant from ^TMP("ORDATA",$J,. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 28690761 COMPONENT/ENTRY POINT: START(MWIDTH,CALL) COMPONENT DESCRIPTION: The START^ORWRP call allows the opening of the OR WORKSTATION device and printing of a report to that device, thereby returning the text of the report in a global array descendant from ^TMP("ORDATA",$J,. VARIABLES: MWIDTH TYPE: Input VARIABLES DESCRIPTION: This is the margin width to which the report should be formatted. VARIABLES: CALL TYPE: Input VARIABLES DESCRIPTION: This variable contains a line tag and routine in the format "TAG^ROUTINE(PARAM)" that will be executed to produce the report output. VARIABLES: TMP('ORDATA',$J, TYPE: Output VARIABLES DESCRIPTION: The output from the linetag and routine executed in the variable CALL will be directed to the global array ^TMP("ORDATA",$J, SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: Consult/Request Tracking utilizes this routine to produce a global array of a report from the Medicine package utilizing the EN^MCAPI(result) entry point. SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE EDITOR: RUTHERFORD,JERALD F NUMBER: 3172 IA #: 3172 DATE CREATED: AUG 28, 2000 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: %ZISP NAME: Special Printer Variables ID: %ZISP GENERAL DESCRIPTION: Entry points for special printer variables. STATUS: Active MAIL MESSAGE: 31943425 COMPONENT/ENTRY POINT: PKILL COMPONENT DESCRIPTION: Use PKILL^%ZISP to kill printer-specific Device Handler variables. All output variables defined by the PSET^%ZISP entry point are killed. COMPONENT/ENTRY POINT: PSET COMPONENT DESCRIPTION: Use PSET^%ZISP to define a set of variables that toggle special printer modes. The corresponding fields in the TERMINAL TYPE file entry for the terminal type in question must be correctly set up, however; that is where PSET^%ZISP retrieves its output values. To toggle a printer mode with one of PSET^%ZISP's output variables, write the variable to the printer using indirection, as follows: D PSET^%ZISP W @IOBARON VARIABLES: IOST(0) TYPE: Input VARIABLES DESCRIPTION: Pointer to the TERMINAL TYPE entry for the printer in question, as set up by the Device Handler. VARIABLES: IOBAROFF TYPE: Output VARIABLES DESCRIPTION: Bar code off VARIABLES: IOBARON TYPE: Output VARIABLES DESCRIPTION: Bar code on VARIABLES: IOCLROFF TYPE: Output VARIABLES DESCRIPTION: Color off VARIABLES: IOCLRON TYPE: Output VARIABLES DESCRIPTION: Color on VARIABLES: IODPLXL TYPE: Output VARIABLES DESCRIPTION: Duplex, long edge binding VARIABLES: IODPLXS TYPE: Output VARIABLES DESCRIPTION: Duplex, short edge binding VARIABLES: IOITLOFF TYPE: Output VARIABLES DESCRIPTION: Italics off VARIABLES: IOITLON TYPE: Output VARIABLES DESCRIPTION: Italics on VARIABLES: IOSMPLX TYPE: Output VARIABLES DESCRIPTION: Simplex VARIABLES: IOSPROFF TYPE: Output VARIABLES DESCRIPTION: Superscript off VARIABLES: IOSPRON TYPE: Output VARIABLES DESCRIPTION: Superscript on VARIABLES: IOSUBOFF TYPE: Output VARIABLES DESCRIPTION: Subscript off VARIABLES: IOSUBON TYPE: Output VARIABLES DESCRIPTION: Subscript on NUMBER: 3173 IA #: 3173 DATE CREATED: AUG 28, 2000 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XGF NAME: XGF Function Library ID: XGF GENERAL DESCRIPTION: This XGF Function Library supports terminals that are ANSI-compatible and at least VT100-compatible. As a result, this software does not support QUME QVT102/QVT102A terminals. Programmer Tools > D ^XGFDEMO: Demo Program To run an interactive demonstration showing the capabilities provided by the XGF Function Library, you can run the XGF demo program. From the programmer prompt, type the following: >D ^XGFDEMO Functional Division of XGF Function Library Cursor/Text Output: IOXY^XGF, SAY^XGF, SAYU^XGF. Keyboard Reader: $$READ^XGF. Setup/Cleanup: CLEAN^XGF, INITKB^XGF, PREP^XGF, RESETKB^XGF. Text Window: CLEAR^XGF, FRAME^XGF, RESTORE^XGF, SAVE^XGF, WIN^XGF. Video Attribute: CHGA^XGF, SETA^XGF. STATUS: Active MAIL MESSAGE: 31945072 COMPONENT/ENTRY POINT: CHGA COMPONENT DESCRIPTION: Usage D CHGA^XGF(atr_codes) Changes individual video attributes for subsequent screen writes. Use this entry point to change individual video attributes for subsequent output. This entry point is different from SETA^XGF in that individual video attributes can be set without affecting all video attributes at once. A call to PREP^XGF must be made at some point prior to calling CHGA^XGF. The attribute codes are not case sensitive. You can append them if you want to set more than one attribute. If you include more than one attribute, their order is not important. B0 and B1 turn off and on the blink attribute; I0 and I1 turn off and on the intensity attribute; R0 and R1 turn off and on the reverse attribute; U0 and U1 turn off and on the underline attribute. E1 turns off all attributes. G0 and G1 turn off and on recognition of an alternate graphics character set so that you can use special graphic characters, in particular those set up by Kernel's GSET^%ZISS entry point. To use graphics characters, be sure you turn on graphics first (with G1) and turn graphics off afterwards (with G0). The change in attribute remains in effect until another CHGA^XGF, PREP^XGF or SETA^XGF CALL is made. VARIABLES: B1 TYPE: Input VARIABLES DESCRIPTION: Blink on VARIABLES: B0 TYPE: Input VARIABLES DESCRIPTION: Blink off VARIABLES: I1 TYPE: Input VARIABLES DESCRIPTION: Intensity high VARIABLES: I0 TYPE: Input VARIABLES DESCRIPTION: Intensity normal VARIABLES: R1 TYPE: Input VARIABLES DESCRIPTION: Reverse video on VARIABLES: R0 TYPE: Input VARIABLES DESCRIPTION: Reverse video off VARIABLES: G1 TYPE: Input VARIABLES DESCRIPTION: Graphics on VARIABLES: G0 TYPE: Input VARIABLES DESCRIPTION: Graphics off VARIABLES: U1 TYPE: Input VARIABLES DESCRIPTION: Underline on VARIABLES: U0 TYPE: Input VARIABLES DESCRIPTION: Underline off VARIABLES: E1 TYPE: Input VARIABLES DESCRIPTION: Turn all off VARIABLES: XGCURATR TYPE: Output VARIABLES DESCRIPTION: This variable always holds the current screen attribute coded as a single character, and is updated when you call CHGA^XGF. COMPONENT/ENTRY POINT: CLEAN COMPONENT DESCRIPTION: Use CLEAN^XGF to exit the XGF screen and keyboard environments. It removes XGF screen and keyboard variables and tables, turns all video attributes off, turns echo on, turns the cursor on, and sets the keypad to numeric mode. COMPONENT/ENTRY POINT: CLEAR COMPONENT DESCRIPTION: Usage D CLEAR^XGF(top,left,bottom,right) Clears a rectangular region of the screen. This entry point is useful to clear a portion of the screen. The CLEAR function works by printing spaces using the current screen attribute in the specified region. If the screen attribute is changed and then the CLEAR function used, the rectangular region is cleared in the new attribute. Acceptable values for the top and bottom parameters range from 0 to IOSL-1. Acceptable values for the left and right parameters range from 0 to IOM-1. VARIABLES: top TYPE: Input VARIABLES DESCRIPTION: Top screen coordinate for box VARIABLES: left TYPE: Input VARIABLES DESCRIPTION: Left screen coordinate for box VARIABLES: bottom TYPE: Input VARIABLES DESCRIPTION: Bottom screen coordinate for box VARIABLES: right TYPE: Input VARIABLES DESCRIPTION: Right screen coordinate for box. VARIABLES: $X,$Y TYPE: Output VARIABLES DESCRIPTION: Set to right and bottom specified as parameters COMPONENT/ENTRY POINT: FRAME COMPONENT DESCRIPTION: Usage D FRAME^XGF(top,left,bottom,right) Draws a box frame on the screen. Use this entry point to display boxes on the screen. The FRAME function does not clear or otherwise change the region that it encompasses. If you need to open an empty framed window you should use WIN^XGF entry point instead. Acceptable values for the top and bottom parameters range from 0 to IOSL-1. Acceptable values for the left and right parameters range from 0 to IOM-1.E VARIABLES: top TYPE: Input VARIABLES DESCRIPTION: Top screen coordinate for box. VARIABLES: left TYPE: Input VARIABLES DESCRIPTION: Left screen coordinate for box VARIABLES: bottom TYPE: Input VARIABLES DESCRIPTION: Bottom screen coordinate for box. VARIABLES: right TYPE: Input VARIABLES DESCRIPTION: Right screen coordinate for box. VARIABLES: $X,$Y TYPE: Output VARIABLES DESCRIPTION: Set to the right and bottom specified as parameters. COMPONENT/ENTRY POINT: INITKB COMPONENT DESCRIPTION: Usage D INITKB^XGF([term_str]) Sets up the XGF keyboard environment only. You should call INITKB^XGF once, before you start making calls to the $$READ^XGF function. This entry point turns on escape processing and any terminators that are passed. Use this entry point only if you are using XGF's Keyboard Reader independently from XGF's screen functions. Otherwise, a call to PREP^XGF does everything to set up keyboard processing that INITKB^XGF does, and aseparate call to INITKB^XGF is not necessary. Unlike PREP^XGF, INITKB^XGF does not set the keypad to application mode. INITKB does not call %ZISS. Thus, documented Kernel variables such as IOKPAM and IOKPNM are not available for use without a separate call to ENS^%ZISS. VARIABLES: term_str TYPE: Input VARIABLES DESCRIPTION: String of characters that should terminate the read. COMPONENT/ENTRY POINT: IOXY COMPONENT DESCRIPTION: Usage D IOXY^XGF(row,col) Positions cursor on the screen at a screen coordinate. This entry point is similar to Kernel's X IOXY function. The row parameter must be between 0 and IOSL-1; the column parameter must be between 0 and IOM- 1. A call to PREP^XGF must be made at some point prior to calling IOXY^XGF. You can specify row and column parameters relative to the current $X and $Y by specifying "+" or "-" to increment or decrement $X or $Y by 1. You can increment or decrement by more than one if you add a number as well, such as "-5" or "+10". Note that you must use quotes to pass a "+" or "-". Otherwise, to specify exact locations for row and column, pass numbers. VARIABLES: row TYPE: Input VARIABLES DESCRIPTION: Row position to move cursor to. VARIABLES: col TYPE: Input VARIABLES DESCRIPTION: Column position to move cursor to. VARIABLES: $X,$Y TYPE: Output VARIABLES DESCRIPTION: Set to the row and column specified as parameters. COMPONENT/ENTRY POINT: PREP COMPONENT DESCRIPTION: Usage D PREP^XGF Sets up the XGF screen and keyboard environments. Before using any XGF screen functions, you must call the PREP^XGF entry point. PREP^XGF sets up screen control variables and tables. It also turns off all video attributes, turns echo off, turns the cursor off, sets the keypad to application mode, and clears the screen. In addition, PREP^XGF does everything that INITKB^XGF does to set up the XGF keyboard environment, including turning escape processing and terminators on. If you call PREP^XGF, a call to INITKB^XGF would be redundant. VARIABLES: XGCURATR TYPE: Output VARIABLES DESCRIPTION: One-character variable containing state of current video attribute. COMPONENT/ENTRY POINT: $$READ COMPONENT DESCRIPTION: Usage S ZYXSTR=$$READ^XGF([no_of_char][,timeout]) $$READ^XGF provides a way to perform reads using escape processing. Reads, when escape processing is turned on, are terminated by , , , , , and other special keystrokes. $$READ^XGF is a low-level reader compared to the VA FileMan reader. In some respects it is as simple as using the M read command. This read function incorporates escape processing which puts the burden on the operating system to read the arrow, function, and all other keys. A call to INITKB^XGF or PREP^XGF must be made at some point prior to calling $$READ^XGF. If the number of characters you request with the first parameter is not entered, the read does not terminate until some terminating character is pressed (or the timeout period is reached). If you don't pass the timeout parameter, DTIME is used for the timeout period. If the read times out, ^ is returned and DTOUT is left defined. VARIABLES: no_of_char TYPE: Input VARIABLES DESCRIPTION: [optional] Maximum # of characters to read. VARIABLES: timeout TYPE: Input VARIABLES DESCRIPTION: [optional] Maximum duration of read, in seconds. VARIABLES: return_value TYPE: Output VARIABLES DESCRIPTION: The string read from the user. Set to the mnemonic of the key that terminated the read; see list below or the table in routine XGKB for list of possible values. VARIABLES: DTOUT TYPE: Output VARIABLES DESCRIPTION: If defined, signifies that the read timed out. COMPONENT/ENTRY POINT: RESETKB COMPONENT DESCRIPTION: Usage D RESETKB^XGF Exits the XGF keyboard environment. You should use the RESETKB^XGF call once you finish making calls to the $$READ^XGF function. The RESETKB^XGF entry point turns terminators and escape processing off and removes any XGF keyboard environment variables. Subsequent reads are processed normally. Use this entry point only if you are using XGF's Keyboard Reader independently from XGF's screen functions. Otherwise, a call to CLEAN^XGF does everything to clean up keyboard processing that RESETKB^XGF does, and a separate call to RESETKB^XGF is not necessary. Unlike CLEAN^XGF, RESETKB^XGF does not set the keypad to numeric mode. COMPONENT/ENTRY POINT: RESTORE COMPONENT DESCRIPTION: Usage D RESTORE^XGF(save_root) Use RESTORE^XGF to restore a previously saved screen region. You can save screen regions using the WIN^XGF and SAVE^XGF entry points. RESTORE^XGF restores the saved screen region in the same screen position as the screen region was saved from. A call to PREP^XGF must be made at some point prior to calling RESTORE^XGF. Specify the array node under which to save the overlaid screen region in closed root and fully resolved form: that is, closed right parenthesis and with variable references such as $J fully resolved. Using M $NAME function is a quick way to pass fully resolved node specifications. VARIABLES: save_root TYPE: Input VARIABLES DESCRIPTION: Global/local array node, closed root form. VARIABLES: $X,$Y TYPE: Output VARIABLES DESCRIPTION: Set to the bottom right coordinate of the restored window. COMPONENT/ENTRY POINT: SAVE COMPONENT DESCRIPTION: Usage D SAVE^XGF(top,left,bottom,right,save_root) Use this entry point to save a screen region. In order to save and restore screen regions, you must do all screen output using calls in the XGF Function Library output. If you instead use the M write command for output, the screen contents cannot be saved and restored. Also, a call to PREP^XGF must be made at some point prior to calling SAVE^XGF. Specify the array node under which to save the overlaid screen region in closed root and fully resolved form: that is, closed right parenthesis and with variable references such as $J fully resolved. Using M $NAME function is a quick way to pass fully resolved node specifications. VARIABLES: top TYPE: Input VARIABLES DESCRIPTION: Top screen coordinate for box. VARIABLES: left TYPE: Input VARIABLES DESCRIPTION: Left screen coordinate for box. VARIABLES: bottom TYPE: Input VARIABLES DESCRIPTION: Bottom screen coordinate for box. VARIABLES: right TYPE: Input VARIABLES DESCRIPTION: Right screen coordinate for box. VARIABLES: save_root TYPE: Input VARIABLES DESCRIPTION: Global/local array node, closed root form. COMPONENT/ENTRY POINT: SAY COMPONENT DESCRIPTION: Usage D SAY^XGF([row],[col],str[,atr]) Outputs a string to the screen (with optional positioning and attributecontrol). Use this entry point rather than the M write command to output strings to the screen. The row and column parameters specify where to print the string. If omitted, the current row and column positions are used. If specified, the row must be between 0 and IOSL-1, and the column must be between 0 and IOM-1. A call to PREP^XGF must be made at some point prior to calling SAY^XGF. VARIABLES: row TYPE: Input VARIABLES DESCRIPTION: [optional] Row position to start write. VARIABLES: col TYPE: Input VARIABLES DESCRIPTION: String to write. VARIABLES: str TYPE: Input VARIABLES DESCRIPTION: [optional] Video attribute to write string with. VARIABLES: atr TYPE: Input VARIABLES DESCRIPTION: See CHGA^XGF for description of atr codes. VARIABLES: $X,$Y TYPE: Output VARIABLES DESCRIPTION: Set to position of the last character output. COMPONENT/ENTRY POINT: SAYU COMPONENT DESCRIPTION: Usage D SAYU^XGF([row],[col],str[,atr]) Outputs a string to the screen (with optional position and attribute control), including the ability to underline an individual character. This entry point is similar to SAY^XGF. The difference is that the first ampersand ("&") character has a special meaning in the output string; it acts as a flag to indicate that the next character should be underlined. You are only allowed one underlined character per call. Typically you would use SAYU^XGF when writing a menu option's text, in order to underline that option's speed key.A call to PREP^XGF must be made at some point prior to calling SAYU^XGF. VARIABLES: row TYPE: Input VARIABLES DESCRIPTION: [optional] Row position to start write. VARIABLES: col TYPE: Input VARIABLES DESCRIPTION: [optional] Column position to start write. VARIABLES: str TYPE: Input VARIABLES DESCRIPTION: String to write ("&" underlines next character). VARIABLES: atr TYPE: Input VARIABLES DESCRIPTION: [optional] Video attribute to write string with (see CHGA^XGF for description of atr codes). VARIABLES: $X,$Y TYPE: Output VARIABLES DESCRIPTION: Set to the position of the last character output. COMPONENT/ENTRY POINT: SETA INTEGRATION REFERENCES LIST MAR 18,2015 11:24 PAGE 10 -------------------------------------------------------------------------------- COMPONENT DESCRIPTION: Usage D SETA^XGF(atr_code) SETA^XGF sets all video attribute simultaneously, for subsequent screen output. This entry point is different from CHGA^XGF in that it takes a different form of the attribute argument, and, unlike CHGA^XGF, sets all attributes. The change in attribute remains in effect until you make another CHGA^XGF, CLEAN^XGF or SETA^XGF call. If you want only a temporary change in attribute, SAY^XGF may be a better function to use. A call to PREP^XGF must be made at some point prior to calling SETA^XGF. The value of the attribute parameter uses one bit for the value of each video attribute. The format of the bits is not documented. The current setting of all video attributes is accessible via the variable XGCURATR, however. Rather than trying to use SETA^XGF to control an individual video attribute's setting, you should use it mainly to restore the screen attributes based on a previously saved value of XGCURATR. VARIABLES: atr_code TYPE: Input VARIABLES DESCRIPTION: Single character containing the states of all video attributes as the bit values. This argument itself should be derived from a previous call to PREP^XGF, CHGA^XGF, or SETA^XGF. VARIABLES: XGCURATR TYPE: Output VARIABLES DESCRIPTION: This variable always holds the current screen attribute coded as a single character, and is updated when you call SETA^XGF. COMPONENT/ENTRY POINT: WIN COMPONENT DESCRIPTION: Usage D WIN^XGF(top,left,bottom,right[,save_root]) Use this entry point to open a text window on the screen and optionally remember what it overlays. If the save root parameter is not passed, you cannot restore the screen behind the window. In order to save the screen region that the window overlays it is absolutely necessary that screen output is done using only the functions in the XGF Function library. If you use the M write command for output, the screen contents cannot be saved. A call to PREP^XGF must be made at some point prior to calling WIN^XGF. Specify the array node under which to save the overlaid screen region in closed root and fully resolved form: that is, closed right parenthesis and with variable references such as $J fully resolved. Using M $NAME function is a quick way to pass fully resolved node specifications. To restore screens you save with the WIN^XGF function, use the RESTORE^XGF entry point. VARIABLES: top TYPE: Input VARIABLES DESCRIPTION: Top screen coordinate for box. VARIABLES: left TYPE: Input VARIABLES DESCRIPTION: Left screen coordinate for box. VARIABLES: bottom TYPE: Input VARIABLES DESCRIPTION: Bottom screen coordinate for box. VARIABLES: right TYPE: Input VARIABLES DESCRIPTION: Right screen coordinate for box. VARIABLES: save_root TYPE: Both VARIABLES DESCRIPTION: [optional] Global/local array node, closed root form. VARIABLES: $X,$Y TYPE: Output VARIABLES DESCRIPTION: If you specify a node as a fifth parameter for save_root, WIN^XGF saves the screen region you overlay in an array at that node. Set to the right and bottom coordinates you specify as parameters. NUMBER: 3174 IA #: 3174 DATE CREATED: AUG 31, 2000 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSBIPM NAME: DBIA3174 ID: PSBIPM GENERAL DESCRIPTION: The entry point EN^PSBIPM is provided by the Bar Code Medication Administration (BCMA) package to provide information to Inpatient Medications to be used in determining the start date for a renewed order. The MOB entry point is used by Inpatient Medications to get information obtained from the BCMA/CPRS Med Order function. The MOBR is used by Inpatient Medications to notify BCMA that the order has been accepted and processed by Inpatient Pharmacy. STATUS: Active EXPIRATION DATE: JAN 2003 MAIL MESSAGE: 32085880 KEYWORDS: PSBIPM COMPONENT/ENTRY POINT: $$EN COMPONENT DESCRIPTION: Provides Inpatient Medications with the type, date, and status of a patients last BCMA action. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The patients internal entry number from the PATIENT FILE, 2. VARIABLES: PSBORDX TYPE: Input VARIABLES DESCRIPTION: The pharmacy order number. VARIABLES: PSBSTUS TYPE: Output VARIABLES DESCRIPTION: This is the status of the last action. VARIABLES: PSBLAST TYPE: Output VARIABLES DESCRIPTION: A FileMan date/time. This is the date of the last action. VARIABLES: PSBADMDT TYPE: Output VARIABLES DESCRIPTION: A FileMan date/time. This is the scheduled administration time. COMPONENT/ENTRY POINT: MOB COMPONENT DESCRIPTION: Provides Inpatient Medications with an array of data returned by the BCMA/CPRS Med Order function. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The patients internal entry number from the PATIENT FILE, 2. VARIABLES: PSBCORN TYPE: Input VARIABLES DESCRIPTION: The CPRS order number. VARIABLES: ARRAY TYPE: Output VARIABLES DESCRIPTION: ^TMP("PSB",$J,0) $P(1) = DFN $P(2) = CPRS order number $P(3) = Schedule ^TMP("PSB",$J,700,0) = Total number of dispense drugs ^TMP("PSB",$J,700,#) = IEN from file 50 ^TMP("PSB",$J,800,0) = Total number of additives ^TMP("PSB",$J,800,#) = IEN from file 52.6 ^TMP("PSB",$J,900,0) = Total number of solutions ^TMP("PSB",$J,900,#) = IEN from file 52.7 COMPONENT/ENTRY POINT: MOBR COMPONENT DESCRIPTION: This entry point is used by Inpatient Medications to notiy BCMA that the order has been processed or rejected. There is no return from this entry point. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The internal entry number from PATIENT FILE, 2. VARIABLES: PSBCORN TYPE: Input VARIABLES DESCRIPTION: The CPRS order number. VARIABLES: PSBORDN TYPE: Input VARIABLES DESCRIPTION: The Inpatient Medications order number if processed, null if rejected. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham EDITOR: CAVE,EDWARD EDITOR: CRUMLEY,JAMIE EDITOR: URSO,EDWARD NUMBER: 3176 IA #: 3176 DATE CREATED: SEP 16, 2003 CUSTODIAL PACKAGE: VBECS CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VBECA4 NAME: DBIA3176-A ORIGINAL NUMBER: 3176 ID: VBECA4 GENERAL DESCRIPTION: The entry point TRAN^VBECA4 is provided by the Blood Bank package to collect transfusion record data based on the patient identifier (DFN) value provided in the call. The API will create entries in the ^TMP global for every record found by the function. This API will replace the use of XTRCT^GMTSLRTE by Health Summary. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31921299 COMPONENT/ENTRY POINT: TRAN COMPONENT DESCRIPTION: INPUT DEFINITION: DFN = Internal entry number from the PATIENT file (#2) (Passed as a parameter) TMPLOC = The first subscript location in the ^TMP global (Passed as a parameter) GMTS1 = Inverse end date of search (Passed as a parameter) GMTS2 = Inverse start date of search (Passed as a parameter) OUTPUT DEFINITION: This API (TRAN^VBECA4) will be the new entry point for Health Summary to use in gathering Blood Transfusion data. The call reads Blood Bank data and creates entries in ^TMP(TMPLOC,$J) for the presentation of the data. Health Summary agrees to stop calling XTRCT^GMTSLRTE and instead call TRAN^VBECA4(DFN,TMPLOC,GMTS1,GMTS2). The output format is: ^TMP(TMPLOC (passed in input parameter),$J,PRODUCT NAME ABBREVIATION) = FULL BLOOD PRODUCT NAME ^TMP(TMPLOC (passed in input parameter),$J,Inverse Date)=Date^Total of Units Pooled_"\"_Product Name Abbreviation SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 3177 IA #: 3177 DATE CREATED: SEP 08, 2000 CUSTODIAL PACKAGE: VBECS CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VBECA4 NAME: DBIA3176-B ORIGINAL NUMBER: 3176 ID: VBECA4 GENERAL DESCRIPTION: The entry point AVUNIT^VBECA4 returns the available units between two dates based on the patient identifier (DFN) value provided in the call. The API will create entries in the ^TMP global for every record found by the function. This API will replace the use of XTRCT^GMTSLRBE by Health Summary. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31921299 COMPONENT/ENTRY POINT: AVUNIT COMPONENT DESCRIPTION: INPUT DEFINITION: DFN = Internal entry number from the PATIENT file (#2) (Passed as a parameter) TMPLOC = The first subscript location in the ^TMP global (Passed as a parameter) GMTS1 = Inverse end date of search (Passed as a parameter) GMTS2 = Inverse start date of search (Passed as a parameter) GMTSNDM = Maximum number to be extracted (Passed as a parameter) OUTPUT DEFINITION: The function will gather Blood Bank unit data for presentation to Health Summary. This API (AVUNIT^VBECA4) will replace XTRCT^GMTSLRBE as the new entry point for Health Summary to use in producing the report. The call reads Blood Bank available unit data and creates entries in ^TMP(TMPLOC,$J) for the temporary storage of the data. Health Summary agrees to stop calling XTRCT^GMTSLRBE and instead call AVUNIT^VBECA4(DFN,TMPLOC,GMTS1,GMTS2, GMTSNDM). The output format is: ^TMP(TMPLOC,$J,0) = ABO Value_U_RH factor ^TMP(TMPLOC,$J,Inverse Date) = Expiration Flag_U_Expiration Date_U_Unit ID_U_Component_U _Volume_U_ABO_U_RH_U_Donation Type_U_Division where unit is located_U_ Location to which unit of blood is being relocated SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING DETAILS: added April 2009 DATE/TIME EDITED: APR 23, 2009@09:30 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MALMROSE,CARY WITH CONCURRENCE OF: MORTON,RANDY NUMBER: 3178 IA #: 3178 DATE CREATED: AUG 29, 2000 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUA4A71 NAME: Convert String to Soundex ID: XUA4A71 GENERAL DESCRIPTION: Use this function to convert a string into a numeric representation of the string, using soundex methods. Soundex represents the phonetic properties of a string; its chief feature is that it assigns similar strings the same soundex representation. STATUS: Active MAIL MESSAGE: 31948360 COMPONENT/ENTRY POINT: $$EN COMPONENT DESCRIPTION: Usage S X=$$EN^XUA4A71(string) VARIABLES: string TYPE: Input VARIABLES DESCRIPTION: String to convert into soundex form. NUMBER: 3179 IA #: 3179 DATE CREATED: AUG 30, 2000 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSSUTIL1 NAME: 3179 ID: PSSUTIL1 GENERAL DESCRIPTION: This API provides Inpatient Medications and Outpatient Pharmacy a means of getting the strength and unit for a specified drug from the DRUG file (#50). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33057322 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: This entry point returns the strength and unit for the drug IEN passed into the routine. If the stength of the drug does not match the stength of the NDF match and the unit contains a / then the unit returned is calculated and may not be contained in the DRUG UNITS file (#50.607) VARIABLES: PSSDRIEN TYPE: Input VARIABLES DESCRIPTION: IEN of drug from DRUG file (#50). VARIABLES: X TYPE: Output VARIABLES DESCRIPTION: The output variable is specifed by the user. The output is in the format strength|^^^IEN of DRUG UNITS file (#50.607)^Name of UNITS^99PSU or if the units are calculated and not in the DRUG UNITS file the format will be strength|^^^^Name of UNITS^99PSU. If there is no strength available the output will be format will be |^^^^^99PSU SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 3180 IA #: 3180 FILE NUMBER: 27.16 GLOBAL ROOT: DD(27.16, DATE CREATED: AUG 29, 2000 CUSTODIAL PACKAGE: VA FILEMAN USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA 3180 ID: DD(27.16, GENERAL DESCRIPTION: There is a "LAYGO" node on the .01 field of ENROLLMENT GROUP THRESHOLD file (#27.16). The code prevents any records from being added to the file. Since there are no FileMan tools to remove a "LAYGO" node once it's set, Enrollment would like permission to add an explicit KILL of the node in a post-install routine. The line of code would be: K ^DD(27.16,.01,"LAYGO") The ENROLLMENT GROUP THRESHOLD file is part of the Enrollment package. STATUS: Active MAIL MESSAGE: 31950681 NUMBER: 3181 IA #: 3181 DATE CREATED: SEP 16, 2003 CUSTODIAL PACKAGE: VBECS CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VBECA1 NAME: DBIA3181-A ORIGINAL NUMBER: 3181 ID: VBECA1 GENERAL DESCRIPTION: These API's are provided to return Blood Bank data to subscribing packages. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 41224230 COMPONENT/ENTRY POINT: ABORH COMPONENT DESCRIPTION: INPUT DEFINITION: DFN = internal entry number from the PATIENT file (#2) (Passed as a parameter). You must precede the internal entry number with the accent grave character ( ` ). OUTPUT DEFINITION: ABO RH This function will return the ABO Blood Group and RH Type value found for the patient provided in the call. This is an extrinsic function call. If no valid patient identifier is provided, the call will return a value of -1. If no ABO Blood Group or RH Type value for the patient exists in the database, the function will return a null value to the call. The values will be return separated by a space (" "). For example, if a patient has Blood Group "A" and RH Type "POS" (positive), the function would return "A POS". VARIABLES: ABORH VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number from the PATIENT file (#2) (Passed as a parameter). You must precede the internal entry number with the accent grave character ( ` ). COMPONENT/ENTRY POINT: ABO COMPONENT DESCRIPTION: INPUT DEFINITION: DFN = internal entry number from the PATIENT file (#2) (Passed as a parameter). You must precede the internal entry number with the accent grave character ( ` ). OUTPUT DEFINITION: "A" or "B" or "AB" or "O" This function will return the ABO Blood Group value found for the patient provided in the call. This is an extrinsic function call. If no valid patient identifier is provided, the call will return a value of -1. If no ABO Blood Group value for the patient exists in the database, the function will return a null value to the call. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number from the PATIENT file (#2) (Passed as a parameter). You must precede the internal entry number with the accent grave character ( ` ). COMPONENT/ENTRY POINT: RH COMPONENT DESCRIPTION: INPUT DEFINITION: DFN = internal entry number from the PATIENT file (#2) (Passed as a parameter). You must precede the internal entry number with the accent grave character ( ` ). OUTPUT DEFINITION: "POS" or "NEG" This function will return the RH Type value for the patient provided in the call. This is an extrinsic function call. If no valid patient identifier is provided, the call will return a value of -1. If no RH Type value for the patient exists in the database, the function will return a null value to the call. VARIABLES: VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number from the PATIENT file (#2) (Passed as a parameter). You must precede the internal entry number with the accent grave character ( ` ). COMPONENT/ENTRY POINT: ABID COMPONENT DESCRIPTION: INPUT DEFINITION: DFN = internal entry number from the PATIENT file (#2) (Passed as a parameter). You must precede the internal entry number with the accent grave character ( ` ). .ARR = The name of an array that will store the value of any antibodies found in Blood Bank patient records by the function. This array must be passed by reference. OUTPUT DEFINITION: If no antibodies are found, the array will be returned empty. For each antibody record found, the array will contain the name of the antibody in the first data piece of the array and any antibody comments in the second data piece. The populated array will be returned with the following structure: ARR("ABID",n) = Antibody ^ Antibody comment Where "n" is a sequential number index for the array. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number from the PATIENT file (#2) (Passed as a parameter). You must precede the internal entry number with the accent grave character ( ` ). VARIABLES: .ARR TYPE: Both VARIABLES DESCRIPTION: The name of an array that will store the value of any antibodies found in Blood Bank patient records by the function. This array must be passed by reference. For each antibody record found, the returned array will contain the name of the antibody in the first data piece of the array and any antibody comments in the second data piece. The populated array will be returned with the following structure: ARR("ABID",n) = Antibody ^ Antibody comment Where "n" is a sequential number index for the array. COMPONENT/ENTRY POINT: AGAB COMPONENT DESCRIPTION: This component is no longer supported with the release of VBECS. COMPONENT/ENTRY POINT: TRRX COMPONENT DESCRIPTION: DFN = internal entry number from the PATIENT file (#2) (Passed as a parameter). You must precede the internal entry number with the accent grave character ( ` ). .ARR = The name of an array that will store the value of any absent antigens found by the function. Must be passed by reference. OUTPUT DEFINITION: ARR = The name of the array, passed to the API by reference, that will be used to store the transfusion reactions found in Blood Bank patient records via the function. Retrieve any previously recorded transfusion reactions. If none exist on record, the array will be returned empty. For each transfusion reaction found, the array element will be assigned the transfusion reaction date/time value at the first data piece and the transfusion reaction type value at the second data piece. The populated array be returned with the following structure: ARR("TRRX",n) = RXN D/T ^ RXN Type Where "n" is a sequential index number. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number from the PATIENT file (#2) (Passed as a parameter). You must precede the internal entry number with the accent grave character ( ` ). VARIABLES: .ARR TYPE: Both VARIABLES DESCRIPTION: The name of the array, passed to the API by reference, that will be used to store the transfusion reactions found in Blood Bank patient records via the function. Retrieve any previously recorded transfusion reactions. If none exist on record, the array will be returned empty. For each transfusion reaction found, the array element will be assigned the transfusion reaction date/time value at the first data piece and the transfusion reaction type value at the second data piece. The populated array be returned with the following structure: ARR("TRRX",n) = RXN D/T ^ RXN Type Where "n" is a sequential index number. COMPONENT/ENTRY POINT: BBCMT COMPONENT DESCRIPTION: This component is no longer supported with the release of VBECS. COMPONENT/ENTRY POINT: AUTO COMPONENT DESCRIPTION: This component is no longer supported with the release of VBECS. COMPONENT/ENTRY POINT: AGPRES COMPONENT DESCRIPTION: This component is no longer supported with the release of VBECS. SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas SUBSCRIBING DETAILS: 2/25/14-Access to entry points ABO and RH for Lab is also documented in ICRs #3182 and 3183. These ICRs were retired as duplicates of ICR #3181. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING DBA Comments: 2/25/14-MM: Retired ICRs 3185 (AGAB), 3186 (AGPRES), 3188 (BBCMT), and 3189 (AUTO). Lab is the subscribing application for these ICRs and the status was pending. Status was changed to retired based on information contained in ICR 3181 for these components indicating components are no longer supported with the release of VBECS. Randy Morton verified APIs are not called in Lab routines. 2/26/14-MM- ICR #3182 and 3183 were retired. A note was added to the Subscribing Details for Lab indicating documentation providing access for Lab to call the ABO and RH entry points is also in ICR #3182 and 3183. DATE/TIME EDITED: FEB 26, 2014@12:14 ACTION: CONTENT CORRECTED AT THE REQUEST OF: ICR,TEAM WITH CONCURRENCE OF: ICR,TEAM NUMBER: 3194 IA #: 3194 DATE CREATED: SEP 12, 2000 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU AUTHORIZATION REMOTE PROCEDURE: TIU AUTHORIZATION ID: 3194 STATUS: Active MAIL MESSAGE: 31932331 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 3/13/14-MM: Added VIA as a subscriber. VIAB*1*1 and TIU*1*283 are patches associated with this project. TIU*1*283 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: JUN 11, 2009@12:03 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: MAR 13, 2014@13:34 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 3195 IA #: 3195 DATE CREATED: APR 29, 2003 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU CAN CHANGE COSIGNER? REMOTE PROCEDURE: TIU CAN CHANGE COSIGNER? ID: 3195 STATUS: Active MAIL MESSAGE: 35801207 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 3197 IA #: 3197 DATE CREATED: SEP 19, 2000 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XQALBUTL NAME: XQALBUTL ID: XQALBUTL GENERAL DESCRIPTION: The DELSTAT entry point in XQALBUTL is a SUPPORTED reference for obtaining information on the recipients of the most recent alert with a specified alert id and the status of whether the alert has been deleted or not for those recipients. DELSTAT - For the most recent alert with XQAIDVAL as the PackageID passed in, on return array VALUES contains the DUZ for users in VALUES along with an indicator of whether the alert has been deleted or not, e.g., DUZ^0 if not deleted or DUZ^1 if deleted. Note that contents of VALUES will be killed prior to building the list. Example: D DELSTAT^XQALBUTL("OR;14765;23",.RESULTS) Returned: The value of RESULTS indicates the number of entries in the array. The entries are then ordered in numerical order in the RESULTS array. RESULTS = 3 RESULTS(1) = "146^0" User 146 - not deleted RESULTS(2) = "297^1" User 297 - deleted RESULTS(3) = "673^0" User 673 - not deleted STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32032631 KEYWORDS: ALERTS KEYWORDS: DELETION KEYWORDS: DELETE KEYWORDS: STATUS KEYWORDS: ALERT KEYWORDS: RECIPIENTS COMPONENT/ENTRY POINT: DELSTAT COMPONENT DESCRIPTION: DELSTAT - For the most recent alert with XQAIDVAL as the PackageID passed in, on return array VALUES contains the DUZ for users in VALUES along with an indicator of whether the alert has been deleted or not, e.g., DUZ^0 if not deleted or DUZ^1 if deleted. Note that contents of VALUES will be killed prior to building the list. Example: D DELSTAT^XQALBUTL("OR;14765;23",.RESULTS) Returned: The value of RESULTS indicates the number of entries in the array. The entries are then ordered in numerical order in the RESULTS array. RESULTS = 3 RESULTS(1) = "146^0" User 146 - not deleted RESULTS(2) = "297^1" User 297 - deleted RESULTS(3) = "673^0" User 673 - not deleted VARIABLES: XQAIDVAL TYPE: Input VARIABLES DESCRIPTION: XQAIDVAL is a value which has been used as the XQAID value for generating an alert by a package. This value is used to identify the most recent alert generated with this XQAID value and that alert is used to generate the responses in terms of recipients and deletion status of the alert for each of the recipients. VARIABLES: VALUES TYPE: Output VARIABLES DESCRIPTION: This variable is passed by reference and is returned as an array. This value is KILLED prior to generation of the results for return. Returned: The value of VALUES indicates the number of entries in the array. The entries are then ordered in numerical order in the VALUES array. VALUES = 3 VALUES(1) = "146^0" User 146 - not deleted VALUES(2) = "297^1" User 297 - deleted VALUES(3) = "673^0" User 673 - not deleted NUMBER: 3198 IA #: 3198 DATE CREATED: SEP 12, 2000 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU DOCUMENTS BY CONTEXT REMOTE PROCEDURE: TIU DOCUMENTS BY CONTEXT ID: 3198 STATUS: Active MAIL MESSAGE: 31932331 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: 5/10/13-The Mental Health Program Office contracted with Capital Solution Design Corporation to provide the Behavioral Health Lab (BHL) software. BHL is a vendor product that calls this VistA RPC. Capital Solution Design John Boles - 202-642-9280 johnboles@capitalsolutiondesign.com VA BHL Support - 202-670-2847 bhl.support@capitalsolutiondesign.com SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 5/10/13-MM: Mental Health was added as a subscriber for Behavioral Health Lab. A note was added to the Subscribing Details section for Mental Health to document Behavioral Health Lab software is using this RPC. Informational patch YS*5.01*111 documents release of BHL. 3/13/14-MM: Added VIA as a subscriber. VIAB*1*1 and TIU*1*283 are patches associated with this project. TIU*1*283 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: JUN 11, 2009@12:02 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: MAY 10, 2013@16:34 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: MAY 10, 2013@16:35 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: MAR 13, 2014@13:37 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 3201 IA #: 3201 DATE CREATED: NOV 06, 2006 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU IS THIS A CONSULT? REMOTE PROCEDURE: TIU IS THIS A CONSULT? ID: 3201 STATUS: Active MAIL MESSAGE: 31932331 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: 5/10/13-The Mental Health Program Office contracted with Capital Solution Design Corporation to provide the Behavioral Health Lab (BHL) software. BHL is a vendor product that calls this VistA RPC. Capital Solution Design John Boles - 202-642-9280 johnboles@capitalsolutiondesign.com VA BHL Support - 202-670-2847 bhl.support@capitalsolutiondesign.com SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 5/10/13-MM: Mental Health was added as a subscriber for Behavioral Health Lab. A note was added to the Subscribing Details section for Mental Health to document Behavioral Health Lab software is using this RPC. Informational patch YS*5.01*111 documents release of BHL. 3/13/14-MM: Added VIA as a subscriber. VIAB*1*1 and TIU*1*283 are patches associated with this project. TIU*1*283 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: JAN 25, 2007@19:04 ACTION: WITHDREW REQUEST AT THE REQUEST OF: SHOVESTUL,MARYANN WITH CONCURRENCE OF: HARVEY,JULIE DATE/TIME EDITED: JUN 11, 2009@12:02 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: MAY 10, 2013@16:51 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: MAY 10, 2013@16:52 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: MAR 13, 2014@13:39 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 3204 IA #: 3204 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU LONG LIST OF TITLES REMOTE PROCEDURE: TIU LONG LIST OF TITLES ID: 3204 STATUS: Active MAIL MESSAGE: 31932331 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: 5/10/13-The Mental Health Program Office contracted with Capital Solution Design Corporation to provide the Behavioral Health Lab (BHL) software. BHL is a vendor product that calls this VistA RPC. Capital Solution Design John Boles - 202-642-9280 johnboles@capitalsolutiondesign.com VA BHL Support - 202-670-2847 bhl.support@capitalsolutiondesign.com SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) SUBSCRIBING DETAILS: Effective with VPS*1*3 DBA Comments: 5/10/13-MM: Mental Health was added as a subscriber for Behavioral Health Lab. A note was added to the Subscribing Details section for Mental Health to document Behavioral Health Lab software is using this RPC. Informational patch YS*5.01*111 documents release of BHL. 3/13/14-MM: Added VIA as a subscriber. VIAB*1*1 and TIU*1*283 are patches associated with this project. TIU*1*283 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. 11/6/14-DT: Added VPS Kiosk as subscriber, effective with VPS*1*3. Margy McClenahan granted concurrence 1/7/13. DATE/TIME EDITED: JUN 11, 2009@12:01 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: MAY 10, 2013@16:55 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: MAY 10, 2013@16:56 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: MAR 13, 2014@13:40 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE DATE/TIME EDITED: NOV 06, 2014@12:45 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: TJAHJO,BUDY WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 3205 IA #: 3205 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU PERSONAL TITLE LIST REMOTE PROCEDURE: TIU PERSONAL TITLE LIST ID: 3205 STATUS: Active MAIL MESSAGE: 31932331 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: 5/10/13-The Mental Health Program Office contracted with Capital Solution Design Corporation to provide the Behavioral Health Lab (BHL) software. BHL is a vendor product that calls this VistA RPC. Capital Solution Design John Boles - 202-642-9280 johnboles@capitalsolutiondesign.com VA BHL Support - 202-670-2847 bhl.support@capitalsolutiondesign.com DBA Comments: 5/10/13-MM: Mental Health was added as a subscriber for Behavioral Health Lab. A note was added to the Subscribing Details section for Mental Health to document Behavioral Health Lab software is using this RPC. Informational patch YS*5.01*111 documents release of BHL. DATE/TIME EDITED: MAY 10, 2013@17:01 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: MAY 10, 2013@17:02 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: TRAXLER,FRANK NUMBER: 3208 IA #: 3208 FILE NUMBER: 991.11 GLOBAL ROOT: RGHL7(991.11, DATE CREATED: FEB 21, 2002 CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3208 ID: RGHL7(991.11, GLOBAL REFERENCE: RGHL7(991.11, FIELD NUMBER: 10 FIELD NAME: TEXT LOCATION: 10;E1,100 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field holds the message for the exception type. GENERAL DESCRIPTION: MPI-AUSTIN needs an integration agreement to support direct reads to ^RGHL7(991.11 for the MPI exception handler. STATUS: Active MAIL MESSAGE: 34146874 SUBSCRIBING PACKAGE: MASTER PATIENT INDEX NUMBER: 3209 IA #: 3209 DATE CREATED: SEP 20, 2000 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR GETS ENTRY DATA GENERAL DESCRIPTION: This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. STATUS: Active MAIL MESSAGE: 31868465 KEYWORDS: DDR KEYWORDS: GETS KEYWORDS: DATA KEYWORDS: ENTRY KEYWORDS: RPC KEYWORDS: FMDC NUMBER: 3210 IA #: 3210 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU UPDATE ADDITIONAL SIGNERS REMOTE PROCEDURE: TIU UPDATE ADDITIONAL SIGNERS ID: 3210 STATUS: Active MAIL MESSAGE: 31932331 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 DATE/TIME EDITED: JUN 11, 2009@12:01 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 3211 IA #: 3211 FILE NUMBER: 9000010 GLOBAL ROOT: AUPNVSIT( DATE CREATED: SEP 22, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3211 ID: AUPNVSIT( GLOBAL REFERENCE: AUPNVSIT(D0,0) FIELD NUMBER: .01 FIELD NAME: VISIT/ADMIT DATE&TIME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .01 FIELD NAME: VISIT ADMIT DATE&TIME LOCATION: 0;1 ACCESS: Write w/Fileman GENERAL DESCRIPTION: The Scheduling Package desires an Integration Agreement with the PCE Package to access and update the #9000010 VISIT file. The .01 VISIT/ADMIT DATE&TIME field will be validated and updated if necessary. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32122260 SUBSCRIBING PACKAGE: SCHEDULING EDITOR: SHETLER,BOB NUMBER: 3213 IA #: 3213 DATE CREATED: SEP 27, 2000 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XQALSURO NAME: XQALSURO ID: XQALSURO CREATOR: IVEY,JOEL GENERAL DESCRIPTION: This integration agreement adds two additional SUPPORTED entry points or APIs to XQALSURO. SETSURO1 should be used in the future instead of SETSURO to establish a surrogate for alerts. SETSURO1 returns a value of 1 if the surrogate was created successfully, otherwise, it returns a text string explaining why the surrogate was not created. SETSURO simply added the specified surrogate, but did not test for cyclic relationships (such that the user eventually would become the surrogate). SETSURO1 does these tests and therefore has the possibility of failure. GETSURO is an API which can be used to obtain information about the current surrogate, including start and end date/times if they are specified. SUROLIST is an API which can be used to obtain a list of the current and future surrogate periods for a selected user. SUROFOR is an API which can be used to obtain a list of any current users that the selected user is acting as a surrogate for. STATUS: Active MAIL MESSAGE: 32068253 KEYWORDS: ALERT KEYWORDS: ALERTS KEYWORDS: SURROGATE KEYWORDS: API COMPONENT/ENTRY POINT: GETSURO COMPONENT DESCRIPTION: $$GETSURO^XQALSURO(XQAUSER) returns a string of '^' separated information on the current surrogate for the user with XQAUSER as his internal entry number in the NEW PERSON file. The value returned is of the form ien^NAME^FM_STARTDATE^FM_ENDDATE where ien is the internal entry number of the SURROGATE in the NEW PERSON file, NAME is the contents of the .01 field for the SURROGATE, FM_STARTDATE is the starting date/time for the SURROGATE in internal Filemanager format, and FM_ENDDATE is the ending date/time for the SURROGATE in internal Filemanager format. S X=$$GETSURO^XQALSURO(124) might yield a value of X containing 2327^DOE,JOHN^3000929.1630^3001006.0800 indicating that user #2327 (John Doe) will become active as surrogate at 4:30 PM 9/29/00 and will remain surrogate until 8:00 am on 10/06/00. If there was no surrogate, the result would be ^^^ If either of the date/times are not specified, they will return a null value for that piece of the return string. VARIABLES: XQAUSER TYPE: Input VARIABLES DESCRIPTION: This is the internal entry number in the NEW PERSON file (file #200) of the user for which alert surrogate information is to be returned. COMPONENT/ENTRY POINT: SETSURO1 COMPONENT DESCRIPTION: This API should be used instead of the SETSURO^XQALSURO API. The SETSURO1 entry point returns a value indicating success (a TRUE (value =1)) or failure (a FALSE (value=message indicating reason for failure)). The SETSURO entry point returned no value and, as long as both a user and surrogate were specified, would simply store the values. This leaves open the possibility that the user is specified as the surrogate or that a chain of surrogates ends up pointing again at the user, cases that could result in a very tight, non-ending, loop being generated if an alert was sent. These possibilities have been tested for in the interactive specifiction of surrogates, and is tested for non-interactive usage in the SETSURO1^XQALSURO API. Usage would be: S XQAUSER=DUZ ; user identification S XQASURO=45 ; Surrogate's DUZ number (internal entry number in file 200) S XQASTRT=3001004.1630 ; Start Date/Time in Filemanager internal format S XQAEND=3001008.1630 ; End Date/Time for surrogate in FM internal format S X=$$SETSURO1^XQALSURO(USER,SURROGAT,START,END) I 'X W !,"Could not activate surrogate",!,?5,X Q The Start and End Date/Time values are optional. If the Start Date/Time is not specified, the surrogate relationship begins immediately. If the End Date/Time is not specified, the surrogate remains active until another surrogate is specified, or the surrogate deleted. VARIABLES: XQAUSER TYPE: Input VARIABLES DESCRIPTION: XQAUSER is the internal entry number in file 200 (DUZ) for the user for which the surrogate should act in receiving alerts. VARIABLES: XQASURRO TYPE: Input VARIABLES DESCRIPTION: XQASURRO is the internal entry number in file 200 (DUZ) for the user who will receive and process alerts for XQAUSER. VARIABLES: XQASTART TYPE: Input VARIABLES DESCRIPTION: XQASTART is an optional START Date/Time for the surrogate activity in Filemanager format. If XQASTART is not specified, the surrogate relationship begins immediately. VARIABLES: XQAEND TYPE: Input VARIABLES DESCRIPTION: XQAEND is an optional date/time for the end of the surrogate relationship in Filemanager format. If XQAEND is not specified, the surrogate remains active until anothersurrogate is specified, or the surrogate deleted. VARIABLES: COMPONENT/ENTRY POINT: SUROLIST COMPONENT DESCRIPTION: The SUROLIST entry point returns a returns for XQAUSER a list of current and/or future surrogates in XQALIST (which must be passed by reference) Usage would be: S XQAUSER=DUZ ; user identification D SUROLIST^XQALSURO(XQAUSER,.USERLIST) This returns USERLIST=count USERLIST(1)=IEN2^NEWPERSON,USER2^STARTDATETIME^ENDDATETIME USERLIST(2)=3^NAME,USER3^3050407.1227^3050406 VARIABLES: XQAUSER TYPE: Input VARIABLES DESCRIPTION: XQAUSER is the internal entry number in file 200 (DUZ) for the user for which the surrogate should act in receiving alerts. VARIABLES: XQALIST TYPE: Both VARIABLES DESCRIPTION: XQALIST is a variable which is passed by reference which will contain the list of current and future surogates for the specified user. COMPONENT/ENTRY POINT: SUROFOR COMPONENT DESCRIPTION: The SUROFOR entry point returns a list of users for which the specified user is currently acting as a surogate for. Usage would be: S XQAUSER=DUZ ; user identification D SUROFOR^XQALSURO(XQAUSER,.USERLIST) This returns USERLIST=count USERLIST(1)=IEN2^NEWPERSON,USER2^STARTDATETIME^ENDDATETIME USERLIST(2)=3^NAME,USER3^3050407.1227^3050406 VARIABLES: XQAUSER TYPE: Input VARIABLES DESCRIPTION: XQAUSER is the internal entry number in file 200 (DUZ) for the user for which the surrogate should act in receiving alerts. VARIABLES: VARIABLES: XQALIST TYPE: Both VARIABLES DESCRIPTION: XQALIST is a variable which is passed by reference which will contain the list of users for whom the specified user is currently acting as a surrogate. The date in the list includes the internal entry number (DUZ) for the user, the user's name, and the start and end dates for the surrogate period. DBA Comments: reactivated 7.29.09 DATE ACTIVATED: JUL 29, 2009 DATE/TIME EDITED: JUL 28, 2009@16:07 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: IVEY,JOEL DATE/TIME EDITED: JUL 29, 2009@12:07 ACTION: APPROVED AT THE REQUEST OF: IVEY,JOEL NUMBER: 3214 IA #: 3214 DATE CREATED: OCT 16, 2000 CUSTODIAL PACKAGE: GEN. MED. REC. - I/O CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRYAPI NAME: GMRYAPI ID: GMRYAPI GENERAL DESCRIPTION: This routine provides entry points to return GEN. MED. REC. - I/O (aka Intake and Output) data to the calling application. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32264501 COMPONENT/ENTRY POINT: INPUT() COMPONENT DESCRIPTION: This function returns the number of entries in the GMRY INPUT TYPE file (#126.56). There are no input or output variables for this function. COMPONENT/ENTRY POINT: OUTPUT() COMPONENT DESCRIPTION: This function returns the number of entries in the GMRY OUTPUT TYPE file (#126.58). There are no input or output variables for this function. SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines EDITOR: TRAXLER,FRANK NUMBER: 3215 IA #: 3215 DATE CREATED: OCT 03, 2000 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR DELETE ENTRY ID: 3215 GENERAL DESCRIPTION: This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. STATUS: Active MAIL MESSAGE: 31868465 KEYWORDS: DDR KEYWORDS: DELETE KEYWORDS: ENTRY KEYWORDS: RPC KEYWORDS: FMDC NUMBER: 3216 IA #: 3216 DATE CREATED: OCT 03, 2000 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR FILER ID: 3216 GENERAL DESCRIPTION: This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. STATUS: Active MAIL MESSAGE: 31868465 KEYWORDS: DDR KEYWORDS: RPC KEYWORDS: FMDC KEYWORDS: FILER NUMBER: 3217 IA #: 3217 DATE CREATED: OCT 03, 2000 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR FIND1 ID: 3217 GENERAL DESCRIPTION: This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. STATUS: Active MAIL MESSAGE: 31868465 KEYWORDS: DDR KEYWORDS: RPC KEYWORDS: FMDC KEYWORDS: FIND1 NUMBER: 3218 IA #: 3218 DATE CREATED: OCT 03, 2000 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR FINDER ID: 3218 GENERAL DESCRIPTION: This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. STATUS: Active MAIL MESSAGE: 31868465 KEYWORDS: DDR KEYWORDS: RPC KEYWORDS: FMDC KEYWORDS: FINDER NUMBER: 3220 IA #: 3220 DATE CREATED: OCT 03, 2000 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR GET DD HELP ID: 3220 GENERAL DESCRIPTION: This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. STATUS: Active MAIL MESSAGE: 31868465 KEYWORDS: DDR KEYWORDS: RPC KEYWORDS: FMDC KEYWORDS: GET KEYWORDS: DD KEYWORDS: HELP NUMBER: 3221 IA #: 3221 DATE CREATED: OCT 03, 2000 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR LISTER ID: 3221 GENERAL DESCRIPTION: This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. STATUS: Active MAIL MESSAGE: 31868465 KEYWORDS: DDR KEYWORDS: RPC KEYWORDS: FMDC KEYWORDS: LISTER NUMBER: 3222 IA #: 3222 DATE CREATED: OCT 03, 2000 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR LOCK/UNLOCK NODE ID: 3222 GENERAL DESCRIPTION: This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. STATUS: Active MAIL MESSAGE: 31868465 KEYWORDS: DDR KEYWORDS: RPC KEYWORDS: FMDC KEYWORDS: LOCK KEYWORDS: UNLOCK NUMBER: 3223 IA #: 3223 DATE CREATED: OCT 03, 2000 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR VALIDATOR ID: 3223 GENERAL DESCRIPTION: This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. STATUS: Active MAIL MESSAGE: 31868465 KEYWORDS: DDR KEYWORDS: RPC KEYWORDS: FMDC KEYWORDS: VALIDATOR NUMBER: 3224 IA #: 3224 DATE CREATED: OCT 03, 2000 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DDR KEY VALIDATOR ID: 3224 GENERAL DESCRIPTION: This RPC entry may be referenced from the Option file to support invoking the RPC from its corresponding FM Delphi Component. The RPC must not be invoked directly. STATUS: Active MAIL MESSAGE: 31868465 KEYWORDS: DDR KEYWORDS: RPC KEYWORDS: FMDC KEYWORDS: KEY KEYWORDS: VALIDATOR NUMBER: 3225 IA #: 3225 DATE CREATED: OCT 05, 2000 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXKCO NAME: Service Catagory Calculation API ID: PXKCO GENERAL DESCRIPTION: CPRS requests an integration agreement to call the SVC^PXKCO routine. This routine calculates the appropriate service category for an encounter, and is needed to correct problems with some encounters generated in CPRS. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32097651 KEYWORDS: PXKCO COMPONENT/ENTRY POINT: SVC VARIABLES: SVC TYPE: Input VARIABLES DESCRIPTION: Initial Service Category VARIABLES: DSS TYPE: Input VARIABLES DESCRIPTION: Stop Code VARIABLES: PXKIO TYPE: Input VARIABLES DESCRIPTION: Set to 1 if Patient is an inpatient, 0 otherwise. VARIABLES: LOC TYPE: Input VARIABLES DESCRIPTION: Hospital Location VARIABLES: $$SVC TYPE: Output VARIABLES DESCRIPTION: Returns the corrected Service Category value. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3227 IA #: 3227 DATE CREATED: OCT 17, 2000 CUSTODIAL PACKAGE: NURSING SERVICE CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: NURAPI NAME: NURAPI ID: NURAPI GENERAL DESCRIPTION: This routine provides entry points to return Nursing package data to the calling package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34763796 COMPONENT/ENTRY POINT: ACTLOCS(.ARRAY) COMPONENT DESCRIPTION: Returns all active nursing locations from the NURS LOCATION file (#211.4) in the array specified. FILE 211.4 points to HOSPITAL LOCATION file (#44). VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: Input - (Required) The name of the array to store the entries. Output - ArrayName(sequential #)=File 211.4 ien^File 44 name (for 211.4 ien). If no active locations returns: ArrayName(1)="NO UNIT". COMPONENT/ENTRY POINT: PTCHK(LOC) COMPONENT DESCRIPTION: This function indicates if any patients (active or inactive) are associated with the Nursing location identified. Returns: 0 - no patients associated with this location 1 - yes, patients are associated with this location -1 - (minus 1) LOC is undefined or not found VARIABLES: LOC TYPE: Input VARIABLES DESCRIPTION: (Required) NURS LOCATION file (#211.4) ien. COMPONENT/ENTRY POINT: APTCHK(LOC) COMPONENT DESCRIPTION: This function indicates if active patients are associated with the Nursing location identified. Returns: 0 - no active patients associated with this location 1 - yes, active patients are associated with this location -1 - (minus 1) LOC is undefined or not found VARIABLES: LOC TYPE: Input VARIABLES DESCRIPTION: (Required) NURS LOCATION file (#211.4) ien. COMPONENT/ENTRY POINT: PTLIST(LOC,.ARRAY) COMPONENT DESCRIPTION: Returns a list of all (active and inactive) patients for a nursing location in the array specified. VARIABLES: LOC TYPE: Input VARIABLES DESCRIPTION: (Required) NURS LOCATION file (#211.4) ien. VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: Input - (Required) Name of array to return entries in Output - Subscripted by sequential number with DFN in first piece and patient name in second piece. Example: ArrayName(sequential #)=DFN^patient name If LOC is undefined or not found, then returns ARRAY(1)=-1. If no patients on the Location, then returns ARRAY(1)="^No Patients". COMPONENT/ENTRY POINT: APTLIST(LOC,.ARRAY) COMPONENT DESCRIPTION: Returns a list of active patients for a nursing location in the array specified. VARIABLES: LOC TYPE: Input VARIABLES DESCRIPTION: (Required) NURS LOCATION file (#211.4) ien. VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: Input - (Required) Name of the array to return entries in Output - Subscripted by sequential number with DFN in first piece and patient name in second piece. Example: ArrayName(sequential #)=DFN^patient name If LOC is undefined or not found, then returns ARRAY(1)=-1. If no patients on the Location, then returns ARRAY(1)="^No Patients". COMPONENT/ENTRY POINT: FINDNLOC(LOC) COMPONENT DESCRIPTION: This function returns the NURS LOCATION file (#211.4) ien and the ien of the location (File 44, Field .01). If LOC is undefined, then returns -1. If no such location returns: "^Location not found". Returns: File 211.4 ien^File 44 ien VARIABLES: LOC TYPE: Input VARIABLES DESCRIPTION: (Required) Name of the Nursing location (as it appears in File 44). The name should begin with the characters 'NUR '. If not, NUR will be appended to the beginning of LOC. COMPONENT/ENTRY POINT: MASWARDS(LOC,.ARRAY) COMPONENT DESCRIPTION: Returns the MAS wards associated with this Nursing location in the array specified. The .01 field of the MAS WARD multiple of the NURS LOCATION file points to the WARD LOCATION file (#42). VARIABLES: LOC TYPE: Input VARIABLES DESCRIPTION: (Required) NURS LOCATION file (#211.4) ien. VARIABLES: ARRAY TYPE: Both VARIABLES DESCRIPTION: Input - (Required) Name of array to return entries in. Output - ARRAY subscripted by the MAS WARD value. Example: ArrayName($P(^NURSF(211.4,LOC,3,D1,0),U,1))="" If LOC is null or not found, then ARRAY(1)=-1. SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS ISC: Hines EDITOR: TRAXLER,FRANK NUMBER: 3228 IA #: 3228 FILE NUMBER: 15.4 GLOBAL ROOT: XDRM( DATE CREATED: OCT 18, 2000 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: VIEW MERGE IMAGES FOR FEE BASIS ID: XDRM( GLOBAL REFERENCE: XDRM(D0,0) FIELD NUMBER: .01 FIELD NAME: MERGED FROM LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains a variable pointer reference to the location in the primary merge file of the entry which was merged into another entry. FIELD NUMBER: .02 FIELD NAME: MERGED TO LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains a variable pointer reference to the entry in the primary file for the merge, into which the entry indicated by the MERGED FROM (#.01) field was merged. GLOBAL REFERENCE: XDRM(D0,1,D1,0) FIELD NUMBER: .01 FIELD NAME: FROM FILE# LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field specifies a file for which a data image was recorded for the entry specified by the MERGED FROM (#.01) field in the parent file (MERGE IMAGES, 15.4). GLOBAL REFERENCE: XDRM(D0,1,D1,1,D2,0) FIELD NUMBER: .01 FIELD NAME: GLOBAL NODE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the global node for which the data is given. GLOBAL REFERENCE: XDRM(D0,1,D1,1,D2,1) FIELD NUMBER: 1.01 FIELD NAME: DATA VALUE LOCATION: 1;E1,245 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the value associated with the current global node. GLOBAL REFERENCE: XDRM(D0,2,D1,0) FIELD NUMBER: .01 FIELD NAME: TO FILE# LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field specifies a file for which a data image was recorded for the entry specified by the MERGED TO (#.02 ) field in the parent file (MERGE IMAGES, 15.4). GLOBAL REFERENCE: XDRM(D0,2,D1,1,D2,0) FIELD NUMBER: .01 FIELD NAME: GLOBAL NODE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the global node for which the data is given. GLOBAL REFERENCE: XDRM(D0,2,D1,1,D2,1) FIELD NUMBER: 1.01 FIELD NAME: DATA VALUE LOCATION: 1;E1,245 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the value associated with the current global node. GLOBAL REFERENCE: XDRM(D0,3,D1,0) FIELD NUMBER: .01 FIELD NAME: POINTERS CHANGED LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains data on a location where a pointer value was changed. The #.01 field contains the information which would be specified as subscripts in the array passed in a call to FILE^DIE. The array subscripts are separated by a ';', and are in the form FILE;IENS;FIELD. GLOBAL REFERENCE: XDRM(D0,3,D1,1) FIELD NUMBER: 1.01 FIELD NAME: ORIGINAL VALUE LOCATION: 1;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the pointer value before it was changed. GENERAL DESCRIPTION: This integration agreement permits the patch FB*3.5*19 post install to examine data in the MERGE IMAGES (#15.4) file. This data will be used to identify and correct problems in the Fee Basis software that may have occurred when patients were merged before installation of patch FB*3.5*19. In addition to reading data in the global, the post install will loop (using $Order) through the following parts of the XDRM global to locate the Fee Basis data. XDRM(D0) loop thru all patient pairs in MERGED IMAGES file XDRM(D0,1,"B", loop thru FROM FILE# "B" x-ref to locate Fee files XDRM(D0,1,D1,1,D2) loop thru GLOBAL DATA for a specific FROM FILE XDRM(D0,2,"B", loop thru TO FILE# "B" x-ref to locate Fee files XDRM(D0,2,D1,1,D2) loop thru GLOBAL DATA for a specific TO FILE XDRM(D0,3,"B", loop thru POINTERS CHANGED "B" x-ref to find Fee files Data in the MERGE IMAGES fill will not be modified under this integration agreement. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32146225 SUBSCRIBING PACKAGE: FEE BASIS ISC: Washington/Silver Spring NUMBER: 3230 IA #: 3230 DATE CREATED: OCT 24, 2000 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA 3230 Imaging Device file entry GENERAL DESCRIPTION: This request is to allow the VistA Imaging package to add a HFS device to the DEVICE file and a Terminal Type entry; this is done during the installation of the Imaging application. The entry for the Device file will be named IMAGING WORKSTATION and the Terminal Type file entry will be named P-IMAGING. This device is used by the GUI portions of VistA Imaging to generate DHCP reports into a global array format. The following is the code used to create this device: EN ;Create an entry in the Device file for an Imaging workstation. ; TERM N A,DA,DD,DO,DIC,DIE,ENTRY,X,Y W !,"I will setup the 'P-IMAGING' entry in the Terminal Type file." I $D(^%ZIS(2,"B","P-IMAGING")) D G DEV . W !,"An entry already exists for 'P-IMAGING' in the Terminal Type file ." ;Set the entry S DIC="^%ZIS(2," S X="P-IMAGING",DIC(0)="O" K DD,D0 D FILE^DICN S ENTRY=+Y G:'ENTRY ERRDEV S DR=".02///0;1///80;2///"_"#"_";4///"_"$C(8)"_";7///"_"D CLOSE^MAGGTU5; 3///64" S DA=ENTRY,DIE="^%ZIS(2," D ^DIE ;.02/SELECTABLE AT SIGNON;1/RIGHT MARGIN;2/FORM FEED;4/BACK SPACE ;7/CLOSE EXECUTE;3/PAGE LENGTH DEV N A,DA,DD,DO,DIC,DIE,ENTRY,X,Y,MAGOS W !,"I will setup an 'Imaging Workstation' entry in the Device file." I $D(^%ZIS(1,"B","IMAGING WORKSTATION")) D Q . W !,"An entry already exists for 'IMAGING WORKSTATION' in the Device f ile." S DIC="^%ZIS(1," S X="IMAGING WORKSTATION",DIC(0)="O" K DD,D0 D FILE^DICN S ENTRY=+Y G:'ENTRY ERRDEV I ^%ZOSF("OS")["DSM" D . S MAGOS="DSM" . S DA=ENTRY,DR=".02///"_"BROKER"_";3///"_"P-IMAGING"_";1///"_"WS.DAT" . S DR=DR_";4///0;5///0;19///"_"(NEWVERSION,DELETE)"_";2///"_"HFS" . S DIE="^%ZIS(1," I ^%ZOSF("OS")["OpenM" D . S MAGOS="OPENM" . S DA=ENTRY,DR=".02///"_"BROKER"_";3///"_"P-IMAGING"_";1///"_"WS.DAT" . S DR=DR_";4///0;5///0;19///"_"""NWS"""_";2///"_"HFS" . S DIE="^%ZIS(1," I ^%ZOSF("OS")["MSM" D . S MAGOS="MSM" . S DA=ENTRY,DR=".02///"_"BROKER"_";3///"_"P-IMAGING"_";1///"_"WS.DAT" . S DR=DR_";4///0;5///0;19///"_"(""WS.DAT"":""M"")"_";2///"_"HFS" . S DIE="^%ZIS(1," I $D(MAGOS) D ^DIE ;.02/LOCATION OF TERMINAL;3/SUBTYPE;1/$I;4=ASK DEVICE;5/ASK PARAMETERS ;19/OPEN PARAMETERS;2/TYPE Q ERRDEV ; W !,"Could not setup the IMAGING WORKSTATION entry in the Device file." W !,"Could not setup the P-IMAGING entry in the Terminal Type file." MSG W !,"Please review the Installation Manual to create this entry." Q STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32165104 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Will be used to created Device and Terminal type entries used by VistA Imaging for displaying DHCP reports on the VistA Imaging GUI application. NUMBER: 3231 IA #: 3231 FILE NUMBER: 4.3 GLOBAL ROOT: XMB(1, DATE CREATED: OCT 27, 2000 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: LOCAL TIMEZONE ID: XMB(1, GLOBAL REFERENCE: XMB('TIMEZONE') FIELD NUMBER: 1 FIELD NAME: TIME ZONE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The three character code represents the time zone and daylight savings where appropriate of the VHA facility supportin the VISTA HIS. GLOBAL DESCRIPTION: This is the field 1 cross-ferefence. GENERAL DESCRIPTION: The Vista Imaging application supports site reporting on a monthly basis and the reporting of critical events that require customer support intervention. Tracking these events remotely is easier if the "TIMEZONE" associated with these events is included in the message. We seek direct read access to the ^XMB("TIMEZONE") for this purpose. VIEWER: SCHLEHUBER,CAMERON VIEWER: MARSHALL,RICK VIEWER: BARRIOS,LUCILLE VIEWER: BEUSCHEL,GARY STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32176354 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: We wish to use this cross-reference to provide accurate timing of local events to remote customer support. NUMBER: 3236 IA #: 3236 DATE CREATED: OCT 30, 2000 CUSTODIAL PACKAGE: PROBLEM LIST CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMPLX NAME: MSG GMPLX ID: GMPLX GENERAL DESCRIPTION: The entry point into the routine GMPLX which is MSG when called as a function, Will return a line of text "+ Next Screen - Prev Screen ?? More actions" STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32186804 KEYWORDS: MSG COMPONENT/ENTRY POINT: MSG COMPONENT DESCRIPTION: Will return one line of Help text as described above. SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 3237 IA #: 3237 DATE CREATED: OCT 30, 2000 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOSIG NAME: DBIA3237 ID: PSOSIG GENERAL DESCRIPTION: This call, provided by Outpatient Pharmacy, will return a default Quantity value or a default Days Supply to CPRS for the Outpatient medication order entry process through CPRS. A value will only be returned if a value can appropriately be determined, based on data passed into the call. If a Quantity value is not received in this call, then a default Quantity value will be calculated. If a Quantity value is received in this call, then a default Days Supply value will be calculated. STATUS: Active MAIL MESSAGE: 33057682 COMPONENT/ENTRY POINT: QTYX(PSOQX) COMPONENT DESCRIPTION: This entry point will be used by CPRS to determine if a default Quantity value or a default Days Supply value can be assigned to an Outpatient order that is being entered through CPRS. VARIABLES: PSOQX('DOSE ORDERED',#) TYPE: Input VARIABLES DESCRIPTION: This array holds the number of Dispense Units per Dose for each dosing sequence entered during the medication order entry process in CPRS. VARIABLES: PSOQX('DURATION',#) TYPE: Input VARIABLES DESCRIPTION: This array holds the durations for each dosing sequence entered during the medication order entry process in CPRS. It is in the form of: S for # of seconds. M for # of minutes. H for # of hours. D for # of days. W for # of weeks. L for # of months. If only a numeric is passed in, then Days will be assumed. VARIABLES: PSOQX('SCHEDULE',#) TYPE: Input VARIABLES DESCRIPTION: This array holds the schedules associated with each dosing sequence entered during the medication order entry process in CPRS. VARIABLES: PSOQX('DAYS SUPPLY') TYPE: Output VARIABLES DESCRIPTION: If the PSOQX("QTY") variable is defined when the call is made, then the PSOQX("DAYS SUPPLY") variable will be used to calculate a default Quantity value. If the PSOQX("QTY") variable is not defined when the call is made, then the PSOQX("DAYS SUPPLY") variable will be the output variable that contains the default Days Supply value, if a value is able to be determined. VARIABLES: PSOQX('QTY') TYPE: Output VARIABLES DESCRIPTION: If this variable is defined when the call is made, then it will be used to calculate a default Days Supply value. If this variable is not defined when the call is made, this will be the output variable that contains the default Quantity value, if a value is able to be determined. VARIABLES: PSOQX('PATIENT') TYPE: Input VARIABLES DESCRIPTION: This variable will only be used when calculating a default Days Supply. It is equal to the internal entry number of the patient from the PATIENT file (#2). VARIABLES: PSOQX('DRUG') TYPE: Input VARIABLES DESCRIPTION: This variable will only be used when calculating a default Days Supply. It is equal to the internal entry number of the drug from the DRUG file (#50). VARIABLES: PSOQX('CONJUNCTION',#) TYPE: Input VARIABLES DESCRIPTION: This array holds the conjunctions for each dosing sequence, 'A' for And, 'T' for Then. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3238 IA #: 3238 FILE NUMBER: 142.1 GLOBAL ROOT: GMT(142.1, DATE CREATED: OCT 30, 2000 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Activate Vista Imaging Health Summary Component ID: GMT(142.1, GLOBAL REFERENCE: GMT(142.1,235) FIELD NUMBER: 5 FIELD NAME: DISABLE FLAG LOCATION: 0;6 ACCESS: Write w/Fileman FIELD DESCRIPTION: This field controls the availability of this GMTS component. FIELD NUMBER: 8 FIELD NAME: OUT OF ORDER MESSAGE LOCATION: 0;8 ACCESS: Write w/Fileman FIELD DESCRIPTION: This is the message displayed to the user if this out of order component is selected. GENERAL DESCRIPTION: The following code is designed to conditionly enable the Imaging Health Summary Component upon package install. ; Enable the Imaging Health Summary component I $D(^GMT(142.1,235)) D . S (DIE,DIC)=142.1,DA=235 . S DR="5///@;8///@" . D ^DIE The request is for direct read and a fileman edit. This code is processed during the Imaging post init. VIEWER: SCHLEHUBER,CAMERON VIEWER: DAYHOFF,RUTH VIEWER: PRICE,RICHARD M VIEWER: BARRIOS,LUCILLE VIEWER: ROWE,KIMBALL STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32179984 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: This completes the functionality which enables the Vista Imaging Health Summary Component at the site when the component exists. NUMBER: 3239 IA #: 3239 DATE CREATED: OCT 31, 2000 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSSUTIL1 NAME: DBIA3239 ID: PSSUTIL1 GENERAL DESCRIPTION: This agreement allows Computerized Patient Record System (CPRS) to pass into Pharmacy Data Management a Pharmacy Orderable Item, and the Pharmacy application for which a medication order is being entered in CPRS. In return, Pharmacy Data Management will return an array of active Dispense Drugs for that Pharmacy application that are tied to the Pharmacy Orderable Item. This call will be used by CPRS so order checks can be performed on all Dispense Drugs tied to an Orderable Item, when a Dispense Drug cannot be associated with a medication order in CPRS. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33057731 COMPONENT/ENTRY POINT: DRG(PSSDD,PSSOI,PSSPK) COMPONENT DESCRIPTION: This entry point will return all active Dispense Drugs tied to a Pharmacy Orderable Item for a specific Pharmacy application. VARIABLES: PSSDD TYPE: Input VARIABLES DESCRIPTION: This is simply the subscripted array name. VARIABLES: PSSOI TYPE: Input VARIABLES DESCRIPTION: This variable is the internal entry number from the PHARMACY ORDERABLE ITEM file (#50.7). VARIABLES: PSSPK TYPE: Input VARIABLES DESCRIPTION: This variable indicates which package the medication order is intended. 'O' for Outpatient, 'I' for Inpatient. VARIABLES: PSSDD(#;#) TYPE: Output VARIABLES DESCRIPTION: This array contains all of the active Dispense Drugs that are matched to the Orderable Item, for that particular package. The first number subscript of the array is the internal entry number from the DRUG file (#50). The second number subscript of the array (following the semicolon), is the pointer to the VA GENERIC file (#50.6) entry that the Dispense Drug is matched to. Each entry will be equal to the drug name. COMPONENT/ENTRY POINT: ITEM(PSSIT,PSSDR) COMPONENT DESCRIPTION: This entry point accepts the Pharmacy Orderable Item and Dispense Drug for a pharmacy order. The call determines whether or not the Dispense Drug is still matched to the same Pharmacy Orderable Item, or if the Dispense Drug has been rematched, and if so, will return the new Pharmacy Orderable Item. VARIABLES: PSSIT TYPE: Input VARIABLES DESCRIPTION: This represents the internal entry number for the Pharmacy Orderable Item, file #50.7. VARIABLES: PSSDR TYPE: Input VARIABLES DESCRIPTION: This represents the internal entry number for the Dispense Drug, file #50. VARIABLES: $$ITEM TYPE: Output VARIABLES DESCRIPTION: This is the output variable, in the following format: 0 means the Dispense Drug is matched to the same Pharmacy Orderable Item. 1^# means the Dispense Drug is matched to a new Pharmacy Orderable Item, and piece 2 is the internal entry number for that item. -1 means invalid data has been passed to the call. COMPONENT/ENTRY POINT: EN1(PSSOA,PSSOAP) COMPONENT DESCRIPTION: This entry point accepts a Pharmacy Orderable Item, and a package application identifier. Based on the package, this call looks at the formulary alternatives for all Dispense Drugs matched to the Pharmacy Orderable Item, and finds all the Pharmacy Orderable Items that those drugs are matched to. If an Orderable Item has at least one active Dispense Drug matched to it for that package, that Orderable Item is returned in the call. The purpose of this call is to provide Orderable Item formulary alternatives to CPRS, if a non-formulary Orderable Item is selected in the medication order process in CPRS. VARIABLES: PSSOA TYPE: Input VARIABLES DESCRIPTION: This variable is passed by reference. The input variable is equal to the internal entry number of the Pharmacy Orderable Item. VARIABLES: PSSOAP TYPE: Input VARIABLES DESCRIPTION: This variable is passed by value. It is either "O" for Outpatient, or "I" for Inpatient. VARIABLES: PSSOA TYPE: Output VARIABLES DESCRIPTION: This is the array of Pharmacy Orderable Items that are found as formulary alternatives, in the form of PSSOA(#)="", where # is the internal entry number from the Pharmacy Orderable Item file. COMPONENT/ENTRY POINT: SCH(SCH) COMPONENT DESCRIPTION: This entry point returns an expanded Schedule for an Outpatient order entered through CPRS. VARIABLES: SCH TYPE: Input VARIABLES DESCRIPTION: This is the condensed Schedule of the Outpatient order, passed by reference. Since it is passed by reference, it is returned as the output variable, as in an expanded form if an expansion if found, or as it was passed in. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3240 IA #: 3240 FILE NUMBER: 3.812 GLOBAL ROOT: XMB(3.8, DATE CREATED: NOV 01, 2000 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Mailgroup Updates ID: XMB(3.8, GLOBAL REFERENCE: XMB(3.8,D0,1, FIELD NUMBER: .01 FIELD NAME: MEMBER LOCATION: 0;1 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: XMB(3.8,D0,6, FIELD NUMBER: .01 FIELD NAME: REMOTE MEMBER LOCATION: 0;.01 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: XMB(3.8,D0,5, FIELD NUMBER: .01 FIELD NAME: MEMBER GROUP NAME LOCATION: 0;.01 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: In order to meet the FDA requirements to track the usage of the medical device known as "Vista Imaging" (the IMAGING package) VA maintains a Vista mailman mail server. The server processes monthly site usage parameters and critical event driven alerts. The 2 issues: 1) We create and populate a local mail group, "MAG SERVER", into which we add the local installer and our own, "G.IMAGING DEVELOPMENT TEAM@FORUM.VA.GOV", remote member. We also, as cleanup, remove a formerly installed remote member which failed often as a result of mail scripts not always having our development domain in place, "G.MAG SERVER@LAVC.ISC-WASH.VA.GOV". 2) Also, for clarity and because remotes may not have access to the resolved DUZ of local recipient's we place the entire recipient list in the text of the message so when coordinating efforts to resolve critical events, the contacts are most assuredly identified. VIEWER: SCHLEHUBER,CAMERON VIEWER: DAYHOFF,RUTH VIEWER: PRICE,RICHARD M VIEWER: BARRIOS,LUCILLE VIEWER: BEUSCHEL,GARY STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32194801 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: 1) for Mail group lookup: S MAGA="MAG SERVER" ; Mail group name S MAGDATA=$$FIND1^DIC(3.8,"","MX",MAGA,"","","ERR") Then: . ;Add G.MAG SERVER @ development site as remote recipient . S MAGM="G.IMAGING DEVELOPMENT TEAM@FORUM.VA.GOV" . I $$FIND1^DIC(3.812,","_MAGDATA_",","MX",MAGM,"","","ERR") D . . S MAGE(3.812,"+1,"_MAGDATA_",",.01)=MAGM . . D UPDATE^DIE("E","MAGE") . ;Remove development domain mailgroup reference . S MAGX=$E("G.MAG SERVER@LAVC.ISC-WASH.VA.GOV",1,30) . S IEN=$$FIND1^DIC(3.812,","_MAGDATA_",","MX",MAGX,"","","ERR") . I +IEN>0 D . . K MAGE . . S MAGE(3.812,IEN_","_MAGDATA_",",.01)="@" . . D UPDATE^DIE("E","MAGE") 2) D GETS^DIQ(3.8,IEN_",","2*;11*;12*","","ARRAY") NUMBER: 3242 IA #: 3242 FILE NUMBER: 3.9 GLOBAL ROOT: XMB(3.9 DATE CREATED: NOV 02, 2000 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DIRECT READ OF XMB(3.9 ID: XMB(3.9 GLOBAL REFERENCE: XMB(3.9,D0,2,D1,0, FIELD NUMBER: 3 FIELD NAME: TEXT LOCATION: 2;0 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: NDF requests a one time agreement with MailMan to do direct global reads to XMB(3.9,DA(1),2,DA Patch PSN*4*41 identified several entries in file 50 as being improperly matched to NDF. Many of these entries were incorrectly so identified. The patch generated a message to users listing the items. Sites have requested a supplemental list showing not only the name of the item, but also the IEN, inactivation date, and whether the item is an investigational drug. The data in file 50 which was used to identify these items was deleted by patch PSN*4*41. The only way to generate these new lists is to read the original message and use the B cross reference in file 50 to get the requested information. LIST^DIC will be used to identify and retrieve the messages. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32230234 SUBSCRIBING PACKAGE: NATIONAL DRUG FILE ISC: Birmingham NUMBER: 3243 IA #: 3243 DATE CREATED: NOV 02, 2000 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJORREN NAME: Active Flag ID: PSJORREN GENERAL DESCRIPTION: This API returns a flag indicating the status of the Orderable Item, Dispense Drug, Additive and/or Solution within the order. A call to $$ACTIVE^PSJORREN(DFN,ON) returns one of the following data: 1 - The drug(s) within the order is active 2^New Orderable Item - A new Orderable Item is found for Unit Dose order 0^Inactive reason - This order has no active drugs STATUS: Active MAIL MESSAGE: 33144835 COMPONENT/ENTRY POINT: $$ACTIVE COMPONENT DESCRIPTION: A call to $$ACTIVE^PSJORREN(DFN,ON) returns one of the following data: 1 - The drug(s) within the order is active 2^New Orderable Item - A new Orderable Item is found for Unit Dose order 0^Inactive reason - This order has no active drugs VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient Internal Entry Number VARIABLES: ON TYPE: Input VARIABLES DESCRIPTION: ON_"U/V" where ON is the order number and "U" is for a Unit dose or "V" for IV order. VARIABLES: $$ACTIVE TYPE: Output VARIABLES DESCRIPTION: Returns 1,2,0 for Unit Dose and 1,0 for IV orders: 1 - The drug(s) within the order is active 2^New Orderable Item - A new Orderable Item is found for Unit Dose order 0^Inactive reason - This order has no active drugs SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3244 IA #: 3244 FILE NUMBER: 773 GLOBAL ROOT: HLMA(D0, DATE CREATED: NOV 06, 2000 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Invalid MPI/PD exception messages sent to FORUM ID: HLMA(D0, GLOBAL REFERENCE: HLMA('C', FIELD NUMBER: 2 FIELD NAME: MESSAGE ID ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: MESSAGE ID x-ref GLOBAL REFERENCE: HLMA(D0, FIELD NUMBER: 13 FIELD NAME: SENDING APPLICATION LOCATION: 0;11 ACCESS: Read w/Fileman FIELD DESCRIPTION: Indicates the application sending the message. FIELD NUMBER: 14 FIELD NAME: RECEIVING APPLICATION LOCATION: 0;12 ACCESS: Read w/Fileman FIELD DESCRIPTION: Indicates the application receiving this message. GLOBAL REFERENCE: HLMA(D0,'MSH',D1, FIELD NUMBER: 200 FIELD NAME: MSH LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field, a word processing data type, is used to store the "MSH" segment when the TCP/IP Lower Layer Protocol is used. GLOBAL DESCRIPTION: The data for this field, MSH, is located on the "MSH" data node. GENERAL DESCRIPTION: Exception messsages are being sent to the MPI/PD team under the wrong circumstances. Non-MPI/PD applications trigger exception messages under inappropriate conditions because of issues in the execution of the VistA Health Level Seven (HL7) software. This IA will eliminate the possibility of non-MPI/PD applications generating exception messages. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32244704 KEYWORDS: invalid exception KEYWORDS: MPI/PD exception messages SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: MASTER PATIENT INDEX SUBSCRIBING PACKAGE: E CLAIMS MGMT ENGINE SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING DETAILS: added 3/22/10 DATE/TIME EDITED: MAR 22, 2010@16:47 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: ACKERMAN,SHIRLEY WITH CONCURRENCE OF: HSU,RAYMOND NUMBER: 3245 IA #: 3245 DATE CREATED: NOV 13, 2000 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU GET ASSOCIATED IMAGES REMOTE PROCEDURE: TIU GET ASSOCIATED IMAGES GENERAL DESCRIPTION: This Remote Procedure Call (RPC) allows the calling application to access a list of Images that have been captured and maintained by VistA Imaging, and have been asscociated with a given Document in TIU. NAME: TIU GET ASSOCIATED IMAGES TAG: GETILST ROUTINE: TIUSRVPL RETURN VALUE TYPE: ARRAY AVAILABILITY: SUBSCRIPTION DESCRIPTION: Given a Document, get the list of associated images. INPUT PARAMETER: TIUDA PARAMETER TYPE: LITERAL REQUIRED: YES SEQUENCE NUMBER: 1 DESCRIPTION: This is the record number (IEN) of the document in the TIU DOCUMENT FILE (#8925). RETURN PARAMETER DESCRIPTION: This is the list of Images associated with the Document identified by TIUDA. For example: TIUY(1)=21734 TIUY(2)=21799 TIUY(3)=21803 Where the rvalue of each list element is the record number (IEN) of each image in the IMAGE FILE (#2005). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32270622 KEYWORDS: IMAGES KEYWORDS: DOCUMENTS SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3246 IA #: 3246 DATE CREATED: NOV 13, 2000 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU GET DOCUMENTS FOR IMAGE REMOTE PROCEDURE: TIU GET DOCUMENTS FOR IMAGE GENERAL DESCRIPTION: This Remote Procedure Call (RPC) allows the calling application to access a list of Documents that have been captured and maintained by TIU, and have been asscociated with a given Image in VistA Imaging. NAME: TIU GET DOCUMENTS FOR IMAGE TAG: GETDLST ROUTINE: TIUSRVPL RETURN VALUE TYPE: ARRAY AVAILABILITY: SUBSCRIPTION DESCRIPTION: Given an image, get the list of associated documents. INPUT PARAMETER: IMGDA PARAMETER TYPE: LITERAL REQUIRED: YES SEQUENCE NUMBER: 1 DESCRIPTION: This is the record number (IEN) of the image in the IMAGE FILE (#2005). RETURN PARAMETER DESCRIPTION: This is the list of Documents associated with the Image identified by IMGDA. For example: TIUY(1)=721734 TIUY(2)=721799 TIUY(3)=721803 Where the rvalue of each list element is the record number (IEN) of image in the TIU DOCUMENT FILE (#8925). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32270623 KEYWORDS: DOCUMENTS KEYWORDS: IMAGE SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3247 IA #: 3247 DATE CREATED: NOV 13, 2000 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU LINK DOCUMENT TO IMAGE REMOTE PROCEDURE: TIU LINK DOCUMENT TO IMAGE GENERAL DESCRIPTION: This Remote procedure call will allow the calling application to link a specific Document in the TIU Document File (#8925) with a specific Image in the Image File (#2005). The call will support a many-to-many cardinality between Documents and Images. NAME: TIU LINK DOCUMENT TO IMAGE TAG: PUTIMAGE ROUTINE: TIUSRVPL RETURN VALUE TYPE: SINGLE VALUE AVAILABILITY: SUBSCRIPTION DESCRIPTION: This RPC links a document with an image. It will support a many-to-many association between documents and images. INPUT PARAMETER: TIUDA PARAMETER TYPE: LITERAL REQUIRED: YES SEQUENCE NUMBER: 1 DESCRIPTION: This is the record number (IEN) of the document in the TIU DOCUMENT FILE (#8925). INPUT PARAMETER: IMGDA PARAMETER TYPE: LITERAL REQUIRED: YES SEQUENCE NUMBER: 2 DESCRIPTION: This is the record number (IEN) of the document in the IMAGE FILE (#2005). RETURN PARAMETER DESCRIPTION: The return variable is a scalar result. If a link is successfully created, it will be the record number of the link in the TIU EXTERNAL LINKAGE FILE (#8925.91). If a link cannot be made (e.g., the document and image are already linked), the return variable will be a two '^'-piece result, with zero in the first '^'-piece, and an explanatory message in the second (e.g., 0^ Document already linked to this image). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32270624 KEYWORDS: DOCUMENT KEYWORDS: IMAGE SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3248 IA #: 3248 DATE CREATED: NOV 13, 2000 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU REMOVE LINK TO IMAGE REMOTE PROCEDURE: TIU REMOVE LINK TO IMAGE GENERAL DESCRIPTION: This Remote procedure call will allow the calling application to REMOVE the link between a specific Document in the TIU Document File (#8925) and a specific Image in the Image File (#2005). NAME: TIU REMOVE LINK TO IMAGE TAG: DELIMAGE ROUTINE: TIUSRVPL RETURN VALUE TYPE: SINGLE VALUE AVAILABILITY: SUBSCRIPTION DESCRIPTION: This RPC will remove a link between a document and an image. Only valid links may be removed. INPUT PARAMETER: TIUDA PARAMETER TYPE: LITERAL REQUIRED: YES SEQUENCE NUMBER: 1 DESCRIPTION: This is the record number (IEN) of the document in the TIU DOCUMENT FILE (#8925). INPUT PARAMETER: IMGDA PARAMETER TYPE: LITERAL REQUIRED: YES SEQUENCE NUMBER: 2 DESCRIPTION: This is the record number (IEN) of the document in the IMAGE FILE (#2005). RETURN PARAMETER DESCRIPTION: This is a BOOLEAN result. If the call is made with record numbers for which a valid link exists, it will remove the link, and the return value will be 1 (TRUE), otherwise, the return value will have two '^'-pieces (i.e., zero and an explanatory message (e.g., 0^ Document and Image not currently linked)). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32270625 KEYWORDS: DOCUMENT KEYWORDS: IMAGE SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3249 IA #: 3249 DATE CREATED: NOV 14, 2000 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MCUIMAG0 NAME: Imaging Medicine Procedure field ID: MCUIMAG0 GENERAL DESCRIPTION: Vista Imaging is requesting permission to use API $$PRCFLD^MCUIMAG0. This is needed needed to lookup the Procedure/Subspecialty pointer field during an image capture via the DICOM Image gateway. The gateway receive images directly from Image Acquisition devices (IFA, Olympus, etc.) and each device sends a pseudo transaction number consisting of the Medicine file and internal entry number for the images to be attached to. This call is required to get the procedure field name/number to do a Fileman lookup on the entry sent. VIEWER: LANG,BARBARA VIEWER: ACKERMAN,WILLIAM VIEWER: TRAXLER,FRANK VIEWER: PETIT,DAN VIEWER: WRIGHT,ROBERT W STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32319445 COMPONENT/ENTRY POINT: PRCFLD COMPONENT DESCRIPTION: The field# in one of the Medicine Procedure data files that points to the Procedure/Subspecialty file (#690). VARIABLES: MEDFILE TYPE: Input VARIABLES DESCRIPTION: Contains a Medicine file number to be used to lookup the PROCEDURE/SUBSPECIALITY field number. SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: DICOM images received on Imaging gateway contain a psuedo transaction number consisting of the medicine file and internal entry number (example: GM-200 would be Generalized Procedure/Consult Medicine file (#699.5) and entry 200). This information is lookup in the Medicine file(s) to get the patient name and procedure/sub specialty name using FILEMAN Database API. To obtain the PROCEDURE/SUBSPECIALTY field number in any Medicine file sent in the psuedo transaction number a call is made to $$PRCFLD^MCUIMAGO. The results are saved in a variable and passed to a FM database call, GETS^DIQ(MEDFILE,MEDIEN,MEDFLDS,"IE","MAGARR","MAGERR") to lookup the entry (MEDIEN) in the medicine file. NUMBER: 3250 IA #: 3250 DATE CREATED: NOV 14, 2000 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MCUIMAG0 NAME: Imaging 3250 ID: MCUIMAG0 GENERAL DESCRIPTION: Vista Imaging is requesting permission to call $$VALID^MCUIMAG0 to validate an entry in a Medicine file. This is used on an Imaging workstation to obtain a psuedo transaction number to be used to capture DICOM images directly from image acquisition devices (IFA, Olympus, etc.). VIEWER: LANG,BARBARA VIEWER: ACKERMAN,WILLIAM VIEWER: TRAXLER,FRANK VIEWER: PETIT,DAN VIEWER: WRIGHT,ROBERT W STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32319458 COMPONENT/ENTRY POINT: VALID COMPONENT DESCRIPTION: Module validate an entry in the Medicine file. VARIABLES: FILE TYPE: Input VARIABLES DESCRIPTION: Medicine file number VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Medicine internal entry number to be validated. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient's DFN VARIABLES: PRC TYPE: Input VARIABLES DESCRIPTION: Pointer to the Procedure/Subspecialty file (#697.2) SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: On an Imaging workstation, a user can select for a specified patient a list of Medicine file entries. Once a selected entry is selected a psuedo transaction number is displayed. The psuedo transaction number consists of the Medicine file and internal entry number selected. Calling $$VALID^MCUIMAGO will verify the entry selected. NUMBER: 3252 IA #: 3252 DATE CREATED: NOV 15, 2000 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCASV1 NAME: CALL TO GMRCASV1 ID: GMRCASV1 GENERAL DESCRIPTION: This DBIA will allow an application to call GUI^GMRCASV1. When this routine is called with the appropriate variables it will pass back the selected consult services, synonyms, indicate if it is a parent or the IEN of the parent, and if there are children (sub services). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 KEYWORDS: CONSULT KEYWORDS: SERVICES KEYWORDS: SYNONYMS COMPONENT/ENTRY POINT: GUI(GMRCARR,GMRCSTRT,GMRCWHY,GMRCSYSN) VARIABLES: GMRCARR TYPE: Both VARIABLES DESCRIPTION: Passed in as the array to return results in. Service - IEN^SVC NAME^PARENT^HAS CHILDREN^SVC USAGE PARENT = "0" if it is the parent record or the IEN of the parent record. HAS CHILDREN = "+" if the service has children (sub-services). SVC USAGE contains "S" if the array item is a synonym of a service entry. VARIABLES: GMRCSTRT TYPE: Input VARIABLES DESCRIPTION: Service to begin building output array from. VARIABLES: GMRCWHY TYPE: Input VARIABLES DESCRIPTION: If value is passed in as "0", all services (Service, Grouper, Tracking Only, Disabled) will be displayed. If value is passed in as "1", only services that are orderable or used for forwarding will be displayed. VARIABLES: GMRCSYN TYPE: Input VARIABLES DESCRIPTION: If value is set to "0", synonyms will not be returned and if value is set to "1", synonyms will be returned. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM DBA Comments: 6/3/14-MC: Brandon DeWayne originally requested to add FBCS as a subscriber to ICR 6/20/13. Approval received by Tony Thompson. Last email correspondence received from Brandon in July 2013. Patch released on 9/11/13 as an emergency patch. Since approval was received and patch has been released, adding FBCS as a subscribing package to ICR. NUMBER: 3259 IA #: 3259 FILE NUMBER: 991.1 GLOBAL ROOT: RGHL7(991.1, DATE CREATED: NOV 16, 2000 CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: CHECK FOR ADFN X-REF IN 991.1 ID: RGHL7(991.1, GLOBAL REFERENCE: RGHL7(991.1,'ADFN',218 GLOBAL DESCRIPTION: checking for the existance of ^RGHL7(991.1,"ADFN",218,). Where 218 is the Exception number for Potential Matches and DFN is the ien of the patient in the Patient file (#2). GENERAL DESCRIPTION: In order to keep the number of repeating Local ICNs being sent to the MPI for resolution when their is still an exception outstanding, the Local/Missing ICN Resolution job will no longer send up patients that have a Potential Match Exception. The only way that a potential match patient can get an ICN assignment would be via the Single Patient Initialization Option, so there is no need to send them up during the background job. Having said that, MPIF would like to be able to check for the Potential match exception by check for: $D(^RGHL7(991.1,"ADFN",218,)) Where DFN is the IEN of the patient in the Patient File. STATUS: Active MAIL MESSAGE: 32279925 COMPONENT/ENTRY POINT: RGHL7(991.1 COMPONENT DESCRIPTION: Checking for the existance of $D(^RGHL7(991.1,"ADFN",218,)) Where DFN is the IEN of the patient in the Patient File. SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA ISC: Oakland NUMBER: 3260 IA #: 3260 FILE NUMBER: 67 GLOBAL ROOT: LRT(67 DATE CREATED: NOV 17, 2000 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Imaging 3260 - Lab Referral file. ID: LRT(67 GLOBAL REFERENCE: 0 FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Patient's name FIELD NUMBER: .09 FIELD NAME: IDENTIFIER LOCATION: 0;9 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Images captured for Laboratory are associated to the Lab accession number which identifies the entry in appropriate sub-file in Laboratory. It is possible to have an accession number associated to the REFERRAL FILE and not the patient file. For this precaution, Imaging is requesting FM read access to this file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32287317 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: During image capture for Laboratory, the end user inputs the Laboratory Accession area, the year and the accession number. This is used to lookup the patient name and ssn. SUBSCRIBING PACKAGE: DSS EXTRACTS NUMBER: 3261 IA #: 3261 GLOBAL ROOT: DD( DATE CREATED: NOV 24, 2000 CUSTODIAL PACKAGE: VA FILEMAN USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: BLOOD BANK AND DIRECT ACCESS TO DD GLOBAL ID: DD( GLOBAL REFERENCE: DD(65,.01,0) GLOBAL DESCRIPTION: Code in routines ^LRBLJCK and ^LRBLJD1 perform Xecution of the input transform stored at this node in piece 5 to 99 of the data value. This input transform is defined for the UNIT ID field (#.01) of the BLOOD INVENTORY file (#65). Routine ^LRBLPED performs a Write of the field name stored at this node in piece 1. This field name is defined for the UNIT ID field (#.01) of the BLOOD INVENTORY file (#65). GLOBAL REFERENCE: DD(65,.01,3) GLOBAL DESCRIPTION: Code in routines LRBLJCK and LRBLJD1 perform a conditional Write of help prompt message stored at this node. This help prompt message is defined for the UNIT ID field (.01) of the BLOOD INVENTORY file (#65). GLOBAL REFERENCE: DD(65,.01,4) GLOBAL DESCRIPTION: Code in routines LRBLJCK and LRBLJD1 perform conditional execution of the executable help stored at this node. This executable help is defined for the UNIT ID field (#.01) of the BLOOD INVENTORY file (#65). GLOBAL REFERENCE: DD(65,.03,0) GLOBAL DESCRIPTION: Code in routine ^LRBLJCK performs 1) the Write of the field name stored at piece 1 of this node, and 2) performs the Xecution of the input transform stored at piece 5 to 99 of this node. The field name and input transform is defined for the INVOICE# field (#.03) of the BLOOD INVENTORY file (#65). GLOBAL REFERENCE: DD(65,.03,3) GLOBAL DESCRIPTION: Code in routine ^LRBLJCK performs a conditional write of the help prompt message stored at this node. This help prompt message is defined for the INVOICE# field (#.03) of the BLOOD INVENTORY file (#65). GLOBAL REFERENCE: DD(65,.03,4) GLOBAL DESCRIPTION: Code in routine LRBLJCK performs a conditional execution of the executable help stored at this node. The executable help is defined for the INVOICE# field (#.03) of the BLOOD INVENTORY file (#65). GLOBAL REFERENCE: DD(65,4.1,0) GLOBAL DESCRIPTION: Code in routine ^LRBLJD performs variable assignment equal to the data type stored at piece 3 at this node. This data type is defined for the DISPOSITION field (#4.1) of the BLOOD INVENTORY file (#65). GLOBAL REFERENCE: DD(65,4.1,1) GLOBAL DESCRIPTION: Code in routine ^LRBLJD and ^LRBLJD1 perform conditional Xecution of the Mumps X-references stored at the following nodes: ^DD(65,4.1,1,1,1) = node 1 of "AC" x-ref ^DD(65,4.1,1,2,1) = node 1 of "APS" x-ref ^DD(65,4.1,1,1,2) = node 2 of "AC" x-ref ^DD(65,4.1,1,2,2) = node 2 of "APS" x-ref ^DD(65,4.1,1,3,2) = node 2 of "AG" x-ref These Mumps x-references is defined for the DISPOSITION field (#4.1) of the BLOOD INVENTORY file (#65). GLOBAL REFERENCE: DD(65,4.2,1,1,1) GLOBAL DESCRIPTION: Code in routine ^LRBLJD1 performs conditional execution of the Regular x-reference stored at this node. This "AC" Regular x-ref is defined for DISPOSITION DATE filed (#4.2) of the BLOOD INVENTORY file (#65). GLOBAL REFERENCE: DD(69.2,.07,3) GLOBAL DESCRIPTION: Code in routine ^LRBLJLA performs a conditional Write of the help prompt message stored at this node. This help prompt message is defined for the LINES IN A LABLE field (#.07) of the LAB SECTION PRINT file (#69.2). GLOBAL REFERENCE: DD(69.2,.07,4) GLOBAL DESCRIPTION: Code in routine ^LRBLJLA performs conditional Xecution of the executable help stored at this node. This executable help is defined for the LINES IN A LABEL field (#.07) of the LAB SECTION PRINT file (#69.2). GLOBAL REFERENCE: DD(69.2,.07,0) GLOBAL DESCRIPTION: Code in routine ^LRBLJLA performs Xecution of the input transform stored at piece 5 to 99 of this node. This input transform is defined for LINES IN A LABEL field (#.07) of the LAB SECTION PRINT file (#69.2). GLOBAL REFERENCE: DD(66,.23,0) GLOBAL DESCRIPTION: Code in routine ^LRBLPED performs a Write of the field name stored at this node in piece 1 of the data string. This field name is for the SPECIFIC GRAVITY field (#.23) of the BLOOD PRODUCT file (#66). GLOBAL REFERENCE: DD(66,.22,0) GLOBAL DESCRIPTION: Code in routine ^LRBLPED performs a Write of the field name stored at this node in piece 1. This field name is for the PEDIATRIC PRODUCT field (#.22) of the BLOOD PRODUCT file (#66). GLOBAL REFERENCE: DD(65,8.1,0) GLOBAL DESCRIPTION: Code in routine ^LRBLQST performs variable assignment equal to the data type stored at piece 3 at this node. This data type is defined for the POS/INCOMPLETE SCREENING TESTS (#8.1) of the BLOOD INVENTORY file (#65). GLOBAL REFERENCE: DD(65,8.3,0) GLOBAL DESCRIPTION: Code in routine ^LRBLQST performs variable assignment equal to the data type stored at piece 3 at this node. This data type is defined for the DONATION TYPE (#8.3) for the BLOOD INVENTORY file (#65). GENERAL DESCRIPTION: The Blood Bank module of the LAB SERVICES package has been granted permission by the custodial package (VA FileMan) to access the DD global as detailed in this DBIA. STATUS: Active DURATION: Next Version MAIL MESSAGE: 32307804 SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING DETAILS: The blood bank software is discriminated as the LRBL namespace contained in the LR namespace or the LAB SERVICES package version 5.2 NUMBER: 3264 IA #: 3264 FILE NUMBER: 101 GLOBAL ROOT: ORD(101, DATE CREATED: NOV 29, 2000 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PROCESSING RTN FIELDS ID: ORD(101, GLOBAL REFERENCE: ORD(101,D0, FIELD NUMBER: 771 FIELD NAME: GENERATE/PROCESS ROUTINE LOCATION: 771;E1,245 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This field is executed on the receiving system. It defines the routine used to process the original inbound message in a transaction and to GENERATE and APPLICATION response/ACK back to the sending system using the entry point, GENACK^HLMA1. GLOBAL REFERENCE: ORD(101,D0, FIELD NUMBER: 772 FIELD NAME: GENERATE/PROCESS ACK ROUTINE LOCATION: 772;E1,245 ACCESS: Both R/W w/Fileman FIELD DESCRIPTION: This field is executed on the sending system when an Acknowledgement or Query response is received. The message ID of the original message is always contained within the response. This is used to identify the location of the original message and the corresponding event point protocol. Note that this pertains to Original and Enhanced Mode Application Acks only. The HL7 package generates and processes Enhanced mode Commit Accepts internally. GENERAL DESCRIPTION: One time IA for the pre-init for patches LA*5.2*58 and LR*5.2*266: The letter "Q" will need to be entered in the Processing RTN field (#771) and the Response Processing RTN field (#772) of the Protocol file (#101) for the LA7D CARELIFE RESULTS and the LA7D CARELIFE SERVER entries. Leaving this field blank will, in some instances, cause an error. FileMan utilities will be used to set these fields. STATUS: Active MAIL MESSAGE: 32285241 SUBSCRIBING PACKAGE: LAB SERVICE ISC: Dallas NUMBER: 3266 IA #: 3266 DATE CREATED: DEC 05, 2000 CUSTODIAL PACKAGE: REGISTRATION USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DPTLK1 NAME: OBTAIN PATIENT DOB FROM DPTLK1 ID: DPTLK1 GENERAL DESCRIPTION: The patient lookup routine, DPTLK1, has a useful api for obtaining a formated date of birth. Imaging is requesting permission to use this api. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32345575 KEYWORDS: DOB COMPONENT/ENTRY POINT: $$DOB(DFN,DGYR) COMPONENT DESCRIPTION: Calling routine passes the Patient's DFN and obtains the corresponding date of birth for that patient. If the patient's primary eligibility is 'Employee' then "SENSISTIVE" is passed in place of the date of birth. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient's DFN. VARIABLES: DGYR TYPE: Input VARIABLES DESCRIPTION: If input value is: 0 - returns 4-digit year (default) 1 - returns 2-digit year 2 - returns filemanager date output DOB = mm/dd/yyyy (default) = mm/dd/yy, if DGYR=1 = yyymmdd, if DGYR=2 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging is using the DOB^DPTLK1 api to obtain a patient's date of birth. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: JSHARVEY 20061128/ ADDED MH AS SUBSCRIBER AS PER FAIN. SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING DETAILS: added 5/26/09 SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT SUBSCRIBING DETAILS: ADDDED 4/3/08 SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 9/7/12-mm: Added VPS as a subscriber for VPS*1*2. After VPS*1*2 is distributed, VPS will no longer need access to ICRs #1685, 3291, 4906 with CPRS for patient lookups. DATE/TIME EDITED: NOV 28, 2007@08:12 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HSU,YUILI WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: MAY 26, 2009@12:57 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MARKS,MARY WITH CONCURRENCE OF: FAIN,ZACHARY DATE/TIME EDITED: APR 03, 2008@09:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: FAIN,ZACHARY DATE/TIME EDITED: SEP 07, 2012@08:32 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN NUMBER: 3267 IA #: 3267 DATE CREATED: DEC 05, 2000 CUSTODIAL PACKAGE: REGISTRATION USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DPTLK1 NAME: OBTAIN PATIENT SSN FROM DPTLK1 ID: DPTLK1 GENERAL DESCRIPTION: The patient lookup routine, DPTLK1, has a useful api for obtaining the patient's social security number. Imaging is requesting permission to use this api. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32345620 KEYWORDS: ssn COMPONENT/ENTRY POINT: SSN COMPONENT DESCRIPTION: On a given patient will display the patient's ssn identifier; except for employees. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient's dfn SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging is using the api to get the patient's social security number. This routine is part of the patient sensitive issue and does not display a ssn for an employee. SUBSCRIBING PACKAGE: VISUAL IMPAIRMENT SERVICE TEAM SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: JSHARVEY 20061128/ ADDED MH AS SUBSCRIBER AS PER FAIN SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING DETAILS: ADDED 5/26/09 SUBSCRIBING PACKAGE: EMERGENCY DEPARTMENT SUBSCRIBING DETAILS: ADDED 4/3/08 SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING SUBSCRIBING DETAILS: 7/23/14-API will be used as part of an HL7 interface between Consults/Request Tracking and the Healthcare Claims Processing System. DBA Comments: 9/7/12-mm: Added VPS as a subscriber for VPS*1*2. After VPS*1*2 is distributed, VPS will no longer need access to ICRs #1685, 3291, 4906 with CPRS for patient lookups. 7/23/14 - MM: Added Consults/Request Tracking as a subscriber to ICR #3267 for GMRC*3.0*75. API will be a part of an HL7 Interface between Consults/Request Tracking and the Healthcare Claims Processing System. Verified project team understood API does not track access to sensitive records. API is used to determine if the 16th sequence in the PV1 segment should be set to 'R' (Restricted Access). Patrick Hua from the project team indicated there is no interaction between their interface and the user. Because everything happens in the background job independent of the user, no tracking is needed by their software. The existing process to track user access to sensitive records occurs externally. This step takes place in CPRS before the hook is called to their software to trigger the outgoing HL7 message. DATE/TIME EDITED: NOV 28, 2006@07:12 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HSU,YUILI WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: MAY 26, 2009@12:58 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MARKS,MARY WITH CONCURRENCE OF: FAIN,ZACHARY DATE/TIME EDITED: APR 03, 2008@09:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: FAIN,ZACHARY DATE/TIME EDITED: SEP 07, 2012@08:40 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN DATE/TIME EDITED: JUL 23, 2014@15:13 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HARMON,LUCY WITH CONCURRENCE OF: ICR,TEAM NUMBER: 3268 IA #: 3268 FILE NUMBER: 8925 GLOBAL ROOT: TIU(8925, DATE CREATED: DEC 07, 2000 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Read file 8925 ID: TIU(8925, GLOBAL REFERENCE: TIU(8925, FIELD NUMBER: .01 FIELD NAME: DOCUMENT TYPE LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field points to file 8925.1 (TIU DOCUMENT DEFINITION). FIELD NUMBER: .02 FIELD NAME: PATIENT LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field points to file 9000001 (PATIENT/IHS). FIELD NUMBER: 1201 FIELD NAME: ENTRY DATE/TIME LOCATION: 12;1 ACCESS: Read w/Fileman FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: .05 FIELD NAME: STATUS LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 1405 FIELD NAME: REQUESTING PACKAGE REFERENCE LOCATION: 14;5 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field allows a linkage to be maintained between the TIU Document and the VistA package for which it was generated. GENERAL DESCRIPTION: Imaging is requesting read permission to file 8925 to obtain the document type, patient name, and document entry date/time. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32354249 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging displays the document type, patient name, and document date/time. Fields .01, .02 and 1201 are read using fileman. SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: MH ADDED 2.15.2011 DATE/TIME EDITED: FEB 15, 2011@07:45 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: TRAXLER,FRANK WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 3269 IA #: 3269 DATE CREATED: DEC 08, 2000 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RAUTL2 NAME: Imaging - Rad variable set ID: RAUTL2 GENERAL DESCRIPTION: Imaging is requesting permission to call RASET^RAUTL2 to set radiology variables needed to call RAO7PC3. Imaging stores only the Radiology Report pointer and not all the information needed by api RAO70C3. STATUS: Active MAIL MESSAGE: 32359583 COMPONENT/ENTRY POINT: RASET COMPONENT DESCRIPTION: This module requires the variable 'Y' set to the Radiology Report (file #74) ien. Variables created are: RACN, RACNI, RADATE,RADFN, RADTE, RADTI, and Y. VARIABLES: Y TYPE: Input VARIABLES DESCRIPTION: Radiology report (IEN) VARIABLES: RACN TYPE: Output VARIABLES DESCRIPTION: Case number VARIABLES: RADATE TYPE: Output VARIABLES DESCRIPTION: External date/time VARIABLES: RADFN TYPE: Output VARIABLES DESCRIPTION: Patient ien VARIABLES: RADTE TYPE: Output VARIABLES DESCRIPTION: FM date/time VARIABLES: RADTI TYPE: Output VARIABLES DESCRIPTION: inverse date/time VARIABLES: RACNI TYPE: Output VARIABLES DESCRIPTION: Case ien VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: String ^RADPT(RADFN,"DT",RADTI,"P",RANCI,0) SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging only store the Radiology report pointer associated with the image and the api RA07PC3 requires the patieint ien, inverse date/time and case ien to create the report array. Passing the report ien in varialbe 'Y' to RASET^RAUTL2 will created the variables needed for the RA07PC3 api. NUMBER: 3270 IA #: 3270 DATE CREATED: DEC 18, 2000 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RAUTL20 NAME: DBIA 3270 ID: RAUTL20 GENERAL DESCRIPTION: Imaging request permission to subscribe to routine RAUTL20, sub-modules EN1 and EN2, that have useful information for print sets. These modules will pass variables that assist in determining if a case is part of a print set. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34027598 COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: Routine for displaying '+' and '.' during a case lookup. Receives variables, RADPT, RADTI and RACNI, outputs variables RAPRTSET and RAMEMLOW. VARIABLES: RADFN TYPE: Input VARIABLES DESCRIPTION: Patient's dfn. VARIABLES: RADTI TYPE: Input VARIABLES DESCRIPTION: The internal entry number (inverse date) for the Exam Date in the Registered Exams subfile (70.02). ex: ^RADPT(RADFN,"DT",RADTI VARIABLES: RACNI TYPE: Input VARIABLES DESCRIPTION: The internal entry number for the multiple in the Examination Subfile (70.03). ex: ^RADPT(RADFN,"DT",RADTI,"P",RACNI VARIABLES: RAPRTSET TYPE: Output VARIABLES DESCRIPTION: An indicator if the case is part of a combined PRINTset; if so RARPTSET=1. VARIABLES: RAMEMLOW TYPE: Output VARIABLES DESCRIPTION: An indicator that indicates if the case is the lowest ien of the print set; if so RAMEMLOW=1. COMPONENT/ENTRY POINT: EN2 COMPONENT DESCRIPTION: Routine for determining if a case number is part of a print set and returns all entries within the printset. VARIABLES: RA4 TYPE: Both VARIABLES DESCRIPTION: Incoming an array of case numbers and outgoing an array of case number ien(s) with the following results. RA4(ienof #70.03)=case number^procedure pointers^ptr #74 VARIABLES: RADFN TYPE: Input VARIABLES DESCRIPTION: Patient's dfn VARIABLES: RADTI TYPE: Input VARIABLES DESCRIPTION: Exam date ien VARIABLES: RACNI TYPE: Input VARIABLES DESCRIPTION: Case number ien VARIABLES: RAPRTSET TYPE: Output SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging is requesting permission to call EN1^RAUTL20 and EN2^RAUTL20 to assist an end-user in deciphering if the case selected is part of a print set. The case selected may be part of a print set and the image is attached to the primary case number of the print set. NUMBER: 3272 IA #: 3272 FILE NUMBER: 200 GLOBAL ROOT: VA(200, DATE CREATED: DEC 20, 2000 CUSTODIAL PACKAGE: KERNEL USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3272 ID: VA(200, GENERAL DESCRIPTION: The Integrated Billing package requests a DBA exemption to allow the .01 field of the IB BILLING PROVIDER ID file (355.9) to point to the NEW PERSON file (200). This field is actually a variable pointer field and the NEW PERSON file would be one of the files included in that variable pointer file set. This will allow IB to access VA provider data without duplicate entry for determining the correct provider id to use for claims. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32303111 SUBSCRIBING PACKAGE: INTEGRATED BILLING NUMBER: 3273 IA #: 3273 FILE NUMBER: 773 GLOBAL ROOT: HLMA(D0, DATE CREATED: DEC 20, 2000 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3273 ID: HLMA(D0, GLOBAL REFERENCE: HLMA( FIELD NUMBER: 7 FIELD NAME: LOGICAL LINK LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 15 FIELD NAME: MESSAGE TYPE LOCATION: 0;13 ACCESS: Read w/Fileman FIELD NUMBER: 16 FIELD NAME: EVENT TYPE LOCATION: 0;14 ACCESS: Read w/Fileman FIELD NUMBER: 8 FIELD NAME: SUBSCRIBER PROTOCOL LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 20 FIELD NAME: STATUS LOCATION: P;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 100 FIELD NAME: DATE/TIME PROCESSED LOCATION: S;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .01 FIELD NAME: DATE/TIME ENTERED LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 13 FIELD NAME: SENDING APPLICATION LOCATION: 0;11 ACCESS: Read w/Fileman GLOBAL DESCRIPTION: The "B" x-ref may also be directly read. GLOBAL REFERENCE: HLMA('AC', GLOBAL DESCRIPTION: Read access to the "AC" x-ref. GENERAL DESCRIPTION: This is a request for the MPI/PD package to have Fileman Read access to several fields for the purpose of improving the information provided in the exception messages,generated while processing HL7 messages, that are sent to the MPI/PD team via Mailman. The exception message currently includes the message id of the message where the exception was encountered. We would like to add to the exception message some information about the HL7 message,including the Logical Link, Message Type,and Event Type. For that purpose we request Fileman read access to the following fields: HL7 Message Administration file (#773): Logical Link (#7) Message Type (#15) Event Type (#16) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32403821 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: MASTER PATIENT INDEX SUBSCRIBING PACKAGE: CLINICAL PROCEDURES NUMBER: 3277 IA #: 3277 DATE CREATED: DEC 29, 2000 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUSRB NAME: XUSRB ID: XUSRB GENERAL DESCRIPTION: This IA records supported API's in the XUSRB routine. This routine is used by Broker for GUI sign-on. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 36071697 COMPONENT/ENTRY POINT: OWNSKEY COMPONENT DESCRIPTION: This api is used by the "XUS KEY CHECK" rpc. This api OWNSKEY^XUSRB can be used to verify if a user has a specified security key assigned. The calling routine will send one or a reference to a subscripted array and the api will return a subscripted array with a value of 1 (user owns key) or 0 (key not found). VARIABLES: RET TYPE: Output VARIABLES DESCRIPTION: A subscripted array with a value of 1 or 0 to indicated if user holds the security key. VARIABLES: LIST TYPE: Input VARIABLES DESCRIPTION: A single value or a subscripted array of security keys to be evaluated. VARIABLES: DUZ TYPE: Used VARIABLES DESCRIPTION: DUZ variable should be defined before calling to this api. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Optional. The DUZ of a user that you want to check if they hold keys. COMPONENT/ENTRY POINT: $$INHIBIT COMPONENT DESCRIPTION: Is API is used to check if LOGON's have been inhibited. There are no inputs. NUMBER: 3278 IA #: 3278 DATE CREATED: DEC 29, 2000 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOSIGDS NAME: DBIA3278 ID: PSOSIGDS GENERAL DESCRIPTION: These calls, provided by Outpatient Pharmacy, will return default values to Computerized Patient Record System (CPRS) for Days Supply and Maximum Number of Refills for the medication order entry process. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33057772 COMPONENT/ENTRY POINT: DSUP(PSOQX) COMPONENT DESCRIPTION: This entry point will be used to return a default Days Supply value to CPRS, based on the patient and the drug selected in the medication order entry process. VARIABLES: PSOQX('PATIENT') TYPE: Input VARIABLES DESCRIPTION: This is equal to the internal entry number of the patient from the PATIENT file (#2). VARIABLES: PSOQX('DRUG') TYPE: Input VARIABLES DESCRIPTION: This is equal to the internal entry number of the drug from the DRUG file (#50). VARIABLES: PSOQX('DAYS SUPPLY') TYPE: Output VARIABLES DESCRIPTION: This is the default Days Supply value. COMPONENT/ENTRY POINT: MAX(PSOQX) COMPONENT DESCRIPTION: This entry point will be used to return a default Maximum Refills value to CPRS, based on the Patient, Drug, and Days Supply selected in the medication order entry process. VARIABLES: PSOQX('PATIENT') TYPE: Input VARIABLES DESCRIPTION: This is equal to the internal entry number of the patient from the PATIENT file (#2). VARIABLES: PSOQX('DRUG') TYPE: Input VARIABLES DESCRIPTION: This is equal to the internal entry number of the drug from the DRUG file (#50). VARIABLES: PSOQX('DAYS SUPPLY') TYPE: Input VARIABLES DESCRIPTION: This is equal to the Days Supply of the medication order. VARIABLES: PSOQX('MAX') TYPE: Output VARIABLES DESCRIPTION: This is the default Maximum Refills value. VARIABLES: PSOQX('DISCHARGE') TYPE: Input VARIABLES DESCRIPTION: This variable will be set to 1 if this order is an Outpatient order that is being entered for an Inpatient, or if these are Inpatient orders being transferred to Outpatient for discharge. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3279 IA #: 3279 DATE CREATED: JAN 02, 2001 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Chicago USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MCARUTL2 NAME: MCARUTL2 ID: MCARUTL2 GENERAL DESCRIPTION: These APIs allow the Imaging package access to the Medicine package data. The APIs will do lookups on the MEDICAL PATIENT File (#690) and the PROCEDURE/SUBSPECIALTY file (#697.2) and return data from the associated Medicine files. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32460321 KEYWORDS: MEDICINE KEYWORDS: API KEYWORDS: IMAGING COMPONENT/ENTRY POINT: SUB COMPONENT DESCRIPTION: For a Patient in the MEDICAL PATIENT file (#690) and Procedure in the PROCEDURE/SUBSPECIALTY file (#697.2), this component will return all of the requested procedures performed on that patient. Coding example of Query call: Case 1 K VAR S DFN=33,SUB=75 S FROM=2990101,TO=3001231 D SUB^MCARUTL2(.VAR,DFN,SUB,FROM,TO) or Case 2 K VAR S DFN=33,SUB="GENERIC SUBSPECIALTY" D SUB^MCARUTL2(.VAR,DFN,SUB) Example of Return Array: Case 1 Where there was a FROM and TO date for the patient. Case 2 Would pickup all data for the patient. In both cases the data would be returned in the following format. VAR=3 VAR(0)=1^3 GENERIC SUBSPECIALTY Procedures found for Patient ROBERTSON,JOHN VAR(1)=Nov 24, 2000@13:09^GENERIC SUBSPECIALTY^ROBERTSON,JOHN^MCAR(699.5^30^1^ VAR(1,2005,1)=16 VAR(2)=Nov 24, 2000@15:13^GENERIC SUBSPECIALTY^ROBERTSON,JOHN^ MCAR(699.5^32^0^ VAR(3)=Nov 24, 2000@15:23^GENERIC SUBSPECIALTY^ROBERTSON,JOHN^MCAR(699.5^ 33^0^ VARIABLES: .ARRAY TYPE: Both VARIABLES DESCRIPTION: (Required) .ARRAY = The return array where the data will be placed. Recommend the array should be namespaced. Return Array: ARRAY can be any variable array that the developer chooses. Recommend the array be namespaced. The API returns all of the procedures found for the patient in the variable array specified. When the API returns the data it will be placed into the variable array specified. ARRAY(0) = Piece1_^_Piece2 Piece1 1 Indicates that the component returned data. 0 Indicates that the component failed. Piece2 is an informational message either indicating how many entries were found for the patient or and error message stating why the component failed. X = Is a sequential number from 1 to the total number of procedures found as indicated by ARRAY. ARRAY(X) = Piece1_^_Piece2_^_Piece3 _^_Piece4_^_Piece5 _^_Piece6_^ Piece1 is the date and time of the procedure in an External format. Piece2 is procedure name within PROCEDURE/SUBSPECIALTY file (#697.2). Piece3 is Patient name. Piece4 is MCAR concatenated with "(" and the file number where the procedure can be found within the Medicine package. Piece5 is the Internal Entry Number of the procedure within the file as indicated in Piece 4 Piece6 indicates that the system found associated images. 1 indicates that there are images for this procedure 0 indicates no images where found. Y = Is a sequential number from 1 to the last IMAGE that is associated with this procedure. ARRAY(X,2005,Y) = Is the IEN of the image within the IMAGE file (#2005). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: (Required) The Internal Entry Number of the Patient with in MEDICAL PATIENT file (#690). VARIABLES: SUB TYPE: Input VARIABLES DESCRIPTION: (Required) Either the Internal Entry Number within the PROCEDURE/SUBSPECIALTY file (#697.2) or the Free Text Name of the entry in PROCEDURE/SUBSPECIALTY file (#697.2). VARIABLES: FROM TYPE: Input VARIABLES DESCRIPTION: (Optional) The start date for the procedure in File Manager format. VARIABLES: TO TYPE: Input VARIABLES DESCRIPTION: (Optional) The end date for the procedure in File Manager format. COMPONENT/ENTRY POINT: PATLK COMPONENT DESCRIPTION: This API is for selecting valid Medicine patients. The calling code would make an extrinsic function call to this entry point and the user would be prompted for a patient. After a patient has been selected the API will pass back the Medical Patient File (#690) internal entry number for that patient. It will return a -1 if a patient is not selected. Coding example of Query call: S X=$$PATLK^MCARUTL2 User interface: Select MEDICAL PATIENT NAME: LANDO,JOSEPH LANDO,JOSEPH 1-5-57 3456711 66 YES ACTIVE DUTY Enrollment Priority: GROUP 1 Category: IN PROCESS End Date: VARIABLES: IEN TYPE: Output VARIABLES DESCRIPTION: Internal Entry Number on the Medical Patient File (#690). COMPONENT/ENTRY POINT: PATSUB COMPONENT DESCRIPTION: This API will return all of the sub-specialties for a given patient with in the Medicine package. Coding example of Query call: KILL VAR D PATSUB^MCARUTL2(.VAR,DFN) Example of Return Array: VAR=8 VAR(0)=1^There were 8 procedures found for patient ROBERTSON,JOHN VAR(1)=ECG^2^2 VAR(2)=EP^4^1 VAR(3)=COL^8^1 VAR(4)=BMA^12^1 VAR(5)=BMB^13^1 VAR(6)=CONSULT^15^2 VAR(7)=PFT^23^10 VAR(8)=HEM^58^1 VARIABLES: .ARRAY TYPE: Both VARIABLES DESCRIPTION: (Required) The total number of procedures found for this patient. .ARRAY = Recommend the return array should be namespaced. Return Values: ARRAY can be any variable array that the developer chooses. When the API returns the data it will be placed into the variable array specified. ARRAY(0) = Piece1_^_Piece2 Piece1 1 Indicates that the component returned data. 0 Indicates that the component failed. Piece2 is an informational message either indicating how many entries were found for the patient or an error message stating why the component failed. X = Is a sequential number from 1 to the total number of procedures found as indicated by ARRAY. ARRAY(X) = Piece1_^_Piece2_^_Piece3 Piece1 is procedure name within PROCEDURE/SUBSPECIALTY file (#697.2). Piece2 is Internal Entry Number within PROCEDURE/ SUBSPECIALTY file (#697.2). Piece3 Total number of entries for that patient for that subspecialty. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: (Required) The Internal Entry Number of the Patient with in MEDICAL PATIENT file (#690). NUMBER: 3280 IA #: 3280 DATE CREATED: JAN 02, 2001 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Chicago USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MCARUTL3 NAME: MCARUTL3 ID: MCARUTL3 GENERAL DESCRIPTION: This API allows the Imaging package access to the Medicine package data. The API will do a lookup on the MEDICAL PATIENT File (#690) and the PROCEDURE/SUBSPECIALTY file (#697.2) for the indicated entry and return the associated Medicine package data. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32460337 KEYWORDS: MEDICINE KEYWORDS: API KEYWORDS: IMAGING COMPONENT/ENTRY POINT: MEDLKUP COMPONENT DESCRIPTION: This component will return all information on the indicated procedure and last associated image if any. Coding example of Query call: K IMAGE S FN=699.5,IEN=33 D MEDLKUP^MCARUTL3(.IMAGE,FN,IEN) Example of Return Array: IMAGE=1^699.5^30^33^ROBERTSON,JOHN^3001124.1309^ Nov 24, 2000@13:09^75^GENERIC SUBSPECIALTY^1^10 VARIABLES: .ARRAY TYPE: Both VARIABLES DESCRIPTION: (Required) .ARRAY = The return array where the data will be placed. Recommend the array should be namespaced. Return Values: ARRAY can be any variable array that the developer chooses. When the API returns the data it will be placed into the variable array specified. ARRAY = Piece1_^_Piece2_^_Piece3_^_ Piece4_^_Piece5_^_ Piece6_^_ Piece7_^_Piece8_^_Piece9_^_ Piece10_^_Piece11 Piece1 1 Indicates that the component returned data. 0 Indicates that the component failed. If the component fails Piece 2 will contain text indicating why the component failed. Piece2 The file number within the Medicine package. Piece3 The Internal Entry Number of the entry within the file indicated by Piece2. Piece4 The Internal Entry Number of the patient within the Medical Patient File (690). Piece5 The External format of the patient name. Piece6 The Procedure date and time in File Manager format. Piece7 The Procedure date and time in External format. Piece8 Pointer to the Procedure/ Subspecialty file (697.2) Piece9 The Name of the Procedure indicated in Piece8. Piece10 The internal entry number of the last image entry within the 2005 multiple in the indicated procedure. For example, ^MCAR(FN,IEN,2005,X,0) where X is the last entry. X is what is returned as Piece 10. Piece11 The internal entry number of the entry within the IMAGE file (#2005) indicated by Piece 10. VARIABLES: FN TYPE: Input VARIABLES DESCRIPTION: (Required) The File number within the Medicine package. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: (Required) The Internal Entry Number of the entry within the indicated file as specified by FN. NUMBER: 3281 IA #: 3281 FILE NUMBER: 9.7 GLOBAL ROOT: XPD(9.7 DATE CREATED: JAN 03, 2001 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Kernel Installation & Distribution System build status. ID: XPD(9.7 GLOBAL REFERENCE: XPD(9.7,D0, FIELD NUMBER: .02 FIELD NAME: STATUS LOCATION: 0;9 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the status of this package at this facility. Possible statuses as of Jan 01, 2001: ===================================== 0 = Loaded from Distribution 1 = Queued for Install 2 = Start of Install 3 = Install Completed 4 = De-Installed FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 17 FIELD NAME: INSTALL COMPLET TIME LOCATION: 1;3 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The status of a Kernel Installation & Distribution System (KIDS) build needs to be determined so a single distribution build Alpha, can queue build Beta, another single distribution. Before build Alpha queues build Beta, build Beta must be loaded from a distribution. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32437604 KEYWORDS: KIDS KEYWORDS: build SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines SUBSCRIBING DETAILS: Radiology/Nuclear Medicine will determine the status of a build by reading, with FileMan, the STATUS (#.02) field of the INSTALL (#9.7) file. SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING DETAILS: Clinical Info Resource Network will determine the status of a build by reading, with FileMan, the STATUS (#.02) field of the INSTALL (#9.7) file. SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI SUBSCRIBING DETAILS: Using FIND^DIC, pass in "B" index into the index parameter. Use screen: I $P(^(0),U,9)=3 [STATUS field #.02] SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT NUMBER: 3282 IA #: 3282 FILE NUMBER: 142 GLOBAL ROOT: GMT(142, DATE CREATED: JAN 03, 2001 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: GMT(142 ID: GMT(142, GLOBAL REFERENCE: GMTS(142,D0 FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Name of the Health Summary Type. FIELD NUMBER: .02 FIELD NAME: TITLE LOCATION: T;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: The title for the Health Summary Type. GENERAL DESCRIPTION: Health Summary grants Imaging permission to read the following fields in the HEALTH SUMMARY TYPE FILE (142). Field Node;Piece Field Name ----- ---------- ----------- .01 0;1 NAME .02 T;1 Title STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32438796 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging displays Health Summary reports by executing the following routines: SELTYP1^GMTS and EN^GMTS1. These routines require variables set to an entry in file 142 and the associated title for the selected entry. All lookups into the file are done with FM22 calls. NUMBER: 3283 IA #: 3283 FILE NUMBER: 870 GLOBAL ROOT: HLCS(870 DATE CREATED: JAN 18, 2001 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3283 ID: HLCS(870 GLOBAL REFERENCE: HLCS(870 FIELD NUMBER: .02 FIELD NAME: INSTITUTION LOCATION: 0;2 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The Registration package requests permission to perform a Read with FileMan of file 870 in order to get the name of links subscribed to by a record. STATUS: Active MAIL MESSAGE: 32484878 SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 3284 IA #: 3284 DATE CREATED: APR 21, 2003 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SCAPMCU2 NAME: DBIA3284 ID: SCAPMCU2 STATUS: Active MAIL MESSAGE: 32444303 COMPONENT/ENTRY POINT: NMPCTP COMPONENT DESCRIPTION: To get Primary Care Position name and IEN. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN in the PATIENT File (#2). VARIABLES: Name TYPE: Output VARIABLES DESCRIPTION: Name of Primary Care position. VARIABLES: IEN TYPE: Output VARIABLES DESCRIPTION: IEN of Primary Care position. SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING DETAILS: Use the routine as API to get Primary Care Position name and IEN. NUMBER: 3285 IA #: 3285 FILE NUMBER: 404.57 GLOBAL ROOT: SCTM(404.57 DATE CREATED: JAN 04, 2001 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3285 ID: SCTM(404.57 GLOBAL REFERENCE: SCTM(404.57,IEN,0) FIELD NUMBER: .11 FIELD NAME: BEEPER NUMBER LOCATION: 0;11 ACCESS: Read w/Fileman FIELD DESCRIPTION: To get the pager of the team position. STATUS: Active MAIL MESSAGE: 32444323 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING DETAILS: Reference ^SCTM(404.57) to get Primary Care Pager. NUMBER: 3286 IA #: 3286 FILE NUMBER: 404.51 GLOBAL ROOT: SCTM(404.51 DATE CREATED: JAN 04, 2001 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3286 ID: SCTM(404.51 GLOBAL REFERENCE: SCTM(404.51,IEN,0) FIELD NUMBER: .02 FIELD NAME: TEAM PHONE NUMBER LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: To get the team phone number. STATUS: Active MAIL MESSAGE: 32444328 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING DETAILS: Reference field #.02 of file #404.51 to get Primary Care Team phone. NUMBER: 3287 IA #: 3287 FILE NUMBER: 8989.3 GLOBAL ROOT: XTV(8989.3 DATE CREATED: JAN 04, 2001 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3287 ID: XTV(8989.3 GLOBAL REFERENCE: XTV(8989.3,D0, FIELD NUMBER: 320 FIELD NAME: DEFAULT DIRECTORY FOR HFS LOCATION: DEV;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: To get the default directory for HFS. GENERAL DESCRIPTION: The IA is requested for a one-time-use for a set of extract routines to read the value of the field. This version of the extract routines will retire after successfully gathered data for qualified patients at the sites. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: AUG 27, 2002 MAIL MESSAGE: 32444331 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING DETAILS: Reference field #320 of file #8989.3 to get the DEFAULT DIRECTORY FOR HFS. NUMBER: 3288 IA #: 3288 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORQOR LIST REMOTE PROCEDURE: ORQOR LIST ID: 3288 STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 9/30/14-MC: Added VPS as a subscriber to ICR #3288 for patch VPS*1*4. Approval given by Teresa Chung. VPS will use ORQOR LIST to retrieve a list of patient orders. NUMBER: 3289 IA #: 3289 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWCS LIST OF CONSULT REPORTS REMOTE PROCEDURE: ORWCS LIST OF CONSULT REPORTS ID: 3289 STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: 5/10/13-The Mental Health Program Office contracted with Capital Solution Design Corporation to provide the Behavioral Health Lab (BHL) software. BHL is a vendor product that calls this VistA RPC. Capital Solution Design John Boles - 202-642-9280 johnboles@capitalsolutiondesign.com VA BHL Support - 202-670-2847 bhl.support@capitalsolutiondesign.com DBA Comments: 5/13/13-MM: Added Mental Health as a subscriber to this ICR for use by the Behavioral Health Lab software. Details of the ICR were added to the subscribing details for Mental Health. Informational patch YS*5.01*111 documents release of BHL. DATE/TIME EDITED: MAY 13, 2013@10:55 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: THOMPSON,TONY DATE/TIME EDITED: MAY 13, 2013@10:56 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: TRAXLER,FRANK NUMBER: 3290 IA #: 3290 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWCS REPORT TEXT REMOTE PROCEDURE: ORWCS REPORT TEXT ID: 3290 STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL NUMBER: 3291 IA #: 3291 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWPT LAST5 REMOTE PROCEDURE: ORWPT LAST5 ID: 3291 STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: 5/10/13-The Mental Health Program Office contracted with Capital Solution Design Corporation to provide the Behavioral Health Lab (BHL) software. BHL is a vendor product that calls this VistA RPC. Capital Solution Design John Boles - 202-642-9280 johnboles@capitalsolutiondesign.com VA BHL Support - 202-670-2847 bhl.support@capitalsolutiondesign.com SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING DETAILS: JSH/10-23-2006 BCE added in agreement between Tony Thompson and Rich Vertigan. As part of the Bar Code Expansion project, Care Fusion's wCareView software will give providers a read-only view of consolidated patient information in a similar fashion as the CPRS Cover Sheet. SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) SUBSCRIBING DETAILS: The ORWPT LAST5 RPC will be triggered by a request sent by the Vecna Kiosk system. Access to this RPC is needed for VPS*1*1. VPS*1*2 will not be using this RPC. SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: JSH/10-23-2006 BCE added as subscriber. 9/12/12-mm: VPS has been added as a subscriber for VPS*1*1. The ORWPT LAST5 RPC will be triggered by a request sent by the Vecna Kiosk system. Access to this RPC is needed for VPS*1*1. VPS*1*2 will not be using this RPC. 5/10/13-MM: Mental Health is currently a subscriber to this ICR. Behavioral Health Lab software will also be using this RPC and details regarding its use of the ICR were added to the subscribing details for Mental Health. Informational patch YS*5.01*111 documents release of BHL. 3/5/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: OCT 23, 2006@06:49 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: THOMPSON,WILLIAM WITH CONCURRENCE OF: VERTIGAN,RICHARD DATE/TIME EDITED: SEP 12, 2012@14:45 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CHELESS,CAROLYN WITH CONCURRENCE OF: CHUNG,TERESA DATE/TIME EDITED: MAY 10, 2013@14:39 ACTION: CONTENT CORRECTED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: CHUNG,TERESA DATE/TIME EDITED: MAY 10, 2013@14:41 ACTION: CONTENT CORRECTED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: MAR 05, 2014@16:58 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 3292 IA #: 3292 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWPT PTINQ REMOTE PROCEDURE: ORWPT PTINQ ID: 3292 STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: 5/10/13-The Mental Health Program Office contracted with Capital Solution Design Corporation to provide the Behavioral Health Lab (BHL) software. BHL is a vendor product that calls this VistA RPC. Capital Solution Design John Boles - 202-642-9280 johnboles@capitalsolutiondesign.com VA BHL Support - 202-670-2847 bhl.support@capitalsolutiondesign.com SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 5/10/13-MM: Mental Health is currently a subscriber to this ICR. Behavioral Health Lab software will also be using this RPC and details regarding its use of the ICR were added to the subscribing details for Mental Health. Informational patch YS*5.01*111 documents release of BHL. 3/6/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. DATE/TIME EDITED: MAY 10, 2013@15:15 ACTION: CONTENT CORRECTED AT THE REQUEST OF: LEWIS,HEATHER WITH CONCURRENCE OF: CHUNG,TERESA DATE/TIME EDITED: MAY 10, 2013@15:16 ACTION: CONTENT CORRECTED AT THE REQUEST OF: CHUNG,TERESA WITH CONCURRENCE OF: TRAXLER,FRANK DATE/TIME EDITED: MAR 06, 2014@10:06 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 3293 IA #: 3293 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWU CLINLOC REMOTE PROCEDURE: ORWU CLINLOC ID: 3293 STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING DETAILS: JSH/10-23-2006 BCE added in agreement between Tony Thompson and Rich Vertig an. As part of the Bar Code Expansion project, Care Fusion's wCareView software will give providers a read-only view of consolidated patient information in a similar fashion as the CPRS Cover 5>Sheet. SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: JSH/10-23-2006 BCE added as a subscriber. 3/7/14 - MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. This ICR was reviewed by Dan Petit for PADP. He did not agree with using CPRS to obtain Scheduling data. In Jamie's review she agreed CPRS does not own the data and if it was not already being used, there may be a better way to obtain the data. DATE/TIME EDITED: OCT 23, 2006@06:50 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: THOMPSON,WILLIAM WITH CONCURRENCE OF: VERTIGAN,RICHARD DATE/TIME EDITED: MAR 07, 2014@13:19 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 3294 IA #: 3294 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWMC PATIENT PROCEDURES REMOTE PROCEDURE: ORWMC PATIENT PROCEDURES ID: 3294 STATUS: Active MAIL MESSAGE: 31932237 SUBSCRIBING PACKAGE: DENTAL SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE NUMBER: 3295 IA #: 3295 DATE CREATED: APR 25, 2003 CUSTODIAL PACKAGE: CLINICAL REMINDERS CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: PXRM REMINDER DIALOG (TIU) GENERAL DESCRIPTION: Returns reminder dialog for a given dialog ien. STATUS: Active MAIL MESSAGE: 35801596 KEYWORDS: PXRMRPCD SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City EDITOR: PULEO,ANTHONY G NUMBER: 3296 IA #: 3296 DATE CREATED: APR 25, 2003 CUSTODIAL PACKAGE: CLINICAL REMINDERS CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: PXRM REMINDER CATEGORY GENERAL DESCRIPTION: Returns list of reminders for a reminder category in display order. STATUS: Active MAIL MESSAGE: 35801603 KEYWORDS: PXRMRPCD SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3297 IA #: 3297 DATE CREATED: APR 21, 2003 CUSTODIAL PACKAGE: INCOME VERIFICATION MATCH USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGLEIVM NAME: DBIA3297 ID: DGLEIVM GENERAL DESCRIPTION: This DBIA is being entered to request access to two IVM APIs by the Registration package. The Registration package is creating a GUI version of the Load/Edit Patient Data option. In this option a financial query will be sent if indicated, just as in the roll and scroll Load/Edit. The APIs called are NEED^IVMCQ and QUERY^IVMCQ1. They mirror the functionality performed by the roll and scroll Load/Edi in REQ^IVMCQ. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32457531 COMPONENT/ENTRY POINT: EN VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This is the IEN from the Patient file (#2). VARIABLES: RESULT TYPE: Output VARIABLES DESCRIPTION: This array will return RESULT(0)="^1^FINANCIAL QUERY SENT" or S RESULT(0)="^1^A FINANCIAL QUERY IS NOT REQUIRED FOR THIS PATIENT" if successful, and RESULT(0)="^0^UNABLE TO PERFORM FINANCIAL QUERY", S RESULT(0)="^1^A FINANCIAL QUERY IS NOT REQUIRED FOR THIS PATIENT" or S RESULT(0)="^0^Patient Not on File" if not. NUMBER: 3298 IA #: 3298 FILE NUMBER: 984.9 GLOBAL ROOT: MPIF(984.9 DATE CREATED: JAN 11, 2001 CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Reference CMOR Request ID: MPIF(984.9 GLOBAL REFERENCE: MPIF(984.9,D0,0) FIELD NUMBER: .01 FIELD NAME: REQUEST NUMBER LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .03 FIELD NAME: DATE REQUESTED LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: .06 FIELD NAME: STATUS LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: .07 FIELD NAME: SITE LOCATION: 0;7 ACCESS: Read w/Fileman FIELD NUMBER: .08 FIELD NAME: TYPE OF MESSAGE LOCATION: 0;8 ACCESS: Read w/Fileman GLOBAL REFERENCE: MPIF(984.9,D0,1) FIELD NUMBER: 1.03 FIELD NAME: TYPE OF REQUEST LOCATION: 1;3 ACCESS: Read w/Fileman GLOBAL REFERENCE: MPIF(984.9,'C', FIELD NUMBER: .02 FIELD NAME: PATIENT LOCATION: 'C' x-reference ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: To identify all requests for a specific patient we are looping through the 'C' cross reference on the PATIENT (#.02) field. GLOBAL REFERENCE: MPIF(984.9,'AC', GENERAL DESCRIPTION: The Registration package is requesting a DBIA with Master Patient Index (MPIF) to read with FileMan the MPIF CMOR REQUEST (#984.9) file as well as a direct global read on the "C" and "AC" cross references. This information is used to display need information need to make decision about changing the CMOR. STATUS: Active MAIL MESSAGE: 32419318 SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 3299 IA #: 3299 DATE CREATED: JAN 12, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFCPDAT NAME: DBIA3299 ID: VAFCPDAT GENERAL DESCRIPTION: The CIRN package is requesting an integration agreement with the registration package to call START^VAFCPDAT. An action has been added to the CIRN Exception Handling [RG CIRN EXCEPTION HANDLING] option. This option allows the user for view Treating Facility and Subscription data associated with the selected patient. STATUS: Active MAIL MESSAGE: 32434310 COMPONENT/ENTRY POINT: START COMPONENT DESCRIPTION: Displays Treating Facility and Subscription data associated with a selected patient. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal entry number for patient file. COMPONENT/ENTRY POINT: MAIN COMPONENT DESCRIPTION: Does the same thing as START but includes a device call. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal entry number for patient file. SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 3300 IA #: 3300 DATE CREATED: MAY 21, 2004 CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MPIFAPI NAME: $$MPIQQ MPIFAPI ID: MPIFAPI GENERAL DESCRIPTION: The Smart Card folks has requested an API to be able to task off the real-time connection to the MPI for an ICN request. This process will be the same as the MPIQ^MPIFAPI(DFN) API, but will task the process off to the background. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32509552 COMPONENT/ENTRY POINT: MPIFQQ COMPONENT DESCRIPTION: New API: S TASK=$$MPIQQ^MPIFAPI(DFN) Input: DFN - IEN of the patient in the Patient (#2) file. Returns: Task Number of the tasked job. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN is the IEN of the patient in the Patient (#2) file. VARIABLES: TASK TYPE: Output VARIABLES DESCRIPTION: TASK = The task number of the TaskMan job. SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING DETAILS: This API has been approved for use by the Smart Card portion of the Registration package. No longer used. SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY NUMBER: 3301 IA #: 3301 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: JAN 30, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: 3301 ID: DPT( GLOBAL REFERENCE: DPT(DO,0) FIELD NUMBER: .6 FIELD NAME: TEST PATIENT INDICATOR LOCATION: 0;21 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Consolidated Mail Outpatient (CMOP) is allowed access to field # .6 Test Patient Indicator so that it may screen such patients from having data transmitted to CMOP hosts. VIEWER: MONTALI,MICHAEL VIEWER: MARKS,MARY VIEWER: WHITLEY,HAL STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32526855 KEYWORDS: CMOP KEYWORDS: TEST PATIENT SUBSCRIBING PACKAGE: CMOP ISC: Birmingham NUMBER: 3302 IA #: 3302 DATE CREATED: JAN 31, 2001 CUSTODIAL PACKAGE: INTEGRATED BILLING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBCNBES1 NAME: DBIA3302 ID: IBCNBES1 CREATOR: LEYVA,KATHRYN GENERAL DESCRIPTION: The ENROLLMENT APPLICATION SYSTEM (EAS) package requests use of the function $$BUFF^IBCNBES1 to add new entries to the INSURANCE BUFFER file (#355.33). Update: IB*2*497 increased the length of the SUBSCRIBER ID field, NAME OF INSURED field, and GROUP NUMBER field to support the EDI New Standards and Operating Rules for VHA providers. This required length increase made it necessary to move the location of these 3 fields to new Data Dictionary nodes. To support this implementation, all subscribers to this ICR will need to make the necessary changes in their applications to reference the new fields and remove the references to the old fields. When all subscribers have implemented the use of the new fields, the old fields will be deleted with IB*2*518. Old and new fields are noted in the field list detail of this ICR. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32530166 COMPONENT/ENTRY POINT: $$BUFF COMPONENT DESCRIPTION: This call adds new entries to the INSURANCE BUFFER file (#355.33). Returns 1 if all entries stored; returns 0 if any of the entries encountered an error while filing. VARIABLES: IBDATA TYPE: Input VARIABLES DESCRIPTION: Array to be passed by reference, contains Insurance entries to be added to the INSURANCE BUFFER file (#355.33). Medicare Only Patient Name (DFN) 60.01 IBDATA("M","DFN") pointer to #2 Source of Information .03 IBDATA("M","SOURCE") 1 - Interview Effective Date 60.02 IBDATA("M","PART A") Effective Date 60.02 IBDATA("M","PART B") Medicare HICN 60.04 IBDATA("M","HICN") *Name of Insured 60.07 IBDATA("M","NAME") Note: IB*2*497 - replaced by 91.01 Name of Insured 91.01 IBDATA("M","NAME") Veteran's Insurance Patient Name (DFN) 60.01 IBDATA(x,60.01) pointer to #2 Source of Information .03 IBDATA(x,.03) 1 - Interview Whose Insurance 60.05 IBDATA(x,60.05) 'v' for Veteran Pt. Relationship to 60.06 IBDATA(x,60.06) '01' for Patient Insured Insurance Company Name 20.01 IBDATA(x,20.01) *Name of Insured 60.07 IBDATA(x,60.07) Note: IB*2*497 - replaced by 91.01 Name of Insured 91.01 IBDATA(x,91.01) *Subscriber ID 60.04 IBDATA(x,60.04) Note: IB*2*497 - replaced by 90.03 Subscriber ID 90.03 IBDATA(x,90.03) *Group Number 40.03 IBDATA(x,40.03) Note: IB*2*497 - replaced by 90.02 Group Number 90.02 IBDATA(x,90.02) Spouse's Insurance Patient Name (DFN) 60.01 IBDATA(x,60.01) pointer to #2 Source of Information .03 IBDATA(x,.03) 1 - Interview Whose Insurance 60.05 IBDATA(x,60.05) 's' for Spouse Pt. Relationship to 60.06 IBDATA(x,60.06) '02' for Spouse Insured Insurance Company Name 20.01 IBDATA(x,20.01) *Name of Insured 60.07 IBDATA(x,60.07) Note: IB*2*497 - replaced by 91.01 Name of Insured 91.01 IBDATA(x,91.01) *Subscriber ID 60.04 IBDATA(x,60.04) Note: IB*2*497 - replaced by 90.03 Subscriber ID 90.03 IBDATA(x,90.03) *Group Number 40.03 IBDATA(x,40.03) Note: IB*2*497 - replaced by 90.02 Group Number 90.02 IBDATA(x,90.02) The entries subscripted by X (w/X=1:1) are regular insurance entries. The second level subscript contains the data to be filed in the buffer for a particular insurance policy. This second level subscript is the field number of the data field in the INSURANCE BUFFER file (#355.33). Source of Information (.03) and Patient Name (60.01) are required. VARIABLES: IBDATA(x) TYPE: Output VARIABLES DESCRIPTION: IBDATA(x,"MESSAGE") where X="M",1:1 A message node is added to the input array for each insurance company, including Medicare. This node will be either the IFN of the new entry in the buffer file if filing was successful or 0^error message. SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM ISC: Albany SUBSCRIBING DETAILS: DBIA subscriber is ENROLLMENT APPLICATION SYSTEM (EAS), Electronic 10-10EZ Processor module. SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 DBA Comments: 2/21/14-DT: Approved. Note:IB*2*497 set up the infrastructure to allow subscribing packages to begin coding against. The future IB*2.0*518 will be distributed at the same time as subscribing packages which will use the longer length fields and delete the shorter fields. DEACTIVATED FOR EDITS BY IB*2*497 PROJECT TEAM (KATHRYN LEYVA). 2/21/14-MM: Added Bill Jutzi as editor to edit ICR in Kathryn's absence. DATE ACTIVATED: FEB 21, 2014 DATE/TIME EDITED: JUN 11, 2009@08:13 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: HARPER,AMY DATE/TIME EDITED: JUN 11, 2009@08:14 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: LEYVA,KATHRYN DATE/TIME EDITED: FEB 21, 2014@18:05 ACTION: APPROVED AT THE REQUEST OF: JUTZI,BILL WITH CONCURRENCE OF: PFEIL,CATHERINE NUMBER: 3303 IA #: 3303 FILE NUMBER: 391.98 GLOBAL ROOT: DGCN(391.98, DATE CREATED: FEB 07, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3303 ID: DGCN(391.98, GLOBAL REFERENCE: DGCN(391.98,'AST' FIELD NUMBER: .04 FIELD NAME: STATUS LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: THE CLINICAL INFORMATION RESOURCE NETWORK PACKAGE NEEDS TO ORDER THROUGH THE PATIENT DATA EXCEPTION (#391.98) FILE TO PRODUCE A DISPLAY SHOWING THE STATUS AND COUNT OF OUTSTANDING PATIENT DATA REVIEW ITEMS. STATUS: Active MAIL MESSAGE: 32553898 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 3304 IA #: 3304 FILE NUMBER: 391.984 GLOBAL ROOT: DGCN(391.984 DATE CREATED: FEB 07, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3304 ID: DGCN(391.984 GLOBAL REFERENCE: DGCN(391.984 FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: THE CLINICAL INFORMATION RESOURCE NETWORK PACKAGE NEEDS TO GET THE EXTERNAL VALUE OF THE EXCEPTION STATUS OF PATIENT DATA REVIEW ENTRIES FOR THE MPI/PD STATUS DISPLAY. STATUS: Active MAIL MESSAGE: 32554036 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 3310 IA #: 3310 DATE CREATED: FEB 13, 2001 CUSTODIAL PACKAGE: SCHEDULING USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SCMCQK NAME: EN and PAT - SCMCQK Access ID: SCMCQK GENERAL DESCRIPTION: The PC Assign or Unassign, [PXCE SC PC Assign/Unassign], protocol uses the Scheduling routine SCMCQK as a means to acquire Team information for display and possible processing. [PXCE SC PC Assign/Unassign], PC Assign or Unassign, is an action item on the PXCE MAIN and PXCE SDAM menus and accesses SCMCQK using the "EN" and "PAT" entry points. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32866145 KEYWORDS: PXCE SC PC KEYWORDS: Assign/Unassign KEYWORDS: SCMCQK COMPONENT/ENTRY POINT: PAT COMPONENT DESCRIPTION: PAT^SCMCQK WILL "PROCESS A PATIENT" COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: EN^SCMCQK IS THE "MAIN CALL" TO SCMCQK TO VERIFY SETUP OF PATIENT/TEAM INFORMATION. SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER EDITOR: JACKSON,TODD NUMBER: 3311 IA #: 3311 DATE CREATED: FEB 13, 2001 CUSTODIAL PACKAGE: SCHEDULING USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SCMCU1 NAME: PXCE SC DISPLAY TEAM INFO Protcol ID: SCMCU1 GENERAL DESCRIPTION: The entry action for the Display Team Information, [PXCE SC DISPLAY TEAM INFO], protocol has the potential to use routine SCMCU1 as means to select a patient. PXCE SC DISPLAY TEAM INFO (TI Display Team Information) is an action item on the PXCE MAIN and PXCE SDAM menus and may access ^SCMCU1 at its "SEL" entry point. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32866149 KEYWORDS: PXCE SC DISPLAY TEAM INFO KEYWORDS: SCMCU1 COMPONENT/ENTRY POINT: SEL COMPONENT DESCRIPTION: SEL^SCMCU1 WILL "SELECT A PATIENT". SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER EDITOR: JACKSON,TODD NUMBER: 3314 IA #: 3314 DATE CREATED: FEB 13, 2001 CUSTODIAL PACKAGE: NDBI CUSTODIAL ISC: Dallas USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: A7ROUSB NAME: Outpatient Pharmacy/NDBI A7RPSOUB ID: A7ROUSB GENERAL DESCRIPTION: The Outpatient Pharmacy package makes a call into the National Database Integration function $$ZIEN52^A7RPSOUB(STATION#,RX#). This function will return either a NDBI Drug Table ien value if the Prescription number for the station supplied was moved to the priamry site in an integrated system or null. Calls into NDBI $$ZIEN52^A7RPSOUB(STATION#,RX#) from Outpatient Pharmacy are contingent on: 1) the presence of the sub-routine $$ZIEN52^A7RPSOUB. 2) a variable that contains a three-digit station number associated with the RX#. If any one of these two conditions is not met, then Outpatient Pharmacy will not make the call. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32579785 KEYWORDS: A7RPSOUB KEYWORDS: NDBI COMPONENT/ENTRY POINT: ZIEN52 COMPONENT DESCRIPTION: National Database Integration function $$ZIEN52^A7RPSOUB returns either the National Drug Table ien number or null. If a value is returned, then RX# from the site supplied was moved to the primary site of an integrated database. VARIABLES: Station# TYPE: Input VARIABLES DESCRIPTION: The station number should be a three digit number of the Prescription number supplied. VARIABLES: RX# TYPE: Input VARIABLES DESCRIPTION: The RX# is the .01 field of the Prescription file. SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 3315 IA #: 3315 DATE CREATED: FEB 14, 2001 CUSTODIAL PACKAGE: VA FILEMAN USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIE NAME: UPDATE DIE ID: DIE GENERAL DESCRIPTION: Registration is requesting to export a new cross reference to the .01 and .09 fields of the Patient file (#2) by hardsetting the ^DD("IX" global nodes and using UPDATE^DIE to get the IEN in ^DD("IX" to use. The reason to hardset the global rather than have KIDS export the x-ref is that the .01 of the Patient file (#2) is has changes in test in the field for the Name Standardization patch which is on indefinate hold. STATUS: Active MAIL MESSAGE: 32582597 COMPONENT/ENTRY POINT: UPDATE COMPONENT DESCRIPTION: for the .01: S ZZFDA(.11,"+1,",.01)=file# <--- would be 2 in this case S ZZFDA(.11,"+1,",.02)=xrefName <--- would be "AMPIZZ" in this case D UPDATE^DIE("","ZZFDA","ZZIEN") S DA=ZZIEN(1) <--- The Updater returns the IEN of the added entry in ZZIEN for the .09: S ZZFDA(.11,"+1,",.01)=file# <--- would be 2 in this case S ZZFDA(.11,"+1,",.02)=xrefName <--- would be "ATSSN" in this case D UPDATE^DIE("","ZZFDA","ZZIEN") S DA=ZZIEN(1) <--- The Updater returns the IEN of the added entry in ZZIEN VARIABLES: ZZFDA TYPE: Input VARIABLES DESCRIPTION: Array containing file number and x-ref name VARIABLES: ZZIEN TYPE: Output VARIABLES DESCRIPTION: IEN for new entry in ^DD("IX" - INDEX file. SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 3317 IA #: 3317 DATE CREATED: FEB 15, 2001 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RARIC1 NAME: Imaging Update Radiology files #3317 ID: RARIC1 GENERAL DESCRIPTION: Routine RARIC1 has callable modules to: 1) to stuff the physician data into an exam record and 2) delete Imaging pointers in the Radiology Report file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32588843 COMPONENT/ENTRY POINT: STUFPHY(RAVERF,RASR,RARTN COMPONENT DESCRIPTION: Adds the physician data into exam record and will delete second staff/ resident if it matches the primary staff/resident VARIABLES: RAVERF TYPE: Input VARIABLES DESCRIPTION: DUZ of physician (primary staff or primary resident) VARIABLES: RASR TYPE: Input VARIABLES DESCRIPTION: Variable equals 15 for staff and 12 if resident. VARIABLES: RARTN TYPE: Output VARIABLES DESCRIPTION: Returns description string from calling this API. COMPONENT/ENTRY POINT: DELIMGPT(RAIE74,RAIE2005 COMPONENT DESCRIPTION: Deletes imaging pointer from the Radiology Report file (74). VARIABLES: RAIE74 TYPE: Input VARIABLES DESCRIPTION: ien for entry in file 74 (Radiology Report). VARIABLES: RAIE2005 TYPE: Input VARIABLES DESCRIPTION: ien for entry in file 2005 (Image) to be deleted from file 74. SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging will use the STUFPHY component to update the radiologist information when an exam has been interpreted. The DELIMGPT module will be used to delete the image pointer from the Radiology Report file when an image is deleted. NUMBER: 3319 IA #: 3319 GLOBAL ROOT: DD(ifn,0,'VR') CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3319 ID: DD(ifn,0,'VR') GLOBAL REFERENCE: DD(ifn,0,'VR') GLOBAL DESCRIPTION: The following code may be used: I $$GET1^DID(N,"","","VERSION")?1"2.5"1A.N S ^DD(N,0,"VR")=2.5 and I '$$GET1^DID(682.1,41,"","NAME") D CLEAN^DILF G POST2 STATUS: Active MAIL MESSAGE: 32599600 SUBSCRIBING PACKAGE: LIBRARY NUMBER: 3320 IA #: 3320 DATE CREATED: FEB 21, 2001 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJBCMA3 NAME: UPDATE BCMA STATUS INFORMATION ID: PSJBCMA3 GENERAL DESCRIPTION: The purpose of this API is to get information from BAR CODE MEDICATION ADMINSTRATION (BCMA) to put in the PHARMACY PATIENT FILE (#55). STATUS: Active MAIL MESSAGE: 33100467 KEYWORDS: PSJBCMA3 COMPONENT/ENTRY POINT: EN(DFN,ON,BCID,STATUS,DATE) VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal Entry number for the patient. (Required) VARIABLES: ON TYPE: Input VARIABLES DESCRIPTION: Order number (from the PHARMACY PATIENT file) to be udpated. (Required) VARIABLES: BCID TYPE: Input VARIABLES DESCRIPTION: The barcode (unique) identifier to be updated. (Required) VARIABLES: STATUS TYPE: Input VARIABLES DESCRIPTION: Bar Code Medication Administration (BCMA) status for the specified BCID. (Required) VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: The date that BCMA changed the status of the specified unique ID. (Required) SUBSCRIBING PACKAGE: BAR CODE MED ADMIN ISC: Birmingham NUMBER: 3321 IA #: 3321 DATE CREATED: FEB 26, 2001 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DBIA 3321 GENERAL DESCRIPTION: Medicine gives permission to the VistA Imaging application to copy the following routines into their Imaging gateways. These routines are not renamed or modified at the destination. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32609115 COMPONENT/ENTRY POINT: MCUIMAGO COMPONENT DESCRIPTION: Routine to file image pointers and delete image pointers in the Medicine files. COMPONENT/ENTRY POINT: MCARUTL2 COMPONENT DESCRIPTION: Utility routine for Imaging to obtain information on Medicine file entries COMPONENT/ENTRY POINT: MCARUTL3 COMPONENT DESCRIPTION: Utility routine for Imaging to obtain information on Medicine file entries. SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging will place copies of the following routines MCUIMAG0, MCARUTL2 and MCARTUL3 into a transport global to be downloaded into the Imaging gateways. These routines are used by Imaging to store Image pointers in the Medicine package and to acquire information regarding the medicine entry. Imaging is also requesting the following information to be provided on each released patch to the aforemention routines. Information: If you are running Vista Imaging, use the menu option to copy the routines to the Imaging DICOM gateways as follows: "On the Vista server (hospital database), use menu option 'Copy Routines to DICOM Gateway' located under the 'Imaging System Manager' Menu. Then on all Text and Image gateways use the 'System Maintenance' menu to select Gateway Configuration and DICOM Master File and then select 'Download Current Radiology and MAS Routines'. This will cause the up-to-date versions of all radiology and MAS routines to be copied to the gateway systems." NUMBER: 3323 IA #: 3323 FILE NUMBER: 74 GLOBAL ROOT: RARPT( DATE CREATED: MAR 01, 2001 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3323 - Image file points to Rad Report ID: RARPT( GLOBAL REFERENCE: RARPT(D0,0) FIELD NUMBER: .01 FIELD NAME: DAY-CASE# LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field contains the date and case number of the Radiology exam associated with this report. GENERAL DESCRIPTION: Radiology gives permission to the Imaging package to point to the Radiology Report file (#74) from the Image (#2005) and Image Audit (#2005.1) data dictionaries. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32634584 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging files 2005 and 2005.1 both have field number 61 defined as a pointer to the Radiology Report file. Fields have been setup with no LAYGO access and these fields are set by an Imaging routine and not by user interaction. The 2005 file is the storage location for all images and file 2005.1 is the storage location for all images deleted at the site; used as an audit trail. ADD^MAGGTIA(MAGRY,MAGGZ) is the api used to update the entries into the Image files; the routine uses UPDATE^DIE to add an image file entry. Input variables: MAGRY is the results of the update and MAGGZ is an array that contains field numbers and associated values for the update. NUMBER: 3324 IA #: 3324 FILE NUMBER: 71 GLOBAL ROOT: RAMIS(71 DATE CREATED: MAR 01, 2001 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3324 - Imaging points to file 71 ID: RAMIS(71 GLOBAL REFERENCE: RAMIS(72,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Name of the RAD/NUC MED PROCEDURE. GENERAL DESCRIPTION: Radiology gives permission to the Imaging package to point to the RAD/NUC MED PROCEDURE file (#71) from the Image (#2005) and Image Audit (#2005.1) data dictionaries. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32634585 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging files 2005 and 2005.1 both have field number 62 defined as a pointer to the RAD/NUC MED PROCEDURE file. Fields have been setup with no LAYGO access and these fields are updated by an Imaging routine and not by user interaction. The 2005 file is the storage location for all images and file 2005.1 is the storage location for all images deleted at the site; used as an audit trail. Field 62 (PACS Procedure) was created to identify the Radiology procedure for the captured image. ADD^MAGGTIA(MAGRY,MAGGZ) is the api used to update the entries into the Image files; the routine uses UPDATE^DIE to add an image file entry. Input variables: MAGRY is the results of the update and MAGGZ is an array that contains field numbers and associated values for the update. NUMBER: 3325 IA #: 3325 DATE CREATED: MAR 01, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGRPTU NAME: DBIA3325 ID: DGRPTU GENERAL DESCRIPTION: The Enrollment Application System requests use of entry point GETPAT^DGRPTU for use by the 1010EZ module. The VistA-resident portion of the 1010EZ module accepts data transmitted to the site electronically from a web-based application where a veteran has entered enrollment data. Before the electronically submitted data can be stored by the 1010EZ module within the site's Patient database, user acceptance of the data is required. The first step in that process is for the user to match, if possible, the veteran's identifying data with an existing Patient record. This entry point, which was previously implemented by the 1010T module, will provide the user interface with standard patient lookup and duplicate checking functions within Registration. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32637286 COMPONENT/ENTRY POINT: GETPAT(DGHOWPT,DGADDF,DFN,DGNEWPF) VARIABLES: DFN TYPE: Output VARIABLES DESCRIPTION: DFN = PATIENT file (#2) IEN; if DFN = -1, then no patient selected. VARIABLES: DGNEWPF TYPE: Output VARIABLES DESCRIPTION: DGNEWPF = New patient added flag; if DGNEWPF = 1, then new patient added; if DGNEWPF = null, then existing patient. VARIABLES: DGHOWPT TYPE: Input VARIABLES DESCRIPTION: How was patient entered: 1 =10-10T registration "" otherwise VARIABLES: DGADDF TYPE: Input VARIABLES DESCRIPTION: Add new entry flag (optional): 1 =Allow new patient SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM SUBSCRIBING DETAILS: This call provides a user interface with the PATIENT file (#2) including standard patient lookup and duplicate checking functions. With user entry of basic patient identifying data (e.g., name, social security number, and date of birth), a matching entry within the Patient database is found or a new Patient record is created. The call is made from routine EASEZI as follows: D GETPAT^DGRPTU("",1,.DFN,.DGNEWPF) where: "" --> DGHOWPT in the formal parameter list. 1 --> DGHADDF in the formal parameter list; allow new patient. NUMBER: 3326 IA #: 3326 DATE CREATED: MAR 01, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTU NAME: DBIA3326 ID: DGMTU STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32637301 COMPONENT/ENTRY POINT: $$LST(DFN,DGDT,DGMTYPT) COMPONENT DESCRIPTION: Retrieve a pointer to the last Means Test or Co-pay Test and its date if the veteran has income test data at the site. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN VARIABLES: DGDT TYPE: Input VARIABLES DESCRIPTION: Date/Time (Optional - default today@2359) VARIABLES: DGMTYPT TYPE: Input VARIABLES DESCRIPTION: Type of Test (Optional - if not defined Means Test will be assumed) VARIABLES: $$LST TYPE: Output VARIABLES DESCRIPTION: Annual Means Test IEN^Date of Test^Status Name^Status Code^Source of Test SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM SUBSCRIBING DETAILS: As part of the Means Test Blocking and letters functionality, $$LST^DGMTU is called from several locations in the EASMT routines to determine the last Means Test and Means Test status for purposes of appointment management and auto-generation of notification letters to the patient. Data transmitted to the VistA 1010EZ module from the web-based application system includes a significant amount of income-related information. This information provides the identity of Spouse and Dependents, as well as some annual income and expense data. If the user has matched the veteran applicant with an existing Patient record, the call to $$LST^DGMTU will provide the most recent income test information held at the site. Then the 1010EZ module will allow the user to compare income data returned by ALL^DGMTU21 with data contained in the 1010EZ application. The call is made from EASESF2 as follows: S LASTINC=$$LST^DGMTU(EASDFN,YREND,1) I LASTINC="" S LASTINC=$$LST^DGMTU(EASDFN,YREND,2) where: EASDFN is DFN YREND is DGDT (set to 12/31 of the current year) DGMTYPT is Type of income test: 1 is Means Test and 2 is Co-Pay Test Type of income test, where 1 is Means Test and 2 is Co-Pay Test. NUMBER: 3327 IA #: 3327 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: MAR 01, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3327 ID: DPT( GLOBAL REFERENCE: DPT( FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .02 FIELD NAME: SEX LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .03 FIELD NAME: DATE OF BIRTH LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: .05 FIELD NAME: MARITAL STATUS LOCATION: 0;5 ACCESS: Both R/W w/Fileman FIELD NUMBER: .08 FIELD NAME: RELIGIOUS PREFERENCE LOCATION: 0;8 ACCESS: Both R/W w/Fileman FIELD NUMBER: .09 FIELD NAME: SOCIAL SECURITY NUMBER LOCATION: 0;9 ACCESS: Read w/Fileman FIELD NUMBER: .091 FIELD NAME: REMARKS LOCATION: 0;10 ACCESS: Both R/W w/Fileman FIELD NUMBER: .111 FIELD NAME: STREET ADDRESS [LINE 1] LOCATION: .11;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .112 FIELD NAME: STREET ADDRESS [LINE 2] LOCATION: .11;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .114 FIELD NAME: CITY LOCATION: .11;4 ACCESS: Both R/W w/Fileman FIELD NUMBER: .115 FIELD NAME: STATE LOCATION: .11;5 ACCESS: Both R/W w/Fileman FIELD NUMBER: .116 FIELD NAME: ZIP CODE LOCATION: .11;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: .117 FIELD NAME: COUNTY LOCATION: .11;7 ACCESS: Both R/W w/Fileman FIELD NUMBER: .131 FIELD NAME: PHONE NUMBER [RESIDENCE] LOCATION: .13;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .132 FIELD NAME: PHONE NUMBER [WORK] LOCATION: .13;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .211 FIELD NAME: K-NAME OF PRIMARY NOK LOCATION: .21;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .212 FIELD NAME: K-RELATIONSHIP TO PATIENT LOCATION: .21;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .213 FIELD NAME: K-STREET ADDRESS [LINE 1] LOCATION: .21;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: .214 FIELD NAME: K-STREET ADDRESS [LINE 2] LOCATION: .21;4 ACCESS: Both R/W w/Fileman FIELD NUMBER: .216 FIELD NAME: K-CITY LOCATION: .21;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: .217 FIELD NAME: K-STATE LOCATION: .21;7 ACCESS: Both R/W w/Fileman FIELD NUMBER: .218 FIELD NAME: K-ZIP CODE LOCATION: .21;8 ACCESS: Both R/W w/Fileman FIELD NUMBER: .219 FIELD NAME: K-PHONE NUMBER LOCATION: .21;9 ACCESS: Both R/W w/Fileman FIELD NUMBER: .21011 FIELD NAME: K-WORK PHONE NUMBER LOCATION: .21;11 ACCESS: Both R/W w/Fileman FIELD NUMBER: .2201 FIELD NAME: E-ZIP+4 LOCATION: .22;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .2202 FIELD NAME: D-ZIP+4 LOCATION: .22;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .2205 FIELD NAME: EMPLOYER ZIP+4 LOCATION: .22;5 ACCESS: Both R/W w/Fileman FIELD NUMBER: .2206 FIELD NAME: SPOUSE'S EMP ZIP+4 LOCATION: .22;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: .2207 FIELD NAME: K-ZIP+4 LOCATION: .22;7 ACCESS: Both R/W w/Fileman FIELD NUMBER: .251 FIELD NAME: SPOUSE'S EMPLOYER NAME LOCATION: .25;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .2515 FIELD NAME: SPOUSE'S EMPLOYMENT STATUS LOCATION: .25;15 ACCESS: Both R/W w/Fileman FIELD NUMBER: .252 FIELD NAME: SPOUSE'S EMP STREET [LINE 1] LOCATION: .25;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .255 FIELD NAME: SPOUSE'S EMPLOYER'S CITY LOCATION: .25;5 ACCESS: Both R/W w/Fileman FIELD NUMBER: .256 FIELD NAME: SPOUSE'S EMPLOYER'S STATE LOCATION: .25;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: .257 FIELD NAME: SPOUSE'S EMP ZIP CODE LOCATION: .25;7 ACCESS: Both R/W w/Fileman FIELD NUMBER: .258 FIELD NAME: SPOUSE'S EMP PHONE NUMBER LOCATION: .25;8 ACCESS: Both R/W w/Fileman FIELD NUMBER: .301 FIELD NAME: SERVICE CONNECTED? LOCATION: .3;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .302 FIELD NAME: SERVICE CONNECTED PERCENTAGE LOCATION: .3;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .313 FIELD NAME: CLAIM NUMBER LOCATION: .31;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: .3192 FIELD NAME: COVERED BY HEALTH INSURANCE? LOCATION: .31;11 ACCESS: Both R/W w/Fileman FIELD NUMBER: .3111 FIELD NAME: EMPLOYER NAME LOCATION: .311;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .31115 FIELD NAME: EMPLOYMENT STATUS LOCATION: .311;15 ACCESS: Both R/W w/Fileman FIELD NUMBER: .3113 FIELD NAME: EMPLOYER STREET [LINE 1] LOCATION: .311;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: .3116 FIELD NAME: EMPLOYER CITY LOCATION: .311;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: .3117 FIELD NAME: EMPLOYER STATE LOCATION: .311;7 ACCESS: Both R/W w/Fileman FIELD NUMBER: .3118 FIELD NAME: EMPLOYER ZIP CODE LOCATION: .311;8 ACCESS: Both R/W w/Fileman FIELD NUMBER: .3119 FIELD NAME: EMPLOYER PHONE NUMBER LOCATION: .311;9 ACCESS: Both R/W w/Fileman FIELD NUMBER: .324 FIELD NAME: SERVICE DISCHARGE TYPE [LAST] LOCATION: .32;4 ACCESS: Both R/W w/Fileman FIELD NUMBER: .325 FIELD NAME: SERVICE BRANCH [LAST] LOCATION: .32;5 ACCESS: Both R/W w/Fileman FIELD NUMBER: .326 FIELD NAME: SERVICE ENTRY DATE [LAST] LOCATION: .32;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: .327 FIELD NAME: SERVICE SEPARATION DATE [LAST] LOCATION: .32;7 ACCESS: Both R/W w/Fileman FIELD NUMBER: .328 FIELD NAME: SERVICE NUMBER [LAST] LOCATION: .32;8 ACCESS: Both R/W w/Fileman FIELD NUMBER: .32102 FIELD NAME: AGENT ORANGE EXPOS. INDICATED? LOCATION: .321;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .32103 FIELD NAME: RADIATION EXPOSURE INDICATED? LOCATION: .321;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: .322013 FIELD NAME: ENVIRONMENTAL CONTAMINANTS? LOCATION: .322;13 ACCESS: Both R/W w/Fileman FIELD NUMBER: .331 FIELD NAME: E-NAME LOCATION: .33;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .332 FIELD NAME: E-RELATIONSHIP TO PATIENT LOCATION: .33;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .333 FIELD NAME: E-STREET ADDRESS [LINE 1] LOCATION: .33;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: .334 FIELD NAME: E-STREET ADDRESS [LINE 2] LOCATION: .33;4 ACCESS: Both R/W w/Fileman FIELD NUMBER: .336 FIELD NAME: E-CITY LOCATION: .33;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: .337 FIELD NAME: E-STATE LOCATION: .33;7 ACCESS: Both R/W w/Fileman FIELD NUMBER: .338 FIELD NAME: E-ZIP CODE LOCATION: .33;8 ACCESS: Both R/W w/Fileman FIELD NUMBER: .339 FIELD NAME: E-PHONE NUMBER LOCATION: .33;9 ACCESS: Both R/W w/Fileman FIELD NUMBER: .33011 FIELD NAME: E-WORK PHONE NUMBER LOCATION: .33;11 ACCESS: Both R/W w/Fileman FIELD NUMBER: .341 FIELD NAME: D-NAME OF DESIGNEE LOCATION: .34;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .3405 FIELD NAME: D-DESIGNEE SAME AS NOK? LOCATION: .34;10 ACCESS: Both R/W w/Fileman FIELD NUMBER: .342 FIELD NAME: D-RELATIONSHIP TO PATIENT LOCATION: .34;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .343 FIELD NAME: D-STREET ADDRESS [LINE 1] LOCATION: .34;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: .344 FIELD NAME: D-STREET ADDRESS [LINE 2] LOCATION: .34;4 ACCESS: Both R/W w/Fileman FIELD NUMBER: .346 FIELD NAME: D-CITY LOCATION: .34;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: .347 FIELD NAME: D-STATE LOCATION: .34;7 ACCESS: Both R/W w/Fileman FIELD NUMBER: .348 FIELD NAME: D-ZIP CODE LOCATION: .34;8 ACCESS: Both R/W w/Fileman FIELD NUMBER: .349 FIELD NAME: D-PHONE NUMBER LOCATION: .34;9 ACCESS: Both R/W w/Fileman FIELD NUMBER: .34011 FIELD NAME: D-WORK PHONE NUMBER LOCATION: .34;11 ACCESS: Both R/W w/Fileman FIELD NUMBER: .362 FIELD NAME: DISABILITY RET. FROM MILITARY? LOCATION: .36;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .368 FIELD NAME: SERVICE DENTAL INJURY? LOCATION: .36;8 ACCESS: Both R/W w/Fileman FIELD NUMBER: .36235 FIELD NAME: RECEIVING A VA PENSION? LOCATION: .362;14 ACCESS: Both R/W w/Fileman FIELD NUMBER: .36255 FIELD NAME: RECEIVING MILITARY RETIREMENT? LOCATION: .362;16 ACCESS: Both R/W w/Fileman FIELD NUMBER: .381 FIELD NAME: ELIGIBLE FOR MEDICAID? LOCATION: .38;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .525 FIELD NAME: POW STATUS INDICATED? LOCATION: .52;5 ACCESS: Both R/W w/Fileman FIELD NUMBER: .531 FIELD NAME: CURRENT PH INDICATOR LOCATION: .53;1 ACCESS: Read w/Fileman FIELD NUMBER: .532 FIELD NAME: CURRENT PURPLE HEART STATUS LOCATION: .53;2 ACCESS: Read w/Fileman FIELD NUMBER: 57.4 FIELD NAME: SPINAL CORD INJURY LOCATION: 57;4 ACCESS: Both R/W w/Fileman FIELD NUMBER: .133 FIELD NAME: EMAIL ADDRESS LOCATION: .13;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: .2516 FIELD NAME: SPOUSE'S DATE OF RETIREMENT LOCATION: .25;16 ACCESS: Both R/W w/Fileman FIELD NUMBER: .31116 FIELD NAME: DATE OF RETIREMENT LOCATION: .311;16 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1010.156 FIELD NAME: MOST RECENT 1010EZ LOCATION: 1010.15;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1010.157 FIELD NAME: COMBAT INDICATED ON 1010EZ LOCATION: 1010.15;7 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1010.158 FIELD NAME: DISABILITY DISCHARGE ON 1010EZ LOCATION: 1010.15;8 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1010.159 FIELD NAME: APPOINTMENT REQUEST ON 1010EZ LOCATION: 1010.15;9 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1010.1511 FIELD NAME: APPOINTMENT REQUEST DATE LOCATION: 1010.15;11 ACCESS: Read w/Fileman FIELD NUMBER: .134 FIELD NAME: PHONE NUMBER [CELLULAR] LOCATION: 13;4 ACCESS: Read w/Fileman FIELD NUMBER: .135 FIELD NAME: PAGER NUMBER LOCATION: 13;5 ACCESS: Read w/Fileman GLOBAL REFERENCE: DPT(D0,.01, FIELD NUMBER: .01 FIELD NAME: ALIAS LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: DPT(DO,.02, FIELD NUMBER: .01 FIELD NAME: RACE INFORMATION LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: METHOD OF COLLECTION LOCATION: 0;2 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: DPT(D0,.06, FIELD NUMBER: .01 FIELD NAME: ETHNICITY INFORMATION LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: METHOD OF COLLECTION LOCATION: 0;2 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: The Enrollment Application System requests ability to read data via FileMan from numerous fields in the PATIENT (#2) file. The VistA-resident portion of the 1010EZ module accepts data transmitted to the site electronically from a web-based application where a veteran has entered enrollment data. In a some cases, information about the veteran applicant will already reside in the site's patient database. If that is the case, then the 1010EZ module is required to display both the newly submitted data and the existing data for comparison purposes. The Enrollment Application System requests ability to write data using FileMan to the same fields in the PATIENT (#2) file. Since the 1010EZ is a means of initiating enrollment/registration, it is of course necessary to commit the data to the database. Medical center users may review and edit the data, as needed, before filing. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32637313 SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM SUBSCRIBING DETAILS: Each data element must pass FileMan validator VAL^DIE before filing by FILE^DIE. NUMBER: 3328 IA #: 3328 FILE NUMBER: 408.12 GLOBAL ROOT: DGPR(408.12 DATE CREATED: MAR 01, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3328 ID: DGPR(408.12 GLOBAL REFERENCE: DGPR(408.12, FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: RELATIONSHIP LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .03 FIELD NAME: PERSON LOCATION: 0;3 ACCESS: Both R/W w/Fileman GLOBAL REFERENCE: DGPR(408.12,D0,E, FIELD NUMBER: .01 FIELD NAME: EFFECTIVE DATE LOCATION: 0;1 ACCESS: Both R/W w/Fileman GLOBAL DESCRIPTION: For global reference ^DGPR(408.12,D0,E,D1,0), the E subscript is the Effective Date in internal FileMan format; the D1 subscript is a sequential integer since there may be more than one subrecord for a given date. GENERAL DESCRIPTION: The Enrollment Application System requests ability to read data via FileMan from several fields in the PATIENT RELATION (#408.12) file. The VistA-resident portion of the 1010EZ module accepts data transmitted to the site electronically from a web-based application where a veteran has entered enrollment data. In a some cases, information about the veteran applicant will already reside in the site's patient database. If that is the case, then the 1010EZ module is required to display both the newly submitted data and the existing data for comparison purposes. The Enrollment Application System requests ability to write data using FileMan to the same fields in the PATIENT RELATION (#408.12) file. Since the 1010EZ is a means of initiating enrollment/registration, it is of course necessary to commit the data to the database. Medical center users may review and edit the data, as needed, before filing. The data placed in file #408.12 will be further edited at the time of formal Registration and Means Testing. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32637330 SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM SUBSCRIBING DETAILS: Data is passed through FileMan validator VAL^DIE before filing by FILE^DIE, or is filed using UPDATE^DIE. NUMBER: 3329 IA #: 3329 FILE NUMBER: 408.13 GLOBAL ROOT: DGPR(408.13 DATE CREATED: MAR 01, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3329 ID: DGPR(408.13 GLOBAL REFERENCE: DGPR(408.13, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: SEX LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .03 FIELD NAME: DATE OF BIRTH LOCATION: 0;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: .09 FIELD NAME: SOCIAL SECURITY NUMBER LOCATION: 0;9 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1.1 FIELD NAME: MAIDEN NAME LOCATION: 1;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1.2 FIELD NAME: STREET ADDRESS 1 LOCATION: 1;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1.3 FIELD NAME: STREET ADDRESS 2 LOCATION: 1;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1.4 FIELD NAME: STREET ADDRESS 3 LOCATION: 1;4 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1.5 FIELD NAME: CITY LOCATION: 1;5 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1.6 FIELD NAME: STATE LOCATION: 1;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1.7 FIELD NAME: ZIP LOCATION: 1;7 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1.8 FIELD NAME: TELEPHONE NUMBER LOCATION: 1;8 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The Enrollment Application System requests ability to read data via FileMan from several fields in the INCOME PERSON (#408.13) file. The VistA-resident portion of the 1010EZ module accepts data transmitted to the site electronically from a web-based application where a veteran has entered enrollment data. In a some cases, information about the veteran applicant will already reside in the site's patient database. If that is the case, then the 1010EZ module is required to display both the newly submitted data and the existing data for comparison purposes. The Enrollment Application System requests ability to write data using FileMan to the same fields in the INCOME PERSON (#408.13) file. Since the 1010EZ is a means of initiating enrollment/registration, it is of course necessary to commit the data to the database. Medical center users may review and edit the data, as needed, before filing. The data placed in file #408.13 will be further edited at the time of formal Registration and Means Testing. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32637362 SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM SUBSCRIBING DETAILS: Data is passed through FileMan validator VAL^DIE before filing by FILE^DIE, or is filed using UPDATE^DIE. NUMBER: 3330 IA #: 3330 FILE NUMBER: 408.21 GLOBAL ROOT: DGMT(408.21 DATE CREATED: MAR 01, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3330 ID: DGMT(408.21 GLOBAL REFERENCE: DGMT(408,21, FIELD NUMBER: 2.01 FIELD NAME: CASH, AMOUNTS IN BANK ACCOUNTS LOCATION: 2;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: 2.03 FIELD NAME: REAL PROPERTY LOCATION: 2;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: 2.04 FIELD NAME: OTHER PROPERTY OR ASSETS LOCATION: 2;4 ACCESS: Both R/W w/Fileman FIELD NUMBER: .01 FIELD NAME: YEAR LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: PATIENT RELATION LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .14 FIELD NAME: TOTAL INCOME FROM EMPLOYMENT LOCATION: 0;14 ACCESS: Both R/W w/Fileman FIELD NUMBER: .17 FIELD NAME: ALL OTHER INCOME LOCATION: 0;17 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1.01 FIELD NAME: MEDICAL EXPENSES LOCATION: 1;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1.02 FIELD NAME: FUNERAL AND BURIAL EXPENSES LOCATION: 1;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1.03 FIELD NAME: EDUCATION EXPENSES LOCATION: 1;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: 1.12 FIELD NAME: GROSS MEDICAL EXPENSES LOCATION: 1;12 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The Enrollment Application System requests ability to read data via FileMan from several fields in the INDIVIDUAL ANNUAL INCOME (#408.21) file. The VistA-resident portion of the 1010EZ module accepts data transmitted to the site electronically from a web-based application where a veteran has entered enrollment data. In a some cases, information about the veteran applicant will already reside in the site's patient database. If that is the case, then the 1010EZ module is required to display both the newly submitted data and the existing data for comparison purposes. The Enrollment Application System requests ability to write data using FileMan to the same fields in the INDIVIDUAL ANNUAL INCOME (#408.21) file. Since the 1010EZ is a means of initiating enrollment/registration, it is of course necessary to commit the data to the database. Medical center users may review and edit the data, as needed, before filing. The data placed in file #408.21 will be further edited at the time of formal Registration and Means Testing. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32637392 SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM SUBSCRIBING DETAILS: If a call to LST^DGMTU indicates that the veteran has in income test for the current income year in the site's database, no data filing is attempted. Data is passed through FileMan validator VAL^DIE before filing by FILE^DIE, or is filed using UPDATE^DIE. NUMBER: 3331 IA #: 3331 FILE NUMBER: 408.22 GLOBAL ROOT: DGMT(408.22 DATE CREATED: MAR 01, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3331 ID: DGMT(408.22 GLOBAL REFERENCE: DGMT(408,22, FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: .02 FIELD NAME: INDIVIDUAL ANNUAL INCOME LOCATION: 0;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: .07 FIELD NAME: AMOUNT CONTRIBUTED TO SPOUSE LOCATION: 0;7 ACCESS: Both R/W w/Fileman FIELD NUMBER: .09 FIELD NAME: INCAPABLE OF SELF-SUPPORT LOCATION: 0;9 ACCESS: Both R/W w/Fileman FIELD NUMBER: .1 FIELD NAME: CONTRIBUTED TO SUPPORT LOCATION: 0;10 ACCESS: Both R/W w/Fileman FIELD NUMBER: .11 FIELD NAME: CHILD HAD INCOME LOCATION: 0;11 ACCESS: Both R/W w/Fileman FIELD NUMBER: .18 FIELD NAME: CHILD 18-23 IN SCHOOL LOCATION: 0;18 ACCESS: Both R/W w/Fileman FIELD NUMBER: .19 FIELD NAME: AMOUNT CONTRIBUTED TO CHILD LOCATION: 0;19 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The Enrollment Application System requests ability to read data via FileMan from several fields in the INCOME RELATION (#408.22) file. The VistA-resident portion of the 1010EZ module accepts data transmitted to the site electronically from a web-based application where a veteran has entered enrollment data. In a some cases, information about the veteran applicant will already reside in the site's patient database. If that is the case, then the 1010EZ module is required to display both the newly submitted data and the existing data for comparison purposes. The Enrollment Application System requests ability to write data using FileMan to the same fields in the INCOME RELATION (#408.22) file. Since the 1010EZ is a means of initiating enrollment/registration, it is of course necessary to commit the data to the database. Medical center users may review and edit the data, as needed, before filing. The data placed in file #408.22 will be further edited at the time of formal Registration and Means Testing. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32637404 SUBSCRIBING PACKAGE: ENROLLMENT APPLICATION SYSTEM SUBSCRIBING DETAILS: If a call to LST^DGMTU indicates that the veteran has in income test for the current income year in the site's database, no data filing is attempted. Data is passed through FileMan validator VAL^DIE before filing by FILE^DIE, or is filed using UPDATE^DIE. NUMBER: 3332 IA #: 3332 DATE CREATED: APR 25, 2003 CUSTODIAL PACKAGE: CLINICAL REMINDERS USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: PXRM REMINDERS AND CATEGORIES GENERAL DESCRIPTION: Returns list of reminders and categories that may be selected. STATUS: Active MAIL MESSAGE: 35801614 KEYWORDS: PXRMRPCD NUMBER: 3333 IA #: 3333 DATE CREATED: MAR 02, 2004 CUSTODIAL PACKAGE: CLINICAL REMINDERS CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRMAPI0 NAME: PXRMAPI0 ID: PXRMAPI0 GENERAL DESCRIPTION: API calls for the reminder package: 1) CATREM^PXRMAPI0 Returns list of reminders and sub-categories for a given category. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 38111073 KEYWORDS: PXRMAPI COMPONENT/ENTRY POINT: CATREM COMPONENT/ENTRY POINT: CATREM(CIEN,.CARRAY) COMPONENT DESCRIPTION: This component return a list of reminders assigned to a specific category. VARIABLES: CIEN TYPE: Input VARIABLES DESCRIPTION: CIEN is the reminder category IEN from file 811.7. VARIABLES: CARRAY TYPE: Output VARIABLES DESCRIPTION: CARRAY is the array of reminders that are assigned to a category. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City EDITOR: PULEO,ANTHONY G NUMBER: 3335 IA #: 3335 FILE NUMBER: 870 GLOBAL ROOT: HLCS(870, DATE CREATED: MAR 06, 2001 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Gather Logical Link Domain ID: HLCS(870, GLOBAL REFERENCE: HLCS(870, FIELD NUMBER: .03 FIELD NAME: DOMAIN LOCATION: 0;7 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is a pointer to the Domain file but we are using the external domain name. FIELD NUMBER: .01 FIELD NAME: NODE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Also allows direct global read access to the "B" x-ref. FIELD NUMBER: .02 FIELD NAME: INSTITUTION LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: LLP TYPE LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: STATE LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 14 FIELD NAME: SHUTDOWN LLP ? LOCATION: 0;15 ACCESS: Read w/Fileman FIELD NUMBER: 400.03 FIELD NAME: TCP/IP SERVICE TYPE LOCATION: 400;3 ACCESS: Read w/Fileman STATUS: Active MAIL MESSAGE: 32610988 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: MASTER PATIENT INDEX SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING NUMBER: 3336 IA #: 3336 FILE NUMBER: 433 GLOBAL ROOT: PRCA(433 DATE CREATED: MAR 07, 2001 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: IB REFERENCING 433 ID: PRCA(433 GLOBAL REFERENCE: PRCA(433,TRDA,0) FIELD NUMBER: .01 FIELD NAME: TRANSACTION NUMBER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: TRANSACTION STATUS LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: These fields are being used by various reports in the Diagnostic Measures module that display the comments from the transactions for each receivable, for example: First Party Follow-up report. GLOBAL REFERENCE: PRCA(433,'C',BILL,TRDA) GLOBAL DESCRIPTION: Various reports in the Diagnostic Measures module use this cross-reference in order to get the transactions entered for a given bill. GLOBAL REFERENCE: PRCA(433,TRDA,1) FIELD NUMBER: 11 FIELD NAME: TRANSACTION DATE LOCATION: 1;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 12 FIELD NAME: TRANSACTION TYPE LOCATION: 1;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 19 FIELD NAME: DATE ENTERED LOCATION: 1;9 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: These fields are being used by various reports in the Diagnostic Measures module that display the comments from the transactions for each receivable, for example: First Party Follow-up report. GLOBAL REFERENCE: PRCA(433,TRDA,5) FIELD NUMBER: 20 FIELD NAME: PREPAYMT TRANS. LOCATION: 5;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 5.02 FIELD NAME: BRIEF COMMENTS LOCATION: 5;2 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: These fields are being used by various reports in the Diagnostic Measures module that display the comments from the transactions for each receivable, for example: First Party Follow-up report. GLOBAL REFERENCE: PRCA(433,TRDA,8) FIELD NUMBER: 86 FIELD NAME: TRANS. COMMENTS LOCATION: 8;6 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: These fields are being used by various reports in the Diagnostic Measures module that display the comments from the transactions for each receivable, for example: First Party Follow-up report. GLOBAL REFERENCE: PRCA(433,TRDA,7,COM,0) FIELD NUMBER: .01 FIELD NAME: COMMENTS LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: These fields are being used by various reports in the Diagnostic Measures module that display the comments from the transactions for each receivable, for example: First Party Follow-up report. GENERAL DESCRIPTION: Various places in the IB package, such as MRA Extract and Diagnostic Measures, need to pull transactions from AR. This agreement allows IB to directly access the AR Transaction file (433). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32843572 SUBSCRIBING PACKAGE: INTEGRATED BILLING EDITOR: ROCHA,MARCELO NUMBER: 3337 IA #: 3337 FILE NUMBER: 430.3 GLOBAL ROOT: PRCA(430.3 DATE CREATED: APR 27, 2006 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: IB referencing 430.3 ID: PRCA(430.3 GLOBAL REFERENCE: PRCA(430.3,D0,0 FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: ABBREVIATION LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: STATUS NUMBER LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 42972411 SUBSCRIBING PACKAGE: INTEGRATED BILLING EDITOR: GUSTAFSON,ERIC S NUMBER: 3339 IA #: 3339 FILE NUMBER: 2 GLOBAL ROOT: DPT DATE CREATED: MAR 09, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA 3339 - FBCS & File 2 fields ID: DPT CREATOR: HARVEY,JULIE S GLOBAL REFERENCE: DPT(D0,0 FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Patient name FIELD NUMBER: .02 FIELD NAME: SEX LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: Patient's Sex (M:MALE;F:FEMALE) FIELD NUMBER: .03 FIELD NAME: DATE OF BIRTH LOCATION: 0;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: Patient's date of birth FIELD NUMBER: .09 FIELD NAME: SOCIAL SECURITY NUMBER LOCATION: 0;9 ACCESS: Read w/Fileman FIELD DESCRIPTION: Patient's social security number FIELD NUMBER: .301 FIELD NAME: SERVICE CONNECTED? LOCATION: .3;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: SERVICE CONNECTED (Y:YES;N:NO) FIELD NUMBER: 391 FIELD NAME: TYPE LOCATION: TYPE;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Patient type. Field is a pointer to ^DG(391. FIELD NUMBER: 1901 FIELD NAME: VETERAN (Y/N)? LOCATION: VET;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Is patient a veteran. (Y:YES;N:NO) GENERAL DESCRIPTION: The subscribers are given permission to read the following fields from the Patient file (#2). Fields: .01 -NAME .02 -SEX .03 -DATE OF BIRTH .09 -SOCIAL SECURITY NUMBER 301 -TYPE 391 -SERVICE CONNECTED? 1901 -VETERAN (Y/N)? STATUS: Active DURATION: Till Otherwise Agreed SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM SUBSCRIBING DETAILS: added 12/11/2008 SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING DETAILS: LR added 3/21/11 DBA Comments: USAGE CHANGED 3/21/11 WHEN SUBSCRIBERS INCREASED PRIVATE -> CONTROLLED REMOVED IMAGING AS SUBSCRIBER ON 12/11/2008 SINCE ICR HAD BEEN WITHDRAWN ADDED FBCS AS A SUBSCRIBER AND CORRECTED DESCRIPTION, THEN APPROVED. DATE ACTIVATED: DEC 11, 2008 DATE/TIME EDITED: DEC 11, 2008@21:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BAUMANN,SCOTT WITH CONCURRENCE OF: PRIETULA,LINDA DATE/TIME EDITED: DEC 11, 2008@20:58 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: PRIETULA,LINDA WITH CONCURRENCE OF: HARVEY,JULIE DATE/TIME EDITED: DEC 11, 2008@21:04 ACTION: APPROVED AT THE REQUEST OF: BAUMANN,SCOTT WITH CONCURRENCE OF: PRIETULA,LINDA DATE/TIME EDITED: DEC 11, 2008@20:45 ACTION: CONTENT CORRECTED AT THE REQUEST OF: PRIETULA,LINDA WITH CONCURRENCE OF: HARVEY,JULIE DATE/TIME EDITED: MAR 21, 2011@09:03 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: SMULLEN,GEOFFREY WITH CONCURRENCE OF: KOPECKY,STEVE DATE/TIME EDITED: MAR 21, 2011@09:04 ACTION: USAGE CHOICE CHANGED AT THE REQUEST OF: HARVEY,JULIE NUMBER: 3342 IA #: 3342 FILE NUMBER: 450 GLOBAL ROOT: PRSPC( DATE CREATED: MAR 27, 2001 CUSTODIAL PACKAGE: PAID USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3342 ID: PRSPC( GLOBAL REFERENCE: PRSPC( FIELD NUMBER: 80 FIELD NAME: SEPARATION IND LOCATION: 1;33 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: IB uses the SEPARATION IND field as part of the process to identify if a VA patient is also a VA employee. First, it will check if the patient SSN is on the PAID EMPLOYEE file (#450) by looking at the "SSN" cross- -reference. If found, it then checks if the field 80 (SEPARATION IND) for the employee has a value different of "Y". If so, it assumes that the patient is a VA employee. GLOBAL REFERENCE: PRSPC('SSN',SSN,DA) GLOBAL DESCRIPTION: With the Social Security Number, IB can use this cross-reference to find the internal entry number (DA) for the SSN holder on the PAID EMPLOYEE file (#450). GENERAL DESCRIPTION: Integrated Billing has permission to access the PAID EMPLOYEE file (#450) for the following fields described in this DBIA: STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32831082 SUBSCRIBING PACKAGE: INTEGRATED BILLING NUMBER: 3343 IA #: 3343 DATE CREATED: APR 18, 2001 CUSTODIAL PACKAGE: INTEGRATED BILLING USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBCOIVM1 NAME: DBIA3343 ID: IBCOIVM1 GENERAL DESCRIPTION: Accounts Receivable has permission to make the following calls to IB in order to get information about bills: STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32843671 COMPONENT/ENTRY POINT: $$BTYP(BN,X) COMPONENT DESCRIPTION: This function returns the bill type as the following: "R" - Pharmacy Refill "P" - Prosthetics "I" - Inpatient "O" - Outpatient AR uses this function in the generation of the AR Workload To-Do List. It passes a pointer to the BILL/CLAIMS file (#399) plus the zero node of this entry and the function returns one of the 4 classifications above for the bill. VARIABLES: BN TYPE: Input VARIABLES DESCRIPTION: Pointer to the bill in file #399 VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: Zeroth node of pointed-to bill entry VARIABLES: $$BTYP TYPE: Output VARIABLES DESCRIPTION: There are 4 possible values returned by this function: "R" - Pharmacy Refill "P" - Prosthetics "I" - Inpatient "O" - Outpatient SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE NUMBER: 3344 IA #: 3344 DATE CREATED: MAR 28, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: DG FIELD MONITOR GENERAL DESCRIPTION: This protocol is an event point which monitors the editing of fields in DG* application files. At the time of this event point, the following variables will be present in the environment: Variable Description -------- ----------------------------------------------- DGDA DA array as exists during Fileman editing DGFILE File or subfile number where changed field resides DGFIELD Number of changed field DGTYPE Type of cross reference action (ADD, DELETE or UPDATE) DGDTH Date/time of change in $Horolog format DGUSER DUZ of user that made the change DGOPT Current menu option in "option_name^menu_text" format DGX X array as documented for Fileman new style x-refs DGX1 X1 array as documented for Fileman new style x-refs DGX2 X2 array as documented for Fileman new style x-refs This protocol is triggered by "listener" cross references on selected fields. By employing logic such as "If DGFILE=2, DGFIELD=.361, DGTYPE="SET", then...", subscribers to this protocol may take action based on edit activity which involves those fields. This event point is designed to occur only once per field editing activity. The DGTYPE variable can be interpreted as follows: o ADD transactions indicate that data has been added to a field that was previously null. The DGX, DGX1 and DGX2 arrays will contain the Fileman X, X1 and X2 arrays (respectively) as documented for the execution of 'SET' logic. o DELETE transactions indicate that previously existing data has been deleted without being replaced. The DGX, DGX1 and DGX2 arrays will contain the Fileman X, X1 and X2 arrays (respectively) as documented for the execution of 'KILL' logic. o UPDATE transactions indicate that existing data has been deleted and new data has been filed. The DGX, DGX1 and DGX2 arrays will contain the Fileman X, X1 and X2 arrays (respectively) as documented for the execution of 'SET' logic. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32789091 KEYWORDS: Monitor KEYWORDS: Listener KEYWORDS: DG SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION SUBSCRIBING DETAILS: The subscribing protocols are: SPN REG STATUS DELETE Notice of Date of Death Deletion SPN REG STATUS UPDATE Update Registration Status to Expired SUBSCRIBING PACKAGE: SCHEDULING SUBSCRIBING DETAILS: The subscribing protocol is: SCMC PCMM INACTIVATE ON DATE OF DEATH SUBSCRIBING PACKAGE: FEE BASIS SUBSCRIBING DETAILS: The subscribing protocol is: FB PATIENT DATA CHANGE SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT SUBSCRIBING DETAILS: The subscribing protocol is: PSU PATIENT DEMOGRAPHIC CHANGE SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: Added VPR DG UPDATES protocol to event point. The VPR protocol listeners will store the patient's DFN in an ^XTMP array; another process within HMP watches this global for patients to update and will re-pull a snapshot of the patient's demographics. DBA Comments: 10/20/14-MM: Added VPR as a subscriber for VPR*1*3. The VPR protocol listeners will simply store the patient's DFN in an ^XTMP array; another process within HMP watches this global for patients to update and will re-pull a snapshot of the patient's demographics. Melanie was notified the ICR team does not currently have Registration knowledgeable resources to review the request and the VPR team is responsible for the technical correctness and use of the event point. They are also responsible for assuring the event point is used for its intended purpose and the protocol they add does not have a negative impact on any of the protocols executed after VPR. She provided the above justification for use of the event point and said she had worked with the event point with CPRS. DATE/TIME EDITED: OCT 20, 2014@15:03 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BEUCHLER,MELANIE WITH CONCURRENCE OF: ICR,TEAM NUMBER: 3345 IA #: 3345 DATE CREATED: APR 18, 2001 CUSTODIAL PACKAGE: INTEGRATED BILLING USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBJD1 NAME: DBIA3345 ID: IBJD1 GENERAL DESCRIPTION: Accounts Receivable has permission to make the following calls to IB in order to get the classification (First or Third Party) for an AR Category. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32843683 COMPONENT/ENTRY POINT: $$CATTYP(IBBCAT) COMPONENT DESCRIPTION: This function classifies an AR category into three types: "F" - First Party Category "T" - Third Party Category "" - Category cannot be classified or invalid category AR uses this function in the generation of the AR Workload To-Do List. It passes an AR Category (pointer to file #430.2) and this function classifies the AR Category as First Party or Third Party. Note: The algorithm used in this function is specific for the Diagnostic Measures module. VARIABLES: IBBCAT TYPE: Input VARIABLES DESCRIPTION: AR Category VARIABLES: $$CATTYP TYPE: Output VARIABLES DESCRIPTION: There are three possible values returned by this function: "F" - First Party Category "T" - Third Party Category "" - Category cannot be classified or invalid category SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE NUMBER: 3346 IA #: 3346 DATE CREATED: MAR 28, 2001 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RCBECHGA NAME: DBIA3346 ID: RCBECHGA GENERAL DESCRIPTION: Integrated Billing has permission to make the following calls to AR in order get information about Repayment Plans. This information is used in 2 reports: First Party Follow-up Report and Repayment Plan Follow-up Report. Both of these reports belong to the Diagnostic Measures module. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32843579 COMPONENT/ENTRY POINT: $$REPDATA(BILL,DAYS) COMPONENT DESCRIPTION: This function returns information about a Repayment Plan associated to an AR receivable. VARIABLES: BILL TYPE: Input VARIABLES DESCRIPTION: Pointer to the ACCOUNTS RECEIVABLE file (#430). VARIABLES: DAYS TYPE: Input VARIABLES DESCRIPTION: Number of days over the due date for a payment not received to be considered defaulted. VARIABLES: $$REPDATA TYPE: Output VARIABLES DESCRIPTION: The value returned by this function is a string that contains the following information separated by "^" (up-arrow): 1. Repayment Plan Start Date (FM format) 2. Balance (Repayment Plan) 3. Monthly Payment Amount 4. Due Date (day of the month) 5. Last Payment Date (from file #433) 6. Last Payment Amount (from file #433) 7. Number of Payments Due 8. Number of Payments Defaulted SUBSCRIBING PACKAGE: INTEGRATED BILLING NUMBER: 3347 IA #: 3347 FILE NUMBER: 340 GLOBAL ROOT: RCD(340 DATE CREATED: MAR 28, 2001 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3347 ID: RCD(340 GLOBAL REFERENCE: RCD(340, FIELD NUMBER: .01 FIELD NAME: DEBTOR LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 110 FIELD NAME: SSN LOCATION: Computed ACCESS: Read w/Fileman FIELD NUMBER: "B" FIELD NAME: X-REF ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 1.01 FIELD NAME: STREED ADDRESS #1 LOCATION: 1;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 1.02 FIELD NAME: STREET ADDRESS #2 LOCATION: 1;2 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 1.03 FIELD NAME: STREET ADDRESS #3 LOCATION: 1;3 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 1.04 FIELD NAME: CITY LOCATION: 1;4 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 1.05 FIELD NAME: STATE LOCATION: 1;5 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 1.06 FIELD NAME: ZIP CODE LOCATION: 1/6 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 1.07 FIELD NAME: PHONE NUMBER LOCATION: 1;7 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 1.08 FIELD NAME: FOREIGN COUNTRY CODE LOCATION: 1;8 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 1.09 FIELD NAME: ADDRESS UNKNOWN LOCATION: 1;9 ACCESS: Direct Global R/W & w/Fileman GLOBAL DESCRIPTION: The fields DEBTOR and SSN are being used by the following Diagnostic Measures reports: First Party Follow-up Report, CHAMPVA/CHAMPUS (Tricare) Follow-up Report, Repayment Plan Follow-up Report and the AR Productivity Report. The "B Cross-Reference and the address fields on the 1 node are used to build HL7 messages for the PFSS project. GENERAL DESCRIPTION: Integrated Billing has permission to access the following fields on the AR DEBTOR file (#340): STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32843552 SUBSCRIBING PACKAGE: INTEGRATED BILLING SUBSCRIBING PACKAGE: REGISTRATION NUMBER: 3348 IA #: 3348 DATE CREATED: MAR 28, 2001 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RCRJRCOT NAME: DBIA3348 ID: RCRJRCOT GENERAL DESCRIPTION: Integrated Billing has permission to make the following calls to AR in order to get information about Transactions (File #433): STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32843612 COMPONENT/ENTRY POINT: $$VALID(TRANDA) COMPONENT DESCRIPTION: This function is used to check if a specific transaction is valid or not. It will return 1 if the transaction is valid and 0 otherwise. IB uses this function in the AR Productivity Report. It passes a pointer to the AR TRANSACTION file (#433) to the function and the function returns if the transaction is valid or not. If the transaction is not valid it is not printed on the report. VARIABLES: TRANDA TYPE: Input VARIABLES DESCRIPTION: Pointer to the AR TRANSACTION file (#433). VARIABLES: $$VALID TYPE: Output VARIABLES DESCRIPTION: There are two possible values returned by this function: 0 - TRANDA is NOT a valid transaction 1 - TRANDA is a valid transaction SUBSCRIBING PACKAGE: INTEGRATED BILLING NUMBER: 3350 IA #: 3350 FILE NUMBER: 351.73 GLOBAL ROOT: IBE(351.73, DATE CREATED: MAR 28, 2001 CUSTODIAL PACKAGE: INTEGRATED BILLING USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3350 ID: IBE(351.73, GLOBAL REFERENCE: IBE(351.73,CLERK,1,ASSIGN) GLOBAL DESCRIPTION: The AR Workload To-Do List process (invoked by the AR Nightly process) will loop through all the assignments for one clerk and will generate the tasks for this clerk, based on the parameters of his assignments. GLOBAL REFERENCE: IBE(351.73,CLERK) GLOBAL DESCRIPTION: The AR Workload To-Do List process (invoked by the AR Nightly process) will loop through all the clerks on this file and will generate tasks for each clerk based on their assignments. GLOBAL REFERENCE: IBE(351.73,CLERK,1,ASSIGN,0) FIELD NUMBER: .02 FIELD NAME: BILL CATEGORY LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to identify which bill category should be considered in the generation of the To-Do List for the assignment. Only one category per assignment is allowed. FIELD NUMBER: .03 FIELD NAME: MINIMUM ACCOUNT BALANCE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to identify the minimum balance for a bill to be included in the To-Do List for the assignment. FIELD NUMBER: .05 FIELD NAME: EXCLUDE REGIONAL COUNSEL BILLS LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to identify if bills referred to Regional Counsel should be excluded from the To-Do List or not. GLOBAL REFERENCE: IBE(351.73,CLERK,1,ASSIGN,1) FIELD NUMBER: 1.01 FIELD NAME: DAYS SINCE LAST PAYMENT LOCATION: 1;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to decide if a bill should be included in the To-Do List or not. The bill will be included in the To-Do List only if number of days since the last payment transaction till the day the To-Do List runs, is not smaller than the number in this field. FIELD NUMBER: 1.02 FIELD NAME: FIRST PARTY-FIRST PATIENT NAME LOCATION: 1;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to identify the first name of the patient name range when generating the To-Do List for the assignment (First Party assignments only). FIELD NUMBER: 1.03 FIELD NAME: FIRST PARTY-LAST PATIENT NAME LOCATION: 1;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to identify the last name of the patient name range when generating the To-Do List for the assignment (First Party assignments only). FIELD NUMBER: 1.04 FIELD NAME: FIRST PARTY-FIRST SSN LOCATION: 1;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to identify the first number of last 4SSN of the patient last 4SSN range when generating the To-Do List for the assignment (First Party assignments only). FIELD NUMBER: 1.05 FIELD NAME: FIRST PARTY-LAST SSN LOCATION: 1;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to identify the last number of last 4SSN of the patient last 4SSN range when generating the To-Do List for the assignment (First Party assignments only). GLOBAL REFERENCE: IBE(351.73,CLERK,1,ASSIGN,2) FIELD NUMBER: 2.01 FIELD NAME: DAYS SINCE LAST TRANSACTION LOCATION: 2;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to decide if a bill should be included in the To-Do List or not. The bill will be included in the To-Do List only if number of days since the last transaction till the day the To-Do List runs, is not smaller than the number in this field. FIELD NUMBER: 2.02 FIELD NAME: FIRST INSURANCE CARRIER LOCATION: 2;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to identify the first Insurance carrier name of the range of Insurance carriers when generating the To-Do List for the assignment (Third Party assignments only). FIELD NUMBER: 2.03 FIELD NAME: LAST INSURANCE CARRIER LOCATION: 2;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to identify the first Insurance carrier name of the range of Insurance carriers when generating the To-Do List for the assignment (Third Party assignments only). FIELD NUMBER: 2.04 FIELD NAME: THIRD PARTY-FIRST PATIENT NAME LOCATION: 2;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to identify the first name of the patient name range when generating the To-Do List for the assignment (Third Party assignments only). FIELD NUMBER: 2.05 FIELD NAME: THIRD PARTY-LAST PATIENT NAME LOCATION: 2;5 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to identify the last name of the patient name range when generating the To-Do List for the assignment (Third Party assignments only). FIELD NUMBER: 2.06 FIELD NAME: THIRD PARTY-FIRST SSN LOCATION: 2;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to identify the first number of last 4SSN of the patient last 4SSN range when generating the To-Do List for the assignment (Third Party assignments only). FIELD NUMBER: 2.07 FIELD NAME: THIRD PARTY-LAST SSN LOCATION: 2;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to identify the last number of last 4SSN of the patient last 4SSN range when generating the To-Do List for the assignment (Third Party assignments only). FIELD NUMBER: 2.08 FIELD NAME: TYPE OF RECEIVABLE LOCATION: 2;8 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field is used to identify the type of receivable that should be included in the To-Do List. There are 5 possible types: 1 - Inpatient, 2 - Outpatient, 3 - Prosthetics, 4 - Pharmacy Refill and 5 - All Receivables. GENERAL DESCRIPTION: Accounts Receivable has permission to access the following fields on the IB DM WORKLOAD PARAMETERS file (#351.73): STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32843692 SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE NUMBER: 3351 IA #: 3351 DATE CREATED: APR 03, 2001 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUPUTU NAME: API CALL TO GET DOCUMENT TITLE IEN ID: TIUPUTU GENERAL DESCRIPTION: The Extrinsic Function $$WHATITLE^TIUPUTU will accept the freetext name of a TIU DOCUMENT DEFINITION of type TITLE, and return its Internal Entry Number in the TIU DOCUMENT DEFINITION File (#8925.1). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32750703 COMPONENT/ENTRY POINT: WHATITLE COMPONENT DESCRIPTION: Call the extrinsic function as follows, to determine the IEN of a given title: S TIUTTL=$$WHATITLE^TIUPUTU("ADVERSE REACTION/ALLERGY") I TIUTTL'>0 Q where the single input parameter for the extrinsic function is the name of the title to be identified. Note that the function will return the IEN of the specified title, or -1, if the text passed in the input parameter cannot be resolved as a valid TITLE. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: This is the freetext name of a valid TIU DOCUMENT DEFINITION of type title. SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING ISC: Salt Lake City SUBSCRIBING PACKAGE: SURGERY SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING PACKAGE: VBECS SUBSCRIBING DETAILS: ADDED 11/27/2007 DBA Comments: JSHARVEY 20061204/ ADDED MH AS A SUBSCRIBER AS PER HSU AND MCCLENAHAN. DATE/TIME EDITED: DEC 04, 2006@12:08 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HSU,YUILI WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: NOV 27, 2007@22:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MORTON,RANDY WITH CONCURRENCE OF: BUECHLER,MELANIE NUMBER: 3352 IA #: 3352 DATE CREATED: APR 05, 2001 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIKCUTL3 NAME: INPUT TEMPLATE RECOMPILATION ID: DIKCUTL3 GENERAL DESCRIPTION: Recompile compiled input templates that contain specific fields within a file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32760292 COMPONENT/ENTRY POINT: DIEZ COMPONENT DESCRIPTION: This entry point can be called from the Post-Install Routine of a KIDS build to recompile all compiled input templates that contain specific fields. (This is useful when the data dictionary definition of a field is changed and that field is sent in a KIDS build. KIDS does not automatically recompile the input templates that contain that field.) Example: If on file 12345 a new cross-reference is created, and that cross-reference contains fields 11 and 12, the following code will recompile all input templates that contain fields 11 and 12: N ZZFLD,ZZLIST F ZZFLD=11,12 S ZZLIST(12345,ZZFLD)="" D DIEZ^DIKCUTL3(12345,.ZZLIST) VARIABLES: TOPFILE_NO TYPE: Input VARIABLES DESCRIPTION: File number. (This is the top-level file number, even if the field being searched for in input templates is within a multiple.) VARIABLES: FIELD_LIST TYPE: Input VARIABLES DESCRIPTION: This input parameter is passed by reference, and is an array of file and field numbers, in the format: FIELD_LIST(file#,field)="" and/or FIELD_LIST(subfile#,subfield#)="" SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: KERNEL SUBSCRIBING PACKAGE: FEE BASIS DBA Comments: MC-4/3/14: Added Fee Basis as a subscriber to ICR #3352 at request of Scott Baumann and concurrence of Michael Ogi and Ron DiMiceli for patch FB*3.5*151 DATE/TIME EDITED: APR 03, 2014@07:49 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BAUMANN,SCOTT WITH CONCURRENCE OF: OGI,MICHAEL NUMBER: 3355 IA #: 3355 FILE NUMBER: 8930.6 GLOBAL ROOT: USR(8930.6, DATE CREATED: APR 13, 2001 CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: EXPORTING NEW ASU STATUS ENTRIES ID: USR(8930.6, GLOBAL REFERENCE: WHOLE FILE W/DD GLOBAL DESCRIPTION: This file contains the allowable states (or statuses) which may be applied to objects for which ASU Business Rules may be declared. GENERAL DESCRIPTION: Periodically, when new functions for document management are introduced by applications making use of ASU, it is necessary to introduce new definitions for the state (or status) of the object being acted upon, following the new processing event. One example is support for the retraction of a TIU Document that was entered in error for the wrong patient. To implement retraction, we needed to be able to identify the new status "retracted," and declare business rules specifying privileges for specific users to act on such documents. Such extensions necessitate adding new entries to the USR RECORD STATUS FILE (#8930.6), and distributing them with patches that implement the new functionality. ASU grants permission to TIU to issue such updates to the USR RECORD STATUS FILE (#8930.6), until otherwise agreed. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32788700 KEYWORDS: ASU STATUS UPDATE SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 3356 IA #: 3356 DATE CREATED: APR 13, 2001 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: Kernel Variable XQY0 GENERAL DESCRIPTION: Registration requests permission to reference the variable XQY0 to obtain the current menu option. DG FIELD MONITOR logic will be designed to run reguardless of the XQY0 being defined or set to "null". The DG FIELD MONITOR protocol provides an event point to monitor field editing in the DG* application files. Cross references and subscribers are added when applications need to monitor activity on a field. XQY0 contains the current menu option in the option name^menu text format when the cross references and event point are executed. This information is made available to the subscribing applications. Variable: XQY0 = First node(zero subscript) of the current option. Patient Name Standardization uses the XQY0 variable to identify the option name. It will populate the NOTES ABOUT NAME (#11) field in the NAME COMPONENTS (#20) file with the User's name, DUZ, and option name when an entry is added or updated in the Name Components file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32789075 KEYWORDS: FIELD KEYWORDS: MONITOR SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES NUMBER: 3357 IA #: 3357 GLOBAL ROOT: DD( DATE CREATED: APR 16, 2001 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3357 ID: DD( GENERAL DESCRIPTION: Inpatient Medications requests an agreement to allow the deletion of the 'V' level for the .01 field of the MAR LABELS file (#53.41). The level was apparently left over when the field was converted from a 'VARIABLE POINTER' data type to a 'SET OF CODES' data type. The 'V' level will be deleted in PSJ*5.0*57 with a direct KILL to the global. STATUS: Active MAIL MESSAGE: 32795373 KEYWORDS: DD( SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 3358 IA #: 3358 FILE NUMBER: 123 GLOBAL ROOT: GMR(123, DATE CREATED: APR 18, 2001 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: BRIEF CONSULTS HS COMP ID: GMR(123, CREATOR: THOMPSON,WILLIAM ANTHONY GLOBAL REFERENCE: GMR(123,'AD',DFN,INV,IEN GLOBAL DESCRIPTION: Used check to see if the patient (DFN) has a consult (IEN) and to list consults by inverse date (INV). This is a direct global read of an index. GLOBAL REFERENCE: GMR(123,D0,0 FIELD NUMBER: .01 FIELD NAME: FILE ENTRY DATE LOCATION: 0;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: Date the consultation request was entered into the file. Transparent to user. FIELD NUMBER: 1 FIELD NAME: TO SERVICE LOCATION: 0;5 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the service or specialty responsible for completion of the consult request. FIELD NUMBER: 2 FIELD NAME: FROM LOCATION: 0;6 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the location that sent the order to the receiving location. FIELD NUMBER: 3 FIELD NAME: DATE OF REQUEST LOCATION: 0;7 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the date and time the order was released. FIELD NUMBER: 8 FIELD NAME: CPRS STATUS LOCATION: 0;12 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the current CPRS status of the consult or request order. FIELD NUMBER: 9 FIELD NAME: LAST ACTION TAKEN LOCATION: 0;13 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the last action that updated the activity tracking audit trail. FIELD NUMBER: 17 FIELD NAME: EARLIEST DATE LOCATION: 0;24 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the earliest date that the provider would like the patient to be seen by the receiving service. GLOBAL REFERENCE: GMR(123,D1,40,D0,0 FIELD NUMBER: 1 FIELD NAME: ACTIVITY LOCATION: 0;2 ACCESS: Read w/Fileman FIELD DESCRIPTION: Consult activity. FIELD NUMBER: 2 FIELD NAME: DATE/TIME OF ACTUAL ACTIVITY LOCATION: 0;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: The date and time the activity was done. FIELD NUMBER: 8 FIELD NAME: PRINTED TO LOCATION: 0;8 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the printer where the CONSULT FORM 513 was printed. FIELD NUMBER: 9 FIELD NAME: RESULT LOCATION: 0;9 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the result of the activity. FIELD NUMBER: 10 FIELD NAME: ACTION METHOD LOCATION: 0;10 ACCESS: Read w/Fileman FIELD DESCRIPTION: The action method will identify how the user performed the action. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32804938 KEYWORDS: GMTS*2.8*46 KEYWORDS: GMTSCNB KEYWORDS: CONSULTS KEYWORDS: HEALTH KEYWORDS: SUMMARY SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: This IA supports the data extract routine used to produce the Consults Brief Health Summary Commponent. DBA Comments: reactivated 1/21/2009 DATE ACTIVATED: JAN 21, 2009 DATE/TIME EDITED: JAN 21, 2009@15:32 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: THOMPSON,WILLIAM WITH CONCURRENCE OF: SHUMWAY,GARY DATE/TIME EDITED: JAN 21, 2009@16:48 ACTION: APPROVED AT THE REQUEST OF: THOMPSON,WILLIAM WITH CONCURRENCE OF: SHUMWAY,GARY NUMBER: 3359 IA #: 3359 FILE NUMBER: 3.8 GLOBAL ROOT: XMB(3.8 DATE CREATED: APR 23, 2001 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3359 ID: XMB(3.8 GLOBAL REFERENCE: XMB(3.8,B, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Reference to the "B" cross reference for the .01 field. GLOBAL REFERENCE: XMB(3.8,AD, FIELD NUMBER: 11 FIELD NAME: MEMBER GROUPS LOCATION: 5;0 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Reference the "AD" cross reference for the MEMBER GROUPS to determine if a mail group is a member of another mail group. GENERAL DESCRIPTION: This DBIA allows Accounts Receivable to delete a mail group. The Accounts Receivable code will first look to see if the mail group exists in file 3.8 by looking at the B cross reference on the NAME (.01) field. If the mail group exists, the code will next loop the AD cross reference on the MEMBER GROUP NAME sub-field (.01) of the MEMBER GROUPS field (11) in file 3.8. If the mail group is a member of another mail group, the mail group will be removed from the MEMBER GROUPS field using DIK. Finally, the mail group will be removed using DIK. The following is an example of the code that deletes the IRS mail group: S RCMIRSDA=+$O(^XMB(3.8,"B","IRS",0)) I RCMIRSDA D . ; check to see if IRS mail group is a member of another . ; mail group. If so, delete it from the other mail group. . S RCDA(1)=0 F S RCDA(1)=$O(^XMB(3.8,"AD",RCMIRSDA,RCDA(1))) Q:'RCDA(1) D . . S RCDA=0 F S RCDA=$O(^XMB(3.8,"AD",RCMIRSDA,RCDA(1),RCDA)) Q:'RCDA D . . . S DA(1)=RCDA(1),DA=RCDA,DIK="^XMB(3.8,"_RCDA(1)_",5," . . . D ^DIK . ; . ; delete the mail group . S DA=RCMIRSDA,DIK="^XMB(3.8," . D ^DIK STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32818453 KEYWORDS: XMB(3.8 KEYWORDS: 3.8 SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Washington/Silver Spring SUBSCRIBING DETAILS: The IRS mail group will be removed in patch PRCA*4.5*169. EDITOR: MINARDI,CHRISTOPHER P EDITOR: BEUSCHEL,GARY NUMBER: 3362 IA #: 3362 FILE NUMBER: 131.7 GLOBAL ROOT: SRS( DATE CREATED: APR 27, 2001 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ACCESS TO FILE OPERATING ROOM FILE (131.7) ID: SRS( GLOBAL REFERENCE: SRS( FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: IFCAP developers are permitted to directly access the NAME field (.01) of the OPERATING ROOM file (131.7) so that this information can be accurately reported on the IFCAP PATIENT DISTRIBUTION COST REPORT. This will resolve a NOIS that was generated due to the fact that previously the report has used the pointer from the SURGERY file (130) field OPERATING ROOM (.02) to access the HOSPITAL LOCATION file (44) field NAME (.01). With this agreement in place IFCAP will be able to use the proper pointer to the HOSPITAL LOCATION file (44) field NAME (.01), namely the NAME field (.01) of the OPERATING ROOM file (131.7). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32834793 KEYWORDS: SURGERY KEYWORDS: OPERATING ROOM SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 3363 IA #: 3363 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWU DT REMOTE PROCEDURE: ORWU DT STATUS: Active SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING PACKAGE: FUNCTIONAL INDEPENDENCE SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR DBA Comments: 4/19/13-MM: Added PADP/NUPA as a subscriber to ICR #3363 for NUPA*1*1. Dan Petit provided concurrence on this request but with some reservations. These findings and concerns were forwarded to Kevin Dezorzi: Findings: This RPC takes an external representation of a Date/Time and attempts to convert it to the internal format of fileman. It further takes the assumption that if 00:00 is passed in as the time (not a valid time representation for Fileman) that the time needs to be converted to 00:00:01 (one second past midnight) so that fileman will be able to do the required conversion of the external representation to internal. Recommendation: Approval with Strong Reservation - This is an internal component/function of the UI designed strictly for the CPRS application. The CPRS GUI is fully responsible for making sure that the date portion of the date/time external representation meets a specification. Subscribing packages will have to follow convention of the CPRS GUI in order for this IA to function appropriately. This is another example of an IA for an IA that should be handled by calling the Fileman or Kernel package directly not via a surrogate. 3/7/14 - MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. Jamie indicated in her review that she philosophically agreed with Dan's review (see 4/19/13 DBA comments from PADP review) but it should be OK with allowing access to VIA. It is difficult to deny an application access when there are 5 other packages with access. 7/10/14-MC: PADP did not complete the class 3 to class 1 conversion process, but it is still installed at sites. Sites have the option to utilize the program, however it is no longer nationally supported. There will be no further patching of the package. PADP has been removed as a subscriber to this ICR. DATE/TIME EDITED: JUN 11, 2009@14:13 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: THOMPSON,TONY DATE/TIME EDITED: APR 19, 2013@16:09 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: DEZORZI,KEVIN WITH CONCURRENCE OF: PETIT,DAN DATE/TIME EDITED: MAR 07, 2014@10:10 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 3364 IA #: 3364 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWLRR CHART REMOTE PROCEDURE: ORWLRR CHART STATUS: Active SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE NUMBER: 3366 IA #: 3366 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWORR AGET REMOTE PROCEDURE: ORWORR AGET STATUS: Active SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING DETAILS: Requested to be added on May 16, 2007. SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING DETAILS: added 11/27/2007 SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 4/18/13-MM: Added PADP/NUPA as a subscriber to ICR #3366 for NUPA*1*1. 3/6/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. 7/10/14-MC: PADP did not complete the class 3 to class 1 conversion process, but it is still installed at sites. Sites have the option to utilize the program, however it is no longer nationally supported. There will be no further patching of the package. PADP has been removed as a subscriber to this ICR. 9/30/14-MC:Added VPS as a subscriber at the request of Carolyn Wheless and approved by Teresa Chung for VPS*1*4. VPS has a need to use AGET^ORWORR to retrieve an abbreviated patient order list. DATE/TIME EDITED: MAY 16, 2007@13:12 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: ACKERMAN,SHIRLEY WITH CONCURRENCE OF: VERTIGAN,RICHARD DATE/TIME EDITED: NOV 27, 2007@21:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: THOMPSON,WILLIAM WITH CONCURRENCE OF: BUECHLER,MELANIE DATE/TIME EDITED: APR 18, 2013@17:49 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: DEZORZI,KEVIN WITH CONCURRENCE OF: PETIT,DAN DATE/TIME EDITED: MAR 06, 2014@10:55 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 3367 IA #: 3367 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWORR GET4LST REMOTE PROCEDURE: ORWORR GET4LST STATUS: Active SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING DETAILS: Requested to be added May 16, 2007 SUBSCRIBING PACKAGE: VISTA INTEGRATION ADAPTOR SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) DBA Comments: 4/19/13-MM: Added PADP/NUPA as a subscriber to ICR #3367 for NUPA*1*1. 3/6/14-MM: Added VIA as a subscriber. VIAB*1*1 and OR*3*392 are patches associated with this project. OR*3*392 distributes the RPC with the App Proxy Allowed field set for VistALink. Jamie reviewed all of the OR and TIU ICR requests for VIA. She stated her understanding of one of the VIA project charges is exposing RPCs already in use by MDWS. She said in general terms, there are several RPCs that CPRS would not approve additional access to under other circumstances. However, since they are already in use by MDWS, at least the RPCs are now documented and the CPRS and TIU teams know any changes might affect other applications. 7/10/14-MC: PADP did not complete the class 3 to class 1 conversion process, but it is still installed at sites. Sites have the option to utilize the program, however it is no longer nationally supported. There will be no further patching of the package. PADP has been removed as a subscriber to this ICR. 9/30/14-MC: Added VPS as a subscriber at the request of Carolyn Wheless and approved by Teresa Chung for VPS*1*4. VPS has a need to use GET4LST^ORWORR to retrieve an order field for a patient's lists of orders. DATE/TIME EDITED: MAY 16, 2007@13:13 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: ACKERMAN,SHIRLEY WITH CONCURRENCE OF: VERTIGAN,RICHARD DATE/TIME EDITED: APR 19, 2013@11:48 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: DEZORZI,KEVIN WITH CONCURRENCE OF: PETIT,DAN DATE/TIME EDITED: MAR 06, 2014@10:57 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: COULTER,MYLES WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 3368 IA #: 3368 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWLRR MICRO REMOTE PROCEDURE: ORWLRR MICRO STATUS: Active SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE NUMBER: 3369 IA #: 3369 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWRP1 LISTNUTR REMOTE PROCEDURE: ORWRP1 LISTNUTR STATUS: Active SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE NUMBER: 3370 IA #: 3370 DATE CREATED: APR 30, 2001 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJ0050 NAME: DBIA3370 ID: PSJ0050 GENERAL DESCRIPTION: For the Pharmacy Ordering Enhancements (POE) project it is necessary to convert the orderable item in the PHARMACY PATIENT file (#55), IV sub-file (#55.01). The same orderable item is also stored in the BCMA MEDICATION LOG file (#53.79). Inpatient Medications is requesting a one-time integration agreement with Bar Code Medication Administration to allow updates to the BCMA MEDICATION LOG file (#53.79) using FileMan. The updates would occur at the time of the POE installation. STATUS: Active MAIL MESSAGE: 32843873 KEYWORDS: PSJ0050 COMPONENT/ENTRY POINT: EN VARIABLES: PSJDFN TYPE: Input VARIABLES DESCRIPTION: Patient Internal File Number (required) VARIABLES: PSJORDER TYPE: Input VARIABLES DESCRIPTION: Order number to be converted (required) VARIABLES: PSJCURR TYPE: Input VARIABLES DESCRIPTION: Internal entry number for the current orderable item VARIABLES: PSJNEW TYPE: Input VARIABLES DESCRIPTION: Internal entry number for the new orderable item SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham NUMBER: 3371 IA #: 3371 DATE CREATED: MAY 04, 2001 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWU HASKEY GENERAL DESCRIPTION: Returns 1 if a user holds a security key, otherwise 0. STATUS: Active MAIL MESSAGE: 34160750 SUBSCRIBING PACKAGE: EVENT CAPTURE ISC: Albany SUBSCRIBING PACKAGE: CARE MANAGEMENT NUMBER: 3372 IA #: 3372 FILE NUMBER: 8927.1 GLOBAL ROOT: TIU(8927.1) DATE CREATED: MAY 09, 2001 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TIU TEMPLATE FIELD ID: TIU(8927.1) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32874781 KEYWORDS: TIU TEMPLATE FIELD SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING DETAILS: In order for the Clinical Reminders Exchange Utility to transport reminder dialogs it needs to also transport TIU Template Fields. Therefore Clinical Reminders requires read and write access via FileMan to all fields of the TIU Template Fields file. NUMBER: 3373 IA #: 3373 DATE CREATED: MAY 10, 2001 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSSUTLA1 NAME: DBIA3373 ID: PSSUTLA1 GENERAL DESCRIPTION: Pharmacy Data Management returns a DEA Special Handling code for a Pharmacy Orderable Item, based on the Dispense Drugs that are matched to that Pharmacy Orderable Item. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33669424 COMPONENT/ENTRY POINT: OIDEA(PSSXOI,PSSXOIP) COMPONENT DESCRIPTION: This entry point will return a DEA Special Handling code for a Pharmacy Orderable Item. VARIABLES: PSSXOI TYPE: Input VARIABLES DESCRIPTION: This variable is the internal entry number from the Pharmacy Orderable Item (#50.7) file. VARIABLES: PSSXOIP TYPE: Input VARIABLES DESCRIPTION: This variable can be one of three values. "O" indicates that this call is being made for an Outpatient Pharmacy order. Either an "I" or a "U" indicates that this call is being made for an Inpatient Medications order. VARIABLES: $$OIDEA TYPE: Output VARIABLES DESCRIPTION: This output variable indicates the DEA Special Handling code at the Pharmacy Orderable Item level, based on dispense drugs matched to the Item. This variable can be one of four values, a "1", a "2", a "0", or null. If a "1" is returned, that indicates that there is at least one active dispense drug matched to that Pharmacy Orderable Item for the specified package, that has a DEA Special Handling Code that contains a "1", or contains a "2". This means that a wet signature is required. If a "2" is returned, that indicates that the first condition wasn't met, and that there is at least one active dispense drug matched to that Pharmacy Orderable Item for the specified package, that has a DEA Special Handling Code that contains a "3", or contains a "4", or contains a "5". This means a wet signature is not required, but it does indicate a Controlled Substance. A "0" is returned if neither of the first two conditions are met, but there are active drugs matched to the Pharmacy orderable Item for the specified package. If there are no active drugs for the specified package matched to the Pharmacy Orderable Item, then a null is returned. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3374 IA #: 3374 DATE CREATED: MAY 10, 2001 CUSTODIAL PACKAGE: ACCOUNTS RECEIVABLE USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RCBEIB NAME: DBIA3374 ID: RCBEIB CREATOR: FIAMENGO,GRACE GENERAL DESCRIPTION: Integrated Billing has permission to make the following call to AR to determine if AR has cancelled a specific receivable associated with a bill. The IB option [IB CANCEL BILL] allows a clerk to cancel a bill which then invokes the call $$CANCEL^RCBEIB. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32879681 COMPONENT/ENTRY POINT: $$CANCEL(PRCASV(ARREC),PRCASV(DATE),PRCASV(BY),PRCASV(AMT ),PRCASV(COMMENT),PRCASV(CRD)) COMPONENT DESCRIPTION: This function returns information on a specific receivable associated with a bill. Please note this package limits the input of variables using string subscripts i.e. the variable PRCASV("ARREC") cannot be entered because it contains "". Also this package limits the display variables to 10 characters then truncates. The correct call from IB to AR is S X=$$CANCEL^RCBEIB($G(PRCASV("ARREC")),$G(PRCASV("DATE")), $G(PRCASV("BY")),$G(PRCASV("AMT")),$G(PRCASV("COMMENT")),$G(PRCASV("ARCRD"))). VARIABLES: ARREC TYPE: Input VARIABLES DESCRIPTION: Ien of the BILL/receivable in ACCOUNTS RECEIVABLE file (#430) that needs to be cancelled. VARIABLES: DATE TYPE: Input VARIABLES DESCRIPTION: This is the date the bill was cancelled. This parameter is optional. VARIABLES: BY TYPE: Input VARIABLES DESCRIPTION: This is the DUZ of the person cancelling the bill. This parameter is optional. VARIABLES: AMT TYPE: Input VARIABLES DESCRIPTION: This is the "$" amount of the bill being cancelled. This parameter is optional. VARIABLES: COMMENT TYPE: Input VARIABLES DESCRIPTION: This is the reason the clerk cancelled the bill. This parameter is optional. VARIABLES: X TYPE: Output VARIABLES DESCRIPTION: The value returned by this function is a string that contains two fields seperated by "^" (up-arrow) and addresses the following 2 scenarios: Receivable has been Cancelled returns a 1 in the first piece and the second piece is null. < i.e. > 1 Receivable has not been Cancelled returns a 0 in the first piece and if available returns the reason why in second piece. "0^reason why goes here" VARIABLES: CRD TYPE: Input VARIABLES DESCRIPTION: This is the IB Correction flag. It is used to notify AR and FMS that the user is in the Correct Rejected/Denied Claim Option. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING DETAILS: DATE ACTIVATED: MAR 21, 2011 DATE/TIME EDITED: MAR 21, 2011@12:15 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: FIAMENGO,GRACE WITH CONCURRENCE OF: MINARDI,CHRIS DATE/TIME EDITED: MAR 21, 2011@13:29 ACTION: APPROVED AT THE REQUEST OF: FIAMENGO,GRACE WITH CONCURRENCE OF: WINTERTON,STEVE NUMBER: 3375 IA #: 3375 DATE CREATED: MAY 14, 2001 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUSRVP NAME: CREATE/DELETE TIU DOCUMENT RECORDS ID: TIUSRVP GENERAL DESCRIPTION: Clinical Procedures will be using the MAKE^TIUSRVP API to create TIU Document records and the DELETE^TIUSRVP API to delete TIU DOCUMENT records. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33545837 COMPONENT/ENTRY POINT: MAKE(SUCCESS,DFN,TITLE,VDT,VLOC,VSIT,VSTR,TIUX,SUPPRESS) VARIABLES: SUCCESS TYPE: Both VARIABLES DESCRIPTION: SUCCESS returns TIU DOCUMENT # (Pointer to TIU Document file #8925). (Passed By Reference) VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN (Patient file #2). VARIABLES: TITLE TYPE: Input VARIABLES DESCRIPTION: Pointer to TIU DOCUMENT DEFINITION file (#8925.1). VARIABLES: VDT TYPE: Input VARIABLES DESCRIPTION: Date(/Time) of Visit. VARIABLES: VLOC TYPE: Input VARIABLES DESCRIPTION: Visit Location (pointer to HOSPITAL LOCATION file #44). VARIABLES: VSIT TYPE: Input VARIABLES DESCRIPTION: Pointer to VISIT file (#9000010). VARIABLES: TIUX TYPE: Input VARIABLES DESCRIPTION: Array containing identifying fields of the document. VARIABLES: VSTR TYPE: Input VARIABLES DESCRIPTION: This parameter identifies the visit location, date/time, and Service Category (Hospitalization, Ambulatory, Telecommunications, or Event (HISTORICAL)) in the form of a semi-colon delimited string (e.g., "469;2970616.1415;A"). VARIABLES: SUPPRESS TYPE: Used VARIABLES DESCRIPTION: BOOLEAN flag indicating whether or not to suppress execution of the COMMIT ACTION for the document in question. This gives the calling application control over the circumstances in which the COMMIT CODE should be executed. COMPONENT/ENTRY POINT: DELETE(ERR,TIUDA,TIURSN) VARIABLES: ERR TYPE: Both VARIABLES DESCRIPTION: Returns error message with ERR=1^Explanation text if the user is NOT authorized to delete the named record. (Passed By Reference) VARIABLES: TIUDA TYPE: Input VARIABLES DESCRIPTION: Record number of TIU Document to be deleted. VARIABLES: TIURSN TYPE: Used VARIABLES DESCRIPTION: This optional parameter specifies the reason for deletion (i.e., Privacy Act, or Administrative Action). SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Hines SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING PACKAGE: INSURANCE CAPTURE BUFFER SUBSCRIBING DETAILS: ADDED JUNE 2009 DBA Comments: JSHARVEY 20061204/ ADDED MH AS A SUBSCRIBER AS PER HSU AND RUSSELL JSHARVEY 20061204/ CHANGED DBIA NAME FROM DBIA3375 JSHARVEY 20061204/ REACTIVATED IA AFTED EDITS. DATE/TIME EDITED: DEC 04, 2006@12:08 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HSU,YUILI WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: JUN 11, 2009@11:59 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: JUN 11, 2009@12:00 ACTION: USAGE CHOICE CHANGED AT THE REQUEST OF: CLARK,KAREN WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 3376 IA #: 3376 FILE NUMBER: 8925 GLOBAL ROOT: TIU(8925,DA,0) DATE CREATED: MAY 14, 2001 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3376 ID: TIU(8925,DA,0) GLOBAL REFERENCE: TIU(8925,DA,0) FIELD NUMBER: .01 FIELD NAME: DOCUMENT TYPE LOCATION: 0;1 ACCESS: Pointed to GENERAL DESCRIPTION: This IA will document the fact that in the CP TRANSACTION file (#702) has a field called TIU NOTE (Field #.06) which points to the TIU DOCUMENT file (#8925). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33545876 SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Hines SUBSCRIBING PACKAGE: SURGERY NUMBER: 3377 IA #: 3377 FILE NUMBER: 8925.1 GLOBAL ROOT: TIU(8925.1,DA,0) DATE CREATED: MAY 14, 2001 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3377 ID: TIU(8925.1,DA,0) GLOBAL REFERENCE: TIU(8925.1,DA,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to GENERAL DESCRIPTION: This IA is to document the fact that the CP DEFINITION file (#702.01) has a field called DEFAULT TIU NOTE (Field #.04) which points to the TIU DOCUMENT DEFINITION file (#8925.1). This IA also documents the fact that field (#.05), USE TIU NOTE TITLE, of the Sub-file (#703.91), MEDICINE FILE PARAMETERS, in the CP CONVERSION file (#703.9) points to the TIU DOCUMENT DEFINITION file (#8925.1). VIEWER: ACKERMAN,NIEN-CHIN STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33545879 SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Hines EDITOR: MCCLENAHAN,MARGARET NUMBER: 3378 IA #: 3378 DATE CREATED: APR 07, 2005 CUSTODIAL PACKAGE: CLINICAL PROCEDURES CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MDAPI NAME: DBIA3378 ID: MDAPI GENERAL DESCRIPTION: This IA documents calls to MDAPI. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33596905 COMPONENT/ENTRY POINT: $$EXTDATA(MDPROC) COMPONENT DESCRIPTION: Entry Point to check if a medical device is associated with the CP Definition. VARIABLES: MDPROC TYPE: Input VARIABLES DESCRIPTION: The CP Definition IEN from CP DEFINITION file (702.01) VARIABLES: $$EXTDATA TYPE: Output VARIABLES DESCRIPTION: This is an extrinsic function and it returns: 1/0 for Yes/No. COMPONENT/ENTRY POINT: $$TIUCOMP(MDNOTE) COMPONENT DESCRIPTION: Entry Point to complete a CP transaction. VARIABLES: MDNOTE TYPE: Input VARIABLES DESCRIPTION: The TIU Document IEN from TIU DOCUMENT file (#8925). VARIABLES: $$TIUCOMP TYPE: Output VARIABLES DESCRIPTION: This is an Extrinsic Function and it returns: 0/1 for fail/success of transaction completion. COMPONENT/ENTRY POINT: $$TIUDEL(MDNOTE) COMPONENT DESCRIPTION: Entry Point to clean up the CP Transaction file entry of the TIU Note that was deleted. VARIABLES: MDNOTE TYPE: Input VARIABLES DESCRIPTION: The TIU Document IEN from TIU DOCUMENT file (#8925). VARIABLES: $$TIUDEL TYPE: Output VARIABLES DESCRIPTION: This is an extrinsic Function and it returns: 0/1 for fail/success of the TIU Note deletion update. COMPONENT/ENTRY POINT: ISTAT(MDARR) COMPONENT DESCRIPTION: Entry Point to update Clinical Procedures of the result of the image(s) that was copied to the Imaging Server. VARIABLES: MDARR TYPE: Input VARIABLES DESCRIPTION: An array of the following: MDARR(0)="0^error message" or "1^success message" MDARR(1)=TrackID (CP;Transaction IEN) MDARR(2)=Image(s) Queue Number MDARR(3..N)=Warnings, if error(s) exist. COMPONENT/ENTRY POINT: ITIU(RESULTS,DFN,CONSULT,VSTRING) COMPONENT DESCRIPTION: This entry point enables VistA Imaging to retrieve/create a TIU note for a consult for attaching images to. VARIABLES: RESULTS TYPE: Output VARIABLES DESCRIPTION: RESULTS(0) will equal one of the following (Required) ; IEN of the TIU note if successful ; or on failure one of the following status messages ; -1^No patient DFN ; -1^No Consult IEN ; -1^No VString ; -1^Error in CP transaction ; -1^Unable to create CP transaction ; -1^Unable to create the TIU document ; -1^No such consult for this patient. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN. (Required) VARIABLES: CONSULT TYPE: Input VARIABLES DESCRIPTION: Consult IEN. (Required) VARIABLES: VSTRING TYPE: Input VARIABLES DESCRIPTION: VString data for TIU Note. (Required) COMPONENT/ENTRY POINT: $$TIUREAS(MDFN,MDOLDC,MDANOTE,MDNDFN,MDNEWC,MDNEWV,MDNTIU ) COMPONENT DESCRIPTION: This entry point enables TIU to notify CP that a TIU note was reassigned and CP needs to clean up and update the TIU note re-assignment. VARIABLES: MDFN TYPE: Input VARIABLES DESCRIPTION: Patient DFN in Patient File (#2). VARIABLES: MDOLDC TYPE: Input VARIABLES DESCRIPTION: The old consult number that the TIU note is being re-assigned from. VARIABLES: MDANOTE TYPE: Input VARIABLES DESCRIPTION: The TIU Note internal Entry Number that is being re-assigned. VARIABLES: MDNDFN TYPE: Input VARIABLES DESCRIPTION: The patient DFN who will be re-assigned to the TIU document. VARIABLES: MDNEWC TYPE: Input VARIABLES DESCRIPTION: The new consult number that will be re-assigned to the TIU document. VARIABLES: MDNEWV TYPE: Input VARIABLES DESCRIPTION: The new visit for the TIU document assignment. VARIABLES: MDNTIU TYPE: Input VARIABLES DESCRIPTION: The new re-assigned TIU document internal entry number. VARIABLES: $$TIUREAS TYPE: Output VARIABLES DESCRIPTION: This is an extrinsic function and it returns: 1 for Success or 0^Error Message. SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: Consult will be calling the $$EXTDATA(MDPROC) entry point to determine whether the procedure requires external data. SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING DETAILS: TIU will be calling the $$TIUCOMP(MDNOTE) entry point to complete the CP transaction, the $$TIUDEL(MDNOTE) entry points to update Clinical Procedures that a TIU document is deleted, and $$TIUREAS(MDFN,MDOLDC, MDANOTE,MDNDFN,MDNEWC,MDNEWV,MDNTIU) entry point to clean up and update a TIU document re-assignment. SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging will be calling the ISTAT(MDARR) entry point to update Clinical Procedures with the result of the image(s) being copied to the Imaging Server. NUMBER: 3380 IA #: 3380 DATE CREATED: MAY 21, 2001 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: PSB VALIDATE ESIG REMOTE PROCEDURE: PSB VALIDATE ESIG ORIGINAL NUMBER: 3380 GENERAL DESCRIPTION: PSB VALIDATE ESIG is used to validate the data in PSBESIG against the user currently signed on (DUZ). STATUS: Active DURATION: Next Version MAIL MESSAGE: 32916315 GOOD ONLY FOR VERSION: Version 1.0 KEYWORDS: PSB KEYWORDS: BCMA NUMBER: 3382 IA #: 3382 DATE CREATED: MAY 21, 2001 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: PSB FMDATE REMOTE PROCEDURE: PSB FMDATE ORIGINAL NUMBER: 3380 GENERAL DESCRIPTION: Used to validate Fileman dates. STATUS: Active DURATION: Next Version MAIL MESSAGE: 32916315 GOOD ONLY FOR VERSION: Version 1.0 KEYWORDS: PSB KEYWORDS: BCMA NUMBER: 3383 IA #: 3383 DATE CREATED: MAY 21, 2001 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: PSB SCANPT REMOTE PROCEDURE: PSB SCANPT ORIGINAL NUMBER: 3380 GENERAL DESCRIPTION: This RPC is used to validate the data scanned in at the scan patient wristband prompt of the mnOpenPatient component. The value passed in is either the full SSN scanned in from the patient wristband -or- the 1U4N syntax of the patient lookup. In either case the call must return only one patient from the lookup. If the 1U4N syntax is used and multiple patients are found the call returns an error. If only one patient is found the RESULTS array is loaded with the patient data and passed back to the client for verification. STATUS: Active DURATION: Next Version MAIL MESSAGE: 32916315 GOOD ONLY FOR VERSION: Version 1.0 KEYWORDS: PSB KEYWORDS: BCMA NUMBER: 3384 IA #: 3384 DATE CREATED: MAY 21, 2001 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: PSB USERLOAD REMOTE PROCEDURE: PSB USERLOAD ORIGINAL NUMBER: 3380 GENERAL DESCRIPTION: This RPC is called at application startup to populate the BCMA_User object with the users defaults. No paramters are passed, the current DUZ is assumed. STATUS: Active DURATION: Next Version MAIL MESSAGE: 32916315 GOOD ONLY FOR VERSION: Version 1.0 KEYWORDS: PSB KEYWORDS: BCMA NUMBER: 3385 IA #: 3385 DATE CREATED: MAY 21, 2001 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: PSB DISPLAY ORDER REMOTE PROCEDURE: PSB DISPLAY ORDER ORIGINAL NUMBER: 3380 GENERAL DESCRIPTION: Returns a display for a selected order when double clicked on the VDL. STATUS: Active DURATION: Next Version MAIL MESSAGE: 32916315 GOOD ONLY FOR VERSION: Version 1.0 KEYWORDS: PSB KEYWORDS: BCMA NUMBER: 3386 IA #: 3386 DATE CREATED: MAY 21, 2001 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: PSB GETPRNS REMOTE PROCEDURE: PSB GETPRNS ORIGINAL NUMBER: 3380 GENERAL DESCRIPTION: Returns all administrations of a PRN order that have NOT had the PRN Effectiveness documented for the last 30 days. STATUS: Active DURATION: Next Version MAIL MESSAGE: 32916315 GOOD ONLY FOR VERSION: Version 1.0 KEYWORDS: PSB KEYWORDS: BCMA NUMBER: 3387 IA #: 3387 DATE CREATED: MAY 21, 2001 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: PSB GETORDERLIST REMOTE PROCEDURE: PSB GETORDERLIST ORIGINAL NUMBER: 3380 GENERAL DESCRIPTION: Returns the current order set for today to display on the client VDL. STATUS: Active MAIL MESSAGE: 32916315 GOOD ONLY FOR VERSION: 1.0 KEYWORDS: PSB KEYWORDS: BCMA NUMBER: 3388 IA #: 3388 DATE CREATED: MAY 21, 2001 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: PSB REACTIONS REMOTE PROCEDURE: PSB REACTIONS ORIGINAL NUMBER: 3380 GENERAL DESCRIPTION: Returns detailed listing of reactions when Reactions Button is clicked. STATUS: Active DURATION: Next Version MAIL MESSAGE: 32916315 GOOD ONLY FOR VERSION: Version 1.0 KEYWORDS: PSB KEYWORDS: BCMA NUMBER: 3389 IA #: 3389 DATE CREATED: MAY 21, 2001 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: PSB SERVER CLOCK VARIANCE REMOTE PROCEDURE: PSB SERVER CLOCK VARIANCE ORIGINAL NUMBER: 3380 GENERAL DESCRIPTION: Returns the variance from the server to the client in minutes. STATUS: Active DURATION: Next Version MAIL MESSAGE: 32916315 GOOD ONLY FOR VERSION: Version 1.0 KEYWORDS: PSB KEYWORDS: BCMA NUMBER: 3390 IA #: 3390 DATE CREATED: MAY 22, 2001 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: PSB VALIDATE ORDER REMOTE PROCEDURE: PSB VALIDATE ORDER ORIGINAL NUMBER: 3390 GENERAL DESCRIPTION: Final check of order against an actual administration date/time used immediately after scanned med has been validated to be a good unadministered order and by the PSBODL (Due List) output. STATUS: Active DURATION: Next Version MAIL MESSAGE: 32916315 GOOD ONLY FOR VERSION: Version 1.0 KEYWORDS: PSB KEYWORDS: BCMA NUMBER: 3391 IA #: 3391 DATE CREATED: MAY 22, 2001 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: PSB PARAMETER REMOTE PROCEDURE: PSB PARAMETER ORIGINAL NUMBER: 3390 GENERAL DESCRIPTION: Return a parameter list. STATUS: Active DURATION: Next Version MAIL MESSAGE: 32916315 GOOD ONLY FOR VERSION: Version 1.0 KEYWORDS: PSB KEYWORDS: BCMA NUMBER: 3395 IA #: 3395 DATE CREATED: MAY 22, 2001 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: PSB TRANSACTION REMOTE PROCEDURE: PSB TRANSACTION ORIGINAL NUMBER: 3390 GENERAL DESCRIPTION: This is the filing RPC for all data returning from the client regarding the medication log. Filing is handled by business rules on the server and this RPC will return either '1^Data Filed' or '-1^reason for not filing data' to the client. Business rules are conducted via the [0] node data. If a '+1^MEDPASS' is encountered it is a complete new med pass and is validated as such. Transaction type MEDPASS is the only type that requires a +1 in the first piece of the header, all other transactions MUST supply a valid medication log entry in the IENS. STATUS: Active DURATION: Next Version MAIL MESSAGE: 32916315 GOOD ONLY FOR VERSION: Version 1.0 KEYWORDS: PSB KEYWORDS: BCMA NUMBER: 3396 IA #: 3396 DATE CREATED: MAY 22, 2001 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: PSB SUBMIT MISSING DOSE REMOTE PROCEDURE: PSB SUBMIT MISSING DOSE ORIGINAL NUMBER: 3390 GENERAL DESCRIPTION: Allows the client to submit a missing dose interactively. STATUS: Active DURATION: Next Version MAIL MESSAGE: 32916315 GOOD ONLY FOR VERSION: Version 1.0 KEYWORDS: PSB KEYWORDS: BCMA NUMBER: 3397 IA #: 3397 GLOBAL ROOT: TMP('OR',$J,'MCAR' DATE CREATED: MAY 29, 2001 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Medicine Report Support ID: TMP('OR',$J,'MCAR' GLOBAL REFERENCE: TMP('OR',$J,'MCAR' GLOBAL DESCRIPTION: Global containing a list of procedures for display in OE/RR. Located at ^TMP("OR",$J,"MCAR", This temporary global is sorted by either inverse date or Procedure Name, based on input parameters. Subscripts S1 and S2 hold the sort values. The sorted version of the TMP global is used for selection of procedures. The second version is used as input to produce the report. $P(^TMP("OR",$J,"MCAR",S1,S2),U,1)=Gross Evaluation ...),U,2)=Pointer to Procedure ...),U,3)=Print Routine (Field #5 from file 697.2) ...),U,4)=Print Line (Field #6 from file 697.2) ...),U,5)=Print Name (Field #7 from file 697.2) ...),U,10)=Summary Title ...),U,11)=Procedure Name ...),U,12)=Print Name_"/"_Procedure Name $P(^TMP("OR",$J,"MCAR","OT",L),U,1)=Print Name ...),U,2)=Pointer to Procedure ...),U,3)=Print Routine ...),U,4)=Print Line ...),U,5)=Print Name ...),U,6)=Date/time of procedure ...),U,7)=Gross Evaluation ...),U,10)=Summary Title ...),U,11)=Inverse date or Procedure (depends on sort) ...),U,12)=Procedure or Inverse date (depends on sort)^ GENERAL DESCRIPTION: This DBIA documents the setting of data into a ^TMP global that is used by CPRS to get a list of patient procedures for display on the CPRS Reports Tab. See DBIA #2757 for related information on API's used. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32946841 KEYWORDS: MCARPS2 SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Hines NUMBER: 3399 IA #: 3399 DATE CREATED: MAY 30, 2001 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SCUTBK3 NAME: ROUTINE SCUTBK3 ID: SCUTBK3 GENERAL DESCRIPTION: In support of hte Smart Card initiative the Registration Package needs the use of Scheduling APIs contained in this routine. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32951468 COMPONENT/ENTRY POINT: VERPAT COMPONENT DESCRIPTION: Entry point for RPC to check client/server pair VARIABLES: SCPATCH TYPE: Input VARIABLES DESCRIPTION: Server patch^Client version VARIABLES: SCRESULT TYPE: Output VARIABLES DESCRIPTION: 0 - Cannot continue 1 - Continue n - RPC Time Limit SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 3400 IA #: 3400 FILE NUMBER: 404.45 GLOBAL ROOT: SCTM(404.45 DATE CREATED: MAY 30, 2001 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: FILE 404.45 ID: SCTM(404.45 GLOBAL REFERENCE: SCTM(404.45 FIELD NUMBER: .01 FIELD NAME: SERVER PATCH NUMBER LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Field holds the patch number of the server software. FIELD NUMBER: .02 FIELD NAME: ASSOCIATED CLIENT LOCATION: 0;2 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Field holds the client version allowed for this server patch number. FIELD NUMBER: .03 FIELD NAME: EFFECTIVE DATE LOCATION: 0;3 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Date this server patch became active. FIELD NUMBER: .04 FIELD NAME: ACTIVE SERVER VERSION LOCATION: 0;4 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: A yes/no field showing whether or not htis server version is active. GENERAL DESCRIPTION: In support of the Smart Card initiative the Registration package needs to use file 404.45 - PCMM SERVER PATCH file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32951472 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING DETAILS: This agreement will allow the Registration package to keep track of client/server pairs at the local site, and server version on the remote site for the Network Data Retrieval functionality of the Smart Card initiative. NUMBER: 3401 IA #: 3401 FILE NUMBER: 404.46 GLOBAL ROOT: SCTM(404.46 DATE CREATED: MAY 30, 2001 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: FILE 404.46 ID: SCTM(404.46 GLOBAL REFERENCE: SCTM(404.46 FIELD NUMBER: .01 FIELD NAME: CLIENT VERSION NUMBER LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Field holds a client version number. FIELD NUMBER: .02 FIELD NAME: CLIENT VERSION ENABLED LOCATION: 0;2 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Yes/No field showing whether or not this client version is active. FIELD NUMBER: .03 FIELD NAME: EFFECTIVE DATE LOCATION: 0;3 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Date this version became active. FIELD NUMBER: .04 FIELD NAME: ASSOCIATED RPC VERSION LOCATION: 0;4 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Patch number for the appropriate server version. GENERAL DESCRIPTION: In support of the Smart Card initiative the Registration package needs to use file 404.46 - PCMM CLIENT PATCH file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32951474 SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING DETAILS: This agreement will allow the Registration package to keep track ofclient/server pairs at the local site, and server version on the remotesite for the Network Data Retrieval functionality of the Smart Cardinitiative. NUMBER: 3402 IA #: 3402 DATE CREATED: MAY 15, 2003 CUSTODIAL PACKAGE: REGISTRATION USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DG SENSITIVE RECORD ACCESS REMOTE PROCEDURE: DG SENSITIVE RECORD ACCESS GENERAL DESCRIPTION: This Remote Procedure Call (RPC) will: - Verify user is not accessing his/her own Patient file record if the Restrict Patient Record Access (#1201) field in the MAS parameters (#43) file is set to yes and the user does not hold the DG RECORD ACCESS security key. If parameter set to yes and user is not a key holder , a social security number must be defined in the New Person file for the user to access any Patient file record. - Determine if user accessing a sensitive record or an employee's record. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 35801634 NUMBER: 3403 IA #: 3403 DATE CREATED: MAY 15, 2003 CUSTODIAL PACKAGE: REGISTRATION USAGE: Supported TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: DG SENSITIVE RECORD BULLETIN REMOTE PROCEDURE: DG SENSITIVE RECORD BULLETIN GENERAL DESCRIPTION: This Remote Procedure Call (RPC) will add an entry to the DG SECURITY LOG (#38.1) file and/or generate the sensitive record access bulletin depending on the value in ACTION input parameter. If ACTION parameter not defined, defaults to update DG Security Log file and generate Sensitive Record Access mail message. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 35801664 NUMBER: 3404 IA #: 3404 FILE NUMBER: .11 GLOBAL ROOT: DD( DATE CREATED: JUN 01, 2001 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: UPDATE NEW-STYLE X-REF ONLY ID: DD( GLOBAL REFERENCE: DD('IX' GENERAL DESCRIPTION: Registration is requesting to export New Style-Cross References to registration files by setting the ^DD("IX" global nodes of the INDEX file using UPDATE^DIE and WP^DIE. This methodology allows us to create New Style cross-references without exporting the field itself. Listed below is an example how the Filer Array would be populated. ;Create filer array S DGFDA(.11,"+1,",.01)= ;FILE NUMBER S DGFDA(.11,"+1,",.02)= ;X-REF NAME S DGFDA(.11,"+1,",.11)="This X-ref invokes DG FIELD MONITOR " ;SHORT DESCRIPTION S DGFDA(.11,"+1,",.2)= ;TYPE S DGFDA(.11,"+1,",.4)= ;EXECUTION S DGFDA(.11,"+1,",.41)= ;ACTIVITY S DGFDA(.11,"+1,",.5)= ;ROOT TYPE S DGFDA(.11,"+1,",.51)= ;ROOT FILE NUMBER S DGFDA(.11,"+1,",.42)= ;USE S DGFDA(.11,"+1,",1.1)= ;SET LOGIC S DGFDA(.11,"+1,",2.1)= ;KILL LOGIC ;CROSS REFERENCE VALUES S DGFDA(.114,"+2,+1,",.01)= ;ORDER NUMBER S DGFDA(.114,"+2,+1,",1)= ;TYPE OF VALUE S DGFDA(.114,"+2,+1,",2)= ;FILE NUMBER S DGFDA(.114,"+2,+1,",3)= ;FIELD NUMBER S DGFDA(.114,"+2,+1,",7)= ;COLLATION ;DESCRIPTION S DGWP(1)="This cross reference activates the DG FIELD MONITOR event point." S DGWP(2)="Applications that wish to monitor edit activity related to this field may" S DGWP(3)="subscribe to that event point and take action as indicated by the changes" S DGWP(4)="that occur. Refer to the DG FIELD MONITOR protocol for a description of" S DGWP(5)="the information available at the time of the event." ;File INDEX record D UPDATE^DIE("","DGFDA","DGIEN","DGERR") I $D(DIERR) D Q ;CHECK FOR ERROR .N DGI S DGI="" .F S DGI=$O(DGERR("DIERR",1,"TEXT",DGI)) Q:DGI="" D ..D MES^XPDUTL(DGERR("DIERR",1,"TEXT",DGI)) ;DISPLAY ERROR ..Q .Q ;File DESCRIPTION field D WP^DIE(.11,DGIEN(1)_",",.1,"","DGWP") ;FILE DESCRIPTION Q STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32961725 KEYWORDS: UPDATE DIE SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany EDITOR: BENNETT,FLETCHER NUMBER: 3405 IA #: 3405 DATE CREATED: JUN 01, 2001 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DICR NAME: TRIG DICR ID: DICR GENERAL DESCRIPTION: Registration is requesting to use TRIG^DICR for the purposes of updating the trigger logic when exporting New Style-Cross References in conjunction with DBIA 3404 to registration files. Usage of this routine is outlined below. TRIG^DICR(.fieldList,.outputList) Where, fieldList = (Input) Array of file/fields that may be triggered. The trigger logic of fields that trigger the fields in this list is modified, as necessary. Format: fieldList(file#,field#)="" outputList = (Output) This array is returned with the list of fields whose trigger logic was modified. Format: outputList(file#,field#)="" STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32962009 KEYWORDS: TRIG DICR COMPONENT/ENTRY POINT: TRIG VARIABLES: fieldlist TYPE: Input VARIABLES: outputlist TYPE: Output SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany SUBSCRIBING PACKAGE: KERNEL NUMBER: 3406 IA #: 3406 DATE CREATED: JUN 20, 2001 CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: MPIF* OPTIONS EXPORTED IN RG* PATCH GENERAL DESCRIPTION: MPI/PD exports some MPIF* namespaced options in RG*1.0*19. The following options are distributed via KIDS as "ATTACH TO MENU." Master Patient Index Menu [MPIF VISTA MENU] Coordinating Master of Record (CMOR) Request [MPIF CMOR MGR] Patient File Initialization to MPI [MPIFINIT DPT TO MPI] Site Parameters Edit for CMOR [MPIF SITE PARAMETER] STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33032055 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 3409 IA #: 3409 FILE NUMBER: 8930 GLOBAL ROOT: USR(8930 DATE CREATED: NOV 29, 2004 CUSTODIAL PACKAGE: AUTHORIZATION/SUBSCRIPTION CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DIRECT READ OF USER CLASS FILE ID: USR(8930 GENERAL DESCRIPTION: TIU requests the ability to directly read the "B" cross reference of USR(8930 (The ASU User Class File #8930). This is to support the ability to check if a specific USER class exists. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 39964610 KEYWORDS: USR(8930 KEYWORDS: 8930 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING DETAILS: TIU needs to make this lookup in order to see if a USER class exists. EDITOR: HAWSEY,JASON NUMBER: 3410 IA #: 3410 FILE NUMBER: 801.41 GLOBAL ROOT: PXRMD(801.41) DATE CREATED: OCT 28, 2004 CUSTODIAL PACKAGE: CLINICAL REMINDERS CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: 3410 ID: PXRMD(801.41) GLOBAL REFERENCE: PXRMD(801.41,D0,0) FIELD NUMBER: 3 FIELD NAME: DISABLED LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field disables use of this dialog when it contains text. The text should be a short message explaining why use of this dialog has been disabled, as it will be displayed if this dialog is selected. FIELD NUMBER: 4 FIELD NAME: TYPE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field defines what type of dialog component this entry is. The type determines the processing that can occur with this entry. FIELD NUMBER: 10 FIELD NAME: COMPONENTS LOCATION: 10,0 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the components that are used to process a reminder. Generally the components relate to the TYPE of entry in the Reminder Dialog File. Reminder dialogs have dialog group or dialog element components. Dialog groups have a combination fo dialog element components. Dialog elements have prompt and forced value components. GLOBAL REFERENCE: PXRMD(801.41,D0,100) FIELD NUMBER: 100 FIELD NAME: CLASS LOCATION: 100;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is the class of a dialog. It is used to seperate the National dialogs that can't be edited except by a programmer and the LOCAL and/or VISN level dialogs that can be edited by local and visn level users. GLOBAL REFERENCE: PXRMD(801.41,DA(1),10,B,DA) GLOBAL DESCRIPTION: This is a cross reference on node 10 allowing for searching for necessary entries. GLOBAL REFERENCE: PXRMD(801.41,D0,10,D1,0) FIELD NUMBER: 2 FIELD NAME: ITEM LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field points to a dialog which is subordinate to this dialog. NOTE: The parent dialog menu or one of its ancestors may not be entered as an item. FIELD NUMBER: .01 FIELD NAME: SEQUENCE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field specifies the order in which this itme will be displayed or processed. GENERAL DESCRIPTION: Clinical Reminders is allowing access to the Reminder Dialog file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 32971529 KEYWORDS: PXRMD(801.41 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING DETAILS: TIU needs the ability to perform direct global reads on the REMINDER DIALOG FILE (801.41). The purpose is to create linkage between the Reminder dialogs and the TIU Templates. NUMBER: 3411 IA #: 3411 DATE CREATED: JUN 25, 2001 CUSTODIAL PACKAGE: CLINICAL REMINDERS CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PXRMPINF NAME: DBIA3411 ID: PXRMPINF GENERAL DESCRIPTION: Routine to delete the reminder patient data cache for a selected patient. VIEWER: SCHLEHUBER,CAMERON VIEWER: TEAGUE,LYN VIEWER: REDINGTON,PATRICK STATUS: Active EXPIRATION DATE: JAN 01, 2002 MAIL MESSAGE: 33053705 KEYWORDS: PXRMPINF COMPONENT/ENTRY POINT: KILLPC COMPONENT DESCRIPTION: The routine may be called directly D KILLPC^PXRMPINF(PXRMDFN). If there is an error in reminder evaluation after the install of patch PSJ*5*61 this is probably due to erroneous patient cache entries created within the prior 24 hours. The routine deletes the patient cache for a selected patient causing the cache to be rebuilt by the reminder evaluation process. VARIABLES: PXRMDFN TYPE: Input VARIABLES DESCRIPTION: Patient identifier in the format "PXRMDFN"_DFN SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING DETAILS: Once off DBA for patch PSJ*5*61. NUMBER: 3412 IA #: 3412 DATE CREATED: JUN 25, 2001 CUSTODIAL PACKAGE: AUTOMATED INFO COLLECTION SYS CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: IBDF1B1 NAME: Print Encounter Forms ID: IBDF1B1 GENERAL DESCRIPTION: The Registration package needs to be able to Print an Encounter Form while Registering a Patient through the GUI Registration. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33064716 COMPONENT/ENTRY POINT: APPT VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This is the IEN of the Patient file (#2). VARIABLES: IBAPPT TYPE: Input VARIABLES DESCRIPTION: This is the time/date NOW, as derived from NOW^%DTC. VARIABLES: IBCLINIC TYPE: Input VARIABLES DESCRIPTION: This variable holds the clinic location IEN (file #44, pointed to by the .01 field of file 409.95). VARIABLES: IBDT TYPE: Input VARIABLES DESCRIPTION: IBDT is the same as DT. SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 3415 IA #: 3415 DATE CREATED: JUN 26, 2001 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORY94 NAME: DBIA3415 ID: ORY94 GENERAL DESCRIPTION: Pharmacy Data Management will invoke this CPRS routine for conversions, as part of the install process of phase 2 of the Pharmacy Ordering Enhancements project. This phase 2 is released as 1 build, containing patches OR*3*94, PSJ*5*50, PSO*7*46 and PSS*1*38. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33058830 COMPONENT/ENTRY POINT: POST COMPONENT DESCRIPTION: This routine loops though all of the Pharmacy quick orders stored in CPRS to fix the following two problems. 1. CPRS looks for any Pharmacy quick orders that use Orderable Items that Pharmacy Data Management has inactivated and makes a call to see if Pharmacy Data Management has a new Orderable Item to replace the old Orderable Item. If a new Orderable Item is returned, CPRS updates the quick order automatically. If a new Orderable Item is not returned, a bulletin is generated at the end of the Post-Init that contains a list of all quick orders that still have inactive Orderable Items, and the bulletin is sent to the user who ran the install. 2. Because this patch changes the way that dose instructions are prompted for in the Outpatient ordering dialog, the same routine will also attempt to convert the dose saved with Outpatient quick orders into the new format. Any quick order that cannot be automatically converted will be listed in the bulletin generated at the end of the Post-Init. SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 3416 IA #: 3416 DATE CREATED: JUN 27, 2001 CUSTODIAL PACKAGE: INPATIENT MEDICATIONS CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSJBCMA4 NAME: DBIA3416 ID: PSJBCMA4 GENERAL DESCRIPTION: The purpose of this API is to allow Bar Code Medication Administration (BCMA) to expire/reinstate Inpatient Medications orders based on an administration event. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33514049 KEYWORDS: PSJBCMA4 COMPONENT/ENTRY POINT: ENE(DFN,ON) COMPONENT DESCRIPTION: The ENE component allows the expiration of an Inpatient Medications order with a schedule type of one-time. The order must be at an Active status and the stop date must be in the future. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal Entry number for the patient. (Required) VARIABLES: ON TYPE: Input VARIABLES DESCRIPTION: Order number (from the PHARMACY PATIENT file) to be udpated. (Required) COMPONENT/ENTRY POINT: ENR(DFN,ON) COMPONENT DESCRIPTION: The ENR component allows the reinstatement of an Inpatient Medications order. The order must have been expired at the request of BCMA and the original stop date must be in the future. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal Entry number for the patient. (Required) VARIABLES: ON TYPE: Input VARIABLES DESCRIPTION: Order number (from the PHARMACY PATIENT file) to be udpated. (Required) SUBSCRIBING PACKAGE: BAR CODE MED ADMIN ISC: Birmingham NUMBER: 3417 IA #: 3417 FILE NUMBER: 72 GLOBAL ROOT: RA(72, DATE CREATED: JUN 28, 2001 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: EXAM STATUS ORDER ID: RA(72, GLOBAL REFERENCE: RA(72,D0,0) FIELD NUMBER: 3 FIELD NAME: ORDER LOCATION: 0;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field contains the logical order that this exam status falls into. Exam status 'CANCELLED' is reserved and has an order of '0'. Exam status 'COMPLETE' is reserved and has an order of '9'. GENERAL DESCRIPTION: As data is gathered, it may be stored in ^TMP("RAE",$J, which global may be killed before and after use. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33065285 KEYWORDS: GMTSRAE SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: Health Summary looks for an 'Examination Status' order of 9 - Completed for displaying examinations within a range of dates of a visit or an admission. NUMBER: 3420 IA #: 3420 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: JUL 19, 2001 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: NOK Work Phone ID: DPT( GLOBAL REFERENCE: DPT(2, FIELD NUMBER: .21011 FIELD NAME: K-WORK PHONE NUMBER LOCATION: .21;11 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: CPRS GUI users have requested to see the Next-of-Kin's work phone number on the CPRS patient inquiry display. Other NOK data is pulled from VADPT, but work phone is not available. After discussing with Mary Marks on a FORUM message, it was decided that we should enter an integration agreement to reference this field until such time as VADPT can be modified to add the work number to the array returned. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33136883 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: HEALTH SUMMARY NUMBER: 3422 IA #: 3422 FILE NUMBER: 391.71 GLOBAL ROOT: VAT(391.71, DATE CREATED: JUL 23, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3422 ID: VAT(391.71, GLOBAL REFERENCE: VAT(391.71,'AXMIT' GLOBAL REFERENCE: VAT(391.71,'C' GENERAL DESCRIPTION: MPI/PD requires read only access to ^VAT(391.71,"AXMIT" to order through the cross-reference and get a count of the number of Treating Facility Updates and Data Updates waiting to be processed. STATUS: Active MAIL MESSAGE: 33145265 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 3423 IA #: 3423 DATE CREATED: JUL 25, 2001 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSSGS0 NAME: DBIA3423 ID: PSSGS0 GENERAL DESCRIPTION: This call provides a Schedule validation check for medication orders entered through Computerized Patient Record System (CPRS). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33152516 COMPONENT/ENTRY POINT: EN(X,PSSLSTPK) COMPONENT DESCRIPTION: This call is used by CPRS Listman to validate a Schedule that is entered for a medication order. This call can be interactive, depending on the Schedule and file set-up, possibly prompting the user to select between duplicate schedules. VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: This variable is passed by reference. It is the Schedule entered for the medication order. VARIABLES: PSSLSTPK TYPE: Input VARIABLES DESCRIPTION: This variable is the pharmacy package for which the order is being entered. "O" will be for Outpatient orders, "I" will be for Inpatient orders. VARIABLES: X TYPE: Output VARIABLES DESCRIPTION: If the Schedule passed this validation checks, the value will be the Schedule, as it was passed in. If the Schedule did not pass the validation checks, this variable will be undefined. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3424 IA #: 3424 DATE CREATED: JUL 25, 2001 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSSQORD NAME: DBIA3424 ID: PSSQORD GENERAL DESCRIPTION: When phase 2 of the Pharmacy Ordering Enhancements project is installed, a rematching process will occur at the time of install, where IV Additives and IV Solutions will be matched to new Pharmacy Orderable Items. Pharmacy needs to provide this new information to CPRS, so CPRS can update as many of their Quick Orders as possible. The old pointer values will be stored in an XTMP global for 30 days to assist in this process. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33152544 COMPONENT/ENTRY POINT: $$EN(PSS1,PSS2) COMPONENT DESCRIPTION: This entry point is used to provide CPRS with updated Pharmacy Orderable Item information to use in Quick Order updates, as a result of the automatic rematching process of the Pharmacy Ordering Enhancements phase 2 install. VARIABLES: PSS1 TYPE: Input VARIABLES DESCRIPTION: This variable is the internal number from the PHARMACY ORDERABLE ITEM (#50.7) File. VARIABLES: PSS2 TYPE: Input VARIABLES DESCRIPTION: This variable is the internal number from the DRUG (#50) File. VARIABLES: $$EN TYPE: Output VARIABLES DESCRIPTION: This variable can be one of three values: "-1" indicates that a new Pharmacy Orderable Item could not be found. "#^0^date" indicates a Pharmacy Orderable Item was found, but the item is inactive. Piece 1 is the internal entry number from the PHARMACY ORDERABLE ITEM (#50.7) File, piece 2 is "0" indicating the item is inactive, and piece 3 is the inactive date. "#^1" indicates a Pharmacy Orderable Item was found. Piece 1 is the internal entry number from the PHARMACY ORDERABLE ITEM (#50.7) File, and piece 2 is "1", indicating that the item is active. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3425 IA #: 3425 DATE CREATED: AUG 03, 2001 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCEDT2 NAME: Consult editing utilities ID: GMRCEDT2 GENERAL DESCRIPTION: The included entry points allow access to information about editng and resubmitting records in the Consult/Request Tracking package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 31334257 COMPONENT/ENTRY POINT: $$EDRESOK(GMRCDA) COMPONENT DESCRIPTION: This entry point provides information regarding the ability to edit and resubmit a particular consult record. VARIABLES: GMRCDA TYPE: Input VARIABLES DESCRIPTION: This variable is the internal entry number from the REQUEST/CONSULTATION (#123) file. VARIABLES: $$EDRESOK TYPE: Output VARIABLES DESCRIPTION: Boolean value 1 (may be edited and resubmitted) 0 (not available for editing and resubmission) SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: FEE BASIS CLAIMS SYSTEM DBA Comments: 6/3/14-MC: Brandon DeWayne originally requested to add FBCS as a subscriber 6/20/13. Approval received by Tony Thompson. Patch was released on 9/11/13 as an emergency patch. Since approval has been received and patch already released, adding FBCS as a subscribing package to ICR. NUMBER: 3426 IA #: 3426 FILE NUMBER: 45 GLOBAL ROOT: DGPT( DATE CREATED: AUG 06, 2001 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3426 ID: DGPT( GLOBAL REFERENCE: DGPT( FIELD NUMBER: 7.1 FIELD NAME: CLOSE OUT FILE LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This is a pointer field to the PTF CLOSE OUT File (#45.84). GENERAL DESCRIPTION: Incomplete Records Tracking is accessing the CLOSE OUT FILE Field (#7.1). CLOSE OUT FILE Field (#7.1) is a pointer to the PTF CLOSE OUT File (#45.84) which will be use to return a close out date entry. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33574158 SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING ISC: Albany EDITOR: YORTY,M ROBERT NUMBER: 3427 IA #: 3427 FILE NUMBER: 440.6 GLOBAL ROOT: PRCH DATE CREATED: NOV 14, 2001 CUSTODIAL PACKAGE: IFCAP USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Purchase Card info ID: PRCH GLOBAL REFERENCE: PRCH(440.6, FIELD NUMBER: .01 FIELD NAME: ORACLE DOCUMENT ID LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: CREDIT CARD NUMBER LOCATION: 0;4 ACCESS: Both R/W w/Fileman FIELD NUMBER: 5 FIELD NAME: STATEMENT DATE LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 14 FIELD NAME: FISCAL YEAR LOCATION: 0;15 ACCESS: Read w/Fileman FIELD NUMBER: 16 FIELD NAME: CARD HOLDER LOCATION: 0;17 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 20 FIELD NAME: VENDOR PURCHASE ORDER LOCATION: 0;21 ACCESS: Read w/Fileman FIELD NUMBER: 6 FIELD NAME: TRANSACTION DATE LOCATION: 0;7 ACCESS: Read w/Fileman GENERAL DESCRIPTION: This is a one time request, limited duration integration agreement. This request is limited to use within changes to Prosthetics version 3.0 made by patch RMPR*3*67. This agreement and the changes made by patch RMPR*3*67 will be terminated at the time that IFCAP releases patch PRC*5.1*45 which is an updated API that meets the extended needs of Prosthetics. This agreement is needed to allow sites to reconcile Prosthetics Orders that had their Purchase Card numbers changed by the credit card supplier. This agreement includes a direct global read only access of the "D" cross- reference at ^PRCH(440.6,"D",date) for processing time needs. As part of this one time request, limited duration integration agreement, direct global read only access of ^PRC(442,ien,0) first piece is requested. STATUS: Active DURATION: Next Version MAIL MESSAGE: 33716794 GOOD ONLY FOR VERSION: pre-CoreFLS SUBSCRIBING PACKAGE: PROSTHETICS ISC: Hines NUMBER: 3429 IA #: 3429 FILE NUMBER: 101.24 GLOBAL ROOT: ORD(101.24, DATE CREATED: NOV 14, 2001 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA #3429 ID: ORD(101.24, GLOBAL REFERENCE: ORD(101.24, FIELD NUMBER: .42 FIELD NAME: MAXIMUM DAYS BACK LOCATION: 4;2 ACCESS: Read w/Fileman FIELD NUMBER: 'B' x-ref ACCESS: Direct Global Read & w/Fileman STATUS: Active MAIL MESSAGE: 33677908 KEYWORDS: BCMA KEYWORDS: CPRS KEYWORDS: MAXIMUM DAYS BACK KEYWORDS: 101.24 SUBSCRIBING PACKAGE: BAR CODE MED ADMIN ISC: Birmingham NUMBER: 3430 IA #: 3430 FILE NUMBER: 40.8 GLOBAL ROOT: DG(40.8, DATE CREATED: AUG 09, 2001 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3430 ID: DG(40.8, GLOBAL REFERENCE: DG(40.8, FIELD NUMBER: 100.01 FIELD NAME: TRACK INCOMPLETE SUMMARIES? LOCATION: DT;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: 100.02 FIELD NAME: DEFAULT PRIMARY PHYSICIAN LOCATION: DT;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: 100.03 FIELD NAME: ARE REPORTS REVIEWED? LOCATION: DT;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: 100.04 FIELD NAME: DEFAULT REVIEWING PHYSICIAN LOCATION: DT;4 ACCESS: Both R/W w/Fileman FIELD NUMBER: 100.05 FIELD NAME: TRACK OUTPATIENT OP REPORTS? LOCATION: DT;5 ACCESS: Both R/W w/Fileman FIELD NUMBER: 100.06 FIELD NAME: DAYS FOR DICTATION LOCATION: DT;6 ACCESS: Both R/W w/Fileman FIELD NUMBER: 100.07 FIELD NAME: DAYS FOR SIGNATURE LOCATION: DT;7 ACCESS: Both R/W w/Fileman FIELD NUMBER: 100.08 FIELD NAME: DAYS FOR REVIEW LOCATION: DT;8 ACCESS: Both R/W w/Fileman FIELD NUMBER: 100.09 FIELD NAME: INCOMPLETE SUMMARIES MESSAGE LOCATION: DT;9 ACCESS: Both R/W w/Fileman FIELD NUMBER: 100.1 FIELD NAME: DEFAULT PHYS. FOR SIGNATURE LOCATION: DT;10 ACCESS: Both R/W w/Fileman FIELD NUMBER: 100.2 FIELD NAME: STD. DEFIC. FOR SHORT FORMS? LOCATION: DT;11 ACCESS: Both R/W w/Fileman FIELD NUMBER: 100.3 FIELD NAME: DEFAULT MEDICAL RECORD TYPE LOCATION: DT;12 ACCESS: Both R/W w/Fileman FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Incomplete Records Tracking is accessing the NAME (#.01) field of the MEDICAL CENTER DIVISION (#40.8) file. Incomplete Records Tracking uses the following reference: "B" cross reference ^DG(40.8,"B",DA) ----------------------------- Incomplete Records Tracking has retained full authority for the "DT" node and its fields located and maintained in the MEDICAL CENTER DIVISION (#40.8) File. This includes development of the data dictionary (DD) for these fields, as well as responsibility for data entry into and data retriveval from these fields. This agreement is a "delegation of custody" of these fields from Registration to Incomplete Records Tracking. It provides Incomplete Records Tracking all rights and privileges to development and distribution for all DD elements and data in these fields. In addition, all DBIAs required for access to the DD and data for these fields will be between any subscriber and Incomplete Records Tracking as the custodian. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33574191 SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING ISC: Albany EDITOR: YORTY,M ROBERT NUMBER: 3431 IA #: 3431 FILE NUMBER: 43 GLOBAL ROOT: DG(43, DATE CREATED: AUG 09, 2001 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3431 ID: DG(43, GLOBAL REFERENCE: DG(43, FIELD NUMBER: 513 FIELD NAME: IRT SHORT FORM LIST GROUP LOCATION: NOT;14 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: Select the name of the mailgroup which should be notified whenever the IRT Background Job is run, options: (IRT Update Std. Deficiencies and IRT Update Std. Def. Background Job), to receive a list of patients that have been discharged less than 48 hours from their admission (Short Form).. If no mailgroup is selected no bulletin will be generated. FIELD NUMBER: 401 FIELD NAME: IRT BACKGROUND JOB LAST RUN LOCATION: IRT;1 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: 1. Incomplete Records Tracking has retained full authority for the "IRT" node and its field IRT BACKGROUND JOB LAST RUN (#401) located in the MAS PARAMETERS (#43) File. 2. Incomplete Records Tracking has retained full authority for the field IRT SHORT FORM LIST GROUP (#513) located in the MAS PAREMETERS (#43) File. This includes development of the data dictionary (DD) for these fields, as well as responsibility for data entry into and data retriveval from these fields. This agreement is a "delegation of custody" of these fields from Registration to Incomplete Records Tracking. It provides Incomplete Records Tracking all rights and privileges to development and distribution for all DD elements and data in these fields. In addition, all DBIAs required for access to the DD and data for these fields will be between any subscriber and Incomplete Records Tracking as the custodian. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33574193 SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING ISC: Albany EDITOR: YORTY,M ROBERT NUMBER: 3432 IA #: 3432 FILE NUMBER: 405 GLOBAL ROOT: DGPM( DATE CREATED: AUG 09, 2001 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3432 ID: DGPM( GLOBAL REFERENCE: DGPM( FIELD NUMBER: 60.01 FIELD NAME: IRT BACKGROUND JOB RUN LOCATION: IRT;1 ACCESS: Direct Global R/W & w/Fileman GENERAL DESCRIPTION: Incomplete Records Tracking has retained full authority for the "IRT" node and its field IRT BACKGROUND JOB RUN (#60.01) located in the PATIENT MOVEMENT (#405) File. This includes development of the data dictionary (DD) for these fields, as well as responsibility for data entry into and data retriveval from these fields. This agreement is a "delegation of custody" of these fields from Registration to Incomplete Records Tracking. It provides Incomplete Records Tracking all rights and privileges to development and distribution for all DD elements and data in these fields. In addition, all DBIAs required for access to the DD and data for these fields will be between any subscriber and Incomplete Records Tracking as the custodian. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33574200 SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING ISC: Albany EDITOR: YORTY,M ROBERT NUMBER: 3433 IA #: 3433 FILE NUMBER: 40.8 GLOBAL ROOT: DG(40.8, DATE CREATED: AUG 09, 2001 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3433 ID: DG(40.8, GLOBAL REFERENCE: DG(40.8,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Incomplete Records Tracking is accessing the NAME Field (#.01) of the MEDICAL CENTER DIVISION (#40.8) File. Incomplete Records Tracking uses the following cross references: "B" cross reference ^DG(40.8,"B",DA) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33574206 SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING ISC: Albany EDITOR: YORTY,M ROBERT NUMBER: 3434 IA #: 3434 FILE NUMBER: .84 GLOBAL ROOT: DI(.84 DATE CREATED: AUG 13, 2001 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DIALOG File Entry Deletion ID: DI(.84 GENERAL DESCRIPTION: When creating patch RGED*2.6*1 to remove Extensible Editor v.2.6, we tried to eliminate the DIALOG (#.84) file entries distributed with the package (9960001 - 9960070) by placing them in the build and marking them as DELETE AT SITE. KIDS did not remove them on the target system because delete access on File .84 is set to an "^". Therefore, a private integration agreement is established to allow the reference to ^DI(.84 using the following code in RGEDPST. ;Delete DIALOG file entries 9960001 through 9960070. N RGEDLOG W !!," Deleting Extensible Editor dialog entries.",!," " S DIK="^DI(.84," F RGEDLOG=9960001:1:9960070 S DA=RGEDLOG D ^DIK W "." W !!," DIALOG entries 9960001 through 9960070 have been deleted." STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33174031 SUBSCRIBING PACKAGE: EXTENSIBLE EDITOR NUMBER: 3435 IA #: 3435 FILE NUMBER: 3.2 GLOBAL ROOT: %ZIS(2 DATE CREATED: MAR 05, 2003 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: CONTROL CODES SUBFILE ID: %ZIS(2 GLOBAL REFERENCE: %ZIS(2,ien,55 FIELD NUMBER: .01 FIELD NAME: ABBREVIATION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: FULL NAME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: CONTROL CODE LOCATION: 1;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The purpose of this agreement is to allow direct MUMPS read access to the CONTROL CODES subfile (#3.2055) of the TERMINAL TYPE file (#3.2). Any subscribing package must coordinate the ABBREVIATION and FULL NAME information with the KERNEL developers when subscribing to this agreement. Also, the agreed upon control codes should be added to this agreement for documentation. Inpatient Medications is using the control codes to create generic print routines for barcode printing. Inpatient Medications will use the following control codes, as will Registration and Bar Code Medication Administration (BCMA).: ET - End Text ETF - End Text Field EB - End Barcode EBF - End Barcode Field EL - End Label FE - Format End FI - Format Initialization FI1 - Format Initialization 1 FI2 - Format Initialization 2 SB - Start Barcode SBF - Start Barcode Field SL - Start Label ST - Start Text STF - Start Text Field SM - Start Med Route SMF - Start Med Route field EM - End Med Route EMF - End Med Route field Outpatient Pharmacy is using the control codes to create a generic print routine for laser labels. Outpatient Pharmacy will use the following control codes: ACI = ADDRESS CHANGE INITIALIZATION ALI = ALLERGY SECTION INITIALIZATION AWI = ALLERGY WARNING INITIALIZATION BLB = BOTTLE LABEL BODY INITIALIZATION BLBC = BOTTLE LABEL BARCODE BLF = BOTTLE LABEL FOOTER INITIALIZATION BLH = BOTTLE LABEL HEADER INITIALIZATION CDII = CRITICAL DRUG INTERACTION INITIALIZATION CNI = COPAY NARRATIVE INITIALIZATION EBLBC = END OF BOTTLE LABEL BARCODE EBT = END OF BARCODE TEXT F10 = TEN POINT FONT - NO BOLD F10B = TEN POINT FONT, BOLDED F12 = TWELVE POINT FONT - NO BOLD F12B = 12 POINT FONT BOLDED F6 = SIX POINT FONT - NO BOLD F8 = EIGHT POINT FONT - NO BOLD F9 = NINE POINT FONT - NO BOLD FDU = FONT DISABLE UNDERLINE FWU = FONT WITH UNDERLINE LL = LASER LABEL LLI = LASER LABEL INIT MLI = MAILING LABEL INITIALIZATION NR = NORMAL ROTATION PFDI = PHARMACY FILL DOCUMENT INITIALIZATION PFDQ = PHARMACY FILL DOCUMENT QUANTITY PFDT = PHARMACY FILL DOCUMENT TRAILER PFDW = PHARMACY FILL DOCUMENT WARNING PFI = PATIENT FILL INITIALIZATION PII = PATIENT INSTRUCTION INITIALIZATION PMII = PMI SECTION INITIALIZATION RMI = RETURN MAIL INITIALIZATION RNI = REFILL NARRATIVE INITIALIZATION RPI = REFILL PRINT INITIALIZATION RT = ROTATE TEXT SBT = START OF BARCODE TEXT SPI = SUSPENSE PRINT INITIALIZATION ST = START OF TEXT WLI = WARNING LABEL INITIALIZATION STATUS: Active MAIL MESSAGE: 33212494 KEYWORDS: %ZIS(2 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING DETAILS: Used by BCMA: EB - End Barcode EL - End Label FI - Format Initialization FI1 Format Initialization 1 FI2 Format Initialization 2 SB - Start Barcode SBF - Start Barcode Field SL - Start Label ST - Start Text STF - Start Text Field Although the name of the control codes are shared with other applications, the coding logic associated with each control code are quite different. close attention should be paid to the usage and sharing of control codes among barcode printing devices. NUMBER: 3436 IA #: 3436 DATE CREATED: AUG 15, 2001 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUSRVR NAME: CALLS TO TIUSRVR ID: TIUSRVR CREATOR: TRAXLER,FRANK STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33226954 COMPONENT/ENTRY POINT: GET1405 COMPONENT DESCRIPTION: Call with record number (IEN) of the document in the TIU DOCUMENT FILE (#8925). - Returns the variable pointer to the REQUESTING PACKAGE REFERENCE (e.g., "IEN;GMR(123," for Consults; or "IEN;SRF(" for Surgery), if a value is present. - Otherwise, returns "-1^" VARIABLES: TIUY TYPE: Output VARIABLES DESCRIPTION: Passed By Reference. Will contain the result of the procedure call. VARIABLES: TIUDA TYPE: Input VARIABLES DESCRIPTION: This is the Record Number (IEN) of the document in the TIU DOCUMENT FILE (#8925) for which the calling application is inquiring. COMPONENT/ENTRY POINT: GETALRT COMPONENT DESCRIPTION: Given an Alert ID for a TIU Signature Alert, returns the string: "^^" VARIABLES: TIUY TYPE: Output VARIABLES DESCRIPTION: Passed by Reference. Contains the result of the call. VARIABLES: XQAID TYPE: Input VARIABLES DESCRIPTION: This is the alert ID for the TIU SIGNATURE ALERT. Its format will be: "TIU" COMPONENT/ENTRY POINT: GETPREF SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: CPRS calls these tags both MUMPS-to-MUMPS, and from RPCs (i.e., see IA #'s 3438 and 3439). SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: MH ADDED 2.15.2011 DATE/TIME EDITED: FEB 15, 2011@07:47 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: TRAXLER,FRANK WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 3437 IA #: 3437 FILE NUMBER: 40.8 GLOBAL ROOT: DG(40.8, DATE CREATED: AUG 15, 2001 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUEN113 NAME: REGISTRATION FILE USED BY TIU - DG(40.8 ID: TIUEN113 GLOBAL REFERENCE: DG(40.8, GLOBAL REFERENCE: DG(40.8,'ADV' FIELD NUMBER: .07 FIELD NAME: INSTITUTION FILE POINTER LOCATION: 0;7 ACCESS: Read w/Fileman GENERAL DESCRIPTION: TIU extracts INSTITUTION FILE POINTER data from the MEDICAL CENTER DIVISION file (#40.8) for a one-time use in the installation environment check routine TIUEN113. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33219813 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 3438 IA #: 3438 DATE CREATED: AUG 15, 2001 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU GET REQUEST GENERAL DESCRIPTION: This Remote Procedure returns the variable pointer to the REQUESTING PACKAGE REFERENCE (File #8925, Field #1405). This would be the record in the Requesting Package (e.g., Consult/Request Tracking or Surgery) for which the resulting document has been entered in TIU. INPUT PARAMETER: TIUDA PARAMETER TYPE: LITERAL REQUIRED: YES SEQUENCE NUMBER: 1 DESCRIPTION: This is the record number (IEN) of the document in the TIU Document File (#8925). RETURN PARAMETER DESCRIPTION: This is the Variable pointer (e.g., "15741;GMR(123,") to the corresponding request. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33226954 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: CPRS calls this entry point as both a Remote Procedure, and MUMPS-to-MUMPS, as documented in IA #3436. NUMBER: 3439 IA #: 3439 DATE CREATED: AUG 15, 2001 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: TIU GET ALERT INFO GENERAL DESCRIPTION: Given a TIU XQAID, return the patient and document type for the item being alerted. INPUT PARAMETER: XQAID PARAMETER TYPE: LITERAL MAXIMUM DATA LENGTH: 60 REQUIRED: YES DESCRIPTION: The XQAID of the alert. RETURN PARAMETER DESCRIPTION: TIUDA^DFN^ where TIUDA is the document IEN in the TIU DOCUMENT File (#8925), DFN is the IEN of the Patient in the PATIENT File (#2), and is an arbitrarily set constant based on the document type. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33226954 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: CPRS makes this call both as an RPC, and in a direct MUMPS-to-MUMPS call, as documented in IA #3436. SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE NUMBER: 3440 IA #: 3440 DATE CREATED: AUG 15, 2001 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUPD NAME: TIU PRINT DRIVER ID: TIUPD GENERAL DESCRIPTION: The API RPC^TIUPD is called both from the remote procedure TIU PRINT RECORD, as documented in DBIA #1834 and MUMPS-to-MUMPS, to print a given record to a named device, either for work or chart copies, and will accommodate both Windows and host printers. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33226954 COMPONENT/ENTRY POINT: RPC COMPONENT DESCRIPTION: Allows printing of TIU Documents on demand. VARIABLES: TIUY TYPE: Output VARIABLES DESCRIPTION: This is an error flag/message which will have two '^'-pieces. The first piece will be a boolean flag indicating whether or not the call failed (0 indicates success, while 1 indicates failure). The second piece is a textual message indicating the nature of the error. In the event of success, the second piece will describe whether the printout will be for a CHART COPY or a WORK COPY. VARIABLES: TIUDA TYPE: Input VARIABLES DESCRIPTION: This is the record number of the document in the TIU DOCUMENT FILE (#8925). It uniquely identifies the document to be printed. VARIABLES: TIUIO TYPE: Input VARIABLES DESCRIPTION: This is the NAME of the device to which the document is to be printed. NOTE: You may not pass the $I for the device, or the Pointer to the DEVICE FILE entry corresponding to the device. ONLY THE DEVICE NAME will work. VARIABLES: TIUFLAG TYPE: Input VARIABLES DESCRIPTION: This is a flag which tells the print driver to specify a CHART versus WORK copy of the document. If it is undefined or its value is 0, then the printed copy will be marked as a WORK COPY. If its value is 1, then it will be marked as a CHART COPY. VARIABLES: TIUWIN TYPE: Input VARIABLES DESCRIPTION: Boolean flag indicating whether the output is directed to a Windows printer (1), or a printer directed directly to the host (0 or ""). SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI NUMBER: 3441 IA #: 3441 DATE CREATED: AUG 16, 2001 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUSRVLI NAME: CALLS TO TIUSRVLI ID: TIUSRVLI GENERAL DESCRIPTION: CPRS makes use of several APIs in TIUSRVLI to determine the complete hierarchical context of a given document when building the TreeView for the Notes, Summaries, and Consults tabs. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33226954 COMPONENT/ENTRY POINT: $$HASDAD(DA) COMPONENT DESCRIPTION: Boolean extrinsic function which evaluates whether a given document has a parent (i.e., either it is an addendum, or an Interdisciplinary Entry). VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: This is the record number (IEN) of the document in file 8925. VARIABLES: TYPE: Output VARIABLES DESCRIPTION: The function returns TRUE (i.e., 1) if the document has a parent (i.e., it's an addendum or an Interdisciplinary entry), or FALSE (i.e., 0) if the document stands alone. COMPONENT/ENTRY POINT: SETDAD(TIUY,DA,TIUI) COMPONENT DESCRIPTION: This subroutine will build an array which includes the complete hierarchical "ancestry" of a given TIU Document. For example, if one passes the record number of an addendum to an Interdisciplnary entry, and the name of an array to be returned (either as $NA(^TMP("",$J)) or as a local array), the module will return the Interdisciplinary Parent entry, and the Interdisciplinary entry to which the addendum belongs. NOTE: Prior to making the call, the local variable SEQUENCE should be set, indicating whether the documents should be returned in ascending ("A") or descending ("D") chronological order. Default is descending (most recent first). VARIABLES: TIUY TYPE: Input VARIABLES DESCRIPTION: This is the NAME of the array (global or local) in which the data should be returned. VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: This is the record number (IEN) of the document in the TIU DOCUMENT FILE (#8925). VARIABLES: TIUI TYPE: Input VARIABLES DESCRIPTION: This OPTIONAL parameter is the subscript from which the array should be incremented (defaults to 1). This allows the calling application to accumulate the ancestry of multiple documents in the same array, by calling SETDAD iteratively. COMPONENT/ENTRY POINT: $$HASKIDS(DA) COMPONENT DESCRIPTION: Boolean extrinsic function which evaluates whether a given document has descendents (i.e., either addenda, or an Interdisciplinary Entries). VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: This is the record number (IEN) of the document in the TIU DOCUMENT FILE (#8925). VARIABLES: TYPE: Output VARIABLES DESCRIPTION: The function returns TRUE (i.e., 1) if the document has descendents (i.e., addenda or Interdisciplinary Entries), or FALSE (i.e., 0) if the document has none. COMPONENT/ENTRY POINT: SETKIDS(TIUY,DA,TIUI) COMPONENT DESCRIPTION: This subroutine will build an array which includes all descendents of a given TIU Document. For example, if one passes the record number of an Interdisciplinary parent document, which has one or more entries, any of which having addenda; and the name of an array to be returned (either as $NA(^TMP("",$J)) or as a local array), the module will return the complete hierarchy. NOTE: Prior to making the call, the local variable SEQUENCE should be set, indicating whether the documents should be returned in ascending ("A") or descending ("D") chronological order. Default is descending (most recent first). VARIABLES: TIUY TYPE: Input VARIABLES DESCRIPTION: This is the NAME of the array (global or local) in which the data should be returned. VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: This is the record number (IEN) of the document in the TIU DOCUMENT FILE (#8925). VARIABLES: TIUI TYPE: Input VARIABLES DESCRIPTION: This OPTIONAL parameter is the subscript from which the array should be incremented (defaults to 1). This allows the calling application to accumulate the ancestry of multiple documents in the same array, by calling SETKIDS iteratively. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3442 IA #: 3442 FILE NUMBER: 3.2 GLOBAL ROOT: %ZIS(2 DATE CREATED: FEB 27, 2003 CUSTODIAL PACKAGE: KERNEL USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ZIS GLOBAL ID: %ZIS(2 GLOBAL REFERENCE: %ZIS(2, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1 FIELD NAME: RIGHT MARGIN LOCATION: 1;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: FORM FEED LOCATION: 1;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 3 FIELD NAME: PAGE LENGTH LOCATION: 1;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 6 FIELD NAME: OPEN EXECUTE LOCATION: 2;E1,245 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: The 'B' cross reference is accessed directly to get to the data. GENERAL DESCRIPTION: This DBIA describes access needed by packages to various parts of the global/file ^%ZIS(2 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 35707795 KEYWORDS: %ZIS SUBSCRIBING PACKAGE: AUTOMATED INFO COLLECTION SYS ISC: Albany SUBSCRIBING DETAILS: The AICS package has permission to execute the following code until an API is developed for this. X $G(^%ZIS(2,$G(IOST(0)),2)) AICS needs to be able to reset a device without the open command. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: OE/RR needs access to the following globals to use and setup an HFS device: ^%ZIS(2,"B", ^%ZIS(2,IFN,0) ^%ZIS(2,IFN,1) EDITOR: ELLIS,DONNA NUMBER: 3443 IA #: 3443 FILE NUMBER: 74 GLOBAL ROOT: RARPT DATE CREATED: AUG 17, 2001 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Check RAD/NUC MED REPORTS file header ID: RARPT CREATOR: CEBELINSKI,GREGORY GLOBAL REFERENCE: RARPT(0) GLOBAL DESCRIPTION: This IA allows the subscribing application the right to look at the file header of the RAD/NUC MED REPORTS file. GLOBAL REFERENCE: RARPT('B' GLOBAL DESCRIPTION: This IA allows the subscribing application the right to traverse the top-level 'B' cross reference of the RAD/NUC MED REPORTS file. GENERAL DESCRIPTION: There are two permissions granted through this Integration Agreement (IA). The first is that VistA Imaging will be granted permission to examine the file header of the RAD/NUC MED REPORTS (#74) file. The purpose is to allow Imaging to verify that the counter in the file header (third piece of ^RARPT(0)) has not decreased significantly since it was last inspected. This approach will enable us to detect major status changes in the global that could be caused by a global restoration, compression, or global move. The second is that VistA Imaging will be granted permission to traverse the top-level 'B' cross reference for records in the RAD/NUC MED REPORTS file. The 'B' cross reference is created via VA FileMan and is placed on the .01 field of the file. The name of the .01 field of the RAD/NUC MED REPORTS file is DAY-CASE#. VIEWER: SCHLEHUBER,CAMERON VIEWER: BARRIOS,LUCILLE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33231927 KEYWORDS: RAD DAY-CASE # KEYWORDS: RAD REPORTS file header KEYWORDS: RAD ACCESSION NUMBER SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: See General description. DATE ACTIVATED: AUG 13, 2010 DATE/TIME EDITED: AUG 13, 2010@10:21 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: CEBELINSKI,GREG DATE/TIME EDITED: AUG 13, 2010@12:21 ACTION: APPROVED AT THE REQUEST OF: CEBELINSKI,GREG WITH CONCURRENCE OF: TROMBETTA,KATHY NUMBER: 3444 IA #: 3444 FILE NUMBER: 43 GLOBAL ROOT: DG(43, DATE CREATED: AUG 16, 2001 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: REGISTRATION FILE USED BY TIU - DG(43 ID: DG(43, GLOBAL REFERENCE: DG(43,1,'GL' FIELD NUMBER: 11 FIELD NAME: MULTIDIVISION MED CENTER? LOCATION: GL;2 ACCESS: Read w/Fileman GENERAL DESCRIPTION: TIU extracts MULTIDIVISION MED CENTER? data from the MAS PARAMETERS file (#43) for use in routine TIULA and TIULA1 to determine if a facility is multidivisional. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33212322 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 3445 IA #: 3445 FILE NUMBER: 42 GLOBAL ROOT: DIC(42, DATE CREATED: AUG 22, 2001 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Determine the Service associated with a ward. ID: DIC(42, GLOBAL REFERENCE: DIC(42, FIELD NUMBER: .03 FIELD NAME: SERVICE LOCATION: 0;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: A service, short for hospital service, is associated with a ward in order to keep patients with similar medical experiences together in order to provide better treatment. Many reports are used to track the number of patient per ward, as well as, how many patients are linked to a particular hospital service. GLOBAL DESCRIPTION: The Service (#.03) field is the third piece located on the zero node (0;3) of the file record. GENERAL DESCRIPTION: In order to determine whether an exam gets sent to PCE for crediting, a check on the patient's physical location must be performed. If the patient is currently being seen in a clinic, or if the patient is assigned to a ward and that ward has a Service defined as Domiciliary, then the record passed this check and can be passed to PCE if other checks are successful. I need to get the Service associated with a ward location, and I am requesting to achieve this by utilizing a "read with FileMan" utility: $$GET1^DIQ(42,ien of file 42 record,.03,"I" -or- "E") where: Where '42' is the file number for the WARD LOCATION file, the second subscript is self-explanatory, '.03' is the SERVICE field number and 'I' indicates we'd like the internal representation, while 'E' indicates that we'd like the external representation of the data. VIEWER: SCHLEHUBER,CAMERON VIEWER: MARKS,MARY VIEWER: CEBELINSKI,GREGORY VIEWER: PETERSON,JAMES R STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33247399 KEYWORDS: SERVICE KEYWORDS: WARD LOCATION SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE ISC: Hines NUMBER: 3446 IA #: 3446 FILE NUMBER: .44 GLOBAL ROOT: DIST(.44 DATE CREATED: AUG 23, 2001 CUSTODIAL PACKAGE: VA FILEMAN USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: coreFLS Foreign File Format ID: DIST(.44 GLOBAL REFERENCE: DIST(.44 FIELD NUMBER: 1 FIELD NAME: FIELD DELIMITER LOCATION: 0;2 ACCESS: Write w/Fileman FIELD NUMBER: 2 FIELD NAME: RECORD DELIMITER LOCATION: 0;3 ACCESS: Write w/Fileman FIELD NUMBER: 5 FIELD NAME: RECORD LENGTH FIXED? LOCATION: 0;6 ACCESS: Write w/Fileman FIELD NUMBER: 7 FIELD NAME: MAXIMUM OUTPUT LENGTH LOCATION: 0;8 ACCESS: Write w/Fileman FIELD NUMBER: 8 FIELD NAME: QUOTE NON-NUMERIC FIELDS? LOCATION: 0;10 ACCESS: Write w/Fileman FIELD NUMBER: 40 FIELD NAME: FORMAT USED? LOCATION: 0;9 ACCESS: Write w/Fileman FIELD NUMBER: 6 FIELD NAME: NEED FOREIGN FIELD NAMES? LOCATION: 0;7 ACCESS: Write w/Fileman FIELD NUMBER: 10 FIELD NAME: SEND LAST FIELD DELIMITER? LOCATION: 0;12 ACCESS: Write w/Fileman FIELD NUMBER: 20 FIELD NAME: FILE HEADER LOCATION: 1;E1,245 ACCESS: Write w/Fileman FIELD NUMBER: 25 FIELD NAME: FILE TRAILER LOCATION: 2;E1,245 ACCESS: Write w/Fileman FIELD NUMBER: 31 FIELD NAME: USAGE NOTES LOCATION: 4;0 ACCESS: Write w/Fileman FIELD NUMBER: 30 FIELD NAME: DESCRIPTION LOCATION: 3;0 ACCESS: Write w/Fileman GENERAL DESCRIPTION: coreFLS needs to obtain data from various files to populate their tables with legacy data. One method being used is the FileMan data export tools. Since it is not possible to send FileMan Foreign File formats via KIDS, we will need to populate FOREIGN FORMAT file (#.44) with an entry. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33249706 KEYWORDS: coreFLS KEYWORDS: FileMan KEYWORDS: Export KEYWORDS: Foreign KEYWORDS: Format SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring NUMBER: 3447 IA #: 3447 FILE NUMBER: .4 GLOBAL ROOT: DIPT DATE CREATED: AUG 23, 2001 CUSTODIAL PACKAGE: VA FILEMAN USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: coreFLS Export Templates ID: DIPT GLOBAL REFERENCE: DIPT FIELD NUMBER: 105 FIELD NAME: EXPORT FORMAT LOCATION: 105;1 ACCESS: Write w/Fileman FIELD NUMBER: 8 FIELD NAME: TEMPLATE TYPE LOCATION: 0;8 ACCESS: Read w/Fileman GENERAL DESCRIPTION: With the new entry into the FOREIGN FORMAT file (#.44) (see IA 3446), the PRCL* namespaced export templates in the PRINT TEMPLATE file (#.4) will need to have the EXPORT FORMAT field (#105) updated to be the foreign format IEN. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33252534 KEYWORDS: coreFLS KEYWORDS: export KEYWORDS: template KEYWORDS: format KEYWORDS: PRCL SUBSCRIBING PACKAGE: IFCAP ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: ENGINEERING ISC: Washington/Silver Spring SUBSCRIBING PACKAGE: EQUIPMENT/TURN-IN REQUEST ISC: Washington/Silver Spring NUMBER: 3448 IA #: 3448 DATE CREATED: SEP 10, 2001 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSBML NAME: PSB MEDICATION HISTORY REPORT ID: PSBML GENERAL DESCRIPTION: The purpose of this agreement is to provide other packages with the ability to call the BCMA Medication History report. It returns a report of medications a patient has received by orderable item. STATUS: Active EXPIRATION DATE: MAY 2003 MAIL MESSAGE: 33414348 GOOD ONLY FOR VERSION: 1.0 KEYWORDS: BCMA KEYWORDS: PSB KEYWORDS: MEDICATION HISTORY COMPONENT/ENTRY POINT: HISTORY VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN number. VARIABLES: PSBOI TYPE: Input VARIABLES DESCRIPTION: Orderable Item number. VARIABLES: RESULTS TYPE: Input VARIABLES DESCRIPTION: The name of the array that the output is passed in. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3449 IA #: 3449 FILE NUMBER: 120.86 GLOBAL ROOT: GMR(120.86, DATE CREATED: SEP 11, 2001 CUSTODIAL PACKAGE: ADVERSE REACTION TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: ADVERSE REACTION ASSESSMENT ID: GMR(120.86, CREATOR: BUECHLER,MELANIE K GLOBAL REFERENCE: GMR(120.86,D0,0) FIELD NUMBER: 2 FIELD NAME: ASSESSING USER LOCATION: 0;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field contains the name of the user who made the last reaction assessment for this patient. FIELD NUMBER: 3 FIELD NAME: ASSESSMENT DATE/TIME LOCATION: 0;4 ACCESS: Read w/Fileman FIELD DESCRIPTION: This field contains the date/time of the last reaction as sessment for this patient. FIELD NUMBER: 1 FIELD NAME: REACTION ASSESSMENT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Set of codes that indicates the patient's allergy assessment level. Value of 1 indicates that the patient has allergies while a value of 0 indicates that the patient has no known allergies (NKA). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33416523 KEYWORDS: GMTSALG SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: Health Summary Allergy Component needs to extract the name of the person making the assessment and the assessment date. SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING PACKAGE: VDEF SUBSCRIBING DETAILS: VDEF needs to be able to determine if a patient has active allergies as part of the PFSS project. SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) SUBSCRIBING DETAILS: VPS is requesting FileMan read access to the Reaction Assessment (#1) field. SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD DBA Comments: 9/28/12-MM: VPS added as a subscriber for VPS*1*2. VPS is requesting FileMan read access to the Reaction Assessment (#1) field. Content corrected - Deleted Dave Naber as editor for ICR. 9/24/14-MC: Deactivated for edits and added Melanie Buechler as an editor to this ICR for VPR*1*3. 9/30/14-MC: Activated at the request of Melanie Buechler and approved by Jason Hawsey. DATE ACTIVATED: SEP 30, 2014 DATE/TIME EDITED: JAN 24, 2007@13:36 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: RANDALL,SHERRY WITH CONCURRENCE OF: NABER,DAVID DATE/TIME EDITED: SEP 28, 2012@09:06 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: WHELESS,CAROLYN WITH CONCURRENCE OF: HAWSEY,JASON DATE/TIME EDITED: SEP 28, 2012@09:09 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: HAWSEY,JASON DATE/TIME EDITED: SEP 30, 2014@13:01 ACTION: APPROVED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: HAWSEY,JASON NUMBER: 3451 IA #: 3451 FILE NUMBER: 8925.1 GLOBAL ROOT: TIU(8925.1, DATE CREATED: SEP 11, 2001 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TIU/SELECTED PROGRESS NOTES ID: TIU(8925.1, GLOBAL REFERENCE: TIU(8925.1,DO,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Pointed to STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33416905 KEYWORDS: GMTS SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: TIU DOCUMENT DEFINITION are pointed to by Health Summary for the PROGRESS NOTES SELECTED component. NUMBER: 3452 IA #: 3452 FILE NUMBER: 4.2 GLOBAL ROOT: DIC(4.2, DATE CREATED: SEP 13, 2001 CUSTODIAL PACKAGE: MAILMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: MAIL.CIO.MED.VA.GOV Domain ID: DIC(4.2, GLOBAL REFERENCE: DIC(4.2,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: CIRN MPI/PD has an agreement to do a read with FileMan on the NAME (#.01) field in the DOMAIN (#4.2) file. This is used in environment check routine, RGP22ENV, to ensure that the instructions in informational patch XM*DBA*139 have been followed for domain "MAIL.CIO.MED.VA.GOV". The environment check routine will not allow patch RG*1.0*22 to be installed unless the "MAIL.CIO.MED.VA.GOV" entry exists. Patch RG*1.0*22 is in support of GCPR. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33427940 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham NUMBER: 3453 IA #: 3453 FILE NUMBER: 4 GLOBAL ROOT: DIC(4, DATE CREATED: SEP 13, 2001 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Enter/Edit OFFICE OF INFORMATION SRV CNTR Entry ID: DIC(4, GLOBAL REFERENCE: DIC(4,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Write w/Fileman FIELD NUMBER: .02 FIELD NAME: STATE LOCATION: 0;2 ACCESS: Write w/Fileman FIELD NUMBER: 11 FIELD NAME: STATUS LOCATION: 0;11 ACCESS: Write w/Fileman GLOBAL REFERENCE: DIC(4,D0,3) FIELD NUMBER: 13 FIELD NAME: FACILITY TYPE LOCATION: 3;1 ACCESS: Write w/Fileman GLOBAL REFERENCE: DIC(4,D0,99) FIELD NUMBER: 99 FIELD NAME: STATION NUMBER LOCATION: 99;1 ACCESS: Write w/Fileman FIELD NUMBER: 100 FIELD NAME: OFFICIAL VA NAME LOCATION: 99;3 ACCESS: Write w/Fileman GENERAL DESCRIPTION: CIRN MPI/PD has an agreement to use a FileMan FILE^DICN call to edit the following fields in the INSTITUTION (#4) file. NAME (#.01), STATE (#.02), STATUS (#11), FACILITY TYPE (#13), STATION NUMBER (#99) and OFFICAL VA NAME (#100). This is done in pre-install routine, PRE^RGP22, to create the OFFICE OF INFORMATION SRV CNTR entry in the INSTITUTION file if it is not present. This functionality is in support of GCPR. The entry created has the following values. NAME: OFFICE OF INFORMATION SRV CNTR STATE: OHIO STATUS: National FACILITY TYPE: VAMC STATION NUMBER: 776 OFFICAL VA NAME: OFFICE OF INFORMATION SERVICE CENTER STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33428453 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham NUMBER: 3454 IA #: 3454 FILE NUMBER: 870 GLOBAL ROOT: HLCS(870, DATE CREATED: SEP 13, 2001 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Enter/Edit VACIO Entry in HL LOGICAL LINK (#870) ID: HLCS(870, GLOBAL REFERENCE: HLCS(870, FIELD NUMBER: .03 FIELD NAME: DOMAIN LOCATION: 0;7 ACCESS: Write w/Fileman FIELD NUMBER: 400.01 FIELD NAME: TCP/IP ADDRESS LOCATION: 400;1 ACCESS: Write w/Fileman FIELD NUMBER: 4.5 FIELD NAME: AUTOSTART LOCATION: 0;6 ACCESS: Write w/Fileman GENERAL DESCRIPTION: MPI/PD build RG*1.0*22 exports (via KIDS) the following HL LOGICAL LINK. NODE: VACIO INSTITUTION: OFFICE OF INFORMATION SRV CNTR LLP TYPE: TCP AUTOSTART: Enabled DOMAIN: MAIL.CIO.MED.VA.GOV QUEUE SIZE: 10 EXCEED RE-TRANSMIT ACTION: restart TCP/IP ADDRESS: 152.127.1.6 TCP/IP PORT: 5000 TCP/IP SERVICE TYPE: CLIENT (SENDER) Post-install routine PST^RGP22, determines if the account is the production or test account. (IA #3335 and #2525 allow the read access necessary to do this.) If the account is the test account, we do not want the 'VACIO' node to be actively used. Therefore, the DOMAIN (#.03) and TCP/IP ADDRESS (#400.01) fields are omitted in the post-install. CIRN MPI/PD has an agreement to use a FileMan DIE call to edit/eliminate the DOMAIN (#.03) and TCP/IP ADDRESS (#400.01) fields in the HL LOGICAL LINK (#870) file for entry 'VACIO'. This functionality is in support of GCPR. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33428911 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY NUMBER: 3455 IA #: 3455 FILE NUMBER: 9000010.06 GLOBAL ROOT: AUPNVPRV DATE CREATED: SEP 14, 2001 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3455 ID: AUPNVPRV GLOBAL REFERENCE: AUPNVPRV(D0,0) FIELD NUMBER: .01 FIELD NAME: PROVIDER LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .02 FIELD NAME: PATIENT NAME LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .04 FIELD NAME: PRIMARY/SECONDARY LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: AUPNVPRV('AD' STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33432656 KEYWORDS: CLINICAL REMINDERS KEYWORDS: V PROVIDER SUBSCRIBING PACKAGE: CLINICAL REMINDERS ISC: Salt Lake City SUBSCRIBING DETAILS: Clinical Reminders needs to determine who was the visit/encounter provider. Therefore Clinical Reminders needs to read the following fields: NUMBER: 3456 IA #: 3456 DATE CREATED: SEP 18, 2001 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGNTAPI1 NAME: DBIA3456-A ORIGINAL NUMBER: 3456 ID: DGNTAPI1 GENERAL DESCRIPTION: The purpose of this API is to facilitate the filing of the Head/Neck Cancer Diagnosis into the NOSE AND THROAT RADIUM HISTORY (#28.11) file when verified through an external application (i.e. PCE Encounter Checkout). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33452476 COMPONENT/ENTRY POINT: $$FILEHNC(DFN) COMPONENT DESCRIPTION: Entry point $$FILEHNC^DGNTAPI(DFN) will file a new record in the NOSE AND THROAT RADIUM HISTORY (#28.11) file if a previous record exists for the DFN and the internal value of the SCREENING STATUS field (#.03) is equal to "3", indicating "PENDING DIAGNOSIS". The new record will consist of data from the previous record plus the following fields and values: Field# Field Name Field Value ------ --------------------- ------------------- 2.01 HEAD/NECK CA DX "Y" 2.02 DATE/TIME DX VERIFIED $$NOW^XLFDT 2.03 DX VERIFIED BY DUZ 2.04 SITE VERIFYING DX $P($$SITE^VASITE,U) Example of use: -------------- I $$FILEHNC^DGNTAPI(DFN) W !,"Verified HEAD/NECK CA DX has been filed." VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of patient in the PATIENT File (#2) VARIABLES: $$FILEHNC TYPE: Output VARIABLES DESCRIPTION: IEN of new entry in NOSE AND THROAT RADIUM HISTORY (#28.11) file 0 - if no previous record exists in the NOSE AND THROAT RADIUM HISTORY (#28.11) for the DFN or the internal value of the SCREENING STATUS field (#.03) is not equal to "3". 0^error message - if an error occurred during the filing of the new record in the NOSE AND THROAT RADIUM HISTORY (#28.11) file. SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER ISC: Albany NUMBER: 3457 IA #: 3457 DATE CREATED: SEP 18, 2001 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGNTAPI NAME: DBIA3457 ID: DGNTAPI GENERAL DESCRIPTION: The purpose of this API is to facilitate the retrieval of veterans' Nose/Throat Radium (NTR) Treatment information from the NOSE AND THROAT RADIUM HISTORY (#28.11) file. The primary mechanism is within the Registration package. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33452477 COMPONENT/ENTRY POINT: $$GETCUR(DFN,TARGET_ROOT) COMPONENT DESCRIPTION: The $$GETCUR^DGNTAPI(DFN,TARGET_ROOT) entry point will be used to obtain a patient's primary/current record from the NOSE AND THROAT RADIUM HISTORY (#28.11) file and place it in the local target array, TARGET_ROOT, passed as a closed root reference. Example of use: -------------- I $$GETCUR^DGNTAPI(DFN,"DGNT") D . W !,"DGNT array now contains patient's primary NTR record." VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of patient in the PATIENT File (#2) VARIABLES: $$GETCUR TYPE: Output VARIABLES DESCRIPTION: IEN of primary entry in NOSE AND THROAT RADIUM HISTORY File (#28.11) "0"- If no NTR history entry is found for the patient. VARIABLES: TARGET_ROOT TYPE: Both VARIABLES DESCRIPTION: Input: (Optional) Target Array name that should be passed as a closed root reference. If the parameter is not passed, then the default TARGET_ROOT is set equal to "DGNTAPI". Output: The output array is in the format of TARGET_ROOT(subscript) with subscript being derived from the following table: subscript field name field val --------- -------------- --------- "DFN" Patient internal "IND" NTR Indicator int^ext "STAT" Screening Status int^ext "NTR" NTR Treatment int^ext "AVI" Aviator Pre 1/31/55 int^ext "SUB" Submarin Pre 1/1/65 int^ext "EDT" Date/Time NTR Enter internal "EUSR" NTR Entered By internal "PRIM" NTR Primary Entry internal "SUPER" Date/Time Supersede internal "VER" Verification Method int^ext "VDT" Date/Time Verified internal "VUSR" Verified By internal "VSIT" Site Verifying Doc internal "HNC" Head/Neck CA DX int^ext "HDT" Date/Time DX Verif internal "HUSR" DX Verified By internal "HSIT" Site Verifying DX internal NUMBER: 3458 IA #: 3458 DATE CREATED: SEP 25, 2001 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORQOR2 NAME: OUTPATIENT PHARMACY ORDER STATUS ID: ORQOR2 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33475721 COMPONENT/ENTRY POINT: $$STATUS(ORN) COMPONENT DESCRIPTION: This entry point will be used by Outpatient Pharmacy to get the Pharmacy order status from the ORDER file (#100). VARIABLES: ORN TYPE: Input VARIABLES DESCRIPTION: The PLACER ORDER # field (#39.3) of the PRESCRIPTION file (#52) which is the internal entry number of the ORDER file (#100). (Required) VARIABLES: $$STATUS TYPE: Output VARIABLES DESCRIPTION: Returns the current status of an order in the format: STATUS^STATUS DESCRIPTION STATUS is the STATUS field (#5) of the ORDER file (#100), a pointer to the ORDER STATUS file (#100.01). SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING NUMBER: 3459 IA #: 3459 DATE CREATED: SEP 25, 2001 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSBMLHS NAME: PSB MEDICATION HISTORY REPORT ID: PSBMLHS GENERAL DESCRIPTION: The purpose of this agreement is to provide other packages with the ability to call the BCMA Medication History report. It returns a report of medications a patient has received by orderable item. This DBIA is for BCMA Version 2.0 only. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33473562 KEYWORDS: PSB KEYWORDS: BCMA COMPONENT/ENTRY POINT: HISTORY VARIABLES: RESULTS TYPE: Input VARIABLES DESCRIPTION: The name of the array that the output ispassed in. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Patient IEN number. VARIABLES: PSBOI TYPE: Input VARIABLES DESCRIPTION: Orderable Item number. NUMBER: 3460 IA #: 3460 FILE NUMBER: 8925 GLOBAL ROOT: TIU(8925 DATE CREATED: SEP 26, 2001 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TIU pointer validation ID: TIU(8925 GLOBAL REFERENCE: TIU(8925, FIELD NUMBER: 2 FIELD NAME: DFN LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33481674 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring NUMBER: 3461 IA #: 3461 FILE NUMBER: 8925.91 GLOBAL ROOT: TIU(8925.91, DATE CREATED: SEP 26, 2001 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TIU pointer validation ID: TIU(8925.91, GLOBAL REFERENCE: TIU(8925.91, FIELD NUMBER: .01 FIELD NAME: DOCUMENT LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: .02 FIELD NAME: IMAGE LOCATION: 0;2 ACCESS: Read w/Fileman GLOBAL REFERENCE: TIU(8925.91,'B', GLOBAL DESCRIPTION: Direct global read of "B" x-ref approved. GENERAL DESCRIPTION: The Text Integration Utilities application grants Imaging permission to read data in file 8925.91. At the time of image acquisition on the DICOM gateway, the only piece of information sent with the image is the associated TIU note entry in file 8925. The gateway needs to determine if an Imaging pointer exists for this document in file 8925.91. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 36050035 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging is reading information from file TIU EXTERNAL DATA LINK (#8925.91). SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING NUMBER: 3462 IA #: 3462 DATE CREATED: OCT 01, 2001 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSOCPIB NAME: DBIA3462 ID: PSOCPIB GENERAL DESCRIPTION: A private IA for IB to call PSO to make them aware of a billing event that has taken place. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33507678 COMPONENT/ENTRY POINT: PSOCPIB COMPONENT DESCRIPTION: Top level entry into routine. VARIABLES: Y(1) TYPE: Input VARIABLES DESCRIPTION: IB will have the variable Y(1) defined with the following pieces: 1st piece = date/time 2nd piece = user causing the update 3rd piece = prescription number 4th piece = fill/refill number 5th piece = partial/full billing flag 6th piece = IB number SUBSCRIBING PACKAGE: INTEGRATED BILLING NUMBER: 3463 IA #: 3463 FILE NUMBER: 100 GLOBAL ROOT: OR( DATE CREATED: OCT 02, 2001 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PHARMACY ORDER DISCONTINUED DATE/TIME ID: OR( GLOBAL REFERENCE: OR(100, FIELD NUMBER: 63 FIELD NAME: DC DATE/TIME LOCATION: 6;3 ACCESS: Direct Global R/W & w/Fileman FIELD DESCRIPTION: This is the exact date/time the order was discontinued. FIELD NUMBER: 31 FIELD NAME: DATE OF LAST ACTIVITY LOCATION: 3;1 ACCESS: Direct Global R/W & w/Fileman FIELD NUMBER: 12 FIELD NAME: PACKAGE LOCATION: 0;14 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 33 FIELD NAME: PACKAGE REFERENCE LOCATION: 4;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Outpatient Pharmacy package request permission to access the ORDER file (#100). Outpatient Pharmacy option, the Expire Prescriptions [PSO EXPIRE PRESCRIPTIONS], routine PSOHLEXP, flags prescriptions that have passed the expire date as expired and sends an HL7 message across to CPRS to flag those prescriptions as expired. Recently we noticed that it not only sends the expire message for expired prescriptions but also for discontinued prescriptions, and as a result in CPRS the discontinued prescriptions are flagged as expired, which is incorrect. Outpatient Pharmacy will correct the statuses of all those prescriptions in CPRS from expired status to discontinued status. This will be a one-time request. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33794771 SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY ISC: Birmingham NUMBER: 3464 IA #: 3464 FILE NUMBER: 772 GLOBAL ROOT: HL(772 DATE CREATED: OCT 03, 2001 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: HL(772 Diagnostic Utility ID: HL(772 GLOBAL REFERENCE: HL(772,'B', GLOBAL DESCRIPTION: "B" CROSS REFERENCE GLOBAL REFERENCE: HL(772, FIELD NUMBER: 200 FIELD NAME: MESSAGE TEXT LOCATION: IN;0 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .01 FIELD NAME: DATE/TIME ENTERED LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 4 FIELD NAME: TRANSMISSION TYPE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 10 FIELD NAME: RELATED EVENT PROTOCOL LOCATION: 0;10 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 20 FIELD NAME: STATUS LOCATION: P;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 21 FIELD NAME: DATE/TIME PROCESSED LOCATION: P;2 ACCESS: Direct Global Read & w/Fileman GLOBAL DESCRIPTION: From the message text multiple, examine the following segments. From the PID segment, get the ICN and the patient DFN. From the QAK segment, get the patient DFN. From the RDT segment, get the ICN. From the VTQ segment, get the SSN. From the MFE segment, for MAD or MUP, get the ICN. GENERAL DESCRIPTION: This IA supports a diagnostic utility used for problem resolution with messaging issues associated with HL7 data transmissions for MPI/PD. The tool will be available for diagnostic purposes as needed by the development team or NVS. The utility compiles data from the HL7 MESSAGE TEXT (#772) file for a selected date range. Each HL7 message in the date range is examined. If the RELATED EVENT PROTOCOL (#10) field contains the MPI/PD protocols (e.g., ""VAF"", ""RG"", or ""MPI"") data is stored in the ^XTMP("RGMT","HL" array. A cross-reference is built on patient ICN and DFN for faster data retrieval for the associated reports. Direct global reads are necessary for efficiency and speed for the data compilation process. A number of diagnostic reports are generated from the compiled data including the following. HL7 Activity by Patient for a Single Protocol for Date Range HL7 Activity by Patient for All MPI/PD Protocols for Date Range HL7 Message Status Summary Report (total number of messages for each date in range, transmission type, and status) Detailed HL7 Message Status Report STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33511198 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK ISC: Birmingham SUBSCRIBING PACKAGE: MASTER PATIENT INDEX NUMBER: 3465 IA #: 3465 FILE NUMBER: 63 GLOBAL ROOT: LR( DATE CREATED: OCT 16, 2001 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Clinical Registries ID: LR( GLOBAL REFERENCE: LR( FIELD NUMBER: 11 FIELD NAME: AUTOPSY DATE/TIME LOCATION: AU;1 ACCESS: Read w/Fileman FIELD NUMBER: 14.1 FIELD NAME: LOCATION LOCATION: AU;5 ACCESS: Read w/Fileman FIELD NUMBER: 14 FIELD NAME: AUTOPSY ACC # LOCATION: AU;6 ACCESS: Read w/Fileman FIELD NUMBER: 12.1 FIELD NAME: PHYSICIAN LOCATION: AU;12 ACCESS: Read w/Fileman FIELD NUMBER: 13.1 FIELD NAME: DATE FINAL AUTOPSY DIAGNOSES LOCATION: AU;4 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 14.5 FIELD NAME: SERVICE LOCATION: AU;8 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 32.2 FIELD NAME: CLINICAL DIAGNOSES LOCATION: 81;0 ACCESS: Read w/Fileman FIELD NUMBER: 32.3 FIELD NAME: PATHOLOGICAL DIAGNOSES LOCATION: 82;0 ACCESS: Read w/Fileman FIELD NUMBER: 14.7 FIELD NAME: AUTOPSY RELEASE DATE/TIME LOCATION: AU;15 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Clinical Registries package requires the ability to send Autopsy data to the national registry. Therefore access to the ^LR(D0,"AU" node is required. 1) Access Autopsy node: ^LR(D0,"AU") - ("AU";1)("AU";5)("AU";6)("AU";12) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33570653 KEYWORDS: Clinical Registries. SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES ISC: Hines NUMBER: 3466 IA #: 3466 DATE CREATED: OCT 05, 2001 CUSTODIAL PACKAGE: GENERIC CODE SHEET CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GECSSTAA NAME: DBIA3466-A ORIGINAL NUMBER: 3466 ID: GECSSTAA GENERAL DESCRIPTION: This IA allows a package to set a key for easily looking up a Generic Code Sheet Stack File document in file 2100.1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33528650 KEYWORDS: SETKEY COMPONENT/ENTRY POINT: SETKEY(A,B) COMPONENT DESCRIPTION: Call this entry point to set the key lookup in file 2100.1. VARIABLES: A TYPE: Output VARIABLES DESCRIPTION: the internal entry number in file 2100.1 that will be returned fro the key when looked up. VARIABLES: B TYPE: Input VARIABLES DESCRIPTION: the key to lookup used to look up the entry. SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Albany NUMBER: 3467 IA #: 3467 DATE CREATED: OCT 05, 2001 CUSTODIAL PACKAGE: GENERIC CODE SHEET CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GECSSGET NAME: DBIA3466-B ORIGINAL NUMBER: 3466 ID: GECSSGET GENERAL DESCRIPTION: This IA allows a package to lookup a Generic Code Sheet Stack File document in file 2100.1 based on a key set by SETKEY^GECSSTAA. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33528654 KEYWORDS: KEYLOOK COMPONENT/ENTRY POINT: KEYLOOK(A,B) COMPONENT DESCRIPTION: Call this entry point to lookup a Generic Code Sheet Stack File document in file 2100.1. The internal entry number of the document will be returned in the GECSDATA variable. VARIABLES: A TYPE: Input VARIABLES DESCRIPTION: the key to pass for looking up a document. VARIABLES: B TYPE: Input VARIABLES DESCRIPTION: a flag. If it is passed as a number, the code sheet for the document found using the key will be returned in the GECSDATA array. If variable B is passed as a 0, the code sheet data will not be returned in the GECSDATA array. SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE ISC: Albany NUMBER: 3468 IA #: 3468 DATE CREATED: OCT 10, 2001 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCCP NAME: CLINICAL PROCEDURE UTILITIES ID: GMRCCP CREATOR: ACKERMAN,NIEN-CHIN GENERAL DESCRIPTION: This integration agreement describes several utilities used to gather information or update Consult records involved in the Clinical Procedures interface to Consult/Request Tracking. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33544530 COMPONENT/ENTRY POINT: CPLIST(GMRCPT,GMRCPR,GMRCRET) COMPONENT DESCRIPTION: This entry point returns a list of Clincial Procedure requests on file for a given patient. VARIABLES: GMRCPT TYPE: Input VARIABLES DESCRIPTION: This is the patient identifier (DFN). VARIABLES: GMRCPR TYPE: Input VARIABLES DESCRIPTION: This optional variable is a pointer to the CP DEFINITION (#702.01) file. If this variable is not passed, all CP requests will be returned. VARIABLES: GMRCRET TYPE: Output VARIABLES DESCRIPTION: This required variable is the name of a global array in which to return the list of CP requests for a patient. The array is returned in the format: ^global(array)= a^b^c^d^e^f where: a=date of request b=CP DEFINITION name c=urgency d=status e=consult ien from file 123 f=CP DEFINITION ien COMPONENT/ENTRY POINT: $$CPDOC(GMRCDA,TIUDA,ACTION) COMPONENT DESCRIPTION: This entry point updates REQUEST/CONSULTATION (#123) file entries by attaching a TIU document as a result. VARIABLES: GMRCDA TYPE: Input VARIABLES DESCRIPTION: This required variable is the file 123 ien. VARIABLES: TIUDA TYPE: Input VARIABLES DESCRIPTION: This required variable is the ien from the TIU DOCUMENT (#8925) file that is to be updated in the consult request (GMRCDA). VARIABLES: ACTION TYPE: Input VARIABLES DESCRIPTION: This required variable is teh activity to take on the consult using the TIU document. The only current implementation is the value of 2 which will update the consult to partial results and attach the TIU document with the Clinical Procedure request. VARIABLES: $$CPDOC TYPE: Output VARIABLES DESCRIPTION: This output variable will return: 1 = successful 0^error = unsuccessful^problem COMPONENT/ENTRY POINT: $$CPLINK(PROC) COMPONENT DESCRIPTION: This entry point is used to determine if a given CP DEFINITION (#702.01) file entry is linked to any entry in the GMRC PROCEDURE (#123.3) file. VARIABLES: PROC TYPE: Input VARIABLES DESCRIPTION: This required variable is a pointer to the CP DEFINITION (#702.01) file. VARIABLES: $$CPLINK TYPE: Output VARIABLES DESCRIPTION: The output of this entry point will be in the form: 1 = currently linked to a GMRC PROCEDURE (#123.3) file entry 0 = not currently linked to a GMRC PROCEDURE (#123.3) file entry COMPONENT/ENTRY POINT: CPLINKS(.NAMES,PROC) COMPONENT DESCRIPTION: This entry point returns a list of the GMRC PROCEDURE (#123.3) file entries linked to a given CP DEFINITION. VARIABLES: NAMES TYPE: Output VARIABLES DESCRIPTION: This variable is passed by reference and is returned as array of GMRC PROCEDUREs linked to a given CP DEFINITION in format: NAMES(x)=GMRC PROCEDURE name^GMRC PROCEDURE ien NAMES(1)="EKG^21" NAMES(2)="EKG PORTABLE^32" if not currently linked, returned as: NAMES(1)="-1^not currently linked" VARIABLES: PROC TYPE: Input VARIABLES DESCRIPTION: This required variable is pointer to the CP DEFINITION (#702.01) file. COMPONENT/ENTRY POINT: $$CPROC(PROC) COMPONENT DESCRIPTION: This entry point returns the CP Definition that is mapped to an orderable procedure. VARIABLES: PROC TYPE: Input VARIABLE SEQUENCE NUMBER: 1 VARIABLES DESCRIPTION: This required variable is a point to the GMRC Procedure (#123.3) file. VARIABLES: $$CPROC TYPE: Output VARIABLE SEQUENCE NUMBER: 1 VARIABLES DESCRIPTION: The output to this entry point is 0 or the pointer to the CP Definition (#702.01) file. SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Hines SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring DATE ACTIVATED: MAR 19, 2008 DATE/TIME EDITED: MAR 19, 2008@17:18 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: ACKERMAN,SHIRLEY WITH CONCURRENCE OF: THOMPSON,WILLIAM DATE/TIME EDITED: MAR 19, 2008@17:19 ACTION: APPROVED AT THE REQUEST OF: ACKERMAN,SHIRLEY WITH CONCURRENCE OF: THOMPSON,WILLIAM NUMBER: 3469 IA #: 3469 DATE CREATED: OCT 11, 2001 CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RGJUSITE NAME: RGJUSITE ID: RGJUSITE GENERAL DESCRIPTION: This function call is used to determine if the MPI/PD messages should be fired. It will check the STOP MPI/PD MESSAGING (#16) field in the CIRN SITE PARAMETER (#991.8) file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33551494 COMPONENT/ENTRY POINT: SEND() VARIABLES: STOP TYPE: Output VARIABLES DESCRIPTION: This function returns a zero if the messages are to be stopped. A positive one is returned if the messages are not to be stopped. A two is returned for suspend. SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA NUMBER: 3470 IA #: 3470 DATE CREATED: OCT 18, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGPMV NAME: DBIA3470 ID: DGPMV GENERAL DESCRIPTION: Incomplete Records Tracking requests access to the Patient Movement routine DGPMV. IRT Enter/Edit screen contains a Treating Specialty Update protocol which calls CA^DGPMV. This protocol is the action to update the Treating Specialty and Primary and Attending physicians for the IRT package and ADT without exiting the IRT enter/edit option. VIEWER: MARKS,MARY STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33679403 COMPONENT/ENTRY POINT: CA VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN is set to the patient number. VARIABLES: DGPMT TYPE: Input VARIABLES DESCRIPTION: DGPMT is the Patient Movement type (set to 6 = Treating Specialty Transfer). VARIABLES: DGPMCA TYPE: Input VARIABLES DESCRIPTION: DGPMCA is the Patient Movement coresponding Admission. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Y is set to the Patient Movement entry added/edited. SUBSCRIBING PACKAGE: INCOMPLETE RECORDS TRACKING NUMBER: 3471 IA #: 3471 DATE CREATED: OCT 19, 2001 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: HLCSAC NAME: HLCSAC ID: HLCSAC STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33581905 COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: This function is for use by the MPI application at each medical center to send HL7 messages over a direct connection to the MPI. The communication protocol that this function utilizes is proprietary. Therefore, this function is not recommended for use by any other application. Usage S returnval=$$EN^HLCSAC(loglink,input,output) If the function is fully successful, the return value will be 0(zero). Otherwise, a non-zero followed by an error message text will be returned in a format similar to "-1^error message". VARIABLES: loglink TYPE: Input VARIABLES DESCRIPTION: Logical Link Name or IEN VARIABLES: input TYPE: Input VARIABLES DESCRIPTION: A clossed root representing an array containing message segments to be sent VARIABLES: output TYPE: Output VARIABLES DESCRIPTION: A closed root representing an array containing message segments returned SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA NUMBER: 3472 IA #: 3472 DATE CREATED: OCT 24, 2001 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCCP NAME: TIU use of GMRCCP ID: GMRCCP GENERAL DESCRIPTION: This integration agreement describes calls used by TIU in GMRCCP. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33599798 COMPONENT/ENTRY POINT: $$CPACTM(GMRCDA) COMPONENT DESCRIPTION: This function returns the actions available for a CP request. VARIABLES: GMRCDA TYPE: Input VARIABLES DESCRIPTION: This required variable is the Request/Consultation file (#123) IEN. VARIABLES: $$CPACTM TYPE: Output VARIABLES DESCRIPTION: The output value of this function will return the following: 0 = not a CP request or TIU*1*109 not present 1 = CP request but no instrument report expected 2 = CP and still waiting on instr. or images 3 = CP and incomplete CP doc attached 4 = CP and complete CP doc attached COMPONENT/ENTRY POINT: $$CPPAT(GMRCDA,GMRCDFN) COMPONENT DESCRIPTION: This function returns whether or not a patient is an object of the specified request. VARIABLES: GMRCDA TYPE: Input VARIABLES DESCRIPTION: This required variable is the Request/Consultation file (#123) IEN. VARIABLES: GMRCDFN TYPE: Input VARIABLES DESCRIPTION: This required variable is the Patient file (#2) IEN. VARIABLES: $$CPPAT TYPE: Output VARIABLES DESCRIPTION: The output value of this function will return the following: 1 = patient is object of request GMRCDA 0 = patient is NOT object of request in GMRCDA COMPONENT/ENTRY POINT: $$CPINTERP(GMRCTIU,GMRCUSER) COMPONENT DESCRIPTION: This function returns whether or not a user is an interpreter for a specified TIU document. VARIABLES: GMRCTIU TYPE: Input VARIABLES DESCRIPTION: This required variable is the TIU Document file (#8925) IEN. VARIABLES: GMRCUSER TYPE: Input VARIABLES DESCRIPTION: This required variable is the New Person file (#200) IEN. VARIABLES: $$CPINTERP TYPE: Output VARIABLES DESCRIPTION: The output value of this function will return the following: 1 = GMRCUSER is an interpreter 0 = GMRCUSER is NOT an interpreter SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING DETAILS: TIU calls $$CPACTM^GMRCCP to check the status of the consult as it related to Clinical Procedures (CP). TIU calls $$CPPAT^GMRCCP to check if the patient is associated with the consult. TIU calls $$CPINTERP^GMRCCP to see if a person can be an Interpreter for a particular document. EDITOR: RUTHERFORD,JERALD F NUMBER: 3473 IA #: 3473 DATE CREATED: OCT 26, 2001 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCTIU NAME: TIU use of GMRCTIU ID: GMRCTIU GENERAL DESCRIPTION: This integration agreement describes calls used by TIU in GMRCTIU. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34485454 COMPONENT/ENTRY POINT: SEND(DFN,OVERRIDE,CP) COMPONENT DESCRIPTION: This procedure gets a list of consults for a patient and returns them in ^TMP. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: This required variable is the Patient file (#2) IEN. VARIABLES: OVRRIDE TYPE: Input VARIABLES DESCRIPTION: This optional variable is a boolean flag to override user validation. VARIABLES: CP TYPE: Input VARIABLES DESCRIPTION: This optional variable is set to 1 if only entries that have CP documents attached should be returned. COMPONENT/ENTRY POINT: GET(GMRC0,GMRCTUFN,GMRCTUST,GMRCAUTH) COMPONENT DESCRIPTION: Update Consult from TIU. VARIABLES: GMRC0 TYPE: Input VARIABLES DESCRIPTION: This required variable is the Request/Consultation file (#123) IEN. VARIABLES: GMRCTUFN TYPE: Input VARIABLES DESCRIPTION: This required variable is the TIU Document file (#8925) IEN. VARIABLES: GMRCTUST TYPE: Input VARIABLES DESCRIPTION: This required variable is the TIU status of report. VARIABLES: GMRCAUTH TYPE: Input VARIABLES DESCRIPTION: This optional variable is the Author of the document. SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING DETAILS: TIU calls $$SEND^GMRCTIU to get a list of consult requests for a patient. TIU calls GET^GMRCTIU to update the Consult from TIU. EDITOR: RUTHERFORD,JERALD F NUMBER: 3475 IA #: 3475 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: NOV 05, 2001 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3475 ID: DPT( GLOBAL REFERENCE: DPT(D0,.322) FIELD NUMBER: .322013 FIELD NAME: ENVIRONMENTAL CONTAMINANTS? LOCATION: .322;13 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The purpose of this DBIA is to allow Surgery to display the patient's status related to environmental contaminants for patients having ambulatory surgery. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33662374 SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 3476 IA #: 3476 DATE CREATED: NOV 05, 2001 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DIEZ NAME: Template uncompile using DIEZ ID: DIEZ GENERAL DESCRIPTION: Registration request permission to un-compile Templates using the un-supported DIEZ call UNC^DIEZ(IEN). The IEN of the Template will be located by the supported call FIND1^DIC. EX: IEN=$$FIND1^DIC(.402,"","X","DVBA C ADD 2507 PAT) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33664427 KEYWORDS: UNC KEYWORDS: DIEZ KEYWORDS: UNC DIEZ COMPONENT/ENTRY POINT: UNC SUBSCRIBING PACKAGE: REGISTRATION ISC: Albany NUMBER: 3477 IA #: 3477 FILE NUMBER: 130 GLOBAL ROOT: SRF( DATE CREATED: NOV 06, 2001 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TIU Uploads to SURGERY file ID: SRF( GLOBAL REFERENCE: SRF(DA, FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .09 FIELD NAME: DATE OF OPERATION LOCATION: 0;9 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 1.15 FIELD NAME: SURGEON'S DICTATION LOCATION: 12;0 ACCESS: Write w/Fileman GENERAL DESCRIPTION: This DBIA documents references from TIU upload routines to the SURGERY (#130), for upload of Surgeon's Dictation into the SURGERY file. VIEWER: MONOSKY,ALAN VIEWER: MONTALI,MICHAEL STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33655623 KEYWORDS: UPLOAD SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING DETAILS: When the TIU-SURGERY interface patch (#TIU*1*112) is released, this agreement will no longer be needed (at least not in its current form), since sites will be uploading into the TIU DOCUMENT file instead of the SURGERY file. NUMBER: 3478 IA #: 3478 DATE CREATED: NOV 15, 2001 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSODRG NAME: PSODRG ID: PSODRG GENERAL DESCRIPTION: Allows CPRS to use EN^PSODRG to obtain information regarding lab tests linked to clozapine medications. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33719466 KEYWORDS: CLOZAPINE KEYWORDS: PSODRG COMPONENT/ENTRY POINT: EN(drug) COMPONENT DESCRIPTION: Information is returned in "LAB": LAB("NOT")=0 if medication is not clozapine LAB("BAD TEST")=0 if one or both lab tests aren't mapped LAB("ANC")=Lab file {#61} ien of ANC^Topography (specimen) file [#61] ien LAB("WBC")=Lab file {#61} ien of WBC^Topography (specimen) file [#61] ien Example: LAB("ANC")=1250^70 LAB("WBC")=1^70 VARIABLES: drug TYPE: Input VARIABLES DESCRIPTION: "drug" is the internal entry number of clozapine medication from the Drug fiile [#50]. VARIABLES: LAB TYPE: Output VARIABLES DESCRIPTION: LAB("NOT")=0 if medication is not clozapine LAB("BAD TEST")=0 if one or both lab tests aren't mapped LAB("ANC")=Lab file {#61} ien of ANC^Topography (specimen) file [#61] ien LAB("WBC")=Lab file {#61} ien of WBC^Topography (specimen) file [#61] ien Example: LAB("ANC")=1250^70 LAB("WBC")=1^70 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3481 IA #: 3481 DATE CREATED: NOV 23, 2001 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTR NAME: SC 0% NON COMPENSABLE ID: DGMTR GENERAL DESCRIPTION: For the Long Term Care Copay initiative IB has a requirement to determine if a patient is SC 0% non-compensable. Currently we are calling $$SC^DGMTR(DFN) to make that determination. VIEWER: NGHIEM,JOHN A STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33821247 COMPONENT/ENTRY POINT: SC COMPONENT DESCRIPTION: Pass in the DFN to $$SC^DGMTR(DFN) returns "1" for yes and a "0" for no. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN is the internal entry number to file 2 Patient File. SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: SCHEDULING DBA Comments: Richard Curtis, a VistA Maintenance developer identified that a pending ICR needed to be updated. On June 4, 2012, in response to not holding up a VistA Maintenance patch release for SD*5.3*585, this DBIA was updated to reflect the Scheduling package is and has been a subscriber. This DBIA was marked as Withdrawn for some unknown reason. We have no history to indicate why it was marked Withdrawn. In order to reflect the proper status of released software, the status was changed to Active. DATE ACTIVATED: JUN 04, 2012 DATE/TIME EDITED: JUN 04, 2012@12:40 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CURTIS,RICHARD WITH CONCURRENCE OF: BEUSCHEL,GARY NUMBER: 3484 IA #: 3484 DATE CREATED: NOV 26, 2001 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: HLUCM NAME: HL7 Capacity Management Phase I API ID: HLUCM GENERAL DESCRIPTION: Returns Health Level 7 (HL7) activity totals for a parameter-supplied time range. Additional control over the HL7 activity included in the totals is available using passed parameters. (See HL*1.6*103 for additional information.) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33755789 KEYWORDS: HL7 KEYWORDS: CM KEYWORDS: CAPACITY MANAGEMENT COMPONENT/ENTRY POINT: $$CM COMPONENT DESCRIPTION: The syntax for the $$CM call point is: $$CM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) The passable parameters for this call pointer are explained below. SDT - Start date/time in Fileman format. (E.g., 3011123.1234) EDT - End date/time in Fileman format. NMSP - Namespace(s) of entries to be included. PROT - Protocol(s) to be included. SAVE - Free text name of inital subscript in ^TMP(SAVE,$j) global created by this call point. COND - Conditions under which matching entries are to be collected. ERR - Location for error information returned by the $$CM call point. ERR is passed by reference. The above information regarding the $$CM call point is provided as an overview of its capabilities. Refer to the documentation included in patch HL*1.6*103 for complete explanation. VARIABLES: $$CM TYPE: Output VARIABLES DESCRIPTION: Calling $$CM^HLUCM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) returns a 3 piece string of data. The pieces of data are: Piece 1 = Number of characters in all messages found by the API call. Piece 2 = Number of messages found by the API call. Piece 3 = Total transmission and receipt time for all messages found by API call. Calling $$CM^HLUCM returns this 3 piece string of data. In addition, when the API is called, it creates some ^TMP global data holding additional information about the messages found. Full information about the global created can be found in the patch HL*1.6*103 documentation. However, a brief overview of the data structure is provided below. The fifth parameter passed into the $$CM^HLUCM API is SAVE. This parameter specifies the initial subscript to be used in the ^TMP global data. (See the SAVE variable for more information.) For example, if the save parameter is passed as "DATA", the ^TMP global data is stored in ^TMP("DATA",$J,...). The ^TMP global data created by the $$CM^HLUCM call point is subdivided (by sorting subscripts) into the following sections: Totals by transmission time, namespace, and protocol. Totals by namespace, incoming/outgoing, namespace, transmission time, and protocol. Totals by namepsace, local/remote, namespace, transmission time, and protocol. Totals by protocol, namespace, and time. To explain the above information more fully, consider the last entry. What this means is that totals are sorted by protocol, and within protocol the totals are sorted by namespace, and within namespace the totals are sorted by transmission time. Example data, and additional explanation of the global data created by the API is in patch HL*1.6*103. VARIABLES: SDT (parameter 1) TYPE: Input VARIABLES DESCRIPTION: The syntax for the $$CM call point is: $$CM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) The first parameter, SDT, is the start time in Fileman format. An example call is shown below. W $$CM^HLUCM(3011123.12,3011123.13,"DG","VAFH A08","DATA","BOTH",.ERR) In this example, SDT has the value of 3011123.12. VARIABLES: EDT (parameter 2) TYPE: Input VARIABLES DESCRIPTION: The syntax for the $$CM call point is: $$CM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) The second parameter, EDT, is the end time in Fileman format. An example call is shown below. W $$CM^HLUCM(3011123.12,3011123.13,"DG","VAFH A08","DATA","BOTH",.ERR) In this example, EDT has the value of 3011123.13. VARIABLES: NMSP (parameter 3) TYPE: Input VARIABLES DESCRIPTION: The syntax for the $$CM call point is: $$CM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) The third parameter, NMSP, is the NAMESPACE of the entry(s) to be included. An example call is shown below. W $$CM^HLUCM(3011123.12,3011123.13,"DG","VAFH A08","DATA","BOTH",.ERR) In this example, NMSP has the value of "DG". See patch HL*1.6*103 documentation for additional details. VARIABLES: PROT (parameter 4) TYPE: Input VARIABLES DESCRIPTION: The syntax for the $$CM call point is: $$CM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) The fourth parameter, PROT, is the PROTOCOL of the entry(s) to be included. An example call is shown below. W $$CM^HLUCM(3011123.12,3011123.13,"DG","VAFH A08","DATA","BOTH",.ERR) In this example, PROT has the value of "VAFH A08". See patch HL*1.6*103 documentation for additional details. VARIABLES: SAVE (parameter 5) TYPE: Input VARIABLES DESCRIPTION: The syntax for the $$CM call point is: $$CM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) The fifth parameter, SAVE, is the initial subscript to use in the ^TMP global data. An example call is shown below. W $$CM^HLUCM(3011123.12,3011123.13,"DG","VAFH A08","DATA","BOTH",.ERR) In this example, SAVE has the value of "DATA". This would cause the Creation of ^TMP("DATA",$J) data. VARIABLES: COND (parameter 6) TYPE: Input VARIABLES DESCRIPTION: The syntax for the $$CM call point is: $$CM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) The sixth parameter, COND, defines criteria to be used when searching For messages. An example call is shown below. W $$CM^HLUCM(3011123.12,3011123.13,"DG","VAFH A08","DATA","BOTH",.ERR) In this example, COND has the value of "BOTH". Passing the value of "BOTH" requires that each message has to have a namespace of "DG" and a protocol of "VAFH A08." In other words, 'both' the namespace and the protocol values have to be true before a message is counted. Instead of "BOTH", the value of "EITHER" can be passed. In the above Example, if "EITHER" had been passed as the value of COND, then Messages will be counted if 'either' the namespace is "DG" or the Protocol is "VAFH A08." In other words, if either criteria is Matched, a message is counted. See patch HL*1.6*103 documentation for addition information. VARIABLES: ERR (parameter 7) TYPE: Output VARIABLES DESCRIPTION: The syntax for the $$CM call point is: $$CM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) The sixth parameter, COND, defines criteria to be used when searching For messages. An example call is shown below. W $$CM^HLUCM(3011123.12,3011123.13,"DG","VAFH A08","DATA","BOTH",.ERR) In this example, ERR is passed by reference. No data is present in The ERR array prior to the call, (and even if it did, the ERR local Array is killed as one of the initial API actions, in order to ensure That the ERR array is empty at the start of processing.) If any Problems are encountered by the API, such as passing in invalid Parameter values, information about the error(s) is placed in the ERR local array and "passed back" to the calling process. See patch HL*1.6*103 documentation for addition information. NUMBER: 3485 IA #: 3485 FILE NUMBER: 58.84 GLOBAL ROOT: PSD(58.84, DATE CREATED: NOV 28, 2001 CUSTODIAL PACKAGE: DRUG ACCOUNTABILITY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3485 ID: PSD(58.84, GLOBAL REFERENCE: PSD(58.84,D0,0) FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Direct Global R/W & w/Fileman GENERAL DESCRIPTION: This is an open agreement between Drug Accountability and Controlled Substances. The terms of this agreement are to allow Controlled Substances access to the NAME (#.01) field in the DRUG ACCOUNTABILITY TRANSACTION TYPE file (#58.84). The method of access can be either Direct Read/Write or by using Filemanager. The reason for this agreement is that prior to the release of Drug Accountability 3.0, this file was the property of Controlled Substances. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33765695 SUBSCRIBING PACKAGE: CONTROLLED SUBSTANCES ISC: Birmingham NUMBER: 3486 IA #: 3486 DATE CREATED: FEB 05, 2004 CUSTODIAL PACKAGE: CORBA SERVICES USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: OMGCOAS1 NAME: IAS FOR OMGCOAS1 ID: OMGCOAS1 GENERAL DESCRIPTION: This API is invoked by the server code for Remote Data Views to request Department of Defense patient data through Station 200 to the FHIE Framework system. The DoD data is retrieved and placed in the common CPRS Remote Data View format. STATUS: Active MAIL MESSAGE: 33921863 COMPONENT/ENTRY POINT: GCPR((IEN,DATATYPE,BEGDATE,ENDDATE,ORMAX) COMPONENT DESCRIPTION: MAKE REQUEST FOR DATA FROM THE FRAMEWORK. Invocation: D GCPR^OMGCOAS1(IEN,DATATYPE,BEGDATE,ENDDATE,ORMAX) Parameters: IEN: Patient IEN DATATYPE: Identifies requested report. Datatypes currently supported: LRO - Lab Orders LRC - Chem & Hem SP - Surgical Pathology CY - Cytology MI - Microbiology RR - Radiology Report RXA - Active Outpatient RX RXOP- All Outpatient RX ADT - Admission/Discharge/Transfer Summary DS - Discharge Summary ALRG - Allergies CONS - Consult Report SADR - Standard Ambulatory Data BEGDATE: Starting date for report (Fileman internal) ENDDATE: Ending date for report (Fileman internal) ORMAX: Maximum number of observations to retrieve Output: Results are returned in nodes of the ^TMP global specific to the requested report, e.g. ^TMP("ORDATA",$J) for ADT. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: Patient IEN VARIABLES: DATATYPE TYPE: Input VARIABLES DESCRIPTION: LRO - Lab Orders LRC - Chem & Hem SP - Surgical Pathology CY - Cytology MI - Microbiology RR - Radiology Report RXA - Active Outpatient RX RXOP- All Outpatient RX ADT - Admission/Discharge/Transfer Summary DS - Discharge Summary ALRG - Allergies CONS - Consult Report SADR - Standard Ambulatory Data VARIABLES: BEGDATE TYPE: Input VARIABLES DESCRIPTION: Starting date for report (Fileman internal format) VARIABLES: ENDDATE TYPE: Input VARIABLES DESCRIPTION: Ending date for report (Fileman internal format) VARIABLES: ORMAX TYPE: Input VARIABLES DESCRIPTION: Maximum number of observations to retrieve VARIABLES: ~TMP("ORDATA",$J, TYPE: Output VARIABLES DESCRIPTION: 1.1.1.1 Output The CPRS Remote Data View server code expects the DoD data to be populated in ^TMP global nodes. The output generated by calls to GCPR^OMGCOAS1 is described in the following sections for each of the supported data partitions. In each section, the global nodes in ^TMP populated by the call are identified, and the data fields stored into these nodes are defined and mapped to elements in one of the data model templates maintained by the NGIT Framework. The following templates are used: LAB Laboratory data LabWebTopTemplate0204 RAD Radiology data RadWebTopTemplate0102 MED Medications data MedWebTopTemplate0205 ENC Patient Encounter data PatientEncounterTemplate0102 WL Working List data WorkingListTemplate0101 CONS Consults data ConsultsTemplate0101 The CORBA request for DoD data may fail with an exception status. If so, an error message is written to the global output node in ^TMP that would otherwise contain the Facility name. The most common cause of an exception is failure to connect to the Framework, in which case the error message should appear as: Unable to connect to DoD repository. Please contact the National Help Desk at 1-888-596-HELP (4357). 1.1.1.1.1 Chemistry and Hematology Data (LRC): ^TMP("LRC",$J,IDT,CNT)=CDT^SPC^TST^RSL^FLG^UNT^LO^HI where: IDT = Inverse collection date/time CND = Print order sequence number from file 60 CDT = Count value for observations SPC = Specimen for lab order in an external printable form TST = Lab test ordered in a external printable form RSL = Numeric result of test FLG = Reference flag (H, *H,L,*L). UNT = Unit of measure (external format). LO = Reference/Therapeutic Lower bound. HI= Reference/Therapeutic Upper bound. ^TMP("LRC ,$J,IDT, C )=Comments ^TMP("LRO",$J,IDT,CNT,"facility")=Facility 1.1.1.1.1 Standard Lab Orders Data (LRO): ^TMP("LRO",$J,IDT,cnt)=CDT^TST^SPC^URG^OS^MD^ODT^ACC^RDT^COL where: IDT = Inverse collection date/time of order. cnt = Count value for observations. CDT = Collection date/time of order. TST = Lab test ordered. Variable format A;B where A=internal pointer, B=external text. SPC = Specimen. Variable format A;B where A=internal pointer, B=external text. URG = Urgency of lab order. OS = Status of lab order. MD = Provider. Variable format A;B where A=internal pointer, B=external text. ODT = Date/Time lab ordered. ACC = Accession number of lab order. RDT = Date/Time results for this lab order available. COL = Lab or ward collect. ^TMP("LRO",$J,IDT,SN_FN,"facility")=Facility 1.1.1.1.1 Surgical Pathology Data: ^TMP("LRA",$J,IDT,0) = ^ ^TMP("LRA",$J,IDT,.1) = "Site/Specimen"^ ^TMP("LRA",$J,IDT,.1,sub1) = .: ^TMP("LRA",$J,IDT,1.4,sub2) = ^TMP("LRA",$J,IDT,"facility") = 1.1.1.1.1 Cytopathology Data: ^TMP("LRCY",$J,IDT,0) = ^ ^TMP("LRCY",$J,IDT,1) = "Site/Specimen"^ ^TMP("LRCY",$J,IDT,1,sub1) = .: ^TMP("LRCY",$J,IDT,"NDX",sub2) = ^TMP("LRCY",$J,IDT,"facility") = 1.1.1.1.1 Microbiology Data: ^TMP("LRM",$J,RPT,SS)=CDT^ACC^CS^SS^TST^RSTA ^TMP("LRM",$J,RPT,SS,"RPT",n)=OC^ON^OQ ;organism category^name^quantity ^TMP("LRM",$J,RPT,SS,"RPT",n,ant)=ANTN^SEN^INT ^TMP("LRM",$J,RPT,SS,"REPORT ,n)=text line of formatted report based on "RPT nodes ^TMP("LRM",$J,RPT,SS,"facility")=Facility where: RPT = Inverse report date/time SS = subscript value CDT = Collection date/time ACC = Accession CS = Collection Sample SS = Specimen TST = Lab Test Ordered RSTA = Report Status ANTN = Antibiotic name SEN = Sensitivity INT = Interpretation 1.1.1.1.1 Radiology Report Data: Global variable definitions: GMTSIDT = reverse exam date/time ^TMP("RAE",$J,GMTSIDT,sub1,0)= ^ ^ ^ ^ ^ ^ ^ ^ ^TMP("RAE",$J, GMTSIDT,sub1,"facility") = ^TMP("RAE",$J, GMTSIDT,sub1,"H",sub2) = ^TMP("RAE",$J, GMTSIDT,sub1,"R",sub2) = report text line, where report text is formatted as follows: Exm Date: Req Phys: Pat Loc: Img Loc: Service: Exam: CPT: Report Status: Date verified: Report: Reason for order: Order Comment: 1.1.1.1.1 All Outpatient RX Data This call is to be used when requesting Outpatient RX data from the FHIE Framework for display through CPRS. ^TMP("PSOO",$J,IFD,0)=ID^FD^DR^PR^ST^RX^QT^RF^EX Where: IFD = Inverse last fill date of Rx. ID = Issue date of Rx. FD = Last fill date of Rx. DR = Drug in Rx. Variable format A;B where A=internal pointer, B=external text. PR = Provider. Variable format A;B where A=internal pointer, B=external text. ST = Status of Rx. Variable format A;B where A=internal pointer, B=external text. RX = Rx number. QT = Quantity of DRG in Rx. RF = Number of refills remaining. EX = Expire/Cancel date of Rx. SIG = Medication instruction for this Rx. Output: ^TMP("PSOO",$J,IFD,n,0)=SIG ^TMP("PSOO",$J,IFD,"facility") = Facility [#Facility number] [,Phone number] 1.1.1.1.1 Discharge Summary report This call is to be used when requesting Discharge Summary data from the FHIE Framework for display through CPRS. The DoD Discharge Summary report will be formatted and passed in the HL7 message to the FHIE framework in formatted form. The report information is retrieved and displayed in the CPRS report exactly as formatted by the DoD CHCS I site. ^TMP("ORDATA",$J,IDT, WP ,1)=1^Facility name ^TMP("ORDATA",$J, IDT, WP ,2)=2^Admitted date/time ^TMP("ORDATA",$J, IDT, WP ,3)=3^Discharge date/time ^TMP("ORDATA",$J, IDT, WP ,4)=4^Author/Dictated by ^TMP("ORDATA",$J, IDT, WP ,5)=5^Approved by ^TMP("ORDATA",$J, IDT, WP ,6)=6^Status ^TMP("ORDATA",$J, IDT,"WP",9,report line number)=9^Report text lines 1.1.1.1.1 ADT Summary report This call is to be used when requesting ADTdata from the FHIE Framework for display through CPRS. The DoD ADT Summary information is passed to the FHIE framework through the appropriate ADT HL7 messages. The data is parsed and formatted into the appropriate ADT summary report consistent with CPRS Remote Data Views. ^TMP("ORDATA",$J,IDT,report line count)=report text line Report Format: DOB: Provider/Specialty: Attending/Ward: Admitting DX: Bed Section: LOS: DXLS: ICD DX: Disposition Place: Admitting Procedures: Procedure Procedure << repeats with multiple observations>> 1.1.1.1.1 Allergy report This call is to be used when requesting Allergy data from the FHIE Framework for display through CPRS. The DoD ADT Summary information is passed to the FHIE framework through the appropriate HL7 messages. The data is parsed and formatted into the appropriate Allergy summary report consistent with CPRS Remote Data Views. ^TMP("ORDATA",$J,IDT,"WP",1)=1^Facility Name ^TMP("ORDATA",$J,IDT,"WP",2)=2^Characteristic Observed (Allergy Reactant) ^TMP("ORDATA",$J,IDT,"WP",3)=3^Allergy Type ^TMP("ORDATA",$J,IDT,"WP",4)=4^ ^TMP("ORDATA",$J,IDT,"WP",5)=5^ ^TMP("ORDATA",$J,IDT,"WP",6,report line number)=6^Comments 1.1.1.1.1 Consult Report This call is to be used when requesting Allergy data from the FHIE Framework for display through CPRS. The DoD ADT Summary information is passed to the FHIE framework through the appropriate HL7 messages. The data is parsed and formatted into the appropriate Allergy summary report consistent with CPRS Remote Data Views. ^TMP("ORDATA",$J,IDT,"WP",1)=1^Facility Name ^TMP("ORDATA",$J,IDT,"WP",2)=2^Request Date ^TMP("ORDATA",$J,IDT,"WP",3)=3^Completion Date ^TMP("ORDATA",$J,IDT,"WP",4)=4^Consult Service ^TMP("ORDATA",$J,IDT,"WP",5)=5^Status ^TMP("ORDATA",$J,IDT,"WP",6)=6^Procedure Type ^TMP("ORDATA",$J,IDT,"WP",7,report line number)=7^Consult Report Text Lines 1.1.1.1.1 SADR Report This call is to be used when requesting this SADR (Standard Ambulatory Data Record) data from the FHIE Framework for display through CPRS. The DoD SADR information is passed to the FHIE framework through the appropriate SADR HL7 messages. The data is parsed and formatted into a SADR report consistent with CPRS Remote Data Views. ^TMP("ORDATA",$J,IDT, WP ,report line count) = report text lines Report Format: Date Facility Hospital Location Encounter Provider ID: PCM Code: Diagnosis: ... Procedure: ... E and M: << Diagnoses and procedures repeat for multiple occurrences in the data>> SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING DETAILS: ADDED 5/26/09 DATE/TIME EDITED: MAY 26, 2009@13:01 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: LOUCK,KEVIN WITH CONCURRENCE OF: BAYLIS,RANDALL NUMBER: 3487 IA #: 3487 FILE NUMBER: 142.1 GLOBAL ROOT: GMT(142.1, DATE CREATED: JAN 08, 2002 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Supported TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: HEALTH SUMMARY COMPONENT FILE #142.1 ID: GMT(142.1, GLOBAL REFERENCE: GMT(142.1, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: PRINT ROUTINE LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: TIME LIMITS APPLICABLE LOCATION: 0;3 ACCESS: Read w/Fileman FIELD NUMBER: 3 FIELD NAME: ABBREVIATION LOCATION: 0;4 ACCESS: Read w/Fileman FIELD NUMBER: 4 FIELD NAME: MAXIMUM OCCURRENCES APPLICABLE LOCATION: 0;5 ACCESS: Read w/Fileman FIELD NUMBER: 5 FIELD NAME: DISABLE FLAG LOCATION: 0;6 ACCESS: Read w/Fileman FIELD NUMBER: 6 FIELD NAME: LOCK LOCATION: 0;7 ACCESS: Read w/Fileman FIELD NUMBER: 8 FIELD NAME: OUT OF ORDER MESSAGE LOCATION: 0;8 ACCESS: Read w/Fileman FIELD NUMBER: 9 FIELD NAME: DEFAULT HEADER NAME LOCATION: 0;9 ACCESS: Read w/Fileman FIELD NUMBER: 10 FIELD NAME: HOSPITAL LOCATION APPLICABLE LOCATION: 0;10 ACCESS: Read w/Fileman FIELD NUMBER: 11 FIELD NAME: ICD TEXT APPLICABLE LOCATION: 0;11 ACCESS: Read w/Fileman FIELD NUMBER: 12 FIELD NAME: PROVIDER NARRATIVE APPLICABLE LOCATION: 0;12 ACCESS: Read w/Fileman FIELD NUMBER: 13 FIELD NAME: PREFIX LOCATION: 0;13 ACCESS: Read w/Fileman FIELD NUMBER: 14 FIELD NAME: CPT MODIFIER APPLICABLE LOCATION: 0;14 ACCESS: Read w/Fileman GLOBAL REFERENCE: GMT(142.1,D0,.1, FIELD NUMBER: .01 FIELD NAME: EXTERNAL/EXTRACT ROUTINE LOCATION: 0;1 ACCESS: Read w/Fileman GLOBAL REFERENCE: GMT(142.1,D0,1, FIELD NUMBER: .01 FIELD NAME: SELECTION FILE LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: SELECTION COUNT LIMIT LOCATION: 0;2 ACCESS: Read w/Fileman GLOBAL REFERENCE: GMT(142.1,D0,3.5, FIELD NUMBER: .01 FIELD NAME: DESCRIPTION LOCATION: 0;1 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33919033 NUMBER: 3488 IA #: 3488 DATE CREATED: DEC 03, 2001 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: HLUCM NAME: HL7 Capacity Management Phase II API ID: HLUCM GENERAL DESCRIPTION: Returns Health Level 7 (HL7) activity totals for a parameter-supplied time range. Additional control over the Hl7 activity included in the totals is available using passed parameters. (See HL*1.6*103 for additional information.) COMPARISON OF $$CM & $$CM2: --------------------------- Patch HL*1.6*79 holds phase I software, and is associated with DBIA# 3484. Phase I software is almost identical to phase II software, except in the number of "messages" returned by the two APIs. The call point for DBIA# 3484 - phase I software - is $$CM^HLUCM. The call point for this DBIA - phase II software - is $$CM2^HLUCM. $$CM^HLUCM returns the number of discrete message occurring during a parameter-defined period of time. $$CM2^HLUCM returns the number of "message units" during the same period of time. All other totals returned by both parameters are identical. A message is an individual message, such as an application acknowledgement. A message unit is made up of all related messages. The difference between a message (phase I, $$CM^HLUCM) and a message unit (phase II, $$CM2^HLUCM) can be illustrated using the following sequence of events. * Baltimore sends a message to Washington. * Washington sends back a commit acknowledgement to Baltimore. * Washington sends an application acknowledgement to Washington. * Baltimore sends back to Washington a commit acknowledgement for the just sent application acknowledgement. In the above example, $$CM^HLUCM would report a count of 4 messages. $$CM2^HLUCM would report a count of 1 message, or "message unit." (Since all 4 messages are "related", they are combined into one reported "message.") STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33789973 KEYWORDS: HL7 KEYWORDS: CM KEYWORDS: CAPACITY MANAGEMENT COMPONENT/ENTRY POINT: $$CM2 COMPONENT DESCRIPTION: The syntax for the $$CM2 call point is: $$CM2(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) The passable parameters for this call pointer are explained below. SDT - Start date/time in Fileman format. (E.g., 3011123.1234) EDT - End date/time in Fileman format. NMSP - Namespace(s) of entries to be included. PROT - Protocol(s) to be included. SAVE - Free text name of inital subscript in ^TMP(SAVE,$j) global created by this call point. COND - Conditions under which matching entries are to be collected. ERR - Location for error information returned by the $$CM call point. ERR is passed by reference. The above information regarding the $$CM2 call point is provided as an overview of its capabilities. Refer to the documentation included in patch HL*1.6*103 for complete explanation. VARIABLES: $$CM2 TYPE: Output VARIABLES DESCRIPTION: Calling $$CM2^HLUCM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) returns a 3 piece string of data. The pieces of data are: Piece 1 = Number of characters in all messages found by the API call. Piece 2 = Number of message units found by the API call. Piece 3 = Total transmission and receipt time for all message units found by API call. Calling $$CM2^HLUCM returns this 3 piece string of data. In addition, when the API is called, it creates some ^TMP global data holding additional information about the messages found. Full information about the global created can be found in the patch HL*1.6*103 documentation. However, a brief overview of the data structure is provided below. The fifth parameter passed into the $$CM2^HLUCM API is SAVE. This parameter specifies the initial subscript to be used in the ^TMP global data. (See the SAVE variable for more information.) For example, if the save parameter is passed as "DATA", the ^TMP global data is stored in ^TMP("DATA",$J,...). The ^TMP global data created by the $$CM2^HLUCM call point is subdivided (by sorting subscripts) into the following sections: Totals by transmission time, namespace, and protocol. Totals by namespace, incoming/outgoing, namespace, transmission time, and protocol. Totals by namepsace, local/remote, namespace, transmission time, and protocol. Totals by protocol, namespace, and time. To explain the above information more fully, consider the last entry. What this means is that totals are sorted by protocol, and within protocol the totals are sorted by namespace, and within namespace the totals are sorted by transmission time. Example data, and additional explanation of the global data created by the API is in patch HL*1.6*103. VARIABLES: SDT TYPE: Input VARIABLES DESCRIPTION: The syntax for the $$CM2 call point is: $$CM2(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) The first parameter, SDT, is the start time in Fileman format. An example call is shown below. W $$CM2^HLUCM(3011123.12,3011123.13,"DG","VAFHA08","DATA","BOTH",.ERR) In this example, SDT has the value of 3011123.12. VARIABLES: EDT TYPE: Input VARIABLES DESCRIPTION: The syntax for the $$CM2 call point is: $$CM2(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) The second parameter, EDT, is the end time in Fileman format. An example call is shown below. W $$CM2^HLUCM(3011123.12,3011123.13,"DG","VAFHA08","DATA","BOTH",.ERR) In this example, EDT has the value of 3011123.13. VARIABLES: NMSP TYPE: Input VARIABLES DESCRIPTION: The syntax for the $$CM2 call point is: $$CM2(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) The third parameter, NMSP, is the NAMESPACE of the entry(s) to be included. An example call is shown below. W $$CM2^HLUCM(3011123.12,3011123.13,"DG","VAFHA08","DATA","BOTH",.ERR) In this example, NMSP has the value of "DG". See patch HL*1.6*103 documentation for additional details. VARIABLES: PROT TYPE: Input VARIABLES DESCRIPTION: The syntax for the $$CM2 call point is: $$CM2(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) The fourth parameter, PROT, is the PROTOCOL of the entry(s) to be included. An example call is shown below. W $$CM2^HLUCM(3011123.12,3011123.13,"DG","VAFHA08","DATA","BOTH",.ERR) In this example, PROT has the value of "VAFH A08". See patch HL*1.6*103 documentation for additional details. VARIABLES: SAVE TYPE: Input VARIABLES DESCRIPTION: The syntax for the $$CM2 call point is: $$CM2(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) The fifth parameter, SAVE, is the initial subscript to use in the ^TMP global data. An example call is shown below. W $$CM2^HLUCM(3011123.12,3011123.13,"DG","VAFH A08","DATA","BOTH",.ERR) In this example, SAVE has the value of "DATA". This would cause the creation of ^TMP("DATA",$J) data. VARIABLES: COND TYPE: Input VARIABLES DESCRIPTION: The syntax for the $$CM2 call point is: $$CM2(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) The sixth parameter, COND, defines criteria to be used when searching for messages. An example call is shown below. W $$CM2^HLUCM(3011123.12,3011123.13,"DG","VAFH A08","DATA","BOTH",.ERR) In this example, COND has the value of "BOTH". Passing the value of "BOTH" requires that each message has to have a namespace of "DG" and a protocol of "VAFH A08." In other words, 'both' the namespace and the protocol values have to be true before a message is counted. Instead of "BOTH", the value of "EITHER" can be passed. In the above example, if "EITHER" had been passed as the value of COND, then messages will be counted if 'either' the namespace is "DG" or the protocol is "VAFH A08." In other words, if either criteria is matched, a message is counted. See patch HL*1.6*103 documentation for addition information. VARIABLES: ERR TYPE: Output VARIABLES DESCRIPTION: The syntax for the $$CM2 call point is: $$CM2(SDT,EDT,NMSP,PROT,SAVE,COND,ERR) The seventh parameter, ERR, is the location for error information returned by the $$CM2 call. Here is an example call: W $$CM2^HLUCM(3011123.12,3011123.13,"DG","VAFH A08","DATA","BOTH",.ERR) In this example, ERR is passed by reference. No data is present in the ERR array prior to the call, (and even if it did, the ERR local array is killed as oneof the initial API actions, in order to ensure that the ERR array is empty at the start of processing.) If any problems are encountered by the API, such as passing in invalid parameter values, information about the error(s) is placed in the ERR local array and "passed back" to the calling process. See patch HL*1.6*103 documentation for addition information. NUMBER: 3489 IA #: 3489 FILE NUMBER: 13 GLOBAL ROOT: DIC(13 DATE CREATED: DEC 04, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3489 ID: DIC(13 GLOBAL REFERENCE: DIC(13,D0,0 => CODE FIELD NUMBER: 3 FIELD NAME: CODE LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: A direct read is used to display the CODE (#3) field if the zero node exists using $DATA on the zero node. VIEWER: MARKS,MARY STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34120090 SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL NUMBER: 3491 IA #: 3491 FILE NUMBER: 40.7 GLOBAL ROOT: DIC(40.7 DATE CREATED: DEC 07, 2001 CUSTODIAL PACKAGE: SCHEDULING CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3491 ID: DIC(40.7 GLOBAL REFERENCE: DIC(40.7, FIELD NUMBER: .01 FIELD NAME: NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 1 FIELD NAME: AMIS REPORTING STOP CODE LOCATION: 0;2 ACCESS: Read w/Fileman FIELD NUMBER: 2 FIELD NAME: INACTIVE DATE LOCATION: 0;3 ACCESS: Read w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33807665 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany NUMBER: 3492 IA #: 3492 DATE CREATED: DEC 12, 2001 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFCPID2 NAME: NAME VAFCPID2 ID: VAFCPID2 GENERAL DESCRIPTION: Master Patient Index VistA application would like to formalize the use of this API for standardization of the name as was done in patch DG*5.3*149 for transmission of patient names to the MPI in the query messages and for comparing existing names to MPI names. No updates to the patient file name would occur during this process. STATUS: Active MAIL MESSAGE: 33825676 COMPONENT/ENTRY POINT: NAME COMPONENT DESCRIPTION: NAME(DFN,MPISTR,FLG) DFN - ien from Patient file MPISTR - name as stored in Patient file FLG - DON'T updated in patient file (default is not to update) - 1="Y", 0=" N" VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Internal entry number of the patient in the patient file. VARIABLES: MPISTR TYPE: Both VARIABLES DESCRIPTION: Initially, this variable is passed into the routine as the patient's name to be standardized. Upon existing the routine, this variable contains the standardized version of the name. VARIABLES: FLG TYPE: Input VARIABLES DESCRIPTION: This field is to denote wether of not the Patient file entry should be updated. Initially that was an option -- currently this field should never be yes. SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA NUMBER: 3493 IA #: 3493 DATE CREATED: DEC 12, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFCDD01 NAME: VAFCDD01 ID: VAFCDD01 GENERAL DESCRIPTION: Master Patient Index VistA would like to formalize the DBIA with Registration for use of AVAFC and XMITFLAG entry points for VAFCDD01. AVAFC - is being used to create an A08 message when the data on the ICN has been correlated but not updated on the site and then the site changes data but the update is not transmitted to the other sites and the MPI. XMITFLAG - is being used to set the REQUIRES TRANSMISSION field in the ADT/HL7 PIVOT file used in conjunction with the $$PIVNW^VAFHPIVT call to create a Treating Facility update entry in the ADT/HL7 PIVOT file. STATUS: Active MAIL MESSAGE: 33786492 COMPONENT/ENTRY POINT: AVAFC COMPONENT DESCRIPTION: This API creates an A08 entry in the ADT/HL7 PIVOT file. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: DFN is the internal entry number of the patient in the patient file that the A08 update is to be created for. COMPONENT/ENTRY POINT: XMITFLAG COMPONENT DESCRIPTION: Turn transmission flag for entry in ADT/HL7 PIVOT file on/off. VARIABLES: PIVOTPTR TYPE: Input VARIABLES DESCRIPTION: - Pointer to entry in ADT/HL7 PIVOT file (#391.71) - Use this parameter if the entry number is known - Not required if using PIVOTNUM parameter - Use of this parameter takes precedence over use the PIVOTNUM parameter VARIABLES: PIVOTNUM TYPE: Input VARIABLES DESCRIPTION: PIVOT NUMBER value (field #.02) for entry in ADT/HL7 PIVOT file (#391.71) - Use this parameter if the pivot number is known - Not required if using PIVOTPTR parameter VARIABLES: TURNOFF TYPE: Input VARIABLES DESCRIPTION: Denotes if REQUIRES TRANSMISSION field (#.08) should be turned on (set to 'YES') or off (set to 'NO') 1 = Turns transmission off 0 = Turns transmission on (default) SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA NUMBER: 3494 IA #: 3494 DATE CREATED: DEC 12, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFHPIVT NAME: VAFHPIVT ID: VAFHPIVT GENERAL DESCRIPTION: This function returns 0 node of the ADT/HL7 Pivot file and ADT/HL7 Pivot file entry number, if no entry in the if no entry in pivot file, create one and return #:0 node STATUS: Active MAIL MESSAGE: 33825885 COMPONENT/ENTRY POINT: $$PIVNW COMPONENT DESCRIPTION: This function returns 0 node of the ADT/HL7 Pivot file and ADT/HL7 Pivot file entry number, if no entry in the if no entry in pivot file, create one and return #:0 node VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The internal entry number of the patient to be added to the pivot file. VARIABLES: EVDT TYPE: Input VARIABLES DESCRIPTION: This the the event date/time (time is optional). VARIABLES: EVTY TYPE: Input VARIABLES DESCRIPTION: This is the event type - in our case for the treating facility update message it would be a 5. VARIABLES: PTR TYPE: Input VARIABLES DESCRIPTION: This is the variable pointer - in our case to the patient file. SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA NUMBER: 3495 IA #: 3495 DATE CREATED: DEC 13, 2001 CUSTODIAL PACKAGE: CORBA SERVICES USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: OMGPID01 NAME: IAS FOR OMGPID01 ID: OMGPID01 GENERAL DESCRIPTION: NEWGCPR^OMGPID01 is the API that the MPI code calls when a new patient is added to the VA MPI. This API performs the findOrRegisterIds interface to the Framework for patient correlation. It is the reverse of the findCandidates interface. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33921775 COMPONENT/ENTRY POINT: NEWGCPR COMPONENT DESCRIPTION: THIS API PERFORMS THE findOrRegisterids interface to the Framework for patient correlation. VARIABLES: IEN TYPE: Input VARIABLES DESCRIPTION: INTERNAL ENTRY NUMBER OF THE PATIENT BEING ADDED TO THE MPI. SUBSCRIBING PACKAGE: MASTER PATIENT INDEX NUMBER: 3496 IA #: 3496 DATE CREATED: DEC 19, 2001 CUSTODIAL PACKAGE: REGISTRATION USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: VAFC REMOTE PDAT REMOTE PROCEDURE: VAFC REMOTE PDAT GENERAL DESCRIPTION: MPI/PD developers request the use of the VAFC REMOTE PDAT remote procedure call distributed in patch DG*5.3*414. This remote procedure call returns the text Patient MPI/PD Data Inquiry report to a remote site. Usage: I +LOC>0 D EN1^XWB2HL7(.RETURN,LOC,"VAFC REMOTE PDAT",1,ICN,"") STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33770270 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: MASTER PATIENT INDEX SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA NUMBER: 3497 IA #: 3497 GLOBAL ROOT: XTMP( DATE CREATED: DEC 19, 2001 CUSTODIAL PACKAGE: DRUG ACCOUNTABILITY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: CSLPHAR NAME: coreFLS/Pharmacy Interface ID: CSLPHAR GLOBAL REFERENCE: XTMP('PSAPUSH', GLOBAL DESCRIPTION: This temprary global will store the content of a pharmacy order receipt. GENERAL DESCRIPTION: Define the use of ^XTMP("PSAPUSH") in the coreFLS/Pharmacy interface. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33858153 KEYWORDS: CSLPHAR COMPONENT/ENTRY POINT: CSLPHAR COMPONENT DESCRIPTION: Parse coreFLS receipt message into ^XTMP("PSAPUSH") which will be used by VistA Drug Accountability package. VARIABLES: XTMP TYPE: Output VARIABLES DESCRIPTION: The coreFLS receipt information will be parsed into ^XTMP("PSAPUSH") in the following format: ^XTMP("PSAPUSH",0) = Kernel Purge Date ^ Today's Date ^XTMP("PSAPUSH",$H,PO#,Receipt#) = Vendor Name ^ PO Date ^ Date Received ^ Pharmacy Location ^ Transaction Type ^ (Null) ^ Ship to Address ^ Revision# ^XTMP("PSAPUSH",$H,PO#,Receipt#,Line#,1) = Item Number ^ Item Description ^ Packaging Multiple (Ordered) ^XTMP("PSAPUSH",$H,PO#,Receipt#,Line#,2) = Controlled Substances Flag ^ Quantity Received ^ Unit of Measure (Received) ^ Packaging Multiple (Received) ^ National Drug Code ^ Purchase Order Quantity ^ Unit Price ^ Vendor Stock Number ^ Unit of Measure (Ordered) ** Receipt# = OrgID_"-"_Receipt# SUBSCRIBING PACKAGE: COMMUNICATIONS SERVICE LIBRARY ISC: Washington/Silver Spring EDITOR: SU,ALLEN NUMBER: 3498 IA #: 3498 DATE CREATED: DEC 26, 2001 CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: CSLSUR1 NAME: DBIA3498 ID: CSLSUR1 GENERAL DESCRIPTION: Build an SIU transaction of patient schedule to transmit to DynaMed. This function is meant to be called in foreground, not background as messages will be displayed to the user. If the transaction is built successfully, the function will display this fact with the Message Control ID. If the transaction cannot be built, the function will display the fact that nothing was built, and the reason this occurred. After the message displays, the user will be expected to hit the or key to continue. STATUS: Active MAIL MESSAGE: 34016627 KEYWORDS: CSLSUR1 KEYWORDS: CoreFLS COMPONENT/ENTRY POINT: $$BLDSEG(1) COMPONENT DESCRIPTION: NOTE: ^TMP("CSLSUR1",$J) will be killed by this call VARIABLES: $$BLDMSG TYPE: Output VARIABLES DESCRIPTION: 0 - Case was not successfully set up in HL7 ^ Reason 1 - Case was set up successfully in HL7 VARIABLES: global TMP('CSLSUR1',$J, TYPE: Input VARIABLES DESCRIPTION: Node Value ---------- ---------------------------------------------------- 1 Surgical Case Number 2 Patient's ID ^ Patient ICN 3 Event Type: 1- New, 2- Edit, 3- Cancel, 4- Delete 4 Start Date and Time ^ End Date and Time ^ Date of Operation 5,0 Surgeon's free text description of the Principal Procedure (up to 135 char) 5,1 Principal CPT Code ^ Name associated with the Principal CPT Code 5,1,1-n CPT Code Modifier Code ^ CPT Code Modifier Name 5,2-n Other CPT Code ^ Other CPT Code Name 5,2-n,1-n CPT Code Modifier Code ^ CPT Code Modifier Name 6 Surgeon ID ^ Surgeon's Name 7 Surgical Specialty ID ^ Surgical Specialty Name 8 Local Surgical Specialty ID ^ Local Surgical Specialty Name 9 Operating Room Code/ID ^ Operating Room Name 10,1-n SPD Comment lines 1 through n, each line 80 characters max 11 Hospital ID (pointer to file #4 Institution File) 12 ID of Requestor ^Name of Requestor 13 ID of Person who enters/edits schedule ^ Name 14 Patient Type: I- Inpatient, O- Outpatient 15 Time Stamp (Time event occurred in the application) 16 Attending Surgeon ID (IEN in file 200) ^Surgeon Name note: ^TMP("CSLSUR1",$J) may be set to null on entry to the API with no negative effect. VARIABLES: 1 TYPE: Input VARIABLES DESCRIPTION: This parameter is required and it indicates the parameters are being passed in ^TMP("CSLSUR1",$J). At this time, this is always set to 1. SUBSCRIBING PACKAGE: SURGERY NUMBER: 3499 IA #: 3499 DATE CREATED: JAN 14, 2002 CUSTODIAL PACKAGE: ENROLLMENT APPLICATION SYSTEM CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: EASMTCHK NAME: DBIA3499 ID: EASMTCHK GENERAL DESCRIPTION: The purpose of this API is to facilitate the check for a required means test for a veteran during appointment management. A deficiency noted in the "Report of Task Force to Review Enrollment, Means Testing and Income Verification", item #22, required VHA to identify a means to acquire veterans' signatures on means tests at a local level. This API provides a procedure that when called will check on a veteran means test status and return a flag on whether a means test is required or not, and optionally, a related text message that can be displayed by the calling procedure. This API is provided in the Enrollment Application Systems namespace. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33955987 KEYWORDS: EAS KEYWORDS: APPOINTMENT BLOCKING COMPONENT/ENTRY POINT: MT(DFN,EASAPT,EASACT,EASDT,EASQT,EASMSG) COMPONENT DESCRIPTION: The MT^EASMTCHK entry point returns a flag and alert messgae if a means test update is required for the patient. If a means test update is not required, a "0" is returned. The IEN in the PATIENT File, #2, is passed into the call as variable DFN. If DFN is not populated, the call fails. EASAPT is the IEN of the Appointment type in the APPOINTMENT TYPE File, #409.1, and EASDT is the date of the appointment. If the Appointment type is not available, then the appointment date/time must be passed in. When the Appointment action flag is "C", the appointment date/time is used to lookup the appointment and determine the appointment type for the MT status determination. Normally either the appointment type or the appointment date/time will be available to the API. If one or the other is not passed in, the API will return "0". VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Contains the Internal Entry Number of the patient in the PATIENT File, #2. VARIABLES: EASAPT TYPE: Input VARIABLES DESCRIPTION: Contains the Internal Entry Number of the appointment type from the APPOINTMENT TYPE, File #409.1. Current requirements are for action only on "Regular" type appointments. VARIABLES: EASACT TYPE: Input VARIABLES DESCRIPTION: Appointment action flag [Optional]. Used to specify the appointment action being taken. If not specified, a default of "Other" is used. Walk-In and Other appointment actions will not block an appointment action, and may be used for returning a MT status message. M - Make an appointment C - Check In/Out an existing appointment W - Unscheduled/Walk-In appointment O - Other (Default) VARIABLES: EASDT TYPE: Input VARIABLES DESCRIPTION: Appointment Date/Time in FileMan format. If the appointment type is not available, then the appointment date/time must be passed. VARIABLES: EASMSG TYPE: Input VARIABLES DESCRIPTION: Return array for alert message [Optional], if defined, the alert text is copied to the array. Can be used in conjunction with EASQT to control how and when alert messages are displayed. VARIABLES: RSLT TYPE: Output VARIABLES DESCRIPTION: Outputcontains the results: 1 - MT Required 0 - MT Not required VARIABLES: EASQT TYPE: Input VARIABLES DESCRIPTION: Silent flag [Optional], if set, prevents display of alert message. NUMBER: 3500 IA #: 3500 FILE NUMBER: 52 GLOBAL ROOT: PSRX(D0 DATE CREATED: JAN 16, 2002 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PDM CONVERSION ACCESS ID: PSRX(D0 GLOBAL REFERENCE: PSRX(D0,2) FIELD NUMBER: 21 FIELD NAME: LOGIN DATE LOCATION: 2;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Pharmacy Data Management (PDM) requests a one-time DBIA with Outpatient Pharmacy to allow direct read access to the PRESCRIPTION file (#52), to retrieve the LOGIN DATE field (#21). As part of the Pharmacy Benefits Management project, PDM is processing through all Unit Dose, IV and Outpatient Pharmacy orders/prescriptions to find the first Pharmacy service date. In order to do this, PDM needs to be able to retrieve the login date information for a prescription. This will be in a multi-package build titled PSS PSJ PSO Service Date. STATUS: Active DURATION: Next Version EXPIRATION DATE: JUL 16, 2002 MAIL MESSAGE: 33972876 KEYWORDS: PSRX( SUBSCRIBING PACKAGE: PHARMACY DATA MANAGEMENT ISC: Birmingham NUMBER: 3501 IA #: 3501 FILE NUMBER: 52 GLOBAL ROOT: PSRX( DATE CREATED: JAN 17, 2002 CUSTODIAL PACKAGE: OUTPATIENT PHARMACY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3501 ID: PSRX( GLOBAL REFERENCE: PSRX( FIELD NUMBER: 20 FIELD NAME: DIVISION LOCATION: 2;9 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: PATIENT LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33974528 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham SUBSCRIBING DETAILS: The Pharmacy Benefits Management package extracts outpatient data monthly to support the VA National Formulary, disease management issues and patient safety initiatives. SUBSCRIBING PACKAGE: MYHEALTHEVET NUMBER: 3502 IA #: 3502 FILE NUMBER: 55 GLOBAL ROOT: PS(55 DATE CREATED: JAN 24, 2002 CUSTODIAL PACKAGE: PHARMACY DATA MANAGEMENT CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: PHARMACY DATA MANAGEMENT ID: PS(55 GLOBAL REFERENCE: PS(55 FIELD NUMBER: .07 FIELD NAME: FIRST SERVICE DATE LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .08 FIELD NAME: ACTUAL/HISTORICAL FLAG LOCATION: 0;8 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(55,D0,'IV',D1 FIELD NUMBER: 9 FIELD NAME: ORIGINAL WARD LOCATION: 2;10 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 68 FIELD NAME: LAST WARD LOCATION LOCATION: 0;23 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 104 FIELD NAME: WARD LOCATION: 0;22 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: PS(55,D0,5,'B',D1 GLOBAL DESCRIPTION: Order Number Cross Reference STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33962300 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham SUBSCRIBING DETAILS: The Pharmacy Benefits Management package extracts patient demographic, inpatient and outpatient data monthly to support the VA National Formulary, disease management issues and patient safety initiatives. The following read only information is needed for the extract: NUMBER: 3503 IA #: 3503 DATE CREATED: JAN 28, 2002 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGUTL2 NAME: PATIENT DATES OF LEAVE FOR A BILLING DATE RANGE ID: DGUTL2 GENERAL DESCRIPTION: Integrated Billing requires a list of the # of leave/pass and ASIH days in a billing cycle period and the start and end dates of each leave period used to compile this number. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34009161 COMPONENT/ENTRY POINT: APLD VARIABLES: DGPMCA TYPE: Input VARIABLES DESCRIPTION: Input variable containing the corresponding admission internal entry number. Variable is required and must contain a valid pointer to the Patient Movement (#405) file. VARIABLES: DGARR TYPE: Both VARIABLES DESCRIPTION: Required variable containing the output array name passed by reference. Function call returns a -1 if the required input parameters are missing or invalid. The following array is returned: DGARR(0)=Total days^Begin Date^Ending Date DGARR(Pointer to Patient Movement file)=Movement Start Date^Movement End Date^Total # of days^Movement type (P405.2)^RTN^Return movement type (P405.2)^Return movement IEN (P405) VARIABLES: DGBDT TYPE: Input VARIABLES DESCRIPTION: Required input variable containing the billing start date VARIABLES: DGEDT TYPE: Input VARIABLES DESCRIPTION: Required input variable containing the billing end date VARIABLES: DGMTYP TYPE: Input VARIABLES DESCRIPTION: Optional parameter containing requested movement types: A: ASIH movements only P: Pass and leave movements only B: Both (default) SUBSCRIBING PACKAGE: INTEGRATED BILLING EDITOR: HARRIS,JANET INTEGRATION REFERENCES LIST MAR 18,2015 11:24 PAGE 11 -------------------------------------------------------------------------------- NUMBER: 3504 IA #: 3504 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: JAN 30, 2002 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: 3504 ID: DPT( GLOBAL REFERENCE: DPT(D0 FIELD NUMBER: .6 FIELD NAME: TEST PATIENT INDICATOR LOCATION: 0;21 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Pharmacy Benefits Management package extracts patient demographic data monthly to support the VA National Formulary, disease management issues and patient safety initiatives. The following read only patient information is needed for the extract: STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33963549 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham NUMBER: 3505 IA #: 3505 FILE NUMBER: 79.2 GLOBAL ROOT: RA(79.2, DATE CREATED: JAN 30, 2002 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Imaging Type file ID: RA(79.2, GLOBAL REFERENCE: RA(79.2, FIELD NUMBER: .01 FIELD NAME: TYPE OF IMAGING LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Name of a type of imaging. FIELD NUMBER: 3 FIELD NAME: ABBREVIATION LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: The abbreviation associated with the type of imaging. GLOBAL REFERENCE: RA(79.2,'C',ABBREVIATION,DA GLOBAL DESCRIPTION: Allows for the look-up of an imaging location by abbreviation. GENERAL DESCRIPTION: Radiology gives Imaging permission to read file 79.2, IMAGING TYPE. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34022321 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging VistARad software provides the Radiologist an on-line worklist (patient exams) displayed on a VistARad workstation. The worklist should contain the Imaging type and its abbreviation for each exam. The information is located in the Imaging Type file (79.2) in fields .01 and 3. Imaging is requesting permission to read this information. SUBSCRIBING PACKAGE: VA POINT OF SERVICE (KIOSKS) SUBSCRIBING PACKAGE: CLINICAL REMINDERS DBA Comments: 10/9/14-MC: Added VPS as a subscriber as requested by Caroyln Wheless and approved by Greg Cebelinski for VPS*1*4. VPS needs to return patient radiology/imagig requests to VetLink, including fields .01 (TYPE OF IMAGING) and 3 (ABBREVIATION) from file #79.2 2/23/15-MC: Added PXRM (Clinical Reminders) as a subscriber to ICR at the request of Robert Ruff and approval of Greg Cebelinski for CPRS v31,patch PXRM*2*45. DATE/TIME EDITED: FEB 23, 2015@10:32 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: RUFF,ROBERT WITH CONCURRENCE OF: CEBELINSKI,GREG NUMBER: 3506 IA #: 3506 FILE NUMBER: 79 GLOBAL ROOT: RA(79 DATE CREATED: FEB 01, 2002 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Imaging (file 79) ID: RA(79 GLOBAL REFERENCE: RA(79,DA,.1 FIELD NUMBER: .12 FIELD NAME: PRINT FLASH CARD FOR EACH EXAM LOCATION: .1;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter to control the printing of flash card for each exam. FIELD NUMBER: .16 FIELD NAME: AUTO USER CODE FILING LOCATION: .1;6 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter to indicate that the user should be asked for their access code during the processing of exams and reports of which various activity logs are kept. FIELD NUMBER: .17 FIELD NAME: DETAILED PROCEDURE REQUIRED LOCATION: .1;7 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter that controls if the entry of a 'detailed', 'series' or 'parent' procedure type should be required during the initial exam registration or request. FIELD NUMBER: .18 FIELD NAME: PRINT JACKET LBLS W/EACH VISIT LOCATION: .1;8 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter controls the automatic printing of a jacket label during each visit. FIELD NUMBER: .19 FIELD NAME: ASK 'CAMERA/EQUIP/RM LOCATION: .1;9 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter controls whether during an exam edit if the camera/equip/rm is asked. FIELD NUMBER: .11 FIELD NAME: TRACK EXAM STATUS CHANGES LOCATION: .1;10 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter to control the collecting of the date and time of exam status changes. FIELD NUMBER: .111 FIELD NAME: ASK EXAM STATUS TIME LOCATION: .1;11 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter that controls the prompting for exact date/time of the exam status change. If this parameter is not set then defaults to current date/time. FIELD NUMBER: .112 FIELD NAME: ALLOW STANDARD REPORTS LOCATION: .1;12 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter controls whether a standard report can be selected during report entry/edit process. FIELD NUMBER: .113 FIELD NAME: ALLOW BATCHING OF REPORTS LOCATION: .1;13 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter that allows placing reports in a batch during report entry. FIELD NUMBER: .114 FIELD NAME: ALLOW COPYING OF REPORTS LOCATION: .1;14 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter that allow copying the contents of one report's text and impression into another. FIELD NUMBER: .116 FIELD NAME: IMPRESSION REQUIRED ON REPORTS LOCATION: .1;16 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter that controls if an impression is required to be given on a report before: 1) the report can be verified and 2) the exam can be considered 'complete'. FIELD NUMBER: .117 FIELD NAME: ASK 'REQUESTED DATE' LOCATION: .1;17 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter that controls if the transcriptionist should be prompted for the Desired Date for the exam. This field is set to 'YES' by the system. FIELD NUMBER: .118 FIELD NAME: ALLOW VERIFYING BY RESIDENTS LOCATION: .1;18 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter that controls if interpreting residents should be allowed to verify other interpreting physicians' reports. FIELD NUMBER: .119 FIELD NAME: TRACK REQUEST STATUS CHANGES LOCATION: .1;19 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter that controls collecting the date and the time of request status changes. FIELD NUMBER: .121 FIELD NAME: ASK 'IMAGING LOCATION' LOCATION: .1;21 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter that controls if the user should be asked when requesting an exam, which 'Imaging Location' the request should be forwarded to. FIELD NUMBER: .122 FIELD NAME: ALLOW RPTS ON CANCELLED CASES? LOCATION: .1;22 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter that controls if the user who does not have the RA MGR key may enter a report for an exam that has a status of CANCELLED. FIELD NUMBER: .124 FIELD NAME: TIME LIMIT FOR FUTURE EXAMS LOCATION: .1;24 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter that controls the number of hours in the future (0-168) that a user may register a patient for an exam. FIELD NUMBER: .125 FIELD NAME: WARNING ON RPTS NOT YET VERIF? LOCATION: .1;25 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter that controls the display of the 'report status' on reports in any status except 'Verified' will print the status surrounded by asterisks under the body of the report. FIELD NUMBER: .126 FIELD NAME: AUTO E-MAIL TO REQ. PHYS? LOCATION: .1;26 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter that controls automatically sending Requesting Physicians the radiology reports via e-mail. FIELD NUMBER: .127 FIELD NAME: ALLOW E-SIG ON COTS HL7 RPTS LOCATION: .1;27 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter that controls automatically adding the Electronic Signature Block printed name of the Verifying Physician that signed the report being transmitted to Rad/Nuc Med via an HL7 interface to a COTS voice reporting system. FIELD NUMBER: .128 FIELD NAME: INTERPRETING STAFF REQ'D? LOCATION: .1;28 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Division parameter that controls the required entry of 'PRIMARY INTERPRETING STAFF' to be mandatory when entering Diagnostic data or Reports. GENERAL DESCRIPTION: Radiology gives Imaging permission to read file 79, RAD/NUC MED DIVISION. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34051889 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging is referencing the .1 data node of file 79, RAD/NUC MED DIVISION. This is to set the variable RAMDV that is needed to execute the routine to update the exam's status to the next default exam status defined in the Radiology's Exam Status file. The RAMDV variable contains the Radiology Division entry's parameters that the module uses during various stages of exam and report processing and inquiring. These parameter switches allow the 'customizing' of the module for each division by the package coordinator. NUMBER: 3507 IA #: 3507 DATE CREATED: JAN 31, 2002 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RAUTL NAME: Imaging - RAUTL ID: RAUTL GENERAL DESCRIPTION: Radiology gives Imaging permission to execute D^RAUTL. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34023155 COMPONENT/ENTRY POINT: D COMPONENT DESCRIPTION: Utility to display the date and time in a readable format. VARIABLES: Y TYPE: Input VARIABLES DESCRIPTION: Y=internal Fileman format of date and time. SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: To be consistent with the display used throughout the Radiology application Imaging is calling D^RAUTL to output the date/time value. NUMBER: 3508 IA #: 3508 DATE CREATED: JAN 31, 2002 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RAUTL11 NAME: Imaging - RAUTL11 ID: RAUTL11 GENERAL DESCRIPTION: Radiology gives Imaging permission to execute SVTCOM^RAUTL11. STATUS: Active DURATION: Till Otherwise Agreed COMPONENT/ENTRY POINT: SVTCOM COMPONENT DESCRIPTION: Utility to read the exam's tech comments and save the results in ^TMP($J,"RAE2" global. VARIABLES: RADFN TYPE: Input VARIABLES DESCRIPTION: Patient's dfn. VARIABLES: RADTI TYPE: Input VARIABLES DESCRIPTION: The EXAM DATE internal entry number. VARIABLES: RACNI TYPE: Input VARIABLES DESCRIPTION: The CASE NUMBER internal entry number. SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: VistARad is calling SVTCOM^RAUTL11 to save the TECH COMMENT in ^TMP($J,"RAE2" global. This information is presented to the Radiologist on the VistARad workstation's on-line exam worklist. NUMBER: 3509 IA #: 3509 DATE CREATED: JAN 31, 2002 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RAO7PC1A NAME: Imaging - RAO7PC1A ID: RAO7PC1A GENERAL DESCRIPTION: Radiology gives Imaging permission to call SETDATA^RAO7PC1A. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34027504 COMPONENT/ENTRY POINT: SETDATA COMPONENT DESCRIPTION: Utility to set the radiology exam information into the ^TMP($J,"RAE1" global. VARIABLES: RADFN TYPE: Input VARIABLES DESCRIPTION: Patient's dfn. VARIABLES: RAIBDT TYPE: Input VARIABLES DESCRIPTION: EXAM DATE internal entry number. VARIABLES: RAEXN TYPE: Input VARIABLES DESCRIPTION: Maximum number of exams to be researched. VARIABLES: RAXIT TYPE: Input VARIABLES DESCRIPTION: Variable to determine exiting from program. VARIABLES: RACNT TYPE: Input VARIABLES DESCRIPTION: Processing counter. VARIABLES: TMP($J,'RAE1',patient TYPE: Output VARIABLES DESCRIPTION: Temporary global that holds the results as follows. TMP($J,"RAE1",Patient IEN,Exam ID)=Procedure name^Case number^ ; Report status^Abnormal alert flag^Report ien^ ; Exam status order #~Exam status name^ ; Imaging location name^Imaging type abbr~ ; Imaging type name^abnormal results flag^CPT Code ; ^CPRS Order ien^Images exist flag SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: VistARAd software is utilizing the SETDATA^RAO7PC1A to set one entry in the ^TMP($J,"RAE1",patient ien,Exam ID) node. This is used when a Radiologist selects an exam from the workstation's exam listing and/or used for prefetching. NUMBER: 3510 IA #: 3510 FILE NUMBER: 78.1 GLOBAL ROOT: RA(78.1, DATE CREATED: FEB 01, 2002 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Imaging - Complication Types ID: RA(78.1, GLOBAL REFERENCE: RA(78.1, FIELD NUMBER: .01 FIELD NAME: COMPLICATION LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: This field contains the name of the type of complication that may be associated with an exam. GENERAL DESCRIPTION: Radiology gives Imaging permission to read the COMPLICATIONS TYPES file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34028213 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging displays the exam's associated COMPLICATION TYPE on the on-line Exam Worklist provided on VistARad workstation for Radiologist to review and process. Imaging is requesting permission to read field #.01 COMPLICATION in file 78.1, COMPLICATION TYPES. NUMBER: 3511 IA #: 3511 FILE NUMBER: 45 GLOBAL ROOT: DGPT( DATE CREATED: FEB 04, 2002 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3511 ID: DGPT( CREATOR: LOUCK,KEVIN GLOBAL REFERENCE: DGPT('B' GLOBAL DESCRIPTION: Patient cross reference. GLOBAL REFERENCE: DGPT('ADS' GLOBAL DESCRIPTION: Discharge Date cross reference. GLOBAL REFERENCE: DGPT(D0,'P','AP6' GLOBAL DESCRIPTION: Procedure Code cross reference. GLOBAL REFERENCE: DGPT(D0,'S','AO' GLOBAL DESCRIPTION: Procedure Code cross reference. GLOBAL REFERENCE: DGPT(D0,'AP' GLOBAL DESCRIPTION: Procedure Code cross reference. GLOBAL REFERENCE: DGPT( FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 2 FIELD NAME: ADMISSION DATE LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79 FIELD NAME: DXLS LOCATION: 70;10 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.16 FIELD NAME: ICD2 LOCATION: 70;16 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.17 FIELD NAME: ICD3 LOCATION: 70;17 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.18 FIELD NAME: ICD4 LOCATION: 70;18 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.19 FIELD NAME: ICD5 LOCATION: 70;19 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.201 FIELD NAME: ICD6 LOCATION: 70;20 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.21 FIELD NAME: ICD7 LOCATION: 70;21 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.22 FIELD NAME: ICD8 LOCATION: 70;22 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.23 FIELD NAME: ICD9 LOCATION: 70;23 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 79.24 FIELD NAME: ICD10 LOCATION: 70;24 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 80 FIELD NAME: PRINCIPAL DIAGNOSIS LOCATION: 70;11 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: DGPT(D0,'M','AC' GLOBAL DESCRIPTION: ICD pointers GENERAL DESCRIPTION: The Pharmacy Benefits Management package extracts outpatient and inpatient visit data monthly to support the VA National Formulary, disease management issues and patient safety initiatives. Patient information is needed from cross references, as well as admission date and ICD codes. These fields are included in the following references: STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33972104 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham EDITOR: LOUCK,KEVIN DBA Comments: 02/06/15 DT: Added Kevin Louck as editor. Coordinating changes for ICD-10 PTF Modifications project team: change the reference of "ICD9 codes" in the description section to "ICD codes" and change to cross-references. DATE/TIME EDITED: FEB 06, 2015@14:13 ACTION: CONTENT CORRECTED AT THE REQUEST OF: LOUCK,KEVIN NUMBER: 3512 IA #: 3512 FILE NUMBER: 9000010 GLOBAL ROOT: AUPNVSIT( DATE CREATED: FEB 04, 2002 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3512 ID: AUPNVSIT( GLOBAL REFERENCE: AUPNVSIT(D0 FIELD NUMBER: .01 FIELD NAME: VISIT/ADMIT DATE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .05 FIELD NAME: PATIENT NAME LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: 15002 FIELD NAME: PATIENT STATUS IN/OUT LOCATION: 150;2 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Pharmacy Benefits Management package extracts outpatient visit data monthly to support the VA National Formulary, disease management issues and patient safety initiatives. The following references are needed for extract. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 33961962 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI NUMBER: 3513 IA #: 3513 DATE CREATED: FEB 05, 2002 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RAORD5 NAME: Imaging - RAORD5 ID: RAORD5 GENERAL DESCRIPTION: Radiology gives Imaging permission to call RAORD5. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34052105 COMPONENT/ENTRY POINT: RAORD5 COMPONENT DESCRIPTION: Routine that prints a Radiology request. VARIABLES: RADFN TYPE: Input VARIABLES DESCRIPTION: Patient's DFN. VARIABLES: RAOIFN TYPE: Input VARIABLES DESCRIPTION: Exam's entry IEN in the RAD/NUC MED ORDERS file (75.1). VARIABLES: RAX TYPE: Input VARIABLES DESCRIPTION: Variable used to exit routine. VARIABLES: RAPGE TYPE: Input VARIABLES DESCRIPTION: Page counter. SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging software uses the "Print Request" routine, RAORD5, to display a selected radiology order on the VistARad workstation. The use of this routine allows the Radiologist to view the order as if he/she was using the Radiology menu option. When displaying information that is stored in the Radiology database the information provided to the Radiologist on a VistARad workstation should be transparent to the application. NUMBER: 3514 IA #: 3514 DATE CREATED: AUG 12, 2003 CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: CSLFB40 NAME: DBIA3514-A ORIGINAL NUMBER: 3514 ID: CSLFB40 GENERAL DESCRIPTION: Define the use of the CSL API to be called by Fee Basis, and the use of ^XTMP by CSL in the interface between Fee Basis and CoreFLS. STATUS: Active MAIL MESSAGE: 37697610 COMPONENT/ENTRY POINT: $$BLDMSG(.DATA,.VendorData,.PatientData) COMPONENT DESCRIPTION: Extrinsic function called by the Fee Basis application to submit a request for Contract Hospital/ Contract Nursing Home Invoice Creation to be exported to CoreFLS by HL7 messaging. The function's return value is a VistA HL7 message ID if message is successfully submitted to HL7 for transmission to CoreFLS. If HL7 cannot process the message, then the $$BLDMSG function returns 0. $$BLDMSG finishes execution after submitting message to HL7, but before response is received from CoreFLS. SUB^CSLFB40 is invoked by HL7 in order to process the CoreFLS response. All results are placed in the ^XTMP global. The HL7 message ID is passed to Fee Basis via the variable CSLTFEE for retrieval of the data in the ^XTMP global. VARIABLES: .DATA TYPE: Input VARIABLES DESCRIPTION: First paramter, passed by reference, contains information related to the authorization document. DATA(1) = Line Item Number DATA(2) = VistA Payment Batch DATA(3) = Vendor Invoice Date, format: YYYYMMDD DATA(4) = Invoice Received Date, format: YYYYMMDD DATA(5) = Payment Flag DATA(6) = Accounting Code String DATA(7) = VistA Invoice Number DATA(8) = Fee Program DATA(9) = PO Number DATA(10) = Invoice Amount DATA(11) = Invoice Line Item Amount DATA(12) = Prompt Pay Type DATA(13) = Payment Type Code DATA(14) = Suspend Code DATA(15) = NVH Amount Claimed DATA(16) = Buyer SSN DATA(17) = Treatment Date From, format: YYYYMMDD DATA(18) = Treatment Date To, format: YYYYMMDD DATA(19) = Total Invoice Line items VARIABLES: .VendorData TYPE: Input VARIABLES DESCRIPTION: Second parameter, passed by reference, is vendor-related information. VDATA(1) = Supplier Number VDATA(2) = Supplier Site Name VARIABLES: .PatientData TYPE: Input VARIABLES DESCRIPTION: Third parameter, passed by reference, is patient-related information: PDATA(1) = Veteran ID (full SSN) PDATA(2) = Veteran ICN PDATA(3) = Veteran Last Name PDATA(4) = Veteran First Name PDATA(5) = Veteran Middle Initial PDATA(6) = Veteran Suffix PDATA(7) = Address Line 1 PDATA(8) = Address Line 2 PDATA(9) = City PDATA(10) = State PDATA(11) = Zip PDATA(12) = Patient Account Number VARIABLES: XTMP global TYPE: Output VARIABLES DESCRIPTION: Header Node: ^XTMP("CSLroutineName;MSGID";0)= PurgeDate^CreateDate^StatusMessage [n] Where: n = piece number ("^" delimited) MSGID = HL7 message ID consisting of Station# concatenated with IEN to ^HLMA for original HL7 message. ^XTMP("CSLFB40;MSGID",0) [1] = Purge Date (current date+35 days), FileMan internal date format. [2] = Create Date (current date), FileMan internal date format. [3] = User-friendly status message to indicate message processing is completed. Data Node: ^XTMP("CSLroutineName;MSGID","Subscript_Name") = data ^XTMP("CSLFB40;MSGID","PRE_VALIDATION_MSG") = Pre Validation Message ^XTMP("CSLFB40;MSGID","VISTA_INVOICE_NUMBER") = VistA Invoice Number ^XTMP("CSLFB40;MSGID","VISTA_PAYMENT_BATCH_ID") = VistA Payment Batch ID ^XTMP("CSLFB40;MSGID","TIME") = [1] = $H when HL7 message was submitted for transmission to CoreFLS. [2] = $H when CoreFLS response was processed. [3] = Computed time used for the round trip to CoreFLS in the following format: days hours:minutes:seconds. [4] = DUZ of user who created the message in VistA Fee Basis. For exceptions sent by CoreFLS, the error message will be stored after the zero node as follows: ^XTMP("CSLFB40;MSGID","ERR",$H) = Error description, applicable for both Application Error (AE) and Application Reject (AR) SUBSCRIBING PACKAGE: FEE BASIS NUMBER: 3515 IA #: 3515 DATE CREATED: NOV 12, 2003 CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: CSLFB14 NAME: DBIA3514-B ORIGINAL NUMBER: 3514 ID: CSLFB14 GENERAL DESCRIPTION: Define the use of the CSL API to be called by Fee Basis, and the use of ^XTMP by CSL in the interface between Fee Basis and CoreFLS. STATUS: Active MAIL MESSAGE: 37697614 COMPONENT/ENTRY POINT: $$BLDMSG(.DATA,.VendorData,.PatientData) COMPONENT DESCRIPTION: Extrinsic function used to submit a request for Authorization Creation /PO Request in CoreFLS via an HL7 message. The function's return value is a VistA HL7 message ID if message is successfully submitted to HL7 for transmission to CoreFLS, in the format Station# concatenated with VistA HL7 IEN to ^HLMA. If HL7 cannot process the message, then the $$BLDMSG function returns 0. $$BLDMSG finishes execution after submitting message to HL7, but before response is received from CoreFLS. SUB^CSLFB14 is invoked by HL7 in order to process the CoreFLS response. All results are placed in the ^XTMP global. The HL7 message ID is passed to Fee Basis via the variable CSLTFEE for retrieval of the data in the ^XTMP global. VARIABLES: .DATA TYPE: Input VARIABLES DESCRIPTION: First parameter, passed by reference, contains information related to the authorization document. DATA(2) = Authorization ID DATA(3) = Accounting Code String DATA(4) = Fee Program DATA(5) = Estimated Amount DATA(6) = Agent's full SSN (Fee Basis user) DATA(7) = Contract Number DATA(8) = Authorization From Date, formatted as YYYYMMDD DATA(9) = Authorization To Date, formatted as YYYYMMDD DATA(10) = Transaction Type Code DATA(11) = Purchase Order Number VARIABLES: .VendorData TYPE: Input VARIABLES DESCRIPTION: Second parameter, passed by reference, is vendor-related information: VDATA(1) = Supplier Number VDATA(2) = Supplier Site Name VARIABLES: .PatientData TYPE: Input VARIABLES DESCRIPTION: Third parameter, passed by reference, is patient-related information: PDATA(1) = Veteran ID (the full SSN) PDATA(2) = Veteran ICN PDATA(3) = Veteran Last Name PDATA(4) = Veteran First Name PDATA(5) = Veteran Middle Initial PDATA(6) = Veteran Suffix VARIABLES: XTMP global TYPE: Output VARIABLES DESCRIPTION: Header Node: ^XTMP("CSLroutineName;MSGID",0) = PurgeDate^CreateDate^StatusMessage [n] Where: n = piece number ("^" delimited) MSGID = HL7 message ID consisting of Station# concatenated with IEN to ^HLMA for original HL7 message. ^XTMP("CSLFB14;MSGID",0) [1] = Purge Date (current date+35 days), FileMan internal date format. [2] = Create Date (current date), FileMan internal date format. [3] = User-friendly status message to indicate message processing is completed. Data Node: ^XTMP("CSLroutineName;MSGID","Subscript_Name") = data ^XTMP("CSLFB14;MSGID","AUTHORIZATION_ID") = Authorization ID ^XTMP("CSLFB14;MSGID","PRE_VALIDATION_MSG") = Pre Validation Message ^XTMP("CSLFB14;MSGID","TIME") [1] = $H when HL7 message was submitted for transmission to CoreFLS. [2] = $H when CoreFLS response was processed. [3] = Computed time used for the round trip to CoreFLS in the following format: days hours:minutes:seconds. [4] = DUZ of user who created the message in VistA Fee Basis. For exceptions sent by CoreFLS, the error message will be stored after the zero node as follows: ^XTMP("CSLFB14;MSGID","ERR",$H) = Error description, applicable for both Application Error (AE) and Application Reject (AR) SUBSCRIBING PACKAGE: FEE BASIS NUMBER: 3516 IA #: 3516 DATE CREATED: AUG 12, 2003 CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: CSLFB16 NAME: DBIA3514-C ORIGINAL NUMBER: 3514 ID: CSLFB16 GENERAL DESCRIPTION: Define the use of the CSL API to be called by Fee Basis, and the use of ^XTMP by CSL in the interface between Fee Basis and CoreFLS. STATUS: Active MAIL MESSAGE: 37697615 COMPONENT/ENTRY POINT: $$BLDMSG(.DATA,.VendorData,.PatientData) COMPONENT DESCRIPTION: Extrinsic function called by the Fee Basis application to submit a request for an Outpatient/Ancillary Invoice Creation to be exported to CoreFLS by HL7 messaging. The function's return value is a VistA HL7 message ID if a message is successfully submitted to HL7 for transmission to CoreFLS, in the format Station# concatenated with VistA HL7 IEN to ^HLMA. If HL7 cannot process the message, then the $$BLDMSG function returns 0. $$BLDMSG finishes execution after submitting message to HL7, and before response is received from CoreFLS. SUB^CSLFB16 is invoked by HL7 in order to process the CoreFLS response. All results are placed in the ^XTMP global. The HL7 message ID is passed to Fee Basis via the variable CSLTFEE for retrieval of the data in the ^XTMP global. VARIABLES: .DATA TYPE: Input VARIABLES DESCRIPTION: First parameter, passed by reference, is an array of general information about the transaction. DATA(1,seq#) = Line Item Number, where seq# will denote the line item number ranging from 1 to n. DATA(2) = Authorization ID DATA(3) = VistA Payment Batch ID DATA(4) = Vendor Invoice Date, format: YYYYMMDD DATA(5) = Invoice Received Date, format: YYYYMMDD DATA(6) = Payment Flag DATA(7) = Accounting Code String DATA(8) = VistA Invoice Number DATA(9) = Fee Program DATA(10) = General Ledger Name DATA(11) = Invoice Amount DATA(12,seq#) = Invoice Line Item Amount DATA(13,seq#) = Prompt Pay Type for line item DATA(14) = Payment Type Code DATA(15,seq#) = Suspend Code for line item DATA(16,seq#) = Amount Claimed for line item DATA(17) = Buyer SSN DATA(18,seq#) = CPT Code for line item DATA(19,seq#) = CPT Modifier for line item DATA(20,seq#) = Treatment Service Date, format: YYYYMMDD DATA(21) = Total Invoice Line items DATA(22,seq#) = Invoice Item counter VARIABLES: .VendorData TYPE: Input VARIABLES DESCRIPTION: Second parameter, passed by reference, contains vendor-related information. VDATA(1) = Supplier Number VDATA(2) = Supplier Site Name VARIABLES: .PatientData TYPE: Input VARIABLES DESCRIPTION: Third parameter, passed by reference, contains patient-related information. PDATA(1) = Veteran ID (full SSN) PDATA(2) = Veteran ICN PDATA(3) = Veteran Last Name PDATA(4) = Veteran First Name PDATA(5) = Veteran Middle Initial PDATA(6) = Veteran's Suffix PDATA(7) = Address Line 1 PDATA(8) = Address Line 2 PDATA(9) = City PDATA(10) = State PDATA(11) = Zip PDATA(12) = Patient Account Number VARIABLES: XTMP global TYPE: Output VARIABLES DESCRIPTION: Header Node: ^XTMP("CSLroutineName;MSGID",0) = PurgeDate^CreateDate^StatusMessage [n] Where: n = piece number ("^" delimited) MSGID = HL7 message ID consisting of Station# concatenated with IEN to ^HLMA for original HL7 message. ^XTMP("CSLFB16;MSGID",0) [1] = Purge Date (current date+35 days), FileMan internal date format. [2] = Create Date (current date), FileMan internal date format. [3] = User-friendly status message to indicate message processing is completed. Data Node: ^XTMP("CSLroutineNme;MSGID",Subscript_Name") = data ^XTMP("CSLFB16;MSGID","VISTA_PAYMENT_BATCH_ID") = VistA Payment Batch ID ^XTMP("CSLFB16;MSGID","VISTA_INVOICE_NUMBER") = VistA Invoice Number ^XTMP("CSLFB16;MSGID","PRE_VALIDATION_MSG") = Pre Validation Message ^XTMP("CSLFB16;MSGID","TIME") [1] = $H when HL7 message submitted for transmission to CoreFLS. [2] = $H when CoreFLS response was processed. [3] = Computed time used for the round trip to CoreFLS in the following format: day hours:minutes:seconds. [4] = DUZ of user who created the message in VistA Fee Basis. For exceptions sent by CoreFLs, the error message will be stored after the zero node as follows: ^XTMP("CSLFB16;MSGID","ERR",$H) = Error description, applicable for both Application Error (AE) and Application Reject (AR) SUBSCRIBING PACKAGE: FEE BASIS NUMBER: 3517 IA #: 3517 DATE CREATED: AUG 12, 2003 CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: CSLFB39 NAME: DBIA3514-D ORIGINAL NUMBER: 3514 ID: CSLFB39 GENERAL DESCRIPTION: Define the use of the CSL API to be called by Fee Basis, and the use of ^XTMP by CSL in the interface between Fee Basis and CoreFLS. STATUS: Active MAIL MESSAGE: 37697617 COMPONENT/ENTRY POINT: $$BLDMSG(.DATA,.VendorData,.PatientDataT) COMPONENT DESCRIPTION: Extrinsic function called by the Fee Basis application to submit a request for a Pharmacy Invoice Creation to be exported to CoreFLS by HL7 messaging. The function's return value is a VistA HL7 message ID if message is successfully submitted to HL7 for transmission to CoreFLS, in the format Station# concatenated with VistA HL7 IEN to ^HLMA. If HL7 cannot process the message, then the $$BLDMSG function returns 0. $$BLDMSG finishes execution after submitting message to HL7 but before response is received from CoreFLS. SUB^CSLFB39 is invoked by HL7 in order to process the CoreFLS response. All results are placed in the ^XTMP global. The HL7 message ID is passed to Fee Basis via the variable CSLTFEE for retrieval of the data in the ^XTMP global. VARIABLES: .DATA TYPE: Input VARIABLES DESCRIPTION: First parameter, passed by reference, contains information related to the authorization document. DATA(1,seq#) = Line Item Number, where seq# will indicate the line item number ranging from 1 to n DATA(2) = Authorization ID DATA(3) = VistA Payment Batch ID DATA(4) = Invoice Date, format: YYYYMMDD DATA(5) = Invoice Received Date, format: YYYYMMDD DATA(6) = Payment Flag DATA(7) = Accounting Code String DATA(8) = VistA Invoice Number DATA(9) = Fee Program DATA(10) = Invoice Amount DATA(11,seq#) = Invoice Line Item Amount DATA(12,seq#) = Prompt Pay Type for line item DATA(13) = Payment Type Code DATA(14,seq#) = Suspend Code for line item DATA(15,seq#) = Amount Claimed for line item DATA(16) = Buyer SSN DATA(17,seq#) = Prescription number for line item DATA(18,seq#) = Date Prescription filled, format:YYYYMMDD DATA(19) = Total Invoice Line items DATA(20,seq#) = Invoice item counter VARIABLES: .VendorData TYPE: Input VARIABLES DESCRIPTION: Second parameter, passed by reference, contains vendor-related information. VDATA(1) = Supplier Number VDATA(2) = Supplier Site Name VARIABLES: .PatientData TYPE: Input VARIABLES DESCRIPTION: Third paramter, passed by reference, contains patient-related information. PDATA(1) = Veteran ID (full SSN) PDATA(2) = Veteran ICN PDATA(3) = Veteran Last Name PDATA(4) = Veteran First Name PDATA(5) = Veteran Middle Initial PDATA(6) = Veteran Suffix PDATA(7) = Address Line 1 PDATA(8) = Address Line 2 PDATA(9) = City PDATA(10) = State PDATA(11) = Zip VARIABLES: XTMP global TYPE: Output VARIABLES DESCRIPTION: Header Node: ^XTMP("CSLroutineName;MSGID";0)= PurgeDate^CreateDate^StatusMessage [n] Where: n = piece number ("^" delimited) MSGID = HL7 message ID consisting of Station# concatenated with IEN to ^HLMA for original HL7 message. ^XTMP("CSLFB39;MSGID",0) [1] = Purge Date (current date+35 days), FileMan internal date format. [2] = Create Date (current date), FileMan internal date format. [3] = User-friendly status message to indicate message processing is completed. Data Node: ^XTMP("CSLroutineName;MSGID","Subscript_Name") = data ^XTMP("CSLFB39;MSGID","PRE_VALIDATION_MSG") = Pre Validation Message ^XTMP("CSLFB39;MSGID","VISTA_INVOICE_NUMBER") = VistA Invoice Number ^XTMP("CSLFB39;MSGID","VISTA_PAYMENT_BATCH_ID") = VistA Payment Batch ID ^XTMP("CSLFB39;MSGID","TIME") = [1] = $H when HL7 message was submitted for transmission to CoreFLS. [2] = $H when CoreFLS response was processed. [3] = Computed time used for the round trip to CoreFLS in the following format: days hours:minutes:seconds. [4] = DUZ of user who created the message in VistA Fee Basis. For exceptions sent by CoreFLS, the error message will be stored after the zero node as follows: ^XTMP("CSLFB39;MSGID","ERR",$H) = Error description, applicable for both Application Error (AE) and Application Reject (AR) SUBSCRIBING PACKAGE: FEE BASIS NUMBER: 3518 IA #: 3518 DATE CREATED: AUG 12, 2003 CUSTODIAL PACKAGE: COMMUNICATIONS SERVICE LIBRARY CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: CSLFB25 NAME: DBIA3514-E ORIGINAL NUMBER: 3514 ID: CSLFB25 GENERAL DESCRIPTION: Define the use of the CSL API to be called by Fee Basis; and to define the use of ^XTMP by CSL in the interface between Fee Basis and CoreFLS. STATUS: Active MAIL MESSAGE: 37697619 COMPONENT/ENTRY POINT: $$BLDMSG(.DATA,.PatientData) COMPONENT DESCRIPTION: Extrinsic function used to submit a request for Authorization Creation /General Ledger Journal Request /Adjustment Request in CoreFLS via an HL7 message. The function's return value is a VistA HL7 message ID if message is successfully submitted to HL7 for transmission to CoreFLS, in the format Station# concatenated with VistA HL7 IEN to ^HLMA. If HL7 cannot process the message, then the $$BLDMSG function returns 0. $$BLDMSG finishes execution after submitting message to HL7, but before response is received from CoreFLS. SUB^CSLFB25 is invoked by HL7 in order to process the CoreFLS response. All results are placed in the ^XTMP global. The HL7 message ID is passed to Fee Basis via the variable CSLTFEE for retrieval of the data in the ^XTMP global. VARIABLES: .DATA TYPE: Input VARIABLES DESCRIPTION: First parameter, passed by reference, contains information related to the authorization document transaction. DATA(2) = Authorization ID DATA(3) = Transaction Type DATA(4) = Accounting Code String DATA(5) = Fee Program DATA(6) = Entered_dr (debit) DATA(7) = Entered_cr (credit) DATA(8) = Estimated Amount DATA(9) = Agent ID DATA(10) = Treatment From Date, formatted as YYYYMMDD DATA(11) = Treatment To Date, formatted as YYYYMMDD VARIABLES: .PatientData TYPE: Input VARIABLES DESCRIPTION: Second parameter, passed by reference, is patient-related information: PDATA(1) = Veteran ID (the full SSN) PDATA(2) = Veteran ICN PDATA(3) = Veteran Last Name PDATA(4) = Veteran First Name PDATA(5) = Veteran Middle Initial PDATA(6) = Veteran Suffix VARIABLES: XTMP global TYPE: Output VARIABLES DESCRIPTION: Header Node: ^XTMP("CSLroutineName;MSGID";0) = PurgeDate^CreateDate^StatusMessage [n] Where: n = piece number ("^" delimited) MSGID = HL7 message ID consisting of Station# concatenated with IEN to ^HLMA for original HL7 message. ^XTMP("CSLFB25;MSGID",0) [1] = Purge Date (current date+35 days), FileMan internal date format. [2] = Create Date (current date), FileMan internal date format. [3] = User-friendly status message to indicate message processing is completed. Data Node: ^XTMP("CSLroutineName;MSGID";"Subscript_Name") = data ^XTMP("CSLFB25;MSGID","AUTHORIZATION_ID") = Authorization ID ^XTMP("CSLFB25;MSGID","PRE_VALIDATION_MSG") = Pre Validation Message ^XTMP("CSLFB25;MSGID","TIME") [1] = $H when HL7 message was submitted for transmission to CoreFLS. [2] = $H when CoreFLS response was processed. [3] = Computed time used for the round trip to CoreFLS in the following format: days hours:minutes:seconds. [4] = DUZ of user who created the message in VistA Fee Basis. For exceptions sent by CoreFLS, the error message will be stored after the zero node as follows: ^XTMP("CSLFB25;MSGID","ERR",$H) = Error description, applicable for both Application Error (AE) and Application Reject (AR) SUBSCRIBING PACKAGE: FEE BASIS NUMBER: 3519 IA #: 3519 DATE CREATED: FEB 11, 2002 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIULAFC NAME: TIU EXTRACT SELECTED FIELDS BY CLASS ID: TIULAFC GENERAL DESCRIPTION: Extraction of selected fields from TIU by Document Class. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34099545 KEYWORDS: TIU KEYWORDS: GMTS KEYWORDS: GMTSCPB COMPONENT/ENTRY POINT: MAIN(DFN,DOC,TIME1,TIME2,OCCLIM,TEXT,.FLDS,IDX) COMPONENT DESCRIPTION: This entry point is used to extract TIU documents by document Reference Date. It differs from MAIN^TIULAPIC in that the fields required may be passed in by reference and the resulting global array may be indexed by a field other that the Reference Date. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The IEN of the PATIENT file #2 (required) VARIABLES: DOC TYPE: Input VARIABLES DESCRIPTION: TIU document class, IEN of the TIU DOCUMENT DEFINITION file #8925.1 (required) VARIABLES: TIME1 TYPE: Input VARIABLES DESCRIPTION: The beginning date for a range of dates to extract TIU documents (optional, default 6666666) VARIABLES: TIME2 TYPE: Input VARIABLES DESCRIPTION: The ending date for a range of dates to extract TIU documents (optional, default 9999999) VARIABLES: OCCLIM TYPE: Input VARIABLES DESCRIPTION: A maxixum limit of occurrences of the type of document to extract (optional, default 999) VARIABLES: TEXT TYPE: Input VARIABLES DESCRIPTION: Boolean flag (1/0) to include or not to include document text with the extraction (required) VARIABLES: .FLDS TYPE: Input VARIABLES DESCRIPTION: An array of fields to extract from the TIU DOCUMENT file #8925 and passed by reference (required) Format: FLD()="" VARIABLES: IDX TYPE: Input VARIABLES DESCRIPTION: This is a field number from the TIU DOCUMENT file #8925 to use to create an index in the ^TMP global (optional). This field must also be included in FLDS() array. Creates the following index in the ^TMP global: ^TMP("TIU",$J,"IDX",,,) This TMP index can be used to display the data in an order other than 'REFERENCE DATE' COMPONENT/ENTRY POINT: VISIT(DFN,DOC,TIME1,TIME2,LIM,TEXT,.FLDS,IDX) COMPONENT DESCRIPTION: This entry point is used to extract TIU documents by document Visit Date. It differs from VISIT^TIULAPIC in that the fields required may be passed in by reference and the resulting global array may be indexed by a field other that the Visit Date. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The IEN of the PATIENT file #2 (required) VARIABLES: DOC TYPE: Input VARIABLES DESCRIPTION: TIU document class, IEN of the TIU DOCUMENT DEFINITION file #8925.1 (required) VARIABLES: TIME1 TYPE: Input VARIABLES DESCRIPTION: The beginning date for a range of dates to extract TIU documents (optional, default 6666666) VARIABLES: TIME2 TYPE: Input VARIABLES DESCRIPTION: The ending date for a range of dates to extract TIU documents (optional, default 9999999) VARIABLES: OCCLIM TYPE: Input VARIABLES DESCRIPTION: A maxixum limit of occurrences of the type of document to extract (optional, default 999) VARIABLES: TEXT TYPE: Input VARIABLES DESCRIPTION: Boolean flag (1/0) to include or not to include document text with the extraction (required) VARIABLES: .FLDS TYPE: Input VARIABLES DESCRIPTION: An array of fields to extract from the TIU DOCUMENT file #8925 and passed by reference (required) Format: FLD()="" VARIABLES: IDX TYPE: Input VARIABLES DESCRIPTION: This is a field number from the TIU DOCUMENT file #8925 to use to create an index in the ^TMP global (optional). This field must also be included in FLDS() array. Creates the following index in the ^TMP global: ^TMP("TIU",$J,"IDX",,,) This TMP index can be used to display the data in an order other than 'VISIT DATE' SUBSCRIBING PACKAGE: HEALTH SUMMARY ISC: Salt Lake City SUBSCRIBING DETAILS: Health Summary will used this API (in leiu of TIUAPIC) when only a few fields are desired during data extraction to help speed up extract/display times. NUMBER: 3520 IA #: 3520 GLOBAL ROOT: %ZTSCH(TASK, DATE CREATED: FEB 12, 2002 CUSTODIAL PACKAGE: KERNEL USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: %ZTSCH(TASK Global ID: %ZTSCH(TASK, GLOBAL REFERENCE: %ZTSCH(TASK, GLOBAL DESCRIPTION: Examine the currently running tasks in the SCHEDULE file. For each task found, examine the ROUTINE field. S TASK=0 F S TASK=$O(^%ZTSCH("TASK",TASK)) Q:'TASK Q:QFLG D .S ROU=$P(^%ZTSCH("TASK",TASK),"^",2) GENERAL DESCRIPTION: CLINICAL INFO RESOURCE NETWORK - Master Patient Index/Patient Demographics (MPI/PD) will make our RGMTRUN utility routine class I at all VA facilities. We will create a remote query tool on the Master Patient Index (MPI) to query a site for the currently running task information. The following code in RGMTRUN examines the currently running tasks in the SCHEDULE file. For each task found, it examines the ROUTINE field. If the ROUTINE field contains "HL" (Health Level Seven), then for that task, EN^XUTMTP(TASK) is called to display the task information. S TASK=0 F S TASK=$O(^%ZTSCH("TASK",TASK)) Q:'TASK Q:QFLG D .S ROU=$P(^%ZTSCH("TASK",TASK),"^",2) .I ROU["HL" D EN^XUTMTP(TASK) This IA is for direct global read of the ^%ZTSCH("TASK",TASK) node of the SCHEDULE file and for direct global read, $P(^%ZTSCH( "TASK",TASK),"^",2) for pieces 2 and 4, ROUTINE and OPTION NAME. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34061170 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: MASTER PATIENT INDEX NUMBER: 3521 IA #: 3521 DATE CREATED: FEB 12, 2002 CUSTODIAL PACKAGE: KERNEL USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUTMTP NAME: XUTMTP Routine ID: XUTMTP GENERAL DESCRIPTION: CLINICAL INFO RESOURCE NETWORK - Master Patient Index/Patient Demographics (MPI/PD) will make our RGMTRUN utility routine class I at all VA facilities. We will create a remote query tool on the Master Patient Index (MPI) to query a site for the currently running task information. The following code in RGMTRUN examines the currently running tasks in the SCHEDULE file. For each task found, it examines the ROUTINE field. If the ROUTINE field contains "HL" (Health Level Seven), then for that task, EN^XUTMTP(TASK) is called to display the task information. S TASK=0 F S TASK=$O(^%ZTSCH("TASK",TASK)) Q:'TASK Q:QFLG D .S ROU=$P(^%ZTSCH("TASK",TASK),"^",2) .I ROU["HL" D EN^XUTMTP(TASK) This IA allows MPI/PD to call the EN entry point in routine XUTMTP. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34061203 COMPONENT/ENTRY POINT: EN(TASK) COMPONENT DESCRIPTION: Examine the currently running tasks in the SCHEDULE file. For each task found, examine the ROUTINE field. If the ROUTINE field contains "HL" (Health Level Seven), then for that task, EN^XUTMTP(TASK) is called to display the task information. Example of information displayed by EN^XUTMTP(TASK): ---------------------------------------------------- 261181: EN^HLCSLM, HL7 Link Manager. No device. DEV,MOU. From 12/31/2001 at 14:17, By USER,NAME. Started running 12/31/2001 at 14:17. Job #: 562039155 VARIABLES: TASK TYPE: Input VARIABLES DESCRIPTION: TaskMan's task ID. VARIABLES: ZTENV TYPE: Input VARIABLES DESCRIPTION: set = 1 VARIABLES: ZTKEY TYPE: Input VARIABLES DESCRIPTION: set = 0 VARIABLES: ZTNAME TYPE: Input VARIABLES DESCRIPTION: set = VARIABLES: ZTFLAG TYPE: Input VARIABLES DESCRIPTION: set = 1 VARIABLES: XUTMUCI TYPE: Input VARIABLES DESCRIPTION: X ^%ZOSF("UCI") S XUTMUCI=Y SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK SUBSCRIBING PACKAGE: MASTER PATIENT INDEX NUMBER: 3522 IA #: 3522 DATE CREATED: FEB 12, 2002 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: %ZOSV NAME: $$OS EXTRINSIC FUNCTION IN ROUTINE %ZOSV ID: %ZOSV CREATOR: FORT,WALLY GENERAL DESCRIPTION: The $$OS^%ZOSV() extrinsic function is only available under Cache'/OpenM systems. This function returns the underlying operating system such as VMS, UNIX or NT. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34118565 COMPONENT/ENTRY POINT: $$OS COMPONENT DESCRIPTION: Usage: I ^%ZOSF("OS")["OpenM" S Y=$$OS^%ZOSV DBA Comments: 20090706 - removed subscribers VISTALINK and HL7 and made Usage = Supported DATE ACTIVATED: JUL 06, 2009 DATE/TIME EDITED: JUL 06, 2009@12:08 ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: FORT,WALLY DATE/TIME EDITED: JUL 06, 2009@16:13 ACTION: USAGE CHOICE CHANGED AT THE REQUEST OF: FORT,WALLY DATE/TIME EDITED: JUL 06, 2009@16:14 ACTION: SUBSCRIBER DELETED AT THE REQUEST OF: HARVEY,JULIE DATE/TIME EDITED: JUL 06, 2009@16:15 ACTION: APPROVED AT THE REQUEST OF: FORT,WALLY NUMBER: 3523 IA #: 3523 DATE CREATED: FEB 20, 2002 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: DGMTU NAME: DBIA3523 ID: DGMTU STATUS: Active MAIL MESSAGE: 34156145 COMPONENT/ENTRY POINT: $$FUT(DFN,DGDT,DGMTYPT) COMPONENT DESCRIPTION: Identify veteran's records with future tests. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: Contains the Internal Entry Number of the patient in the PATIENT File, #2. VARIABLES: DGDT TYPE: Input VARIABLES DESCRIPTION: Date (Optional- default to today). VARIABLES: DGMTYPT TYPE: Input VARIABLES DESCRIPTION: Type of Test (Optional - default to Means Test) VARIABLES: $$FUT TYPE: Output VARIABLES DESCRIPTION: If a future DCD test was performed it will be returned, else the earliest performed future test for the Income Year will be. Data returned: Future MT IEN^Date of Test (Future)^Status Name^Status Code^Source of Test NUMBER: 3524 IA #: 3524 DATE CREATED: FEB 14, 2002 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XDRDFPD NAME: XDRDFPD ID: XDRDFPD GENERAL DESCRIPTION: This integration agreement is for access from the top of the routine XDRDFPD. Entry at this location will result in the user being prompted for a specific file to check for duplicate entries, then prompted for a specific entry within that file. To proceed there must be an entry for the selected file in the DUPLICATE RESOLUTION file (#15.1). The routine then checks other entries within the specified file to determine whether they are potential duplicates based upon the information and routines specified in the DUPLICATE TESTS sub-file (field #1100) for the specified file. Entries which are identified as potential duplicates are entered into the DUPLICATE RECORD file (#15). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34121049 KEYWORDS: DUPLICATE KEYWORDS: RESOLUTION COMPONENT/ENTRY POINT: XDRDFPD COMPONENT DESCRIPTION: Entry at this location will result in the user being prompted for a specific file to check for duplicate entries, then prompted for a specific entry within that file. To proceed there must be an entry for the selected file in the DUPLICATE RESOLUTION file (#15.1). The routine then checks other entries within the specified file to determine whether they are potential duplicates based upon the information and routines specified in the DUPLICATE TESTS sub-file (field #1100) for the specified file. Entries which are identified as potential duplicates are entered into the DUPLICATE RECORD file (#15). SUBSCRIBING PACKAGE: MASTER PATIENT INDEX SUBSCRIBING DETAILS: Master Patient Index Austin is utilizing the Duplicate Record Merge software from within Kernel Toolkit to search for patients already existing in the index. NUMBER: 3525 IA #: 3525 DATE CREATED: FEB 14, 2002 CUSTODIAL PACKAGE: TOOLKIT CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XDRDFPD NAME: EN XDRDFPD ID: XDRDFPD GENERAL DESCRIPTION: This entry point provides the ability to perform a search on a specified file for potential duplicates to a specified file entry, using user specified criteria in the DUPLICATE RESOLUTIION file (#15.1). The routine creates entries in the DUPLICATE RECORD file (#15) of potential duplicates identified for subsequent verification. The users must create an entry in the DUPLICATE RESOLUTION file for the file that will be analyzed. This entry must include data in the CANDIDATE COLLECTION ROUTINE field (#.09) which will specify the routine to be used as the basis for identifying those that might be potential duplicates. These candidates are then compared using the data and routines specified in the DUPLICATE TESTS sub-file (field #1100) for the analyis. The weighted result from these tests is then compared to the POTENTIAL DUPLICATE THRESHOLD% value to determine if an entry should be considered a potential duplicate and entered into the DUPLICATE RECORD file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34121053 KEYWORDS: DUPLICATE KEYWORDS: RESOLUTION COMPONENT/ENTRY POINT: EN COMPONENT DESCRIPTION: This entry point is used to identify potential duplicates in the file XDRL to the file entry number contained in the variable XDRCD. This Entry point assumes XDRCD and XDRFL are defined. VARIABLES: XDRCD TYPE: Input VARIABLES DESCRIPTION: The variable XDRCD contains the internal entry number of the desired file entry for which potential duplicates are to be identified. Any potential duplicates that are found are entered into the DUPLICATE RECORD file (#15). VARIABLES: XDRFL TYPE: Input VARIABLES DESCRIPTION: This variable contains the file number for which the duplicate resolution search will be performed. This file number will be used to extract all the relevant fields for the tests from the DUPLICATE RESOLUTION file (#15.1). SUBSCRIBING PACKAGE: MASTER PATIENT INDEX SUBSCRIBING DETAILS: Master Patient Index Austin is utilizing the Duplicate Record Merge software from within Kernel Toolkit to search for patients already existing in the index. EDITOR: CHESNEY,CHRISTINE M EDITOR: SCHRAM,JACK D NUMBER: 3526 IA #: 3526 DATE CREATED: FEB 14, 2002 CUSTODIAL PACKAGE: TOOLKIT USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XDRDFPD NAME: SETUP XDRDFPD ID: XDRDFPD GENERAL DESCRIPTION: Master Patient Index Austin is utilizing the Duplicate Record Merge software from within Kernel Toolkit to search for patients already existing in the index. STATUS: Active MAIL MESSAGE: 34121055 COMPONENT/ENTRY POINT: SETUP SUBSCRIBING PACKAGE: MASTER PATIENT INDEX EDITOR: CHESNEY,CHRISTINE M EDITOR: SCHRAM,JACK D NUMBER: 3527 IA #: 3527 DATE CREATED: FEB 14, 2002 CUSTODIAL PACKAGE: TOOLKIT USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XDRDMAIN NAME: CHECK XDRDMAIN ID: XDRDMAIN GENERAL DESCRIPTION: Master Patient Index Austin is utilizing the Duplicate Record Merge software from within Kernel Toolkit to search for patients already existing in the index. STATUS: Active MAIL MESSAGE: 34121056 COMPONENT/ENTRY POINT: CHECK SUBSCRIBING PACKAGE: MASTER PATIENT INDEX EDITOR: CHESNEY,CHRISTINE M EDITOR: SCHRAM,JACK D NUMBER: 3528 IA #: 3528 DATE CREATED: FEB 14, 2002 CUSTODIAL PACKAGE: TOOLKIT USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XDRDQUE NAME: FILE XDRDQUE ID: XDRDQUE GENERAL DESCRIPTION: Master Patient Index Austin is utilizing the Duplicate Record Merge software from within Kernel Toolkit to search for patients already existing in the index. STATUS: Active MAIL MESSAGE: 34121057 COMPONENT/ENTRY POINT: FILE COMPONENT DESCRIPTION: This sub-routine sets-up the XDRD array that is used when initially searching files for duplicates. The information stored in this array is derived from file #15.1 (Duplicate Resolution). If the variable "XDRFL" is set then that will be used as the file number, otherwise the user will be prompted for the file. If the file doesn't exist in file #15.1, "-1" will be returned. VARIABLES: XDRFL TYPE: Used VARIABLES DESCRIPTION: XDRFL is set to the file number. If this variable is not set then the user will be prompted for the file. "-1" will be returned if the file doesn't exist in file 15.1. VARIABLES: XDRD(array) TYPE: Output VARIABLES DESCRIPTION: The XDRD(array) will be returned for valid file entries. This array stores the search critera for the Merge s/w. SUBSCRIBING PACKAGE: MASTER PATIENT INDEX EDITOR: SCHRAM,JACK D NUMBER: 3529 IA #: 3529 FILE NUMBER: 21 GLOBAL ROOT: DIC(21 DATE CREATED: FEB 15, 2002 CUSTODIAL PACKAGE: REGISTRATION USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3529 ID: DIC(21 GLOBAL REFERENCE: DIC(21,DA,0) FIELD NUMBER: .03 FIELD NAME: CODE LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Beneficiary Travel uses a direct read on the zero node of the PERIOD OF SERVICE (#21) File. VIEWER: MARKS,MARY STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34126900 SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL SUBSCRIBING PACKAGE: SCHEDULING NUMBER: 3530 IA #: 3530 FILE NUMBER: 9000010 GLOBAL ROOT: AUPNVSIT( DATE CREATED: FEB 27, 2002 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3530 ID: AUPNVSIT( GLOBAL REFERENCE: AUPNVSIT(D0 FIELD NUMBER: 81203 FIELD NAME: DATA SOURCE LOCATION: 812;3 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Visit's Data Source, pointer to file 839.7 GENERAL DESCRIPTION: Integrated Billing receives encounters from PCE but screens out many based on certain criteria. One of these criteria is the Data Source of the encounter. The following reference is needed to identify the Data Source of an encounter to determine if the encounter should pass to Integrated Billing. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34166457 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: LAB SERVICE NUMBER: 3531 IA #: 3531 FILE NUMBER: 839.7 GLOBAL ROOT: PX(839.7, DATE CREATED: FEB 27, 2002 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3531 ID: PX(839.7, GLOBAL REFERENCE: PX(839.7,D0 FIELD NUMBER: .01 FIELD NAME: SOURCE NAME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Name of a Data Source. GENERAL DESCRIPTION: Integrated Billing receives encounters from PCE but screens out some based on the Data Source of the encounter. The following reference is needed to identify the Data Source of an Encounter to determine if the encounter is billable. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34166463 SUBSCRIBING PACKAGE: INTEGRATED BILLING ISC: Albany SUBSCRIBING PACKAGE: CLINICAL REMINDERS NUMBER: 3532 IA #: 3532 FILE NUMBER: .401 GLOBAL ROOT: DIBT DATE CREATED: FEB 27, 2002 CUSTODIAL PACKAGE: VA FILEMAN USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Imaging DIBT read ID: DIBT GLOBAL REFERENCE: DIBT(D0 GLOBAL REFERENCE: DIBT(D0,'DC' GLOBAL DESCRIPTION: The node that contains the fields and search value representation. Example: ^DIBT(1228,"DC",1)=^9>20 < don't execute commit code; SUPPRESS=0 or UNDEFINED ==> DO execute commit code). COMPONENT/ENTRY POINT: DELETE(ERR,TIUDA,TIURSN,OVRRIDE) COMPONENT DESCRIPTION: Deletes TIU Document records...Evaluates authorization. VARIABLES: TIUDA TYPE: Input VARIABLES DESCRIPTION: Record number of TIU Document to be deleted. VARIABLES: TIURSN TYPE: Used VARIABLES DESCRIPTION: This optional parameter specifies the reason for deletion (i.e., Privacy Act, or Administrative Action). It only needs to be passed if the document has already been signed, and the user is still authorized to delete the record. VARIABLES: ERR TYPE: Output VARIABLES DESCRIPTION: Returns error message with ERR=1^Explanation text if the user is NOT authorized to delete the named record (e.g., it's his, but signed; or it's not his, and he better keep his paws off it). VARIABLES: OVRRIDE TYPE: Input VARIABLES DESCRIPTION: This optional BOOLEAN parameter indicates to the API whether the business rules defined by the site for the DELETE action should be overridden for the document in question. Allowable values are 1 (TRUE), or 0 (FALSE). DEFAULT is 0 (FALSE). COMPONENT/ENTRY POINT: MAKEADD(TIUDADD,TIUDA,TIUX,SUPPRESS) COMPONENT DESCRIPTION: This call allows the creation of addenda to TIU Documents. Beginning when TIU*1*184 is released, please call MAKEADD^TIUSRVP2 instead. Although MAKEADD^TIUSRVP will still work, the version in TIUSRVP2 will be more efficient. VARIABLES: TIUDA TYPE: Input VARIABLES DESCRIPTION: This is the record number of the parent document in file 8925. VARIABLES: TIUX TYPE: Input VARIABLES DESCRIPTION: This is a local input array containing the data to be filed for the addendum record, formatted as follows: TIUX(.02)=45678 TIUX(1301)=2960703.104556 TIUX(1302)=293764 TIUX("TEXT",1,0)="The patient is a 70 year old WHITE MALE, who presented to the ONCOLOGY CLINIC" TIUX("TEXT",2,0)="On JULY 3, 1996@10:00 AM, with the chief complaint of NECK PAIN..." VARIABLES: SUPPRESS TYPE: Input VARIABLES DESCRIPTION: BOOLEAN flag indicating whether or not to suppress execution of the COMMIT ACTION for the document in question. This gives the calling application control over the circumstances in which the COMMIT CODE should be executed. VARIABLES: TIUDADD TYPE: Both VARIABLES DESCRIPTION: This is the record number of the resulting addendum. NOTE: If no addendum record may be created, then the return variable will look as follows: "-1^Could not create addendum." COMPONENT/ENTRY POINT: SIGN(.ERR,TIUDA,TIUX) COMPONENT DESCRIPTION: Validates and applies an electronic signature to a document. Beginning when TIU*1*184 is released, please call SIGN^TIUSRVP2 instead. Although SIGN^TIUSRVP will still work, the version in TIUSRVP2 will be more efficient. VARIABLES: ERR TYPE: Both VARIABLES DESCRIPTION: Passed by reference to return #^text of error message from Dialog file if the user is NOT authorized to sign the document or if the ES code is invalid; if successful, ERR=0. VARIABLES: TIUDA TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT file (#8925) VARIABLES: TIUX TYPE: Input VARIABLES DESCRIPTION: User's electronic signature code, assumed to be encrypted by the Broker's ENCRYP^XUSRB1. SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: CARE MANAGEMENT SUBSCRIBING PACKAGE: IMAGING SUBSCRIBING PACKAGE: SPINAL CORD DYSFUNCTION SUBSCRIBING PACKAGE: MENTAL HEALTH SUBSCRIBING DETAILS: ADDED 7/25/07 SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING SUBSCRIBING DETAILS: During the process of developing an HL7 interface (GMRC*3.0*75) between the VistA Consult/Request Tracking software and the Healthcare Claims Processing System, an API was identified which requires an integration agreement for its use. Patch GMRC*3.0*75 will utilize the MAKEADD^TIUSRVP2 API for signing and addending TIU documents. The Healthcare Claims Processing System will store an internal IEN for the TIU Document entry. The following is a summary of dealing with the issue of a patient requesting the note to be edited - requiring th note IEN for the TIU Document entry to be changed in the HCPS product: 1. HCPS/RAS System passes in a TIU# via HL7 interface to the VistA Consult Interface in GMRC*3.0*75. The issue is that when the TIU note is amended (i.e., a patient requests a correction, etc.) the TIU# will change. The users on the HCPS/RAS system need to be aware that this could happen and when it does, the original TIU# would be hidden (i.e., no longer valid). The HCPS/RAS user would then need to follow a manual process to obtain/update the TIU#. 2. The amendment process needs to be added to test scripts so that a list of amendment steps so that the Harris (VistA Consult) team can verify what happens in their test environment. 3. The Harris team will relay this information to the HCPS/RAS team so that it can be documented in their manuals. A potential example of text follows - and this applies to any other new subscribing applications: Whenever an amendment is made to a TIU note that HCPS is pointing to by the Chief, MIS or a Privacy Act Officer, then a local process needs to be in place where they must verify that local policy is followed for a manual update to the "HCPS file name, field name" to change the TIU pointer to point to the amended note's internal entry number. DBA Comments: 08/29/14 DT: Added Consult Request Tracking as subscriber. Since HCPS/RAS is storing the note internal entry number, a plan was also included to address the scenario where the note is amended per patient request, resulting in a new note internal entry number needing to be manually edited in the HCPS/RAS file to reflect the amended note internal entry number. This was determined based on meetings with the HCPS/RAS team, Consults developer (Philip Yeager), and TIU developer (Margy McClenahan). DATE/TIME EDITED: JUL 25, 2007@09:00 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HSU,YUI WITH CONCURRENCE OF: MCCLENAHAN,MARGY DATE/TIME EDITED: AUG 29, 2014@13:18 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: YEAGER,PHILIP WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 3536 IA #: 3536 DATE CREATED: MAR 01, 2002 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUSRVLR NAME: TIU GET DOCUMENTS FOR REQUEST ID: TIUSRVLR STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34184240 COMPONENT/ENTRY POINT: GETDOCS(TIUY,OVP,SEQUENCE) COMPONENT DESCRIPTION: This API returns the list of documents associated with a given Request (e.g., Consult Request, or Surgical Case). VARIABLES: OVP TYPE: Input VARIABLES DESCRIPTION: This is the variable pointer (e.g., "12745;GMR(123," or "14672;SRF(") that identifies the record in the requesting application. VARIABLES: SEQUENCE TYPE: Used VARIABLES DESCRIPTION: This optional variable indicates the date order of the documents in the returned array. "A"=ascending (Regular date/time) "D"=descending (Reverse date/time) (default) VARIABLES: TIUY TYPE: Output VARIABLES DESCRIPTION: The return global array has elements with the following positional values: IEN^TITLE^REFERENCE DATE/TIME (INT)^PATIENT NAME (LAST I/LAST 4)^AUTHOR (INT;EXT)^HOSPITAL LOCATION^SIGNATURE STATUS^Visit Date/Time^ Discharge Date/time^Variable Pointer to Request (e.g., Consult)^# of Associated Images^Subject^Has Children^IEN of Parent Document NOTE: Although the subscriber may define the TIUY parameter when calling this API, the parameter value is not used. The API initializes the return array value for TIUY as ^TMP("TIULIST",$J). Thus, the subscriber must reference the global ^TMP("TIULIST",$J as the return global array. SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING PACKAGE: VA CERTIFIED COMPONENTS - DSSI SUBSCRIBING PACKAGE: IMAGING DBA Comments: 4/12/13-MM: Added Imaging as a subscriber to ICR #3536 for MAG*3.0*110 scheduled to be released in August 2013. DATE/TIME EDITED: APR 12, 2013@16:44 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CASUGAY,ELSIE WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 3537 IA #: 3537 DATE CREATED: MAR 01, 2002 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUSROI NAME: TIUSROI Calls ID: TIUSROI GENERAL DESCRIPTION: This IA documents calls in the routine TIUSROI. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34184330 COMPONENT/ENTRY POINT: ES(TIUDA,TIUDUZ) COMPONENT DESCRIPTION: This API applies the user's electronic signature to a document. VARIABLES: TIUDA TYPE: Input VARIABLES DESCRIPTION: IEN of TIU DOCUMENT file (#8925) VARIABLES: TIUDUZ TYPE: Input VARIABLES DESCRIPTION: DUZ of user signing document SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 3538 IA #: 3538 FILE NUMBER: 43.1 GLOBAL ROOT: DG(43.1, DATE CREATED: MAR 05, 2002 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3538 ID: DG(43.1, GLOBAL REFERENCE: DG(43.1,BT FIELD NUMBER: 30.01 FIELD NAME: DEDUCTIBLE/VISIT LOCATION: BT;1 ACCESS: Both R/W w/Fileman FIELD NUMBER: 30.02 FIELD NAME: DEDUCTIBLE/MONTH LOCATION: BT;2 ACCESS: Both R/W w/Fileman FIELD NUMBER: 30.03 FIELD NAME: MILEAGE RATE LOCATION: BT;3 ACCESS: Both R/W w/Fileman FIELD NUMBER: 30.04 FIELD NAME: FISCAL SYMBOLS LOCATION: BT;4 ACCESS: Both R/W w/Fileman FIELD NUMBER: 30.05 FIELD NAME: C&P REVIEW VISIT MILEAGE RATE LOCATION: BT;5 ACCESS: Both R/W w/Fileman FIELD NUMBER: .01 FIELD NAME: DATE LOCATION: 0;1 ACCESS: Both R/W w/Fileman GENERAL DESCRIPTION: Beneficiary Travel needs access to add DATE (#.01) field entries in the MAS EVENT RATES (#43.1) file. Entry is done using a Fileman call. ------------------------------- Beneficiary Travel will retain full authority for the "BT" node and its fields located in the MAS EVENT RATES (#43.1) File. This includes development of the data dictionary (DD) for these fields, as well as responsibility for the data entry into and data retriveval from these fields. This agreement is a "delegation of custody" of these fields from Registration to Beneficiary Travel. It provides Beneficiary Travel all rights and privileges to development and distribution for all DD elements and data in these fields. In addition, all DBIAs required for access to the DD and data for these fields will be between any subscriber and Beneficiary Travel as the custodian. VIEWER: MARKS,MARY STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34198688 SUBSCRIBING PACKAGE: BENEFICIARY TRAVEL NUMBER: 3539 IA #: 3539 DATE CREATED: APR 22, 2002 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: XUSSPKI NAME: Digital Signature Storage ID: XUSSPKI GENERAL DESCRIPTION: This IA is for a set of API's to facilitate the use of PKI Digital Signatures in VistA applications. STATUS: Active MAIL MESSAGE: 34394633 KEYWORDS: PKI COMPONENT/ENTRY POINT: $$STORESIG COMPONENT DESCRIPTION: This API is used to save a base64 encoded Digital Signature. It returns a 1 if the signature is filed OK. or it retunes "-1^message". VARIABLES: P1 TYPE: Input VARIABLES DESCRIPTION: This is the base64 encoded HASH of the data, That is used to link the Signature with the data. We currently use SHA-1 for the hash function. VARIABLES: P2 TYPE: Input VARIABLES DESCRIPTION: This is the length of the Signature. It can be used to check that all the data was received. It is used to check that the length received matches that was sent. VARIABLES: P3 TYPE: Input VARIABLES DESCRIPTION: This is the array that has the Digital Signature. It is passed by reference. (.ABC) VARIABLES: P4 TYPE: Input VARIABLES DESCRIPTION: This is the DUZ of the user whos signagture we are storing. VARIABLES: P5 TYPE: Input VARIABLES DESCRIPTION: This is the file number that holds the data that was signed. COMPONENT/ENTRY POINT: $$VERIFY COMPONENT DESCRIPTION: This API is used to verify a Digital Signature. The hash of the data is checked against the hash stored in the Signature. Revocation checking is done. Returns "OK" if every thing checks. or returns "-1^message". VARIABLES: P1 TYPE: Input VARIABLES DESCRIPTION: The Hash to lookup the signature to be checked. VARIABLES: P2 TYPE: Input VARIABLES DESCRIPTION: This is the closed root to where the data is. VARIABLES: P3 TYPE: Input VARIABLES DESCRIPTION: [optional] This is the date that should be used to check the validity of the signature. COMPONENT/ENTRY POINT: $$CRLURL COMPONENT DESCRIPTION: This API is used to save the URL's needed to colect the CRL's that are needed for Certificate revocation checking. VARIABLES: P1 TYPE: Input VARIABLES DESCRIPTION: This is a string of CRLURL's seperated by $C(9). Only ones that start with http: or ldap: will be stored. The entries in this file are sent to the Verification Server every hour so current CRL files can be loaded into the server. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY SUBSCRIBING DETAILS: ADDED 10/26/2011 DATE/TIME EDITED: OCT 26, 2011@13:18 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MORRISON,JENNIFER WITH CONCURRENCE OF: MENDOZA,RAUL NUMBER: 3540 IA #: 3540 DATE CREATED: MAR 06, 2002 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUSRVP NAME: TIUSRVP, Entry Point: FILE ID: TIUSRVP GENERAL DESCRIPTION: This IA documents the call to FILE^TIUSRVP. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34202848 COMPONENT/ENTRY POINT: FILE(SUCCESS,TIUDA,TIUX,SUPPRESS,TIUCPF) COMPONENT DESCRIPTION: This API calls the VA FileMan filer and commits updates to a TIU document. VARIABLES: SUCCESS TYPE: Both VARIABLES DESCRIPTION: This is the return parameter, which is passed by reference. If an error occurs, it will be a pointer to the FM dialog file followed by the integer 1 in the second "^"-piece (e.g.,8925001^1). VARIABLES: TIUDA TYPE: Input VARIABLES DESCRIPTION: This is the record # (IEN) of the TIU Document in file #8925. VARIABLES: SUPPRESS TYPE: Used VARIABLES DESCRIPTION: This Boolean flag is passed in to suppress the call to the COMMIT CODE for thr TIU DOCUMENT in question (i.e., SUPPRESS=1 ==> don't execute commit code; SUPRESS=0 of UNDEFINED ==> DO execute commit code). VARIABLES: TIUCPF TYPE: Used VARIABLES DESCRIPTION: This optional parameter indicates whether or not the title of this document is a member of the Clinical Procedures Class (1=Yes and 0=No). VARIABLES: TIUX TYPE: Input VARIABLES DESCRIPTION: This is a local input array containing the data to be filed for the addendum record, formatted as follows: TIUX(.02)=45678 TIUX(1301)=2960703.104556 TIUX(1302)=293764 TIUX("TEXT",1,0)="The patient is a 70 year old WHITE MALE, who presented to the ONCOLOGY CLINIC" TIUX("TEXT",2,0)="On JULY 3, 1996@10:00 AM, with the chief complaint of NECK PAIN..." SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham SUBSCRIBING DETAILS: This IA allows a one time use of FILE^TIUSRVP by SURGERY as part of the post-install process for the Surgery Electronic Signature for Operative Reports patch. SUBSCRIBING PACKAGE: LAB SERVICE SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 3541 IA #: 3541 DATE CREATED: MAR 07, 2002 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SROSRPT NAME: GET OPTOP ID: SROSRPT GENERAL DESCRIPTION: This DBIA documents the call to SROSRPT to return optop information on a surgical case. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34392519 COMPONENT/ENTRY POINT: OPTOP(SRTN,SRLAST,SRG) VARIABLES: SRTN TYPE: Input VARIABLES DESCRIPTION: This is the IEN of the surgical case in the SURGERY file (#130). VARIABLES: SRLAST TYPE: Used VARIABLES DESCRIPTION: This optional parameter decides if the optop will be returned with a summary status at the end. 0 or null : include summary status at end 1 : omit summary status at end 2 : include summary status at end plus document text from TIU VARIABLES: SRG TYPE: Both VARIABLES DESCRIPTION: This optional parameter is the return array. If null, information will be returned in ^TMP("SROP",$J,SRTN). SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3542 IA #: 3542 DATE CREATED: MAR 07, 2002 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SRONP NAME: GET OPTOP FOR NON-OR PROCEDURE ID: SRONP GENERAL DESCRIPTION: This DBIA documents the call to SRONP to return optop information on a non-OR procedure. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34392527 COMPONENT/ENTRY POINT: OPTOP(SRTN,SRLAST,SRG) VARIABLES: SRTN TYPE: Input VARIABLES DESCRIPTION: This is the IEN of the non-OR procedure in the SURGERY file (#130). VARIABLES: SRLAST TYPE: Used VARIABLES DESCRIPTION: This optional parameter decides if the optop will be returned with a summary status at the end. 0 or null : include summary status at end 1 : omit summary status at end 2 : include summary status at end plus document text from TIU VARIABLES: SRG TYPE: Both VARIABLES DESCRIPTION: This optional parameter is the return array. If null, information will be returned in ^TMP("SRNOR",$J,SRTN). SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3544 IA #: 3544 FILE NUMBER: 200 GLOBAL ROOT: VA(200 DATE CREATED: MAR 12, 2002 CUSTODIAL PACKAGE: KERNEL USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: IMAGING - NEW PERSON FILE ID: VA(200 GLOBAL REFERENCE: VA(200,'ARC',CLASSIFICATION,DUZ GLOBAL DESCRIPTION: This is the cross-reference on the RAD/NUC MED CLASSIFICATION field (#.01) of subfile (200.072). Used to determine the classification of the end-user in Radiology. GENERAL DESCRIPTION: Kernel gives Imaging permission to read the Radiology Classification in the New Person file. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34228123 SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: VistARad software provides the Radiologist a paperless workstation functionality including Radiology exam worklists and on-line Radiology requisition and enables them to update the status and interpretation for the exam all on-line. Our requirements are to perform all of this within seconds of the click of a button. The functionality to update the exam status to "INTREPRETED" requires the end user to be either a Resident or Staff and this is defined in the NEW PERSON file in the RAD/NUC MED CLASSIFICATION subfile (200.072). Imaging is reading the "ARC" cross reference to field RAD/NUC MED CLASSIFICATION (.01 field) to sub-file 200.072. The following is an example of the code used where as the value of RIST will be either an "R" or an "S". It is possible for an end-user to have both of these classifications and either of the classification can update the Radiology exam status. The variable DUZ is determined at sign-on.: S RIST="" F X="S","R" I $D(^VA(200,"ARC",X,DUZ)) S RIST=X Q SUBSCRIBING PACKAGE: RADIOLOGY/NUCLEAR MEDICINE SUBSCRIBING DETAILS: Added 3/14/2008 DATE/TIME EDITED: MAR 14, 2008@16:01 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MO,SELINA WITH CONCURRENCE OF: FORT,WALLY NUMBER: 3545 IA #: 3545 FILE NUMBER: 45 GLOBAL ROOT: DGPT DATE CREATED: MAR 13, 2002 CUSTODIAL PACKAGE: REGISTRATION CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3545 ID: DGPT GLOBAL REFERENCE: DGPT( FIELD NUMBER: 80 FIELD NAME: PRINCIPLE DIAGNOSIS LOCATION: 70;11 ACCESS: Read w/Fileman FIELD NUMBER: DGPT('AAD', ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: The Clinical Case Registries system needs access to the 'AAD' x-ref (admission date) and for field #80 (principle diagnosis). STATUS: Active MAIL MESSAGE: 34235452 KEYWORDS: Clinical Case Registry KEYWORDS: ROR SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES ISC: Hines SUBSCRIBING DETAILS: The Clinical Registries system needs to utilize the 'AAD' x-ref when running it's registry update process. The x-ref orders patients by admission date. Field #80 also needs to be accessed to ascertain if the patient received any Diagnoses that would warrant them entry to the registry. NUMBER: 3546 IA #: 3546 FILE NUMBER: 40.8 GLOBAL ROOT: DG(40.8, DATE CREATED: MAR 14, 2002 CUSTODIAL PACKAGE: REGISTRATION USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: File 40.8 access ID: DG(40.8, GLOBAL REFERENCE: DG(40.8,DO,0 FIELD NUMBER: .07 FIELD NAME: Institution File Pointer LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Field is a pointer to the INSTITUTION file (#4). GLOBAL REFERENCE: DG(40.8,'AD' FIELD NUMBER: .07 FIELD NAME: Institution File Pointer LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: See above. GENERAL DESCRIPTION: The Patient Representative package would like access to the "AD" cross-reference of the MEDICAL CENTER DIVISION file (#40.8), a cross-reference on the Institution File Pointer field (#.07). Patient Rep will use this cross-reference to screen choices for it's Division field. VIEWER: MARKS,MARY STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34232898 SUBSCRIBING PACKAGE: PATIENT REPRESENTATIVE SUBSCRIBING DETAILS: Patient Rep will use the "AD" cross-reference to screen choices for the Division file (#37) of the CONSUMER CONTACT file (#745.1). SUBSCRIBING PACKAGE: IMAGING NUMBER: 3547 IA #: 3547 FILE NUMBER: 357.69 GLOBAL ROOT: IBE(357.69, DATE CREATED: MAR 20, 2002 CUSTODIAL PACKAGE: AUTOMATED INFO COLLECTION SYS USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: File TYPE OF VISIT(#357.69) read access by CPT code ID: IBE(357.69, GLOBAL REFERENCE: IBE(357.69, FIELD NUMBER: .01 FIELD NAME: CODE LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman GENERAL DESCRIPTION: Patient Care Encounter will use $D(^IBE(357.69,D0)) to verify if a CPT code in the V CPT(#9000010.18) file exists in the Type of Visit(#357.69) file. If the CPT code is found in this file, the QUANTITY(#.16) field in the V CPT file will be set to 1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34254957 SUBSCRIBING PACKAGE: PCE PATIENT CARE ENCOUNTER NUMBER: 3548 IA #: 3548 DATE CREATED: MAR 25, 2002 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIULC1 NAME: TIUCL1, Entry Point: DOCCLASS ID: TIULC1 STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34271959 COMPONENT/ENTRY POINT: DOCCLASS(TIUTYP) COMPONENT DESCRIPTION: The extrinsic function $$DOCCLASS^TIULC1(TIUTYP) returns the IEN in the TIU DOCUMENT DEFINITION File (#8925.1) for the document class associated with the specified document type (TIUTYP). VARIABLES: TIUTYP TYPE: Input VARIABLES DESCRIPTION: This is the ien in file 8925.1 of the DOCUMENT TYPE. SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING NUMBER: 3549 IA #: 3549 DATE CREATED: APR 01, 2002 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED ROUTINE: VAFCHFS NAME: VAFC HFS SCRATCH ID: VAFCHFS GENERAL DESCRIPTION: The MPI/PD Data Quality Management team, working on the Master Patient Index (MPI) at Austin, needs access to facility information to improve data quality and resolve differences on the MPI. Functionality was provided in DG*5.3*414, released Jan 03, 2002, to enable them to remotely retrieve facility data through remote procedure calls (RPCs). This was done by establishing the "VAFC HFS SCRATCH" entry in the PARAMETER DEFINITION (#8989.51) file in DG*5.3*414. CLINICAL INFO RESOURCE NETWORK routines would like to use the "VAFC HFS SCRATCH" entry in the PARAMETER DEFINITION (#8989.51) file to access, open, use, and close the HFS directory for RPCs. Master Patient Index/Patient Demographics (MPI/PD) is requesting an IA with Registration to reference the "VAFC HFS SCRATCH" entry in routine RGMTHFS. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34311787 SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 3550 IA #: 3550 FILE NUMBER: 870 GLOBAL ROOT: HLCS(870, DATE CREATED: AUG 22, 2002 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: HLCS(870,'C' ID: HLCS(870, GLOBAL REFERENCE: HLCS(870,'C' GLOBAL DESCRIPTION: The ^HLCS(870,"C",site,ien) verifies that site has a logical link of ien in the logical link file. GENERAL DESCRIPTION: This general purpose integration agreement exists for packages needing to access the "C" cross-reference in the HL Logical Link file (#870). All packages that desire to be subscribers to this integration agreement must submit the details for their use of the "C" cross-reference to the VistA HL7 package developers for approval. The cross-reference access details will be included in the individual subscriber section of this agreement. VIEWER: SCHLEHUBER,CAMERON VIEWER: GARCIA,JOSE STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34991530 SUBSCRIBING PACKAGE: MASTER PATIENT INDEX ISC: Birmingham SUBSCRIBING DETAILS: Subscriber: MPI Austin Method: The MPI Austin software would like to look at ^HLCS(870,"C",site ien) for a screen to only allow the selection of a site that has a HL7 logical link established. Details: The code used by MPI code to access the "C" cross-reference is shown below. ASKST() ; N DIC,X,Y,DTOUT,DUOUT SITE S DIC="^DIC(4,",DIC(0)="QEAM",DIC("A")="Select the site to send to: " S DIC("S")="I $D(^HLCS(870,""C"",+Y))" D ^DIC I $D(DTOUT)!($D(DUOUT)) Q 0 I Y<1 G SITE Q $$STA^XUAF4(+Y) SUBSCRIBING PACKAGE: KERNEL ISC: Oakland SUBSCRIBING DETAILS: Subscriber: Kernel Master File Server (MFS) Method: MFS uses the ^HLCS(870,"C",SITE-IEN,LINK-IEN) cross-reference to determine which sites are to receive update messages. Details: The code used when accessing the "C" cross-reference is shown below. S (I,J)=0 F S I=$O(^HLCS(870,"C",I)) Q:'I D .S J=$O(^HLCS(870,"C",I,0)) Q:'J .S LLNK=$P($G(^HLCS(870,J,0)),U) .S HLL("LINKS",I)="XUMF MFK^"_LLNK (See integration agreement# 3734 for access of piece one(1) of the zero node.) NUMBER: 3551 IA #: 3551 FILE NUMBER: 101.43 GLOBAL ROOT: ORD(101.43, DATE CREATED: APR 04, 2002 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3551 ID: ORD(101.43, GENERAL DESCRIPTION: With the development of the Med Order Button for BCMA version 2.0, BCMA requires the ability to perform direct global reads on the following fields; ^ORD(101.43,D0,.1)= (#.1) INACTIVATED [1D] Used to validate that the scanned medication is still active for use as a medication. ^ORD(101.43,D0,0)= (#.01) NAME [1F] Used to display the medication name back to the user when they scan a medication. ^ORD(101.43,D0,PS)= (#50.1) INPATIENT MED [1S] ^ (#50.2) OUTPATIENT MED [2S] ==>^ (#50.3) IV BASE [3S] ^ (#50.4) IV ADDITIVE [4S] ^ ==>(#50.5) SUPPLY [5S] ^ (#50.6) NON-FORMULARY [6S] ^ Used to determine that the medication scanned is marked for Inpatient Med and if the med is an IV base or additive. "ID" cross-reference file to determine if the drug scanned is not in the CPRS orderable item file. STATUS: Active DURATION: Till Otherwise Agreed EXPIRATION DATE: DEC 31, 2002 MAIL MESSAGE: 34335147 KEYWORDS: med order button KEYWORDS: BCMA KEYWORDS: CPRS KEYWORDS: 101.43 KEYWORDS: ORDERABLE ITEM SUBSCRIBING PACKAGE: BAR CODE MED ADMIN ISC: Birmingham SUBSCRIBING DETAILS: This DBIA is only good for 1 year. BCMA will work with CPRS to convert these direct reads in to an API. NUMBER: 3552 IA #: 3552 DATE CREATED: APR 04, 2002 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: HLCS2 NAME: $$PARAM EXTRINSIC FUNCTION IN ROUTINE HLCS2 ID: HLCS2 GENERAL DESCRIPTION: The $$PARAM^HLCS2 API is used extensively by the Health Level 7 (HL7) package. This API returns a string of text, delimited by the up-arrow, holding critical environment information. This API is being made available to the VistA community on a controlled subscription basis. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34312043 COMPONENT/ENTRY POINT: $$PARAM COMPONENT DESCRIPTION: The following example API call demonstrates syntax, and also shows a sample of the output of this call. >W $$PARAM^HLCS2 81^BALTIMORE.MED.VA.GOV^P^512^MARYLAND HCS^512^3030^HL7 MSG^^^^ When $$PARAM^HLCS2 is called, a string is returned containing key HL7 environment values. The values in the string are delimited by the up-arrow ('^'). The pieces of data returned, and the source for the data, is listed below. Piece Type-Data Data Source -------------------------------------------------------------------- 1 Numeric Domain file pointer DOMAIN field (#.02) in the HL COMMUNICATION PARAMETERS file (#869.3). 2 Text Domain name NAME field (#.01) in the DOMAIN file entry. (See piece #1.) 3 Text Set of codes DEFAULT PROCESSING ID field (#.03) in the HL COMMUNICATION PARAMETERS file (#869.3). 4 Numeric Institution pointer INSTITUTION field (#.04) in the HL COMMUNICATION PARAMETERS file (#869.3). 5 Text Institution name NAME field (#.01) in the INSTITUTION file (#4). (See piece 4.) 6 Text Station number STATION field (#99) in the INSTITUTION file (#4). (See piece 4.) 7 Numeric Mail Group pointer MAIL GROUP field (#.05) in the HL COMMUNICATION PARAMETERS file (#869.3). 8 Text Mail Group name NAME field (#.01) in the MAIL GROUP file (#3.8). (See piece 7.) 9 Numeric PURGE COMPLETED MESSAGES field (#41) in the HL COMMUNICATION PARAMETERS file (#869.3). 10 Numeric PURGE AWAITING ACK MESSAGES field (#42) in the HL COMMUNICATION PARAMETERS file (#869.3). 11 Numeric PURGE ALL MESSAGES field (#43) in the HL COMMUNICATION PARAMETERS file (#869.3). 12 Numeric DEFAULT RETENTION field (#51) in the HL COMMUNICATION PARAMETERS file (#869.3). VARIABLES: $$PARAM TYPE: Output SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING SUBSCRIBING PACKAGE: KERNEL SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE SUBSCRIBING PACKAGE: VDEF SUBSCRIBING PACKAGE: ADVERSE REACTION TRACKING SUBSCRIBING PACKAGE: GEN. MED. REC. - VITALS SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY SUBSCRIBING PACKAGE: MYHEALTHEVET SUBSCRIBING PACKAGE: REGISTRATION SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE DBA Comments: 9/7/12-mm: Added AMIE as a subscriber for DVBA*2.7*181, CAPRI Virtual VA, Voc. Rehab Enhancements & Defect Fixes. CAPRI is implementing a web services client interface with the Master Veteran Index that uses HL7v3 messaging. $$PARAM^HLCS2 will be used to retrieve the Default Processing ID. DATE/TIME EDITED: SEP 07, 2012@10:34 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: MCGINNIS,RON WITH CONCURRENCE OF: MOORE,JIM NUMBER: 3553 IA #: 3553 DATE CREATED: APR 04, 2002 CUSTODIAL PACKAGE: MASTER PATIENT INDEX VISTA USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MPIF001 NAME: SET TEST SYSTEM PATIENT ICN ID: MPIF001 VIEWER: SCHLEHUBER,CAMERON VIEWER: REED,DANNY VIEWER: CHESNEY,CHRISTINE M STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34322948 COMPONENT/ENTRY POINT: $$SETICN COMPONENT DESCRIPTION: $$SETICN^MPIF001(DFN,ICN,CHKSUM) This function updates the ICN (#991.01) and ICN Checksum (#991.02) fields in the Patient file (#2). VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of patient in Patient file (#2) VARIABLES: ICN TYPE: Input VARIABLES DESCRIPTION: ICN (without checksum) to be updated VARIABLES: CHKSUM TYPE: Input VARIABLES DESCRIPTION: ICN checksum to be updated VARIABLES: $$SETICN TYPE: Output VARIABLES DESCRIPTION: 1 - successfully updated -1^error message - problem while updating SUBSCRIBING PACKAGE: CONSULT/REQUEST TRACKING ISC: Salt Lake City SUBSCRIBING DETAILS: This entry point will be called in TEST system environments only. EDITOR: RUTHERFORD,JERALD F NUMBER: 3554 IA #: 3554 DATE CREATED: APR 08, 2002 CUSTODIAL PACKAGE: CLINICAL INFO RESOURCE NETWORK USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RGEX03 NAME: DBIA3554 ID: RGEX03 GENERAL DESCRIPTION: MPI requries the use of the GETEX^RGEX03 API for a remote procedure call to the VA sites from the MPI Austin. This is to retrieve exception data from the treating facilities for data quality management. STATUS: Active MAIL MESSAGE: 34339147 COMPONENT/ENTRY POINT: GETEX COMPONENT DESCRIPTION: Returns an array of exception data for a patient. VARIABLES: RETURN TYPE: Both VARIABLES DESCRIPTION: Array to pass back exception data. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: IEN of Patient file (#2) SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA NUMBER: 3555 IA #: 3555 FILE NUMBER: 4 GLOBAL ROOT: DIC(4 DATE CREATED: APR 09, 2002 CUSTODIAL PACKAGE: KERNEL USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Enter/edit Austin Entry ID: DIC(4 GENERAL DESCRIPTION: The HL7 package has an agreement to use a FileMan FILE^DICN call to edit the following fields in the INSTITUTION (#4) file. NAME (#.01), STATE (#.02), STATUS (#11), FACILITY TYPE (#13), STATION NUMBER (#99) and OFFICAL VA NAME (#100). This is done in pre-install routine, PRE^HLP92, to create the AUSTIN entry in the INSTITUTION file if it is not present. This functionality is in support of the Federal Heath Information Exchange (FHIE). The entry created will have the following values. NAME: AUSTIN STATE: TEXAS STATUS: National FACILITY TYPE: DPC STATION NUMBER: 200 OFFICAL VA NAME: AUSTIN GLOBAL REFERENCE: ^DIC(4,D0,0) .01 NAME 0;1 Write w/Fileman .02 STATE 0;2 Write w/Fileman 11 STATUS 0;11 Write w/Fileman GLOBAL REFERENCE: ^DIC(4,D0,3) 13 FACILITY TYPE 3;1 Write w/Fileman GLOBAL REFERENCE: ^DIC(4,D0,99) 99 STATION NUMBER 99;1 Write w/Fileman 100 OFFICIAL VA NAME 99;3 Write w/Fileman STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34340915 SUBSCRIBING PACKAGE: HEALTH LEVEL SEVEN NUMBER: 3556 IA #: 3556 DATE CREATED: APR 11, 2002 CUSTODIAL PACKAGE: AUTOMATED LAB INSTRUMENTS CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: LA7QRY NAME: GET LAB RESULTS ID: LA7QRY CREATOR: MCCORMACK,JOHN GENERAL DESCRIPTION: Clinical Registries system requires access to the API GCPR^LA7QRY to analyze lab tests and results. This API is required during the registry update process and the data extract process. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 38029705 KEYWORDS: Clinical Registries KEYWORDS: Hepatitis C KEYWORDS: Lab HDR KEYWORDS: Lab Results COMPONENT/ENTRY POINT: GCPR COMPONENT DESCRIPTION: This component is passed a patient identifier, start and end dates (for when specimens were taken) and NLT and/or LOINC codes and specimen types. The component passes back an array with details of any lab tests with results that occurred within the start and end dates that were for the LOINC or NLT codes and specimen types that were passed in. The structure of the returned values is as described in the VistA Laboratory VA HDR HL7 Interface Specification. This document is available from the VA VistA Documentation Library http://www.va.gov/vdl/ Example call: S LA7PTID="0000000000v000000^PI" S LA7SDT="3000101" S LA7EDT=$$NOW^XLFDT S LA7SC="*" S LA7SPEC="*" S LA7DEST=$NA(^TMP("ZZTMP",$J)) S X=$$GCPR^LA7QRY(LA7PTID,LA7SDT,LA7EDT,.LA7SC,. LA7SPEC,.LA7ERR,LA7DEST," |^~\&") VARIABLES: LA7PTID TYPE: Input VARIABLES DESCRIPTION: Patient identifier, either SSN or MPI/ICN or medical record number. If MPI/ICN then should be full ICN (10 digit number followed by "V" and six digit checksum) Pass in the 2nd piece of this variable the type of identifier: SS = Social Security number PI = VA MPI Integration Control Number MR = medical record number of patient in file PATIENT/IHS (#9000001) Example: 1000720100V271387^PI 123456789^SS 123456789^MR VARIABLES: LA7SDT TYPE: Input VARIABLES DESCRIPTION: Start date of query (FileMan D/T, time optional). VARIABLES: LA7EDT TYPE: Input VARIABLES DESCRIPTION: End date of query (FileMan D/T, time optional) (FileMan D/T^type of date ("CD" or "RAD") Both start and end date values can pass a parameter in the second piece to indicate that the date values are for specimen collection date/time (CD) or results available date (RAD). Example: LA7SDT="2991001.1239^CD" LA7EDT="2991002.0331^CD" LA7SDT="3010201^RAD" LA7EDT="3010201^RAD" VARIABLES: LA7SC TYPE: Input VARIABLES DESCRIPTION: Array of search codes, either NLT or LOINC (code^coding system ("NLT" or "LN"); Example: LA7SC(1)="89628.0000^NLT" LA7SC(2)="84330.0000^NLT" LA7SC(3)="84295.0000^NLT" LA7SC(4)="14749-6^LN" or The "*" (wildcard) for any code; Example: LA7SC="*" or A list of subscripts (separated by commas) from where the results will be extracted ("CH", "MI" or "SP"). Example: LA7SC="CH,MI" (CH and MI results only). Pass in the 2nd piece of LA7SC the indicator (1) to return VUID when available. Example: LA7SC="*^1" or LA7SC="CH,MI^1" VARIABLES: LA7SPEC TYPE: Input VARIABLES DESCRIPTION: Array of specimen types using HL7 source table 0070 or "*" (wildcard) for any code. Currently specimen type only supported for CH and MI subscripted tests. Example: LA7SPEC="*" or LA7SPEC(1)="UR" LA7SPEC(2)="SER" LA7SPEC(3)="PLAS" VARIABLES: LA7DEST TYPE: Both VARIABLES DESCRIPTION: Closed root global reference to return search results (optional). If this parameter is omitted or equals an empty string, then node ^TMP("HLS",$J) is used. Example: LA7DEST=$NA(^TMP("ZZTMP",$J)). The information returned in this global reference uses the structure of an HL7 message to format the results of the query. VARIABLES: LA7HL7 TYPE: Input VARIABLES DESCRIPTION: HL7 field separator and encoding characters (4) to use to encode results (optional). If undefined or incomplete (length<5) then field separator "|" and encoding characters "^\~&" are used. See HL7 standard for further information of use and purpose of field separator and encoding characters. VARIABLES: LA7ERR TYPE: Output VARIABLES DESCRIPTION: Array (by reference) containing any errors. LA7ERR(error number) = text of error message The following error codes and text are returned: 1 Invalid patient identifier passed 2 No patient found with requested identifier 3 No laboratory record for requested patient 4 Database error - missing laboratory record for requested patient 5 If ICN passed and MPI returns error then the error message for a given ICN 6 Unknown search code "__" passed, where is a LOINC or NLT code passed in input parameter LA7SC. 7 Invalid list of subscripts: '_, where is the value passed in input parameter LA7SC. 99 No results found for requested parameters SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES ISC: Hines SUBSCRIBING DETAILS: Clinical Registries system requires access to the API GCPR^LA7QRY to analyze lab tests and results. This API is required during the registry update process and the data extract process. SUBSCRIBING PACKAGE: HEALTH DATA REPOSITORY SUBSCRIBING PACKAGE: CLINICAL PROCEDURES SUBSCRIBING PACKAGE: SURGERY DBA Comments: 5/21/14-MC: Surgery added as a subscriber. Patch is SR*3.0*180. Requested by James Harris and approval received from Carol Anzaldua. DATE ACTIVATED: JUL 14, 2010 DATE/TIME EDITED: JUL 14, 2010@14:51 ACTION: APPROVED AT THE REQUEST OF: MCCORMACK,JOHN DATE/TIME EDITED: MAY 21, 2014@11:20 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: HARRIS,JAMES WITH CONCURRENCE OF: ANZALDUA,CAROL DATE/TIME EDITED: MAY 21, 2014@11:21 ACTION: SUBSCRIBER ADDED NUMBER: 3557 IA #: 3557 FILE NUMBER: 69.9 GLOBAL ROOT: LAB(69.9, DATE CREATED: APR 11, 2002 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3557 ID: LAB(69.9, GLOBAL REFERENCE: LAB(69.9, FIELD NUMBER: .01 FIELD NAME: SITE NAME LOCATION: 0;1 ACCESS: Read w/Fileman FIELD NUMBER: 95.3 FIELD NAME: LOINC HISTORICAL MAPPING DATE LOCATION: 95;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: The Clinical Registries system requires access to field #95.3 of file #69.9 (this field indicates if the Loinc historical mapper has been run) and field #.01 of file #95.3 (to check if the Loinc code exists and if so get it's value and control digit). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34519838 KEYWORDS: Clinical Registries KEYWORDS: Hepatitis C SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES ISC: Hines SUBSCRIBING DETAILS: The Clinical Registries system requires access to field #95.3 of file #69.9 (this field indicates if the Loinc historical mapper has been run) and field #.01 of file #95.3 (to check if the Loinc code exists and if so get it's value and control digit). NUMBER: 3558 IA #: 3558 DATE CREATED: APR 12, 2002 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: ORMEVNT1 NAME: Process orders after Surgery ID: ORMEVNT1 GENERAL DESCRIPTION: This agreement allows the Surgery package to call routine ORMEVNT1 when a patient has a surgical procedure, for the purpose of automatically discontinuing and/or releasing orders. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34360449 COMPONENT/ENTRY POINT: OR1(DA,X) COMPONENT DESCRIPTION: This entry point will automatically discontinue active orders and/or release new orders after a surgical procedure, based on local rules defined in the CPRS files OE/RR Auto-DC Rules #100.6 and OE/RR Patient Event #100.2. VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: The ien of the case in the Surgery file #130 VARIABLES: X TYPE: Input VARIABLES DESCRIPTION: The date/time the patient left the OR COMPONENT/ENTRY POINT: OR2(DA) COMPONENT DESCRIPTION: This entry point will make a note in the Activity Log for the surgical event when the date/time the patient left the OR is changed or deleted. VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: The ien of the case in the Surgery file #130 SUBSCRIBING PACKAGE: SURGERY ISC: Birmingham NUMBER: 3559 IA #: 3559 FILE NUMBER: 130 GLOBAL ROOT: SRF( DATE CREATED: APR 12, 2002 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: Read access to Surgery file ID: SRF( GLOBAL REFERENCE: SRF(D0,0) FIELD NUMBER: .01 FIELD NAME: PATIENT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Pointer to Patient file #2 FIELD NUMBER: .02 FIELD NAME: OPERATING ROOM LOCATION: 0;2 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Pointer to Operating Room file #131.7, where .01 = pointer to Hospital Location file #44 FIELD NUMBER: .04 FIELD NAME: SURGICAL SPECIALTY LOCATION: 0;4 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Pointer to Local Surgical Specialty file #137.45 GLOBAL REFERENCE: SRF(D0,'CON') FIELD NUMBER: 35 FIELD NAME: CONCURRENT CASE LOCATION: CON;1 ACCESS: Direct Global Read & w/Fileman FIELD DESCRIPTION: Pointer to Surgery file #130, of another operation at same time GENERAL DESCRIPTION: This agreement allows CPRS to look at specific fields in the Surgery file to be able to properly manage orders when the patient leaves the OR. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34367815 SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3560 IA #: 3560 FILE NUMBER: 9000010.18 GLOBAL ROOT: AUPNVCPT( DATE CREATED: APR 15, 2002 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Birmingham USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DBIA3560 ID: AUPNVCPT( GLOBAL REFERENCE: AUPNVCPT( FIELD NUMBER: .01 FIELD NAME: CPT LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .03 FIELD NAME: VISIT LOCATION: 0;3 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .05 FIELD NAME: DIAGNOSIS LOCATION: 0;5 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: AUPNVCPT('C' GLOBAL DESCRIPTION: Patient Name Cross Reference STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34373617 SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT ISC: Birmingham SUBSCRIBING DETAILS: The Pharmacy Benefits Management package extracts outpatient visit data monthly to support the VA National Formulary, disease management issues and patient safety initiatives. The following references are needed for extract. NUMBER: 3561 IA #: 3561 DATE CREATED: JUL 03, 2003 CUSTODIAL PACKAGE: TOOLKIT USAGE: Supported TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MXMLDOM NAME: M XML PARSER ID: MXMLDOM GENERAL DESCRIPTION: This utility provides a M based XML version 1.0 parser. It supports both the SAX interface and the DOM interface. STATUS: Active MAIL MESSAGE: 36681720 COMPONENT/ENTRY POINT: $$EN COMPONENT DESCRIPTION: This is the entry point to perform initial processing of the XML document. The client application must first call this entry point to build the in-memory image of the document before the remaining methods can be applied. The return value is a handle to the document instance that was created and is used by the remaining API calls to identify a specific document instance. VARIABLES: DOC TYPE: Input VARIABLES DESCRIPTION: Either a closed reference to a global root containing the document or a filename and path reference identifying the document on the host system. If a global root is passed, the document must either be stored in standard FileMan word-processing format or may occur in sequentially numbered nodes below the root node. Thus, if the global reference is "^XYZ , the global must be of one of the following formats: ^XYZ(1,0) = "LINE 1 ^XYZ(2,0) = "LINE 2 ... or ^XYZ(1) = "LINE 1 ^XYZ(2) = "LINE 2 ... VARIABLES: OPT TYPE: Input VARIABLES DESCRIPTION: A list of option flags that control parser behavior. Recognized option flags are: 0 = Terminate parsing on encountering a warning. (By default, the parser terminates only when a conformance or validation error is encountered.) VARIABLES: $$EN TYPE: Output VARIABLES DESCRIPTION: Returns a nonzero handle to the document instance if parsing completed successfully, or zero otherwise. This handle is passed to all other API methods to indicate which document instance is being referenced. This allows for multiple document instances to be processed concurrently. COMPONENT/ENTRY POINT: DELETE COMPONENT DESCRIPTION: Deletes the specified document instance. A client application should always call this entry point when finished with a document instance. VARIABLES: HANDLE TYPE: Input VARIABLES DESCRIPTION: The value returned by the $$EN^MXMLDOM call that created the in-memory document image. COMPONENT/ENTRY POINT: $$NAME COMPONENT DESCRIPTION: Returns the name of the element at the specified node within the document parse tree. VARIABLES: HANDLE TYPE: Input VARIABLES DESCRIPTION: The value returned by the $$EN^MXMLDOM call that created the in-memory document image. VARIABLES: NODE TYPE: Input VARIABLES DESCRIPTION: The node whose associated element name is being retrieved. VARIABLES: $$NAME TYPE: Output VARIABLES DESCRIPTION: The name of the element associated with the specified node. COMPONENT/ENTRY POINT: $$CHILD COMPONENT DESCRIPTION: Returns the node of the first or next child of a given parent node, or 0 if there are none remaining. VARIABLES: HANDLE TYPE: Input VARIABLES DESCRIPTION: The value returned by the $$EN^MXMLDOM call that created the in-memory document image. VARIABLES: PARENT TYPE: Input VARIABLES DESCRIPTION: The node whose children are being retrieved. VARIABLES: CHILD TYPE: Input VARIABLES DESCRIPTION: If specified, this is the last child node retrieved. The function will return the next child in the list. If the parameter is zero or missing, the first child is returned. VARIABLES: $$CHILD TYPE: Output VARIABLES DESCRIPTION: The next child node or zero if there are none remaining. COMPONENT/ENTRY POINT: $$SIBLING COMPONENT DESCRIPTION: Returns the node of the specified node's immediate sibling, or 0 if there is none. VARIABLES: HANDLE TYPE: Input VARIABLES DESCRIPTION: The value returned by the $$EN^MXMLDOM call that created the in-memory document image. VARIABLES: NODE TYPE: Input VARIABLES DESCRIPTION: The node in the document tree whose sibling is being retrieved. VARIABLES: $$SIBLING TYPE: Output VARIABLES DESCRIPTION: The node corresponding to the immediate sibling of the specified node, or zero if there is none. COMPONENT/ENTRY POINT: $$PARENT COMPONENT DESCRIPTION: Returns the parent node of the specified node, or 0 if there is none. VARIABLES: HANDLE TYPE: Input VARIABLES DESCRIPTION: The value returned by the $$EN^MXMLDOM call that created the in-memory document image. VARIABLES: NODE TYPE: Input VARIABLES DESCRIPTION: The node in the document tree whose parent is being retrieved. VARIABLES: $$PARENT TYPE: Output VARIABLES DESCRIPTION: The parent node of the specified node, or zero if there is no parent. COMPONENT/ENTRY POINT: TEXT COMPONENT DESCRIPTION: Extracts non-markup text associated with the specified node. VARIABLES: HANDLE TYPE: Input VARIABLES DESCRIPTION: The value returned by the $$EN^MXMLDOM call that created the in-memory document image. VARIABLES: NODE TYPE: Input VARIABLES DESCRIPTION: The node in the document tree that is being referenced by this call. VARIABLES: TEXT TYPE: Both VARIABLES DESCRIPTION: This parameter must contain a closed local or global array reference that is to receive the text. The specified array is deleted before being populated. COMPONENT/ENTRY POINT: $$TEXT COMPONENT DESCRIPTION: Extracts non-markup text associated with the specified node. VARIABLES: HANDLE TYPE: Input VARIABLES DESCRIPTION: The value returned by the $$EN^MXMLDOM call that created the in-memory document image. VARIABLES: NODE TYPE: Input VARIABLES DESCRIPTION: The node in the document tree that is being referenced by this call. VARIABLES: TEXT TYPE: Both VARIABLES DESCRIPTION: This parameter must contain a closed local or global array reference that is to receive the text. The specified array is deleted before being populated. VARIABLES: $$TEXT TYPE: Output VARIABLES DESCRIPTION: If called as an extrinsic function, the return value is true if text was retrieved, or false if not. COMPONENT/ENTRY POINT: CMNT COMPONENT DESCRIPTION: Extracts comment text associated with the specified node. VARIABLES: HANDLE TYPE: Input VARIABLES DESCRIPTION: The value returned by the $$EN^MXMLDOM call that created the in-memory document image. VARIABLES: NODE TYPE: Input VARIABLES DESCRIPTION: The node in the document tree that is being referenced by this call. VARIABLES: TEXT TYPE: Both VARIABLES DESCRIPTION: This parameter must contain a closed local or global array reference that is to receive the text. The specified array is deleted before being populated. COMPONENT/ENTRY POINT: $$CMNT COMPONENT DESCRIPTION: Extracts comment text associated with the specified node. VARIABLES: HANDLE TYPE: Input VARIABLES DESCRIPTION: The value returned by the $$EN^MXMLDOM call that created the in-memory document image. VARIABLES: NODE TYPE: Input VARIABLES DESCRIPTION: The node in the document tree that is being referenced by this call. VARIABLES: TEXT TYPE: Both VARIABLES DESCRIPTION: This parameter must contain a closed local or global array reference that is to receive the text. The specified array is deleted before being populated. VARIABLES: $$CMNT TYPE: Output VARIABLES DESCRIPTION: If called as an extrinsic function, the return value is true if text was retrieved, or false if not. COMPONENT/ENTRY POINT: $$ATTRIB COMPONENT DESCRIPTION: Retrieves the first or next attribute associated with the specified node. VARIABLES: HANDLE TYPE: Input VARIABLES DESCRIPTION: The value returned by the $$EN^MXMLDOM call that created the in-memory document image. VARIABLES: NODE TYPE: Input VARIABLES DESCRIPTION: The node whose attribute name is being retrieved. VARIABLES: ATTRIB TYPE: Output VARIABLES DESCRIPTION: The name of the last attribute retrieved by this call. If null or missing, the first attribute associated with the specified node is returned. Otherwise, the next attribute in the list is returned. VARIABLES: $$ATTRIB TYPE: Output VARIABLES DESCRIPTION: The name of the first or next attribute associated with the specified node, or null if there are none remaining. COMPONENT/ENTRY POINT: $$VALUE COMPONENT DESCRIPTION: Retrieves the value associated with the named attribute. VARIABLES: HANDLE TYPE: Input VARIABLES DESCRIPTION: The value returned by the $$EN^MXMLDOM call that created the in-memory document image. VARIABLES: NODE TYPE: Input VARIABLES DESCRIPTION: The node whose attribute value is being retrieved. VARIABLES: ATTRIB TYPE: Input VARIABLES DESCRIPTION: The name of the attribute whose value is being retrieved by this call. VARIABLES: $$VALUE TYPE: Output VARIABLES DESCRIPTION: The value associated with the specified attribute. NUMBER: 3562 IA #: 3562 DATE CREATED: APR 16, 2002 CUSTODIAL PACKAGE: SURGERY CUSTODIAL ISC: Birmingham USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: SROTIUD NAME: Calls to Routine SROTIUD ID: SROTIUD GENERAL DESCRIPTION: This DBIA documents calls to the routine SROTIUD. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34379925 COMPONENT/ENTRY POINT: OS(DA) COMPONENT DESCRIPTION: This entry point will delete the existing pointer in the TIU OPERATIVE SUMMARY field (#1000) of the Surgery file (#130) when a document is deleted, and it will then call the TIU API to generate a new Stub entry in TIU for that case. VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: The ien of the case in the Surgery file #130. COMPONENT/ENTRY POINT: NON(DA) COMPONENT DESCRIPTION: This entry point will delete the existing pointer in the TIU PROCEDURE REPORT (NON-OR) field (#1002) of the Surgery file (#130) when a document is deleted, and it will then call the TIU API to generate a new Stub entry in TIU for that case. VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: The ien of the case in the Surgery file #130. COMPONENT/ENTRY POINT: NURS(DA) COMPONENT DESCRIPTION: This entry point will delete the existing pointer in the TIU NURSE INTRAOP REPORT field (#1001) of the Surgery file (#130) when a document is deleted and then call the TIU API to generate a new Stub entry in TIU for that case. VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: This is the IEN of the case in the Surgery file #130. COMPONENT/ENTRY POINT: ANES(DA) COMPONENT DESCRIPTION: This entry point will delete the existing pointer in the TIU ANESTHESIA REPORT field (#1003) of the Surgery file (#130) when a document is deleted and then call the TIU API to generate a new Stub entry in TIU for that case. VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: This is the IEN of the case in the Surgery file #130. SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 3563 IA #: 3563 DATE CREATED: APR 17, 2002 CUSTODIAL PACKAGE: RADIOLOGY/NUCLEAR MEDICINE CUSTODIAL ISC: Chicago USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: RAO7PC4 NAME: RAO7PC4 ID: RAO7PC4 GENERAL DESCRIPTION: Allows CPRS to use EN1^RAO7PC4 and SET1^RAO7PC4 to obtain and display infomation for alert follow-up actions. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34380935 COMPONENT/ENTRY POINT: EN1 COMPONENT DESCRIPTION: Variable XQADATA must be set by subscribing package. Custodial package displays follow-up action for Imaging Exam/Request Changed alert in character (roll and scroll) based environment. VARIABLES: XQADATA TYPE: Input VARIABLES DESCRIPTION: This variable is used within the Kernel Alert utility to store a package-specific data string when an alert is triggered. It is then used in the alert follow-up action to display data appropriate for the alert. COMPONENT/ENTRY POINT: SET1 COMPONENT DESCRIPTION: Variable XQADATA must be set by subscribing package. Custodial package sets data in ^TMP($J,"RAE4") to be used by the subscribing package in follow-up action displays for the Imaging Exam/Request Changed alert. Subscribing package must KILL ^TMP($J,"RAE4") after using the data. The intent of this entry point is to return data for use in GUI displays but subscribing packages can use the api in other contexts as well. VARIABLES: XQADATA TYPE: Input VARIABLES DESCRIPTION: This variable is used within the Kernel Alert utility to store a package-specific data string when an alert is triggered. It is then used in the alert follow-up action to display data appropriate for the alert. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City NUMBER: 3564 IA #: 3564 DATE CREATED: APR 25, 2002 CUSTODIAL PACKAGE: BAR CODE MED ADMIN CUSTODIAL ISC: Birmingham USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: PSBAPIPM NAME: DBIA3564 ID: PSBAPIPM CREATOR: SINGER,RICHARD GENERAL DESCRIPTION: The entry point EN^PSBAPIPM is provided by the Bar Code Medication Administration (BCMA) package to provide information to Inpatient Medications to be used in determining the start date for a renewed order. The MOB entry point is used by Inpatient Medications to get information obtained from the BCMA/CPRS Med Order function. The MOBR is used by Inpatient Medications to notify BCMA that the order has been accepted and processed by Inpatient Pharmacy. STATUS: Active MAIL MESSAGE: 34407274 KEYWORDS: PSBAPIPM COMPONENT/ENTRY POINT: $$EN COMPONENT DESCRIPTION: Provides Inpatient Medications with the type, date, and status of a patients last BCMA action. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The patients internal entry number from the PATIENT FILE, 2. VARIABLES: PSBORDX TYPE: Input VARIABLES DESCRIPTION: The pharmacy order number. VARIABLES: PSBSTUS TYPE: Output VARIABLES DESCRIPTION: This is the status of the last action. VARIABLES: PSBLAST TYPE: Output VARIABLES DESCRIPTION: A FileMan date/time. This is the date of the last action. VARIABLES: PSBADMDT TYPE: Output VARIABLES DESCRIPTION: A FileMan date/time. This is the scheduled administration time. COMPONENT/ENTRY POINT: MOB COMPONENT DESCRIPTION: Provides Inpatient Medications with an array of data returned by the BCMA/CPRS Med Order function. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The patients internal entry number from the PATIENT FILE, 2. VARIABLES: PSBCORN TYPE: Input VARIABLES DESCRIPTION: The CPRS order number. VARIABLES: ARRAY TYPE: Output VARIABLES DESCRIPTION: ^TMP("PSB",$J,0) $P(1) = DFN $P(2) = CPRS order number $P(3) = Schedule ^TMP("PSB",$J,700,0) = Total number of dispense drugs ^TMP("PSB",$J,700,#) = IEN from file 50 ^TMP("PSB",$J,800,0) = Total number of additives ^TMP("PSB",$J,800,#) = IEN from file 52.6 ^TMP("PSB",$J,900,0) = Total number of solutions ^TMP("PSB",$J,900,#) = IEN from file 52.7 COMPONENT/ENTRY POINT: MOBR COMPONENT DESCRIPTION: This entry point is used by Inpatient Medications to notiy BCMA that the order has been processed or rejected. There is no return from this entry point. VARIABLES: DFN TYPE: Input VARIABLES DESCRIPTION: The internal entry number from PATIENT FILE, 2. VARIABLES: PSBCORN TYPE: Input VARIABLES DESCRIPTION: The CPRS order number. VARIABLES: PSBORDN TYPE: Input VARIABLES DESCRIPTION: The Inpatient Medications order number if processed, null if rejected. SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS ISC: Birmingham SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING SUBSCRIBING DETAILS: ADDED 20101103 DATE ACTIVATED: NOV 03, 2010 DATE/TIME EDITED: NOV 03, 2010@16:14 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: PULEO,ANTHONY WITH CONCURRENCE OF: TEMPLETON,SHANNON NUMBER: 3565 IA #: 3565 DATE CREATED: MAY 07, 2002 CUSTODIAL PACKAGE: LAB SERVICE CUSTODIAL ISC: Dallas USAGE: Controlled Subscription TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: LR7O ALL EVSEND RESULTS GENERAL DESCRIPTION: This event protocol is invoked by the lab package when lab results have been verified by a lab technician. Packages can hang their own protocols off this event to carry out various actions when lab results are verified, by editing this protocol in the PROTOCOL file (#101). At the time the event is triggered the variable OREMSG holds the pointer to the array containing the HL7 message created by Lab. Currently, this hold the value of ^TMP("LRCH",$J). Looking in this global will give all the order/result information in HL7 format. For example: ^TMP("LRCH",2176,1)=MSH|^~\&|LABORATORY|5000|||ORM 2)=PID||16|16;DPT(|HOOD,ROBIN 3)=PV1|I|14|||||||| 4)=ORC|RE|7090879^OR|17;3020507;1;CH;6979491.865777^LRCH||CM| |^ ^^20020507134223-0600^20020507134246-0600|20020507134223-0600 |5^MALMROSE,CARY|14^ANDERSON,DOCTOR||20020507134223-0600| 7)=OBR|1||81744.0000^Lithium^99NLT^198^LITHIUM^99LRT||2002050 7134223-0600||1||20020507134240-0600|0X500;SERUM;SNM;1;BLOOD ;99LRS^^^72;SER UM;99LRX|||CH 0507 1||20020507134246-0600||F|^^^^^R;9|14 8)=OBX|1|ST|81744.0000^Lithium^99NLT^198^LITHIUM^99LRT||3| mEq/L |.5-1.5|HH||F|||5^MALMROSE,CARY STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34466996 KEYWORDS: LAB RESULTS SUBSCRIBING PACKAGE: CLINICAL CASE REGISTRIES SUBSCRIBING DETAILS: SUBSCRIBING PACKAGE: PHARMACY BENEFITS MANAGEMENT NUMBER: 3566 IA #: 3566 DATE CREATED: APR 25, 2002 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUSRVPL NAME: Imaging - TIUSRVPL ID: TIUSRVPL GENERAL DESCRIPTION: Execution at GETILST is called to retrieve a list of associated images for a document entry in TIU. Execution at PUTIMAGE is called to store an image pointer in file 8925.91, creating an Image-To-Document link. Execution at DELIMAGE is called to delete an image pointer in a TIU document. Execution at GETDLST is called to get a list of associated TIU documents for a given image entry. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34408341 COMPONENT/ENTRY POINT: PUTIMAGE COMPONENT DESCRIPTION: API to store an Image pointer in file 8925.91. VARIABLES: IMGDA TYPE: Input VARIABLES DESCRIPTION: This variable contains an Image pointer. VARIABLES: TIUY TYPE: Output VARIABLES DESCRIPTION: Return variable will be a two-piece value, first piece will indicate success (1) of failure (0) and the second piece indicate the reason of failure. COMPONENT/ENTRY POINT: DELIMAGE COMPONENT DESCRIPTION: API to delete the image pointer in the DOCUMENT FILE. VARIABLES: TIUY TYPE: Output VARIABLES DESCRIPTION: Return variable is a two-piece value, first piece indicates success (1) or failure (0) and second piece is the reason for the failure. VARIABLES: TIUDA TYPE: Input VARIABLES DESCRIPTION: The document pointer (ien). VARIABLES: IMGDA TYPE: Input VARIABLES DESCRIPTION: The image pointer (ien) COMPONENT/ENTRY POINT: GETILST COMPONENT DESCRIPTION: API to get a list of associated image pointer for a specified DOCUMENT. VARIABLES: TIUY TYPE: Output VARIABLES DESCRIPTION: A sequential array of image pointers (ien). VARIABLES: TIUDA TYPE: Input VARIABLES DESCRIPTION: The DOCUMENT pointer (ien). COMPONENT/ENTRY POINT: GETDLST COMPONENT DESCRIPTION: API to get a list of associated documents for a specified Image pointer. VARIABLES: TIUY TYPE: Output VARIABLES DESCRIPTION: A sequential array of document pointers (ien). SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Text Integration Utilities grants Imaging permission to call several modules in routine TIUSRVPL. DBA Comments: 9/20/12-MM: Imaging team requested typo correction in ICR #3566. GETILIST should be GETILST. Change made to General Description and Component name. Typo found during review of MAG*3.0*135. DATE/TIME EDITED: SEP 20, 2012@13:42 ACTION: CONTENT CORRECTED AT THE REQUEST OF: RENEE,JOLIE WITH CONCURRENCE OF: MCCLENEHAN,MARGY NUMBER: 3567 IA #: 3567 DATE CREATED: APR 26, 2002 CUSTODIAL PACKAGE: IMAGING CUSTODIAL ISC: Washington USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: MAGGSIUI NAME: Imaging - MAGGSIUI ID: MAGGSIUI GENERAL DESCRIPTION: 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. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34543920 KEYWORDS: IMPORT API COMPONENT/ENTRY POINT: IMPORT COMPONENT DESCRIPTION: This API receives imported images from an application. The API will return an array indicating whether the transaction was successful or unsuccessful. VARIABLES: MAGRY TYPE: Output VARIABLES DESCRIPTION: The status of the call will be returned in an array. Two examples are given below. Example 1: Successful Queue MAGRY(0)="111^Data has been Queued." A Background Processor Import Queue Number '^' message is returned in the (0) node. No other nodes are defined. Example 2: unsuccessful Queue MAGRY (0)="0^Required parameter is null" MAGRY (1)="Tracking ID is Required. !" MAGRY (2)="Status Handler is Required. !" MAGRY (3)="Acquisition Site is Required. !" node (0) = 0 '^' Error message node(1..n)= all error messages incurred during validation. VARIABLES: IMAGES TYPE: Input VARIABLES DESCRIPTION: An array of fully qualified file names. Each entry is the full path of the Image using UNC notation, and optionally a short description of the Image as the second '^' piece. If the array entry doesn't contain a short description as the 2nd '^' piece, the API will generate a default image short description from the procedure and procedure date. All images in the array will be saved as a group of images. If the array only contains 1 image, it will be saved as a single image. The following is an example of an input array: IMAGES(1)="\\image server\image share\filename.ext^image description" IMAGES(2)="\\image server\image share\filename2.ext" IMAGES(3)="\\image server\image share\filename3.ext^image description" IMAGES(4)="\\image server\image share\filename4.ext" VARIABLES: MAGIX TYPE: Input VARIABLES DESCRIPTION: An array of predefined 'nodes' and data. Example: MAGIX("ACQD")="COMPUTER AT EDS" MAGIX("ACQL")=99 MAGIX("ACQS")=688 MAGIX("DOCCTG")=19 MAGIX("DOCDT")="05/05/1999" MAGIX("IDFN")=1033 MAGIX("STSCB")="TESTCB^MAGGSIUI" MAGIX("TRKID")="GK;101" The following are possible predefine nodes that can be passed; please note that the items with an asterick (*) are required information. ACQD* - Acquisition Device: 'Computer Name' of Device (Domain Name for non-NT). ACQL - Hospital Location: Pointer to VistA Hospital Location File. ACQS* - Acquisition Site: Pointer to VistA Institution File. ACQN* - Acquisition Site Station Number : This is the Value of field #99 in the Institution File (#4). (Note: Either ACQN or ACQS is required, An error will be returned if the calling Application sends values for both) CDUZ - DUZ of person capturing the image. CMTH - Call Method: A Method to call that will generate the image(s) (Note: Either an 'Image Array' or a 'Call Method' is required). DFLG - Delete Flag: '1' if images should be deleted after successful processing (The default is '0', No Deletion). DOCCTG - Document Category: Pointer to VistA MAG DESCRPTIVE CATEGORIES file. (Note: VistA Imaging is discontinuing the use of this Field. In a future version of the Import API, the MAG DESCRIPTIVE CATEGORIES (#2005.81) file will no longer be used as a description of the Image and will not be accepted as a value in the Input Array. The new index fields: IXTYPE, IXSPEC, IXPROC, IXORIGIN will be used for describing an Image.) DOCDT - Document Date: (FileMan External or Internal Date) IXTYPE* - Type Index: Internal or external entry in the IMAGE INDEX FOR TYPES (#2005.83) file. (Note: IXTYPE and DOCCTG cannot both be included in the input array.) IXSPEC - Specialty/SubSpecialty Index: Internal or external entry in the IMAGE INDEX FOR SPECIALTY/SUBSPECIALTY (#2005.84) file. IXPROC - Procedure/Event Index: Internal or external entry in the IMAGE INDEX FOR PROCEDURE/EVENT (#2005.85) file. IXORIGIN - Origin Index: Set of codes that describe where the image was produced. Possible values are VA, NON-VA, FEE and DOD. (Not required. It will default to VA). GDESC - Short Description for the Image or Image Group (60 chars) IDFN* - VistA Patient DFN IMAGE - Full path of image in UNC notation ^ Optional Image Description ITYPE - Image Type: The type of image (file extension); please consult Imaging for the different file types currently supported. PASSWORD - Encrypted Password for the network\machine where the import image is located. PXDT - Procedure Date/Time (FileMan External or Internal Date Time) PXIEN - Procedure IEN PXPKG - Procedure Package STSCB* - Status Handler: "Tag^Routine" of initiating package. Imaging will call this to return the resulting status of the Import process. TRKID* - Tracking ID = PackageID_;_unique identifier Example: "DOC;453" TRTYPE - Transaction Type: 'NEW' or 'MOD' or 'DEL' (TRYTPE is for Future use. Any value is ignored, it defaults to 'NEW'.) USERNAME - Username for the network or machine where the import image resides. SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Hines SUBSCRIBING DETAILS: Clinical Procedures is using the Imaging Import Component to import images from a Medical device into the VistA database. NUMBER: 3568 IA #: 3568 DATE CREATED: AUG 07, 2003 CUSTODIAL PACKAGE: TEXT INTEGRATION UTILITIES CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: TIUCP NAME: DBIA3568 ID: TIUCP GENERAL DESCRIPTION: Clinical Procedures API(s) STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 36855478 COMPONENT/ENTRY POINT: LNGCP COMPONENT DESCRIPTION: This API returns a longlist of titles for the Clinical Procedures CLASS. VARIABLES: Y TYPE: Output VARIABLES DESCRIPTION: Array of 44 nearest Titles to that indicated by the user in the direction passed. VARIABLES: FROM TYPE: Input VARIABLES DESCRIPTION: Reference Titles from which the longlist is scrolling. VARIABLES: DIR TYPE: Input VARIABLES DESCRIPTION: Direction from which the longlist is scrolling from the reference Title. COMPONENT/ENTRY POINT: ISCP COMPONENT DESCRIPTION: This API returns a true/false whether the TIU title is under the Clinical Procedures class. VARIABLES: TITLE TYPE: Input VARIABLES DESCRIPTION: The IEN for TIU Document Definition file (#8925.1). VARIABLES: TIUY TYPE: Output VARIABLES DESCRIPTION: Return value is 1 or 0; a one will indicate that the input value (TITLE) is defined as a Clinical Procedure. COMPONENT/ENTRY POINT: ISHISTCP COMPONENT DESCRIPTION: Return value is 1 or 0; a one indicates that the title exists under Document Class Historical Procedures. VARIABLES: TITLE TYPE: Input VARIABLES DESCRIPTION: The IEN of a Title in the TIU Document Definition file (#8925.1). COMPONENT/ENTRY POINT: CPCLASS COMPONENT DESCRIPTION: Gets the IEN for entry CLINICAL PROCEDURES in the TIU Document Definition file (#8925.1) VARIABLES: Y TYPE: Both VARIABLES DESCRIPTION: Returns either the CLINICAL PROCEDURES TIU Document file (#8925.1) IEN or 0. SUBSCRIBING PACKAGE: CLINICAL PROCEDURES ISC: Hines SUBSCRIBING DETAILS: Clinical Procedures will use the LNGCP API to get a selectable longlist of TIU Document titles for Clinical Procedures. The Clinical Procedures Medicine Conversion will use the ISHISTCP API to determine whether a title is appropriate for a converted medicine report. SUBSCRIBING PACKAGE: IMAGING ISC: Washington/Silver Spring SUBSCRIBING DETAILS: Imaging is utilizing the ISCP^TIUCP (API) to determine the PACKAGE for the TIU note associated with an image captured. The IMAGE file (#2005) stores the PACKAGE field and is used during the filtering process of images on the display software. Imaging also uses CPCLASS. SUBSCRIBING PACKAGE: VIRTUAL PATIENT RECORD SUBSCRIBING DETAILS: Effective with VPR*1*0. DBA Comments: 08/02/13 DT: Added VPR as subscriber, effective with VPR*1*0. DATE/TIME EDITED: AUG 02, 2013@13:41 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: BUECHLER,MELANIE WITH CONCURRENCE OF: MCCLENAHAN,MARGY NUMBER: 3572 IA #: 3572 DATE CREATED: NOV 17, 2004 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Controlled Subscription TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWORB FASTUSER GENERAL DESCRIPTION: The Mental Health Assistant GUI (part of the Mental Health package) would like an agreement to use the ORWORB FAST USER remote procedure. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 39934800 SUBSCRIBING PACKAGE: AUTOMATED MED INFO EXCHANGE SUBSCRIBING PACKAGE: BAR CODE EXPANSION SUBSCRIBING DETAILS: As part of the Bar Code Expansion project, Care Fusion's wCareView software will give providers a read-only view of consolidated patient information in a similar fashion as the CPRS Cover Sheet. DBA Comments: JSH 2006-11-05/ Added BCE as a subscriber as per Tony Thompson/BCE and Rich Vertigan/OERR. DATE/TIME EDITED: NOV 05, 2006@10:31 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: THOMPSON,WILLIAM WITH CONCURRENCE OF: VERTIGAN,RICHARD NUMBER: 3574 IA #: 3574 DATE CREATED: MAY 13, 2002 CUSTODIAL PACKAGE: HEALTH LEVEL SEVEN USAGE: Controlled Subscription TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: HLCSLM NAME: HL7 LINK MANAGER ID: HLCSLM GENERAL DESCRIPTION: This routine manages various activities of the HL7 Link Manager. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34464718 KEYWORDS: HLCSLM COMPONENT/ENTRY POINT: STAT COMPONENT DESCRIPTION: This function checks the status of the LINK MANAGER, and returns a value of 1 if it is up, or a value of 0 if it is down. SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING ISC: Salt Lake City SUBSCRIBING DETAILS: Used in Remote Data Views. SUBSCRIBING PACKAGE: CLINICAL INFO RESOURCE NETWORK NUMBER: 3575 IA #: 3575 DATE CREATED: MAY 13, 2002 CUSTODIAL PACKAGE: CONSULT/REQUEST TRACKING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMRCTIU1 NAME: TIU use of GMRCTIU1 ID: GMRCTIU1 GENERAL DESCRIPTION: This integration agreement describes calls used by TIU in GMRCTIU1. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34485150 COMPONENT/ENTRY POINT: ROLLBACK(DA,TIUDA) COMPONENT DESCRIPTION: Roll-back a CT record when result is deleted or reassigned. VARIABLES: DA TYPE: Input VARIABLES DESCRIPTION: This required variable is the Request/Consultation file (#123) IEN. VARIABLES: TIUDA TYPE: Input VARIABLES DESCRIPTION: This required variable is the TIU Document file (#8925) IEN. SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING DETAILS: TIU calls ROLLBACK^GMRCTIU1 to roll-back the consult when a document associated with a consult is deleted or reassigned. NUMBER: 3578 IA #: 3578 DATE CREATED: MAY 15, 2002 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSRM NAME: DBIA3578 ID: GMTSRM GENERAL DESCRIPTION: 1) OPTION GMTS TYPE ENTER/EDIT will allow the CAC to Create and/or modified a Health Summary Report from the TIU HS Object Menu STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34495042 COMPONENT/ENTRY POINT: MAIN SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING DETAILS: NUMBER: 3579 IA #: 3579 DATE CREATED: MAY 15, 2002 CUSTODIAL PACKAGE: HEALTH SUMMARY CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: Routine DBIC APPROVAL STATUS: APPROVED ROUTINE: GMTSRI NAME: DBIA3579 ID: GMTSRI GENERAL DESCRIPTION: STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34495045 COMPONENT/ENTRY POINT: GMTSRI COMPONENT DESCRIPTION: No variables are being passed. SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City NUMBER: 3580 IA #: 3580 FILE NUMBER: 9000010 GLOBAL ROOT: AUPNVSIT( DATE CREATED: MAY 15, 2002 CUSTODIAL PACKAGE: PCE PATIENT CARE ENCOUNTER CUSTODIAL ISC: Albany USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: TIU use of Global AUPNVSIT(+VSIT,0) ID: AUPNVSIT( GLOBAL REFERENCE: AUPNVSIT( FIELD NUMBER: .01 FIELD NAME: VISIT/ADMIT DATE&TIME LOCATION: 0;1 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .07 FIELD NAME: SERVICE CATEGORY LOCATION: 0;7 ACCESS: Direct Global Read & w/Fileman FIELD NUMBER: .22 FIELD NAME: HOSPITAL LOCATION LOCATION: 0;22 ACCESS: Direct Global Read & w/Fileman GLOBAL REFERENCE: AUPNVSIT("AA", GLOBAL DESCRIPTION: Direct global read access is permitted. GENERAL DESCRIPTION: Direct global read of the 0th node of the Visit file (#9000010), $G(^AUPNVSIT(+VSIT,0)). STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34484202 SUBSCRIBING PACKAGE: TEXT INTEGRATION UTILITIES ISC: Salt Lake City SUBSCRIBING DETAILS: TIU does a direct global read of $G(^AUPNVSIT(+VSIT,0)) and looks at the 1st piece, 7th piece and 22nd piece to build what TIU calls the Visit String, VSTR, which has the following format: Hospital Location;Visit/Admit Date&Time;Service Category SUBSCRIBING PACKAGE: ACCOUNTS RECEIVABLE NUMBER: 3581 IA #: 3581 FILE NUMBER: 2 GLOBAL ROOT: DPT( DATE CREATED: MAY 16, 2002 CUSTODIAL PACKAGE: REGISTRATION USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: DIQ FOR DATE ENTERED INTO FILE AND ALIAS ID: DPT( GLOBAL REFERENCE: DPT( FIELD NUMBER: .097 FIELD NAME: DATE ENTERED INTO FILE LOCATION: 0;16 ACCESS: Read w/Fileman GLOBAL REFERENCE: DPT(D0,.01, FIELD NUMBER: .01 FIELD NAME: ALIAS LOCATION: 0;1 ACCESS: Read w/Fileman GENERAL DESCRIPTION: Master Patient Index VistA wil use GETS^DIQ to retreive the DATE ENTERED INTO FILE (#.097) and ALIAS (#1) fields from the PATIENT (#2) file, to be stored in an array and returned in a remote RPC call. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34469894 SUBSCRIBING PACKAGE: MASTER PATIENT INDEX VISTA EDITOR: CHESNEY,CHRISTINE M NUMBER: 3582 IA #: 3582 FILE NUMBER: 100 GLOBAL ROOT: OR(100, DATE CREATED: MAY 20, 2002 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING CUSTODIAL ISC: Salt Lake City USAGE: Private TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: INPATIENT CLEANUP ID: OR(100, GLOBAL REFERENCE: OR(100, FIELD NUMBER: 33 FIELD NAME: PACKAGE REFERENCE LOCATION: 4;1 ACCESS: Read w/Fileman FIELD DESCRIPTION: This information allows the package to link the order in OR with its more detailed order information in the individual package. It is the package's responsibility to define and determine the structure of this information. FIELD NUMBER: 5 FIELD NAME: STATUS LOCATION: 3;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: POINTER TO ORDER STATUS FILE (#100.01). FIELD NUMBER: 21 FIELD NAME: START DATE LOCATION: 0;8 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the start date/time of the order. FIELD NUMBER: 22 FIELD NAME: STOP DATE LOCATION: 0;9 ACCESS: Read w/Fileman FIELD DESCRIPTION: This is the stop date/time of the order. STATUS: Active DURATION: Till Otherwise Agreed MAIL MESSAGE: 34516008 SUBSCRIBING PACKAGE: INPATIENT MEDICATIONS SUBSCRIBING PACKAGE: OUTPATIENT PHARMACY SUBSCRIBING PACKAGE: LAB SERVICE DBA Comments: 4/20/12 - Jamie Crumley is the developer for both CPRS and Lab for the LSRP project. She has requested to add Lab as a subscriber to this ICR. Access to these fields is necessary to move pending Lab orders to Cerner system. Patches are LR*5.2*393 and LR*5.2*383. 3/29/13-MM: Added comment regarding patch LR*5.2*393: LR*5.2*393 is part of the Laboratory System Re-engineering Project. This patch has been installed at the Huntington VAMC. As of 3/25/13, it is not known if or when the patch will be nationally released. There is also a possibility a different LR patch will release this functionality. DATE/TIME EDITED: APR 20, 2012@12:24 ACTION: SUBSCRIBER ADDED AT THE REQUEST OF: CRUMLEY,JAMIE WITH CONCURRENCE OF: CRUMLEY,JAMIE NUMBER: 3583 IA #: 3583 DATE CREATED: MAY 21, 2002 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORBCMA5 GETUDID REMOTE PROCEDURE: ORBCMA5 GETUDID ORIGINAL NUMBER: 3583 GENERAL DESCRIPTION: Get Unit/Dose Order Dialog Form ID for BCMA V2.0 RPC: GETUDID^ORBCMA5 STATUS: Active MAIL MESSAGE: 34526710 KEYWORDS: ORBCMA5 SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING DETAILS: Get Unit/Dose Order Form ID which used for BCMA V2.0 NUMBER: 3584 IA #: 3584 DATE CREATED: MAY 21, 2002 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORBCMA5 GETIVID REMOTE PROCEDURE: ORBCMA5 GETIVID ORIGINAL NUMBER: 3583 GENERAL DESCRIPTION: Get IV Order Dialog Form ID for BCMA V2.0 RPC: GETIVID^ORBCMA5 STATUS: Active MAIL MESSAGE: 34526713 KEYWORDS: ORBCMA5 SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING DETAILS: Get IV Order Form ID which used for BCMA V2.0 NUMBER: 3585 IA #: 3585 DATE CREATED: MAY 21, 2002 CUSTODIAL PACKAGE: ORDER ENTRY/RESULTS REPORTING USAGE: Private TYPE: Remote Procedure DBIC APPROVAL STATUS: APPROVED NAME: ORWUBCMA USERINFO REMOTE PROCEDURE: ORWUBCMA USERINFO ORIGINAL NUMBER: 3583 GENERAL DESCRIPTION: Get the relevant information of current user for BCMA V2.0 RPC: USERINFO^ORWUBCMA STATUS: Active MAIL MESSAGE: 34526715 KEYWORDS: ORWUBCMA SUBSCRIBING PACKAGE: BAR CODE MED ADMIN SUBSCRIBING DETAILS: Get relevant information for current user which is needed by BCMA V2.0. NUMBER: 3586 IA #: 3586 DATE CREATED: MAY 22, 2002 CUSTODIAL PACKAGE: VA FILEMAN CUSTODIAL ISC: San Francisco USAGE: Private TYPE: Other DBIC APPROVAL STATUS: APPROVED NAME: New Style Xref and Fileman Variables GENERAL DESCRIPTION: The HUI Project is using a new style cross-reference, type Action and is executed at the Record level. In the routine XUHUI the following Fileman array/variables are being read: DIFILE() to get the file and sub-file numbers and pass them on in a name spaced variable XUHUIFIL(). DIFLD() to get the field(s) and pass them on in a name spaced variable XUHUIFLD(). DA() to get the IEN(s) and pass them on in a name spaced variable XUHUIDA(). The being used is as follows: ZL XUHUI ZP S2:S2+6 S2 ;Section 2 N XUHUIFIL,XUHUIFLD,XUHUIDA,XUHUIX,XUHUIX1,XUHUIX2 S XUHUIFIL=DIFILE ;File # I $D(DIFLD) M XUHUIFLD=DIFLD ;Field # I '$D(DIFLD) S XUHUIFLD="" S XUHUIXR=$G(XUHUIXR) M XUHUIDA=DA ;IEN(s) of record It is realized some of these variables may be undefined or null and that Fileman reserves the right to changed the variables. It is with this intent that it would be nice if a notice was given to the XUHUI* developer that these are being changed so that patch coordination can happen. STATUS: Active MAIL MESSAGE: 34524851 SUBSCRIBING PACKAGE: KERNEL ISC: Oakland NUMBER: 3587 IA #: 3587 FILE NUMBER: 3.51 GLOBAL ROOT: XMB(3.51, DATE CREATED: MAY 23, 2002 CUSTODIAL PACKAGE: KERNEL CUSTODIAL ISC: San Francisco USAGE: Controlled Subscription TYPE: File DBIC APPROVAL STATUS: APPROVED NAME: SPOOLED HEALTH SUMMARY DOCUMENT ID: XMB(3.51, GLOBAL REFERENCE: XMB(3.51, FIELD NUMBER: 2 FIELD NAME: STATUS LOCATION: 0;3 ACCESS: Read w/Fileman FIELD DESCRIPTION: Status is checked of a spooled document. When ready (r) then the document is transmitted via the PDX package. FIELD NUMBER: 8 FIELD NAME: NUMBER OF LINES LOCATION: 0;9 ACCESS: Read w/Fileman FIELD DESCRIPTION: The number of lines is checked pri